Systems Insight Manager 6.1 User Guide

Note that file names on Linux and HP-UX operating systems are case-sensitive. The directory used by
Systems Insight Manager to store tools is as follows:
• for HP-UX and Linux systems: /var/opt/mx/tools
• for Windows systems: C:\Program Files\HP\Systems Insight Manager\tools
11. To add the new tool to Systems Insight Manager, perform the procedure described in the section “Adding
a TDEF to Systems Insight Manager”.
For more information about specific SSA tool attributes, see SSA-specific attributes.
Example Web launch tool
A web launch tool launches an application requiring a URL. The example below launches the application
WebJetAdmin for a device selected within the Systems Insight Manager window as long as that device is a
printer. The <web-block> element (in bold below) provides the URL of the managed node where WebJetAdmin
is installed. The parameter %n is used to substitute the managed node hostname. The <toolbox-enabled>
element can have a value of true or false. If the <toolbox-enabled> element is true, it will be associated with
the Toolboxes under Systems Insight Manager User and Authorization. This allows a trusted user to disable
the tool in the Toolbox if the value is false. This tool launches in a separate browser window using the
“target-frame” of WJAFrame. For additional parameters, see mxtool command parameters.
NOTE: In the previous example, hostname.domain should be replaced with the FQDN of where the
WebJetAdmin tool is running.
For more information about specific web launch tool requirements and attributes, see WLA-specific attributes.
For more information about parameterized strings, see Parameterized strings.
Example MSA tool
The MSA tool executes on the CMS and is functional with multiple targets. The process executes once, and
then is passed to all targets selected. The example below shows an MSA tool that deploys the SSH public
key to the selected managed target nodes as long as those nodes are recognized as iLO devices on an HP
single partition server. To do this manually, the administrator would:
• Log on as Administrator on the CMS
• Use Start/Run or a command line prompt to enter the command.
• Mxagentconfig –a –n <nodename> -u <username> -p <password>
• Repeat the command for each managed system
• Log off the system
The <msa-block> element (in bold below) initiates mxagentconfig and requires the user name and
password parameters.
Creating custom tools through the Systems Insight Manager CLI 73