SAP BPC 7.
0 NW Configuration
Guide
Configuration Guide
SAP Business Planning and Consolidation 7.0
version for SAP NetWeaver
Target Audience
Technical Consultants
System Administrators
ADDONX.CG_BPC
Release 2007
PUBLIC
Document version: 1.1 – 07/28/2009
Copyright
© Copyright 2009 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, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z,
System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390,
OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+,
POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System
Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX,
Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM
Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of
Adobe Systems Incorporated 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.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, 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 other countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web
Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their
respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and
in other countries. Business Objects is an SAP company.
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.
(C) SAP AG BPC 7.0 NW Configuration Guide 2
Icons in Body Text
Icon Meaning
Caution
Example
Note
Recommendation
Syntax
Additional icons are used in SAP Library documentation to help you identify different types of
information at a glance. For more information, see Help on Help General Information Classes
and Information Classes for Business Information Warehouse on the first page of any version of
SAP Library.
Typographic Conventions
Type Style Description
Example text Words or characters quoted from the screen. These include field
names, screen titles, pushbuttons labels, menu names, menu paths,
and menu options.
Cross-references to other documentation.
Example text Emphasized words or phrases in body text, graphic titles, and table
titles.
EXAMPLE TEXT Technical names of system objects. These include report names,
program names, transaction codes, table names, and key concepts of a
programming language when they are surrounded by body text, for
example, SELECT and INCLUDE.
Example text Output on the screen. This includes file and directory names and their
paths, messages, names of variables and parameters, source text, and
names of installation, upgrade and database tools.
Example text Exact user entry. These are words or characters that you enter in the
system exactly as they appear in the documentation.
<Example text> Variable user entry. Angle brackets indicate that you replace these
words and characters with appropriate entries to make entries in the
system.
EXAMPLE TEXT Keys on the keyboard, for example, F2 or ENTER.
(C) SAP AG BPC 7.0 NW Configuration Guide 3
Table of Contents
Server Configuration................................................................................................................5
Modifying Machine.config Files.............................................................................................5
Setting COM+ Object Application Pooling Pool Size .............................................................6
Miscellaneous Server Options ..............................................................................................7
ABAP Configuration..............................................................................................................7
Client Configuration .................................................................................................................8
Client Options.......................................................................................................................8
BPC Performance Management...............................................................................................9
BPC Processing Tiers ..........................................................................................................9
Cube Fact Tables...............................................................................................................10
Cube Optimization..............................................................................................................10
Cube Modification...............................................................................................................10
Writeback Parameters ........................................................................................................11
SQE Parameters ................................................................................................................11
(C) SAP AG BPC 7.0 NW Configuration Guide 4
Server Configuration
You configure the Business Planning and Consolidation .NET Web and Application server to
ensure that it and its related services function properly and reliably.
Procedure
You modify the machine.config file.
This ensures that there is a balance between the number of threads “working” requests
and deadlock occurrences that would prevent the application server from processing.
See Modifying Machine.config Files [Page 5].
You set the application pooling pool size for the COM+ objects. See Setting COM+
Object Application Pooling Pool Size [Page 6].
You configure Internet Information Services (IIS) to set memory recycling in an
application pool. See Setting Memory Recycling in the IIS Application Pool.
You can increase the memory size to handle larger data regions. See Setting 3GB
Support for Memory on the COM+ Object.
Modifying Machine.config Files
To ensure that the right balance is struck between the number of threads “working” requests and
deadlock occurrences that would cause the application server to “sleep” and not process
anymore, you can modify the machine.config file, which resides in the
\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Config\ directory.
Procedure
1. Set both the <maxWorkerThreads> and <maxIOTheads> to 100 as follows:
<ProcessModel
,,,, (Other settings)
maxWorkerThreads="100"
maxIoThreads="100"
/>
2. Adjust <minFreeThreads> such that its value is equal to that of multiplying the factor 88
to that of the number of CPUs on the server (i.e., minFreeThreads=88 x # of CPU).
Similarly adjust <minLocalRequestFreeThreads> such that its value is equal to that of
multiplying the factor 76 to that of the number of CPUs on the server (that is,
minLocalRequestFreeThreads=76 x # of CPUs).
Finally, make sure that the value of <appRequestQueueLimit> is increased to 500.
(C) SAP AG BPC 7.0 NW Configuration Guide 5
Assuming a server with two processors, here is an example:
<httpRuntime
minFreeThreads="176"
minLocalRequestFreeThreads="152"
appRequestQueueLimit="500"
/>
3. Set <machineKey> options properly.
The <machineKey> tag in web.config or machine.config tells the .NET framework how to
create the hash on forms tickets (which is the proof that you have been authenticated).
The default is for each web application to create its own hash key. So, if you took your
authentication cookie created on one machine and try to access another machine, it
would fail when checking the hash code to make sure it hadn’t been tampered.
Therefore, if you are using a web farm (multiple web servers where you can automatically
be routed to any one of them within a particular session), the hash key needs to be the
same on all the machines. This way, when the authentication cookie is checked, the
authentication ticket used on one web server can still be valid on another server. Note
that this is a requirement for the web servers, not the application server. You can specify
it for just the BPC IIS application in its web.config file; you do not have to specify it for all
IIS applications in the general machine.config file. If you are not using a web farm, you do
not need to change the <machineKey> element.
4. If using a deployment where the web servers do not reside on the same servers as the
Application servers, adjust HTTP TCP/IP connections settings in the machine.config file
of the web server(s) as follows:
<connectionManagement>
<add address=”app server ip” maxconnection=”48”/>
<add address="*" maxconnection="2"/>
</connectionManagement>
Setting COM+ Object Application Pooling Pool Size
For load balancing purposes, set the application pooling pool size for the COM+ components
OsoftLogging, OsoftUserManage, and OsoftWebFileManage.
Procedure
1. Choose Start >Administrative Tools > Component Services > COM+ applications.
2. Right-click the application.
3. Choose Properties, then on the Pooling & Recycling tab, change the application pool size
to 4.
(C) SAP AG BPC 7.0 NW Configuration Guide 6
Miscellaneous Server Options
You can set a number of server options in the Server Manager. These settings are used by
server diagnostics, and should mirror those in Microsoft IIS web.config. For more information, see
the Server Manager documentation on the Service Marketplace at
http://service.sap.com/instguidesEPM-BPC.
Activities
To set server options in Server Manager, choose > Options > Server Options.
ABAP Configuration
You should ensure that SAP NetWeaver 7.0 Enhancement Package 1 is properly installed and
configured before setting up BPC. For more information, see the NetWeaver documentation on
the Service Marketplace at http://service.sap.com/instguides > SAP Netweaver > SAP Netweaver
7.0 (2004s) > Installation Guide.
(C) SAP AG BPC 7.0 NW Configuration Guide 7
Client Configuration
Client Options
In BPC Server Manager, you can set the following client options:
Option Description
Client Auto Update Used to update support patches.
Enable server to be
This option, when selected, ensures that all users are challenged for
Sarbane-Oxley
a user name and password when they attempt to access the server.
compliant
Microsoft XML version This allows you to specify files for an XML parser. Recommended:
number Do not change this setting.
Activities
To set client options in Server Manager, choose > Options > Client Options.
(C) SAP AG BPC 7.0 NW Configuration Guide 8
BPC Performance Management
A number of factors affect BPC performance, including the following:
Number of dimension members
Amount of transactional data in a given application
Number of concurrent users
Hardware
Network bandwidth
BPC Processing Tiers
To optimize BPC performance, it is useful to understand the tiers comprised by BPC, and the
processing that occurs on those tiers. The following table outlines these tiers:
Tier Description
The following processes occur at the database level:
Data reads
Data write-backs
Write-back performance is primarily affected by work
Database status locks, the validation framework, concurrency
lock parameters, and the security model.
Metadata reads and writes
Application file storage (book repositories, report and input
templates, unstructured data, conversion files, and
transformation files)
The following processes occur at the application server level:
NetWeaver Script logic, calculations, and MDX parsing
ABAP
Parameter-driven logic
Application
Server Data Manager loads and ETL (extraction, transform, load)
OLAP engine and calculations
The following processes occur at the web server level:
Microsoft IIS User authentication
Web and
Appliction Server Web Service request parsing and processing
BPC Web
(C) SAP AG BPC 7.0 NW Configuration Guide 9
BI Accelerator
The BI Accelerator can be used to eliminate database read times
(optional
through the use of in-memory storage.
component)
Cube Fact Tables
Each InfoCube has the following two fact tables:
E fact table, for compressed records
F fact table, for uncompressed records
Records are automatically compressed during the optimization process (zero elimination is not
used).
For more information about modifying and scheduling optimization process chains, see the
http://service.sap.com/instguidescpm-bpc > 7.0, version for NetWeaver > SAP BPC 7.0 Data
Manager Guide.
For more information about optimization process chains, see the
http://service.sap.com/instguidescpm-bpc > 7.0, version for NetWeaver > SAP BPC 7.0 Data
Manager Guide.
Cube Optimization
Optimizations have been implemented as process chains. As such, you can schedule them using
Data Manager or execute them using Administration.
For more information about modifying and scheduling optimization process chains, see the
http://service.sap.com/instguidescpm-bpc > 7.0, version for NetWeaver > SAP BPC 7.0 Data
Manager Guide.
For more information about executing optimization process chains, see the
http://service.sap.com/instguidescpm-bpc > 7.0, version for NetWeaver > SAP BPC 7.0
Administration Guide.
Cube Modification
During the optimization process, BPC will create a shadow cube and move the data to that cube
when the system determines a data model reorganization is needed (for performance reasons).
Any external modifications made to the cube (for example, through transaction RSA1) will be lost,
and will not be moved with the data. These modifications include such things as tablespaces, BI
Accelerator indexes, DTPs (distributed transaction processing), aggregates, and database
performance parameters.
(C) SAP AG BPC 7.0 NW Configuration Guide 10
Writeback Parameters
You can modify writeback parameter values in transaction UJRO. These values are maintained at
the individual application level. In general, you will not need to change the default values. They
are described in the following table:
Parameter Default Description
This specifies the size into which packages are divided during
PACKAGE_SIZE 40000
the writeback process.
If (the number of dimensions multiplied by the number of unique
members in each dimension) is greater than (number of records
SPARSITY_COEF 5
multiplied by the this value), then the record set is considered
sparse.
If the number of records being saved is less records than or
RECLEVEL_NR 10
equal to this value, record-based locking will be implemented.
In the situation where record-level locking is not being
implemented and a sparse data set is being saved, this value
MULTIPLY_COEF 50 specifie the maximum number of members for which you can
implement record level locking (that is, when to swap to using a
BETWEEN range in the lock table).
In the situation where record level locking is not being
implemented and the data set being saved is NOT sparse, any
dimensions with less than this number of distinct member
INTERVAL_NR 10
values in the dataset will be locked using their single values. If
the dimension has more than this number of records, the range
between the low to high values will be locked.
SQE Parameters
You can modify SQE parameter values in transaction UJQ0. These values are maintained at the
individual application level. In general, you will not need to change these values. They are
described in the following table:
Parameter Default Description
If (the number of dimensions multiplied by the number of
unique members in each dimension) is greater than (number
SPARSITY_COEF 5
of records multiplied by this value), then the record set is
considered sparse.
(C) SAP AG BPC 7.0 NW Configuration Guide 11
