Customizing Event Integration

Table 1. Additional configuration tasks after event integration installation
Task	Architecture type	Administrator
Configuring IBM Tivoli Monitoring Situation Update Forwarder event flow to OMNIbus.	Bidirectional	Netcool/OMNIbus
Changing the configuration values of the IBM Tivoli Monitoring Situation Update Forwarder.	Bidirectional	Netcool/OMNIbus
Updating the IBM Tivoli Monitoring Situation Forwarder to forward event status updates to additional monitoring servers.	Bidirectional	Netcool/OMNIbus
Customizing how the IBM Tivoli Monitoring OMNIbus triggers handle event status updates from the monitoring servers.	Bidirectional	Netcool/OMNIbus
Changing the default acknowledgment timeout used when sampled events are deleted or cleared in Netcool/OMNIbus.	Bidirectional	Netcool/OMNIbus
Editing the configuration parameters that the hub monitoring server uses to forward events.	Unidirectional and bidirectional	IBM Tivoli Monitoring
Specifying which situations forward events to Netcool/OMNIbus.	Unidirectional and bidirectional	IBM Tivoli Monitoring Operator
Understanding and Customizing the Event Contents.	Unidirectional and bidirectional	IBM Tivoli Monitoring
Converting from unidirectional architecture to bidirectional architecture.	Bidirectional	Netcool/OMNIbus
Customizing event status processing behavior when agent switching is used or the agent goes offline.	Unidirectional and bidirectional	IBM Tivoli Monitoring
Creating a Netcool/OMNIbus WebGUI tool to launch from WebGUI to the Tivoli Enterprise Portal.	Unidirectional and bidirectional	Netcool/OMNIbus

Configuring IBM Tivoli Monitoring Situation Update Forwarder event flow to OMNIbus
This section outlines the scenarios and process for configuring IBMTivoli Monitoring Situation Update Forwarder event flow to OMNIbus

Changing the configuration values of the IBM Tivoli Monitoring Situation Update Forwarder
After installation of IBM Tivoli Event Synchronization, you can change the configuration values of the Situation Update Forwarder that were specified during installation.

Updating the IBM Tivoli Monitoring Situation Forwarder to forward event status updates to additional monitoring servers
If you are using the bidirectional architecture and have multiple hub monitoring servers forwarding situation events to the same Netcool/OMNIbus ObjectServer, the IBM Tivoli Monitoring Situation Update Forwarder must be defined with the list of monitoring servers that it should send event status updates to.

Customizing 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.

Changing the default acknowledgment timeout used when sampled events are deleted or cleared in Netcool/OMNIbus
When a situation event from a sampled situation is forwarded to the Tivoli Netcool/OMNIbus ObjectServer and that event is later deleted or cleared in the ObjectServer, the behavior of the bidirectional event synchronization architecture is to send a request to the hub Tivoli Enterprise Monitoring Server to acknowledge the situation with a specified timeout.

Editing the configuration parameters that the hub monitoring server uses to forward events
Edit the hub monitoring server Tivoli Event Integration Facility EIF configuration file to customize the configuration parameters that specify up to five failover Netcool/OMNIbus EIF probes or to adjust size of the event cache.

Specifying which situations forward events to Netcool/OMNIbus
By default, when the hub Tivoli Enterprise Monitoring Server has been configured for the Tivoli Event Integration Facility, events for situations enabled for event forwarding are sent to the default EIF receiver.

Converting from unidirectional architecture to bidirectional architecture
This section outlines the steps for converting from unidirectional to bidirectional architecture.

Customizing event status processing behavior when agent switching is used or the agent goes offline
This section contains the variables for customizing the behavior of event status processing when agent switching is used.

Creating a Netcool/OMNIbus WebGUI tool to launch from WebGUI to the Tivoli Enterprise Portal
If you want your Netcool/OMNIbus WebGUI users to launch the Tivoli Enterprise Portal to see additional details about events shown in the WebGUI, you can create a WebGUI tool that launches the Tivoli Enterprise Portal from the Netcool/OMNIbus Event List UI.