Previous Topic: Event Management UtilitiesNext Topic: Prerequisites


How the Event Management Utilities Process Works

When an application generates an Event Management message, it uses one of the supplied application program interfaces (APIs) (assembler or C/C++) to direct messages to the Event Management Utilities. Depending on the particular platforms that are involved, there can be many different techniques for communicating with Event Management. Currently, these Event Management transports are supported:

SNMP

Enables the messages to form formal SNMP traps, which can then be routed to Event Management or other network managers.

SYSLOGD

Enables the messages to be routed to the syslog daemon. The daemon is an IBM-supplied UNIX process that can be configured to route messages to Event Management.

CCS Event Management

Enables the messages to be processed directly without using a transport such as SYSLOGD, WTO, or SNMP. Event Management has an optional store-and-forward feature that ensures message delivery.

The Event Management Utilities evaluate each message against a user-supplied configuration policy, and depending on the options that are selected, reformats and broadcasts the message to Event Management using one or more of the message transports. This flexibility provides you with granular control over message processing and integration with Event Management.

Use the Event Management Utilities configuration statements to:

Note: Wherever possible, interface applications directly with Event Management rather than using Framework Event Management Utilities. Framework Event Management Utilities is intended for special cases when an application cannot use Event Management directly.