Third Party Adapters

[Former Member]

How does Adapter Engine communicate with IS and How to select third party adapters in Adapter Engine

[Former Member]

Hi srinu..

from help i could gather some information for u...

Adapter Engine

Purpose

You use the Adapter Engine to connect the Integration Engine to SAP systems (RFC adapter) and external systems. You use the various adapters in the Adapter Engine to convert XML and HTTP-based messages to the specific protocol and format required by these systems, and the other way around.

Implementation Considerations

The Adapter Engine is based on the adapter framework. The adapter framework is based on the SAP J2EE Engine (as part of the SAP Web Application Server) and the J2EE Connector Architecture (JCA). The adapter framework provides interfaces for configuration, management, and monitoring of adapters.

The adapter framework has its own queuing and logging services. This means that you can run the Adapter Engine temporarily without a connection to the Integration Server.

The Adapter Engine is a separate software component that is automatically installed on the Integration Server. In this case, it is the central Adapter Engine. However, you can also install the Adapter Engine separately on another host. It is then a non-central Adapter Engine.

Integration

You configure the adapters in the configuration part of theIntegration Builder. You define the parameters of the respective adapter during thedefinition of collaboration profiles in thecommunication channel. It is possible to define generic modules for each adapter in the module processor to equip the adapter with additional functions.

It is possible to integrate customer adapters into the Adapter Engine. See also: Adapter Development.

Features

The Adapter Engine provides adapters, which you use to do the following, depending on their configuration:

· Communicate with SAP R/3 systems using the RFC interface (RFC adapter)

· Enable data exchange with the SAP Business Connector (SAP Business Connector adapter)

· Exchange data with external systems using a file interface or an FTP server (file/FTP adapter)

· Access databases using JDBC (JDBC adapter)

· Communicate with messaging systems using the JMS API (JMS adapter)

· Integrate remote clients or Web Service providers using the SOAP adapter (SOAP adapter)

· Connect marketplaces to the Integration Engine (Marketplace adapter)

· Connect e-mail servers to the Integration Engine (mail adapter)

· Communicate with systems that support the RosettaNet standard (RNIF adapter)

· The CIDX adapter supports Chem eStandards, an open standard for business-to-business data exchange in the chemical industry.

· The XI adapter is used for communication between Integration Servers and with the PCK.

In the adapter configuration, you specify whether an adapter is to be located at the inbound channel (sender adapter) or at the outbound channel (receiver adapter) of an Integration Engine.

Receiver adapters support system acknowledgments but not application acknowledgments.

hope it is usefull..

cheers,

Raghavesh

[bhavesh_kantilal]

Hi,

Take a look at the XI overview document to understand the archi of XI,

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/a3d3c390-0201-0010-c490-bd8...

Regards,

Bhavesh