Configuring event forwarding on a hub monitoring server

If you use either Netcool/OMNIbus or the Tivoli Enterprise Console, in addition to the Tivoli Enterprise Portal or the Enhanced 3270 user interface, to manage events in your enterprise, you can configure a hub monitoring server to forward situation events to these event servers for correlation and management. The hub monitoring server must be configured to enable forwarding and to specify the default destination server.

About this task

Use the following parameters to configure event forwarding in the RTE configuration profile of a hub monitoring server:
KDS_TEMS_EIF_FLAG
Determines whether or not event forwarding is enabled.
KDS_TEMS_EIF_HOST
The fully qualified host name or dotted decimal IPV4 address of the primary event server and of up to seven backup event servers.
KDS_TEMS_EIF_PORT_NUM
The port number on which the Tivoli Enterprise Console® event server or OMNIbus EIF probe listens for events.
KDS_TEMS_EIF_EVENT_LISTENER
The type of event server: Tivoli Enterprise Console or Netcool/OMNIbus.
KDS_TEMS_EIF_DISABLE_TEC_EMITTER
Disables emitter activities in workflow policies running on the Tivoli Enterprise Portal.
KDS_X_TEMS_EIF_BFR_EVT
Determines whether or not events are buffered or stored when they cannot be sent to the event server.
KDS_X_TEMS_EIF_BFR_EVT_PATH
The full path name of the file in which forwarded events are stored.
KDS_TEMS_EIF_BUFFER_EVENT_MAXSZE
The maximum size, in KB, of the cache in which events are stored when they cannot be sent to the event server.
KDS_X_TEMS_EIF_FLT_ATTR1
The name of an attribute in a statement that is used to filter events that are forwarded.
KDS_X_TEMS_EIF_FLT_CLASS1
The name of the event class included in the filter statement.
KDS_X_TEMS_EIF_FLT_MODE
Determines whether events that match the filter criteria statement are forwarded or discarded.
For more information about these parameters and their permissible values, see Tivoli Enterprise Monitoring Server (KDS) parameters.

What to do next

The following tasks must be completed outside the configuration software to implement situation event forwarding:
  • The destination event server or servers must be configured to receive the events.
  • A situation update forwarding process (the event synchronization component) must be installed on the event receivers.
  • For situation events forwarded to the Tivoli Enterprise Console:
    • The .baroc files for the monitoring agents reporting to the hub must be installed and imported on the Tivoli Enterprise Console server, and the rule base must be updated.
    • If any distributed agents report either directly or indirectly (through a distributed remote monitoring server) to a z/OS hub, map and resource files for each monitoring agent must be transferred from a hub monitoring server on a Windows, Linux®, or UNIX system to the RKANDATV library of the runtime environment that contains the hub monitoring server on z/OS.
    • If z/OS agents report to a z/OS hub monitoring server in another CSI, their map files must be copied to the RKANDATV library of the runtime environment that contains the hub.
The section on Integrating event management systems in the IBM Tivoli Monitoring: Installation and Setup Guide provides detailed instructions for configuring the Tivoli Event Console and OMNIbus to receive forwarded events, including installing the event synchronization component and the .baroc files.

For more information on event forwarding, see Event forwarding.