Show TOC

Function documentationLandscape Management Database (LMDB)

 

The SAP Solution Manager landscape management database (LMDB) is the central landscape information repository. A system landscape description is the basis for almost all SAP Solution Manager applications, like Monitoring and Alerting. To calculate updates and upgrades with the maintenance planner in SAP Support Portal, a landscape description is required.

SAP Solution Manager collects and stores detailed information about the technical system landscape. This information is built from two parts: the software descriptions from the SAP software catalog (SAP CR content) and the information that is sent automatically by technical systems via the system landscape directory (SLD).

System Information Flow in the Landscape

The following graphic describes how system information is distributed in the landscape:

  1. Set up data suppliers to register technical systems automatically in the System Landscape Directory (SLD).

  2. Most of the system information in the LMDB is provided by synchronization with a system landscape directory (SLD) in the system landscape, which continuously gathers data sent by the data suppliers that are installed on the technical systems. Smaller amounts of information in the LMDB are created manually. The SMD agent (Outside Discovery) writes directly into the LMDB.

    During the setup of SAP Solution Manager, the landscape description, CIM model, and SAP Software Catalog (SAP CR content) are copied from the SLD to the LMDB by an initial, full synchronization. After this, incremental synchronization propagates system changes from the SLD to the LMDB every 10 minutes.

    For more information, see Connecting LMDB to System Landscape Directory (SLD).

  3. a. The SAP Solution Manager applications use the system information managed in the LMDB, for example change control management, monitoring and alerting, and root cause analysis.

    b. With the system information, applications can monitor systems in the landscape.

  4. From the LMDB, technical system information is sent to SAP Support Portal, to be used by the maintenance planner, for example.

  5. Based on the dependencies between technical systems, the maintenance planner can calculate the stack XML files that are required for planned installations, upgrades, and updates. The files are pushed to the download basket.

  6. With the files, you can implement new software on the technical systems.

Integration

Sources Providing LMDB Content

The LMDB derives its content from the following sources:

  • System Landscape Directory (SLD)

    By synchronization, the SLD provides the LMDB with the latest data from the data suppliers, which are installed in the technical systems. This includes the SAP software catalog (SAP CR content) and the CIM model.

    For more information, see Connecting the LMDB to System Landscape Directory (SLD).

  • Outside Discovery

    The SMD agent provides the Outside Discovery information and writes landscape data directly into the LMDB, to be used by diagnostics.

    For more information see the following Wiki pages: http://wiki.scn.sap.com/wiki/x/yoEtCgInformation published on SAP site and http://wiki.scn.sap.com/wiki/x/n4efFgInformation published on SAP site.

  • Editor for Technical Systems in the LMDB

    Some information, like business partner information or additional attributes, can only be created manually in the technical system editor of the LMDB. Apart from these exceptions, do not create system information manually. If the system is registered subsequently by an SLD data supplier, manual information cannot be overwritten because the LMDB has a higher rank than the SLD. You would, therefore, have to update manually created data manually, in the future, and it can become obsolete.

    For more information, see Editing Technical System Information.

A technical system description in the LMDB has the following prerequisites:

  • Up-to-date CIM model and SAP CR content in the SLD that is connected to the LMDB.

  • Active synchronization between the LMDB and the SLD.

  • All technical systems register themselves in the SLD.

Some SAP Solution Manager applications may require additional configuration, such as grouping technical systems.

Do not create and edit technical system information manually. For more information, see Managing Technical System Information. Some information, however, needs to be created manually, such as additional attributes or business partner information.

Many entities in the system landscape description are identified partly by host names (not fully-qualified and case insensitive). For this reason, every host (server) in the landscape must have at least one unique host name. It is used in the system configuration, which is essential for the system landscape description. For example, the host name “localhost” cannot be used in this part of the system configuration. For more information, see SAP Note 1052122Information published on SAP site.

  • As of SAP Solution Manager 7.1, the LMDB is mandatory for managing technical system information in SAP Solution Manager.

  • The Solution Manager Systems storage (transaction SMSY) is disabled with SAP Solution Manager 7.2. See Deactivation of Transaction SMSY.

  • As of 7.2, the entity "product system" is no longer used. Instead, software maintenance dependencies between technical systems are modeled in the maintenance planner in SAP Support Portal.

More Information