SI ZI NG GUI DE Si zi ngSAP x RPM,Ver si on 4.0 Rel eased f orSAP Cust omer s and Par t ner s Doc umentVer si on 1.0, J anuar y 2008 Copyright 2008 SAP AG. 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. 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, and Informix are trademarks or registered trademarks of IBM Corporation 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. J ava is a registered trademark of Sun Microsystems, Inc. J avaScript 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. Disclaimer Some components of this product are based on J ava. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressively prohibited, as is any decompilation of these components. SAP Library document classification: CUSTOMERS & PARTNERS Documentation in the SAP Service Marketplace You can find this documentation at the following address: http://service.sap.com/sizing SAP AGReleased for SAP Customers and Partners2TABLE OF CONTENTS 1INTRODUCTION......................................................................................................................................... 2 1.1FUNCTIONS OF SAP XRPM 4.0................................................................................................................ 2 1.2ARCHITECTURE OF SAP XRPM 4.0.......................................................................................................... 3 1.3FACTORS THAT INFLUENCE THE PERFORMANCE....................................................................................... 3 2SIZING FUNDAMENTALS AND TERMINOLOGY .............................................................................. 4 3INITIAL SIZING FOR SAP XRPM 4.0 ..................................................................................................... 5 3.1ASSUMPTIONS.......................................................................................................................................... 5 3.2SIZING GUIDELINE.................................................................................................................................... 6 4MISCELLANEOUS...................................................................................................................................... 8 5COMMENTS AND FEEDBACK................................................................................................................ 8 SAP AG Sizing SAP xRPM 4.5 - SAP Customers and Partners1 1Introduction Successful organizations are those that can maximize business value, achieve balance, and align their overall portfolio with strategic objectives. The SAP xApp Resource and Portfolio Management (SAP xRPM) composite application helps you deliver on this, and helps you deliver on it more effectively. SAP xRPM addresses your organization's need for strategic and operational portfolio management. An enterprise-level solution for the management of a range of portfolios including product innovation management (PIM), professional service portfolios, and enterprise IT SAP xRPM enables you to better control and innovate projects, processes, products, and services across their life cycles. Powered by the SAP NetWeaver platform, SAP xRPM "snaps-on" to existing heterogeneous IT landscapes and leverages data from disparate systems (including human resource, financial, project management, and desktop systems) enabling new, cross-functional business processes and providing ready insight into operations. For example: Prebuilt integration with SAP and non-SAP systems provides out-of-the-box transparency into project-cost actuals, forecasts, baselines, and other KPIs across your entire portfolio. Deep integration with your HR system, including visibility into the organizational structure to support both line and pool management, enables resource allocation and strategic capacity planning based on up-to-date information on skills, availability, and approval workflows. Flexible dashboards and sophisticated analytics drawn from disparate systems enable continuous monitoring of your portfolio's performance. SAP xRPM aligns activities, resources, and budgets with business priorities so that you can maximize the value of your portfolio and leverage your existing investments in IT systems, skills, and resources. Together with other SAP solutions tightly integrated by the SAP NetWeaver platform, SAP xRPM can support your new product development and introduction processes. 1.1Functions of SAP xRPM 4.0 SAP xRPM 4.0 enables the following key business processes: Portfolio Management: Capabilities that help you make the right go/kill decisions and prioritize your use of resources. Dashboards that allow you to easily monitor and control your overall portfolio and pipeline, as well as key performance indicators. Product/Project Management: Project, cost, and resource management capabilities improve the management of the entire product development and introduction process. Functional Execution: A broad range of capabilities support functional-level tasks such as initial ideas capture, product development, strategic sourcing, supply chain planning, prototyping, production ramp-up, and market launch. SAP AG Sizing SAP xRPM 4.5 - SAP Customers and Partners2 1.2Architecture of SAP xRPM 4.0 SAP xRPM 4.0 is based on the Netweaver 7.0 technology stack. This includes the Web Application Server 7.0, Enterprise Portal 7.0 and Business Warehouse 7.0. The following software components comprise SAP xRPM 4.0: ABAP CPRXRPM Java CPRXRPM_UI Portal Business Package BPPPM_DC The following slide highlights the technical landscape of SAP xRPM 4.0 1.3Factors that influence the performance The component which has the most important influence on performance and memory consumption within SAP xRPM is the item dashboard. When sizing the SAP xRPM system, consideration of the requirements for the item dashboard should ensure an overall appropriate size for other components in SAP xRPM as well. Performance and memory consumption of the item dashboard depend on the following criteria: Number of items processed in the item dashboard Length of additional customer fields added to the item attribute structure Number of authorizations maintained in the portfolio and items These criteria have to be included in the sizing of an SAP xRPM system in addition to the standard sizing criteria (like number of users, think time ). SAP AG Sizing SAP xRPM 4.5 - SAP Customers and Partners3 2Sizing Fundamentals and Terminology SAP provides general sizing information on the SAP Service Marketplace. For the purpose of this guide, we assume that you are familiar with sizing fundamentals. For more information, see http://service.sap.com/sizing Sizing General Sizing Procedures. This section explains the most important sizing terms, which are used extensively in this document. Sizing Sizing means determining the hardware requirements of an SAP application, such as the network bandwidth, physical memory, CPU processing power, and I/O capacity. The size of the hardware and database is influenced by both business aspects and technological aspects. This means that the number of users using the various application components and the data load they put on the server must be taken into account. Benchmarking Sizing information can be determined using SAP Standard Application Benchmarks and scalability tests (see http://www.sap.com/benchmark). Released for technology partners, benchmarks provide basic sizing recommendations to customers by placing a substantial load upon a system during the testing of new hardware, system software components, and relational database management systems (RDBMS). All performance data relevant to the system, user, and business applications are monitored during a benchmark run and can be used to compare platforms. SAPSThe SAP Application Performance Standard (SAPS) is a hardware-independent unit that describes the performance of a system configuration in the SAP environment. It is derived from the Sales and Distribution (SD) Benchmark, where 100 SAPS is defined as the computing power to handle 2,000 fully business processed order line items per hour. (For more information about SAPS, see http://www.sap.com/benchmark SAPS). Initial Sizing Initial sizing refers to the sizing approach that provides statements about platform-independent requirements of the hardware resources necessary for representative, standard delivery SAP applications. The initial sizing guidelines assume optimal system parameter settings, standard business scenarios, and so on. Expert Sizing This term refers to a sizing exercise where customer-specific data is being analyzed and used to put more detail on the sizing result. The main objective is to determine the resource consumption of customized content and applications (not SAP standard delivery) by comprehensive measurements. For more information, see http://service.sap.com/sizingSizing GuidelinesGeneral Sizing ProceduresExpert Sizing. Configuration and System Landscaping Hardware resource and optimal system configuration greatly depend on the requirements of the customer-specific project. This includes the implementation of distribution, security, and high availability solutions by different approaches using various third-party tools. In the case of high availability through redundant resources, for example, the final resource requirements must be adjusted accordingly. There are some "best practices" which may be valid for a specific combination of operating system and database. To provide guidance, SAP created the NetWeaver configuration guides (http://service.sap.com/instguidesSAP NetWeaver). SAP AG Sizing SAP xRPM 4.5 - SAP Customers and Partners4 3Initial Sizing for SAP xRPM 4.0 3.1Assumptions The memory consumption and performance of the item dashboard depends on the Number of items in the portfolio in general Number of items processed in the dashboard Length of additional customer fields added to the item attribute structure Number of authorizations maintained in the portfolio and items A portfolio contains a certain number of portfolio items that are processed in the item dashboard. The higher the number of portfolio items processed in the dashboard, the higher the CPU times and memory consumptions are. To ensure that the runtime for presenting the item dashboard to the end user stays below a certain time period regardless of the number of items in the portfolio, a configuration setting is available which limits the number of items processed in the item dashboard. This configuration can be done in Customizing, by choosing SAP xApp Resource and Portfolio Management (SAP xRPM)Global CustomizingGlobal SettingsOverride Default Global Settings. To configure the item number limit, add the following entry in this table:0007 General Default Values0004 Maximum No of Items to be displayed in the Dashboard In theSettings Value field for this entry, you can specify the maximum number of items to be shown in dashboards.Example: 0007 General Default Values 0004 Maximum No of Items to be Displayed in the Dashboard 100 With this setting, a portfolio can have 1000 or 2000 portfolio items; the runtime of the dashboard for processing 100 items according to this configuration will stay about the same. Information, that the number of processed items was limited SAP AG Sizing SAP xRPM 4.5 - SAP Customers and Partners5 Number of items processed by the item dashboard Technical background: A portfolio contains a certain number of items. Function module /RPM/ITEM_GETLIST selects all items in a given portfolio and provides the item list to the Java Web Dynpro Component Item Dashboard. This item list is restricted to the Number of items to be displayed in dashboards. The filtering of the items, which will be provided to the dashboard, is based on the Changed On Date attribute of the items in that portfolio (the filter takes the most recently updated items). 3.2Sizing guideline 3.2.1Assumptions This sizing guide is based on an out of the box utilization of SAP xRPM. The following factors may influence the sizing requirements and thus may lead to higher CPU and memory requirements. Customer enhancements to the item retrieval processing Additional customer fields on the item attribute structure (/RPM/TS_ITEM_D_API) Extensive utilization of authorization assignments (high number of ACL entries) Sizing focuses on CPU and memory. Disk requirements are negligible. 3.2.2Calculation Sizing is driven by the number of dashboard displays and the size of the dashboard itself. Therefore the sizing consists of several steps: 1.Determine the average number of dashboard items processed per dashboard 2.Determine the peak number of dashboard displays per hour 3.Calculate the CPU requirements in SAPS 4.Calculate the memory requirements in MB Step 1: Determine the average number of dashboard items processed per dashboard This information will be delivered by the application team. For example, the average number of dashboard items will be 100 (this is a medium size).Note that the performance-influencing factor is the number of dashboard items processed per dashboard, not the number of items displayed or visible on the dashboard UI. For example, a dashboard may have processed 100 items, but only 20 are displayed on the list. Step 2: Determine the peak number of dashboard displays per hour The item dashboard displays, which are the most critical processes within SAP xRPM, determine the size of an xRPM system. The sizing guideline is based on the peak number of displays per hour on the peak day of the year. How many concurrent users (product managers and portfolio managers) will work on xRPM on the busiest day of the year? On average, how many dashboards displays will the users perform on that day? How many work hours does this busiest day have? Alternatively, you can simplify the calculation by determining the peak number of concurrent users per hour on the peak day and the average number of dashboards per user per hour.For example, just before closing the financial planning, 500 users will work from 9am-5pm. Each user will display 40 dashboards on average on that day. The calculation is: 500*40/8 = 2500 dashboard displays per hour. SAP AG Sizing SAP xRPM 4.5 - SAP Customers and Partners6 Step 3: Calculate the CPU requirements in SAPS The calculation is very simple:SAPS = DISPLAYS * (CAT_PORTAL_SAPS + CAT_XRPM_SAPS) DISPLAY is the number of dashboard displays calculated in step 2 CAT_PORTAL_SAPS is the number of Portal SAPS per dashboard category size. You can obtain this value from the table below. For example the Portal SAPS calculation factor for a medium-sized dashboard is 0.16. CAT_ CAT_XRPM_SAPS is the number of xRPM SAPS per dashboard category size. You can obtain this value from the table below. For example the Portal SAPS calculation factor for a medium-sized dashboard is 0.04. CategoryUp to # of items per dashboardPortal SAPSxRPM Core SAPS Small 500.150.03 Medium1000.160.04 Large3000.180.05 Extra Large300+Contact hardware vendor or SAP Example 2500 * (0.16 + 0.04) = 500 SAPS Note For standalone servers the minimum requirements are 2000 SAPS, 8 GB memory Do not abuse the formula, meaning that you should not scale the number of dashboard items higher than 300 Step 3: Calculate the memory requirements in MB xRPM Core: 12 MB net requirements per user, independent of the number of items in the dashboard. Or, you may assume 4-6 GB per 1000 SAPS, if you run xRPM Core as standalone, and depending on the number of concurrent users. Portal: Per 1000 SAPS, take 6 GB of memory See also SAP Note 723909 (in particular section 2) for configuration of the server nodes in the Portal. SAP AG Sizing SAP xRPM 4.5 - SAP Customers and Partners7 4Miscellaneous For additional information on SAP xRPM 4.0, please refer to the following sources: Installation Guide: http://service.sap.com/instguides SAP xApps SAP xApp Resource and Portfolio Management SAP xRPM 4.0 Online Help: http://help.sap.com/content/documentation/xapps/index.htm SAP xApp Resource and Portfolio Management Training and Education: http://service.sap.com/okp SAP xRPM 4.0 5Comments and Feedback Both are very welcome; please send them to: Yvonne Waibel, PLM Solution Managementyvonne.waibel@sap.com SAP AG Sizing SAP xRPM 4.5 - SAP Customers and Partners8