×
 
 
  •  
$helper.renderConfluenceMacro('{bmc-global-announcement:$space.key}')

Unsupported content

 

This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.
BMC Cloud Lifecycle Management 4.5 ... Administering the product Common administrator tasks Creating objects in BMC Server Automation

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. 

This topic contains the following sections:

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 applications 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.

This section provides high-level guidelines for creating a BLPackage Deploy Job. When you perform this procedure, you are creating software packages that you can use when defining an application in a service blueprint in BMC Cloud Lifecycle Management. Applications let you deploy software on VMs that you provision using the cloud.

Best practice: Because the BLPackage Deploy Job supports blueprint parameterization, BMC recommends that you create a BLPackage Deploy Job instead of using an application component template.

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

To create a BLPackage Deploy Job

BMC Server Automation BLPackages can be used to install applications on target virtual machines.

A BLPackage is a collection of server assets, software packages, and an XML instruction set. A BLPackage can include installers, files, configuration objects, and so on. The BLPackage can also include parameterized property values among its server assets. The parameterized property values must match exactly the blueprint parameter values used by the service blueprint.

  1. Log on to BMC Server Automation.
  2. Click Depot.
  3. Open the BLPackage that requires a local property for editing.
  4. Click the Local Properties tab to add a local property to the BLPackage. In this example, HTTP_PORT is used.
  5. Click Add .

  6. 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 a 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.

  7. 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).

  8. Click the Package tab.

  9. Select the new server object that you imported into the BLPackage.

  10. Create a BLPackage Deploy Job that deploys the BLPackage that you parameterized.

  11. Create the job in the CSM_Applications subfolder of the Jobs folder. Click the Package tab to view the local properties that you parameterized. Make sure the BMC Cloud Lifecycle Management administrator knows these parameters.

  12. Set the following extended properties in the BLPackage Deploy Job:

    • PRODUCT_MANUFACTURER

    • PRODUCT_NAME

    • PRODUCT_VERSION
      These values are written to the Product Catalog and can be found later when adding software packages to the service blueprint.

  13. Execute the Publish Product Catalog Job to update the Product Catalog with the new object.

    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.

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.

You now can use this parameterized BLPackage by adding it to an application in a service blueprint.

Note

A service blueprint parameter name must exactly match the name of a BLPackage's local property.

For more information about using parameters in a BLPackage, see Configuring service blueprint parameters, especially To configure parameters. For more information about adding applications to a service blueprint, see Creating, copying, or editing a service blueprint, especially To add and define applications in a service blueprint.

To create a new application component template

  1. In the BMC Server Automation Console, select the CSM_Application_Packages subfolder of the Component Templates folder.
  2. Right-click and select New > Component Template to display the Create New Component Template wizard.

  3. Under Allowed Operations, select Deploy.

  4. 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.


  5. Complete the wizard, and click Finish.

To create a Component Discovery Job

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

To create a Batch Job

  1. Choose an appropriate subfolder in the Jobs folder.
  2. Right-click and select New > Batch Job to display the New Batch Job dialog box.

  3. 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.
  4. Complete the wizard and click Finish.

To add the Batch Job to the application component template.

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

  3. Save the updated component template.

Where to go from here

Publishing the Product Catalog

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Last modified by Lisa Greene on Jul 27, 2016
deploy_job application_component_template bmc_server_automation

Comments

Log in or register to comment.

Creating a system package in BMC Server Automation
Publishing the Product Catalog
© Copyright 2024 BMC Software, Inc.
Legal notices

Powered by Atlassian Confluence and Scroll Viewport

© Copyright 2005-2024 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.