Alert Rule
Alert rules are objects in Integration Directory. An alert rule defines conditions at which an alert should be created. A rule contains the following information:
-
A set of Integration Directory configuration objects.
The following configuration objects can be used for an alert rule: Integration Flow, parties, communication components, sender agreement, receiver agreement, integrated configuration, and configuration scenario. Note that you can use sender agreement and receiver agreement objects only for AS ABAP-based runtime components.
-
Message status conditions and affected runtime components.
By default, an alert rule applies to all message error statuses and runtime components. During configuration the alert rule can be set to apply only to certain status groups or statuses, as well as only to certain components.
-
A list of consumers that have registered themselves for this rule.
When evaluating a message against an alert rule, in case at least one of the message parameters matches a configuration object in this rule, an Alert Engine should generate an alert.
An alert rule is identified by an ID, has a name, a description, and references to all the configuration objects for which it would be responsible. Similarly to the other PI configuration objects, it can have several versions and can also be transported to other directories of different system landscapes. An alert rule must be activated to be distributed to the Alert Engine on the runtime components to which it applies.
Default Rule
There is a unique type of alert rule referred to as "default" . This rule has the following features:
-
If you want to use it you should create it using a dedicated procedure for creating a default alert rule.
-
It has a fixed name DEFAULT_ALERTRULE and description, and you cannot modify them.
-
There are no configuration objects assigned to this rule, and you cannot assign configuration objects.
-
It applies to all message statuses, and you cannot modify these settings.
-
You are allowed to select to which runtime components it applies.
-
It shares the same life cycle as all other alert rules.
-
When created, a default alert rule has no consumers assigned to it. You should assign consumers as necessary.
When the default alert rule is present on the system, the Alert Engine uses it for evaluating all alert events and creating alerts.
Life Cycle of the Rules
Each alert rule has its own life cycle. Users can create, activate, modify, and delete an alert rule as necessary. Changes to an existing alert rule are only valid after the rule has been activated in the Integration Directory. If a rule is deleted and this deletion is activated, alert consumers obtain information about this.
You should consider the following when working with alert rules:
-
When transporting alert rules from a source to a target Integration Directory, some of the alert rule parameters can be adjusted automatically, whereas others might need to be adjusted manually. For more information, see Transporting Alert Rules .
-
An alert rule can apply to an AS ABAP system that supports only the Alert Framework mechanism available in earlier SAP NetWeaver releases. When you activate such a rule, it is deployed to the Alert Engine on the central Advanced Adapter Engine. You also need to configure the AS ABAP system to send alert events to this central Advanced Adapter Engine system as described in SAP Note 1584248
. This way you are able to integrate the older AS ABAP systems with the newer component-based message alerting.For more information, see Integrating Alert Framework-Based Systems .