Technical Communication at Design Time

Connection from ES Repository to System Landscape Directory

The System Landscape Directory (SLD) contains information about the technical communication of the involved systems at design time. In the ES Repository use the system properties com.sap.aii.connect.cr.name and com.sap.aii.connect.cr.httpport to connect to the SLD.

Enterprise Services Repository

The Enterprise Services Repository is the central store for SAP NetWeaver design objects for service development and their related metadata. The Enterprise Services Repository is an AS Java application and is available to you, if you have SAP NetWeaver Process Integration or SAP NetWeaver Composition Environment in your system landscape.

Connection	Protocol	Stored in
Between Enterprise Services Repository Client and Server	RMI P4	Properties com.sap.aii.connect.rmi.protocol, com.sap.aii.connect.repository.rmiport.ssl
To the System Landscape Directory to Load Software Component Versions	HTTP	Create technical user ESRSLD<SID> Authentication: User name/password Assigned roles: SAP_XI_IR_SERV_USER and SAP_SLD_CONFIGURATOR
To the Services Registry to Publish Service Interfaces	HTTP	Client Proxy on the AS Configuration in SAP NetWeaver Administrator under SOA Management Application and Scenario Communication Single Service Administration Client Proxy Name:ServicesRegistrySi Authentication: User name/password Role: SERVICES_REGISTRY_READ_WRITE

Services Registry (Optional)

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, there must be a connection to the UDDI server and to the classification service.

Connection

Protocol

Stored in

To the UDDI Server

HTTP

SAP NetWeaver Administrator: SOA Management Technical Configuration Destination Template Management

UDDI_DESTINATION

Authentication: User name/password

To Classification Service

HTTP

SAP NetWeaver Administrator: SOA Management Technical Configuration Destination Template Management

CLASSIFICATION_DESTINATION

Authentication: User name/password

You reach the Services Registry under: http://<hostname>:<port>/sr_central.

Service Provider System (AS ABAP)

Connection

Protocol

Stored in

To the Enterprise Services Repository

(Enterprise Services Repository Browser)

RFC

RFC connection:

RFC Destination: SAP_PROXY_ESR

Target Host: Server Name or IP address

Service Number: Port number

Path Prefix: /rep

To the Services Registry to Publish Service Definitions and Service Endpoints

HTTP

Transaction SOAMANAGER Service Administration Single Service Administration Consumer Proxy

Proxy for Services Registry: CO_SERVICES_REGISTRY_FLAT_SI

Authentication: User name/password, SAP authentication assertion ticket

Access to Provider WSDL

Connection

Protocol

Stored in

AS ABAP

HTTP

Transaction SOAMANAGER Service Administration Single Service Administration Service

Authentication: User name/password

Service Consumer System

Connection	Protocol	Stored in
To the Services Registry	HTTP	Call the central Services Registry by using the following address: `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:

Configuring the AS ABAP for Supporting SSL