Publishing templates to the Product Catalog

Templates can be published in the Product Catalog and then used to provision servers with databases on them by adding them to BMC Cloud Lifecycle Management (CLM) blueprints. The status of a template for use in PaaS provisioning can be viewed in the Template View page, accessed by clicking the CLM Templates tab on the Templates Repository page. Once a template has been published, it is no longer available in the default Templates tab. Users with CLM Administrator capabilities can edit the body of a template that has been added to the Product Catalog.

Before you begin

If necessary, add variables to a BDA template so those variables can be used as parameters in CLM. Note the exact name of each parameter.
You can set up your own parameters in a template, or you can choose from the following list of built-in parameters that are available for all templates.

For more information, see Using parameters in PaaS provisioning.

To publish BDA templates to the Product Catalog

1. From the Management Console main page, select Templates in the Context Frame.
   The Templates Repository page displays.
2. Click the CLM Templates tab.
   The CLM Templates Repository page displays. The Templates section displays all the templates that have been created for provisioning database instances in PaaS and their status. Entries in the Removal Templates section can no longer be published.

3. To filter the list of templates by associated database type, in the Template Repository Filter section, select a value from the Database list box and click Filter.

4. To filter the list of templates by associated wizard type, select a value from the Wizard list box and click Filter.

5. To search for a specific template, enter the template name in the Find Template field and click Find.
   To sort the list of templates by the values in a column, click on the header for that column.
   For example, clicking the PaaS header sorts the templates in order of Platform as a Service status.

6. In the PaaS column, locate the unpublished template corresponding to the instance you want to create.

   Alternatively, select View from the menu for the template and view the status for the template in the CLM Status row of the PaaS CLM Catalog Information section.

7. Select Catalog Options from the menu.
   The options that you can use for managing the templates in the CLM Product Catalog vary depending on the current status of the template, represented by icons in the PaaS column, as detailed in the following table:
   
   

   Icon	Meaning	Available options
   	Published - Enabled Added to the Product Catalog and published. Can be used in CLM blueprints	Set Offline Unpublish
   	Published - Disabled Added to the Product Catalog and published. Can be used in CLM blueprints after it is enabled	Enable Unpublish
   	Not Published Has not been added to the Product Catalog	Publish
   	Archived Added to the Product Catalog and not published. Cannot be used in CLM blueprints	None

8. In the CLM Catalog Options section, for an unpublished template in the PaaS Status row, select Publish from the menu.
9. Click Update CLM Catalog.

10. Click OK on the confirmation message page and confirm details on the verification page.

11. To no longer publish a template that has been published, select Unpublish.
    
    

    Note

    In order to unpublish a template from CLM through the BDA Manager, the user name entered in the CLM Username field of the CLM Configuration page must be the super-user created during the CLM installation. A cloudAdmin user cannot unpublish a template. 
    

12. To set a published and enabled template offline, select Set Offline.

To publish SQL Actions to the Product Catalog

CLM publishes template to the Product Catalog through a SQL Action which is used to add an application to a PaaS resource set. Actions are not added directly to the Product Catalog; rather they are referenced using the fully qualified path specified for the Action when you create it in BDA. You can then define parameters as name/value pairs in the blueprint and they get passed down to the SQL script to determine how Actions are run in your environment. you define the parameters as name/value pairs in the blueprint and they get passed down to the script. For more information on parameters used in CLM, see Using parameters in PaaS provisioning.

1. Log on to BDA as a Create Database user and navigate to the created Oracle database instance in the Grid.
2. From the Management Console main page, select Actions > Action Repository in the Context Frame.
3. In the Action Repository list, locate the Action that was imported to the repository when you installed or upgraded BDA (for example, Create-Oracle-Master-Database-User).
4. Select View from the menu for that Action.
5. In the Action View page, note the name of the Action in the Fully Qualified Name row and the container in the Container row (for example, /Create-Oracle-Master-Database-User).
6. Publish the Action in the Product Catalog Console in CLM.

Where to go next

1. Prepare BDA 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.

   Note

   When you set up the service blueprint in BMC Cloud Lifecycle Management, you are required to specify, among other properties, the name of the resource set. This name corresponds to the name assigned to the deployed database. The name that you specify must conform to the Oracle naming conventions for database provisioning. See Set up service blueprints for specific information about how to create and specify the details for the resource set.

   You will also be required to set up and add parameters to the resource set used in PaaS provisioning. This process requires defining SQL Actions in BDA, which contain specific environment variables used in the SQL Action. For more information, see Creating an Action and Actions environment variables.