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
Change the default deduplication trigger
The deduplication triggers provided by the IBM Tivoli Monitoring event synchronization component and the standard deduplication triggers provided with Netcool/OMNIbus are in conflict with each other. The standard deduplication triggers modify the Severity and Summary attributes that results in those attributes having incorrect values for IBM Tivoli Monitoring events for both unidirectional and bidirectional event synchronization.
The standard deduplication triggers must be modified by the Netcool/OMNIbus administrator to ignore events from IBM Tivoli Monitoring. The deduplication trigger to modify depends on the Netcool/OMNIbus architecture type:
single-tier architecture:
- In a single-tier architecture without high availability, modify the deduplication trigger.
- In a single-tier architecture with a bidirectional failover gateway for high availability, modify the agg_deduplication trigger in each ObjectServer.
Multitier architecture:
- In a multitier architecture without high availability, modify the deduplication trigger on the Objectserver in the aggregation tier.
- In a multitier architecture with a bidirectional failover gateway for high availability, modify the agg_deduplication trigger on each ObjectServer in the aggregation tier.
You can modify the appropriate trigger from either the Netcool/OMNIbus Administrator nco_config interface or using the nco_sql CLI on the Netcool/OMNIbus ObjectServer.
- Change the default deduplication trigger using Netcool/OMNIbus Administrator
This section outlines the steps for changing the default deduplication trigger using Netcool/OMNIbus Administrator.
- Use the nco_sql command to modify the deduplication trigger in environments without a bidirectional failover gateway
This section shows you how to use the nco_sql command to modify the deduplication trigger in environments without a bidirectional failover gateway.
- Use nco_sql to modify the agg_deduplication trigger in environments with a bidirectional failover gateway
This section shows you how to use the nco_sql command to modify the deduplication trigger in environments with a bidirectional failover gateway.
Parent topic:
Update the Netcool/OMNIbus ObjectServer with IBM Tivoli Monitoring attributes, tables, and triggers