Hi ,
In XI, we can categorise the adapters as follows:
Technical Adapter: such as HTTP, SOAP, JDBC, Mail, etc.
SAP Application Adapters: such as RFC and IDoc.
Non-SAP Application Adapters: such as Oracle, Seibel, PeopleSoft, etc.
Industry Standard Adapters: such as CIDX, RosettaNet, EDI, etc.
Adapters: The task of an Adapter in SAP XI is to translate from the sender message format to XI message format or XI message format to receiver message format and can also be a called as a communication protocol between sender/receiver and SAP XI. Let us discuss various adapters which are widely and commonly used.
File Adapter: This is easiest adapter to start your hand on with SAP XI. You have the option to receive XML files or flat files. We use file content conversion to handle flat files like CSV files etc.
Details:
http://help.sap.com/saphelp_nw2004s/helpdata/en/ae/d03341771b4c0de10000000a1550b0/frameset.htm
Idoc Adapter: The next most commonly used adapter is Idoc adapter for sending and receiving Idocs
from SAP XI. The foremost step before configuring the idoc adapter is the system settings that have to be done
Details:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb...
Configuration steps required for posting idoc's (XI):
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
RFC Adapter: RFC adapter allows SAP XI to communicate with Integrating Systems using remote function call. It is nothing but a wrapper of SAP JCO.
Details:
http://help.sap.com/saphelp_nw2004s/helpdata/en/ae/d03341771b4c0de10000000a1550b0/frameset.htm
JDBC Adapter: We use this adapter to connect database systems using the JDBC driver. We need to deploy JDBC driver
Details:
http://help.sap.com/saphelp_nw2004s/helpdata/en/ae/d03341771b4c0de10000000a1550b0/frameset.htm
Mail Adapter: We can send and receive mails in SAP XI using mail adapter or by configuring SAP Connect and using SAP XI RFC Adapter
Details:
http://help.sap.com/saphelp_nw2004s/helpdata/en/ae/d03341771b4c0de10000000a1550b0/frameset.htm
SOAP Adapter: SOAP Adapter converts the SOAP messages into SAP XI message format that is SOAP with header attachments. This in an area many needs to really concentrate as it is heart of the ESA literature going forward.
Details:
http://help.sap.com/saphelp_nw2004s/helpdata/en/ae/d03341771b4c0de10000000a1550b0/frameset.htm
HTTP Adapter: The first thing any one need before starting is HTTP client for testing their scenarios
Refer:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/66dadc6e-0a01-0010-9ea9-bb6d8ca4...
JMS Adapter: I really don’t have a fair idea on this adapter and only help you in providing the links. You need JMS drivers before you start your interface.
Please go through the following links.....
Async/Sync Communication using JMS adapter without BPM (SP 19):
/people/sudheer.babu2/blog/2007/01/18/asyncsync-communication-using-jms-adapter-without-bpm-sp-19
Sync/Async communication in JMS adapter without BPM (SP19):
/people/venkataramanan.parameswaran/blog/2007/01/18/syncasync-communication-in-jms-adapter-without-bpm-sp19
First would be to deploy drivers for JMS scenarios - https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3867a582-0401-0010-6cbf-9644e49f...
Secondly, to configure JMS adapters;
http://help.sap.com/saphelp_nw04/helpdata/en/cd/d85a9d6fab7d4dbb7ae421f710626c/content.htm
In case JMS scenario that you have is a sync one, in that case if you are below SP19 you might have to build a BPM - ref: http://help.sap.com/saphelp_nw04/helpdata/en/83/d2a84028c9e469e10000000a1550b0/content.htm
/people/sudheer.babu2/blog/2007/01/18/asyncsync-communication-using-jms-adapter-without-bpm-sp-19
/people/venkataramanan.parameswaran/blog/2007/01/18/syncasync-communication-in-jms-adapter-without-bpm-sp19
How to correlate JMS messages - https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5059f110-0d01-0010-7c8b-fdc...
How to use conversion modules in JMS - https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f02d12a7-0201-0010-5780-8bf...
XI to Tibco Integration
XI provides SOAP adapters, Sender/receiver SOAP adapters to enable SOAP exchange between Xi integration server and remote clients. TIBCO BW/IM provides SOAP palettes which can be used to expose a web service(enable call from XI to TIBCO) or to send a request to a Web service(enable call from TIBCO to XI SOAP adapter).
One other way is to write Java/J2EE Applications using TIBCO SDK/RV APIs and then host them on the SAP J2EE engine. In this scenario we can use Java Proxy RunTime and send/receive messages to/from XI integration server.
One other way is to use TIBCO Enterprise for JMS client libraries. If you have a TIBCO environment(adapters/BW processes using JMS as the transport type) , then you can integrate with XI environment using JMS adapter provided by XI adapter framework. You need to make the JMS client libraries provided by TIBCO JMS server available to the XI JMS adapter and you should be all set.
Refer to following links for JMS adapter
http://help.sap.com/saphelp_nw2004s/helpdata/en/cd/d85a9d6fab7d4dbb7ae421f710626c/content.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3867a582-0401-0010-6cbf-9644e49f...
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f02d12a7-0201-0010-5780-8bfc7d12...
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/3.0/how%20to%20...
/thread/217893 [original link is broken]
/people/alessandro.guarneri/blog/2006/01/04/jms-sender-adapter-handling-too-short-lines
/people/william.li/blog/2006/11/13/how-to-use-saps-webas-j2ees-jms-queue-in-exchange-infrastructure
Regards,
Raj.
Bluesky
