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: J2EE Connection Architecture) and communicates with Resource Adapters, which are either a component of usage type Process Integration or are provided 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 (J2EE): For adapter communication within a system network.
Partner Connectivity Kit (J2EE): Enables business partners who do not have Process Integration installed to receive and send messages (see: 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.
Both the central and non-central Adapter Engines are configured centrally in the Integration Directory, and a central monitor. The Partner Connectivity Kit (PCK), on the other hand, has to be configured locally because Process Integration is not installed.
The Plain J2SE Adapter Engine is only used in a few special cases. In this case, configuration and monitoring are both local.
No comments:
Post a Comment