Integrating Business Systems by Using SAP ABAP Proxies XI Connectivity

The following documentation describes an integration scenario in which the business system, which is connected to the Integration Server by means of ABAP proxies, takes on the role of either a sender system or a receiver system, or both.

Use

SAP systems based on Web AS 6.40 and higher are able to exchange data by using messages and HTTP. These systems can use ABAP proxies to connect to the Integration Server.

SAP systems up to and including Release 4.6 are not able to exchange data by using XML messages and http. Such systems can only connect to the Integration Server by means of the IDoc adapter or the RFC adapter.

To connect the platform-independent message interfaces, which are stored in the Integration Repository, to the Integration Server, use the ABAP proxy interface.

Description

You can use executable ABAP proxies to exchange messages between a business system and the Integration Server. Executable ABAP proxies are shipped by SAP with all platform-independent message interfaces. However, you have to generate these proxies first before you can use them for your own interfaces.

An application in a business system calls a client proxy to send a message. The proxy runtime receives the message and the Integration Server processes it.

To forward messages to a receiver business system, the proxy runtime receives the message on the receiver system, and then calls the ABAP class that implements the relevant server proxy.

The local Integration Engine has the task of a message sender or receiver here. It does not perform any mapping or routing actions.

Example

A SAP Web AS 6.40 system uses a client proxy to send a message to the Integration Engine. The message is processed by the Integration Server. Two receivers are determined:

· Another Web AS 6.40 system

· A system that cannot receive XML messages directly (for example, an SAP 4.0B system)

On the receiver side, the SAP Web AS 6.40-based system receives a message, which is used by a server proxy to call the ABAP class. The other receiver system must be connected by means of the IDoc adapter or the RFC adapter.