RFC vs Proxy

Hello ,
We are working on JDBC to RFC scenario in SAP XI,
We have to do
huge functionality like calling Two standard Transaction working on two BDC programs and Creating the Log errors and additional performs in side the RFc.
IS it advisable to do like that..
Or better to use Server proxy.
If we use server proxy what are the advantages and issues in this scenario.

difference between RFC and Proxy :
*proxy is always better than RFc in many cases *
Proxy Supports Synchronus and asynchronus Communicatio .
proxy it is used to procees the Mapping and rooting on Integration Enginee bypass th Adapter Enginee so it will improve the performance.
dont need to create Sender Communiv=cation Channel and Agreement in ID .
proxy support more than 5 MB.
proxy is used to control Application, Sysytem Error.
supports Ackonwledgements
supports Attachments
but if u want to use Client Proxy then need to write REport.
Rfc :
RFc Supports Synchronus and asynchronus Communication.
Dont need to write any Repotr.
need to create Communication channels in ID.
RFC Adapter :
http://help.sap.com/saphelp_nw04/helpdata/en/33/c6e63b60c25767e10000000a11402f/frameset.htm
step by step:
http://www.****************/Tutorials/XI/RFC2JDBC/Index.htm
proxy:
http://help.sap.com/saphelp_nw04/helpdata/en/86/58cd3b11571962e10000000a11402f/frameset.htm
what is Server proxy and client proxy
Client Proxy - https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1387
Server Proxy - https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1457
Step-by-Step Guide on Proxy Runtime Configuration and Proxy to JDBC Scenario Using Canonical Objects and PIS in PI 7.1
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e0ac1a33-debf-2c10-45bf-fb19f6e15649?QuickLink=index&overridelayout=true
http://www.****************/Tutorials/XI/ABAPClientProxy/page1.htm
refer below thread for more info:
http://scn.sap.com/thread/2144939

Similar Messages

Which is better for bulk message scenario in sap xi RFC or Proxy

which is better for bulk message scenario in ( RFC or Proxy ) ?
Edited by: prabhatxi on Aug 6, 2010 4:44 PM

Proxy will alwaays be better option in this case, as it is adapter less framework, and communication happens directly with XI central integration engine. So it is always fast communication and gives good performance.
But still you should consider other factors, you may consider using RFC as well, as sometime we go for RFC/IDOC as this are the standard interfaces already available rather than creating structure...
May be you can share more info on what type/volume data are you planning to send via XI?
Hope this cleart your doubt..
Divyesh

BAPI or RFC or PROXY

Hi Experts,
I have a scenario where purchase order and goods receipt info is coming from an external application to XI.
Too update ECC with the same..do i use a bapi/rfc or proxy?
I mean call bapi in the proxy or import bapi directly?..what is the best procedure?
Is it possible to use purchase order IDOC?...
Do we have any BAPI for creating internal order?

Hi Teja,
Find below some of the threads related to that.
[When and Where and how to use Proxies]
[When to use RFC ,Idoc and proxies]
[Re: Proxies Vs. Adapters: When to use Proxy?]
[Use of Proxies(both java and abap)]
Regards,
Venu V
Edited by: Venu V on Jul 27, 2009 2:24 PM

"MAPPING" EXCEPTION_DURING_EXECUTE in scenario RFC TO PROXY

Hello all
I am facing a problem in a RFC PROXY SCENARIO and I don´t whether I can solve it .
System A : R3
System B : XI
And my scenario is RFC TO PROXY.
i will implement the proxy in the ABAP XI . For now I have entered no code.
I have mapped an rfc from r3 to my data type . My message mapping , Interface maping works very well .
When I start the program in R3 . I got the following error in the trace of sxmb_moni
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_MM_MAT_</SAP:P1>
<SAP:P2>java.lang.NullPointerException</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>java.lang.NullPointerException thrown during application mapping com/sap/xi/tf/_MM_MAT_:</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
How can make this scenario working ?

Stan,
Follow the steps below:
1. Take the source XML message from SXI_MONI
2. Save the xml message into your desktop.
3. Log into Integration Repository and open the concerned mapping object.
4. Go to test tab and upload this xml at the source side.
5. see whether everything is green at source message type.
6. execute
7. you will find the error in the log immediately after executing
see for the error and take appropriate action.
Best Regards,
Kiran Bobbala

Query on using RFC or proxy

Hi,
I have a scenario which is from SAP to PI to Legacy. The legacy system is giving a wsdl file.And from SAP we have a standard BAPI available. I am thinking of going for a RFC-PI- SOAP scenario. But there are discussions going on to use Proxy. Please let me know which would be the feasible option using RFC or proxy at the sender.IT is a synchronus
Thanks

is depends upon the requirement- if u have std bapi of RFc available for the same requirement then go for that and if not then u can create ur custom program to send the data through proxy...proxy will have added advantage of performance..over RFC.
chirag

RFC - Java Proxy (Synchronous) invoking method

Hi,
I have problems to call my inbound java proxy.
My scenario consist of send RFC -> Java Proxy (Synchronous)
Proxy this registered
http://hcp095.intra.csc.es:50100/ProxyServer/register?ns=http://csc.es/xi/rca&interface=Z_RCA_SCS&bean=ZRCASCS_PortTypeBean&method=zRCASCS
ejb-jar.xml:
<ejb-jar>
    <description>EJB JAR description</description>
    <display-name>EJB JAR</display-name>
    <enterprise-beans>
        <session>
            <ejb-name>ZRCASCS_PortTypeBean</ejb-name>
            <home>com.sap.aii.proxy.xiruntime.core.AbstractProxyInboundHome4</home>
            <remote>com.sap.aii.proxy.xiruntime.core.AbstractProxyInboundRemote4</remote>
            <local-home>com.sap.aii.proxy.xiruntime.core.AbstractProxyInboundLocalHome4</local-home>
            <local>com.sap.aii.proxy.xiruntime.core.AbstractProxyInboundLocal4</local>
            <ejb-class>es.csc.xi.rca.ZRCASCS_PortTypeBean</ejb-class>
            <session-type>Stateless</session-type>
            <transaction-type>Container</transaction-type>
        </session>
    </enterprise-beans>
</ejb-jar>
Class Impl:
package es.csc.xi.rca;
public class ZRCASCS_PortTypeImpl extends AbstractProxy implements ZRCASCS_PortType {
public ZRCASCSResponse_Type zRCASCS(ZRCASCS_Type parameters) throws ZRCASCSException_Message_Exception, SystemFaultException, ApplicationFaultException{
        //throw new RuntimeException();
        Rca_ws a = new Rca_ws();
        return a.zRCASCS(parameters);
Error: XI_Monitor
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Error invoking method zRCASCS of proxy bean $Proxy305: cannot assign instance of com.sap.guid.GUID to field com.sap.aii.proxy.xiruntime.core.MessageSpecifierImpl.guid of type com.sap.guid.IGUID in instance of com.sap.aii.proxy.xiruntime.core.MessageSpecifierImpl: com.sap.aii.proxy.xiruntime.core.XmlInboundException: Error invoking method zRCASCS of proxy bean $Proxy305: cannot assign instance of com.sap.guid.GUID to field com.sap.aii.proxy.xiruntime.core.MessageSpecifierImpl.guid of type com.sap.guid.IGUID in instance of com.sap.aii.proxy.xiruntime.core.MessageSpecifierImpl</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
Error: defaultTrace
#hcp095.intra.csc_XID_19271950#ANGUZMAN#ec20b7f019f611de98340011259e6830#
SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain##
#com.sap.aii.proxy.xiruntime.core.XmlProxyException: Error invoking method zRCASCS of proxy bean $Proxy366:
cannot assign instance of com.sap.guid.GUID to field com.sap.aii.proxy.xiruntime.core.MessageSpecifierImpl.guid
of type com.sap.guid.IGUID in instance of com.sap.aii.proxy.xiruntime.core.MessageSpecifierImpl
     at com.sap.aii.proxy.xiruntime.core.XmlProxyJ2EE.call(XmlProxyJ2EE.java:192)
     at com.sap.aii.proxy.xiruntime.core.XmlProxy$ProxyBeanCaller.call(XmlProxy.java:225)
     at com.sap.aii.proxy.xiruntime.core.XmlProxy.processRequest(XmlProxy.java:194)
     at com.sap.aii.proxy.xiruntime.core.XmlInbound.processRequestMessage(XmlInbound.java:126)
     at com.sap.aii.proxy.xiruntime.core.XmlInbound.processMessage(XmlInbound.java:83)
     at com.sap.aii.proxy.xiruntime.sbeans.JPRBean.onMessage(JPRBean.java:158)
     at com.sap.aii.proxy.xiruntime.sbeans.JPRLocalLocalObjectImpl0_0.onMessage(JPRLocalLocalObjectImpl0_0.java:175)
     at com.sap.aii.af.ra.ms.impl.ServicesImpl.deliver(ServicesImpl.java:276)
     at com.sap.aii.adapter.xi.ms.XIEventHandler.onDeliver(XIEventHandler.java:1049)
     at com.sap.aii.af.ra.ms.impl.core.queue.RequestConsumer.onMessage(RequestConsumer.java:119)
     at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:850)
     at com.sap.aii.af.ra.ms.runtime.MSWorkWrapper.run(MSWorkWrapper.java:56)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(AccessController.java:180)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
If somebody can help me.
Thank you very much

Solved!!!
to assign library references to the project application-j2eeengine.xml
com.sap.aii.proxy.xiruntime
com.sap.aii.messaging.runtime
com.sap.xi.util.misc
com.sap.guid

RFC to Proxy

Hello Experts,
We are converting our all interfaces from RFC to Proxy for better performance...
Just wanted to know that for the Data types that we are going to use in place of RFC, for proxy, do we need to develop it on our own or is there any way that we can directly copy it from RFC?
Thanks and Regards,
Hetal

Hi Hetal
Are you using the Imported RFC?. DT which you used earlier can be exported out. When you create DT click on tag XSD. Then export it.
Use the same XSD imported as external definition for any use.
Imported RFC i think will be exported as WSDL. You can use WSDL also for your use.
Using External definition you dont need DT. Directly create MI with inbound or outbound.
in MM you can use external definition directly
Thanks
Gaurav

RFC and PROXY

Hi all,
i have a standard bapi which is at receiver side,and i neeed to update the data .it is asynchronous.can i use a RFC adapter or should i use proxy here?
Regards,
keerthi

Hi,
There are advantages / disadvantages for RFC / Proxies / Idocs. 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
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
Regards,
Rajani.

Choosing among IDoc, RFC and Proxy

Hi every one,
We have 2 SAP systems, one in the US and other in Kuwait.
The project is in the proof of concept phase. To communicate between the systems, I have a choice to choose among IDoc, RFC and Proxy.
Can someone direct me in this direction.
What are criteria that should be considered in choosing one of the methods of communication.
My other question is that,
there might not be internet facility at the remote location that is in Kuwait. I thought of going for asynch communication...I hope I am right in this.
Please correct me and direct me.
-Naveen.

I guess you should start with the scenarios that you have in hand.
During proof-of-concept stage, you analyze what kind of scenarios that you might encounter in the real-world or during the build stage and choose the technology (RFC/IDoc/Proxy) to prove the end-to-end capability of building an interface.
During the scenario evaluation stage, list out the "out-of-the-box" capabilities of both the SAP systems and come up with a decision tree of when to use RFC, IDoc or Proxies.
Also make sure that you include quality of service and error handling capabilities. In case of IDoc's the error handling capability is all standard and you don't need to build anything from scratch.
I guess these would be some criteria based on which you can evaluate which method to choose from.

In PI 7.1 better performance is reached using RFC or Proxy?

Hello Experts,
As with PI 7.1 which one would be better option to have better performance?
1)Proxy which goes through the Integration Engine by omiting Advance adaptor Engine
2)RFC which goes through the AAE by omiting Integration Engine
As we know there are alot of advantages of Proxies over RFC:
1. Proxy communication always by passes the Adapter Engine and will directly interact with the application system and Integration engine. So it will give us better performance.
2. Proxies communicate with the XI server by means of native SOAP calls over HTTP.
3. Easy to handle messages with ABAP programming if it is ABAP Proxy .
4. Proxy is good for large volumes of data. we can catch and persist the errors ( both system & application fault ) which was generated by Proxy setting.
Thanks in Advance
Rajeev

Hey
More than the performance,its a question of requirement.
There are several restrictions which you need to consider before using AAE.To name a few
IDOC,HHTP adapter wont be available
No support for ABAP mapping
No support for BPM
No support for proxy
No support for Multimapping,content based routing ( in first release)
So if you want to use any of the above you cant use AAE in first place.but performance is significantly improved,upto 4 times better that simple AE-IE
/people/william.li/blog/2008/01/10/advanced-adapter-engine-configuration-in-pi-71
check the above blog and the article mentioned in it.
Now coming to proxy,it supports all the above and performance is not that bad either.
so it all boils down to what your requirements are:)
Thanks
Aamir

RFC o Proxy PI 7.1.1

Hi all,
in previous versions on SAP PI SAP recommends the use of PROXYS than RFC, but what about PI 7.1.1 with AAE and the PI protocol (XI3.0) was added to SOAP Adapter?
How can we decided if choose Proxys than RFC adapter since both run in the AAE and both have the same pipelines?
for example: in this company never use ABAP Proxys,here use Xi 3.0 so i have recommending the use of Proxys, but also a migration to PI 7.1.1 is schedulled. so? how can i deffend the use of proxys now since RFC adapters and XI protocols run in the AAE?
Hope my questions is clear.
Thanks
Rodrigo P-.

The use of PROXY/ RFC/ IDOC is suggested keeping in mind their individual performances in the backend i.e. in the ECC. If i am on track then the use of IDOC/ PROXY/ RFC does not have an issue in SAP XI/ PI....processing an IDOC is heavy on the system or IDOC should not be used for frequent transactions and some similar limitations are valid for ECC.
So even if we are using AAE in SAP PI, the execution will remain the same in ECC.
Regards,
Abhishek.

RFC to proxy scenario

Hi,
Here is scenario...
External non-SAP system invokes RFC from SAP and we want that this goes through PI.
Thinking about approach to have proxy on SAP side and configure RFC (definition is taken from SAP ERP system) sender adapter for other external system?
What are restrictions of this approach or is better to skip PI in this case, what are experiences?
Is there any online guide for this approach?
Regards,
N.

Hi,
http://help.sap.com/saphelp_nwpi71/helpdata/en/5e/3f7440c26ed262e10000000a155106/content.htm
Use this.
Sreeni.

Call to RFC via proxy...

I have a scenario where a Proxy is calling an RFC. My question is will the control return back to XI after the call or does it return after the complete processing of the RFC? Could someone please clarify?

hi siru,
if ur scenario is synch then xi wud call the rfc , the rfc will be executed and only after the execution is complete , xi will receive the result and send to the other system. thus the scenario "waits" for the rfc to execute. further processing in sender application is blocked.
while in asynch the scenario is complete as soon as xi calls the rfc. the applications here are loosely coupled.
if u r using BPM, many simultaneous branches can wrk and send/receive messages acc to the process design.
[reward if helpful]
regards,
latika.

RFC(ABAP Proxy)-------XI-------- FILE Asynch

Hi All,
Good evening.
Please let me clear one thing, the message automatically comes into XI when executing proxy at R/3 side? or we have to send from RWB by using the path
component monitoring-->Proxyruntime----->sendmessage
there we paste the message from SXMB_MONI of R/3?
Please clarify my doubt ASAP.
Thanks & Regards,
Nagarjuna.

Hi
You can test the scenario from SXMB_Moni of R/3.
Or you can call the execute_synchronous method and the whole scenario will work fine.
Please refer below scenarios
File to R/3 via ABAP Proxy
/people/prateek.shah/blog/2005/06/14/file-to-r3-via-abap-proxy - FCC
ABAP Proxy Runtime
http://help.sap.com/saphelp_nw04s/helpdata/en/02/265c3cf311070ae10000000a114084/frameset.htm
Setting Up Point-to-Point Connections with proxy
http://help.sap.com/saphelp_nw04s/helpdata/en/85/78af1bf407434796aaf8dbd6d4e7b7/frameset.htm
Reliable Messaging EOIO in ABAP Proxies
/people/arulraja.ma/blog/2006/08/18/xi-reliable-messaging-150-eoio-in-abap-proxies
/people/stefan.grube/blog/2006/07/28/xi-debug-your-inbound-abap-proxy-implementation
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3dfac358-0d01-0010-5598-d4900e81a30c
Thanks
Swarup

RFC & proxy adapters not working

Hi Gurus,
We have PI 7.31 single stack installed on our company.
Since the last 2 days, we are not able to have a successful communication between PI and ECC on RFC and proxy adapters.
On the previous days, weeks and months there were no issues like this one.
The error that we are getting on the message monitor is next one for our incoming proxy interfaces:
From the Message Details tab:
Status
systemError
Status Details
Receiver delivery: Cannot determine receiver channel (Cannot find the receiver channel)
Error Category
XI_J2EE_ADAPTER_ENGINE
Error Code
CHANNEL_DETERMINATION_FAILED
From the Message Log tab:
29/04/2015 14:56:42.673
Information
Trying to put the message into the send queue
29/04/2015 14:56:44.448
Information
Message successfully put into the queue
29/04/2015 14:56:44.452
Information
The message was successfully retrieved from the send queue
29/04/2015 14:56:44.456
Information
Message status set to DLNG
29/04/2015 14:56:44.496
Information
Message selected to be processed again when the receiver channel is started
29/04/2015 14:56:44.501
Error
Transmitting the message to endpoint <local> using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.RetryControlException: Channel stopped by administrative task.
For OB proxy calls, this is the error that we get in the sxi_monitor on the ERP:
Status Details column: Error Parsing PI Message
Error while calling Integration Server:
com.sap.aii.af.service.administration.api.cpa.CPAChannelStoppedException: Channel stopped by administrative task. at com.sap.aii.af.service.administration.impl.cpa.CommonCPA.checkChannelState(CommonCPA.java:57) at com.sap.aii.af.service.administration.impl.cpa.LookupManagerDelegate.getCPAObject(LookupManagerDelegate.java:86) at com.sap.aii.adapter.soap.web.MessageServlet.doPost(MessageServlet.java:487) at javax.servlet.http.HttpServlet.service(HttpServlet.java:754) at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
Regarding the RFC adapter, this is the error we can see in the CCM:
Error in processing caused by: RfcException: [qlaspi00.xxx|eq610q0]
    message: CPIC-CALL: SAP_CMACCPTP on convId: 00000000
LOCATION    SAP-Gateway on host qlaerp01.xxx / sapgw01
ERROR       registration of tp eq610q0 from host
            qlaspi00.xxx not allowed
TIME        Wed Apr 29 16:20:22 2015
RELEASE     721
COMPONENT   SAP-Gateway
VERSION     2
RC          720
MODULE      gwxxrd.c
LINE        3644
COUNTER     5492
    Return code: RFC_SYS_EXCEPTION(3)
    error group: 102
    key: RFC_ERROR_COMMUNICATION
Exception raised by qlaspi00.xxx|eq610q0
On the SM59 tx in the ERP the test connections are failing for the RFC destinations that we are using on this environment, and these were working in the past.
Also, BASIS team notify us that the programs are registered so they don't know that else to do on their side.
The actions I took were:
CPA full refresh cache
Restart all PI components (done by BASIS team)
Stop and start channels
Inactivate and Activate channels
Please notice that all these processes were working in the past and there were NO modifications on the same.
Where can I continue looking on these errors to find the issue?
Any help will be very appreciated!
Thanks in advanced!
Regards.

Claudio
The error indicates that the channel has been stopped. Did you check the administrative logs in the comm channel monitor to see if someone or an ATP schedule has stopped the channel?
Rgds
Eng Swee

RFC vs Proxy

Similar Messages

Maybe you are looking for