Skip to Content
0

SOAP -XI 3.0 Proxy Error PO 7.5

Mar 20 at 06:34 AM

217

avatar image

Hi All,

I am working on PO 7.5 newly implemented system and in the Inbound Proxy while sending the Data from PO-->S4D system we get below error for all the scenarios in the system

we have done the required configuration in the S4 system

1)sxmb_adm-->Integrated engine configuration -->Associated Int server

2)HTTP RFC connection from s4D to PO system-works fine

3)HTTP destination created from PO to S4 system-works fine

4)Activated SICF XI engine services

Are we missing anything? Please suggest

Failed to call the endpoint: null

SOAP: Call failed: java.io.IOException: Error receiving or parsing request message: java.io.IOException: HTTP Error response for SOAP request or invalid content-type

using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: Error receiving or parsing request message: java.io.IOException: HTTP Error response for SOAP request or invalid content-type." tabindex="0" style="white-space:normal;">Transmitting the message to endpoint using connection File_http:// sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: Error receiving or parsing request message: java.io.IOException: HTTP Error response for SOAP request or invalid content-type

Thanks,

Guru

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

4 Answers

Dhivakar Muthusamy Mar 20 at 12:40 PM
0

Hi ,

If the receiver channel is configured with HTTP destination, Please ping the destination and check whether it give HTTP 500 response.

Check whether the Proxy implementation for this interface is active in ABAP system. This could also happen if your sending an TEXT/HTML message instead of xml.

Try implementing this to get a detailed error log in this case and investigate

https://blogs.sap.com/2015/10/26/http-tracing-in-soap-receiver-adapters-with-tracehttp-module-parameter/

Regards,

Dhivakar.

Share
10 |10000 characters needed characters left characters exceeded
Pavan Dogiparthy Mar 20 at 07:22 AM
0

Hi,

Is it synchronous or Asynchronous, If it is synchronous make sure that response mapping done at PO and ensure that S4D system able to provide response.

Might be error due to inbound proxy does not returning any response.

Regards

Pavan

Show 5 Share
10 |10000 characters needed characters left characters exceeded

Hi Pavan,

This is Asynchronous .

File to Proxy -FTP -->PO-->S4

The mapping is successful and the message is delivere

d to Receiver SOAP channel.

soaperror.jpg (105.4 kB)
0

Hi,

Adding to dhivakar point if that is the case

you can use MessageTransformBean with parameter

Transform.ContentType and with value text/xml.

Regards

Pavan

0

Hi GurudattaWouldn't you provide your request payload coming to S4?

Regards, Evgeniy.

0

The Issue is resolved now.

In the receiver channel we were using HTTP destination to s4 dev system which is the usually way in the SOAP receiver channel

But in this case using the URL destination in the "connection parameters" and giving the target URL of the s4d system followed by

/sap/xi/engine?type=entry solved the issue and the messages are delivered to the s4 dev system.

Thanks,

Guru

0

As issue got resolved. Please close the thread by accepting your answer as right answer.

Regards

Pavan

0
Marc A De Jesus Mar 22 at 07:55 AM
0

Hi Gurudatta,

Can you provide the request payload to further check this?

Thank you!

Regards,

Marc

Show 1 Share
10 |10000 characters needed characters left characters exceeded

The Issue is resolved now.

In the receiver channel we were using HTTP destination to s4 dev system which is the usually way in the SOAP receiver channel

But in this case using the URL destination in the "connection parameters" and giving the target URL of the s4d system followed by

/sap/xi/engine?type=entry solved the issue and the messages are delivered to the s4 dev system.

Thanks,

Guru

1
gurudatta d Mar 26 at 01:19 PM
0

Hi All,

The Issue is resolved now.

In the receiver channel we were using HTTP destination to s4 dev system which is the usually way in the SOAP receiver channel

But in this case using the URL destination in the "connection parameters" and giving the target URL of the s4d system followed by

/sap/xi/engine?type=entry solved the issue and the messages are delivered to the s4 dev system.

Thanks,

Guru

Share
10 |10000 characters needed characters left characters exceeded