Quantcast
Channel: SCN : Unanswered Discussions - ABAP Development
Viewing all articles
Browse latest Browse all 8768

Configure web service + logical port

$
0
0

Hi guys!

 

I have to consume a web service which is installed on a remote System (MS SQL Server). After some issues (activate services in SICF, configure firewall) I was able to generate the client proxy in SE80. For doing this I used the URL to the WSDL file. You can find the WSDL file attached to this post.

 

Right after this I created the Logical port using Transaction SOAMANAGER (as LPCONFIG is obsolete). I wanted to generate the Logical port based on the WSDL again so I used the the same URL as in SE80. But this time I receive an error (I faced this error many times in different situations in SOAMANAGER too).

 

Error: HTTP: Error in Interface for Management of HTTP destinations

WSDL_ERROR.png

So I uploaded the WSDL by hand and I coudl generate the logical point. I can find my connection in SM59 (interessting: even if I received the error before SOAMANAGER creates a Connection in SM59 but I don't find it in SOAMANAGER).

 

When I perform a Connection test for my SM59 Connection (created via SOAMANAGER using the Manual upload of the WSDL file) I receive an error: HTTP/1.1 400 Bad Request

 

SM59_ERROR.png

 

I have tested my Client proxy in SE80 using the same Logical point. As expected I receive here an error too. The error message is not very helpful to me (I have implemented the note 1424747).

 

SE80_ERROR.png

 

Same error I reveive in my test report where I consume the web service.

 

TESTREPORT_ERROR.png

Does anybody has any idea about the problem? Could it be that a Service in SICF is missing so that the Logical point is not generated proper? Could it be that the firewall still blocks something? Or is it an error that occurs in the remote System and I simply don't reveive a clear error message?

 

Thanks a lot and kind regards,

Florian


Viewing all articles
Browse latest Browse all 8768

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>