Sizing Guide 40 V5

8/6/2019 Sizing Guide 40 V5

http://slidepdf.com/reader/full/sizing-guide-40-v5 1/14

Released for SAP Customers and Partners

!!!!



© SAP AG Released for SAP Customers and Partners 2

© Copyright 2007 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 mentionedare 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/sizing



© SAP AG Sizing SAP Solution Manager - SAP Customers and Partners 2

1 IntroductionSAP Solution Manager supports your entire product lifecycle on one platform.

1.1 Functions 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 and

operating 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 operations

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

1.2 Architecture of SAP Solution ManagerThe SAP Solution Manager runs in a separate central system, to which all other SAP systems areconnected. Systems that are administered using the SAP Solution Manager are referred to as"satellite systems". These satellite systems are bundled either within a solution or within a project.

Sizing of Solution Manager does not include and is not dependent on the sizing of any of the satellitesystem types, but on the number of satellite system types connected to the Solution Manager. Followthe Solution Manager ABAP sizing for the ABAP stack requirements and the Solution ManagerDiagnostics J2EE stack sizing for the J2EE stack requirements.




When sizing your SAP Solution Manager system, you should consider the following questions:

What is the most important business or scenario in Solution Manager?

Which process or customizing influences the estimated business throughput?

Are there limitations on the time window?

What is the number of entries stored in the database including indexes?

In ABAP stack, how many users will work with the system?

In ABAP stack, how many documents will be processed?

In JAVA stack, garbage collection runs should be used for sizing.




1.3 Factors that influence performance

Scenario Performance influencing factors Note….Solution Monitoring • alerts of System Monitoring

and Business ProcessMonitoring per connectedserver that are to beprocessed (see Appendix forExample)

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

• data download for and

processing of EarlyWatchAlert/Service Level Reportsper system (see Appendix forExample).

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 solution

1.

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

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

2.

Implementation andUpgrade

• number of users anddocuments processed

Service Desk andChange RequestManagement

• number of users

Collaboration • documents processed Number of Service Reportsdownloaded

Diagnostics • garbage collection runs The Diagnostics Server runs in 2different modes :

• Dialog Mode: Times of dialoguser 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.

1Average 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, 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: 30s

2SAP Note 546685 (Archiving in the Solution Manager (Operation); SAP Note 638785 (SAP Solution

Manager - reduce data volumes)




2 Initial Sizing for SAP Solution Manager

Assumptions

General Information

1. Sizing assumptions for

Implementation and Upgrade are based on SD user SD-USER in the Quick Sizer Tool;

Service Desk und Change Request Management are based on CRM user SRV-USER in theQuick Sizer Tool;

Collaboration is based on CRM user SRV-USER in the Quick Sizer Tool;

Solution Monitoring and Diagnostics are not included in the Quick Sizer Tool.

For more information on the Quick Sizer Tool, see Appendix: Using the Quick Sizer.

2. All assumption examples should be regarded as general assumptions regarding numbers ofservers, etc.. In practice, you may have a greater or smaller number of servers, etc. Werecommend that you base your sizing estimate on the assumptions for the landscape with the nexthighest number of servers. For example, if your server number is 60, then you should base yourestimate on the sizing recommendations for Large sized system landscapes.

3. In general, all assumptions in this paper are based on Unicode.

For more information on specific dependencies, see: http://service.sap.com/unicode -> Unicode atSAP -> Unicode Media Library -> Unicode Information on Specific Topics -> Unicode: HardwareRequirements and Customer Experience.

Large sized system landscape

Assuming you use all scenarios, we recommend3:

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 projectdocumentation

This recommendation specifies hardware requirements for the use of all scenarios in a large sized system landscape example (all ABAP systems -> without Diagnostics) 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)

3For detailled hardware recommendations on the individual scenarios, see: Appendix (Table: Large

sized system landscape)




Medium sized system landscape


SAPS: 1650


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 Diagnostics) with the following proposition :



Number of systems: 45 (= number of EarlyWatch Alert Reports per week)

Number of users for Implementation or Change Request Management: 40 (10 with 2 dialogsteps/min and 30 with 10 dialog steps/hour)


Number of users for Collaboration: 3 (1 with 2 dialog steps/min and 2 with 10 dialog steps/hour)

Small sized system landscape


SAPS: 600


Disk: 300 GB + 2.5 GB growth per month due to EarlyWatch Alert Reports and projectdocumentation

This recommendation specifies hardware requirements for the use of all scenarios in a small sized system landscape example (all ABAP systems -> without Diagnostics) with the following proposition :



Number of systems: 6 (= number of EarlyWatch Alert Reports per week)

Number of users for Implementation or Change Request Management: 13 (3 with 2 dialogsteps/min and 10 with 10 dialog steps/hour)


Number of users for Collaboration: 1 (1 with 2 dialog steps/min)

4For detailled hardware recommendations on the individual scenarios, see: Appendix (Table: Medium

sized system landscape)5

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




Root Cause Analyses: Diagnostics

MEDIUM SCALE

We recommend6

: SAPS: 550

Memory: 1.1 GB

Disk: 500 MB

This assumption specifies hardware recommendations for Diagnostics (J2EE) based on a minimumscale. They are to be added to the hardware recommendations for the scenarios based on the ABAPstack:


Number of users: 1 (high load user)

Number of active running tasks: 1

Time window reserved for background mode: 8 hours7

LARGE SCALE

We recommend8:

SAPS: 1500

Memory: 2.5 GB

Disk: 5 GB

This assumption specifies hardware recommendations for Diagnostics Add-In (J2EE) based on alarger scale. They are to be added to the hardware recommendations for the scenarios based on theABAP stack:


Number of users: 3 (high load user)Number of active running tasks: 1

Time window reserved for background mode: 8 hours9

6For detailled hardware recommendations on this scenario, see: Appendix (Table: Medium Scale

Diagnostics).

7Diagnostics can handle four monitored servers per hour in the background mode.

8For detailled hardware recommendations on this scenario, see: Appendix (Table: Large Scale

Diagnostics).

9Diagnostics can handle four monitored servers per hour in the background mode.




AppendixUsing the Quick SizerFor 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.




Detailled Sizing Recommendations

Large sized system landscape

Hardware Recommendations (to be added, ifapplicable)

Scenario Memory in GB(RAM)

CPU in SAPS10

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

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


10

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.




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


Small Scale Diagnostics

Hardware Recommendations (to be added, if applicable)Scenario

CPU in SAPS Memory in MB(RAM)

Disk in MB

Solution ManagerDiagnostics (DIALOGMODE)

11

250

(Virtualize 1 CPU by 50%)

600

Solution ManagerDiagnostics(BACKGROUND MODE)

300

Virtualize 1 CPU by 60%

500 500

Large Scale Diagnostics

TotalCalculation

CPU inSAPS

Memoryin GB(RAM)

Disk in GB

CPU (dialog mode) 2 CPU (3 users)

CPU (background mode) 1 CPU (10 servers)

Memory required forbackground processing

100 MB (1 task)

Memory required for dialogprocessing

600 MB (3 users)

1500 2.5 5

11See as well SAP Note 915676 for sizing Diagnostics, and SAP Note 797147 sizing of Wily

Introscope Enterprise Manager.




• 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 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 manuallyinto SAP Solution Manager and use it as an alert notification infrastructure.

Sizing Guide 40 V5

Documents

Transcript of Sizing Guide 40 V5