Configuring A2A Processes
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.
An A2A process can contain different forms of communication (or a combination of forms of communication).
● Integration Server communication
● Direct communication between two business systems
The configuration procedure depends on which form of communication is being used.
More information:
Configuring Integration Server Communication
Configuring Direct Communication
Note the following special features and concepts when configuring A2A processes.
Special Concepts when Configuring A2A Processes
Relevant Configuration Object |
Concepts |
Communication party Communication component Communication channel |
In application-to-application 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. |