Generating an ESR-Based Provider Proxy

Prerequisites

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

Context

You work with the Enterprise Service Browser in the ABAP back-end system and follow the general procedure for generating proxies.

More information: ABAP Proxy Generation - General Procedure

Procedure

  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.
    An active provider proxy now exists in the ABAP back-end system, in which the service will be provided.
  4. To be able to call a Web service, you have to create a runtime configuration. To do this, use the SAP NetWeaver Administrator. Start this tool from the SOA Manager (transaction code SOAMANAGER).

Results

An endpoint exists that can be used to call the Web service.

The provider proxy comprises the following:

  • An ABAP proxy interface

  • An implementing class that implements the proxy interface

    The implementing class contains the operations that were modeled in the Enterprise Services Repository as methods.

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 proxy interface is generated and cannot be changed.

Example

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

        
METHOD ZMY_II_SYNCHRON_INBOUND_INTERF~EXECUTE_SYNCHRONOUS.
        
**** INSERT IMPLEMENTATION HERE ****
        
OUTPUT-RESPONSE_MESSAGE_TYPE-SIMPLE = INPUT-REQUEST_MESSAGE_TYPE-SIMPLE.
        
    
ENDMETHOD.