expecting response from the XI engine

[Former Member]

Hi,

I am currently working on a prototype scenario where we are connecting an external webservise with SAP R/3 through XI. The external system (webservice) makes a call to XI and expects a response back as soon as the message reaches XI. Is there any way we can send the acknowledgement from XI (either from Adapter Engine or Integration Engine???) to the sender webservice?

I greatly appreciate valuable input.

Thank you,

Arjun.

[Former Member]

https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/3531 [original link is broken] [original link is broken] [original link is broken] [original link is broken]

The above link may be useful to your query.

Kindly reward Points.

[Former Member]

Hi,

Will the receiver of the webservice also need to send a response back to the sender? If so, then how can you have 2 responses with1 sync interface?

If you just want to have a response from XI, then you can use ccBPM to send a response back. So, the webservice will be sent to a BPM, and inside BPM a response is constructed and sent back to the sender. In addition, the request message can be sent to other receiver(s), but you will not be able to send the response back to the sender, since the sender already received a response from ccBPM.

Regards,

Bill

[Former Member]

Hi Bill,

The receiver of the Webservice doesn't have to send the response back. It's an asynchronous call. So is there anyway we can send the acknowledgement from the adapter engine or Integration engine?. Or is there any solution to handle this scenario?

Thank you,

Arjun.

[Former Member]

Hi Arjun -

When the web service client makes an asynchronous call to XI/SOAP adapter, the adapter will return a HTTP 200 response with an empty SOAP envelope. The client can look for this as a technical acknoledgement that the message was received.

Keep in mind however that this doesn't provide guaranteed, EO delivery, but rather "AtLeastOnce" delivery - a small chance for duplicates can occur. In order to eliminate this possibility, the client can send a unique message id in the request. See the SOAP FAQ Note - 856597 for more details.

Regards,

Jin