Technical System Landscape at Design Time

This graphic is explained in the accompanying text.

The following components are involved in technical communication:

The technical system landscape is mapped in the System Landscape Directory (SLD).
The SLD is based on the Application Server (AS) Java. From SLD, software component versions are loaded to the Enterprise Services Repository.
In the Enterprise Services Repository the Enterprise Services Builder provides objects for modeling services. Users access these objects using the UI Client.
The Enterprise Services Repository is based on AS Java. Service interfaces from the Enterprise Services Repository can be published in the Services Registry. The Enterprise Services Repository and Services Registry are part of SAP NetWeaver Composition Environment or SAP NetWeaver Process Integration.
The service provider is an AS ABAP.
You generate proxies in transaction SE80 in AS ABAP.

You configure ABAP Web Services with transaction SOAMANAGER.
Web services can be published to the Services Registry.
- Service interfaces from the Enterprise Services Repository can be published in the Services Registry.
- From AS ABAP you can publish service definitions and service endpoints in the Services Registry.
The basis of the Services Registry is the classification service and a UDDI server v3.0. Each AS Java has a local Services Registry. Configure one of these registries as the central registry in your system landscape.
The service consumer, an AS ABAP, searches for and finds the service definition in the Services Registry.
The service consumer generates and implements the consumer proxy in AS ABAP.

For more information about the technical system landscape, see the resources listed in the table below.

Topic	Guide/Tool	Quick Link to the SAP Service Marketplace
Technical description of Web services and the underlying components such as SAP NetWeaver	Master Guide	`service.sap.com/instguides`
Security		`Service.sap.com/security`