Configure 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

If you are using the bidirectional architecture, the IBM Tivoli Monitoring
Situation Update Forwarder can send events to Netcool/OMNIbus in the following
cases:

The Situation Update Forwarder sends events to Netcool/OMNIbus if it detect

errors when it is processing event status updates initiated from the OMNIbus Object
Server.

The Situation Update Forwarder sends an event to Netcool/OMNIbus to update the

default acknowledgement timeout when the sitconf.sh or sitconf.cmd commands are
executed.

To send events from the Situation Update Forwarder to Netcool/OMNIbus, update the
values for the following parameters in the
event_sync_install_dir/omnibus/errorevent.conf file:

ServerName
ServerPort

where:

event_sync_install_dir

Is the location where the IBM Tivoli Monitoring Event Synchronization Component
is installed on your Netcool/OMNIbus ObjectServer system.

ServerName

Is the name of the computer where the EIF probe is running.

ServerPort

Is the listening port for the EIF probe. The default value is 9998.

=========================

Situation Update Forwarder (SUF) overview.

Question & Answer

Question

Understanding how SUF works.

Cause

ITM Tools SitForwarder understanding.

Answer

The event generated is at the ITM situation and
the Tivoli EIF probe. Various triggers then run
of that is a single line entry (per event) in a
the sitforwarder side of SUF which makes a SOAP
specified in the event as the CCMS port.
enters the Omnibus ObjectServer via
calling automations and the output
cache file. This is then read by
connection back to TEMS on the port