Overview of the BMC Cloud Lifecycle Management integration

BMC Database Automation (BDA) version 8.9.00 is certified with BMC Cloud Lifecycle Management (CLM) 4.1 Patch 7.  

Note

For this compatibility to work, apply the Hotfix that contains the updated BDAPaasProvider.jar as mentioned here.

BDA version 8.9.00 is also certified with BMC CLM 4.6.04 with the Hotfix from Knowledge Articles 000128785 and 000128786

This is a direct integration with CLM and does not require installation of any other products, components, or agents. You can use existing templates in BDA and, after publishing the templates to the CLM product catalog, you can create Oracle RAC, Restart-enabled, or single database instances with every service in CLM and can share those instances across multiple services. This ability to provision a solution stack on top of a platform is known as platform as a service (PaaS).

Each of the supported database types are selected as resources that you can onboard to CLM using a registered BDA provider. By defining input parameters directly in CLM, the provider directs CLM where to obtain the resources from BDA in order to provision the database using PaaS. Once you onboard the PaaS resource, you can then create a service blueprint that enables you to request that instances, nodes, or a database are added or removed to or from the new environment.

For BDA to integrate with CLM, you must first ensure that certain prerequisites are met.

Benefits of the integration

The integration enables you to reduce the number of database servers and setup requests for new database instances to be created on a smaller set of shared database servers. You can share those databases amongst other services while leveraging the existing CLM environment. You can also run custom Actions after the database is deployed (for example, loading data in a database or deploying application schemas). The integration increases the standardization of database instance configurations in the estate, reducing database licensing and support costs. 

User example

The following table depicts a typical scenario where certain roles leverage the integration to implement PaaS:

RoleProductStep
Database AdministratorBDA

Installs and configures a database server environment (clustered or standalone)

Database AdministratorBDAUses templates in BDA to create database instances in the database server environment
Cloud AdministratorCLMOnboards and pools the database server environments
Cloud AdministratorCLMDesigns service offerings that include new database instances (based on templates) on the shared database server infrastructure
UserCLMRequests instances of the services and utilizes the database instances in the same environment

Supported databases

BDA supports PaaS provisioning on the following Oracle databases and OS platform versions:

  • Database Versions
    • 11.2.0.1
    • 11.2.0.2
    • 11.2.0.3
    • 11.2.0.4
    • 12.1.0.1 
    • 12.1.0.2

Note

BDA supports creating a Container Database (CDB) only for database versions 12.1.0.1 and 12.1.0.2. You can create a CDB database for a single instance, RAC, and Restart.

  • Platforms
    • x86
    • x86_64
  • OSs
    • RHEL5 (single instance, Restart-enabled, and RAC)
    • RHEL6 (single instance, Restart-enabled, and RAC)
    • Windows 2008R2 (single instance only)

 Process for using PaaS provisioning

Tip

If you are preparing the integration for the first time, start with the BMC Cloud Lifecycle Management documentation which describes where most of the end-to-end provisioning tasks will take place.

    Before you integrate BDA with CLM, ensure that pre-configuration requirements are met.

    1. Configure the settings BDA uses to connect to CLM that enables the integration.
    2. Provide configuration parameter values to enable a connection between BDA and BMC Atrium CMDB.
    3. Register the BDA-PaaS provider to tell CLM where to obtain resources needed for provisioning.

    Publish templates to the Product Catalog and use them to provision servers with databases on them by adding the template details to CLM blueprints.

    Define actions in BDA and publish them to the Product Catalog.

    The final tasks for setting up and using PaaS are performed the BMC Cloud Lifecycle Management documentation .

    1. Prepare BMC Database Automation as an onboard resource when performing PaaS provisioning in CLM.
    2. Set up service blueprints that enable you to request that standalone nodes, databases, and RAC clusters be added or removed to or from the onboarded environment.

    Where to go next

    Enable the integration with BMC Cloud Lifecycle Management

    Was this page helpful? Yes No Submitting... Thank you

    Comments