Message-based Alerting

[Former Member]

Hello!

I have configured Message-based Alerting for a File -> IDoc scenario and I receive the alerts in the RWB Inbox as well as by mail. The alerts usually contain Alert-ID, Message-ID, Rule Name, Error-Code, Error-Category, Sender Interface, Sender Service, Receiver Interface and Receiver Service.

But some mails contain Alert-ID, Sender Interface and Sender Service only. I assume that these errors are triggered by the Adapter Engine as no Message-ID has been generated yet and they are not visible in SXMB_MONI.

However, I was not able to find any errors in the Adapter Monitoring nor in the Messaging System Monitoring. Is there I way I can find out what triggered these alerts using the Alert-ID?

Regards, Tanja

[bhavesh_kantilal · Accepted solution]

><i>However, I was not able to find any errors in the Adapter Monitoring nor in the Messaging System Monitoring. Is there I way I can find out what triggered these alerts using the Alert-ID?</i>

That is strange. You should have an entry of the message either in Adapter / Comm Channel Monitoring or Message Monitoring.

Also, maybe these errors are corrected ( eg : if there is some connectivity issues ) and so you are not able to see this message. Remember the adapter retires to send the message 3 times at an interval of 5 minutes for every error.

Regards

Bhavesh

[Former Member · Accepted solution]

Since they are probably triggered by the AE prior to Message ID assignment - your best bet will be to look through processed messages. See if any of these failed before being corrected (as suggested by Bhavesh)

One approach is to look in the visual admin log after turning on the trace - this always provides me with the best insights to any of my AE issues since so much can go wrong prior to IE processing.

The other is to adjust the retry count to 1 every 10 minutes in the visual admin - and turn to a high trace value.

sincerely,

--NM