Show TOC Start of Content Area

Procedure documentation Generating Proxies  Locate the document in its SAP Library structure


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.

If a proxy is generated for an inside-out service or an external WSDL document, proxy generation is executed in the Object Navigator (transaction SE80).


For more information about programming with proxies, see Proxy Programming.


Depending on the proxy type, the following tasks must be executed before the proxy can be generated:

      All objects must have been created in the Integration Repository.

If a proxy is to be generated for an object that references another object in the same namespace, the proxy for the referenced object is generated automatically. So, for example, a proxy can be generated for an interface that references a specific data type.

If a referenced object is in another namespace, you must generate the proxy for the referenced object separately.

      The package structure must be defined in the ABAP backend system.

The package structure defines where the proxies are created, where the main service provider is located, and how the packages fit into the general application structure.

      Prefixes can be defined for ABAP objects.

It is recommended that you define prefixes as this ensures that ABAP objects are assigned clear and consistent names in the backend system.


Proxy Generation Using Transaction SPROXY


       1.      Start the Enterprise Services Repository Browser (transaction code SPROXY).

       2.      Make the software component version and namespace easy to locate.

       3.      Expand the Service Interfaces/Message Interfaces nodes.

       4.      Choose an outbound interface.

For more information on the states of objects, refer to Object States.

       5.      Open the context menu and choose Create.

The system asks you to enter a prefix and a transport request.

       6.      Confirm the action.

The client proxy is generated. During this process, the corresponding data types and message types are generated in the same namespace.

The Configuration tab shows the default properties extracted from the WSDL document. These properties define the settings of a runtime configuration that is generated when the proxy is used.

       7.      Save.

       8.      Activate the client proxy.

When the client proxy is active, the proxy classes and associated methods are created and activated automatically.


Proxy Generation Using the Object Navigator (Transaction SE80)

       1.      Start the Repository Browser (transaction code SE80).

       2.      Open the package that you want to create the consumer proxy for.

       3.      In the context menu of the package, choose Create Enterprise Service/Web Service Proxy Object.

       4.      Choose Service Consumer in the dialog box.

       5.      Choose Continue.

       6.      Choose the source of the WSDL document: Enterprise Services Repository, a URL, or a file.

For more information on the Enterprise Services Repository, refer to the section Creating Consumers/Providers for the Enterprise Services Repository 7.1.

       7.      Choose Continue.

       8.      Specify a URL or file name.

       9.      Specify a package, a prefix, and a transport request.

   10.      Choose Continue. The client proxy is generated.

   11.      Save.

   12.      Activate the client proxy.

The proxy classes and associated methods are now created and activated.


Refer also to the Tips for Proxy Generation and the executions in the section Displaying ABAP Proxy Objects.



To generate proxies, the WSDL description of the interface is read using HTTP. The objects are not created in the system until you choose the Activate function. Before you activate these objects, you can save metadata managed by the transaction that contains all the information needed for generating the proxy. You can then generate the proxy itself later.









End of Content Area