IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Set up event forwarding to Netcool/OMNIbus > Architecture scenarios > Netcool/OMNIbus Multitiered and High-availability Architecture
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Installation and configuration
If you are installing IBM Tivoli Monitoring and Netcool/OMNIbus event integration for the first time, perform the tasks in this table.
However, if you are upgrading an existing event integration environment, see Upgrade from a previous installation of IBM Tivoli Monitoring and Netcool/OMNIbus integration.
Installation and configuration: Netcool/OMNIbus Multitiered and High-Availability Architecture ObjectServers
Task Architecture Type Administrator 1. Install Netcool/OMNIbus ObjectServers in a multitiered architecture or single-tier high availability environment if they are not already installed, or upgrade them to the fix pack version required by IBM Tivoli Monitoring.
See the Netcool/OMNIbus Information Center for detailed instructions on this task: 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. Install the Netcool/OMNIbus Probe for Tivoli EIF if it is not already installed or upgrade it to the release required by IBM Tivoli Monitoring. If you are using peer-to-peer probe failover, install and configure master and slave EIF probes.
See the Netcool/OMNIbus Information Center for detailed instructions on this task: 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. For each Netcool/OMNIbus ObjectServer in the aggregation tier or for each ObjectServer in a single-tier architecture, see Install the IBM Tivoli Monitoring Event Synchronization Component. If you are installing Netcool/OMNIbus ObjectServer in a high availability environment, install the event synchronization component on the primary and backup ObjectServer in the single-tier architecture and in the aggregation tier.
Unidirectional and bidirectional Netcool/OMNIbus 4. For each gateway between ObjectServers in a multitier or single-tier architecture, see Update gateways to map attributes. Unidirectional and bidirectional Netcool/OMNIbus 5. For each bidirectional failover gateway in an aggregation tier or single-tier with high availability, see Update the bidirectional failover gateway to replicate tables. Unidirectional and bidirectional Netcool/OMNIbus 6. For each Netcool/OMNIbus ObjectServer in the collection tier: Update the OMNIbus database schema in the collection tier. Unidirectional and bidirectional Netcool/OMNIbus 7. For each Netcool/OMNIbus ObjectServer in the aggregation tier or for each ObjectServer in the single-tier architecture, see Update the OMNIbus database schema on single-tier or aggregation tier ObjectServers. Unidirectional and bidirectional Netcool/OMNIbus 8. For each ObjectServer in the aggregation tier or in a single-tier architecture, see Change the default deduplication trigger Unidirectional and bidirectional Netcool/OMNIbus 9. For each Netcool/OMNIbus ObjectServer in the aggregation tier or in the single-tier architecture, see Configure the OMNIbus server for program execution from scripts. Bidirectional Netcool/OMNIbus 10. For each Netcool/OMNIbus ObjectServer in the aggregation tier or in the single-tier architecture, Start the IBM Tivoli Monitoring Situation Update Forwarder. See Start and stop the IBM Tivoli Monitoring Situation Update Forwarder. Bidirectional Netcool/OMNIbus 11. For each Netcool/OMNIbus ObjectServer in the display tier, see Update the OMNIbus database schema in the display tier. Unidirectional and bidirectional Netcool/OMNIbus 12. Restart each gateway that was updated in steps 4 and 5 based on the following suggested restart order for a multitier architecture:
- Restart gateways between the collection and aggregation tiers.
- Restart bidirectional failover gateways in the aggregation tier.
- Restart gateways between the aggregation and display tiers.
See the Netcool/OMNIbus Information Center for more details on restarting the gateways: http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.tivoli.namomnibus.doc/welcome_ob.htm.
Unidirectional and bidirectional Netcool/OMNIbus 13. For each EIF probe, see Configure the Netcool/OMNIbus EIF probe. If you are using a multitier architecture you must also ensure that the EIF probes are configured to connect to an ObjectServer in the collection tier.
Unidirectional and bidirectional Netcool/OMNIbus 14. For each hub monitoring server, see Configure the hub monitoring server to forward events. If you are using peer-to-peer probe failover, configure the Hub to forward events to the master probe. Unidirectional and bidirectional IBM Tivoli Monitoring 15. If you are using peer-to-peer probe failover, use the tacmd createEventDest command to create an event destination for the EIF slave probe. See the Command Reference. Unidirectional and bidirectional IBM Tivoli Monitoring 16. If you are using peer-to-peer probe failover, configure each situation to be forwarded to the event destination for the master probe and to the event destination for the slave probe using the Tivoli Enterprise Portal Situation Editor or the tacmd createsit or editsit commands. Unidirectional and bidirectional IBM Tivoli Monitoring 17. Verify installation and configuration. Unidirectional and bidirectional IBM Tivoli Monitoring and Netcool/OMNIbus 18. Determine if additional configuration tasks should be performed. See Customize Event Integration. Unidirectional and bidirectional IBM Tivoli Monitoring and Netcool/OMNIbus
Parent topic:
Netcool/OMNIbus Multitiered and High-availability Architecture