
Users can create and administrate alert rules using the corresponding tools provided in the system. Users who are responsible for maintaining the PI system can manage alert rules using SAP NetWeaver Administrator. Users who are responsible for configuring the PI system can also manage alert rules directly in Integration Directory.
Configuration Basics
The creation and configuration of alert rules is a task that should be performed on the central system in your PI domain, where you also run the Integration Directory. You cannot configure alert rules on decentral systems.
Subscribing consumers for alert rules in not part of the alert configuration process. The subscription process is driven by the alert consumer, which takes care for discovering available alert rules and registering itself as a consumer for the rules.
Best Practices
You can use the following best practice recommendations when configuring alert rules:
AS ABAP-based runtime components
Assign the corresponding sender and receiver agreement. Alternatively, you can assign the corresponding sender and receiver interface.
AS Java-based runtime components, when using Integration Flow or integrated configuration
When the configuration scenario is implemented via Integration Flow or integrated configuration, the alert configuration should be done by referencing the existing Integration Flow or integrated configuration object. Consider the following aspects:
When using Integration Flow, the Alert Engine does not use the message header attributes to check if that message matches the alert rule; it uses the Integration Flow ID instead. It is important to remember that the Integration Flow ID is not known on other runtime components outside the Advanced Adapter Engine Extended (AEX) system. For example, if the message is passed from the AEX system to an ABAP Proxy system, the Integration Flow ID is not passed to subsequent runtime components. Therefore, if you want the alert rule to match the message, you should also add to the rule the corresponding configuration objects for the interfaces that are relevant in that ABAP Proxy.
Integrated configuration is defined by sender party, sender component, and sender interface combined with sender namespace. The receiver interface combined with namespace are optional.
AS Java-based runtime components
Create an alert rule that contains two separate configuration objects:
One with sender interface to catch exceptions before receiver determination.
One with receiver interface to catch exceptions after receiver determination.