on 07-24-2009 10:50 AM
Hello,
we got a some idiosyncratic problem:
we want to connect o an SAP CRM2007 a 3rd level party tool. We do it on our demo system (let me call it A) and another system (let me call it B) wich are on the same release level.
The wsdl of the demosystem looks quite different in the service-tag
The demosystem A shows up like this and is running fine with soap ui
<wsdl:service name="service"><wsdl:port name="ZCWK_xxxx" binding="tns:ZCWK_xxxx"><soap:address location="http://path_to_location:8000/sap/bc/srt/rfc/sap/ZCWK_XXX/client/ZCWK_XXXX/ZCWK_XXXX"/></wsdl:port></wsdl:service>
The other system B shows up the wsdl like this
<wsdl:service name="ZCWK_xxxx"><wsdl:port name="ZCWK_xxxx" binding="tns:ZCWK_xxxx"><soap:address location="http://path_to_location:8000/sap/bc/srt/rfc/sap/ZCWK_XXX/client/ZCWK_XXXX/ZCWK_XXXX"/></wsdl:port></wsdl:service>
The difference is the name "service" and "ZCWK_xxxx".
What can cause this difference. I already checked the configuration of the service in the SE80 and the soap manager they are the same in the system A and B.
But when I open the WSDL in the SOAManager and copy the soap:address location in the internet explorer I m getting the answer in B: SRT: Wrong Content-Type and empty http body
What is wrong?
Thanks for your help
Thanks for your help
Hi
can you please validate accordingly as below documents
https://www.sdn.sap.com/irj/sdn?rid=/webcontent/uuid/d99b2014-0b01-0010-a8a0-aa830dbdf5e8 [original link is broken]
/people/thomas.jung3/blog/2004/11/17/bsp-a-developers-journal-part-xiv--consuming-webservices-with-abap
regards
nag
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.