Regarding proxy and adapter

[Former Member]

In the doc, it is said that for SAP WAS > 6.20, we can develop interface and use proxy. So why we still use SOAP adapter when connecting to web service, Is it a must?

Any comments will be greatly appreciated.

[Former Member]

Adapters: The task of an Adapter in SAP XI is to translate from the sender message format to XI message format or XI message format to receiver message format and can also be a called as a communication protocol between sender/receiver and SAP XI.

see this link.. very informative.....

/people/sravya.talanki2/blog/2006/12/27/aspirant-to-learn-sap-xiyou-won-the-jackpot-if-you-read-this-part-iii

SOAP Adapter: SOAP Adapter converts the SOAP messages into SAP XI message format that is SOAP with header attachments. This in an area many need to really concentrate as it is heart of the ESA literature going forward.As per the question the reason for using SOAP adapter often for connecting to Webservices is its compatibility.The Webservice creates an XML file for containing information about its parameters and holds a HEADER and BODY similar to that of SOAP which answers the question clearly.

Proxies: Proxies are used while communicating with systems like SAP WAS >= 6.20 as they are provided with inbuilt integration engines. You will usually create a message interface in the repository and then generate a proxy in the application system. Proxy executables reside either in sender or receiver systems. Proxies are used only when sender/receiver and SAP XI understand XI message format. The one most important difference between a proxy and adapter is that the adapter converts the sender/receiver format to the XI message format but where as proxy does not need to do that as they natively understand the XI message format. ABAP proxies and Java proxies are available in SAP XI which can be used depending upon the requirements. For ABAP refer ABAP Client proxy and ABAP Server Proxy and for java refer Java Proxy . Donot forget to activate your proxies using the link Activate your ABAP Proxy! What is an error occurs?Donot tell me that you will raise a forum thread! Make a difference! Refer Debug your inbound ABAP Proxy implementation and Monitoring for Processed XML messages in ABAP Proxy.

Award points if helpful

Regards : Deepika Kuppachari

[nikhil_bose]

shen,

when we create proxies, we need WSDL for the corresponding proxy. using this web service description, we are accessing the Message Interfaces, Action and the Location of where the services are available. So to make use of Proxies generated in XI we need WSDL

This WSDL is SOAP wrapped (i.e. it comes inside SOAP envelop) and we need SOAP Adapter to process it (Convert to XML)

regards,

nikhil

[agasthuri_doss]

Hi,

1) The SOAP adapter enables you to exchange SOAP messages between remote clients or Web service

servers and the Integration Server or the PCK.You need to configure the SOAP adapter so that you can

exchange SOAP messages between the Integration Engine and remote clients or servers of Web

services.

2) 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.

3) The SOAP adapter provides a runtime environment that includes various SOAP components for the

processing of SOAP messages. we can combine these SOAP components with separate components

to meet your needs and requirements .

4) The SOAP adapter uses a helper class to instantiate and control SOAP components. If you want to use

your own SOAP processing logic you must make your helper class known to the SOAP adapter.

5) Information about the Integration Engine destination (when the Integration Engine is acting as a service

provider and therefore the SOAP adapter must be configured as a sender adapter).

6) Information about the Web service provider destination (when the Integration Engine is acting as a

service client and therefore the SOAP adapter must be configured as a receiver adapter).

Regards

Agasthuri Doss

[Former Member]

hi

SOAP adapter is used in the web serivec because all the message exchange will be done in xml format

soap is helpful to convert the file in soap-xml format

thanks

Regards

vijay

[Former Member]

hi

Proxies are interfaces which will get executed in the application system. They can be created only in the system from message interfaces using the proxy generation functions.

You can use proxies for systems with WAS >=6.20

XI will communicate in native language with SAP systems via proxies. Proxies uses XML - SOAP based communication for both ABAP and Java Proxies

Proxy generation generates classes and structures for the interfaces and data types written in WSDL. The range of commands in the Integration Builder is restricted to a suitable WSDL subset for system integration."

The WSDL are generated for the Message Interface created, so Proxies use the SOAP protocol, Proxy is not a substitute for SOAP but if you want to perform some operations in R/3 then it is helpful to use ABAP proxy.

ABAP proxy generation gets the WSDL description for message interfaces from the Integration Repository (WSDL Web Service Description Language) by using http. In WSDL, data that is transferred using messages is described using XSD (XML Schema Definition Language).

The Integration Builder does not support the full range of WSDL (for message interfaces) and XSD (for data types) commands; this is not the case for WSDL in the Web service infrastructure, however.

Proxies are used only when sender/receiver and SAP XI understand XI message format. The one most important difference between a proxy and adapter is that the adapter converts the sender/receiver format to the XI message format but where as proxy does not need to do that as they natively understand the XI message format.

For a webservice you should use eitehr a SOAP adapter or HTTP adapter. If your interfaces are going to connect SAP then I would rather suggest to use proxies. If they are externally located and if they are third party interfaces then we can go for webservices

for SAOP adapter Plz chk this link

http://help.sap.com/saphelp_nw04/helpdata/en/69/a6fb3fea9df028e10000000a1550b0/frameset.htm

If U hv any further queries then reply..

Thanks

Manas

[Former Member]

Hi, Shen:

WebService and ABAP Proxy, there are two different concepts, even they can all connect application system to XI:

The ABAP proxy are generated from SAP application system (WAS >=6.20), based on the message interface you created Integration Builder, more particularly, integration repository.

If the proxy is generated based on outbound interface (going out of application system), it is called client proxy, vice verse, it is server proxy.

Customized ABAP program is needed to call Proxy objects, or to be called by proxy. Local Integration engine communicate with central Integration engine with native XI protocol, so no explicit adpater needed.

XI Type of adapter need to be used for ABAP Proxy (Not SOAP adapter)

Message flow for client proxy

ABAP Program -> Proxy Runtime -> Local IE =====> XI 

Message flow for Server Proxy:

XI ======> Local IE -> Proxy Runtime -> ABAP Program

Netweaver Application server support Webserice, so it can both consume SOAP messages via SOAP sender adpater and send SOAP request message to external webservice via SOAP receiver adapter.

So the application server via SOAP connection is not restricted to be SAP system, it can be any system that support SOAP transport protocol.

Regards.

Liang

Edited by: Liang Ji on Apr 5, 2008 6:46 AM

[Former Member]

You use SOAP adapter when you need to XI to talk to a web service.

Proxies are used for XI to talk to SAP systems with SAP Web AS > 6.20