HP Systems Insight Manager 7.2 Technical Reference Guide

warning message appears and only the first value is placed in the resulting key file. If badly
formatted files are encountered, warning messages appear.
The key file is created when CLI mxlmkeyconfig is executed. If the resulting key file already exists,
then the previous keys remain and the information from the source key files are added to the
resulting key file.
HP SIM command line tools
Use the CLItools to execute basic UNIX and Windows commands remotely on one or more systems.
NOTE: For additional information about the individual commands, see the associated manpage
on an HP-UX, ESX (non-embedded), Solaris, IBM, and Linux system or the Windows command line
help where the command tool is installed.
NOTE: Command line tools provided by HP-UX and Linux, such as the ls and df commands,
are run as root by default. For security reasons, you might want them to run as a specific user to
avoid permitting unintended capabilities to a user.
Procedure 1 Launching a command line tool
1. Choose one of the following:
• Select Tools→Command Line Tools→UNIX/Linux for Linux or UNIX command line tools.
• Select Tools→Command Line Tools→Windows for Windows command line tools.
2. Select the command line tool that you want to run, and follow the steps to launch the tool. For
assistance with the steps, see Managing with tasks.
3. Click Run Now to launch the tool.
4. In the Parameters field, enter the parameters for the tool.
5. If applicable, enter the privilege elevation password.
Command line interface
Use the mxexec command to launch these command line tools on one or more systems from the
command line interface. For assistance with this command, see the HP Systems Insight Manager
Command Line Interface Guide, at http://www.hp.com/go/insightmanagement/sim/docs.
Custom tools
Custom tools are executed on the CMS and on target systems. They can 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 tool to launch Notepad. You can create or
launch SSA, MSA, and WLA tools. You can create the following types of custom tools:
• Remote tool
A tool that runs on selected target systems. It might copy files to the target systems or run
specific X-Window applications on the target systems. You can schedule this tool.
• CMS tool
A tool that runs on the CMS. It is usually a script or batch file and can pass in environment
variables. Using Automatic Event Handling, you can configure this tool to run when events
are received. You can schedule this tool.
• Web page tool
A tool that launches a web URL. The URL is launched in a separate browser window on the
CMS. You cannot schedule this tool.
For more information on custom tools, see Custom tools.
28 Product overview