Runtime

Use

SAP Exchange Infrastructureruntime consists of a series of components:

·        The Integration Engine executes the integration logic of the Integration Server and converts messaging (of the Integration Server or application systems).

·        The proxy runtime uses proxies to exchange messages with the Integration Server. This section addresses the programming model for ABAP and Java proxies.

·        The Adapter Engine uses the RFC adapter and external adapters to exchange messages with the Integration Server.

·        The respective adapters are either connected using the Adapter Engine or run independently (for instance, the IDoc adapter and the plain HTTP adapter).

·        Central monitoring monitors XI runtime components, the message flow, and the performance.

See also: Connectivity

Integration

The proxy runtime and the adapters (Adapter Engine) also fetch information from the System Landscape Directory (SLD) the first time a message is sent, so that they can write the logical sender in the messages (in application systems it is initially only possible to call technical information about the system). In the proxy runtime, the procedure is as follows:

...

       1.      The proxy runtime fetches the SLD address from the exchange profile. The SLD contains all business systems, including the Integration Server.

       2.      The proxy runtime sends the SLD a technical ID for the sender system. Once this ID is entered in the SLD and the corresponding associations are available, the proxy runtime receives the name of the sender business system and the address of the corresponding Integration Server as a response.

       3.      The proxy runtime can now specify the logical business system as the sender in the message and forward it to the Integration Server.

Prerequisites

The following prerequisites must be fulfilled before you can exchange messages using the Integration Server:

·        The runtime components of SAP XI and the application systems involved in the communication must be configured (for example, the local Integration Engine in the application system must know the address of the Integration Server). This task is also referred to as technical configuration.

·        The collaborative process must be configured in the Integration Builder ( configuration). This contains configuration data on the logical level (logical routing) and the technical level (communication channel).

See also: Roles and Tool Access

The transition from technical configuration to the configuration of the collaborative process is continuous. This documentation mainly describes the latter configuration but also deals with the technical configuration. For more information about the technical configuration, see the Configuration Guide. The guide is on SAP Service Marketplace at http://service.sap.com/instguides.