Response Failure!

[Former Member]

Hey all,

My web service is trying to send a message and he always gets a HTTP FAILURE as response. I have set up a synchronous party with a synchronous HTTP adapter and a response data type( which is nothing but a string field). Is the response automatically triggered when the incoming request comes in? Like whether is it pulled from the synchrounous message interface? I am just wondering what kind of runtime settings need to be done during configuration?

Any ideas guys..

-Teresa

[henrique_pinto]

If you are using SOAP, use SOAP adapter instead of plain HTTP adapter. It lacks some functionalities that SOAP standard needs.

Regards,

Henrique.

[Former Member]

No, we are not using WSDL’s. But we are using standard message types with header wrappers. So the idea was to go with a synchronous HTTP sender with a response. Do you think we should go with WSDL’s for the B2B? Or may be just use the SOAP sender instead of a HTTP sender? Any ideas ‘cos we are running out of them…:)

-Teresa

[henrique_pinto]

Well,

I'd try the soap option, because I've read somewhere that Soap (and some advanced http services) require http message split/merge (the messasge's broken in pieces and then it's recovered on the client side), but Http plain adapter doesn't support that.

I don't know if that's a rumor, but I'd try it out.

Regards,

Henrique.

[Former Member]

I guess this is a very basic web service question. In asynchronous HTTP sender, will the sender B2B application get a 200 response for a successful posting?

-Teresa

[henrique_pinto]

Define the QoS as Exactly Once.

It should then send the http 200.

Regards,

Henrique.

[Former Member]

Thanks Pinto. We set up the sender URL to be http://<hostname><port>/sap/xi/adapter_plain?namespace=<ns>&interface=<int>&service=<service>&party=...

But the external webservice is getting a failure response(404). Is this because of improper query string or do I need to set up an RFC with HTTP?

Teresa

[former_member206604]

Hi,

<i>>>>http://<hostname><port>/sap/xi/adapter_plain?namespace=<ns>&interface=<int>&service=<service>&party=<party>&qos=EOIO</i>

In your URL it says EOIO -> Exactly Once In Order. I guess it should be EO that is Exacly Once. Check out that.

Thanks,

Prakash

[Former Member]

Ooops sorry its EO...But still the error persists

Teresa

[henrique_pinto]

Theresa,

I've just realized that you are trying to do Soap Async using http adapter.

I don't know if the plain http adapter will send Http 200 by default, for async requests. I'd recommend once more for you to use Soap adapter.

Regards,

Henrique.

[Former Member]

Hi,

Thanks for the information. I am not doing a WSDL but a simple XML payload from a B2B webservice. So according to your suggestion, I need to set up a sender SOAP adapter

http://<hostname>:<port>/ XISOAPAdapter/MessageServlet?channel=party:service:channel/nosoap = true/qos=EO

with Do Not Use SOAP envelope? Do I set the qos in the URL or in the comm. Channel setting would be sufficient?

Correct me if I am wrong.

[former_member206604]

Hi,

may be you can go thru this link might be helpful

Thanks,

Prakash

[Former Member]

Hi,

I set the sender SOAP to http://<hostname>:<port>/ XISOAPAdapter/MessageServlet?channel=party:service:channel&nosoap = true&qos=EO and the web service is sending messages but none of the messages are able to be seen in the SXMB_MONI. Even if they do are not successful, I would like to see a message in the monitoring screen. What could be the issue?

Teresa

[former_member206604]

Hi,

Did you check Adapter Monitoring? Is there any error?

Then also check MDT see if there is any error.

mdt : http://host:port/mdt

Thanks,

Prakash