Show TOC

Background documentationAdapters Locate this document in the navigation structure

 

Adapters enable the Integration Engine and the Partner Connectivity Kit (PCK) to communicate with different applications.

You only require an adapter to communicate with SAP systems older than Release 6.20 and with external systems. A direct system connection using proxies and without additional adapters is supported for SAP systems that are based on Application Server 6.20 or higher.

For more information, see:

Integration Engine

Partner Connectivity Kit

Adapter Types
  • The IDoc adapter integrates existing SAP components with the Integration Engine. It converts XML- and HTTP-based documents to IDocs, and the other way around. This enables you to integrate your existing SAP infrastructure with the SAP infrastructure based on system integration and the exchange of XML messages.

  • The plain HTTP adapter gives application systems the option of communicating with the Integration Engine and exchanging business data in a simple format, using an HTTP connection.

  • Using the adapter type WS you can configure the communication of systems that use the Web service runtime to communicate with each other. The adapter type supports the Web Service Reliable Messaging protocol.

    It is possible to configure a direct communication between service providers and service consumers or you can configure the adapter so that the Integration Server is implemented with its enhanced routing and mapping characteristics.

  • The Advanced Adapter Engine provides you with various adapters that you can use to connect external systems to your Integration Engine. You can use these adapters to convert XML and HTTP-based messages to the specific protocols and formats of the respective external systems and the other way around.

    It is also possible to configure a message exchange without the involvement of the Integration Engine for adapters of the Advanced Adapter Engine (apart from the RNIF and CIDX adapters).

    For more information, see: Execute integrated configuration

    • You can specify generic modules for adapters in the Adapter Engine in the module processor. These modules give the adapters additional functions. SAP provides modules for integrating in the adapters of the Adapter Engine.

      For more information, see: Module

    • For notes on the development of adapters and modules, see: Developing Adapters and Modules.

    For more information, see:

    Advanced Adapter Engine

    Inserting Modules into Module Processor

  • Using the WS adapter you can configure the communication of systems, which communicate with each other using the Web service runtime either directly (point-to-point) or using the Integration Server.

  • In addition to the Adapter Engine, the Adapter Engine (Java SE) is still available.

    For more information, see: Working with the Adapter Engine (Java SE)

Adapter Types and Attributes

Adapter Type

Transport Protocol

Message Protocol

Quality of Service

Attachments

Attributes in Message Header

Acknowledgments

IDoc

Sender:

tRFC

File

Receiver:

tRFC

IDoc-XML

EO, EOIO with qRFC

No

System error acknowledgments

Application acknowledgements

Application error acknowledgements

RFC

RFC

RFC-XML

BE, EO, EOIO

No

Sender

Acknowledgments

Plain-HTTP

HTTP(S) 1.0

XI payload in HTTP body

BE, EO, EOIO

No

Sender

Receiver

No

SAP Business Connector (BC)

HTTP(S)

RFC XML with envelope

IDoc-XML

BE, EO

No

Acknowledgments

File/FTP

File system (NFS)

File transfer protocol/file transfer protocol using SSL/TLS

File

File with content conversion

BE, EO, EOIO

Yes

(Sender)

Sender

Receiver

JDBC

JDBC 2.0

Sender:

JDBC 2.0

Receiver:

XML SQL Format

Native SQL String

BE, EO, EOIO

No

JMS

SonicMQ JMS Provider

WebSphereMQ (non-JMS)

Access JMS Provider with JNDI

(Read) JMS Provider Administered Objects from File

Access JMS Provider Generically

JMS 1.x

EO, EOIO

No

Sender

Receiver

SOAP

Sender:

HTTP

Receiver:

HTTP(S)

SMTP(S)

SOAP 1.1

BE, EO, EOIO

Yes

(sender, receiver)

Sender

Receiver

Marketplace

HTTP(S)

JMS Sonic MQ 3.5

MML

BE, EO

Yes

(sender, receiver)

Mail

Sender:

IMAP4

POP3

Receiver:

IMAP4

SMTP

XIALL

XIPAYLOAD

BE, EO, EOIO

Yes, for XIPAYLOAD

(sender, receiver)

Sender

Receiver

RNIF

HTTP 1.1

HTTPS

RNIF 2.0

EO

Yes

Sender

Receiver (for two-action responder)

RNIF11

HTTP 1.1

HTTPS

RNIF 1.1

EO

No

Sender

Receiver (for two-action responder)

CIDX

HTTP 1.1

HTTPS

RNIF 1.1

EO

No

Sender

XI

HTTP(S) 1.0

XI 2.0

XI 3.0

BE, EO, EOIO

Yes

WS

HTTP(S) 1.0

WS 1.0

EO

EOIO

Yes

Yes