Show TOC

Integration DirectoryLocate this document in the navigation structure


In the Integration Directory you configure a business process that you have modeled and specified in the ES Repository. This means the following: You set up the business process for a specific system landscape. Here you specify the components that communicate with each other (usually business systems) and other details of the communication. These other details can include, for example, routing rules, which determine the receiver a message in a process is to be forwarded to, or the configuration settings of the adapter used for the connection of non-SAP protocols or systems.

Whilst you define the basic process flow in the ES Repository (at design time ), that is the communication participants that communicate with each other and the interfaces, data structures, and mapping for exchanging data, independently from the system landscape, in the Integration Directory (at configuration time ) you determine:

  • Which system landscape is behind the communication participants

  • How messages are exchanged within this system landscape (routing)

  • What mappings are used

  • What technical details are valid for communication (adapter configuration)

In addition to this you can, for example, further specify the configuration by defining specific security settings for exchanging messages.

All configuration data is structured and organized in the Integration Directory in the form of configuration objects .

Using Tools to Configure Efficiently

The manual execution of all configuration steps can be very complex and time-consuming for large scenarios. Therefore, tools are provided to help you execute the configuration efficiently and quickly.

More information: Using Tools to Configure Efficiently

Working with the Integration Builder

The user interface in the Integration Directory is the Integration Builder. The user interface and its general functions are described in Working with the Integration Builder


All the information that you enter in the Integration Directory at configuration time is available in the caches of the Integration Engine (and the Adapter Engines, if these are involved) for message processing at runtime.