Setting up a Command Execution and Analysis Instance

To create an instance of the Remote Command Execution and Analysis tool

1.	Go to the Configure tab, click on the element on which you wish to use the tool.

If the element was created using Element Profile then add the new application class through the same route.

2.	On the Element Properties page, scroll to the Application Class section, click on Add.

3.	On the Add Applications page, select Miscellaneous from the drop down category list and click Next.

All application classes belonging to the BMC Performance Manager Express Monitoring Studio package are listed under Miscellaneous.

4.	On the Available Application Classes page, select Studio - Remote Command Execution and Analysis and select the number of instances you wish to create, click Next.

5.	You can create up to 10 instances at this stage, or create just 1 now and add others later. You arrive at the Properties and Credentials page. Enter the information required for setting up the Remote Command Execution and Analysis instance and click Add.

The "Information Required for Monitoring" at this step differs depending whether the command is to be executed on a remote Windows system or a UNIX/Linux system. The rest of the procedure and interface is the same irrespective of the type of system.

Information required for monitoring

Name	On Windows	On UNIX/Linux
Descriptive Label	Label describing the application class/monitoring tool
Collection Interval	Frequency of collection (monitoring/polling). Unit: Minutes (Default 5 minutes)
Credentials Connect As Password Credentials Execute As Password Credentials	Login used to connect to the remote element through WMI Password associated with the login above Shared credentials used for authentication N/A	Login used to connect to the remote element through Telnet or SSH Password associated with the login above Shared credentials used for authentication Login used to execute the command. Specify only if you need to use a different login than the "Connect As" login specified above. Once connected, the "su" command will be used to impersonate as the specified user and execute the command. Password associated with the login above. Shared credentials used for authentication
Hostname	Hostname or IP address of the remote element (Appears by default)
Remote Access Method	N/A (Automatically connects using WMI)	Telnet or SSH. Select the method to connect to the remote element.
Debug Mode	Yes enables the debug mode, while No disables it. The debug output produced is stored on the RSM server in a file located at: %RSM_HOME%/RSM(xx)/SEN_MS/sen_ms_debug_osCommand_hostName.log. Do not leave the debug mode enabled for too long as the debug file may grow indefinitely.

6.	Enter the information and click Next and you arrive at the Properties and Credentials page asking for the Input Properties of the new command execution instance.

To execute a script or command line utility from the RSM on remote managed elements: Ensure the presence of a folder called sen_ms on the RSM at %RSM_HOME%\RSMxx\; or create one. If a command has already been executed via the same RSM, then the folder will already exist (see here).

Before adding the command line instance: copy the script or command-line utility needed by the command line to the sen_ms folder.

Input Properties

Name	Description/Instructions
Descriptive Label	Enter a label to describe this new command execution instance.
Command to be Executed	Enter the command to be executed on the remote system. To execute a script or command line utility stored on the RSM, enter the command line in this syntax: %{FromRSM:filename} argument1 (please see here for specific details).
Timeout After	Enter the maximum execution time before timeout occurs. "0" disables the timeout. Unit: Seconds.

7.	Either click Next to arrive at the thresholds setting page, or, add a string search or a numeric value extraction for this command execution instance. The string search and numeric value extraction instances can also be set later on this instance.

8.	On clicking Next the input properties are displayed grayed-out. This page allows you to verify, edit or delete the newly-created instances and/or add another instance for the same element. If the information is correct, go on to the next step.

9.	You are at the Thresholds, Properties and Credentials page. Set/modify thresholds and alert conditions:

By default, the Execution Status parameter is enabled to raise an Alarm if the command is not executed before timeout occurs. You can modify this setting if it does not suit your requirements. Thresholds and alerts can be set for each parameter. Check the Warning and/or Alarm boxes next to the parameters to activate alerts as per your specific requirements. See details of parameters and alert conditions in the Reference Guide.

Thresholds can be set or modified at any time by clicking on the element > Configure > ”application class name” > Edit Thresholds, Properties and Credentials.

10.	Click Finish. Changes have been Saved, a message pops up, and an icon appears in the left pane of the window displaying the newly-created command instance. You can also see the new instance of the class under Application Classes.

You have successfully executed a command remotely.

Editing or Deleting an instance

To edit or delete the instance, follow the regular procedure as for all Performance Managers on the Portal, or see Editing or Deleting an Instance.