Model a service interface in the Enterprise Services Repository.

(More information:Defining Custom Services)

To make the implementation of the services possible, SOA Middleware enables generation of proxies for the consumer and provider side - based on the definitions in the ES Repository. For this purpose, a programming language-dependent representation of the abstract model is generated in the corresponding provider system - based on the metadata of the service model. This entity is referred to as a “service definition”. It contains the generated programming language structures, generally also an object-oriented interface methods and parameters, and other metadata. This service definition is then implemented by the application developer, and thereby the technical communication details are abstracted. This enables the user of the proxy to concentrate fully on the implementation of the business aspects. The tools for implementation and use of service interfaces are also embedded in the standard development environment of SAP NetWeaver. In this case, this is the ABAP Workbench.

Generate a provider proxy.

While the service modeling takes place centrally in the ES Repository, the proxy generation and subsequent service implementation is bound locally to a certain system or back end. Before the corresponding Web service proxy is generated, the developer decides in which system the proxy is to be generated. Afterwards, he or she starts the proxy generation locally in this system. This transfers the entities from the ES Repository into programming language structures (for example, interface, classes, data types) in the local system. These proxies and their defined data are stored persistently in the respective applications or application systems and are treated as part of the same, as if they had been created manually. The actual application and service runtimes are thus independent of the ES Repository.

Call transaction SPROXY, select the inbound service interface, and choose Create Proxy from the context menu. Enter the name of a package. (Refer to Working with ABAP Proxies).

The service definition is automatically generated during proxy generation.

After generation, the provider proxy contains methods for each service operation.

Fill the operations with the required logic.

In the Properties tab of the service interface, click the name of the provider class, and then specify the method name in order to get to the editor.

More information: Implementing the Provider Proxy.

Create a runtime configuration for the provider proxy. In the Object Navigator (transaction SE80), choose Start SOA Manager. For more information, refer to Configuring a Service Provider (from point 5 onwards).

Test your service in the Web Service Navigator.

Select the service definition in the Object Navigator (Transaction SE80) and choose Start Web Service Navigator. Make sure that a connection to the Web Service Navigator has been set up (refer to Setting Up the WS Navigator). If the service has not yet been configured, a standard configuration is created before starting the Web Service Navigator. In this case, choose the appropriate pushbutton.

More information: Testing a Service.