IBM Tivoli Netcool/OMNIbus Version 8.1

Triggers

You can use triggers to detect changes in the ObjectServer and run automated responses to these changes. This enables the ObjectServer to process alerts without requiring an operator to take action. You can also use automation to manage deduplication, which reduces the quantity of data held in the ObjectServer by eliminating duplicate events.

You can use database triggers, temporal triggers, and signal triggers in automations:

Database triggers fire if any of the following database changes occur:
- An attempt is made to insert a row into a table.
- An attempt is made to update a row in a table.
- An attempt is made to delete a row from a table.
- An attempt is made to insert a row into a table, but a row with the same value for the Identifier primary key already exists. You can use a reinsert trigger to deduplicate rows in the ObjectServer.
  You can create your own deduplication trigger to cause a different action to occur.
Temporal triggers fire repeatedly based on a specified frequency.
For example, you can use a temporal trigger to delete all clear rows (Severity = 0) from the alerts.status table that have not been modified within a certain period of time.
Signal triggers fire when a predefined system signal is raised or when a user-defined signal is raised using the RAISE SIGNAL command.
For example, you can send an email to an operator when the ObjectServer starts or stops because system signals are generated.

You do not have to do anything to create or configure system signals. You must explicitly create, raise, and drop user-defined signals.

Library | Support |