Webservice hell - invalid content type for SOAP: TEXT/HTML

[#1]

Hi All

I'm trying to call a webservice in XI and getting the dreaded "invalid content type for SOAP: TEXT/HTML" error.

Running it in XMLSpy it works perfectly well, but not in XI.

Here are some screenshots:

1) The Request sent from XMLSpy

[XMLSpy Request - Successful|http://www.host-images.com/u/files/3spjf72drc9ncjhtiovo.jpg]

2) The successful response to XMLSpy

[XMLSpy response|http://www.host-images.com/u/files/c3u8k9bplpzu8z6il61a.jpg]

3) Here is the error in XI in RWB, together with the XML payload

[XML and RWB error|http://www.host-images.com/u/files/9ex5dhqua9y07lhpja09.jpg]

4) Here is the SOAP Comms Channel

[Comms channel|http://www.host-images.com/u/files/w6pa90yy0nkly628535i.jpg]

Note:

1. The 'Target URL' and the 'SOAP Action' are taken directly from the parameters used successfully in XMLSpy

2. I have already added 'localejbs/AF_Modules/MessageTransformBean' / 'Transform.ContentType' / text/xml;charset=utf-8

I woul really appreciate some help with this, as I'm getting kind of desparate.

Thanks in advance.

[Former Member]

chk this

/people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009

[Former Member]

HI

I have confirmed the Target URL http://webservices.oxatis.com/webservices/HttpServices/SOAP/OrderServices.asmx

is the same as is sugested by XMLSpy.

I confirm that the SOAP action "OrderGetList" is the same as XMLSpy suggests.

I confirm that Transform.ContentType text/xml is set, as suggested.

Unfortunately in XI I am still getting:

Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: invalid content type for SOAP: TEXT/HTML: java.io.IOException: invalid content type for SOAP: TEXT/HTML

The same parameters in XMLSpy work perfectly.

[Former Member]

Hi Andy,

We faced similar problem & found alternative.

Try out, if it works for u as well.

1) Use HTTP Adapter instead of SOAP.

Transport Protocol : HTTP 1.0

Message Protocol : XI Payload in HTTP Body

Adapter Engine : Integration Server

Addressing type : URL Address.

Target Host:

Service Number :

Path Prefix:

Authentication type : we hv used Ananymus login, as our login details in payload header.

Content Type : application/soap+xml;charset=UTF-8( this is IMP).

Header Fields.

Name value

Host target host

XI Payload Manipulation

XML Code : UTF-8

Hope, this helps...

-santosh.

[baskar_gopalakrishnan2]

Even if your soapaction is wrong or target url is invalid , you have chance to get this error. Please test with blank in action and see the result. This is my few cents..