Hi Rajani,
Below is a short intro on ABAP proxy
Why Proxies over RFCs/BAPI’s and IDOCs
Proxies over RFC’s/BAPI’s:
-
Proxies communicate with the XI server by means of native SOAP calls over HTTP whereas RFC does not, so you have to convert from SOAP to RFC calls and vice versa . So XML conversion is required.
Proxies can be can be used for both synchronous and asynchronous communication , RFC/BAPI is basically only intended for Synchronous comm. which asks much more system resources from your XI system
RFC/BAPI has its own overhead of function call for large chunk of data
Proxies over IDOCs:
-
IDocs are always asynchronous - no response
Every business transaction in SAP does not necessarily has a corresponding standard IDOC
Heavy transfer of data in IDOCs (If we consider IDOC transfer, we might be in need of few fields for which we have to transfer the whole IDOC. In the case of Proxy, we can write a report to trigger the proxy & wherein we can fetch only the required fields that has to be sent from R/3 to XI
JPG,PDF files can be sent as attachments in addition to the XML Message though proxies as they communicate thru SOAP Protocol.
Note: Since SAP is moving towards a SOA framework , proxies are best suited for this environment as it uses native SOAP calls over HTTP.
All SAP systems above WAS 6.4 would be using proxies to communicate with the external systems
Types of ABAP Proxies:
-
1. Based on the mode of communication:
Synchronous Proxy -Sender is awaiting response from the Receiver immediately. i.e. When you send data, it expects an immediate acknowledgement.
Asynchronous Proxy - Sender is not waiting for any acknowledgement.
2. Based on ABAP application:
Client Proxy – ABAP application utilizes ABAP Proxy to send message to IS in XI protocol format
Server Proxy – ABAP Proxy receives XML message from IS and converts it to be received by application sytem(R/3 in our case)
3. Based on ABAP web services:
Client proxy – Allows calling web service on internet (synchronous only). Does not require IS services.
Sever Proxy - Allows using inbound MI as WS( synchronous only)
Point-to-point – communication between two SAP WA servers.
4. Based on flow of messages
Inbound Proxy – receives messages to external system
Outbound Proxy - sends messages to external system
ABAP Proxy generation and its pre-requisites
-
--Means converting the non-language specific interface descriptions in WSDL into executable interfaces
--Enables the proxy runtime to communicate between the application systems
--Creates both the classed and structures necessary for the interface and the data types written in WSDL
--Generate through transaction SPROXY
Steps for Proxy generation and testing
-
1.Goto transaction SPROXY
2.Search for the message interface to be generated
3.Right-click on the MI and choose ‘CREATE’
4.Give the appropriate package and prefix.
5.Make sure to rename the structures and classes to the standards
6.Generate the proxy and save
To test a proxy , simply execute the proxy and copy the payload with the data to be sent , if its an inbound proxy.
If its an outbound proxy , run the report that triggers the proxy method
Pre-requisites
-
-ABAP – SAP systems based on SAP WAS 6.4 or WAS 6.20 with pluggins
-JAVA – J2EE applications:SAP J2EE engines WAS 6.40
-For BASIS versions less than 4.6 one goes for RFCs and IDOCs and for versions 4.7 or above you go for proxies
Hope this info helps,
Regards,
Vinayak Kamath
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.