SOAP Adapter - Guaranteed delivery

[Former Member]

Hi ppl,

I have a requirment where we are exploring the possibility of the source system being able to expose its data in http format so that we can get use XI SOAP adapter to get the same over https. As SOAP adapter would access the data through WAN, what would happen to the data if the WAN is broken? How does the guaranteed delivery work in case of SOAP adapter?

[former_member192295 · Accepted solution]

Hi,

Even WAN broekn also channel itself will try to send data until dependson retry value. If retry reaches maximum value it will stuck at that point. We can do manually resend message through Resend option in Message Monitoring window under Runtime Workbench

[Former Member · Accepted solution]

thanks for your reply. For inbound messages, how will the data be recieved by SOAP adapter in case of broken WAN. If the source system is exposing the data once in every minute and the WAN is broken for 10 min, when it comes up again, will SOAP adapter recieve all the messages sent by the source system during the connectivity failure? I am not sure how the expose of data in http format works.

[former_member181962 · Accepted solution]

Hi Ethan,

I do not think that it is SOAP sender adapter's resposibilty.

It is the sender system's responsibility to resend the messages when the link is up again.

However for outbound messages, it is the responsibility of receiver soap adapter to deliver the message , in case of links being down.

Regards,

ravi

[Former Member · Accepted solution]

>

> thanks for your reply. For inbound messages, how will the data be recieved by SOAP adapter in case of broken WAN. If the source system is exposing the data once in every minute and the WAN is broken for 10 min, when it comes up again, will SOAP adapter recieve all the messages sent by the source system during the connectivity failure? I am not sure how the expose of data in http format works.

From your comments, it seems that the source system acts as a client, and PI (SOAP Adapter) will receive the data from the client.

You can configure the "Quality of Service" of the sender soap adapter with 3 possible options:

- Exactly once (async)

- Exactly once in order (async)

- Best effort (synchronous)

In the first two cases, your client will get an HTTP 200 response (with an empy SOAP message), while in the last case it will get as a response the message you have configured in PI. Take into account that in the first two cases, even if there is an internal error in PI (mapping error for example) your SOAP adapter will still have delivered an HTTP 200 response, as the SOAP adapter did its mission (received the message and delivered it to the Integration Server).

If the client can't reach PI, it won't get an HTTP 200, it will get an HTTP 500 or other error code, so it's your client responsability to retry sending the message until it gets the proper response.

http://help.sap.com/saphelp_nwpi71/helpdata/en/fc/5ad93f130f9215e10000000a155106/content.htm

Edited by: Jorge Lopez on Jul 13, 2009 3:20 PM