HP Systems Insight Manager 6.0 User Guide

G Custom tool definition files
Custom tool definition files are XML files that describe how Systems Insight Manager should run tasks based
on a program, script, or UTL added by the user. This appendix describes the wuyntax of these tool definition
files (tdef). For more information, see "???".
Tool type-specific requirements
SSA-specific attributes
An SSA tool executes on a selected target and is only aware of the target system environment. In executing
an SSA tool, the Systems Insight Manager Distributed Task Facility (DTF) of the CMS uses SSH to send one
or more files to the target system, which then executes the tool. An example of an SSA tool would be a tool
that wraps a common Unix command such as ls. cat, or cp.
Table G-1 SSA-specific attributes
Description
Syntax
1
Attribute
You should specify only one command or
copy-block or both; however, you may
<ssa-block> (command/copy-block
attributes) </ssa-block>
ssa-block
specify up to 16 multiple copy-blocks can
be specified. After the command and/or
copy-blocks, one may specify the parameters
for the command and/or copy-block.
Specifies the command for an SSA tool. If
the command accepts parameters, you must
<command> (parameters)
</command>
command
specify the command as a “Parameterized
strings”. This element may have two
attributes: command-type and log.
Specifies a source file path and a destination
file path for a copy operation. The source
<copy-block> (attribute data)
</copy-block>
copy-block
element specifies the source file path for a
copy operation. The destination element
specifies the destination file path for a copy
operation. The default permission of the
copied block is 755. The chmod command
is required to set a custom permission.
1 Replace italicized text between start and stop tags with actual attribute/value/data. Non-italicized text represents valid entry option.
You must specify values for attributes; there are no default values.
MSA-specific attributes
An MSA tool executes typically on the CMS and can work with multiple target systems. When launched,
the MSA process is created once and then passed to all targets on the list. An XWindows tool is an example
of an MSA tool.
MSA command tools must specify a command and the system on which the command will execute.
Table G-2 MSA-specific attributes
Description
Syntax
1
Attribute
Specifies an MSA command, the parameters
for the command, and an execution node
on which the command executes.
<msa-block> (commnad/parameters)
</msa-block>
msa-block
Specifies the command for an MSA tool. If
the command accepts parameters, you must
<command> (parameters)
</command>
command
specify the command as a “Parameterized
strings”. This element may have two
attributes: command-type and log.
<execution-node> (parameters)
</execution-node>
Execution-node
1 Replace italicized text between start and stop tags with actual attribute/value/data. Non-italicized text represents valid entry option.
You must specify values for attributes; there are no default values.
Tool type-specific requirements 147