Alert monitor for messages in error status

[Former Member]

Hi, it is possible to configure de Xi Alert Monitor to show in the message body the error that shows the message monitoring?

In the SOAP header when there is an error y can see a tag "error" and it shows this info (for example):

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">

<SAP:Category>XIServer</SAP:Category>

<SAP:Code area="MAPPING">STARTUP_EXCEPTION</SAP:Code>

<SAP:P1>com.sap.aii.utilxi.prop.api.PropertiesException</SAP:P1>

<SAP:P2>Unable to read configuration data (ExchangeProfil~</SAP:P2>

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Error occurred while starting the Java application &quot;IntegrationServices&quot;; restart the application</SAP:Stack>

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

It is a way to show any of this information in the message body that sends the Alert monitor?

Regards.

Mariano.

[Former Member]

thanks to all

mariano.

[Former Member]

Hi,

you will not be able to get the entire msg payload of SXMB_MONI in alert.

But you can create a alert category and in its Long text you can have variables for Error Category and Error Text. So you will get alert mails with Error category and Error Text.

Regards,

Rajeev Gupta

[prateek]

There is no direct option to send the entire payload.

You may use Container varible in BPM and use values from the payload.

An alternative could be use of BPM, where in you may use exception branch and send a mail using send step including the payload data.

Regards,

Prateek

[Former Member]

Thanks Prateek, but another question, what about the messages that already have passed trhough XI and are in the R3 queues ?

Regards

Mariano,.

[Former Member]

Hi,

No alert in XI can be generated for msgs in R/3 Queues.

Regards,

Rajeev Gupta

[prateek]

If there was no setup earlier, then you can't do anything about the messages in R/3 queues. XI can't be made responsible for everything :).

Regards,

Prateek