Implementing a Server Proxy 

Use

Web services are primarily used to publish an implemented service already existing in a system so that it can be called by other users (for example, by using a client proxy on the SAP Web AS). However, it is also possible to describe a service interface in WSDL independently of the system, and then implement it later in an application system.

The ABAP proxy runtime supports this scenario, with the limitation that you can only generate server proxies using the message interfaces of the XI Integration Repository. You can use a server proxy to do the following:

·        To implement a service that can be addressed by the SAP XI Integration Server

·        To implement a service that can be called as a Web service

How the server proxy is used depends on the runtime configuration.

Customers that do not have SAP XI Release 3.0 or higher installed cannot access the Integration Repository or exchange messages directly using XI.

Procedure

..

Server proxies are ABAP object interfaces. Implement a class for your generated ABAP object interface and enter it on the Properties tab page of the server proxy by calling transaction SE80 or transaction SPROXY. Upon receipt of a message, the ABAP proxy runtime calls the method EXECUTE_SYNCHRONOUS of the implementing class (in asynchronous communication: EXECUTE_ASYNCHRONOUS).

Therefore, the application must simply implement the class for the server proxy. Proxy generation automatically creates a class with an appropriate signature and empty method. The name of this class is located on the tab page Properties. The application can, however, also enter any class with a suitable signature.

When a message is processed successfully, a commit work is triggered at the receiver.