Configuring TREX for the System Landscape Directory (SLD) 

Use

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 Portal help.sap.com ® Documentation ® SAP NetWeaver ® SAP Library ® SAP NetWeaver ® Application Platform ® Java Technology in SAP Web Application Server ® Administration Manual ® Server Administration ® SAP System Landscape Directory

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.

Prerequisites

·        After the TREX installation, the SLD client and the associated executable files are located on your TREX host:

·        The administrator of your SAP system landscape has fulfilled the following prerequisites:

¡        The SLD server is running.

¡        The administrator has 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.

For more information about configuring sldreg, see the SAP Service Market Place service.sap.com/installnw2004s and read the Configuration of Data Suppliers section of the Post-Installation Guide – System Landscape Directory.

¡        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.

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 dialog instances use the configuration files for the central instance as \\<host_central_instance>\sapmnt\<SAPSID>\SYS\global

Result

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

·        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

·        System ID

·        Instance number

·        Installation directory

·        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)