Technical System Landscape at Design Time 
Web Services System Landscape
The following components are involved in technical communication:
The technical system landscape is mapped in the System Landscape Directory (SLD).
From which SLD are software component versions loaded on the Enterprise Services Repository.
If the SLD is not part of the system landscape then only local software components can be created in the ES Repository.
In the Enterprise Services Repository the Enterprise Services Builder provides objects for modeling services. User access to these objects can be made using the UI Client.
Service interfaces from the Enterprise Services Repository can be published in the Services Registry.
The service provider is an AS Java.
You perform the proxy generation in AS Java in the Integrated Development Environment.
The Web service and Web service client configuration is provided in the SAP NetWeaver Administrator.
Web services are published in the Services Registry.
Service interfaces from the Enterprise Services Repository can be published in the Services Registry.
Service definitions and service endpoints from the Application Server (SAP NetWeaver Administrator) can be published in the Service Registry.
The basis of the Services Registry is the classification service and an UDDI server v3.0 of the AS Java. Each AS Java provides a local Services Registry. Configure one of these registries as the central registry in your system landscape.
The service consumer, an AS Java, searches for and finds the service definition in the Services Registry.
The service consumer generates and implements the consumer proxy in AS Java.