ITM260
How to Handle Landscape Data to Maintain and
Manage Your System Landscape
LAB Preview
Wolf Hengevoss LM PM
September 2013
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.
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.
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
2
Agenda
Introduction
 Landscape data handling – the exercises landscape
 Landscape entities
News in SAP Solution Manager LMDB
Exercises landscape – technical & product systems, product instances
Exercises
Summary
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
3
Introduction
Why to invest in landscape data?
Landscape data is the basis for all processes in application lifecycle management.
Checks of landscape data are increasing
Landscape entities are…
 Product systems
 Logical components
 Technical scenarios
Also, diagnostic relevance flag needs to be set
Landscape data is based on technical system information and created in the SAP Solution Manager.
During the exercises, you will create all these entities for 3 technical systems being closely connected
to each other to ensure correct handling during maintenance.
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
5
Landscape data handling – the exercises landscape
LAB Preview
Technical system  SLD  LMDB  techn. scenario/product system/logical comp.
Monitoring
Installation of
SAP Product
Version
SAP Service
Marketplace
Update /Upgrade
ACC
ACC
NW-PI
NW-PI
NW-DI
NW-DI
MOpz
MOpz
Web
Web
Dynpro
Dynpro
Java
Java
ACC
EC9 (AS ABAP)
NW-PI
Web
Dynpro
Java
CC9
CC9
EC9
EC9
CC9
forwarding
SLD <DEV/QA>
CC9
EC9
EC9
CC9
PC9
Logical
Solution /
Logical
Components
Log. Comp.
Components
…CC9…
…CC9…
…EC9…
…EC9…
….PC9…
…PC9…
Sys-Mon
PC9
PC9
PC9
Agent
CC9
project data
PC9 (AS Java)
landscape data
data
technical landscape
data supplier
Agent
full automatic sync.
SLD <central>
CC9 (AS ABAP)
send data
(SMSY)
SMSY
(SMSY)
Product
Techn.
Product
Techn.
System
Editor
Scenario
System Editor Scenario
EC9
Agent
ChaRM
ChaRM
ChaRM
LMDB
LMDB
LMDB
NW-DI
Hardware
Monitor
Appl.
technical system data
gather, provide, and distribute data
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
SAP
SAP
Solution
Manager
SAPSolution
SolutionManager
Manager
7.1
7.1
SPS10
7.1SPS10
SPS05
maintain and use landscape data
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.
6
Product systems – maintenance of product versions
SAP Product with 1 AS ABAP / AS ABAP & AS Java Parts on two Technical Systems
Product systems describe the
installation of one product version:
Product systems ensure
 Product versions on a technical system are
described correctly
 If a Product version is installed on more than 1
technical systems all these are addressed
during updates and upgrades automatically
Product System
“AB3”
Product System
“ER9”
Product Version Y
Product Version X
Product Instances
Product Y:
Product Instances,
Product Y:
Product instances
 group software components (SCs), which need
to be handled to maintain a product
 All SCs on a technical system need to be
covered by selected product instances
Product Instances
(Product X):
ABAP PI1
ABAP PI2
Java PI7
Java PI8
ABAP PI5
Java PI9
ABAP PI6
Product systems can have different
landscape patterns:
 1 technical system (see PS AB3)
 2 technical systems in a sidecar (see PS ER9)
 More than 2 technical systems in a hub
(shown later)
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
AB3
PC9
sidecar
CC9
7
Technical scenarios
LAB Preview
Technical scenarios and defined scope
Monitoring and setup
needs to take care of all
technical systems of a
scenario
technical scenario
type “System Monitoring”
EC9
PC9
CC9
Technical scenarios
group technical systems
defining the scope of
monitoring
 Note: You need technical
system’s (including agents’
data) to define and use
technical scenarios for
monitoring purposes.
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
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.
8
News in SAP Solution Manager LMDB
Product System Editor
LAB Preview
Improved search for proposal of missing product instances
In case product instances are not completely registered, a new search for proposals in LMDB
Product System Editor displays (only) product instances that are fitting available software
components:
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
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.
10
Logical components
LAB Preview
Find it in Managed System Configuration
Logical components can link the abstract software feature
definition to concrete technical implementations – they…
 are used for example in Change Request Management
 … work on product instances connected to product systems
 … can be assigned directly in the Managed System Configuration
or on the LMDB Start Screen.
 Logical components are stored in a SMSY compatible way
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
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.
11
LMDB reporting and dashboards – transaction LMDB
LAB Preview
Information on the system landscape for better landscape management
Dashboard showing
the number of landscape
entities in the LMDB:
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
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.
12
Business partner
LAB Preview
Use data from transaction "BP" to enrich landscape data
For improved management of technical systems, business partners can be assigned in the LMDB:
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
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.
13
Exercise: Prepare a managed system




Product system and maintenance transaction
Diagnostics flag
Logical component
Technical scenario
Exercises – settings in Managed System Configuration
Product system, diagnostics flag, and logical component
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
LAB Preview
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.
15
Exercises – creating a technical scenario
LAB Preview
Find it in the Technical System Editor
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
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.
16
Exercise landscape – technical & product systems, product instances
SAP NetWeaver Portal system used as a hub by SAP ERP & SAP CRM
Product System
“PC9“
Product Version:
SAP EHP2 f. SAP NW 7.0
Product System
“EC9”
Product System
“CC9”
Product Versions:
SAP EHP5 f. ERP 6.0
SAP ERP 6.0
SAP EHP2 f. SAP NW 7.0
SAP Portfolio Mgmt…. 6.0
Portal Content Common
Portal Cont. Self Srv.
SAP XSS (Self Services)
Product Instances:
SAP ECC Server
Central Applications
Oil & Gas
Oil & Gas w. Utils.
Appl. Server ABAP
Product Versions:
Product Instances:
EP Core
SAP CRM 7.0
SAP EHP1 f. SAP NW 7.0
Appl. Server Java
Portal Content
Prod. Instances:
SAP NW - AS Java
SAP NW - EP Core
Appl. Server ABAP
SAP XECO
CRM AS ABAP
SAP XSS (Self Services)
CRM Portal Content
Portal Content
CRM App. Srv. Java
Hub
EC9
ERP backend
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
PC9
Portal frontend
CC9
CRM backend
17
Exercises – log on information
You need the following systems, users and passwords …
Laptop access
• User = student
• Password / Domain= given
by instructor / Fair
Central SAP Solution Manager system M83 (per group – expls: ITM260-01)
• User = ITM260-## (where “##” is your two digits group number)
• Password = given
by instructor
Systems to use per group (expls: E01/P01/C01; EC0/PC0/CC0 )
– E00 in the exercises document works like EC9 and all other systems:
• Technical system E## = SAP ERP backend
• Technical system P## = Enterprise Portal frontend
• Technical system C## = SAP CRM backend
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
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.
18
LAB Preview
Summary
LMDB has been significantly improved with SAP Solution Manager 7.1
Unification of landscape data handling by SMSY replacement
Simplified handling of landscape data and putting things together in Managed System Configuration
 Additional proposals for missing product instances
 Diagnostics relevant flag assignment
 Update of product system data after an update or upgrade
Enhanced use of landscape data:
 Assignment of business partners to systems
 Reporting features including dashboards
Use these new functions to ensure up-to-date landscape data and landscape
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
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.
19
Further Information
SAP Public Web
scn.sap.com  Landscape Descriptions (http://scn.sap.com/docs/DOC-8935)
www.sap.com
SAP Education and Certification Opportunities
www.sap.com/education
Watch SAP TechEd Online
www.sapteched.com/online
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
20
SAP TechEd Virtual Hands-on Workshops and SAP TechEd Online
Continue your SAP TechEd education after the event!
SAP TechEd Virtual Hands-on Workshops
SAP TechEd Online
 Access hands-on workshops post-event
 Available January – March 2014
 Complementary with your SAP TechEd registration
 Access replays of keynotes, Demo Jam, SAP TechEd
LIVE interviews, select lecture sessions, and more!
 View content only available online
http://saptechedhandson.sap.com/
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
http://sapteched.com/online
21
Feedback
Please complete your session evaluation for ITM260.
Thanks for attending this SAP TechEd session.
© 2013 SAP AG or an SAP affiliate company. 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.
National product specifications may vary.
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.
SAP 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.
Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
23