LMDB Setup Guide En

Landscape Management Database (LMDB)

S AP Solut ion Manager 7 .1 SP01

- 2 -

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

- 3 -

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.

- 4 -

Copyright ...................................................................................................................................... - 2 -

Landscape Management Database (LMDB) ................................................................................... - 6 -

Use ............................................................................................................................................... - 6 -

Installing LMDB ............................................................................................................................ - 6 -

Landscape Data Management Topology ..................................................................................... - 7 -

Integration .................................................................................................................................... - 7 -

Architecture ...................................................................................................................................... - 9 -

Landscape Data Management „The Big Picture“........................................................................... - 14 -

Synchronization of SLD and LMDB ............................................................................................... - 15 -

Use ............................................................................................................................................. - 15 -

Prerequisites .............................................................................................................................. - 15 -

Functional Scope ........................................................................................................................ - 15 -

Synchronization of LMDB and SMSY ............................................................................................ - 17 -

Use ............................................................................................................................................. - 17 -

Prerequisites .............................................................................................................................. - 17 -


Result ......................................................................................................................................... - 17 -

Installing LMDB .............................................................................................................................. - 18 -

Use ............................................................................................................................................. - 18 -

Prerequisites .............................................................................................................................. - 18 -

Initially Configuring LMDB .......................................................................................................... - 18 -

Result ......................................................................................................................................... - 20 -

Using LMDB ................................................................................................................................... - 21 -

Use ............................................................................................................................................. - 21 -

LMDB Entities ................................................................................................................................ - 21 -

Create Technical System with Data Suppliers ............................................................................... - 23 -

Use ............................................................................................................................................. - 23 -

Prerequisites .............................................................................................................................. - 23 -

Create Technical Systems with Data Suppliers ......................................................................... - 23 -

Technical System Editor ................................................................................................................ - 27 -


Display System Configuration with the Technical System Editor .................................................. - 28 -

Use ............................................................................................................................................. - 28 -

Prerequisites .............................................................................................................................. - 28 -

Displaying the System Configuration with the Technical System Editor .................................... - 28 -

Create Technical System with the Technical System Editor ......................................................... - 29 -

Use ............................................................................................................................................. - 29 -

Prerequisites .............................................................................................................................. - 29 -

Create Technical System Description with the Technical System Editor .................................. - 29 -

- 5 -

Change System Configuration with the Technical System Editor ................................................. - 30 -

Use ............................................................................................................................................. - 30 -

Prerequisites .............................................................................................................................. - 30 -

Change the Description of a Technical System with the Technical System Editor.................... - 30 -

Result ......................................................................................................................................... - 31 -

Delete Technical System ............................................................................................................... - 31 -

Use ............................................................................................................................................. - 31 -

Prerequisites .............................................................................................................................. - 31 -

Delete the Description of a Technical System with the Technical System Editor ...................... - 32 -

Migrate SMSY Data to LMDB ........................................................................................................ - 32 -

Use ............................................................................................................................................. - 32 -

Prerequisites and Functional Scope .......................................................................................... - 33 -

Migrating ..................................................................................................................................... - 34 -

Result ......................................................................................................................................... - 35 -

Technical Scenario ........................................................................................................................ - 36 -

Use ............................................................................................................................................. - 36 -

Prerequisites .............................................................................................................................. - 36 -

Create and Change Technical Scenarios .................................................................................. - 36 -

RFC Connections ........................................................................................................................... - 39 -

Use ............................................................................................................................................. - 39 -

Prerequisites .............................................................................................................................. - 39 -

Configuring RFC Connections ................................................................................................... - 39 -

LMDB Administration ..................................................................................................................... - 41 -

Use ............................................................................................................................................. - 41 -


Troubleshooting ............................................................................................................................. - 42 -

Glossary ......................................................................................................................................... - 45 -

- 6 -

Landscape Management Database (LMDB)

Use

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

The main task of LMDB is to provide information about the system landscape, centrally. The Solution Manager System Landscape (transaction SMSY) and SLD already provide comparable functions, with different technologies, for different purposes. LMDB aims for a more flexible extendability of the landscape model and the unification of SLD and SMSY in SAP Solution Manager.

Particularly significant landscape elements are technical systems, product systems and logical components.

Installing LMDB

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

If you upgrade SAP Solution Manager from release 7.0 to 7.1, you must install LMDB. From SAP Solution Manager 7.1, technical system data can only be maintained in the technical system editor, not in SMSY.

You can migrate technical system data from SMSY into LMDB, but it is not recommended. Register by Data Supplier instead.

You can also adjust various configuration parameters in Customizing for SAP Solution Manager, if required. In Customizing for SAP Solution Manager (transaction SPRO SAP Reference IMG), choose: SAP Solution Manager Technical Settings Landscape System Repository (LMDB) Set Up Parameters

http://www.dmtf.org/

- 7 -

Landscape Data Management Topology

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

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

SLD

(design-time)SLD

(runtime)

Systems Managing Systems

SAP Solution

Manager

LMDBSLD Sync

(unidirectional)

Forwarding of data on

Technical Systems

Manual export/ import

(optionally using CTS+)

Data Supplier registrat.

of Technical Systems

Integration

Technically, LMDB is the ABAP complement of SLD in Java. SLD and LMDB cooperate via a connection to synchronize contents, using the same principle as the synchronization between two SLD systems. All data which is already in a connected SLD can therefore be read from LMDB. The „SMSY synchronization“ from LMDB to SMSY makes technical system data in LMDB accessible to read applications in SMSY.

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

System Data Supplier

The automatic registration of systems to SLD, and its synchronization with the LMDB is the preferred way of putting landscape elements in the LMDB. The data suppliers are implemented in the managed systems. Most data suppliers currently send their data to SLD, for example the ABAP application server (AS) with the transaction SLD Administration (RZ70). Synchronization of SLD and LMDB contents put this data 1:1 in the LMDB. A small part of the data supplier, „Outside Discovery“, writes its data directly in the LMDB.

Technical System Editor

Systems are registered manually in the Technical System Editor if there is no data supplier, or the data supplier cannot be used, for example because of a firewall. The disadvantage of this manual method is that the data is not updated automatically, so manually entered data can become obsolete. If the system is subsequently registered, previously manually-entered data is not refreshed or overwritten.

Migrating data from the transaction SMSY into LMDB

Data migration from SMSY to LMDB is a special case of a data supplier. The step in the transaction SOLMAN_SETUP copies SMSY data to technical systems in the LMDB, usually once only, immediately after upgrading SAP Solution Manager to version 7.1.

Downloading the software catalog

- 8 -

Data about usable products and software components is delivered in the SAP Service Marketplace. This content, SAP CR CONTENT, can currently only be put in SLD, but can be synchronized 1:1 into LMDB.

For more information, see SAP note 669669.

Downloading the SAP CIM model

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

Landscape Verification Tool

The Landscape Verification Tool analyzes whether your system landscape, particularly the assignment of product systems, is maintained correctly in the Solution Manager system landscape (transaction SMSY).

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

http://www.sdn.sap.com/irj/sdn/alm-update-management?rid=/webcontent/uuid/70fc3790-7ec9-2d10-57ad-95b2d0d1185d

- 9 -

Architecture

LMDB describes landscape elements with the SAP enhancement of the Distributed Management Task Force Common Information Model (CIM), analogously to the System Landscape Directory (SLD).

For more information, see the SAP Developer Network, under http://sdn.sap.com/irj/sdn/nw-sld and www.dmtf.org.

Integration in the system landscape

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

Configuration 1

The systems in the system landscape are registered in a remote SLD (1a), which is then synchronized with LMDB (2a). LMDB is then synchronized with SMSY (3), and, if required, data is migrated (4). This is the recommended configuration.

System Landscape

System 1

System 2

System 3

AS Java

Remote SLD

Solution Manager

LMDB SMSY

Migration (4)

SMSY - Synchronization (3)

(1a) Sync (2a)

http://www.dmtf.org/

- 10 -

Sync (2b)

Configuration 2

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

Note:

Technical systems must be registered on only one SLD, otherwise inconsistencies may arise in LMDB.

Productive System landscape

System 1

System 2

System 3

AS Java

Remote SLD

Solution Manager

LMDB SMSY

Migration (4)


(1a) Sync (2a)

Remote SLD

System 1

System 2

System 3

non - productive system landscape

AS Java

(1b)

- 11 -

Configuration 3

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

Configuration 4

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

System landscape

System 1

System 2

System 3

AS Java

Remote SLD

Solution Manager

LMDB SMSY

Migration (4)


(1a)

Sync (2b)

Local SLD

(1b)

System landscape

System 1

System 2

System 3

(1c)

Solution Manager

LMDB SMSY

Migration (4)

SMSY - Synchronization (3) Sync (2b)

Local

SLD

- 12 -

Minimum System Landscape Directory (SLD) Requirements

SAP NetWeaver Release

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

SAP NetWeaver Release (SLD) Supported Support Package Stack Level

SAP NetWeaver 6.40 not supported

SAP NetWeaver 7.0 not supported

EHP1 for SAP NetWeaver 7.0 not supported

EHP2 for SAP NetWeaver 7.0 SP6, patch 5

SAP NetWeaver 7.1 SP9

EHP1 for SAP NetWeaver 7.1 all SPs

SAP NetWeaver 7.2 all SPs

SAP NetWeaver 7.3 all SPs

If you cannot give your central SLD a required status, you can use another SLD which does satisfy the minimum requirements (e.g. the SAP Solution Manager SLD), and fill it with the data from your central SLD, using SLD bridge functionality.

Model and CR Content

The CIM model and SAP CR content requirements are:

CIM model 1.6.16 or higher

Newest SAP CR CONTENT, at least version 7.0

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

Change notification from SLD

The immediate notification of LMDB about changes in SLD accelerates the synchronization of changes in the SLD – LMDB – SMSY chain, but active change notification from SLD to LMDB requires a higher version of SLD:

SAP NetWeaver Release (SLD) Supported Support Package Stack Level


EHP1 for SAP NetWeaver 7.1 SP7



See SAP Note 1546079 for details.

- 13 -

Integration with the System Landscape Directory

There are data suppliers for most technical systems which register the system in the System Landscape Directory (SLD) automatically, so SLD is the central data source for LMDB. You should make changes to technical systems by registering in SLD again.

Data supplier to register systems in SLD automatically

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

Sequence: There is a sequence for the contents between SLD and LMDB, as between two SLDs. It determines which status wins in case of conflicts. The LMDB must always have priority (see Initial Configuration of LMDB), otherwise manual changes in LMDB would be overwritten by SLD.

For further information, see the SAP Community Network, under (SAP NetWeaver System Landscape Directory: Conflicts & Ranks in Full Automatic Content Synchronization)

For further information about SLD topology, see the SLD Planning Guide in the SAP Community Network (http://www.sdn.sap.com/irj/sdn/nw-sld)

If there are several SLDs in the system landscape, e.g. an SLD for the production systems and one for the development and test systems, you can connect several source SLDs to the LMDB.

Technical systems should only be registered in one SLD, otherwise inconsistencies may arise in LMDB.

Integration with the Solution Manager System Landscape (SMSY)

From SAP Solution Manager release 7.1, you can only change technical systems in the LMDB technical system editor.

You still manage product systems in the Solution Manager system landscape (transaction SMSY). Some SAP Solution Manager applications still get their landscape information from the SMSY data repository.

Integration with the Landscape Verification Tool

The Landscape Verification Tool analyzes whether your system landscape, particularly the assignment of product systems, is maintained correctly in the Solution Manager system landscape (transaction SMSY).

For further information, see the SAP Community Network, under Landscape Verification

http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/20264


http://sdn.sap.com/irj/sdn/nw-sld


- 14 -

Landscape Data Management „The Big Picture“

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

LMDB SLD

Full AutomaticSynchronisation

SMSY

ContinuousSynchronisation

Optional:RepeatableTechnical System migration

Applications, e.g.

Maintenance Optimizer

Monitoring & Alerting

Root Cause Analysis

Usage of Landscape

Technical

System

Solution Manager

- Maintain- Enhance- Monitor

Data Supplier configuration, e.g.:- Transaction RZ70 (ABAP)- Visual Administrator,

NetWeaver Administrator (Java)

- SLDREG

Landscape Description

3

1

2

5

4

3*

1. The data supplier registers technical systems in SLD

2. The technical system information, the CIM model, and the CR content are synchronized with LMDB by Full Automatic Synchronization.

3. Technical system descriptions are continuously replicated from LMDB to SMSY

3* Technical system descriptions can be migrated from SMSY to LMDB.

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

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

The landscape data management components are described in detail below.

- 15 -

Synchronization of SLD and LMDB

Use

This function ensures that the data from SLD is complete and up-to-date in LMDB.

Prerequisites

You have performed the LMDB basic configuration.

SLD is running (see Minimum System Landscape Directory (SLD) Requirements).

A managed system is registered in SLD.

Users and authorization

SAP Solution Manager

o User with administration authorization

SLD

o The user in an SLD with a release since SAP NetWeaver 7.1, needs the role SAP_SLD_CONTENT_SYNC.

o The user in an SLD with release SAP NetWeaver 7.0, needs the role SAP_SLD_GUEST.

Functional Scope

SLD and LMDB (content) is synchronized in the same way as two SLD systems with full automatic content synchronization.

Synchronization is based on the following procedure:

All changes are recorded sequentially in the source (SLD change log).

Remote communication is by HTTP(S).

The recipient (here LMDB) is notified when a change occurs (exception: the source is SLD 7.0).

The recipient (LMDB) gets the change.

Regular polling and notification ensure synchronization.

The recipient performs conflict resolution on the changes.

The conflict resolution result determines the sequence of source and target.

A conflict is when the target has a different initial status than when making the change in the source.

After installation or upgrade of SAP Solution Manager 7.1, LMDB is empty, so in the first phase of the process, all contents are read from the source (SLD) into the target (LMDB). This is called full synchronization. It takes several hours, and should be scheduled overnight. LMDB notes the starting time of the process, and switches to incremental synchronization mode when full synchronization has finished. Changes are then propagated either immediately, or at the latest every 10 minutes, in batch jobs.

The following points apply to the configuration of synchronization in the transaction SOLMAN_SETUP (see „Initial Configuration of LMDB“):

You cannot configure notifications for SLD version 7.0.

Set the sequence of the source (SLD) lower than the sequence of the target (LMDB). This prevents changes in SLD from overwriting manual changes made in LMDB in the technical system editor.

- 16 -

Leave large gaps in the sequence, e.g. SLD=100, LMDB=200. This gives you flexibility when changing your synchronization landscape.

If there is a default sequence, don’t change it, or you can affect other, previous synchronization connections.

Although the minimum release requirements are lower, use a separate remote SLD with version 7.1 or higher for synchronization, so that you have the latest SLD functional scope. The local SLD in Solution Manager has the version 7.0 (see Architecture). In the remote SLD, all landscape data should be consolidated. Ideally, all systems in the landscape register there directly. If this is not possible, LMDB must be synchronized with several SLDs, but several SLDs may contain contradictory data. The contents of LMDB depends on the sequence of the changes in the various SLD systems. Even if the procedure is theoretically unambiguously specified, the search for errors in several SLDs in the case of conflict can be time-consuming, so it is better to use one SLD to supply LMDB.

Once it has been configured, synchronization between SLD and LMDB is automatic. LMDB queries SLD for changes every 10 minutes. They are then copied into LMDB. If SLD has version 7.1, and notification is active, SLD reports changes to LMDB which gets the data.

For more information, see the SAP Community Network, under (How to Ensure that SLD Data is Available during Maintenance)



- 17 -

Synchronization of LMDB and SMSY

Use

A lot of SAP Solution Manager applications, such as the work center or transaction SOLMAN_SETUP, get their landscape information from LMDB. Others do so from SMSY, so all relevant technical system information must be copied from LMDB into SMSY.

Prerequisites

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

SLD and LMDB have been initially synchronized.



o The SOLMAN batch user (e.g. SOLMAN_BTC) created in SOLMAN_SETUP, is used automatically here.

Functional Scope

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

Automatic synchronization of changes from SLD

When changes are written from SLD to LMDB, they are logged in the LMDB change log. A check is made for new changes, at least every 5 minutes. If there are changes, all technical system data is written to SMSY.

Automatic synchronization of changes written manually to LMDB by the technical system editor

When you save the changes, the system writes them directly to SMSY, and they are logged in the change log.

Result

Status changes in LMDB are in SMSY in less than 5 minutes, so changes in SLD are in SMSY in less than 15 minutes.

- 18 -

Installing LMDB

Use

To be able to use LMDB, you must perform basic configuration for it in the transaction SOLMAN_SETUP, during the basic configuration of SAP Solution Manager after installation or upgrade.

Prerequisites

You have performed all previous system preparation steps in SOLMAN_SETUP.

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

Users and authorizations


o Users with administration authorization

SLD

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

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

Initially Configuring LMDB

1. Call the transaction SOLMAN_SETUP.

2. Choose System Preparation

When you start to configure LMDB, the system checks whether LMDB has an object server name. If not, a window opens, and you can enter a new object server name. This name, with the CIM namespace, specifies the absolute path of the LMDB objects. The object server names should be different in all SLDs and LMDBs. SAP Note 935245 contains naming recommendations.

3. Choose Prepare Landscape -> Set Up LMDB, in the guided activity.

4. In the area Remote Content Change Subscriptions, choose Add, and follow the wizard.

1. Specify whether you want to use notifications, which are only available with SLD from NetWeaver version 7.1 (see „Minimum System Landscape Directory (SLD) Requirements“. If you select this option and use SLD NetWeaver version 7.0, you are later informed that this function is not available.

SLD has a minimum support package level requirement for notification configuration. See SAP Note 1546079.

2. Enter the SLD connection data. The URL for SLD is http://<host name>:<port>. In a standard installation, the port is: 5<SLD system Java instance number>00.

- 19 -

3. Enter the namespace and the sequence of the source (SLD) which you entered in step 2.

The default namespace is sld/active.

The sequence is a positive whole number which specifies the sequence in the synchronization landscape: the higher the number, the higher the sequence. If the namespace already has a sequence, it is displayed when you select the namespace. You should not change it. If you must do so, retain the sequence (higher/lower) of existing synchronization connections. If there is no assignment, -1 is displayed, and you can assign a sequence to the namespace.

The sequence should be lower than the sequence of the target.

Example: To be flexible for subsequent changes in your synchronization landscape, use a sequence of 100 for the source and 200 for the target.

4. If the source SLD has NetWeaver version 7.1 and supports notifications (see „Minimum System Landscape Directory (SLD) Requirements“, enter the target connection information. Otherwise, this wizard step is inactive.

5. Enter the namespace and sequence of the target (LMDB).

For LMDB from release 7.1, only the namespace active is supported.

The sequence which you enter here should be higher than the sequence of the source, to prevent changes made manually in the Technical System Editor being overwritten by the synchronization.

Example: To be flexible for subsequent changes in your synchronization landscape, use a sequence of 100 for the source and 200 for the target. If a sequence has already been assigned to SLD, add 100 to it.

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

Synchronization starts when you activate the configuration.

Complete synchronization can take several hours, depending, for example, on the number of systems in SLD, and the hardware.

Note:

See SAP Note 1555955 and the Troubleshooting section for information about updating Oracle database statistics.

- 20 -

Monitoring the Synchronization Process

You can monitor the procedure with standard transactions.

Transaction SM37 monitors jobs. The job log tells you, for example, the progress of a complete synchronization, or any problems. The name of the synchronization job for the target namespace is SAP_LMDB_LDB_<namespace ID>, e.g. SAP_LMDB_LDB_0000000001.

Transaction SLG1 (Display Logs) for the object AI_LMDB, shows synchronization errors, by default. You can extend the analysis, and for example, also show warnings. Extending can impair performance, so only do so if necessary.

In the view V_LMDB_LOG_CONF, you can configure the analysis per user. You can restrict it at user, subobject and log level.

Jobs usually run under the SOLMAN_BTC system user. If no user is configured, a job runs under the user who activated the subscription.

Result

The result of complete synchronization is that the CIM model and the entire content of SLD are loaded into LMDB. LMDB has the status Incremental Synch. Active.

- 21 -

Using LMDB

Use

All Solution Manager work centers, especially all SAP Solution Manager Diagnostics applications, which mainly use technical system data, get their technical system information from LMDB. A lot of steps in the transaction SOLMAN_SETUP also get their information from LMDB. Other SAP Solution Manager applications also get their landscape data, especially product system and logical component data, from SMSY.

You can perform the following tasks with LMDB:

Create technical system using data suppliers

Create technical system manually with the Technical System editor

Display or change system configuration with the Technical System editor

Delete technical system

Migrate SMSY data to LMDB

LMDB Entities

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

Entity Data Source Editor Notes

ABAP application server SLD data supplier Technical system editor

Apache Tomcat server SLD data supplier Technical system editor

No installed application product information

Business object cluster SLD data supplier Technical system editor

Database system SLD data supplier, outside discovery

Technical system editor

Diagnostics Agent SLD data supplier Technical system editor

Introscope Enterprise Manager Server

Manual SOLMAN_SETUP Configuration from SOLMAN_SETUP

Introscope Manager of Manager

Manual SOLMAN_SETUP Configuration from SOLMAN_SETUP

Java application server SLD data supplier Technical system editor

LiveCache AS ABAP data supplier

Technical system editor

Master Data Management server

SLD data supplier Technical system editor

Microsoft internet information service

Outside discovery Technical system editor


- 22 -

.NET System Manual Technical system editor

TREX system SLD data supplier Technical system editor

SAP Web Dispatcher SLD data supplier Technical system editor

IBM WebSphere Cell SLD data supplier Technical system editor


Unspecific application system

SLD data supplier Technical system editor

Host Outside discovery Not in SAP Solution Manager 7.1 SP1

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

Product system Manual SMSY

Logical component Manual SMSY

- 23 -

Create Technical System with Data Suppliers

Use

The preferred way of putting landscape elements in LMDB is automatic system registration. The data suppliers are implemented in various systems. Most of them send their data to SLD. This data is sent 1:1 to LMDB by synchronizing the contents from SLD. The SMD agent („Outside Discovery“) writes directly into the LMDB. This is mainly host and database data.

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

Prerequisites

You have performed the basic configuration of LMDB.

You have initially synchronized SLD and LMDB.


Systems to be connected

AS ABAP administration user

AS Java administration user

For all other products, see the product IMG.

SLD

SLDDSUSER or another user with the role SAP_SLD_DATA_SUPPLIER.

Create Technical Systems with Data Suppliers

Each architecture has its own data supplier, which is described in detail in its documentation. For some system types, the data supplier is outside the architecture („Outside Discovery“), and writes directly into LMDB. Other system types have to be captured manually. The following sections describe the recommended system integration procedure per system type.

Detailed information about individual products is beyond the scope of this setup guide. Information about the configuration of specified products is in the SAP Community Network, under (Maintenance of Product in the System Landscape)

ABAP Application Server (AS ABAP)

There is an SLD data supplier for AS ABAP, from release 4.0B, so always register an AS ABAP in SLD with the transaction RZ70, and synchronize the data automatically with LMDB and SMSY.

From NetWeaver version 7.02, the AS ABAP data supplier provides installed product instance information, so the installed products must only be configuration in LMDB for older NetWeaver versions. When the installed products have been maintained, a product system with the relevant product instances is automatically created in SMSY. Check the definition of the product system in SMSY. Assign other technical systems to the product system (for example AS Java), if necessary.

Set up the data supplier for AS ABAP as follows:

1. Log on to the system to be registered.

2. Call transaction RZ70.

3. Enter the SLD service host and service (sapgwXX). These parameters are in SLD, under Administration Details.

4. Activate the configuration

5. Start the data collector and job scheduling

http://sdn.sap.com/irj/sdn/nw-sld

http://wiki.sdn.sap.com/wiki/x/4I-uDQ


- 24 -

Apache Tomcat Server (ATC)

There is a data supplier for the Apache Tomcat server, which delivers Apache Tomcat server product information. Product information is not always provided for the installed applications, so manual post-processing in LMDB is sometimes required.

Business Object Cluster (BOBJ)

There is a data supplier for Business Objects Enterprise (BOE), which delivers the product information, so manual post-processing in LMDB is not required. For other BOBJ products, there is a data supplier for the system type „Unspecific Application System“.

Database System (DBSYSTEM)

Various database system information is delivered by various data suppliers, e.g. AS ABAP. The SMD agent Outside Discovery delivers all the information directly to LMDB (the information is not available in SLD). The Outside Discovery delivers software component information, which is sufficient for database systems, so manual post-processing in LMDB is not required.

Diagnostics Agent (DIAGAGENT)

There are data suppliers for diagnostics agents, which deliver all necessary information, so manual post-processing in LMDB is not required.

Introscope Enterprise Manager Server (IS_EM)

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

Introscope Manager of Manager (IS_MOM)

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

Java Application Server (AS Java)

There is a data supplier, which is set up with the Visual Administrator until NetWeaver Release 7.00, and with the SAP NetWeaver Administrator from NetWeaver Release 7.10, for the AS Java. From NetWeaver Version 7.02, the AS Java data supplier delivers information about installed product instances, so installed products only need to be configured in LMDB for older NetWeaver versions

Setup with the Visual Administrator is as follows:

1. Start the Visual Administrator of the system to be registered. It is in the directory \usr\sap\<SID>\<Instance>\j2ee\admin (go.bat for Windows, or go.sh for Linux/Unix)

2. In Visual Administrator, choose Cluster → Server → Services → SLD Data Supplier → Runtime → HTTP Settings

3. Enter the following http connection data:

SLD host

Default http port (z.B. 5<instance number>00

Specify the user SLDDSUSER, and check that it has the J2EE security role DataSupplierLD.

the user password

4. Save your entries

5. Check your settings by sending data to SLD manually.

Setup with the SAP NetWeaver Administrator is as follows:

1. Start the SAP NetWeaver Administrator with the URL: http://<host>:<port>/nwa

2. Choose Configuration Management Security Management Destinations

- 25 -

3. Create a target of type http with the name SLD_DataSupplier, and enter the required data. If this target already exists, check its configuration, and change it if necessary. Check the connection with Ping Destination.

4. Save your settings

5. Choose Configuration Management Infrastructure Management SLD Data Supplier Configuration

6. Choose Collect and Send Data

LiveCache

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

Master Data Management Server (MDM)

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

Microsoft Internet Information Service (MSIISINST)

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

.NET System (MS_.NET)

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

TREX System

There are data suppliers for TREX systems, but they do not deliver product information, so you must enter it in LMDB in the technical system editor, subsequently.

SAP Web Dispatcher (WEBDISP)

The SAP Web Dispatcher has a data supplier, which does not deliver product information, from version 7.2. You must add the product information in the LMDB in the technical system editor, subsequently.

IBM WebSphere Cell (WEBSPHERE)

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

Unspecific Application System

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

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

You create unspecific application systems for which there are no data suppliers, in LMDB in the technical system editor, manually.

Current overview of known unspecific application systems:

Technology Type Type Product Data Supplier

ALLOY Stand- SAP Alloy (IBM) yes

- 26 -

alone

BCMClusterTechnology Cluster SAP BCM SOFTWARE yes

BOFC_Cluster Cluster SBOP FINANCIAL CONSOLIDATION

in preparation

BPCMSCluster Cluster SBOP BPC MS in preparation

BPCNWCluster Cluster SBOP BPC NW in preparation

ClickSoftwareCluster Cluster SAP WS&O BY CLICKSOFTWARE

yes

ConvergentChargingCluster Cluster SAP Convergent Charging yes

CSLCluster Cluster TPT Commodity SL yes

DataServicesCluster Cluster SBOP Data Services yes

EPOSCluster Cluster SAP ENTERPRISE POS yes

ESOCluster Cluster SAP SOURCING/CLM yes

InfoInterchangeServer Stand-alone

SAP INFO INTERCHANGE yes

LiveEnterprise Cluster SBOP EVENT INSIGHT yes

MigrationCluster Cluster SMSY Migration yes

PCMCluster Cluster SBOP PCM yes

PMCluster Cluster SAP PROMOTION yes

RTOMCluster Cluster SAP RTOM yes

SAPPOS_Cluster Cluster SAP POS yes

SBOPEnterprise31 Cluster SBOP Enterprise 3.1 yes

Host (Computer System)

A host is not really a technical system – technical systems are installed on hosts. The technical systems are based on the host, but because the host is an underlying system, accurate information about it is important. The required detailed information is provided by the Outside Discovery, via the SMD agent. SAP Solution Manager release 7.1 SP1 does not contain a host editor.

- 27 -

Technical System Editor

The technical system editor creates, changes and deletes technical system data in LMDB, manually.

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

Functional Scope

The technical system editor has the modes Create, Display and Edit. The current mode is displayed in the top line.

You cannot make changes in display mode. To switch from display to edit mode, choose Edit.

You can change or delete the selected technical system in edit mode.

To switch from edit display mode, choose Write-Protected. You can check the plausibility of the changed data with Check.

You can save changed data with Save.

The technical system editor window is divided into three areas in edit and display modes:

Header

The header displays the technical system name and type.

Navigation

The navigation area at the left-hand side of the window shows the components of the technical system type, e.g. the software used, the system database and the technical instances.

Detail Area

The detail area, at the right-hand side of the window shows details of the system component selected in the navigation area. In edit mode, you can change this data.

- 28 -

Display System Configuration with the Technical System Editor

Use

The technical system editor can display detailed information about the technical systems in your system landscape.

Prerequisites





o SAP_SYSTEM_REPOSITORY_DIS

Displaying the System Configuration with the Technical System Editor

There are two ways of displaying the system configuration with the technical system editor.

Alternative 1

1. Call the SAP Solution Manager transaction SOLMAN_SETUP.

2. Choose Managed Systems Configuration

3. Choose the system to be displayed, in the Technical Systems tab.

4. Choose System Operations Display System.

The technical system editor opens and displays the technical system data.

Alternative 2

1. Call the SAP Solution Manager work center (transaction SOLMAN_WORKCENTER)

2. Choose the SAP Solution Manager Administration work center

3. Choose Landscape

4. You can create a query

5. Select the system to be displayed

6. Choose System Operations Display System

The technical system editor opens and displays the technical system data.

Only alternative 1 is described below, alternative 2 also applies to creation, change or delete.

- 29 -

Create Technical System with the Technical System Editor

Use

If there is no data supplier for a system, you can create a system in the LMDB, manually, with the technical system editor.

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

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

Prerequisites





o To create a technical system in LMDB, you need the role: SAP_SYSTEM_REPOSITORY_ALL

This role authorizes you to change systems in LMDB. You can restrict the authorization with LMDB authorization objects. Copy the role into your namespace, and change the role.

Create Technical System Description with the Technical System Editor


2. Choose the Technical Systems tab in the Managed Systems Configuration view.

3. In the Technical Systems tab, choose System Operations Create System.

The system opens the Technical System Editor in create mode.

4. Specify the system type. The system only offers system types which you can create with the editor. Choose Continue.

5. The system asks for further data, e.g. the system name, the installation number and the host name, depending on the system type selected. Choose Continue.

6. An extended system name (SID) is proposed. Accept it and choose Save.

7. You go to another guided activity, in which you can complete the information about your system.

For more information, see the SAP Community Network, under (Maintenance of Product in the System Landscape)



- 30 -

Change System Configuration with the Technical System Editor

Use

When you create a technical system in LMDB, manually, its data is not automatically updated, because of the priority of LMDB. If changes are required, you must also make them manually. For some system types, manual changes are required because, for example, information delivered by older data suppliers is no longer sufficient. See Create Technical System with Data Suppliers

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

Prerequisites





o To change a technical system in LMDB, you need the role: SAP_SYSTEM_REPOSITORY_ALL

This role authorizes you to change systems in LMDB. Special LMDB authorization objects can restrict authorization. Copy the role into your namespace and change the role.

Change the Description of a Technical System with the Technical System Editor

You can open the technical system editor and change entries, in the following ways:

Call from the transaction SOLMAN_SETUP:


2. Choose Managed Systems Configuration.

3. Choose a system in the Technical Systems tab.

4. Choose System Operations Maintain System.

The technical system editor opens.

5. Make the changes.

6. Save your entries.

Call from SMSY:

1. Call the SAP Solution Manager transaction SMSY.

2. Choose a technical system.

3. Go to change mode.

- 31 -

4. Confirm the message that technical system data can only be maintained in LMDB.

The technical system editor opens.

5. Make the changes.

6. Save your entries.

Result

The changes made in LMDB are synchronized into SMSY.

Delete Technical System

Use

The technical system editor can delete technical systems in the LMDB.

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

Directly deleting the description of a technical system in LMDB is only meaningful if you have made changes to this description in LMDB, manually, or migrated the description from SMSY into LMDB.

If you delete a technical system, you must ensure that it is deleted everywhere. The sequence and timing of the deletions is important, because of automatic synchronization, because it could reverse a deletion.

The deleted technical system is automatically reregistered if it is in a landscape, and has a system data supplier which is configured in SLD. If such systems are really to be deleted, the data supplier must be deactivated first.

Prerequisites





o To delete a technical system in LMDB, you need the role: SAP_SYSTEM_REPOSITORY_ALL

This role authorizes you to change systems in LMDB. Special LMDB authorization objects can restrict the authorization. Copy the role to your namespace and change the role.

- 32 -

Delete the Description of a Technical System with the Technical System Editor

Procedure

To delete a technical system, proceed in the following sequence:

1. If the system is known to SLD, delete it there first. It will be automatically registered again if it is in the landscape, and has a system data supplier which is configured in SLD. If the description of such a technical systems is really to be permanently deleted, deactivate the data supplier first.

2. When you have deleted in SLD, delete the system in LMDB next. Explicit deletion in LMDB is only necessary if you have changed the system manually, because it is then protected against propagation of the deletion.

3. The technical system deleted in LMDB is also automatically deleted in SMSY, but dependent product systems are not deleted, so you must also change or delete the product systems in SMSY, manually. For technical systems of type ABAP, this is obligatory. For all other system types it is only necessary if it is part of a product system.

Delete the description of a technical system in LMDB

1. Call the transaction SOLMAN_SETUP.


3. Choose the Technical Systems tab.

4. Choose a system, and System Operations -> Maintain System.

The technical system editor opens for the selected system, in edit mode.

5. Choose Delete Technical System.

Note:

If you delete a technical system in LMDB which was written there by SLD, it is only deleted until SLD next writes changed system data to LMDB, but the data in LMDB is then incomplete, so repair it with the report RLMDB_SYNC_TECHNICAL_SYSTEM. For detailed information about restoring a technical system, see „Troubleshooting“.

Delete the description of a technical system in SLD

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

Migrate SMSY Data to LMDB

Use

If data has already been created manually in SMSY, and there is no data supplier, migrate this data from SMSY to LMDB. You can migrate several technical systems at the same time.

Note: You should not create landscape data manually, you should collect it from data suppliers, so that it is regularly updated.


- 33 -

You can migrate the following types of technical systems:

ABAP application servers (ABAP)

Java application servers (JAVA)

Master Data Management servers (MDM)

Unspecific cluster systems (UNSPECIFIC)

Prerequisites and Functional Scope





o To migrate a technical system into LMDB, you need the role: SAP_SYSTEM_REPOSITORY_ALL

This role authorizes you to change systems in LMDB.

ABAP application servers (ABAP): Prerequisites: - The „Installation Number“ field must be maintained. - The „Message Server“ field must be maintained. - A database must be assigned to the system. - The „Server“ field of the assigned database must be maintained. Functional scope: Complete migration is supported for den ABAP application servers, i.e. all system entities, e.g. clients, instances, software components, and other attributes, are migrated to LMDB.

Note

Only migrate AS ABAP systems for which you cannot configure transaction RZ70 (firewall, etc.)

Java application servers (JAVA) Prerequisites: - A database must be assigned to the system. - The „Server“ field of the assigned database must be maintained. Functional scope: Only partial migration is supported for JAVA application servers, because of good coverage by data suppliers, i.e. only manually-maintained system entities, e.g. Other Attributes (landscape pattern, etc.) are migrated into LMDB.

Master Data Management Server (MDM) Prerequisites: - The correct product instances of a product system must be assigned to the technical system. Example: Technical system of type MDM with a technical instance in the server role „MDM Server“; Product system with product version „SAP MDM 5.5“ The technical system must be assigned to the product system product instance „Master Data Server“. Analogously: „Layout Server“,“Import Server“, „Syndication Server“. - The extended system IDs of technical and product systems must be the same. - The software components for the technical instances, e.g. software component „MDM_SERVER“ for the technical instance in the server role „MDM Server“, must be in the technical system. - The technical system has an instance in the server role „MDM Server“. - The „Instance Number“ and Server fields are maintained.

- 34 -

- The „Instance“ field is maintained and follows the SMSY naming convention. - A database must be assigned to the system. - The „Server“ field of the assigned database must be maintained. Functional scope: Migration of the entities instance, database, software component and other attributes are supported for the type Master Data Management server.

Note

Only migrate MDM systems for which you cannot configure the MDM Data Supplier (firewall, etc.)

Unspecific cluster system (UNSPECIFIC) Prerequisites: - A database must be assigned to the system. - The „Server“ field of the assigned database must be maintained. - One or more product instances of a product system must be assigned to the the technical system. - The extended system IDs of technical and product systems must be the same. - Software components must be maintained in the system Functional scope: Migration of the entities Instance, Database, Software Component and Other Attributes are supported for the type Unspecific Cluster system.

Note

Migrate only UNSPECIFIC systems for which you cannot configure the data supplier (no data supplier, firewall, etc.)

Migrating

Note

Only migrate system data for which there is no data supplier.

Only system data which is sufficient to create an LMDB entry is migrated. You can check your system data in SMSY with the Landscape Verification tool.

System data which could not be migrated, is post-processed in the technical system editor.

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

Perform the following steps to migrate the description of technical systems from SMSY to LMDB:


2. Choose System Preparation.

3. Choose Prepare Landscape Set Up LMDB.

4. Go to change mode.

5. Choose Migrate from SMSY to LMDB.

6. Select systems.

Tip:

Filter by the term Manual in the Source column, to find all manually-created systems in SMSY.

7. Choose Migrate Selected Rows.The migration runs in a background job. Each systems takes a few minutes, depending on the system type and size

8. Choose Display Log, to display the migration log containing success or error information.


- 35 -

Note

The log is only displayed when the background job has finished. You can choose Display Log until it appears.

Result

Manually-created technical systems have been migrated to LMDB.

- 36 -

Technical Scenario

Use

A technical scenario is a group of technical systems which work together, technically.

For example, you can monitor the availability and performance of the connections of all technical systems in a technical scenario, with "Connection Monitoring".

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

Information about technical scenarios is saved in the LMDB.

Prerequisites





o To create or change a technical scenario in LMDB, you need the role: SAP_SYSTEM_REPOSITORY_ALL

This role authorizes you to change systems in LMDB. Special LMDB authorization objects can restrict authorization. Copy the role to your namespace and change it.

Create and Change Technical Scenarios

There are two ways of configuring technical scenarios, described below.

Create a technical scenario

1. Call the transaction SOLMAN_SETUP (or the same function in the SAP Solution Manager: Configuration work center)

2. Under Associated Links Configuration, choose Technical Scenario Wizards

The system opens the Stand-Alone Technical Scenario Maintenance Application

3. Choose Create

4. Choose the technical scenario type, enter a name and a description, and choose Continue

5. Choose technical systems and Continue

6. Check your entries and Save

- 37 -

Change a technical scenario

1. Call the transaction SOLMAN_SETUP (or the same function in the SAP Solution Manager: Configuration work center)

2. Under Associated Links Configuration, choose Technical Scenario Wizards

The system opens the Stand-Alone Technical Scenario Maintenance Application

3. Choose a scenario and Edit

4. You can change technical scenario description, and choose Continue

5. Change the Stack Definition and choose Continue


Dual Stack Technical Scenario in Managed System Configuration

There is another way of creating or editing technical scenarios for dual stacks, in the Technical Scenarios tab in the Managed System Configuration, where there is a filter for technical scenarios of type DBL_STACK.

Dual stacks are usually identified automatically as such, and a technical scenario of type DBL_STACK is created for them. You can use these technical scenarios to configure the managed system for both stacks at the same time.

Create a technical scenario of type DBL_STACK

No technical scenario may be automatically created for a dual stack system if, for example, the technical systems have not been registered in SLD for some time, or the technical systems were registered in SLD in the „wrong“ sequence. The fact that it is a dual stack comes from the ABAP system. If the Java stack is registered in SLD after the ABAP stack, the dual stack is not recognized. In this case, register the ABAP stack in SLD again (or wait 24 hours). There should then be a technical scenario dual stack for this system.

You can also create a technical scenario of type DBL_STACK manually:

1. Call the transaction SOLMAN_SETUP


3. In the Technical Scenarios tab, choose Scenario Operations Create Scenario.

The system opens the Technical Scenario Maintenance Application, in create mode.

4. Enter a name and description for the scenario, and choose Continue

5. Specify the technical system ABAP and Java, and the database, and choose Continue.


- 38 -

Change a technical scenario of type DBL_STACK

To edit an existing technical system of type DBL_STACK, proceed as follows:



3. In the Technical Scenarios tab, choose a scenario.

4. Choose Scenario Operations Maintain Scenario

The system opens the Technical Scenario Maintenance Application, in change mode.

5. You can change the technical scenario description, and choose Continue

6. Change the Stack Definition and choose Continue


- 39 -

RFC Connections

Use

From SAP Solution Manager release 7.1, technical systems are saved in LMDB, so RFC connections between SAP Solution Manager and systems to be managed, can also be created or edited either from the technical system editor or from the Managed System Configuration.

Prerequisites





o To create or change RFC connections, you need the role: SAP_SM_BASIC_SETTINGS

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

Configuring RFC Connections

Configuration with LMDB




11. Choose a system and System Operations -> Maintain System.

The technical system editor opens in editing mode for the selected system.

12. Choose Destinations.

13. Choose RFC Maintenance.

You can configure the RFC connection in the window which opens, and save.

14. Close this new window.

15. Save your settings in the technical system editor.

- 40 -

Configuration during Managed System Configuration




4. Choose a system and System Config.

Configuration of Managed Systems opens for the selected system, in a new window.

5. Perform the required steps in the guided activity.

6. Configure the RFC connection under item 3.

7. Save the configurations.

- 41 -

LMDB Administration

Use

Note: LMDB administration is an expert function. Only make changes if you are in a position to evaluate the consequences.

This function displays CIM class and instance information, changes CIM instance attributes, deletes CIM instances, and deletes technical systems.

There are detailed search functions to select information.

You go to LMDB Administration via the work center (transaction SOLMAN_WORKCENTER) SAP Solution Manager Administration Infrastructure LMDB Administration

Functional Scope

There are various information tabs. Except for the CIM Class Statistics tab, you select objects to be displayed, in the search function. Various search criteria, with operators, are available for each search. You can add or delete search rows. You can save the search filter values for future searches.

Search for CIM Instances

This tab shows all CIM instances which satisfy your search criteria. You can display further details of a selected row, in a dialog box, with Details. In edit mode, you can change attributes in the Instance Attriibutes tab, and delete CIM instances or their technical systems, in this dialog box. Multiple selections are possible, so you can delete several elements in one step. When you delete a technical system, all CIM instances of the technical systems are deleted, as well as the selected CIM instance.

Changes only take effect after saving.

Instance Change Statistics

This tab displays changes to CIM instances. The top table shows changes by CIM classes and users, so a CIM class appears more than once if several users have changed their instances. If you select an entry, the bottom table shows its CIM instances with the times of the earliest and latest changes.

You can display details, and change attributes, as described in the Search for CIM Instances tab.

Get Change Log

This tab displays change log entries by class, user and time of change.

You can display details, and change attributes, as described in the Search for CIM Instances tab.

CIM Class Statistics

This tab displays statistical information about all CIM classes. You can update the information with Synchronize. If there are a lot of instances, synchronization can take some time, and time out. In this case, use the asynchronous variant.

- 42 -

Troubleshooting

Restore a Damaged Technical System Description

Information about a technical system in LMDB can be damaged for various reasons, for example:

The system was changed manually with the technical system editor.

Incorrect system information was migrated from the Solution Manager system landscape (SMSY).

A system description was put in LMDB by two different SLDs. If the data in the SLDs differs (e.g. one SLD with data supplier, and one with manual data import), LMDB can be inconsistent.

In the last case, remove the incorrect information from the SLD.

To make LMDB consistent:

1. Run the report RLMDB_SYNC_TECHNICAL_SYSTEM.

2. Enter the following parameters:

Source SLD: The SLD with the correct system description.

Target namespace: The LMDB target namespace (usually „active“).

System type: From the pull-down menu.

Extended System ID

Detail Trace: This option puts all synchronized CIM instance information in the output.

Delete before Synchronization: The entire technical system is deleted in LMDB before synchronizing from SLD.

Caution:

This option can lose manually-entered data, e.g. product assignments.

3. Run the report

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

- 43 -

Restore a Deleted Technical System

If a technical system has been deleted from the LMDB, its extended SID is no longer known in LMDB, so the report from RLMDB_SYNC_TECHNICAL_SYSTEM (Restore a Damaged Technical System) cannot recover the data from SLD. To reload all system data into LMDB again, perform the following steps:

1. Log on to the source SLD.

2. Go to CIM Instances (in an SLD with release NetWeaver 7.0: „Content Maintenance“).

3. Choose the CIM class for your system type.

System Type Name/Caption CIM Class

ABAP Application Server ABAP SAP_BCSystem

ATC Apache Tomcat Server SAP_ATCServer

BOBJ Business Objects Cluster SAP_BOCluster

DBSYSTEM Database System SAP_DatabaseSystem

DIAGNAGENT Diagnostics Agent SAP_DiagnosticsAgentInstance

IS_EM Introscope Standalone Enterprise Manager

SAP_ISEMServer

IS_MOM Introscope Enterprise Manager Cluster

SAP_ISMOMServer

JAVA Application Server Java SAP_J2EEEngineCluster

LIVE_CACHE liveCache SAP_LiveCache

MDM Master Data Management Server

SAP_MDMDataServer

MS_.NET .NET System SAP_DotNetSystemCluster

MSIISINST Microsoft Internet Information Services

SAP_MSIISInstance

THIRDPARTY Generic Application System

SAP_ApplicationSystem

TREX TREX System SAP_TrexSystem

UNSPAPP Unspecific Stand-alone System

SAP_UnspecificStandaloneApplicationSystem

UNSPECIFIC Unspecific Cluster System

SAP_UnspecificClusterSystem

WEBDISP SAP Web Dispatcher SAP_BCWebDispatcher

WEBSPHERE IBM WebSphere Cell SAP_IBMWSCell

4. Filter to find your system, e.g. by SID or host name.

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

1. Add an X to the description.

2. Save the change.

3. Reverse the change.

4. Save again.

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

7. Use the report RLMDB_SYNC_TECHNICAL_SYSTEM, as described under „Restore a Damaged Technical System“, to transfer all the system information to LMDB.

Performance Problems in Initial Complete Synchronization

The initial complete synchronization of SLD to LMDB can take several hours. As well as the missing or obsolete database statistics mentioned in „Initially Configure LMDB“, a too small shared memory area

- 44 -

can increase the runtime of the initial complete synchronization. For more information, see SAP Note 1555955, and the following section.

Administration of ABAP Shared Memory Areas for LMDB

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

The Shared Objects Monitor (transaction SHMM) gives an overview of the area instances in shared objects memory of the current application server. For more details about transaction SHMM, see: http://help.sap.com/saphelp_nw70/helpdata/de/5f/678d3f7057eb0ce10000000a114084/content.htm

The area relevant for LMDB is:

CL_LMDB_MODEL_SHM_AREA.

It has a size of ca. 12 MByte.

The size of all objects in shared memory is specified by the profile parameter

abap/shared_objects_size_MB

Transaction SHMM shows how much shared memory is currently in use, and how much free space remains, in the „Shared Objects Memory“ tab.

Use of Shared Memory:

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

If there is not enough memory for the shared memory segment, or the shared memory segment CL_LMDB_MODEL_SHM_AREA cannot be created, read the LMDB process class information from the database, with impaired performance.

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

http://help.sap.com/saphelp_nw70/helpdata/de/5f/678d3f7057eb0ce10000000a114084/content.htm

- 45 -

Glossary

Product:

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

Example: SAP ERP

Product version:

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

Example: SAP ERP 6.0

Product instance (previously main instance):

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

Example: SAP ECC Server

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

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

Product system (previously system):

Grouping of technical systems which belong to one or more products. (SV-SMG)

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

Software component:

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

Example: SAP_BASIS, SAP_HR

Logical component:

Logical set of systems with the same SAP product release, to be able to use this system landscape uniformly in various SAP Solution Manager use scenarios, i.e. in implementation, operational processing, and permanent optimization. The system-client combinations assigned to it usually have the same transport paths and different uses, such as development, quality assurance and production systems. This separates the abstract component level from the physical system level, allowing system-independent business process definition. (SV-SMG)

SLD/LMDB content synchronization:

SLD/LMDB Content Synchronization is the synchronization between SLD and LMDB, as described in „Synchronization between SLD and LMDB“.

- 46 -

SMSY Synchronization:

SMSY Synchronisation is the synchronization between LMDB and SMSY, as described in „Synchronization between LMDB and SMSY“.

SOLMAN_SETUP:

Transaction to configure SAP Solution Manager.

Documents

LMDB Setup Guide En