cancel
Showing results for 
Search instead for 
Did you mean: 

SOAP and HTTP

Former Member
0 Kudos

Hello Friends,

1)In one of the scenarios ..They are implementing HTTP Is it better to implement

HTTP for Synchronous receiver side or It would be advisable to use SOAP for Syn Receiver side.

2)Can Reciver HTTP handles Syn communication.

Accepted Solutions (0)

Answers (3)

Answers (3)

prateek
Active Contributor
0 Kudos

1) HTTP has two major advantages.

- the SOAP header overhead is avoided

- as HTTP adapter resides directly on the Integration Server, the adapter engine processing is avoided.

2)Yes

Regards,

Prateek

Former Member
0 Kudos

But HTTP adapter uses HTTP version 1.0 and does not support returning fault messagesto the sender. Mean if HTTP adapter at the receiver side you can only get the response...but unable to send the Fault Message to the caller.

But in case of SOAP you can achieve it.

Thanks

Farooq

Former Member
0 Kudos

Satya Kumar,

1) SOAP messages are more secure and since most applicatioins are moving towards a webservice architecture you would be better off with a soap adapter. All things considered equal SOAP is a better choice.

2) I dont think plain receiver HTTP can handle sync comm.

regards,

Arvind R

Former Member
0 Kudos

on the receiver side,both HTTP and SOAP will behave pretty much the same,there isn't much difference on receiver side,yes HTTP can be used for sync on both sender and receiver side.

if you wan't to use HTTP or SOAP on sender side,then HTTP will give better performance coz message are posted directly to the integration engine thus bypassing adapter engine

Thanx

Aamir