HP

HP Systems Insight Manager Technical Reference Guide

English
  Tools that Extend Management  |  Custom Commands   

Custom Commands

»Table of Contents
»Index
»Notices
»Introduction
»Product Overview
»Getting Started
»Discovery and Identification
»Users and Authorizations
»Networking and Security
»Monitoring Systems, Clusters, and Events
»Storage Integration
»Managing with Tasks
»Tools that Extend Management
»Cluster Monitor
»Command Line Tools
»Creating New Command Line Tools
Custom Commands
»Creating a New Custom Command
»Managing Custom Commands
»Editing a Custom Command
»Environment Variables for Custom Commands
»New Web Launch Tool
»Configuring DMI Access
»Configuring SNMP Access
»Device Ping
»Disk Thresholds
»License Manager
»Management Processor Tools
»Managing MIBs
»Installing OpenSSH
»PMP Tools
»Removing and Restoring Tools
»Replicate Agent Settings
»RPM Package Manager
»Server Migration Pack
»System Management Homepage
»System Page
»Version Control
»Virtual Machine Management Pack
»WBEM Based Tools
»Available MSA Tools
»Partner Applications
»Reporting
»Administering Systems and Events
»Troubleshooting
»Reference Information
»Printable version
»Glossary
»Using Help
» Related Procedures
» Related Topic

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.

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.

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

  • New Custom Commands. Select ToolsCustom CommandsNew Custom Commands. The New Custom Commands page appears.

  • Manage Custom Commands. Select ToolsCustom CommandsManage Custom Commands. The Manage Custom Commands page appears.

  • New Web Launch Tool. Select ToolsCustom CommandsNew Web Launch Tool. The New Web Launch Tool page appears. This tool is for Linux and HP-UX systems only.

  • Remove a Tool. Select OptionsRemove a Tool. The Remove a Tool page appears.

Related Procedures

» Custom Commands - Creating a New Custom Command
» Custom Commands - Managing Custom Commands

Related Topic

» Custom Commands - Environment Variables for Custom Commands