
You have accessed the alert rule configuration tool. For more information, see Accessing Rules .
If you want to be able to apply an alert rule to a certain AS ABAP system, you must define this system as a business system in the Integration Directory. For more information, see Define Business System as Communication Component .
In addition, for AS ABAP systems using enhancement package 1 for SAP NetWeaver 7.3 or later releases, you must configure the communication between the corresponding AS ABAP system and the Integration Directory. For more information, see Configuring Business Systems (with Web Service Communication) .
To have the message payload information in the alert, you should configure in advance the user-defined search feature for the runtime component that processes the message. For more information, see Configuring User-Defined Message Search (for Advanced Adapter Engine) and Configuring the User-Defined Message Search (for Integration Engine).
The system stores the changes you made to the alert rule. You can complete the alert rule modification process in the following ways:
Choose .
The system performs a test of the alert rule and notifies you if some of its parameters need additional modification. You can receive notifications when the alert rule contains configuration objects or runtime components that do not exist anymore, as well as in other cases.
To distribute the alert rule to the relevant runtime components choose .
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 about activation, see Working with Change Lists .