IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Set up event forwarding to Netcool/OMNIbus > Customize Event Integration

IBM Tivoli Monitoring, Version 6.3 Fix Pack 2


Convert from unidirectional architecture to bidirectional architecture

This section outlines the steps for converting from unidirectional to bidirectional architecture.

If you are using the unidirectional architecture for event integration between your hub monitoring servers and Netcool/OMNIbus and you decide to switch to the bidirectional architecture, you must perform the following tasks for each of your Netcool/OMNIbus ObjectServers that will be sending event status updates back to a hub monitoring server:

  1. Ensure you have the IBM Tivoli Monitoring Event Synchronization Component installed on the machine with your Netcool/OMNIbus ObjectServer.

  2. Configure the OMNIbus server to support execution from scripts for running the Situation Update Forwarder.

  3. Define each monitoring server that is forwarding events to Netcool/OMNIbus ObjectServer to the IBM Tivoli Monitoring Situation Update Forwarder and start the IBM Tivoli Monitoring Situation Update Forwarder.

  4. Update the Netcool/OMNIbus ObjectServer database schema to add the IBM Tivoli Monitoring triggers that send bi-directional event status updates to your hub monitoring servers.

    Follow the procedure in Update the OMNIbus database schema on single-tier or aggregation tier ObjectServers to load the itm_sync.sql file. You do not need to load the itm_db_update.sql or itm_proc.sql files because they were loaded into the ObjectServer when you enabled unidirectional event integration.

  5. Edit the get_config_parms procedure in Netcool/OMNIbus Object to choose the default bidirectional behavior when an Acknowledgement Expired event status update is sent from the hub monitoring server to Netcool/OMNIbus:

    1. Use the nco_config utility to start Netcool/OMNIbus Administrator.

    2. Connect to the Netcool/OMNIbus ObjectServer where you are making the change.

    3. Select Automation → Procedures from the menu.

    4. Edit the get_config_parms procedure and change:

        set sit_ack_expired_def_action = 'ACCEPT';

      to

        set sit_ack_expired_def_action = 'REJECT';

    5. Save the trigger and exit from Netcool/OMNIbus Administrator.


Parent topic:

Customize Event Integration

+

Search Tips   |   Advanced Search