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.

Similar Messages

Problem in JAVA PROXY

hi all,
i am working on java proxy, after writing the code in the NWDS,
iam getting below error
Error :The project was not built since its classpath is incomplete. Cannot find the class file for com.sap.aii.utilxi.misc.api.BaseException. Fix the classpath then try rebuilding this project.
can any one tell me the solution
thanks & regards,
Madhav

Classpath Configuration
Configure your CLASSPATH for the SDK by adding the SDK's libraries. These are located in the /lib/ folder in the folder in which you have unpackaged the SDK. This folder contains all the libraries required by the SDK for development.
Note: If you are using NetWeaver Developer Studio, this step occurs automatically when you create a project. See below for details.
Eclipse / NetWeaver Developer Studio Configuration
To create a project with the SDK in Eclipse or SAP NetWeaver Developer Studio:
In Eclipse or NetWeaver Developer Studio, select File --> New --> Project.
In the New Project Wizard, select Java, and click Next.
In the Project name field, enter a name for your project.
In the Project contents section, deselect the Use default checkbox.
Click Browse and navigate to the folder in which you unzipped the BI Java SDK. Select it, and click OK.
Click Finish at the bottom of the Wizard dialog box.
http://help.sap.com/javadocs/NW04S/current/bi/installation.html
Ps: If helful please reward points

Problem with Java Proxy and Socket Connection

Hi Gurus!!
I have developed a Java Proxy that connects via socket with a Server Socket application. This Server Socket application accepts more than one connection at the same time.
When I connect the first time from my Java Proxy, the connection is correctly established. When the first connection opened, if a try a second connection, this is not established.
I use "new Socket(SocketServer,SocketPort);" to open the connection.
I think that all time the Java Proxy is trying to open the same connection, and this is a problem.
Is there a way to indicate to the server that is a new connection and that the existing connections remain?
Anybody could help me, please?
Thanks and regards,
Manuel Míguez.

Sorry!!!!i must give you more information.
The error which i have when i push the submit button is
HTTP Status 404 -
type Status report
message
descriptionThe requested resource () is not available.
GlassFish Server Open Source Edition 3.0.1
My thought is that the error is in this line
String connectionURL = "jdbc:mysql://localhost/mybooking";in mysql when i write this code then the table opens with no problems:
mysql>show databases;
mysql>usebooking;
mysql>showtables;
mysql>describe booking;Furthermore i have added in my web application the library mysql JDBC driver my-sql-connector-java-5.1.6.bin.jar
Edited by: 813355 on Nov 22, 2010 1:50 AM
Edited by: 813355 on Nov 22, 2010 2:00 AM

Problem EJB - Java Proxy XI

Hi,
I have created a receiver java proxy asynchronous interface. The Message Interface inbound is a Idoc.
I have used the How to Work with XI 3.0 Java Proxies
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/7d4db211-0d01-0010-1e8e-9b07fc2113ab
The sender and receiver message I dont problem, all is correct. But when execute the EJB it leaves east problem to me:
#com.sap.engine.services.ejb#sap.com/com.sap.xi.proxyserver
#com.sap.engine.services.ejb#J2EE_GUEST
#0#SAP J2EE Engine JTA Transaction : [0ffffff81ffffffebffffff9200bffffffb4]
#simonxid_SXD_8514450#XIAPPLUSER
#cd25eae0830d11dc89690016350b5872
#SAPEngine_Application_Thread[impl:3]_21
##0#0#Error##Java###
[EXCEPTION]
#1#com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method onMessage. The transaction is marked for rollback.
     at com.sap.aii.proxy.xiruntime.sbeans.JPRLocalLocalObjectImpl0.onMessage(JPRLocalLocalObjectImpl0.java:196)
     at com.sap.aii.af.ra.ms.impl.ServicesImpl.deliver(ServicesImpl.java:253)
     at com.sap.aii.adapter.xi.ms.XIEventHandler.onDeliver(XIEventHandler.java:1041)
     at com.sap.aii.af.ra.ms.impl.core.queue.ReceiveConsumer.invokeHandler(ReceiveConsumer.java:383)
     at com.sap.aii.af.ra.ms.impl.core.queue.ReceiveConsumer.onMessage(ReceiveConsumer.java:100)
     at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:795)
     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)
Caused by: java.lang.NoClassDefFoundError: Lcom/sap/aii/af/service/trace/Trace;
     at java.lang.Class.getDeclaredFields0(Native Method)
     at java.lang.Class.privateGetDeclaredFields(Class.java:1522)
     at java.lang.Class.getDeclaredField(Class.java:1214)
     at java.io.ObjectStreamClass.getDeclaredSUID(ObjectStreamClass.java:1474)
     at java.io.ObjectStreamClass.access$400(ObjectStreamClass.java:47)
     at java.io.ObjectStreamClass$3.run(ObjectStreamClass.java:335)
     at java.security.AccessController.doPrivileged(Native Method)
     at java.io.ObjectStreamClass.<init>(ObjectStreamClass.java:333)
     at java.io.ObjectStreamClass.lookup(ObjectStreamClass.java:253)
     at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:453)
     at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1521)
     at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1435)
     at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1626)
     at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)
     at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1845)
     at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1769)
     at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1646)
     at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)
     at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1603)
     at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1271)
     at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1845)
     at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1769)
     at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1646)
     at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)
     at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1845)
     at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1769)
     at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1646)
     at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)
     at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1845)
     at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1769)
     at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1646)
     at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)
     at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1603)
     at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1271)
     at java.io.ObjectInputStream.readObject(ObjectInputStream.java:324)
     at com.sap.engine.services.rmi_p4.reflect.LocalInvocationHandler.replicateParameters(LocalInvocationHandler.java:96)
     at com.sap.engine.services.rmi_p4.reflect.LocalInvocationHandler.invokeInternal(LocalInvocationHandler.java:70)
     at com.sap.engine.services.rmi_p4.reflect.AbstractInvocationHandler.invoke(AbstractInvocationHandler.java:53)
     at $Proxy209.invokeMethod(Unknown Source)
     at sun.reflect.GeneratedMethodAccessor420.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187)
     at $Proxy210.invokeMethod(Unknown Source)
     at com.sap.aii.proxy.xiruntime.core.XmlProxyJ2EE.call(XmlProxyJ2EE.java:169)
     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.onMessage(JPRLocalLocalObjectImpl0.java:179)
     ... 9 more
#1.5#0016350B5872005C000003A600000F7000043D52C5C56E9D#1193325621546#com.sap.aii.af.ra.ms.impl.core.queue.ReceiveConsumer#sap.com/com.sap.aii.af.ms.app#com.sap.aii.af.ra.ms.impl.core.queue.ReceiveConsumer.invokeHandler(QueueMessage, MessageController, Services)#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [0ffffff81ffffffebffffff9200bffffffb4]#simonxid_SXD_8514450#XIAPPLUSER#cd25eae0830d11dc89690016350b5872#SAPEngine_Application_Thread[impl:3]_21##0#0#Error##Java###Rolling back transaction for message due to: #2#ccac4e10-830d-11dc-825f-0016350b5872(INBOUND)#<null>#
#1.5#0016350B5872005C000003A700000F7000043D52C5C56F5C#1193325621546#com.sap.aii.af.ra.ms.impl.core.queue.ReceiveConsumer#sap.com/com.sap.aii.af.ms.app#com.sap.aii.af.ra.ms.impl.core.queue.ReceiveConsumer.invokeHandler(QueueMessage, MessageController, Services)#J2EE_GUEST#0##simonxid_SXD_8514450#XIAPPLUSER#cd25eae0830d11dc89690016350b5872#SAPEngine_Application_Thread[impl:3]_21##0#0#Error##Java###Transaction rolled back for meesage due to: #2#ccac4e10-830d-11dc-825f-0016350b5872(INBOUND)#<null>#
The system 6.40 SP14
Thanks
T.Guzman

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

Problem in syn proxy scenario.

Hello All,
My SAP xi system verion 3.0 and service pack 19 and R/3 system WAS6.2
the proxy connection between this two system is not there so we applied the addon( APPINT 200_620 ) on the R/3 system for the connection.
now the connection established and while testing the interface following error getting in response message.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="PERSIST">MSGGUID_EXISTING</SAP:Code>
<SAP:P1>E38274809B0A11DFBDEC8E67ACBB6402</SAP:P1>
<SAP:P2>CENTRAL</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Message ID E38274809B0A11DFBDEC8E67ACBB6402 for pipeline CENTRAL, version , already exists in system</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
i searched and got one SAP note1272854, according to the note i applied the correction , but still facing the same issue.
Please advice what need to be done.
Thanks and Regards,
Chinna
Edited by: chinnasapxi on Jul 29, 2010 2:27 PM
Edited by: chinnasapxi on Jul 29, 2010 3:40 PM

Corrected the URL given in the RFC destination

I downloaded a 1.2GB file in Aptosid linux with Firefox and cannot locate the 'Download' directory where the file went by default - please show location, ta

Where is the default ' Downloads ' location?
I have downloaded a 1.2GB file and it shows in the Downloads window, but I am unable to locate it in the filesystem.
I forgot to make a Downloads directory in my home directory first, and have since made one.
Thanks
Denis

If you can find the downloads window (Keyboard shortcut Ctlr+Shift+Y in Linux) right clicking on the file entry should give an option to open the folder it is in.
If the option is greyed out it was probably only put in a temporary location and may have been deleted. You could try searching by name and date & size.
You may be interested in
* [[What to do if you can't download or save files]]
Note you could have looked at the prefs to try to figure out the location that would have been used, but not once you have reset it.
Does your distro not provide the newest releases of Firefox, you appear to be on Iceweasel 9, the standard Release of Firefox is now fx14.

Java Proxy Runtime: failure to locate proxy bean on inbound call

Hello gurus of the SDN,
I have been trying to get an inbound Java Proxy scenario to work in XI 3.0 but have not been able to get the JPR to recognize my generated and deployed java code. My scenario is set up to call the java proxies generated from a message interface based on the MATMAS Idoc. I successfully deployed the generated java proxies on the same host box as is running the XI instance. The objects are named as follows
Message interface on XI = Inbound_MATMAS04
Generated proxy bean = Inbound_MATMAS04_PortTypeBean
Implementing class = InboundMATMAS04_PortTypeImpl
Implementing method = inboundMATMAS04
I used the JPR transport servlet to register the interface and implementing class but am not sure if I did this correctly. I used the following entry in my web browser:
http://nadcp786:50000/ProxyServer/register?
ns=urn:xiTrainingLabs:groupXX:SAP&
interface=InboundMATMAS04&
bean=InboundMATMAS04_PortTypeImpl&
method=inboundMATMAS04
I also tried using the localejb/ prefix for the bean name in the above step since the code is co-located. When I trigger the scenario, the Idoc info is passed into XI and the Java Proxy Runtime is called, but I get the following error response back in the SOAP header:
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="PARSING">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Cannot locate proxy bean InboundMATMAS04_PortTypeImpl: com.sap.aii.proxy.xiruntime.core.XmlInboundException: Cannot locate proxy bean InboundMATMAS04_PortTypeImpl</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Finally, appended at the end of this post is the audit log of the messaging system showing that the JPR is called but without being able to locate the bean. I think I am missing a configuration step somewhere, but cant figure out what it is!! Can anyone help me?
Many thanks in advance.
Regards,
Nick Simon
Time Stamp     Status     Description
2004-10-25 19:47:32     Success     The message was successfully received by the messaging system. Profile: XI URL: http://nadcp786.bcsdc.lexington.ibm.com:50000/MessagingSystem/receive/JPR/XI
2004-10-25 19:47:32     Success     Using connection JPR. Trying to put the message into the receive queue.
2004-10-25 19:47:32     Success     The message was successfully retrieved from the receive queue.
2004-10-25 19:47:32     Success     The message status set to DLNG.
2004-10-25 19:47:32     Success     Java proxy runtime (JPR) accepted the message
2004-10-25 19:47:34     Error     JPR could not process the message. Reason: Cannot locate proxy bean localejbs/InboundMATMAS04_PortTypeImpl
2004-10-25 19:47:34     Error     Delivery of the message to the application using connection JPR failed, due to: Cannot locate proxy bean localejbs/InboundMATMAS04_PortTypeImpl.
2004-10-25 19:47:34     Error     The message status set to FAIL.
2004-10-25 19:47:34     Error     Asynchronous error detected: Cannot locate proxy bean localejbs/InboundMATMAS04_PortTypeImpl. Trying to report it.
2004-10-25 19:47:34     Error     Asynchronous error reported.
Message was edited by: Nicholas Simon

Hi
How do you determine the JNDI naming of the a EJB?
I have following entry in JNDI directory in the root
Object Name FlightQueryIn
Class Name javax.naming.Reference
Context Name
Object Value Reference Class Name:
Type: clientAppName
Content: sap.com/JavaProxyEAR
Type: interfaceType
Content: remote
Type: home
Content: com.sap.aii.proxy.xiruntime.core.AbstractProxyInboundHome4
Type: ejb-link
Content: FlightSeatAvailabilityQueryIn_PortTypeBean
Type: jndi-name
Content: FlightQueryIn
Type: remote
Content: com.sap.aii.proxy.xiruntime.core.AbstractProxyInboundRemote4
I tried to register the bean with JPR using:
http://ctsapxid01:50100/ProxyServer/register?ns=http://sap.com/xi/XI/Demo/Airline&interface=FlightSeatAvailabilityQuery_In&bean=FlightQueryIn&method=flightSeatAvailabilityQueryIn
I followed the following blog
http://wiki.sdn.sap.com/wiki/display/Java/JavaProxyChangesinPI7.1fromPI7.0
Thanks,
Chris

Proxy Scenario (abap client)- XI, ICM_CONNECTION_FAILED

Hi Forum,
I have a problem with a Proxy Scenario (ABAP client proxy),
My scenario is R/3 (abap client proxy)--->XI ,
the client proxy while sending message to XI throws an error, which is seen in SXMB_MONI as:
404 Resource not found
Partner not reached
Error: -20
Version: 6040
Component: ICM
Date/Time: Fri Jan 25 09:20:54 2008
Module: icxxconn_mt.c
Line: 2124
Server: xxxap5_RP1_05
Detail: Connection request from (143/22024/0) to host: xxXP1.xxx.com, service: 8000 failed (NIEHOST_UNKNOWN) AP-T143, U22024, 500 xxUSER, , 09:20:54, M0, W0, , 1/0
I can see a stuck entry (LUW), for this in SMQ2, even on several re-execution of that LUW in SMQ2, it gives an error:
SYSFAIL
XI Error Client_Receive_Filaed

Hi
404 Resource not found
There might be the problem with the server having not to find anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
*Possible Tips:- *
404 is an HTTP response code that indicates that the resource in question couldn't be found. Usually this is due to an incorrect URL, so it is better to cross check all URLs. Check pipeline URL in the SLD in the business system of the Integration Server For this go to SLD->Business System-><yourIntegrtaion Server>->Pipeline URL: It should be like this http://<host>:<port>/sap/xi/engine?type=entry Where host is the host name of the Integration Server and port is the HTTP(8xxx) port. To verify this in Integration Server you can do like this. Go to SXMB_ADM->Integration Engine Configuration->Choose Edit from Menu -> Change Global Configuration Data to switch to change mode. Then select System Landscape - Load Configuration. (This is not required always)
Check that the port really is the ICM HTTP Port and not the J2EE port i.e SMICM then menu GOTO --> SERVICES and check the port number for HTTP. It should be HTTP port
If the error is Page cannot be displayed, cannot find server in https configurations Check and correct the SSL configuration for the ABAP and the J2EE side of the system
If the error is because of integration server when using Proxy communications then check these. i.e SXMB_ADM->Integration Engine Configuration->Corresponding Integration Server enrty should be dest://<Http Integration server-Destination> Where < Http Integration server -Destination > is the RFC destination (SM59) of type HTTP connection (type H) to the Integration Server. In this case, host name, port, and path prefix are saved in the RFC destination
Refer below link
/people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi
Thanks
Swarup

Problem with java and pogo games

i use mozilla and now with the problems with java and hackers cannot play my pogo games,what can i do? i disabled my java i tried java 6 doesnt work or is not safe,what is a safe way to play games on pogo that use java?

Oracle has released a Java 7 Update 11 to address security vulnerabilities and you should update to that version.
*https://support.mozilla.org/kb/how-to-use-java-if-its-been-blocked
See also:
*http://kb.mozillazine.org/Java#Windows_installation_issues
You can find the latest Java version on the Oracle website.
See Java Platform > Java SE 7U11 and Java 6U38 (Download JRE)
*http://www.oracle.com/technetwork/java/javase/downloads/index.html

XI Configuration incase of Java Proxy

Hello
I am trying Java Proxy scenario in which I generated Java Proxies of my XI interface.I used NetWeaver Developer Studio to implement my business logic using the generated classes from XI.
But I guess its not connecting to XI when tried to execute from NWDS.On XI side I configured Business System with no sender configuration and configured Receiver Determination for the business system (basically similar to what we configure for HTTP Adapter).
Just wanted to get clear whether we need to define Sender(sender comm channel) incase of Proxies or any business system instead of business service.As far as I know since its invoking a EJB directly from the lookup it should not require that but not sure.
Thanks in advance.
Regards
Ashish

Hi,
take a look at Java Proxy Inside Storys:
Part I:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/java proxies and sap xi - the inside story,%20Part%201.pdf
Part II:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/java proxies and sap xi - the inside story,%20Part%20II.pdf
Regards,
Robin

Our school is having problems with Java.

Our school is having problems with Java. We cannot open our gradebooks which require jnlp or java to open. They worked until January 31 and then quit. I uploaded the Java from oracle but it doesn't open anything it just keeps running. Any ideas?

See Java for OS X 2012-006: How to re-enable the Apple-provided Java SE 6 applet plug-in and Web Start functionality. That might be what you need, not Java 7.

Java proxy problem:com.sap.aii.proxy.xiruntime cannot be resolved to a type

hi:
    i am new to Java proxy and new to SAP netweaver developer studio.
    thei PI version is 7.1
    I have generate a java proxy , then create a project in netweaver developer studio and import this java proxy according document "How Tou2026Work with XI 3.0 Java Proxies".
    but i can not find :aii_proxy_xirt.jar aii_msg_runtime.jar on the PI server, only guidgenerator.jaraii_utilxi_misc.jar could be found. then i could not config the build path.
    in the SAP netweaver developer studio, the error shows like :com.sap.aii.proxy.xiruntime cannot be resolved to a type
   then how to resolve this problem
   thank you very much

Hi Cheng,
I am trying to create a java proxy to send message from WebAS to PI using java proxy.
I am using NWDS 7.1. Can you please help with step on how to create a java proxy in NWDS 7.1?
Thanks and best regards,
Arun prabhu S

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:
     <b>Sender Service:</b>          JPX_DEV (Java Proxy Client)
     <b>Receiver Service:</b>     DES210_DEV (R/3 4.6C)
But the second try and so on the services that I saw in the monitor are:
     <b>Sender Service:</b>          DES210_DEV (R/3 4.6C)
     <b>Receiver Service:</b>     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

Problem in creating a java proxy for PHP web service

This is a problem in generating a java proxy for a PHP webservice.
I have a PHP service running on Wamp Server and also a PHP client which is able to call the service.
The WSDL for the PHP web service is also generated .
I am trying to create a java proxy using the jdev (10.1.3.0.3) from the wsdl file.
The wsdl generated by the php program is
<?xml version="1.0" encoding="ISO-8859-1" ?>
<definitions xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:si="http://soapinterop.org/xsd" xmlns:tns="urn:hellowsdl" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="urn:hellowsdl">
<types>
<xsd:schema targetNamespace="urn:hellowsdl">
<xsd:import namespace="http://schemas.xmlsoap.org/soap/encoding/" />
<xsd:import namespace="http://schemas.xmlsoap.org/wsdl/" />
</xsd:schema>
</types>
<message name="helloRequest">
<part name="name" type="xsd:string" />
</message>
<message name="helloResponse">
<part name="return" type="xsd:string" />
</message>
<portType name="hellowsdlPortType">
<operation name="hello">
<documentation>Says hello to the caller</documentation>
<input message="tns:helloRequest" />
<output message="tns:helloResponse" />
</operation>
</portType>
<binding name="hellowsdlBinding" type="tns:hellowsdlPortType">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" />
<operation name="hello">
<soap:operation soapAction="urn:hellowsdl#hello" style="rpc" />
<input>
<soap:body use="encoded" namespace="urn:hellowsdl" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
</input>
<output>
<soap:body use="encoded" namespace="urn:hellowsdl" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
</output>
</operation>
</binding>
<service name="hellowsdl">
<port name="hellowsdlPort" binding="tns:hellowsdlBinding">
<soap:address location="http://localhost/mywork/myphp.php" />
</port>
</service>
</definitions>After making following changes to the wsdl program, I tried to generate java proxy.
<definitions name="hellowsdl"
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:si="http://soapinterop.org/xsd" xmlns:tns="http://localhost/mywork/hellowsdl.wsdl" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://localhost/mywork/myphpwsdl.wsdll">
<types>
<xsd:schema targetNamespace="http://localhost/mywork/hellowsdl.wsdl">
<xsd:import namespace="http://schemas.xmlsoap.org/soap/encoding/" />
<xsd:import namespace="http://schemas.xmlsoap.org/wsdl/" />
</xsd:schema>
</types>
<message name="helloRequest">
<part name="name" type="xsd:string" />
</message>
<message name="helloResponse">
<part name="return" type="xsd:string" />
</message>
<portType name="hellowsdlPortType">
<operation name="hello">
<documentation>Says hello to the caller</documentation>
<input message="tns:helloRequest" />
<output message="tns:helloResponse" />
</operation>
</portType>
<binding name="hellowsdlBinding" type="tns:hellowsdlPortType">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" />
<operation name="hello">
<soap:operation soapAction="" style="rpc" />
<input>
<soap:body use="encoded" namespace="http://localhost/mywork/hellowsdl" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
</input>
<output>
<soap:body use="encoded" namespace="http://localhost/mywork/hellowsdl" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
</output>
</operation>
</binding>
<service name="hellowsdl">
<port name="hellowsdlPort" binding="tns:hellowsdlBinding">
<soap:address location="http://localhost/mywork/myphp.php" />
</port>
</service>
</definitions>This is how the java stub file looks like:
public class HellowsdlBinding_Stub
    extends oracle.j2ee.ws.client.StubBase
    implements demo.mypackage.HellowsdlPortType {
     * public constructor
    public HellowsdlBinding_Stub(HandlerChain handlerChain) {
        super(handlerChain);
        _setProperty(ENDPOINT_ADDRESS_PROPERTY, "http://localhost/mywork/hellowsdl.php");
        setSoapVersion(SOAPVersion.SOAP_11);
        setServiceName( new QName("http://localhost/mywork/hellowsdl","hellowsdl"));
        setPortName( new QName("http://localhost/mywork/hellowsdl","hellowsdlPort"));
     * implementation of hello
    public java.lang.String hello(java.lang.String name)
        throws java.rmi.RemoteException {
        StreamingSenderState _state = null;
        try {
            _state = _start(_handlerChain);
            if (_getProperty(ClientConstants.DIME_ENCODE_MESSAGES_WITH_ATTACHMENTS) != null) {
                _state.getMessageContext().getMessage().setProperty("DimeEncode",_getProperty(ClientConstants.DIME_ENCODE_MESSAGES_WITH_ATTACHMENTS));
            InternalSOAPMessage _request = _state.getRequest();
            _request.setOperationCode(hello_OPCODE);
            _state.getMessageContext().setProperty("oracle.j2ee.ws.mgmt.interceptor.operation-qname",new QName("","hello"));
            demo.mypackage.runtime.HellowsdlBinding_hello_ReqS _myHellowsdlBinding_hello_ReqS = new demo.mypackage.runtime.HellowsdlBinding_hello_ReqS();
        _myHellowsdlBinding_hello_ReqS.setName(name);
        SOAPBlockInfo _bodyBlock = new SOAPBlockInfo(ns1_hello_hello_QNAME);
        _bodyBlock.setValue(_myHellowsdlBinding_hello_ReqS);
        _bodyBlock.setSerializer(myns1_hello__HellowsdlBinding_hello_ReqS_SOAPSerializer);
        _request.setBody(_bodyBlock);
        _state.getMessageContext().setProperty("http.soap.action", "http://localhost/mywork/hellowsdl");
        _send((String) _getProperty(ENDPOINT_ADDRESS_PROPERTY), _state);
        demo.mypackage.runtime.HellowsdlBinding_hello_RespS _myHellowsdlBinding_hello_RespS = null;
        Object _responseObj = _state.getResponse().getBody().getValue();
        if (_responseObj instanceof SOAPDeserializationState) {
            _myHellowsdlBinding_hello_RespS =
                (demo.mypackage.runtime.HellowsdlBinding_hello_RespS)((SOAPDeserializationState)_responseObj).getInstance();
        } else {
            _myHellowsdlBinding_hello_RespS =
                (demo.mypackage.runtime.HellowsdlBinding_hello_RespS)_responseObj;
        return _myHellowsdlBinding_hello_RespS.get_return();
    } catch (RemoteException e) {
        // let this one through unchanged
        throw e;
    } catch (JAXRPCException e) {
        throw new RemoteException(e.getMessage(), e);
    } catch (Exception e) {
        if (e instanceof RuntimeException) {
            throw (RuntimeException)e;
        } else {
            throw new RemoteException(e.getMessage(), e);
* this method deserializes the request/response structure in the body
protected void _readFirstBodyElement(XMLReader bodyReader, SOAPDeserializationContext deserializationContext, StreamingSenderState state) throws Exception {
    int opcode = state.getRequest().getOperationCode();
    switch (opcode) {
        case hello_OPCODE:
            _deserialize_hello(bodyReader, deserializationContext, state);
            break;
        default:
            throw new SenderException("sender.response.unrecognizedOperation", Integer.toString(opcode));
* This method deserializes the body of the hello operation.
private void _deserialize_hello(XMLReader bodyReader, SOAPDeserializationContext deserializationContext, StreamingSenderState state) throws Exception {
    try {
        Object myHellowsdlBinding_hello_RespSObj =
            myns1_helloResponse__HellowsdlBinding_hello_RespS_SOAPSerializer.deserialize(ns1_hello_helloResponse_QNAME,
                bodyReader, deserializationContext);
        SOAPBlockInfo bodyBlock = new SOAPBlockInfo(ns1_hello_helloResponse_QNAME);
        bodyBlock.setValue(myHellowsdlBinding_hello_RespSObj);
        state.getResponse().setBody(bodyBlock);
    } catch (DeserializationException e) {
        if (e.getSoapFaultSubCodeType() == JAXRPCExceptionBase.FAULT_CODE_NONE && e.getSoapFaultCodeType() != JAXRPCExceptionBase.FAULT_CODE_DATA_ENCODING_UNKNOWN) {
            e.setSoapFaultSubCodeType(JAXRPCExceptionBase.FAULT_CODE_BAD_ARGUMENTS);
        throw e;
public String _getEncodingStyle() {
    return SOAPEncodingConstants.getSOAPEncodingConstants(soapVersion).getURIEncoding();
public void _setEncodingStyle(String encodingStyle) {
    throw new UnsupportedOperationException("cannot set encoding style");
public ClientTransport getClientTransport() {
    return super._getTransport();
* This method returns an array containing (prefix, nsURI) pairs.
protected String[] _getNamespaceDeclarations() {
    return myNamespace_declarations;
* This method returns an array containing the names of the headers we understand.
public QName[] _getUnderstoodHeaders() {
    return understoodHeaderNames;
* This method handles the case of an empty SOAP body.
protected void _handleEmptyBody(XMLReader reader, SOAPDeserializationContext deserializationContext, StreamingSenderState state) throws Exception {
public void _initialize(InternalTypeMappingRegistry registry) throws Exception {
    super._initialize(registry);
    myns1_hello__HellowsdlBinding_hello_ReqS_SOAPSerializer = (CombinedSerializer)registry.getSerializer(SOAPEncodingConstants.getSOAPEncodingConstants(soapVersion).getURIEncoding(), demo.mypackage.runtime.HellowsdlBinding_hello_ReqS.class, ns1_hello_TYPE_QNAME);
    myns1_helloResponse__HellowsdlBinding_hello_RespS_SOAPSerializer = (CombinedSerializer)registry.getSerializer(SOAPEncodingConstants.getSOAPEncodingConstants(soapVersion).getURIEncoding(), demo.mypackage.runtime.HellowsdlBinding_hello_RespS.class, ns1_helloResponse_TYPE_QNAME);
private static final QName _portName = new QName("http://localhost/mywork/hellowsdl", "hellowsdlPort");
private static final int hello_OPCODE = 0;
private static final QName ns1_hello_hello_QNAME = new QName("http://localhost/mywork/hellowsdl", "hello");
private static final QName ns1_hello_TYPE_QNAME = new QName("http://localhost/mywork/hellowsdl", "hello");
private CombinedSerializer myns1_hello__HellowsdlBinding_hello_ReqS_SOAPSerializer;
private static final QName ns1_hello_helloResponse_QNAME = new QName("http://localhost/mywork/hellowsdl", "helloResponse");
private static final QName ns1_helloResponse_TYPE_QNAME = new QName("http://localhost/mywork/hellowsdl", "helloResponse");
private CombinedSerializer myns1_helloResponse__HellowsdlBinding_hello_RespS_SOAPSerializer;
private static final String[] myNamespace_declarations =
                                    new String[] {
                                        "ns0", "http://localhost/mywork/hellowsdl"
private static final QName[] understoodHeaderNames = new QName[] { };
}The errors that are produced are-
java.rmi.RemoteException: HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Bad response: 404 Not Found; nested exception is:
     HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Bad response: 404 Not Found
Kindly help to resolve this.
Thanks.

This is a problem in generating a java proxy for a PHP webservice.
I have a PHP service running on Wamp Server and also a PHP client which is able to call the service.
The WSDL for the PHP web service is also generated .
I am trying to create a java proxy using the jdev (10.1.3.0.3) from the wsdl file.
The wsdl generated by the php program is
<?xml version="1.0" encoding="ISO-8859-1" ?>
<definitions xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:si="http://soapinterop.org/xsd" xmlns:tns="urn:hellowsdl" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="urn:hellowsdl">
<types>
<xsd:schema targetNamespace="urn:hellowsdl">
<xsd:import namespace="http://schemas.xmlsoap.org/soap/encoding/" />
<xsd:import namespace="http://schemas.xmlsoap.org/wsdl/" />
</xsd:schema>
</types>
<message name="helloRequest">
<part name="name" type="xsd:string" />
</message>
<message name="helloResponse">
<part name="return" type="xsd:string" />
</message>
<portType name="hellowsdlPortType">
<operation name="hello">
<documentation>Says hello to the caller</documentation>
<input message="tns:helloRequest" />
<output message="tns:helloResponse" />
</operation>
</portType>
<binding name="hellowsdlBinding" type="tns:hellowsdlPortType">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" />
<operation name="hello">
<soap:operation soapAction="urn:hellowsdl#hello" style="rpc" />
<input>
<soap:body use="encoded" namespace="urn:hellowsdl" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
</input>
<output>
<soap:body use="encoded" namespace="urn:hellowsdl" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
</output>
</operation>
</binding>
<service name="hellowsdl">
<port name="hellowsdlPort" binding="tns:hellowsdlBinding">
<soap:address location="http://localhost/mywork/myphp.php" />
</port>
</service>
</definitions>After making following changes to the wsdl program, I tried to generate java proxy.
<definitions name="hellowsdl"
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:si="http://soapinterop.org/xsd" xmlns:tns="http://localhost/mywork/hellowsdl.wsdl" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://localhost/mywork/myphpwsdl.wsdll">
<types>
<xsd:schema targetNamespace="http://localhost/mywork/hellowsdl.wsdl">
<xsd:import namespace="http://schemas.xmlsoap.org/soap/encoding/" />
<xsd:import namespace="http://schemas.xmlsoap.org/wsdl/" />
</xsd:schema>
</types>
<message name="helloRequest">
<part name="name" type="xsd:string" />
</message>
<message name="helloResponse">
<part name="return" type="xsd:string" />
</message>
<portType name="hellowsdlPortType">
<operation name="hello">
<documentation>Says hello to the caller</documentation>
<input message="tns:helloRequest" />
<output message="tns:helloResponse" />
</operation>
</portType>
<binding name="hellowsdlBinding" type="tns:hellowsdlPortType">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" />
<operation name="hello">
<soap:operation soapAction="" style="rpc" />
<input>
<soap:body use="encoded" namespace="http://localhost/mywork/hellowsdl" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
</input>
<output>
<soap:body use="encoded" namespace="http://localhost/mywork/hellowsdl" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
</output>
</operation>
</binding>
<service name="hellowsdl">
<port name="hellowsdlPort" binding="tns:hellowsdlBinding">
<soap:address location="http://localhost/mywork/myphp.php" />
</port>
</service>
</definitions>This is how the java stub file looks like:
public class HellowsdlBinding_Stub
    extends oracle.j2ee.ws.client.StubBase
    implements demo.mypackage.HellowsdlPortType {
     * public constructor
    public HellowsdlBinding_Stub(HandlerChain handlerChain) {
        super(handlerChain);
        _setProperty(ENDPOINT_ADDRESS_PROPERTY, "http://localhost/mywork/hellowsdl.php");
        setSoapVersion(SOAPVersion.SOAP_11);
        setServiceName( new QName("http://localhost/mywork/hellowsdl","hellowsdl"));
        setPortName( new QName("http://localhost/mywork/hellowsdl","hellowsdlPort"));
     * implementation of hello
    public java.lang.String hello(java.lang.String name)
        throws java.rmi.RemoteException {
        StreamingSenderState _state = null;
        try {
            _state = _start(_handlerChain);
            if (_getProperty(ClientConstants.DIME_ENCODE_MESSAGES_WITH_ATTACHMENTS) != null) {
                _state.getMessageContext().getMessage().setProperty("DimeEncode",_getProperty(ClientConstants.DIME_ENCODE_MESSAGES_WITH_ATTACHMENTS));
            InternalSOAPMessage _request = _state.getRequest();
            _request.setOperationCode(hello_OPCODE);
            _state.getMessageContext().setProperty("oracle.j2ee.ws.mgmt.interceptor.operation-qname",new QName("","hello"));
            demo.mypackage.runtime.HellowsdlBinding_hello_ReqS _myHellowsdlBinding_hello_ReqS = new demo.mypackage.runtime.HellowsdlBinding_hello_ReqS();
        _myHellowsdlBinding_hello_ReqS.setName(name);
        SOAPBlockInfo _bodyBlock = new SOAPBlockInfo(ns1_hello_hello_QNAME);
        _bodyBlock.setValue(_myHellowsdlBinding_hello_ReqS);
        _bodyBlock.setSerializer(myns1_hello__HellowsdlBinding_hello_ReqS_SOAPSerializer);
        _request.setBody(_bodyBlock);
        _state.getMessageContext().setProperty("http.soap.action", "http://localhost/mywork/hellowsdl");
        _send((String) _getProperty(ENDPOINT_ADDRESS_PROPERTY), _state);
        demo.mypackage.runtime.HellowsdlBinding_hello_RespS _myHellowsdlBinding_hello_RespS = null;
        Object _responseObj = _state.getResponse().getBody().getValue();
        if (_responseObj instanceof SOAPDeserializationState) {
            _myHellowsdlBinding_hello_RespS =
                (demo.mypackage.runtime.HellowsdlBinding_hello_RespS)((SOAPDeserializationState)_responseObj).getInstance();
        } else {
            _myHellowsdlBinding_hello_RespS =
                (demo.mypackage.runtime.HellowsdlBinding_hello_RespS)_responseObj;
        return _myHellowsdlBinding_hello_RespS.get_return();
    } catch (RemoteException e) {
        // let this one through unchanged
        throw e;
    } catch (JAXRPCException e) {
        throw new RemoteException(e.getMessage(), e);
    } catch (Exception e) {
        if (e instanceof RuntimeException) {
            throw (RuntimeException)e;
        } else {
            throw new RemoteException(e.getMessage(), e);
* this method deserializes the request/response structure in the body
protected void _readFirstBodyElement(XMLReader bodyReader, SOAPDeserializationContext deserializationContext, StreamingSenderState state) throws Exception {
    int opcode = state.getRequest().getOperationCode();
    switch (opcode) {
        case hello_OPCODE:
            _deserialize_hello(bodyReader, deserializationContext, state);
            break;
        default:
            throw new SenderException("sender.response.unrecognizedOperation", Integer.toString(opcode));
* This method deserializes the body of the hello operation.
private void _deserialize_hello(XMLReader bodyReader, SOAPDeserializationContext deserializationContext, StreamingSenderState state) throws Exception {
    try {
        Object myHellowsdlBinding_hello_RespSObj =
            myns1_helloResponse__HellowsdlBinding_hello_RespS_SOAPSerializer.deserialize(ns1_hello_helloResponse_QNAME,
                bodyReader, deserializationContext);
        SOAPBlockInfo bodyBlock = new SOAPBlockInfo(ns1_hello_helloResponse_QNAME);
        bodyBlock.setValue(myHellowsdlBinding_hello_RespSObj);
        state.getResponse().setBody(bodyBlock);
    } catch (DeserializationException e) {
        if (e.getSoapFaultSubCodeType() == JAXRPCExceptionBase.FAULT_CODE_NONE && e.getSoapFaultCodeType() != JAXRPCExceptionBase.FAULT_CODE_DATA_ENCODING_UNKNOWN) {
            e.setSoapFaultSubCodeType(JAXRPCExceptionBase.FAULT_CODE_BAD_ARGUMENTS);
        throw e;
public String _getEncodingStyle() {
    return SOAPEncodingConstants.getSOAPEncodingConstants(soapVersion).getURIEncoding();
public void _setEncodingStyle(String encodingStyle) {
    throw new UnsupportedOperationException("cannot set encoding style");
public ClientTransport getClientTransport() {
    return super._getTransport();
* This method returns an array containing (prefix, nsURI) pairs.
protected String[] _getNamespaceDeclarations() {
    return myNamespace_declarations;
* This method returns an array containing the names of the headers we understand.
public QName[] _getUnderstoodHeaders() {
    return understoodHeaderNames;
* This method handles the case of an empty SOAP body.
protected void _handleEmptyBody(XMLReader reader, SOAPDeserializationContext deserializationContext, StreamingSenderState state) throws Exception {
public void _initialize(InternalTypeMappingRegistry registry) throws Exception {
    super._initialize(registry);
    myns1_hello__HellowsdlBinding_hello_ReqS_SOAPSerializer = (CombinedSerializer)registry.getSerializer(SOAPEncodingConstants.getSOAPEncodingConstants(soapVersion).getURIEncoding(), demo.mypackage.runtime.HellowsdlBinding_hello_ReqS.class, ns1_hello_TYPE_QNAME);
    myns1_helloResponse__HellowsdlBinding_hello_RespS_SOAPSerializer = (CombinedSerializer)registry.getSerializer(SOAPEncodingConstants.getSOAPEncodingConstants(soapVersion).getURIEncoding(), demo.mypackage.runtime.HellowsdlBinding_hello_RespS.class, ns1_helloResponse_TYPE_QNAME);
private static final QName _portName = new QName("http://localhost/mywork/hellowsdl", "hellowsdlPort");
private static final int hello_OPCODE = 0;
private static final QName ns1_hello_hello_QNAME = new QName("http://localhost/mywork/hellowsdl", "hello");
private static final QName ns1_hello_TYPE_QNAME = new QName("http://localhost/mywork/hellowsdl", "hello");
private CombinedSerializer myns1_hello__HellowsdlBinding_hello_ReqS_SOAPSerializer;
private static final QName ns1_hello_helloResponse_QNAME = new QName("http://localhost/mywork/hellowsdl", "helloResponse");
private static final QName ns1_helloResponse_TYPE_QNAME = new QName("http://localhost/mywork/hellowsdl", "helloResponse");
private CombinedSerializer myns1_helloResponse__HellowsdlBinding_hello_RespS_SOAPSerializer;
private static final String[] myNamespace_declarations =
                                    new String[] {
                                        "ns0", "http://localhost/mywork/hellowsdl"
private static final QName[] understoodHeaderNames = new QName[] { };
}The errors that are produced are-
java.rmi.RemoteException: HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Bad response: 404 Not Found; nested exception is:
     HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Bad response: 404 Not Found
Kindly help to resolve this.
Thanks.

Facing Problem in Deploying EAR for Client Java Proxy.

Hi All,
            I am facing problems in deploying EAR in PI/XI server.
The scenario is Client Java Proxy to SAP
. I have followed the the pdf-how to create java proxies in 3.0. Using that I have created the EJB module and it archive.
Finally created the EAR without errors. But while deploying the same in PI server, it throws the following error. Please do help me out in providing any inputs on the same.
Deploy trace is seen below:-
Deploy of the ear has errors :
java.rmi.RemoteException: Cannot deploy application sap.com/BusPartnerEAR..
Reason: Errors while compiling:
D:/usr/sap/ECD/DVEBMGS03/j2ee/cluster/server0/apps/sap.com/BusPartnerEAR/EJBContainer/temp/temp1175887267437/com/mud/sAPFICA/businessPartner/_MIOSBusinessPartner_PortTypeRemoteObjectImpl0_0_Tie.java:91: illegal escape character
      if (method.equals("U0024descriptor")) {
                          ^
D:/usr/sap/ECD/DVEBMGS03/j2ee/cluster/server0/apps/sap.com/BusPartnerEAR/EJBContainer/temp/temp1175887267437/com/mud/sAPFICA/businessPartner/_MIOSBusinessPartner_PortTypeRemoteObjectImpl0_0_Tie.java:98: illegal escape character
      if (method.equals("U0024jcoRuntimeMetaData")) {
                          ^
D:/usr/sap/ECD/DVEBMGS03/j2ee/cluster/server0/apps/sap.com/BusPartnerEAR/EJBContainer/temp/temp1175887267437/com/mud/sAPFICA/businessPartner/_MIOSBusinessPartner_PortTypeRemoteObjectImpl0_0_Tie.java:112: illegal escape character
      if (method.equals("U0024generationInfo")) {
                          ^
D:/usr/sap/ECD/DVEBMGS03/j2ee/cluster/server0/apps/sap.com/BusPartnerEAR/EJBContainer/temp/temp1175887267437/com/mud/sAPFICA/businessPartner/_MIOSBusinessPartner_PortTypeRemoteObjectImpl0_0_Tie.java:119: illegal escape character
      if (method.equals("U0024messageSpecifier")) {
                          ^
D:/usr/sap/ECD/DVEBMGS03/j2ee/cluster/server0/apps/sap.com/BusPartnerEAR/EJBContainer/temp/temp1175887267437/com/mud/sAPFICA/businessPartner/_MIOSBusinessPartner_PortTypeRemoteObjectImpl0_0_Tie.java:152: illegal escape character
      if (method.equals("U0024runtime")) {
                          ^
D:/usr/sap/ECD/DVEBMGS03/j2ee/cluster/server0/apps/sap.com/BusPartnerEAR/EJBContainer/temp/temp1175887267437/com/mud/sAPFICA/businessPartner/_MIOSBusinessPartner_PortTypeRemoteObjectImpl0_0_Tie.java:195: illegal escape character
      if (method.equals("U0024messageSpecifierRead")) {
                          ^
D:/usr/sap/ECD/DVEBMGS03/j2ee/cluster/server0/apps/sap.com/BusPartnerEAR/EJBContainer/temp/temp1175887267437/com/mud/sAPFICA/businessPartner/_MIOSBusinessPartner_PortTypeRemoteObjectImpl0_0_Tie.java:202: illegal escape character
      if (method.equals("U0024messageSpecifier__")) {
                          ^
D:/usr/sap/ECD/DVEBMGS03/j2ee/cluster/server0/apps/sap.com/BusPartnerEAR/EJBContainer/temp/temp1175887267437/com/mud/sAPFICA/businessPartner/_MIOSBusinessPartner_PortTypeRemote_Stub.java:93: illegal escape character
          org.omg.CORBA_2_3.portable.OutputStream out = (org.omg.CORBA_2_3.portable.OutputStream)_request("U0024descriptor", true);
                                                                                ^
D:/usr/sap/ECD/DVEBMGS03/j2ee/cluster/server0/apps/sap.com/BusPartnerEAR/EJBContainer/temp/temp1175887267437/com/mud/sAPFICA/businessPartner/_MIOSBusinessPartner_PortTypeRemote_Stub.java:112: illegal escape character
      ServantObject so = servantpreinvoke("U0024descriptor", MIOSBusinessPartner_PortTypeRemote.class);
                                              ^
D:/usr/sap/ECD/DVEBMGS03/j2ee/cluster/server0/apps/sap.com/BusPartnerEAR/EJBContainer/temp/temp1175887267437/com/mud/sAPFICA/businessPartner/_MIOSBusinessPartner_PortTypeRemote_Stub.java:134: illegal escape character
          org.omg.CORBA_2_3.portable.OutputStream out = (org.omg.CORBA_2_3.portable.OutputStream)_request("U0024jcoRuntimeMetaData", true);
                                                                                ^
D:/usr/sap/ECD/DVEBMGS03/j2ee/cluster/server0/apps/sap.com/BusPartnerEAR/EJBContainer/temp/temp1175887267437/com/mud/sAPFICA/businessPartner/_MIOSBusinessPartner_PortTypeRemote_Stub.java:153: illegal escape character
      ServantObject so = servantpreinvoke("U0024jcoRuntimeMetaData", MIOSBusinessPartner_PortTypeRemote.class);
                                              ^
D:/usr/sap/ECD/DVEBMGS03/j2ee/cluster/server0/apps/sap.com/BusPartnerEAR/EJBContainer/temp/temp1175887267437/com/mud/sAPFICA/businessPartner/_MIOSBusinessPartner_PortTypeRemote_Stub.java:216: illegal escape character
          org.omg.CORBA_2_3.portable.OutputStream out = (org.omg.CORBA_2_3.portable.OutputStream)_request("U0024generationInfo", true);
                                                                                ^
D:/usr/sap/ECD/DVEBMGS03/j2ee/cluster/server0/apps/sap.com/BusPartnerEAR/EJBContainer/temp/temp1175887267437/com/mud/sAPFICA/businessPartner/_MIOSBusinessPartner_PortTypeRemote_Stub.java:235: illegal escape character
      ServantObject so = servantpreinvoke("U0024generationInfo", MIOSBusinessPartner_PortTypeRemote.class);
                                              ^
D:/usr/sap/ECD/DVEBMGS03/j2ee/cluster/server0/apps/sap.com/BusPartnerEAR/EJBContainer/temp/temp1175887267437/com/mud/sAPFICA/businessPartner/_MIOSBusinessPartner_PortTypeRemote_Stub.java:257: illegal escape character
          org.omg.CORBA_2_3.portable.OutputStream out = (org.omg.CORBA_2_3.portable.OutputStream)_request("U0024messageSpecifier", true);
21 errors
Awaiting for your replies...
Regards,
Dhana

Hi,
     Thanks for your input..
   I have also opend the EAR as ZIP file and deleted the existing listing libaries
apart from the actual implementing Jar and META-INF folder.
I have tried deploying the Jar for the second time, it is throwing the same error.
What I did is...Once the EAR is created, I went to Resource perspective in NWDS and copied the EAR from the EAR project and used the same for deployment.
Is there is anything else to be modified or deleted before deployement?
Regards,
Dhana

Problem in JAVA proxy scenario: cannot locate QSI root directory

Similar Messages

Maybe you are looking for