Show TOC

Procedure documentationConnecting LMDB to System Landscape Directory (SLD)

 

LMDB should receive as much system information as possible from an SLD.

SLD synchronization is the preferred way to create landscape descriptions in the LMDB.

  1. The SLD gets landscape data from data suppliers in the managed systems. For most technical systems there are data suppliers, which - once configured - automatically register the systems in the SLD:

    • 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 other SAP products and third-party systems)

    • SLD data suppliers based on other HTTP clients

  2. During the setup of SAP Solution Manager, an initial, full synchronization is triggered. It transfers the complete landscape description from the connected SLD to the LMDB.

    Also the SAP software catalog (SAP CR content) and CIM model synchronized.

  3. After the initial, full synchronization, an incremental synchronization is started every 10 minutes.

    The LMDB receives SLD changes automatically when they occur, using polling by LMDB or active change notifications by the SLD. For more information, see SAP Note 1546079Information published on SAP site.)

    The incremental synchronization propagates changes, not complete system data. So if you want to remove a system from the LMDB, delete it in SLD, not in the LMDB. The deletion in the SLD is propagated to the LMDB like all other changes. For more information, see Deleting Technical System Information.

    The SAP CR content and CIM model must be updated manually, for example every three months. For more information, see SAP Note 669669Information published on SAP site.

Prerequisites

Ideally, all technical system information is collected by one SLD. If this is not possible, the LMDB must be synchronized with several SLDs or an additional SLD is collecting all data by SLD bridge forwarding. Because the LMDB content depends on the sequence of changes in the various SLDs, any overlap between system data in multiple source SLDs risks inconsistencies in the LMDB.

Required SAP NetWeaver Version for the SLD

SLD is based on SAP NetWeaver. To see which SAP NetWeaver versions are supported for SLD synchronization with the LMDB, see SAP Note 2175739Information published on SAP site.

If your central SLD does not have the required status, you can use another SLD which does satisfy the minimum requirements (for example the local SLD in SAP Solution Manager) and synchronize it with your central SLD, using SLD bridge-forwarding or full, automatic synchronization.

Required CIM Model and SAP Software Catalog Version

SAP Note 1701770Information published on SAP site explains the which CIM model and SAP CR content are required for the SLD that is connected to the LMDB.

SAP Note 669669Information published on SAP site explains how to update the CR content in theSLD and LMDB.

If SAP CR content is inconsistent in the SLD or LMDB, you can repair it. For more information, see the following notes:

  • SAP Note 1939864Information published on SAP site (Check if SAP CR Content is corrupt in LMDB or SLD)

  • SAP Note 1891566Information published on SAP site (Repair of LMDB CR Content)

  • SAP Note 1093168Information published on SAP site (Repair of SLD CR Content)

CIM model and SAP CR content should not be more than three months older than the latest version in SAP Support Portal. SLD content updates are published every month. A new major version of the SAP CR content is created every year.

Variants of LMDB Integration

There are different was of integrating 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). 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.

It is important that there is no overlap 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:

Another 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).

LMDB integration variant 4:

If there is no SLD with the required software version 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 SLD of SAP Solution Manager 7.2 has the SAP NetWeaver version 7.40.

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 SAP CR content retrieved from SLD is filtered automatically by the LMDB. For one LMDB, 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 the 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.

For more information, see the System Landscape Directory (SLD) at http://scn.sap.com/docs/DOC-8042Information published on SAP site, especially the Planning Guide.

Prerequisites for Setup of the Synchronization Between SLD and LMDB

  • In SAP Solution Manager Configuration (transaction SOLMAN_SETUP), you have performed the steps under Start of the navigation path Mandatory Configuration Next navigation step System Preparation End of the navigation path.

  • Under Start of the navigation path Mandatory Configuration Next navigation step Infrastructure Preparation Next navigation step SLD Connections End of the navigation path, you have created the connections required for SAP Solution Manager. You have defined at least one connection with the role Source for LMDB. For more information, see the help tray in the UI.

  • The SLD is running.

  • Users and authorizations:

    • For SAP Solution Manager, users need administrative authorization.

    • For an SLD as of release SAP NetWeaver 7.1, users need the role SAP_SLD_CONTENT_SYNC.

      For an SLD on EHP2 on SAP NetWeaver 7.0, users need at least the role SAP_SLD_GUEST.

Procedure

To use the LMDB, configure it in the of SAP Solution Manager setup, configure it in SAP Solution Manager: Configuration, after installation or upgrade:

  1. Start transaction SOLMAN_SETUP and choose Start of the navigation path Mandatory Configuration Next navigation step Infrastructure Preparation Next navigation step Set Up Landscape Management Next navigation step LMDB Synchronization End of the navigation path.

    Choose Edit.

  2. In the initial setup, you have to configure the LMDB object server, in this screen. This is a one-time activity.

  3. In the Synchronization Connections between SLD and LMDB area, choose Add. A dialog box opens where you can define the synchronization connection.

    The input help offers all SLD connections that you defined in the previous setup step.

    For more information, follow the instructions in the help text of the dialog.

    To determine which status has priority in case of conflicts, a ranking is defined between SLD and LMDB. A conflict occurs if the an object has different statuses in LMDB and SLD. This can happen, for example, if you have manually changed the system information (originally from the SLD) with the LMDB technical system editor. The LMDB must always have priority; this prevents changes in SLD from overwriting changes made manually in the LMDB in the technical system editor. For more information, see SAP NetWeaver System Landscape Directory: Conflicts & Ranks in Full, Automatic Synchronization in SAP Community Network at http://scn.sap.com/docs/DOC-8516Information published on SAP site.

    Example: To be flexible for subsequent changes in your synchronization landscape, use a rank of 1000 for the source (SLD) and 2000 for the target (LMDB).

    If the source SLD supports change notifications, an additional popup appears in which you can enter the target LMDB connection. Enter connection parameters that the SLD can use to notify the LMDB about changes. The data you enter here will be written to the destination store of the AS Java of the SLD. It will be visible in the SLD under Start of the navigation path Administration Next navigation step Content Synchronization Next navigation step Sync Notifications End of the navigation path.

  4. Save your entries and close the dialog box.

    If you have problems when you try to save, see SAP Note 1699142Information published on SAP site.

  5. You can change some connection parameters later. In the list of synchronization connections, choose Advanced to specify, for example, whether you want to use change notifications (see Prerequisites).

  6. If you add more than one SLD, set the Is CR Source indicator for the SLD that provides the SAP Software Catalog (SAP CR content). This should be the first synchronization connection you activate.

    Choose Activate for each SLD connection, if you have not already done so.

  7. The initial, full synchronization with the SLD takes several hours, depending, for example, on the number of systems in the SLD.

    If the job is aborted, it automatically restarts after ten minutes (according to the polling interval) and resumes at the point where it was canceled.

  8. After the full synchronization, the system carries out an incremental synchronization every ten minutes (standard) to propagate changes to the LMDB.

Monitoring the Synchronization

To monitor synchronization, you have the following options:

  • In SAP Solution Manager, you can view information about the synchronization job. Start transaction SOLMAN_SETUP and choose Start of the navigation path Mandatory Configuration Next navigation step Infrastructure Preparation Next navigation step Set Up Landscape Management End of the navigation path.

    Select a synchronization connection and choose Advanced.

  • Transaction SM37 (Simple Job Selection) displays jobs and logs. Search for jobs starting with SAP_LMDB_LDB_* and enter an asterisc (*) under User name field empty. (Jobs usually run under the SOLMAN_BTC system user.) The name of the synchronization job for the target namespace is SAP_LMDB_LDB_<number of LMDB target namespace> e.g. SAP_LMDB_LDB_0000000001.

    The job log for the initial, full synchronization contains information like the following:

    Number of relevant source instances: 654321.

    From this you can extrapolate job duration: A job should write about 10 objects per seconds into the LMDB. For more information about performance, see SAP Note 1594654Information published on SAP site.

  • Transaction SLG1 (Analyze Application Log) display logs.

    All relevant information is stored in the job log. Transaction SLG1 is only required for low-level analysis.

    Under Object, enter AI_LMDB to find the application logs related to the LMDB.

    To increase the detail level of SLG1 logs, start transaction SM30 and maintain the V_LMDB_LOG_CONF view. The log level can be set per user and sub-object in the LMDB. Several log levels are supported, for example:

    • Error (default)

    • No logging

    • Error and Warning

    • Error, Warning and Info

  • Transaction SM12 (Select Lock Entries) displays locks.

    Under Table name, enter LMDB*. During content synchronization, a change in the LMDB can be blocked by another user. If so, the active sync job is cancelled because changes must be processed in the order in which they occurred in the source system. The next scheduled synchronization job will continue at the same point, later. Locks will usually have been released in the meantime, and pending changes can be processed. If a lock persists, check the lock entries.

For performance issues with the full synchronization job, see SAP Note 1555955Information published on SAP site.

Result

You have connected the LMDB to a central SLD, which provides changes in system descriptions by incremental synchronization, so all SAP Solution Manager applications use the latest system information, for example to monitor the systems.

Checking the Data Supplier Status

You can check this in the editor for technical systems in the Landscape Management application. On the overview screen of a technical system, choose the More link for detailed status information.

To check the data supplier status of several system types, start the Landscape Management application and choose Landscape Reporting. The report SAP: Technical Systems – Data Supplier Completeness lists the status of all selected technical systems. For more information, see SAP Note 1842956Information published on SAP site and 1869701Information published on SAP site.

More Information

For information on how to use automatic data suppliers, see the following sources of information: