SAP

SAP offers several adapters to connect the Integration Engine to SAP legacy systems, as well as to external systems.
To find detail information on each adapter, click the corresponding area in the graphics below or select the corresponding entry in the list of adapters
below.

Overview of SAP Adapters

Adapters to Connect to Existing SAP Systems Adapters to Connect to Third Party and Messaging Systems

IDoc Adapter
File/FTP Adapter

RFC Adapter
Database (JDBC) Adapter

Java Messaging Service (JMS) Adapter

Specialized Messaging Adapters Adapters to Connect to Marketplaces

"Plain HTTP" Adapter
Marketplace Adapter

SOAP Adapter

Connectivity to Mainframes

Connecting CICS and SAP XI by Using SOAP

Further Information
For further information on adapters provided by SAP, see

XI 2.0 Online documentation under Runtime → Adapters

XI 2.0 Master Guide
Adapters to Connect to Existing SAP Systems
These adapters enable the Integration Server to communicate with SAP systems older than Release 6.20.

IDoc Adapter
Version 2.0 (contained in XI 2.0)
Supported release(s)/version(s) of the SAP applications based on
integrated software/standard

SAP Basis 3.1I or higher

SAP Web Application Server 6.10 or higher

Brief description of currently
supported features
Non-SAP applications with a certified IDoc interface, e.g. EDI systems (requires a reference R/3 system
to connect to for IDoc meta data)
The IDoc Adapter enables the exchange of IDoc messages with connected (SAP) applications via the
RFC protocol. Within the Integration Server IDocs are converted to XML messages or transferred as
native IDocs, depending on whether or not the IDoc should be delivered to receiver(s) as is.
Please note the following restriction:

Only the payload of a received message is evaluated. Additional attachments (such as trace
attachments) are ignored and not forwarded.

Availability
(when this adapter can be made available
Available with XI 2.0 at the beginning of ramp-up
by SAP to customers, or when this is
planned)
End of maintenance of the adapter Same as XI 2.0
Unidirectional/bi-directional
Bi-directional
(access to/from connected system)
Supported quality of service in
messaging
Guaranteed exactly once delivery of IDocs to and from the application system. Asynchronous IDoc
(best effort delivery, guaranteed exactly
interfaces only.
once delivery, guaranteed in order delivery,
etc.)
Supported data transfer languages
The IDoc Adapter supports the exchange of IDocs with SAP applications running in any single
(codepages of connected systems, Unicode,
codepage, or in Unicode modus.
etc.)
Platforms supported
Same as XI 2.0 (IDoc Adapter is contained in Integration Server)
(OS/DB combinations)
Supported end user languages
(for configuration and administration German, English, French, Japanese
purposes)
Sizing requirements
(CPU, RAM, disk space) (at least the Not installed separately
minimum requirements)
HA capabilities
Not installed separately, i.e. same as for Integration Server
(whether HA is supported, and how)
Further Information See Online documentation XI 2.0 under Runtime → Adapters → IDoc Adapter.

RFC Adapter
Version 2.0 (contained in XI 2.0)
Supported release(s)/version(s) of the SAP applications based on
integrated software/standard

SAP Basis 3.1I or higher

Brief description of currently supported
features
Availability
(when this adapter can be made available by
SAP to customers, or when this is planned)
End of maintenance of the adapter
Unidirectional/bi-directional
(access to/from connected system)
Supported quality of service in messaging
(best effort delivery, guaranteed exactly once
delivery, guaranteed in order delivery, etc.)
Supported data transfer languages
(codepages of connected systems, Unicode, etc.) codepage, or in Unicode modus.
Platforms supported
(OS/DB combinations)
Supported end user languages
(for configuration and administration purposes)
Sizing requirements
(CPU, RAM, disk space) (at least the minimum
requirements)
HA capabilities
(whether HA is supported, and how)
Further Information
Adapters to Connect to Third Party and Messaging Systems

SAP Web Application Server 6.10 or higher
The RFC Adapter enables you to connect SAP systems to the Integration Server in order to convert
XML messages to RFC function calls or vice versa.
Please note the following restrictions:

The RFC Adapter supports only transactional RFCs (tRFC), but no queued RFC (qRFC).

The RFC Adapter supports no Callbacks.

Non-SAP programs that use the RFC SDK cannot be used with the RFC Adapter, since
they do not offer any metadata.

There's no SAPgui support for debugging.

The context in the called system is not kept open over multiple calls (calls are stateless;
there is no session).

Only the payload of a received message is evaluated. Additional attachments (such as
trace attachments) are ignored and not forwarded.
The RFC Adapter is installed with the Integration Server and can be configured and maintained
with the Adapter Engine.
For more information on the Adapter Engine, see Online documentation XI 2.0 under Runtime →
Adapters → Adapter Engine.
Available with XI 2.0 at the beginning of ramp-up
Same as XI 2.0
Bi-directional
Best effort (synchronous RFC); guaranteed exactly once delivery of RFCs to and from the
application system (tRFC).
The RFC Adapter supports the exchange of RFCs with SAP applications running in any single
With respect to installation, the RFC Adapter consists of two parts, an ABAP-based part that runs
on SAP Web Application Server, and a Java-based part, implemented with the Adapter Engine.
The Java-part of the RFC Adapter uses SAP Java Connector (JCo) in order to convert RFC data
from an SAP system to XML. In particular, that SAP JCo has to be used that is part of J2EE Engine
of SAP Web Application Server.
Due to this, the RFC Adapter (Java part) supports all platforms that are supported by

SAP JCo
For more information on the platforms supported by SAP JCo, see SAP note 549268.

SAP J2EE Engine (part of SAP Web Application Server)
For more information on the platforms supported by SAP J2EE Engine, see SAP Web
Application Server - Product Availabilty Matrix

the Adapter Engine of SAP Exchange Infrastructure
The Adapter Engine runs on any environment where Java Development Kit (JDK) 1.3.1 is
installed.
English, German, French, and Japanese
Not installed separately
Not installed separately, i.e. same as for Integration Server
See Online documentation XI 2.0 under Runtime → Adapters → RFC Adapter.
 File/FTP Adapter
Version 2.0 (contained in XI 2.0)
Supported release(s)/version(s) File systems and FTP Server
of the integrated
software/standard
Brief description of currently The File/FTP Adapter enables you to connect file systems or FTP servers to the Integration Server. The file
supported features content may be sent as it is or in the case of CSV ("Comma Separated Value")-like structured files be
converted to a simple XML message for further processing in the Integration Server. Content received from
the Integration Server may be put as it is to a file or converted from a prepared XML format to a CSV format.
The File/FTP Adapter can be configured and maintained with the Adapter Engine. The Adapter Engine is
automatically installed on the Integration Server. However, it is possible to install the Adapter Engine and to
configure the File/FTP Adapter on another host.

Availability
(when this adapter can be made
Available with XI 2.0 at the beginning of ramp-up
available by SAP to customers, or
when this is planned)
End of maintenance of the
Same as XI 2.0
adapter
Unidirectional/bi-directional
Bi-directional
(access to/from connected system)
Supported quality of service in
messaging
Guaranteed exactly once delivery of files supported; guaranteed in order delivery supported (as far as a
(best effort delivery, guaranteed
sequence of files is defined)
exactly once delivery, guaranteed in
order delivery, etc.)
Supported data transfer Text files should be based on codepage UTF-8 in order to be processable by the Integration Engine.
languages Nevertheless, the File/FTP Adapter is able
(codepages of connected systems,
Unicode, etc.)
to use any codepage installed in the Java runtime environment (in case of foreign character sets)
to convert the files from any codepage sent by the Integration Server to any codepage

to convert files from any codepage to UTF-8 when sending to the Integration Server

The File/FTP Adapter runs on any environment where Java Development Kit (JDK) 1.3.1 is installed.
Platforms supported
Nevertheless, a reliable operation of the adapter is subject to the extent and the requirements of the specific
(OS/DB combinations)
scenario.
Supported end user languages
(for configuration and administration English, German, French, and Japanese
purposes)
Sizing requirements
128 MB RAM minimum, 256 MB RAM recommended (note that the actual requirements depend on the
(CPU, RAM, disk space) (at least the
delivery rate and the size of the messages).
minimum requirements)
HA capabilities If the connection to file system / FTP server is lost, it will be re-established as long as no breakdown of the
(whether HA is supported, and how) adapter occurs (guaranteed exactly once delivery of files prevents from any data inconsistencies).
Further Information See Online documentation XI 2.0 under Runtime → Adapters → Adapter Engine.

Database (JDBC) Adapter

Version 2.0 (contained in XI 2.0)
Supported release(s)/version(s) Database systems (with JDBC interface)
of the integrated
software/standard
Brief description of currently The JDBC Adapter enables you to connect database systems to the Integration Server in order to convert
supported features database content to XML messages and vice versa. Database content may be retrieved with any SQL
statement including stored procedures. For content from the Integration Server a specific XML format is
 specified that allows SQL-INSERT, UPDATE, SELECT, DELETE or stored procedure statements to be
processed. Any number of statements may be grouped together in one message. The content of a message
is always retrieved or stored inside one database transaction.
The JDBC Adapter can be configured and maintained with the Adapter Engine. The Adapter Engine is
automatically installed on the Integration Server. However, it is possible to install the Adapter Engine and to
configure the JDBC Adapter on another host.

Availability
(when this adapter can be made
Available with XI 2.0 at the beginning of ramp-up
available by SAP to customers, or
when this is planned)
End of maintenance of the
Same as XI 2.0
adapter
Unidirectional/bi-directional
Bi-directional
(access to/from connected system)
Supported quality of service in
messaging
(best effort delivery, guaranteed Guaranteed exactly once delivery of data supported; guaranteed in order delivery supported
exactly once delivery, guaranteed in
order delivery, etc.)
Supported data transfer
languages
The JDBC Adapter supports the codepage of the database system.
(codepages of connected systems,
Unicode, etc.)
The JDBC Adapter runs on any environment where Java Development Kit (JDK) 1.3.1 is installed.
Platforms supported
Nevertheless, a reliable operation of the adapter is subject to the extent and the requirements of the specific
(OS/DB combinations)
scenario.
Supported end user languages
(for configuration and administration English, German, French, and Japanese
purposes)
Sizing requirements
128 MB RAM minimum, 256 MB RAM recommended (note that the actual requirements depend on the
(CPU, RAM, disk space) (at least the
delivery rate and the size of the messages).
minimum requirements)
HA capabilities If the connection to database system is lost, it will be re-established as long as no breakdown of the adapter
(whether HA is supported, and how) occurs (guaranteed exactly once delivery of messages prevents from any data inconsistencies).
Further Information See Online documentation XI 2.0 under Runtime → Adapters → Adapter Engine.

Java Messaging Service (JMS) Adapter

Version
Supported release(s)/version(s) of the
integrated software/standard
Brief description of currently supported
features
2.0 (contained in XI 2.0)
Messaging systems (with JMS interface)
The JMS Adapter enables you to connect messaging systems to the Integration Server in order to
exchange messages with those messaging products.
The JMS Adapter can be configured and maintained with the Adapter Engine. The Adapter Engine is
automatically installed on the Integration Server. However, it is possible to install the Adapter Engine
and to configure the JMS Adapter on another host.

Availability
(when this adapter can be made available by Available with XI 2.0 at the beginning of ramp-up
SAP to customers, or when this is planned)
End of maintenance of the adapter Same as XI 2.0
Unidirectional/bi-directional
Bi-directional
(access to/from connected system)
Supported quality of service in messaging
Guaranteed exactly once delivery of messages supported; guaranteed in order delivery of messages
(best effort delivery, guaranteed exactly once
supported
delivery, guaranteed in order delivery, etc.)
Supported data transfer languages
(codepages of connected systems, Unicode, The JMS Adapter supports the codepage of the messaging system.
etc.)
The JMS Adapter runs on any environment where Java Development Kit (JDK) 1.3.1 is installed.
Platforms supported
Nevertheless, a reliable operation of the adapter is subject to the extend and the requirements of
(OS/DB combinations)
the specific scenario.
Supported end user languages
English, German, French, and Japanese
(for configuration and administration purposes)
Sizing requirements
256 MB RAM recommended (note that the actual requirements depend on the delivery rate and the
(CPU, RAM, disk space) (at least the minimum
size of the messages).
requirements)
If the connection to messaging system is lost, it will be re-established as long as no breakdown of
HA capabilities
the adapter occurs (guaranteed exactly once delivery of messages prevents from any data
(whether HA is supported, and how)
inconsistencies).
Further Information See Online documentation XI 2.0 under Runtime → Adapters → Adapter Engine.

Specialized Messaging Adapters

"Plain HTTP" Adapter

Version
Supported release(s)/version(s) of the
integrated software/standard
Brief description of currently supported
features
2.0 (contained in XI 2.0)
Non-SAP applications using a plain HTTP connection.
The Plain HTTP Adapter enables application systems to communicate with the Integration
Server and to exchange business data via HTTP without a SOAP envelope around the HTTP
payload (plain HTTP).
The external systems are connected using the Internet Communication Framework of the SAP
Web Application Server.

Availability
(when this adapter can be made available by SAP to Available with XI 2.0 at the beginning of ramp-up
customers, or when this is planned)
End of maintenance of the adapter Same as XI 2.0
Unidirectional/bi-directional
Bi-directional
(access to/from connected system)
Supported quality of service in messaging
Best effort delivery guaranteed; guaranteed exactly once delivery possible (if a GUID is
(best effort delivery, guaranteed exactly once
specified in the URL)
delivery, guaranteed in order delivery, etc.)

Supported data transfer languages The Plain HTTP Adapter supports the exchange of data in any format possible. Codepage
(codepages of connected systems, Unicode, etc.) convertion guaranteed for exchange of XML messages.
Platforms supported
Same as XI 2.0 (Plain HTTP Adapter is contained in Integration Server)
(OS/DB combinations)
Supported end user languages
German, English, French, Japanese
(for configuration and administration purposes)
Sizing requirements
(CPU, RAM, disk space) (at least the minimum Not installed separately
requirements)
HA capabilities
Not installed separately, i.e. same as for Integration Server
(whether HA is supported, and how)
Further Information See Online documentation XI 2.0 under Runtime → Adapters → Plain HTTP Adapter.

SOAP Adapter
Version
Supported release(s)/version(s) of
the integrated software/standard
Brief description of currently
supported features
2.0 (contained in XI 2.0)
Remote clients or servers of Web Services
The SOAP Adapter enables you to exchange SOAP messages between the Integration Server and remote
clients or providers of Web Services.
The SOAP inbound Adapter runs on the Integration Server. The SOAP outbound Adapter can be
configured and maintained with the Adapter Engine. The Adapter Engine is automatically installed on the
Integration Server. However, it is possible to install the Adapter Engine and to configure the SOAP
outbound Adapter on another host.

Availability
(when this adapter can be made available
Available with XI 2.0 at the beginning of ramp-up
by SAP to customers, or when this is
planned)
End of maintenance of the adapter Same as XI 2.0
Unidirectional/bi-directional
Bi-directional
(access to/from connected system)
Supported quality of service in
messaging
Guaranteed exactly once delivery of messages supported; guaranteed in order delivery of messages
(best effort delivery, guaranteed exactly
supported
once delivery, guaranteed in order
delivery, etc.)
Supported data transfer languages
(codepages of connected systems, The SOAP Adapter supports the codepage of the external system.
Unicode, etc.)
Platforms supported

SOAP inbound Adapter: Same as XI 2.0 (SOAP inbound Adapter is contained in Integration
(OS/DB combinations)
Server)

SOAP outbound Adapter: The SOAP outbound Adapter runs on any environment where Java
Development Kit (JDK) 1.3.1 is installed. Nevertheless, a reliable operation of the adapter is
subject to the extend and the requirements of the specific scenario.

Supported end user languages

(for configuration and administration English, German, French, and Japanese
purposes)
Sizing requirements

SOAP inbound Adapter: Not installed separately, i.e. same as for Integration Server
(CPU, RAM, disk space) (at least the
minimum requirements)
SOAP outbound Adapter: 256 MB RAM recommended (note that the actual requirements depend
on the delivery rate and the size of the messages).

HA capabilities

SOAP inbound Adapter: Not installed separately, i.e. same as for Integration Server
(whether HA is supported, and how)

SOAP outbound Adapter: Not (yet) supported

Further Information See Online documentation XI 2.0 under Runtime → Adapters → Adapter Engine.

Adapters to Connect to Marketplaces

Marketplace Adapter
Version 2.0 (contained in XI 2.0)
Supported release(s)/version(s) of mySAP marketplaces
the integrated software/standard
Brief description of currently The SAP Marketplace Adapter can be used to connect the Integration Server to mySAP marketplaces. It
supported features enables to exchange messages between the Integration Server and mySAP marketplaces by transforming
the XI message format (XML body with a SOAP envelope) into mySAP marketplace's message format
MarketSet Markup Language (MMS), and vice versa.
Availability
(when this adapter can be made
Available with XI 2.0 at the beginning of ramp-up
available by SAP to customers, or when
this is planned)
End of maintenance of the adapter Same as XI 2.0
Unidirectional/bi-directional
Bi-directional
(access to/from connected system)
Supported quality of service in
messaging
(best effort delivery, guaranteed Best effort delivery and guaranteed exactly once delivery of messages is supported.
exactly once delivery, guaranteed in
order delivery, etc.)
Supported data transfer languages
Marketplace Adapter supports the exchange of SOAP messages with Marketplace systems running on
(codepages of connected systems,
codepage UTF-8, or in Unicode modus.
Unicode, etc.)
Platforms supported Same as XI 2.0 (Marketplace Adapter is contained in Integration Server); additionally, SQL Server databases
(OS/DB combinations) are supported.
Supported end user languages
(for configuration and administration English, German, French, Spanish, Italian, Japanese, Korean, Norwegian, and Portuguese
purposes)
Sizing requirements
(CPU, RAM, disk space) (at least the The actual sizing requirements depend on the delivery rate and the size of the messages.
minimum requirements)
HA capabilities Dispatching mechanism for messages between different server nodes supports high availability
(whether HA is supported, and how) requirements. In order to guarantee full failover capabilities, specific configuration of the server node may
be required.
Note that SAP Marketplace Adapter is based on J2EE Engine of SAP Web Application Server. For more
information on High Availabilty of SAP Web AS, see the page High Availabilty for the SAP Web Application
Server in the High Availabilty area in SAPNet (http://intranet.sap.com/ha).

For information on the configuration of Marketplace Adapter, see SAP Marketplace Adapter and SAP
Further Information
Messaging System 2.0 SP1