Invalid transport binding settingsHTTP Client, does not have endpoint url

[Former Member]

Hello,

I am testing a web service that I´ve just published succesfully from the ERP (WSPUBLISH transaction) from the WS Navigator. The WS has endpoints, but when I try to test it, it shows me the following error in a pop up window,

"Invalid transport binding settingsHTTP Client, does not have endpoint url specified."

Please, if you have any idea to solve this, it´s welcome.

Thanks

Regards

SU

[Former Member]

Hi Guys

we are trying to consume a webservice from CE 7.2 version and facing same issue.

We published the service from se80, created endpoint in soamanager and tested fine from SR.

But when trying to consume the service from VC component in NWDS and test the same we are getting

Invalid transport binding settingsHTTP Client, does not have endpoint url specified.

Any suggestions.

Regards

Sumana.

[Former Member]

Hi,

I have created WSDL direclty in BPM and deployed on the server CE 7.2 SP3. I am able to see the wsdl in WS navigator and when tried to test it it gives me ": Invalid transport binding settingsHTTP Client, does not have endpoint url".

I did the same in CE 7.1 and it works for me. Can any one please let me know the solution for this?

Regards,

Krishna

[Former Member]

It is very strange,

When I test the web service from http://localhost:port/sr, it does not work. But when I test it from http://localhost:port/wsnavigator it works fine. Why?

Regards

SU

[Former Member]

Hi,

did you create endpoint using SOAMANAGER?

Check there is url difference of wsdl in Service registry and WSNavigator.

Regards,

Gourav

[Former Member]

Hello Gourav,

I published the service through WSPUBLISH. In SOAMANAGER I was unable because it shows me the following error,

"Error retrieving Service Registry (SR) version information".

The main difference of the steps in the two transactions is that just after the executing, WSPUBLISH ask me for login to the SR and in SOAMANAGER I dont know why it didnt ask me and fail. (I am not sure where I have to change this parameter).

In the other hand, In /SR the WSDL is,

http://hostname:port/sap/bc/srt/wsdl/bndg_DEFF7D90B50663F197470017A4770400/wsdl11/binding/ws_policy/...

In /WSNavigator the WSDL is,

http://hostname:port/sap/bc/srt/wsdl/bndg_DEFF7D90B50663F197470017A4770400/wsdl11/allinone/ws_policy... - (I search this from soamanager transaction, and executing the wsnavigator from there).

Thanks

Regards

SU

Edited by: soauniverse on Jan 12, 2010 3:57 PM

Edited by: soauniverse on Jan 12, 2010 4:00 PM

Edited by: soauniverse on Jan 12, 2010 4:16 PM

[Former Member]

Hi,

>WSPUBLISH ask me for login to the SR

You need to provide correct user/id in configuration (these user id are for PI system) where as in SOAMANAGER you should use ECC password, recheck configuration in SM59.

I don't know why url is different in SR and WSNavigator but url in wsnavigator is correct one, I myself faced this issue in past but not remeber how did i solved it, will come back on this tomorrow.

Use url Wsnavigato url http://hostname:port/sap/bc/srt/wsdl/bndg_DEFF7D90B50663F197470017A4770400/wsdl11/allinone/ws_policy...

as it is correct one, other url doesn't have endpoint.

For problem related to SOAMANAGER connection to SR see SAP Note Number: 1319742 heading Services Registry Connection Setup.

Regards,

Gourav

[Former Member]

Hello,

Similar issue was fixed in 7.11 SP2, see note 1343014.

Thanks

Regards

SU

Edited by: soauniverse on Jan 15, 2010 3:06 PM