HP Systems Insight Manager 5.2 Update 2 Technical Reference Guide

https://deploy.hp.com:280/deploy/deployimage.jsp?
device1=nodea.hp.com&device2=nodeb.hp.com
If we have only 1 selected target system in the above example, the expanded URL string would look like:
https://deploy.hp.com:280/deploy/deployimage.jsp? device1=nodea.hp.com
Because there is no current selection when we get to the repeat block, the entire repeat block is suppressed
during the substitution process.
Related procedures
• Creating a new remote tool
• Creating a new CMS tool
• Creating a new web page tool
• Removing and restoring custom tools
Related topics
• Command line tools
• Managing custom tools
Custom tools reference
Tool types
There are six basic types of HP Systems Insight Manager (HP SIM) tools, single-system aware (SSA) tools,
multiple-system aware (MSA) tools, Web-launch aware (WLA) tools, automation tools, message driven bean
tools, and application launch.
SSA tools are executed on a target system and are only aware of the target system environment. When
executing an SSA tool, therefore, the Distributed Task Facility (DTF) sends the tool information to each HP
SIM agent to execute the tool. An example of an SSA tool would be a tool that wraps a common UNIX
command, such as ls, cat, or cp.
MSA tools are executed on a central system, sometimes the Central Management Server (CMS), and know
how to handle a list of target systems. An example of an MSA tool would be a tool that wraps the functionality
of Ignite-UX on HP-UX systems.
WLA tools are generally executed in a browser and are specified by a universal resource location (URL).
Automation and message driven bean tools are executed on the CMS and perform some action, such as
discovery on the target systems.
IMPORTANT: These two tools are internal HP tools and are not for general use.
Custom tools are executed on the CMS. One instance of the tool is started for each target system.
Parameterized strings
To create tools properly, the tool developer must understand how URLs and command lines are formed.
Using parameterized strings, tool developers can greatly enhance the options available in creating tool
definition files (TDEFs).
Parameterized strings are strings that contain replacement fields, similar to the format strings used in the
popular printf() function in the standard C library. These fields can be replaced by values entered by the
user at runtime (as defined by the tool parameters attribute), by some standard task properties supplied by
the Task Controller, values related to the selected target systems or system groups, or by property values
retrieved from a global tool properties file. This allows a very specific URL or command line to be generated.
Parameterized strings substitution table
The following parameters provide substitution of global attribute values:
DescriptionParameter
Task ID for the task being executed%t
Custom tools 337