You can use automation to detect changes in the ObjectServer and to run automated responses to these changes. This enables the ObjectServer to process alerts without requiring an operator to take action.
For example, network alerts often include the message Link Down, which indicates that there is a problem in the network. When the problem is resolved, the ObjectServer receives another alert including the message Link Up. Using a correctly-configured automation, the ObjectServer can automatically associate the two alerts, recognize that the Link Up message indicates that the problem is resolved, and delete both alerts.
You can also use automation to manage deduplication, which reduces the quantity of data held in the ObjectServer by eliminating duplicate events. Netcool/OMNIbus includes a number of standard automations.
Triggers form the basis of the ObjectServer automation subsystem. Triggers automatically perform a trigger action or fire when the ObjectServer detects an incident associated with a trigger. In a trigger, you can run SQL commands, and call procedures in response to the change.
Signals and procedures are also part of the automation subsystem. Signals can have triggers attached to them, so that the ObjectServer can automatically respond when a signal is raised. Procedures are executable programs that are created to perform common operations, and you can run them in a trigger, or from the SQL interactive interface.