Show TOC

Integrating Alert Framework-Based SystemsLocate this document in the navigation structure

Use

When creating an alert rule you should specify to which runtime components in your PI domain it would apply. When you specify a runtime component that runs on AS ABAP system, there are three possible cases:

  • Systems that support the component-based message alerting and are configured to use it. These systems have Alert Engine and can process local alert events and generate alerts.

  • Systems that support both alerting mechanisms, the component-based message alerting and the Alert Framework, and are configured to use the Alert Framework.

  • Systems that support only the Alert Framework mechanism provided in earlier SAP NetWeaver releases. These systems lack Alert Engine and can only generate alert events.

For the second and third case, if you want to integrate such systems in the component-based message alerting mechanism used in your PI domain, you would need to perform the additional steps described below.

Prerequisites

  • The user account you use is allowed to use transactions SXMB_ADM and SM59.

  • The user account you use is allowed to view and modify system details in SAP NetWeaver Administrator. For more information, see SAP NetWeaver Administrator .

  • You are allowed to configure where an alert consumer should connect to retrieve alerts.

Procedure

  1. When creating or managing an alert rule that you want to use for systems in your PI domain that support only the Alert Framework mechanism, make sure you have added these systems as components to the alert rule.

  2. Activate the alert rule.

    The system recognizes when an alert rule applies to older Alert Framework-based systems. Instead of deploying the rule on these systems, it deploys it to the Alert Engine on the central Advanced Adapter Engine (AAE).

  3. Configure the AS ABAP systems to send alert events to the central AAE system as described in SAP Note 1584248 Information published on SAP site.

  4. On the central AAE system, for each AS ABAP system you configured in the previous step, you should create a resource adapter in the following way:

    1. Log on to SAP NetWeaver Administrator and navigate to Start of the navigation path Configuration Next navigation step Infrastructure Next navigation step Application Resources End of the navigation path.

      For more information, see Application Resources Management .

    2. Choose Start of the navigation path Create New Resource Next navigation step New Resource Adapter End of the navigation path.

    3. Select the SAPJRATemplate template.

    4. Enter a name of your choice application and choose Next .

    5. In the Resource Adapter step, choose the Settings tab and enter a unique (for each AS ABAP system) value in the JNDI Name field.

    6. On the Properties tab, enter the following details:

      • For ProgramID , enter SXMS_ALERT_ERROR_RECEIVE .

      • For GatewayServer and GatewayService , enter the same values you used for configuring the gateway properties of the TCP destination on the AS ABAP system as described in SAP Note 1584248.

      • For MaxReaderThreadCount enter 3 .

      • For DestinationName , enter a destination that points to the ABAP system.

        For more information about how to create this destination, see Destination Service and Parameters for SAP JRA Configuration .

    7. Choose Next until you reach the JCA Connection Factory step, and then proceed as follows:

      • On the Namespace tab, enter a unique (for each AS ABAP system) value in the JNDI Name field.

      • On the Configuration Properties tab, enter the same destination you specified earlier on the Resource Adapter step.

    8. Choose Save .

  5. For all alert consumers registered for the alert rule, configure them to connect to the central AAE system to retrieve the alerts generated for the corresponding AS ABAP systems.

Result

The Alert Engine on the central AAE is ready to receive and process alert events coming from older Alert Framework-based systems. The alerting mechanism behaves in the following way:

  1. When an Alert Framework-based system generates an alert event, it sends it to the central AAE system for processing.

  2. The Alert Engine on the central AAE system does the following:

    1. Obtains and stores the alert rules that apply for the Alert Framework-based system.

    2. Processes the "remote" alert events coming from the external AS ABAP system using the alert rules that apply to this system and generates alerts.

      Note that it performs this processing separately from the processing of the alert events generated locally on the central AAE system.

    3. For each alert consumer assigned for the alert rules in question, the Alert Engine stores the alerts generated for the external system in a dedicated local store for this consumer.

  3. An alert consumer connects to the central AAE system and retrieves the alerts generated for it from the corresponding local store.

    This way the alert consumer receives the alerts originating from alert events on the external AS ABAP system.

The figure below illustrates the flow of alert events and alert rules among systems involved in this scenario.

More Information