Trying to call a webservice generated by coldfusion

[Former Member]

Hi

We are running SAP PI 7.11.

We are trying, from SAP PI, to call a webservice that is created by coldfusion - the target url is called

http:/...../edb_service.cfc?wsdl via the SOAP adapter (RECEIVER)

Our adapter/comm channel fails with a http error 500:

"SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 500 Internal Server Error. Setting message to status failed."

It appears that we are not getting any connection at all. When trying to call the webservice from XMLSPY it works fine? Are there any restriction to call a webservice created by coldfusion?

How can I get any better logging of the call attempt, because I can not see anything out of the comm. channel eror message.

Any help would be appreciated.

Thx

[Former Member · Accepted solution]

Hi

the target url should be http:/...../edb_service.cfc

also mention the correct action.

you would not get the error.

Regards

Monika

[Former Member · Accepted solution]

well we gave up in the end, because of time constraints, and coded the receiver webservice in ASP and now everything is working great.

[stefan_grube]

> http:/...../edb_service.cfc?wsdl

This URL is definitely wrong. The target URL must not end with ?wsdl.

[Former Member]

Yes I thought that it looked strange and I tried without ?wsdl but it is still giving me exactly the same errormessage...

And I also tried cpacache refresh full - just in case.

Edited by: bohamo on Nov 29, 2010 1:13 PM

[stefan_grube]

> Yes I thought that it looked strange and I tried without ?wsdl but it is still giving me exactly the same errormessage...

Maybe you not just try, but ask someone for the correct URL?

You might find the URL inside the WSDL also.

[Former Member]

Well inside the wsdl it is listed with ?wsdl and when I try that one in xmlspy it works ok?

[stefan_grube]

What do you find in the WSDL under service -> port -> soap:address location attribute?