OSI/MHS Management Programming Manual

Introduction to Management Programming for
OSI/MHS
OSI/MHS Management Programming Manual424824-001
1-9
Event-Management Interface
Figure 1-6 shows the following sequence of events:
1. An event occurs in the subsystem environment.
2. The MHS manager reports the event by sending an event message, formatted as an
SPI buffer, to the local EMS collector. Note that these processes send event
messages directly to the collector, not through SCP.
3. The collector stores the event message in a disk file called the event log.
(If a forwarding distributor is present, this distributor forwards the event message to
a collector on a remote node. The remote collector stores the message in an event
log on its own node, so that the message exists on both nodes.)
4. An application installs an EMS filter specifying the selection of event messages it
wants to receive. (Filters are optional, but recommended. If no filter is installed, all
event messages will be delivered to the application.)
Figure 1-5. OSI/MHS Event Management Interface
105CDT .CDD
Event Management Service (EMS)
OSI/MHS Subsystem
Event
Messages
Accounting
Messages
Alternate
Collector
Primary
Collector
Distributor
Filter
Event
Log
Event
Log
MR Group
LO Group
MS Group
GI Group
MHS
Manager
RS Group
Management
Application