When you have more than one system in your landscape with Services Registry installed, you have to select one of them to be the central Services Registry in your system landscape. Each AS Java has a local Services Registry. If you have Process Integration (PI) or Composition Environment (CE) installed in your system landscape, for example, 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.
The user account you use should be assigned to the SAP_JAVA_WS_ADMIN_BIZ role. For more information, see Authorizations .
Creating a Connection to the Central Services Registry
To start SAP NetWeaver Administrator, enter the following address in a Web browser:
On the Consumer Proxies tab, enter ServicesRegistrySi in the Find field and choose Go .
Select ServicesRegistrySi .
On the Configuration tab, select ServicesRegistrySiPort .
On the General tab, change the WS Endpoint URL to the one of your central Services Registry.
The URL must be in the following format: http://[host]:[port]/ServicesRegistrySiService/ServicesRegistrySiPort
On the Security tab, set the authentication method for the Services Registry
Select either User ID/Password (Basic) or Logon Ticket .
Apply at least basic authentication.
Select Details and enter the user ID and password of a user account on the system that hosts the central Services Registry.
The following roles must be assigned to the technical user account you specify at this step:
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_Admin.
Maintaining the Connection to the Central Services Registry
The system that you have configured to use a central Services Registry connects to it using the credentials of a user account on the system that hosts this Services Registry. In case this user account expires, your system would not be able to connect to the central Services Registry and can behave like it is not configured. In such situation, you can do the following:
Navigate to the Security tab as described above, and check if authentication type is set to User ID/Password (Basic) .
If this is the case, check whether the user and the password that are entered are correct.
You can check if the password is not expired by trying to log on with the user and password to the system that hosts the central Services Registry.
If the password is expired the system can ask you to change it. Change the password, or request an administrator on this system to do this.
After changing the password, make sure the user account has been used for logging in at least once before you use it to configure a central Services Registry on another system.
On your system, enter the new password into the Security tab as described above and save the changes.
If this user and password are used for other configurations update them too.
Try to access the central Services Registry from your system.
Access the central Services Registry using the following address: http://[host]:[port]/sr_central .