Custom commands are executed on the central management server (CMS) and not on target systems, and are intended to be scripts, batch files, or executables that can reference environment variables set by the tool in order to access system or event information. For example, creating a custom command to launch Notepad.

Custom commands require the use of environment variables which are parameters passed to the launched application to make it perform as expected. Refer to Custom Commands - Environment Variables for Custom Commands for more information. The launch command string includes system variables and user-defined variables for your application. For example, you could pass an environment variable that runs a script to check on the status of your mail server.

Note:
	DOS environment variables are supported in the custom command parameters and work as parameters on the New Custom Command page or the Manage Custom Commands page. However, they must be surrounded by double % signs. For example, to pass in the NOTICELABEL environment variable as a parameter, it should be entered as %%NOTICELABEL%% on the parameter line. The environment variables can also be accessed from a batch file or script file. To use them in a batch file or a script file, only a single % sign should precede and succeed the environment variable name. Refer to Command Line Tools - Parameterized Strings Substitution Table for a list of other substitutable variables.

Custom commands that you create are displayed under the ToolsCustom Commands menu option.

You have multiple scheduling options. Refer to Managing with Tasks - Scheduling a Task for more information about scheduling options.

Important:
	The application must be able to execute in the security context provided to HP Systems Insight Manager (HP SIM) (the default is LocalSystem).

Related Procedures

Related Topic