on 2008 Jun 23 6:22 AM
what is advantage of adapters (like idoc , file ..) in XI ?
Thank in advance
gupt
HI
I think u have received all the knowledge regarding the Adapters. Plz close the thread if u r satisified with the answers.
Edited by: vemuganti naga phalguna on Jun 25, 2008 12:55 PM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
/people/michal.krawczyk2/blog/2005/01/02/simple-adapter-and-message-monitoring
chk it
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi gupta ,
The Adapter Framework is responsible for communication between the SAP XI Integration Server and any SAP or non-SAP systems.
The Adapter Framework communicates using JCA 1.0 connections (2) and the JCA 1.0 Common Client Interface (CCI) with an adapter. The JCA 1.0 container of the SAP J2EE server uses the JCA 1.0 Service Programming Interface (SPI) to exchange server-relevant information with the adapter according to JCA 1.0 (1). Therefore, the adapter must be a JCA 1.0-compliant resource adapter. Since JCA 1.0 does not define the communication direction from the adapter to the Adapter Framework (application in the JCA sense), the Adapter Framework is called from the adapter with a standard Enterprise JavaBean 2.0 session bean.
A message from the Integration Server is received in the Adapter Framework by the messaging service. Based on the receiver information, the corresponding module chain is selected in the module processor for further processing.
The Adapter Framework contains two default module chains: one for the sender/inbound direction and one for the receiver/outbound direction. You can use these default module chains for your adapter if the entire message processing is executed within the adapter. You can enhance the default module chains with customer-specific modules. The module processor controls the steps in the module chain by calling generic and, if defined, adapter-specific modules (3). The last module in the module chain forwards the message to the adapter using JCA CCI (2). The adapter transfers the message to the connected system.
Transport Protocol and Message protocol in Adapter CC parameters
Transport Protocol
This parameter defines the transport protocol for processing the message.
Message Protocol
This parameter defines the message protocol for processing the message.
In what format does the message come from Sending system to XI and what happens after it reaches XI
The Adapter Framework controls the exchange of synchronous and asynchronous XI messages and communicates with the Integration Server to do this.
The adapters in the Adapter Framework convert XI messages to the protocols of connected external systems and the other way around.
If your adapter provides a mechanism to create WSDL, XSD, or DTD files to create message metadata.
The loading of example XML documents is supported but should be avoided, as it does not describe all document variants.
You use the Adapter Engine to connect the Integration Engine to SAP systems (RFC adapter) and external systems. You use the various adapters in the Adapter Engine to convert XML- and HTTP-based messages to the specific protocol and format required by these systems, and the other way around.
Please go through below links
SAP NW 7.0 Process Integration - Adapter Framework & Adapter Strategy
SAP NetWeaver End-to-End Process Integration: Adapter Framework
Development of Adapters for the SAP XI Adapter Framework
Structure of the Adapter Framework
http://help.sap.com/saphelp_nw04/helpdata/en/fd/16e140a786702ae10000000a155106/frameset.htm
Adapter Framework Module Interfaces (SAP Library - Partner Connectivity Kit)
http://help.sap.com/saphelp_nw04/helpdata/en/32/43d84072378031e10000000a1550b0/frameset.htm
Full life cycle project and Implementation project
End-to-End Process Integration: New Features with SAP NetWeaver 2004s Relevant for SAP Exchange Infrastructure Customers
Adapters enable communication between the XI integration engine and an application system. This leads to the compatibility between heterogeneous systems.Adapters convert the XI protocol (SOAP with attachments over HTTP) to the protocol spoken by the application system and vice-versa.The key purpose of XI is to integrate heterogeneous systems and adapters are the key enabler to achieving this goal
Adapter Categories
Application adapters provided by SAP (IDoc and RFC) and 3rd party vendors (Seeburger, Siebel, Oracle, ...)
Technical adapters relate to specific protocols
File systems (FTP / File)
RDBMS systems (JDBC)
Messaging systems (JMS)
Web services (SOAP)
Mail servers (SMTP)
SAP Business Connector
Marketplaces
Industry standard adapters
RosettaNet
CIDX
The Adapter Engine
The XI Adapter engine is the home of the majority of the XI adapters. Only the IDoc adapter and the plain HTTP adapter do not reside on the adapter engine. They reside on the Integration Server.
It is fully integrated in to the XI landscape with tools provided for configuration, logistics and monitoring. It's Adapter Framework is based on the JCA.
SAP XI requires an adapter framework to communicate outside of the SAP system. These adapters translate code from external applications to an XML message for NetWeaver processes using the Java Connector Architecture.It is a part of the Adapter Engine, which provides interfaces for configuring, managing, and monitoring adapters.
Structure of the Adapter Framework
http://help.sap.com/saphelp_nw04/helpdata/en/fd/16e140a786702ae10000000a155106/content.htm
Adapter for SAP XI environment
List of all adapters compatible with XI 3.0
Adapter and Module Development
http://help.sap.com/saphelp_nw04/helpdata/en/8b/895e407aa4c44ce10000000a1550b0/content.htm
Legacy Integration with the SAP XI Adapter
Installing the SAP XI Integration Components of the XI Adapter
http://documentation.softwareag.com/crossvision/xio311/install/sapXiInstall.htm
reg,
suresh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi gupta ,
The Adapter Framework is responsible for communication between the SAP XI Integration Server and any SAP or non-SAP systems.
The Adapter Framework communicates using JCA 1.0 connections (2) and the JCA 1.0 Common Client Interface (CCI) with an adapter. The JCA 1.0 container of the SAP J2EE server uses the JCA 1.0 Service Programming Interface (SPI) to exchange server-relevant information with the adapter according to JCA 1.0 (1). Therefore, the adapter must be a JCA 1.0-compliant resource adapter. Since JCA 1.0 does not define the communication direction from the adapter to the Adapter Framework (application in the JCA sense), the Adapter Framework is called from the adapter with a standard Enterprise JavaBean 2.0 session bean.
A message from the Integration Server is received in the Adapter Framework by the messaging service. Based on the receiver information, the corresponding module chain is selected in the module processor for further processing.
The Adapter Framework contains two default module chains: one for the sender/inbound direction and one for the receiver/outbound direction. You can use these default module chains for your adapter if the entire message processing is executed within the adapter. You can enhance the default module chains with customer-specific modules. The module processor controls the steps in the module chain by calling generic and, if defined, adapter-specific modules (3). The last module in the module chain forwards the message to the adapter using JCA CCI (2). The adapter transfers the message to the connected system.
Transport Protocol and Message protocol in Adapter CC parameters
Transport Protocol
This parameter defines the transport protocol for processing the message.
Message Protocol
This parameter defines the message protocol for processing the message.
In what format does the message come from Sending system to XI and what happens after it reaches XI
The Adapter Framework controls the exchange of synchronous and asynchronous XI messages and communicates with the Integration Server to do this.
The adapters in the Adapter Framework convert XI messages to the protocols of connected external systems and the other way around.
If your adapter provides a mechanism to create WSDL, XSD, or DTD files to create message metadata.
The loading of example XML documents is supported but should be avoided, as it does not describe all document variants.
You use the Adapter Engine to connect the Integration Engine to SAP systems (RFC adapter) and external systems. You use the various adapters in the Adapter Engine to convert XML- and HTTP-based messages to the specific protocol and format required by these systems, and the other way around.
Please go through below links
SAP NW 7.0 Process Integration - Adapter Framework & Adapter Strategy
SAP NetWeaver End-to-End Process Integration: Adapter Framework
Development of Adapters for the SAP XI Adapter Framework
Structure of the Adapter Framework
http://help.sap.com/saphelp_nw04/helpdata/en/fd/16e140a786702ae10000000a155106/frameset.htm
Adapter Framework Module Interfaces (SAP Library - Partner Connectivity Kit)
http://help.sap.com/saphelp_nw04/helpdata/en/32/43d84072378031e10000000a1550b0/frameset.htm
Full life cycle project and Implementation project
End-to-End Process Integration: New Features with SAP NetWeaver 2004s Relevant for SAP Exchange Infrastructure Customers
Adapters enable communication between the XI integration engine and an application system. This leads to the compatibility between heterogeneous systems.Adapters convert the XI protocol (SOAP with attachments over HTTP) to the protocol spoken by the application system and vice-versa.The key purpose of XI is to integrate heterogeneous systems and adapters are the key enabler to achieving this goal
Adapter Categories
Application adapters provided by SAP (IDoc and RFC) and 3rd party vendors (Seeburger, Siebel, Oracle, ...)
Technical adapters relate to specific protocols
File systems (FTP / File)
RDBMS systems (JDBC)
Messaging systems (JMS)
Web services (SOAP)
Mail servers (SMTP)
SAP Business Connector
Marketplaces
Industry standard adapters
RosettaNet
CIDX
The Adapter Engine
The XI Adapter engine is the home of the majority of the XI adapters. Only the IDoc adapter and the plain HTTP adapter do not reside on the adapter engine. They reside on the Integration Server.
It is fully integrated in to the XI landscape with tools provided for configuration, logistics and monitoring. It's Adapter Framework is based on the JCA.
SAP XI requires an adapter framework to communicate outside of the SAP system. These adapters translate code from external applications to an XML message for NetWeaver processes using the Java Connector Architecture.It is a part of the Adapter Engine, which provides interfaces for configuring, managing, and monitoring adapters.
Structure of the Adapter Framework
http://help.sap.com/saphelp_nw04/helpdata/en/fd/16e140a786702ae10000000a155106/content.htm
Adapter for SAP XI environment
List of all adapters compatible with XI 3.0
Adapter and Module Development
http://help.sap.com/saphelp_nw04/helpdata/en/8b/895e407aa4c44ce10000000a1550b0/content.htm
Legacy Integration with the SAP XI Adapter
Installing the SAP XI Integration Components of the XI Adapter
http://documentation.softwareag.com/crossvision/xio311/install/sapXiInstall.htm
cheers!
gyanaraj
****Pls reward points if u find this helpful
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI
The Adapter Framework runs on the J2EE stack of the SAP WEB AS. The Adapter Framework provides common functionality for the:
1) Adapter Engine
2) Partner Connectivity Kit (PCK)
And supports the J2EE Connector Architecture (JCA). The Adapter Framework provides and extendable platform for developing and running adapters in the XI environment.
Common functionality provided to the Adapter Engine and PCK by the Adapter Framework include scalability, clustering, high availability, thread management, queuing, and logging services. The Adapter Framework can also stand alone without connection to an integration server and still provide the properties and features provided to the Adapter Engine and PCK.
The Adapter Framework also provides overall integration enabling the centralized configuration, administrating and monitoring of each deployed adapter within the integration directory. This allows the monitoring of the end to end message flow across all XI components and applications across a system landscape. It helps prevent redundant maintenance, provides a single point of access and common UI, and provides transportable configuration.
Adapters
are part of the Adapter Framework. Adapters provide the technical connectivity to enable the integration of SAP and non-SAP applications through XIu2019s Integration Engine.
Adapter Framework Monitoring (i.e. information per Communication Channel / Adapter) can be accessed via the following URL: http://<host>:<port>/AdapterFramework. This is monitoring only, not stop / start or control of the Adapter itself.
Again, Adapters are used for connectivity from and to external systems with XI that cannot communicate via proxies. There are numerous Adapter Types already available and more constantly being added. For a current list, see:
u2022 SAP Service Marketplace under u2018SAP XI in Detailu2019 then u2018Connectivityu2019 for SAP provided adapters
u2022 http://www.sap.com/partners/icc for 3rd party vendor certified adapters
Adapter Engine: We use adapters to connect other systems to integration server. Apart from idoc adapter all adapters run on adapter engine, it provides services like messaging, queuing, security handling. Adapter converts messages from sender into XI Message format, and converts messages from integration engine to receiver message format.
Types of Adapters:
Application Adapters
Technical Adapters
Industry Standard Adapters
Adapter Engines:
Central Adapter Engine
Non Central Adapter Engine
J2se Adapter engine
PCK
Adapters are part of adapter framework. They provide technical connectivity to enable the integration of sap and non sap applications.
XI Adapter
The communication via web service may have advantages, if you want communicate with non XI systems.
In your scenario, there is direct communication between XI engines, so you can go for XI adapter. The XI adapter which is normally used to configure the exchange of messages with in an Integration Server, canbe extended to exchange messages between the two Integration Servers in the scenario.
Purpose
You configure the XI adapter to exchange messages with an Integration Engine. Both XI 3.0 and XI 2.0 message protocols are supported. You also use the XI adapter to exchange messages between SAP Exchange Infrastructure and the Partner Connectivity Kit (PCK).
You can use security settings to sign messages and check the signature. You can encrypt and decrypt message payloads.
Features
u2022 To receive XML messages from a sender system, configure the sender XI adapter.
JDBC -- 1)Read database ( Using query and Stored Procedure)
2) Write database using SP and Query and standary
statement structure provided by SAP.
3) Synchronous Communication with database using BPM.
FILE -- 1) Pick and drop file on FTP server
2) Pick and drop file from XI server itself using NFS.
3) Module configuration.
4) Content conversion.
5) Dynamic file name using variables.
6) creating queues if required.
IDOC -- > Posting IDocs to SAP systems.
XI --- > 1) Communicate with systems using ABAP stack
2) J2SE engines
3) Other XI environments
4) Routing of data to other environments.
SOAP -- > 1) Posting Webservices
IDOC ADAPTER:
Idoc adapter resides on the ABAP engine and the Idoc is sent directly to the Integration Engine of XI from the R3 system hence no sender idoc adapter and no sender agreement for the idoc adapter. The IDOC Adapter is implemented in ABAP and reside directly on the Integration Server (ABAP Stack).Hence cannot define a sender IDOC channel in directory due to the fact that the IDOC adapter does not run in J2EE Adapter Framework but is an "built in" adapter same for the HTTP adapter also.
The IDOC Adapter is implemented in ABAP and reside directly on the Integration Server (ABAP Stack).You cannot define a sender IDOC channel in directory due to the fact that the IDOC adapter does not run in J2EE Adapter Framework but is a "built in" adapter.
Idoc adapter resides on the ABAP engine and the Idoc is sent directly to the Integration Engine of XI from the R3 system and so , no sender idoc adapter and no sender agreement for the idoc adapter
Advantages and Disadvantages of IDOC adapter:
1. Limited to 1000 bytes / record.
2. User cannot access the data as in PSA.
3. Data Security is more.
4. Good for less volume of data.
5.Fast to load, easy processing, low programming for standard IDOCu2019s
6.Good knowledge of IDOC processing required, time consuming if changes have to be made to a created IDOC
7.It cannot be used for SYNCHRONOUS COMMN
8.Maintence of port and Genration of partner profile is difficult.
9.ALE configuration steps required for both in XI and SAP-R/3.
Go through the below link for furtehr assistance on Adapters
http://enterprisearchitecture.nih.gov/ArchLib/AT/TA/IntegrationAdaptersBrick.htms
cheers
Edited by: vemuganti naga phalguna on Jun 25, 2008 12:57 PM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Adapters are used in XI for converting sender format in to the local format of XI or the local format to the receiver format of XI.they help us in communicating..
we can categorise the adapters:
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#
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:
Many of todays interfaces still base on file exchanges which e.g often used to integrated mainframe applicatonns.
new file interface should tray to use XML - based messages, so that a later migration to a webservice based
communication can be implemented with less effort.
Consideation regarding XI file Adapter:
1) FTP file transfer is handled by the sending system.
2) FTP file transfer is done to a temporary file name:<file name>.tmp(existingtemp.files are overwritten)
IDOC #
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:
In the case where we encounter a standard IDOC provided by SAP or Situation where a mapping is available or
an IDOC as well as a BAPI exits, the approach will be dependent on the specific integration scenarioo......
for For example, options might be
1) sending one IDOC at a time
2) combing multiple IDOCS and sending as a single IDOC.
3) making one single RFC call, for each business transation.
4) avoiding multiple calls to the same BAPI / RFC by deploying a wrapper BAPI and sending all records in one call.
5) Using the proxy and sending all data in one shot and making single calls to the BAPI from the proxy.
proxy and rfc adapter #
a proxy on the SAP application system should be used while interfacing with a standard BAPI or remote enabled
function modules on the application system. the proxy will be invoked by SAP PI/XI and on the application system
the proxy will call the BAPI. in SAP systems with WEB AS versions <6.20 the proxy option is not available and hence
the RFC adapter should be used insted.
Disadvantage:
pre-built meta data and the mapping that SAP delivers will not be usefull as the BAPI is wrapped with a proxy.
so if the pre-defined integration content is not taken into account the proxy should be used insted of configuring
the RFC adapter and calling the BAPI / RFC
Advantage:
it bypasses the adapter engine and directly interacts with the application system and integration engine thereby
enchancing the performance
XI SOAP Adapter
If a non sap application already provides webservice interfaces, this integration technology should be preferred to
migrate to a service-oriented architecture.
XI JDBC Adapter
If non sap application stores its data in a common database and no webservice interfaces are availble, an integration based
on database exchane tables may be a feasible solution,so that file uplode and downlode logic can be avoided.
XI Plain HTTP Adapter.
Especially in case of external communicaton with customers or suppliers which don't have web service based interfaces in a place,plain HTTP with
XML - based or even flat-text messages has to be used.new interfaces should try to use WEB services insted.
Regards
Srinivasreddy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Adapters purpose is to convert the data(source data to XML format and vice versa using Message Protocol) and Transfer the data(by using the transport protocol).
http://help.sap.com/saphelp_nw70/helpdata/EN/ae/d03341771b4c0de10000000a1550b0/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/ad/bf93409c663228e10000000a1550b0/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/0d/5ab43b274a960de10000000a114084/frameset.htm
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Advantages of File ;->
1) Fast
2) Support Content conversion, we can convert any type of file to XML using FCC.
3) Supports NFS protocol and FTP also
4) Can use EO and EOIO both.
5) Module support.
6) Easy to monitor and Debug.
7) Can access remote and Local servers.
😎 Can produce dynamic file names and folder directory using dynamic variable substitution.
9) Have options like counter, timestamp etc.
10) It can be configured on Decentral adapter engine like J2SE easily.
Disadvantages :
1) Does not produce XML directly like JDBC adapter.
2) Content conversion is difficult and need lot of effort to produce the desired structure.
JDBC
Advantages : 1) Can read any database if proper drivers are installed.
2) Creates XML structure of data from database
automatically
3) No content conversion required
4) Query and Stored procedure supported.
5) Can be used for both Synchronus and Asynchronous
processing.
Disadvantages : 1) Correct drivers need to be deployed for each type
of database
Kulwinder
Reward if Helpful
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Adapters are used in XI for converting sender format in to the local format of XI or the local format to the receiver format of XI.they help us in communicating..
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:
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:
JMS Adapter: I really dont 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...
Thanks,
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:
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:
JMS Adapter: I really dont 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...
Thanks,
Vijaya
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Gupta,
Please read the Rules of Engagement before posting further questions in SDN forums. Do some research, there are plenty of articles in SDN and help.sap.com to help you start with. Read those and post a question if you have any problems with that. A question like this is very very abstract and does not add any value to to anybody.
P.S: I am sure this question is going to gather you a lot of links from SDN and help.sap.com. Instead you could do that yourself using the search functionality.
Regards,
Jaishankar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
66 | |
11 | |
11 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.