Configuring a Central Services Registry 

Use

Select one Services Registry to be the central one in your system landscape. Each AS Java has a local Services Registry. If you have for example  Process Integration (PI) or Composition Environment (CE) installed in your system landscape, each Java AS instance can play the role of this central Services Registry.

All other systems in the landscape publishing their Web services have to be configured to point to this central Services Registry.

Procedure

...

       1.      To start SAP NetWeaver Administrator, enter the following address in a web browser:

http://<host>:<port>/nwa

       2.      Choose SOA Management → Business Administration → Web Services Administration.

       3.      In the Search by field select Proxy Definition Name and enter ServicesRegistrySi in the Value field.

       4.      From the result list select ServicesRegistrySi.

       5.      In the Configuration tab, select the logical port ServicesRegistrySiPort and choose Edit.

       6.      In the Details section in the URL field adjust the wsdl URL of the Services Registry to the one of the central Services Registry.

http://<host>:<port>/ServicesRegistrySiService/ServicesRegistrySiPort

       7.      In the Security tab specify all security settings and save.

○       Apply at least basic authentication (HTTP authentication).

○       Select Details and enter the User ID and password.

Use a technical user for this connection.

The following roles have to be assigned to Services Registry users:

■       For read access: SERVICES_REGISTRY_READ_ONLY and the UDDI role UDDI_Tier1

■       For unlimited access to Services Registry content: SERVICES_REGISTRY_READ_WRITE and the UDDI role UDDI_TierN

More information: User Roles for the UDDI