Show TOC

Configuring Component-Based Message AlertingLocate this document in the navigation structure

Use

In releases up to SAP NetWeaver 7.3, SAP provided the Alert Framework mechanism, known also as message-based alerting. With Enhancement Package 1 for SAP NetWeaver 7.3 and newer releases, SAP provides additionally a new component-based message alerting mechanism.

The new component-based message alerting has been introduced since with the Java-only PI installation types there is no ABAP stack required, and therefore the existing message-based alerting solution (which is ABAP-based) is not natively supported.

During the installation of SAP NetWeaver release that supports both alerting mechanisms, or during an upgrade to such a release, you should choose which of these alerting mechanisms you want to use in your system.

Below you can find the steps on how to perform basic configuration of the new alerting mechanism during installation or upgrade.

Procedure

Installation Notes

When you have installed enhancement package 1 for SAP NetWeaver 7.3, the CTC wizard configures component-based message alerting automatically.

Find below the steps that are performed by the CTC wizard (for the case you need to manually configure this feature).

When you want to use the new component-based message alerting, make sure that you adapt the corresponding parameters (ALERTING_TARGET or alerting.target as described below) in all involved runtime engines (ABAP Integration Engines, Central Adapter Engine and Non-Central Adapter Engine) as follows:

  • Use transaction SXMB_ADM to configure Integration Engine.

  • Use SAP NetWeaver Administrator ( Start of the navigation path Configuration  Next navigation step Infrastructure Next navigation step JAVA System Properties Next navigation step Services: XPI Service: AF Core End of the navigation path) to configure Advanced Adapter Engine.

    Note that the alerting parameters of the XPI Service: AF Core service are not online modifiable. When you change their value, make sure you restart the system for the changes to take effect.

Installation Steps for the Integration Engine

The following configuration steps are only relevant in case you have chosen the dual-stack installation option for SAP PI.

  1. In the SAP system of the Integration Server, choose the Integration Engine Administration transaction (transaction code SXMB_ADM).

  2. Choose Integration Engine Configuration .

  3. Specify the runtime engine that should be configured as Alert Engine (in field Corresponding Integ. Server ).

  4. Select the change mode.

  5. Use parameter ALERTING_IS_ACTIVE to switch on alerting for this runtime engine.

  6. Add parameter ALERTING_TARGET and set a value for it in one of the following ways:

    • Set 1 to switch on component-based message alerting. SAP recommends this option.

    • Set 0 in case you want to use the "classic" Alert Framework mechanism. SAP does not recommend this option.

    Note The parameters ALERTING_IS_ACTIVE and ALERTING_TARGET belong to the category MONITOR

Installation Steps for the Advanced Adapter Engine

The following configuration steps are relevant both for single-stack and dual-stack installation of SAP PI.

  1. Start the SAP NetWeaver Administrator.

    Specify the following information in your browser: http://[host]:[port]/nwa.

  2. Navigate to Start of the navigation path Configuration  Next navigation step Infrastructure Next navigation step JAVA System Properties Next navigation step XPI Services: AF Core  End of the navigation path and choose tab Services .

  3. Set the value of the alerting.target service property to 1.

    and alerting.isActive (value true).

  4. Set the value of the alerting.target service property in one of the following ways:

    • Set 1 to switch on component-based message alerting. SAP recommends this option.

    • Set 0 in case you want to use the "classic" Alert Framework mechanism. SAP does not recommend this option.

      Note that if you want to use the Alert Framework mechanism for a new single-stack installation, you need to follow the steps described in the Message Alerting for SAP PI Advanced Adapter Engine Extended article: http://scn.sap.com/docs/DOC-3525Information published on SAP site

  5. Restart the system for the changes to take effect.

Upgrade Steps

When you upgrade your system to Enhancement Package 1 for SAP NetWeaver 7.3, you can choose to upgrade to single-stack or to a dual stack system. In case the "classical" Alert Framework mechanism has been switched on your system before the upgrade, the CTC wizard can ask you if you like to switch on the new component-based message alerting mechanism. In case you upgrade your system to enhancement package 1 for SAP NetWeaver 7.3, and in case the "classic" alerting function is switched off, the configuration is not changed.

During the upgrade, the above described configuration parameters and properties of the Integration Engine and the Advanced Adapter Engine can take the same range of values. Depending on the settings of the system you upgrade and the upgrade path you choose, you can choose one of the following:

  • Upgrade to dual-stack system.

    In this case, SAP recommends choosing the component-based message alerting mechanism.

    Alternatively, you can choose to use the Alert Framework mechanism.

  • Upgrade to single-stack system.

    In this case, SAP recommends choosing the component-based message alerting mechanism.

    Note that if you want to use the Alert Framework mechanism for an upgrade to single-stack system, you need to follow the steps described in the Message Alerting for SAP PI Advanced Adapter Engine Extended article: http://scn.sap.com/docs/DOC-3525Information published on SAP site. SAP does not recommend this option.

More Information

SAP note 1826188 Information published on SAP site provides information about the impact on switching to component-based message alerting.

The configuration and usage of the new component-based message alerting mechanism are described in Component-Based Message Alerting .