CBMA not alerting for EOIO message mapping failures

[former_member230722]

Hi Experts

We are on PI 7.4 SP7 and are looking to migrate from the Alert Framework to CBMA (due to the options that it provides around exclusions of components).

We have configured CBMA in our dev environment and are successfully receiving alerts from the adapter engine and the integration engine using the default alert rule. 

The issue we have is with EOIO message mapping failures.  We get alerts for other mapping failures where the QOS is not EOIO (i.e. EO).  We are not trying to monitor blocked queues or pending messages.  We just want to capture the alert when the actual EOIO message gets processed and goes into system error.  When we change the interface to EO, we do get the alerts but not when we switch it back to EOIO even though the message has been processed and gone to system error status.

Does anybody have any ideas around getting this to work?  Are we missing something?

Many thanks,

Georgia

[former_member186851]

Hello Georgia.

check the below link and try the approach,I dont think normal mechanism of CBMA will work for EOIO.

Alerting for stuck messages on the Adapter Engine | SCN

[former_member230722]

Hi,

Thanks for the reply.  The link refers to monitoring for stuck messages that are not in error status - I am aware that CBMA won't monitor for queue build-up and queueed messages that are not in error.  I am not interested in capturing queued messages. 

I just want to capture the error of the message that did fail and went into error status irrespectively of whether it blocks a queue behind it.  This was being captured previously with the Alert Framework. 

Any suggestions?

Thanks

[vadimklimov]

Hello Raghuraman,

Alerting works regardless quality of service, so shall work well for both EO and EOIO scenarios.

Hello Georgia,

We have EOIO scenarios and use CBMA, and it generates alerts. So, may I ask you to confirm that:

• The message for the faulty EOIO scenario gets into status "System Error";
• Following steps described in Tihomir's blog , please check if alert message gets produced. If not, then there are recommendations in the mentioned blog on how you can trace alert evaluation and generation events and see if they get processed or not.

Regards,

Vadim

[former_member186851]

Ok Vadim,I thought it wont be working for EOIO.

[former_member230722]

Hi Vadim,

The diagnostic information in Tihomir's blog is very useful. 

Eventually, SAP suggested note 1999515 - PI: Some errors are not captured in Component-Based Message Alerting.  Although this was not applicable for our service pack, we were able to apply it successfully and it did resolve our issue.

Thanks for your help,

Georgia

[vadimklimov]

Hello Georgia,

Thank you for the update - good remark regarding the Note and fix!

Regards,

Vadim