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 gateways to map attributes
If a Netcool/OMNIbus multitier architecture or single-tier high-availability architecture is used, then the gateways between ObjectServers need to be modified to add the relevant attributes for IBM Tivoli Monitoring integration with OMNIbus.
This task should be performed by a Netcool/OMNIbus administrator.
In a multitier architecture, update the map definition file for each of these gateways that exist in your environment:
- Collection tier to aggregation tier unidirectional gateways.
- Aggregation tier bidirectional failover gateways.
- Aggregation tier to display tier unidirectional gateways.
In a single-tier high-availability architecture, update the map definition file for the bidirectional failover gateway between the primary and backup ObjectServers.
Perform the following steps for each affected gateway.
- Copy the GATE_itm.map file from an ObjectServer where the IBM Tivoli Event Synchronization component was installed. The GATE_itm.map file can found be 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 mappings in the GATE_itm.map file into the gateway map definition file that also uses the .map extension. The following two types of mappings can be found in the GATE_itm.map file:
- Custom IBM Tivoli Monitoring attributes for the ObjectServer alerts.status table: these attributes should be added to the STATUSMAP mapping entry in the gateway map definition file. Your gateway map file might contain this comment block to identify where to add these custom attributes:
############################################################################## # # CUSTOM alerts.status FIELD MAPPINGS GO HERE # ##############################################################################
- Custom IBM Tivoli Monitoring table mappings: Custom Tivoli Monitoring tables can be added to the ObjectServer database. The mapping definitions for custom tables only need to be copied to the gateway map definition file for bidirectional failover gateways:
- in the aggregation tier of a multitier high-availability architecture, or
- in a single-tier high-availability architecture
Copy the mapping definitions for the custom tables from the GATE_itm.map file to the end of the bidrectional failover gateway map definition file.
What to do next
You must restart the gateways for the changes to take effect. However, restart the gateways only after all other updates to the OMNIbus database schema are complete. Table 1 to determine when to restart the gateways.
Parent topic:
Update the Netcool/OMNIbus ObjectServer with IBM Tivoli Monitoring attributes, tables, and triggers