Creating a BMC BladeLogic Deploy Job to deploy a BMC BladeLogic Package

A BMC BladeLogic Deploy Job is used to deploy one or more files, including software, stored in the BMC Server Automation Depot on one or more servers. Deploying multiple files requires the use of a BMC BladeLogic Package to collect those files and related changes for configuration objects, applications, and files. The deploy job uses the package to execute those changes on the target servers. The package is copied to the target servers, and the instruction-set that is built into the package is executed.

To create a Deploy Job, you must know the ID of the folder in which you want to create the job and the database key (DBKey) of the BMC BladeLogic Package. A single workflow can be created to obtain the ID and DBKey and create the Deploy Job.

Using TrueSight Orchestration Development studio to create a new module and a new process in the module

To obtain the ID

1. Create a called process:
   1. From the BMC_BladeLogic-AD-Operations_Manager module, choose v7.42=> JobGroup > Group Name to ID.

   2. Drag and drop the Call Process activity between Start and Endactivities, as shown in the following figure.

      

       

      Success

      Tip

      To view the complete path of the called process, place your cursor over the Call Process activity.

2. Determine the required inputs for the called process:

3. Double-click the Group Name to ID called process to display the Propertypanel.

   Property panel for the JobGroup:Group Name to ID called process

   

    

4. In the Call Process Input Mapping pane, review the values in the Output Name column. Write down all the output names that are required. In this example, groupName is the only output name that is required.
5. Click Cancel to close the Property panel.
6. Create an input parameter for the value to be mapped.
   1. Double-click on the Start activity to display the Property panel.
   2. Click Add to insert an Input Parameter entry.
   3. Double-click the field under the Input Parameter Name column and type groupName in the field.
       This name is displayed when the process is tested or executed.
   4. Double-click in the Context Name field to launch the Context Browser.
   5. Click Add Context to open the Create Context Data window.
   6. Type a name for this Context Item (for example groupName), and then click OK.
   7. In the Context Browser, double-click the newly created Context Item. The Context Item automatically populates the Property panel of the Start Activity.

   8. Select the check box in the Required?column, as shown in the following figure.

      

   9. Click OK to save the input parameter.
7. Map the inputs on the called process:
   1. Double-click the Group Name to ID called process to display the Property panel.
   2. Double-click the Input Type column for the groupName row.
   3. From the Parameter type menu, select Context item.
   4. To launch the Context Browser, click Context Browser .
   5. In the Context Browser, double-click the groupName entry.
   6. Click OK to close the detail panel and display the Property panel.
       The groupName Context Item defined on the Start activity is now mapped to the groupName input for this called process.

1. Map the value returned for the ID to a Context Item:
   1. In the Call Process Output Mapping pane of the Property panel, double-click the Output Name column for the ID row to display the detail pane.
   2. From the Parameter type menu, select Context item.
   3. Click the Context Browser symbol .
   4. Click Add Context to open the Create Context Data window.
   5. Type a name for this Context Item (for example ID), and then click OK.
   6. In the Context Browser, double-click the ID entry.
   7. Click OK to close the detail panel and display the Property panel.
      The ID value returned by this called process is now mapped to a Context Item. This Context Item can be used as an input for a subsequent called process in this workflow.
   8. Click OK to save the mappings.
2. Test the process and debug as required.
   For more information about these functions, see Called-processes.

To obtain a database key (DBKey)

1. Add a called process to the existing workflow:
   1. From the BMC_BladeLogic-AD-Operations_Manager module, choose v7.42 => BlPackage => Get DB Key by Group and Name.
   2. Drag the Call Process Activity to the right of the Group Name to ID called process.
2. Determine the required inputs for the called process:
   1. Double-click the Get DB Key by Group and Name called process to display the Propertypanel, as shown in the following figure:

1. 
   
   1. In the Call Process Input Mapping pane, review the values in the Output Name column. Write down all the output names that are required. In this example, parentGroup and packageName are the only output names that are required.
   2. Define these inputs using the method described in step 3 in the previous procedure.
2. Map the required inputs on the Get DBKey by Group and Name called process using the method described in the previous procedure.
3. Map the value returned for the DBKey to a Context Item:
   1. In the Call Process Output Mapping pane, double-click the Output Name column for the DBKey row to display the detail pane.
   2. Use the method described in  Step 5 in the previous procedure.
       The Property panel for Get DB Key by Group and Name contains mappings.

1. Click OK to save the mappings and test the process and debug, as required.

To create and deploy a job using the ID and DBKey

1. Add a called process to the existing workflow:
   1. From the BMC_BladeLogic-AD-Operations_Manager module, choose v7.42 => DeployJob => Create Deploy Job.
   2. Drag the Call Process activity to the workflow.
2. Determine the required inputs for the called process:
   1. Double-click the Create Deploy Job called process to display the Property panel, as shown in the following figure:

1. 
   
   1. Use the method described in Obtaining the ID to define the following inputs on the Startactivity:
      • deployJob Name 
      • serverName
      • isSimulateEnabled
      • isCommitEnabled
      • isStagedIndirect 
2. Map the inputs using the method described in Obtaining the ID. These mappings uses Context Items defined on the Start activity and Context Items mapped to values for the ID and DBKey in the preceding called processes.
3. Test the process and debug as required.  Your completed process should contain the called processes as illustrated in the following figure: