Page tree
Skip to end of metadata
Go to start of metadata


In this Wiki, we will take a look at how to set up Component Based Message Alerting (CBMA) in SAP Process Integration (PI) or SAP Process Orchestration (PO) systems and we will take a look at how to troubleshoot for errors/issues using the XPI Inspector tool.


We will provide the links which describe how to configure this functionality.


As SAP PI has transitioned from the traditional Dual Stack system to the Java only system, the Alerting mechanism which relied mainly on ABAP technologies has also needed to transition to the Java only world. CBMA is the new alerting tool for PI/PO systems. 


How to configure Component Based Message Alerting is documented in the resources below:

SAP help: Alert Configuration
SAP help Configuring Component-Based Message Alerting
SAP help Component-Based Message Alerting

SAP Community blog: Michal’s PI tips: Component-Based Message Alerting

Key points:

  1. If you have a Dual stack PI system Go to transaction SXMS_ADMIN Specific Configuration

    ALERTING_IS_ACTIVE = 1 - switches on CBMA alerting for the ABAP Runtime engine
    ALERTING_TARGET = 1 - switches on CBMA alerting on ABAP side

  2. In the Java NetWeaver Administrator go to the URL http://<server>:<port>/nwa/sys-config
    → Services → XPI Services: AF Core
    alerting.isActive = true - switches on alerting for the Java Runtime engine = 1 - switches on CBMA Alerting on Java side

  3. Ensure these parameters are set at Instance level (ZATPL_AIO) and not at Node level (IDxxxxx)

  4. These basic settings must also be configured in any other systems that you wish to include in your alerting landscape e.g. backend ABAP Proxy systems or decentral Adapter Engines. See the notes below for details:
    1. SAP KBA 2360905 The Component-Based Message Alert doesn't work on backend ECC system
    2. SAP KBA 2200611 Alerts not forwarded from Non-Central Adapter Engine in SAP PI


Use the XPI Inspector tool with Example 100 (Custom) to collect traces for the following logging locations:

See SAP KBA 2381478 XPI traces for Component Based Message Alerting, for more details.

Reading the XPI Trace:

  • Open the resulting zip file and go to result.xml
  • Click on the hyperlink under the Errors
  1. Search for text: "PI error event had been sent to the master queue" =>

    Tip: You can use the MsgId value to search the trace for all alert related entries for this message ID.

  2. Search for text: "PI error event had been retrieved from the master queue" =>

  3. RulesEngine.executeRules

  4. Search for text: "PI alert had been delivered to consumer queue" =>

  5. AlertConsumerJob.sendMail

Some Known Issues:

SAP Note 2411534 CBMA alert suppressing improvment
SAP Note 1980625 Adding jms.persistence property to XPI Service: AF Core
SAP Note 2122500 Alerting: wrong mail receiver in e-mail consumer job
SAP Note 2279043 New Feature: Alerting: changes and improvements in Component Based Message Alerting
SAP Note 2119910 PI component-based alerting: No writing of logs

  • No labels