Alert rules to enable alerts for sxmb_moni errors in ECC server.

[former_member188019]

Hi all,

in our scenario:

LegacyApplication--->FileAdapter--->PI--->InboundProxy--->ECC

We configured PI alerts using Michal's blog

http://scn.sap.com/community/pi-and-soa-middleware/blog/2005/09/09/xi-alerts--step-by-step

so now, if there is an error in PI, e.g. mapping error etc, we are getting the alerts

but if the message processing is successful in PI, and delivered to ECC, and if there is any error in the inbound proxy functionality in ecc, how can we get the alerts.

i can see in the sxmb_moni on ecc server, the message red, in error state.

as of my knowledge, on ECC server too, we can use tcode ALRTCATDEF, and define alertcategories, where we can specify the reciepients and the information using Container elements.

But, incase of PI alerts, we were using alert rules in RWB to enable the alerts for specific/all errors.

Incase of ECC alers, is there any way to define rules for enabling the alerts, using the alert category defined in ECC.

Madhu.

[MichalKrawczyk · Accepted solution]

Hi,

>>>Incase of ECC alers, is there any way to define rules for enabling the alerts, using the alert category defined in ECC.

Please have a look at this - on how to execute an alert in ECC (proxy)

http://scn.sap.com/people/sukumar.natarajan/blog/2007/01/07/how-to-raise-alerts-from-abap-proxy

Regards,

Michal Krawczyk

[former_member188019 · Accepted solution]

thanks again Michal for the link,

in the referred blog, everything like filling the container variables, triggering alert etc are done in the inbound proxy code itself.

it seems, it will be very tightly coupled, if we embed the alert triggering logic within the inbound proxy itself.

it may be not maintainable, if we want to enable alerts for all the interfaces in ECC, meaning do we need to append the logic into every inbound proxy.

[MichalKrawczyk · Accepted solution]

Hi,

>>>it may be not maintainable, if we want to enable alerts for all the interfaces in ECC,

in order to make sure it is (and it can be) you should define one class for doing that

and reuse it with FEH properly as per my blog:

http://scn.sap.com/community/pi-and-soa-middleware/blog/2011/02/24/pixi-forward-error-handling-feh-f...

this way it can be maintained very nicely,

Regards,

Michal Krawczyk