Landscape Management Database (LMDB)

The main task of LMDB is to centrally provide information about the system landscape. The SAP Solution Manager

System Landscape (transaction SMSY) and SLD already provide comparable functions, with different technologies,

for different purposes.

LMDB was introduced in SAP Solution Manager 7.1 and since then is mandatory.

If you upgrade SAP Solution Manager from release 7.0 to 7.1, you must configure LMDB. As of SAP Solution

Manager 7.1, technical system data can only be maintained in the technical system editor of LMDB, not in SMSY

any longer. It is highly recommended to clean up the technical systems in SMSY before upgrade to 7.1.

Integration of LMDB into Landscape Data Management Topology

1. The data supplier registers technical systems in SLD

2. The technical system information, the CIM model, and the CR content are initially synchronized with

LMDB by a Full Automatic Synchronization, and then by incremental synchronization every 10 minutes.

3. Technical system descriptions are continuously replicated from LMDB to SMSY (every 5 minutes).

In addition, SMSY receives some additional system information, such as license information, directly from

ABAP systems via RFC (once a day).

Technical system descriptions can be migrated from SMSY to LMDB once

4. The SAP Solution Manager applications access the landscape descriptions (LMDB and SMSY).

5. The landscape descriptions are used, for example, to monitor, maintain or enhance technical systems

Sources Providing LMDB Content

The content of LMDB comes from the following sources, independently of the technical data flow:

SLD Data Supplier Technically, LMDB is the ABAP complement of Java-based SLD. SLD and LMDB synchronize contents in the same way two SLD systems do. All data that is in a connected SLD already can be read by LMDB. The automatic registration of systems to SLD, and its synchronization with the LMDB is the preferred way of

putting landscape elements in the LMDB. The data suppliers are implemented in the managed systems. Most data suppliers

currently send their data to SLD.

Technical System Editor in LMDB

Systems are registered manually in the Technical System Editor in LMDB if there is no data supplier, or the data

supplier cannot be used, for example because of a firewall. The disadvantage of this manual method is that the

data is not updated automatically, so manually entered data can become obsolete. If the system is subsequently

registered, previously manually-entered data is not refreshed or overwritten.

SAP Solution Manager System Landscape (SMSY)

Data migration from SMSY to LMDB is a special case of a data supplier. The step in the transaction SOLMAN_SETUP

copies SMSY data to technical systems in the LMDB, usually only once, immediately after upgrading SAP Solution

Manager to version 7.1. (Synchronization from LMDB to SMSY makes technical system data in LMDB accessible to

read applications in from SMSY.)

SAP software catalog (CR content) Data about usable products and software components is delivered in the SAP Service Marketplace. This content, SAP CR CONTENT, is transported into SLD and synchronized 1:1 into LMDB. For more information, see SAP note 669669.

SAP CIM model The current SAP CIM model is also in the software component SAP CR CONTENT, and is put in LMDB via SLD, like the SAP software catalog. Landscape Verification Tool

The Landscape Verification Tool analyzes whether your system landscape, particularly the assignment of product

systems, is maintained correctly in the SAP Solution Manager System Landscape (transaction SMSY).

Variants of LMDB Integration

Integration 1

The systems in the system landscape are registered in a remote SLD (1a), which is then synchronized with LMDB

(2a). LMDB is then synchronized with SMSY (3), and, if required, data is migrated (4). This is the recommended

configuration.

Integration 2 The production systems in the system landscape are registered in a remote SLD (1a), and the non-production systems in another remote SLD (1b). Both remote SLDs can be synchronized directly with LMDB (2a, 2b), but only one remote SLD can provide the CR content for LMDB. You specify which one when you configure LMDB. It should be the remote SLD with the newest CR content. LMDB is then synchronized with SMSY (3), and, if required, data is migrated (4). Note:

If multiple SLDs are connected to LMDB, one technical system must be registered on only one SLD, otherwise

inconsistencies may arise in LMDB.

Integration 3

A variant is an additional local SLD in SAP Solution Manager, which is filled by data supplier forwarding (1b), and

which then fills LMDB (2b).

Integration 4 In another variant, without remote SLD, the systems register directly with the local SLD (SLD 7.0) (1c). If you have no remote SLD, you can also use the local SAP Solution Manager SLD.

If there is no SLD in your system landscape (or if there is only an outdated SLD), use the local SLD in the SAP

Solution Manager as central SLD for LMDB synchronization.

Synchronization of one LMDB with more than one SLD System

CIM and CR Content retrieved from SLD is filtered automatically by the LMDB – you must select one SLD as the source for this kind of data.

All other content cannot be filtered and therefore must not overlap. Practically, this can only be achieved if SLD systems connected to the LMDB run in separated landscapes

The figure shows two cases: a valid configuration on the left, and an invalid configuration on the right. Only the central SLD of each landscape connected to the LMDB is shown here. Such a scenario can be found if a hosting provider has several customers or a company separated subsidiaries:

Valid: Both SLD systems are used in separated landscapes, which make connections to the same

LMDB for both SLD a valid option.

Invalid: Both SLDs are used in separated landscapes but connected with mechanisms of data exchange, which makes connections to the same LMDB for both SLDs an invalid option, because the unique path principle is violated. Note: All names (e.g. host names and Business system names) need to be unique across all landscapes (no overlap of names is allowed in all landscapes connected to the LMDB).

Configuring LMDB for Synchronization with SLD Prerequisites:

Minimum System Landscape Directory (SLD) Requirements“)

For SAP Solution Manager, users need administration authorization For SLD:

o In SLD from release SAP NetWeaver 7.1, the user needs the role SAP_SLD_CONTENT_SYNC.

o In SLD from release SAP NetWeaver 7.0, the user at least needs the role SAP_SLD_GUEST.

Procedure:

1. Start transaction SOLMAN_SETUP and choose System Preparation Prepare Landscape Set

Up LMDB. When you start to configure LMDB, the system checks whether LMDB has an object server name. If not, you are prompted to enter a new object server name. This name, in combination with the CIM namespace, specifies the absolute path of the LMDB objects. The object server names should be different in all SLDs and LMDBs. In LMDB, it is always appropriate to use the server name as object server name.

2. In the Synchronization Connections between SLD and LMDB area, choose Add. A window opens. To create a new synchronization connection, make the following entries: a. Description: Enter a free text to describe the new SLD connection.

b. Source URL: Enter the source URL for SLD, which is http://<host name>:<port>. In a standard

installation, the port is: 5<SLD system Java instance number>00. Example: http://sldserver:54300

c. Source Namespace: Enter the CIM namespace of the source (SLD). The default namespace is sld/active.

d. Rank of Source Namespace: The rank is a positive whole number which specifies priorities of system descriptions in the synchronization landscape: the higher the number, the higher the rank. A previously selected rank number is displayed after you selected the namespace. If there is no assignment done before for the SLD namespace rank, -1 is displayed as rank, and you

have to assign a rank to the namespace.

e.Target Namespace: If the source SLD has NetWeaver version 7.1 and supports notifications (see „Minimum System Landscape Directory (SLD) Requirements“, enter the target (LMDB) connection information. For LMDB in SAP Solution Manager release 7.1, only the target namespace active is supported. If the same SLD does not support notifications, the system does not prompt for a target (LMDB) connection.

f. Rank of Target Namespace: Enter rank of the target (LMDB). Choose a number higher than the one for the source (SLD). Example: If a rank has already been assigned to SLD, add 1000 to it.

3. You get a summary. If you want to save your settings and activate them later, confirm with Complete. To start content synchronization immediately, choose Save and Activate. Synchronization with SLD starts

when you activate the configuration.

4. Specify whether you want to use notifications, which are only available with SLD from NetWeaver version 7.1

Monitoring the Synchronization Process To monitor synchronization, you have the following options:

Directly in SAP Solution Manager, you can view information about the synchronization job. Start transaction SOLMAN_SETUP and choose System Preparation Prepare Landscape Set Up LMDB. Select a synchronization connection and choose Advanced.

Transaction SM37 (Simple Job Selection) displays jobs and logs. Jobs usually run under the

SOLMAN_BTC system user. The name of the synchronization job for the target namespace is

SAP_LMDB_LDB_<namespace ID>, e.g. SAP_LMDB_LDB_0000000001. Within the job log you can find

the information how many instances need to be synchronized, for example: Full Sync: Number of

instances to be synced from destination LMDB_SyncDest1: 373920 From this you can

extrapolate the job duration: A job should write about 10 objects per seconds into the LMDB. In addition, you will find two lines for each object type, for example: Full Sync. of SAP_Product: 2661 source instances, 0 target instances Full

Sync. of SAP_Productfinished: 2661 creations, 0 modifications, runtime 390 s

In this example, only 6.8 instances were processed per second, which is not very good.

Transaction SLG1 (Analyze Application Log) display logs. Under Object, enter AI_LMDB. So you can

find the application logs related to LMDB. To increase the log details level of SLG1 logs, start transaction

SM30 and maintain the view V_LMDB_LOG_CONF. The log level can be set per user and sub-object in

LMDB. Several log levels are supported, like:

o Error (default)

o No logging

o Error and Warning

o Error, Warning and Info

Transaction SM12 (Select Lock Entries) displays locked jobs. Under Table name, enter LMDB*.

During content synchronization, it can happen that a change in LMDB is blocked by locks held by another user. In such a case the active sync job is stopped prematurely because changes need to be processed in the same order as they occurred in the source system. The next scheduled sync job will continue at the same point later. Usually blocking locks are released in the meantime and pending changes can be processed. If a blocking situation exists for a longer period of time, check the lock entries.

Integration with SAP Solution Manager System Landscape

(SMSY)

As of SAP Solution Manager 7.1, you can only change technical systems in the LMDB Technical System Editor, but

no longer in the SAP Solution Manager System Landscape (SMSY). But you still maintain product systems in SMSY

and some SAP Solution Manager applications still get their landscape information from SMSY. Therefore, all

relevant technical system information must be continuously synchronized from LMDB into SMSY.

Prerequisites:

SOLMAN_SETUP (system preparation).

SOLMAN_BTC), which was created during Setup (SOLMAN_SETUP), is used automatically.

The synchronization of LMDB and SMSY is completely automatic and unidirectional. There are two actions which copy changes from LMDB into SMSY:

Automatic synchronization of changes from SLD When changes are written from SLD to LMDB, they are logged in the LMDB change log. A check is made for new changes, at least every 5 minutes. If there are changes, all technical system data is written to SMSY. Status changes in LMDB are replicated to SMSY in less than 5 minutes. Changes in SLD are polled at least every 10 minutes from LMDB (with notification this is significantly faster). So changes in SLD are replicated via LMDB towards SMSY in less than 15 minutes (under normal circumstances).

Technical System Editor When you save changes made with the Technical System Editor, the system writes the changes directly to SMSY. So there should be no delay. Note that SMSY also receives some additional system information, such as license information, directly from ABAP systems via RFC connection once a day. All other information is provided by SLD via LMDB.

Working with LMDB A lot of SAP Solution Manager applications (such as the work centers, Diagnostics, and several steps in transaction SOLMAN_SETUP) receive their system landscape information directly from LMDB.. Other SAP Solution Manager applications get their landscape data, especially product system and logical component data, from SMSY. You can perform the following tasks with LMDB:

Technical System Editor

Technical System Editor

Accessing LMDB LMDB data is used and displayed at various locations in the SAP Solution Manager. To centrally view, change, and create LMDB data, you can use the following transactions:

SOLMAN_SETUP) Choose Managed Systems

Configuration.

– Work Centers (transaction SOLMAN_WORKCENTER) In the Solution Manager

Administration work center, choose Landscape.

Technical System Editor and

Host Editor. To access LMDB Administration, start transaction LMDB_ADM. Note that these transaction are

not included in the standard user roles by default.

Register Technical Systems Automatically Prerequisites:

have performed the basic configuration of LMDB.

o AS ABAP administration user

o AS Java administration user

o For all other products, see the product IMG.

SLD user: SLDDSUSER or another user with SAP_SLD_DATA_SUPPLIER role.

ABAP Application Server (AS ABAP) As of release 4.0B, there is an SLD data supplier for AS ABAP. Always register an AS ABAP in SLD with transaction RZ70 and system information will be synchronized automatically with LMDB and SMSY. Apache Tomcat Server (ATC) There is a data supplier for the Apache Tomcat server, which delivers product information. But for the installed applications, product information is not always provided, so manual post-processing in LMDB can be required. Business Object Cluster (BOBJ) There is a data supplier for Business Objects Enterprise (BOE), which delivers product information. For other BOBJ products, there is a data supplier for the Unspecific Application System system type. Database System (DBSYSTEM) Database system information is delivered by various data suppliers, e.g. AS ABAP. The SMD agent Outside Discovery delivers all the information directly to LMDB (the information is not available in SLD). The Outside Discovery delivers software component information, which is sufficient for database systems, so manual post-processing in LMDB is not required. Diagnostics Agent (DIAGAGENT) There are data suppliers for diagnostics agents, which deliver all necessary information, so manual post-processing in LMDB is not required. Introscope Enterprise Manager Server (IS_EM) You manage information about the Introscope Enterprise Manager, in the SAP Solution Manager transaction SOLMAN_SETUP, so manual post-processing in LMDB is not required.

Introscope Manager of Manager (IS_MOM) You manage information about the Introscope Manager of Manager in the SAP Solution Manager transaction SOLMAN_SETUP, so manual post-processing in LMDB is not required.

LMDB Administration Note LMDB Administration is an expert tool. It is strongly recommended that it only used by very experienced users. You can start LMDB Administration in the following ways:

Solution Manager: Work Centers (transaction SOLMAN_WORKCENTER) Related Links

SAP Solution Manager Administration Infrastructure Administration LMDB Administration.

LMDB_ADM.

LMDB Administration provides the following options:

(available as of SP03).

save search criteria for future searches.

The different functions of the tool are distributed on the following tabs:

Overview This tab and its sub-tabs give you an overview of performance data, content synchronization status, namespace configuration, and domain settings. You cannot make any changes.

Instance Browser On this tab you can search for CIM instances. You can display further details of a selected row, in the Details dialog box. In edit mode, you can change attributes in the Instance Attributes tab of the Details dialog box, You can delete CIM instances or their corresponding technical systems. When you delete a technical system, all CIM instances of the technical systems are deleted, as well as the selected CIM instance. You can also display statistical information about all CIM classes. To update the information, choose Synchronize. If there are a lot of instances, synchronization can take some time and lead to a time-out error. In this case, choose Asynchronous Generation.

Change Log Browser On this tab you can search for change log entries of CIM instances. If you select an entry, the bottom table shows its CIM instances with the times of the earliest and latest changes. From the search results, you can display details and change attributes, as described in the Search for CIM Instances tab.