HI
Proxy communication starts with objects in integration repository and adapter communication starts with application system.
Proxy is a structure where there is no processing function module associated. You need to explicitly write the Business Logic/Call the subroutines here.
ABAP proxy generation is part of the SAP Web AS 6.40. ABAP proxy generation enables you to generate proxies to communicate by using the Web service infrastructure and by using SAP Exchange Infrastructure. ABAP proxies that were generated from message interfaces in the Integration Repository (IR) can be used in both infrastructures. This means that if none of the Integration Server services are required for a proxy-to-proxy communication scenario in ABAP, you can use a point-to-point connection using the Web service infrastructure instead.
u2022 Java proxy generation in the Integration Builder (Design) generates proxies from message interfaces in the Integration Repository. Java proxy generation packs the proxy objects in a Jar file, which you can save locally. You use the generated classes in J2EE applications on the SAP J2EE Engine.
Basically proxies are used for adapter less communication & main purpose of it is to bypass adapter engine.
Proxy generation enables you to create proxies in application systems. Proxies encapsulate the creation or parsing of XML messages and the communication with the relevant runtime components required to send or receive the messages. The proxy runtime controls these processes and can itself be controlled in application programs by means of additional methods.
Since the communication between the sender and receiver is decoupled, you can use proxies to exchange messages with various different communication parties, and also by using adapters. However, this section of the documentation only discusses the programming model for the proxy runtime.
We can generate proxies out of the message interface (inbound/outbound) defined in Integration repository.
Proxy generation converts non-language specific interface descriptions in WSDL into executable interfaces know as proxies. Proxies are executable interfaces in the application system.
There are two kinds of proxies:
1) Java proxies - generated in IR from WSDL description of interface u2013 results in .jar file containing generated java classes.
2) ABAP proxies - generated in application server with SPROXY transaction based on WSDL representation of message interface.
Note: For WAS release lower than 6.20 adapters are the only means to establish
connection. From WAS 6.20, proxy generation feature enables application systems to communicate with XI using proxies. Proxies enable adapter-less
communication (native connectivity).
You can get details about PrProxy : Proxy is a structure where there is no processing function module associated. You need to explicitly write the Business Logic/Call the subroutines .
Choosing of RFC adapter depends on the version of the system we r going to communicate.
Using RFC Adapter is the only option when we have SAP system with WAS 6.1 or older.
RFC Adapter may not be considered as the best option when we have WAS 6.2 onwards.
Proxys bypasses adapter engine & they communicate directly with IE .
Thru proxys
You can handle large amount of data
You can handle error messages
if you want to reduce the work load over XI server
then the best way is avoiding protocol conversion which adapters does(XYZ format to XML format)
if we use proxy which will be deployed on local proxy engine which in turn does protocol conversion instead of giving the job to XI.
i.e is (XYZ to XML format is done by proxy runtime and passed to XI at XI no conversion is done)
go thru this link :
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/2162oxies [original link is broken] [original link is broken] [original link is broken] here..
A)Proxies communicate with the XI server by means of native SOAP calls over HTTP.
ABAP Proxies uses Web service and Http Protocols.
Proxy communication always by passes the Adapter Engine and will directly interact with the application system and Integration engine - so it will and should give us a better performance.
A) Proxies use the SOAP protocol, Proxy is not a substitute for SOAP but if you want to perform some operations in R/3 directly, then use ABAP proxy.
refer the below links for further assistance
/people/prasad.ulagappan2/blog/2005/06/27/asynchronous-inbound-java-proxy
/people/rashmi.ramalingam2/blog/2005/06/25/an-illustration-of-java-server-proxy
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/7d4db211-0d01-0010-1e8e-9b0...
/people/stefan.grube/blog/2006/07/28/xi-debug-your-inbound-abap-proxy-implementation
Client Proxy - /people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
Server Proxy - /people/siva.maranani/blog/2005/04/03/abap-server-proxies
/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies - Activate Proxy
/people/siva.maranani/blog/2005/04/03/abap-server-proxies - ABAP Server Proxy
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy - ABAP Client Proxy
/people/thomas.jung3/blog/2004/11/17/bsp-a-developers-journal-part-xiv--consuming-webservices-with-abap
/people/prateek.shah/blog/2005/06/14/file-to-r3-via-abap-proxy - ABAP Proxy
http://help.sap.com/saphelp_nw2004s/helpdata/en/48/d5a1fe5f317a4e8e35801ed2c88246/frameset.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/ba/f21a403233dd5fe10000000a155106/frameset.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/41e08c90-0201-0010-9197-d8774336...
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f0ae9874-109c-2910-f48a-e91f0cdd...
/people/sravya.talanki2/blog/2006/07/28/smarter-approach-for-coding-abap-proxies
http://help.sap.com/saphelp_nw2004s/helpdata/en/02/265c3cf311070ae10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/ba/f21a403233dd5fe10000000a155106/frameset.htm
cheers
reward points if found useful
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.