sap xi adapters

8/13/2019 SAP XI Adapters

1/8

SAPSAP 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 adaptersbelow.

Overview of SAP Adapters

Adapters to Connect to Existing SAP Systems IDoc Adapter RFC Adapter

Adapters to Connect to Third Party and Messaging Systems File/FTP Adapter Database (JDBC) Adapter Java Messaging Service (JMS) Adapter

Specialized Messaging Adapters "Plain HTTP" Adapter SOAP Adapter

Adapters to Connect to Marketplaces Marketplace 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


2/8

Adapters to Connect to Existing SAP Systems

These adapters enable the Integration Server to communicate with SAP systems older than Release 6.20.

Doc Adapter

Version 2.0 (contained in XI 2.0)

Supported release(s)/version(s) of theintegrated software/standard

SAP applications based on SAP Basis 3.1I or higher SAP Web Application Server 6.10 or higher

Non-SAP applications with a certified IDoc interface, e.g. EDI systems (requires a reference R/3 systemto connect to for IDoc meta data)

Brief description of currentlysupported features

The IDoc Adapter enables the exchange of IDoc messages with connected (SAP) applications via theRFC protocol. Within the Integration Server IDocs are converted to XML messages or transferred asnative 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 traceattachments) are ignored and not forwarded.

Availability (when this adapter can be made availableby SAP to customers, or when this isplanned)

Available with XI 2.0 at the beginning of ramp-up

End of maintenance of the adapter Same as XI 2.0

Unidirectional/bi-directional (access to/from connected system) Bi-directional

Supported quality of service inmessaging (best effort delivery, guaranteed exactlyonce delivery, guaranteed in order delivery,etc.)

Guaranteed exactly once delivery of IDocs to and from the application system. Asynchronous IDocinterfaces only.

Supported data transfer languages (codepages of connected systems, Unicode,etc.)

The IDoc Adapter supports the exchange of IDocs with SAP applications running in any singlecodepage, or in Unicode modus.

Platforms supported (OS/DB combinations) Same as XI 2.0 (IDoc Adapter is contained in Integration Server)

Supported end user languages (for configuration and administrationpurposes)

German, English, French, Japanese

Sizing requirements (CPU, RAM, disk space) (at least theminimum requirements)

Not installed separately

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

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

RFC Adapter



SAP applications based on SAP Basis 3.1I or higher


3/8

SAP Web Application Server 6.10 or higher

Brief description of currently supportedfeatures

The RFC Adapter enables you to connect SAP systems to the Integration Server in order to convertXML 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 maintainedwith the Adapter Engine.For more information on the Adapter Engine, see Online documentation XI 2.0 under Runtime

Adapters Adapter Engine .

Availability (when this adapter can be made available bySAP to customers, or when this is planned)




Supported quality of service in messaging (best effort delivery, guaranteed exactly oncedelivery, guaranteed in order delivery, etc.)

Best effort (synchronous RFC); guaranteed exactly once delivery of RFCs to and from theapplication system (tRFC).

Supported data transfer languages (codepages of connected systems, Unicode, etc.)

The RFC Adapter supports the exchange of RFCs with SAP applications running in any singlecodepage, or in Unicode modus.

Platforms supported (OS/DB combinations)

With respect to installation, the RFC Adapter consists of two parts, an ABAP-based part that runson 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 datafrom an SAP system to XML. In particular, that SAP JCo has to be used that is part of J2EE Engineof 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 InfrastructureThe Adapter Engine runs on any environment where Java Development Kit (JDK) 1.3.1 isinstalled.

Supported end user languages (for configuration and administration purposes) English, German, French, and Japanese

Sizing requirements (CPU, RAM, disk space) (at least the minimumrequirements)



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

Adapters to Connect to Third Party and Messaging Systems


4/8

File/FTP Adapter


Supported release(s)/version(s)of the integratedsoftware/standard

File systems and FTP Server


The File/FTP Adapter enables you to connect file systems or FTP servers to the Integration Server. The filecontent may be sent as it is or in the case of CSV ("Comma Separated Value")-like structured files beconverted to a simple XML message for further processing in the Integration Server. Content received fromthe 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 isautomatically installed on the Integration Server. However, it is possible to install the Adapter Engine and toconfigure the File/FTP Adapter on another host.

Availability (when this adapter can be madeavailable by SAP to customers, orwhen this is planned)


End of maintenance of theadapter Same as XI 2.0


Supported quality of service inmessaging (best effort delivery, guaranteedexactly once delivery, guaranteed inorder delivery, etc.)

Guaranteed exactly once delivery of files supported; guaranteed in order delivery supported (as far as asequence of files is defined)

Supported data transferlanguages (codepages of connected systems,Unicode, etc.)

Text files should be based on codepage UTF-8 in order to be processable by the Integration Engine.

Nevertheless, the File/FTP Adapter is able 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.Nevertheless, a reliable operation of the adapter is subject to the extent and the requirements of the specificscenario.


English, German, French, and Japanese


128 MB RAM minimum, 256 MB RAM recommended (note that the actual requirements depend on thedelivery rate and the size of the messages).

HA capabilities (whether HA is supported, and how) If the connection to file system / FTP server is lost, it will be re-established as long as no breakdown of theadapter 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


Supported release(s)/version(s)of the integratedsoftware/standard

Database systems (with JDBC interface)


The JDBC Adapter enables you to connect database systems to the Integration Server in order to convertdatabase content to XML messages and vice versa. Database content may be retrieved with any SQLstatement including stored procedures. For content from the Integration Server a specific XML format is


5/8

specified that allows SQL-INSERT, UPDATE, SELECT, DELETE or stored procedure statements to beprocessed. Any number of statements may be grouped together in one message. The content of a messageis always retrieved or stored inside one database transaction.

The JDBC Adapter can be configured and maintained with the Adapter Engine. The Adapter Engine isautomatically 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 madeavailable by SAP to customers, orwhen this is planned)


End of maintenance of theadapter Same as XI 2.0



Guaranteed exactly once delivery of data supported; guaranteed in order delivery supported

Supported data transferlanguages (codepages of connected systems,Unicode, etc.)

The JDBC Adapter supports the codepage of the database system.


The JDBC 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 extent and the requirements of the specificscenario.



Sizing requirements

(CPU, RAM, disk space) (at least theminimum requirements)

128 MB RAM minimum, 256 MB RAM recommended (note that the actual requirements depend on thedelivery rate and the size of the messages).

HA capabilities (whether HA is supported, and how)

If the connection to database system is lost, it will be re-established as long as no breakdown of the adapteroccurs (guaranteed exactly once delivery of messages prevents from any data inconsistencies).


Java Messaging Service (JMS) Adapter



Messaging systems (with JMS interface)


The JMS Adapter enables you to connect messaging systems to the Integration Server in order toexchange messages with those messaging products.

The JMS Adapter can be configured and maintained with the Adapter Engine . The Adapter Engine isautomatically installed on the Integration Server. However, it is possible to install the Adapter Engineand to configure the JMS Adapter on another host.

Availability (when this adapter can be made available bySAP to customers, or when this is planned)





Guaranteed exactly once delivery of messages supported; guaranteed in order delivery of messagessupported


6/8

Supported data transfer languages (codepages of connected systems, Unicode,etc.)

The JMS Adapter supports the codepage of the messaging system.


The JMS 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 purposes) English, German, French, and Japanese


256 MB RAM recommended (note that the actual requirements depend on the delivery rate and thesize of the messages).


If the connection to messaging system is lost, it will be re-established as long as no breakdown ofthe adapter occurs (guaranteed exactly once delivery of messages prevents from any datainconsistencies).


Specialized Messaging Adapters

"Plain HTTP" Adapter



Non-SAP applications using a plain HTTP connection.


The Plain HTTP Adapter enables application systems to communicate with the IntegrationServer and to exchange business data via HTTP without a SOAP envelope around the HTTPpayload (plain HTTP).

The external systems are connected using the Internet Communication Framework of the SAPWeb Application Server.

Availability (when this adapter can be made available by SAP tocustomers, or when this is planned)





Best effort delivery guaranteed; guaranteed exactly once delivery possible (if a GUID isspecified in the URL)

Supported data transfer languages (codepages of connected systems, Unicode, etc.)

The Plain HTTP Adapter supports the exchange of data in any format possible. Codepageconvertion guaranteed for exchange of XML messages.

Platforms supported (OS/DB combinations) Same as XI 2.0 (Plain HTTP Adapter is contained in Integration Server)

Supported end user languages (for configuration and administration purposes) German, English, French, Japanese




Further Information See Online documentation XI 2.0 under Runtime Adapters Plain HTTP Adapter .

SOAP Adapter


7/8


Supported release(s)/version(s) ofthe integrated software/standard

Remote clients or servers of Web Services


The SOAP Adapter enables you to exchange SOAP messages between the Integration Server and remoteclients or providers of Web Services.

The SOAP inbound Adapter runs on the Integration Server. The SOAP outbound Adapter can beconfigured and maintained with the Adapter Engine . The Adapter Engine is automatically installed on theIntegration Server. However, it is possible to install the Adapter Engine and to configure the SOAPoutbound Adapter on another host.

Availability (when this adapter can be made availableby SAP to customers, or when this isplanned)




Supported quality of service inmessaging (best effort delivery, guaranteed exactlyonce delivery, guaranteed in orderdelivery, etc.)

Guaranteed exactly once delivery of messages supported; guaranteed in order delivery of messagessupported

Supported data transfer languages (codepages of connected systems,Unicode, etc.)

The SOAP Adapter supports the codepage of the external system.


SOAP inbound Adapter: Same as XI 2.0 (SOAP inbound Adapter is contained in IntegrationServer)

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




SOAP inbound Adapter: Not installed separately, i.e. same as for Integration Server 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

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


Adapters to Connect to Marketplaces

Marketplace Adapter


Supported release(s)/version(s) ofthe integrated software/standard

mySAP marketplaces

Brief description of currently The SAP Marketplace Adapter can be used to connect the Integration Server to mySAP marketplaces. It


8/8

supported features enables to exchange messages between the Integration Server and mySAP marketplaces by transformingthe XI message format (XML body with a SOAP envelope) into mySAP marketplace's message formatMarketSet Markup Language (MMS) , and vice versa.

Availability (when this adapter can be madeavailable by SAP to customers, or when

this is planned)





Best effort delivery and guaranteed exactly once delivery of messages is supported.

Supported data transfer languages (codepages of connected systems,Unicode, etc.)

Marketplace Adapter supports the exchange of SOAP messages with Marketplace systems running oncodepage UTF-8, or in Unicode modus.


Same as XI 2.0 (Marketplace Adapter is contained in Integration Server); additionally, SQL Server databasesare supported.


English, German, French, Spanish, Italian, Japanese, Korean, Norwegian, and Portuguese


The actual sizing requirements depend on the delivery rate and the size of the messages.


Dispatching mechanism for messages between different server nodes supports high availabilityrequirements. In order to guarantee full failover capabilities, specific configuration of the server node maybe required.

Note that SAP Marketplace Adapter is based on J2EE Engine of SAP Web Application Server. For moreinformation 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 ).

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

sap xi adapters

Documents