Content Preview:

Post-Installation Guide: SAP System
Landscape Directory on SAP Web AS 6.40
Today, system landscapes consist of multiple distributed software components with different platform
dependencies, different interfaces, and different requirements regarding installation and change
management. An overall concept is required that facilitates the implementation, upgrade, and maintenance
of even the most complex system landscapes. This is where SAP System Landscape Directory (SLD)
comes into play. SLD acts as a central information provider where comprehensive information about all the
installable and installed elements of your system landscape is stored.

1. Introduction
SLD is the central information provider for the whole system landscape. Generally, SLD is deployed after the
installation of each SAP Web Application Server Java 6.30 or higher. Nevertheless, to bring the SLD server
into operation, it has to be configured and activated.
This documentation includes the following information:
???? Network topologies for using SLD in different scenarios
???? Post-installation of the SLD server
???? Configuration of data suppliers for SLD
???? Configuration of SLD clients that use the ABAP API for SLD
This documentation does not contain information about installing the SAP Web Application Server. For more
information, see the Installation Guide – SAP Web Application Server Java on…

As previously mentioned, the SLD server acts as a central information provider for the enterprise system
landscape. Therefore, the most common installation scenario is that all systems inside a system landscape
including all sub-networks share a single SLD server.

Download SAP System Landscape Directory on SAP Web AS Java 6.40.Pdf:

[smartads]
Download file