Skip to Content
author's profile photo Former Member
Former Member

External Adapters


Can u plz elaborate about the external adapters



Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

4 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Jun 16, 2008 at 08:38 AM


    In XI, we can categorise the adapters as follows:

    Technical Adapter: such as HTTP, SOAP, JDBC, Mail, etc.

    SAP Application Adapters: such as RFC and IDoc.

    Non-SAP Application Adapters: such as Oracle, Seibel, PeopleSoft, etc.

    Industry Standard Adapters: such as CIDX, RosettaNet, EDI, etc.

    Adapters: The task of an Adapter in SAP XI is to translate from the sender message format to XI message format or XI message format to receiver message format and can also be a called as a communication protocol between sender/receiver and SAP XI. Let us discuss various adapters which are widely and commonly used.

    File Adapter: This is easiest adapter to start your hand on with SAP XI. You have the option to receive XML files or flat files. We use file content conversion to handle flat files like CSV files etc.


    Idoc Adapter: The next most commonly used adapter is Idoc adapter for sending and receiving Idocs from SAP XI. The foremost step before configuring the idoc adapter is the system settings that have to be done


    Configuration steps required for posting idoc's (XI):


    RFC Adapter: RFC adapter allows SAP XI to communicate with Integrating Systems using remote function call. It is nothing but a wrapper of SAP JCO.


    JDBC Adapter: We use this adapter to connect database systems using the JDBC driver. We need to deploy JDBC driver


    Mail Adapter: We can send and receive mails in SAP XI using mail adapter or by configuring SAP Connect and using SAP XI RFC Adapter


    SOAP Adapter: SOAP Adapter converts the SOAP messages into SAP XI message format that is SOAP with header attachments. This in an area many needs to really concentrate as it is heart of the ESA literature going forward.


    HTTP Adapter: The first thing any one need before starting is HTTP client for testing their scenarios


    JMS Adapter: I really don’t have a fair idea on this adapter and only help you in providing the links. You need JMS drivers before you start your interface.

    Please go through the following links.....

    Async/Sync Communication using JMS adapter without BPM (SP 19):


    Sync/Async communication in JMS adapter without BPM (SP19):


    First would be to deploy drivers for JMS scenarios -

    Secondly, to configure JMS adapters;

    In case JMS scenario that you have is a sync one, in that case if you are below SP19 you might have to build a BPM - ref:



    How to correlate JMS messages -

    How to use conversion modules in JMS -



    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jun 16, 2008 at 08:58 AM
    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jun 16, 2008 at 08:40 AM

    hi gunasekhar,

    go thru the below blog




    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jun 16, 2008 at 11:50 AM


    Adapters are part of adapter framework. They provide technical connectivity to enable the integration of sap and non sap applications.

    Adapters convert from any format like File, Jdbc etc to XML format

    RFC Adapter:

    The RFC Adapter supports connectivity to SAP system from release 3.1.x upwards (remember that from 6.20 onwards proxies can be used instead if desired). The RFC Adapter maps Remote Function Calls (RFCs) to XML messages and vice versa.

    The RFC Adapter is part of the Integration Engine. The sender RFC adapter is located before the Engine pipeline and calls it. On the outbound (receiver) side it is called by the pipeline and is considered a pipeline service. Both use SAP JCo (Java Connector) Service to manage metadata for mapping RFC data to XML and vice versa. That is, on a message coming inbound to XI the SAP JCo Service in the Adapter Engine converts the RFC Data to XML prior to the message reaching the inbound adapter which then passes it on to the pipeline. As the message is transferred out of XI it moves through the outbound RFC Adapter and to the JCo service which then translates it from RFC Data to XML.

    Again, the RFC Adapter is comprised of the inbound (to XI from a sender system a.k.a.

    sender adapter) and the outbound (from XI to a receiver system a.k.a. receiver adapter). The configuration for each is specific to type and will be described in better detail in those sections.

    General Functionality

    u2022 Only guaranteed delivery for tRFC

    u2022 No SAPGui, callbacks, qRFC, RFC Library clients

    u2022 Context in the called system is not kept open over multiple calls (stateless)

    u2022 No RFCs to non-SAP systems (i.e. RFC clients created via the RFC SDK)

    u2022 No bundling of multiple calls

    u2022 Asynchronous calls are persisted, synchronous calls are persisted only if logging is enabled

    IDoc Adapter:

    The IDoc Adapter allows processing of IDocs using the Integration Engine from release 3.1.x upwards (remember that from 6.20 onwards proxies can be used instead if desired). The IDoc Adapter converts the IDocs to IDoc XML format so they can be processed by the Integration Server pipeline into XML. On the outbound side XML messages are converted to IDoc XML via the Integration Server which in turn is converted to native IDoc format by the IDoc Adapter. Like the RFC Adapter the inbound IDoc Adapter is located before the Integration Server and calls it. On the outbound side it is called by the pipeline and is considered a pipeline service.

    If there is no need to modify / interrogate the data records of the IDoc (SAP to SAP straight transfer as an example) a configuration parameter can be set. This will prevent conversion into IDoc XML and uses tables instead, increasing system performance. See the Sender Adapter section for more detail.

    General Functionality:

    u2022 IDocs sent / received are of a tRFC nature (asynchronous only)

    u2022 All existing IDoc Types can be used, even custom

    u2022 IDocs can be transferred in packages, assuming all IDocs can be converted to IDoc XML format

    u2022 IDocs can be received / processed by the Integration Server or sent to an external system through Serialization

    Required configurations vary widely based on sender / receiver system types. The below is primarily focused on SAP (logical system) to XI to SAP (logical system) communication.

    File Adapter:

    The File Adapter allows message transfer to and from a FTP service / file system. Included in this also is NFS server. Files can be transferred in a number of formats / encodings. As an example, files can be sent / received as flat files (defined length structures) or as .csvu2019s (comma separated values). In general, files must be based on codepage UTF-8 for processing by the Integration Server. However, the File Adapter can use every codepage that is installed in the java runtime environment for conversion purposes

    Database (JDBC) Adapter:

    The JDBC Adapter allows access to any DB that allows a JDBC driver to access the DB. This driver is not supplied with the adapter but must come from the DB provider or a 3rd party. The adapter converts database content to XML and vice versa.

    Database content can be read with any SQL statement using a special XML format. This format enables SQL INSERT, UPDATE, SELECT, DELETE or even stored procedures. A message is always processed in one database transaction.

    Java Messaging Service (JMS) Adapter

    The JMS Adapter allows support for an arbitrary JMS provider, as well as for select queue connections (SonicMQ, Websphere, etc). This driver is not supplied with the adapter but must come from the product vendor or a 3rd party. The adapter allows message content to be sent from a messaging system to the Integration Server and vice versa.

    XI Adapter

    The XI Adapter is used for communication, via direct XML / HTTP message exchange (no message protocol conversion required)

    1. With an Integration Engine (ABAP based). Both XI 2.0 and 3.0 protocols are supported

    2. With a party using the Partner Connectivity Kit

    3. With an Adapter Engine based either on XI 2.0 or 3.0

    The XI Adapter is used with the Proxy Runtime (covered in another chapter) when communicating via ABAP or java proxies.

    SOAP Adapter

    The SOAP Adapter provides a runtime environment that includes various SOAP components for the processing of SOAP messages from remote clients or Web services. This is required as XI communicates with a modified SOAP u2018with attachmentsu2019 which is not directly interoperable with SOAP.

    HTTP Adapter

    The HTTP Adapter allows connection between the Integration Server and application systems. External systems connect to the Integration Server using the native HTTP interface (HTTP payload without SOAP envelope) which is converted to XI protocol (SOAP with header enhancements). The HTTP Adapter allows synchronous and asynchronous message functionality.

    MarketSet Adapter

    The MarketSet Adapter allows communication with public or private exchanges or with business partners over open protocols. It translates XI message protocol to MML (MarketSet Markup Language) and vice versa. The MarketSet Adapter also supports synchronous / asynchronous messaging as well as differing qualities of service.

    refer the following links for further assistance on Adapters:

    Configuration steps required for posting idoc's (XI):



    reward points if found useful

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.