Integration of System Landscape Management 
Integration
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:
You have to set up data suppliers that will automatically register technical systems in the System Landscape Directory (SLD). You can do this for ABAP systems in transaction RZ70, for Java systems with the Visual Administrator or SAP NetWeaver Administrator, for third-party systems with data suppliers based on the sldreg executable, or with other HTTP clients to transfer system information.
For more information, see Register Technical Systems Automatically by Data Suppliers.
A full, automatic synchronization copies the landscape description, CIM model, and SAP Software Catalog (CR content) to the Landscape Management Database (LMDB). Every 10 minutes, incremental synchronization propagates system changes from the SLD to the LMDB.
For more information, see Connect LMDB to System Landscape Directory (SLD).
Technical system descriptions are continuously synchronized from the LMDB to the SAP Solution Manager System Landscape storage (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. Thereafter, you must create information only in the LMDB. For more information, see Migrate System Information from SMSY to LMDB.
The SAP Solution Manager applications use the system descriptions that are managed in the LMDB.
In maintenance transactions, you can create stack XML files with which the SAP Global Support Backbone (SAP Support Portal) can calculate the download basket for updates and upgrades.
With the correct system information, applications can monitor and maintain systems in the landscape.
Sources Providing LMDB Content
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, which are implemented in the managed systems, for example ABAP application servers send data to SLD with transaction RZ70. 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.
SAP Software Catalog (CR Content)
Information about usable products and software components is available in the SAP Service Marketplace. This CR content is imported into the SLD and synchronized 1:1 with the LMDB. For more information, see SAP note 669669.
SAP CIM Model
The current SAP CIM model is imported into the SLD, like the SAP software catalog.
For more information, see Connect LMDB to System Landscape Directory (SLD).
Outside Discovery
Some data suppliers that reside outside of the registered technical systems write landscape data directly into LMDB. This is called “Outside Discovery”.
Technical System Editor and Product System Editor 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 in the technical system editor of the LMDB manually. 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 edited manually, previously, is not overwritten.
Product system information must always be created manually because the individual technical systems do not know how a product is distributed in the whole landscape.
For more information, see Complete Technical System Information Manually and Create Product System Information.
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, enabling you to rescue manually created information from SMSY instead of recreating it in LMDB again. For more information, see Migrate System Information from SMSY to LMDB.
Variants of LMDB Integration
The following graphics explain the most important ways you can integrate LMDB into the system landscape.
LMDB Integration Variant 1
The systems in the system landscape register themselves in a remote SLD (1), which is then synchronized with LMDB (2). 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). 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 LMDB (2a and 2b), but you must specify which one provides the SAP Software Catalog (CR content) for LMDB. It should be the one with the newest 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 different SLD. Otherwise, the risk of getting inconsistencies in LMDB is high (for details see the note below and SAP Note 1669649).
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 LMDB (3). LMDB is then synchronized with SMSY (4), and, if required, you can migrate data from SMSY to LMDB (5).
LMDB Integration Variant 4
If there is no SLD with the required software version (see Connect 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
To synchronize the LMDB with more than one SLD, consider the following rules:
As in other data exchange mechanisms, the unique path principle for data needs to be followed 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 LMDB from which SLD: The CIM model and the 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 therefore must 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 LMDB.
More Information
For more information, see the Planning Guide — System Landscape Directory in the SAP Community Network at http://scn.sap.com/docs/DOC-8042.