Sizing Guide

SAP Solution Manager 7.0 as of SP15

Released for SAP Customers and Partners

April 2008

Released for SAP Customers and Partners

Sizing SAP Solution Manager - SAP Customers and Partners

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. 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.

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. 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/instguides

SAP AG

Released for SAP Customers and Partners

Sizing SAP Solution Manager - SAP Customers and Partners

CONTENTS
CONTENTS.................................................................................................................................................... 1 HISTORY OF CHANGES ................................................................................................................................... 2 1 INTRODUCTION........................................................................................................................................ 4 SCENARIO OVERVIEW OF SAP SOLUTION MANAGER ...................................................................................... 4 ARCHITECTURE OF SAP SOLUTION MANAGER ................................................................................................ 5 FACTORS THAT INFLUENCE PERFORMANCE ..................................................................................................... 6 2 INITIAL SIZING FOR SAP SOLUTION MANAGER.............................................................................. 9 ASSUMPTIONS ............................................................................................................................................... 9 GENERAL INFORMATION ................................................................................................................................ 9 LARGE SIZED SYSTEM LANDSCAPE .............................................................................................................. 10 MEDIUM SIZED SYSTEM LANDSCAPE ............................................................................................................ 10 SMALL SIZED SYSTEM LANDSCAPE .............................................................................................................. 11 3 SIZING RECOMMENDATIONS FOR ADDITIONAL COMPONENTS .............................................. 12 APPENDIX ................................................................................................................................................... 13

SAP AG

April 2008

Sizing SAP Solution Manager - SAP Customers and Partners

History of Changes
This Sizing Guide is updated with each new Support Package Stack in SAP Service Marketplace at service.sap.com/instguides -> SAP Componens -> SAP Solution Manager -> <current release>. Make sure you have the latest version of the Sizing Guide. The following table provides an overview of the most important changes that were made in the latest versions: Date of Update 30.04.2007 Topic Sizing recommendations for SEP package (TDMS; RBE); Additional information on factors that influence performance SP15 06.02.2008 Reference table on documentation on Sizing for additional components (e,g. BI etc.) Sizing for System Monitoring if functionality of Alert Inbox is used Sizing Recommendations for Diagnostics are changed and can be obtained from the according Guides for Diagnostics (see: table for additional components) Section on how-to read detailling sizing tables Sizing recommendations for SEP package deleted 28.04.2008 Name change: SAP Solution Manager 4.0 becomes SAP Solution Manager 7.0

Documentation types in the software life cycle:

SAP AG

April 2008

Sizing SAP Solution Manager - SAP Customers and Partners

For a detailled overview on which documentation is relevant for each individual phase, see SAP Note 1088980. We strongly recommend that you use the documents available here. The guides are regularly updated.

SAP AG

April 2008

Sizing SAP Solution Manager - SAP Customers and Partners

1 Introduction
One of the issues that you need to take care of at an early stage and throughout the product life cycle is the system resources you require. The sizing of your hardware will be a precondition for its good performance. Sizing means that you determine the hardware requirements for your SAP Solution Manager system. This is again depending on both your business aspects (How you want to use Solution Manager) and technological aspects (How many users will use the system and how high is the data load for the system). Your system needs to able to handle peak loads and to display a predictable behaviour. For sizing and performance the database tier and application tier (services e.g.: dialog, update, batch) are the most important ones which relates to CPU, main memory and disk space. Regarding Solution Manager this depends largely on the use of the various scenarios you use. The following paragraph gives a short overview of them. For detailled information on these scenarios, see Service Marketplace -> SAP Components -> Master Guide SAP Solution Manager <current release>.

Scenario Overview of SAP Solution Manager

The Implementation and Upgrade scenarios support the implementation of customer projects and the definition of template projects and upgrade projects. In template projects, you define one or more templates containing scenarios, documents and configuration for re-use in other systems, e.g. for a global roll-out of centrally defined implementation settings. These Implementation and Upgrade scenarios include roadmaps, an editor for creating and maintaining business blueprints, access to the Implementation Guides (IMG), and tools for testing, monitoring and distributing Customizing. The Solution Monitoring scenario provides support for functionalities such as Service-Level Reporting, EarlyWatch Alert, Business Process Monitoring, System Monitoring, Central System Administration, System Landscape Reporting, as well as user-defined alerts. The Service Desk of the SAP Solution Manager offers a complete infrastructure for organizing and operating a solution-wide support organization at your site. The Service Desk promotes effective user support in your SAP solution landscape every step of the way - from the end-users to your internal support organization and when necessary to SAP. Change Request Management in SAP Solution Manager is aligned to the processes in the IT Infrastructure Library (ITIL), the de facto standard for service management. As defined in ITIL, the objective of Change Management is to carry out changes economically and in a timely manner with minimal risk. Change Request Management includes processes for managing change requests, project management, and change logistics. The operations Collaboration section of the SAP Solution Manager is the point of access to SAP support services, including remote services, on-site services, self services, and Best Practice documents. Based on your solution configuration, recommendations for these services are triggered dynamically. The reports resulting from each service are available and are archived in the operations section. The reports are useful documentation stored in the SAP Solution Manager and serve as reference information for the efficient future operation of your solution landscape. A key requirement for efficient and safe support of IT solutions is the ability to perform root cause analysis with speed and efficiency. Diagnostics in SAP Solution Manager provides standardized tools for the support of customer solutions, including third-party components. The tools enable a systematic and targeted cross-component localization of the root cause of IT problems. The centralized approach avoids that many experts have to search for possible root causes on all components involved, in most cases without success. With the possibilities of Diagnostics, your support organization can both save costs and accelerate the time required for problem resolution.

SAP AG

April 2008

Sizing SAP Solution Manager - SAP Customers and Partners

Architecture of SAP Solution Manager

SAP Solution Manager (Software Component ST) is based on NW ABAP and Java 7.0 and CRM 5.0 (e.g. scenarios: Service Desk and Change Management). It runs in a separate central system, to which all other systems of your system landscape are connected. Systems that are administered using the SAP Solution Manager are referred to as "satellite systems". Sizing of Solution Manager does not include and is not dependent on the sizing of any of the satellite system types, but on the number of satellite system types connected to the Solution Manager. Follow the Solution Manager ABAP sizing for the ABAP stack requirements. Hardware requirements, such as network bandwidth, physical memory, CPU power, and I/O capacity, are influenced by both business and technological requirements. You need to take into account the number of users using the various application components and the load placed on the network. The Solution Manager Diagnostics J2EE stack sizing for the J2EE stack requirements are not described in this document. Refer to hardware requirements in the according Guides for E2E scenarios (Diagnostics) on the Service Marketplace: service.sap.com/diagnostics For a more detailled description on architecture: Service Marketplace -> SAP Components ->Security Guide SAP Solution Manager <current release>.

SAP AG

April 2008

Sizing SAP Solution Manager - SAP Customers and Partners

Factors that Influence Performance

The most important concepts to consider are the following: Concept Scenario Note... Which scenarios are used and are to be used? You can use all scenarios or just one, for instance Solution Monitoring. You may start with Maintenance Optimizer and Solution Monitoring, and integrate step by step most of the other scenarios. Connected servers are especially relevant for Solution Monitoring sizing. How are your solutions designed? To "customize" your solutions you need to consider which scenarios you are going to use. For instance, if you are going to use Business Process Monitoring, your business process will probably connect via various satellite systems, this should be your main consideration. For instance, you would like to activate Business Process Monitoring for a business process which runs via a SAP CRM system and a SAP ERP system. Both systems (both in system role: production) should be in the solution. If you are are not using Business Process Monitoring you can tailor the systems per solutions according to other demands.

Servers of satellite systems connected Solutions in productive use

SAP AG

April 2008

Sizing SAP Solution Manager - SAP Customers and Partners

The following table shows which factors per scenario are important and need to be considered: Scenario Solution Monitoring (if graphical display for solutions is used) 1 Performance influencing factors alerts of System Monitoring and Business Process Monitoring per connected server that are to be processed2 Note. We recommend not setting up more than 2000 alerts per solution landscape. If you want to monitor more alerts you should create further solution landscapes. We recommend max. 46 - 60 systems per solution4.

---------------------------------------------data download for and processing of EarlyWatch Alert/Service Level Reports per system3

-------------------------------------------------After the EarlyWatch Alert data download, the system processes the data, sequentially. This action is typically performed as a background job at night or at other times with less load. We strongly recommend automatically deleting or archiving older reports 5. We recommend about 100 server per solution. Larger landscapes with with more than 100 systems should have separate solutions.

Solution Monitoring (if System Monitoring Alert Inbox functionality of the System Monitoring Work Center is used) Solution Monitoring (BI- Analyses)

number of connected servers per solution

if the client for BI-Analyses is to be the same as the client for productive Solution Manager number of users and documents processed number of users

In this case you need to consider additional sizing information for Business Intelligence (BI), see Reference table on documentation on Sizing for additional components

Implementation and/or Upgrade Service Desk and/or Change Request Management Collaboration

documents processed

Number of Service Reports downloaded

1 2 3 4

Graphical display is not supported by the Work Center approach. See Appendix for example See Appendix for example

Average assumption: 40 alerts per connected server/2000 alerts per solution, independent of the number of servers (for more information on alerts in the Setup System Monitoirng session, see appendix). In the System Monitoring session you should define for one Solution not more than 2000 alerts, disregarding the number of systems.
Time scale 2000 alerts per solution: Initial call of System Monitoring graphic: 75s; Refresh of System Monitoring graphic: 30s
5

SAP Note 546685 (Archiving in the Solution Manager (Operation); SAP Note 638785 (SAP Solution Manager - reduce data volumes)

SAP AG

April 2008

Sizing SAP Solution Manager - SAP Customers and Partners

Scenario Diagnostics

Performance influencing factors garbage collection runs

Note. The Diagnostics Server runs in 2 different modes: Dialog Mode: Times of dialog user interaction, e.g. performance analysis of a monitored satellite system. Background Mode: Time window for automated tasks, e.g. gathering configuration data of a monitored system. Normally, these tasks are scheduled in times of low dialog usage (nightly). There is no technical dependency between the two modes - dialog and background activities can be mixed. For Diagnostics sizing see: Reference table on documentation on Sizing for additional components

SAP AG

April 2008

Sizing SAP Solution Manager - SAP Customers and Partners

2 Initial Sizing for SAP Solution Manager

Assumptions
General Information
Assumptions per scenario (excluding Diagnostics): Scenario Implementation and/or Upgrade Service Desk and/or Change Request Management Collaboration Assumption based on SD user SD-USER in the Quick Sizer Tool based on CRM user SRV-USER in the Quick Sizer Tool based on CRM user SRV-USER in the Quick Sizer Tool based on number of alerts per server (solution design) both scenarios are primarily based on CRM functionality scenario is primarily based on CRM functionality not included in the Quick Sizer Tool Note.

Solution Monitoring

All assumption examples should be regarded as general assumptions regarding numbers of servers, etc.. In practice, you may have a greater or smaller number of servers, etc. We recommend that you base your sizing estimate on the assumptions for the landscape with the next highest number of servers. For example, if your server number is 60, then you should base your estimate on the sizing recommendations for Large sized system landscapes. In general, all assumptions in this paper are based on Unicode. For more information on specific dependencies, see: http://service.sap.com/unicode -> Unicode at SAP -> Unicode Media Library -> Unicode Information on Specific Topics -> Unicode: Hardware Requirements and Customer Experience.

SAP AG

April 2008

Sizing SAP Solution Manager - SAP Customers and Partners

Large Sized System Landscape

Assuming you use all scenarios, we recommend6: SAPS: 3300 Memory: 8 - 16 GB (depending on the scenarios in use) Disk: 600 GB + 11.5 GB growth per month due to EarlyWatch Alert Reports and project documentation This recommendation specifies hardware requirements for the use of all scenarios in a large sized system landscape example (all ABAP systems -> without Diagnostics7) with the following example proposition: Number of alerts per server: 40 Number of servers: 75 Number of systems: 95 (= number of EarlyWatch Alert Reports per week) Number of users for Implementation or Change Request Management: 120 (30 with 10 dialog steps/min and 90 with 10 dialog steps/hour) Number of documents processed during Implementation: 25,000 Number of users for Collaboration: 5 (2 with 10 dialog steps/min and 3 with 10 dialog steps/hour)

Medium Sized System Landscape

Assuming you use all scenarios, we recommend8: SAPS: 1650 Memory: 4 - 8 GB (depending on the scenarios in use) Disk: 400 GB + 4.75 GB growth per month due to EarlyWatch Alert Reports and project documentation This recommendation specifies hardware requirements for the use of all scenarios in a medium sized system landscape example (all ABAP systems -> without Diagnostics9) with the following proposition: Number of alerts per server: 40 Number of servers: 35 Number of systems: 45 (= number of EarlyWatch Alert Reports per week) Number of users for Implementation or Change Request Management: 40 (10 with 2 dialog steps/min and 30 with 10 dialog steps/hour) Number of documents processed during Implementation: 10,000 Number of users for Collaboration: 3 (1 with 2 dialog steps/min and 2 with 10 dialog steps/hour)

For detailled hardware recommendations on the individual scenarios, see: Appendix (Table: Large sized system landscape)

For additional Diagnostics Sizing, see the according documents for installation and configuration service.sap.com/diagnostics 8 For detailled hardware recommendations on the individual scenarios, see: Appendix (Table: Medium sized system landscape)
9

For additional Diagnostics Sizing, see the according documents for installation and configuration service.sap.com/diagnostics

SAP AG

April 2008

10

Sizing SAP Solution Manager - SAP Customers and Partners

Small Sized System Landscape

Assuming you use all scenarios, we recommend10: SAPS: 600 Memory: 2 - 4 GB (depending on the scenarios in use) Disk: 300 GB + 2.5 GB growth per month due to EarlyWatch Alert Reports and project documentation This recommendation specifies hardware requirements for the use of all scenarios in a small sized system landscape example (all ABAP systems -> without Diagnostics11) with the following proposition: Number of alerts per server: 40 Number of servers: 5 Number of systems: 6 (= number of EarlyWatch Alert Reports per week) Number of users for Implementation or Change Request Management: 13 (3 with 2 dialog steps/min and 10 with 10 dialog steps/hour) Number of documents processed during Implementation: 5,000 Number of users for Collaboration: 1 (1 with 2 dialog steps/min)

10

For detailled hardware recommendations on the individual scenarios, see: Appendix (Table: Small sized system landscapes).

11

For additional Diagnostics Sizing, see the according documents for installation and configuration service.sap.com/diagnostics

SAP AG

April 2008

11

Sizing SAP Solution Manager - SAP Customers and Partners

3 Sizing Recommendations for Additional Components

The following table lists further useful information for additional components: Content Note... Diagnostics For additional Diagnostics Sizing, see the according documents for installation and configuration service.sap.com/diagnostics SAP Note 797147 service.sap.com/sld service.sap.com/slm service.sap.com/adobe If BI runs on the same client as Solution Manager additional sizing is necessary service.sap.com/bi SAP Quality Center by HP SAP Redwood Job Scheduling Windows editions and memory support (FAQ) Master Guide SAP NetWeaver 7.0 Help on Application Usage for Solution Manager; Links to further documentation for SAP NetWeaver, SAP Business Suite service.sap.com/solutionmanager service.sap.com/job-scheduling SAP Note 313347 service.sap.com/installNW70 help.sap.com

Wily Introscope Enterprise Manager System Landscape Directory Software Lifecycle Manager Adobe Document Services Business Intelligence

SAP AG

April 2008

12

Sizing SAP Solution Manager - SAP Customers and Partners

Appendix
Using the Quick Sizer For your own calculations, please refer to service.sap.com/Quicksizer (this example is based on SD user SD-USER): 1. Insert your customer number. 2. Choose a project name. 3. Press Create Project.

4. In the hierarchical tree on the left, choose mySAP Business Suite-> Enterprise Resource Planning-> Sales and Service. 5. In the fields for SD-USER, insert the number of estimated concurrent medium activity users (assuming two dialog steps/min.) and low activity users (assuming 10 dialog steps/hour). 6. Choose Calculate result.

RESULT: The Quick Sizer calculates CPU, disk and memory resource categories.

SAP AG

April 2008

13

Sizing SAP Solution Manager - SAP Customers and Partners

Detailled Sizing Recommendations

How to read the tables: To be able to: size CPUs in SAPS add the according SAPS for the scenarios you want to use, e.g.: if you want to use Solution Monitoring and Change Management add: 1000 SAPS + 700 SAPS = 1700 SAPS. If you would use Service Desk and Change Management add: 700 SAPS + 700 SAPS = 1400 SAPS. determine disk in GB add the according numbers for the scenarios used. For our example of using Solution Monitoring and Change Management add: 50 GB + 100 GB = 150 GB. Add an additional 1.5 GB growth per month due to Early Watch Alert Reports = 165 GB. If you would use Service Desk and Change Management add: 100 GB + 100 GB = 200 GB. size RAM select the most consuming scenario and determine which scenarios you would like to add in the future, e.g. in our example we want to start with Solution Monitoring and Change Management: Solution Monitoring = 8 GB, Change Managament = 4 GB. In this case 8 GB would be sufficient. But: as we probably want to use more scenarios of Solution Manager more than 8 GB would be optimal. If we would only use scenario Collaboration, 4 GB would be sufficient. As Diagnostics is not considered in this document, please refer to the relevant documentation and add CPU, disk and RAM accordingly. Large sized system landscape Scenario Memory in GB (RAM) Hardware Recommendations (to be added, if applicable) CPU in SAPS12 Solution Monitoring 8 1000 Disk in GB 50 (+ 1.5 GB/ growth per month due to EarlyWatch Alert Reports) 150 (+ 5 GB/ documentation project) 4 700 100

Implementation OR Upgrade of SAP Solutions Service Desk OR Change Request Management Collaboration

400

100

50

12

SAPS is a hardware independent unit to describe the CPU-related performance characteristic of a given hardware configuration. For more information on SAPS and their equivalent in hardware performance, www.sap.com/benchmark -> SAPS.

SAP AG

April 2008

14

Sizing SAP Solution Manager - SAP Customers and Partners

Medium sized system landscape Scenario Memory in GB (RAM) Hardware Recommendations (to be added, if applicable) CPU in SAPS Solution Monitoring 6 550 Disk in GB 50 (+ 0.75 GB/ growth per month due to EarlyWatch Alert Reports) 100 (+ 2GB/ documentation project) 3 300 50

Implementation of SAP Solutions OR Upgrade of SAP Solutions Service Desk OR Change Request Management Collaboration

200

100

50

Small sized system landscape Scenario Memory in GB (RAM) Hardware Recommendations (to be added, if applicable) CPU in SAPS Solution Monitoring 4 100 Disk in GB 50 (+ 0.5 GB/ growth per month due to EarlyWatch Alert Reports) 50 (+ 1 GB/ documentation project) 2 2 100 100 50 50

Implementation or Upgrade of SAP Solutions Service Desk or Change Request Management Collaboration

100

SAP AG

April 2008

15

Sizing SAP Solution Manager - SAP Customers and Partners

Examples EarlyWatch Alert Reports only Assumption: You only want to use EarlyWatch Alert Reports in Solution Manager and no other scenario. You have approximately 200 production systems in your landscape. Solution The Solution Manager processes the EarlyWatch Alert Reports once a week in a background job. As you can schedule the job for a period of low CPU load (e.g., every Monday at 2:00 a.m.), the CPU resources (SAPS) you require are not as great as those we recommend for the use of the complete Solution Monitoring scenario (System Monitoring and Business Process Monitoring included). As a rule of thumb, you would need about 500 SAPS to process 100 EarlyWatch Alert Reports. You may also consider spreading the EarlyWatch Alert load over several solutions (e.g. two or three solutions). You can then schedule the processing time for a different day in each solution (e.g., Monday for the first solution and Tuesday for the second). This could also be of value, if you work in different time zones.

System Monitoring The Setup System Monitoring session within SAP Solution Manager provides alerts, which can be activated by default. They are a first hint to reasonable alerts.

Alert Group Hardware Alerts/DB Alerts Server alerts

Alert Names CPU Utilization CPU 5minLoadAverage Paging in Paging out OS_Collector

Alerts for ABAP based Instances

Errors/Administrating Alerts Dialog Alerts

Program Errors (Dialog) Response time Load+Gen Time DB request time Long runners Dialog steps Users logged in

Background Alerts

Program errors (background) Aborted jobs

Memory Managament Alerts

R/3 paging used R/3 rollused PrivWpNumber Program buffer Single record buffer Generic key buffer Screen buffer CUA buffer Table definition buffer

SAP AG

April 2008

16

Sizing SAP Solution Manager - SAP Customers and Partners

Field description buffer Initial records buffer Short name TAB Internet Transaction Server (ITS) Internet Pricing and Configurator (ICP) Performance/Availability Alerts IPC Server Alerts Server Threads used Availability Server Pricing Configurator

The proposed limitation of alerts depends on the Solution Manager architecture. Within Solution Manager you need to define so-called Solutions. You can regard them as containers for systems. In the System Monitoring session you define/configure for these systems (in your solution) which alerts for each system you would like to see in the Monitoring graphic of Solution Manager (in the graphic you see all systems which are in this solution in one glance). The refresh from the Solution Manager CEN to this graphical overview runs every 5 min by default.

System Monitoring and ALM In general, ALM is not supported by Solution Manager. If needed, you can integrate ALM manually into SAP Solution Manager and use it as an alert notification infrastructure.

SAP AG

April 2008

17