HP Systems Insight Manager 7.2 Technical Reference Guide

Table 54 Substitution of the selected target (continued)
DescriptionParameter
related systems attributes is omitted for each system, the
network name and IP address is returned. The network
name and IP address are returned in the form "network
name|ip address". If more than one system is returned,
they are comma-delimited. Note that the relationship type
"MgmtProcToServer" can return related system information
for all management processor relationship types.
The value of the named attribute of the target system.%(attribute%)
Table 55 Repetition to support multiple selected target systems
DescriptionParameter
Repeated pattern (only repeats if a current selection exists).
If a current target selection does not exist, the text between
%( ... %)
the delimiters is removed on expansion. This enables the
text to be optional and dependent on the target selection
list.
Selection index (one-based).%i
Do not substitute anything, but increment the selection index
to the next integer and the referenced target system to the
next target in the selected target list.
%z
Encrypted text (encrypt after all other parameters have
been substituted).
%< ... %>
Enables you to retain a % in the command or URL after
parameterized substitution occurs. This feature would be
%%
beneficial for custom commands to utilize some predefined
operating system environment variable (EV) within the
command itself, such as an existing diretory path string,
predefined argument, or parameter value. The EV name
that you specify in the custom command must exist in the
environment that the custom command will be running. For
example, if you knew that an EV called MyPath existed on
the CMS where the custom command will be running, you
could include the EV within your custom command using
the following syntax: %%MyPath%%. When the custom
command runs on the specified CMS, it would appear as
%MyPath%, and the command line interpreter would
expand the EV to its actual value.
Tool filtering
Tool filtering is a facility enabling the tool writer to control whether the tool should be executed on
a selected system. Most tools are platform-dependent. For example, the bdf tool depends on the
bdf command, which is provided on HP-UX platforms, but is not available under that name on
Linux platforms. A tool should be visible only in the Tools menu when there is at least one discovered
system that passes the filter requirements. A discovered system must pass the filter requirements
and is executed only if all the filter requirements are passed. To do this, the tool specifies in a
system filter expression the system attributes that must be possessed by all systems it can run on.
NOTE: If a tool cannot be launched for selected systems, an error message appears with
information about why the tool cannot be launched.
The system attributes required for a tool to run are specified by system filter expressions having
the form:
<node-filter name="attribute-name" operator="eq"
Custom tools reference 471