on 01-08-2010 9:48 AM
Hi.
I've run into a problem, when calling a java proxy (PI 7.1) from the WS adapter.
I get the following error:
______________________________________________________________________________________________________
<sap:ExceptionChain xmlns:sap="http://www.sap.com/webas/710/soap/runtime/abap/fault/system/SystemFault"> <sap:ChainedException> <Exception_Name>CX_SOAP_SEQ_EX_TO_QRFC</Exception_Name> <Exception_Text>wsrm create failed</Exception_Text> </sap:ChainedException> <sap:ChainedException> <Exception_Name>CX_SOAP_CORE</Exception_Name> <Exception_Text>SRT: Error in WSRM Soap Application</Exception_Text> </sap:ChainedException> <sap:ChainedException> <Exception_Name>CX_SOAP_FAILURE_FAULT</Exception_Name> <Exception_Text>SOAP fault when calling Web service</Exception_Text> </sap:ChainedException> <sap:ChainedException> <Exception_Name>CX_SOAP_FAULT</Exception_Name> <Exception_Text>Reliable Messaging Exception - String: com.sap.engine.services.webservices.espbase.server.additions.exceptions.ProcessException: No operation found using soap keys [http://docs.oasis-open.org/ws-rx/wsrm/200702], [CreateSequence]. InterfaceMapping Object class: com.sap.engine.services.webservices.espbase.mappings.InterfaceMapping mappings: {BindingQName={http://xxxx.xxx/easy/easy}EasyInput_iaBinding, SEIName=xxxx.xxx.easy.easy.EasyInputIa, BindingType=Soap, PortTypeQName=EasyInput_ia, JAXWSInterface=true, PortQName=EasyInput_ia_Port, ServiceQName=EasyInput_ia_Service, InterfaceMappingID=6eaa09dc:12559f3fa1b:-76a4}.; Lang: en; Code: ProcessException; Actor: Server; NS: http://www.sap.com/NW05/soap/features/wsrm/</Exception_Text>; </sap:ChainedException> </sap:ExceptionChain>
______________________________________________________________________________________________________
The Java Proxy (Web service) works fine from WS Navigator when called there, and the scenario itself works fine as well.
So the only problem is when calling the Proxy from the WS adapter.
The scenario looks like this (Asynchronous): FILE --> PI > WS (> Java Proxy)
Hope someone have an idea
Best Regards...
Peter
Hi Robert.
I havn't been able to figure this out yet. My interface was just made to see if I could get the WS adapter to work, and I havn't been successfull yet (havn't spend much time trying either).
My next move would be to create an ABAP proxy, to see if I have success with that (at least there is a how-to guide to help here).
I will come back to this tread when I find a solution.
Best regards...
Peter
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Manfred.
Yes I did.
I tried to remove the reference, and use the webservice via SOAP adapter.
That didnt seem to work eighter.
I will dig a little deeper into this, and return with a solution... I Hope
Thanks for the reply.
Peter
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi again Manfred.
It does behave differently.
I get an error looking like this now:
System error while calling Web service adapter: <sap:ExceptionChain xmlns:sap="http://www.sap.com/webas/710/soap/runtime/abap/fault/system/SystemFault"> <sap:ChainedException> <Exception_Name>CX_SOAP_FAILURE</Exception_Name> <Exception_Text>CX_ST_REF_ACCESS:An exception occurred.XSLT exception.Error accessing the ref. node 'PROT_NAME'</Exception_Text> </sap:ChainedException> <sap:ChainedException> <Exception_Name>CX_SOAP_CORE</Exception_Name> <Exception_Text>CX_ST_REF_ACCESS:An exception occurred.XSLT exception.Error accessing the ref. node 'PROT_NAME'</Exception_Text> </sap:ChainedException> <sap:ChainedException> <Exception_Name>CX_SOAP_ROOT</Exception_Name> <Exception_Text>An exception occurred</Exception_Text> </sap:ChainedException> <sap:ChainedException> <Exception_Name>CX_SXMLP</Exception_Name> <Exception_Text>XSLT exception</Exception_Text> </sap:ChainedException> <sap:ChainedException> <Exception_Name>CX_ST_REF_ACCESS</Exception_Name> <Exception_Text>Error accessing the ref. node 'PROT_NAME': Main Program:SRT_HIB_PROT_SESSION| Program:SRT_HIB_PROT_SESSION| Line: 15| Valid:X</Exception_Text> </sap:ChainedException> </sap:ExceptionChain> Error when processing Web service call Error when calling SOAP Runtime functions: CX_ST_REF_ACCESS:An exception occurred.XSLT exception.Error accessing the ref. node 'PROT_NAME' An exception occurred XSLT exception Error accessing the ref. node 'PROT_NAME'
Does it ring a bell?
Best Regards...
Peter
Hi Peter,
Did you ever find out what caused your original error? I am getting the same message. I have tested from 3 SOAP test tools and get the same problem. (Tried SAP WS Navigator test tool, SoapUI, and SOAPScope).
I checked the blog on this error and it says the regenerate the web service client; but I have done that by re-importing a new WSDL into the test tools above.
My error is:
<SOAP-ENV:Envelope xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SOAP-ENV:Body>
<SOAP-ENV:Fault>
<faultcode>SOAP-ENV:Client</faultcode>
<faultstring>com.sap.engine.services.webservices.espbase.server.additions.exceptions.ProcessException: No operation found using soap keys [], [spmat_jdbc_receiver_proxy]. InterfaceMapping Object class: com.sap.engine.services.webservices.espbase.mappings.InterfaceMapping mappings: {BindingQName={urn:nexeninc:pi:ll:spmat:100}SI_I_Sync_SPMAT_JDBC_Receiver_ProxyBinding, BindingType=Soap, PortTypeQName={urn:nexeninc:pi:ll:spmat:100}SI_I_Sync_SPMAT_JDBC_Receiver_Proxy, JAXWSInterface=true, InterfaceMappingID=-27e4d529:127632b5c52:-7ebb}.</faultstring>
<detail>
<yq1:com.sap.engine.services.webservices.espbase.server.additions.exceptions.ProcessException xmlns:yq1="http://sap-j2ee-engine/client-runtime-error">
<!--com.sap.engine.services.webservices.espbase.server.additions.exceptions.ProcessException: No operation found using soap keys [], [spmat_jdbc_receiver_proxy]. InterfaceMapping Object class: com.sap.engine.services.webservices.espbase.mappings.InterfaceMapping mappings: {BindingQName={urn:nexeninc:pi:ll:spmat:100}SI_I_Sync_SPMAT_JDBC_Receiver_ProxyBinding, BindingType=Soap, PortTypeQName={urn:nexeninc:pi:ll:spmat:100}SI_I_Sync_SPMAT_JDBC_Receiver_Proxy, JAXWSInterface=true, InterfaceMappingID=-27e4d529:127632b5c52:-7ebb}.-->
</yq1:com.sap.engine.services.webservices.espbase.server.additions.exceptions.ProcessException>
</detail>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Any tips would be very helpful.
Thanks!
RBL
Hi Peter,
did you reference the WS-RM application in your application as described in this [help document|http://help.sap.com/saphelp_nwpi71/helpdata/de/46/7f2fef88190ad3e10000000a11466f/content.htm]?
If not you could try using the soap adapter instead of the ws adapter.
Cheers,
Mane
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
25 | |
12 | |
9 | |
6 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.