Landscape Management Database (LMDB)

The Landscape Management Database (LMDB) is a directory of elements of a system landscape. The core task of the LMDB is to provide information about the entire system landscape at a central location. The Solution Manager System Landscape (SMSY) and the System Landscape Directory (SLD) already provide this function with different technologies for different applications. The aim of the LMDB is to unify the SLD and SMSY in SAP Solution Manager. The LMDB is supplied with data automatically, in as far as this is possible.

                               

Integration with the System Landscape Directory
Data suppliers exist for most technical systems and automatically register these systems in the System Landscape Directory (SLD). The SLD, therefore, is the central data source for the LMDB. Changes to technical systems should be carried out in the SLD where possible.
Integration with the Solution Manager System Landscape


For information on the advantages of the LMDB with regards to the previous SMSY storage, see the SCN blog Evolution of landscape data management - What's better with LMDB?
SAP Note 1679673 explains the most important differences between LMDB and SMSY.

There is a clear separation of tasks in System Landscape Directory (SLD) and LMDB:

The SLD is the target for self-registration of technical systems in the IP landscape. This technical systems information is provided for applications in non-productive and productive applications such as SAP NetWeaver Process Integration and WebDynpro (Java) based applications that need this information. Because of the productive use of the data it provides, often many SLD systems are used in customer landscapes (see SLD Topology: How-To Gather and Distribute SLD-Data in Your IT-Landscape).

The LMDB retrieves technical system information from the SLD as a basis for landscape data, to manage technical systems in monitoring and maintenance processes. It acts as a single source of truth in SAP Solution Manager. It provides a centralized UI approach to landscape verification functions and transaction SMSY.

As of SAP Solution Manager 7.1 SP0-4, the LMDB manages information about technical systems, hosts.

As of SP5, the LMDB also manages product system information.

Transaction SMSY is the "old" system information storage, being replaced by the LMDB bit by bit.

Up to SAP Solution Manager 7.1 SP4, SMSY is still used to manage product system information, but gets all technical systems information from the LMDB.

As of SP5, SMSY is only used to manage project-related data (logical components and solutions); the required data (technical systems and product systems) ar edited and provided by the LMDB (see New in SP05: Product System Editor in the Landscape Management Database of SAP Solution Manager 7.1).

                               

As of SAP Solution Manager 7.2, SMSY does not exist any longer. See Deactivation of Transaction SMSY.

The separation of roles is reflected in the architecture: Technical systems can register only in the SLD. All data changes in the SLD are retrieved immediately by the LMDB, as well as the CIM model and the CR content (SAP software catalog). Because both SLD and LMDB are needed in one landscape; without an SLD connected, LMDB cannot work AND data in SLD and LMDB must be consistent and must not overlap.