Unsupported content 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.

Creating automation scripts

For every action that you want to perform in an external system (target) by using BMC Release Process Management, you must create an automation script. Once you have your automation scripts ready, you can use them in various steps of a request and then run the request.

To create an automation script

  1. Click the Environment tab and then click Automation.
  2. Click Create Automation on the right side of your screen.
  3. Select Automation in the To use as list.
  4. In the Choose Automation Categorylist, select one of the following options as appropriate:
    • BMC Application Automation 8.2: Select this option to create a new script for performing functions in version 8.2.00 of BMC Application Automation.
    • BMC Remedy 7.6.x: Select this option to create a new script for performing functions in version 7.6.04 SP2 of BMC Remedy IT Service Management Suite.
    • General: Select this option to create a new script for performing general functions like executing a command on your local or remote computer.
    • Hudson / Jenkins: Select this option to create a new script for performing functions in the Hudson tool.
    • RLM Deployment Engine: Select this option to create a new script for performing functions in version 4.3.00 of BMC VaraLogix Q Deployment Automation.
    • You can also create a new category for integrating with other external systems and select that category for creating anew script. For more information, see Managing-automation-categories.

  5. In the Apply templatelist, select an option that you want to use as a base for creating your script. 

    Note

    You must already have existing templates before creating the script to see options in the Apply template list.

  6. In the Script integration serverlist, select that integration server which you want to use for connecting with the external system.When you select an option in this list, the details related to that integration server are automatically added in the script body.

    Notes

    • You must already have existing templates before creating the script to see options in the Script integration server list.
    • The system does not allow you to add an integration server, if your script body is empty.
    • If you are creating a general script that you do not intend to use for performing some action in a particular target external system, then you do not require an integration server.
  7. In the Script Name box, specify a unique name to identify the script.
  8. In the Description box, specify a short description regarding the purpose for which you are creating the script.
  9. In the Script body area, specify the Ruby script that is run when you use the script in a step and run the request. The script body is the core of an automation script. The action that you want to perform and how you want to execute it depends on how you design the arguments and the logic in the script body. For more information about designing the script body, see Designing-the-script-body-of-an-automation-script.
  10. In the Script typelist, select one of the following options as appropriate:
    1. Template: Select this option if you want to save this script as a template for future use.
    2. System: Select this option if you want to save this script as a base script that can be only viewed or copied but not modified by anyone apart from the Administrator.
    3. User: Select this option if you want to save this script as a normal script for your personal use and available for viewing, copying, and modifying. 
  11. Click Add script to save the script or click the cancel link to exit without saving any changes.

Related topics

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*