- SAP Community
- Products and Technology
- Technology
- Technology Q&A
- Soap VS HTTP adapter
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Soap VS HTTP adapter
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 05-19-2008 10:47 AM
hi guruz,
which client tool used for sending soap request and http request?and what is the main difference between http and soap.
from my understanding in both we are using extetrnal web object (webservices).
please guide me
warm regards.
- SAP Managed Tags:
- SAP Process Integration
Accepted Solutions (0)
Answers (7)
Answers (7)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
hi Pawan,
SOAP : Push or recive data from a webservice,
HTTP: Push or receive data from web application, you can send a simple XML file as well.
for SOAP you can use SOAP GUI or XML SPy and for HTTP you can use test tool by microsoft WFETCH
http://www.robweb.de/wfetch.zip and
regards,
Sachin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Pavan,
SOAP is use to convert the normal file in to the Xml format.
the soap is nothing but the simple object application protocol.
Purpose
The SOAP adapter enables you to exchange SOAP messages between remote clients or Web service servers and the Integration Server or the PCK.
it is user in to consume , create a web service. and in creation of RFC.that is the main advantage of soap...
the format ot soap is
Envelope
-->> Header
--->>>Application data
-
>>>>>data
out actual message in your data. and it is secure.
In the SOAP adapter, you can specify security settings to be used to sign/verify the SOAP body. In addition, you can specify the standard to be used for signing/verifying the SOAP message.
For FAQs about the SOAP adapter, see SAP Note 856597.
Integration
You configure the adapter in the configuration part of the Integration Builder or the PCK.
The receiver SOAP adapter can be used for mapping lookups.
See also: Mapping Lookups
Features
● To be able to send SOAP messages to the Integration Server/PCK, you must configure the sender SOAP adapter.
● To be able to send SOAP messages from the Integration Server/PCK to remote clients or Web service servers, you must first configure the receiver SOAP adapter.
The receiver adapter supports system acknowledgments but not application acknowledgments.
● You have the option of using the Axis framework in the SOAP adapter.
HTTP
Purpose
The plain HTTP adapter gives application systems the option of communicating with the Integration Engine and exchanging business data using a plain HTTP connection. Depending on the receiver system, outbound messages can be enhanced with certain information.
Integration
The plain HTTP adapter is part of the Integration Engine. It comprises two parts, namely an adapter at the Integration Engine inbound channel and an adapter at the Integration Engine outbound channel.
For compatibility reasons, both the old XI message protocol (2.0) and the current XI message protocol (3.0) are supported at the inbound and outbound channel.
The adapter at the inbound channel is located before the Integration Engine pipeline and calls this pipeline. The adapter at the outbound channel is called by the pipeline, and can therefore be regarded as part of the pipeline. It requires a corresponding communication channel from the technical routing for each logical receiver.
A communication channel with a receiver HTTP adapter can be created automatically for business systems that are defined in the System Landscape Directory. See also: Creating Communication Channels Automatically
Features
The plain HTTP adapter is used by external systems to connect to the Integration Engine using the native HTTP interface (HTTP payload without SOAP envelope). These systems are connected using the Internet communication framework of the SAP Web Application Server. For this purpose, the Integration Engine HTTP inbound channel contains an HTTP service delivered by SAP, called /sap/xi/adapter_plain.
There are two usage types for the plain HTTP adapter:
● Synchronous processing
Ordering on the Internet with an order number as a response.
● Asynchronous processing
Ordering on the Internet without confirmation of the purchase.
In principle, both scenarios are possible at the Integration Engine HTTP inbound and outbound channels.
In special cases for particular external servers with CGI scripts, for example, marketplaces, it is possible to send the payload as an HTML form using HTTP post. The payload is enhanced correspondingly. For example, the content type is included in the payload.
SOAP Sender:
http://help.sap.com/saphelp_nw04/helpdata/en/fc/5ad93f130f9215e10000000a155106/content.htm
SOAP Receiver:
http://help.sap.com/saphelp_nw04/helpdata/en/5d/112d20f6ce6c46ba66afb98d278fbd/content.htm
Since your scenario is synchronous, You can use RFC adapter as sender side and SOAP adapter as Receiver side.
/people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1
/people/shabarish.vijayakumar/blog/2006/03/28/rfc--xi--webservice--a-complete-walkthrough-part-2
/people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
Main difference is HTTP is resides on ABAP stach hence u can not monitor HTTP adapter through RWB. FOr HTTP u dont require sender agreeement and sender communication channel.
where as
SOAP adapter resides on java stach hence u can monitor the status of SOAP adapter.
SOAP and HTTP are both communication protocols. But SOAP is messaging protocol concerned with packaging of messages in XML protocol and transfer then using HTTP .
http://en.wikipedia.org/wiki/SOAP
http://en.wikipedia.org/wiki/HTTP
Regards,
Vinod.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
hi,
SOAP is used when we need to commuincate via Webservice or remote interaction but HTTP used if some on from web needs to talk to XI server directly we use HTTP
/people/padmankumar.sahoo/blog/2005/02/15/an-overview-of-soap
Thanks,
Madhu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
tools used
you can use Altove XMl spy, Stylus Studio, SOAP UI for sending/generating SOAP requests.
You can use 'wfetch' for sending/generating http requests.
differences
1)SOAP is ...to communicate WEB SERVICES..it support WSDL files...using XMLSpy you can send the request.
HTTP is...to communicate with WEB pages
http://help.sap.com/saphelp_nw04/helpdata/en/44/79973cc73af456e10000000a114084/content.htm
2)SOAP in background uses XML + http
you expose outbound interface as a webservice and create a SOAP request to access it.
you send http request to ping a integration scenario directly at the integration engine.
3)SOAP
An Overview of SOAP
/people/padmankumar.sahoo/blog/2005/02/15/an-overview-of-soap
/people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1
/people/shabarish.vijayakumar/blog/2006/03/28/rfc--xi--webservice--a-complete-walkthrough-part-2
/people/padmankumar.sahoo/blog/2005/02/15/an-overview-of-soap
How to use SOAP adapter:
Note: reward points if solution found helpfull
Regards
Chandrakanth.k
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Pawan,
Please go through the following link to have more insight on your query.
/people/padmankumar.sahoo/blog/2005/02/15/an-overview-of-soap
This should help.
Regards,
Karthik
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
U may develop ur own clients. The difference between clients is that SOAP client sends http message with soap header, while http client sends plain http data without header
SOAP is always used for webservices. But http not always.
Regards,
Prateek
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
HI ,
Both adapters are for different purpose.
The SOAP adapter enables you to exchange SOAP messages between remote clients or Web service servers and the Integration Server or the PCK. the SOAP adapter is a java application which is making only a envelope of some XML tags, you can easily create them for yourself with a mapping.
http://help.sap.com/saphelp_nw2004s/helpdata/en/69/a6fb3fea9df028e10000000a1550b0/content.htm
The Plain http adapter is a part of ntegration Engine. It uses native http format i.e no SOAP Envelops. The HTTP is (native) adapter of the (ABAP) WAS, it is much more performant and more stable.
http://help.sap.com/saphelp_nw2004s/helpdata/en/44/79973cc73af456e10000000a114084/content.htm
Check this weblogs on both of these adapters for some more information:
Sending a Simple SOAP envelope to XI via HTTP using ASP
https://www.sdn.sap.com/sdn/weblogs.sdn?blog=/pub/wlg/1442 [original link is broken] [original link is broken] [original link is broken]
More links for SOAP Adapter:
/people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi
http://help.sap.com/saphelp_nw04/helpdata/en/9f/fdca3f01f33e1ce10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/69/a6fb3fea9df028e10000000a1550b0/frameset.htm
More links on HTTP adapters.
/people/siva.maranani/blog/2005/09/15/push-data-to-mvc-architectured-application-using-xi
/people/prasadbabu.nemalikanti3/blog/2006/02/27/collecting-and-bundling-vendor-records-from-different-multiple-interfaces-file-systempeoplesoft-and-sending-to-sap-r3-system-part-2
I hope the info above has helped you understand http and soap adapters better.
Cheers...
Vasu
Reward Points if found useful **
Edited by: BVS on May 19, 2008 11:51 AM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Exploring GraphQL and REST for SAP Developers in Technology Blogs by SAP
- General Splitter in CI - Namespace Prefix Problem in Technology Blogs by Members
- CAP odata-v2-adapter: batch request is not supported? in Technology Q&A
- HTTP Receiver adapter with Dynamic value in URL using header/property value in CPI in Technology Q&A
- Getting Response from GSP but that is not getting converted/consumed to SAP System in Technology Q&A
| User | Count |
|---|---|
| 86 | |
| 10 | |
| 10 | |
| 10 | |
| 7 | |
| 6 | |
| 6 | |
| 5 | |
| 5 | |
| 4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.