Plan and Prepare Changes to Best Use, Maintain, and Enhance Your IT Landscape
Your IT landscape consists of all servers running our business software. To keep your business running and continuously improve your processes, both servers and software are changing constantly. To manage the required changes, people in different roles need to work closely together - on a very high level, this is shown in figure 1. While the names of the three roles will differ slightly from company to company, you should recognize the overall process:
Figure 1a: Main roles in landscape management: Line of Business, IT Architect, and Basis Administrator working together to identify required changes, plan and evaluate them based on the current landscape description and prepare the implementation of new or additional software product versions.
The following figure shows tools involved in the planning process handling landscape data:
Figure 1b: Main applications and their connections in landscape management.
Best Practice Guide to Planning Landscape Changes
We are working on this process in a group dedicated to Release Management and Innovation Adoption. The recommendation for the complete process is described in a Planning Landscape Changes - a Best Practice Guide(SMP login required). This guide will be updated reflecting progress in process described and also exist in different version. Therefore, this information is is available via an overview page:
Planning Landscape Changes - a Best Practice Guide.
Hint: Since this guide is intended to be a living document being updated over time, you may want to follow this link it offers links to the guide in different versions:
- SAP Solution Manager 7.2 and the Maintenance Planner
- SAP Solution Manager 7.1 and the Maintenance Planner
- SAP Solution Manager 7.1 and the Maintenance Optimizer
Figure 2 is taken from that guide and shows the roles in more detail:
Figure 2: Tools and activities involved in the best practice process of innovation adoption to update or upgrade installations of SAP Business Suite products taken from the best practices guide - in its new version describing the process using using the Maintenance Planner..
Information on Related Tools and Processes
SAP Solution Manager
As shown in figure 2, SAP Solution Manager is a key component in landscape change management:
- It is the provider of landscape data consumed by the Maintenance Planner (which is provided as a service of SAP Solution Manager)
- It offers tools to estimate the test effort caused by planned changes and help you to run the systems in your landscape
These 2 topics are described in the following as Landscape Descriptions and Maintenance Planning.
On this SCN page you'll get information and links to SAP's product model, System Landscape Directory, and SAP Solution Manager LMDB.
Data for landscape descriptions are increasingly used in the SAP Support Portal; to learn about the topology recommendations, read...
- Topology of SLD, LMDB, and Customer Profile – How to Get Reliable Landscape Data in SAP Support Portal as a Basis for Planning
- Uploading, Accessing, and Trouble-Shooting System Data in the Customer Profile Used for Planning Changes in Your IT Landscape
- New: Required SAP NW Version of the Source SLD for LMDB in SAP Solution Manager 7.2 & Options to Get there.
Landscape Verification is an important step in having a valid landscape descripton.
If you compare the planning process in SAP Solution Manager 7.1 and 7.2 you see functions have moved the cloud,
offering SAP Solution Manager services you can easily consume.
Simulate and Plan Changes in Your Systems or Tracks based on a Graphical UI
The Maintenance Planner is a new tool now available combing functions required to plan system updates, upgrades, new installations and system conversion to SAP S/4HANA and SAP BW/4HNA. The Maintenance Planner offers maintenance dependencies as a successor of product systems - learn about scenarios of using one or the other:
- Product Systems and Maintenance Planner in SAP Solution Manager 7.1
- Landscape Entities & Maintenance Planner in SAP Solution Manager 7.2
Maintenance Planner is constantly developed further with new functions and integration of related steps. For more details. see the blogs on release highlights of the Maintenance Planner. Also see the wiki Maintenance Tools for more guides and information
Maintenance Optimizer SUNSET: Maintenance Optimizer had its sunset at Jan 9, 2017; in SAP Solution Manager 7.1. SEA (Scope and Effort Analyzer) will continue to be supported.
Guidance about Useful Landscape Layouts
Landscape recommendations provide a clear guidance about useful landscape layouts for most of typical use cases. The recommendations outline supported deployment options for SAP products, listing pros and cons of each option and simplify the consumption of the material by using a common methodology containing a simple rating of each option.This information helps customers designing their system landscapes according to the recommendations by SAP. It is available in the Landscape Recommendations.
Applying Landscape Changes
Landscape data are used to manage your landscape. You do not create them just for the tools managing them but you need to see them in the big picture: System and landscape data are emerging when you install software and are needed to define changes in the landscape, which are applied then by software logistic tools To find out more about tools like Software Provisioning Manager (SWPM) and Software Update Manager (SUM) go to http://scn.sap.com/community/it-management/alm/software-logistics.
If you are using the system copy function of the software provisioning manager, you need to take care of the changed landscape data in the System Landscape Directory (SLD). This blog describes it: How to Deal with Landscape Data Created during System Copy
Dual-Stack Systems can be split into separate technical systems (with the exception of mandatory dual-stacks such as versions of SAP NetWeaver PI and SAP Solution Manager). After such a split, you need to take care – or do some house-keeping – in the System Landscape Directory (SLD) and also think of the landscape description in SAP Solution Manager LMDB: Dual-Stack Split – How to Ensure Correct Technical System Data in SLD and LMDB after the Split@ the SCN.
SAP Landscape Management (SAP LaMa) Helps You Automate Repetitive Tasks and Gain Unprecedented Visibility and Control over SAP and non-SAP Systems
Note: After a name change the product SAP Landscape Management might be mixed with the topic of this page but is part of the process described here.
With this product, you can automate repetitive tasks and gain unprecedented visibility and control over SAP and non-SAP systems in both traditional and virtual infrastructures. In particular, it provides an end-to-end system copy with fully automated post-copy steps. As a result, you can boost efficiency and agility and lower operating costs.
From the perspective of landscape data management, you can apply all ALM processes to technical systems controlled by LVM.
If you are using virtual host names assigned to the technical systems all processes in LVM including relocate can be used. If you're using physical host names, you can still manage your technical systems and apply ALM processes based on landscape data but relocation is not possible.
For more information, see SAP Landscape Management.
Manage your System and Network Assets
Maximize the value of your IT landscape – and gain transparency across your asset base. Our IT infrastructure management software integrates seamlessly with SAP Solution Manager to help you quickly discover all network assets, continuously monitor asset data, and drive an integrated infrastructure and application lifecycle process.
Planning Landscape Changes (Best Practice Guides): Overview of guide versions
- Planning Landscape Changes
- Special Cases in Update and Upgrade