IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Set up event forwarding to Netcool/OMNIbus > Installation and configuration > Update the Netcool/OMNIbus ObjectServer with IBM Tivoli Monitoring attributes, tables, and triggers
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Update the bidirectional failover gateway to replicate tables
If a Netcool/OMNIbus multitier architecture or single-tier high-availability architecture is used, then the bidirectional gateways between ObjectServers must be modified to replicate IBM Tivoli Monitoring custom tables in the ObjectServer database.
This task should be performed by a Netcool/OMNIbus administrator.
In a multitier high-availability architecture, update the bidirectional failover gateways used between the ObjectServers in the aggregation tier. In a single-tier high-availability architecture, update the bidirectional failover gateway between the primary and backup ObjectServers.
Perform the following steps for each affected bidirectional failover gateway.
- Copy the GATE_itm.tblrep.def file from an ObjectServer where the IBM Tivoli Event Synchronization component was installed. You can find the GATE_itm.tblrep.def file in the event_sync_install_dir/omnibus/multitier directory where event_sync_install_dir is the location where the IBM Tivoli Monitoring Event Synchronization component is installed.
- Copy the table replication definitions in the GATE_itm.tblrep.def file to the bottom of the gateway table replication definition file that also uses the .tblrep.def file extension. Use the following criteria to determine which table definitions to copy:
- Always copy the replication definition for the alerts.itm_loopback_events table.
- Copy the replication definition for the alerts.itm_heartbeat_events table if monitoring agents will be sending events directly to Netcool/OMNIbus and the agents will be configured to send heartbeat events. If you plan to use agent heartbeat settings, you must also run the itm_heartbeat.sql file when updating the OMNIbus database schema in a single-tier architecture or in the aggregation tier of a multitier architecture.
- Copy the replication definition for the alerts.itm_cleared_event_cache table if you are planning to use bidirectional event synchronization between the monitoring servers and ObjectServer. If you copy this definition, you must also execute the itm_event_cache.sql file when updating the OMNIbus database schema in a single-tier architecture or in the aggregation tier of a multitier architecture.
What to do next
You must restart the gateways for the changes to take effect. However, the restart should occur after all other updates to the OMNIbus database schema are complete.See Table 1 to determine when to restart the gateways.
Parent topic:
Update the Netcool/OMNIbus ObjectServer with IBM Tivoli Monitoring attributes, tables, and triggers