User Guide Landscape Planner

Transcription

1 User Guide Landscape Planner

2 Table of Contents 1. Getting Started About Landscape Planner Technical Advantages of Landscape Planner Who Should Read This Guide A Quick Tour Accessing Landscape Planner Runtime Prerequisites Exploring System Landscape Systems Available on Your Landscape... 6 Procedure SAP Solution Manager System Details Modeling Status of Systems Identifying System Dependencies Updating a System Installing a New System Validating and Releasing a Landscape Plan Simulating a Fiori Solution Reference Links Support

3 1. Getting Started 1.1. About Landscape Planner SAP provides the flexibility to implement various components of SAP Business Suite, SAP BusinessObjects and SAP NetWeaver within a landscape. In such a complex landscape, there exist an increasing number of dependencies between each component. Planning any changes to such a landscape is difficult without accurate information on system dependencies. Landscape Planner is a browser based tool that helps IT administrators efficiently plan and implement changes to a landscape (that is: install a new system, update or upgrade). It helps identify the dependencies between systems in a landscape, and understand the impact of system changes on the landscape Technical Advantages of Landscape Planner Enables planning landscape changes using accurate landscape data that it obtains from the customer profile. Thus, it leads to faster decision making. For example, the tool provides accurate information on all update or upgrade options that are available for a particular system. Thereby, it helps reduce the effort that you need to perform an update or upgrade. Helps identify and evaluate changes to the landscape before implementing it. Thereby, reduces the risk of a change. For example, the tool provides accurate information on system dependencies. This information is critical to efficiently perform an update or upgrade activity. Provides information on inconsistent landscape data (systems that are wrongly modeled in SAP Solution Manager) Who Should Read This Guide This guide is intended for IT administrators or SAP consultants who are responsible for planning and implementing updates, upgrades, and new system installations. 3

4 1.4. A Quick Tour The figure below shows a typical process involved in the Application Lifecycle Management (ALM), and the role of Landscape Planner. In ALM, Landscape Planner helps you plan a system update or upgrade, and to generate a landscape plan. You can use this landscape plan in Maintenance Optimizer (MOPz) to generate a stack.xml file. Figure 1: Application Lifecycle Management The image above depicts the Application Lifecycle Management cycle with the various processes involved. Each stage is briefly described below, starting at SLD: Register the technical systems in System Landscape Data (SLD), which then synchronizes its data into the Landscape Management Database (LMDB). In the LMDB, you create product systems. LMDB uploads both technical and product system information to the Customer Profile data available in the SAP Support Portal. Landscape Planner uses this data, and allows you to plan any changes to your landscape. Landscape plan that you generate using Landscape Planner describes these changes. You can now import the landscape plan into Maintenance Optimizer (MOPz) as a basis of a new maintenance transaction. MOPz creates a stack.xml file that is consumed by the Software Update Manager (SUM). If you are looking for more detailed information, this graphic is also available on the home page of Landscape Planner, and serves as an interactive way to find documentation of each step. 4

5 2. Accessing Landscape Planner Landscape Planner is a hosted application on SAP Service Marketplace (SMP). To access Landscape Planner: 1. Go to 2. Login with your SAP credentials (S user) 2.1. Runtime Prerequisites 1. You have installed Google Chrome or Internet Explorer (version 9 and above) browser on your system. 2. Your SAP Solution Manager system is of release 7.0 SP 23 or above. 3. You have implemented the SAP Notes and on the SAP Solution Manager system. This note identifies the Solution Manager that sends the system landscape data to Landscape Planner. 4. You have implemented the SAP Note This note allows the Maintenance Optimizer (MOPz) to consume the landscape plan generated from Landscape Planner. If your SAP Solution Manager system is of release 7.1 SP 06 or above, you need not implement the above notes. You must see Import Landscape Plan button on the home screen of maintenance optimizer (MOPz) after you have successfully implemented this note. If you cannot see Import Landscape Plan button even after implementing the note, check if you have assigned a business partner role to this user: To assign a business partner role: 1) In the SAP Solution Manager system, go to the transaction /nbp_gen. 2) Add your SAP Solution Manager system. 3) Chose the user by double clicking on the User. 4) In the menu panel, choose Edit Create business partner 5. You must ensure that Landscape Fetch job is running on your SAP Solution Manager system. This is necessary to synchronize your system information with the SAP Portal. For more information, see: 5/content.htm 5

6 3. Exploring System Landscape Landscape Planner User Guide 3.1. Systems Available on Your Landscape You can use the Landscape Planner tool to identify all systems that are available on your landscape. Procedure 1. Access Landscape Planner. Go to and login with your SAP credentials (S user). 2. Choose Systems tab. The tool displays all the systems that are available on your landscape. In addition, it also displays the name of the technical system and the system type (ABAP, JAVA, Dual Stack, HANA DB, and so on.) Tip: Click on the search icon product version., to search for a particular system based on the product name or 3. Choose a particular system. The Landscape Planner opens the Plan Area of that system. On this screen the Landscape Planner tool provides information on the system ID, product instances, product version, the system type (ABAP, JAVA, and Dual Stack), the software components installed on the system, and so on. Example: For technical system B15 - the system type is ABAP; the product is SAP SRM; the SAP Solution Manager system name is S17; the SAP Solution Manager release is The current version of Landscape Planner does not support viewing more than 500 systems in the row view. 6

7 3.2. SAP Solution Manager System Details For each system on your landscape, the Landscape Planner tool provides information about the SAP Solution Manager systems that replicates data of that particular system into the customer profile. This information includes the name of the SAP Solution Manager system and its release. Example: The technical system B15 is replicated from SAP Solution Manager system S17 In addition, the Landscape Planner tool also provides information on the database host, and the database type of a particular system. You need to personalize your settings to view these details (SAP Solution Manager system, database host, database type, and so on.) 1. Choose Personalize on home page of Landscape Planner. 2. Select the attributes or filters that you like to see. 3. Choose Save If you are viewing the SAP systems that are available on your landscape in Table View, you can only sort columns that are available as default attributes or filters values in personalize screen Modeling Status of Systems The Landscape Planner tool provides you with the information on modeling status for any particular system that you have installed in your landscape. You can use Landscape Planner to identify all systems that you have incorrectly modeled in the SAP Solution Manager system. 1. Access Landscape Planner. Go to and login with your SAP credentials (S user). 2. Choose Systems tab. 3. In the Modeling Status filter, choose Error. The tool displays only those systems that are wrongly modeled in the SAP Solution Manager system. These systems are incorrectly modeled in SAP Solution Manager system for various reasons, and as a result an error is displayed. For more information on the error, choose the Error icon displayed on the system. Example: The technical system B05 is incorrectly modeled in the SAP Solution Manager system S16 7

8 3.4. Identifying System Dependencies For any system that is available on your landscape, you can use Landscape Planner tool to identify all its dependent systems provided that you have correctly modeled these dependencies in LMDB. Refer to the below table for some examples on system dependencies. Procedure 1. Access Landscape Planner. Go to and login with your SAP credentials (S user) 2. Choose the Systems tab. 4. Choose a system. The Landscape Planner opens the Plan Area of that system. 3. Choose Dependencies Dependency Meaning The system that is directly dependent to your chosen system. For example: ERP backend (HCM) system and a Portal system are directly dependent to each other. Product Maintenance : Direct Product Maintenance : ALL If you choose Direct Dependency for a Java system which is a hub connected to more than one other backend systems, the plan area displays only one system at a time. Choose Direct Dependency again and select any of the back end systems to view direct dependencies for each of it. All systems those are directly dependent to your chosen system. For example: ERP systems connected to a Portal system, which in turn is connected to a CRM backend system. 8

9 Example: ABAP technical system PRO has a direct dependency with JAVA technical system EP3. Product instances EHP6 for SAP ERP 6.0 and SAP NETWEAVER 7.0 are common to both these technical systems. Tip: Use the Navigation Panel available at bottom of the page to move horizontally across the screen. 9

10 4. Updating a System The Landscape Planner tool allows you to efficiently perform an update or upgrade activity on any system installed on your landscape. The tool provides all the update or upgrade options that are available for the system that you choose. By executing the below procedure, you can use Landscape Planner tool to simulate an update or upgrade activity on any of the systems, and evaluate the impact of this update or upgrade activity on other dependent systems. Procedure 1. Access Landscape Planner Go to and login with your SAP credentials (S user). 2. Choose Systems tab 3. From the systems that are displayed, choose a system that you want to update or upgrade. Tip: You can use the search icon product version. to search for a system based on the product name or 4. Update the system In the Plan Area, choose Update displayed on top of the system. 5. In the pop-up, choose from the update or upgrade options that are available for this system, For example: You can choose the target software level, product, product version, stack level, technical usages, and so on, for the system that you want to update. 6. Choose the Finish icon 7. Choose the Save icon to save this activity as a landscape plan. 8. Provide a name to the landscape plan and choose OK. The Update icon displayed across a component (product instances, software components or technical system), indicates that the component needs to be updated due to your desired landscape changes. The Installed icon, displayed across a component, indicates that the component is to be newly installed due to your desired landscape changes. 10

11 You have now simulated an update or upgrade activity for a particular system. Now, you can evaluate the impact of this update or upgrade activity on the system landscape. 9. Choose Transactions from the menu panel. 10. Choose the landscape plan that you have created. This landscape plan opens in the Plan Area. Tip: Use the filters Created by or Modified by to easily identify your landscape plan. 11. Choose Dependencies. Dependency Product Maintenance : Direct Product Maintenance : ALL Meaning The system that is directly dependent to your chosen system. For example: ERP backend (HCM) system and a Portal system are directly dependent to each other. If you choose Direct Dependency for a Java system which is a hub connected to more than one other backend systems, the plan area displays only one system at a time. Choose Direct Dependency again and select any of the back end systems to view direct dependencies for each of it. The systems that are directly and indirectly connected to the chosen system are displayed. For Example: For a Java system which is a hub connected to more than one backend systems, the plan area displays all systems (direct and indirect). Tip: Use the Navigation Panel available at the bottom of the page to move horizontally across the screen. 11

12 5. Installing a New System By executing the below procedure, you can use Landscape Planner to simulate and evaluate the impact of installing a new system on your landscape. 1. The current release of Landscape Planner only supports installing a new single ABAP system. 2. Please refer to the simplified Unified Consumption Experience for new system installation: Procedure 1. Access Landscape Planner. Go to and login with your SAP credentials. 2. Click the icon to simulate an installation in your landscape. 3. In the popup, choose from the installation options that are available for this new system. For example: You can choose the target software level, product, product version, stack level, technical usages, and so on. 4. Choose the Finish icon 5. Choose the Save icon to save this activity as a landscape plan. 6. Provide a name to the landscape plan and choose OK. The icon displayed across a component (product instances, software components or technical system), indicates that the component is updated due to installing a new system on the landscape. The icon, displayed across a component, indicates that the component is newly installed due to installing a new system. You have now simulated a new installation on your landscape. For evaluating the impact of this system on the landscape, 7. Choose Transactions from the menu bar. 8. Choose the landscape plan that you created for the new system. The landscape plan opens in the Plan Area. Tip: Use the filters Created by or Modified by to easily identify your landscape plan. 9. Choose Dependencies to view all systems impacted due to this new installation. Dependency Meaning 12

13 The system that is directly dependent to your chosen system. Product Maintenance : Direct Product Maintenance : ALL For example: ERP backend (HCM) system and a Portal system are directly dependent to each other. All systems those are directly dependent to your chosen system. For example: ERP systems connected to a Portal system, which in turn is connected to a CRM backend system. Tip: Use the Navigation Panel available at the bottom of the page to move horizontally across the screen. You cannot use a landscape plan for new installations in maintenance optimizer to generate a stack.xml file. 13

14 6. Validating and Releasing a Landscape Plan You can validate and release the landscape changes, and use this information in maintenance optimizer (MOPz) to generate a stack.html file for your planned changes. Procedure 1. Click on the Actions icon and choose Finalize Landscape Plan. If the validation is successful, the message The validation check is performed successfully is displayed at the bottom of the screen. Else, if validation fails, check the log by clicking the log icon You can withdraw this landscape plan. Click on the Actions icon in the menu bar and choose the option Withdraw landscape plan, and redo your planning with other update options. 2. Once validated, you can download the landscape plan in PDF format. To do so, click the Actions icon and choose Download Landscape Plan. This PDF document provides you with the information on both, the current status of your landscape, and also the overview of changes that you have planned for your landscape. 3. Set landscape plan for approval. After the system validates your landscape plan, if you wish to have your landscape plan to be reviewed and approved by a business expert, click the Actions icon in the menu bar and choose Set landscape Plan for approval. The status of the landscape plan is set to Pending approval. 4. Release the landscape plan for implementation. To release a landscape plan, and to generate a stack.xml file (in Maintenance Optimizer) for these landscape changes, click the Actions icon in the menu bar and choose Release Landscape Plan. The tool now loads the landscape plan, with status Released, to the Change Management work center of SAP Solution Manager. The release option is only available if the current status of the landscape plan is Pending approval. 14

15 Figure 5 Component view On choosing the desir ed deployment pattern, sel ect the s ystem for i mplementing the s oftwar e c ompon Choos e fr om the list choose the relevant Fiori s olutions to be i mpl emented i n your l ands cape Choos e fr om the list choose the relevant Fiori s olutions to be i mpl emented i n your l ands cape Landscape Planner User Guide 7. Simulating a Fiori Solution You can plan and simulate one or more Fiori solutions on Landscape Planner. The process flow of simulating a process flow is shown below: Procedure Figure 2: Process flow- Simulating a Fiori solution 1. Click the installation options on the top left corner, and choose Select to simulate a Fiori solution Result: The list of Fiori solutions available is displayed 2. From the list, choose the relevant Fiori solutions or a Fiori solution stack to be implemented in your landscape. Result: Other Fiori Solutions which can run on the same system for the above selected solution are listed 3. Select the solutions that need to be implemented and click the button Plan and Simulate. 4. Two views are provided for supporting the planning activity: Component view: Provides details on the software component requirements. Deployment view: Provides different deployment patterns available for implementation in the landscape. 5. On choosing the desired deployment pattern, select the system for implementing the software components. Target system can be existing systems in landscape or choose new system for the implementation 6. Once you have selected a target system, you can visualize the impact by clicking the button Click to visualize impact 7. Click the save button to save the changes for later use. 8. You can follow the remaining steps as described in the section Validating and Releasing a Landscape Plan 15

16 8. Reference Links About Landscape Planner: About UCE (SAP SCN): Unified Consumption Experience user guide: About SUM: 9. Support In case of issues, open a message on the CSN component BC-UPG-LP Alternatively, for any other queries or concerns, mail us at SAP_Landscape_Planner@sap.com by mentioning the customer number in the mail body. 16

17 Copyright 2014 SAP SE. 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 SE. 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, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iseries, pseries, xseries, zseries, z/os, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/os, POWER, POWER5, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation. 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. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mysap, mysap.com, xapps, xapp, SAP NetWeaver, 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 in several other countries all over the world. 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. These materials are provided as is 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 shall not be liable for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. SAP does not warrant the accuracy or completeness of the information, text, graphics, links or other items contained within these materials. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third party web pages nor provide any warranty whatsoever relating to third party web pages. SAP NetWeaver How-to Guides are intended to simplify the product implementation. While specific product features and procedures typically are explained in a practical business context, it is not implied that those features and procedures are the only approach in solving a specific business problem using SAP NetWeaver. Should you wish to receive additional information, clarification or support, please refer to SAP Consulting. Any software coding and/or code lines / strings ( Code ) included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, except if such damages were caused by SAP intentionally or grossly negligent. Disclaimer Some components of this product are based on Java. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressively prohibited, as is any decompilation of these components. Any Java Source Code delivered with this product is only to be used by SAP s Support Services and may not be modified or altered in any way. 17