HP Systems Insight Manager User Manual
Page 73
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 Systems Insight Manager menus, so an entry in the Deploy menu is made and called
Software Distributor, which when invoked allows the administrator to execute this custom tool.
Procedure 17-1 Creating the Software Distributor tool
1.
Log into the CMS using a valid user name and password. Systems Insight Manager grants authorization
based on the operating system login.
NOTE:
Only administrators have command line access to Systems Insight Manager on a Windows
CMS. Administrators on a HP-UX/Linux CMS must have root capability.
2.
Open a terminal window or a command prompt window to execute Systems Insight Manager commands.
3.
Open a text editor and create a new file by typing the XML version text and tool list tags as follows:
NOTE:
Your text editor must be able create a text-only file with no embedded formatting.
4.
Following the leading XML version and tool-list tags, type the tool name tag of
to define the type and name of the tool. The revision string
is used to keep track of different versions of the tool as will be seen later. Enter the subsequent category,
description, and comment elements to further define the tool for Systems Insight Manager and the user
(the description and comments will be displayed in the GUI window for that particular tool).
5.
Enter the execute-as-user element with the value of Administrator to define the user whose permissions
are allowed on the target node. After entering the execute-as-user element, the TDEF should display as
follows:
6.
The include-filter element specifies which hardware and/or operating system filters will be applied. For
this example, enter the include-filter data as shown below.
7.
Following the include-filter element is a block element that is the heart of the tool and includes the
command(s) to be executed. Enter the ssa block element as shown below. It will copy the file to the
specified destination and execute it there. In the example, the HP Security Patch v.1 executable is given
the filename hpsecurity_patch.exe.
Creating custom tools through the Systems Insight Manager CLI
73