SOAP Receiver Success / HTTP Receiver Error

[Former Member]

Hello,

we have to connect to a http server (HTTP with user authentication). I have tried both a HTTP receiver channel as well as a SOAP receiver channel (option "Do Not Use SOAP Envelope").

Connection using the SOAP receiver works without problem. If we switch to plain HTTP receiver (same connection details) we get the following error:

"HTTP client code 400 reason ICM_HTTP_CONNECTION_FAILED".

What could the reason for this? Probably related to the ABAP Stack?

Edited by: Florian Guppenberger on Jan 26, 2010 3:12 PM

[Former Member · Accepted solution]

can you create a HTTP RFC Dest in SM59?

You can test the connection there. If that works, then PI Comm Channel should work too.

what are you trying to do?

[Former Member · Accepted solution]

Yes, I have tested the connection on SM59. Was successful, still only the SOAP receiver channel works but not the HTTP receiver even if it is pointing to this SM59 connection.

I am wondering if this problem could be related to the http header data?

[Former Member · Accepted solution]

HTTP destination works but ur scenario fails, could be problem with the data u r sending

Also HTTP 400 is Bad Request (The request contains bad syntax or cannot be fulfilled)

Can you also check with the third party if they have a log for this message (may b rejected by their system too)

[Former Member · Accepted solution]

Yes, looks like the connection is rejected by the other system. However if this is really the case it is still strange that the http request sent by the SOAP receiver is not rejected.

I will check whether there are some logs available on the other system....

[MichalKrawczyk]

Hi,

>>>What could the reason for this? Probably related to the ABAP Stack?

check the log on ABAP for RFC dest from SM59

there you might see some more info

BTW

does PI/XI have access to this http sever ? (no firewalls etc?)

Regards,

Michal Krawczyk

[markangelo_dihiansan]

Hi Florian,

If you'll be using Plain HTTP with just a username and password, you can directly use the URL path instead of HTTP destination in your receiver settings. Please give it a try.

Hope this helps,

[Former Member]

Yes,

I have tried both options for the plain HTTP receiver:

1. Setting up a HTTP destination in SM59

2. Configuring URL and Password directly in the channel

Both of them have the same (negative) results, but URL / User / Password are the same as for the SOAP receiver...