IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Administrator's Guide > Configure connectors for the common event console > Common Event Console Configuration window
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
OMNIbus Connector tab
Click the OMNIbus Connector tab to view or change the information for an IBM Tivoli Netcool/OMNIbus connector. To have the events from a Tivoli Netcool/OMNIbus ObjectServer displayed in the common event console, you must configure an IBM Tivoli Netcool/OMNIbus connector.
To configure a connector, click New. The resulting OMNIbus Connector page contains the following information that defines an IBM Tivoli Netcool/OMNIbus connector:
- Connector name
- The name that is to be displayed in the common event console for this connector.
- Maximum number of events for this connector
- The maximum number of events that are to be available in the common event console for this connector.
- Computer name of event system
- The computer name of the event system that is associated with this connector.
- Port number of event system
- The ObjectServer port number (usually 4100), which this connector uses to retrieve events from the Tivoli Netcool/OMNIbus event system.
- User name for accessing event system
- The user name that is used when accessing the event system that is associated with this connector.
- Password
- The password that is associated with the user name.
- SQL WHERE clause that restricts events for common event console
- This clause can be applied only to the part of an event that is built from the Tivoli Netcool/OMNIbus alerts.status table. For example, Severity <> 0 causes all events with a severity that is not equal to 0 to be available in the common event console.
If you do not define a clause, all Tivoli Netcool/OMNIbus events are available in the common event console.
- View cleared events
- You can choose Yes or No. A value of Yes means that cleared events for this connector are available in the common event console.
- Time interval (in minutes) for polling event system
- The number of minutes between each poll of the event system for new or changed events.
The Tivoli Netcool/OMNIbus ObjectServer automatically sends new or changed events to the common event console as they become available. Therefore, the primary purpose of this checking is to ensure that the server and the connection to the server are functioning properly.
- Time interval (in seconds) between reconnection attempts
- The number of seconds of delay between reconnection attempts when the connector loses its connection to the event system.
- Number of reconnection attempts
- The maximum number of consecutive reconnection attempts to make if the connector loses its connection to the event system.
If this value is set to 0 and the connector loses its connection, the connector remains inoperable indefinitely.
If this value is set to -1 and the connector loses its connection, the connector attempts to reconnect indefinitely.
- Information for extra table columns
- The common event console includes five extra table columns that you can customize. In the remaining fields on this page, you can define the Tivoli Netcool/OMNIbus field type and field name that identify the field that is to be mapped to each of these customizable columns.
For the field type, you can choose one of the following values:
- alerts.status, which means that the field contains data from the alerts.status table in the Tivoli Netcool/OMNIbus ObjectServer.
- alerts.details, which means that the field contains data from the alerts.details table in the Tivoli Netcool/OMNIbus ObjectServer.
- Extended, which means that the field contains extended attributes from a Tivoli Enterprise Console event that has been forwarded to the Tivoli Netcool/OMNIbus event system.
Parent topic:
Common Event Console Configuration window