Entering PaaS resource provider registration information

This procedure 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 add the BDA-Paas provider to enable provisioning based on BMC Database Automation capabilities. 

Currently, BMC Database Automation is the only platform-as-a-service (PaaS) resource provider that BMC Cloud Lifecycle Management offers. 

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 PAAS as the resource provider type to register.
   
   
2. Enter the following information:
   
   • Name—Name for this instance of the PaaS provider.
   • Description—A 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)—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—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—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. Click Submit.

To register BMC Database Automation as a resource provider

Still using 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—A useful description of the provider. Descriptions can help you distinguish provider instances and help you find a provider by using Search.
   • Host—The BMC Database Automation Manager host name.
   • Port—The Simple Object Access Protocol (SOAP) port used for communicating with BMC Database Automation. Change this only if you have changed the port value in the mdf.conf file in BMC Database Automation Manager.
   • Username—The user for BMC Database Automation.

     NoteIt is recommended that you use the default system admin credentials (like sysadmin) or application specific credentials for registering the BDA Provider rather than using a domain based user for the registration.
   • Password—The user's password for BMC Database Automation.
   • SSL—Enter True to enable SSL when communicating with the API for BMC Database Automation.
   • Allow Self Signed Certificates—Enter True to allow 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.
   • Job Polling in seconds—The interval at which the status of a job in BMC Database Automation is checked.
   • Verify Polling in seconds—The interval at which the status of the init-verify portion of a job in BMC Database Automation is checked.
   • Refresh Cache Interval in seconds—The interval at which BMC Cloud Lifecycle Management queries BMC Database Automation for objects to be onboarded.
   • Supported Types Refresh in seconds—Specifies the refresh interval for products that BMC Database Automation offers for provisioning.
   • Auto Enable Oracle Permission Fixing—Enter True to enable automatic fixing of permission issues that can be encountered in Oracle if different users exist for a cluster/grid versus a database.
   • Auto Increment Oracle Listener Port—Enter True to automatically increase the TCP/IP port on which the listener should listen.

     NoteIf you are registering an Oracle RAC or Oracle Restart provider, this option should be set to False.
   • Disable Provisioning Rollback—Enter True 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.
   • Target Availability Polling in seconds—The interval for checking whether an external ID is currently involved with a job.
    
3. Click Submit.

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