Technical Communication at Design Time 
The Enterprise Services Repository is the central store for SAP NetWeaver design objects for service development and their related metadata.
Connection |
Protocol |
Stored in |
To the System Landscape Directory to Load Software Component Versions |
HTTP |
Destination Service Authorization: Username/Password Role: SAP_SLD_GUEST |
To the Services Registry to Publish Service Interfaces |
HTTP |
Client Proxy on the AS Configuration in NetWeaver Administrator under Client Proxy Name: ServicesRegistrySi Authentication: User name/password Role: SERVICES_REGISTRY_READ_WRITE |
Each AS Java has a local Services Registry. If there are multiple AS Javas in your system landscape, select one registry to be the central registry. Here you can publish Web services of the system landscape.
To configure the Services Registry, you must create a connection to the UDDI server and to the classification service.
Connection |
Protocol |
Stored in |
To the UDDI Server |
HTTP |
SAP NetWeaver Administrator: UDDI_DESTINATION Basic Authentication |
To Classification Service |
HTTP |
SAP NetWeaver Administrator: CLASSIFICATION_DESTINATION Basic Authentication |
You can access the central Services Registry under: http://<hostname>:<port>/sr_central.
Connection |
Protocol |
Stored in |
AS Java |
HTTP |
To enable authentication for provider WSDL access, for service Web Services Container, set system property wsdl.security to true. You can use the following autheticationmethods:
|
Connection |
Protocol |
Stored in |
To the Enterprise Services Repository (Enterprise Services Repository Browser) |
HTTP |
IDE under . |
To the Services Registry to Publish Service Definitions and Service Endpoints |
HTTP |
SAP NetWeaver Administrator Proxy Definition Name: ServicesRegistrySi Basic Authentication |
Connection |
Protocol |
Stored in |
To the Services Registry |
HTTP |
Connect to Services Registry Basic Authentication You can access the central Services Registry under: http://<hostname>:<port>/sr_central. |
DIAG and RFC connections can be protected using Secure Network Communications (SNC). HTTP and RMI P4 connections are protected using the Secure Sockets Layer (SSL) protocol.
For more information see the SAP NetWeaver security guide under: Transport Layer Security