Creating custom tool definition files for HP Systems Insight Manager 5.1 or greater (481365-002, January 2009)

5
Table
2
.
Basic TDEF elements
Element
Syntax
Description
To
ol type and
name
<
tool type
-
tool
name=”
name of
tool
”>
</
tool type
-
tool>
Defines the type of tool (SSA, MSA, or web
-
launch) and the
name. The name should be descriptive and must be in
quotations.
Tool type = ssa
-
command, msa
-
command, web
-
launch, app
-
launch
.
C
ategory
<category>
</category>
Element used by HP SIM for organizing tools, limited to 80
charac
ters. This is used for toolbox
authorizations.
D
escription
<description>
</description>
Optional element that describes, in 1024 characters or less,
the too
l to the user and will be shown in the task wizard when
the task is created.
C
omments
<comment>
</comment
>
Optional element that explains what the tool will do.
Execute as user
<execute
-
as
-
user>
</execute
-
as
-
user>
Optional element that specifies the user
whose permissions can
execute the command string on the target node. If not set, it will
default to the user who created or ran the task.
Include
-
filter
<include
-
filter>
</include
-
filter>
Optional element that defines filters for hardware and/or
operatin
g system. Elements invoked in the filter have a direct
effect on whether the tool will appear in the menu. Used in the
target selection when a task is created using this tool.
Tool block
<
tool type
-
block>
</
tool type
-
block>
Heart of the tool that defines
the action [command(s) to be
taken based on the tool type (see
Appendix A
)]. The commands
support parameter expansions so specific target information
can be passed on to the tool. See
Appendix C
for a list of
options. Tool type = ssa, msa, web
Attribute
<
a
ttribute
name=”
name of
the attribute”
>
</attribute>
An expandable list of name
-
value pairs that are attributes
added and/or required for
HP
SIM client applications.
This
allows extending the tool definition without requiring a schema
change. Must include the name of the attribute. For common
attribute descriptions see
Appendix D
.
Note
: Replace italicized text with actual val
ue or data.
Creating a custom SSA tool
This procedure uses the CLI to create a custom SSA tool for copying any executable file to a
managed
system
(target system) and having it execute (install) there. The following procedure uses the CMS as
the access sys
tem.
This example illustrates the creation of a custom tool that will install a security patch on every
Windows server managed by HP
SIM. If done manually, the administrator would have to locate each
Windows server and perform the following commands in tha
t server:

Log on as Administrator

Access a network drive or portable media containing a copy of the file
hpsecurity_patch.exe
and co
py that file to the local drive

Use Start/Run or a command line prompt to enter the command:
<install_path>
\
hpsecurity_patch
.exe

Log off of the system
For this example, it is assumed that the administrator will want to execute this procedure again and
be able to quickly locate it in the HP SIM menus, so an entry in the
Deploy
menu will be made and