Sbop Pc 10 m Install

5/26/2018 Sbop Pc 10 m Install

1/54

Installation Guide

SAP BusinessObjects Planning and Consolidation 10.0version for the Microsoft platform

Target Audience

Technical Consultants

System Administrators

CUSTOMERDocument version: 1.70 2014-04-02


2/54

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +49/18 05/34 34 34

F +49/18 05/34 34 20www.sap.com

Copyright 2014 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.

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, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere,Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered

trademarks of IBM Corporation.

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.

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

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

Any Java Source Code delivered with this product is only to be used by SAPs Support Services and may not be modified or

altered in any way.

Documentation in the SAP Service Marketplace

You can find this document at the following address: http://service.sap.com/instguidesEPM-BPC.

2/54 CUSTOMER 2014-04-02
http://service.sap.com/instguidesEPM-BPC.http://service.sap.com/instguidesEPM-BPC.


3/54

Document History

The following table provides an overview of the most important document changes.

Version Date Description

1.0 2012-01-31 Accompanies the General Availability release.

1.1 2012-03-05 Revised chapters Installing the Anti-Cross Site Scripting Library and Installing

on a Single Server.

Added chapter Using Client Certificates.

1.15 2012-03-30 Added SAP Note 1665656 for SP6 to SAP Notes for the Installation.1.20 2012-04-03 In the topic Installing the Server in a Multiserver Configuration added the

recommendation to use a round robin approach to assign resources for load

balancing.

1.25 2012-04-30 In the topic Installing the Prerequisites Basic Steps added that we do not

recommend installing Microsoft Office on the application server. Also, removed

the note at the end of the procedure that discussed launching the installation of a

Microsoft ACE OLEDB Provider on a machine with a Microsoft Office installation.

1.30 2012-06-07 Modified the document to incorporate SQL Server 2012 support within support

package 7.

1.35 2012-06-08 Additional modifications for SQL Server 2012 support within support package 7.

1.36 2012-06-11 Updated the location of the machine.config file in the topic Configuring the

Planning and Consolidation .NET Application Servers.

1.37 2012-06-13 Updated .NET 2.0 to .NET 4.0 in the topic Configuring the Planning and

Consolidation .NET Application Servers.

1.38 2012-10-17 Improved the installation procedure in the topic Installing on a Single Server.

1.39 2012-12-05 Changes in the topics Prerequisites and Installing the Prerequisites Basic Steps

updated the required version of Microsoft Visual C++ and vcredist_x64.exe.

1.4 2013-04-30 Updated the topic Installing the Administration Client[page 37] with versions of Microsoft

Internet Explorer and Microsoft Office supported as of support package 10.

1.5 2013-09-09 Updated the topic SAP Notes for the Installation with the central note number

for support package 11.

1.6 2013-10-17 Updated the topic Proxy Server and Firewall Issues[page 41] with a note to refer to SAP

Note 1505250 for information about firewall ports.

1.65 2014-01-10 Updated the topic SAP Notes for the Installation with the central note number

for support package 12.

1.70 2014-04-02 Added topics about configuring SSL in IIS and in SQL Server Reporting Services.

2014-04-02 CUSTOMER 3/54


4/54

Table of Contents

Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1.1 SAP Notes for the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1.2 Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Chapter 2 Installing Planning and Consolidation Servers . . . . . . . . . . . . . . . . . . . . . . 9

2.1 Basic Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2.2 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2.3 Before Starting the Planning and Consolidation Server

Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.4 Logging on to Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

2.5 Service-level Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2.6 Standard and Advanced Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2.7 Installing the Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2.7.1 Installing the Prerequisites Basic Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2.7.2 Installing the Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

2.7.3 Installing the SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

2.7.4 Installing Analysis Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

2.7.5 Installing the Anti-Cross Site Scripting Library . . . . . . . . . . . . . . . . . . . . . . . . 22

2.8 Installing on a Single Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

2.9 Installing the Server in a Multiserver Configuration . . . . . . . . . . . . . . . . . . . . 24

Chapter 3 After Installing Planning and Consolidation Servers . . . . . . . . . . . . . . . . 25

3.1 Post-Installation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253.2 Connecting to Solution Manager Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . 26

3.3 Configuring the Planning and Consolidation .NET Application

Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

3.4 Post-Installation: Optional Configuration Steps . . . . . . . . . . . . . . . . . . . . . . . . 28

3.4.1 Enabling the Management Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

3.4.2 Setting Up ODBC Logging in IIS for the Default Web Site . . . . . . . . . . . . . . . . 29

3.4.3 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server

2008 R2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

4/54 CUSTOMER 2014-04-02


5/54

3.4.4 Removing Default Access to the Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

3.4.5 Management Console Access Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

3.4.6 Configuring Planning and Consolidation to use SSL . . . . . . . . . . . . . . . . . . . . 32

3.4.7 Using Client Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

3.4.8 Configuring MS SQL Server Reporting Services to use SSL . . . . . . . . . . . . . . . 34

Chapter 4 Installing Planning and Consolidation Administration Client and the

SAP BusinessObjects EPM solutions, Add-in for Microsoft

Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

4.1 Installing the Administration Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

4.2 Installing the EPM Add-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

4.3 Using the Client Auto Update Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Chapter 5 Connection Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

5.1 Checking for Open Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

5.2 Proxy Server and Firewall Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Chapter 6 Installing Planning and Consolidation with Two Active Directory

Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Chapter 7 Installing Planning and Consolidation in a Terminal Services or CitrixServer Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

7.1 Terminal Services Home Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

7.2 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

7.3 Installing Planning and Consolidation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

7.4 Creating a Shortcutto the Launch Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Chapter 8 Installing SSIS Custom Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

8.1 Composition of SSIS Custom Task Installation . . . . . . . . . . . . . . . . . . . . . . . . 47

8.2 Before You Modify the SSIS Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

8.3 Setup of a COM+ Application on the Application Server . . . . . . . . . . . . . . . . . 51

2014-04-02 CUSTOMER 5/54


6/54

This page is left blank for documentsthat are printed on both sides.


7/54

1 Introduction

The SAP BusinessObjects Planning and Consolidation Installation Guide is intended for System

Administrators who perform Planning and Consolidation server and Administration client

installations. It contains everything you need to know about installing the prerequisite components

and the server and client software.

The installation package contains a full installation program. While we do not offer a software upgrade

for this release, we provide detailed instructions on how to migrate your existing environments. For

more information, see the Upgrade Guide, which is available on SAP Service Marketplace at http://

service.sap.com/instguidesEPM-BPC Planning and Consolidation 10.0, version for the Microsoft platform .

For more information about the Planning and Consolidation Office client software, see the SAP

BusinessObjects EPM solutions, add-in for Microsoft Officehelp.

New Installation Program Features in 10.0

The following items are new to the installation program for Planning and Consolidation:

Planning and Consolidation supports all available operating system languages for all servers

(Application, File, OLAP, and SQL):

Planning and Consolidation supports full 64-bit deployment on all server components

Planning and Consolidation supports VMWare based installation

Planning and Consolidation supports Citrix XenApp Enterprise and Platinum installed on

Windows Server 2008 or Windows Server 2008 R2 for remote desktop access

Planning and Consolidation no longer requires a separate Web server; only an application server.

You can install the application server on a single machine or on multiple machines with network

load balancing (NLB). If you use the NLB option, you can choose on which machine to install the

sample environment.

1.1 SAP Notes for the Installation

Read the following SAP Notes before you start the installation. These SAP Notes contain the most

recent information on the installation, as well as corrections to the installation documentation. Make

sure that you have the up-to-date version of each SAP Note, which you can find in the SAP Service

Marketplace at the Internet address http://service.sap.com/notes.

SAP Note Number Title Comments

1584890 Documentation Addendum Contains information that does not yet appear inthe application help of Business Planning and

1 Introduction

1.1 SAP Notes for the Installation

2014-04-02 CUSTOMER 7/54
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1584890&_NLANG=en&_NVERS=0http://service.sap.com/noteshttp://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1584890&_NLANG=en&_NVERS=0http://service.sap.com/noteshttp://service.sap.com/instguidesEPM-BPChttp://service.sap.com/instguidesEPM-BPC


8/54

SAP Note Number Title Comments

Consolidation 10.0, version for the Micrososft

platform.

1897745 Planning & Consolidation 10 for

Microsoft SP12 Central Note

This note contains important information about

the installation of support package 12.








































the installation of support package 2.1573539 Planning & Consolidation 10 for




1.2 NamingConventions

In this document, the following naming conventions apply.

Variable Description

Server name or IP address and port number of SAP Planning and Consolidation application

location.

The drive where SAP Planning and Consolidation is installed.

The default for this is C:/PC_MS.

1 Introduction

1.2 Naming Conventions

8/54 CUSTOMER 2014-04-02
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1601213&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1573539&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1591848&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1601213&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1620464&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1643037&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1665656&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1689792&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1733053&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1755355&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1804918&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1846917&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1897745&_NLANG=en&_NVERS=0


9/54

2 Installing Planning and ConsolidationServers

This section includes the basic steps for installing a Planning and Consolidation server, the prerequisites,

and what to do before, during, and after the server installation.

2.1 Basic Steps

To install a Planning and Consolidation server, follow the steps outlined below:

1. Determine your server configuration. For guidelines, see the SAP Planning and Consolidation Master

Guideat http://service.sap.com/instguidesepm-bpc 10.0, version for the Microsoft platform .

2. Perform the tasks in the Before Starting the Planning and Consolidation Server Installation[page 11] section,

including installing all prerequisites.

3. From the application server, install the Planning and Consolidation server. See Installing Planning and

Consolidation on a Single Server[page 22].

NOTE

You mustinstall both Planning and Consolidation 10.0 as well as the most recent Planning

and Consolidation 10.0 Support Package available from the SAP Service Marketplace at

http://service.sap.com/swdc Software Downloads Support Packages and Patches A - Z Index

B SAP BPC FOR MICROSOFT SBOP PC 10.0 FOR MICROSOFT Comprised Software Component

Versions SAP CPM BPC 10.0 M Windows Server on x64 64bit .

4. If you have multiple machines, see Installing the Server in a Multiserver Configuration[page 24].

5. Perform the steps in the section After Installing Planning and Consolidation Servers[page 25].

2.2 Prerequisites

The following table describes the software you need to install before installing the Planning and

Consolidation server, and the minimum versions required.

NOTE

A list of the supported operating systems and database systems is also available in the Product

Availability Matrix on SAP Service Marketplace at http://service.sap.com/pam. Search on

Planning and Consolidation.

2 Installing Planning and Consolidation Servers

2.1 Basic Steps

2014-04-02 CUSTOMER 9/54
http://service.sap.com/pamhttp://service.sap.com/swdchttp://service.sap.com/instguidesepm-bpc


10/54

Component Minimum Requirement

Operating System The requirements outlined below are for the following operating systems:

Windows Server 2008 (64-bit) Standard, Enterprise, or Data Center with

or without Hyper-V

Windows Server 2008 R2 (64-bit) Foundation, Standard, Enterprise, orData Center with or without Hyper-V

NOTE

The operating system must be configured with NTFS.

Relational Database Microsoft SQL Server 2008 Enterprise Edition

Microsoft SQL Server 2008 R2 (Gemini) Enterprise Edition

Microsoft SQL Server 2012 Enterprise Edition

OLAP Database Microsoft SQL Server 2008 Enterprise Edition Analysis Server

Microsoft SQL Server 2008 R2 Enterprise Edition Analysis Server

Microsoft SQL Server 2012 Enterprise Edition Analysis Server

Data Integration Microsoft SQL Server 2008 Enterprise Edition SQL Service Integration

Services

Microsoft SQL Server 2008 R2 Enterprise Edition SQL Service

Integration Services

Microsoft SQL Server 2012 Enterprise Edition SQL Service Integration

Services

Other Requirements MSXML 4.0 SP2 or later

ADOMD.NET:

ADOMD.NET 10.0 when running SQL Server 2008 or 2008 R2

ADOMD.NET 11.0 when running SQL Server 2012

SQL Server software components

.NET 4.0

IIS 7.5 or IIS 7.0

(Included in your Operating System. IIS 7.5 is required for Windows 2008

R2 editions.)

Anti-Cross Site Scripting Library 4.2

This component must be downloaded before installing the server. The

server installation program asks for the path of each file and copies the

files into the appropriate Planning and Consolidation path.

Microsoft Visual C++ 2010 SP1 Redistributable Package (x64)

Microsoft Access Database Engine 2010 64bit

VMWare ESX 3.x or ESX 4.0

(Required only if a landscape deployment strategy using virtualizationtechnologies is planned.)

NOTE

MSXML 4.0 SP2, ADOMD.NET 10.0, and Microsoft Visual C++ 2010 SP1

Redistributable Package (x64) are included with the installation

program, but not installed automatically.

RECOMMENDATION

For SQL Server 2008 only, we recommend the installation of Microsoft SQL Server 2008 SP1

(or later) cumulative update package 6 or higher to solve a problem with incorrect periodic


2.2 Prerequisites

10/54 CUSTOMER 2014-04-02


11/54

values being returned with calculated accounts. For more information, see SAP Note number

1429246, which also contains download information.

We recommend SQL Server 2008 (or R2) Enterprise Edition or SQL Server 2012 Enterprise

Edition for the OLAP database to support proactive cache and cube partitioning. It is

technically possible to use SQL Server 2008 (or R2) Standard Edition or SQL Server 2012

Standard Edition for data integration servers, but we do not recommend this.

2.3 Before Starting the Planning and Consolidation ServerInstallation

You must perform the following tasks before starting your Planning and Consolidation server

installation:

Install all the prerequisite software, including all of the latest Microsoft hotfixes. For more

information, see Installing the Prerequisites[page 15].

If you access your application through a firewall, verify with your network administrator which

TCP ports to choose during the installation. By default, port 80 is the setting for standard http

access, and port 443 is the setting for https access. If you require a service to listen on a different

port, you can specify it during the installation program in Advanced Settings.See Standard and Advanced

Settings[page 14].

Make sure all required server ports are open, and that there is communication between the physicalservers on which you are going to install the server types. See Checking for Open Ports[page 41].

Set up the required service accounts that you need to install the Planning and Consolidation server.

See Service-Level Accounts[page 13].

The sample environment, EnvironmentShell, has been updated in this version of Planning and

Consolidation, and automatically overwrites the previous version. If you have made any

modifications to EnvironmentShell that you want to keep, make a copy of it before continuing

with the installation.

If you have the URLScan and IIS Lockdown tools installed on your application server, you must

reinstall them.

Disable your anti-virus software program. After the installation, when you enable the program,

turn off Script Blocking.

If a version of Planning and Consolidation on a NetWeaver platform exists, uninstall it before you

install Planning and Consolidation 10.0, version for the Microsoft platform.

Do not install the FileShare server type on a domain controller.

Configure your server for NTFS, which is required. To convert to NTFS (from FAT), at a command

prompt enter: convert c: fs:ntfs/V.

All servers in a multiserver environment must be members of the same domain.


2.3 Before Starting the Planning and Consolidation Server Installation

2014-04-02 CUSTOMER 11/54
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1429246&_NLANG=en&_NVERS=0


12/54

In a multiserver environment, the installing ID must be a domain user ID. We recommend that

you do not log on to the servers using a local server user ID, even if the user ID is a member of the

Administrator group on the server. This way you have the proper authority to install software and

to modify the Component Services. See Logging On to Servers[page 12].

You must determine the IP addresses or server names for all servers before installing Planning and

Consolidation. We recommend that you use static IP addresses.

IIS must be enabled.

If the application server is not able to copy files to the database server during the installation because

of port access reasons (DMZ, WORKGROUP, or nontrusted domain authentication failures), do

the following:

1. Copy the EnvironmentShell database file, Server\EnvironmentShell.db10, from the

Planning and Consolidation installation program to any folder on the SQL server (for example,c:\EnvironmentShell.db10).

Make sure that the SQL instance Service Account has read, write and update permissions on

the file.

2. During the installation procedure (on the Server Informationpage), specify the location of the

EnvironmentShell database file in the Server Information Advanced Options Local path for

EnvironmentShell DB field (for example, c:\EnvironmentShell.db10).

Install the Anti-Cross Site Scripting Library, which provides protection to Web-based applications

against Cross-Site Scripting (XSS) attacks. See Installing the Anti-Cross Site Scripting Library[page 22].

2.4 Logging on to Servers

When installing in a multiserver environment, you must use a domain user ID to log on to all

components.

A local server user ID is a member of the Administrator group on the server. A domain user ID is a

member of the Administrator group of a domain to which the server belongs, or a member of the

Administrator group on the local server.

Errors may display during the installation program and in the diagnostic program if the installing user

is not assigned to the Administrator group directly, but is assigned to a group with Administrator rights.

You can ignore these messages.

NOTE

If you change the password used to install Planning and Consolidation, you must change the

password for the applicable Planning and Consolidation service. To do this, go to Server Manager

on the application server, and select Server Reset Logon Credentials . For more information, see

the SAP Planning and Consolidation Operations Guidein http://service.sap.com/instguidesepm-bpc

10.0, for the Microsoft Platform SBOP Plan & Consol 10.0 MS Administrator's Guide .


2.4 Logging on to Servers

12/54 CUSTOMER 2014-04-02
http://service.sap.com/instguidesepm-bpc


13/54

2.5 Service-level Accounts

Service accounts are Windows domain IDs with access to all Planning and Consolidation servers with

varying levels of privileges. They allow the software to use the minimum amount of privilege required

for each job, making it more secure.

You must define these user IDs on the Windows machine. For security purposes, they should not be

used to define Planning and Consolidation users.

Prerequisites

Planning and Consolidation 10.0 has the following Windows services:

BPC SendGovernor, which manages Microsoft Analysis Service locks to ensure consistent performance

and avoid deadlocks

BPC ServiceManager, which manages the System Landscape Directory (SLD) service, logging service

and global caches

BPC CTS ServiceManager, which listens and handles CTS import requests from the CTS+ transport

management system.

Since these services should be able to access to the FileShare server, an Admin account is assigned

automatically to the service during the installation of the Planning and Consolidation server program.

Even though an Admin account has been assigned to the server correctly, the services may fail to start

with the error message:

Could not start the BPC SendGovernor service.

The reason for this is that the Admin account is not registered as a service.When installing a service to run under a domain user account, the account must have the right to

logon as a service on the local machine. This logon right strictly applies only to the local computer

and must be granted in the Local Security Policy.

To edit the Local Security Policy of the computer you want to define the logon as a service

permission, perform the following actions:

1. Start the Local Security Settings Microsoft Management Console (MMC) snap-in.

2. Expand Local Policies, and then click User Rights Assignment.

3. In the right-hand pane, right-click Log on as a service, and then click Security.

4. Add the user to the policy, and click OK.

5. Close the Local Security Settings MMC snap-in.

For more details, see How to Troubleshoot Service Startup Permissions: http://

support.microsoft.com/kb/259733.

Features

During the installation, enter user IDs and passwords for the following user types:

System Admin ID

This ID is read-only and is the same as the installation user ID, that is, the system displays the ID

on the installation screen but you cannot modify it. This ID allows access to code that provides


2.5 Service-level Accounts

2014-04-02 CUSTOMER 13/54
http://support.microsoft.com/kb/259733http://support.microsoft.com/kb/259733


14/54

system administrator-level functionality. For example, this ID can write to the Windows registry,

has full access to the FileShare server, and can create, remove, backup, and restore OLAP and SQL

databases. The system administrator should be a member of the domain users group, local

administrators group, and SQL administrators group.

Admin ID

This ID allows access to code that provides Administrator-level functionality. For example, this ID

can create subdirectory access on the FileShare server, read/write metadata and application set

database data in OLAP, and can create and remove tables in SQL. The Administrator should be a

member of the domain users group and the local administrators group.

User ID

This ID allows access to code at the user level. For example, this ID can read and write temporary

files on the servers, has write access to FileShare data, and can read metadata and data in OLAP andSQL. The User ID must be a member of the domain users group.

2.6 Standard and Advanced Settings

The following tables describe the standard and advanced settings for the installation program. After

the server is installed, you can change these settings using the Server Manager.

NOTE

When defining server names, the name refers to the NetBIOS name, IP address, and fully qualifieddomain names (FQDN).

Standard Settings

Standard settings are typically used for a single-server environment. The following table describes each

setting:

Server Option Value Description

SQL Database server name The name of the SQL DB server.

OLAP server name The name of the OLAP server.

File Share server name The default value is the name of the File Share server that should bethe computer name.

Local data path Where the data files are saved on the File Share server. By default, this

is C:/PC_MS/Data.

Application server name The name of the application server.

Advanced Settings

Advanced settings are typically used in a multiserver environment. The following table describes each

setting:


SQL Server Name The name of the SQL DB server. Defaults to the local server.


2.6 Standard and Advanced Settings

14/54 CUSTOMER 2014-04-02


15/54


Instance name The SQL instance name. If left blank, the default instance is used.

Port number The default port number for the SQL Server is 1433.

Provider The only available value is SQL.

Local path for EnvironmentShell

DB

The location of the EnvironmentShell database.

OLAP Server Name The name of the OLAP server.

Instance name The OLAP instance name. The instance name can be changed.

Port number The default value is 2383.

File Share Server Name The default value is the name of the File Share server that should be

the computer name.

Local data path Where the data files are saved on File Share server. By default, this is

C:/PC_MS/Data.

Application Server Name The name of the application server.

Web site The IIS Web site name, if it differs from the default Web site.

HTTP compression The default value is No. (Yesprovides better performance in some

situations.)

Protocol The available values are httpor https. The default value is http.

Port number The port number to which the application server connects. 80is the

default for http and 443is the default for https.

Authentication type Note: If you have chosen SAP BusinessObjects User Management Systemin the

installation screen, Authentication typedoes not appear in Advanced

settings (as that IIS authentication type is Anonymous in CMS mode).

Windows or Kerberos. The default is Windows. If you change this valuefrom Windows to Kerberos, you must make some additional changes.

See the Kerberos authentication settingssection in the SAP Library

Server Manager Guideon http://service.sap.com/instguidesEPM-BPC

10.0, for the Microsoft Platform .

Scheduler Server Name The name of the server used for scheduling, usually the application

server, for example, GMPV50072862B. If you have multiple application

servers, select the appropriate one.

NOTE

If the primary server stops working you must manually configure

your application server database to froward requests to anotherapplication server.

2.7 Installing the Prerequisites

2.7.1 Installing the Prerequisites Basic Steps

Before installing your Planning and Consolidation server, you must install the prerequisite Microsoft

software: the operating system, IIS, SQL server, analysis services, ADOMD.NET, and MSXML. This

section provides guidance on installing each component. For specific versions required, see



2014-04-02 CUSTOMER 15/54
http://service.sap.com/instguidesEPM-BPC


16/54

Prerequisites[page 9] and the Product Availability Matrix on the SAP Service Marketplace at http://

service.sap.com/pam. Search on Planning and Consolidation.

NOTE

To ensure a successful installation, you must install the software in the order listed in this

procedure.

Check all third-party infrastructure services to ensure that they are functioning, and that their

authentication models are documented (stated), since you need to reference this information

during the installation. These third-party services include IIS, OLAP service, SQL services, and

Active Directory (AD).

We recommend not installing Microsoft Office on the application server.

Procedure1. If you want to use CMS for Planning and Consolidation authorization, you must download and

install it on its own server. For more information, see the SAP BusinessObjects Planning and Consolidation

Master Guide.

After installing the CMS server, you must install the User Management Client (UMC) 10 on each

application server before you start the installation. You can find the UMC installation package

(UMC.exe) on the Planning and Consolidation CD in a folder called UMC_100_INSTALLER. When

you run the installation package, the wizard guides you through the following steps:

1. Choose a language for the UMC install wizard to use.

2. Check that the prerequisite check status is Succeededand click Next.

3. When you are ready to install the UMC, click Nexton the welcome screen.

4. Click I accept the License Agreement, and then Next.

5. Choose the destination directory for the UMC installation and click Next.

6. Select the languages that you wish to install.

7. Select the features that you want to install (POAFHelper dotnetis mandatory for Planning

and Consolidation).

8. On Start Installation, click Nextto complete the installation.

2. Install the required operating system on the single-server computer or on each physical server fora multiserver configuration. See Installing the Operating System[page 17].

3. Install the latest service pack for your operating system. To install this service pack, go tohttp://

www.microsoft.com.

4. From your operating system's media, install IIS.

5. From your SQL Server media, install SQL Server and its required service packs and hot fixes. See

Installing SQL Server[page 17].

6. From your SQL Server media, install Analysis Services Enterprise Edition and its required service

packs and hot fixes. See Installing Analysis Services[page 21].



16/54 CUSTOMER 2014-04-02
http://www.microsoft.com/http://www.microsoft.com/http://service.sap.com/pamhttp://service.sap.com/pam


17/54

7. On your application server, install ADOMD.NET. The Planning and Consolidation zip file contains

the ADOMD.NET installation package in the following locations:

For SQL Server 2008 \BPC Setup\Server\SQLSERVER2008_ASADOMD10_x64.msi

For SQL Server 2012 \BPC Setup\Server\SQLSERVER2012_ASADOMD11_x64.msi

8. On your application server, install MSXML 4.0 Service Pack 2 or later.

The MSXML 4.0 SP2 installation package is contained in the Planning and Consolidation zip file at

the following location: \BPC Setup\Server\msxml.msi.

9. On your application server, install Microsoft Visual C++ 2010 SP1 Redistributable Package (x64).

The Microsoft Visual C++ 2010 SP1 Redistributable Package (x64) installation package is contained

in the Planning and Consolidation zip file at the following location: \BPC Setup\Server

\vcredist_x64.exe.

NOTE

The version of vcredist_x64.exe in \BPC Setup\Server\ has been updated to 10.0.40219. If you

have a previous version on your application server, you must install the newer version.

10. On your application server, install Microsoft Access Database Engine 2010(x64).

You can download it from the Microsoft Web site at:http://www.microsoft.com/downloads/en/

details.aspx?FamilyID=C06B8369-60DD-4B64-A44B-84B371EDE16D&=en.

2.7.2 Installing the Operating System

Before installing the operating system, make sure that you configure your server for NTFS.

For a list of languages that are supported, see the Product Availability Matrix on the SAP Service

Marketplace at http://service.sap.com/pam. Search on Planning and Consolidation.

Planning and Consolidation can support all servers with an operating system in any language.

NOTE

Currently, Planning and Consolidation does not support an operating system in bi-directional

languages such as Hebrew.

Procedure

If you are installing IIS 7.0 or 7.5, you must enable the following features: Enable Basic Authenticationand Windows Authentication; these are not installed by default.

Install IIS 6 Metabase Compatibility role

Planning and Consolidation uses the ADSI provider to handle IIS administration such as virtual

directory and security but IIS 7 does not install the ADSI provider by default.

2.7.3 Installing the SQL Server

Prerequisites

During the installation procedure, you have the opportunity to specify the location of the

EnvironmentShell database file. Check that it is possible to access EnvironmentShell from the location



2014-04-02 CUSTOMER 17/54
http://service.sap.com/pamhttp://service.sap.com/pamhttp://www.microsoft.com/downloads/en/details.aspx?FamilyID=C06B8369-60DD-4B64-A44B-84B371EDE16D&%3Cdisplaylang%3E=enhttp://www.microsoft.com/downloads/en/details.aspx?FamilyID=C06B8369-60DD-4B64-A44B-84B371EDE16D&%3Cdisplaylang%3E=en


18/54

where you intend to install the SQL server. If it is not possible for port access reasons (DMZ,

WORKGROUP, or nontrusted domain authentication failures), copy EnvironmentShell to a location

on the SQL server (for example C:\EnvironmentShell.db10). You specify this location on the Server

Informationpage by choosing Server Information Advanced Options Local Path for EnvironmentShell DB .

Procedure

This section describes the general steps for installing the SQL Server, component options, and

considerations when installing and configuring a 2008, 2008 R2, and 2012 SQL Server.

SQL Server Considerations

We recommend installing all required components in sequence. For example, install the Operating

System (Windows Server), then enable IIS and ASP.NET and install any Windows Server service

packs.

IIS and .NET Framework 4.0 are required on your application server.

NOTE

If you encounter a 500 HTTP Error when trying to connect to the Planning and Consolidation

Web Client, refer to Microsoft Support articles 2520479 and 2468871 for assistance.

To reinforce security, we recommend that you install the SQL server, and SSAS components to a

nondefault instance of SQL Server.

General Installation Steps

1. Launch the SQL Server Setup program, entering a product key if necessary and accepting the license

terms.

2. Choose Installto install the SQL support files.

3. In Feature Selections, select instance and shared features as indicated in the SQL Server Component

Optionssection below, then choose Next.

4. Review disc space requirements, then choose Next.

5. In Server Configuration, Perform the following actions:

1. In the Service Accountstab, enter a Planning and Consolidation sysadmin account for the SQL

Server Database Engineand the SQL Server Analysisservices. This is required so that the Planningand Consolidation sysadmin can create and process the Planning and Consolidation database

because the Microsoft SQL server tries to back up or restore database with the privileged

account. This account is also required during Backup Environmentand Restore Environmentin the

Server Manager.

For a single-server environment, this account is also required if the backup file is located in a

different domain machine because SQL tries to access the folders and files with this account.

For the a multiple-server environment, SQL server retrieves the information of backup file

from the application server and the account requires the folder access privilege for the

application server.



18/54 CUSTOMER 2014-04-02


19/54

To ensure that you have the complete access privileges, we recommend the Planning and

Consolidation sysadmin for this service account.

2. In the Collationtab, set the collation settings to SQL_Latin1_General_CP1_CI_AS.

Choose Next.

6. Set Database Engine Configurationoptions, then choose Next.

We recommend you choose Mixed mode (Windows authentication and SQL authentication). This allows you

to use a restrictive SQL ID that works with the drill-through feature. If you must restrict SQL

authentication for security reasons, you can define a specific parameter in your drill-through

queries. If you do not need drill-through support, or use it without leveraging SQL authentication,

you can install the SQL Server in Windows-only mode.

7. Accept the Analysis Services Configurationdefault options and the remaining default options of the

installation program.8. Choose Installto begin the installation with the options you have set.

SQL Server Component Options

For Single-Machine Installations

Install the following components from the Feature Selectionscreen:

Database Engine Services

Analysis Services

Integration Service, which is listed as one of the Shared Features

For Multiple Machine Installations

For multiple machine installations, install the following components on each server:

Server Component What to Install

SQL Server Database Engine Services

SSAS Server Analysis Services

Application Server The following Shared Features:

Client Tools Connectivity

Integration Services

Client Tools SDK

Custom Settings for the SQL Server

As of version 10.0, Planning and Consolidation supports the following new features for SQL Server 2008,

SQL Server 2008 R2, and SQL Server 2012:

Process Dimension

It is now possible to process a dimension with multiple selections. At processing time, the process

dimension module makes changed or added information for each dimension and process for all selected

dimensions and cubes in parallel.



2014-04-02 CUSTOMER 19/54


20/54

Optimize Model

If there are custom partitions for a FACT partition in the OLAP database, an optimization module can

process custom partitions in parallel when Fullor Incremental Optimizeis performed. However, if a full

optimize is performed with the compress database option, the model should not be processed in parallelbecause only one OLAP object (cube) is required to be processed. If there are no custom partitions,

partitions in the cube are not processed in parallel because there is only one partition in the cube.

Read Committed Snapshot

You can set the SQL isolation level to be Read Committed Snapshotmode for each SQL database and for

application server and application set databases.

NOTE

Setting the SQL isolation level to be Read Committed Snapshotmode for a database can only be doneonce and cannot be reversed.

Real Time MOLAP

You can set the OLAP storage model of the write-back partition to be MOLAP (Multidimensional OLAP).

This setting remains even during modifying and copying a model.

You should set the OLAP storage model of the write-back partition after installing Planning and

Consolidation (without an environment) and after restoring an environment. The process to set the

OLAP storage modes is as follows:

Enable proactive caching

Update the cache when data changes to 0

Reduce outdated cache latency to 0

Bring the system online immediately

Enable notification with the SQL server after setting the tblFactWBtable

Table Partitioning

You can create partition function and scheme but only for the fact table.

For more information, see the Microsoft white paper Table Partitioning in SAP BI on Microsoft SQL Server

2005/2008, which you can download from www.microsoft.com(search on Table Partitioning to find

all relevant articles).

After Installing SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012

From SQL Server Configuration Manager, confirm that the SQL Server Browserservice is

running. The browser service is required for Planning and Consolidation.

From SQL Server Configuration Manager, do the following:

1. Select Protocols for , then double-click TCP/IPfrom the right side of the window.

2. When prompted for the TCP/IP Properties, select IP Addresses. You see two IPs that indicate the

localhost and external network interface machine.



20/54 CUSTOMER 2014-04-02
http://www.microsoft.com/


21/54

3. If you want to use IP1, which indicates Server IP, set Enabledto Yesand specify the TCP Port, as

desired.

4. Delete 0from TCP Dynamic Ports. Set IPAll - TCP Ports as desired (for example, 1533).

RECOMMENDATION

We do not recommend using dynamic ports.

In an SQL server, the default instance has a listener, which listens on a fixed port (TCP

port 1433). However, for the named instance the port on which the SQL server listens is

random and dynamically selected when the named instance of the SQL server starts. This

recommendation prevents any conflict problems.

From the SQL Server Configuration Manager, specify the client protocol options for the application

server:

1. Select Client Protocolsfrom the SQL Native Client Configurationfolder.2. From the right side of the window, double-click TCP/IP. The TCP/IP Propertieswindow is

displayed. Set the default port to the same port as you set for the above step (for example,

1533), then select OK.

From SQL Server Configuration Manager, open SQL Server Analysis Services Log On tab and

confirm that the user identified as the Log on asuser has the sysadminSQL Server role defined under

Server Rolesin the SQL Server Management Studio. This is required so Analysis Services can process

the SQL Server.

From SQL Server Management Studio, do the following tasks:

1. If you want to use a port with a named instance, select the server type Analysis Services, select

the server name (it should be automatically selected unless you have several instances), then

select Connect.

2. Right-click Analysis server object(top object named instance), and select Properties. The Analysis

Server Propertieswindow displays, which shows all configurable properties.

3. For enhanced security, change the default value to your port number (for example, 2724).

This means that you use a fixed port, as for the SQL Server option. Then choose OK.

NOTE

We do not support a nondefault port with the default instance in this release. If you wantto use the default instance, do not change the port number.

Restart SQL and OLAP.

Confirm that the installation has completed successfully by checking that there are no installation

related problems on the event viewer. You can now install Planning and Consolidation.

2.7.4 Installing Analysis Services

Procedure

After you install SQL Server and its required service packs and hotfixes, you must install SQL Server

Analysis Services and its required service packs and hotfixes.



2014-04-02 CUSTOMER 21/54


22/54

NOTE

If you have migrated your Analysis Services repository to the SQL Server, back up the database

that contains the repository before installing this release.

To install Analysis Services for SQL Server 2008, SQL Server 2008 R2, or SQL Server 2012, follow the steps

and guidelines in http://technet.microsoft.com/en-us/library/ms143219.aspx.

To avoid slow performance when a user has more than six OLAP databases, follow the steps and

guidelines in the Performance Guide for SQL 2008 at http://www.microsoft.com/downloads/

details.aspx?FamilyID=3be0488d-e7aa-4078-a050-ae39912d2e43&displaylang=en.

2.7.5 Installing the Anti-Cross Site Scripting Library

Procedure

Before installing Planning and Consolidation servers, you must download the Anti-Cross Site Scripting

Library (version 4.2, which provides protection to Web-based applications against Cross-Site Scripting

(XSS) attacks to have it available for the Planning and Consolidation installation program.

1. Download the Anti-Cross Site Scripting Library file AntiXSSLibrary.DLLfrom the Microsoft Web

site at http://www.microsoft.com/download/en/details.aspx?id=28589.

2. Save the extracted file locally.

When you install Planning and Consolidation Server, a step in the process requires you to identify the

path toAntiXssLibrary.dll

.

2.8 Installing on a Single Server

When you install all Planning and Consolidation server components on a single server, you should

consider the following issues:

Make sure the server has a minimum of 800 MB of hard disk space.

Additional environment installations require more free disk space, which is a minimum of two

times the uncompressed size of the environment files.

When you install Planning and Consolidation on a single-server, the system adds the following server

components:

SQL Server

SQL Server Analysis Services (SSAS)

Application Server

FileShare server

Procedure

To install Planning and Consolidation on a single server, take the following steps:

1. Exit all Windows programs.



22/54 CUSTOMER 2014-04-02
http://www.microsoft.com/download/en/details.aspx?id=28589http://technet.microsoft.com/en-us/library/ms143219.aspxhttp://www.microsoft.com/download/en/details.aspx?id=28589http://www.microsoft.com/downloads/details.aspx?FamilyID=3be0488d-e7aa-4078-a050-ae39912d2e43&displaylang=enhttp://www.microsoft.com/downloads/details.aspx?FamilyID=3be0488d-e7aa-4078-a050-ae39912d2e43&displaylang=enhttp://technet.microsoft.com/en-us/library/ms143219.aspx


23/54

2. Log on to the server with a local server user ID or domain user ID. For more information, see Logging

on to servers[page 12].

3. Make sure all prerequisite software is installed on the server. For more information, see Installing

the Prerequisites[page 15].

4. Obtain SAP Planning and Consolidation archive from the Downloads SAP Installations &

Upgrades area of SAP Service Marketplace.

5. Extract the files from the archive. Go to the BPC Setupfolder and run the StartUp.exefile.

6. From the Server Installscreen, select Install the Planning and Consolidation server.

7. From the Welcomescreen, choose Next.

8. From the License Agreementpage, choose I accept the terms of the license agreement, then choose Next.

9. From the Installation Methodpage, accept the default, Single machine, enter a system ID for the system

landscape directory (SLD), and choose Next.NOTE

Entering a system ID of the SLD is only required if you have a SAP Solution Manager license.

If you do not have a SAP Solution Manager license, you can leave this field empty.

10. From the Authentication Methodpage, choose the desired authentication method and choose Next.

11. If you have chosen SAP BusinessObjects User Management Systemin the previous screen, on the CMS

Authentication page enter the information required to log on to CMS as an administrator.

The following information is required:

Field Description

System name CMS system name (server name:port number), for example, CMSServer:

6400

Trusted CMS name CMS system name. If a CMS cluster name exists, use the cluster name.

Use a comma (, ) to separate multiple names.

Authentication type Select the appropriate value from the list

Administrator ID The user identifier of the dedicated administrator account

Administrator password Password for the administrator account

Group name Group of BusinessObjects Enterprise users who have access to the system.

This group name is filtered as the default when adding a user in Planning

and Consolidation Administration. Use a comma ( , ) to separate

multiple names.

12. After entering the CMS administrator authentication details, choose Next.

13. From the Service type accountspage, enter service-level account user IDs and passwords. See Service-

Level Accounts[page 13].

14. After defining the IDs and passwords, choose Next.

15. From the Server Information page(see Standard and Advanced Settings[page 14]), do one of the following:

Review the standard settings, and choose Next.

To set advanced settings, choose the Advanced Settingsbutton. Enter the desired information

and choose Next.



2014-04-02 CUSTOMER 23/54


24/54

16. Specify the location and name of AntiXssLibrary.dll. See Installing the Anti-Cross Site Scripting Library.[page

22]

Choose Next.

17. Select destination folders for Programs and Data. The Data files include Webfolders and FileDB

(published reports) and should be installed on a separate drive in a production environment. This

recommendation reduces the hard disk I/O time and helps to speed up SQL commands.

Accept the defaults or make your selections, then choose Next.

18. Select the default values for the Web client. The values are used to determine the default language

and region for the Web client when you connect to it. You can change the values in the Planning

and Consolidation Server Manager.

19. The installation process takes a few moments. When it is complete, choose Exit.

20. A prompt is displayed to restart your computer. Select OKto restart.21. Perform the steps in After Installing Planning and Consolidation Servers[page 25].

2.9 Installing the Server in a Multiserver Configuration

Procedure

A multiserver installation is the most flexible installation option. It allows you to install the required

server types in a variety of ways and configure the servers as a Network Load Balancing (NLB)

environment.

The recommended Planning and Consolidation practice is to assign resources using a round robinapproach for load balancing.

You can install the SQL, OLAP, and FileShare types remotely from the application server. You need to

perform additional server installations if you have multiple application servers.

Installing each Planning and Consolidation application server in a multiserver (NLB) configuration is

identical to the procedure for a single server (see Installing on a Single Server[page 22]) with the following

exceptions:

On the Installation Methodpage, do not accept the default; instead, choose Network Load Balancing

environment. With this option, there is an additional choice to Include sample environment (required on only

one of the application servers). This is because when you install the application server, it connects to the

database server and creates the sample environment (EnvironmentShell). Installing the sample

environment is required on only one application server and you may choose which one.

In the Virtual Namefield enter the virtual IP address / virtual name in the default properties.


2.9 Installing the Server in a Multiserver Configuration

24/54 CUSTOMER 2014-04-02


25/54

3 After Installing Planning andConsolidation Servers

3.1 Post-Installation Steps

Procedure

Perform these steps after installing the Planning and Consolidation servers for new installations of

Planning and Consolidation:

1. Connect your Planning and Consolidation system to Solution Manager Diagnostics (SMD) to allowsupport staff to identify, analyze, and resolve problems with your application. See Connecting to Solution

Manager Diagnostics[page 26].

2. Configure the Planning and Consolidation .NET and application server to ensure that it and its

related services function properly and reliably. For more information, see Configuring the Planning and

Consolidation .NET Application Server[page 27].

3. Optional configuration steps[page 28]:

1. To ensure proper functioning of the Management Console, create an SQL user, and modify

the System DSN and IIS to reflect those user credentials. See Enabling Management Console[page

28].

2. Configure custom ODBC logging for the default Web site. For details of how to configure

custom logging for ODBC in IIS 7.0 or 7.5, see Setting Up ODBC Logging in IIS 7.0 for the Default Web

Site[page 29].

3. Manually set up an ODBC data source for the Management Console. See Setting Up an ODBC

Data Source[page 30].

4. Modify the default access rights to the Management Console. By default, users in Active

Directory can access the Management Console with whatever rights they have been granted

on the server. For information about removing default access and creating a group that canaccess the console, see Removing Default Access to the Console[page 31].

5. Add authorized users or groups to the group that can access the Management Console. We

recommend that you only grant Management Console access to system administrators;

Planning and Consolidation users should not have any access. For more information, see

Management Console Access Control[page 32].

6. Configure the use of client certificates for authentication. See Using Client Certificates[page

33].

4. Take the following steps to set up security:

If you are defining security and application structure, continue with step 5.

3 After Installing Planning and Consolidation Servers

3.1 Post-Installation Steps

2014-04-02 CUSTOMER 25/54


26/54

If you want to designate someone other than the system administrator to manage security

and application structure, log on to EnvironmentShell, designate a user as a Primary

Administrator.

This user must have Administration Environment and Security Define User task rights,

so that he or she can add and delete environments and define user security.

The Primary Administrator can continue with the next step (5).

5. From the machine on which you administer Planning and Consolidation, install the

Administration client. See Installing the Administration Client[page 37].

6. Start Planning and Consolidation Administration from the launch page.

7. Select Connection Wizard, and log on to EnvironmentShell.

8. Create a new environment using EnvironmentShell as the source.

9. Log on to the newly created environment, and set up users, teams, andtask profiles. (You mustset up task profiles since there is no access to Planning and Consolidation tasks.)

10. Set up your data access profiles, and add users (or teams) to one or more data access profiles. (You

must complete this step, since there is no access to dimensions or members.)

NOTE

To allow users to request and query large amounts of data, you can edit the metabase.xmlfile located

at C:\Windows\system32\inetsrv\.Set the following parameters to the stated values:

ASPBUFFERINGLIMIT = 10485760

MAXREQUESTENTITYALLOWED = 10485760

3.2 Connecting to Solution Manager Diagnostics

NOTE

You only need to perform the steps in this section if you have a SAP Solution Manager licence.

The diagnostics functions in SAP Solution Manager allow identification, analysis, and resolution of

problems. This procedure provides the steps required to connect Planning and Consolidation to

Solution Manager Diagnostics.

Procedure

1. Install the Diagnostics Agent according to SAP Note1234387on all servers where application servers

are installed.

NOTE

Installation files for Diagnostics Agent are available on Service Marketplace by navigating to

Support Packages and Patches Entry by Application Group SAP Technology Components SAP

SOLUTION MANAGER SAP SOLUTION MANAGER 7.0 EHP 1 Entry by Component Agents

for managed systems DIAGNOSTICS AGENT 7.11 .


3.2 Connecting to Solution Manager Diagnostics

26/54 CUSTOMER 2014-04-02
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1234387&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1234387&_NLANG=en&_NVERS=0


27/54

Download the installation file based on the 64-bit Windows Server system landscape.

2. To access the DBA Cockpit, you must create a user account with sufficient rights on all Windows

Servers where Microsoft SQL Server is installed. Do the following:

1. Start Computer Management, then select Action New User .

2. Create a new user.

3. Right-click on the user, then choose Properties. On the Member Oftab, select Add.

4. Add the group SQLServerSQLAgentUser$$MSSQLSERVER.

5. Log on to Microsoft SQL Server Management Studio, then select Databases Security

Logins .

6. Right-click on the user.

7. Select New Loginand enter the user you created previously, ensuring that Windows

Authentication is set.8. Select Server roles, select sysadmin, then choose OK.

3. Set up your system for Diagnostics.

Refer to End-to-End Root Cause Analysis System Landscape Setup Guide, which is available on Service

Marketplace at https://service.sap.com/~sapidb/011000358700000074392009E, and follow

the chapters that apply to Planning and Consolidation.

3.3 Configuring the Planning and Consolidation .NET

Application ServersProcedure

Modifying machine.config Files

To ensure the right balance 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.configfile, which resides in the \WINDOWS\Microsoft.NET\Framework64

\v4.0.30319\Config\directory.

1. In .NET 4.0, the processModelelement in machine.configsupports the attribute autoConfigto

specify whether to automatically configure settings to achieve optimal performance based on themachine configuration. You can set this attribute to Trueor False.

For more information, see http://msdn.microsoft.com/en-us/library/7w2sway1.aspx.

2. If you are using a Web farm, you must change the tag in Web.config(for just the

Planning and Consolidation application) or Machine.config(for all applications, including

Planning and Consolidation) to ensure the validationKeyand decryptionKeykeys have the same

value on all application, servers. This way, when the authentication cookie is checked, the

authentication ticket used on one server can still be valid on another server.

For more information and sample Visual Basic code for generating random key values, see http://

msdn.microsoft.com/en-us/library/ms998288.aspx


3.3 Configuring the Planning and Consolidation .NET Application Servers

2014-04-02 CUSTOMER 27/54
http://msdn.microsoft.com/en-us/library/ms998288.aspx#paght000007_webfarmdeploymentconsiderationshttp://msdn.microsoft.com/en-us/library/ms998288.aspx#paght000007_webfarmdeploymentconsiderationshttp://msdn.microsoft.com/en-us/library/7w2sway1.aspxhttps://service.sap.com/~sapidb/011000358700000074392009E


28/54

#paght000007_webfarmdeploymentconsiderationsand http://msdn.microsoft.com/en-us/

library/ms998310.aspx.

3.4 Post-Installation: Optional Configuration Steps

The steps listed below are optional and do not affect the main functions of Planning and Consolidation.

1. To ensure proper functioning of the Management Console, create an SQL user, and modify the

System DSN and IIS to reflect those user credentials. See Enabling Management Console[page 28].

2. Configure custom ODBC logging for the default Web site. For details of how to configure custom

logging for ODBC in IIS 7.0 or 7.5, see Setting Up ODBC Logging in IIS 7.0 for the Default Web Site [page

29].

3. Manually set up an ODBC data source for the Management Console. See Setting Up an ODBC DataSource[page 30].

4. Modify the default access rights to the Management Console. By default, users in Active Directory

can access the Management Console with whatever rights they have been granted on the server.

For information about removing default access and creating a group that can access the console,

see Removing Default Access to the Console[page 31].

5. Add authorized users or groups to the group that can access the Management Console. We

recommend that you only grant Management Console access to system administrators; Planning

and Consolidation users should not have any access. For more information, see Management Console

Access Control[page 32].

6. Configure the use of SSL in Planning and Consolidation. See Configuring Planning and Consolidation to use

SSL[page 32].

7. Configure the use of client certificates for authentication. See Using Client Certificates[page 33].

8. Configure Microsoft SQL Server Reporting Services to use SSL. See Configuring MS SQL Server Reporting

Services to use SSL[page 34].

3.4.1 Enabling the Management ConsoleProcedure

To ensure proper functioning of the Management Console, you must do the following:

1. Change the Microsoft SQL Server authentication mode to SQL Server and Windows Authentication mode

2. Create a Microsoft SQL Server user to access AppServeras the default database. Give the

db_Ownerdatabase role to the user for AppServerdatabase.

3. Enter the Microsoft SQL Server user information in the BPC_ManagementDSNsystem DSN in

DataSource (OBDC).

4. In the IIS Web site of the Planning and Consolidation application server, modify the Active Log

Formatoption to use ODBC Logging. Enter the following values:



28/54 CUSTOMER 2014-04-02
http://msdn.microsoft.com/en-us/library/ms998310.aspxhttp://msdn.microsoft.com/en-us/library/ms998310.aspxhttp://msdn.microsoft.com/en-us/library/ms998288.aspx#paght000007_webfarmdeploymentconsiderations


29/54

DSNis BPC_ManagementDSN

Tableis BPCLog

The Microsoft SQL Server Usernameand Password.

5. Restart IIS.

NOTE

Without these updates, the Management Console does work, but some functionality (specifically

User Activity and Service Status) does not work as expected.

Should you need to uninstall Planning and Consolidation, we recommend that you reset the

Active Log Formatfield in IIS to W3C Extended Log File Format.

3.4.2 Setting Up ODBC Logging in IIS for the Default Web Site

This procedure describes how to configure custom logging for ODBC in IIS for the default Web site.

Prerequisites

ODBC logging has been configured according to the Microsoft Knowledge Base article 245243, How to

configure ODBC logging in IIS.

Procedure

Setting the Log File Format and customLogPluginClsid

Set the log file format and log plug-in ID for ODBC logging.

In the file ApplicationHost.config, set the property customLogPluginClsidto the value {FF16065B-

DE82-11CF-BC0A-00AA006111E0}. Set the logFormatto Custom. You can find this in the

node in ApplicationHost.config, as shown here:

Use the following AppCmds to configure IIS to use ODBC logging for the default Web site:

appcmd site set /site.name:"Default Web Site" /

logFile.customLogPluginClsid:"{FF16065B-DE82-11CF-BC0A-00AA006111E0}"

appcmd site set /site.name:"Default Web Site" /logFile.logFormat:"Custom"

Configuring ODBC Logging Parameters in ApplicationHost.config

Configure ApplicationHost.config to contain the database table information, as set up in the Microsoft

Support article specified in the Prerequisites section. Configure these settings in the

node under .

EXAMPLE



2014-04-02 CUSTOMER 29/54


30/54

Use the following AppCmds to configure these attributes for the default Web site:

appcmd set config "Default Web Site" /section:odbcLogging /

dataSource:"BPC_ManagementDSN" /commit:appHost

appcmd set config "Default Web Site" /section:odbcLogging /tableName:"BPCLog" /

commit:appHost

appcmd set config "Default Web Site" /section:odbcLogging /userName:"Username" /

commit:appHost

appcmd set config "Default Web Site" /section:odbcLogging /password:"mypassword" /

commit:appHost

NOTE

You cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver. You must

use the SQL Server ODBC driver. For more information, see the Microsoft Knowledge Base article

931202, The requirements for using the ODBC logging feature in IIS.

3.4.3 Setting Up an ODBC Data Source in Windows Server2008 or Windows Server 2008 R2

Procedure

This procedure describes how to set up an ODBC data source for the Management Console in Windows

Server 2008 or Windows Server 2008 R2.

Proceed as follows:

1. Open ODBC Connection Manager.

2. On the System DSN tab page, add a new DSN: Choose Add.

Choose SQL Serveras the driver.

Choose Finish.

3. In the Name and Description fields, enter BPC_ManagementDSN.

4. In the Serverfield, enter the name of your SQL Server. Choose Next.

5. Leave the default settings, and choose Next.

6. Choose the Change the default database tofield and enter AppServer. Choose Next.

7. Leave default settings, and choose Next.

8. Choose OK.



30/54 CUSTOMER 2014-04-02


31/54

3.4.4 Removing Default Access to the Console

NOTE

If you have chosen SAP BusinessObjects User Management System in the installation screen, you

do not need to remove or configure access because the Management Console service always runs

with the System Admin ID account, which is a member of the Administrators group.

Procedure

To remove default access to the Management Console and create a group that does have access to the

console, use the procedure described below.

NOTE

Create your Management Console administrative group either on the server that hosts the

Management Console or in the Active Directory.

1. In the context menu of the server's My Computericon, choose Manage.

2. In the Computer Management dialog box, choose Local Users and Groups Groups .

NOTE

Alternatively, you can perform analogous steps in Active Directory.

3. In the Groupscontext menu, choose New Group.

4. Enter data as required. Click Create.

5. In the Computer Management dialog box, choose Services and Applications Internet Information Services

Web Sites Default Web Sites Management Console .6. In the Management Consolecontext menu, choose Permissions.

7. Click Add, and add the group you created earlier in this procedure.

8. Click Advanced.

9. On the Permissionstab, deselect the Allow inheritable permissions from the parent to propagate to this object and all

child objects. Include these with entries explicitly defined here. checkbox.

NOTE

This step is a necessary precursor to the completion of this procedure.

10. In the Securitydialog box, click Copyto ensure that the Systemgroup retains its privileges.

11. Remove access to the Management Console from all groups that should not have it.

12. Choose Authenticationin the center pane, then disable Windows authentication.

Result

Users who have not been granted access to the Management Console can still open the Management

Console Web page, but it contains no data or menu options. This does not affect the access that a user

would otherwise have to Planning and Consolidation.



2014-04-02 CUSTOMER 31/54


32/54

3.4.5 Management Console Access Control

After establishing the Management Console group, you can add users or groups to it. For more

information about creating this group, see Removing Default Access to the Console[page 31]. Their rights in

Active Directory determine what they can access in the Console.

By default, any member of the Administrators Active Directory group on the application server or

domain has full access to all of the features of the Console except the Planning and Consolidation

logging area. Access to Planning and Consolidation logging is controlled within the Planning and

Consolidation Administration Client task security. The user must be granted View system logstask

privileges. For more information, see the SAP Library Planning and Consolidation Administrator's Guidein

http://service.sap.com/instguidesepm-bpc 10.0, version for the Microsoft platform .

Your IT policy determines whether you grant access by group or user. You may wish to create several

levels of Console users (read-only users, for example) in your environment.To grant or limit access to users or groups, you can add or remove the following privileges from the

areas described in this table:

Privilege Rights Management Area

Task Manager and Kill Process Administrators group on application server or domain

Performance Monitor Counters Administrators group on application server or domain

Power Users group on application server or domain

Performance Monitor Users group on application server

Microsoft Analysis Services performance

monitoring Administrators group on application server or domain

Microsoft SQL Server Monitoring (performance

counters and statistics) Administrators group on application server or domain

3.4.6 Configuring Planning and Consolidation to use SSL

Procedure

Creating a Certificate for the Server

During the handshake phase of the SSL communication the server must send its certificate to the client.The client then uses the certificate to encrypt information and send it back to the server.

The procedure below describes how to create a self-signed certificate for the server.

RECOMMENDATION

We recommend that you limit the use of self-signed certificates to testing only. For a productive

system you should obtain a certificate signed by a well-known certification authority (CA).

1. Start the Internet Information Services (IIS) Manager. To do that, go to Start All Programs Administrative

Tools Internet Information Services (IIS) Manager .



32/54 CUSTOMER 2014-04-02
http://service.sap.com/instguidesepm-bpc


33/54

2. In the Connectionspanel on the left-hand side, select the server node and then choose Server

Certificates.

3. In the Actionspanel on the right hand side, choose the Create Self-Signed Certificateaction.

4. Enter the name that you want the certificate to be identified by, for example,

MyTestSSLCertificate.

IIS generates a new SSL certificate for you that has one years expiry lease. The certificate is issued to

the local server name.

Binding the Certificate to the Web Site

The procedure below describes how to bind the certificate to the web site for which SSL connections

must be used.

1. In the Connectionspanel, select the web site node.

2. In the Actionspanel choose Bindings.

3. In the Site Bindingsdialog that appears, choose the Addbutton to create a new binding.

4. Configure the parameters as follows:

Type= https

IP Address=[::1]- this is a shorthand expression for the local server name

Port= 443- this is the default SSL port

SSL Certificate= enter your newly created certificate name

5. Choose OKto create the new binding and then close the Site Bindingsdialog.

6. Restart the IIS processes. To do this, choose Restartfrom the Actionspanel.7. In the middle panel, under the IISsection, choose SSL Settings.

8. In the SSL Settingsscreen select the Require SSLcheckbox.

9. In the Actionspanel choose to Applythese settings.

To test the SSL connection, in the Actionspanel, choose the Browse [::1] 443 (https)link.

3.4.7 Using Client Certificates

To enable the use of client certificates in Planning and Consolidation, you must follow several manualsteps.

NOTE

Planning and Consolidation supports client certificate authentication in Windows

Authentication Modebut does not support it in CMS Authentication Mode. When using a client

certificate, Single Sign-On (SSO) between the EPM Add-in, the Web client and the Administration

client is not supported.

For more information about the SSL settings page, see http://technet.microsoft.com/en-us/

library/cc753810.aspx



2014-04-02 CUSTOMER 33/54
http://technet.microsoft.com/en-us/library/cc753810.aspxhttp://technet.microsoft.com/en-us/library/cc753810.aspx


34/54

For more information about configuring the client certificate mapping authentication, see http://

technet.microsoft.com/en-us/library/cc732996(WS.10).aspx

When you create the client certificates, you can set the type of certificate in the SSL Settings screen in

Internet Information Services (IIS) Manager.

Procedure

1. Set the options for client certificates.

1. In the IIS Manager, select the web site where you installed Planning and Consolidation.

2. Choose SSL Settings.

3. In the Client certificatessection, select the Accept client certificatesoption.

This option allows you to use a client certificate or username and password (Basic

authentication) to connect to Planning and Consolidation.

2. Enable anonymous authentication.

1. In the IIS Manager, expand the node of the Planning and Consolidation web site.

2. Select the ManagementConsoledirectory (/ManagementConsole) to open the

ManagementConsolehome page.

3. Double-click Authenticationand enable Anonymous Authentication.

4. Select the BPCdirectory (/SAP/BPC) and enable Anonymous Authenticationthe same way

as in step 3.

5. Select the SBCdirectory (/SAP/POA/SBC) and enable Anonymous Authenticationthe same

way as in step 3.3. Change the web configuration settings.

1. Open the ..\\Websrvr\Web\BPC\web.configfile.

2. Find the text clientCredentialType="Windows".

3. Change value of clientCredentialTypeto "None"(clientCredentialType="None").

4. Open the ..\PC_

Documents

Sbop Pc 10 m Install