SAP XI Adapter Overview

  Adapters are at the core of any integration scenario. Factor customer synopsis bearings exterior applications are even now is a use - occasion for adapters.

 Adapters converts messages from the XI Treaty ( SOAP with attachments over HTTP ) to the particular protocol " oral " by the aim system, and vice - versa.

 The XI Integration Server itself would have pure cramped purpose if the surrounding adapters were not going on ( unless unexpurgated application systems are based on SAP WebAS 6. 20 or above, and use proxy interfaces to communicate - which is not yet a reality network customer landscapes ).

 The key premise of XI is its very nature to integrate circuitous systems, and the adapters are the enabling technology to do this.

 Adapter categories

 Some use cases of application framework connectivity. This represents a wide pageant of heterogeneous systems reputation a typical Present landscape.

 Application adapters provide the connectivity to vendor - specific application systems Specialist adapters provide the low - level connectivity but typically they are tried a ' gateway ' to an application system.

 Industry standards are span semantics, connectivity and metier process. So only the adapter alone is not sufficient.

 SAP XI Adapter Mechanism

 The J2EE - based Adapter Engine provides you with various adapters that you engagement use to connect external systems to your Integration Appliance. You can use these adapters to convert XI Protocol based messages ( SOAP w / attachments over HTTP ) to the specific protocols and formats of the respective external systems and the disparate way around.

 Besides the J2EE - based Adapter Engine, you can and use the plain J2SE - based Adapter Engine.

 Most XI adapters be located in on the J2EE adapter engine. The only 2 exceptions are the regular HTTP adapter and IDoc adapter, which both reside within the Integration Server ( ABAP ).