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, 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 the SAP Help Portal help.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 that generates an XML file of this type and registers itself with the SLD server using sldreg.
After the TREX installation, the SLD client and the associated executable files are located on your TREX host.
The SLD server is running.
You or your SLD administrator have generated the SLD configuration files slddest.cfg and slddest.cfg.key.
The slddest.cfg.key file is only available if the configuration of sldreg was generated using the - usekeyfile parameter.
The user specified in the SLD configuration file slddest.cfg belongs to the DataSupplierLD user role, in order to have permission to send the files to the SLD.
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.
Set the environment variables required by TREX by executing the following scripts in a command prompt in the directory <TREX_DIR>:
Bourne shell sh, Bourne-again shell bash, Korn shell ksh:
C shell csh:
Execute the following commands:
Without the usekeyfile parameter: sldreg -configure <path>/slddest.cfg
With the usekeyfile parameter: sldreg -usekeyfile -configure <path>/slddest.cfg
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.
To display the information about TREX systems and services navigate to the screen Content Maintenance
On the initial screen for the
In the initial screen for the
In the screen Content Maintenance navigate to Subset and choose All With Instances in the dropdown list.
Navigate to Class. The dropdown list displays the TREX services (for example TREX Index Service, TREX Name Service) and systems recognized by the SLD.
Information Transferred to the SLD Server
TREX transfers the following information to the SLD server:
Information About Naming and Version
Software component version (for example, TREX 7.0)
SAP name (for example, TREX)
Version (for example, 7.0)
Information About the TREX Servers
Host name, on which the server is running
Port number that the server is using
Type of server, for example, indexserver
Web server URL (instead of the port)
RFC destination of the RFC server (instead of the port)
Information About the TREX Instances on Individual Hosts
Version information for the TREX software
Information About the TREX Configuration
Name of the TREX hosts ( Hosts) that belong to the TREX system landscape
TREX server roles
Roles of the TREX name server ( Name Server Mode)
Possible roles are: 1st, 2nd, 3rd Master Name Server, Slave Server
Use as master index server or master queue server
Roles of the master, slave, and backup index servers
TREX preprocessor mode ( Preprocessor Mode)
Information about the TREX installation directory ( Base Path)
Services that have been started by the TREX daemon ( Services)