IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Set up event forwarding to Netcool/OMNIbus > Customize Event Integration > Customize how the IBM Tivoli Monitoring OMNIbus triggers handle event status updates from the monitoring servers
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Configure stop situation event behavior for pure situations
When the IBM Tivoli Monitoring triggers in Netcool/OMNIbus process a situation stop event, the triggers clear all events for the situation that are detected by the remote monitoring server specified by the ITMThruNode OMNIbus attribute. However, you can configure the IBM Tivoli Monitoring triggers to ignore situation stop events for pure events.
To configure this behavior, you must update the following statement in the itm_event_clear trigger from:
set puresitstop = ’CLOSE’;to:
set puresitstop = ’OPEN’;You can either use the Netcool/OMNIbus Administrator to edit the itm_event_clear trigger or modify the trigger in the itm_db_update.sql file provided with the IBM Tivoli Monitoring event synchronization component and then re-load the itm_db_update.sql file into Netcool/OMNIbus ObjectServer. After modifying itm_db_update.sql, issue the following command on your Netcool/OMNIbus ObjectServer:
%OMNIHOME%\..\bin\redist\isql -U <username> -P <password> -S <server_name> < <path_to_file>\itm_db_update.sql
$OMNIHOME/bin/nco_sql -user <username> -password <password> -server <server_name> < <path_to_file>/itm_db_update.sqlWhere:
- OMNIHOME
- Is the system-defined variable defining the installation location of OMNIbus.
- username
- Is the OMNIbus ObjectServer user name.
- password
- Is the OMNIbus ObjectServer password.
- server_name
- Is the OMNIbus ObjectServer name defined for process control.
- path_to_file
- Is the fully qualified path to the specified SQL file.
Parent topic:
Customize how the IBM Tivoli Monitoring OMNIbus triggers handle event status updates from the monitoring servers