Landscape Management Database (LMDB

)

S AP S o l u t i o n M a n a g e r 7 . 1 S P 0 2 a n d S P 0 3

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.

-2-

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 -

-3-

technical system data can only be maintained in the technical system editor of LMDB. The tool Landscape Verification can support this clean up.1. There is a migration of technical systems data from SMSY to LMDB.1 and since then is mandatory. LMDB was introduced in SAP Solution Manager 7. with different technologies.dmtf. As of SAP Solution Manager 7. It is highly recommended to clean up the technical systems in SMSY before upgrade to 7.Introduction: Landscape Management Database (LMDB) The Landscape Management Database (LMDB) is a directory of the elements in a system landscape. for different purposes. If you upgrade SAP Solution Manager from release 7. LMDB aims for a more flexible extendibility of the landscape model and the unification of SLD and SMSY in SAP Solution Manager. analogously to the System Landscape Directory (SLD). you must configure LMDB.0 to 7. The SAP Solution Manager System Landscape (transaction SMSY) and SLD already provide comparable functions. delete old technical systems in SMSY that are no longer needed. E. -4- .1. “systems“. “products“. and “software components“. Typical model elements are “computers“.g. see www. not in SMSY any longer.org.1. The corresponding chapter within the Setup Guide provides more details. LMDB uses the SAP enhancement of the Distributed Management Task Force (DMTF) Common Information Model (CIM) to describe the landscape elements. The main task of LMDB is to centrally provide information about the system landscape. For more information about CIM.

and the CR content are initially synchronized with LMDB by a Full Automatic Synchronization. maintain or enhance technical systems. Technical system descriptions are continuously replicated from LMDB to SMSY (every 5 minutes). SMSY receives some additional system information. 1. In addition.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. The technical system information. The landscape descriptions are used. 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). directly from ABAP systems via RFC (once a day). such as license information. to monitor. The data supplier registers technical systems in SLD 2. -5- . and then by incremental synchronization every 10 minutes. 5. 3. for example. the CIM model.

Most data suppliers currently send their data to SLD. A small part of the data suppliers. All data that is in a connected SLD already can be read by LMDB.) Managed Systems: Non-Productive Environment Other systems (prod. This content. previously manually-entered data is not refreshed or overwritten. The data suppliers are implemented in the managed systems. is transported into SLD and synchronized 1:1 into LMDB. The automatic registration of systems to SLD. independently of the technical data flow:  SLD Data Supplier Technically. For more information. SAP CR CONTENT. LMDB is the ABAP complement of Java-based SLD. so manually entered data can become obsolete. immediately after upgrading SAP Solution Manager to version 7. see SAP note 669669. SLD and LMDB synchronize contents in the same way two SLD systems do. Synchronization of SLD and LMDB contents put this data 1:1 in the LMDB. writes its data directly in the LMDB.Systems Managing Systems SAP Solution Manager LMDB Data Supplier registrat. or the data supplier cannot be used. for example the ABAP application server (AS) with the transaction SLD Administration (RZ70).)  SAP software catalog (CR content) Data about usable products and software components is delivered in the SAP Service Marketplace.1. The disadvantage of this manual method is that the data is not updated automatically. The step in the transaction SOLMAN_SETUP copies SMSY data to technical systems in the LMDB. -6- . „Outside Discovery“. and its synchronization with the LMDB is the preferred way of putting landscape elements in the LMDB. usually only once. (Synchronization from LMDB to SMSY makes technical system data in LMDB accessible to read applications in from SMSY. for example because of a firewall.) NWDI PI (non-prod.) Managed Systems: Productive Environment Sources Providing LMDB Content The content of LMDB comes from the following sources.) Systems (non-prod. of Technical Systems Forwarding of data on Technical Systems Manual export/ import (optionally using CTS+) SLD Sync (unidirectional) SLD (design-time) SLD (runtime) PI (prod.  SAP Solution Manager System Landscape (SMSY) Data migration from SMSY to LMDB is a special case of a data supplier.  Technical System Editor in LMDB Systems are registered manually in the Technical System Editor in LMDB if there is no data supplier. If the system is subsequently registered.

SMSY and LMDB in a system landscape. This is the recommended configuration. under (Landscape Verification) Variants of LMDB Integration The following graphics explain the interaction of SLD. LMDB is then synchronized with SMSY (3).  Landscape Verification Tool The Landscape Verification Tool analyzes whether your system landscape. and is put in LMDB via SLD. is maintained correctly in the SAP Solution Manager System Landscape (transaction SMSY). which is then synchronized with LMDB (2a). data is migrated (4). and. if required. see the SAP Community Network. in the recommended configuration: Integration 1 The systems in the system landscape are registered in a remote SLD (1a). For more information. particularly the assignment of product systems. SAP CIM model The current SAP CIM model is also in the software component SAP CR CONTENT. -7- . like the SAP software catalog.

data is migrated (4). LMDB is then synchronized with SMSY (3). and. It should be the remote SLD with the newest CR content. one technical system must be registered on only one SLD. but only one remote SLD can provide the CR content for LMDB. Note: If multiple SLDs are connected to LMDB. otherwise inconsistencies may arise in LMDB. You specify which one when you configure LMDB. if required.Integration 2 The production systems in the system landscape are registered in a remote SLD (1a). 2b). and the nonproduction systems in another remote SLD (1b). -8- . Both remote SLDs can be synchronized directly with LMDB (2a.

If you have no remote SLD. Integration 4 In another variant. 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.0) (1c). use the local SLD in the SAP Solution Manager as central SLD for LMDB synchronization. when the LMDB is synchronized with more than one SLD system. For more information. without remote SLD.Integration 3 A variant is an additional local SLD in SAP Solution Manager. the systems register directly with the local SLD (SLD 7. which is filled by data supplier forwarding (1b). -9- . you can also use the local SAP Solution Manager SLD. see the SLD Planning Guide in the SAP Community Network. the unique path principle for data needs to be fulfilled. If there is no SLD in your system landscape (or if there is only an outdated SLD). Synchronization of one LMDB with more than one SLD System As in other mechanisms of data exchange. and which then fills LMDB (2b).

an SLD satisfies the minimum requirements for LMDB: SAP NetWeaver Release (SLD) SAP NetWeaver 6. 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). patch 5 SP9 all SPs all SPs all SPs Although the minimum release requirements are lower.0 EHP2 for SAP NetWeaver 7. This way you have the latest . Invalid: Both SLDs are used in separated landscapes but connected with mechanisms of data exchange. because the unique path principle is violated. All other content cannot be filtered and therefore must not overlap. The figure shows two cases: a valid configuration on the left.3 Supported Support Package Stack Level not supported not supported not supported SP6. 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. 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. and an invalid configuration on the right.g. it is recommended that youuse a separate remote SLD with version 7.1 or higher for synchronization with LMDB.0 EHP1 for SAP NetWeaver 7.2 SAP NetWeaver 7. Note: All names (e.0 SAP NetWeaver 7. and since when (which support package stack). Practically. this can only be achieved if SLD systems connected to the LMDB run in separated landscapes. and whether. which makes connections to the same LMDB for both SLDs an invalid option.1 EHP1 for SAP NetWeaver 7.40 SAP NetWeaver 7.10 - . Only the central SLD of each landscape connected to the LMDB is shown here.1 SAP NetWeaver 7. which make connections to the same LMDB for both SLD a valid option.

If your central SLD does not have the required status. LMDB must be synchronized with several SLDs. all systems in the landscape register to one remote SLD directly. This SLD is the central data source for LMDB. which automatically register systems in SLD. If possible. Regular polling and notification ensure a robust synchronization. This can happen. There are data suppliers for most technical systems. if you have changed the system information (originally coming from SLD) with the LMDB Technical System Editor in the meantime. but several SLDs may contain contradictory data. you should make changes to technical systems by updating their registration in SLD. outside SAP Solution Manager. The usual case is to configure one central SLD for your whole system landscape.16 or higher Newest SAP CR CONTENT. Model and CR Content The CIM model and SAP CR content requirements are:   CIM model 1.11 - . The polling interval usually is ten minutes.SLD functional scope. the search for errors . (The local SLD in SAP Solution Manager has version 7.6. for example. (For more information. but not by making manual changes in LMDB. The contents of LMDB depend on the sequence of the changes in the various SLD systems. A ranking is defined between SLD and LMDB. at least version 7. Even if the procedure is theoretically unambiguously specified.02).0 For more information about updating CR content. It automatically determines which status „wins‟ in case of conflicts. The immediate notification of LMDB about changes in SLD accelerates the synchronization of changes in the SLD – LMDB – SMSY chain.1 SAP NetWeaver 7.1 EHP1 for SAP NetWeaver 7. LMDB receives the SLD changes automatically when a change occurs (using polling or notifications). just like between two SLDs. see SAP Note 1546079. you can use another SLD which does satisfy the minimum requirements (e. the SLD in SAP Solution Manager) and synchronize it with your central SLD. and generic data suppliers for most other products in the SAP environment. using SLD bridge forwarding functionality or by full automatic synchronization.2 SAP NetWeaver 7. A conflict exists if the status of an object on recipient side (LMDB) differs from what is expected by the source system (SLD). but active change notification from SLD to LMDB requires a higher version of SLD: SAP NetWeaver Release (SLD) SAP NetWeaver 7. see SAP Note 669669. There are two data supplier types: specific data suppliers for AS ABAP and AS Java.) Note the following recommendations when you plan the configuration of synchronization between SLD and LMDB:  Ideally.3 Supported Support Package Stack Level SP12 SP7 SP5 SP3 For more information. The remote communication uses HTTP(S). If this is not possible. The LMDB must always have priority. see SAP NetWeaver System Landscape Directory: Conflicts & Ranks in Full Automatic Synchronization in the SAP Community Network. Change notification from SLD All supported SLD-Versions support the polling of the information. this prevents changes in SLD from overwriting manual changes made in LMDB in the Technical System Editor.g.

When you start to configure LMDB. make the following entries: a. In a standard installation. Start transaction SOLMAN_SETUP and choose System Preparation  Prepare Landscape  Set Up LMDB. the user needs the role SAP_SLD_CONTENT_SYNC. it is always appropriate to use the server name as object server name. the system checks whether LMDB has an object server name. Example: http://sldserver:54300 c.0. b. The object server names should be different in all SLDs and LMDBs. you are prompted to enter a new object server name. If there is no assignment done before for the SLD namespace rank. Configuring LMDB for Synchronization with SLD To be able to use LMDB.1. LMDB queries SLD for changes every 10 minutes. This name. This is done during the basic configuration of SAP Solution Manager after installation or upgrade. the user at least needs the role SAP_SLD_GUEST. As of SLD 7. users need administration authorization For SLD: o o In SLD from release SAP NetWeaver 7. you must perform the basic configuration in the setup of SAP Solution Manager. In SLD from release SAP NetWeaver 7. For further naming recommendations.  Once it has been configured. In the Synchronization Connections between SLD and LMDB area. in combination with the CIM namespace. 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. Description: Enter a free text to describe the new SLD connection. Source Namespace: Enter the CIM namespace of the source (SLD). d. and you have to assign a rank to the namespace. The default namespace is sld/active. A window opens. (With SLD version 7. Procedure: 1. which is http://<host name>:<port>. incremental synchronization between SLD and LMDB is automatic. . If not.0 only polling is enabled.in several SLDs in the case of conflict can be time-consuming. This is also called polling.1. A previously selected rank number is displayed after you selected the namespace. SLD is running (see „Minimum System Landscape Directory (SLD) Requirements“) Users and authorizations: For SAP Solution Manager. the port is: 5<SLD system Java instance number>00. specifies the absolute path of the LMDB objects. choose Add. see SAP Note 935245. 2. Prerequisites:    You have performed all previous system preparation steps in SOLMAN_SETUP. the higher the rank.12 - . so it is better to use one SLD to supply LMDB. you can configure notifications to trigger processing of changes in a more timely fashion. Source URL: Enter the source URL for SLD. In LMDB. -1 is displayed as rank. To create a new synchronization connection.

f. only the target namespace active is supported. Within the job log you can find the information how many instances need to be synchronized. which are only available with SLD from NetWeaver version 7. If the source-namespace already had a rank you should not change the rank since this is the rank of the namespace in SLD. you will find two lines for each object type. To start content synchronization immediately. . Choose a number higher than the one for the source (SLD). runtime 390 s In this example. 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. depending. e. of SAP_Productfinished: 2661 creations. add 1000 to it. In addition.8 instances were processed per second.0. you can restart it. For LMDB in SAP Solution Manager release 7. which is not very good. The name of the synchronization job for the target namespace is SAP_LMDB_LDB_<namespace ID>. you can view information about the synchronization job. If the full synchronization job fails. It will continue with the last object before it has been cancelled. Start transaction SOLMAN_SETUP and choose System Preparation  Prepare Landscape  Set Up LMDB. 3. you have the following options:  Directly in SAP Solution Manager. 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.1 and supports notifications (see „Minimum System Landscape Directory (SLD) Requirements“. If you select this option and use SLD NetWeaver version 7. 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. only 6. If the same SLD does not support notifications. the system does not prompt for a target (LMDB) connection. Example: If a rank has already been assigned to SLD. Issues with Oracle statistics require manual activities some minutes after you started the synchronization. and the hardware.13 - .1. If you want to save your settings and activate them later.g.Example: To be flexible for subsequent changes in your synchronization landscape. use a rank of 1000 for the source and 2000 for the target.  Transaction SM37 (Simple Job Selection) displays jobs and logs.1 (see „Minimum System Landscape Directory (SLD) Requirements“. 4. Jobs usually run under the SOLMAN_BTC system user. The initial. For more information. enter the target (LMDB) connection information. full automatic synchronization with SLD can take several hours. choose Save and Activate. Rank of Target Namespace: Enter rank of the target (LMDB). You get a summary. on the number of systems in SLD. of SAP_Product: 2661 source instances. Synchronization with SLD starts when you activate the configuration. So changing this rank might have impact on other content synchronizations as well. Monitoring the Synchronization Process To monitor synchronization. for example: Full Sync. Specify whether you want to use notifications. 0 target instances Full Sync. see Outdated Oracle Database Statistics in the Troubleshooting section. you are later informed that this function is not available. e. SAP_LMDB_LDB_0000000001. 0 modifications. Target Namespace: If the source SLD has NetWeaver version 7. for example. Select a synchronization connection and choose Advanced. confirm with Complete.

So you can find the application logs related to LMDB.g. 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. Under Object. you can only change technical systems in the LMDB Technical System Editor.For more information . Prerequisites:    You have performed the basic configuration of LMDB in SOLMAN_SETUP (system preparation). like: o Error (default) o No logging o Error and Warning o Error. start transaction SM30 and maintain the view V_LMDB_LOG_CONF. Changes in SLD are polled at least every 10 minutes from LMDB (with notification this is significantly faster). but no longer in the SAP Solution Manager System Landscape (SMSY). see SAP note 1555955 (SAP Solution Manager 7.14 - . SOLMAN_BTC). see the following sources of information: o o o  SAP Note 1594654 Troubleshooting section. Status changes in LMDB are replicated to SMSY in less than 5 minutes. . it can happen that a change in LMDB is blocked by locks held by another user.1. If there are changes. at least every 5 minutes. But you still maintain product systems in SMSY and some SAP Solution Manager applications still get their landscape information from SMSY. LMDB Sync Log Insights in the SAP Employee Network Transaction SLG1 (Analyze Application Log) display logs. To increase the log details level of SLG1 logs. The log level can be set per user and sub-object in LMDB. Integration with SAP Solution Manager System Landscape (SMSY) As of SAP Solution Manager 7. they are logged in the LMDB change log. Several log levels are supported.Performance Checks for LMDB). If a blocking situation exists for a longer period of time. A check is made for new changes. all technical system data is written to SMSY. Usually blocking locks are released in the meantime and pending changes can be processed. check the lock entries. all relevant technical system information must be continuously synchronized from LMDB into SMSY. Under Table name. Users and authorizations in SAP Solution Manager: The SAP Solution Manager batch user (e. enter AI_LMDB.1 . For known issues with the full synchronization job. Warning and Info  Transaction SM12 (Select Lock Entries) displays locked jobs. Therefore. which was created during Setup (SOLMAN_SETUP). SLD and LMDB have been initially synchronized. The next scheduled sync job will continue at the same point later. 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. enter LMDB*. During content synchronization.

from SMSY. and create LMDB data. SAP Solution Manager – Work Centers (transaction SOLMAN_WORKCENTER) In the Solution Manager Administration work center. For further information. see Landscape Verification in the SAP Community Network. the system writes the changes directly to SMSY. To centrally view.15 - Notes . Other SAP Solution Manager applications get their landscape data.So changes in SLD are replicated via LMDB towards SMSY in less than 15 minutes (under normal circumstances). 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. change. Diagnostics. 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.  Automatic synchronization of changes written manually to LMDB by the Technical System Editor When you save changes made with the Technical System Editor. To access LMDB Administration. and how to edit them: Entity Data Source Editor . Working with LMDB A lot of SAP Solution Manager applications (such as the work centers. directly from ABAP systems via RFC connection once a day. Note that SMSY also receives some additional system information. start transaction LMDB_ADM. you can use the following transactions:    SAP Solution Manager Configurations (transaction SOLMAN_SETUP) Choose Managed Systems Configuration. You can use transaction LMDB to directly enter the LMDB Editors like Technical System Editor and Host Editor. All other information is provided by SLD via LMDB. especially product system and logical component data. such as license information. their data sources.. particularly the assignment of product systems. So there should be no delay. choose Landscape. Integration with Landscape Verification The Landscape Verification tool analyzes whether your system landscape. is maintained correctly in the SAP Solution Manager System Landscape (transaction SMSY). and several steps in transaction SOLMAN_SETUP) receive their system landscape information directly from LMDB.

outside discovery Technical System Editor SOLMAN_SETUP SOLMAN_SETUP Technical System Editor Technical System Editor Technical System Editor Technical System Editor Technical System Editor Technical System Editor Technical System Editor Technical System Editor Technical System Editor Not in SAP Solution Manager 7.1 SP1 Outside Discovery enhances the system information of SLD data suppliers.NET System TREX system SAP Web Dispatcher IBM WebSphere Cell Unspecific application system Host SLD data supplier Manual Manual SLD data supplier SLD data supplier (AS ABAP) SLD data supplier Outside discovery Manual SLD data supplier SLD data supplier SLD data supplier SLD data supplier SLD data supplier.16 - . Dual stacks (AS ABAP + AS JAVA) recognized automatically No installed application product information No installed application product information Configuration from SOLMAN_SETUP Configuration from SOLMAN_SETUP Technical scenario Manual SOLMAN_SETUP Product system Logical component Manual Manual SMSY SMSY Register Technical Systems Automatically (Recommended) The preferred way of creating system landscape information in LMDB is automatic system registration. Most of them send their data to SLD. outside discovery Technical System Editor Technical System Editor Technical System Editor Technical System Editor Outside Discovery enhances the system information of SLD data suppliers.ABAP application server Apache Tomcat server Business object cluster Database system SLD data supplier SLD data supplier SLD data supplier SLD data supplier. This data is sent 1:1 to LMDB by synchronizing the contents from SLD. The data suppliers are implemented in various systems. . No installed application product information Diagnostics Agent Introscope Enterprise Manager Server Introscope Manager of Manager Java application server LiveCache Master Data Management server Microsoft internet information service .

For more information. so manual post-processing in LMDB is not required. . under http://sdn. Business Object Cluster (BOBJ) There is a data supplier for Business Objects Enterprise (BOE). The Outside Discovery delivers software component information. AS ABAP. in the SAP Solution Manager transaction SOLMAN_SETUP. and writes directly into LMDB. For other BOBJ products. which is sufficient for database systems. You have initially synchronized SLD and LMDB.17 - . which delivers product information. Information for some other system types must be created manually. The SMD agent Outside Discovery delivers all the information directly to LMDB (the information is not available in SLD). see the product IMG. Detailed information about individual products is beyond the scope of this setup guide. Database System (DBSYSTEM) Database system information is delivered by various data suppliers. For hosts. SLD user: SLDDSUSER or another user with SAP_SLD_DATA_SUPPLIER role. Outside discovery enhances the system information. Introscope Manager of Manager (IS_MOM) You manage information about the Introscope Manager of Manager in the SAP Solution Manager transaction SOLMAN_SETUP. ABAP Application Server (AS ABAP) As of release 4. Prerequisites:    You have performed the basic configuration of LMDB.com/irj/sdn/nw-sld. so manual post-processing in LMDB can be required. Diagnostics Agent (DIAGAGENT) There are data suppliers for diagnostics agents. see Setting Up the SLD Data Supplier for AS ABAP Based Systems in the SAP Help Portal. Always register an AS ABAP in SLD with transaction RZ70 and system information will be synchronized automatically with LMDB and SMSY. For more information about the configuration of specified products. Each architecture has its own data supplier. But for the installed applications. which is described in detail in its documentation. Microsoft IIS. so manual post-processing in LMDB is not required. and databases. which deliver all necessary information. there is a data supplier for the Unspecific Application System system type. see Maintenance of Product in the System Landscape in the SAP Community Network. e. see the SAP Community Network. Apache Tomcat Server (ATC) There is a data supplier for the Apache Tomcat server. which would not be sufficient otherwise.sap. The following sections describe the recommended system integration procedure per system type. so manual post-processing in LMDB is not required. which delivers product information.For more information. so manual post-processing in LMDB is not required. the data supplier (SMD Agent in Outside Discovery) is outside the architecture. Users and authorization for systems to be connected: o o o AS ABAP administration user AS Java administration user For all other products. product information is not always provided.0B. Introscope Enterprise Manager Server (IS_EM) You manage information about the Introscope Enterprise Manager. there is an SLD data supplier for AS ABAP.g.

IBM WebSphere Cell (WEBSPHERE) There are data suppliers.NET System (MS_. Manual post-processing in LMDB may be required for the applications which run in WebSphere.0. For more information. the configuration can be performed manually in the Visual Administrator. You create unspecific application systems for which there are no data suppliers. which deliver product information about the Microsoft Internet Information service. for IBM WebSphere Cell systems. You must specify the products of the applications which run in the Microsoft Internet Information service.702 710 SPS07 and all higher releases.NET) There are usually no data suppliers which deliver product information for . The data supplier provides no product information. Since NetWeaver Version 7. from version 7. the configuration is done in SAP NetWeaver Administrator. it is possible – under certain circumstances – the AS Java data supplier can deliver information about installed product instances. an unspecific cluster application system can have several application servers. TREX System There are data suppliers for TREX systems. 701. An unspecific stand-alone application system has only one server. The data suppliers for this system type usually also deliver the product information.1 and above. in LMDB 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 installed products only need to be configured in LMDB for older NetWeaver versions. via Outside Discovery.02. which deliver product information. LiveCache The LiveCache system information is provided by the following versions of the AS ABAP data supplier: 640 SPS23. so manual post-processing in LMDB is not required. You must maintain this information in LMDB manually. but it does not deliver product information. see Setting Up the SLD Data Supplier for Java-Based Systems in the SAP Help Portal. Unspecific Application System (UNSPECIFIC) There are data suppliers for the various variants (technology types) of unspecific application systems. manually. manually.18 Data Supplier yes yes yes .NET systems. SAP Web Dispatcher (WEBDISP) The SAP Web Dispatcher has a data supplier. . For Release 7.Java Application Server (AS Java) There is a data supplier which is usually set up during system installation. but they do not deliver product information. so assign the LiveCache product instance to the LiveCache system in the Technical System Editor. Until NetWeaver Release 7. so you must manually enter it in LMDB in the Technical System Editor. Microsoft Internet Information Service (MSIISINST) There are data suppliers for the Microsoft Internet Information Service. 700 SPS17. You must add the product information in LMDB. Current overview of known unspecific application systems: Technology Type ALLOY BCMClusterTechnology BOFC_Cluster Type Stand-alone Cluster Cluster Product SAP Alloy (IBM) SAP BCM SOFTWARE SBOP FINANCIAL . create the LiveCache manually in the Technical System Editor. Unspecific application systems can be stand-alone (UNSPAPP) or cluster (UNSPECIFIC).2. so manual postprocessing in LMDB is not required. In all other cases.

via the SMD agent. The required detailed information is provided by the Outside Discovery. or by initial data migration from SMSY. For more information. As of release 7. Avoid manual entries in LMDB. you can manually create. The technical systems are based on the host. in case the data suppliers do not deliver it automatically Maintenance of the Diagnostics Relevance indicator for product instances Maintenance of Custom Attributes . because they can become inconsistent or obsolete.1 SP2. SAP Solution Manager contains a host editor.1 yes yes yes yes yes Host (Computer System) A host is not really a technical system – technical systems are installed on hosts. Note: LMDB content should be created and updated automatically by synchronization with SLD. Outside Discovery. 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).CONSOLIDATION BPCMSCluster BPCNWCluster ClickSoftwareCluster ConvergentChargingCluster CSLCluster DataServicesCluster EPOSCluster ESOCluster InfoInterchangeServer LiveEnterprise MigrationCluster OTHERS (can only be used for technical systems entered manually. and delete information about technical systems in LMDB. see Host Editor section. change. and data from SLD which is changed in LMDB will no longer be updated by synchronization of LMDB with SLD. dedicated for project based integrations of customer products to SAP Solution Manager) PCMCluster PMCluster RTOMCluster SAPPOS_Cluster SBOPEnterprise31 Cluster Cluster Cluster Cluster Cluster Cluster Cluster Cluster Stand-alone Cluster Cluster Cluster/Standalone SBOP BPC MS SBOP BPC NW SAP WS&O BY CLICKSOFTWARE SAP Convergent Charging TPT Commodity SL SBOP Data Services SAP ENTERPRISE POS SAP SOURCING/CLM SAP INFO INTERCHANGE SBOP EVENT INSIGHT SMSY Migration Standard customer specific product yes yes yes yes yes yes yes yes yes yes yes no Cluster Cluster Cluster Cluster Cluster SBOP PCM SAP PROMOTION SAP RTOM SAP POS SBOP Enterprise 3.19 - . but because the host is an underlying system. Technical System Editor With the Technical System Editor. as far as possible. accurate information about it is important.

If you connect the system with a data supplier later. Note: Manually-created technical systems are not automatically updated. manually. choose Managed Systems Configuration  Technical Systems  System Operations  Create System. 2. choose Managed Systems Configuration  Technical Systems. . Then choose System Operations  Display System. If you want to copy the SLD status to LMDB. all missing information is written from SLD to LMDB.Display System Description with Technical System Editor The Technical System Editor can display detailed information about the technical systems in your system landscape. Choose Next.20 - . 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). and change the role. Prerequisites:    You have performed the basic configuration of LMDB. you need the SAP_SYSTEM_REPOSITORY_ALL role. for example system name. change. proceed as follows: 1. and host name. so they can become obsolete. Copy the role into your namespace. You have initially synchronized SLD and LMDB. Select a system type from the input help and choose Continue. Define further data. with the Technical System Editor. If the information differs between SLD and LMDB. 3. or delete a technical system in LMDB. depending on the system type selected. In the following. installation number. choose SAP Solution Manager Administration  Landscape  Define New Query and select a system. Prerequisites:    You have performed the basic configuration of LMDB. But you can use alternative 2 as well and carry out the same operations. Call In the SAP Solution Manager Configuration (transaction SOLMAN_SETUP). Create System Description with Technical System Editor If there is no data supplier for a system. the LMDB version is retained. Alternative 2: In SAP Solution Manager – Work Center (transaction SOLMAN_WORKCENTER). only the access via Alternative 1 is described. You have initially synchronized SLD and LMDB. you can create a system in the LMDB. Users and authorization in SAP Solution Manager: To create. proceed as described under Restoring a Damaged Technical System Description in the Troubleshooting section. You can restrict the authorization with LMDB authorization objects. To create a completely new technical system description. Select a technical system and then choose System Operations  Display System.

Prerequisites: see Create System Description with the Technical System Editor. in which you can enter detailed information about your system. 3. and if it has a system data supplier which is configured in SLD. But dependent product systems are not deleted. you must make them manually. manual changes can be required because. Choose Delete Technical System. see Maintenance of Product in the System Landscape in the SAP Community Network. If you delete a technical system. they are not overwritten by SLD content synchronization. the Landscape Management Database (LMDB) or the SAP Solution Manager System Landscape (SMSY). Delete the system in LMDB.4. you must ensure that it is deleted consistently in the complete SLD and LMDB system landscape. If the system is known in an SLD. To delete a technical system description from the complete system landscape. information delivered by older data suppliers is no longer sufficient. If such systems are really to be deleted. its data is not updated with SLD information because the rank of LMDB is higher. so you must also change or delete . Prerequisites: see Create System Description with the Technical System Editor. The technical system description that you deleted in LMDB is automatically deleted in SMSY as well. because it is then protected against propagation of the deletion in SLD. 2. Start SAP Solution Manager: Configuration (transaction SOLMAN_SETUP:) and choose Managed Systems Configuration  Technical Systems  System Operations  Maintain System. Make the changes. for example. For some system types. Call In the SAP Solution Manager Configuration (transaction SOLMAN_SETUP). because automatic synchronization could restore deleted data. The sequence of deletion is important. and choose Managed Systems Configuration  Technical Systems  System Operations  Maintain System. Delete Technical System Description with Technical System Editor The Technical System Editor can delete technical system descriptions in LMDB. proceed as follows: 1. because LMDB has higher rank. An extended system ID (ExtSID) is proposed. delete it there first. 5. if changes of manually created data are required. Click Display Navigation Tree to see individual categories. 3. Another guided activity opens. Explicit deletion in LMDB is only necessary if you changed the system manually. 4. See Register Technical System Automatically. the data supplier must be deactivated first. Change System Description with Technical System Editor When you create technical system descriptions in LMDB. Deleting the description of a technical system in LMDB is only makes sense for manually created descriptions in LMDB. Accept it and choose Save. or if you migrated the description from SMSY into LMDB. proceed in the following sequence: 1. manually. The deleted technical system is automatically re-registered if it is in a landscape. If you complete or change such entries in LMDB. A technical system is known in at least one System Landscape Directory (SLD). Therefore. For detailed information on how to define certain products manually. deactivate the data supplier. If the system is known in an SLD. Save your entries. 2. To change technical system description.21 - .

one SLD with data supplier. The Resync from SLD function does not work. which is described in the next section. the RLMDB_SYNC_TECHNICAL_SYSTEM report is the only way to resynchronize data from SLD. For all other system types it is only necessary if it is part of a product system. LMDB data can be inconsistent. To repair this. read Restore a Deleted Technical System in the Troubleshooting section. Click the Resync from SLD button. If you deleted system information in LMDB manually. do remain (they are deleted during the resynchronization process but are immediately recovered). Only data from automatic SLD data suppliers is synchronized. see the next section (Resynchronzation Report). Resynchronization by Resync from SLD Function As of SP03. for example because the same system is described differently in two SLDs attached to your LMDB. this function does not work for technical systems that you deleted manually. if you want to.the product systems in SMSY manually. If you need to delete even the assignments. Note: If you delete a technical system description coming from SLD in LMDB. use this report. a restore of technical system descriptions from SLD can be required:    The system was changed manually with the Technical System Editor. In this case. To restore SLD data. Note For SP03. see Deleting System Descriptions from SLD in the SAP Community Network. Simply deleting the system in LMDB and triggering the SLD data supplier again does not solve the problem. remove the incorrect information from the SLD first. If the data in the SLDs differs (e. Resynchronization from SLD (with or Without Deletion of Assignments) For the following reasons. you have to use this report to restore the information. If there is more than one SLD connected. for example product assignments. Incorrect system information was migrated from SMSY. Resynchronization by Report In SP02. .22 - . you have to select one. it is only deleted until the next incremental synchronization. and a skeleton of the technical system would appear in LMDB rather than the whole system description. you can restore the complete technical system description from SLD directly in the Technical System Editor. Note If data is inconsistent in SLD. because only that information is synchronized that is new from the SLD‟s point of view. For technical systems of type ABAP. Inconsistent system descriptions were created in LMDB by two different SLDs. and one with manual data import). The result can be an incomplete system description. This would only update the information that has changed since the last system registration. It also enables you to delete all assignments. Delete the description of a technical system in SLD For more information about deleting system descriptions from SLD. You can review the changes made by the resynchronization before you click the Save button to persist them. this is obligatory. All assignments. use the resynchronization report. Data created manually in LMDB and assignments are not deleted by this function.g.

LMDB adds zeros.23 - . the ExtSID is defined automatically by LMDB. By default. Start transaction SE38 and run the report RLMDB_SYNC_TECHNICAL_SYSTEM. as of version SP02. see Resynchronization from SLD. Enter the following parameters:       Source SLD: Select the SLD with the correct system description. as described before. SAP systems have a predefined. Many SAP Solution Manager Applications use the ExtSID to identify a technical system. If there are less than three characters. Additionally. 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. 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 possible. LMDB only accepts uppercase letters and numbers. three-digit system ID (SID) from which the ExtSID is derived. 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. the automatic generation of ExtSIDs cannot ensure the ExtSIDs of AS ABAP and AS Java are the identical. The preferred way to change an ExtSID is to do it manually. If you do not choose this indicator. customers can also use a BAdI implementation (LMDB_EXTSID_GENERATOR) to change the proposed value of the extended system IDs. 2. in most cases. Note In case of a dual stack. this would be active. In this case. depending on the number of CIM instances. The ExtSID must consist of three to eight characters. the system carries out a resynchronization without deleting assignments and manually created information. For more information. 3. ExtSID C1D00001 can be derived). In case of duplicate SIDs for a given system type. a suffix with 5 digits is appended to the ExtSID. Target Namespace: Select the LMDB target namespace. Technical System  Software  Installed Flag . the running the report would have the same effect as the Resync from SLD function in the Technical System Editor. An ExtSID of more than eight characters is truncated. for example product assignments. SID and ExtSID are kept identical. Caution: Selecting this option deletes all data that you entered manually. For an ExtSID.Proceed as follows: 1. (Example: From SID C1D. Run the report The synchronization can take a few minutes. LMDB deletes special characters and Unicode characters. 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.

using one of the alternative hostnames. Software is sometimes assigned. But Diagnostics is still supposed to refer to the original version of the underlying product. For example the FQDN is important for some configuration tasks and the URL Framework. you can use the Host Editor. which then will be transferred to LMDB. Alternative FQDNs and IP addresses are listed under Alternative Hostnames. After saving a new definition. Those alternatives are related to the multiple possible network configurations on the host. For host information coming from Outside Discovery: Change the FQDN in the SMD Agent. For the single value used in the Host Overview. Background: In some cases. the flag is used to define content that should be used for Diagnostics instead of the content that is really installed. Select a host and choose Host Operations  Maintain Host. technical systems. The flag is not set if the software is Diagnostics-relevant but not installed. To do so. This implies that the FQDN is no longer overwritten by changes reported via SLD or Outside Discovery. For more information. Manufacturer.Set the Installed flag if the selected entity is installed physically on the system. To do so. check the Details in the System Overview of the Technical System Editor. which writes directly to LMDB. the new attribute will be available to select in the Technical System Editor of LMDB. or Release. Standard attributes are Location. and hosts. For more information. in more detail. To maintain the definitions. It defines which of the assigned entities will be used by the Diagnostics application. access transaction SMSY and select any system under Select Object. . see SAP note 1626853. but the corresponding executables are not physically installed. Access the Technical System Editor and choose Resync from SLD. Then choose Utilities  Attribute Definition. LMDB receives the FQDN and IP address from the data supplier with the highest rank. see Cannot Create RFC Connection Because the Host FQDN Is Wrong in the Troubleshooting section. in this case. Monitoring System. Maintenance of FQDN and IP address In the Host Overview the FQDN (fully qualified domain name) and the corresponding IP address is shown. from the SMD agent of Outside Discovery. the flag is not set. Technical System  Software  Diagnostics-Relevant Flag You can set the Diagnostics Relevant flag for Product Versions in combination with product instances. Host Editor Host descriptions come from SLD and. go to SAP Solution Manager Administration  Landscape and select Hosts. 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. Maintenance of Custom Attributes In LMDB you can maintain Custom Attributes for servers. The information is transported to and used by SMSY (for example to filter systems according to their location).24 - . in this case you have two options:    Change the FQDN manually. using the correct alternative name. Select the SLD that contains the correct FQDN and IP address. This may not be the preferable value. the installation of add-ons can update the version of software components of a product. To find out which data supplier did provide the host information.

Each system takes a few minutes. 1. proceed as follows: 1. to display the migration log containing success or error information. Select the required systems and choose Migrate Selected Rows. can be maintained manually in the Technical System Editor of LMDB. you can choose Display Log.25 - . so that the information is updated regularly. System descriptions that you cannot migrate. if absolutely necessary. The migration runs in a background job. system-oriented migration is supported:  System-Oriented Migration for AS ABAP Complete migration is supported for ABAP application servers and all system entities. instances. You can check your system descriptions in SMSY with the Landscape Verification tool. Aspect-oriented migration: for transfer of a single kind of information for all systems in SMSY to LMDB. Migrate SMSY Data to LMDB (One-Time Activity) SMSY can contain manually created system description for which no data suppliers are available. Not all data from SMSY needs to be required. If possible. you do not require this type of migration. you can migrate data once from SMSY to LMDB.0 as Add-on. depending on its type and size. do not create landscape data manually. or manually added data. 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. System-Oriented (Complete) Migration System-oriented migration transfers system description from LMDB to SMSY for which no data suppliers are available (For more information.1 it is automatically installed. It is the recommended way to migrate manually maintained data. only migrate or create system descriptions that are really necessary. for example because of a firewall. For the following system types. To avoid superfluous effort. For more information. Note  Only migrate systems for which you cannot configure data suppliers. software components. Only system description that is sufficient to create an LMDB entry is migrated. If you do not have such systems. 2. clients. and other attributes. . 3. see Register Technical System Automatically).Deletion of a Host The deletion of hosts in the Host Editor of LMDB is supported as of SP03. see Landscape Verification in the SAP Community Network. Switch to Edit mode and choose Migrate from SMSY to LMDB. To reduce the manual effort for initial transfer of this data to LMDB. With SAP Solution Manager 7. for example. Consider a SMSY clean-up before migration. Collect it automatically from data suppliers instead. When the background job has finished.    To migrate technical system descriptions from SMSY to LMDB. The tool is available in SAP Solution Manager 7. Also avoid migration of manually created data. Start SAP Solution Manager: Configuration (transaction SOLMAN_SETUP) and choose System Preparation  Prepare Landscape  Set Up LMDB.

You have maintained the Instance Number and Server. for example the MDM_SERVER software component in the MDM Server server role. Software components must be maintained in the system. You have maintained the Manufacturer of the assigned database. and Syndication Servers. In this case. The extended system IDs of technical and product systems must be the same. the following prerequisites apply: o o o o o o o o The extended system IDs (ExtSIDs) of technical and product systems must be identical. You have assigned one or more product instances of a product system to the technical system. and a product system with product version SAP MDM 5.26 - . You have maintained the Server of the assigned database. For MDM . software component and other attributes are supported for the type Master Data Management server. A database must be assigned to the system. must be in the technical system. You have maintained the Manufacturer of the assigned database. Users and authorization for SAP Solution Manager: SAP_SYSTEM_REPOSITORY_ALL role 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 Manufacturer of the assigned database must be maintained.Layout Server. Prerequisites: o o o o o You have assigned a database to the system in SMSY. Import Server. The Server of the assigned database must be maintained. Software Component and Other Attributes are supported for the type Unspecific Cluster system. Prerequisite: You have assigned the correct product instances of a product system to the technical system. You have initially synchronized SLD and LMDB. System-Oriented Migration of Master Data Management Server (MDM) Migration of the entities instance. You have maintained the Instance according to the SMSY naming convention.Prerequisites: o o o o You have performed the basic configuration of LMDB. The technical system has an instance in the MDM Server server role. . Example: You have a technical system of type MDM with a technical instance with MDM Server server roll. Database.5. database. The software components for the technical instances.  System-Oriented Migration of Unspecific Cluster System (UNSPECIFIC) Migration of the entities Instance. You have maintained the Server of the assigned database. the technical system must be assigned to the product instance Master Data Server.

for example manually maintained information under Other Attributes or relevant product instances of technical systems. choose Solution Manager: Configuration (transaction SOLMAN_SETUP)  Basic Configuration  Configure Manually  Migrate Installed Product Instances Data. . a system must have values under Other Attributes.27 - . Create a technical scenario: In the SAP Solution Manager: Configuration (transaction SOLMAN_SETUP). System must exist in both SMSY and LMDB. technically. choose Technical Scenario Wizards under Related Links  Configuration. Usually all system types from SMSY are supported. see SAP Note 1608341. Prerequisites to use technical scenarios in SAP Solution Manager:    You have performed the basic configuration of LMDB. with Connection Monitoring. For SP01 and SP02. You have initially synchronized SLD and LMDB. You can migrate the following aspects of technical systems:  Installed Product Instances: As of SP03. To create or change a technical scenario in LMDB. The specific aspect must be maintained in SMSY. Choose Create and follow the procedure. The specific aspect must not be maintained in LMDB yet. Change a technical scenario: In the SAP Solution Manager Configuration (transaction SOLMAN_SETUP). for example. In Technical Scenario Maintenance window. Diagnostic-relevant product instances: As of SP03. see SAP Note 1607771.  Prerequisites:     You have maintained the product systems properly.Aspect-Oriented Migration Aspect-oriented migration transfers one single kind of information for all systems in SMSY to LMDB. the system checks this based on the extended system ID (ExtSID). Information about technical scenarios is saved in the LMDB. select a system and choose Maintain. Technical Scenario A technical scenario is a group of technical systems which work together. It is the recommended way to migrate manually maintained data from SMSY to LMDB. a system must not have values under Custom Attributes and in the Landscape Pattern field in LMDB. choose Solution Manager: Configuration (transaction SOLMAN_SETUP)  Basic Configuration  Configure Automatically  Migrate Diag relevant flags. During migration. for example. For SP01 and SP02. choose Technical Scenario Wizards under Related Links  Configuration. For example. Special LMDB authorization objects can restrict authorization. you can monitor the availability and performance of the connections of all technical systems in a technical scenario.  Other Attributes (Custom Attributes) can be migrated as of SP03 with transaction LMDB_MIG_CUST_ATTR. you need the SAP_SYSTEM_REPOSITORY_ALL role in SAP Solution Manager. Copy the role to your namespace and change it.

1. start SAP Solution Manager: Configuration (transaction SOLMAN_SETUP). The RFC connection is configured in step 3. If required. In this case. Start SAP Solution Manager: Configuration (transaction SOLMAN_SETUP). choose Managed System Configuration  Technical Scenarios  Scenario Operations  Maintain Scenario. the dual stack is not recognized if the Java stack is registered in SLD after the ABAP stack. 3. . You can use these technical scenarios to configure the managed system for both stacks at the same time. Configuration of RFC Connections During Managed System Configuration 1. Change a DBL_STACK technical scenario To edit an existing technical system of type DBL_STACK. register the ABAP stack in SLD again or wait for 24 hours. Start SAP Solution Manager: Configuration (transaction SOLMAN_SETUP) and choose Managed System Configuration  Technical Systems tab. and the system creates a DBL_STACK technical scenario. Users and authorization in SAP Solution Manager: SAP_SM_BASIC_SETTINGS role. 2. RFC Connections As of SAP Solution Manager 7. you can also create a DBL_STACK technical scenario manually: Start SAP Solution Manager: Configuration (transaction SOLMAN_SETUP). which is created at the start of the SAP Solution Manager. Create a DBL_STACK technical scenario It can happen that a technical scenario is not created automatically for a dual stack system. choose Managed System Configuration  Technical Scenarios and filter for technical scenarios of type DBL_STACK (Dual Stack). therefore. To view technical scenarios for dual stacks. The information that it is a dual stack system comes from the ABAP system. You have initially synchronized SLD and LMDB. if the technical systems have not been registered in SLD for some time. Follow the guided activity. technical systems are saved in LMDB. there should be a DBL_STACK technical scenario for this system. Then. Dual stacks are usually identified automatically. assigned to the user SOLMAN_ADMIN. for example. This role is. Prerequisites:    You have performed the basic configuration of LMDB.Dual Stack Technical Scenario in Managed System Configuration The simplest case of a technical scenario is a dual stack (AS ABAP and AS JAVA). and RFC connections between SAP Solution Manager and managed systems can be created or edited in LMDB. choose Managed System Configuration  Technical Scenarios  Scenario Operations  Create Scenario and follow the procedure. for example.28 - . or if the technical systems were registered in SLD in the wrong sequence. Select a system and choose Configure System.

choose Asynchronous Generation.  Instance Browser On this tab you can search for CIM instances. as well as the selected CIM instance. synchronization can take some time and lead to a time-out error. 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. It is strongly recommended that it only used by very experienced users. as described in the Search for CIM Instances tab. namespace configuration. If you select an entry. You can delete CIM instances or their corresponding technical systems.  LMDB Administration provides the following options:      Displaying a status overview about LMDB considering performance and configuration aspects (available as of SP03). Displaying CIM class and instance information Changing CIM instance attributes Deleting CIM instances. From the search results. In this case. You can add or delete search rows and save search criteria for future searches. You can display further details of a selected row. the bottom table shows its CIM instances with the times of the earliest and latest changes. and domain settings. You can also display statistical information about all CIM classes. content synchronization status. 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. you can display details and change attributes. you can change attributes in the Instance Attributes tab of the Details dialog box. all CIM instances of the technical systems are deleted. To update the information. choose Synchronize. When you delete a technical system. . Searching for information in LMDB with various search criteria.  Change Log Browser On this tab you can search for change log entries of CIM instances.29 - . In edit mode. If there are a lot of instances. Start transaction LMDB_ADM.LMDB Administration Note LMDB Administration is an expert tool. You cannot make any changes. in the Details dialog box.

Go to CIM Instances (in NetWeaver 7. . Log on to the source SLD. Save the change. see Resynchronization from SLD (with or Without Deletion of Assignments). Restore a Deleted Technical System If a technical system has been deleted from LMDB. 3. 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.Troubleshooting Damaged Technical System Description in LMDB Example: Additional clients have been created manually in SLD to configure SAP Process Integration. For more information. 5.30 - . Choose the CIM class for your system type. 2. System Type ABAP ATC BOBJ DBSYSTEM DIAGNAGENT Name/Caption Application Server ABAP Apache Tomcat Server Business Objects Cluster Database System Diagnostics Agent Introscope Standalone Enterprise IS_EM Manager Introscope Enterprise Manager IS_MOM Cluster JAVA Application Server Java LIVE_CACHE liveCache MDM Master Data Management Server MS_. Run a re-synchronization from SLD. 4. 2.0: Content Maintenance). Make a pseudo-change to your system. for example by SID or host name.NET System Microsoft Internet Information MSIISINST Services THIRDPARTY Generic Application System TREX TREX System UNSPAPP Unspecific Stand-alone System CIM Class SAP_BCSystem SAP_ATCServer SAP_BOCluster SAP_DatabaseSystem SAP_DiagnosticsAgentInstance SAP_ISEMServer SAP_ISMOMServer SAP_J2EEEngineCluster SAP_LiveCache SAP_MDMDataServer SAP_DotNetSystemCluster SAP_MSIISInstance SAP_ApplicationSystem SAP_TrexSystem SAP_UnspecificStandaloneApplicati onSystem SAP_UnspecificClusterSystem SAP_BCWebDispatcher SAP_IBMWSCell UNSPECIFIC Unspecific Cluster System WEBDISP SAP Web Dispatcher WEBSPHERE IBM WebSphere Cell 4. Add an X to the description. Reverse the change. To load all data of a deleted system into LMDB again.NET . Filter to find your system. perform the following steps: 1. 3. its ExtSID and any key information is no longer known in LMDB. This results in an overlap: Different system descriptions in different source SLDs and duplicate entries for the system clients are created in LMDB. for example: 1. This data has been imported via content synchronization and mixed up with the correct description in the SAP Solution Manager SLD. Save again.

and select the SLD containing the correct FQDN.  Solution for SP02: For host information from Outside Discovery: Change the FQDN in the SMD Agent. To find out which data supplier did provide the host information. check the Details in the System Overview of the Technical System Editor. A predecessor job is processing a large number of pending changes and has not finished yet. using one of the alternative hostnames. 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. For more information.31 - . there are two possible reasons:   There are no pending changes to be synchronized. To transfer all the system information to LMDB. Outside Discovery will not overwrite the value anymore. use the Resynch from SLD button. choose Resync from SLD. following jobs are immediately set to complete in order to let the preceding job finish synchronization properly. Performance Issues During Synchronization For information on how to check the progress of synchronization. Solution: No action required. You have to pick the correct one from this list. . Only when the running job is finished. For host information coming from an SLD: see Solution for SP02. 7. The key instance and the extended SID. using the correct alternative name. using one of the alternative hostnames. In this case. For host information from SLD: Access the Technical System Editor.  Solution for SP03: For host information coming from Outside Discovery: Change the FQDN manually in the header data. the following jobs will run productively again. Wait until the changes are replicated into LMDB. Or change the FQDN manually in the System Overview. see Monitoring the Synchronization Process. see SAP Note 1626853. Note You can see all available alternative FQDNs and IP addresses under Alternative Hostnames in the Host Editor. are written to LMDB. which then will be synchronized into LMDB. but no detailed system information.6. 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.

Performance Issues Because of Exhausted Shared Memory The LMDB in SAP Solution Manager 7. with dramatic performance impact. Check whether the shared memory area is used:  In SP02: Log on to the SAP Solution Manager system with an administration user. This is quicker than individual database accesses. If the shared memory of the server is exhausted. Check the shared memory status on the Content Synchronization Status tab. You can get the number of successful read accesses from the field „Accumulated Read Locks“ in the transaction SHMM. please refer to Administration of ABAP Shared Memory Areas for LMDB in the next section. The size of all objects in shared memory is specified by the abap/shared_objects_size_MB profile parameter. For more information about shared memory-handling in the context of LMDB. 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. start transaction SE38. From SAP Solution Manager Release 7. and how much free space remains. This effects long response times. proceed as follows: . or the shared memory segment CL_LMDB_MODEL_SHM_AREA cannot be created. For more information.32 - . The area relevant for LMDB is 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. Administration of ABAP Shared Memory Areas for LMDB Shared memory objects are ABAP object instances in the shared memory of the application server. No Progress in Incremental Synchronization If the incremental synchronization between SLD and LMDB does not finish after a long time. It has a size of about 15 MB. Use of Shared Memory When LMDB processes run. LMDB processes will access the database instead of shared memory. On the Shared Objects Memory tab in SHMM. At runtime. class information is read from shared memory. there is an alarm in the Self-Monitoring area of the SAP Solution Manager Administration work center. you can see how much shared memory is currently in use. which allow that data is shared in various user sessions.  In SP03: Start transaction LMDB_ADM (LMDB Administration). the report tries to create the shared memory instance and provides a message about its current status.1 relies on ABAP shared objects in the shared memory of the application server. LMDB uses ABAP shared objects to buffer CIM class information in shared memory. The report tries to read data from the shared memory area (CL_LMDB_MODEL_SHM_AREA). and execute the RLMDB_SHM_READ_TEST report. The Shared Objects Monitor (transaction SHMM) provides an overview of the area instances in shared objects memory of the current application server. see: Shared Objects Monitor – Transaction SHMM in the SAP Help Portal. if the shared memory area for LMDB cannot be created.1 SP1. or if the shared memory segment for the LMDB cannot be created for other reasons. If there is not enough memory for the shared memory segment. the system reads class information from the database always.

or SLD is down. This means that someone has changed the name of the object server. statistics can be outdated. Repeat the change of the object server name in SLD. 3.5 Setup LMDB to check whether all pending changes are being processed completely.5 Setup LMDB. 4. that shared memory is exhausted.1 system. 2. In case the statistics are out-of-date. see Update Statistics with BRCONNECT in the SAP Help Portal. If statistics are calculated at this time. start transaction SM37. Rename the object server name to its previous name under SLD  Administration  Profile  Object Server. Delete the SLD synchronization in SOLMAN_SETUP. Outdated Oracle Database Statistics If the SAP Solution Manager system is installed with an Oracle database. enter *LDB* under Job Name and an asterisk (*) under User. Reasons can be. proceed as follows: 1. the Cost Based Optimizer (CBO) will tend to run a full table scan during all subsequent database accesses. To create a job overview. If the number of Pending Source Changes is larger than 0. If the name change of the object server was made on purpose in SLD. For more information. start transaction DB20 with parameter LMDB_P_INSTANCE and check the optimizer statistics. it is recommended to update the statistics repeatedly while the content synchronization job is running. use the Update Statistics with BRCONNECT function. The job log in SM37 must not show any more errors. 2. Check the job logs and look for the error messages. which LMDB now cannot identify correctly any longer. 5. for example because of full automatic synchronization of SLD and LMDB. Wait for about ten minutes and return to transaction SOLMAN_SETUP  System Preparation  6.33 - . If the LMDB tables are continually filled. without the CBO realizing this. most LMDB tables are empty. Check whether the synchronization is still active under transaction SOLMAN_SETUP  System Preparation  6.1. If the name change in SLD was made by mistake. 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”. the real costs for the full table scan become higher and higher. 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) . After you started the content synchronization between SLD and LMDB. you have to ensure that the Oracle database statistics are updated. After the installation or upgrade of the SAP Solution Manager 7. Pending changes from SLD are not transferred to LMDB. click Details. To do so. only carry out step 1 and 2. This will force the Cost Based Optimizer (CBO) to realize the increasing fill level of the LMDB tables. Create a new SLD synchronization in SOLMAN_SETUP. the changes are not going through and the connection between source and target is probably corrupt. and if the Date of Source Change Log ID is in the past. For best performance. If it is active. database statistics are outdated. for example.

Therefore. Unicode Characters in a Non-Unicode LMDB If system descriptions in an SLD include characters that are Unicode characters. avoid the maintenance of Unicode characters in SLD.34 - . they are replaced by a hash (#) in the LMDB description on a Non-Unicode SAP Solution Manager system. The performance improvement will become effective automatically.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. For more information. 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. . see SAP Note 1555955.

because the various product instances in a product perform various tasks. Product system (previously system): Grouping of technical systems which belong to one or more products. collect and send information from the monitored system to SAP Solution Manager. Like products. Example: SAP ERP Product version: A version or release of an SAP product. A product system SAP Solution Manager comprises one technical system ABAP and one technical system JAVA.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. 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. Example: SAP Solution Manager. Technical systems may consist of technical (sub)systems. SAP_HR . It performs business tasks. Software component: Set of software objects grouped in packages and delivered together. Product: An SAP offering in the SAP price list. A software component usually exists in several release versions. these are defined in the Product and Production Management System (PPMS).35 - . because it can be installed.0 Product instance (previously main instance): The smallest installable entity of a product. which are updated by upgrades. Example: SAP_BASIS. The purpose of Outside Discovery is to automatically discover. and a functional entity. Example: SAP ERP 6. A product instance is both a technical entity. You can import support packages separately for each software component. All products are specified in the Product and Production Management System (PPMS).

.36 - .

Sign up to vote on this title
UsefulNot useful