Show TOC

Background documentationConfiguring A2A Processes Locate this document in the navigation structure

 

This section provides an overview of the most important concepts relating to the configuration of company-internal processes (or application-to-application (A2A) processes) in the Integration Directory.

The detailed procedure for configuring this is dependent on which communication form is to be used (communication using the Integration Serve/Advanced Adapter Engine or direct communication).

Note the following special features when configuring A2A processes:

Special Features when Configuring A2A Processes

Relevant Configuration Object

Concepts

(Communication party)

Communication component

Communication channel

In A2A processes, you are the integration expert making the configuration settings and you know the whole system landscape. In this case, you can address the known business systems from the System Landscape Directory as the senders and receivers of messages. To do so, define all relevant business systems as communication components in the Integration Directory.

You usually use communication components that are not assigned to a communication party. The definition of communication parties only becomes relevant when configuring business-to-business processes.

Sender agreement

Receiver agreement

Direct connection

  • Integration Server communication

    You must always define receiver agreements (for each technical receiver of a message). You only have to define sender agreements when using special sender adapters that are configured explicitly at the inbound channel of the Integration Server (for example, sender file/FTP adapters).

  • Direct communication

    The direct connection contains the configuration data that enables two business systems to communicate with each other directly, that is, without using an Integration Server.