IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Set up event forwarding to Netcool/OMNIbus > Customize Event Integration
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Customize how the IBM Tivoli Monitoring OMNIbus triggers handle event status updates from the monitoring servers
You can configure how the IBM Tivoli Monitoring OMNIbus triggers handle acknowledgment expiration and resurface status update events from the hub monitoring servers when the bidirectional architecture is used.
You can also configure how stop situation event status updates are handled for pure situation events for both the unidirectional and bidirectional architecture. For more information about handling event status updates, see Event behavior.
It might also be necessary to edit the procedure that sends event status updates from Netcool/OMNIbus to IBM Tivoli Monitoring if Netcool/OMNIbus is installed into a directory path containing spaces or the Situation Update Forwarder will be run by a user other than root.
- Configure acknowledgement expiration and resurface status update event behavior
This section outlines the process for configuring acknowledgement expiration and resurface status update event behavior.
- Configure stop situation event behavior for pure situations
When the IBM Tivoli Monitoring triggers in Netcool/OMNIbus process a situation stop event, the triggers clear all events for the situation that are detected by the remote monitoring server specified by the ITMThruNode OMNIbus attribute. However, you can configure the IBM Tivoli Monitoring triggers to ignore situation stop events for pure events.
- Edit the eventcmd procedure
This section lists possible modifications to the eventcmd procedure.
- Edit the writeitmcmd procedure
This section lists possible modifications to the writeitmcmd procedure.
Parent topic:
Customize Event Integration