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 acknowledgement expiration and resurface status update event behavior
This section outlines the process for configuring acknowledgement expiration and resurface status update event behavior.
The get_config_parms procedure in the <event_sync_install_dir>/omnibus/itm_proc.sql file defines three configuration parameters:
set sit_ack_expired_def_action = ’REJECT’ set sit_resurface_def_action = ’ACCEPT’ set situpdate_conf_file = ’situpdate.conf’
When unidirectional architecture is used, the itm_proc.sql file must be configured to accept the acknowledgment expiration and resurface status update events from the hub monitoring servers.
The sit_ack_expired_def_action variable defines the action to be taken for an event by the OMNIbus server when an acknowledgment expiration status update is received for an event from a hub monitoring server. An acknowledgment expiration status update occurs if the event was acknowledged in the Tivoli Enterprise Portal with a timeout and the event is still true when the timeout expires. The default action is to reject the request if the event is still in the acknowledged state in the Netcool/OMNIbus ObjectServer. In this case, OMNIbus sends information back to the hub monitoring server to change the state of the event from Acknowledgement Expired to Acknowledged. If you want to change the action taken by the OMNIbus server to Accept the acknowledgment expiration, modify the statement in itm_proc.sql to set sit_ack_expired_def_action = ’ACCEPT’. In this case, the event is deacknowledged in Netcool/OMNIbus but still has the acknowledged with expiration status in the hub monitoring server.
The variable sit_resurface_def_action defines the action to be taken by the OMNIbus server when a situation event has resurfaced in IBM Tivoli Monitoring. An event is resurfaced when it has been deacknowledged in the Tivoli Enterprise Portal Situation Event Console. The default action of the OMNIbus server is to Accept this request and Deacknowledge the event. If you would like to change the action taken by OMNIbus server to Reject the resurface of the event, modify the statement to set sit_resurface_def_action = ’REJECT’ in itm_proc.sql. If the action is REJECT, OMNIbus then sends information back to the hub monitoring server to change the state of the event back to Acknowledged and the event remains in the acknowledged state in the Netcool/OMNIbus ObjectServer.
The variable situpdate_conf_file specifies the name of the configuration file to be used by the IBM Tivoli Monitoring Situation Update Forwarder. If you would like to change the name of the configuration file, modify the statement to set situpdate_conf_file = ’newname.conf’.
After modifying itm_proc.sql, issue the following command on your Netcool/OMNIbus ObjectServer:
Where:
- 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