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
As of SAP Solution Manager Release 7.1, changes to technical systems can only be made in the Technical System Editor of the LMDB. You still manage your product systems in the Solution Manager System Landscape (transaction SMSY). Some applications of SAP Solution Manager still retrieve their landscape information from transaction SMSY.
Integration with the Landscape Verification Tool
You can use the Landscape Verification Tool to analyze whether your system landscape has been maintained correctly in the Solution Manager system landscape (transaction SMSY). We recommend that you perform this analysis before migrating data from transaction SMSY to the LMDB to ensure that all of the required information is available in transaction SMSY. For more information, see Landscape Verification Tool.
You make settings for the LMDB in the SAP Solution Manager configuration (transaction SOLMAN_SETUP or work center SAP Solution Manager: Configuration). To do this, in the System Preparation, for the step Prepare Landscape, choose the substep Set Up LMDB.
You can also adjust various configuration parameters in customizing for SAP Solution Manager, if required. To do this, in customizing for SAP Solution Manager, choose the path
To describe the landscape elements, the LMDB, like the SLD, uses the SAP extension of the Common Information Model (CIM) of the Distributed Management Task Force (see also www.dmtf.org). Typical elements in this model are “computers”, “systems”, “products”, and “software components”.
In the technical view, the LMDB displays the mapping of the Java SLD implemented in ABAP. The cooperation of the SLD and the LMDB takes place using a connection to sychronize the contents, which works on the same principle as the synchronization between two SLD systems. It is therefore possible to read all data from the LMDB that already exists in the SLD. The cooperation between the SMSY and the LMDB takes place on the one hand with the possibility to migrate data from SMSY to LMDB and on the other hand with the automatic synchronization from LMDB to SMSY.
The figures below illustrates the interaction between the SLD, SMSY, and the LMDB in a system landscape, based on the recommended configuration:
Configuration 1: The systems in the system landscape are registered with a remote SLD (1a). From here, the data is synchronized to the LMDB (2a). The SMSY synchronization (3) and, if necessary, the migration (4) are carried out from the LMDB. This is the recommended configuration.
Configuration 2: A variant would be the additional use of a local SLD in SAP Solution Manager, which is filled using Data Supplier Forwarding (1b) and provides the LMDB with data from there (2b). This configuration does not contain all the data. For this reason, it is not suitable for PI monitoring.
Configuration 3: In another variant, without a remote SLD, the systems register directly with the local SLD (SLD 7.0) (1c).
As part of SAP Solution Manager, the LMDB provides information about the system landscape and the available SAP software. This information is used by applications within and outside SAP Solution Manager through an access layer. The applications then influence the system landscape based on this information. This then leads, in turn, to the updating of the data in the LMDB.
The contents of the LMDB are supplied from the following sources, independently of the technical data flow:
System Data Supplier
Automatic system registration is the preferred method for providing the LMDB with landscape elements. The data suppliers are implemented in the different systems. Most of the data suppliers currently report their data to the SLD, for example, AS ABAP using transaction SLD Administration (RZ70). This data is transferred 1:1 to the LMDB through the synchronization of contents between the SLD and the LMDB. A smaller number of data suppliers write data directly to the LMDB.
Technical System Editor
Manual system registration in the technical system editor is intended for cases where there is no data supplier, or where the data supplier cannot be used, for example due to a firewall. The biggest disadvantage of this manual method is that there is no way to automatically update the data, since data entered manually can become obsolete after a certain period.
Migrating Data from Transaction SMSY to the LMDB
The data migration from SMSY to the LMDB is a special data supplier. The step integrated into the configuration of SAP Solution Manager (transaction SOLMAN_SETUP) enables data entered in SMSY to be transferred to the LMDB.
Download of the SAP Software Catalog
The data about the usable products and software components is provided using the SAP Service Marketplace (SMP). This SAP CR CONTENT can currently only be imported into an SLD. This data is transferred 1:1 to the LMDB through the synchronization of contents between the SLD and the LMDB.
For more information, see SAP Note 669669.
Downloading the SAP CIM Model
The current SAP CIM model is also part of the software component SAP CR CONTENT and is imported into the LMDB via the SLD in the same way as the SAP software catalog.
For more information about the LMDB, see the LMDB Setup Guide on SAP Service Marketplace at http://service.sap.com/solutionmanager .
For more information about setting up a system landscape and using SLDs, see the System Landscape Directory Planning Guide in the SAP Community Network at http://www.sdn.sap.com/irj/sdn/nw-sld.
More information about the CIM model used in the LMDB and SLD is also available under the same link.