Unable to interpret Response from client proxy

Hello SAP Guru's, 
I am working on trying to consume an external web service using a client (consumer) proxy. 
I've created the proxy using the WSDL file provided by the service (see below). I am able to actually call the proxy and execute the service, however, I cannot seem to properly handle the response coming back from the synchronous service call. When I use the WSNAVIGATOR to test the service I get the following message: 'Part 'processWorkOrderReturn' not found in response !'. 
When I try to test it using SE80 and the Test function, I get the following error message: "SOAP:1,023 SRT: Processing error in Internet Communication Framework: ("ICF Error when receiving the response: ICM_HTTP_CONNECTION_FAILED")". 
Here is the WSDL (edited to protect IP addresses): 
&lt?xml version="1.0" encoding="UTF-8" ?&gt 
- &ltwsdl:definitions targetNamespace="http://sapphire.aeroint.com/connect/services" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://sapphire.aeroint.com/connect/services" xmlns:intf="http://sapphire.aeroint.com/connect/services" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"&gt 
- &lt!-- 
WSDL created by Apache Axis version: 1.4 
Built on Apr 22, 2006 (06:55:48 PDT) 
--&gt 
&ltwsdl:types&gt 
&ltschema elementFormDefault="qualified" targetNamespace="http://sapphire.aeroint.com/connect/services" xmlns="http://www.w3.org/2001/XMLSchema"&gt 
&ltcomplexType name="WorkOrderType"&gt 
&ltsequence&gt 
&ltelement name="code" nillable="true" type="xsd:string" /&gt 
&ltelement name="description" nillable="true" type="xsd:string" /&gt 
&ltelement name="faultClassification" nillable="true" type="xsd:string" /&gt 
&ltelement name="malfunctionEffect" nillable="true" type="xsd:string" /&gt 
&ltelement name="name" nillable="true" type="xsd:string" /&gt 
&ltelement name="position" nillable="true" type="xsd:string" /&gt 
&ltelement name="status" nillable="true" type="xsd:string" /&gt 
&ltelement name="vehicleSerialNumber" nillable="true" type="xsd:string" /&gt 
&lt/sequence&gt 
&lt/complexType&gt 
&ltelement name="parameters" type="impl:WorkOrderType" /&gt 
&ltcomplexType name="Return"&gt 
&ltsequence&gt 
&ltelement name="return" nillable="true" type="xsd:string" /&gt 
&lt/sequence&gt 
&lt/complexType&gt 
&ltelement name="processWorkOrderReturn" type="impl:Return" /&gt 
&lt/schema&gt 
&lt/wsdl:types&gt 
&ltwsdl:message name="processWorkOrderRequest"&gt 
&ltwsdl:part element="impl:parameters" name="parameters" /&gt 
&lt/wsdl:message&gt 
&ltwsdl:message name="processWorkOrderResponse"&gt 
&ltwsdl:part element="impl:processWorkOrderReturn" name="processWorkOrderReturn" /&gt 
&lt/wsdl:message&gt 
&ltwsdl:portType name="ConnectManager"&gt 
&ltwsdl:operation name="processWorkOrder" parameterOrder="parameters"&gt 
&ltwsdl:input message="impl:processWorkOrderRequest" name="processWorkOrderRequest" /&gt 
&ltwsdl:output message="impl:processWorkOrderResponse" name="processWorkOrderResponse" /&gt 
&lt/wsdl:operation&gt 
&lt/wsdl:portType&gt 
&ltwsdl:binding name="ConnectManagerSoapBinding" type="impl:ConnectManager"&gt 
&ltwsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" /&gt 
&ltwsdl:operation name="processWorkOrder"&gt 
&ltwsdlsoap:operation soapAction="" /&gt 
&ltwsdl:input name="processWorkOrderRequest"&gt 
&ltwsdlsoap:body use="literal" /&gt 
&lt/wsdl:input&gt 
&ltwsdl:output name="processWorkOrderResponse"&gt 
&ltwsdlsoap:body use="literal" /&gt 
&lt/wsdl:output&gt 
&lt/wsdl:operation&gt 
&lt/wsdl:binding&gt 
&ltwsdl:service name="ConnectManagerService"&gt 
&ltwsdl:port binding="impl:ConnectManagerSoapBinding" name="ConnectManager"&gt 
&ltwsdlsoap:address location="http://&ltIP Address:Port&gt/connect/services/ConnectManager" /&gt 
&lt/wsdl:port&gt 
&lt/wsdl:service&gt 
&lt/wsdl:definitions&gt 
Here is the actual test Request that is passed to the system: 
POST /connect/services/ConnectManager HTTP/1.1 
Host: &ltIP Address:Port&gt 
Content-Type: text/xml; charset=UTF-8 
Connection: close 
SAP-PASSPORT: &ltsome big long number&gt 
Content-Length: 852 
SOAPAction: "" 
&lt?xml version="1.0" encoding="UTF-8" ?&gt 
&ltSOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xs="http://www.w3.org/2001/XMLSchema"&gt 
&ltSOAP-ENV:Header&gt 
&ltsapsess:Session xmlns:sapsess="http://www.sap.com/webas/630/soap/features/session/"&gt 
&ltenableSession&gttrue&lt/enableSession&gt 
&lt/sapsess:Session&gt 
&lt/SOAP-ENV:Header&gt 
&ltSOAP-ENV:Body&gt 
&ltpns:parameters xmlns:pns='http://sapphire.aeroint.com/connect/services'&gt 
&ltpns:code&gt0200-1&lt/pns:code&gt 
&ltpns:description&gtXVY&lt/pns:description&gt 
&ltpns:faultClassification&gtTestA&lt/pns:faultClassification&gt 
&ltpns:malfunctionEffect&gtTestB&lt/pns:malfunctionEffect&gt 
&ltpns:name&gtWTZ&lt/pns:name&gt 
&ltpns:position&gt02:00&lt/pns:position&gt 
&ltpns:status&gtACCEPTED&lt/pns:status&gt 
&ltpns:vehicleSerialNumber&gt05-12345&lt/pns:VehicleSerialNumber&gt 
&lt/pns:parameters&gt 
&lt/SOAP-ENV:Body&gt 
&lt/SOAP-ENV:Envelope&gt 
Please note, this actually does successfully reach out and call the service on the remote system. 
Finally, here is the actual Response that is generated and submitted back to me: 
HTTP/1.1 200 OK 
Server: Apache-Coyote/1.1 
X-Powered-By: Servlet 2.4; JBoss-4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)/Tomcat-5.5 
Set-Cookie: &ltvalue is hidden&gt 
Content-Type: text/xml;charset=utf-8 
Date: Tue, 27 Oct 2009 16:56:58 GMT 
Connection: close 
&lt?xml version="1.0" encoding="UTF-8"?&gt 
&ltsoapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"&gt 
&ltsoapenv:Body&gt 
&ltprocessWorkOrderReturn xmlns=""&gt 
&ltreturn>Arising Created in Sapphire&lt/return&gt 
&lt/processWorkOrderReturn&gt 
&lt/soapenv:Body&gt 
&lt/soapenv:Envelope&gt 
My Question is this, why isn't our system finding the response structure (or more to the point why isn't it successfully able to interpret the response?). The 'processWorkOrderReturn' element appears to be in the response and in fact appears to be correct. Am I missing something? 
Thanks, 
-Jon
Edited by: Jon ***** on Oct 27, 2009 8:04 PM
Edited by: Jon ***** on Oct 27, 2009 8:05 PM
Edited by: Jon ***** on Oct 27, 2009 8:13 PM

Hi Axel,
Yes, I was able to eventually solve the problem. The problem was caused by the raw data of the response coming back from the server. The raw response included an XML tag with no namespace xmlns="". The SAP system failed to interpret this tag and consequently was not able to process the rest of the message. I wish the error messages had been a little more clear, but I was able to actually (eventually) debug into the soap runtime engine and spotted that it was failing when attempting to intepret the specific tag ' processWorkOrderReturn xmlns="" '. From there it was just trial and error to figure out that it needed to have a namespace supplied that matched the definition in the WSDL file.
Hope your problem is as easy to solve as ours was.
-Jon
Edited by: Jon ***** on Nov 30, 2009 1:37 PM

Similar Messages

Not getting response from Client Proxy

Hi,
We are developing a scenario - File->PI->Proxy using ABAP Proxies.We are posting a file thru PI 7.0 to R/3 .In R/3 the server proxy(Inbound Asynchronous) will receive the message and BAPI will be called. The response from the BAPI will be reaching the server proxy and passed to the client proxy(Outbound Asynchronous).
Server Proxy(request) --> BAPI --> Server Proxy(response) --> Client Proxy(response)
The response from the client proxy has to be send to PI and a file will be generated as the output.
Can anyone provide me suggestions to call client proxy from a server proxy by passing the response message to client proxy???
Thanks in advance.
Regards,
Dibyajyoti

Hi,
I hope, you are done till the Implementation of Server Proxy, where you are calling a Bapi and passing the Input variables the Interface received and BAPI is giving a response back.
Now your question, how to send the response back Asynchronously.
I think, you have to do the same, what you do for a client proxy and at last call the method EXECUTE_ASYNCHRONOUS before the Final Commit Staement. I think this should work.
But using Synchronous Interface in such cases is always a handy and easier option.
Regards,
Subhendu

Client seems to be unable to read response from service

(This is on weblogic 8.1 SP2 using the JWSDP-1.6)
I'm getting the error below on the client side when I call the service using this code:
Stub stub = (Stub)(new DataExchanger_Impl().getDataExchangerSoap());
DataExchangerSoap hello = (DataExchangerSoap)stub;
String result = hello.exchangeData("user","23234-234234","confirm","xml data here");
out.println(result);
Given the stakc trace below I looked at the DataExchangerSoap_Stub class on line 70. This appears to be the client sending the data to the server.
send((String) getProperty(ENDPOINT_ADDRESS_PROPERTY), _state);
On the server I see the incoming data, process it and return an xml string:
<exchangeDataResult>
<status>OK</status>
<message>Transaction accepted.</message>
</exchangeDataResult>
No errors occur on the server. Looking at the stack trace from the client it seems it never even gets to the point where it trys to read the response.
What the hell does this error message mean?
[java] java.rmi.RemoteException: Runtime exception; nested exception is:
[java] unexpected element name: expected={https://partners.mcdata.com/}exchangeDataResponse, actual={http://partners.mcdata.com}exchangeDataResponse
[java] at com.sun.xml.rpc.client.StreamingSender._handleRuntimeExceptionInSend(Ljava.lang.RuntimeException;)V(StreamingSender.java:248)
[java] at com.sun.xml.rpc.client.StreamingSender._send(Ljava.lang.String;Lcom.sun.xml.rpc.client.StreamingSenderState;)V(StreamingSender.java:230)
[java] at com.mcdata.websvc.riverbed.server.DataExchangerSoap_Stub.exchangeData(Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;)Ljava.lang.String;(DataExchangerSoap_Stub.java:70)
[java] at jsp_compiled.__index._jspService(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(__index.java:134)
[java] at weblogic.servlet.jsp.JspBase.service(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(JspBase.java:33)
[java] at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run()Ljava.lang.Object;(ServletStubImpl.java:971)
[java] at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;Lweblogic.servlet.internal.FilterChainImpl;)V(ServletStubImpl.java:402)
[java] at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(ServletStubImpl.java:305)
[java] at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run()Ljava.lang.Object;(WebAppServletContext.java:6350)
[java] at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Lweblogic.security.subject.AbstractSubject;Ljava.security.PrivilegedAction;)Ljava.lang.Object;(AuthenticatedSubject.java:317)
[java] at weblogic.security.service.SecurityManager.runAs(Lweblogic.security.acl.internal.AuthenticatedSubject;Lweblogic.security.acl.internal.AuthenticatedSubject;Ljava.security.PrivilegedAction;)Ljava.lang.Object;(SecurityManager.java:118)
[java] at weblogic.servlet.internal.WebAppServletContext.invokeServlet(Lweblogic.servlet.internal.ServletRequestImpl;Lweblogic.servlet.internal.ServletResponseImpl;)V(WebAppServletContext.java:3635)
[java] at weblogic.servlet.internal.ServletRequestImpl.execute(Lweblogic.kernel.ExecuteThread;)V(ServletRequestImpl.java:2585)
[java] at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(ExecuteThread.java:197)
[java] at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:170)
[java] at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Source)
[java] Caused by: unexpected element name: expected={https://partners.mcdata.com/}exchangeDataResponse, actual={http://partners.mcdata.com}exchangeDataResponse
[java] at com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.internalDeserialize(Ljavax.xml.namespace.QName;Lcom.sun.xml.rpc.streaming.XMLReader;Lcom.sun.xml.rpc.encoding.SOAPDeserializationContext;)Ljava.lang.Object;(LiteralObject
SerializerBase.java:161)
[java] at com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.deserialize(Ljavax.xml.namespace.QName;Lcom.sun.xml.rpc.streaming.XMLReader;Lcom.sun.xml.rpc.encoding.SOAPDeserializationContext;)Ljava.lang.Object;(LiteralObjectSerializ
erBase.java:95)
[java] at com.mcdata.websvc.riverbed.server.DataExchangerSoap_Stub._deserialize_exchangeData(Lcom.sun.xml.rpc.streaming.XMLReader;Lcom.sun.xml.rpc.encoding.SOAPDeserializationContext;Lcom.sun.xml.rpc.client.StreamingSenderState;)V(DataExchan
gerSoap_Stub.java:117)
[java] at com.mcdata.websvc.riverbed.server.DataExchangerSoap_Stub._readFirstBodyElement(Lcom.sun.xml.rpc.streaming.XMLReader;Lcom.sun.xml.rpc.encoding.SOAPDeserializationContext;Lcom.sun.xml.rpc.client.StreamingSenderState;)V(DataExchangerS
oap_Stub.java:104)
[java] at com.sun.xml.rpc.client.StreamingSender._send(Ljava.lang.String;Lcom.sun.xml.rpc.client.StreamingSenderState;)V(StreamingSender.java:158)
[java] ... 14 more

When I use
http://208.47.133.243/riverbedshipserver/exchangeData?WSDL
to view the WSDL what is returned has the non-ssl namespace in it and it doesn't match the WSDL I used to generated the service to begin with.
The WSDL doesn't get packaged into the service EAR file, should it? If so where is it supposed to be placed?
Where the heck is 8.1 getting that namespace setting that doesn't have the https in stead of http?
Here is the WSDL I used to create the service:
<?xml version="1.0" encoding="utf-8"?>
<wsdl:definitions
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:tns="https://partners.mcdata.com/"
xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
targetNamespace="https://partners.mcdata.com/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
name="">
<wsdl:types>
<s:schema elementFormDefault="qualified" targetNamespace="https://partners.mcdata.com/">
<s:element name="exchangeData">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="sender" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="password" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="transactionType" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="data" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="exchangeDataResponse">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="exchangeDataResult" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
</s:schema>
</wsdl:types>
<wsdl:message name="exchangeDataSoapIn">
<wsdl:part name="parameters" element="tns:exchangeData" />
</wsdl:message>
<wsdl:message name="exchangeDataSoapOut">
<wsdl:part name="parameters" element="tns:exchangeDataResponse" />
</wsdl:message>
<wsdl:portType name="DataExchangerSoap">
<wsdl:operation name="exchangeData">
<wsdl:input message="tns:exchangeDataSoapIn" />
<wsdl:output message="tns:exchangeDataSoapOut" />
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="DataExchangerSoap" type="tns:DataExchangerSoap">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" />
<wsdl:operation name="exchangeData">
<soap:operation soapAction="https://208.47.133.243/riverbedshipserver/exchangeData" style="document" />
<wsdl:input>
<soap:body use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="DataExchanger">
<wsdl:port name="DataExchangerSoap" binding="tns:DataExchangerSoap">
<soap:address location="https://208.47.133.243/riverbedshipserver/exchangeData" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>

ISE No EAP response from Client

Hi,
So on the same switch, same port configuration, 1 users laptop has absoutely no issues authenticating on the port.
On another port, same configuration, I see the below error in ISE.
Same windows settings on both laptops regarding the 802.1x authentication.
No response received during 120 seconds on last EAP message sent to the client :
5411 No response received during 120 seconds on last EAP message sent to the client
Any ideas as to why or whats happening here?

Verify that supplicant is configured properly to conduct a full EAP conversation with ISE. Verify that NAS is configured properly to transfer EAP messages to or from supplicant. Verify that supplicant or network access server (NAS) does not have a short timeout for EAP conversations. Check the network that connects the NAS to ISE. If the external ID store is used for the authentication, it may be not responding fast enough for current timeouts. For more information you can see the below link.
http://www.cisco.com/en/US/solutions/collateral/ns340/ns414/ns742/ns744/docs/howto_81_troubleshooting_failed_authc.pdf

Slow response from Webmail Proxy on the first SSL connection

Hi,
I encounter a queer problem with Messenger Express 5.2 patch1, acting as a http proxy (Mesenger Express Multiplexor) for another Messaging 5.2P1.
The first time a user tries to connect through HTTPS since a certain amount of time, it takes about one minute to get the webmail login page. And then it takes one more minute to have the user authenticated after it enters the credentials.
The next connections are almost immediate.
Has anyone already seen this problem ?
The same server doesn't show this problem when connecting on port 80 without SSL.
It looks like the encryption keys exchange negociation takes a very long time.
Can this come from a compatibility problem between the client (Communicator 4.75, IE5 or IE6) and the server ?
Are there recommandations regarding Internal Encryption modules and/or server certificates ?
(Algorithms , key length...)
Any answer would be appreciated.
Regards,
Vincent MAZARD
[email protected]
DML France

1. Basically, there's a problem on one of the servers which the ASC is hosted on.
2. It's not at your end. Nothing needs to be or can be done on your devices to resolve it.
3. No.
(106571)

Response from Synchronus Proxy

Hi ,
I am sending data from FILE-XI-R/3 through ABAP Proxy to create purchase order.
I want to send back response(PO number created) from Proxy to XI .I want to
keep the response in XI itself.
Do I need BPM to achieve this scenario since FILE adapter is asynchronus?
Thanx.
Rekha.

Hi,
your BPM can look like this:
receive step (FTP adapter) -> transformation step
(mapping from file message to proxy.request) -> send step
(send proxy message) sync step so you can get the
request -> then if you want you can put another
transformation step to map proxy.response to something
else and send it or not...
you have to create one mapping (file to proxy.request)
if you want you can also do proxy.response to something else)
the same goes with interfaces mappings one or two
if you want you can also use BAPI (wrapped) instead of
usinf proxies as most probaby you'll be using the same
BAPI inside your proxy call
the scenario would be the same but you would use RFC
apdater in the send step
BTW
the bapi you'd have to wrap is: BAPI_PO_CREATE
Regards,
michal

Unable to connect application from client

hey friends,
With this URL:
http://webserv:7777/forms/frmservlet?form=test
i can run it locally but if try it with another machine,it says page cannot be displayed.
The softwares that i have installed it are :
RHEL 4
oracle datbase 10.2.0.1
ORacle applicationserver standalone forms and services 10.1.2

Telnet requires seperate service altogether... Telnet would not be a check point for such a problem.
Try to ping using machine name (the name used in hosts file), first from the local machine, and if successful, then from network machine:
ping myhostYou will be able to successfully ping using machine name only if you have hosts file configured properly.
Aalap Sharma :)

Unable to invoke ADFBC based ws using client proxy

Hie
I created a custom am method and exposed it as a webservice and deployed it to my integrated wls.
Then i generated the client proxy specifying the wsdl running at localhost.
now when i am trying to call the service method from client proxy i get following exception. Not sure how to resolve..please advise..
avax.xml.ws.WebServiceException: java.lang.IllegalArgumentException: prefix ns1 is not bound to a namespace
     at com.sun.xml.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:144)
     at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:125)
     at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:95)
     at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:136)
     at $Proxy43.storePost(Unknown Source)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at weblogic.wsee.jaxws.spi.ClientInstanceInvocationHandler.invoke(ClientInstanceInvocationHandler.java:84)
     at $Proxy44.storePost(Unknown Source)
     at oracle.apps.crm.smm.view.service.proxy.SmmAMServiceSoapHttpPortClient.main(SmmAMServiceSoapHttpPortClient.java:42)
Caused by: java.lang.IllegalArgumentException: prefix ns1 is not bound to a namespace
     at com.sun.xml.bind.DatatypeConverterImpl._parseQName(DatatypeConverterImpl.java:388)
     at com.sun.xml.bind.v2.runtime.unmarshaller.XsiTypeLoader.parseXsiType(XsiTypeLoader.java:92)
     at com.sun.xml.bind.v2.runtime.unmarshaller.XsiTypeLoader.startElement(XsiTypeLoader.java:70)
     at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallingContext._startElement(UnmarshallingContext.java:481)
     at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallingContext.startElement(UnmarshallingContext.java:459)
     at com.sun.xml.bind.v2.runtime.unmarshaller.InterningXmlVisitor.startElement(InterningXmlVisitor.java:71)
     at com.sun.xml.bind.v2.runtime.unmarshaller.SAXConnector.startElement(SAXConnector.java:148)

Hi Bora,
I guess that you are having a username/password for directory manager on OUD proxy (let's say cn=proxymgr / proxypwd), and another username/password for directory manager your ODSEE servers (let's say cn=odseemgr / odseepwd).
When you connect to OUD proxy using cn=proxymgr to perform a search on your backend, OUD proxy creates a connection to the ODSEE backend with the same credentials (because the proxy is configured in use-client-identity mode), i.e. cn=proxymgr / proxypwd. If this user does not exist on ODSEE (or has the same name with a different password), you get an error 49.
To avoid this issue, OUD proxy offers configuration parameters in the proxy-workflow-element: the exclude-list and remote-ldap-server-bind-dn / remote-ldap-server-bind-password. You have to add cn=proxymgr to the exclude-list, and set remote-ldap-server-bind-dn to cn=odseemgr, remote-ldap-server-bind-password to odseepwd.
This way, when connecting with cn=proxymgr, the proxy will know that he should not use the client credentials, but rather cn=odseemgr when discussing with ODSEE backend.
This concept is explained in OUD admin guide, Configuring the Bind Mode.
HTH,
Flo.

SAP Client Proxy to Webservice Synchronous Scenario

Hi Experts,
I have an outbound Synchronous Scenario.In which i have to trigger a Client Proxy from SAP side and Connect to a WebService using PI.
I have with me the WSDl and URL for Webservice.Can anyone guide me with the necessary steps.
Regards
Gaurav

Hi gaurav,
From client proxy u have to send request and get the response back...
So, for this create 2 corresponding data types and message types. and mapping will be between request message type which u created and request wsdl message and another mapping for response wsdl message and response message type which u created.
create service interface outbound synchronous(give the message types which u created) and inbound synchronous(give the wsdl request and response messages).
Regards,
Sunitha

WS Adapter: Scenario SAP(Client)Proxy= PI= WS

Hello Experts,
I have a scenario - SAP to PI to 3rdParty(NON-SAP).
This is merely data getting pushed out of SAP ECC to 3rd party. Not request-response type.
The REQUIREMENT is P2P Communication Scenario thus will not make use of Integration Sever.
Data will be sent from ABAP(Client)Proxy => PI => WS Adapter/Direct Connection.
Question:
1. Is there any application where I can test the webservice?(i.e. INFOPATH)
If its a request-resopnse type of scenario I can make use of INFOPATH to test the webservice however this is only
consuming of service.
2. Is there anyway to test the webservice other than connecting to the actual 3rd party?AND I dont want to create a server proxy from another ECC client. My test should be SAP->PI->NOn SAP.
Ta!!
Edited by: el_sapinator on Oct 19, 2010 3:51 PM

Hi gaurav,
From client proxy u have to send request and get the response back...
So, for this create 2 corresponding data types and message types. and mapping will be between request message type which u created and request wsdl message and another mapping for response wsdl message and response message type which u created.
create service interface outbound synchronous(give the message types which u created) and inbound synchronous(give the wsdl request and response messages).
Regards,
Sunitha

Unable to read SEARCH response from backend server

Currently we have problem when searching huge amounts of users against new SunOne Directory Server v6.3
in production and acceptance.
[17:12:43] root@ecdiala03-2[!]# /opt/app/sun/ds6/bin/dsadm -V
[dsadm]
dsadm : 6.3 B2008.0311.0058 NAT
[slapd 64-bit]
Sun Microsystems, Inc.
Sun-Java(tm)-System-Directory/6.3 B2008.0311.0058 64-bit
ns-slapd : 6.3 B2008.0311.0058 NAT
Slapd Library : 6.3 B2008.0311.0058
Front-End Library : 6.3_MTR_5087249_1_20081209 B2008.1210.1821
==============================================================
Its not working while searching huge amounts of users against DPS.However, Its working while searching huge amounts of users against DS.
Below is the error from access log of DPS when the problem occurred.
==================================
31/Mar/2009:14:08:17 +0200] - CONNECT - INFO - conn=4565433 client=153.88.247.15:2719 server=ecdiala03-1:389 protocol=LDAP
[31/Mar/2009:14:08:17 +0200] - PROFILE - INFO - conn=4565433 assigned to connection handler cn=default connection handler, cn=connection handlers, cn=config
[31/Mar/2009:14:08:17 +0200] - OPERATION - INFO - conn=4565433 op=0 BIND dn="uid=itimadm1,ou=system accounts,o=ericsson" method="SIMPLE" version=3
[31/Mar/2009:14:08:17 +0200] - SERVER_OP - INFO - conn=4565433 op=0 BIND dn="uid=ITIMADM1,ou=system accounts,o=Ericsson" method="SIMPLE"" version=3 s_msgid=17 s_conn=ecditna03-2:72725
[31/Mar/2009:14:08:17 +0200] - SERVER_OP - INFO - conn=4565433 op=0 BIND RESPONSE err=0 msg="" s_conn=ecditna03-2:72725
[31/Mar/2009:14:08:17 +0200] - PROFILE - INFO - conn=4565433 assigned to connection handler cn=BindDone,cn=connection handlers,cn=config
[31/Mar/2009:14:08:17 +0200] - OPERATION - INFO - conn=4565433 op=0 BIND RESPONSE err=0 msg="" etime=0
[31/Mar/2009:14:08:17 +0200] - OPERATION - INFO - conn=4565433 op=1 msgid=2 SEARCH base="ou=External,o=Ericsson" scope=2 filter="(objectclass=inetorgperson)" attrs="*"
[31/Mar/2009:14:08:17 +0200] - SERVER_OP - INFO - conn=4565433 op=1 SEARCH base="ou=external,o=ericsson" scope=2 filter="(objectclass=inetorgperson)" attrs="*" s_msgid=18 s_conn=ecditna03-2:72725
[31/Mar/2009:14:12:25 +0200] - OPERATION - INFO - conn=4565433 op=1 SEARCH RESPONSE err=1 msg="Unable to read SEARCH response from backend server : Timeout when waiting to read from input stream" nentries=33959 etime=248309
[31/Mar/2009:14:17:25 +0200] - DISCONNECT - INFO - conn=4565433 reason="other" msg="Exception caught while polling client connection LDAP.153.88.247.15.2719 -- java.io.IOException: Connection reset by peer"
================================
>>
> > [15:12:29] root@ecdiala03-1[!]# ./dpadm -V
> >
> > [dpadm]
> >
> > dpadm :
> >
6.3_PD_COMBO_CUMULATIVE_VIRTUAL_15112008_ED2.0+6774589+6780423+6778308+6782659_2
> > B2008.1212.0459 NAT
> >
> >
> >
> > [DPS]
> >
> > Sun Microsystems, Inc.
> >
> >
Sun-Java(tm)-System-Directory-Proxy-Server/6.3_PD_COMBO_CUMULATIVE_VIRTUAL_15112008_ED2.0+6774589+6780423+6778308+6782659_2
> > B2008.1212.0436
> >
> > =================

We have changed the value of data-source-read-timeout in DPS from 20s to 30m.As per application test, the "time out" error has gone, but we get a new error as following.
==========================
[27/Apr/2009:05:28:36 +0200] - SERVER_OP - INFO - conn=209469 op=8 SEARCH base="ou=internal,o=ericsson" scope=2 filter="(objectclass=ericssonInternal)" attrs="EriCA-AttesterNL EriCA-EmploymentForm EriCA-KeyRecoveryNL-Auth EriCA-NL-Auth EriCA-NLOTP-Admin EriCA-NLOTP-User EriCA-accountExpires c cn departmentNumber description displayName eriCompanySynch eriCountry eriCountryCode eriEmployeeStatus eriExpired eriIsManager eriMasterDomain eriOpOrgUnitAbbreviation eriOpOrgUnitIdentifier eriOpOrgUnitName eriOperationalManager eriPartner eriPartnerTrigram eriPwSynchDate eriSignType eriSignum eriSignumStatus facsimileTelephoneNumber givenName isMemberOf l mail memberOf mobile objectClass ou sametimebrowseldap sametimehomeserver sametimeuser smChallResp smDisabled smXauthRADIUSServer sn telephoneNumber title uid uidNumber " s_msgid=27 s_conn=ecditna03-2:8645
[27/Apr/2009:06:06:23 +0200] - SERVER_OP - INFO - conn=209469 op=8 SEARCH RESPONSE err=0 msg="" nentries=236367 s_conn=ecditna03-2:8645
[27/Apr/2009:06:06:23 +0200] - OPERATION - INFO - conn=209469 op=8 SEARCH RESPONSE err=0 msg="" nentries=236367 etime=2266483
[27/Apr/2009:06:11:27 +0200] - DISCONNECT - INFO - conn=209469 reason="other" msg="Exception caught while polling client connection LDAP.153.88.247.15.4862 -- java.io.IOException: Connection reset by peer"
================
Each time while application client (153.88.247.15) connecting DPS to read, they will exit with connection reset error.
Could you please kindly give us some suggestion if this error is realted to the DPS?

"500 Internal Server Error" response from asynchronous AquaLogic proxy

Hi,
We have a proxy service deployed to AquaLogic Service Bus (alsb) v3.0 as a WSDL-based SOAP/HTTP service. The WSDL for the proxy defines a single one-way operation (i.e. no response message is defined), making it an asynchronous operation. The proxy routes the request through a couple business services and then routes the response to a URL specified in the request (in the ReplyTo element of a WS-Addressing header). Essentially it's an asynchronous request-response pattern that accepts requests from a web service and calls back to that web service with the response.
This proxy service works perfectly when run from the test page in the ALSB console. However, when calling the proxy from the real client web service, AquaLogic returns a "500" response from the HTTP POST. The WSDL and everything look correct, and we can use the proxy's URL to download the WSDL with no problem.
Is this a known problem?
Thanks!
-Eric

HI,
I am looking for a solution to the problem (i am using Oracle service Bus_10.3).
After publishing, I can get the wsdl from the web browser but calling the proxy service directly results:
com.bea.control.ServiceControlException: Unexpected exception raised invoking getTerminalDistance on control com.demo.control.TerminalLocationServiceControl. Use getCause() to see the root cause.[java.rmi.RemoteException: SOAPFaultException - FaultCode [{http://schemas.xmlsoap.org/soap/envelope/}Server] FaultString [BEA-380001: Internal Server Error] FaultActor [null] Detail [<detail><con:fault xmlns:con="http://www.bea.com/wli/sb/context"><con:errorCode>BEA-380001</con:errorCode><con:reason>Internal Server Error</con:reason><con:location><con:node>RouteNode3</con:node><con:path>response-pipeline</con:path></con:location></con:fault></detail>]; nested exception is:
 weblogic.wsee.jaxrpc.soapfault.WLSOAPFaultException: BEA-380001: Internal Server Error]
 at com.bea.control.servicecontrol.impl.ServiceControlImpl.invoke(ServiceControlImpl.java:696)
 at com.demo.control.TerminalLocationServiceControlBean.getTerminalDistance(TerminalLocationServiceControlBean.java:132)
 at com.demo.control.TerminalLocationImpl.getTerminalDistance(TerminalLocationImpl.java:51)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at weblogic.wsee.component.pojo.JavaClassComponent.invoke(JavaClassComponent.java:112)
 at weblogic.wsee.ws.dispatch.server.ComponentHandler.handleRequest(ComponentHandler.java:84)
 at weblogic.wsee.handler.HandlerIterator.handleRequest(HandlerIterator.java:141)
 at weblogic.wsee.ws.dispatch.server.ServerDispatcher.dispatch(ServerDispatcher.java:114)
 at weblogic.wsee.ws.WsSkel.invoke(WsSkel.java:80)
 at weblogic.wsee.server.servlet.SoapProcessor.handlePost(SoapProcessor.java:66)
 at weblogic.wsee.server.servlet.SoapProcessor.process(SoapProcessor.java:44)
 at weblogic.wsee.server.servlet.BaseWSServlet$AuthorizedInvoke.run(BaseWSServlet.java:285)
 at weblogic.wsee.server.servlet.BaseWSServlet.service(BaseWSServlet.java:169)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
 at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
 at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
 at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
 at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
 at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3504)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(Unknown Source)
 at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2186)
 at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2092)
 at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.rmi.RemoteException: SOAPFaultException - FaultCode [{http://schemas.xmlsoap.org/soap/envelope/}Server] FaultString [BEA-380001: Internal Server Error] FaultActor [null] Detail [<detail><con:fault xmlns:con="http://www.bea.com/wli/sb/context"><con:errorCode>BEA-380001</con:errorCode><con:reason>Internal Server Error</con:reason><con:location><con:node>RouteNode3</con:node><con:path>response-pipeline</con:path></con:location></con:fault></detail>]; nested exception is:
 weblogic.wsee.jaxrpc.soapfault.WLSOAPFaultException: BEA-380001: Internal Server Error
 at weblogic.wsee.jaxrpc.StubImpl.throwRemoteException(StubImpl.java:296)
I have implemented one testservice and trying to invoke Aqualogic proxy using service control generated through weblogic workshop and getting above error. but if I use test console of Service bus to test this proxy, it runs fine. Also I have configured proxy service message flow where i am using "Replace" action to replce the header from the incoming reuest with the following as my business service expects this security token:
<soap:Header xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" soap:mustUnderstand="1">
<wsse:UsernameToken xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="UsernameToken-24512621">
<wsse:Username>sample:parlayx</wsse:Username>
<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">1234</wsse:Password>
</wsse:UsernameToken>
</wsse:Security>
</soap:Header>
please Please share any additional configuration/settings needed.
thanks
Narendra

Remove SOAP Header Element from ALSB Proxy Service Response

I've got a client of one of my ALSB Proxy services that needs the SOAP header element removed from the response. I'm struggling to find a way to do that with a WSDL-based proxy service. Do I need to change my service to an Any XML Service or is there an easier way?

At the same time, could you please also tell me how do i convert a XML Response from a business service to a SOAP Response in Proxy Service.
My client is expecting a soap response and the backend gives back only the XML Response
Thanks in advance!!
~Swagat

Adding header info from JPD Proxy client

We have created a JPD RMI Proxy. The JPD has a JMS execution path and an
http execution path. We set the headers by actually creating the http
message themselves. We can use the generated proxy jar and call it from a
client. It does work. The problem is, we want to set the headers in the
client but there appears to be no interface to do so. It is a simple hello
world application with a clientRequest() method that takes an XMLBean as a
parameter.

At the same time, could you please also tell me how do i convert a XML Response from a business service to a SOAP Response in Proxy Service.
My client is expecting a soap response and the backend gives back only the XML Response
Thanks in advance!!
~Swagat

Client Proxy--unable to edit Execute Asynchronous method !!!!

Hi All,
With Reference to the blog stated below
/people/sravya.talanki2/blog/2006/07/28/smarter-approach-for-coding-abap-proxies
I tried to write code inside the Execute Asynchronous method. But I was unable to edit the method and it comes as can not edit Proxy Objects. Is there any steps to do to make edit option available for this method.
Regards,
Sundar.

Hi,
you never write code in client proxies in the generated method
you can only do it for server proxies
if you want to use the client proxy you need to call it from your own
report (or function module)
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Unable to interpret Response from client proxy

Similar Messages

Maybe you are looking for