ABAP Proxy Runtime 

Use

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, see ABAP Web Services.

Integration

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 Integration Repository, the Exchange Infrastructure, a local file, a URL, or from a registry.

Features

ABAP proxy runtime provides a uniform programming model for using proxies as a Web service or for XI (see: Programming with Provider and Consumer Proxies).

Uses for Provider and Consumer Proxies

Consumer Proxy	Provider Proxy
Calls a Web service in the Internet (synchronous)	Provides a service interface as a Web service (interface pattern: XI3.0-compatible) (to be called synchronously)
Direct communication between the proxy runtime and the integration server, synchronous (best effort) and asynchronous (exactly once (in order))
Point-to-point connection using Web services (only synchronous)

Point-to-Point Connections

Communication using Web services is synchronous and point-to-point. The XI runtime also supports synchronous communication, but needs the Integration Server 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:

See also Setting Up Point-to-Point Connections.