Entering PaaS resource provider registration information

This topic continues the process described in Registering resource providers.

The procedures describe how to set up the generic platform-as-a-service (PaaS) resource provider for BMC Cloud Lifecycle Management and then how to add a proxy provider such as the BDA-Paas provider to enable provisioning based on BMC Database Automation capabilities. You can also add a generic public PaaS and add Cloud Foundry or a custom provider as a proxy provider.

This topic contains the following sections:

To register a PaaS resource provider

Access the Register Provider dialog box and then perform the following procedure:

1. Select the resource provider type to register:
   • PAAS: Select this option for a generic on-premises resource provider. (This option is a prerequisite for BMC Database Automation.)
   • Public PAAS: Select this option for a generic public cloud. (This option is a prerequisite for Cloud Foundry or a custom provider you create).
     
     
2. (PaaS only) Enter the following information:
   • Name—Name for this instance of the PaaS provider.
   • Description—Useful description of the provider. Descriptions can help you distinguish provider instances and find a provider when using Search.
   • Supported resource types cache refreshment interval (seconds)—Value that controls the frequency by which the PaaS provider refreshes its cache of supported resource types. The child providers of the PaaS provider determine what resource types are supported. The set of types supported by each child provider can change over time, so the PaaS provider's cache of supported resource types can also change.
   • Use built-in pool placement logic—Option that indicates custom pool placement logic is necessary and is being implemented as a third-party provider that is a child of the PaaS provider.
   • Use built-in resource placement logic—Option that indicates custom resource placement logic is necessary and is being implemented as a third-party provider that is a child of the PaaS provider. Capacity-based placement is an example of custom resource placement logic.
    

3. (PublicPaaS only) Enter the following information: 

   • Name—Name for this instance of the PaaS provider.
   • Description—Useful description of the provider. Descriptions can help you distinguish provider instances and find a provider when using Search.
    

4. Click Submit.

_{Back to top}

To register BMC Database Automation as a proxy resource provider

From the Register Provider dialog box, perform the following procedure:

1. Select BDA-PaaS as the resource provider type to register.
   
   
2. Enter the following information:
   
   • Name—Name for this instance of a PaaS BMC Database Automation provider.
   • Description—Useful description of the provider. Descriptions can help you distinguish provider instances and help you find a provider by using Search.
   • Host—BMC Database Automation Manager host name.
   • Port—Simple Object Access Protocol (SOAP) port used for communicating with BMC Database Automation. Change this value only if you have changed the port value in the mdf.conf file in BMC Database Automation Manager.

   • Username—User for BMC Database Automation.
      

     Note

     Use the default system admin credentials (like sysadmin) or application-specific credentials for registering the BDA Provider instead of a domain-based user for the registration. 
   • Password—User's password for BMC Database Automation.
   • SSL—Value to enable SSL when communicating with the API for BMC Database Automation. Enter True.
   • Allow Self Signed Certificates—Value that allows use of self-signed certificates without setting up a Java keystore. All host name validation and other security mechanisms are disabled. Typically, this option is only used to test an SSL connection. Enter True.
   • Job Polling in seconds—Interval at which the status of a job in BMC Database Automation is checked.
   • Verify Polling in seconds—Interval at which the status of the init-verify portion of a job in BMC Database Automation is checked.
   • Refresh Cache Interval in seconds—Interval at which BMC Cloud Lifecycle Management queries BMC Database Automation for objects to be onboarded.
   • Supported Types Refresh in seconds—Refresh interval for products that BMC Database Automation offers for provisioning.
   • Auto Enable Oracle Permission Fixing—Value to enable automatic fixing of permission issues that can be encountered in Oracle if different users exist for a cluster/grid versus a database. Enter True.

   • Auto Increment Oracle Listener Port—Value to automatically increase the TCP/IP port on which the listener should listen. Enter True.

     Note

     If you are registering an Oracle RAC or Oracle Restart provider, set the option to False.

   • Disable Provisioning Rollback—Value to disable the automatic removal of a database that failed to provision. Preventing automatic removal can be useful when failures occur and you want environments left intact for investigation. Enter True.
   • Target Availability Polling in seconds—Interval for checking whether an external ID is currently involved with a job.
    

3. Click Submit.

_{Back to top}

To register Cloud Foundry as a proxy resource provider

From the Register Provider dialog box, perform the following procedure:

1. Select PublicPaaSCloudFoundry as the resource provider type to register.
   
   
2. Enter the following information:
   
   • Name—Name for this instance of a PaaS Cloud Foundry provider.
   • Description—Useful description of the provider. Descriptions can help you distinguish provider instances and help you find a provider by using Search.
   • Host URL—URL used to connect to the Cloud Foundry host. You can enter the default URL (https://api.run.pivotal.io), or, if Cloud Foundry is hosted on your on-premises environment, you can enter your own URL.
   • Retry Count—Number of allowable attempts to access the host.
   • Retry Interval—Interval (in seconds) between each retry.
    

3. Click Submit.

After performing these procedures, you can onboard resources, as described in Onboarding and offboarding PaaS resources.

_{Back to top}