Show TOC

Background documentationIntegration of System Landscape Management


System Information Flow in the Landscape

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

These are the steps that distribute technical system information in the system landscape and in SAP Solution Manager:

  1. Set up data suppliers to automatically register technical systems in the System Landscape Directory (SLD). You can use the following tools:

    • transaction RZ70 (for ABAP technical systems)

    • Visual Administrator or SAP NetWeaver Administrator (for Java technical systems)

    • SLD data suppliers based on the sldreg executable (for third-party systems)

    • SLD data suppliers based on other HTTP clients

    For more information, see Registering Technical Systems Automatically by Data Suppliers.

  2. The Landscape Management Database (LMDB) content is initially provided by full, automatic synchronization from SLD to LMDB, which copies the landscape description, CIM model, and SAP Software Catalog (SAP CR content) to the LMDB. Incremental synchronization propagates system changes from the SLD to the LMDB every 10 minutes.

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

  3. Technical system descriptions are continuously synchronized from the LMDB to the SAP Solution Manager System Landscape storage (transaction SMSY) to keep SMSY up-to-date. SMSY is an older storage for system landscape information and is still used by some applications.

    For more information, see Automatic Synchronization from LMDB to SMSY.

    3*: You can migrate system descriptions that were created manually in SMSY to the LMDB once during the LMDB setup. There is no need to re-create this data, manually, in the LMDB. For more information, see Migrating System Information from SMSY to LMDB.

  4. The SAP Solution Manager applications use the system descriptions in the LMDB. For example, Maintenance Optimizer calculates maintenance transactions based on this information.

  5. With the system information, applications can monitor and maintain systems in the landscape.

Sources Providing LMDB Content

The LMDB derives its content from the following sources:

  • System Landscape Directory (SLD)

    The SLD provides the LMDB with data from the following sources:

    • System landscape information

      SLD synchronization is the preferred way to create landscape descriptions in the LMDB. The SLD gets landscape data from data suppliers in the managed systems, for example ABAP application servers send data to SLD with transaction RZ70, which is available on the managed system. Technically, the LMDB is the ABAP complement of Java-based SLD. SLD and LMDB synchronize content in the same way as two SLD systems do. All data from a connected SLD will be synchronized one—to—one with the LMDB, unless the information for a technical system has been edited manually in the LMDB. Manually created information will not be overwritten by changes propagated by the SLD.

    • SAP software catalog (SAP CR content) and CIM model

      Information about usable products and software components is available in the SAP Service Marketplace. This SAP CR content is imported into the SLD and synchronized 1:1 with the LMDB. This data must be updated regularly, for example every three months. For more information, see SAP note 669669Information published on SAP site.

      The current SAP CIM model is also imported through the SLD.

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

  • Outside Discovery

    Some data suppliers that reside outside of the registered technical systems, such as SMD agents (Outside Discovery), write landscape data directly into the LMDB.

  • Editor for Technical Systems in the LMDB

    If there is no data supplier, or if it cannot be used (for example because of a firewall), you can create system information manually in the technical system editor of the LMDB. This has the disadvantage that you also have to update manually created data manually, or it can become obsolete. If the system is subsequently registered by an SLD data supplier, information that was previously edited manually is not overwritten.

    For more information, see Completing Technical System Information Manually.

  • Editor for Product Systems in the LMDB

    Product system information must always be created manually because the individual technical systems do not know how a product is distributed across the landscape.

    For more information, see Creating Product System Information.

    Once created manually, product system definitions are updated automatically when the related technical systems are updated by the SLD data supplier. If, for example, a technical system of type AS ABAP is updated from EHP5 to EHP6, the information is updated for the product system as well. This functionality is available as of SAP Solution Manager 7.1 SP09.

  • SAP Solution Manager System Landscape (SMSY)

    When you upgrade to SAP Solution Manager 7.1, you can migrate system information from SMSY to LMDB during SAP Solution Manager Configuration (transaction SOLMAN_SETUP). This is a one-time activity to capture manually created information from SMSY instead of re-creating it in the LMDB again. For more information, see Migrating System Information from SMSY to LMDB.

    For all information in the LMDB, you can no longer use transaction SMSY to make changes. SMSY is read-only.

Variants of LMDB Integration

There are different was of integrating System Landscape Directories (SLDs) with the LMDB.

LMDB integration variant 1 (recommended):

The systems in the system landscape register themselves in a remote SLD (1), which is then synchronized with the LMDB (2). The LMDB is synchronized with SMSY, to keep SMSY up-to-date (3). If required, you can migrate manually created data in SMSY to LMDB (4), which only needs to be done once, during configuration of SAP Solution Manager. This is the recommended configuration.

LMDB integration variant 2:

The production systems in the system landscape register themselves in one remote SLD (1a), the non-production systems in a different one (1b). Both remote SLDs can be synchronized directly with the LMDB (2a and 2b), but you must specify which one provides the SAP Software Catalog (SAP CR content) for the LMDB. It should be the one with the newest SAP CR content. LMDB is then synchronized with SMSY (3), and, if required, you can migrate data from SMSY to LMDB (4).

It is important that there is no overlapping between system descriptions in the two SLDs. Otherwise, the risk of inconsistencies in the LMDB is high. Because overlapping system descriptions cannot be avoided technically, this variant is not recommended.

For details see the note below and SAP Note 1669649Information published on SAP site.

LMDB integration variant 3:

A valid variant is to use an additional local SLD in SAP Solution Manager: The systems register themselves in a remote SLD (1), which forwards data to the local SLD (2). From here, the system information is synchronized with the LMDB (3). The LMDB is then synchronized with SMSY (4), and, if required, you can migrate data from SMSY to the LMDB (5).

LMDB integration variant 4:

If there is no SLD with the required software version (see Connecting the LMDB to System Landscape Directory (SLD)) or no SLD at all in your system landscape, use the local SLD in SAP Solution Manager as the central SLD for your technical systems (1). The local SAP Solution Manager 7.1 SLD has the version 7.0.

Note Note

Rules for Setting Up Synchronization Between SLD and LMDB:

  • As in other data exchange mechanisms, the unique path principle for data applies when the LMDB is synchronized with more than one SLD. There must be only one source for each unit of data.

  • The kind of content is important to decide which data is synchronized with the LMDB from which SLD: The CIM model and the SAP CR content retrieved from SLD are filtered automatically by the LMDB. For one LMDB namespace, you must select one SLD as the source for this kind of data.

  • The system descriptions cannot be filtered and must therefore not overlap. This can only be achieved in practice if the SLD systems connected to the LMDB run in separate landscapes, and are not connected to each other. One technical system must be registered on only one SLD, otherwise inconsistencies can arise in LMDB. Ensure that each type of information is transported by only one connection. Do not define bridge-forwarding between two SLDs, which are in full, automatic synchronization with the LMDB.

End of the note.

More Information

For more information, see the System Landscape Directory (SLD) at published on SAP site, especially the Planning Guide.