HP TopTools - Manual (Page 74)

HP Toptools for Unicenter User Guide
By distributing Unicenter and Toptools together, full functionality of HP Toptools for Unicenter is available, while
keeping node counts down and thus improving the performance of the Unicenter server.
HP Web JetAdmin for Unicenter
HP Web JetAdmin does not specify a maximum node count. As a result, you may scale Web JetAdmin with your
Unicenter server or distribute as depicted in the figure above.
6.4 Application Notes
Integration between HP Toptools and Unicenter provides for many additional management application
opportunities. Administrators, third party consultants, operations staff, and even end-users with the appropriate
authority, can add considerable value to the HP Toptools for Unicenter integration by defining enterprise
management policies. For example, Unicenter could be directed to generate a helpdesk trouble ticket automatically
whenever a critical event takes place on an HP device. Another useful application policy might be to lock a user’s
keyboard whenever a security breach or virus is detected.
A variety of events or traps can be managed utilizing the same procedures outlined below. The following examples
provide a step-by-step procedure for developing integrated policies for HP devices and Unicenter using Event
Management.
The Event Management component of Unicenter is comprised of three parts: Event Console, Message Records, and
Message Actions. Event Management intercepts the system log as part of a regular installation. When a Message
Record is matched against a console message, a Message Action is then carried out. Wildcard characters, such as *
and ? can be used to further refine a Message Record match. For additional information on Event Management,
please refer to the CA Reference Guide in the Unicenter Books Online.
Unicenter policies can be defined to Event Management through CAUTIL (CA’s Command Line Interface), the
Enterprise Management GUI, or the Unicenter API. The following examples will employ CAUTIL record
definitions for easy deployment to external client sites running Unicenter. These definitions can be entered into a
file with a simple text editor and then executed at the client site. Note: %HOST% is a variable name for the Event
Management machine where these definitions are to be defined. For information on using Unicenter Event
Management, please refer to the CA Reference Guide in the Unicenter Books Online.
6.4.1 Helpdesk Application
This example detects a disk nearly full situation and then opens a helpdesk trouble ticket on the Unicenter Problem
component.
1. Determine the event to be managed and the policy you wish to administer. Make a note of the precise textual
syntax of the event or trap message. For example, SNMPTRAP – C:\ is 90% full
2. Define the Message Record to match the console message. For example,
CAUTIL -D=%HOST% DEFINE MSGRECORD MSGID='SNMPTRAP – ?:\ is 9?% full ' TYPE=MSG
This example will only confirm a match when any disk usage exceeds 89%. Note the use of the two question mark
wildcard characters in the MSGID text string relative to the example trap.
3. Define the Message Action to create the helpdesk trouble ticket. For example,
CAUTIL -D=%HOST% DEFINE MSGACTION NAME=(*,*) ACTION=COMMAND
TEXT=”’C:\path\dsktrap.bat &userid &datem &time8 &nodeid &5’”
We have used a Message Action to execute a batch file located in the directory called path, which, in this case,
will execute another CAUTIL command. This Message Action example passes five parameters that will be
used in the batch file to create the trouble ticket. The &5 is a variable, which corresponds to the fifth field of the
Unicenter Event Console text message, in this case is ‘90%’. For more information about creating Message
Actions, refer to MSGACTIONS in the CA Reference Guide.
Page 74