This action might not be possible to undo. Are you sure you want to continue?
Setting Up and Using The Landscape Management Database (LMDB)
Applicable Releases: SAP Solution Manager 7.1, SP4
Version 1.10 January 2012
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. These materials are provided “as is” 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. SAP shall not be liable for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. SAP does not warrant the accuracy or completeness of the information, text, graphics, links or other items contained within these materials. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third party web pages nor provide any warranty whatsoever relating to third party web pages. SAP NetWeaver “How-to” Guides are intended to simplify the product implementation. While specific product features and procedures typically are explained in a practical business context, it is not implied that those features and procedures are the only approach in solving a specific business problem using SAP NetWeaver. Should you wish to receive additional information, clarification or support, please refer to SAP Consulting. Any software coding and/or code lines / strings (“Code”) included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, except if such damages were caused by SAP intentionally or grossly negligent. Disclaimer Some components of this product are based on Java™. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressively prohibited, as is any decompilation of these components. Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified or altered in any way.
Document Version 1.10 Description Update of supported technical systems New document layout Updated graphics Smaller corrections and changes First official release of this guide
Type Style Example Text Description Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options. Cross-references to other documentation Example text Emphasized words or phrases in body text, graphic titles, and table titles File and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools. User entry texts. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system. Keys on the keyboard, for example, F2 or ENTER.
Icon Description Caution Important Note Recommendation or Tip Example
.............................. 6 Integration with System Landscape Directory (SLD) ........................................................................... 29 Damaged Technical System Description in LMDB ........................................................................................................................................................ 2 Variants of LMDB Integration .............................. 7 Monitoring the Synchronization Process ............................................................................................................................................................................................................................................................................ 30 Cannot create RFC Connection Because of Wrong Host FQDN ....... 17 Create System Description with Technical System Editor ..................................................... 30 Performance Issues During Synchronization ..................................................................................................................................................................................................................................................................... 13 Technical System Editor ............................................................................................. 16 Display System Description with Technical System Editor ...................................................................................................................................................................................................................................................................................................... 28 Troubleshooting .................... 29 Running Job Leads to Quick Completion of Following Jobs ............ 17 Change System Description with Technical System Editor ........ 31 Performance Issues Because of Exhausted Shared Memory ............................................................... 18 Delete Technical System Description with Technical System Editor .................................................................................................................................... 29 Restore a Deleted Technical System ..... 23 Aspect-Oriented Migration ......... 33 iv ................................................... 21 Host Editor ..................................................... 23 System-Oriented (Complete) Migration ........................................................................................................................... 3 Integration of LMDB ................. 31 No Progress in Incremental Synchronization ................................................................. 19 Special Settings and Functions of the Technical System Editor ................... 22 Migrate SMSY Data to LMDB (One-Time Activity) ............................................... 33 Glossary ....................................................................................................... 11 LMDB Entities ................................................ 18 Resynchronization from SLD (with or Without Deletion of Assignments) ............................................................................................................................................................................................................ 9 Integration with SAP Solution Manager System Landscape (SMSY) ................................................... 6 Configuring LMDB for Synchronization with SLD ..... 26 RFC Connections .......................................................Table of Contents Introduction Landscape: Management Database (LMDB) .... 1 Integration of LMDB into Landscape Data Management Topology .................................................................................... 1 Landscape Management – “The Big Picture” .................................................................................................................................... 26 LMDB Administration ................................. 32 Unicode Characters in a Non-Unicode LMDB ...... 11 Working with LMDB.......................... 10 Integration with Landscape Verification ..................................................... 11 Accessing LMDB ........................................................................................ 1 Sources Providing LMDB Content ................................................ 23 Technical Scenario ........................................................................ 11 Register Technical Systems Automatically................................................................................................ 25 Dual Stack Technical Scenario in Managed System Configuration .....
and software components. The main task of LMDB is to centrally provide information about the system landscape. LMDB uses the SAP enhancement of the Common Information Model (CIM.1 and since then is mandatory.dmtf. products.1. As of SAP Solution Manager 7. To describe them. LMDB was introduced with SAP Solution Manager 7. not in SMSY any longer. LMDB aims for a more flexible extendibility of the landscape model and for using the same landscape data model as the SLD in a unified approach. see www.1. you must configure LMDB. Typical model elements are technical systems. for more information. The System Landscape Directory (SLD) and the SAP Solution Manager System Landscape (SMSY) provide comparable functions. If you upgrade from SAP Solution Manager 7. product systems. technical system data can only be maintained in the technical system editor of LMDB.org). with different technologies. for different purposes.Introduction Landscape: Management Database (LMDB) The Landscape Management Database (LMDB) is a directory of system landscape elements. 1 .0 to 7. Integration of LMDB into Landscape Data Management Topology Landscape Management – “The Big Picture” The following graphic describes the flow of landscape data management components.
maintain. see SAP note 669669. All data from a connected SLD can be synchronized with LMDB in a 1:1 relationship. 3* Optionally. you must create information in LMDB only. like the SAP software catalog. Note that during the following SAP Solution Manager versions. Technically. the applications monitor. you can migrate technical system descriptions that were created in SMSY manually to LMDB. Technical System Editor in LMDB If there is no data supplier. the Maintenance Optimizer. They are called “Outside Discovery”. for Java systems with the Visual Administrator or NetWeaver Administrator. SLD synchronization is the preferred way. SAP Software Catalog (CR Content) Data about available products and software components is delivered in the SAP Service Marketplace. for example. For more information. The disadvantage of this 2 . the landscape description. Technical system descriptions are continuously replicated from LMDB to the Solution Manager System Landscape tool (SMSY) to keep SMSY updated. for example Application Servers ABAP send data to SLD with transaction RZ70. automatic synchronization. for third-party systems with the sldreg executable. In a full. which are implemented in the managed systems.These are the basic steps to distribute technical system information in the system landscape and in SAP Solution Manager: 1. or if it cannot be used (for example because of a firewall). Different SAP Solution Manager applications access the landscape descriptions of LMDB and SMSY. The setup can be done for ABAP systems with transaction RZ70. LMDB is the ABAP complement of Java-based SLD. or other clients to transfer information. Monitoring and Alerting. Sources That Provide LMDB Content The content of LMDB comes from the following sources. Based on the landscape descriptions. 5. 2. Outside Discovery Some data suppliers on technical systems write landscape data directly into LMDB. SLD gets landscape data from data suppliers. SLD and LMDB synchronize contents in the same way two SLD systems do. 4. and enhance technical systems. This is a one-time activity. and SAP Software Catalog (CR Content) are copied to the Landscape Management Database (LMDB). This CR content is transported to SLD and synchronized 1:1 into LMDB. Afterwards. CIM model. more and more SMSY functionalities will be merged to LMDB. you can manually register a system in the Technical System Editor of LMDB. and Root Cause Analysis. SAP CIM Model The current SAP CIM Model is delivered by the SAP Service Marketplace via SLD. You set up data suppliers that will automatically register technical systems in the System Landscape Directory (SLD). 3. It comprises SAP products as well as registered third-party products. independently of the technical data flow: System Landscape Directory (SLD) To create landscape descriptions in LMDB.
otherwise. Variants of LMDB Integration The following graphics explain the interaction of SLD. and. This is the recommended configuration. in the recommended configuration: Integration 1 (Preferred Variant) The systems in the system landscape are registered in a remote SLD (1). it can become obsolete. LMDB is then synchronized with SMSY (3). usually only once and immediately after upgrading to SAP Solution Manager 7. If the system is subsequently registered by an SLD data supplier. It copies technical system information from SMSY into LMDB. information that was entered manually before is not overwritten. 3 . if required.1. SMSY and LMDB in a system landscape. SAP Solution Manager System Landscape (SMSY) Data migration from SMSY to LMDB is an optional step in SAP Solution Manager Configuration (transaction SOLMAN_SETUP).manual method is that you also have to update manually created data manually. which is then synchronized with LMDB (2). manually created data in SMSY is migrated to LMDB (4).
and the nonproduction systems in a different remote SLD (1b).com/irj/sdn/nw-sld. Both remote SLDs can be synchronized directly with LMDB (2a. LMDB is then synchronized with SMSY (3).sap. For example. see the Planning Guide – System Landscape Directory at http://sdn. data is migrated (4). Make sure that each type of information is only transported by one connection. which are in full. one technical system must be registered on only one SLD.Integration 2 The production systems in the system landscape are registered in a remote SLD (1a). It should be the remote SLD with the newest CR content. if required. and. 4 . but only one remote SLD can provide the CR content for LMDB – you have to specify which one when you configure LMDB. automatic synchronization with LMDB. For more information. otherwise inconsistencies may arise in LMDB. Note If multiple SLDs are connected to LMDB. do not define a bridge forwarding between two SLDs. 2b).
when the LMDB is synchronized with more than one SLD system. and which then fills LMDB (2b).Integration 3 A variant is an additional local SLD in SAP Solution Manager. All other content cannot be filtered and therefore must not overlap. without remote SLD. the systems register directly with the local SLD (SLD 7. which is filled by data supplier forwarding (1b). see the SLD Planning Guide in the SAP Community Network. 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. this can only be achieved if SLD systems connected to the LMDB run in separated landscapes. 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.0) (1). Practically. Synchronization of one LMDB with more than one SLD System As in other mechanisms of data exchange. 5 . Integration 4 In another variant. For more information. the unique-path-principle for data needs to be fulfilled.
If your central SLD does not have the required status. In contrast. see SAP Note 669669.1 Supported Support Package Stack Level SP12 6 . it is recommended that you use a separate remote SLD with version 7.20 or higher Newest SAP CR Content. (The local SLD in SAP Solution Manager has version 7.5 For more information about updating CR content.0 SAP NetWeaver 7. Change notification from SLD All supported SLD versions support the polling of the information from LMDB. This way you have the latest SLD functional scope. and whether.3 Supported Support Package Stack Level not supported not supported not supported SP6.g. automatic synchronization.1 EHP1 for SAP NetWeaver 7.0 EHP2 for SAP NetWeaver 7.1 SAP NetWeaver 7. Model and CR Content The CIM model and SAP CR Content (SAP software catalog) have the following requirements: CIM model 1. an SLD satisfies the minimum requirements for LMDB: SAP NetWeaver Release (SLD) SAP NetWeaver 6. but active change notification from SLD to LMDB requires a higher version of SLD: SAP NetWeaver Release (SLD) SAP NetWeaver 7.1 or higher for synchronization with LMDB. you can use another SLD which does satisfy the minimum requirements (e.2 SAP NetWeaver 7. at least version 7. The polling interval usually is ten minutes. the immediate change notification of LMDB by SLD accelerates the synchronization of changes in the SLD – LMDB – SMSY chain.6.Integration of LMDB Integration with System Landscape Directory (SLD) SAP NetWeaver Release The following table gives an overview of the SAP NetWeaver versions for an LMDB-compatible SLD.40 SAP NetWeaver 7. using SLD bridge forwarding functionality or by full.02).0 EHP1 for SAP NetWeaver 7. patch 5 SP9 all SPs all SPs all SPs Although the minimum release requirements are lower. and since when (which support package stack). the SLD in SAP Solution Manager) and synchronize it with your central SLD.
which automatically register systems in SLD. Automatic Synchronization in the SAP Community Network. so it is better to use one SLD to supply LMDB.3 For more information. if you have changed the system information (originally coming from SLD) with the LMDB Technical System Editor in the meantime. the search for errors in several SLDs in the case of conflict can be time-consuming. LMDB queries SLD for changes every 10 minutes. The contents of LMDB depend on the sequence of the changes in the various SLD systems. The remote communication uses HTTP(S). outside SAP Solution Manager. but not by making manual changes in LMDB.2 SAP NetWeaver 7. This is done during the basic configuration of SAP Solution Manager after installation or upgrade. you must perform the basic configuration in the setup of SAP Solution Manager. this prevents changes in SLD from overwriting manual changes made in LMDB in the Technical System Editor.) Ideally. (With SLD version 7. There are two data supplier types: specific data suppliers for AS ABAP and AS Java. This is also called polling.EHP1 for SAP NetWeaver 7.0 only polling is enabled. Prerequisites: You have performed all previous system preparation steps in SOLMAN_SETUP.1 SAP NetWeaver 7. see SAP NetWeaver System Landscape Directory: Conflicts & Ranks in Full. all systems in the landscape register to one remote SLD directly. A ranking is defined between SLD and LMDB. This SLD is the central data source for LMDB. LMDB must be synchronized with several SLDs. for example. you can configure notifications to trigger processing of changes in a more timely fashion. The LMDB must always have priority. you should make changes to technical systems by updating their registration in SLD. but several SLDs may contain contradictory data. just like between two SLDs. SP7 SP5 SP3 There are data suppliers for most technical systems. If this is not possible.1. As of SLD 7. (For more information. LMDB receives the SLD changes automatically when a change occurs using polling or notifications: Once it has been configured. A conflict exists if the status of an object on recipient side (LMDB) differs from what is expected by the source system (SLD). Regular polling and notification ensure a robust synchronization. Even if the procedure is theoretically unambiguously specified. incremental synchronization between SLD and LMDB is automatic. This can happen. see SAP Note 1546079. The usual case is to configure one central SLD for your whole system landscape. and generic data suppliers for most other products in the SAP environment. Configuring LMDB for Synchronization with SLD To be able to use LMDB. SLD is running (see „Minimum System Landscape Directory (SLD) Requirements “) Users and authorizations: 7 . It automatically determines which status „wins‟ in case of conflicts. If possible.
make the following entries: a. the system checks whether LMDB has an object server name.1 and supports notifications (see „Minimum System Landscape Directory (SLD) Requirements“) 8 . 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. choose Add. b. f. you are prompted to enter a new object server name. 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. Source Namespace: Enter the CIM namespace of the source (SLD). If there is no assignment done before for the SLD namespace rank. When you start to configure LMDB. Source URL: Enter the source URL for SLD. This name. The object server names should be different in all SLDs and LMDBs. in combination with the CIM namespace. To create a new synchronization connection.0. users need administration authorization For SLD: o o In SLD from release SAP NetWeaver 7. For further naming recommendations.1. The default namespace is sld/active. In a standard installation. User: Enter the SLD user you have created for this connection d. If the source-namespace already had a rank you should not change the rank since this is the rank of the namespace in SLD. Procedure: 1. Target Namespace: If the source SLD has NetWeaver version 7. In SLD from release SAP NetWeaver 7. the higher the rank. 2. Start transaction SOLMAN_SETUP and choose System Preparation Prepare Landscape Set Up LMDB. In LMDB. e. 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. Example: http://sldserver:54300 c. -1 is displayed as rank. In the Synchronization Connections between SLD and LMDB area.For SAP Solution Manager. If not. Description: Enter a free text to describe the new SLD connection. the user needs the role SAP_SLD_CONTENT_SYNC. specifies the absolute path of the LMDB objects. see SAP Note 935245. the port is: 5<SLD system Java instance number>00. A previously selected rank number is displayed after you selected the namespace. Example: To be flexible for subsequent changes in your synchronization landscape. which is http://<host name>:<port>. So changing this rank might have impact on other content synchronizations as well. it is always appropriate to use the server name as object server name. the user at least needs the role SAP_SLD_GUEST. and you have to assign a rank to the namespace. use a rank of 1000 for the source and 2000 for the target. A window opens.
If you want to save your settings and activate them later. which are only available with SLD from NetWeaver version 7. start transaction SM30 and maintain the view V_LMDB_LOG_CONF. Synchronization with SLD starts when you activate the configuration. If the same SLD does not support notifications. SAP_LMDB_LDB_0000000001. So you can find the application logs related to LMDB. 4. Transaction SLG1 (Analyze Application Log) display logs. you are later informed that this function is not available. you can restart it. Rank of Target Namespace: Enter rank of the target (LMDB). choose Save and Activate. The name of the synchronization job for the target namespace is SAP_LMDB_LDB_<namespace ID>. 3. Monitoring the Synchronization Process To monitor synchronization. see SAP Note 1594654. like: 9 . Under Object. g.1. If the full synchronization job fails. depending. The initial step with the full. e. If you select this option and use SLD NetWeaver version 7. Example: If a rank has already been assigned to SLD. To start content synchronization immediately. Choose a number higher than the one for the source (SLD). Several log levels are supported. see Outdated Oracle Database Statistics in the Troubleshooting section. Jobs usually run under the SOLMAN_BTC system user. The log level can be set per user and sub-object in LMDB. on the number of systems in SLD. It will continue with the last object before it has been cancelled. automatic synchronization with SLD can take several hours.enter the target (LMDB) connection information. enter AI_LMDB. the system does not prompt for a target (LMDB) connection. Issues with Oracle statistics require manual activities some minutes after you started the synchronization. Within the job log you can find following information: Full Sync: Number of instances to be synced from destination LMDB_SyncDest1: 373920 From this you can extrapolate job duration: A job should write about 10 objects per seconds into the LMDB. only the target namespace active is supported. Start transaction SOLMAN_SETUP and choose System Preparation Prepare Landscape Set Up LMDB. You get a summary. confirm with Complete. for example. For more information. you can view information about the synchronization job. To increase the log details level of SLG1 logs. add 1000 to determine the LMDB rank. Select a synchronization connection and choose Advanced.g. For LMDB in SAP Solution Manager release 7. Specify whether you want to use notifications. Transaction SM37 (Simple Job Selection) displays jobs and logs. For more information about performance issues.1 (see „Minimum System Landscape Directory (SLD) Requirements “.0. you have the following options: Directly in SAP Solution Manager. and the hardware.
So changes in SLD are replicated via LMDB towards SMSY in less than 15 minutes (under normal circumstances). The Landscape Verification tool can support you with this. It is highly recommended to clean up the technical systems in SMSY before upgrading to 7. Integration with SAP Solution Manager System Landscape (SMSY) As of SAP Solution Manager 7. A check is made for new changes. all relevant technical system information must be continuously synchronized from LMDB into SMSY. 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. Users and authorizations in SAP Solution Manager: The SAP Solution Manager batch user (e. Warning and Info Transaction SM12 (Select Lock Entries) displays locked jobs. it can happen that a change in LMDB is blocked by locks held by another user.o Error (default) o No logging o Error and Warning o Error. Therefore. SOLMAN_BTC). you can only change technical systems in the LMDB Technical System Editor.g.1. check the lock entries. During content synchronization.Performance Checks for LMDB). For example. If a blocking situation exists for a longer period of time. 10 . Prerequisites: You have performed the basic configuration of LMDB in SOLMAN_SETUP (system preparation). enter LMDB*. If there are changes. is used automatically. The next scheduled sync job will continue at the same point later. they are logged in the LMDB change log. There is a migration of technical systems data from SMSY to LMDB. Usually blocking locks are released in the meantime and pending changes can be processed.1 . delete old technical systems in SMSY that are no longer needed. which was created during Setup ( SOLMAN_SETUP). The synchronization of LMDB and SMSY is completely automatic and unidirectional. SLD and LMDB have been initially synchronized. but no longer in the SAP Solution Manager System Landscape (SMSY). at least every 5 minutes. 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. Under Table name. Changes in SLD are polled at least every 10 minutes from LMDB (with notification this is significantly faster). For known issues with the full synchronization job. see SAP note 1555955 (SAP Solution Manager 7. Status changes in LMDB are replicated to SMSY in less than 5 minutes. But you still maintain product systems in SMSY and some SAP Solution Manager applications still get their landscape information from SMSY.1. all technical system data is written to SMSY.
the system writes the changes directly to SMSY. You can use transaction LMDB to directly enter the LMDB Editors like Technical System Editor and Host Editor. choose Landscape.. you can use the following transactions: SAP Solution Manager Configurations (transaction SOLMAN_SETUP) Choose Managed Systems Configuration. is maintained correctly in the SAP Solution Manager System Landscape (transaction SMSY). Automatic synchronization of changes written manually to LMDB by the Technical System Editor When you save changes made with the Technical System Editor. change. and several steps in transaction SOLMAN_SETUP) receive their system landscape information directly from LMDB. especially product system and logical component data. So there should be no delay. LMDB Technical Elements The following table gives an overview of the elements that are relevant for LMDB. Note that these transactions are not included in the standard user roles by default. Working with LMDB A lot of SAP Solution Manager applications (such as the work centers. To access LMDB Administration. particularly the product systems. start transaction LMDB_ADM. from SMSY. Other SAP Solution Manager applications get their landscape data. For more information. their data sources. SAP Solution Manager – Work Centers (transaction SOLMAN_WORKCENTER) In the Solution Manager Administration work center. see Landscape Verification in the SAP Community Network. 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. and how to edit them: 11 . Integration with Landscape Verification The Landscape Verification tool analyzes whether your system landscape. To centrally view. Diagnostics. and create LMDB data.
manual Technical System Editor Technical System Editor 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 12 No installed application product information No installed application product information Configuration from SOLMAN_SETUP Configuration from SOLMAN_SETUP .Technical Element . outside discovery SLD data supplier Manual Manual SLD data supplier (AS ABAP) SLD data supplier Outside discovery SLD data supplier SLD data supplier SLD data supplier SLD data supplier.NET System Apache Tomcat server Application Server ABAP Application Server Java Business Objects Cluster Database System Data Source Manual SLD data supplier SLD data supplier SLD data supplier SLD data supplier SLD data supplier. outside discovery Editor Technical System Editor Technical System Editor Technical System Editor Technical System Editor Technical System Editor Technical System Editor Notes No installed application product information Outside Discovery enhances the system information of SLD data suppliers. Diagnostics Agent HANA Database IBM WebSphere Application Server Introscope Enterprise Manager Cluster Introscope Standalone Enterprise Manager LiveCache Master Data Management Server Microsoft Internet Information Services SAP Web Dispatcher Sybase Unwired Platform TREX System Unspecific Cluster System SLD data supplier SLD data supplier.
For more information about the configuration of specified products. Users and authorization for systems to be connected: o AS ABAP administration user o AS Java administration user o For all other products. Prerequisites: You have performed the basic configuration of LMDB. some send it directly to LMDB. Always register an AS ABAP in SLD with transaction RZ70 and system information will be synchronized automatically with LMDB and SMSY. which would not be sufficient otherwise. This data is sent 1:1 to LMDB by synchronizing the contents from SLD. Dual stacks (AS ABAP + AS JAVA) recognized automatically Technical Scenario Manual SOLMAN_SETUP Product System Logical Component Manual Manual SMSY SMSY Register Technical Systems Automatically The preferred way of creating system landscape information in LMDB is automatic system registration. Outside discovery enhances the system information. For more information. there is an SLD data supplier for AS ABAP. Detailed information about individual products is beyond the scope of this setup guide. For hosts.sap. see the product IMG. and writes directly into LMDB. The data suppliers are implemented in various systems. under http://sdn.Unspecific Standalone Application System Host SLD data supplier. see Maintenance of Product in the System Landscape in the SAP Community Network. outside discovery Technical System Editor LMDB Outside Discovery enhances the system information of SLD data suppliers. ABAP Application Server (AS ABAP) As of release 4. The following sections describe the recommended system integration procedure per system type. You have initially synchronized SLD and LMDB.0B. the data supplier (SMD Agent in Outside Discovery) is outside the architecture. SLD user: SLDDSUSER or another user with SAP_SLD_DATA_SUPPLIER role. Most of them send their data to an SLD. see the SAP Community Network. and databases. Information for some other system types must be created manually. which is described in detail in its documentation. manual SLD data supplier. 13 . Each architecture has its own data supplier.com/irj/sdn/nw-sld. Microsoft IIS.
g.1 and above. so manual post-processing in LMDB is not required. 700 SPS17.For more information.02. For Release 7. For more information. 701. Until NetWeaver Release 7. Java Application Server (AS Java) There is a data supplier which is usually set up during system installation. AS ABAP. LiveCache The LiveCache system information is provided by the following versions of the AS ABAP data supplier: 640 SPS23. which is sufficient for database systems. Business Object Cluster (BOBJ) There is a data supplier for SAP BusinessObjects Business Intelligence. Introscope Manager of Manager (IS_MOM) You manage information about the Introscope Manager of Manager in the SAP Solution Manager transaction SOLMAN_SETUP. see Setting Up the SLD Data Supplier for Java-Based Systems in the SAP Help Portal. Since NetWeaver Version 7. which deliver all necessary information. Introscope Enterprise Manager Server (IS_EM) You manage information about the Introscope Enterprise Manager. Diagnostics Agent (DIAGAGENT) There are data suppliers for diagnostics agents. The data supplier provides no product 14 . e. 702. so manual post-processing in LMDB is not required. But for the installed applications. which delivers product information. so manual post-processing in LMDB can be required. it is possible – under certain circumstances – the AS Java data supplier can deliver information about installed product instances. product information is not always provided. the configuration can be performed manually in the Visual Administrator. the configuration is done in SAP NetWeaver Administrator. The Outside Discovery delivers software component information. see Setting Up the SLD Data Supplier for AS ABAP Based Systems in the SAP Help Portal.0. in the SAP Solution Manager transaction SOLMAN_SETUP. which delivers product information. The SMD agent Outside Discovery delivers all the information directly to LMDB (the information is not available in SLD). Apache Tomcat Server (ATC) There is a data supplier for the Apache Tomcat server. so manual post-processing in LMDB is not required. create the LiveCache manually in the Technical System Editor. so manual post-processing in LMDB is not required. In all other cases. 710 SPS07 and all higher releases. Database System (DBSYSTEM) Database system information is delivered by various data suppliers. so installed products only need to be configured in LMDB for older NetWeaver versions.
NET System (MS_. Unspecific Application System (UNSPECIFIC) There are data suppliers for the various variants (technology types) of unspecific application systems.NET) There are usually no data suppliers which deliver product information for .information.2. but they do not deliver product information. so manual postprocessing in LMDB is not required. which deliver product information about the Microsoft Internet Information service. An unspecific stand-alone application system has only one server.NET systems. SAP Web Dispatcher (WEBDISP) The SAP Web Dispatcher has a data supplier. You must specify the products of the applications which run in the Microsoft Internet Information service. but it does not deliver product information. so you must manually enter it in LMDB in the Technical System Editor. Current overview of known unspecific application systems: Technology Type ALLOY BCMClusterTechnology BOFC_Cluster BPCMSCluster Type Stand-alone Cluster Cluster Cluster Product SAP Alloy (IBM) SAP BCM SOFTWARE SBOP FINANCIAL CONSOLIDATION SBOP BPC MS 15 Data Supplier yes yes yes yes . via Outside Discovery. Microsoft Internet Information Service (MSIISINST) There are data suppliers for the Microsoft Internet Information Service. You must add the product information in LMDB. TREX System There are data suppliers for TREX systems. You create unspecific application systems for which there are no data suppliers. IBM WebSphere Cell (WEBSPHERE) There are data suppliers. You must maintain this information in LMDB manually. The data suppliers for this system type usually also deliver the product information. from version 7. . so manual post-processing in LMDB is not required. manually. in LMDB in the Technical System Editor. for IBM WebSphere Cell systems. an unspecific cluster application system can have several application servers. manually. Unspecific application systems can be stand-alone (UNSPAPP) or cluster (UNSPECIFIC). Master Data Management Server (MDM) There are data suppliers that deliver product information for the Master Data Management server. which deliver product information. Manual post-processing in LMDB may be required for the applications which run in WebSphere. so assign the LiveCache product instance to the LiveCache system in the Technical System Editor.
accurate information about it is important.1 yes yes yes yes yes Host (Computer System) A host is not really a technical system – technical systems are installed on hosts. Avoid manual entries in LMDB. see Host Editor section. because they can become inconsistent or obsolete. For more information. you can manually create. The required detailed information is provided by the Outside Discovery. Technical System Editor With the Technical System Editor. and data from SLD which is changed in LMDB will no longer be updated by synchronization of LMDB with SLD.1 SP2. 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 Stand-alone Cluster Cluster Cluster/Standalon e 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 no Cluster Cluster Cluster Cluster Cluster SBOP PCM SAP PROMOTION SAP RTOM SAP POS SBOP Enterprise 3. via the SMD agent. As of release 7.BPCNWCluster ClickSoftwareCluster ConvergentChargingClust er CSLCluster DataServicesCluster EPOSCluster ESOCluster InfoInterchangeServer LiveEnterprise MigrationCluster Others (can only be used for technical systems entered manually. as far as possible. The technical systems are based on the host. but because the host is an underlying system. 16 . SAP Solution Manager contains a host editor. Note LMDB content should be created and updated automatically by synchronization with SLD. Outside Discovery. and delete information about technical systems in LMDB. change. or by initial data migration from SMSY.
But you can use alternative 2 as well and carry out the same operations. 17 . Then choose System Operations Display System. Alternative 2: In SAP Solution Manager – Work Center (transaction SOLMAN_WORKCENTER). Prerequisites: You have performed the basic configuration of LMDB. If the information differs between SLD and LMDB. Select a technical system and then choose System Operations Display System. so it can become outdated. all missing information is written from SLD to LMDB. In the following. only the access via Alternative 1 is described. with the Technical System Editor.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). proceed as described under Restoring a Damaged Technical System Description in the Troubleshooting section. 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). in case the data suppliers do not deliver it automatically Maintenance of the Diagnostics Relevance indicator for product instances Maintenance of Custom Attributes Display System Description with Technical System Editor The Technical System Editor can display detailed information about the technical systems in your system landscape. If you want to copy the SLD status to LMDB. manually. If you connect the system with a data supplier later. choose Managed Systems Configuration Technical Systems. You have initially synchronized SLD and LMDB. Note Manually-created technical system information is not updated automatically. you can create a system in the LMDB. choose SAP Solution Manager Administration Landscape Define New Query and select a system. Prerequisites: You have performed the basic configuration of LMDB. the LMDB version is retained. Create System Description with Technical System Editor If there is no data supplier for a system.
and host name. For some system types. A technical system is known in at least one System Landscape Directory (SLD). manually. Define further data. For more information. See Register Technical System Automatically. 5. In the SAP Solution Manager Configuration (transaction SOLMAN_SETUP). Prerequisites: see Create System Description with the Technical System Editor. To create a completely new technical system description. 2. for example. If you complete or change such entries in LMDB. Select a system type from the input help and choose Continue. Users and authorization in SAP Solution Manager: To create. you need the SAP_SYSTEM_REPOSITORY_ALL role. its data is not updated with SLD information because the rank of LMDB is higher. Click Display Navigation Tree to see individual categories. you must make them manually. manual changes can be required because. 3. Start SAP Solution Manager: Configuration (transaction SOLMAN_SETUP:) and choose Managed Systems Configuration Technical Systems System Operations Maintain System. choose Managed Systems Configuration Technical Systems System Operations Create System. and change the role. change. Save your entries. Another guided activity opens. if changes of manually created data are required. 2. 4. see Maintenance of Product in the System Landscape in the SAP Community Network. Copy the role into your namespace. for example system name. You can restrict the authorization with LMDB authorization objects. Therefore. Accept it and choose Save. To change technical system description. An extended system ID (ExtSID) is proposed. proceed as follows: 1. proceed as follows: 1. they are not overwritten by SLD content synchronization. because LMDB has a higher rank. Choose Next. or delete a technical system in LMDB. the Landscape Management Database (LMDB) or the SAP Solution Manager System Landscape (SMSY). in which you can enter detailed information about your system. 18 . installation number. Make the changes. 3. Change System Description with Technical System Editor When you create technical system descriptions in LMDB. depending on the system type selected. information delivered by older data suppliers is no longer sufficient. Delete Technical System Description with Technical System Editor The Technical System Editor can delete technical system descriptions in LMDB.
If the data in the SLDs differs (e. 4. Explicit deletion in LMDB is only necessary if you changed the system manually. If such systems are really to be deleted. deactivate the data supplier. Choose Delete Technical System. proceed in the following sequence: 1. For technical systems of type ABAP. The deleted technical system is automatically reregistered if it is in a landscape. Call In the SAP Solution Manager Configuration (transaction SOLMAN_SETUP). because it is then protected against propagation of the deletion in SLD. The technical system description that you deleted in LMDB is automatically deleted in SMSY as well. and if it has a system data supplier which is configured in SLD. 2. it is only deleted until the next incremental synchronization. and one with manual data import). To repair this. But dependent product systems are not deleted or adjusted – you must adjust the product system information in SMSY manually.g. Delete the system in LMDB. see Deleting System Descriptions from SLD in the SAP Community Network. For all other system types it is only necessary if it is part of a product system. If the system is known in an SLD. The result can be an incomplete system description. or if you migrated the description from SMSY into LMDB. one SLD with data supplier. Inconsistent system descriptions were created in LMDB by two different SLDs. the data supplier must be deactivated first. Incorrect system information was migrated from SMSY. delete it there first. If you delete a technical system. you must ensure that it is deleted consistently in the complete SLD and LMDB system landscape. because automatic synchronization could restore deleted data.Deleting the description of a technical system in LMDB is only makes sense for manually created descriptions in LMDB. If the system is known in an SLD. Resynchronization from SLD (with or Without Deletion of Assignments) For the following reasons. and choose Managed Systems Configuration Technical Systems System Operations Maintain System. LMDB data can be inconsistent. The sequence of deletion is important. To delete a technical system description from the complete system landscape. Note If you delete a technical system description coming from SLD in LMDB. this is obligatory. a restore of technical system descriptions from SLD can be required: The system was changed manually with the Technical System Editor. 3. Delete the description of a technical system in SLD For more information about deleting system descriptions from SLD. 19 . read Restore a Deleted Technical System in the Troubleshooting section. Prerequisites: see Create System Description with the Technical System Editor. because only that information is synchronized that is new from the SLD‟s point of view.
Target Namespace: Select the LMDB target namespace. this would be active. All assignments. You can review the changes made by the resynchronization before you click the Save button to persist them. in most cases. Resynchronization by Resync from SLD Function As of SP03. If there is more than one SLD connected. If you deleted system information in LMDB manually. The Resync from SLD function does not work. In this case. for example product assignments. the system carries out a resynchronization without deleting assignments and manually created information. this function does not work for technical systems that you deleted manually. do remain (they are deleted during the resynchronization process but are immediately recovered). If you need to delete even the assignments. Resynchronization by Report In contrast to the Resync from SLD function. Click the Resync from SLD button. use the resynchronization by report described below. This would only update the information that has changed since the last system registration. For more information. you can restore the complete technical system description from SLD directly in the Technical System Editor. see Resynchronization from SLD. which is described in the next section. see the next section (Resynchronzation Report). Data created manually in LMDB and assignments are not deleted by this function. 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. Proceed as follows: 1. remove the incorrect information from the SLD first. you have to use this report to restore the information. Only data from automatic SLD data suppliers is synchronized. such as product assignments. If you do not choose this indicator. use the resynchronization report. In this case. 2. and all manually created data for a technical system. this report also enables you to delete all assignments. you have to select one. Note If data is inconsistent in SLD.Simply deleting the system in LMDB and waiting for the SLD to send the data again does not solve the problem. the running the report would have the same effect as the Resync from SLD function in the Technical System Editor. If you (re-)created the system manually in LMDB. Start transaction SE38 and run the report RLMDB_SYNC_TECHNICAL_SYSTEM. and a skeleton of the technical system would appear in LMDB rather than the whole system description. Caution 20 . for example because the same system is described differently in two SLDs attached to your LMDB. Enter the following parameters: Source SLD: Select the SLD with the correct system description. Note For SP03 and SP04.
Note In case of a dual stack. the ExtSID must not be changed anymore. 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. 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 eight-character ExtSID. Many SAP Solution Manager Applications use the system type plus ExtSID to identify a technical system. three-digit system ID (SID) from which the ExtSID is derived. The system itself does not know the ExtSID. LMDB deletes special characters and Unicode characters. the ExtSID is defined automatically by LMDB when the system is created. If possible. Additionally. LMDB adds zeros. ExtSID C1D00001 can be derived). If you want to have identical ExtSIDs for both parts. in this case. as described before. it is a local name inside SAP Solution Manager. depending on the number of CIM instances. Run the report The synchronization can take a few minutes. By default. SID and ExtSID are identical. a suffix with 5 digits is appended to the ExtSID. Technical System Software Diagnostics-Relevant Flag You can set the Diagnostics Relevant flag for Product Versions in combination with product instances. (Example: From SID C1D. the installation of add-ons can update the version of software components of a product. An ExtSID of more than eight characters is truncated. but the corresponding executables are not physically installed. as of version SP02. 3. It defines which of the assigned entities will be used by the Diagnostics application. customers can also use a BAdI implementation (LMDB_EXTSID_GENERATOR) to change the proposed value of the extended system IDs. SAP systems have a predefined. adjust one of the ExtSIDs immediately after the system has been created in LMDB. the automatic generation of ExtSIDs cannot ensure the ExtSIDs of AS ABAP and AS Java are identical. But Diagnostics is still supposed to refer to the original version of the 21 . Technical System Software Software Component Versions of Lead-Selected Product Instance Installed Flag Set the Installed flag if the selected entity is installed physically on the system. The flag is not set if the software is Diagnostics-relevant but not installed. The ExtSID must consist of uppercase letters and numbers and of three to eight characters. 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. Background: In some cases. Software is sometimes assigned. for example product assignments. In case of duplicate SIDs for a given system type. the flag is not set.Selecting this option deletes all data that you entered manually. Afterwards. The preferred way to change an ExtSID is to do it manually. If you manually enter less than three characters.
This may not be the preferable value. Standard attributes are Location. Deletion of a Host 22 . Maintenance of Custom Attributes In LMDB you can maintain Custom Attributes for servers. access transaction SMSY and select any system under Select Object. LMDB receives the FQDN and IP address from the data supplier with the highest rank. Host Editor Host descriptions come from SLD and. which then will be transferred to LMDB. and hosts. The information is transported to and used by SMSY (for example to filter systems according to their location). Those alternatives are related to the multiple possible network configurations on the host. For more information. Monitoring System. which write directly to LMDB. in more detail. To do so. For host information coming from Outside Discovery: Change the FQDN in the SMD Agent. check the Details in the System Overview of the Technical System Editor. in this case you have three options: Change the FQDN manually. Note Only create or edit host information manually if it cannot be provided by data suppliers. To find out which data supplier did provide the host information. This implies that the FQDN is no longer overwritten by changes reported via SLD or Outside Discovery. from the SMD agents of Outside Discovery. Then choose Utilities Attribute Definition. Access the Technical System Editor and choose Resync from SLD. Alternative FQDNs and IP addresses are listed under Alternative Hostnames. Select a host and choose Host Operations Maintain Host. For the single value used in the Host Overview. For example the FQDN is important for some configuration tasks and the URL Framework. To edit host information. To create host information. Select the SLD that contains the correct FQDN and IP address. 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. the new attribute will be available to select in the Technical System Editor of LMDB. Manufacturer. choose Host Operations Maintain Host. using the correct alternative name. or Release. For more information. see Cannot Create RFC Connection Because the Host FQDN Is Wrong in the Troubleshooting section. use the Host Editor under SAP Solution Manager: Work Centers (transaction SOLMAN_WORKCENTER) SAP Solution Manager Administration Landscape Hosts.underlying product. the flag is used to define content that should be used for Diagnostics instead of the content that is really installed. After saving a new definition. see SAP note 1626853. technical systems. using one of the alternative hostnames. FQDN and IP Address of a Host In the Host Overview the FQDN (fully qualified domain name) and the corresponding IP address is shown.
Note 23 . It is the recommended way to migrate manually maintained data from SMSY to LMDB. Migrate SMSY Data to LMDB (One-Time Activity) When you upgrade to SAP Solution Manager 7. System must exist in both SMSY and LMDB. for example.The deletion of hosts in the Host Editor of LMDB is supported as of SP03. see SAP Note 1608341. choose Solution Manager: Configuration (transaction SOLMAN_SETUP) Basic Configuration Configure Manually Migrate Installed Product Instances Data. If you do not have such systems. For SP01 and SP02. for example. see Register Technical System Automatically). you do not require this type of migration. For SP01 and SP02. The specific aspect must not be maintained in LMDB yet. the system checks this based on the extended system ID (ExtSID). There are two different types of migration: Aspect-oriented migration (recommended): for transfer of a single kind of information for all technical systems from SMSY to LMDB. You have maintained the product systems properly. Aspect-Oriented Migration (recommended) Aspect-oriented migration transfers one single kind of information for all systems in SMSY to LMDB. Prerequisites: System-Oriented. complete migration: transfers complete technical system descriptions from SMSY to LMDB when no data suppliers are available.1. you can migrate data from SMSY to LMDB once. a system must not have values under Custom Attributes and in the Landscape Pattern field in LMDB. This can be done only once during the setup of SAP Solution Manager. SMSY can contain manually created system description for which no data suppliers are available. Other Attributes (Custom Attributes) can be migrated as of SP03 with transaction LMDB_MIG_CUST_ATTR. Complete Migration System-oriented migration transfers complete technical system description from SMSY to LMDB for which no data suppliers are available (For more information. Diagnostic-relevant product instances: As of SP03. It is the recommended way to migrate manually maintained data. see SAP Note 1607771. During migration. for example manually maintained information under Other Attributes or relevant product instances of technical systems. a system must have values under Other Attributes. To reduce the manual effort for initial transfer of this data to LMDB. or manually added data. 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 Automatically Migrate Diag relevant flags. The specific aspect must be maintained in SMSY. System-oriented.
For the following system types. instances. system-oriented migration is supported: System-Oriented Migration for AS ABAP Complete migration is supported for AS ABAP technical systems and all system entities. 4. The Manufacturer of the assigned database must be maintained. If possible. You have initially synchronized SLD and LMDB. System descriptions that you cannot migrate. if absolutely necessary. Not all data from SMSY needs to be required. The Server of the assigned database must be maintained. 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. do not create landscape data manually. You can check your system descriptions in SMSY with the Landscape Verification tool. Collect it automatically from data suppliers instead. Switch to Edit mode and choose Migrate from SMSY to LMDB. to display the migration log containing success or error information. When the background job has finished.0 as Add-on. clients. System-Oriented Migration of Master Data Management Server (MDM) Migration of the entities instance.1 it is automatically installed. so that the information is updated regularly. To avoid superfluous effort. depending on its type and size. 3. software components. you can choose Display Log. Each system takes a few minutes. Also avoid migration of manually created data. for example because of a firewall. software component and other attributes are supported for the type Master Data Management server. Start SAP Solution Manager: Configuration (transaction SOLMAN_SETUP) and choose System Preparation Prepare Landscape Set Up LMDB. 2. only migrate or create system descriptions that are really necessary. can be maintained manually in the Technical System Editor of LMDB. With SAP Solution Manager 7. proceed as follows: 1. Only migrate systems for which you cannot configure data suppliers. To migrate technical system descriptions from SMSY to LMDB. The tool is available in SAP Solution Manager 7. The migration runs in a background job. For more information. database. Consider a SMSY clean-up before migration. for example. Select the required technical systems and choose Migrate Selected Rows. 24 . and other attributes. see Landscape Verification in the SAP Community Network. Prerequisites: o o o o You have performed the basic configuration of LMDB. Only system description that is sufficient to create an LMDB entry is migrated.
o 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. the technical system must be assigned to the product instance Master Data Server. and a product system with product version SAP MDM 5. must be in the technical system. System-Oriented Migration of Unspecific Cluster System (UNSPECIFIC) Migration of the entities Instance. o You have maintained the Manufacturer of the assigned database. 25 . Database.Layout Server. with Connection Monitoring. o The software components for the technical instances. Choose Create and follow the procedure. Import Server. You have initially synchronized SLD and LMDB. Prerequisites to use technical scenarios in SAP Solution Manager: You have performed the basic configuration of LMDB. Information about technical scenarios is saved in the LMDB. Copy the role to your namespace and change it. you need the SAP_SYSTEM_REPOSITORY_ALL role in SAP Solution Manager. In this case. o You have maintained the Server of the assigned database.5. o The extended system IDs of technical and product systems must be the same. the following prerequisites apply: o The extended system IDs (ExtSIDs) of technical and product systems must be identical. To create or change a technical scenario in LMDB. for example the MDM_SERVER software component in the MDM Server server role. Prerequisites: o You have assigned a database to the system in SMSY. o You have maintained the Manufacturer of the assigned database. Technical Scenario A technical scenario is a group of technical systems which work together. technically. 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. o You have maintained the Instance Number and Server. choose Technical Scenario Wizards under Related Links Configuration. Create a technical scenario: In the SAP Solution Manager: Configuration (transaction SOLMAN_SETUP). 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. For MDM . o A database must be assigned to the system. o You have assigned one or more product instances of a product system to the technical system. For example. and Syndication Servers. Software components must be maintained in the system. o You have maintained the Instance according to the SMSY naming convention. o You have maintained the Server of the assigned database.
1. choose Managed System Configuration Technical Scenarios and filter for technical scenarios of type DBL_STACK (Dual Stack). In this case. the dual stack is not recognized if the Java stack is registered in SLD after the ABAP stack. choose Managed System Configuration Technical Scenarios Scenario Operations Maintain Scenario. for example. Prerequisites: You have performed the basic configuration of LMDB. for example. start SAP Solution Manager: Configuration (transaction SOLMAN_SETUP). You have initially synchronized SLD and LMDB. choose Technical Scenario Wizards under Related Links Configuration. Create a DBL_STACK technical scenario It can happen that a technical scenario is not created automatically for a dual stack system. start SAP Solution Manager: Configuration (transaction SOLMAN_SETUP). register the ABAP stack in SLD again or wait for 24 hours. or if the technical systems were registered in SLD in the wrong sequence. RFC Connections As of SAP Solution Manager 7. Dual stacks are usually identified automatically. You can use these technical scenarios to configure the managed system for both stacks at the same time. Then. The information that it is a dual stack system comes from the ABAP system. technical systems are saved in LMDB. If required. Users and authorization in SAP Solution Manager: SAP_SM_BASIC_SETTINGS role. assigned to the user SOLMAN_ADMIN. Change a DBL_STACK technical scenario To edit an existing technical system of type DBL_STACK. there should be a DBL_STACK technical scenario for this system. Dual Stack Technical Scenario in Managed System Configuration The simplest case of a technical scenario is a dual stack (AS ABAP and AS JAVA). which is created at the start of the SAP Solution Manager. choose Managed System Configuration Technical Scenarios Scenario Operations Create Scenario and follow the procedure. In Technical Scenario Maintenance window. To view technical scenarios for dual stacks. This role is.Change a technical scenario: In the SAP Solution Manager Configuration (transaction SOLMAN_SETUP). if the technical systems have not been registered in SLD for some time. select a system and choose Maintain. therefore. Configuration of RFC Connections During Managed System Configuration 26 . and RFC connections between SAP Solution Manager and managed systems can be created or edited in LMDB. you can also create a DBL_STACK technical scenario manually: Start SAP Solution Manager: Configuration (transaction SOLMAN_SETUP). and the system creates a DBL_STACK technical scenario.
Follow the guided activity. Start SAP Solution Manager: Configuration (transaction SOLMAN_SETUP) and choose Managed System Configuration Technical Systems tab. 2. 3. 27 .1. The RFC connection is configured in step 3. Select a system and choose Configure System.
You can delete CIM instances or their corresponding technical systems. In this case. You can also display statistical information about all CIM classes. Displaying CIM class and instance information Changing CIM instance attributes Deleting CIM instances. choose Asynchronous Generation. in the Details dialog box. LMDB Administration provides the following options: Displaying a status overview about LMDB considering performance and configuration aspects (available as of SP03). Instance Browser On this tab you can search for CIM instances. namespace configuration. you can display details and change attributes. Searching for information in LMDB with various search criteria. you can change attributes in the Instance Attributes tab of the Details dialog box. If there are a lot of instances. the bottom table shows its CIM instances with the times of the earliest and latest changes. 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. Change Log Browser On this tab you can search for change log entries of CIM instances. You can display further details of a selected row. synchronization can take some time and lead to a time-out error. It is strongly recommended that it is only used by experienced users. You can add or delete search rows and save search criteria for future searches.LMDB Administration Note LMDB Administration is an expert tool. and domain settings. In edit mode. 28 . From the search results. content synchronization status. as well as the selected CIM instance. When you delete a technical system. Start transaction LMDB_ADM. You cannot make any changes. as described in the Search for CIM Instances tab. and delete multiple technical systems The different functions of the tool are distributed on the following tabs: Overview This tab gives you an overview of performance data. all CIM instances of the technical systems are deleted. To update the information. If you select an entry. choose Synchronize.
Go to CIM Instances (in NetWeaver 7. perform the following steps: 1. This results in an overlap: Different system descriptions in different source SLDs and duplicate entries for the system clients are created in LMDB.NET System Apache Tomcat Server Application Server ABAP Application Server Java Business Objects Cluster Database System Diagnostics Agent HANA Database IBM WebSphere Application Server Introscope Enterprise Manager Cluster Introscope Standalone Enterprise Manager liveCache Master Data Management Server Microsoft Internet Information Services SAP Web Dispatcher Generic Application System Sybase Unwired Platform TREX System Technical System Type MS_. This data has been imported via content synchronization and mixed up with the correct description in the SAP Solution Manager SLD. its ExtSID and any key information is no longer known in LMDB. see Resynchronization from SLD (with or Without Deletion of Assignments). 3. Restore a Deleted Technical System If a technical system has been deleted from LMDB. Choose the CIM class for your system type. Log on to the source SLD. To load all data of a deleted system into LMDB again.Troubleshooting Damaged Technical System Description in LMDB Example: Additional clients have been created manually in SLD to configure SAP Process Integration.NET ATC ABAP JAVA BOBJ DBSYSTEM DIAGNAGENT HANADB WEBSPHERE IS_MOM IS_EM LIVE_CACHE MDM MSIISINST WEBDISP THIRDPARTY SUP TREX 29 CIM Class SAP_DotNetSystemCluster SAP_ATCServer SAP_BCSystem SAP_J2EEEngineCluster SAP_BOCluster SAP_DatabaseSystem SAP_DiagnosticsAgentInstance SAP_HDBSystem SAP_IBMWSCell SAP_ISMOMServer SAP_ISEMServer SAP_LiveCache SAP_MDMDataServer SAP_MSIISInstance SAP_BCWebDispatcher SAP_ApplicationSystem SAP_SUPCluster SAP_TrexSystem . Technical System Type – Caption . Run a re-synchronization from SLD. For more information. 2. 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.0: Content Maintenance).
Make a pseudo-change to your system. for example: 1. The key instance and the extended SID. Solution: No action required. To find out which data supplier did provide the host information. Or change the FQDN manually in the System Overview. Add an X to the description. 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. check the Details in the System Overview of the Technical System Editor. using one of the alternative host names. the following jobs will run productively again. 5. 4. and select the SLD containing the correct FQDN. 2. using one of the alternative hostnames. Only when the running job is finished. Save again. following jobs are immediately set to complete in order to let the preceding job finish synchronization properly. are written to LMDB. In this case. Note 30 . A predecessor job is processing a large number of pending changes and has not finished yet. Solution: Wait until the predecessor job has finished. Save the change. for example by SID or host name. 3.Unspecific Cluster System Unspecific Standalone Application System UNSPECIFIC UNSPAPP SAP_UnspecificClusterSystem SAP_UnspecificStandaloneApplicatio nSystem 4. Cannot Create RFC Connection Because of Wrong Host FQDN Problem: You cannot create an RFC connection because the FQDN of the host is incorrect. as described under Resynchronization from SLD. Outside Discovery will not overwrite the value anymore. Wait until the changes are replicated into LMDB. 6. 7. Reverse the change. but no detailed system information. Filter to find your system. use the Resync from SLD button. For host information coming from an SLD: Access the Technical System Editor. choose Resync from SLD. Solution: For host information coming from Outside Discovery: Change the FQDN manually in the header data. To transfer all the system information to LMDB.
and how much free space remains. The area relevant for LMDB is CL_LMDB_MODEL_SHM_AREA. This effects long response times. see Monitoring the Synchronization Process. Use of Shared Memory When LMDB processes run. Performance Issues Because of Exhausted Shared Memory The LMDB in SAP Solution Manager 7. with dramatic performance impact. if the shared memory area for LMDB cannot be created. You can get the number of successful read accesses from the field „Accumulated Read Locks“ in the transaction SHMM. For more information. start transaction LMDB_ADM (LMDB Administration). You have to pick the correct one from this list. 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. which allow that data is shared in various user sessions. see: Shared Objects Monitor – Transaction SHMM in the SAP Help Portal. If there is not enough memory for the shared memory segment. 31 . the system reads class information from the database always. As of SP4.1 SP1. class information is read from shared memory. On the Shared Objects Memory tab in SHMM. The size of all objects in shared memory is specified by the abap/shared_objects_size_MB profile parameter. there is an alarm in the Self-Monitoring area of the SAP Solution Manager Administration work center.You can see all available alternative FQDNs and IP addresses under Alternative Hostnames in the Host Editor. If the shared memory of the server is exhausted. At runtime. Check the shared memory status under Content Synchronization Status on the Overview tab. it has a size of about 40 MB.Performance Issues During Synchronization For information on how to check the progress of synchronization. This is quicker than individual database accesses. From SAP Solution Manager Release 7. you can see how much shared memory is currently in use. LMDB uses ABAP shared objects to buffer CIM class information in shared memory. or if the shared memory segment for the LMDB cannot be created for other reasons. Administration of ABAP Shared Memory Areas for LMDB Shared memory objects are ABAP object instances in the shared memory of the application server. The Shared Objects Monitor (transaction SHMM) provides an overview of the area instances in shared objects memory of the current application server.1 relies on ABAP shared objects in the shared memory of the application server. LMDB processes will access the database instead of shared memory. or the shared memory segment CL_LMDB_MODEL_SHM_AREA cannot be created. To see whether the shared memory area is used.
If the number of Pending Source Changes is larger than 0. Wait for about ten minutes and return to transaction SOLMAN_SETUP System Preparation 6. that shared memory is exhausted. This means that someone has changed the name of the object server. see Update Statistics with BRCONNECT in the SAP Help Portal. without the CBO realizing this. statistics can be outdated. Repeat the change of the object server name in SLD. you have to ensure that the Oracle database statistics are updated. Make sure to update statistics for the following tables as well: LMDB_P_ASSOC (Associations) LMDB_P_CHANGELOG (Change Log) 32 . The job log in SM37 must not show any more errors. 2. only carry out step 1 and 2.1 system. After you started the content synchronization between SLD and LMDB. it is recommended to update the statistics repeatedly while the content synchronization job is running. click Details.No Progress in Incremental Synchronization If the incremental synchronization between SLD and LMDB does not finish after a long time. Create a new SLD synchronization in SOLMAN_SETUP. enter *LDB* under Job Name and an asterisk (*) under User. database statistics are outdated. For more information. To create a job overview. 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”. and if the Date of Source Change Log ID is in the past. Outdated Oracle Database Statistics If the SAP Solution Manager system is installed with an Oracle database. start transaction SM37. Reasons can be. most LMDB tables are empty. for example. 5. 3. 4. If the name change of the object server was made on purpose in SLD. start transaction DB20 with parameter LMDB_P_INSTANCE and check the optimizer statistics. proceed as follows: 1. After the installation or upgrade of the SAP Solution Manager 7. the real costs for the full table scan become higher and higher. Rename the object server name to its previous name under SLD Administration Profile Object Server. automatic synchronization of SLD and LMDB. For best performance. In case the statistics are out-of-date. If it is active.5 Setup LMDB to check whether all pending changes are being processed completely. Check whether the synchronization is still active under transaction SOLMAN_SETUP System Preparation 6. If the LMDB tables are continually filled. proceed as follows: 1. To do so. Check the job logs and look for the error messages. use the Update Statistics with BRCONNECT function. which LMDB now cannot identify correctly any longer. Pending changes from SLD are not transferred to LMDB. This will force the Cost Based Optimizer (CBO) to realize the increasing fill level of the LMDB tables. 2. Delete the SLD synchronization in SOLMAN_SETUP. the changes are not going through and the connection between source and target is probably corrupt. the Cost Based Optimizer (CBO) will tend to run a full table scan during all subsequent database accesses. for example because of full. If statistics are calculated at this time.5 Setup LMDB. If the name change in SLD was made by mistake. or SLD is down.
see SAP Note 1555955. It is recommended that you do not stop the synchronization job for a statistics update . A product instance is both a technical entity. Like products.0 Product instance (previously main instance): The smallest installable entity of a product. avoid the maintenance of Unicode characters in SLD. 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) You can update the statistics with BRCONNECT while the content synchronization job is running. All products are specified in the Product and Production Management System (PPMS). automatic synchronization. Example: SAP ERP Product version: A version or release of an SAP product. The performance improvement will become effective automatically. Therefore. these are defined in the Product and Production Management System (PPMS). 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. Example: SAP ERP 6. 33 . It performs business tasks. Product: An SAP offering in the SAP price list. 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. because it can be installed. The purpose of Outside Discovery is to automatically discover. For more information. and a functional entity. collect and send information from the monitored system to SAP Solution Manager. 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. because the various product instances in a product perform various tasks.
a software component is installed on the system and is used by only one instance. which are updated by upgrades. On MS IIS systems.1 has the product instance AS ABAP (SAP SOLUTION MANAGER 7. A software component usually exists in several release versions. Product system (previously system): Grouping of technical systems which belong to one or more products.Example: SAP ECC Server The product SAP Solution Manager 7. a software component is installed on every host. Example: SAP Solution Manager. depending on the number of instances using it). Technical systems may consist of technical (sub)systems. A product system SAP Solution Manager comprises one technical system ABAP and one technical system JAVA.0: Application Server ABAP). a software component is installed on the system and is used by every instance.1: Solution Manager ABAP Stack). On BOBJ systems. Technical system (previously system component for non-ABAP systems): Self-contained technical unit which is installed and administered as a whole. once per each instance. 34 . SAP_HR On ABAP systems. Example: SAP_BASIS. Software component: Set of software objects grouped in packages and delivered together. and includes the product instance AS ABAP (SAP EHP2 FOR SAP NETWEAVER 7. You can import support packages separately for each software component. (Therefore it can be installed several times on one host.
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue listening from where you left off, or restart the preview.