XI acknowledgment from axis soap adapter

[Former Member]

We have implemented an integration from SAP ERP to an external system via XI. SAP sends a message to XI via proxy which is then mapped to a web service call to the external system via the axis soap adapter. If there is a problem the axis adapater sends back an acknowlodgement message with the soap error. This message is correctly interpreted by XI as en error acknowledgement. The acknowledgement message however fails in the routing as it is not able to find a receiver agreement for routing the message back. There is of course actually no valid recepient for this acknowledgement as the original message was created using an asynchronous proxy call. The problem is however that the original message is flagged as successful even though the acknowledgement contains an error. What we want to achieve is that the error in the acknowledgment causes the original message in XI to be flagged as failed, to allow error detection. Does anyone have any idea how to achive this ?

Rgds

Evind Langsaeter

[stefan_grube · Accepted solution]

If you want to use acknowledgements with ABAP proxies, you need a receiver channel and a receiver agreement pointing back to the ABAP system. Otherwise the acknowledgement cannot be delivered.

Have you requested an acknowledgment in ABAP proxy code?

The message is flagged as successfull, when the message is delivered correctly. You have to check the acknowledgment state in the monitor.

The acknowledgments are not intented to use for monitoring purpose in XI server. The sender application systems should use the acknowledgments for their individual purpose.

Regards

Stefan

[Former Member · Accepted solution]

Hi

We do not require any acknowledgements. But for the cases where the soap call is delivered, but returns a http response of 500 together with a complete soap envelope containing a soap fault, the Soap Axis Receiver Adapter is issuing an u201CApplicationErroru201D Acknowledgement Message (referring to the original request message) (even though it is not requested). This Acknowledgement Message is failing on the Integration Server with a configException u201CFailed to determine a receiver agreement for the given messageu201D. We have tried to create a receiver agreement and reciever channel with the given keys from the error message, but still getting the same result.

Issue A: How to get this (non-requested) Acknowledge message to process without error.

Issue B: How to get a proper u201Cerror-messageu201D telling that the original request message was not really delivered though (as the soap call gets a http response of 500).

Rgds

Eivind

[stefan_grube · Accepted solution]

You see the erros in runtime workbench. You can do alerting based on that errors.

Regards

Stefan