Creating a BMC Server Automation Deploy Job or an application component template

This topic provides high-level guidelines for creating a BLPackage Deploy Job or an application component template. It contains the following sections:

In the server provisioning process, you can choose between creating and publishing a BLPackage Deploy Job or an application component template. Because the BLPackage Deploy Job supports blueprint parameterization and the application component template does not, BMC recommends that you create a BLPackage Deploy Job.

For detailed information, see the following topics in the BMC Server Automation documentation:

Before you begin

If you plan to create a BLPackage Deploy Job, use BMC Server Automation to create BLPackages that can be used to install application on target virtual machines. A BLPackage can include installers, files, configuration objects, and so on.

If you plan to create an application component template, use BMC Server Automation to create Software Deploy Jobs to install applications on target virtual machines.

To create a BLPackage Deploy Job

A BLPackage is a collection of server assets, software packages, and an XML instruction set. The BLPackage includes parameterized property values among its server assets. The parameterized property values must match exactly the blueprint parameter values used by the service blueprint.

Unknown macro: {multi-excerpt}

Log in to BMC Server Automation.
Click Depot.
Open the BLPackage that requires a local property for editing.
Click the Local Properties tab to add a local property to the BLPackage. In this example, HTTP_PORT is used.
Click Add .
Define the local properties that are used to parameterize the BLPackage.
For example, you can add a local property called HTTP_PORT that you will use with service blueprint.

Note

The name you assign to the local property must exactly match the name in the service blueprint.
In the example shown above, HTTP_PORT has a default value of 80. When end-users request an offering from the Service Catalog, they can change the default HTTP port from 80 to the port number they require.
Use the local properties as parameters you can pass in to the deployment of your application.
1. If the required object (file, configuration setting, registry key) does not already exist in the BLPackage, you must first import that server object into the BLPackage.
2. Parameterize the file by editing the BLPackage (for example, changing the object attributes).
Click the Package tab.
Select the new server object that you imported into the BLPackage.
Create a BLPackage Deploy Job that deploys the BLPackage that you parameterized.

You must create the job in the CSM_Applications subfolder of the Jobs folder.
You can click the Package tab to view the local properties that you parameterized. Make sure the BMC Cloud Lifecycle Management administrator knows these parameters.
Set the following extended properties in the BLPackage Deploy Job:
- PRODUCT_MANUFACTURER
- PRODUCT_NAME
- PRODUCT_VERSION
  These values are written to the DML and you can view them later in the service blueprint under the Software Packages tab.
Execute the Publish Product Catalog Job to update the DML with your new object.

All the Deploy Jobs where you set the PRODUCT_MANUFACTURER, PRODUCT_NAME, or PRODUCT_VERSION properties in the CSM_Application folder are published to BMC Cloud Lifecycle Management cloud database.
Note

A Publish Product Catalog Job is automatically created during installation in the CSM_Publish_Product_Catalog folder.
You can ignore warnings about Patch Catalog and Compliance templates.

Where to go from here

You now can use this parameterized BLPackage inside the service blueprint.

Note

The service blueprint parameter name must match exactly with the BLPackage local property.

For more information, see Configuring service blueprint parameters, especially To configure parameters.

To create a new application component template

In the BMC Server Automation Console, select the CSM_Application_Packages subfolder of the Component Templates folder.
Right-click and select New > Component Template to display the Create New Component Template wizard.
Under Allowed Operations, select Deploy.
In Step 3 of the wizard, enter values for the following properties:
Property
Value
PRODUCT_MANUFACTURER
Enter the manufacturer's name.
PRODUCT_VERSION
Enter the product version number.
ATRIUM_SYNC_ENABLED
Set to True.
Complete the wizard, and click Finish.

To create a Component Discovery Job

Select the newly created component template. Right-click and select Discover to open the New Component Discovery Job wizard.
Complete the relevant panels in the Component Discovery Job wizard.

To create a Batch Job

Choose an appropriate subfolder in the Jobs folder.
Right-click select New > Batch Job to display the New Batch Job dialog box.
Add the Software Deploy Job to the sequence of jobs in the Batch Job, and then add the Component Discovery Job after it. Do not place the Component Discovery Job first in the job sequence.
Complete the wizard and click Finish.

To add the Batch Job to the application component template.

Open the newly created component template, and choose the Install/Uninstall tab.
Add the newly created Batch Job to the Installer Batch Job and/or Uninstaller Batch Job field.
Save the updated component template.

Property	Value
`PRODUCT_MANUFACTURER`	Enter the manufacturer's name.
`PRODUCT_VERSION`	Enter the product version number.
`ATRIUM_SYNC_ENABLED`	Set to True.