A modern computing environment consists of a number of hardware and software components that depend on each other with regard to installation, software updates, and demands on interfaces. The SAP System Landscape Directory (SLD) simplifies the administration of your system landscape.
The SLD is a server application that communicates with a client application using the Hypertext Transfer Protocol (HTTP). The SLD server contains component information, a landscape description, and a name reservation, which are based on the standard Common Information Model (CIM). The CIM standard is a general schema for describing the elements in a system landscape. This standard is independent of any implementation.
The component description provides information about all available SAP software modules, as well as their combination options and dependencies. This includes version numbers, current patch level, and dependencies between landscape components.
For more information about the SAP System Landscape Directory, see SAP Help Portalhelp.sap.com.
To supply data to the SLD that originates from a system other than a J2EE or ABAP system, the executable sldreg is used. The sldreg sends data in XML format using a predefined DTD. For this purpose it uses an HTTP connection, as shown in the figure below:
On the TREX host, there is an SLD client, which generates an XML file of this type and which registers itself with the SLD server using sldreg.
The slddest.cfg.key file is only available if the configuration of sldreg was generated using the - usekeyfile parameter.
Generating SLD Configuration Files
In case you generate the SLD configuration files (slddest.cfg and slddest.cfg.key) by yourself you have to know the host, port, user and password of the SLD server. You generate these configuration files by using the executable files which are located on your TREX host.
Copying the SLD Configuration Files to the Global SLD Directory
To configure TREX for the System Landscape Directory (SLD), you copy the SLD configuration files slddest.cfg and slddest.cfg.key (if available) to the global SLD directory on your TREX host.
This directory is called <disk_drive>:\usr\sap\<SAPSID>\SYS\global on Windows and /usr/sap/<SAPSID>/SYS/global on UNIX. In the case of a distributed TREX installation on Windows, all TREX instances use the configuration files for the TREX global file system with first TREX instance as \\<host_central_instance>\sapmnt\<SAPSID>\SYS\global.
By copying the files slddest.cfg and slddest.cfg.key, you have configured TREX for integration in the System Landscape Directory (SLD).
TREX checks every five minutes whether anything has changed in the TREX system landscape and reports any changes automatically to the SLD server. If nothing has changed, TREX reports every twelve hours to the SLD server. This allows you to see that this landscape is still active.
Information Transferred to the SLD Server
TREX transfers the following information to the SLD server:
Information about naming and version
Information about the TREX servers
Information about the TREX instances on individual hosts
Information about the TREX configuration
Possible roles are: 1st, 2nd, 3rd Master Name Server, Slave Server