Communication Using Adapter Runtime 

A central component of the adapter runtime is the Adapter Framework, with services for messaging, queuing, and security handling. The adapter framework supports the JCA standard (JCA: Java Connector Architecture) and uses resource adapters, which are provided either as part of usage type Process Integration or by SAP partners. All adapters shipped by SAP are resource adapters, apart from the IDoc adapter.

The following adapter components are based on the adapter framework:

●      Adapter Engine for adapter communication within a system network.

●      The Partner Connectivity Kit with which business partners who have not installed Process Integration can receive and send messages

More information: Integrating Smaller Business Partners with the PCK

The following graphic provides an overview:

The Adapter Engine and the Business Process Engine are tightly linked to the Integration Engine. Whether the Adapter Engine is employed or not depends on the requirements of the collaborative process.

●      You normally use the central Adapter Engine; it covers the conversion of the majority of collaborative processes within a system landscape.

●      You can use the non-central Adapter Engine when you require it to work closer to the application systems. This may be necessary if a system is separated from the Integration Server by a firewall.

You configure both the central and non-central Adapter Engines centrally in the Integration Directory, and both have a central monitor. The Partner Connectivity Kit (PCK), on the other hand, has to be configured locally because usage type Process Integration is not installed.

The Adapter Engine (Java SE) is only used in a few special cases. In this case, configuration and monitoring are both local.