Adapters 
Purpose
Adapters enable the PCK to communicate with different systems.
Features
Adapters are used to connect the PCK both to SAP Exchange Infrastructure and to other systems.
The PCK provides a variety of adapters for this purpose. You can use these adapters to convert XML and HTTP-based messages to the specific protocols and formats of these systems and the other way around.
The PCK provides adapters, which you can use to do the following, depending on how they are configured:
· Communicate with SAP systems using the RFC interface (RFC adapter)
· Enable data exchange with the SAP Business Connector (SAP Business Connector adapter)
· Exchange data with systems by 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 e-mail servers to the PCK (mail adapter)
· Exchange data with SAP Exchange Infrastructure (XI adapter)
In the adapter configuration, you specify whether an adapter is located at the inbound channel (sender adapter) or at the outbound channel (receiver adapter) of the PCK.
Adapter Types and Attributes
Adapter Type |
Transport Protocol |
Message Protocol |
Quality of Service |
Attachments |
Acknowledgments |
Attributes in Message Header |
RFC |
RFC |
RFC-XML |
BE, EO, EOIO |
No |
See below under Acknowledgments. |
Sender |
SAP Business Connector (BC) |
HTTP(S) |
RFC XML with envelope IDoc-XML |
BE, EO |
No |
See below under 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) |
See below under Acknowledgments. |
Sender Receiver |
JDBC |
JDBC 2.0 |
Sender Adapter: JDBC 2.0 Receiver Adapter: · XML SQL format · Native SQL format
|
BE, EO, EOIO |
No |
See below under Acknowledgments. |
|
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 |
See below under Acknowledgments. |
Sender Receiver |
SOAP |
Sender Adapter: · HTTP Receiver Adapter: · HTTP(S) · SMTP(S) |
SOAP 1.1 |
BE, EO, EOIO |
Yes (sender, receiver) |
See below under Acknowledgments. |
Sender Receiver |
Sender Adapter: · IMAP4 · POP3 Receiver Adapter · IMAP4 · SMTP |
· IXALL · XIPAYLOAD |
BE, EO, EOIO |
Yes, for XIPAYLOAD (sender, receiver) |
See below under Acknowledgments. |
Sender Receiver |
|
XI |
HTTP(S) 1.0 |
· XI 2.0 · XI 3.0 |
BE, EO, EOIO |
No |
|
|
Acknowledgments
Receiver adapters that run on the Adapter Engine support system acknowledgments if they are requested by the sender. Acknowledgements are triggered when a message is successfully processed by the adapter or if an error occurs while it is being processed. Receiver adapters do not support application acknowledgments. Sender adapters of the Adapter Engine do not request any acknowledgments.
Adapter-Specific Attributes in the Message Header
Some adapters support specific message attributes. See also: Adapter-Specific Attributes in the Message Header
Module Processor
It is possible to define generic modules for adapters in the module processor to equip the adapter with additional functions. For more information about the modules that are provided by SAP, see Modules.
For more information about developing adapters and modules, see Adapter and Module Development.