IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Set up event forwarding to Netcool/OMNIbus
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Upgrade from a previous installation of IBM Tivoli Monitoring and Netcool/OMNIbus integration
This section contains the tasks you must perform if you are upgrading from a previous installation of IBM Tivoli Monitoring and Netcool/OMNIbus integration.
If you have already installed and configured event integration between IBM Tivoli Monitoring and Netcool/OMNIbus and you are upgrading IBM Tivoli Monitoring, perform the tasks listed in Table 1 to upgrade each of the environments that will be receiving events from the latest version of IBM Tivoli Monitoring.
Upgrading from a previous installation of IBM Tivoli Monitoring and Netcool/OMNIbus integration.
Task Architecture Type Administrator 1. Upgrade Netcool/OMNIbus ObjectServer, if necessary, to a release or fix pack version required by IBM Tivoli Monitoring.
See the Netcool/OMNIbus Information Center for instructions on performing the upgrade: http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.tivoli.namomnibus.doc/welcome_ob.htm. See also Required software for event integration with Netcool/OMNIbus.
Unidirectional and bidirectional Netcool/OMNIbus 2. Back up the rules files in the Netcool/OMNIbus Probe for Tivoli EIF's operating system directory and then upgrade the Netcool/OMNIbus Probe for Tivoli EIF, if necessary, to the release required by IBM Tivoli Monitoring.
See the Netcool/OMNIbus Information Center for instructions on performing the upgrade: http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.tivoli.namomnibus.doc/welcome_ob.htm. See also Required software for event integration with Netcool/OMNIbus.
Unidirectional and bidirectional Netcool/OMNIbus 3. Upgrade the IBM Tivoli Monitoring Event Synchronization Component. Unidirectional and bidirectional Netcool/OMNIbus or IBM Tivoli Monitoring 4. Upgrade existing IBM Tivoli Monitoring events to use new OMNIbus attributes. Unidirectional and bidirectional Netcool/OMNIbus 5.
Update the Netcool/OMNIbus ObjectServer with IBM Tivoli Monitoring attributes, tables, and triggers.If you have made any customizations to the IBM Tivoli Monitoring triggers in the Netcool/OMNIbus ObjectServer, you should make the same updates to the new version of the triggers and procedures. You can edit the .sql files provided with the IBM Tivoli Monitoring Event Synchronization before loading them into Netcool/OMNIbus ObjectServer. For a list of customizations that might have been made to the existing triggers, see Customize how the IBM Tivoli Monitoring OMNIbus triggers handle event status updates from the monitoring servers.
Unidirectional and bidirectional Netcool/OMNIbus 6. Ensure that you have a default deduplication trigger. See Replace the default deduplication trigger. Unidirectional and bidirectional Netcool/OMNIbus 7. If you did not replace the default deduplication trigger in the previous task, ensure that you have changed the existing default duplication trigger to ignore IBM Tivoli Monitoring events. See Change the default deduplication trigger for details. Unidirectional and bidirectional Netcool/OMNIbus 8. Update the EIF Probe Rules. Unidirectional and bidirectional Netcool/OMNIbus
- Upgrade the IBM Tivoli Monitoring Event Synchronization Component
When you upgrade the IBM Tivoli Monitoring event synchronization component for IBM Tivoli Netcool/OMNIbus you install the newest version of the Situation Update Forwarder, and replace any scripts that have been updated since the base version.
- Upgrade existing IBM Tivoli Monitoring events to use new OMNIbus attributes
If you are upgrading from IBM Tivoli Monitoring Version 6.2.2 (or earlier) to the latest version of IBM Tivoli Monitoring, you must upgrade the existing monitoring events in the Netcool/OMNIbus ObjectServer alerts.status table to use a new OMNIbus attribute.
- Replace the default deduplication trigger
With previous versions of the triggers provided by the IBM Tivoli Monitoring event synchronization component, the default deduplication trigger was overwritten in the Netcool/OMNIbus ObjectServer. The overwriting causes you to lose any customizations you made to the trigger. The latest version of the event synchronization component provides a deduplication trigger specific to Tivoli Monitoring called itm_deduplication.
- Update the EIF Probe Rules
The Netcool/OMNIbus Probe for Tivoli EIF should be updated with the latest versions of the IBM Tivoli Monitoring probe rules files. This task should be performed by the Netcool/OMNIbus administrator.
Parent topic:
Set up event forwarding to Netcool/OMNIbus