There are two different uses for the ABAP proxy runtime:
● You want to exchange messages with the Integration Server by using ABAP proxies. To send a message to the Integration Server, use a consumer proxy. To provide a service on the SAP Web AS that can be addressed by messages from the Integration Server, use a provider proxy.
● You want to call a Web service in the Internet and have generated a consumer proxy for this purpose. For a description of how Web services are used, refer to ABAP Web Services.
You generate proxies from an interface description in WSDL (Web Service Description Language) by using ABAP proxy generation. Before you generate a proxy, you can determine whether this description is to be loaded from the Repository, from a local file, from a URL, or from a Registry.
The ABAP proxy runtime provides a uniform programming model for using proxies (refer to Consuming a Stateless Web Service (XI 3.0 compatible)).
Communication using Web services is point-to-point. The XI runtime requires the integration server in order to be able to forward messages. In the first case there is, of course, a performance advantage; in the second case you can use the mapping, routing, and BPM services of the Integration Server, and configure the receiver centrally:
More information: Setting Up Point-to-Point Connections.