on 04-09-2010 11:06 AM
Hi All,
I have configured a SOAP to SOAP sync interface.
The interface works fine as Proxy/RFC to SOAP sync.
I am sending the SOAP request using Altova. I get the error as Internal server error on the PI server.
If I try the config in ID using payload from IR OpMapping it is able to determine all steps.
From the payload in Altova if I test config in ID then it is not able to determine Interface, Receiver and receiver agreement.
Could you help me pin point anything wrong that I may be doing?
Thanks.
Also for ref.. the message from IR OpMapping is as below
<?xml version="1.0" encoding="UTF-8"?>
<ns0:ZbapiWebservice1 xmlns:ns0="urn:sap-com:document:sap:soap:functions:mc-style">
<P1>7</P1>
<P2>8</P2>
</ns0:ZbapiWebservice1>
From Altova it looks like this,
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<SOAP-ENV:Body>
<m:ZbapiWebservice1 xmlns:m="urn:sap-com:document:sap:soap:functions:mc-style">
<P1>7</P1>
<P2>8</P2>
</m:ZbapiWebservice1>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Edited by: Ankesh on Apr 9, 2010 3:37 PM
use the free tool available at http://www.soapui.org/
it gives you a better testing experience. As mentioned earlier, XMLSpy seems to have issues in some cases so the SOAPUI might be a better option
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Shabarish,
Thanks for updating about the tool. I found the tool quite good.
Though I am getting the same error when using soapUI too. I will paste below a part of the error log. it talks of some binding not found.
Could you just check if it makes any sense to you.
Error Log:
HTTP/1.1 500 Internal Server Error
server: SAP NetWeaver Application Server 7.10 / AS Java 7.10
transfer-encoding: chunked
content-type: text/xml; charset=utf-8
content-encoding: gzip
date: Fri, 09 Apr 2010 13:35:58 GMT
set-cookie: saplb_*=(**************)27456250; Version=1; Path=/
set-cookie: JSESSIONID=SBFBJn5KwRILgJ_W31zomPq0qNA2usjiJwH68qIB_SAP; Version=1; Path=/
<?xml version='1.0'?>
<!-- see the documentation -->
<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'>
<SOAP:Body>
<SOAP:Fault>
<faultcode>SOAP:Server</faultcode>
<faultstring>Server Error</faultstring>
<detail>
<s:SystemError xmlns:s='http://sap.com/xi/WebService/xi2.0'>
<context>XIAdapter</context>
<code>ADAPTER.JAVA_EXCEPTION</code>
<text><![CDATA[
com.sap.aii.af.service.cpa.impl.exception.CPALookupException: Couldn't retrieve binding for the given channelId: Binding:CID=null;
at com.sap.aii.af.service.cpa.impl.lookup.AbstractLookupManager.getBindingByChannelId(AbstractLookupManager.java:243)
at com.sap.aii.adapter.soap.web.MessageServlet.doPost(MessageServlet.java:419)
Hi Ankesh,
i feel you have not changed the target address url of the WSDL generated from the webservice wizard. Try the following url in your target address url of WSDL making necessary changes
http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel
Regards
Shailesh
Edited by: Shailesh Kunjiraman on Apr 9, 2010 3:49 PM
Hi Shailesh,
The end point url is
http:/host:port/XISOAPAdapter/MessageServlet?channel=:SERVICE_NAME:COMM_CHANNEL&version=3.0&Sender.Service=SERVICE_NAME&Interface=NAMESPACE%5ESERVICE_INTERFACE
This is what is contained in the WSDL generated from ID.
Do I need to truncate this to http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel ???
You dont need to truncate theURL....it is ok.
From the error text (binding for channelId).....just make sure that you are using the same name in your URL as you have given to the channel in ID.....all the names are case-sensitive.....ensure that there are no spaces in the names that you use in the URL.
Can you test the message successfully from RWB --> Componentn Monitoring --> Integration Engine --> Test Message?
Just make sure that the names are the same and if still facing any issue....re-activate the ID objects for this scenario...may be the CACHE is stuck somewhere.
Regards,
Abhishek.
What URL are you using? Saw some posts in SDN which mentioned some problem with Altova XML Spy....instead can you check with SAP SOAP Client.
Update:
The request that you send from a SOAP tool should be like:
Request Message Format:
<?xml version="1.0" encoding="UTF-8" ?>
<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'>
<SOAP:Body>
<Your Payload without XML tag <?xml version="1.0" encoding="UTF-8"?>>
</SOAP:Body>
</SOAP:Envelope>
Regards,
Abhishek.
Edited by: abhishek salvi on Apr 9, 2010 4:02 PM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
83 | |
10 | |
10 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.