ABAP REPORTS: November 2008

SAP XI Adaptar Message flow

This is the simplified flow for a typical message entering the AE from the IS. Communication between the IS and AE is done using the XI-protocol (SOAP w/ attachments) over HTTP(s).

Upon arrival in the J2EE engine the message is queued and persisted as appropriate. These services are provided by the messaging layer.

The message goes through a series of modules (generic and specific, possibly custom written).

The message is posted to the backend application using the appropriate native protocol The core services provided by the AF (described in the previous slide) are leveraged throughout the joutney of the message in the AE.

The PCK is using the same adapter framework providing core services.

Since the PCK is intended to be completely detached from the Integration Server (different business partner), central configuration and adminsitration is not possible.

Therefore the following components have been provided with the PCK Configuration UI (which is really a lean Integration Directory) Monitoring and administration UI.

SAP XI Aarchitecture of the Adapter Frame work

The Adapter framework is the underlying technology supporting most of the XI adapters. The slide shows the internal architecture of the AF.

As a quick walkthrough of the slide, here is an explanation of the numbers present in the diagram:

1: Each specific adapter (developed either by SAP or a third-party) must comply with the JCA 1.0 specification (Java Connector Architecture). For instance, the adapter logic must have a system contract and application contract with the base J2EE engine.

2/3: Internally, each specific adapter is considered as a “module“ attached to the adapter framework module processor.

The module contains the logic specific to a given adapter. New modules can also be developed by the customer when there is a need for custom Java Code at the adapter level. The module is then called like a ‚user exit‘ and must be referenced explicitely in the communication channel configuration. Standard modules from SAP do not need to be referenced explicitely (with the exception of the SOAP adapter).

4: The adapter-specific configuration objects are accessed locally from the CPA Cache, which itself is derived from Integration Directory (central configuration). See the chapter on CPA-cache for more details.

5: The AF provides some administration services common for all adapters (ie monitoring and health check). Most of the administration features are accessible from the runtime workbench. However some AF administration is done in the J2EE Administrator tool directly . The adapter framework has its own persistence layer, which is in the database schema underlying the J2EE engine.

6: low-level technical utilities (threads, transaction management). Standard features of the J2EE engine are leveraged here.

7: logging API: the logging is consistent with the rest of the applications deployed in the J2EE Engine.

8: The message metadata is derived directly from the Integration Repository.

9: The Integration Repository also contains ‚adapter metadata‘. This is how the containers for the adapter-specific configuration are defined. This is also how 3rd parties can define such containers for additional adapters. The adapter metadata translates into adapter-specific configuration screens in the ID. It is consumed by the adapter framework at runtime.

The Adapter Framework resides on the SAP J2EE Engine 6.40. In the case of the JMS and JDBC adapters, the appropriate vendor-specific drivers must be deployed on the J2EE Engine in order to function properly.

SAP XI Connectivity

PCK is based on the adapter framework.

PCK does not inherit central configuration data from the Integration Directory PCK has its own user interface (which is a subset of the Integration Directory) for configuration of individual adapters.

SAP Partner Connectivity Kit (PCK) is based on Adapter Framework .

SAP PCK‘s objective is to enable XML document exchange between SAP XI and business partner not using SAP XI .

SAP PCK also provides an extensible platform for developing and running individual JCA Resource adapters.

Communication between SAP XI and SAP PCK is via SAP XI messaging protocol SAP PCK Includes the following adapters: File/FTP, JDBC, JMS, SOAP, RFC, IDoc (once available for SAP PCK).

Optionally SAP PCK can host further adapters that are available from SAP or 3rd party adapter providers.

Enablement of smaller companies / subsidiaries to exchange XML documents with their business partner’s / headquarter’s SAP XI as shown below.