Importing automation scripts from the library

BMC provides default scripts for integrating with external systems and performing various functions. For more information about the supported integrations, the various scripts available for that integration, and the tasks that you can perform using each script, see Integrating.

You can change the status for your automation scripts to allow or prevent their usage. For more information, see Using-status-of-objects.

Before you begin

Before you start importing automation scripts to perform functions in a particular external system, you must first configure the external system to integrate with BMC Release Process Management:

• For information about integrating with BMC Remedy IT Service Management, see Configuring-for-integrating-with-BMC-Remedy-IT-Service-Management-Suite.

• For information about integrating with BMC Application Automation, see Configuring-for-integrating-with-BMC-Application-Automation.
• For information about integrating with BMC Release Package and Deployment, see Configuring-for-integrating-with-BMC-Release-Package-and-Deployment.
• For information about integrating with Hudson, see Hudson.
• For information about integrating with JIRA, see JIRA.
• For information about integrating other external systems, see Other-integrations.

To import scripts from the library

1. Go to Environment > Automation.
2. On the right pane, click Import scripts from Library.

3. In the Import automations scripts from Library dialog box, complete the following tasks:

   1. In the Integration Server list, select one of the configured integration servers.

   2. In the To use as list, do one of the following:

      • To import a local shell script that runs on the engine of the host that started the automation, select Local Shell.

      • To import an automation script that transfers other files or scripts between the servers, select Remote Dispatcher.

        Notes

        • To Import remote dispatcher automation scripts, you must specify the agent type for the server.
        • You can use remote dispatcher automation scripts only in other automation scripts. You cannot use remote dispatcher scripts in the steps of a request.
        • In the Dispatch file put automation script, the source and target file paths are relative to the SS_CHANNEL_ROOT value. The default values for the SS_CHANNEL_ROOT are the following:
          • Linux: '/tmp'
          • Windows: 'C:/windows/temp'

      • To import an automation script that is run by the appropriate server, select Remote Shell.
      • To import scripts that obtain the necessary data for operating other automation scripts, select Data Retriever.

      • To import a Ruby automation script that runs on the host that started the automation, select Local Ruby.

        Note

        • To import local ruby scripts, you must fist import all related data retriever scripts.
        • All imported local ruby scripts have the direct_execute parameter set as true by default.
   3. In the Category list, select  the automation category of your automation script.

   4. In the Agent Type list, select one of the agent types used by the remote server:

      • NSH
      • SSH

      Note

      The Agent Type parameter is required for remote automation scripts only.

   After you specify the required parameters for the automation script, a list of available scripts is displayed.

4. Select one or more of the scripts that you want to import, and then click Import. 
   To preview a script, click Preview .

To change the automation script status

1. Go to Environment > Automation.
2. In the automation scripts list, find the appropriate script.
3. For the required automation script, in the Actions column, click << or >>.
   _{click the image to expand} 
   

For more information about the states available for automation scripts, see Using-status-of-objects.