Difference between RFC adapter and a proxy

Can any one tell me the technical difference between RFC adapter and a proxy?
reg

There are advantages / disadvantages for RFC / Proxies / Idocs. So if I am in your position depending upon the requirement I will choose one. Some of the differences are:
RFC and Proxy:
RFC/BAPI has its own overhead of function call.
Proxies communicate with the XI server by means of native SOAP calls over HTTP .RFC does not, so you have to convert from SOAP to RFC calls and vice versa. So XML conversion is required.
ABAP Proxies uses Webservice and Http Protocols.
If you use ABAP Proxy , you can reduce the overhead calling the function again and again.
Proxy and Idoc:
IDOC : After recieving the strucutred data It processes it using a Function Module associated with it.
Proxy : Proxy is a structure where there is no processing function module associated. You need to explicitly write the Business Logic/Call the subroutines here
This is my absolutely my view. Another guy has his own response. So first go through your requirements and then you can decide for what to go.
Also go through this urls which may help you:
/people/michal.krawczyk2/blog/2006/04/19/xi-rfc-or-abap-proxy-abap-proxies-with-attachments
RFC VS PROXY
/people/ravikumar.allampallam/blog/2005/08/14/choose-the-right-adapter-to-integrate-with-sap-systems
Re: IDOC and RFC
Re: Proxy Vs IDOC
Thanks
Rodrigo

Similar Messages

  • Difference In RFC Adapter and XI proxy

    I am using RFC adapter for master data and XI proxy for transaction data , can anyone tell me what is major difference and what is negative point in using RFC adapter
    Thanking you
    sridhar

    Hi,
    Adapters enable the Integration Engine and the Partner Connectivity Kit (PCK) to communicate with different applications.Adapters 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, for example. In the process, XML and HTTP-based documents are converted to IDocs (IDoc adapter) and RFCs (RFC adapter) and the other way around. This enables you to integrate your existing SAP infrastructure with the new SAP infrastructure, which is based on system integration and the exchange of XML messages.
    The plain HTTP adapter gives application systems the option of communicating with the Integration Engine and exchanging business data in a simple format, using an HTTP connection.
    RFC Adapter :
    The RFC adapter enables you to use the functions of the Integration Engine or the PCK in existing SAP landscapes. It is used by SAP systems to connect to the Integration Engine or the PCK by using the RFC interface. It supports SAP systems as of version 3.1x.
    For FAQs about the RFC adapter, see SAP Note 730870
    The RFC adapter is provided by the Adapter Engine and the PCK. It essentially comprises two parts, namely a sender adapter at the Integration Engine inbound channel, and a receiver adapter at the Integration Engine outbound channel.
    The adapters are configured in the configuration part of the Integration Builder, or in the configuration part of the PCK. You use the SAP Java Connector (JCo), which enables you to manage metadata. This in turn enables you to map RFC data generically to RFC XML and the other way around.
    The receiver RFC adapter can be used for mapping lookups.A communication channel with a receiver RFC adapter can be created automatically for business systems that are defined in the System Landscape Directory.
    The RFC adapter maps the following RFC calls to XML messages and the other way around:
    Synchronous RFC calls (sRFCs) in messages with quality of service Best Effort (BE)
    ●     Transactional RFC calls (tRFCs) in messages with quality of service Exactly Once (EO)
    ●     The receiver RFC adapter can also process messages with quality of service Exactly Once In Order (EOIO). They are mapped to transactional RFC calls (tRFC).
    You require the sender adapter if you want to use the Integration Engine or the PCK to process RFCs. The RFC adapter converts the incoming RFC data to XML message format (RFC XML) so that it can be processed by the Integration Engine or the PCK.
    You require the receiver adapter if the determined receiver system expects the data from the Integration Engine or the PCK to arrive in RFC format. In this case, the Integration Engine or the PCK must transfer the received XML message (RFC XML) to the RFC adapter. The RFC adapter converts the RFC XML message to a valid RFC call and executes the call.
    Proxy :
    Generally speaking, interfaces are where functions in a system can be executed. In the context of SAP Exchange Infrastructure, only the following interfaces are relevant:
    ·        Interfaces designed for message exchange between application systems
    ·        Interfaces used by a cross-component integration process to receive or send messages, or both
    Starting with a cross-system integration process, you can then derive the corresponding interfaces required. SAP Exchange Infrastructure supports this process by using an integration scenario to describe the collaborative process. The integration scenario summarizes the interfaces required for this collaborative process.
    You can use SAP interfaces that already exist in systems, non-SAP interfaces that are connected to SAP Exchange Infrastructure using adapters, or define new interfaces called message interfaces in the Integration Repository. Both worlds can also be interconnected in a collaborative process.
    Interfaces are an essential component of SAP Exchange Infrastructure:
    ·        You define the interfaces to be used in an integration scenario.
    ·        Cross-component integration processes use interfaces to exchange messages.
    ·        You define the XML transformations for messages that are to be exchanged between two interfaces in a mapping.
    ·        You assign an interface in a sender system to one or more interfaces in a receiver system in logical routing.
    ·        You generate proxies to implement your scenario based on message interfaces.
    You save interface descriptions (message interfaces, BAPIs, RFCs, and IDocs) in the Integration Repository so that they can be referenced throughout SAP Exchange Infrastructure. However, adapters for external systems do not normally use interfaces; instead they access files or database tables in order to function, for example. For this reason, it is not necessary to import these interfaces into the Integration Repository. If the structure of the message is described using a WSDL, XSD, or DTD schema, you can import the schema as an external definition.
    Hope this will help you.
    Regards
    Aashish Sinha
    PS : reward points if helpful

  • Differences between SOAP Adapter and WS Adapter

    Hi Experts,
    In order to consume a service in SAP ECC by SAP PI 7.1, I´m using a service based on RFC. I tryed sucessfully to do that using SOAP Adapter and WS Adapter.
    What are the differences between using a receiver communication channel with SOAP adapter or WS adapter? Which is the better way ?
    Tks in advance.

    Hi,
    Please go through the below URLs for a discussion of SOAP  and WS adapters:
    The difference between SOAP adapter and WS adapter in PI 7.1
    WS adapter vs. SOAP adapter
    Regards,
    Rajeev Gupta
    Edited by: RAJEEV GUPTA on Jan 9, 2009 3:41 PM

  • The difference between SOAP adapter and WS adapter in PI 7.1

    Hello all,
    can anybody explain what is the main difference between SOAP adapter and WS adapter in PI 7.1?
    I have checked this [link|http://help.sap.com/saphelp_nwpi71/helpdata/en/0d/5ab43b274a960de10000000a114084/frameset.htm]
    but was not able to find the real difference.
    Or better, what can I do with WS adapter I can't do with SOAP adapter? What are their advantages/disadvantages?
    Thank you all, Igor.

    In addition to RM, ws adapter also support other ws standard like SAML which is not available in SOAP adatper. Beside:
    if your sender or receiver is SAP system, you can also monitor the message in the sender/receiver in addition to the PI box. This is a very good thing, because sometime the MONI in PI shows nothing wrong, but the MONI in your receiver will show you error message that's only related to the receiver system.
    However, if you define ws sender CC, and your ws client doesn't support RM, you will have issue sending ws request.
    And ws CC will generate ws runtime in PI box, if your configuration is wrong (like user name and password not correct), even if you correct it, the ws runtime sometime won't be regenated based on the correction. In this case you need to delete the ws CC/agreement, and re-create it with all correct information.
    Beside make sure your basis team configured the PI system properly regarding ws. If not, you will have lot of pain to figure the problem which was my case.
    Jayson

  • Difference between HTTP adapter and SOAP adapter

    Hi All,
      Can any one tell me abt what is the main difference between HTTP adapter and SOAP  adapter.when we'll use these eactly?
    Thanks
    pullarao.

    Hi Rao,
    Please go through the below links to understand it:
    https://www.sdn.sap.com/sdn/weblogs.sdn?blog=/pub/wlg/1442 [original link is broken] [original link is broken] [original link is broken] [original link is broken]
    More links for SOAP Adapter:
    /people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi
    http://help.sap.com/saphelp_nw04/helpdata/en/9f/fdca3f01f33e1ce10000000a114084/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/69/a6fb3fea9df028e10000000a1550b0/frameset.htm
    More links on HTTP adapters.
    /people/siva.maranani/blog/2005/09/15/push-data-to-mvc-architectured-application-using-xi
    /people/prasadbabu.nemalikanti3/blog/2006/02/27/collecting-and-bundling-vendor-records-from-different-multiple-interfaces-file-systempeoplesoft-and-sending-to-sap-r3-system-part-2
    Regards,
    Subhasha

  • Difference between OA Adapter and DB Adapter

    Hi All,
    i am very new to SOA, Let me know the difference between OA Adapter and DB Adapter.
    thanks
    Hari

    The EBS (OA) Adapter is mainly a sort of wrapper around DB and AQ adapter supporting the different interfaces of EBS including Business Events(AQ).
    The adapter introspects the Integration Repository. And it sets the responsiblity/application context for you when connecting. The ebs-user and responsibility are set in the wsdl. Using the database adapter you should take care of that yourself.
    Honestly, if you're basically using custom-plsql api's or the pl/sql api's of ebs (eg. TCA) then you're perfectly fine with the DB-adapter. The only thing is that you should set the responsiblity in the pl/sql yourself (for example in the intialization block of the pl/sql package).
    Regards,
    Martien

  • Difference between AQ Adapter and JMS Adapter

    Hi All,
    i am very new to SOA. let me know the difference between AQ Adapter and JMS Adapter.
    thanks
    Hari

    Please go thru the bellow link
    http://www.mscd.edu/~ittsdba/oradoc817/ois.817/a83729/adois07.htm#408020
    Krishna

  • Difference between XI adapter and HTTP adapter

    Hi,
    I am not very clear on the exact difference between XI adapter and HTTP adapter.
    I want to know, when should we use XI adapter and when to use HTTP adapter.
    Regards,
    Santosh

    Hi,
    We use HTTP Adapter in case of the Application is trying to post the HTTP Request message to XI and able to receive the HTTP Message from XI also.
    While using the HTTP as Sender , HTTP Sits on ABAP Stack and can able to communicate with the Integration Server Directly, No need of any Adapter here, it is adapterless communication
    In Case of Client Proxies
    Source application can directly interact with the XI by executing the report in SAP R/3 & will be able to send the XML data to IS,
    So no need of the XI Adapter in this case to post xml to XI.
    In Case of Server Proxies
    Now XI has to post the xml data to the Target Application, here some thing shld be there to establish the medium with the Target System. So we use XI adapter here.
    In the receiver case, we need XI Adaper to communicate XI integration Server with the Local Integration Engine( Which we made in SAP R/3's Business system as local IE) to post the data
    Basically XI adapter will be used in normal scenarios also to communicate Adapter Engine with Integration Server internally while delivering the msg.
    Check this Msg Flow how the XI Adapter is used in Normal Scenarios
    Understanding message flow in XI
    REgards
    Seshagiri

  • Difference between File adapter and FTP adapter

    hi,
    I would like to know what is the difference between File adapter and FTP adapter
    thanks
    Yatan

    Both file and ftp adapters are non-concurrent jca adaps, however we go for file adapters mostly when you have files on your local environment and do not need to wait for someone to FTP the files on a timely basis. In case of FTP Adapter, we would need an FTP Server, a remote location with access where in files pitch in for polling.
    Also, File adapter is dependent on the local folder and OS, however FTP adapter is dependent on the local as well as the remote file system/OS/folder permissions/user access.

  • Difference between Idoc Adapter and Proxies..

    HI XI Guru's,
    I am new to XI, I wanted to know what is the difference between Idoc adpater and proxies. When and what should be preffered ?
    Warm Regards,
    - Priya R

    idocs which mean - (intermediate documents)  are standard  document formats which sap systems use to store as well send data from one system to another. If this is the format in which data has to received by R/3 then you will use idoc adapter in XI.  idoc adapter can be used to communicate between systems is with  SAP release higher than  3.1.X. Communication using idoc adapter is always asynchronous.
    proxies are available for communication between  SAP systems with version WAS 6.20 and above. They support both synchronous as well as asynchronous modes of communication. Generally when you are looking at developing new application using WAS 6.20 and above then you can design the interfaces for this new applications in SAP XI and generate the required code for these interfaces automatically in SAP systems using transaction code - SPROXY in the case of ABAP Proxy and in the case of Java proxies the code is generated by SAP XI system itself. You only have to implement these interfaces in your new application. So, basically you have to only worry about building the application and the interface part is taken care by XI itself. you can also look at using proxies when data has to be inserted or fetched from custom/standard tables in R/3 using XI.
    ,idoc adapter can be used for commuincation between ABAP stacks only but Proxy can be used for both ABAP as well JAVA stack.

  • Difference between RFC, SYSTEM and AUDIT users?

    Hi All,
    Can you highlight the main differences between the following users:
    RFC
    SYSTEM
    AUDIT
    how do their functions differenciate them ?
    Thanks in advance,
    Diwakar

    RFC User
    RFC user is basicly used to receive status messages. An RFC user has to be created in all the system clients where messages needs to be recieved. An RFC user can also be used for receiving messages using SMTP plug-in.
    The RFC User is an sap user of type System and that's why no person can logon with this user on SAP System.
    Following is thr procedure to create RFC User, remember the purpose is to recieve messages including status messages as well.
    Creation of RFC User
    Go to  Tools > Administration > User Maintenance > Users.
    Enter a name, for example MAIL_ADMIN.
    Select "New"
    On the Logon data tab page, select the user type System.
    Enter a password.
    On the Profiles tab page, enter the authorization profile S_A.SCON. This profile minimizes the risk of misuse, even if the communication system does not store the password is encoded form.
    Select "Save"
    Both RFC user and a System user are of type System only. Now the difference, depends upon the profile and authorization of the user.
    Audit users are of type dialog, and can be used by a person to logon to system. There might be many roles assigned to this user. My understanding is that an Audit User is not a standard sap type user but just a dialog user and can be created with a conventional method of creating any other dialog users with a specific profile and authorizations.
    Still to confirm, Can you please tell us, how many types of users does it shown in 4.6c at the time of user creation?
    Best Regards,
    Amol Bharti

  • Difference between DB adapter and Ebusiness Application adapter

    Could anyone please explain the difference between the two adapters?
    If you want to access Applications objects, you could this via the DB adapter - so why use the other one?
    Rgds, Henrik

    DB adapter connect to any database, bu form most of all the Oracle database.
    The Apps Adapter is based on the DB adapter, and access only the specific components of Oracle EBS, that are exposed.
    Marc

  • Diff between Seeburger Adapter and File Adapter

    Hi All,
             My company needs to interact with some banks and the banks are particular that they want SFTP, which is not supported by  File Adapter, so we have decided to go with Seeburger adapter.
    Now what are the differences between File adapter and seeburger adapter?
    I believe that Seeburger adapter does not support File Content Conversion, Archiving etc.
    Could you all pls put some light on the diff between file adapter and seeburger adapter when it comes to dealing with files?
    Xier

    Hi
    You are aware with working of File Adapter.
    The most direct way of using the Seeburger adaptors is to configure the BIC as a module. There is a software component from seeburger called bicmapper which will allow you to
    1. Define or import the inbound message metadefinition in various formats ( edifact, xml,...)
    2. Using a mapping create an xml variant as the output metadefinition or edifact in the other direction.
    3. Create a one to one mapping between input en output.
    4. Export the metadata in xsd or sda format for import in XI
    5. Generate an SDA which can be deployed in XI and used as a module.
    Have a look here,
    http://www.seeburger.com/fileadmin/com/pdf/SAP_Exchange_Infrastructure_Integratio_Strategy.pdf
    Some Seeburger related information
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/e2aeb02c-0601-0010-d680-c9be61ffa390
    Go through this threads:
    http://www.seeburger.com/fileadmin/com/pdf/SAP_Exchange_Infrastructure_Integratio_Strategy.pdf
    Need Material on Seeburger Adapters.
    Seeburger Adapter
    Installing seeburger adapter
    http://www.seeburger.com/xi-adapters/
    Thanks

  • Difference between WS runtime and proxy runtime

    HI,
    I'm new to PI/XI. 1) Could anyone please explain about the real difference between WS runtime and Proxy runtime?
    2) How to configure the scenario's for WS communication and proxy communication?
    3) what is the adapter type we should use for this in ID?
    4) How to convert the proxy to webservice? etc.
    Thanks in adavnce
    Regards,
    Baskaran K

    I'm new to PI/XI.
    I would suggest that you first make use of the Search facility of SDN. If I am not wrong all your questions will be answered by a Search.
    Regards,
    Abhishek.

  • What is the Difference between AQ adpater and JMS adapter??

    What is the Difference between AQ adpater and JMS adapter in BPEL11g??
    In what scenarios we go for AQ and for what scenarios we go for JMS adapter???

    Go for AQ when using Oracle Advanced Queueing (the database stuff).
    Use JMS when using JMS (in memory of file queues)
    hth,
    Peter Paul

Maybe you are looking for