HP Systems Insight Manager - Manual (Page 304)

known values on the selected systems. The protocol filter type requires that the protocol must exist on the
system before the operators can be applied. This means that the neq and nct operators also depend on
the system to have that protocol. The other filter also works like the
protocol filter such that the attribute being
filtered upon must exist on the system before the operators can be applied. If a tool uses the other and/or
protocol filters, then at least one system must contain the filterable attributes for the tool to be displayed in
the GUI.
Version numbers
The OSRevision and Protocol Support system attributes have values that are interpreted as version numbers
if possible. A version number is a series of non-negative decimal numbers separated by period (.) characters.
When comparing version numbers, the following rules are used:
•
The leftmost numbers in the series are most significant, so 1.0 is greater than 0.1.
•
Leading zeroes on the numbers are disregarded, so 003 is equal to 3.
•
Two adjacent period characters are interpreted as if they delimited the number zero, so 1.0.3 is equal
to 1..3
•
A beginning period character is interpreted as if preceded by a zero, so .9 is equal to 0.9.
•
Trailing zero numbers are disregarded, so 1.0.0 is equal to 1.
Other requirements
SSA command tools must contain an execute statement (execStmt) or a file copy statement (copyStmt),
or both. If only the execute statement is specified, no files are copied before executing the command. If only
a file copy statement is specified, after the files are copied, no command is executed. If they are both
specified, the files are copied first and then the command is executed.
MSA command tools must specify a command and the system on which the command will execute.
Tool names must be at least one character, and no more than 256 characters in length. The first character
of the name must be alphabetic. Characters after the first can be letters, digits, spaces, or any of the characters
- . ( ) or _.
Web-launch aware tools must specify a main URL.
When specifying file copy pairs, the destination file paths for each file copy pair within a single TDEF must
be unique. Specifying the same destination file path for multiple source file paths results in a file parsing
error.
An error occurs when running a tool that copies a file if the file does not exist or is unreadable. The source
file path is not checked at the time the tool is created or modified, but the path must exist at the time the tool
is executed.
When the log element is set to true, standard out and standard error output from the execution of the tool is
logged in the Central Management Server (CMS) log file /var/opt/mx/logs/mx.log. When it is set to
false, only summary task log information, such as start and end times and task status is logged.
Document type definition
The Document Type Definition (DTD) file defines the constraints for an XML file. These constraints include the
valid element tags, attributes, and the cardinality of elements in an XML file. The tool DTD file is named
toollist.dtd
and is included in the following paragraph. Note that because of manpage formatting,
the DTD contents might not appear the same as in the file.
<?xml version="1.0" encoding="UTF-8" ?>
<!-- The tool-list element can contain zero or more of
ssa-command-tool elements, msa-command-tool elements,
web-launch-tool elements, automation-tool elements or
app-launch-tool elements.-->
304 Tools that extend management