bpc nw sizing guidelines version 0

Sizing SAPBusinessObjectsPlanning andConsolidation 7.0,Version for SAPNetWeaver

Document Version 0.984, June 2009

SIZING GUIDE

© SAP AG Released for SAP Customers and Partners 3

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

SAP Library document classification: CUSTOMERS &PARTNERS

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

http://service.sap.com/sizing

© SAP AG Sizing SAP BusinessObjects Planning and Consolidation, version for SAP NetWeaver 1

TABLE OF CONTENTS

1 INTRODUCTION................................................................................................................................... 1

1.1 FUNCTIONS OF SAP BPC SAP NETWEAVER.................................................................................... 11.2 ARCHITECTURE OF SAP BPC SAP NETWEAVER.............................................................................. 11.3 FACTORS THAT INFLUENCE THE PERFORMANCE ................................................................................... 4

2 SIZING FUNDAMENTALS AND TERMINOLOGY ........................................................................... 4

3 INITIAL SIZING FOR SAP BPC SAP NETWEAVER......................................................................... 5

3.1 ASSUMPTIONS .................................................................................................................................... 53.2 BASIC SCENARIOS .............................................................................................................................. 53.3 SIZING GUIDELINE .............................................................................................................................. 6

3.3.1 Sizing Category.......................................................................................................................... 63.3.2 CPU & Memory Sizing............................................................................................................... 7

4 COMMENTS AND FEEDBACK ............................................. ERROR! BOOKMARK NOT DEFINED.

1 IntroductionSAP BusinessObjects Planning and Consolidation, version for SAP NetWeaver (SAP BPC SAPNETWEAVER) is a robust planning and consolidation application designed to meet organizationalbudgeting, planning, consolidation, and reporting requirements. It supports a wide array of top-downand bottom-up financial planning needs, as well as consolidation processes necessary to ensure asmooth and timely financial close, all through a single application. Through the implementation andutilization of SAP BPC, organizations are empowered to meet increasingly stringent regulations,effectively plan strategically and tactically, and obtain the information necessary to gain importantinsights.

1.1 Functions of SAP BusinessObjects, version for SAPNetWeaver

The primary capabilities of SAP BusinessObjects Planning and Consolidation 7.0, version for SAPNetWeaver include:

Budgeting/Planning/Forecasting

/Consolidation/ Financial Clos

1.2 Architecture of SAP BusinessObjects, version for SAPNetWeaver

SAP Business Planning and Consolidation, version for SAP NetWeaver, runs on the SAP NetWeaverBI platform, and also requires a Microsoft .NET application server.

At a high level, it has four tiers:


Client tier – Used to run Zero Footprint (aka ZFP, Web), Office (Excel, Word, PowerPoint), or Admin(Standalone .NET client application).NET Web Server and Application Server tier – Used for data mapping and pass through betweenclient and SAP NETWEAVER App Servers and perform user authenticationsSAP NetWeaver application tier – SAP NetWeaver BI Application Servers (OLAP Engine andApplication Logic)Database tier – Any Database including SAP NETWEAVER BI physical data storage

Server ComponentsTo help you understand the configurations let’s review the technology components used by SAP BPC.For further details on the hardware requirements and underlying software requirements please refer tothe service market place.

SAP Business Planning and Consolidation – Master Guide & Installation Guidehttps://service.sap.com/instguidescpm-bpc

1. Database Tier

Can be any database supported by SAP NetWeaver (MS SQL, Oracle, DB2, MaxDB, etc…)

Full support of 64 bit and Unicode capabilities

Common Processing

All reads of data

https://service.sap.com/instguidescpm-bpc


All write back of data

Metadata read/write

File Storage Read/Write

Storage location for all application files

Book Repository

Report & Input Templates

Unstructured Data

Conversion & Transformation Files

2. SAP NetWeaver ABAP Application Server

Supports any Application Server configuration supported by SAP NetWeaver

Common Processing

Script Logic, calculations, and MDX Parsing

Parameter Driven Logic

Data Manager Loads and ETL

Data Tables to XML Conversions and vice versa

OLAP Engine and Calculations

3. Microsoft IIS Web Server

Microsoft IIS

Supports all SOA (Service Oriented Architecture)

Collection of CPM Services

Performs user authentication

Common Processing

Send and receive data between client and ABAP Application

Server

Rendering of System Reports

Live Reports Rendering

PDF Rendering for Distributor

SOAP Processing and conversion of data formats

Hosts ZFP

Note: this tier is a 32-bit architecture.

4. BI Accelerator

Optional component

Used to optimize database read times for large data volumes


1.3 Factors that influence the performanceThe following factors will influence the performance of BPC SAP NETWEAVER:

Active concurrent users in the system

Records of the Application

Complexity of any script logic and the formula used for calculation, planning

Complexity of any consolidation logic

Complexity of any member access rules

Data volume per query or volume of any operation transporting data

2 Sizing Fundamentals and TerminologySAP provides general sizing information on the SAP Service Marketplace. For the purpose of thisguide, we assume that you are familiar with sizing fundamentals. You can find more information athttp://service.sap.com/sizing Sizing General Sizing Procedures.

This section explains the most important sizing terms, as these terms are used extensively in thisdocument.

SizingSizing means determining the hardware requirements of an SAP application, such as the networkbandwidth, physical memory, CPU processing power, and I/O capacity. The size of the hardware anddatabase is influenced by both business aspects and technological aspects. This means that thenumber of users using the various application components and the data load they put on the servermust be taken into account.

BenchmarkingSizing information can be determined using SAP Standard Application Benchmarks and scalabilitytests (www.sap.com/benchmark). Released for technology partners, benchmarks provide basic sizingrecommendations to customers by placing a substantial load upon a system during the testing of newhardware, system software components, and relational database management systems (RDBMS). Allperformance data relevant to the system, user, and business applications are monitored during abenchmark run and can be used to compare platforms.

SAPSThe SAP Application Performance Standard (SAPS) is a hardware-independent unit that describes theperformance of a system configuration in the SAP environment. It is derived from the Sales andDistribution (SD) Benchmark, where 100 SAPS is defined as the computing power to handle 2,000fully business processed order line items per hour. (For more information about SAPS, seehttp://www.sap.com/benchmark SAPS).

Initial SizingInitial sizing refers to the sizing approach that provides statements about platform-independentrequirements of the hardware resources necessary for representative, standard delivery SAPapplications. The initial sizing guidelines assume optimal system parameter settings, standardbusiness scenarios, and so on.

Expert SizingThis term refers to a sizing exercise where customer-specific data is being analyzed and used to putmore detail on the sizing result. The main objective is to determine the resource consumption ofcustomized content and applications (not SAP standard delivery) by comprehensive measurements.For more information, see http://service.sap.com/sizing Sizing Guidelines General SizingProcedures Expert Sizing.


http://www.sap.com/benchmark).

http://www.sap.com/benchmark



Configuration and System LandscapingHardware resource and optimal system configuration greatly depend on the requirements of thecustomer-specific project. This includes the implementation of distribution, security, and highavailability solutions by different approaches using various third-party tools. In the case of highavailability through redundant resources, for example, the final resource requirements must beadjusted accordingly.

There are some "best practices" which may be valid for a specific combination of operating systemand database. To provide guidance, SAP created the SAP NetWeaver configuration guides(http://service.sap.com/instguides SAP NetWeaver).

Hardware Minimum RequirementsUnless otherwise indicated, the sizing guidelines specify the net requirements of the businessapplication. The minimum requirements for installing an “empty” system are specified in the respectiveimplementation guides (http://service.sap.com/instguides, in the section for hardware and softwarerequirements). The same applies for front-end PC minimum and optimal requirements.

3 Initial Sizing for SAP BPC, version for SAP NetWeaver

3.1 AssumptionsThe following assumptions were utilized in the testing that informed this sizing approach:

Simple access rule is defined: one dimension is set as secure dimension and simple memberaccess rules have been defined on this dimension

440 records will be retrieved per query

440 records will be sent to server per scenario for data entry

User performing data entry will perform a follow up action approximately once per minutefollowing a query execution, once every 3 minutes following write-back

Further assumptions are made correspondingly according to the different scenarios definedbelow

3.2 Basic ScenariosAccording to the complexity of the scenarios in BPC, we classified requirements for using BPC assmall, mid-complexity and very-complex.

Simple Requirements: include simple calculations, lightweight consolidations, simple input,light default logic, and limited MDX based formulas

Assumption: To simulate this scenario, our test will assume 40% users will run queries onbase member, 30% users will run aggregation (MDX) queries and 30% users will perform write-back. Query will be run in average every 60 seconds per user, write back once every 3 minuteson average

Mid-Complexity Requirements: include simple calculations, utilizing most consolidationprograms, quite a bit of default logic, and limited MDX based formulas

Assumption: TBD

Very-Complex Requirements: include complex calculations, utilizing all consolidationprograms, very detailed default logic, and full use of MDX based formulas

Assumption: TBD

http://service.sap.com/instguides

http://service.sap.com/instguides


3.3 Sizing guideline

3.3.1 Sizing Category

The system can be classified into the following 9 categories based on the above combination ofrequirement complexity and user bases.

Simple Requirements, Small User Base

Include simple calculations, lightweight consolidations, simple input, light default logic, andlimited MDX based formulas

100 named users with 20 active concurrent users

Simple Requirements, Midsize User Base Include simple calculations, lightweight consolidations, simple input, light default logic, and

limited MDX based formulas


Simple Requirements, Large User Base Include simple calculations, lightweight consolidations, simple input, light default logic, and



Simple Requirements, Extra Large User Base Includes simple calculations, lightweight consolidations, simple input, light default logic, and



Mid-Complexity Requirements, Small User Base Includes simple calculations, utilizing most consolidation programs, quite a bit of default logic,

and limited MDX based formulas

100 users with 20 active concurrent users

Mid-Complexity Requirements, Midsize User Base Includes simple calculations, utilizing most consolidation programs, quite a bit of default logic,



Mid-Complexity Requirements, Large User Base Includes simple calculations, utilizing most consolidation programs, quite a bit of default logic,



Very-complex Requirements, Small User Base Includes complex calculations, utilizing all consolidation programs, very detailed default logic,

and full use of MDX based formulas


100 users with 20 active parallel users

Very-complex Requirements, Midsize User Base Includes complex calculations, utilizing all consolidation programs, very detailed default logic,



Very-complex Requirements, Large User Base Includes complex calculations, utilizing all consolidation programs, very detailed default logic,



3.3.2 CPU & Memory SizingThese figures are based on extensive testing that represents the “simple” scenario. While theseestimates are based on direct observation, actual resource utilization may vary from the estimatesprovided here. Differences in operating systems, databases, and actual use of the application maycause variations. If you are re-sizing an existing SAP NetWeaver BW system for BPC, use an “additivesizing” approach – i.e. ensure that your SAP NetWeaver servers have additional or already existingcapacity, or add additional hardware resources to accommodate the added workload imposed by BPC.

SAP NetWeaver Server(s) .NET Web Server(s)System CategoryCPU in*SAPS

Total Memory CPU Memory

Simple RequirementSmall User Base 4000 16 GB 1 server / 4

CPU cores 4GB

Simple RequirementMidsize User Base 8000 32 GB 1 server / 4

CPU cores 4GB

Simple RequirementLarge User Base 16000 48 GB 2 servers X 4

CPU cores2 servers

4GBSimple Requirement

Extra Large User Base 32000 64 GB 2 servers X 4CPU cores

2 servers 4GB

Mid-Complexity RequirementsSmall User Base

More dataneeded

More dataneeded

More dataneeded

More dataneeded

Mid-Complexity RequirementsMidsize User Base

More dataneeded

More dataneeded

More dataneeded

More dataneeded

Mid-Complexity RequirementsLarge User Base

More dataneeded

More dataneeded

More dataneeded

More dataneeded

Very Complex RequirementsSmall User Base

More dataneeded

More dataneeded

More dataneeded

More dataneeded

Very Complex RequirementsMidsize User Base

More dataneeded

More dataneeded

More dataneeded

More dataneeded

Very Complex RequirementsLarge User Base

More dataneeded

More dataneeded

More dataneeded

More dataneeded

* 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, see www.sap.com/benchmark -> SAPS

http://www.sap.com/benchmark


4 Observations from performance testing that informedthe creation of this guide

In order to support a large number of concurrent users, an appropriate basis configuration must bein place. An SAP NetWeaver dialog instance can support a maximum of 100 dialog processes,and each dialog process consumes a certain amount of memory. Thus, in order to support ahigher number of users, multiple SAP dialog instances may be required (including the possibility ofseveral dialog instances on one server).

Ensure that an appropriate amount of swap space is configured for SAP NetWeaver instances –SAP recommends 2x physical memory.

Significant performance improvements were observed when the latest BPC support package wasapplied.

Significant performance improvements were observed when Oracle database statistics were updatedwith brtools, including running with the settings “all”, “all_part” and “infocubes”.

Contrary to guidance provided in note 830576, we observed significant performance degradation whenwe increased the size of the Oracle parameter PGA_AGGREGATE_TARGET. We saw optimalresults with this parameter set to 600 MB.

Parameter settings in accordance with SAP notes 192658 (Setting parameters for BW systems),1044441 (Basis parameterization for NW 7.0 BI systems), and 830576 (Parameterrecommendations for Oracle 10g) were utilized effectively in our testing.

In order to accommodate higher numbers of concurrent users, SAP note 31687 (“Maximumnumber of conversations exceeded”) was applied, in particular – the environment variableCPIC_MAX_CONV was added on the .NET servers, with the value “200”.

Our tests included a very wide degree of variation of selections on queries and of datasets used in writeback. Because of this very high degree of variation, the performance overhead of the OLAP cachemechanism outweighed it potential performance benefits. In our example, performance improvedsomewhat significantly when we turned off the OLAP cache. It is worth noting that real world scenarioswill not likely have nearly the same type of wide degree of variation of selections like the ones utilized inour tests, and therefore the cache may be beneficial for performance. In summary, it is worthmonitoring the effects of the OLAP cache in your own environment to determine if it is beneficial forperformance in your particular case.

Note that the .NET layer is a 32-bit architecture. 32 bit windows servers cannot address more than 4GB of RAM.

5 Comments and FeedbackThis is a first draft release of SAP Business Planning & Consolidation 7.0, version for SAP NetWeaverSizing Guide. To improve this guide, we appreciate your feed back and comments.

Please send your feedback and comments to: Ron Silberstein, [email protected]

mailto:[email protected]

bpc nw sizing guidelines version 0

Documents