Hi satheesh reddy ,
These r the details regarding proxy :
Proxy Generation
Proxy generation converts non-language-specific interface descriptions in WSDL into executable interfaces known as Proxies. Depending on the target programming language, you choose one of the following:
· 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.
· 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.
You create proxy objects in the development system by using the proxy generation functions. They are transported and shipped by using the tools in the development system. There are separate tools in the Integration Repository
Introductory Notes
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.
Use
You can generate client or server proxies in ABAP to send or receive messages. You generate client proxies from outbound message interfaces and server proxies from inbound message interfaces.
Procedure
Generating Proxies By Using Transaction SPROXY
1. Call transaction SPROXY in the system in which you want to generate a client or server proxy.
The system displays a navigation tree on the left-hand side of the screen; it has the same structure as the interface maintenance tree in the Integration Builder. The interface objects are ordered according to software component version, namespace and object type (also see: ABAP Proxy Generation).
If no connection to the Integration Repository exists, the system only displays interface objects in the tree structure for which a proxy exists in the system.
2. Choose an interface object for which no proxy already exists. To create a proxy for this interface object, double click the context menu Create Proxy.
3. In the dialog box, specify the name of the package where you want to create the proxy objects. You can also specify a prefix for the names of all objects to be created to avoid naming conflicts with names that already exist in the system.
Generating Proxies By Using the Object Navigator (Transaction SE80)
1. Call the Object Navigator (transaction SE80) in the system in which you want to generate a client or server proxy. Select a package and call the context menu. Choose Create ® Enterprise Service / Web Service ® Proxy Object.
2. In the subsequent dialog window, choose the source of the WSDL document (URL/http destination, local file, UDDI or XI Repository).
If you choose XI Repository as the source of the WSDL document, the hierarchy of the software component versions in the Integration Repository is displayed in the subsequent window. The interface objects are ordered according to software component version, namespace and object type (also see: ABAP Proxy Generation). Choose an interface object for which no proxy already exists and confirm by choosing Copy.
3. In the subsequent dialog window, enter the name of the package where you want to create the proxy objects. You can also specify a prefix for the names of all objects to be created to avoid naming conflicts with names that already exist in the system.
Result
To generate proxies, the WSDL description of the message interface is read using HTTP. If no naming conflicts occur during the conversion, you can call the hierarchy of the generated objects from the tab page Structure. The objects are only then saved in the system once you choose Activate. Up to the point of activation, you can save metadata that contains all information for generation and that is managed by the transaction, and continue with generation at a later date.
These r the web-sites which give a step-by-step solution using proxies :
http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/c9/74246d8ad2447799063d39013e9a11/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/86/58cd3b11571962e10000000a11402f/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm
These r the blogs from SDN which give a detailed solution using different proxies :
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
/people/siva.maranani/blog/2005/04/03/abap-server-proxies
/people/stefan.grube/blog/2006/07/28/xi-debug-your-inbound-abap-proxy-implementation
/people/prateek.shah/blog/2005/06/14/file-to-r3-via-abap-proxy
/people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi
**********Please reward points if u find this useful
cheers,
gyanaraj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.