SAP XI CONNECTIVIY ABAP

The choice of adapters vs proxies comes into play when connecting SAP applications Before WebAS 6.20 the only connectivity option in/out of the SAP system is RFC/BAPI/IDoc Starting with the WebAS 6.10 the native HTTP connectivity has been added to the basis layer Starting with the WebAS 6.20, each application system has its own local integration engine and is therefore able to connect to XI via proxies over HTTP / SOAP with attachments (XI protocol) At the present time, the vast majority of SAP applications still fall in the first category (IDoc or RFC/BAPI based) This is true for all applications based on 4.6C and below. Since RFC/IDoc is the only technology available for interfaces.

This is still true for most applications based on WebAS 6.20 or above. Indeed most applications still use RFC/BAPIs and IDocs.

Newer applications are starting to emerge, which are based on the ‘outside-in’ methodology (proxies, native connectivity, no adapters).

At this point in time this is only a small set of SAP applications .
As this is the long-term development strategy (towards ESA approach), this form of connectivity will gain importance in the future and ultimately this will be the only form of interfaces in/out of SAP applications.

SAP® Business Packages for Industry Standards

Provides Solution Kits for specific industries and delivers mappings for RosettaNet, CIDX Application adoption .

Enhance business applications like mySAP CRM or mySAP SCM to support SAP® Business Packages for high.

MApping

Including message sets for the industries according their priority Support mappings: versions, upgrade, maintenance Process Integration .

SAP® Business Packages’ message protocol implementation (such as RNIF 2.0 and RNIF 1.1 for CIDX)

Provision of Collaboration Agreements

In the case of Industry standards support, the adapters play a key role in the SAP Business Packages, but they are only part of the picture.

The idea of an SAP Business Package is to provide all levels of support for a given Industry Standards Semantic level (mappings, interfaces).

Process level (BPM)

Application level (R/3, CRM, SCM,...)

Connectivity (adapters)

Adapter mappings and adapter metadata are stored in the Integration Repository Centralized Integration Repository contains all relevant information for collaborative processes All content adheres to open standards Adapters provide technical connectivity The PCK will be detailed in one of the following units.

As already established the PCK is also 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.


Adapter Framework runs on J2EE Stack of SAP Web AS :

Adapter Framework is platform for Adapter Engine and SAP PCK Adapter Framework provides an extensible platform for developing and running adapters in SAP XI environment Adapter Engine utilizes central configuration, monitoring, administration .
(19)