Could not establish connection to Services Registry

[Former Member]

I have configured the Services registry as detailed in the following:

http://help.sap.com/saphelp_nwpi71/helpdata/en/45/c1ea61a1194432e10000000a155369/frameset.htm

http://help.sap.com/saphelp_nwpi71/helpdata/en/46/bb923d06582710e10000000a11466f/frameset.htm

But when i try and publish from the Integration Directory i get the following error:

Could not establish connection to Services Registry; configure connection to Services Registry in SAP NetWeaver Administrator and try again

also, when i display the WSDL, the Endpoints are not fully qualified.... how can these errors be rectified?

[Former Member]

OSS Note https://service.sap.com/sap/support/notes/1287938 covers this problem.

Symptom

You change the custom endpoint URL and the Web Services Navigator continues to invoke the URL that you entered before.

Other terms

Web Services Navigator, custom endpoint, invocation

Reason and Prerequisites

When you enter a new custom endpoint URL, the change does not take effect on the Web Services Navigator.

Solution

We recommend that you update your system with the latest available patch level for NetWeaver 7.10 SP8.

As a workaround you could simply change to the endpoint in WSDL and then back to the custom endpoint every time when you want to change the custom endpoint URL.

[marksmyth]

Hello Barry

Please try the following:

1. Login to Netweaver Administrator (NWA).

2. Click on the link 'SOA Management'.

3. Under 'SOA Management' click on the link 'Business Administration'.

4. Now go to the link 'Web Services Administration'.

5. Here search for Proxy definition with the name 'ServicesRegistrySi'

6. Now select the proxy definition such that its properties are

displayed.

7. Then go to the 'Configuration' tab and then select the proxy

definition again i.e ServiceRegistrySiPort

8. Now edit the proxy definition to point the WS Endpoint URL

http://<hostname>:<portno>/ServicesRegistrySiService/ServicesRegistrySiPort

Regards

Mark

[Former Member]

Hi Mark

Thanks but we got the link to the SR Working...

we had that already configured that as part of the install and it was working. there is an OSS note that said the same thing...

We had to do a system restore as the data got corrupted.

the other issue i thought was fixed does not write the FQDN/New URLs to the WSDL and I am opening an OSS Note for this.

[Former Member]

Okay...

the Endpoints can be fully qualified by selecting the "Options" button and overwriting the URL before publishing, but the same error persists where i cannot access the Services Registry from the Integration Directory...

The above (in bold)does not actually work and update the URLs for the endpoints.....

I can access the SR by visiting http://host.fqdn:5<sysno>00/sr

but there is no communication between SR and ID...