Enabling integration with BMC Cloud Lifecycle Management

You can integrate BMC Cloud Lifecycle Management (CLM) with BMC Database Automation (BDA) as explained in this topic.

Integration prerequisites

Best practice

Review the BDA – CLM certification matrix to ensure that a certified BDA version is being used for the integration.

Before you integrate BDA with CLM, ensure that the following requirements are met:

Your BDA managers are running Red Hat Enterprise Linux version Red Hat 5.5 and later. If you are running a version earlier than 5.5, CLM components will not install.
BDA agents are installed on all the servers that will be used for the integration.
You have installed the following RPMs required for the integration with CLM:

clarity-clm-content (imports the create user Action)
clarity-clm-components
clarity-jre

To install the RPMs, type the following option at the end of the install.sh script:
--clm
For more information about installing BDA, see Installing the Manager software in a stand-alone configuration.
Ensure that you have CLM Administrator capabilities. This enables you to create and administer CLM templates. Paired with the Edit Template capability, the CLM Administrator capability also enables you to perform the following activities:
- Publish
- Enable
- Disable
- Edit

You do not need CLM Administrator capabilities to clone, export, or view a published template.

Tip

The Create-Oracle-Master-Database-User Action is imported when the --clm option is passed to install.sh or update.sh. It can be specified as a post-provisioning Action for Create Database jobs if you want to Create a Database user. When provisioning from CLM, use this as a master account to log on to the Oracle database if you do not have access to the server on which you created the database.

If you plan to provision Oracle databases that include service names, ensure that enable_oracle_service_names is set to true in the /app/clarity/dmanager/etc/d2500_config file on the BDA Manager:

enable_oracle_service_names=true

This enables the provisioning of service names for new databases.
Note

Any existing databases - including those on which the service name was set in the template when the database was provisioned - will not include service names.
See OS requirements for additional requirements for the Manager.

Notes

Integration with CLM is not currently supported on Multi-Manager configurations.

The JVM server stops when you stop the MTD service. See the following example:

root@rh6-ma-170 /]# service mtd stop
SHARED_JVM server on port localhost:7891 stopped

The JVM server does not start again when you restart the MTD service.

[root@rh6-ma-170 /]# service mtd start
Starting mtd:                                              [  OK  ]
[root@rh6-ma-170 /]# /app/clarity/perl/bin/perl -MInline::Java::Server=status
SHARED_JVM on port localhost:7891 is not running

You must manually start the JVM server as shown in the following example:

[root@rh6-ma-170 /]# /app/clarity/perl/bin/perl -MInline::Java::Server=start
SHARED_JVM server on port localhost:7891 started with pid 32734

To enable the Application Programming Interface (API) listener

Open the /app/clarity/dmanager/etc/mtd.conf file.
Uncomment the following line:
service=static MtdApiSoapAcceptor "-c 2 -s 0 -p 8087 -k /app/clarity/dmanager/etc/server.key -x /app/clarity/dmanager/etc/server.pem -y /app/clarity/dmanager/etc/cacert.pem"
Note

If you enable SSL by setting –s to 1, you must also provide valid SSL server keys and certificates, or you will be unable to connect to the API.
Add the following line:
auth_mode=authentication
Save the file and close the editing session.
Enter the following command to restart the mtd service:
/etc/init.d/mtd restart

To enable the configuration

In the Management Console, select Configuration > CLM Configuration.
In the CLM Configuration page, populate the following fields and click Next.
- CLM Server Hostname—Name or IP address of the Cloud AR System server, where the Cloud database is installed.
- CLM Server Port—(Optional) Port used for communicating with the Cloud AR System server (for example, 0, or any other AR port).
- CLM Version—Version of CLM for connecting to the Cloud AR System server. This value is the CLM stack version (for example, 4.0, 4.1, or 4.6).
- CLM Username—User Name for the Cloud Administrator to connect to the Cloud AR System server. In order to publish and unpublish a template from CLM through the BDA Manager, this must be the super-user created during the CLM installation. A cloudAdmin user cannot unpublish a template.
- CLM Password—Password for connecting to the Cloud AR System server.
Click Test Connection.
Select Enable CLM.
When this option is disabled, the relevant GUI fields are not displayed.
Click Save Configuration.

Warning

Changing the configuration when templates have a status of Published can lead to inconsistency between the BDA template repository and the CLM Product Catalog.

To register the BDA-PaaS provider

Registering the BDA-PaaS provider tells CLM where to obtain resources needed for provisioning.

Note

Before you can register the BDA-PaaS provider, you must first set up the overall PaaS provider to enable provisioning in CLM. To do this, follow the steps in To set up the overall PaaS provider Open link .

To register the BDA provider, you must set parameters for the BDA-PaaS provider type in CLM.

To view a list of the parameters and their meaning, click here...

Parameter	Definition
Name	The name for this instance of a PaaS BDA 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 BDA Manager host name
Port	The Simple Object Access Protocol (SOAP) port for communicating with BDA. Change this value only if you have changed the port value in the mdf.conf file in the BDA Manager.
Username	The user for BDA
Password	The user's password for BDA
SSL	Select true from the menu to enable SSL when communicating with the API for BDA.
Allow Self Signed Certificates	Select true from the menu 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 BDA is checked
Verify Polling in seconds	The interval at which the status of the init-verify portion of a job in BDA is checked
Refresh Cache Interval in seconds	The interval at which CLM queries BDA for objects to be onboarded
Supported Types Refresh in seconds	The refresh interval for products that BDA offers for provisioning
Auto Enable Oracle Permission Fixing	Select true from the menu 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	Select true from the menu to automatically increase the TCP/IP port on which the listener should listen. Note: If you are registering an Oracle RAC or Oracle Restart provider, this option should be set to False.
Disable Provisioning Rollback	Select true from the menu 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

For more information, see To set up the overall PaaS provider Open link .

Note

Currently, the only available PaaS provider is BDA.

Where to go next

Publish the templates to the Product Catalog