Show TOC

Procedure documentationConfiguring a Central Services Registry Locate this document in the navigation structure

 

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

Creating a Connection to the Central Services Registry

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

    http://[host]:[port]/nwa

  2. Choose   SOA Management   Application and Scenario Communication   Single Service Administration  .

  3. On the Consumer Proxies tab, enter ServicesRegistrySi in the Find field and choose Go.

  4. Select ServicesRegistrySi.

  5. On the Configuration tab, select ServicesRegistrySiPort.

  6. 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

  7. On the Security tab, set the authentication method for the Services Registry

  8. Select either User ID/Password (Basic) or Logon Ticket.

    Apply at least basic authentication.

  9. 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_TierN.

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:

  1. Navigate to the Security tab as described above, and check if authentication type is set to User ID/Password (Basic).

  2. 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.

  3. 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.

  4. 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.

  5. Try to access the central Services Registry from your system.

Result

You can access the central Services Registry using the following address: http://[host]:[port]/sr_central.