cancel
Showing results for 
Search instead for 
Did you mean: 

SAP PI JMS/API provides only one message per error type

Former Member
0 Kudos

Dear all,

I`m facing with a strange behavior in PI 7.4 (API/JMS to Mail) and I hope to get some advice to find the cause:

In order to customize subject of the alert mail I set up a simple API to Mail interface based on Michal Krawczyk´s blog Component based message alerting – API.

This is running fine apart of following “tiny” unwanted feature:

Every time API is requested for alerts it responds only one message per error type for each receiver.

For example, let`s assume we got 20 errors on PI for 5 different receivers, each 4 messages and for the sake of simplicity all happened because of mapping error. Then API responds/provides only 5 error messages. But I want to get all 20 errors.

Any idea what is causing this behavior?

BTW, I get the same behavior for another similar scenario using JMS to Mail.

Thank you all in advance.

Best,

Hamed

Accepted Solutions (1)

Accepted Solutions (1)

Jochen_Gugel
Explorer
0 Kudos

Hi guys

I am colleague of Hamed, we investigated further and seem as we found the solution.
Our assumption that the alerts per errorneous message is release dependent is partly correct.
Strictly speaking the compression depends on PI System property XPI Service: AF Core alerting.suppressInterval as described in SAP Note 913858 A16b.

For CBMA this property has not been supported from start, SAP Note 2233551 contains release infos regarding support of this property.
This property is used to define the time interval for suppressing additional errors.
By Setting the value 0 the compression could be deactivated and for all errorneous Messages alerts will be created.

best regards
Jochen

Answers (1)

Answers (1)

Former Member
0 Kudos

Update: the behavior seems to be release-dependent. Unlike PI 7.40.14, the same scenario is working as required on PI 7.31.8 - API sends all error messages without any compression (one message per error type for each receiver component).

Is this behavior known to someone?

Thanks