Starting version 8.9.03, BMC Server Automation is renamed to TrueSight Server Automation. This space contains information about BMC Server Automation 8.9.02 and previous versions. For TrueSight Server Automation 8.9.03 and later releases, see TrueSight Server Automation 8.9.

Creating Network Shell Script Jobs

Network Shell Script Jobs let you run a Network Shell script on one or more servers.

Before you begin

  • To create a Network Shell Script Job you must first add a script to the Depot. See Adding a Network Shell script.
  • If a Network Shell Script Job runs a local script (that is, the script is copied to one or more remote servers and then executed locally on those servers), you must identify a staging directory that holds the script on each target server. To accomplish this, you must assign a value to the STAGING_DIR property on all target servers. Only a local script requires a staging directory. For more information see Setting values for system object properties and Changing property values for one or more system objects.
  • If a Network Shell Script Job includes BLCLI commands that read or write to a local path (a path on the machine where the BLCLI is running), the user must have read or write access to the path at the operating system level. Otherwise, the command fails. The "user" in this context is the operating system user, not the BMC Server Automation user. On Windows, a typical operating system user has the necessary read and write privileges.
    For example, consider a Network Shell Script Job that invokes a BLCLI command that exports an object to a specified directory. In a typical Linux setup, the BLCLI process runs as the user bladmin. If bladmin does not have write access to the specified directory, the command fails.

  • If you want the option of choosing an older version (rather than the current version) of a script for association with the Network Shell Script Job, ensure that you have set up a Git repository and have been committing your changes to scripts into the Git repository, as described in Walkthrough: Managing versions of NSH scripts using Git.

To create Network Shell Script Jobs

  1. Do one of the following:
    • Using the Depot folder, navigate to a script that you want to deploy. Right-click the script and select NSH Script Job from the pop-up menu.
    • Open the Jobs folder and navigate to the job folder where you want to create a new Network Shell Script Job. Right-click the job folder and select New > NSH Script Job from the pop-up menu.
      The New NSH Script Job wizard opens.
  2. Provide information for the Network Shell Script Job, as described in the following sections:
  3. Click Finish after completing the last step of the wizard.
Was this page helpful? Yes No Submitting... Thank you