H custom tool definition files, Tool type-specific requirements, Ssa-specific attributes – HP Systems Insight Manager User Manual
Page 189: Msa-specific attributes, Ssa-specific attributes msa-specific attributes
H 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).
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
(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 22 SSA-specific attributes
Description
Syntax
1
Attribute
You should specify only one command
or copy-block or both; however, you
may 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.
attributes)
ssa-block
Specifies the command for an SSA tool.
If the command accepts parameters,
you must specify the command as a
“Parameterized strings” (page 191)
. This
element may have two attributes:
command-type and log.
command
Specifies a source file path and a
destination file path for a copy
operation. The source 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.
copy-block
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.
Tool type-specific requirements 189