Business Communication

Use

There are several types of message exchange within an Advanced Adapter Engine Extended, all involving a central Advanced Adapter Engine.

The types of message exchange are depicted in the following figure, each with the required type of protocol and user for authentication.

Business Communication (AEX)

The message exchange between business systems or business partners can be separated into the following communication parts with several communication variants.

• Sender to Advanced Adapter Engine (AAE)

  There are four types of communication (outlined the figure above) by means of which an AAE receives a message:

  • The sender ( s1 ) is an associated ABAP business system working with ABAP proxies that send messages by using the XI protocol (connected to the AAE by the SOAP adapter).

  • The sender ( s2 ) is a Java proxy that sends messages by using the XI protocol.

  • The sender ( s3 ) is a system that sends messages in a non-XI protocol.

• AAE to receiver

  There are four analogous types of communication by means of which an AAE sends a message to the next receiver:

  • The receiver ( r1 ) is an ABAP business system working with ABAP proxies that receive messages in the XI protocol.

  • The receiver ( r2 ) is a Java proxy that receives messages in the XI protocol.

  • The receiver ( r3 ) is a system that receives messages in a non-XI protocol.

Concerning users for authentication, U=d(S) denotes that the user is obtained by means of an Integration Directory configuration, whereas U=c(S) means that the user is obtained by any other configuration in the sender system. The latter implies that the identity of the user in the sender system is not propagated to the AAE. However, PI also allows the user context of a message to be propagated unchanged from the sender to the receiver. More information: Configuring Principal Propagation Using the Advanced Adapter Engine