WSDL without endpoint in Services Registry

[Former Member]

Hi,

I have successfully configured an enterprise service from ECC 6.0 by following this tutorial ([Configuration of Enterprise Services using SICF and SOAMANAGER|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/20b723f8-a422-2c10-aca5-fe64eeda1ff2&overridelayout=true]). After the configuration, I published the enterprise service to the Services Registry using WSPUBLISH.

However, when I tried to consume the service in Visual Composer, I got a connection error. Later, I discovered that it was due to the binding WSDL generated in SOAMANAGER in which the endpoint port was automatically set to 443 instead of 8001 (my http port). Luckily enough, I have found an identical problem posted to SDN forum ([soamanager referencing wrong port number in wsdl document |;). From there I learned that an SAPNOTE 1263112 must be uploaded to my ERP. Now, this problem is solved.

Nevertheless, after I have built a VC model that consumes the service, which is now found in the Services Registry, deployed and run it, I got this error message "Error in connection: Could not execute Web service, consult your administrator". To investigate the source of the problem, I copied the URL of the WSDL generated in SOAMANAGER from the link Open WSDL document for selected binding and created a logical destination in NWA for the direct consumption in VC. This time, the VC model worked!

This lead me to think that the problem lies in the binding WSDL in Services Registry. So, I checked the SR again and found that the URL for the binding WSDL in the "Endpoint" tab is different from the one in SOAMANAGER:

1. In SR

http://myserver:8001/sap/bc/srt/wsdl/bndg_4AAD0B64E0BC0263E1008000C0A8A53D/wsdl11/binding/ws_policy/...

2. In SOAMANAGER

http://myserver:8001/sap/bc/srt/wsdl/bndg_4AAD0B64E0BC0263E1008000C0A8A53D/wsdl11/allinone/ws_policy...

The binding WSDL in SR does not contain the endpoint. However, the endpoint is shown in the 2nd column "Target Address" of the endpoint table in "Endpoint" tab.

To summarize, I could not consume service that was configured in SOAMANAGER and subsequently published to SR. But, with the WSDL in SOAMANAGER, the service could be directly consumed.

Does anyone have idea about this problem?

Thanks in advance.

Regards,

Joon Meng

[Former Member]

Hi,

Usually endpoint in SR is published as per SOAMANAGER (allinone/ws_policy/document?sap-client=800). Try to republish service again using "WSPUBLISH" with endpoint and chose "force publication" option.

You can also publish service using url directly from SR (goto "publish" tab).

Regards,

Gourav

[Former Member]

Hi Gourav,

So far I have published all the services only in "WSPUBLISH" with the option "Service definition & endpoints" and "Force publication". And I have tried to republish but the result was the same.

Can I provide classification information if I publish the service directly in SR?

Regards,

Joon Meng

[Former Member]

Hi,

Yes you can provide classification while publishing services from SR (atleast in PI 7.1 Ehp1).

Regards,

Gourav

[Former Member]

Hi,

After some research I found that SAP Note 1113161 describes the problem I encountered. The only difference is that it is caused by WSCONFIG, whereas I have problem with SOAMANAGER. I will check it out with the Basis guy.

Regards,

Joon Meng

[Former Member]

Hi Joon Meng,

I am experciencing the same issue you describe.

Did this note solved your problem ? (i guess you were talking about note 1113162)

Thanks for your feedback.

Br

Remi

[Former Member]

Hi,

any update about this?

thanks,

joon meng