cancel
Showing results for 
Search instead for 
Did you mean: 

File to SOAP,error in sender file adapter

Former Member
0 Kudos

Hi,

I am doing a scenario FILE to SOAP where In file adapter I am using Quality od service as Exactly once in order.I am getting the below error.It works fine when I use QOS=Exactly once.Not sure why,can you guys please help me.Can we really use QOS-EOIO for sender file adapter,where exacly do we use it.

Thanks

<?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>

Edited by: guest xi on Apr 16, 2008 11:55 AM

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi !

To use QoS = EOIO, you should specified it only in the sender adapter and also fill the Queue Name field, so each XML message generated from the incoming file is queued in that queue and processed in order by IS. It should work right away after entering the Communication Channel, and changing the QoS from EO to EOIO and entering the queue name. Please try both QoS with the same file to discard that the problem is in the test itself.

Best regards,

Matias.

Former Member
0 Kudos

Hi,

Thanks for your replies guys.I diid give the queue name ,I dont know what is causing the error.Now even QOS=EO which was working fine before is throwing an error.I am using the same file name for both

<?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>

Former Member
0 Kudos

The receiver system is dowm,that what I heard.I will try to test once it is up.I guess that is what causing the problem.

Thanks

Former Member
0 Kudos

Hi !

If once the receiver system is up, you are still having troubles, check this threads:

Regards,

Matias

ps: please award points if helpful.

stefan_grube
Active Contributor
0 Kudos

> If once the receiver system is up, you are still having troubles, check this threads:

Why do you think so?

This errormessage means, that you receive an HTML page instead of in XML document. That happens usually in case of error number 4xx like 401 no authorization, 404 page not find and so on.

When the receiving systm is done, then you have a 404 error.

Regards

Stefan

Former Member
0 Kudos

Once the receiver system in up,I will test it and we can see what happens.Thanks for your replies guys,appreciate your help

Former Member
0 Kudos

Did you specify the queue name when you selected EOIO as QOS.