sizing guide sm 70 sp15

Released for SAP Customers and Partners

SAP SolutionManager 7.0 as ofSP15

Released for SAP Customers and Partners

April 2008

Sizing Guide

Sizing SAP Solution Manager - SAP Customers and Partners

© SAP AG Released for SAP Customers and Partners 2

© Copyright 2008 SAP AG. All rights reserved.

No part of this publication may be reproduced ortransmitted in any form or for any purpose without theexpress permission of SAP AG. The informationcontained herein may be changed without prior notice.

Some software products marketed by SAP AG and itsdistributors contain proprietary software components ofother software vendors.

Microsoft, Windows, Outlook, and PowerPoint areregistered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, ParallelSysplex, MVS/ESA, AIX, S/390, AS/400, OS/390,OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP,Intelligent Miner, WebSphere, Netfinity, Tivoli, andInformix are trademarks or registered trademarks of IBMCorporation in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registeredtrademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame,WinFrame, VideoFrame, and MultiWin are trademarks orregistered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks orregistered trademarks of W3C®, World Wide WebConsortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of SunMicrosystems, Inc., used under license for technologyinvented and implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAPNetWeaver, and other SAP products and servicesmentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG inGermany and in several other countries all over theworld. All other product and service names mentionedare the trademarks of their respective companies. Data

contained in this document serves informational purposesonly. National product specifications may vary.

These materials are subject to change without notice.These materials are provided by SAP AG andits affiliated companies ("SAP Group") for informationalpurposes only, without representation or warranty of anykind, and SAP Group shall not be liable for errors oromissions with respect to the materials. The onlywarranties for SAP Group products and services are thosethat are set forth in the express warranty statementsaccompanying such products and services, if any.Nothing herein should be construed as constituting anadditional warranty.

DisclaimerSome components of this product are based on Java™.Any code change in these components may causeunpredictable and severe malfunctions and is thereforeexpressively prohibited, as is any decompilation of thesecomponents.

SAP Library document classification: CUSTOMERS &PARTNERS

Documentation in the SAP Service MarketplaceYou can find this documentation at the following address:http://service.sap.com/instguides

http://service.sap.com/instguides


© SAP AG April 2008 1

CONTENTSCONTENTS.................................................................................................................................................... 1

HISTORY OF CHANGES ................................................................................................................................... 2

1 INTRODUCTION........................................................................................................................................ 4

SCENARIO OVERVIEW OF SAP SOLUTION MANAGER ...................................................................................... 4ARCHITECTURE OF SAP SOLUTION MANAGER ................................................................................................ 5FACTORS THAT INFLUENCE PERFORMANCE..................................................................................................... 6

2 INITIAL SIZING FOR SAP SOLUTION MANAGER.............................................................................. 9

ASSUMPTIONS ............................................................................................................................................... 9GENERAL INFORMATION ................................................................................................................................ 9LARGE SIZED SYSTEM LANDSCAPE .............................................................................................................. 10MEDIUM SIZED SYSTEM LANDSCAPE............................................................................................................ 10SMALL SIZED SYSTEM LANDSCAPE .............................................................................................................. 11

3 SIZING RECOMMENDATIONS FOR ADDITIONAL COMPONENTS .............................................. 12

APPENDIX ................................................................................................................................................... 13



History of ChangesThis Sizing Guide is updated with each new Support Package Stack in SAP Service Marketplace atservice.sap.com/instguides -> SAP Componens -> SAP Solution Manager -> <currentrelease>.

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 latestversions:

Date of Update Topic

30.04.2007 Sizing recommendations for SEP package (TDMS; RBE);

Additional information on factors that influenceperformance

Reference table on documentation on Sizing foradditional components (e,g. BI etc.)

Sizing for System Monitoring if functionality of Alert Inboxis used

Sizing Recommendations for Diagnostics are changedand can be obtained from the according Guides forDiagnostics (see: table for additional components)

Section on how-to read detailling sizing tables

SP15 06.02.2008

Sizing recommendations for SEP package deleted

28.04.2008 Name change: SAP Solution Manager 4.0 becomes SAPSolution Manager 7.0

Documentation types in the software life cycle:



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 availablehere. The guides are regularly updated.



1 IntroductionOne of the issues that you need to take care of at an early stage and throughout the product life cycleis the system resources you require. The sizing of your hardware will be a precondition for its goodperformance. Sizing means that you determine the hardware requirements for your SAP SolutionManager system. This is again depending on both your business aspects (How you want to useSolution Manager) and technological aspects (How many users will use the system and how high isthe data load for the system). Your system needs to able to handle peak loads and to display apredictable 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. Thefollowing paragraph gives a short overview of them. For detailled information on these scenarios, seeService Marketplace -> SAP Components -> Master Guide SAP Solution Manager <currentrelease>.

Scenario Overview of SAP Solution ManagerThe Implementation and Upgrade scenarios support the implementation of customer projects andthe definition of template projects and upgrade projects. In template projects, you define one or moretemplates containing scenarios, documents and configuration for re-use in other systems, e.g. for aglobal roll-out of centrally defined implementation settings. These Implementation and Upgradescenarios include roadmaps, an editor for creating and maintaining business blueprints, access to theImplementation Guides (IMG), and tools for testing, monitoring and distributing Customizing.

The Solution Monitoring scenario provides support for functionalities such as Service-LevelReporting, EarlyWatch Alert, Business Process Monitoring, System Monitoring, Central SystemAdministration, System Landscape Reporting, as well as user-defined alerts.

The Service Desk of the SAP Solution Manager offers a complete infrastructure for organizing andoperating a solution-wide support organization at your site. The Service Desk promotes effective usersupport in your SAP solution landscape every step of the way - from the end-users to your internalsupport organization and when necessary to SAP.

Change Request Management in SAP Solution Manager is aligned to the processes in the ITInfrastructure Library (ITIL), the de facto standard for service management. As defined in ITIL, theobjective of Change Management is to carry out changes economically and in a timely manner withminimal 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 SAPsupport services, including remote services, on-site services, self services, and Best Practicedocuments. Based on your solution configuration, recommendations for these services are triggereddynamically. The reports resulting from each service are available and are archived in the operationssection. The reports are useful documentation stored in the SAP Solution Manager and serve asreference 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 causeanalysis with speed and efficiency. Diagnostics in SAP Solution Manager provides standardized toolsfor the support of customer solutions, including third-party components. The tools enable a systematicand targeted cross-component localization of the root cause of IT problems. The centralized approachavoids that many experts have to search for possible root causes on all components involved, in mostcases without success. With the possibilities of Diagnostics, your support organization can both savecosts and accelerate the time required for problem resolution.



Architecture of SAP Solution ManagerSAP 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, towhich all other systems of your system landscape are connected. Systems that are administered usingthe SAP Solution Manager are referred to as "satellite systems". Sizing of Solution Manager does notinclude and is not dependent on the sizing of any of the satellite system types, but on the number ofsatellite system types connected to the Solution Manager. Follow the Solution Manager ABAP sizingfor 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 thenumber 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 arenot described in this document. Refer to hardware requirements in the according Guidesfor E2E scenarios (Diagnostics) on the Service Marketplace: service.sap.com/diagnostics

For a more detailled description on architecture: Service Marketplace -> SAP Components ->SecurityGuide SAP Solution Manager <current release>.



Factors that Influence Performance

The most important concepts to consider are the following:

Concept Note...

Scenario Which scenarios are used and are to be used? You can use allscenarios or just one, for instance Solution Monitoring. You maystart with Maintenance Optimizer and Solution Monitoring, andintegrate step by step most of the other scenarios.

Servers of satellite systemsconnected

Connected servers are especially relevant for Solution Monitoringsizing.

Solutions in productive use How are your solutions designed?

To "customize" your solutions you need to consider whichscenarios you are going to use. For instance, if you are going touse Business Process Monitoring, your business process willprobably connect via various satellite systems, this should be yourmain consideration.

For instance, you would like to activate Business ProcessMonitoring for a business process which runs via a SAP CRMsystem and a SAP ERP system. Both systems (both in systemrole: production) should be in the solution.

If you are are not using Business Process Monitoring you cantailor the systems per solutions according to other demands.



The following table shows which factors per scenario are important and need to be considered:

Scenario Performance influencing factors Note….

Solution Monitoring(if graphical display forsolutions is used)1

alerts of System Monitoringand Business ProcessMonitoring per connectedserver that are to beprocessed2

----------------------------------------------

data download for andprocessing of EarlyWatchAlert/Service Level Reportsper system3

We recommend not setting up morethan 2000 alerts per solutionlandscape. If you want to monitormore alerts you should create furthersolution landscapes. We recommendmax. 46 - 60 systems per solution4.

--------------------------------------------------

After the EarlyWatch Alert datadownload, the system processes thedata, sequentially. This action istypically performed as a backgroundjob at night or at other times with lessload. We strongly recommendautomatically deleting or archiving olderreports 5.

Solution Monitoring(if System MonitoringAlert Inbox functionalityof the SystemMonitoring WorkCenter is used)

number of connected serversper solution

We recommend about 100 server persolution. Larger landscapes with withmore than 100 systems should haveseparate solutions.

Solution Monitoring(BI- Analyses)

if the client for BI-Analyses isto be the same as the clientfor productive SolutionManager

In this case you need to consideradditional sizing information forBusiness Intelligence (BI), seeReference table on documentation onSizing for additional components

Implementationand/or Upgrade

number of users anddocuments processed

Service Desk and/orChange RequestManagement

number of users

Collaboration documents processed Number of Service Reportsdownloaded

1 Graphical display is not supported by the Work Center approach.2 See Appendix for example3 See Appendix for example4 Average assumption: 40 alerts per connected server/2000 alerts per solution, independent of thenumber of servers (for more information on alerts in the Setup System Monitoirng session, seeappendix). In the System Monitoring session you should define for one Solution not more than 2000alerts, disregarding the number of systems.Time scale 2000 alerts per solution:

Initial call of System Monitoring graphic: 75s; Refresh of System Monitoring graphic: 30s5 SAP Note 546685 (Archiving in the Solution Manager (Operation); SAP Note 638785 (SAP SolutionManager - reduce data volumes)



Scenario Performance influencing factors Note….

Diagnostics garbage collection runs The Diagnostics Server runs in 2different modes: Dialog Mode: Times of dialog

user interaction, e.g. performanceanalysis of a monitored satellitesystem.

Background Mode: Time windowfor automated tasks, e.g.gathering configuration data of amonitored system.

Normally, these tasks are scheduledin times of low dialog usage (nightly).There is no technical dependencybetween the two modes - dialog andbackground activities can be mixed.

For Diagnostics sizing see: Referencetable on documentation on Sizing foradditional components



2 Initial Sizing for SAP Solution Manager

Assumptions

General InformationAssumptions per scenario (excluding Diagnostics):

Scenario Assumption Note….

Implementation and/orUpgrade

based on SD user SD-USER inthe Quick Sizer Tool

Service Desk and/orChange RequestManagement

based on CRM user SRV-USER inthe Quick Sizer Tool

both scenarios are primarily based onCRM functionality

Collaboration based on CRM user SRV-USER inthe Quick Sizer Tool

scenario is primarily based on CRMfunctionality

Solution Monitoring based on number of alerts perserver (solution design)

not included in the Quick Sizer Tool

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 youbase your sizing estimate on the assumptions for the landscape with the next highest number ofservers. For example, if your server number is 60, then you should base your estimate on the sizingrecommendations for Large sized system landscapes.

In general, all assumptions in this paper are based on Unicode. For more information on specificdependencies, see: http://service.sap.com/unicode -> Unicode at SAP -> Unicode Media Library ->Unicode Information on Specific Topics -> Unicode: Hardware Requirements and CustomerExperience.

http://service.sap.com/unicode



Large Sized System LandscapeAssuming 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 sizedsystem landscape example (all ABAP systems -> without Diagnostics7) with the following exampleproposition:

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 LandscapeAssuming 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 sizedsystem landscape example (all ABAP systems -> without Diagnostics9) with the followingproposition:

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)

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

7 For additional Diagnostics Sizing, see the according documents for installation and configurationservice.sap.com/diagnostics8 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 configurationservice.sap.com/diagnostics



Small Sized System LandscapeAssuming 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 sizedsystem landscape example (all ABAP systems -> without Diagnostics11) with the followingproposition:

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: Smallsized system landscapes).

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



3 Sizing Recommendations for Additional ComponentsThe following table lists further useful information for additional components:Content Note...

Diagnostics For additional Diagnostics Sizing, see theaccording documents for installation andconfigurationservice.sap.com/diagnostics

Wily Introscope Enterprise Manager SAP Note 797147

System Landscape Directory service.sap.com/sld

Software Lifecycle Manager service.sap.com/slm

Adobe Document Services service.sap.com/adobe

Business Intelligence If BI runs on the same client as SolutionManager additional sizing is necessary

service.sap.com/bi

SAP Quality Center by HP service.sap.com/solutionmanager

SAP Redwood Job Scheduling service.sap.com/job-scheduling

Windows editions and memory support (FAQ) SAP Note 313347Master Guide SAP NetWeaver 7.0 service.sap.com/installNW70

Help on Application Usage for SolutionManager; Links to further documentation forSAP NetWeaver, SAP Business Suite

help.sap.com



AppendixUsing the Quick SizerFor your own calculations, please refer to service.sap.com/Quicksizer (this example is based on SDuser 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 ResourcePlanning-> 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.



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 youwant 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 + 700SAPS = 1400 SAPS.

determine disk in GB add the according numbers for the scenarios used. For our example ofusing Solution Monitoring and Change Management add: 50 GB + 100 GB = 150 GB. Add anadditional 1.5 GB growth per month due to Early Watch Alert Reports = 165 GB. If you woulduse 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 liketo add in the future, e.g. in our example we want to start with Solution Monitoring and ChangeManagement: Solution Monitoring = 8 GB, Change Managament = 4 GB. In this case 8 GBwould be sufficient. But: as we probably want to use more scenarios of Solution Managermore than 8 GB would be optimal. If we would only use scenario Collaboration, 4 GB would besufficient.

As Diagnostics is not considered in this document, please refer to the relevantdocumentation and add CPU, disk and RAM accordingly.

Large sized system landscape

Hardware Recommendations (to be added, ifapplicable)

Scenario Memory in GB(RAM)

CPU in SAPS12 Disk in GB

Solution Monitoring 8 1000 50 (+ 1.5 GB/ growth permonth due to EarlyWatchAlert Reports)

Implementation ORUpgrade of SAPSolutions

4 400 150 (+ 5 GB/documentation

project)

Service Desk ORChange RequestManagement

4 700 100

Collaboration 3 100 50

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

http://www.sap.com/benchmark



Medium sized system landscape


Scenario Memory in GB(RAM)

CPU in SAPS Disk in GB


Implementation of SAPSolutions OR Upgradeof SAP Solutions

3 200 100 (+ 2GB/ documentation

project)

Service Desk ORChange RequestManagement

3 300 50


Small sized system landscape


Scenario Memory inGB (RAM)

CPU in SAPS Disk in GB


Implementation or Upgradeof SAP Solutions

2 100 50 (+ 1 GB/ documentation

project)

Service Desk or ChangeRequest Management

2 100 50




Examples

EarlyWatch Alert Reports only

Assumption:

You only want to use EarlyWatch Alert Reports in Solution Manager and no other scenario. You haveapproximately 200 production systems in your landscape.

Solution

The Solution Manager processes the EarlyWatch Alert Reports once a week in a background job. Asyou can schedule the job for a period of low CPU load (e.g., every Monday at 2:00 a.m.), the CPUresources (SAPS) you require are not as great as those we recommend for the use of the completeSolution Monitoring scenario (System Monitoring and Business Process Monitoring included). As arule 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 threesolutions). 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 indifferent time zones.

System Monitoring

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

Alert Group Alert Names

HardwareAlerts/DB Alerts

Server alerts CPU Utilization

CPU 5minLoadAverage

Paging in

Paging out

OS_Collector

Alerts for ABAPbased Instances

Errors/Administrating Alerts Program Errors (Dialog)

Dialog Alerts 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



Field description buffer

Initial records buffer

Short name TAB

InternetTransaction Server(ITS)

Performance/AvailabilityAlerts

Threads used

Availability

Internet Pricing andConfigurator (ICP)

IPC Server Alerts Server

Server Pricing

Configurator

The proposed limitation of alerts depends on the Solution Manager architecture. Within SolutionManager you need to define so-called Solutions. You can regard them as containers for systems. Inthe System Monitoring session you define/configure for these systems (in your solution) which alertsfor each system you would like to see in the Monitoring graphic of Solution Manager (in the graphicyou see all systems which are in this solution in one glance). The refresh from the Solution ManagerCEN 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 manuallyinto SAP Solution Manager and use it as an alert notification infrastructure.

sizing guide sm 70 sp15

Documents