cancel
Showing results for 
Search instead for 
Did you mean: 

Getting invalid content type for SOAP: TEXT/HTML exception for Soap Adapter

Former Member
0 Kudos

I am trying to invoke Webservice using SOAP Receiver Adapter

but I am getting error

<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: invalid content type for SOAP: TEXT/HTML</SAP:AdditionalText>

Pls let me know

Regards

Accepted Solutions (0)

Answers (4)

Answers (4)

prabhu_s2
Active Contributor
0 Kudos

check these....will be helpful to troubleshoot:

Receiver SOAP Adapter configuration.

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/40728f7b-0401-0010-d9bc-8c7...

http://help.sap.com/saphelp_nw2004s/helpdata/en/29/5bd93f130f9215e10000000a155106/frameset.htm

(check the address in soap address location in wsdl)

Former Member
0 Kudos

HI,

The problem is that your Xi server is not able to connect to the web service.

So everytime when it sends the message .... it gets the error page back "This page cannot be displayed" (A typical HTML page when you are not able to connect to internet)

Now since this is a HTML page hence cotent type "text/html".

Try chacking your connection settings.... check ur proxy settings....(Ur proxy might not be accepting your loginn ID)... try changing your proxy settings

U can use tools like TCPMON for debugging such SOAP scenarios and check out wat message u are sending and wat response you are getting....

Former Member
0 Kudos

I have already tested it in my test env.

Now I have moved to to my production env with all the valid username and passwords

I am getting this error

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Call Adapter

-->

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">

<SAP:Category>XIAdapterFramework</SAP:Category>

<SAP:Code area="MESSAGE">GENERAL</SAP:Code>

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: invalid content type for SOAP: TEXT/HTML</SAP:AdditionalText>

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack />

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

prabhu_s2
Active Contributor
0 Kudos

try to check with my post earlier....shud be helpful...did u check with the address?

Former Member
0 Kudos

HI,

see

• Q: What character encoding is supported by the SOAP sender adapter?

A: The SOAP sender adapter can accept any character encoding supported by the local JDK. When you are using a particular character encoding with content type text/xml, you must make sure that the encoding name given in the content type and in the XML declaration must be consistent. What makes this more complex is that the default values. The default encoding for "text/xml" is US-ASCII, whereas the default encoding for the XML declaration is UTF-8 or UTF-16. The following examples show several valid combinations of content-type and XML declartion:

text/xml

<?xml version='1.0' encoding='us-ascii'?>

text/xml; charset='utf-8'

<?xml version='1.0' encoding='utf-8'?>

text/xml; charset='utf-8'

no declaration

text/xml; charset='iso-8859-1'

<?xml version='1.0' encoding='iso-8859-1'?>

application/xml

<?xml version='1.0' encoding='iso-8859-1'?>

The response message from the SOAP sender is normally encoded in UTF-8. If you want to change this encoding, for instance to iso-8859-1, you can supply the encoding information with the xmlenc variable in the request URL as in:

http://host:port /XISOAPAdapter/MessageServlet?channel=p:s:c&xmlenc=iso-8859-1

Related Questions "What character encoding is supported by the SOAP receiver adapter?"

Regards

Chilla

Former Member
0 Kudos

Hello,

I did not get you very much.

Can you pls tell me what changes I have to do in Soap Sender Adapter and Soap Receiver Adapter

Regards

prabhu_s2
Active Contributor
0 Kudos

The Problem is your web service is not accepting the content type text/plain. The below Weblog explains how to debug a SOAP Call.

/people/varadharajan.krishnasamy/blog/2007/01/09/troubleshooting-soap-message--xi