ABAP Proxy Generation
ABAP |
Use
Using ABAP the proxy generation function you can generate ABAP proxy objects to an SAP system from an interface description in the SAP NetWeaver Exchange Infrastructure Integration Repository.
Prerequisites
The proxy generation process retrieves the WSDL description of the interface from the Integration Repository using HTTP. The address of the corresponding server is obtained. Queries to the Repository are subject to authentication. User and password for these requests are also obtained here. Information is also taken from the exchange profile to navigate from ABAP proxy generation to the Integration Builder start page. For more information, refer to the section Exchange Profile Parameters.
You must also have created message interfaces in the interface maintenance of the Integration Repository before you can generate for these proxies.
Integration
You can send and receive messages using the generated ABAP proxies. (See ABAP Proxy Runtime).
Features
You can edit ABAP proxy objects either in the Object Navigator (transaction SE80) or in transaction SPROXY:
● The Object Navigator displays proxy objects created in the system in the navigation tree under Enterprise Services ® Client-Proxies, Server-Proxies, and Proxy Dictionary Objects). When you create new proxy objects, the hierarchy of software component versions from the Integration Repository is displayed in the service wizard. To create a client proxy, position the cursor on client proxy and choose Create in the context menu. Choose Service Consumer and Enterprise Services Repository in the service wizard.Note that in the component hierarchy, interfaces can be displayed for both the Integration Repository 7.0 and the Enterprise Services Repository 7.1.
● You can display the interface objects from the Integration Repository (or the Enterprise Services Repository) by using the navigation tree in transaction SPROXY. If no connection to the Integration Repository exists, the tree presents an overview of those interface objects for which a proxy object already exists in the system.
Both transactions show information about proxy objects on the right-hand side (see Displaying ABAP Proxy Objects).
All imported software component versions in CRM, ABA, or APO are displayed in the Integration Builder. Conversely, only the appropriate components of a particular version are installed in the SAP System (such as ABA 6.20 or CRM 3.0). Therefore, only these software component versions are offered.
Views in Transaction SPROXY
In transaction SPROXY, you access both Integration Repository objects and generated objects by using the navigation tree. If namespaces are deleted there, then they are no longer visible in the navigation tree in transaction SPROXY, however it is possible that proxy objects already exist in the system for these namespaces. For this reason, the navigation tree in transaction SPROXY has two views:
Activities
...
1. Generate ABAP proxy objects for an interface or for other interface objects (see: Generating Proxies).
2. Check whether you need to make any changes following the automatic naming of proxy objects.
3. If the description was changed in the Integration Repository, you must regenerate proxy objects.