Anda di halaman 1dari 12

Sizing Guide

Sizing SAP BusinessObjects


Web Intelligence, Version 4.0
Support Package 2

Released for SAP Customers and Partners

Document Version 1.0, July 2011


Copyright 2011 SAP AG. All rights reserved. serves informational purposes only. National product
specifications may vary.
No part of this publication may be reproduced or transmitted These materials are subject to change without notice. These
in any form or for any purpose without the express permission materials are provided by SAP AG and its affiliated
of SAP AG. The information contained herein may be companies ("SAP Group") for informational purposes
changed without prior notice. only, without representation or warranty of any kind, and SAP
Group shall not be liable for errors or omissions with respect
Some software products marketed by SAP AG and its to the materials. The only warranties for SAP Group products
distributors contain proprietary software components of other and services are those that are set forth in the express
software vendors. warranty statements accompanying such products and
services, if any. Nothing herein should be construed as
Microsoft, Windows, Outlook, and PowerPoint are registered constituting an additional warranty.
trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, Disclaimer


MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, Some components of this product are based on Java. Any
pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, code change in these components may cause unpredictable
WebSphere, Netfinity, Tivoli, and Informix are trademarks or and severe malfunctions and is therefore expressly
registered trademarks of IBM Corporation in the United States prohibited, as is any decompilation of these components.
and/or other countries.
SAP Library document classification: CUSTOMERS &
Oracle is a registered trademark of Oracle Corporation. PARTNERS

UNIX, X/Open, OSF/1, and Motif are registered trademarks of Documentation in the SAP Service Marketplace
the Open Group. You can find this documentation at the following address:
http://service.sap.com/sizing

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

Copyright/Trademark
1 Sizing SAP <application> - SAP Customers and Partners
__________________________________________________________________________________

TABLE OF CONTENTS

1. Introduction..............................................................................................................................2
1.1 Functions of SAP BusinessObjects Web Intelligence..................................................................2
1.2 Architecture of SAP BusinessObjects Web Intelligence ..............................................................3
1.3 Factors that influence sizing .......................................................................................................4
2 Sizing Fundamentals and Terminology ..................................................................................5
3 Initial Sizing for SAP BusinessObjects Web Intelligence ......................................................6
3.1 Assumptions ..............................................................................................................................6
3.1.1 Viewing Web Intelligence documents with queries on RDBMS................................................6
3.1.2 Web Intelligence viewing with queries on SAP BW BEx .......................................................6
3.2 Sizing guideline..........................................................................................................................7
3.2.1 Web Intelligence viewing with queries on RDBMS ..................................................................8
3.2.2 Web Intelligence viewing with queries on SAP BW - BEx........................................................8
4 Miscellaneous ........................................................................................................................ 10
5 Comments and Feedback ...................................................................................................... 10

1.
2
Sizing SAP BusinessObjects Web Intelligence 4.0 - SAP Customers and Partners
__________________________________________________________________________________

1. INTRODUCTION
Web Intelligence is an ad hoc query and analysis application that allows end users to define queries on
corporate data and format reports. Other end users can modify the query definition and report structure
in existing reports to customize the content and presentation according to their specific business needs.
Web Intelligence has three deployment options to cover a broad range of end-user needs and company
policies:
DHTML client (referred to as Business Intelligence reporting in the SAP BusinessObjects BI launch
pad) designed for customers seeking a zero-footprint solution where nothing is installed on the
users desktop.
Java Report Panel - designed for analysts or report designers who require an online tool with a
smooth user experience and a powerful set of features. A Java applet is installed on the users
desktop.
Web Intelligence Rich Client designed for users who need to modify the formatting of reports and
analyze the data without being connected to the SAP BusinessObjects Business Intelligence
platform. For example, in situations where the user is travelling or working without an internet
connection. The application is installed on the users desktop.
Note: The Web Intelligence Rich Client is out of the scope of this sizing document, because this module
does not require system resources on the server side

1.1 Functions of SAP BusinessObjects Web Intelligence


Web Intelligence reports can be designed on any corporate data sources supported by BusinessObjects
universes (that is, OLAP, RDBMS and Web Services).

Users interact with Web Intelligence to perform the following actions:


run ad hoc queries
view reports
refresh data in existing reports
drill to detailed or aggregate data from the values displayed on reports
export reports to a different file format (PDF, MS Excel, CSV)
share reports with other users via the SAP BusinessObjects BI platform deployed at their
organization

Copyright/Trademark
3
Sizing SAP BusinessObjects Web Intelligence 4.0 - SAP Customers and Partners
__________________________________________________________________________________

1.2 Architecture of SAP BusinessObjects Web Intelligence


Web Intelligence has a three-tier architecture:
Client tier (that is, the browser for the DHTML Client or Java Report Panel, or the Web Intelligence
Rich Client installed on a users desktop).
Server tier (that is, the web server, web application server, BusinessObjects BI platform backend
including Adaptive Processing Server (APS), and Web Intelligence Processing Server)
Data Source tier (that is, the data sources upon which Web Intelligence document contents are
based, such as SAP BW, supported RDBMS and OLAP).
Note: The client tier and the data source tier are out of the scope of this sizing guide.

Graphic 1: Architecture of SAP BusinessObjects Web Intelligence

Copyright/Trademark
4
Sizing SAP BusinessObjects Web Intelligence 4.0 - SAP Customers and Partners
__________________________________________________________________________________

Note: For the purposes of this document, the server tier layer is detailed into two parts: (1) Web and
Web Application Server tier, (2) BusinessObjects Business Intelligence (BI) server tier.

This sizing guide provides information on the following layers :


Web and Web Application Server tier supported Web and Web Application Servers, such as
Apache, Tomcat, and IBM WebSphere etc.
BusinessObjects BI server tier consisting of :
o BI Reporting Engine Web Intelligence Report Processing Server
o BI backend (BI platform) layer Central Management Server (CMS), File Repository Servers
(FRS), Server Intelligence Agent (SIA), and CMS database (when deployed on SQL Server
Express)
o Adaptive Processing Server (APS) one of the new processes introduced to the BI platform
core services in version 4.0. Specifically for Web Intelligence, the APS is used for:
charts and graphs provided by the Common Visual Object Model component (CVOM)
the Semantic Layer (i.e., query generation, data and metadata definition and retrieval on
BusinessObjects universes and SAP BW - SAP BEx (DSL)
the data federation handling of multiple data providor sources into the universe by the SAP
BusinessObjects Data Federator component

Note: It is recommended that the APS be deployed on separate hardware, because certain data
sources require high memory consumption on the APS.

1.3 Factors that influence sizing


There are four major factors that affect Web Intelligence resource consumption:

1. Number of concurrent users and number of open documents


The higher the number of users, the more Web Intelligence requires system resources. This factor is
based on the assumption that each user is running a single Web Intelligence document. In a real-life
usage scenario, a single user session often has multiple documents running (for example, SAP
Business Objects BI 4.0 multi-tabs or Browser multi-tabs). Because of this, it is necessary to take into
account the number of open Web Intelligence documents instead of the number of users. Therefore, the
metric to apply when estimating Web Intelligence system resource requirements is the number of
concurrent running documents.

2. Document data volume and/or query and report complexity


In viewing mode, two additional factors impact Web Intelligence system resource usage:
data volume -- the larger the data volume the more Web Intelligence requires system resources
query complexity the more complex the query (for example, queries with multiple filters and sorts),
the more Web Intelligence requires system resources
In report editing mode, the following factor also impacts system resource usage:
complexity of the document structure (for example, documents that include the auto-fit setting, page
breaks, sorts, alerters, styles, sections, expand/collapse etc.) increases the amount of system
resources required by Web Intelligence when a report is generated

3. User operation types


The type of operation end-users perform and the frequency with which they perform those operations is
another factor that impacts Web Intelligence system resource usage. In addition, different operations
put load on different components in the Web Intelligence system. For example, opening a document
puts load on the Web Intelligence and web application server, whereas navigating in a document folder
puts load on the CMS and web application server. (Note: Opening documents can also benefit from the
Web Intelligence cache mechanism on the Web Intelligence server, which contributes to faster
performance with a lower consumption of resources.) Operations such as refresh can generate high
load on the persistence layer (such as relational database or OLAP data source) as well as Web
Intelligence. Exporting Web Intelligence documents to PDF format is another resource intensive
operation on the Web Intelligence Server.

Copyright/Trademark
5
Sizing SAP BusinessObjects Web Intelligence 4.0 - SAP Customers and Partners
__________________________________________________________________________________

4. Type of data provider


The way the data is retrieved into a Web Intelligence document is another factor that impacts
system resource usage:
Web Intelligence queries on SAP BW require a DSL Bridge service. DSL Bridge is a dedicated
connectivity between the Web Intelligence Report Processing Server and SAP Business
Warehouse (BW) and is hosted by the Adaptive Processing Server (APS).
Queries on multiple data sources via a BusinessObjects universe can consume higher system
resources on the APS than queries on a single data source, because this type of connectivity
requires a Data Federator service hosted by the APS.

In terms of end-user interactivity with Web Intelligence, document refresh is the principal operation that
requires the intervention of these connectivity services. Also, the larger the data volume retrieved by the
query definition, the higher the resource requirement on the APS.

2 SIZING FUNDAMENTALS AND TERMINOLOGY


SAP provides general sizing information on the SAP Service Marketplace. For the purpose of this guide,
we assume that you are familiar with sizing fundamentals. You can find more information at
http://service.sap.com/sizing Sizing Guidelines General Sizing Procedures.
This section explains the most important sizing terms, as these terms are used extensively in this
document.
Sizing
Sizing means determining the hardware requirements of an SAP application, such as the network
bandwidth, physical memory, CPU processing power, and I/O capacity. The size of the hardware and
database is influenced by both business aspects and technological aspects. This means that the
number of users using the various application components and the data load they put on the server
must be taken into account.
Benchmarking
Sizing information can be determined using SAP Standard Application Benchmarks and scalability
tests (www.sap.com/benchmark). Released for technology partners, benchmarks provide basic sizing
recommendations to customers by placing a substantial load upon a system during the testing of new
hardware, system software components, and relational database management systems (RDBMS). All
performance data relevant to the system, user, and business applications are monitored during a
benchmark run and can be used to compare platforms.
SAPS
The SAP Application Performance Standard (SAPS) is a hardware-independent unit that describes the
performance of a system configuration in the SAP environment. It is derived from the Sales and
Distribution (SD) Benchmark, where 100 SAPS is defined as the computing power to handle 2,000 fully
business processed order line items per hour. (For more information about SAPS, see
http://www.sap.com/benchmark Measuring in SAPS).
Initial Sizing
Initial sizing refers to the sizing approach that provides statements about platform-independent
requirements of the hardware resources necessary for representative, standard delivery SAP
applications. The initial sizing guidelines assume optimal system parameter settings, standard business
scenarios, and so on.
Expert Sizing
This term refers to a sizing exercise where customer-specific data is being analyzed and used to put
more detail on the sizing result. The main objective is to determine the resource consumption of
customized content and applications (not SAP standard delivery) by comprehensive measurements. For
more information, see http://service.sap.com/sizing Sizing Guidelines General Sizing
Procedures Expert Sizing.
Configuration and System Landscaping
Hardware resource and optimal system configuration greatly depend on the requirements of the
customer-specific project. This includes the implementation of distribution, security, and high availability
solutions by different approaches using various third-party tools. In the case of high availability through
redundant resources, for example, the final resource requirements must be adjusted accordingly.

Copyright/Trademark
6
Sizing SAP BusinessObjects Web Intelligence 4.0 - SAP Customers and Partners
__________________________________________________________________________________

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

3 INITIAL SIZING FOR SAP BUSINESSOBJECTS WEB


INTELLIGENCE

3.1 Assumptions
The sizing guidelines in this document are based on the assumptions provided in this section.
Note: a different assumption results in a different guideline, so the numbers below might not be
applicable to all use cases.

For the purposes of this sizing guide, four user profiles are allocated to usage patterns commonly
performed by different types of Web Intelligence end users:

Information Consumer: opens and navigates reports to view data


Information Worker: refreshes reports to view the latest values
Data Analyst: drills to detailed and aggregated values to perform root cause analysis
Line Of Business (LOB) Manager: captures snapshot of results in a PDF version of a report to share
with internal stakeholders

3.1.1 Viewing Web Intelligence documents with queries on RDBMS

Mixed user profiles where Information Consumers = 70%, Information Workers = 5%, Data Analysts
= 20 %, LOB Managers = 5% of total user population. Each profile consists of the following scenario
(weight of the steps per iteration1i in %) :
o Information Consumers - Login (10%) + Open and Report Navigation (90%)
o Information Workers - Login (10%) + Open (18%) + Refresh (72%)
o Data Analysts - Login (10%) + Open (18%) + Drill (72%)
o LOB Managers - Login (10%) + Open (18%) + ExportPDF (72%)

Think time2ii 45 seconds between each action (mouse click)


Document characteristics: DP size 7,000 rows consisting of 2 sub-reports: 1st report 25 sections, 25
charts and tables, 72 pages. 2nd report 5 sections, 5 charts and tables, 1 page.
Data provider: relational database via BusinessObjects universe (.unv), single source
Web Intelligence report viewer : DHTML
BI platform setting - Auditing off. Platform Search Indexing stopped.
Specific parameters
o Web Intelligence parameter Maximum Connection 300
o Web Server (Tomcat6) Max Thread 500

In terms of typical hardware in an enterprise scale deployment of SAP BusinessObjects BI 4.0, a node
in an SAP BusinessObjects BI 4.0 cluster would typically be an 8 core machine with 16 GB minimum or
equivalent. See the Sizing Companion for SAP BusinessObjects BI 4.0 (SP0) at:
http://www.service.sap.com/sizing Sizing Guidelines Solutions & Platform New Structure
SAP BusinessObjects Sizing SAP BusinessObjects BI 4.0 - Companion

3.1.2 Web Intelligence viewing with queries on SAP BW BEx

The difference of the sizing assumption from that of the RDBMS above is the user profile distribution,
queries, and the Web Intelligence report contents. In terms of sizing, it is the Refresh operation that
makes the principal difference because of the supplementary cost related to the DSL Bridge in APS, as
previously mentioned.

The sizing of Web Intelligence 4.0 is influenced more by the data volume than by the query complexity.
Concerning the BEx query performance tuning.

Copyright/Trademark
7
Sizing SAP BusinessObjects Web Intelligence 4.0 - SAP Customers and Partners
__________________________________________________________________________________

Mixed user profiles where Information Consumers = 70%, Information Workers = 10%, Data
Analysts = 15 %, LOB Managers = 5% of total user population. Each profile consists of the following
scenario (weight of the steps per iteration in %) :
o Information Consumers - Login (10%) + Open and Report Navigation (90%)
o Information Workers - Login (10%) + Open (18%) + Refresh (72%)
o Data Analysts - Login (10%) + Open (18%) + Drill (72%)
o LOB Managers - Login (10%) + Open (18%) + ExportPDF (72%)

Document characteristics: 9 variations: three Web Intelligence documents, each of which are
designed on a query of differing complexity: Simple (Q1), Fairly Complex (Q2) and Complex (Q3).
Each document has 3 different data volumes Small, Medium, and Large :

o Small = 40,000 cellsiii


o Medium = 400,000 cells
o Large = 1 million cells

Summary of the characteristics of 9 Web Intelligence reports based on SAP BW:


Query type Q1 (Simple) Q2 (Fairely Complex) Q3 (Complex)
# of characteristics 5 10 10
# of Key Figures 5 8 15
# of hierarchies 0 3 3
# of variables 0 5 6
# cells (K) 40 400 1,000 40 500 1,000 40 500 1,000
# rows 3,950 39,666 99,643 2,452 28,123 56,789 1,788 20,138 41,263

3.2 Sizing guideline


The following initial sizing guideline that follows in this document is derived from the assumptions
detailed above.

Please contact your hardware vendor to find out the SAPS of your hardware. A list of SAP SD
Benchmark certifications is available at: http://www.sap.com/solutions/benchmark/sd2tier.epx

Examples of SAPS for typical hardware: a server with 4 CPU/Core has a capacity of 4890 SAPS (for a
processor released in 2007); a server with 8 CPU/Core has a capacity of 11240 SAPS (for a processor
released in 2009).

Copyright/Trademark
8
Sizing SAP BusinessObjects Web Intelligence 4.0 - SAP Customers and Partners
__________________________________________________________________________________

3.2.1 Web Intelligence viewing with queries on RDBMS

Category for
Enterprises CPU requirements in SAPS Minimum Memory requirements in GB
in number of
concurrent
users Web Web
WebIntelligence BI WebIntelligence BI
App APS App APS
Server Platform Server Platform
Server Server

50 600 1100 400 100 1 1 1 2

100 1200 2200 800 200 2 2 2 2

300 3600 6600 2400 600 6 6 6 6

More than 300 Please contact SAP or your hardware partner

3.2.2 Web Intelligence viewing with queries on SAP BW - BEx

The sizing guideline for this stack is presented in three tables separately by the data volume, 40,000
cells, 500,000 cells, and 1 million cells.

The memory size of APS (for DSL Bridge) is derived by the following assumption:
Memory size used by each query x number of users refreshing reports (i.e. number of queries) divided
by 2, assuming that 2 queries are simultaneous. In the case of 100 concurrent users, 10% of them are
running refresh, which means 10 / 2 = 5 concurrent queries.

Another 1GB is added to cover the other APS services such as CVOM, Data Federator, and Monitoring.

40,000 cells:
Category for
CPU requirements in SAPS Minimum Memory requirements in GB
Enterprises
in number of
concurrent
users Web App WebIntelligence BI Web App WebIntelligence BI
APS APS
Server Server Platform Server Server Platform

50 700 1150 500 100 1 1 2 2

100 1300 2300 1000 200 2 2 3 2

300 4000 6900 3000 600 6 6 6 6

More than 300 Please contact SAP or your hardware partner

Copyright/Trademark
9
Sizing SAP BusinessObjects Web Intelligence 4.0 - SAP Customers and Partners
__________________________________________________________________________________

500,000 cells:
Category for
CPU requirements in SAPS Minimum Memory requirements in GB
Enterprises
in number of
concurrent Web App WebIntelligence BI Web App WebIntelligence BI
APS APS
users Server Server Platform Server Server Platform

50 700 1350 650 200 1 1 2 2

100 1300 2700 1300 400 2 2 3 2

300 4000 8000 3900 1200 6 6 9 6

More than 300 Please contact SAP or your hardware partner

1 million cells:
Category for
CPU requirements in SAPS Minimum Memory requirements in GB
Enterprises
in number of
concurrent Web App WebIntelligence BI Web App WebIntelligence BI
APS APS
users Server Server Platform Server Server Platform

50 700 1500 1300 300 1 1 2 2

100 1300 3000 2600 600 2 2 4 2

300 4000 9000 7600 1800 6 6 12 6


More than 300 Please contact SAP or your hardware partner

Copyright/Trademark
10
Sizing SAP BusinessObjects Web Intelligence 4.0 - SAP Customers and Partners
__________________________________________________________________________________

CPU Sizing - Webi on BEx


25000

20000

15000
SAPS

10000

5000

0
50 100 300 50 100 300 50 100 300
users users users users users users users users users
40K cells 500K cells 1000K cells
Web App Server 700 1300 4000 700 1300 4000 700 1300 4000
WebIntelligence Server 1150 2300 6900 1350 2700 8000 1500 3000 9000
APS 500 1000 3000 650 1300 3900 1300 2600 7600
BI Platform 100 200 600 200 400 1200 300 600 1800

4 MISCELLANEOUS
For further information related to Web Intelligence sizing, see:
Sizing Companion for SAP BusinessObjects BI 4.0 (SP0) (see:
http://www.service.sap.com/sizing Sizing Guidelines Solutions & Platform New
Structure SAP BusinessObjects Sizing SAP BusinessObjects BI 4.0 Companion)
SAP BusinessObjects Web Intelligence 4.0 product documentation for administrators and users
(see: http://help.sap.com/content/bobj/bi/web_intelligence.htm#4)
SAP NetWeaver Business Warehouse documentation: (see:
http://help.sap.com/saphelp_nw70/helpdata/en/0a/fad542d304db1ae10000000a1550b0/frames
et.htm)

5 COMMENTS AND FEEDBACK


Comments and feedback are very welcome; please send them to Yumiko Hata, SAP Labs France,
yumiko.hata@sap.com
i
Iteration refers to the series of user operations taken between login and logout.
ii
Think time refers to the time spent by the user to read the results of an operation on the client front end before
requesting another operation that triggers a server event; for example, the time between opening a Web
Intelligence document and clicking Refresh.
iii
The number of cells counted when you represent the entire Web Intelligence micro cube by a flat table and export
it to Excel.

Copyright/Trademark