Configuring accelerated event notification
You can configure Tivoli Netcool/OMNIbus for accelerated event notification of events that could present a risk to the system. The Accelerated Event Notification (AEN) system provides a means of accelerating high-priority events to help ensure that systems can continue to run without interruption.
- Determine the conditions under which you want to accelerate events.
Consider whether to use the probe rules file to flag events for acceleration,
or whether to set up conditions within a post-insert, post-update,
or post-reinsert trigger in the ObjectServer.
If the conditions under which events should be accelerated are set up in the rules file, and are complex, you might need to configure the alerts.status table with a dedicated column to receive a flag that identifies an event as an accelerated event.
Typically, you can run a post-insert trigger on inserted events to determine whether they meet the conditions for acceleration, or run a post-update trigger on updated events that have been enriched with information from other sources, or run a post-reinsert trigger to escalate repeating events.
- Determine whether you require a dedicated gateway for forwarding accelerated events. Consider the use of a dedicated gateway if you want to eliminate the possibility of unexpected delays caused by high volumes of events, which may largely be non-critical, or if you want to send accelerated events to a different ObjectServer than that used for normal IDUC updates. If using a dedicated gateway, you must configure that gateway to replicate only accelerated inserts and updates.
- Set up a dedicated event column to flag an event for acceleration, if required.
- Set up channels to define the type of event data to be included in accelerated event notifications, and the recipients of this event data.
- Configure post-insert, post-update, or post-reinsert triggers to act on accelerated events that are inserted or updated in the alerts.status table.