cancel
Showing results for 
Search instead for 
Did you mean: 

Webservice Consumption Soamanager Port Ping Error Release 7.31

0 Kudos

Hello,

I am trying to consume a Web service in Release 7.31. I did this in an older release and it works fine. I have imported the WSDL and created the Proxies and also a Logical Port (manually) with the same parameters as in the  older release. The Problem is I can not Ping the WebService in SOAMANAGER. By creating the Logical Port, an automatically RFC Connection in SM59 was created in release 7.0, but in 7.3 this feature is no more available.  The Error which occurs when I Ping the Service is Web service ping failed (RC=400). Service Ping ERROR: Bad Request. No trace or log is shown for the ping service. The 7.31 System was fresh installed.

What changes do I have to make, so that the Service Proxy would work?


Thank you in advance,

Best regards,

Flavius Frum


Accepted Solutions (1)

Accepted Solutions (1)

jimguo
Advisor
Advisor
0 Kudos

Hello,

After implemented note 1597000, the test operation uses HEAD method instead of GET. If the

external service provider does not support HEAD method, the error will appear.

Anyway, it does not mean the proxy is not working. You can try to test the proxy via SE80.

Hope this can help you.

Jim

0 Kudos

Hello Jim,

I thought the problem was that the Ping was not working and that's why I couldn't use the actual web service.

By analyzing the payload trace I discovered that the message format was changed. I set the parameter Message ID Protocol to Suppress ID Transfer and I could implement and use the web service.  I do not use / need the message protocol.

The Function Ping the Service is not working properly, so I think implementing your note, would change that, but in my case, it was not necessary.

Thank you,

Flavius

Answers (0)