Landscape Management Database (LMDB)

S AP Solut ion Manager 7 .1 SP02 and SP 03

- 2 -

Copyright © Copyright 2011 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

Disclaimer

The information in this document is confidential and proprietary to SAP and may not be disclosed without the permission of SAP. This document is not subject to your license agreement or any other service or subscription agreement with SAP. SAP has no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation and SAP's strategy and possible future developments, products and or platforms directions and functionality are all subject to change and may be changed by SAP at any time for any reason without notice. The information on this document is not a commitment, promise or legal obligation to deliver any material, code or functionality. This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. This document is for informational purposes and may not be incorporated into a contract. SAP assumes no responsibility for errors or omissions in this document, except if such damages were caused by SAP intentionally or grossly negligent. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

- 3 -

Contents

Copyright ............................................................................................................................................ - 2 - Introduction: Landscape Management Database (LMDB) ............................................................ - 4 - Integration of LMDB into Landscape Data Management Topology ............................................. - 5 -

Landscape Data Management – „The Big Picture“ ......................................................................... - 5 - Sources Providing LMDB Content ................................................................................................... - 6 - Variants of LMDB Integration ........................................................................................................... - 7 -

Integration with System Landscape Directory (SLD) .................................................................. - 10 - System Landscape Directory (SLD) Requirements ....................................................................... - 10 - Configuring LMDB for Synchronization with SLD .......................................................................... - 12 - Monitoring the Synchronization Process ....................................................................................... - 13 -

Integration with SAP Solution Manager System Landscape (SMSY) ........................................ - 14 - Integration with Landscape Verification ....................................................................................... - 15 - Working with LMDB ......................................................................................................................... - 15 -

Accessing LMDB ............................................................................................................................ - 15 - LMDB Entities ................................................................................................................................ - 15 - Register Technical Systems Automatically .................................................................................... - 16 - Technical System Editor ................................................................................................................ - 19 -

Display System Description with Technical System Editor ........................................................ - 20 - Create System Description with Technical System Editor ......................................................... - 20 - Change System Description with Technical System Editor ....................................................... - 21 - Delete Technical System Description with Technical System Editor ......................................... - 21 - Resynchronization from SLD (with or Without Deletion of Assignments) .................................. - 22 -

Resynchronization by Resync from SLD Function ................................................................. - 22 - Resynchronization by Report ................................................................................................. - 22 -

Special Settings and Functions of the Technical System Editor ................................................ - 23 - Host Editor ..................................................................................................................................... - 24 -

Migrate SMSY Data to LMDB (One-Time Activity) ........................................................................ - 25 - System-Oriented (Complete) Migration ......................................................................................... - 25 - Aspect-Oriented Migration ............................................................................................................. - 27 -

Technical Scenario .......................................................................................................................... - 27 - Dual Stack Technical Scenario in Managed System Configuration ....................................... - 28 -

RFC Connections ............................................................................................................................ - 28 - LMDB Administration ...................................................................................................................... - 29 - Troubleshooting .............................................................................................................................. - 30 -

Damaged Technical System Description in LMDB ........................................................................ - 30 - Restore a Deleted Technical System ............................................................................................ - 30 - Running Job Leads to Quick Completion of Following Jobs ......................................................... - 31 - Cannot create RFC Connection Because of Wrong Host FQDN .................................................. - 31 - Performance Issues During Synchronization ................................................................................. - 31 - Performance Issues Because of Exhausted Shared Memory ....................................................... - 32 - No Progress in Incremental Synchronization ................................................................................. - 32 - Unicode Characters in a Non-Unicode LMDB ............................................................................... - 34 -

Glossary ........................................................................................................................................... - 35 -

- 4 -

Introduction: Landscape Management Database (LMDB) The Landscape Management Database (LMDB) is a directory of the elements in a system landscape. LMDB uses the SAP enhancement of the Distributed Management Task Force (DMTF) Common Information Model (CIM) to describe the landscape elements, analogously to the System Landscape Directory (SLD). Typical model elements are “computers“, “systems“, “products“, and “software components“. For more information about CIM, see www.dmtf.org.

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 aims for a more flexible extendibility of the landscape model and the unification of SLD and SMSY in SAP Solution Manager.

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. E.g. delete old technical systems in SMSY that are no longer needed. The tool Landscape Verification can support this clean up.

There is a migration of technical systems data from SMSY to LMDB. The corresponding chapter within the Setup Guide provides more details.

- 5 -

Integration of LMDB into Landscape Data Management Topology

Landscape Data Management – „The Big Picture“

The following diagram describes the data flow for the landscape data management components.

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

3* 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.

- 6 -

PI (non-prod.) Systems (non-prod.)NWDIOther systems (prod.)PI (prod.)

Managed Systems: Non-Productive Environment Managed Systems: Productive Environment

SLD

(design-time)SLD

(runtime)

Systems Managing Systems

SAP Solution

Manager

LMDBSLD Sync

(unidirectional)

Forwarding of data on

Technical Systems

Manual export/ import

(optionally using CTS+)

Data Supplier registrat.

of 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, for example the ABAP application server (AS) with the transaction SLD Administration (RZ70). Synchronization of SLD and LMDB contents put this data 1:1 in the LMDB. A small part of the data suppliers, „Outside Discovery“, writes its data directly in the LMDB.

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.

- 7 -

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

For more information, see the SAP Community Network, under (Landscape Verification)

Variants of LMDB Integration

The following graphics explain the interaction of SLD, SMSY and LMDB in a system landscape, in the recommended configuration:

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.

- 8 -

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.

- 9 -

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.

For more information, see the SLD Planning Guide in the SAP Community Network.

Synchronization of one LMDB with more than one SLD System

As in other mechanisms of data exchange, the unique path principle for data needs to be fulfilled, when the LMDB is synchronized with more than one SLD system. The kind of content is important to make a decision from which SLD which data is synchronized:

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.

- 10 -

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

Integration with System Landscape Directory (SLD)

System Landscape Directory (SLD) Requirements

SAP NetWeaver Release

The following table gives an overview of the SAP NetWeaver versions for an LMDB-compatible SLD, and whether, and since when (which support package stack), an SLD satisfies the minimum requirements for LMDB:

SAP NetWeaver Release (SLD) Supported Support Package Stack Level

SAP NetWeaver 6.40 not supported

SAP NetWeaver 7.0 not supported

EHP1 for SAP NetWeaver 7.0 not supported

EHP2 for SAP NetWeaver 7.0 SP6, patch 5

SAP NetWeaver 7.1 SP9

EHP1 for SAP NetWeaver 7.1 all SPs

SAP NetWeaver 7.2 all SPs

SAP NetWeaver 7.3 all SPs

Although the minimum release requirements are lower, it is recommended that youuse a separate remote SLD with version 7.1 or higher for synchronization with LMDB. This way you have the latest

- 11 -

SLD functional scope. (The local SLD in SAP Solution Manager has version 7.02).

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

Model and CR Content

The CIM model and SAP CR content requirements are:

CIM model 1.6.16 or higher

Newest SAP CR CONTENT, at least version 7.0

For more information about updating CR content, see SAP Note 669669.

Change notification from SLD

All supported SLD-Versions support the polling of the information. The polling interval usually is ten minutes. The immediate notification of LMDB about changes in SLD accelerates the synchronization of changes in the SLD – LMDB – SMSY chain, but active change notification from SLD to LMDB requires a higher version of SLD:

SAP NetWeaver Release (SLD) Supported Support Package Stack Level

SAP NetWeaver 7.1 SP12

EHP1 for SAP NetWeaver 7.1 SP7

SAP NetWeaver 7.2 SP5

SAP NetWeaver 7.3 SP3

For more information, see SAP Note 1546079.

There are data suppliers for most technical systems, which automatically register systems in SLD. The usual case is to configure one central SLD for your whole system landscape, outside SAP Solution Manager. This SLD is the central data source for LMDB. If possible, you should make changes to technical systems by updating their registration in SLD, but not by making manual changes in LMDB.

There are two data supplier types: specific data suppliers for AS ABAP and AS Java, and generic data suppliers for most other products in the SAP environment.

LMDB receives the SLD changes automatically when a change occurs (using polling or notifications). The remote communication uses HTTP(S). Regular polling and notification ensure a robust synchronization.

A ranking is defined between SLD and LMDB, just like between two SLDs. It automatically determines which status „wins‟ in case of conflicts. A conflict exists if the status of an object on recipient side (LMDB) differs from what is expected by the source system (SLD). This can happen, for example, if you have changed the system information (originally coming from SLD) with the LMDB Technical System Editor in the meantime. The LMDB must always have priority; this prevents changes in SLD from overwriting manual changes made in LMDB in the Technical System Editor. (For more information, see SAP NetWeaver System Landscape Directory: Conflicts & Ranks in Full Automatic Synchronization in the SAP Community Network.)

Note the following recommendations when you plan the configuration of synchronization between SLD and LMDB:

Ideally, all systems in the landscape register to one remote SLD directly. If this is not possible, LMDB must be synchronized with several SLDs, but several SLDs may contain contradictory data. The contents of LMDB depend on the sequence of the changes in the various SLD systems. Even if the procedure is theoretically unambiguously specified, the search for errors

- 12 -

in several SLDs in the case of conflict can be time-consuming, so it is better to use one SLD to supply LMDB.

Once it has been configured, incremental synchronization between SLD and LMDB is automatic. LMDB queries SLD for changes every 10 minutes. This is also called polling.

As of SLD 7.1, you can configure notifications to trigger processing of changes in a more timely fashion. (With SLD version 7.0 only polling is enabled.

Configuring LMDB for Synchronization with SLD

To be able to use LMDB, you must perform the basic configuration in the setup of SAP Solution Manager. This is done during the basic configuration of SAP Solution Manager after installation or upgrade.

Prerequisites:

You have performed all previous system preparation steps in SOLMAN_SETUP.

SLD is running (see „Minimum System Landscape Directory (SLD) Requirements“)

Users and authorizations:

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. For further naming recommendations, see SAP Note 935245.

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.

- 13 -

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

If the source-namespace already had a rank you should not change the rank since this is the rank of the namespace in SLD. So changing this rank might have impact on other content synchronizations as well. Therefore if you must change the rank you should retain the relative rank position (higher/lower) towards the rank of all other existing synchronization connections. So you must have a consistent view over all your SLD/LMDB content synchronization rank settings before you can decide for the correct rank change.

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 (see „Minimum System Landscape Directory (SLD) Requirements“. If you select this option and use SLD NetWeaver version 7.0, you are later informed that this function is not available.

The initial, full automatic synchronization with SLD can take several hours, depending, for example, on the number of systems in SLD, and the hardware. If the full synchronization job fails, you can restart it. It will continue with the last object before it has been cancelled.

Issues with Oracle statistics require manual activities some minutes after you started the synchronization. For more information, see Outdated Oracle Database Statistics in the Troubleshooting section.

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.

- 14 -

For more information , see the following sources of information:

o SAP Note 1594654

o Troubleshooting section.

o LMDB Sync Log Insights in the SAP Employee Network

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.

For known issues with the full synchronization job, see SAP note 1555955 (SAP Solution Manager 7.1 - Performance Checks for LMDB).

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:

You have performed the basic configuration of LMDB in SOLMAN_SETUP (system

preparation).

SLD and LMDB have been initially synchronized.

Users and authorizations in SAP Solution Manager: The SAP Solution Manager batch user

(e.g. 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).

- 15 -

So changes in SLD are replicated via LMDB towards SMSY in less than 15 minutes (under normal circumstances).

Automatic synchronization of changes written manually to LMDB by the 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.

Integration with Landscape Verification

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

For further information, see Landscape Verification in the SAP Community Network.

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:

Enter technical system descriptions using data suppliers

Enter technical system descriptions manually with the Technical System Editor

Display or change technical system descriptions with the Technical System Editor

Delete technical system descriptions

Migrate SMSY data to LMDB once

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:

SAP Solution Manager Configurations (transaction SOLMAN_SETUP)

Choose Managed Systems Configuration.

SAP Solution Manager – Work Centers (transaction SOLMAN_WORKCENTER)

In the Solution Manager Administration work center, choose Landscape.

You can use transaction LMDB to directly enter the LMDB Editors like 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.

LMDB Entities

The following table gives an overview of the entities relevant for LMDB, their data sources, and how to edit them:

Entity Data Source Editor Notes

- 16 -

ABAP application server SLD data supplier Technical System Editor

Apache Tomcat server SLD data supplier Technical System Editor

No installed application product information

Business object cluster SLD data supplier Technical System Editor

Database system SLD data supplier, outside discovery

Technical System Editor

Outside Discovery enhances the system information of SLD data suppliers.

Diagnostics Agent SLD data supplier Technical System Editor

Introscope Enterprise Manager Server

Manual SOLMAN_SETUP Configuration from SOLMAN_SETUP

Introscope Manager of Manager

Manual SOLMAN_SETUP Configuration from SOLMAN_SETUP

Java application server SLD data supplier Technical System Editor

LiveCache SLD data supplier (AS ABAP)

Technical System Editor

Master Data Management server

SLD data supplier Technical System Editor

Microsoft internet information service

Outside discovery Technical System Editor

No installed application product information

.NET System Manual Technical System Editor

TREX system SLD data supplier Technical System Editor

SAP Web Dispatcher SLD data supplier Technical System Editor

IBM WebSphere Cell SLD data supplier Technical System Editor

No installed application product information

Unspecific application system

SLD data supplier Technical System Editor

Host SLD data supplier, outside discovery

Not in SAP Solution Manager 7.1 SP1

Outside Discovery enhances the system information of SLD data suppliers.

Technical scenario Manual SOLMAN_SETUP Dual stacks (AS ABAP + AS JAVA) recognized automatically

Product system Manual SMSY

Logical component Manual SMSY

Register Technical Systems Automatically (Recommended)

The preferred way of creating system landscape information in LMDB is automatic system registration. The data suppliers are implemented in various systems. Most of them send their data to SLD. This data is sent 1:1 to LMDB by synchronizing the contents from SLD.

- 17 -

For more information, see the SAP Community Network, under http://sdn.sap.com/irj/sdn/nw-sld.

Prerequisites:

You have performed the basic configuration of LMDB.

You have initially synchronized SLD and LMDB.

Users and authorization for systems to be connected:

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.

Each architecture has its own data supplier, which is described in detail in its documentation.

For hosts, Microsoft IIS, and databases, the data supplier (SMD Agent in Outside Discovery) is outside the architecture, and writes directly into LMDB. Outside discovery enhances the system information, which would not be sufficient otherwise.

Information for some other system types must be created manually. The following sections describe the recommended system integration procedure per system type.

Detailed information about individual products is beyond the scope of this setup guide. For more information about the configuration of specified products, see Maintenance of Product in the System Landscape in the SAP Community Network.

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.

For more information, see Setting Up the SLD Data Supplier for AS ABAP Based Systems in the SAP Help Portal.

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.

- 18 -

Java Application Server (AS Java)

There is a data supplier which is usually set up during system installation. Until NetWeaver Release 7.0, the configuration can be performed manually in the Visual Administrator. For Release 7.1 and above, the configuration is done in SAP NetWeaver Administrator.

Since NetWeaver Version 7.02, it is possible – under certain circumstances – the AS Java data supplier can deliver information about installed product instances, so installed products only need to be configured in LMDB for older NetWeaver versions. For more information, see Setting Up the SLD Data Supplier for Java-Based Systems in the SAP Help Portal.

LiveCache

The LiveCache system information is provided by the following versions of the AS ABAP data supplier: 640 SPS23, 700 SPS17, 701,702 710 SPS07 and all higher releases. In all other cases, create the LiveCache manually in the Technical System Editor. The data supplier provides no product information, so assign the LiveCache product instance to the LiveCache system in the Technical System Editor.

Master Data Management Server (MDM)

There are data suppliers that deliver product information for the Master Data Management server, so manual post-processing in LMDB is not required.

Microsoft Internet Information Service (MSIISINST)

There are data suppliers for the Microsoft Internet Information Service, which deliver product information about the Microsoft Internet Information service, via Outside Discovery. You must specify the products of the applications which run in the Microsoft Internet Information service, manually.

.NET System (MS_.NET)

There are usually no data suppliers which deliver product information for .NET systems. You must maintain this information in LMDB manually.

TREX System

There are data suppliers for TREX systems, but they do not deliver product information, so you must manually enter it in LMDB in the Technical System Editor.

SAP Web Dispatcher (WEBDISP)

The SAP Web Dispatcher has a data supplier, but it does not deliver product information, from version 7.2. You must add the product information in LMDB.

IBM WebSphere Cell (WEBSPHERE)

There are data suppliers, which deliver product information, for IBM WebSphere Cell systems. Manual post-processing in LMDB may be required for the applications which run in WebSphere.

Unspecific Application System (UNSPECIFIC)

There are data suppliers for the various variants (technology types) of unspecific application systems. Unspecific application systems can be stand-alone (UNSPAPP) or cluster (UNSPECIFIC). An unspecific stand-alone application system has only one server, an unspecific cluster application system can have several application servers.

The data suppliers for this system type usually also deliver the product information, so manual post-processing in LMDB is not required.

You create unspecific application systems for which there are no data suppliers, in LMDB in the Technical System Editor, manually.

Current overview of known unspecific application systems:

Technology Type Type Product Data Supplier

ALLOY Stand-alone SAP Alloy (IBM) yes

BCMClusterTechnology Cluster SAP BCM SOFTWARE yes

BOFC_Cluster Cluster SBOP FINANCIAL yes

- 19 -

CONSOLIDATION

BPCMSCluster Cluster SBOP BPC MS yes

BPCNWCluster Cluster SBOP BPC NW yes

ClickSoftwareCluster Cluster SAP WS&O BY CLICKSOFTWARE yes

ConvergentChargingCluster Cluster SAP Convergent Charging yes

CSLCluster Cluster TPT Commodity SL yes

DataServicesCluster Cluster SBOP Data Services yes

EPOSCluster Cluster SAP ENTERPRISE POS yes

ESOCluster Cluster SAP SOURCING/CLM yes

InfoInterchangeServer Stand-alone SAP INFO INTERCHANGE yes

LiveEnterprise Cluster SBOP EVENT INSIGHT yes

MigrationCluster Cluster SMSY Migration yes

OTHERS (can only be used for technical systems entered manually; dedicated for project based integrations of customer products to SAP Solution Manager)

Cluster/Standalone Standard customer specific product no

PCMCluster Cluster SBOP PCM yes

PMCluster Cluster SAP PROMOTION yes

RTOMCluster Cluster SAP RTOM yes

SAPPOS_Cluster Cluster SAP POS yes

SBOPEnterprise31 Cluster SBOP Enterprise 3.1 yes

Host (Computer System)

A host is not really a technical system – technical systems are installed on hosts. The technical systems are based on the host, but because the host is an underlying system, accurate information about it is important. The required detailed information is provided by the Outside Discovery, via the SMD agent. As of release 7.1 SP2, SAP Solution Manager contains a host editor. For more information, see Host Editor section.

Technical System Editor

With the Technical System Editor, you can manually create, change, and delete information about technical systems in LMDB. Note:

LMDB content should be created and updated automatically by synchronization with SLD, Outside Discovery, or by initial data migration from SMSY. Avoid manual entries in LMDB, as far as possible, because they can become inconsistent or obsolete, and data from SLD which is changed in LMDB will no longer be updated by synchronization of LMDB with SLD.

The following information about technical systems can only be created manually in LMDB:

Technical system types without automatic data supplier

Software assignments (product instances and product versions), in case the data suppliers do not deliver it automatically

Maintenance of the Diagnostics Relevance indicator for product instances

Maintenance of Custom Attributes

- 20 -

Display System Description with Technical System Editor

The Technical System Editor can display detailed information about the technical systems in your system landscape.

Prerequisites:

You have performed the basic configuration of LMDB.

You have initially synchronized SLD and LMDB.

Users and authorization in SAP Solution Manager: SAP_SYSTEM_REPOSITORY_DIS user

There are two ways of displaying the system configuration with the Technical System Editor:

Alternative 1:

In SAP Solution Manager: Configuration (transaction SOLMAN_SETUP), choose Managed Systems

Configuration Technical Systems. Select a technical system and then choose System Operations Display System.

Alternative 2:

In SAP Solution Manager – Work Center (transaction SOLMAN_WORKCENTER), choose SAP Solution

Manager Administration Landscape Define New Query and select a system. Then choose System Operations Display System.

In the following, only the access via Alternative 1 is described. But you can use alternative 2 as well and carry out the same operations.

Create System Description with Technical System Editor

If there is no data supplier for a system, you can create a system in the LMDB, manually, with the Technical System Editor.

Note:

Manually-created technical systems are not automatically updated, so they can become obsolete.

If you connect the system with a data supplier later, all missing information is written from SLD to LMDB. If the information differs between SLD and LMDB, the LMDB version is retained. If you want to copy the SLD status to LMDB, proceed as described under Restoring a Damaged Technical System Description in the Troubleshooting section.

Prerequisites:

You have performed the basic configuration of LMDB.

You have initially synchronized SLD and LMDB.

Users and authorization in SAP Solution Manager: To create, change, or delete a technical

system in LMDB, you need the SAP_SYSTEM_REPOSITORY_ALL role.

You can restrict the authorization with LMDB authorization objects. Copy the role into your namespace, and change the role.

To create a completely new technical system description, proceed as follows:

1. Call In the SAP Solution Manager Configuration (transaction SOLMAN_SETUP), choose

Managed Systems Configuration Technical Systems System Operations Create System.

2. Select a system type from the input help and choose Continue.

3. Define further data, depending on the system type selected, for example system name, installation number, and host name. Choose Next.

- 21 -

4. An extended system ID (ExtSID) is proposed. Accept it and choose Save.

5. Another guided activity opens, in which you can enter detailed information about your system. Click Display Navigation Tree to see individual categories.

For detailed information on how to define certain products manually, see Maintenance of Product in the System Landscape in the SAP Community Network.

Change System Description with Technical System Editor

When you create technical system descriptions in LMDB, manually, its data is not updated with SLD information because the rank of LMDB is higher. Therefore, if changes of manually created data are required, you must make them manually.

For some system types, manual changes can be required because, for example, information delivered by older data suppliers is no longer sufficient. See Register Technical System Automatically.

If you complete or change such entries in LMDB, they are not overwritten by SLD content synchronization, because LMDB has higher rank.

Prerequisites: see Create System Description with the Technical System Editor.

To change technical system description, proceed as follows:

1. Start SAP Solution Manager: Configuration (transaction SOLMAN_SETUP:) and choose

Managed Systems Configuration Technical Systems System Operations Maintain System.

2. Make the changes.

3. Save your entries.

Delete Technical System Description with Technical System Editor

The Technical System Editor can delete technical system descriptions in LMDB.

A technical system is known in at least one System Landscape Directory (SLD), the Landscape Management Database (LMDB) or the SAP Solution Manager System Landscape (SMSY).

Deleting the description of a technical system in LMDB is only makes sense for manually created descriptions in LMDB, or if you migrated the description from SMSY into LMDB.

If you delete a technical system, you must ensure that it is deleted consistently in the complete SLD and LMDB system landscape. The sequence of deletion is important, because automatic synchronization could restore deleted data. The deleted technical system is automatically re-registered if it is in a landscape, and if it has a system data supplier which is configured in SLD. If such systems are really to be deleted, the data supplier must be deactivated first.

Prerequisites: see Create System Description with the Technical System Editor.

To delete a technical system description from the complete system landscape, proceed in the following sequence:

1. If the system is known in an SLD, deactivate the data supplier.

2. If the system is known in an SLD, delete it there first.

3. Delete the system in LMDB. Explicit deletion in LMDB is only necessary if you changed the system manually, because it is then protected against propagation of the deletion in SLD.

Call In the SAP Solution Manager Configuration (transaction SOLMAN_SETUP), and choose

Managed Systems Configuration Technical Systems System Operations Maintain System. Choose Delete Technical System.

4. The technical system description that you deleted in LMDB is automatically deleted in SMSY as well. But dependent product systems are not deleted, so you must also change or delete

- 22 -

the product systems in SMSY manually. For technical systems of type ABAP, this is obligatory. For all other system types it is only necessary if it is part of a product system.

Note:

If you delete a technical system description coming from SLD in LMDB, it is only deleted until the next incremental synchronization. The result can be an incomplete system description, because only that information is synchronized that is new from the SLD‟s point of view. To repair this, read Restore a Deleted Technical System in the Troubleshooting section.

Delete the description of a technical system in SLD

For more information about deleting system descriptions from SLD, see Deleting System Descriptions from SLD in the SAP Community Network.

Resynchronization from SLD (with or Without Deletion of Assignments)

For the following reasons, a restore of technical system descriptions from SLD can be required:

The system was changed manually with the Technical System Editor.

Incorrect system information was migrated from SMSY.

Inconsistent system descriptions were created in LMDB by two different SLDs. If the data in the SLDs differs (e.g. one SLD with data supplier, and one with manual data import), LMDB data can be inconsistent.

Simply deleting the system in LMDB and triggering the SLD data supplier again does not solve the problem. This would only update the information that has changed since the last system registration, and a skeleton of the technical system would appear in LMDB rather than the whole system description.

Resynchronization by Resync from SLD Function

As of SP03, you can restore the complete technical system description from SLD directly in the Technical System Editor. Click the Resync from SLD button. If there is more than one SLD connected, you have to select one. You can review the changes made by the resynchronization before you click the Save button to persist them.

Only data from automatic SLD data suppliers is synchronized.

Data created manually in LMDB and assignments are not deleted by this function. All assignments, for example product assignments, do remain (they are deleted during the resynchronization process but are immediately recovered). If you need to delete even the assignments, see the next section (Resynchronzation Report).

Note

For SP03, this function does not work for technical systems that you deleted manually. In this case, use the resynchronization report, which is described in the next section.

Resynchronization by Report

In SP02, the RLMDB_SYNC_TECHNICAL_SYSTEM report is the only way to resynchronize data from

SLD. To restore SLD data, use this report. It also enables you to delete all assignments, if you want to.

If you deleted system information in LMDB manually, you have to use this report to restore the information. The Resync from SLD function does not work.

Note

If data is inconsistent in SLD, for example because the same system is described differently in two SLDs attached to your LMDB, remove the incorrect information from the SLD first.

- 23 -

Proceed as follows:

1. Start transaction SE38 and run the report RLMDB_SYNC_TECHNICAL_SYSTEM.

2. Enter the following parameters:

Source SLD: Select the SLD with the correct system description.

Target Namespace: Select the LMDB target namespace; in most cases, this would be

active.

System Type

Extended SID

Set the Detailed Trace indicator

Delete before Resync indicator: Choose this indicator to delete the entire technical system description in LMDB before resynchronization from SLD. If you do not choose this indicator, the system carries out a resynchronization without deleting assignments and manually created information. In this case, the running the report would have the same effect as the Resync from SLD function in the Technical System Editor. For more information, see Resynchronization from SLD.

Caution:

Selecting this option deletes all data that you entered manually, for example product assignments.

3. Run the report

The synchronization can take a few minutes, depending on the number of CIM instances.

Special Settings and Functions of the Technical System Editor

Maintain Extended System IDs (ExtSIDs)

A technical system is uniquely identified by its system type and an ExtSID. By default, the ExtSID is defined automatically by LMDB. SAP systems have a predefined, three-digit system ID (SID) from which the ExtSID is derived. If possible, SID and ExtSID are kept identical. In case of duplicate SIDs

for a given system type, a suffix with 5 digits is appended to the ExtSID. (Example: From SID C1D,

ExtSID C1D00001 can be derived).

Many SAP Solution Manager Applications use the ExtSID to identify a technical system. Therefore the ExtSID should not be changed after the system is used by any SAP Solution Manager application because this may result in data inconsistencies.

For an ExtSID, LMDB only accepts uppercase letters and numbers. The ExtSID must consist of three to eight characters. If there are less than three characters, LMDB adds zeros. An ExtSID of more than eight characters is truncated. LMDB deletes special characters and Unicode characters.

Note

In case of a dual stack, the automatic generation of ExtSIDs cannot ensure the ExtSIDs of AS ABAP and AS Java are the identical.

You can manually change the ExtSID as long as you did not execute the Managed System Setup in the Solution Manager Setup for this system.

The preferred way to change an ExtSID is to do it manually, as described before. Additionally, as of

version SP02, customers can also use a BAdI implementation (LMDB_EXTSID_GENERATOR) to

change the proposed value of the extended system IDs.

Technical System Software Installed Flag

- 24 -

Set the Installed flag if the selected entity is installed physically on the system. Software is sometimes assigned, but the corresponding executables are not physically installed; in this case, the flag is not set. The flag is not set if the software is Diagnostics-relevant but not installed.

Technical System Software Diagnostics-Relevant Flag

You can set the Diagnostics Relevant flag for Product Versions in combination with product instances. It defines which of the assigned entities will be used by the Diagnostics application.

Background: In some cases, the installation of add-ons can update the version of software components of a product. But Diagnostics is still supposed to refer to the original version of the underlying product. To do so, the flag is used to define content that should be used for Diagnostics instead of the content that is really installed.

Maintenance of Custom Attributes

In LMDB you can maintain Custom Attributes for servers, technical systems, and hosts. The information is transported to and used by SMSY (for example to filter systems according to their location). Standard attributes are Location, Manufacturer, Monitoring System, or Release.

You can maintain Custom Attributes for technical systems and servers (hosts):

Technical System Editor Define Header Data Custom Attributes tab

Host Editor Define Header Data Custom Attributes tab

To create new Custom Attributes, access transaction SMSY and select any system under Select Object. Then choose Utilities Attribute Definition. After saving a new definition, the new attribute will be available to select in the Technical System Editor of LMDB.

Host Editor

Host descriptions come from SLD and, in more detail, from the SMD agent of Outside Discovery, which writes directly to LMDB.

To maintain the definitions, you can use the Host Editor. To do so, go to SAP Solution Manager Administration Landscape and select Hosts. Select a host and choose Host Operations Maintain Host.

Maintenance of FQDN and IP address

In the Host Overview the FQDN (fully qualified domain name) and the corresponding IP address is shown. For example the FQDN is important for some configuration tasks and the URL Framework. Alternative FQDNs and IP addresses are listed under Alternative Hostnames. Those alternatives are related to the multiple possible network configurations on the host.

For the single value used in the Host Overview, LMDB receives the FQDN and IP address from the data supplier with the highest rank. This may not be the preferable value; in this case you have two options:

Change the FQDN manually, using one of the alternative hostnames. This implies that the FQDN is no longer overwritten by changes reported via SLD or Outside Discovery.

Access the Technical System Editor and choose Resync from SLD. Select the SLD that contains the correct FQDN and IP address.

For host information coming from Outside Discovery: Change the FQDN in the SMD Agent, using the correct alternative name, which then will be transferred to LMDB. For more information, see SAP note 1626853.

To find out which data supplier did provide the host information, check the Details in the System Overview of the Technical System Editor.

For more information, see Cannot Create RFC Connection Because the Host FQDN Is Wrong in the Troubleshooting section.

- 25 -

Deletion of a Host

The deletion of hosts in the Host Editor of LMDB is supported as of SP03.

Migrate SMSY Data to LMDB (One-Time Activity) SMSY can contain manually created system description for which no data suppliers are available, or manually added data. To reduce the manual effort for initial transfer of this data to LMDB, you can migrate data once from SMSY to LMDB. This can be done only once. There are two different types of migration:

System-oriented migration: for transfer of system descriptions from LMDB to SMSY when no data suppliers are available.

Aspect-oriented migration: for transfer of a single kind of information for all systems in SMSY to LMDB. It is the recommended way to migrate manually maintained data.

System-Oriented (Complete) Migration

System-oriented migration transfers system description from LMDB to SMSY for which no data suppliers are available (For more information, see Register Technical System Automatically). If you do not have such systems, you do not require this type of migration.

Note

Only migrate systems for which you cannot configure data suppliers, for example because of a firewall. If possible, do not create landscape data manually. Collect it automatically from data suppliers instead, so that the information is updated regularly. Also avoid migration of manually created data.

Only system description that is sufficient to create an LMDB entry is migrated. You can check your system descriptions in SMSY with the Landscape Verification tool. The tool is available in SAP Solution Manager 7.0 as Add-on. With SAP Solution Manager 7.1 it is automatically installed. For more information, see Landscape Verification in the SAP Community Network.

System descriptions that you cannot migrate, can be maintained manually in the Technical System Editor of LMDB, if absolutely necessary.

To avoid superfluous effort, only migrate or create system descriptions that are really necessary. Not all data from SMSY needs to be required. Consider a SMSY clean-up before migration.

To migrate technical system descriptions from SMSY to LMDB, proceed as follows:

1. Start SAP Solution Manager: Configuration (transaction SOLMAN_SETUP) and choose System

Preparation Prepare Landscape Set Up LMDB.

1. Switch to Edit mode and choose Migrate from SMSY to LMDB.

2. Select the required systems and choose Migrate Selected Rows. The migration runs in a background job. Each system takes a few minutes, depending on its type and size.

3. When the background job has finished, you can choose Display Log, to display the migration log containing success or error information.

For the following system types, system-oriented migration is supported:

System-Oriented Migration for AS ABAP

Complete migration is supported for ABAP application servers and all system entities, for example, clients, instances, software components, and other attributes.

- 26 -

Prerequisites:

o You have performed the basic configuration of LMDB.

o You have initially synchronized SLD and LMDB.

o Users and authorization for SAP Solution Manager: SAP_SYSTEM_REPOSITORY_ALL

role

o You have maintained the following data in SMSY for ABAP application servers (ABAP):

Installation Number

Message Server

A database must be assigned to the system.

The Server of the assigned database must be maintained.

The Manufacturer of the assigned database must be maintained.

System-Oriented Migration of Master Data Management Server (MDM)

Migration of the entities instance, database, software component and other attributes are supported for the type Master Data Management server.

Prerequisite: You have assigned the correct product instances of a product system to the technical system.

Example: You have a technical system of type MDM with a technical instance with MDM Server server roll, and a product system with product version SAP MDM 5.5. In this case, the technical system must be assigned to the product instance Master Data Server.

For MDM - Layout Server, Import Server, and Syndication Servers, the following prerequisites apply:

o The extended system IDs (ExtSIDs) of technical and product systems must be identical.

o The software components for the technical instances, for example the MDM_SERVER

software component in the MDM Server server role, must be in the technical system.

o The technical system has an instance in the MDM Server server role.

o You have maintained the Instance Number and Server.

o You have maintained the Instance according to the SMSY naming convention.

o A database must be assigned to the system.

o You have maintained the Server of the assigned database.

o You have maintained the Manufacturer of the assigned database.

System-Oriented Migration of Unspecific Cluster System (UNSPECIFIC)

Migration of the entities Instance, Database, Software Component and Other Attributes are supported for the type Unspecific Cluster system.

Prerequisites:

o You have assigned a database to the system in SMSY.

o You have maintained the Server of the assigned database.

o You have maintained the Manufacturer of the assigned database.

o You have assigned one or more product instances of a product system to the technical system.

o The extended system IDs of technical and product systems must be the same. Software components must be maintained in the system.

- 27 -

Aspect-Oriented Migration

Aspect-oriented migration transfers one single kind of information for all systems in SMSY to LMDB, for example manually maintained information under Other Attributes or relevant product instances of technical systems. It is the recommended way to migrate manually maintained data from SMSY to LMDB. Usually all system types from SMSY are supported.

You can migrate the following aspects of technical systems:

Installed Product Instances:

As of SP03, choose Solution Manager: Configuration (transaction SOLMAN_SETUP) Basic

Configuration Configure Manually Migrate Installed Product Instances Data. For SP01 and SP02, see SAP Note 1607771.

Diagnostic-relevant product instances:

As of SP03, choose Solution Manager: Configuration (transaction SOLMAN_SETUP) Basic

Configuration Configure Automatically Migrate Diag relevant flags. For SP01 and SP02, see SAP Note 1608341.

Other Attributes (Custom Attributes) can be migrated as of SP03 with transaction

LMDB_MIG_CUST_ATTR.

Prerequisites:

You have maintained the product systems properly.

System must exist in both SMSY and LMDB. During migration, the system checks this based on the extended system ID (ExtSID).

The specific aspect must be maintained in SMSY, for example, a system must have values under Other Attributes.

The specific aspect must not be maintained in LMDB yet, for example, a system must not have values under Custom Attributes and in the Landscape Pattern field in LMDB.

Technical Scenario A technical scenario is a group of technical systems which work together, technically. For example, you can monitor the availability and performance of the connections of all technical systems in a technical scenario, with Connection Monitoring. Information about technical scenarios is saved in the LMDB.

Prerequisites to use technical scenarios in SAP Solution Manager:

You have performed the basic configuration of LMDB.

You have initially synchronized SLD and LMDB.

To create or change a technical scenario in LMDB, you need the

SAP_SYSTEM_REPOSITORY_ALL role in SAP Solution Manager. Special LMDB authorization

objects can restrict authorization. Copy the role to your namespace and change it.

Create a technical scenario:

In the SAP Solution Manager: Configuration (transaction SOLMAN_SETUP), choose Technical Scenario

Wizards under Related Links Configuration. Choose Create and follow the procedure.

Change a technical scenario:

In the SAP Solution Manager Configuration (transaction SOLMAN_SETUP), choose Technical Scenario

Wizards under Related Links Configuration. In Technical Scenario Maintenance window, select a system and choose Maintain.

- 28 -

Dual Stack Technical Scenario in Managed System Configuration

The simplest case of a technical scenario is a dual stack (AS ABAP and AS JAVA).

To view technical scenarios for dual stacks, start SAP Solution Manager: Configuration (transaction

SOLMAN_SETUP), choose Managed System Configuration Technical Scenarios and filter for

technical scenarios of type DBL_STACK (Dual Stack).

Dual stacks are usually identified automatically, and the system creates a DBL_STACK technical scenario. You can use these technical scenarios to configure the managed system for both stacks at the same time.

Create a DBL_STACK technical scenario

It can happen that a technical scenario is not created automatically for a dual stack system, for example, if the technical systems have not been registered in SLD for some time, or if the technical systems were registered in SLD in the wrong sequence. The information that it is a dual stack system comes from the ABAP system; therefore, the dual stack is not recognized if the Java stack is registered in SLD after the ABAP stack. In this case, register the ABAP stack in SLD again or wait for 24 hours. Then, there should be a DBL_STACK technical scenario for this system.

If required, you can also create a DBL_STACK technical scenario manually:

Start SAP Solution Manager: Configuration (transaction SOLMAN_SETUP), choose Managed System

Configuration Technical Scenarios Scenario Operations Create Scenario and follow the procedure.

Change a DBL_STACK technical scenario

To edit an existing technical system of type DBL_STACK, Start SAP Solution Manager: Configuration

(transaction SOLMAN_SETUP), choose Managed System Configuration Technical Scenarios

Scenario Operations Maintain Scenario.

RFC Connections As of SAP Solution Manager 7.1, technical systems are saved in LMDB, and RFC connections between SAP Solution Manager and managed systems can be created or edited in LMDB.

Prerequisites:

You have performed the basic configuration of LMDB.

You have initially synchronized SLD and LMDB.

Users and authorization in SAP Solution Manager: SAP_SM_BASIC_SETTINGS role. This

role is, for example, assigned to the user SOLMAN_ADMIN, which is created at the start of the SAP Solution Manager.

Configuration of RFC Connections During Managed System Configuration

1. Start SAP Solution Manager: Configuration (transaction SOLMAN_SETUP) and choose

Managed System Configuration Technical Systems tab.

2. Select a system and choose Configure System.

3. Follow the guided activity. The RFC connection is configured in step 3.

- 29 -

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:

Access Solution Manager: Work Centers (transaction SOLMAN_WORKCENTER) Related

Links SAP Solution Manager Administration Infrastructure Administration LMDB Administration.

Start transaction LMDB_ADM.

LMDB Administration provides the following options:

Displaying a status overview about LMDB considering performance and configuration aspects (available as of SP03).

Searching for information in LMDB with various search criteria. You can add or delete search rows and save search criteria for future searches.

Displaying CIM class and instance information

Changing CIM instance attributes

Deleting CIM instances, and delete multiple technical systems

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.

- 30 -

Troubleshooting

Damaged Technical System Description in LMDB

Example: Additional clients have been created manually in SLD to configure SAP Process Integration. This data has been imported via content synchronization and mixed up with the correct description in the SAP Solution Manager SLD. This results in an overlap: Different system descriptions in different source SLDs and duplicate entries for the system clients are created in LMDB.

Run a re-synchronization from SLD.

For more information, see Resynchronization from SLD (with or Without Deletion of Assignments).

Restore a Deleted Technical System

If a technical system has been deleted from LMDB, its ExtSID and any key information is no longer known in LMDB. Neither the re-synchronization from in the Technical System Editor nor the report RLMDB_SYNC_TECHNICAL_SYSTEM can recover data from SLD without the ExtSID. To load all data of a deleted system into LMDB again, perform the following steps:

1. Log on to the source SLD.

2. Go to CIM Instances (in NetWeaver 7.0: Content Maintenance).

3. Choose the CIM class for your system type.

System Type Name/Caption CIM Class

ABAP Application Server ABAP SAP_BCSystem

ATC Apache Tomcat Server SAP_ATCServer

BOBJ Business Objects Cluster SAP_BOCluster

DBSYSTEM Database System SAP_DatabaseSystem

DIAGNAGENT Diagnostics Agent SAP_DiagnosticsAgentInstance

IS_EM Introscope Standalone Enterprise Manager

SAP_ISEMServer

IS_MOM Introscope Enterprise Manager Cluster

SAP_ISMOMServer

JAVA Application Server Java SAP_J2EEEngineCluster

LIVE_CACHE liveCache SAP_LiveCache

MDM Master Data Management Server SAP_MDMDataServer

MS_.NET .NET System SAP_DotNetSystemCluster

MSIISINST Microsoft Internet Information Services

SAP_MSIISInstance

THIRDPARTY Generic Application System SAP_ApplicationSystem

TREX TREX System SAP_TrexSystem

UNSPAPP Unspecific Stand-alone System SAP_UnspecificStandaloneApplicationSystem

UNSPECIFIC Unspecific Cluster System SAP_UnspecificClusterSystem

WEBDISP SAP Web Dispatcher SAP_BCWebDispatcher

WEBSPHERE IBM WebSphere Cell SAP_IBMWSCell

4. Filter to find your system, for example by SID or host name.

5. Make a pseudo-change to your system, for example:

1. Add an X to the description.

2. Save the change.

3. Reverse the change.

4. Save again.

- 31 -

6. Wait until the changes are replicated into LMDB. The key instance and the extended SID, but no detailed system information, are written to LMDB.

7. To transfer all the system information to LMDB, use the Resynch from SLD button, as described under Resynchronization from SLD.

Running Job Leads to Quick Completion of Following Jobs

If you notice that one or more jobs for incremental synchronization are completed very quickly (within seconds) with status OK, there are two possible reasons:

There are no pending changes to be synchronized.

Solution: No action required.

A predecessor job is processing a large number of pending changes and has not finished yet. In this case, following jobs are immediately set to complete in order to let the preceding job finish synchronization properly. Only when the running job is finished, the following jobs will run productively again.

Solution: Wait until the predecessor job has finished.

Cannot create RFC Connection Because of Wrong Host FQDN

Problem: You cannot create an RFC connection because the FQDN of the host is incorrect.

Solution for SP02:

For host information from Outside Discovery: Change the FQDN in the SMD Agent, using the correct alternative name, which then will be synchronized into LMDB. For more information, see SAP Note 1626853.

For host information from SLD: Access the Technical System Editor, choose Resync from SLD, and select the SLD containing the correct FQDN. Or change the FQDN manually in the System Overview, using one of the alternative hostnames.

Solution for SP03:

For host information coming from Outside Discovery: Change the FQDN manually in the header data, using one of the alternative hostnames. Outside Discovery will not overwrite the value anymore.

For host information coming from an SLD: see Solution for SP02.

To find out which data supplier did provide the host information, check the Details in the System Overview of the Technical System Editor.

Note

You can see all available alternative FQDNs and IP addresses under Alternative Hostnames in the Host Editor. You have to pick the correct one from this list.

Performance Issues During Synchronization

For information on how to check the progress of synchronization, see Monitoring the Synchronization Process.

- 32 -

Performance Issues Because of Exhausted Shared Memory

The LMDB in SAP Solution Manager 7.1 relies on ABAP shared objects in the shared memory of the application server. If the shared memory of the server is exhausted, or if the shared memory segment for the LMDB cannot be created for other reasons, LMDB processes will access the database instead of shared memory. This effects long response times. This behavior becomes obvious in the work

process overview (transactions SM50 and SM66) where a lot of work processes are accessing the

LMDB_P_CLASS table.

Check whether the shared memory area is used:

In SP02:

Log on to the SAP Solution Manager system with an administration user, start transaction

SE38, and execute the RLMDB_SHM_READ_TEST report. The report tries to read data from the

shared memory area (CL_LMDB_MODEL_SHM_AREA), and this should be the result:

Reading Changelog OD: <number> in Namespace ID: LDB:0000000001 If this is not the result, the report tries to create the shared memory instance and provides a message about its current status. For more information about shared memory-handling in the context of LMDB, please refer to Administration of ABAP Shared Memory Areas for LMDB in the next section.

In SP03:

Start transaction LMDB_ADM (LMDB Administration). Check the shared memory status on the

Content Synchronization Status tab.

Administration of ABAP Shared Memory Areas for LMDB

Shared memory objects are ABAP object instances in the shared memory of the application server, which allow that data is shared in various user sessions. This is quicker than individual database accesses. At runtime, LMDB uses ABAP shared objects to buffer CIM class information in shared memory.

The Shared Objects Monitor (transaction SHMM) provides an overview of the area instances in shared

objects memory of the current application server. For more information, see: Shared Objects Monitor – Transaction SHMM in the SAP Help Portal.

The area relevant for LMDB is CL_LMDB_MODEL_SHM_AREA. It has a size of about 15 MB.

The size of all objects in shared memory is specified by the abap/shared_objects_size_MB profile parameter.

On the Shared Objects Memory tab in SHMM, you can see how much shared memory is currently in

use, and how much free space remains.

Use of Shared Memory

When LMDB processes run, class information is read from shared memory. You can get the number of successful read accesses from the field „Accumulated Read Locks“ in the transaction SHMM.

If there is not enough memory for the shared memory segment, or the shared memory segment CL_LMDB_MODEL_SHM_AREA cannot be created, the system reads class information from the database always, with dramatic performance impact.

From SAP Solution Manager Release 7.1 SP1, there is an alarm in the Self-Monitoring area of the SAP Solution Manager Administration work center, if the shared memory area for LMDB cannot be created.

No Progress in Incremental Synchronization

If the incremental synchronization between SLD and LMDB does not finish after a long time, proceed as follows:

- 33 -

1. Check whether the synchronization is still active under transaction SOLMAN_SETUP System Preparation 6.5 Setup LMDB. If it is active, click Details. If the number of Pending Source Changes is larger than 0, and if the Date of Source Change Log ID is in the past, the changes are not going through and the connection between source and target is probably corrupt. Reasons can be, for example, that shared memory is exhausted, database statistics are outdated, or SLD is down.

2. To create a job overview, start transaction SM37, enter *LDB* under Job Name and an

asterisk (*) under User. Check the job logs and look for the error messages.

Error Because of Changed Object Server Name

The job log can provide the following error: “A change of object server name in the source system has been detected”. This means that someone has changed the name of the object server, which LMDB now cannot identify correctly any longer. Pending changes from SLD are not transferred to LMDB.

If the name change of the object server was made on purpose in SLD, proceed as follows:

1. Rename the object server name to its previous name under SLD Administration Profile Object Server.

2. Wait for about ten minutes and return to transaction SOLMAN_SETUP System Preparation

6.5 Setup LMDB to check whether all pending changes are being processed completely.

The job log in SM37 must not show any more errors.

3. Delete the SLD synchronization in SOLMAN_SETUP.

4. Repeat the change of the object server name in SLD.

5. Create a new SLD synchronization in SOLMAN_SETUP.

If the name change in SLD was made by mistake, only carry out step 1 and 2.

Outdated Oracle Database Statistics

If the SAP Solution Manager system is installed with an Oracle database, statistics can be outdated. After the installation or upgrade of the SAP Solution Manager 7.1 system, most LMDB tables are empty. If statistics are calculated at this time, the Cost Based Optimizer (CBO) will tend to run a full table scan during all subsequent database accesses. If the LMDB tables are continually filled, for example because of full automatic synchronization of SLD and LMDB, the real costs for the full table scan become higher and higher, without the CBO realizing this.

After you started the content synchronization between SLD and LMDB, you have to ensure that the

Oracle database statistics are updated. To do so, start transaction DB20 with parameter

LMDB_P_INSTANCE and check the optimizer statistics. In case the statistics are out-of-date, use the

Update Statistics with BRCONNECT function. For more information, see Update Statistics with BRCONNECT in the SAP Help Portal.

For best performance, it is recommended to update the statistics repeatedly while the content synchronization job is running. This will force the Cost Based Optimizer (CBO) to realize the increasing fill level of the LMDB tables.

Make sure to update statistics for the following tables as well:

LMDB_P_ASSOC (Associations)

LMDB_P_CHANGELOG (Change Log)

LMDB_P_CLASS (Classes)

LMDB_P_GUID (GUIDs of Instance References)

LMDB_P_LONG_VAL (Long Value Storage)

LMDB_P_NAMESPACE (CIM Namespaces)

LMDB_P_PQ_NAMES (Hash Values for Names)

LMDB_P_QUALIFIER (CIM Qualifier Declarations)

- 34 -

You can update the statistics with BRCONNECT while the content synchronization job is running. It is

recommended that you do not stop the synchronization job for a statistics update. The performance improvement will become effective automatically, whereas a new synchronization job will take some time to check and process data up to the point where it was interrupted during the full automatic synchronization.

For more information, see SAP Note 1555955.

Unicode Characters in a Non-Unicode LMDB

If system descriptions in an SLD include characters that are Unicode characters, they are replaced by a hash (#) in the LMDB description on a Non-Unicode SAP Solution Manager system.

Therefore, avoid the maintenance of Unicode characters in SLD.

- 35 -

Glossary Outside Discovery in SMD Agent:

The Outside Discovery is part of the SAP Solution Manager Diagnostics Agent (SMD Agent) within the Agelet called DCC. The purpose of Outside Discovery is to automatically discover, collect and send information from the monitored system to SAP Solution Manager.

Product:

An SAP offering in the SAP price list. It performs business tasks. All products are specified in the Product and Production Management System (PPMS).

Example: SAP ERP

Product version:

A version or release of an SAP product. Like products, these are defined in the Product and Production Management System (PPMS).

Example: SAP ERP 6.0

Product instance (previously main instance):

The smallest installable entity of a product. A product instance is both a technical entity, because it can be installed, and a functional entity, because the various product instances in a product perform various tasks.

Example: SAP ECC Server

Technical system (previously system component for non-ABAP systems):

Self-contained technical unit which is installed and administered as a whole. Technical systems may consist of technical (sub)systems.

Product system (previously system):

Grouping of technical systems which belong to one or more products.

Example: SAP Solution Manager. A product system SAP Solution Manager comprises one technical system ABAP and one technical system JAVA.

Software component:

Set of software objects grouped in packages and delivered together. A software component usually exists in several release versions, which are updated by upgrades. You can import support packages separately for each software component.

Example: SAP_BASIS, SAP_HR

- 36 -