Skip to Content

ADAPTERS IN XI/PI

  • Adapters enable the Integration EnginePartner Connectivity Kit
  • SAP offers several adapters to connect the Integration Engine to SAP legacy systems, as well as to external systems.
  • In this way, adapters integrate existing SAP components with SAP Exchange Infrastructure.

Different types of adapters

Application Adapters

Industry Standard Adapters

Technical Adapters

RFC Adapter

RosettaNet (RNIF 1.1) Adapter

Connectivity with WS providers and WS consumers (WS channel)

IDoc Adapter

RosettaNet (RNIF 2.0) Adapter

File/FTP Adapter (file system, FTP servers)

CIDX (RNIF 1.1) Adapter

Database (JDBC) Adapter

Java Messaging Service (JMS) Adapter

SOAP Adapter

“Plain HTTP” Adapter

Mail Adapter (mail servers using SMTP, IMAP4, POP3)

SAP Business Connector Adapter (SAP BC)

Marketplace Adapter (mySAP marketplaces)

Application Adapters:

  1. RFC Adapter
  2. IDoc Adapter

RFC Adapter:

  • RFC Adapter converts the incoming RFC calls to XML and XML messages to outgoing RFC calls. We can have both synchronous (sRFC) and asynchronous (tRFC) communication with SAP systems. The former works with Best Effort QoS (Quality of Service) while the later by Exactly Once (EO).
  • RFC Adapter is installed on the J2EE Adapter Engine and can be monitored via Adapter Monitoring and Communication Channel Monitoring in the Runtime Workbench.

RFC Sender Adapter

  • In this case, Sender SAP system requests XI Integration Engine to process RFC calls. This could either be synchronous or asynchronous.
  • On the source SAP system, go to transaction SM59 and create a new RFC connection of type ‘T’ (TCP/IP Connection). On the Technical Settings tab, select “Registered Server Program” radio button and specify an arbitrary Program ID. Note that the same program ID must be specified in the configuration of the sender adapter communication channel. Also note that this program ID is case-sensitive.

                   

RFC Receiver Adapter

  • In this case, XI sends the data in the RFC format (after conversion from XML format by the receiver adapter) to the target system where the RFC is executed.
  • Configuring the receiver adapter is even simpler. Create a communication channel in ID of type RFC Receiver (Please see the figure below). Specify the RFC Client parameters like the Application server details, logon credentials etc and activate the channel.

 

IDoc adapter

  • SAP XI IDoc Adapter is by and far the most widely used adapter.
  • IDoc Adapter converts the incoming IDoc to XML and XML messages to outgoing IDoc.
  • The IDoc adapter resides on the ABAP stack of the integration server and hence no Sender Agreement is necessary in order to setup the sender adapter.
  • A point to note is that using IDoc adapters, we can only have asynchronous (tRFC) processing.

IDoc Sender:

  • On the XI system, create a RFC destination of type R/3 connection, pointing to the source SAP Application system.
  • Also, create a port for the source system using transaction IDX1. Mention the above created RFC destination in the IDX1 port configuration.
  • This is required as XI uses this configuration to read the IDoc metadata from the source system.
  • Once you have done this, your XI system is ready to receive IDocs from the source SAP system.

 

IDoc Receiver Adapter

  • On the XI system, create a RFC destination of type R/3 connection, pointing to the source SAP Application system.
  • Also, create a port for the source system using transaction IDX1. Mention the above created RFC destination in the IDX1 port configuration.
  • This is required as XI uses this configuration to read the IDoc metadata from the source system. Once you have done this, your XI system is ready to receive IDocs from the source SAP system.

 

Industry Standard Adapters:

  1. RosettaNet (RNIF 1.1) Adapter
  2. RosettaNet (RNIF 2.0) Adapter
  3. CIDX (RNIF 1.1) Adapter

RosettaNet Adapter:

  • RNIF adapters support the data communication standard – RosettaNet Implementation Framework (RNIF) defined by RosettaNet. This standard defines RNIF protocols version 1.1 and 2.0. The RNIF adapters 1.1 and 2.0 are based on these protocols.
  • The adapters change the XI message format to the required RosettaNet message format. The adapters also change the format of messages from partner systems to the XI system.
  • You use RNIF adapters to send messages between the Integration Server and a RosettaNet-compliant system.
  • You implement RNIF adapters when you want to communicate with partner systems that do not understand the XI message format.

RosettaNet (RNIF 1.1) Adapter:

  • You use the RNIF Adapter 1.1 to send messages between the Integration Server and a RosettaNet-compliant system that supports RNIF version 1.1. The adapter changes the XI message format to the required RosettaNet message format. The adapter also changes the format of messages from partner systems to the XI system.
  • Supports the secure HTTP transport protocol for delivering business messages between trading partners
  • Ensures that a message sender is authorized to send the subject message to the receiving partner

RosettaNet (RNIF 1.1) Adapter Sender:

 

RosettaNet (RNIF 1.1) Adapter Receiver:

 

RosettaNet (RNIF 2.0) Adapter:

  • You can use the RNIF Adapter 2.0 to send messages between the Integration Server and a RosettaNet-compliant system that supports RNIF version 2.0.
  • The adapter transforms the Exchange Infrastructure (XI) message format to the RosettaNet message format.
  • The RNIF 2.0 Adapter supports some features not available in the RNIF Adapter 1.1.

RosettaNet (RNIF 2.0) Sender:

 

RosettaNet (RNIF 2.0) Receiver:

 

CIDX (RNIF 1.1) Adapter:

  • The CIDX adapter enables the execution of business transactions between CIDX trading partners based on Chem eStandards specifications.
  • The adapter implements the transport, packaging, and routing of CIDX business messages and signals as defined in the Chem eStandards envelope and security specifications (based on RNIF 1.1 specifications; more information: cidx.org).
  • Transport protocols to be used are HTTPS and HTTP. With HTTPS, client authentication is possible for sender party and receiver party.

CIDX (RNIF 1.1) Adapter Sender:

 

CIDX (RNIF 1.1) Adapter Receiver:

 

Technical Adapters:

  1. Connectivity with WS providers and WS consumers (WS channel)
  2. File/FTP Adapter (file system, FTP servers)
  3. Database (JDBC) Adapter
  4. Java Messaging Service (JMS) Adapter
  5. SOAP Adapter
  6. “Plain HTTP” Adapter
  7. Mail Adapter (mail servers using SMTP, IMAP4, POP3)
  8. SAP Business Connector Adapter (SAP BC)
  9. Marketplace Adapter (mySAP marketplaces)

Connectivity with WS providers and WS consumers (WS channel):

  • Using a communication channel that you have implemented the adapter type WS for, you can configure communication between Web service consumers.
  • Web service provider (for direct communication), or communication between Integration Server and a connected Web service consumer or Web service provider (for Integration Server communication).

WS Adapter Sender:

 

WS Adapter Receiver:

 

File/FTP Adapter (file system, FTP servers):

  • File Adapter converts incoming file into XML and vice versa. The adapter resides on the J2EE stack of the XI server.
  • It can read/write files directly from/to the XI server at the OS level using File System protocol.
  • It also works using FTP protocol, using which it can read/write files from/to any server location.
  • Configuration of File Adapter is quite simple and straightforward.

File Adapter Sender:

    

File Adapter Receiver:

   

Database (JDBC) Adapter:

  • The JDBC adapter is used to connect to different database systems via SAP PI.
  • The adapterconverts database content to XML messages and vice versa.
  • Sender JDBC Adapter is used to read data from databases while the receiver JDBC adapter writes data from SAP PI to the relevant databases.
  • To be able to use JDBC adapter with a particular database, you must install the corresponding JDBC drivers on your SAP PI server. The driver files can be obtained from the database vendor.

Database (JDBC) Adapter Sender:

 

Database (JDBC) Adapter Receiver:

 

Java Messaging Service (JMS) Adapter :

  • Oracle CEP provides two JMS adapters that you can use in your event applications to send and receive messages to and from a JMS queue, respectively, without writing any Java code. In particular:
  • The inbound JMS adapter receives map messages from a JMS queue and automatically converts them into events by matching property names with a specified event type. You can optionally customize this conversion by writing your own Java class to specify exactly how you want the incoming JMS messages to be converted into one or more event types.
  • The outbound JMS adapter sends events to a JMS queue, automatically converting the event into a JMS map message by matching property names with the event type. You can optionally customize this conversion by writing your own Java class to specify exactly how you want the event types to be converted into outgoing JMS messages.
  • The outbound JMS adapter sends events to a JMS queue, automatically converting the event into a JMS map message by matching property names with the event type. You can optionally customize this conversion by writing your own Java class to specify exactly how you want the event types to be converted into outgoing JMS messages.

   Java Messaging Service (JMS) Adapter Sender :

 

Java Messaging Service (JMS) Adapter Receiver:

 

 

SOAP Adapter:

  • The SOAP adapter enables you to exchange SOAP messages between remote clients or Web service servers and the Integration Server or the PCK.
  • In the SOAP adapter, you can specify security settings to be used to sign/verify the SOAP body. In addition, you can specify the standard to be used for signing/verifying the SOAP message.
    • SOAP Sender Adapter converts incoming SOAP messages into XML. In order to trigger SOAP Adapter, the sending application must send the message to the address in the following format:
    • http://<hostname>:<port>/XISOAPAdapter/MessageServlet? channel=<party>:<service>:<channel>.

SOAP Adapter Sender:

 

SOAP Adapter Receiver:

 

“Plain HTTP” Adapter:

  • The plain HTTP adapter gives application systems the option of communicating with the Integration Engineexchanging business data
  • The plain HTTP adapter is part of the Integration Engine. It comprises two parts, namely an adapter at the Integration Engine inbound channel and an adapter at the Integration Engine outbound channel.
  • The plain HTTP adapter is used by external systems to connect to the Integration Engine using the native HTTP interface (HTTP payload without SOAP envelope). These systems are connected using the Internet communication framework of the SAP Web Application Server. For this purpose, the Integration Engine HTTP inbound channel contains an HTTP service

There are two usage types for the plain HTTP adapter:

●     Synchronous processing

Ordering on the Internet with an order number as a response.

● Asynchronous processing

Ordering on the Internet without confirmation of the purchase.

“Plain HTTP” Adapter Sender:

 

“Plain HTTP” Adapter Receiver:

 

Mail Adapter (mail servers using SMTP, IMAP4, POP3 ):

  • The mail adapter resides on the J2EE stack and converts the XI messages into emails and transfers them to email server or in simple words sends them as emails to intended recipient(s).
  • The adapter supports SMTP as well as IMPA4 protocol. Message protocol provides two options, namely XIALL and XIPAYLOAD.
  • In the former entire SOAP message is sent as an attachment in mail along with the payload while in the latter only the message payload is sent.

Mail Adapter Sender:

 

Mail Adapter Receiver:

 

SAP Business Connector Adapter (SAP BC):

  • The SAP Business Connector adapter (BC adapter) supports the B2B protocol of the SAP Business Connector, which is based on HTTP.
  • The BC adapter enables you to replace a business connector with SAP Exchange Infrastructure or the PCK in scenarios where several SAP Business Connectors are used. This ensures guaranteed message delivery by SAP XI.
  • To connect to SAP Exchange Infrastructure and the PCK, you need SAP Business Connector 4.7.

SAP BC Adapter Sender:

 

SAP BC Adapter Receiver:

 

Marketplace Adapter (mySAP marketplaces):

  • We use the marketplace adapter to connect the Integration Server to marketplaces.
  • It enables messages to be exchanged by converting the XI message format to the marketplace format Market Set Markup Language (MML) and the other way around.
  • To be able to send messages from marketplaces to the Integration Server, you must first configure the sender marketplace adapter.
  • ·To be able to send messages from the Integration Server to marketplaces, you must first configure the receiver marketplace adapter
  • The receiver adapter supports system acknowledgments but not application acknowledgments.
  • The marketplace adapter takes existing attachments into account and forwards them on.

Marketplace Adapter Sender:

 

Marketplace Adapter Receiver:

 

ADAPTERS IN XI/PI

  • Adapters enable the Integration EnginePartner Connectivity Kit
  • SAP offers several adapters to connect the Integration Engine to SAP legacy systems, as well as to external systems.
  • In this way, adapters integrate existing SAP components with SAP Exchange Infrastructure.

Different types of adapters

Application Adapters

Industry Standard Adapters

Technical Adapters

RFC Adapter

RosettaNet (RNIF 1.1) Adapter

Connectivity with WS providers and WS consumers (WS channel)

IDoc Adapter

RosettaNet (RNIF 2.0) Adapter

File/FTP Adapter (file system, FTP servers)

CIDX (RNIF 1.1) Adapter

Database (JDBC) Adapter

Java Messaging Service (JMS) Adapter

SOAP Adapter

“Plain HTTP” Adapter

Mail Adapter (mail servers using SMTP, IMAP4, POP3)

SAP Business Connector Adapter (SAP BC)

Marketplace Adapter (mySAP marketplaces)

Application Adapters:

  1. RFC Adapter
  2. IDoc Adapter

RFC Adapter:

  • RFC Adapter converts the incoming RFC calls to XML and XML messages to outgoing RFC calls. We can have both synchronous (sRFC) and asynchronous (tRFC) communication with SAP systems. The former works with Best Effort QoS (Quality of Service) while the later by Exactly Once (EO).
  • RFC Adapter is installed on the J2EE Adapter Engine and can be monitored via Adapter Monitoring and Communication Channel Monitoring in the Runtime Workbench.

RFC Sender Adapter

  • In this case, Sender SAP system requests XI Integration Engine to process RFC calls. This could either be synchronous or asynchronous.
  • On the source SAP system, go to transaction SM59 and create a new RFC connection of type ‘T’ (TCP/IP Connection). On the Technical Settings tab, select “Registered Server Program” radio button and specify an arbitrary Program ID. Note that the same program ID must be specified in the configuration of the sender adapter communication channel. Also note that this program ID is case-sensitive.

                   

RFC Receiver Adapter

  • In this case, XI sends the data in the RFC format (after conversion from XML format by the receiver adapter) to the target system where the RFC is executed.
  • Configuring the receiver adapter is even simpler. Create a communication channel in ID of type RFC Receiver (Please see the figure below). Specify the RFC Client parameters like the Application server details, logon credentials etc and activate the channel.

 

IDoc adapter

  • SAP XI IDoc Adapter is by and far the most widely used adapter.
  • IDoc Adapter converts the incoming IDoc to XML and XML messages to outgoing IDoc.
  • The IDoc adapter resides on the ABAP stack of the integration server and hence no Sender Agreement is necessary in order to setup the sender adapter.
  • A point to note is that using IDoc adapters, we can only have asynchronous (tRFC) processing.

IDoc Sender:

  • On the XI system, create a RFC destination of type R/3 connection, pointing to the source SAP Application system.
  • Also, create a port for the source system using transaction IDX1. Mention the above created RFC destination in the IDX1 port configuration.
  • This is required as XI uses this configuration to read the IDoc metadata from the source system.
  • Once you have done this, your XI system is ready to receive IDocs from the source SAP system.

 

IDoc Receiver Adapter

  • On the XI system, create a RFC destination of type R/3 connection, pointing to the source SAP Application system.
  • Also, create a port for the source system using transaction IDX1. Mention the above created RFC destination in the IDX1 port configuration.
  • This is required as XI uses this configuration to read the IDoc metadata from the source system. Once you have done this, your XI system is ready to receive IDocs from the source SAP system.

 

Industry Standard Adapters:

  1. RosettaNet (RNIF 1.1) Adapter
  2. RosettaNet (RNIF 2.0) Adapter
  3. CIDX (RNIF 1.1) Adapter

RosettaNet Adapter:

  • RNIF adapters support the data communication standard – RosettaNet Implementation Framework (RNIF) defined by RosettaNet. This standard defines RNIF protocols version 1.1 and 2.0. The RNIF adapters 1.1 and 2.0 are based on these protocols.
  • The adapters change the XI message format to the required RosettaNet message format. The adapters also change the format of messages from partner systems to the XI system.
  • You use RNIF adapters to send messages between the Integration Server and a RosettaNet-compliant system.
  • You implement RNIF adapters when you want to communicate with partner systems that do not understand the XI message format.

RosettaNet (RNIF 1.1) Adapter:

  • You use the RNIF Adapter 1.1 to send messages between the Integration Server and a RosettaNet-compliant system that supports RNIF version 1.1. The adapter changes the XI message format to the required RosettaNet message format. The adapter also changes the format of messages from partner systems to the XI system.
  • Supports the secure HTTP transport protocol for delivering business messages between trading partners
  • Ensures that a message sender is authorized to send the subject message to the receiving partner

RosettaNet (RNIF 1.1) Adapter Sender:

 

RosettaNet (RNIF 1.1) Adapter Receiver:

 

RosettaNet (RNIF 2.0) Adapter:

  • You can use the RNIF Adapter 2.0 to send messages between the Integration Server and a RosettaNet-compliant system that supports RNIF version 2.0.
  • The adapter transforms the Exchange Infrastructure (XI) message format to the RosettaNet message format.
  • The RNIF 2.0 Adapter supports some features not available in the RNIF Adapter 1.1.

RosettaNet (RNIF 2.0) Sender:

 

RosettaNet (RNIF 2.0) Receiver:

 

CIDX (RNIF 1.1) Adapter:

  • The CIDX adapter enables the execution of business transactions between CIDX trading partners based on Chem eStandards specifications.
  • The adapter implements the transport, packaging, and routing of CIDX business messages and signals as defined in the Chem eStandards envelope and security specifications (based on RNIF 1.1 specifications; more information: cidx.org).
  • Transport protocols to be used are HTTPS and HTTP. With HTTPS, client authentication is possible for sender party and receiver party.

CIDX (RNIF 1.1) Adapter Sender:

 

CIDX (RNIF 1.1) Adapter Receiver:

 

Technical Adapters:

  1. Connectivity with WS providers and WS consumers (WS channel)
  2. File/FTP Adapter (file system, FTP servers)
  3. Database (JDBC) Adapter
  4. Java Messaging Service (JMS) Adapter
  5. SOAP Adapter
  6. “Plain HTTP” Adapter
  7. Mail Adapter (mail servers using SMTP, IMAP4, POP3)
  8. SAP Business Connector Adapter (SAP BC)
  9. Marketplace Adapter (mySAP marketplaces)

Connectivity with WS providers and WS consumers (WS channel):

  • Using a communication channel that you have implemented the adapter type WS for, you can configure communication between Web service consumers.
  • Web service provider (for direct communication), or communication between Integration Server and a connected Web service consumer or Web service provider (for Integration Server communication).

WS Adapter Sender:

 

WS Adapter Receiver:

 

File/FTP Adapter (file system, FTP servers):

  • File Adapter converts incoming file into XML and vice versa. The adapter resides on the J2EE stack of the XI server.
  • It can read/write files directly from/to the XI server at the OS level using File System protocol.
  • It also works using FTP protocol, using which it can read/write files from/to any server location.
  • Configuration of File Adapter is quite simple and straightforward.

File Adapter Sender:

    

File Adapter Receiver:

   

Database (JDBC) Adapter:

  • The JDBC adapter is used to connect to different database systems via SAP PI.
  • The adapter converts database content to XML messages and vice versa.
  • Sender JDBC Adapter is used to read data from databases while the receiver JDBC adapter writes data from SAP PI to the relevant databases.
  • To be able to use JDBC adapter with a particular database, you must install the corresponding JDBC drivers on your SAP PI server. The driver files can be obtained from the database vendor.

Database (JDBC) Adapter Sender:

 

Database (JDBC) Adapter Receiver:

 

Java Messaging Service (JMS) Adapter :

  • Oracle CEP provides two JMS adapters that you can use in your event applications to send and receive messages to and from a JMS queue, respectively, without writing any Java code. In particular:
  • The inbound JMS adapter receives map messages from a JMS queue and automatically converts them into events by matching property names with a specified event type. You can optionally customize this conversion by writing your own Java class to specify exactly how you want the incoming JMS messages to be converted into one or more event types.
  • The outbound JMS adapter sends events to a JMS queue, automatically converting the event into a JMS map message by matching property names with the event type. You can optionally customize this conversion by writing your own Java class to specify exactly how you want the event types to be converted into outgoing JMS messages.
  • The outbound JMS adapter sends events to a JMS queue, automatically converting the event into a JMS map message by matching property names with the event type. You can optionally customize this conversion by writing your own Java class to specify exactly how you want the event types to be converted into outgoing JMS messages.

   Java Messaging Service (JMS) Adapter Sender :

 

Java Messaging Service (JMS) Adapter Receiver:

 

 

SOAP Adapter:

  • The SOAP adapter enables you to exchange SOAP messages between remote clients or Web service servers and the Integration Server or the PCK.
  • In the SOAP adapter, you can specify security settings to be used to sign/verify the SOAP body. In addition, you can specify the standard to be used for signing/verifying the SOAP message.
    • SOAP Sender Adapter converts incoming SOAP messages into XML. In order to trigger SOAP Adapter, the sending application must send the message to the address in the following format:
    • http://<hostname>:<port>/XISOAPAdapter/MessageServlet? channel=<party>:<service>:<channel>.

SOAP Adapter Sender:

 

SOAP Adapter Receiver:

 

“Plain HTTP” Adapter:

  • The plain HTTP adapter gives application systems the option of communicating with the Integration Engineexchanging business data
  • The plain HTTP adapter is part of the Integration Engine. It comprises two parts, namely an adapter at the Integration Engine inbound channel and an adapter at the Integration Engine outbound channel.
  • The plain HTTP adapter is used by external systems to connect to the Integration Engine using the native HTTP interface (HTTP payload without SOAP envelope). These systems are connected using the Internet communication framework of the SAP Web Application Server. For this purpose, the Integration Engine HTTP inbound channel contains an HTTP service

There are two usage types for the plain HTTP adapter:

●     Synchronous processing

Ordering on the Internet with an order number as a response.

● Asynchronous processing

Ordering on the Internet without confirmation of the purchase.

“Plain HTTP” Adapter Sender:

 

“Plain HTTP” Adapter Receiver:

 

Mail Adapter (mail servers using SMTP, IMAP4, POP3 ):

  • The mail adapter resides on the J2EE stack and converts the XI messages into emails and transfers them to email server or in simple words sends them as emails to intended recipient(s).
  • The adapter supports SMTP as well as IMPA4 protocol. Message protocol provides two options, namely XIALL and XIPAYLOAD.
  • In the former entire SOAP message is sent as an attachment in mail along with the payload while in the latter only the message payload is sent.

Mail Adapter Sender:

 

Mail Adapter Receiver:

 

SAP Business Connector Adapter (SAP BC):

  • The SAP Business Connector adapter (BC adapter) supports the B2B protocol of the SAP Business Connector, which is based on HTTP.
  • The BC adapter enables you to replace a business connector with SAP Exchange Infrastructure or the PCK in scenarios where several SAP Business Connectors are used. This ensures guaranteed message delivery by SAP XI.
  • To connect to SAP Exchange Infrastructure and the PCK, you need SAP Business Connector 4.7.

SAP BC Adapter Sender:

 

SAP BC Adapter Receiver:

 

Marketplace Adapter (mySAP marketplaces):

  • We use the marketplace adapter to connect the Integration Server to marketplaces.
  • It enables messages to be exchanged by converting the XI message format to the marketplace format Market Set Markup Language (MML) and the other way around.
  • To be able to send messages from marketplaces to the Integration Server, you must first configure the sender marketplace adapter.
  • ·To be able to send messages from the Integration Server to marketplaces, you must first configure the receiver marketplace adapter
  • The receiver adapter supports system acknowledgments but not application acknowledgments.
  • The marketplace adapter takes existing attachments into account and forwards them on.

Marketplace Adapter Sender:

 

Marketplace Adapter Receiver:

 

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply