Using the Event Monitoring Service (June 2003)

Understanding the Event Monitoring Service
Client and Target Applications
Chapter 1 21
Client and Target Applications
This section describes some of the client and target application options
and processes. Target applications can be written using the EMS API.
EMS with ServiceGuard
ServiceGuard can be configured with EMS to monitor the health of
selected resources, such as disks. Based on the status of the resources,
ServiceGuard can decide to fail packages over. When working with EMS,
ServiceGuard acts as both the client and target application. EMS works
with MC/ServiceGuard and ServiceGuard Extension for RAC.
Configure EMS requests for use with ServiceGuard packages by editing
the package configuration ASCII file.
In addition, it is recommended that you also create requests through
EMS to:
• Enable a redundant notification system
• Monitor events that affect high availability
• Enable alerts due to a package failover
ServiceGuard may already be configured to monitor the health of nodes,
services, and subnets, and to make failover decisions based on the status
of these resources. Using EMS with ServiceGuard adds to the set of
failures or events that trigger failover and affect availability.
EMS GUI Client Application
The EMS GUI client application found in the Resource Management
area of SAM is used to create monitoring requests for resources and
targets. The EMS GUI starts from the graphical version of SAM. Click
through and select from the various screens to define your monitoring
request. The options include:
1. Select the resources to be monitored.
The full path of a resource includes the resource class hierarchy and
instance. An example of a full resource path for the physical volume
status of the device /dev/dsk/c0t1d2 belonging to volume group
vgDataBase, is /vg/vgDataBase/pv_pvlink/status/c0t1d2.