RFC - XI - Java Proxy

Hi all,
I need to configure RFC -> XI -> Java proxy.
While doing so, i am getting below error in SXMB_MONI
HTTP_RESP_STATUS_CODE_NOT_OK
following error occurred while parsing the HTTP request: com.sap.engine.services.httpserver.exceptions.ParseException: Incorrect request line: [POST MessagingSystem/receive/AFW/XI HTTP/1.0].. Exception id:
Can any body please suggest the solution.
Any help will be appriciated.
Regards,
Kulwant

hi
port 50000 is the dedicated java-http port. port 8000 is the ICM-port (Internet Communictaion Manager). The ICM distinguishes with the URL-path whether it has to forward the request to the ABAP-stack or to the Java stack.
ICM port for Java server like http://hostname:80nn/index.html.
For the J2EE Engine, 20 ports are available for the dispatcher element and 80 are available for the server elements, since five is the maximum number of ports for a server process. Therefore, no more than 16 server cluster elements can be created on one instance.
The default J2EE Engine ports meet the following requirements:
● The port value is a number over 50000
● For each cluster element the ports begin with 50000+100*instance_number, where instance_number is a two digit number from 00 to 99 specifying the number of central instance and dialog instances.
You can see the instance number from the directory, where the J2EE Engine is installed. Under /usr/sap/<SID>, there is a directory which name contains the instance name including the instance number, for example, JC40 (where 40 is the instance number).
○ For dispatcher cluster elements
The ports are created from 50000100*instance_numberport_index, where port_index is a number from 0 to 19 inclusive.
check the below link for
J2EE Engine Dispatcher Ports
http://help.sap.com/saphelp_nw04s/helpdata/en/a2/f9d7fed2adc340ab462ae159d19509/frameset.htm
reward points if helpfull
regards
kummari

Similar Messages

RFC - XI - Java Proxy HTTP_RESP_STATUS_CODE_NOT_OK

Hi all,
I need to work on RFC->XI-> Java proxy.
While excuting, i am getting an error :
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
<SAP:P1>400</SAP:P1>
<SAP:P2>Bad Request</SAP:P2>
Can any body please guide?
Regards,
Kulwant

Hi Kulwanth,
Plz do check the mentioned possibilities for your error one by one:
1.Did you maintain Client, userid, password, and lang information in SICF transaction -> sap/xi/engine? Double click on service and check whether you have entered correct information.
2.Then you might check the roles of the XIISUSER in SU01. In some case there are some double roles, i.e., two times the role SAP_XI_IS_SERV_USER assigned. One might have the date of the last update, the other one might have apparently the older version. Delete the older roles manually and the error should disappear.
3.to send messages to xi you need a service id / pwd which is specific to your landscape usually its xiappluser. Contact your basis group for password.
4.
Activated all services on the r3 system.
Create HTTP connection to XI from r3
sm59-> http connetons to r3
let us say you have created a HTTP connection in the integrationserver_XI, make sure in its settings the prefix path is set to /sap/xi/engine?type=entry. Also check its log on credentials, you can use xiappluser.
IN Integration builder, receiver communication channel make sure you have entered proper
host service number
path = /sap/xi/enigne?type = receiver.
5. It might also be that you have authorization problems with your XISUPER. In the visual administrator and in ABAP SU01, make your XISUPER has all the necessary(SAP_SLD* and SAP_XI*) roles assigned to it. If not, try to assign these and see if this can be of any help.
6. can you also try the following;
Visual Admin -> start the service,
"com.sap.aii.af.ms.app".
Please go through the followings links also :
http://help.sap.com/saphelp_nw04/helpdata/en/82/f4993c03e0cd37e10000000a11405a/content.htm
The specified item was not found.
http://help.sap.com/saphelp_nw04/helpdata/en/39/83682615cd4f8197d0612529f2165f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/39/83682615cd4f8197d0612529f2165f/frameset.htm
I hope the info provided help you solve your error.
Regards,
Vinod.

Java Proxy stuck in JPRRqst Queue

Hi,
I try to do Synchronous process between RFC to Java Proxy. it was wokrikg fine but suddenly Messages stuck in queue.
RFC sends a message after mapping. I looked sxmb_moni it looks like message delivered to Java Proxy but it didn't. after a while outbound service interface gives "no response" error because of time out. but when i look at http://*****:50000/mdt/Systatus proxy messages stuck in JPRRqst Queue
Queue Name Threads Assigned/Working
JPRRqst 11/11
My proxy didn't even start. Strange thing this process did work fine and when this error happens, I receive different data from data that come from RFC. example
RFC sends
MANDT 001
MATNR 3N5979
SERVICE_ID 16261
But i receive
<?xml version="1.0" encoding="UTF-8"?>
<ns0:Z************ xmlns:ns0="urn:sap-com:document:sap:rfc:functions">
 <I_TPARTAV>
 <MANDT>000</MANDT>
 <MATNR>979</MATNR>
 <SERVICE_ID>0000</SERVICE_ID>
Have you any ideas?

try this - in RWB in msg monitoring at AE level see the msgs for this scenario......try to find first msg in error and cancel it...then see whether ur remaining msgs are getting processed or not........

RFC lookup with java proxy class, how do I use "fromXml()"?

Hi,
I'm trying to do an RFC lookup in XI using java proxy classes (SAP Enterprise Connector).
The XMLPayload comes from a java proxy class which has been converted to xml using a method called
.fromXml() for this. I just don't know how to use and I can't find any documentation for it.
Would very much appreciate if someone could provide me with an example of how to use this class
Best Regards
Olof Trönnberg

http://xstream.codehaus.org/javadoc/com/thoughtworks/xstream/XStreamer.html#fromXML(com.thoughtworks.xstream.io.HierarchicalStreamDriver,%20java.io.Reader)

Java Proxy - XI - RFC Synchronous Scenario OUTBINDING Problem.

Java Proxy -> XI -> RFC Synchronous Scenario. Problem
Hi,
 I'm doing a Java Proxy -> XI -> RFC Syncronous Scenario.
 A Java Server Socket is running as a Demon. When a client make a request to the Java Server Socket, this one call Java Proxy Client and set up the parameters.
 The first time that execute the scenario it works perfectly but no the next one and so on.
 The error when I check the monitor (TCODE: SXMB_MONI) is in PLSRV_OUTBOUND_BINDING.
<Trace level="1" type="B" name="CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV">
<Trace level="1" type="T">no outbound binding found.</Trace>
<Trace level="1" type="T">No standard agreement found for , DES210_DEV, , JPX_DEV, urn:servipago:SERVIPAGO_SAP_02, mi_os_t1</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
And it has sense, because my scenario doesn't begin with the execution of FM (RFC).
A Hint, my services in the first try are:
 Sender Service: JPX_DEV (Java Proxy Client)
 Receiver Service: DES210_DEV (R/3 4.6C)
But the second try and so on the services that I saw in the monitor are:
 Sender Service: DES210_DEV (R/3 4.6C)
 Receiver Service: JPX_DEV (Java Proxy Client)
I can't understand why they swich each other.
Any idea?

Hi,
Outbound binding problem is because of Reciever Determination/Agreement is not activated or refreshed correctly.
Try to recreate or refresh and activate it. Then check it.
also do the cache refresh in SXI_CACHE.
Also in go to Integration Builder(XI home page)->Administration->Cache Overview and do all the cache refresh.
Hope this helps
Regards,
Moorthy

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

Java Proxy and ABAP Proxy

hi,
can any one send me some documents on Java Proxy and ABBAP Proxy
regards,
John

hi,
Proxies are nothing but a mechanism to shift the application logic from the XI server onto the sender or reciever system so as to reduce the effort on the side of XI.Depending upon where the proxies are generated ,it is differentiated as client proxy ( sender ) and server proxy ( receiver ) .In R3 system having WAS 6.2 and above its already has an inbuilt small IE so the proxy generation is favoured and possilbe,for more on this please go thru the following links
Proxies: are interfaces which will get executed in the application system. They can be created only in the system from message interfaces using the proxy generation functions.
The biggest advantage of the proxy is that it always by passes the Adapter Engine and will directly interact with the application system and Integration engine - so it will and should give us a better performance.
The literal definition of a proxy is an object / process authorized to act for another; an agent or a substitute. In simpler terms, proxies in the XI context are objects used to encapsulate the creation (from a sender system) or parsing of XML (at a receiver system) as well as the communication with the relevant runtime components required to send or receive those messages. The Proxy Runtime controls these objects / processes, and can itself be controlled by the applications it communicates with.
The Proxy currently has the following components available:
1. ABAP Proxy Communication using XI or Web Services
2. Java Proxy Communication using XI (J2EE)
For further reference, visit the following sites,
To test a connection - /people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
Client Proxy - /people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
Server Proxy - /people/siva.maranani/blog/2005/04/03/abap-server-proxies
Testing proxy - /people/stefan.grube/blog/2006/07/28/xi-debug-your-inbound-abap-proxy-implementation
JAVA Proxies:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a068cf2f-0401-0010-2aa9-f5ae4b2096f9
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f272165e-0401-0010-b4a1-e7eb8903501d
ABAP Proxies:
/people/sap.user72/blog/2005/12/13/integration-builders-through-proxy-server-part--2
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
/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
/people/michal.krawczyk2/blog/2006/04/19/xi-rfc-or-abap-proxy-abap-proxies-with-attachments
/people/sukumar.natarajan/blog/2007/01/07/how-to-raise-alerts-from-abap-proxy
/people/sravya.talanki2/blog/2006/07/28/smarter-approach-for-coding-abap-proxies
ON SDN TV
https://www.sdn.sap.com/irj/sdn/advancedsearch?query=abap%20proxy%20xi&cat=sdn_all&start=11#

XI 2.0 Java Proxy error

Hi All,
I am receiving the following error:
RFC_ADAPTER.JCO_RUNTIME_EXCEPTION:System error when calling the outbound RFC adapter (cannot deserialize JCo request from XML)
The message I'm sending is synchronous coming from a Java Webapp and requesting infomation from R/3.
There are two pieces to the interface I have created. The first is calling a function which validates a few fields then returns 'return codes'. The second will create a sales order and return a few numbers. They are built into the same interface and use message splitting based on an input field. The verification piece is working which tells me that this is not a problem with the actual RFC adapter but when I run the 'create sales order' function I receive the aforementioned error.
n e thoughts?

Hi Stefan, thx for the reply.
I am running the latest version of the function. I do have one date field in the RFC structure, the rest are strings. The data going into that date field is being mapped from a string field in the sent message. This shouldn't be a problem (I don't believe) I have done this in many other interfaces.
I noticed that in my xi monitor (SXMB_MONI) under the column labeled 'Outbound' the acronym 'RFC' shows up for my failing message. When I send a message through the other java proxy interface that works I get nothing in the column. I'm not sure if this means n e thing but I thought I would through that in.
I've also set up my scenario changing from synchronous to asynchronous and using the file adapter and it seems to make it through, minus the error on the return message.
.. I forgot to mention that there have not been any changes to the RFC adapter configuration. ... and I have restarted it to see if that would make a difference. It did not.
n e other ideas?
Message was edited by: Larry Chaput

Error in scenario for client Java Proxy

2006-04-28 15:30:49 Success Java proxy runtime (JPR) is transferring the request message to the messaging System
2006-04-28 15:30:49 Success Application attempting to send an XI message synchronously using connection JPR.
2006-04-28 15:30:49 Success Trying to put the message into the call queue.
2006-04-28 15:30:49 Success Message successfully put into the queue.
2006-04-28 15:30:49 Success The message was successfully retrieved from the call queue.
2006-04-28 15:30:49 Success The message status set to DLNG.
2006-04-28 15:30:50 Error Received XI System Error. ErrorCode: NO_RECEIVER_CASE_BE ErrorText: ErrorStack: No receiver could be determined
2006-04-28 15:30:50 Error Returning synchronous error notification to calling application: XIServer:NO_RECEIVER_CASE_BE:.
2006-04-28 15:30:50 Error Transmitting the message using connection http://<SERVER>:<PORT>/sap/xi/engine?type=entry failed, due to: XIServer:NO_RECEIVER_CASE_BE:.
2006-04-28 15:30:50 Error The message status set to FAIL.
2006-04-28 15:30:50 Error Returning to application. Exception: XIServer:NO_RECEIVER_CASE_BE:
2006-04-28 15:30:50 Error JPR failed to transfer the request message to the messaging system. Reason: XIServer:NO_RECEIVER_CASE_BE:
I am getting this in the audit log for a Java Proxy <> XI <> RFC scenario. What could be the problem?
the configuration in integration directory seems to be perfectly fine however the message flow fails giving this error NO_RECEIVER_CASE_BE
Regards,
Amol

HI Amol,
Did you check the Message type/Message Inetrface names in the Java Proxy ?
Also check for Receiever Determinations in the configuration.
I assume that , you have created the Communication Channel under the Business System created as Standalone Java System.. If not check this.
Go to SXI_CACHE and check for the Receiever Determination created in the Configuration...
Hope this helps,
regards,
Moorthy

Problem in JAVA proxy scenario: cannot locate QSI root directory

Hi Frnds,
i am using RFC to JavaProxy, actually through java proxy we are connecting to the bank for payment.
And the bank has provided one payment client application which needs to be installed on the server for interacting with the bank,
and we had installed the payment client on to the server. But we are getting following type of error in the response,
SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Error invoking method egateJavaMsgIntInOutJava of proxy bean $Proxy258: cannot locate QSI root directory: com.sap.aii.proxy.xiruntime.core.XmlInboundException: Error invoking method egateJavaMsgIntInOutJava of proxy bean $Proxy258: cannot locate QSI root directory</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
What could be the possible solution in order to solve this error.
Thanks,
Raj
Edited by: RajSrivastava on Jul 8, 2009 11:03 AM

Hi Madhav,
Please check the following links regarding to u rproblem.
Java Proxy Server: cannot locate proxy bean...
Cannot locate proxy bean IN RWB
https://forums.sdn.sap.com/click.jspa?searchID=11113489&messageID=3039952
warm regards
mahesh.

RFC _XI _Java Proxy. Help needed

Hi
I am executing a scenario rfc_xi_java proxy.
I am getting the error in SXMB_MONI of xi server in call adapter step.
+ <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
<Trace level="1" type="System_Error">HTTP-client: error response= java.lang.NullPointerException at com.sap.aii.adapter.xi.ms.XIMessage.getMessageId(XIMessage.java:2631) at com.sap.aii.adapter.xi.ms.XIEventHandler.onRequest(XIEventHandler.java:761) at com.sap.aii.af.ra.ms.impl.ServerConnectionImpl.request(ServerConnectionImpl.java:146) at com.sap.aii.af.ra.ms.impl.core.transport.http.MessagingServlet.doPost(MessagingServlet.java:308) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160)</Trace>
</Trace>
<Trace level="1" type="T">Sender scheme external =</Trace>
<Trace level="1" type="T">Sender agency external =</Trace>
<Trace level="1" type="T">Sender party external =</Trace>
<Trace level="1" type="T">Sender party normalized =</Trace>
<Trace level="1" type="T">Party normalization: receiver</Trace>
<Trace level="1" type="T">Receiver scheme external =</Trace>
<Trace level="1" type="T">Receiver agency external =</Trace>
<Trace level="1" type="T">Receiver party external =</Trace>
<Trace level="1" type="T">Receiver party normalized =</Trace>
<Trace level="1" type="T">Sender: Header before undo of mapping</Trace>
<Trace level="1" type="T">Party =</Trace>
<Trace level="1" type="T">Agency =</Trace>
<Trace level="1" type="T">Scheme =</Trace>
<Trace level="1" type="T">Service = GYD_100</Trace>
<Trace level="1" type="T">Receiver: Header before undo of mapping</Trace>
<Trace level="1" type="T">Party =</Trace>
<Trace level="1" type="T">Agency =</Trace>
<Trace level="1" type="T">Scheme =</Trace>
<Trace level="1" type="T">Service = JRACF</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
</SAP:Trace>
I have followed all the steps from SAP HOW to Java proxy.
1.In Java proxy I am creating a responce object and putting some values and returning it. No thing more than that.
2. I could be able to see message sent from r/3 in XI server.
3. I have tested the rfc destination in r/3 server
4. Programme id in rfc dist is maching with the programe id in the communication channel.
Any help is greatly appreciated
Thank you
Monika Dietz
Message was edited by: Monika Dietz

Hi
check these links
java Proxy Objects Developing Message Interfaces :
http://feedfury.com/content/14188168-java_proxy_objects_developing_message_interfaces.html
Java Proxy Objects Tables Developing Message Interfaces:
http://feedfury.com/content/14188167-java_proxy_objects_tables_developing_message_interfaces.html
Java Proxy Objects Enumerations Developing Message Interfaces :
http://feedfury.com/content/14188166-java_proxy_objects_enumerations_developing_message_interfaces.html
work with java proxies- xi 3.0
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/7d4db211-0d01-0010-1e8e-9b07fc2113ab
Regards,
Suryanarayana

Java Proxy Code Sample

Hello SAP community. Does anyone have a step-by-step code sample for creating either a jsp or web dynpro application in Netweaver to use a java proxy to connect to XI that will calls a RFC or BAPI in SAP R3?

Hi
See the Code sample and pdf help it the SDN samples and tutorials
https://www.sdn.sap.com/irj/sdn/downloaditem?rid=/library/uuid/f0b0e990-0201-0010-cc96-d7ecd2e51715
https://www.sdn.sap.com/irj/sdn/developerareas/webdynpro?rid=/library/uuid/49f2ea90-0201-0010-ce8e-de18b94aee2d
Kind Regards
Mukesh

Best Scenarios when to use IDOC Adapter, RFC Adapter and Proxy

Please provide me links/weblogs which demonstrate the full scenario that when to use IDOC Adapter, RFC Adapter and Proxy when working with sender R/3 system.
Regards
Rachit

Hi abhinash,
Check these links for java proxy
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/a068cf2f-0401-0010-2aa9-f5ae4b2096f9
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f272165e-0401-0010-b4a1-e7eb8903501d
for ABAP Proxy ...
/people/siva.maranani/blog/2005/04/03/abap-server-proxies
/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
/people/prateek.shah/blog/2005/06/14/file-to-r3-via-abap-proxy
http://help.sap.com/saphelp_nw2004s/helpdata/en/48/d5a1fe5f317a4e8e35801ed2c88246/frameset.htm
for RFC .....
RFC-xi-SOAP Scenario
How to send RFC response message back to XI File/FTP adapter?
https://weblogs.sdn.sap.com/pub/wlg/3865//Troubleshooting [original link is broken] [original link is broken] [original link is broken] [original link is broken]
/people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1
Hope you will find them useful ..
Regards
Abhi

RFC VS Abap Proxy

Quest point where the RFC is better the AbapPorxy than?
In me to inform

Hi ChangSoo
1. The biggest advantage of the proxy is that it always by passes the Adapter Engine and will directly interact with the application system and Integration engine - so it will and should give us a better performance.
2. 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.
3. ABAP proxies supports two different protocols; XI and Web Services
4. Most important is that they can be used for both synchronous and asynchronous communication .
RFC/BAPI is basically only intended for Synchronous comm. which asks much more system resources from your XI system.
5. Proxies are used when you have large chunks of data coming in and that too if its unstructured, so if it comes from a SAP system we go for a ABAP proxy, if its from a non sap system, we take a java proxy.
For abap proxy we may use a report to send a proxy data to sap xi.
6. EOIO quality of service can be obtained with Proxies and not with RFC/BAPI.
RFC/BAPI support BE( Best Effort ) when used synchronously.
Cheers...
Vasu
** REward Points if found useful **

Communication between SOAP and java proxy does not work

Hi Group,
i want to proceed following scenario:
SOAP->XI->JavaProxy
For that i have created of the message interface of a remote function module my java proxy.
Calling the java proxy with following scenario works successfully:
RFC->XI->JavaProxy
Further, i have created in the integration engine(configuration) my wsdl file. In the SAP
Netwaever Developer Studio, i have made a standalone proxy project, that is consuming the
web service out of the wsdl file.
Testing the web service client with following example works fine:
SOAP->XI->RFC
But when i try the scenario SOAP->XI->JavaProxy, i get following rmi exception on client side:
java.rmi.RemoteException: Service call exception; nested exception is:
java.lang.Exception: Element 'Z_GPS_PING.Response' not found in response message.
at com.demo.sap.MI_WEBSRV_GPS_PING_OUTBBindingStub.MI_WEBSRV_GPS_PING_OUTB(MI_WEBSRV_GPS_PING_OUTBBindingStub.java:86)
at com.demo.test.TT_Pinger.main(TT_Pinger.java:36)
Caused by: java.lang.Exception: Element 'Z_GPS_PING.Response' not found in response message.
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.getResponseDocument(MimeHttpBinding.java:942)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1231)
at com.demo.sap.MI_WEBSRV_GPS_PING_OUTBBindingStub.MI_WEBSRV_GPS_PING_OUTB(MI_WEBSRV_GPS_PING_OUTBBindingStub.java:79)
... 1 more
In the monitoring, the execution of both directions is ok. In the response message, i can see the result of the java proxy.
Here is the result:
<ns:Z_GPS_PING.Response xmlns:ns="urn:sap-com:document:sap:rfc:functions">
<E_RETURNCODE>PINGOK </E_RETURNCODE>
</ns:Z_GPS_PING.Response>
My first thought, was, that i have a problem with the prefix, so i have changed it via xslt transformation into "rfc",
but it got the same error message.
Does anyone know, which problem we have here?
For any hint or suggestion, i would be much obliged.
Greetings,
Sigi
P.S. WAS and Sap Netweave Dev Studio is on patch level 12

Hi Group,
the SAP has solved the Problem now.
The coresponding OSS note is: 862926
(release date 18.07.05)
The reason was, that the response payload name wasn't
"maindocument". For that, the adapter didn't found the payload and returned an emty one.
Greetings,
Sigi

RFC - XI - Java Proxy

Similar Messages

Maybe you are looking for