Show TOC

Procedure documentationGenerating a Provider Proxy Locate this document in the navigation structure

 

To provide a Web service, a so-called provider proxy needs to be created. Provider proxies are created and implemented in the ABAP back-end system, in which the service will be provided.

A provider proxy comprises the following:

  • An ABAP object interface

  • An implementing class

A template for the implementing class is created during proxy generation. A developer must add the appropriate application code to the implementing class. The ABAP object interface is not changed.

A provider proxy is based on an inbound service interface.

Prerequisites

A provider proxy needs to be generated in the ABAP back-end system, in which the service will be provided.

Provider proxies can only be generated for objects in the Enterprise Services Repository. The corresponding ES Repository object is an inbound service interface.

To generate a provider proxy, the following objects must already have been designed in the Enterprise Services Repository:

  • Data types

  • Message types

  • Service interface and its operations

Procedure

You work with the Enterprise Services Repository Browser in the back-end system.

Following the general procedure for generating proxies, perform the following steps:

  1. Generate a provider proxy for an inbound service interface.

  2. Activate the provider proxy.

    When the provider proxy is activated, all the underlying data types and message types will also be activated.

  3. Implement the provider proxy.

    To implement a provider proxy, you need to add application coding.

  4. To be able to call a Web service, you have to create a runtime configuration.

    To do this, use the SOA Manager (transaction code SOAMANAGER).

Result

An active provider proxy now exists in the ABAP back-end system, in which the service will be provided.

The provider proxy comprises an ABAP proxy interface and an implementing class that uses the proxy interface. The implementing class contains the operations that were modeled in the Enterprise Services Repository as methods.

Example

Below is an example of an implementation of a method that returns an echo of imported data:

Syntax Syntax

  1. 1.	METHOD ZMY_II_SYNCHRON_INBOUND_INTERF~EXECUTE_SYNCHRONOUS.
  2. 2.	**** INSERT IMPLEMENTATION HERE ****
  3. 3.	OUTPUT-RESPONSE_MESSAGE_TYPE-SIMPLE = 
  4. 4.	INPUT-REQUEST_MESSAGE_TYPE-SIMPLE.
  5. 5.	ENDMETHOD.
End of the code.

More Information

Working with the SOA Manager