Configuring a shell script or batch command to play back

Use the Multi File Uploader to upload shell script or batch command CLI scripts to the Application Management Console.

1. In the navigator in the Tivoli Enterprise Portal, select Application Management Console > Robotic Scripts.
2. In the Multi File Uploader view, click New > CLI Playback Script.
3. In the Add Script window: enter the script name; navigate to the location where the script resides and select the script; enter a description and click OK.
   
   Note: Do not select ARM Enabled unless your CLI command is already ARM-enabled. If you are uncertain, do not select this option. If your script runs successfully and you can see it in the playback workspaces, but there is no response time data in the Application or Transaction workspaces, your script was not ARM-enabled.
4. In the Recordings list, select the script and click Upload.
   
   The status changes from Uploading to Successful when the script has successfully uploaded.
   Tip: If the script upload fails, in the Multi File Uploader window, select File > Preferences and check that the Application Management Console details are correct:

   • Server - the Application Management Console (T3) agent hostname or IP address.
   • Port - the port that the Application Management Console is listening on. The default is 1976.
   • SSL, KeyStore Path, KeyStore Password - required only if they are also configured on the Application Management Console.
5. In the Application Management Configuration Editor, select Applications > Applications and click New.
6. In the Create Application window, enter a name for the command and click OK.
7. In the list of applications, right-click your new application and select Create New Transaction.
8. In the Create Transaction window, enter a transaction name and set the following fields before clicking OK:
   • Agent type - Robotic Response Time
   • Transaction type - Command Line
9. In the Command Line tab, select the script and ensure that it is active. In the Command to invoke field, enter the name of the shell script or batch command and any command line arguments. For example, myCliScript.bat
   
10. Create a profile to distribute and play back the CLI command:
    Tip: You can add more than one CLI script to the same profile. This approach allows you to manage a group of scripts that are distributed to the same managed systems. By grouping the scripts this way, you can start and stop the scripts individually. Similarly, you can update the transaction properties for one script only, without affecting the properties for other scripts. Distribution however, is global to all of the scripts defined in the profile. That is, you cannot distribute scripts to different managed systems when the scripts are grouped together in the same profile. When you change the distribution for one script, you make the same change for all of the scripts in that profile.
    1. Select Profiles and click New.
    2. In the Create Profile window, enter a name for the profile, set the type to Robotic Response Time, and click OK.
    3. Select the newly created profile in the list. On the Transactions tab, click Add.
    4. In the Transaction Selection list, select the new application and click OK.
    5. Select the transaction and configure the playback parameters in the Properties pane. Set the number of retries to zero (0), and the Collect instances field to False. Instance data is not used in CLI playback command processing.
    6. Select the Distribution tab and distribute the CLI command to Robotic Response Time playback servers.
    7. Click Apply to save the profile and OK.