alm274-handling landscape data with sap solution manager 7.1

8/10/2019 ALM274-Handling Landscape Data with SAP Solution Manager 7.1

http://slidepdf.com/reader/full/alm274-handling-landscape-data-with-sap-solution-manager-71 1/21

Wolf Hengevoss / TIP Core LM Product Management

September, 2011

ALM274Handling Landscape Data with SAP Solution Ma



© 2011 SAP AG. All rights reserved.

Disclaimer

This presentation outlines our general product direction and should not be relied on

purchase decision. This presentation is not subject to your license agreement or anywith SAP. SAP has no obligation to pursue any course of business outlined in this pr

develop or release any functionality mentioned in this presentation. This presentatio

strategy and possible future developments are subject to change and may be chang

time for any reason without notice. This document is provided without a warranty of a

express or implied, including but not limited to, the implied warranties of merchantab

particular purpose, or non-infringement. SAP assumes no responsibility for errors or

document, except if such damages were caused by SAP intentionally or grossly neg




Agenda

Introduction to Landscape Data Management with SAP Solution Manager 7.1

Landscape Data Management becomes Centralized

Landscape Data and Client-Applications Using Them

Administrative Steps in Gathering Landscape Data – The Big Picture

Data Flow in the Tools and Systems Handling Landscape Items

LMDB – Data Exchange with the System Landscape Directory

Landscape Data Distribution

Product Systems – Generic Description

Technical Scenarios – Generic Description

Exercises

Landscape Data Maintenance for Updates/Upgrades and Monitoring

Summary



Introduction – Landscape Data Manage

with the SAP Solution Manager 7.1


http://slidepdf.com/reader/full/alm274-handling-landscape-data-with-sap-solution-manager-71 5/21© 2011 SAP AG. All rights reserved.

Landscape Data Management becomes CentralizedLandscape Management Database becomes available with SAP Solutio

Landscape Management Database (LMDB) – Role

Provides a centralized data store – a single source of truth in the SAP Solution Manager

Provides central access to handling landscape data in the SAP Solution Manager

– Technical Systems’ data from the SLD are stored in the LMDB

– Product Systems’ data from SMSY data shown in the LMDB

– Landscape verification is started from the LMDB

Landscape Management Database (LMDB) – How to Use IT

Integrate the LMDB with the SLD systems in your IT landscape

Connect your Technical Systems via the SLD to the LMDB

Connect system agents to the LMDB



Landscape Data and Client-Applications Using ThemTechnical Systems’ Data go to the SLD; System’s Data are Grouped into Landsc

Technical SystemsSystem Landscape Directory SAP Soluti

includ

Installation

Hardware NW-DI

Web

Dynpro

JavaNW-PI

…read / write

landscape data

write system data system data transfer

Moni-

toring

Applications in the non-productive and

productive area using landscape data

Applications in th

using landscape

A lot of applications need landscape data, so a lot of processes will suffer when quality lacks.

SLD Data Suppliers and Agents provide data required to operate, maintain, and monitor systems.

Data Supplier and Agent data are handled in the SAP Solution Manager’s LMDB, which is your single

land

DAJ

DAA



Administrative Steps in Gathering Landscape DataThe Big Picture

Technical Systems System Landscape Directory SAP Solution Man

including LM

• Set up SLD Data Supplier

• Set Up Agents Pure automated processes

• Maintain CIM/CR versions

• Develop data (e.g. for NW-PI, NW-DI)• Maintain PI product assignment

Some mechanical manual actions

• Configure SLD co

• Create / maintain• Configure Manage

System Operatio

Decisions on mai

• LMDB is the central tool of the process in gathering and managing landscape data

• Technical systems’ data is registered in the SLD and gathered in the LMDB

• LMDB offers access to system data required for maintenance and monitoring



Data Flow in Tools & Systems Hand

Landscape Items



SAP Solution Manager 7.1

LMDB – Data Exchange with the System Landscape DireUsing Full Automatic Synchronization

Technical System

Dual Stack C11Central

SLD

LMDB

System registration via

Data Supplier AS ABAP

System registration via

Data Supplier AS Java

Full Automatic

Content Synchronization

Model Version = 1.6.9.16 (or higher)

CR Content = 7.3

Technical Systems:

- C11 on pwdf2308 AS ABAP- C11 on pwdf2308 AS Java

Business Systems: B1, B2

Model Version = 1.6.9.16 (or higher)

CR Content = 7.3

Technical Systems:

- C11 on pwdf2308 AS ABAP- C11 on pwdf2308 AS Java

Business Systems: B1, B2

All systems report to a central SLD; additional information is entered manually or imported from other SLDs

All SLD data is synced into the LMDB via a central SLD based on the use of the same CIM Model.

LMDB provides data to diagnostics applications and to applications using SMSY

I m p o

r t o f

a d d i t i o n

a l d a t a

read / write

SLDSLD Client UI

Manual creation

of SLD data

=



SAP Solution

Manager 7.1

Landscape Data Distribution in a Typical LandscapeTopology with SLD and LMDB – SLD Topology in Non-Production/Prod

Landscape Area ProdLandscape Area non-Product ion

Systems (non-prod.)NWDI Oth

SLD

(design-time) centra

(runti

If no other SLD is available in

the landscape,

in SAP Solution Manager 7.1

the local SLD can be activatedin addition to LMDB

as a target for data suppliers.LMDB

PI (Dev.) PI (prod.)




landscape 1

Systems

Managing

Systems SAMa

LMDB

landscape 2 landscape 1

Central

SLD 2

Systems

Managing

Systems SAP SolutionManager 7.1

LMDB

Central

SLD 1

Central

SLD 1 PI transports

Bridge Forwardin

Landscape Data Distribution – LMDB Synced with More Topology in Detail – Schemas Following and Violating the Unique-Path




Product Systems – Generic DescriptionSAP Product with AS ABAP & AS Java Parts on two Technical System

JAP

Product Instances:

ABP

Product Instances:

A3

A2

J1

J2 A1

Product System

“ABP”

Maintenance needs to take care of all

Technical Systems used to install

one ProductProduct Systems group Technical

Systems and are the basis for system

updates and upgrades:

Product Systems gather all Technical

Systems used to install one Product A

Product System ABP uses two Technical

Systems, ABP & JAP

Product System JVP contains ProductInstances of Product J and Product A

Landscape Patterns show the reuse

of Technical Systems, to be taken into

account during an update

You need Technical System’s data

to define Product Systems. Hub




Host xyz123

Product Systems – Generic DescriptionSAP Product with AS ABAP & AS Java Parts on two Technical System

TDI(AS Java)

TDI(AS ABAP)

Technical Scenario

type “Dual Stack”

Monitoring needs to take care of all

Technical Systems of a solution intoaccount

Technical Scenarios group Technical

Systems and are the basis for monitoring:

Technical Scenarios of type Dual Stack group

all Technical Systems used of a Dual Stack

system

Technical Scenarios of type Monitoring group

all Technical Systems used to run a certain

business process

You need Technical System’s

(including Agents’) data to define and

use Techn ical Scenarios

Technical

type “Mon

Host xyz123

ERP



Exercise

Handling Landscape Data from the Technical System to the Product S




Landscape Data Maintenance for Updates/Upgrades andTechnical System SLD LMDB / SMSY / Landscape Verification

SLD <local>

Hardware

MOpzUpdate /UpgradeSAP Service

Marketplace

Product Sys

TDI TDI

local TDI (AS ABAP)

TDI

TDI

Monitor

Monitor

Apps

local TDI (AS Java)

check

SLD CIM/CR

local SLD

1aconfigure SLD

Data Supplier

(local NWA)

2aconfigure SLD

Data Supplier

(local RZ70 )

2bcheck

full automatic sync

(LMDB Setup)

1b maint

for mai

(LMD

3bconfigure SLD

bridge forwarding

local SLD

1c

SLD <M36>

check

system data

(LMDB / SMSY)

3a

Provide Data Gather & Send Data Maintain &

SMSY

TDI

TDITechn.

Scen.




Further Information

SAP Public Web:

SAP Developer Network (SDN):www.sdn.sap.com/irj/sdn/nw-sld Landscape Descriptions

Related SAP Education and Certification Opportunities

http://www.sap.com/education/ Search for SAP Solution Manager

Related Workshops/Lectures at SAP TechEd 2011

ALM202, Central Landscape Data Management with SAP Solution Manager 7.1

ALM270, Efficient Monitoring for SAP NetWeaver BW and SAP BusinessObject

ALM272, Customizing and Enhancement of System Monitoring and Reporting,

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

http://www.sdn.sap.com/irj/sdn/nw-sld?rid=/webcontent/uuid/d06d6033-0b86-2e10-7a9b-d749085be62f

http://www.sap.com/education/

http://www.sap.com/education/

http://www.sdn.sap.com/irj/sdn/nw-sld?rid=/webcontent/uuid/d06d6033-0b86-2e10-7a9b-d749085be62f






Summary




SummaryLandscape Data Management becomes Centralized with SAP Solution

Landscape Management Database unifies landscape data management inside and

Solution Manager (SMSY and SLD)

• Landscape Management Database is the single source for Technical Systems’ data in the S

Manager 7.1

• Landscape Management Database UI integrates access to all landscape data in one tool.

Configure your LMDB to integrate data from Technical Systems and SLD syste

up-to-date landscape description for business people and administrators.



FeedbackPlease complete your session evaluation.

Be courteous — deposit your trash,

and do not take the handouts for the following session.




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 t rademarks 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 and Java are registered trademarks of Oracle and/or its affiliates.

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 registe

Wide Web Consortium, Massachusetts Institute of Techno

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesignStreamWork, and other SAP products and services ment

respective logos are trademarks or registered trademarks

countries.

Business Objects and the Business Objects logo, Busines

Crystal Decisions, Web Intelligence, Xcelsius, and other B

services mentioned herein as well as their respective logo

trademarks of Business Objects Software Ltd. Business O

SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQ

products and services mentioned herein as well as their r

registered trademarks of Sybase, Inc. Sybase is an SAP c

All other product and service names mentioned are the tr

companies. Data contained in this document serves infor

product specifications may vary.

The information in this document is proprietary to SAP. N

reproduced, copied, or transmitted in any form or for any

written permission of SAP AG.

alm274-handling landscape data with sap solution manager 7.1

Documents