Wolf Hengevoss, TIP CORE Lifecycle Management

September 7, 2012
ALM264
Centralized Landscape Data Handling and Usage with
SAP Solution Manager 7.1
2012 SAP AG. All rights reserved. 2
Disclaimer
This presentation outlines our general product direction and should not be relied on in making a
purchase decision. This presentation is not subject to your license agreement or any other agreement
with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or to
develop or release any functionality mentioned in this presentation. This presentation and SAP's
strategy and possible future developments are subject to change and may be changed by SAP at any
time for any reason without notice. 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. SAP assumes no responsibility for errors or omissions in this
document, except if such damages were caused by SAP intentionally or grossly negligent.
2012 SAP AG. All rights reserved. 3
Agenda
Introduction
Entities in system landscape management
Technical scenarios
Product systems and landscape patterns
Big picture of landscape data handling the exercises setup
Exercises Overview
Landscape data handling the exercises steps
Log On information
Summary and further information
Details
Introduction
Landscape data handling example: the exercises setup and landscape data entities
2012 SAP AG. All rights reserved. 5
Planning/Projects:
Logical Landscape
Operation:
Technical Landscape
Entities in system landscape management
Software catalog, logical landscape, and technical landscape
Content
Software Catalog
Solution Map / Business
Process Repository
Logical landscape
planning
Solutions/Business
Processes
Technical landscape
operation
Technical System
Technical Scenario
Product System

Logical components connect logical
and technical landscapes
Logical Component
Solution Business Process
Monitoring
Technical Scenario
Maintenance
Product System
Content delivered
by SAP
SLD
LMDB
SAP
Software Catalog
(CR Content)
Product Instance
Software
Component
Product Version
Support
Package
Solution Map
Business Process
Repository
Technical System
Installed Support
Package
Installed Software
Component (Version)
Installed Product
Instance
2012 SAP AG. All rights reserved. 6
Host xyz123
Technical scenarios
Examples: Technical Scenarios types dual-stack and monitoring
TDI
(AS Java)
TDI
(AS ABAP)
technical scenario
type Dual-Stack
Monitoring and setup needs to take care
of all technical systems of a scenario
Technical scenarios group technical
systems :
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

Note: You need technical systems (including
agents data) to define and use technical
scenarios for monitoring purposes.
technical scenario
type Monitoring
Host xyz123
ERP
Host xyz234
BO1
automatically
created
manually
created
2012 SAP AG. All rights reserved. 7
Product systems and landscape patterns
Minimizing the effort customer system landscapes
Minimum impact on landscape
Often, more than one SAP application is
deployed on a technical system (see figure)
This causes interdependencies of technical systems during
maintenance activities described in landscape patterns
Need to avoid unnecessary updates of connected systems
Landscape Pattern
MOpz interprets landscape pattern and calculates
software updates for connected systems (hubs) with
minimum system impact
Update of hubs only if necessary
Sidecar systems always updated together
New: Product systems with SAP Solution Manager 7.1 SP5
can contain more than one technical systems of type ABAP
(but these cannot work as a hub)

NetWeaver
software
update

SID
=
EPP
EP-C
XSS 605
AS JAVA 7.0
ERP
Content SRM
Content
SAP NetWeaver Portal
SAP ERP
SID = ERP
ECC 6.0 EHP5
AS ABAP 7.02
SAP SRM
SID = SRP
SRM 7.0
AS ABAP 7.01
Product System EPP
Product
System
ERP
Product
System
SRP
Hub
2012 SAP AG. All rights reserved. 8
Big picture of landscape data handling the exercises setup
Technical system SLD LMDB techn. scenario/product system/logical comp.
Hardware
Update /Upgrade
SAP Service
Marketplace
TDI TD1
Monitoring
send data gather, provide, and distribute data maintain and use landscape data
TDI TD1
Techn.
Scenario
Product
System Editor
Monitor
Appl.
ChaRM
MOpz
TDI
SLD <local>
TDI TD1
TDI (AS J ava)
TDI (AS ABAP)
LMDB
ChaRM
technical landscape data
project data
SMSY
technical system data
other
other
TS
DS
Installation of
SAP Product
Version
<other>
forwarding
data
supplier
data supplier
SLD
<wdflbmt0777>
Dual-Stack
SAP Solution Manager
7.1 SP5 <M36 on wdflbmt0777>
full
automatic
synchronization
P.S
M10
P.S
TDI
M10I TDI
logical
comp. /
solution
PS
TDI
Mg. Sys.
Setup
Exercises
Systems, Users, Passwords, and Exercises Overview
2012 SAP AG. All rights reserved. 10
Exercises overview: centralized landscape data handling and usage
Technical system & landscape data in SLD, LMDB, for maintenance and monitoring
Part 1 Gather and Send Data 4
1a) Check Your Local SLDs State Regarding CIM/CR Content (Local SLD) 4
1b) Check Configuration of the SLD Bridge Forwarding (Local SLD) 5
1c) Check Full Automatic Synchronization of LMDB and SLD (Central System M36) 6
Part 2 Provide Data 9
2a) Check Configuration of and Trigger the SLD Data Supplier AS Java of Your Dual-Stack 9
2b) Check Configuration of and Trigger the SLD Data Supplier AS ABAP of Your Dual-Stack 10
Part 3 Maintaining & Using Technical System and Landscape Data 13
3a) Check Technical System Data in the LMDB & Change the Extension of the Extended SID 13
3b) Create Data for Monitoring & Maintenance the Central Entry Managed System Setup 18
3b1) Select a Technical Scenario to Define the Scope of Your Managed System Configuration 18
3b2) Assign Software to Technical Systems Setting of the Diagnostics Flag and Product System Creation 19
3b3) Product System Verification 23
3c) Use Your Product System in the LMDB to Create a Maintenance Transaction 29
3d) Create and Remove a Solution and Logical Component Based on the Data in the LMDB 31
3e) Delete Your Product System in the LMDB 36
2012 SAP AG. All rights reserved. 11
Exercises log on information
System access and passwords
You need the following systems, users and passwords:

Local system TDI and SLD:
User = ALM264_ADMIN
Password = see exercise description

Central SAP Solution Manager system M36
User = ALM264adm_xx (where xx is your group number)
Password = see exercise description
Summary and further information

2012 SAP AG. All rights reserved. 13
Summary
Achievements with SAP Solution Manager 7.1 SP5
Unification & centralization
SLD and LMDB share the same data model and act as coupled applications
All technical landscape data is created in and provided by the LMDB
Project-related data in logical components and solutions is based on LMDB and handled in SMSY
Simplification
LMDB provides a product system editor with integrated verification and access to the MOpz
Technical scenarios define the scope of managed system setup bringing your system into ALM
2012 SAP AG. All rights reserved. 14
Further Information
SAP Education and Certification Opportunities
www.sap.com/education
Watch SAP TechEd Online
www.sapteched.com/online
SAP Public Web
scn.sap.com Landscape Descriptions (http://scn.sap.com/docs/DOC-8935)
http://service.sap.com/solutionmanager and http://service.sap.com/mopz
www.sap.com
Feedback
Please complete your session evaluation for ALM264.
Thanks for attending this SAP TechEd session.