Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
cancel
Showing results for 
Search instead for 
Did you mean: 
Former Member

Many of you aware of a new feature in SAP PI 7.31 which is Component Based Message Alerting ( CMBA) . You can find more information about CMBA in Michal's blog at http://scn.sap.com/community/pi-and-soa-middleware/blog/2012/03/25/michals-pi-tips-component-based-m...

But there are some questions about components that runs on AS ABAP system ( ABAP proxies) .

  • Is it possible to capture ABAP proxy errors in SAP PI 7.31?  - Answer : Yes
  • Can we get alerts from CMBA for  such failures? - Answer YES
  • What are the configurations to be done in ECC and PI systems?    - Answer- There are some

The following steps should be done

1) Create an alert rule in PI for ABAP proxy components and activate the alert rule .

2) Create a TCP/IP connection named CENTRALMONITORINGSERVER-XIALERTS in ECC with program ID SXMS_ALERT_ERROR_RECEIVE

3) Create a RFC connection in PI .Points to ECC ( You can reuse your existing IDOC default destination as well )

4) Create JCO resource adapter + JCA connection Factory in NWA

Steps 2,3,4 should be done in each ABAP system which are connected to AAE/AEX.

Alert Rule in PI

The alert rule should look like this and I have two connected ABAP proxy systems.Make sure you checked ABAP Runtime option in Message Status Tab

TCP/IP connection in ECC

Create TCP/IP connection named as CENTRALMONITORINGSERVER-XIALERTS, Connection Type T with program ID as SXMS_ALERT_ERROR_RECEIVE and gateway host as PI system details. Please refer  OSS note 1584248.

This RFC will be used to send alert events to AAE/AEX system

I am reusing the default IDOC destination (i.e) XI_IDOC_DEFAULT_DESTINATION for this configuration hence step 3 is not required in my case. But you can create a new a RFC destination as per http://help.sap.com/saphelp_nw73/helpdata/en/C2/91865252C84716B3B8BE394851C9C0/frameset.htm.

JCO resource adapter + Connection Factory

Now there should some activities to be done in NWA.

-Go to Configuration-->Infrastructure -->Application Resources

     Create a New resource adapter

Select SAPJRATemplate

In application field , please enter value on your own for each ABAP AS system

Enter Unique Value for JNDI name

Please enter the following parameters

Program ID           : SXMS_ALERT_ERROR_RECEIVE

MaxThread Count  :  <Your own value ? Normally this should be 3

Gateway server     :  PI gateway Server

Gateway service    :  PI gateway Service

Destination name  : XI_IDOC_DEFAULT_DESTINATION

In the next step JCA connection Factory Set up, please enter the same JNDI name which you entered in the previous step

And in configuration Properties , enter the DestinationName (i.e) _IDOC_DEFAULT_DESTINATION

Thats alll :smile:

How to test

Please make sure you configured alert consumer+ email client configurations in NWA to receive the alert notifications as per Michal's bolg

Create a alert event like simple stop Sender SOAP adpater in PI which is used to send ABAP proxy messages from ECC to PI and this will be throw an error message " Channel Stopped by Administration Task "   and wait for the alert consumer job to finish.

You could see the email alert in your inbox.

Original Source : http://help.sap.com/saphelp_nw73ehp1/helpdata/en/ce/d9b40646464dc78d750169d25d7278/content.htm

Thanks to michal.krawczyk2 for his valuable inputs :smile:

16 Comments
Labels in this area