ABAP Proxy Generation 

Use

You can send and receive messages using generated proxies. (See ABAP Proxy Runtime.)

Prerequisites

If you are generating a proxy from a WSDL document that was created from a local file, from a URL, go to the Procedure section below.

If you are generating a proxy from a WSDL document from the XI Repository, note the following:

The proxy generation retrieves the WSDL description of the interface from the Integration Repository using HTTP. The address of the appropriate server is taken from the exchange profile (parameters 1, 2, and 3 – see below). Queries to the Repository are subject to authentication. The user and password for these queries are also taken from here (parameters 5 and 6). Information used to navigate from the ABAP Proxy Generation to the initial page of the Integration Builder is also taken from the exchange profile (parameters 1, 2, and 4).

Example configuration for accessing
interfaces in the Integration Repository (exchange profile)

No.	Section	Parameter	Value (Example)
1	Connections	com.sap.aii.connect.repository.name	pwdf0436
2	Connections	com.sap.aii.connect.repository.httpport	1080
3	Connections	com.sap.aii.connect.repository.contextRoot	rep
4	Connections	com.sap.aii.connect.integrationbuilder.startpage.url	rep/start/index.jsp
5	ApplicationSystem	com.sap.aii.applicationsystem.serviceuser.name	hugo
6	ApplicationSystem	com.sap.aii.applicationsystem.serviceuser.pwd	hugopass

These parameters must be set by an administrator for technical configuration of the XI system landscape, not by the developer.

Procedure

Proxy Generation using the Object Navigator (transaction SE80)

...

       1.      Call the Object Navigator (transaction SE80) in the system where you want to generate the server or client proxy. Select a package. From the context menu, choose Create ® Enterprise Services / Web Services  ® Proxy Object.

       2.      In the dialog box that appears, choose the WSDL Source (URL/HTTP destination, local file, UDDI, or XI Repository).

If you have chosen XI Repository as the WSDL source document, the hierarchy of software component versions of the Integration Repository appears. The interface objects are sorted by software component version, namespace, and object type.

Software component versions and namespaces of the Integration Repository are only displayed if they are available locally in the system. The selection of software component versions in the navigation tree in the SPROXY or SE80 dialogs is also a subset of the software component versions of the Integration Repository.

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 – and thus displayed – in the SAP System (such as ABA 6.20 or CRM 3.0).

 

If a connection to the Integration Repository could not be established at the start of the transaction, you can ascertain more exactly what went wrong, and fix this problem (or have it fixed), by choosing Goto  ® Connection Test.

Choose an interface object for which no proxy yet exists, and confirm by choosing Copy.

       3.      In the dialog box that appears, enter the name of the package where you want to create the proxy objects. In addition, you can enter a prefix for all the objects you are about to create, which prevents name conflicts with existing objects in the system. Note also the Tips for Proxy Generation.

Check whether you have to make adjustment after naming the proxy objects automatically. If the WSDL description has changed, you must regenerate the proxy object.

The Object Navigator displays proxy objects created in the system in the navigation tree under Enterprise Services ® Web Service Library (client proxies, server proxies, and proxy Dictionary-objects).

Proxy Generation using the transaction SPROXY

...

       1.      Call the transaction SPROXY in the system where you want to generate the server or client proxy.

The left side of the screen shows a navigation tree whose structure has been copied from Interface Maintenance in the Integration Builder.

The interface objects are sorted by software component version, namespace, and object type. If a connection to the Integration Repository cannot be established, the tree displays only those interface objects for which proxies are available in the system, so that they can be displayed.

       2.      Choose an interface object for which no proxy yet exists. Create the proxy, either by double-clicking, or by choosing Create Proxy from the context menu.

In the dialog box that appears, enter the name of the package where you want to create the proxy objects. In addition, you can enter a prefix for all the objects you are about to create, which prevents name conflicts with existing objects in the system.

Displaying and changing proxy properties

In the Object Navigator, or when generating a proxy using SPROXY, the following tabs are displayed on the right side of the screen:

Tabs displayed when generating an ABAP proxy

Tab	Meaning
Properties	Properties of generation, such as package or last user to change the proxy. For server proxies, you specify the name of the implementing class here.
Name conflicts	This tab is only displayed immediately after the proxy is generated. It allows you to correct names that were truncated during generation, or that needed to be changed because a collision occurred.
Generation	A list of all the objects generated for an object
Structure	This tab is similar to the Generation tab, except that here the objects are sorted according to their use in a tree structure. Example:   Class CO_X     ->Method MYMETHOD       ->Importing OUTPUT
Type mappings	Even if the proxy was generated successfully, there are situations where generation was only possible on the basis of certain implicit assumptions. (For example, restrictions of the value range need to be checked by the programmer). If such situations arose during generation, they are listed in an application log.
Preconfiguration	Preconfiguration involves specifying the properties for the runtime environment of the proxy, where these properties are known in the development phase.  Preconfiguration forms the basis for the logical port settings. The proposed values come from the WSDL document used to generate the proxy. (See also: Creating a Logical Port.) This tab is displayed when synchronous client proxies are generated.

Result

You can call the hierarchy of generated objects from the Structure tab. The objects are not created in the system until you choose the Activate function. Before you activate these objects, you can save administered metadata from the transaction that contains all the information needed for generating the proxy. You can then generate the proxy itself later.