Show TOC

Adapters (Advanced Adapter Engine)Locate this document in the navigation structure

Use

Adapters enable the runtime engines of SAP PI 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.

Adapter Types

  • The IDoc adapter (AAE) integrates existing SAP components with the Advanced Adapter 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 HTTP adapter (AAE) gives application systems the option of communicating with the Advanced Adapter Engine and exchanging business data in a simple format, using an HTTP connection.

  • The Advanced Adapter Engine provides you with various adapters that you can use to connect external systems to your Advanced Adapter 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).

    • 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 notes on the development of adapters and modules, see: Developing Adapters and Modules .

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

The following tables list the available adapters provided by SAP and summarize key attributes.

Adapters of the Advanced Adapter Engine

Adapter Type

Transport Protocol

Message Protocol

Quality of Service

Attachments

Attributes in Message Header

Acknowledgments

IDoc (AAE)

tRFC

IDoc XML

EO, EOIO

No

No

ALEAUDIT

XI Acknowledgement

RFC

RFC

RFC-XML

BE, EO, EOIO

No

Sender

Acknowledgments

HTTP(AAE)

HTTP(S) 1.1

POST

GET

BE

EO

EOIO

Yes

Sender

Receiver

System acknowledgments

System error acknowledgments

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

Web Service HTTP(S) SOAP 1.1 and 1.2

WS-Reliable Messaging 1.0 and 1.1

Best Effort, Exactly Once, Exactly Once In Order No No No

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