Proxy alerting with CMBA on AEX 7.31

[matthias_isenburg]

cmba = component-based message alerting

Hi All,

like explained on

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

and with the help of the following blogs

http://scn.sap.com/community/pi-and-soa-middleware/blog/2013/02/26/sap-pi-731-abap-proxy-monitoring-...
http://scn.sap.com/community/pi-and-soa-middleware/blog/2012/03/25/michals-pi-tips-component-based-m...

i tried to configure alerting of a abap proxy system which is part of the pi domain (runtime component).

For any reason the alerting doesn't work (only for proxy systems).

Some facts:

- We are running AEX 7.31 on SPS12 and our ABAP Proxy is a SAP Release 7.31 SPS07.

- For the proxy system, we want to use the (older) alerting mechanisms "Alert Framework-based system". So the ALERT EVENTS should come from the proxy using the alert rules of the AEX.

sap note  1584248:
The existence of the destination CENTRALMONITORINGSERVER-XIALERTS now suppresses the call of the central monitoring server and the alert calls occur as of now via the manually-created destination on the AAE

- IE configuration on proxy:

ALERTING_IS_ACTIVE = 1 (1 - Alerting is activated on this PI component (default setting)
ALERTING_TARGET = 0 (0 - Alert event is sent to the central alert server (default setting)

- configurations

1. Alert rule on pi -> done
2. alert consumer for e-mail notifications/ AlertConsumerJob on pi -> done & works (Alerting ONLY on the Central Adapter Engine (AEX java only) using CMBA works successfully.)
3. RFC on proxy side: CENTRALMONITORINGSERVER-XIALERTS -> done & test works
4. RFC connection on pi. Points to proxy: "XI_IDOC_DEFAULT_DESTINATION" -> done
5. JCO resource adapter + JCA connection Factory on pi -> done

- tests on proxy

program = SXMSALERT_ALERT_TEST

UTC Stamp               Counter    Local Date    Local Time    MsgGuid

20140929084707,0530220          0   29.09.2014    10:47:07      0200040000051ED491F6A62AF98443C5
*Calling Monitoring Server starting new task
20140929084707,0571360          0   29.09.2014    10:47:07      0200040000051ED491F6A62AF98443C5
*   > with destination IN GROUP DEFAULT
20140929084707,0639530          0   29.09.2014    10:47:07      0200040000051ED491F6A62AF98443C5
*AlertRecords successfully delivered*
20140929084707,0660230          0   29.09.2014    10:47:07      0200040000051ED491F6A62AF98443C5
*Delegate processing of SXMS_ALERT_ERROR_RECEIVE to TCP/IP destination CENTRALMONITORINGSERVER-XIALERTS
20140929084709,7510100          0   29.09.2014    10:47:09      0200040000051ED491F6A62AF98443C5
*Successfully returned from TCP/IP call to SXMS_ALERT_ERROR_RECEIVE

* Alert sent successfuly via SXMS_ALERT_ERROR_SEND. MsgId:  0200040000051ED491F6A62AF98443C5

-> No Errors were displayed with program SXMSALERT_LOGREADER.

Summarized,

1. Alerting ONLY on the Central Adapter Engine (AEX java only) using CMBA works successfully
2. Program "SXMSALERT_ALERT_TEST" sends successfully (no errors) alert events from the proxy with TCP/IP destination CENTRALMONITORINGSERVER-XIALERTS, but no alert is generated on the alert engine.

Where could be the error? How can i analyze this issue? Maybe with with the help of this picture?

http://help.sap.com/static/saphelp_nw73ehp1/en/ce/d9b40646464dc78d750169d25d7278/d36c33119ea3423f9a5...

Are the "External test Alert Events" really arrived on the "Alert Engine"? How can i check this?

Do you have other ideas?

Thanks in advance,
Matthias

[Former Member]

Hello Matthias,

I am working on the same configuration at the moment and I am stuck at the same point - CBMA works fine for the AEX but not for the ABAP Proxy. Have you been able to solve your problem?

Thanks for your reply,

Markus

[matthias_isenburg]

Hi Markus,

Since 29.09.2014 we have an OPEN sap ticket. So far no solution.

To reproduce the problem, please do the following:

PO log configuration:
com.sap.aii.af.service.alerting = "ALL"
com.sap.aii.af.service.alert.router = "ALL"

Now, execute report "SXMSALERT_ALERT_TEST" in the PROXY.

DefaultTrace on PO:

"ABAP error code !XI Alert Test ErrorCodeis not available in errorCodesToLabels.properties"-message is logged in the default Trace file.

Afterwards sth. like,

Entering method with ({
"ErrCat": "!XI Alert TestArea",
"ErrCode": "!XI Alert Test ErrorCode",
"ErrText": "This is only a test alert!",
"FromParty": "!XI Alert Test SenderParty",
"FromService": "!XI Alert Test SenderService",
"Interface": "!XI Alert Test ReceiverInterface",
"MsgId": "02000400006D1EE4A0A113A8D73F8E00",
"Namespace": "!XI Alert Test com/sap/xi/receiver/service/alerting",
"ToParty": "!XI Alert Test ReceiverParty",
"ToService": "!XI Alert Test ReceiverService"
})

with

No alert rule found yet. Evaluate default rule...

First insights with SAP:

• /pimon -> Monitoring -> Adapter-Engine -> Cache-Monitor, register alert rules (Adapter Engine): NO ENTRY

Reason why only CBMA works fine for the AEX:

When i activate the component "Central Adapter Engine" for any Alert Rule, the Object is written in the CPA Cache. This is why, alerting (ONLY) on the Central Adapter Engine using CMBA works successfully.

When i deacivate the "Central Adapter Engine" in the Alert Rule and activate (ONLY) the PROXY, the CPA Cache remains empty.

• New info from SAP is now to check the "Message Header Rules" under /pimon -> Configuration and Administration -> Common -> Message Alert Configuration -> DEFAULT_ALERTRULE (in ou case). The alerts are evaluated based on the header rules. But in our case i can't add sth. here. All is greyed out.

Also in edit mode.By the way in our case no Message Header Rules is maintained.

Maybe it helps,
Matthias

[Former Member]

Hello Matthias,

the alerting is now working for our system, Alerts from the ABAP Proxy System are processed by the CBMA. Our problem was that a collegue had accidently deleted the DEFAULT_ALERTRULE right before I did my tests.

If I get your last post right your Problem ist that the rules you create in the Integration Builder do no get copied to the CPA Cache when you activate them. I tested it, it is working fine on our System, even for rules where only an ABAP Proxy System is activated and not the Central Adapter Engine.

Did you create the DEFAULT_RULE on your system? Is this rule activated as expected an working fine?

Our System is NW 7.4 SP7 but most components were patched to a current state in November, maybe a SP update will help you with your problem?

Best regards,

Markus

[matthias_isenburg]

Hi Markus,

Thanks for your informations. Now everything points to the fact, that we have really a CPA CAche problem.

The "DEFAULT_ALERTRULE" was created automatically with the flag on "Create Default Rule" and works successfully for the Central Adapter Engine. So i assume no configuration failure for my part. I hope so 😉

Maybe, a SP Update helps. We are running SAP PO on 7.31 SP12.

But i still hope of the SAP Support.

Best regards,
Matthias

[Former Member]

Right, if you entered an Alert Consumer there is nothing more to configure, then I wish you good luck with your support ticket!

[JaySchwendemann]

Dear all,

sorry for "highjacking" this but just for chance: Was there a reason to got the "Use Message Alert Framework" way, even if your Proxy NW System does support CBMA as its NW 7.31?

I'm not really sure if CBMA would be supported in a "native" manner by such systems. By any means I couldn't get it to work with native CBMA but there was not problem configuring my proxy NW 7.4 system to use old Message Alert Framework following the mentioned blog at the beginning.

So I'm wondering: Is native CBMA for proxy receiver systems > 7.3 really an option?

[Former Member]

Hello Jens,

as I already wrote, we have our NW 7.4 ABAP Proxy Systems configured with CBMA with our PO system as alert receiver as it was documented in the links on top, so native CBMA for a proxy system is an option.

Does this answer your question?

Best regards,

Markus

[JaySchwendemann]

Hi Markus,

thanks for answering. I understand that you may connect a NW 7.4 ABAP Proxy system to a PI AEX / PO system where the latter uses CBMA.

However, you said you used the links on the top to set this up. Those links however point to a solution where the NW 7.4 ABAP Proxy system actually uses Message Alert Framework in favor of CBMA and only PI / PO uses CBMA.

You could check how your ABAP system is set up via transaction SXMS_IECONF --> Category = MONITOR --> Parameter = ALERTING_TARGET --> Value = 1.

AFAIK setting the Parameter ALERTING_TARGET to 1 activates direct CBMA in ABAP system. However, I'm not completely sure if this is actually supported when having a PI AEX or a PO

Many thanks and kind regards

Jens

[Former Member]

Hello Jens,

The first link (http://help.sap.com/saphelp_nw73ehp1/helpdata/en/ce/d9b40646464dc78d750169d25d7278/content.htm) explains how configure the ABAP system & AEX, it refers to Note 1584248 "Adapter Engine Extended (AEX) as alert recipient" that explains how the configuration on the ABAP system has to be configured, main point on the ABAP System is the creation of the sm59 connection with the correct name.

ALERTING_TARGET does not has to be set, it is not configured in our case at all (An ABAP ERP System based on NW 7.4 sends its alerts to a PI/PO AEX (Java Only) based on NW 7.4).

Best regards,

Markus

[JaySchwendemann]

Hello Markus,

thanks for your answer. I think the main point that's still not completely clear to me is: Does one really have to configure its ABAP proxy system with NW 7.31 or higher in such way the note http://service.sap.com/sap/support/notes/1584248 suggests?

The note says "In an AEX installation, the Advanced Adapter Engine (AAE) must be able to process alert events that come from existing ABAP systems of releases lower than SAP NetWeaver 7.3.1."

So for me this sounds like native CBMA within the ABAP proxy system in case of 7.31 or higher should be supported.

I however acknowledge the fact that you can indeed set up a NW 7.31 or higher ABAP proxy system to use Alert Framework with setup outlined in mentioned note http://service.sap.com/sap/support/notes/1584248. but this, in my opinion does not use CBMA on the ABAP system and should not be necessary.

Of course, I could be terribly wrong, that's why I'm asking if someone did really set up such way

Cheers

Jens

[Former Member]

Hi Jens,

not sure if you are still watching this post. Anyway I have same doubt as you. PO CBMA works with old alert in ECC, but not when enabling CBMA at ECC.

I am going to create OSS for sap to see what they will say. If you have any update on this matter, please share.

Thanks

Jayson

[JaySchwendemann]

Jayson,

yeah, we (on a sandbox environment) succeeded in setting this up.

The main point the documentation was lacking (at that time, could still be the case, did not check) was that you ought to use some configuration from setting up the WS Adapter as Alerting Rules use the same mechanism for distribution to the AS ABAP receiver business systems.

This is what I done in short:

• Setup configuration URL of the receiving business system in SLD
• In ID go to tab "Logon data" and activate "Support Distribution of Configuration". Giva a user that has enought rights in receiver BS.
• Configure HTTP Destinatin "INTEGRATION_DIRECTORY_HMI" in receiver BS
• Execute transaction "SXI_CACHE_CONFIG" in receiver BS

Will blog about this in detail. Stay tuned.

Thanks to for pointing me to the right direction about this.

Cheers

Jens

[Former Member]

Hi Jens

thank you very much for the update. Did you also have to setup WS runtime in the ABAP AS (SRT_ADMIN)? there is quite a few config to do to enable WS adapter, I am really looking forward to your blog. However not sure if I can wait so long.

When do you think you could make the blog available? Would you post the link to your blog in this discussion so that we can easily navigate to your blog?

Really eager to see if I can make it work in my environment based on your experience.

Thank you so much.

Jayson

[Former Member]

Also, Jens

you've commented in the blog http://scn.sap.com/community/pi-and-soa-middleware/blog/2012/12/27/component-based-message-alerting-..., I personally think what it said in the blog is not exactly correct, the blog basically sets up another email mechanism in ABAP AS by capturing the alert. What I understand is that CBMA is a central piece, alerts in ABAP should be sent to PO / AEX, and PO consumer configuration determines email sending. So only one place to configure email, which is PO central CBMA. The blog basically deals with abap alert locally in ABAP AS, without sending alert to central CBMA.

Can you comment?

Thanks

Jayson