WAS 640 notification

[Former Member]

Hey all,

I am currently working on a file to r/3 scenario using proxies into R/3. I would like to set up notifications in cases where the XI processes work but the proxy in R/3 fails. Would a standard alert management be helpful or do I need to create a notifcation workflow in R/3?

-Teresa

[Former Member]

Any ideas on this?? Appreciate it..

-Teresa

[former_member206604]

Hi,

If you prefer XI to do the job then

1.Make a Sync proxy call, the proxy will return the response message details and based on that you can trigger an alert in XI.

2. Let the proxy be Async, try to send a Ack back but there might be a limitation in notification

3. Try using the Fault message

Thanks,

Prakash

[Former Member]

Thanks. I am using an asynch proxy. Could you shed some light on the ack. And fault messages? Would the ack. Be received even when there is an error at the proxy side?

[bhavesh_kantilal]

Teresa,

If you are making a Synchronous Call to the Proxy, then in case there is an Application Error this error will also be propogated back to XI. Using a Synch Proxy call will make things easier.

Regards,

Bhavesh

[Former Member]

In most cases I would think developers would be using asynchronous interfaces to take advantage of XI's guaranteed delivery mechanisms.

From what I can find out XI does not get any feedback (when you look at SXMB_MONI) when a prox receiver goes into error. The reason for this I think is because its deemed an "application" error, so the "application" system should handle it.

Once way to do this is to capture errors with CCMS. You can then have an auto-reaction method in CCMS that forwards the errors to ALM in XI (Alert Management).

[bhavesh_kantilal]

Jason,

<i>From what I can find out XI does not get any feedback (when you look at SXMB_MONI) when a prox receiver goes into error</i>

Actually, in Synch Proxy calls the application error is propogated back to XI. Just take a look at the legend of SXMB_MONI and you will find a symbol for application error and such errors can be captured in XI ,( if required and feasible ).

But, like you mentioned, loose coupling is essnetial in XI and so one should try to make asynch calls from XI as possible.

Regards,

Bhavesh

[Former Member]

Hi Bhavesh,

My post was talking about async only. in which case it is true that XI does not get feedback from the application system (out of the box).