Show TOC

Background documentationCommunication with Embedded Process Integration Locate this document in the navigation structure

 

The following documentation describes an integration scenario in which you can install an SAP application together with an embedded Process Integration on SAP NetWeaver Application Server. An additional business system is connected to the Integration Server of the embedded Process Integration by means of proxies or the adapter runtime. This business system can assume the role of either a sender system (using client proxies) or a receiver system (using server proxies), or both.

Note Note

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

End of the note.

You do not require a separate SAP NetWeaver Application Server for an embedded Process Integration.

Prerequisites

  • The embedded Process Integration must be installed in a separate client.

  • Only one embedded Process Integration instance can be installed on each application server.

  • Systems must be Unicode-enabled (the embedded Process Integration only supports Unicode systems).

Description

An application in a business system calls a client proxy to send a message. The proxy runtime receives the message from a business sender system and the Integration Server of the embedded Process Integration processes the message further.

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

This graphic is explained in the accompanying text.

Example

A business system uses a client proxy or the adapter runtime to send a message to the Integration Server of the embedded Process Integration. The message is then processed by the Integration Server. Two receivers are determined:

  • An additional application server system

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

On the receiver side, the application server system receives a message, which is used by a server proxy to call the Java class. The other receiver system must be connected by means of the IDoc adapter or the RFC adapter.