-
Installation GuideSAP BusinessObjects Planning and Consolidation
10.0version for the Microsoft platform
Target Audience Technical Consultants System Administrators
CUSTOMERDocument version: 1.37 2012-06-13
-
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +49/18 05/34 34 34F +49/18 05/34 34 20
www.sap.com
Copyright 2012 SAP AG. All rights reserved.No part of this
publication may be reproduced or transmitted in any form or for any
purpose without the express permission of SAP AG. The information
contained herein may be changed without prior notice.Some software
products marketed by SAP AG and its distributors contain
proprietary software components of other software
vendors.Microsoft, Windows, Outlook, and PowerPoint are registered
trademarks of Microsoft Corporation.IBM, DB2, DB2 Universal
Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400,
OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, 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 MarketplaceYou can find this
document at the following address:
http://service.sap.com/instguidesEPM-BPC.
2/54 CUSTOMER 2012-06-13
-
Document History
The following table provides an overview of the most important
document changes.Version Date Description1.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.
2012-06-13 CUSTOMER 3/54
-
Table of Contents
Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.1 SAP
Notes for the Installation . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . 71.2 Naming Conventions . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . 9
Chapter 2 Installing Planning and Consolidation Servers . . . .
. . . . . . . . . . . . . . . . . 112.1 Basic Steps . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . 112.2 Prerequisites . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . 112.3 Before Starting the Planning and Consolidation
Server
Installation . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . 132.4 Logging
on to Servers . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . 142.5 Service-level Accounts . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . 152.6 Standard and Advanced Settings . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . 162.7
Installing the Prerequisites . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . 172.7.1 Installing the
Prerequisites Basic Steps . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . 172.7.2 Installing the Operating System . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
192.7.3 Installing the SQL Server . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . 192.7.4 Installing
Analysis Services . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . 232.7.5 Installing the Anti-Cross
Site Scripting Library . . . . . . . . . . . . . . . . . . . . . .
. . 242.8 Installing on a Single Server . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . 242.9 Installing
the Server in a Multiserver Configuration . . . . . . . . . . . . .
. . . . . . . 26
Chapter 3 After Installing Planning and Consolidation Servers .
. . . . . . . . . . . . . . . 273.1 Post-Installation Steps . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . 273.2 Connecting to Solution Manager Diagnostics . . . .
. . . . . . . . . . . . . . . . . . . . . 283.3 Configuring the
Planning and Consolidation .NET Application
Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . 293.4
Post-Installation: Optional Configuration Steps . . . . . . . . . .
. . . . . . . . . . . . . . 303.4.1 Enabling the Management Console
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
303.4.2 Setting Up ODBC Logging in IIS for the Default Web Site . .
. . . . . . . . . . . . . . 313.4.3 Setting Up an ODBC Data Source
in Windows Server 2008 or Windows Server
2008 R2 . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . 32
4/54 CUSTOMER 2012-06-13
-
3.4.4 Removing Default Access to the Console . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . 323.4.5 Management Console
Access Control . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . 333.4.6 Using Client Certificates . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . 374.2 Installing the EPM
Add-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . 384.3 Using the Client Auto Update Program . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Chapter 5 Connection Issues . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . 415.1
Checking for Open Ports . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . 415.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 Citrix Server Deployment . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
7.1 Terminal Services Home Directories . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . 457.2 System Requirements . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . 457.3 Installing Planning and Consolidation . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . 457.4 Creating
a Shortcut to the Launch Page . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . 46
Chapter 8 Installing SSIS Custom Tasks . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . 478.1 Composition of
SSIS Custom Task Installation . . . . . . . . . . . . . . . . . . .
. . . . . 478.2 Before You Modify the SSIS Packages . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . 508.3 Setup of a
COM+ Application on the Application Server . . . . . . . . . . . .
. . . . . 51
2012-06-13 CUSTOMER 5/54
-
This page is left blank for documents that are printed on both
sides.
-
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 Office help.
New Installation Program Features in 10.0The 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 InstallationRead 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.
1 Introduction1.1 SAP Notes for the Installation
2012-06-13 CUSTOMER 7/54
-
SAP Note Number Title Comments1584890 Documentation Addendum
Contains information that does not appear in the
application help of Planning and Consolidation 10.0, version for
the Micrososft platform.
1733053 SAP Planning and Consolidation 10.0 SP08, version for
the Microsoft platform
This is the Central Note for Planning and Consolidation 10.0
SP08.This note contains important information about the
installation of SAP Planning and Consolidation 10.0, version for
the Microsoft platform.
1689792 SAP Planning and Consolidation 10.0 SP07, version for
the Microsoft platform
This is the Central Note for Planning and Consolidation 10.0
SP07.This note contains important information about the
installation of SAP Planning and Consolidation 10.0, version for
the Microsoft platform.
1665656 SAP Planning and Consolidation 10.0 SP06, version for
the Microsoft platform
This is the Central Note for Planning and Consolidation 10.0
SP06.This note contains important information about the
installation of SAP Planning and Consolidation 10.0, version for
the Microsoft platform.
1643037 SAP Planning and Consolidation 10.0 SP05, version for
the Microsoft platform
This is the Central Note for Planning and Consolidation 10.0
SP05.This note contains important information about the
installation of SAP Planning and Consolidation 10.0, version for
the Microsoft platform.
1620464 SAP Planning and Consolidation 10.0 SP04, version for
the Microsoft platform
This is the Central Note for Planning and Consolidation 10.0
SP04.This note contains important information about the
installation of SAP Planning and Consolidation 10.0, version for
the Microsoft platform.
1601213 SAP Planning and Consolidation 10.0 SP03, version for
the Microsoft platform
This is the Central Note for Planning and Consolidation 10.0
SP03.This note contains important information about the
installation of SAP Planning and Consolidation 10.0, version for
the Microsoft platform.
1591848 SAP Planning and Consolidation 10.0 SP02, version for
the Microsoft platform
This is the Central Note for Planning and Consolidation 10.0
SP02.This note contains important information about the
installation of SAP Planning and Consolidation 10.0, version for
the Microsoft platform.
1 Introduction1.1 SAP Notes for the Installation
8/54 CUSTOMER 2012-06-13
-
SAP Note Number Title Comments1573539 SAP Planning and
Consolidation 10.0
SP01, version for the Microsoft platform
This is the Central Note for Planning and Consolidation 10.0
SP01.This note contains important information about the
installation of SAP Planning and Consolidation 10.0, version for
the Microsoft platform.
1.2 Naming ConventionsIn 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 Introduction1.2 Naming Conventions
2012-06-13 CUSTOMER 9/54
-
This page is left blank for documents that are printed on both
sides.
-
2 Installing Planning and Consolidation Servers
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 StepsTo 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
Guide at 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
13] 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 24].NOTEYou must install
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 26].5. Perform the steps in the
section After Installing Planning and Consolidation Servers [page
27].
2.2 PrerequisitesThe following table describes the software you
need to install before installing the Planning and Consolidation
server, and the minimum versions required.
NOTEA 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 Servers2.1 Basic
Steps
2012-06-13 CUSTOMER 11/54
-
Component Minimum RequirementOperating 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, or Data Center with or without Hyper-V
NOTEThe 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.2This 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++ 2005 Runtime Libraries SP1 Microsoft Access
Database Engine 2010 64bit VMWare ESX 3.x or ESX 4.0
(Required only if a landscape deployment strategy using
virtualization technologies is planned.)
NOTEMSXML 4.0 SP2, ADOMD.NET 10.0, and Microsoft Visual C++ 2005
Runtime Libraries SP1 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 Installing Planning and Consolidation Servers2.2
Prerequisites
12/54 CUSTOMER 2012-06-13
-
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 Server
Installation
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 17]. 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
16].
Make sure all required server ports are open, and that there is
communication between the physical servers 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 15].
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 Installing Planning and Consolidation Servers2.3 Before
Starting the Planning and Consolidation Server Installation
2012-06-13 CUSTOMER 13/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 14].
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 Information
page), 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 24].
2.4 Logging on to ServersWhen 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.
NOTEIf 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 Guide in
http://service.sap.com/instguidesepm-bpc
10.0, for the Microsoft Platform SBOP Plan & Consol 10.0 MS
Administrator's Guide .
2 Installing Planning and Consolidation Servers2.4 Logging on to
Servers
14/54 CUSTOMER 2012-06-13
-
2.5 Service-level AccountsService 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.
PrerequisitesPlanning 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.
FeaturesDuring 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 Installing Planning and Consolidation Servers2.5 Service-level
Accounts
2012-06-13 CUSTOMER 15/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 IDThis 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 IDThis 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 and SQL. The User ID must be a member of the domain users
group.
2.6 Standard and Advanced SettingsThe 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.
NOTEWhen defining server names, the name refers to the NetBIOS
name, IP address, and fully qualified domain names (FQDN).
Standard SettingsStandard settings are typically used for a
single-server environment. The following table describes each
setting:Server Option Value DescriptionSQL 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 be
the 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 SettingsAdvanced settings are typically used in a
multiserver environment. The following table describes each
setting:Server Option Value DescriptionSQL Server Name The name of
the SQL DB server. Defaults to the local server.
2 Installing Planning and Consolidation Servers2.6 Standard and
Advanced Settings
16/54 CUSTOMER 2012-06-13
-
Server Option Value Description 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
DBThe 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. (Yes provides better performance in some
situations.) Protocol The available values are http or https.
The default value is http. Port number The port number to which the
application server connects. 80 is the
default for http and 443 is the default for https.
Authentication type Note: If you have chosen SAP BusinessObjects
User Management System in the
installation screen, Authentication type does 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 value from Windows to Kerberos, you must make some
additional changes.See the Kerberos authentication settings section
in the SAP Library Server Manager Guide on
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.
NOTEIf the primary server stops working you must manually
configure your application server database to froward requests to
another application server.
2.7 Installing the Prerequisites2.7.1 Installing the
Prerequisites Basic StepsBefore 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
2 Installing Planning and Consolidation Servers2.7 Installing
the Prerequisites
2012-06-13 CUSTOMER 17/54
-
Prerequisites [page 11] and the Product Availability Matrix on
the SAP Service Marketplace at http://service.sap.com/pam. Search
on Planning and Consolidation.
NOTETo 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 Succeeded and click Next.3. When you are ready to
install the UMC, click Next on 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 dotnet is mandatory for Planning
and Consolidation).8. On Start Installation, click Next to
complete the installation.
2. Install the required operating system on the single-server
computer or on each physical server for a multiserver
configuration. See Installing the Operating System [page 19].
3. Install the latest service pack for your operating system. To
install this service pack, go to http://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 19].6. From your SQL Server media,
install Analysis Services Enterprise Edition and its required
service
packs and hot fixes. See Installing Analysis Services [page
23].
2 Installing Planning and Consolidation Servers2.7 Installing
the Prerequisites
18/54 CUSTOMER 2012-06-13
-
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++ 2005
Runtime Libraries SP1.The Microsoft Visual C++ 2005 SP1
installation package is contained in the Planning and Consolidation
zip file at the following location: \BPC
Setup\Server\vcredist_x64.exe.
NOTEThe version of vcredist_x64.exe in \BPC Setup\Server\ has
been updated to 8.0.61000. 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.
NOTECurrently, Planning and Consolidation does not support an
operating system in bi-directional languages such as Hebrew.
ProcedureIf you are installing IIS 7.0 or 7.5, you must enable
the following features: Enable Basic Authentication and 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 ServerPrerequisitesDuring 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
2 Installing Planning and Consolidation Servers2.7 Installing
the Prerequisites
2012-06-13 CUSTOMER 19/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 Information page by
choosing Server Information Advanced Options Local Path for
EnvironmentShell DB .
ProcedureThis 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.NOTEIf 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 Steps1. Launch the SQL Server Setup
program, entering a product key if necessary and accepting the
license
terms.2. Choose Install to install the SQL support files.3. In
Feature Selections, select instance and shared features as
indicated in the SQL Server Component
Options section below, then choose Next.4. Review disc space
requirements, then choose Next.5. In Server Configuration, Perform
the following actions:
1. In the Service Accounts tab, enter a Planning and
Consolidation sysadmin account for the SQL Server Database Engine
and the SQL Server Analysis services. This is required so that the
Planning and 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 Environment
and Restore Environment in 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.
2 Installing Planning and Consolidation Servers2.7 Installing
the Prerequisites
20/54 CUSTOMER 2012-06-13
-
To ensure that you have the complete access privileges, we
recommend the Planning and Consolidation sysadmin for this service
account.
2. In the Collation tab, set the collation settings to
SQL_Latin1_General_CP1_CI_AS.Choose Next.
6. Set Database Engine Configuration options, 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 Configuration default options
and the remaining default options of the installation program.
8. Choose Install to begin the installation with the options you
have set.
SQL Server Component OptionsFor Single-Machine
InstallationsInstall the following components from the Feature
Selection screen: Database Engine Services Analysis Services
Integration Service, which is listed as one of the Shared
FeaturesFor Multiple Machine InstallationsFor multiple machine
installations, install the following components on each
server:Server Component What to InstallSQL Server Database Engine
ServicesSSAS Server Analysis ServicesApplication Server The
following Shared Features:
Client Tools Connectivity Integration Services Client Tools
SDK
Custom Settings for the SQL ServerAs 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 DimensionIt 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.
2 Installing Planning and Consolidation Servers2.7 Installing
the Prerequisites
2012-06-13 CUSTOMER 21/54
-
Optimize ModelIf there are custom partitions for a FACT
partition in the OLAP database, an optimization module can process
custom partitions in parallel when Full or Incremental Optimize is
performed. However, if a full optimize is performed with the
compress database option, the model should not be processed in
parallel because 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 SnapshotYou can set the SQL isolation level to be
Read Committed Snapshot mode for each SQL database and for
application server and application set databases.
NOTESetting the SQL isolation level to be Read Committed
Snapshot mode for a database can only be done once and cannot be
reversed.
Real Time MOLAPYou 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 tblFactWB tableTable PartitioningYou 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 Browser service 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/IP from 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.
2 Installing Planning and Consolidation Servers2.7 Installing
the Prerequisites
22/54 CUSTOMER 2012-06-13
-
3. If you want to use IP1, which indicates Server IP, set
Enabled to Yes and specify the TCP Port, as desired.
4. Delete 0 from TCP Dynamic Ports. Set IPAll - TCP Ports as
desired (for example, 1533).RECOMMENDATIONWe 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
Protocols from the SQL Native Client Configuration folder.2. From
the right side of the window, double-click TCP/IP. The TCP/IP
Properties window 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 as user has the sysadmin SQL Server role defined under Server
Roles in 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 Properties
window 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.
NOTEWe do not support a nondefault port with the default
instance in this release. If you want to 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 ServicesProcedureAfter 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.
2 Installing Planning and Consolidation Servers2.7 Installing
the Prerequisites
2012-06-13 CUSTOMER 23/54
-
NOTEIf 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
LibraryProcedureBefore 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.DLL from 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 to AntiXssLibrary.dll.
2.8 Installing on a Single ServerWhen 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
serverProcedureTo install Planning and Consolidation on a single
server, take the following steps:1. Exit all Windows programs.
2 Installing Planning and Consolidation Servers2.8 Installing on
a Single Server
24/54 CUSTOMER 2012-06-13
-
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
14].
3. Make sure all prerequisite software is installed on the
server. For more information, see Installing the Prerequisites
[page 17].
4. Obtain SAP Planning and Consolidation from the Downloads SAP
Installations & Upgrades area of SAP Service Marketplace, then
extract the files and run StartUp.exe.
5. From the Server Install screen, select Install the Planning
and Consolidation server.6. From the Welcome screen, choose Next.7.
From the License Agreement page, choose I accept the terms of the
license agreement, then choose Next.8. From the Installation Method
page, accept the default, Single machine, enter a system ID for the
system
landscape directory (SLD), and choose Next.NOTEEntering 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.
9. From the Authentication Method page, choose the desired
authentication method and choose Next.10. If you have chosen SAP
BusinessObjects User Management System in 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
DescriptionSystem name CMS system name (server name:port number),
for example, CMSServer:
6400Trusted 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 listAdministrator ID The user
identifier of the dedicated administrator accountAdministrator
password Password for the administrator accountGroup 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.
11. After entering the CMS administrator authentication details,
choose Next.12. From the Service type accounts page, enter
service-level account user IDs and passwords. See Service-
Level Accounts [page 15].13. After defining the IDs and
passwords, choose Next.14. From the Server Information page (see
Standard and Advanced Settings [page 16]), do one of the
following:
Review the standard settings, and choose Next. To set advanced
settings, choose the Advanced Settings button. Enter the desired
information
and choose Next.
2 Installing Planning and Consolidation Servers2.8 Installing on
a Single Server
2012-06-13 CUSTOMER 25/54
-
15. Specify the location and name of AntiXssLibrary.dll. See
Installing the Anti-Cross Site Scripting Library. [page 24]Choose
Next.
16. 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.
17. 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.
18. The installation process takes a few moments. When it is
complete, choose Exit.19. A prompt is displayed to restart your
computer. Select OK to restart.20. Perform the steps in After
Installing Planning and Consolidation Servers [page 27].
2.9 Installing the Server in a Multiserver
ConfigurationProcedureA 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
robin approach 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 24]) with the following exceptions: On the
Installation Method page, 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 Name field enter the virtual IP address / virtual
name in the default properties.
2 Installing Planning and Consolidation Servers2.9 Installing
the Server in a Multiserver Configuration
26/54 CUSTOMER 2012-06-13
-
3 After Installing Planning and Consolidation Servers
3.1 Post-Installation StepsProcedurePerform 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 allow
support staff to identify, analyze, and resolve problems with
your application. See Connecting to Solution Manager Diagnostics
[page 28].
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 29].
3. Optional configuration steps [page 30]: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 30].
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 31].
3. Manually set up an ODBC data source for the Management
Console. See Setting Up an ODBC Data Source [page 32].
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 32].
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 33].
6. Configure the use of client certificates for authentication.
See Using Client Certificates [page 34].
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 Servers3.1
Post-Installation Steps
2012-06-13 CUSTOMER 27/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, and task profiles. (You must
set 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.)
NOTETo allow users to request and query large amounts of data,
you can edit the metabase.xml file located at
C:\Windows\system32\inetsrv\. Set the following parameters to the
stated values: ASPBUFFERINGLIMIT = 10485760 MAXREQUESTENTITYALLOWED
= 10485760
3.2 Connecting to Solution Manager DiagnosticsNOTEYou 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.
Procedure1. Install the Diagnostics Agent according to SAP Note
1234387 on all servers where application servers
are installed.NOTEInstallation 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 After Installing Planning and Consolidation Servers3.2
Connecting to Solution Manager Diagnostics
28/54 CUSTOMER 2012-06-13
-
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 Of tab, 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 Login and 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
Servers
ProcedureModifying machine.config FilesTo 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.config file, which
resides in the
\WINDOWS\Microsoft.NET\Framework64\v4.0.30319\Config\ directory.1.
In .NET 4.0, the processModel element in machine.config supports
the attribute autoConfig to
specify whether to automatically configure settings to achieve
optimal performance based on the machine configuration. You can set
this attribute to True or 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 validationKey and decryptionKey keys
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 After Installing Planning and Consolidation Servers3.3
Configuring the Planning and Consolidation .NET Application
Servers
2012-06-13 CUSTOMER 29/54
-
#paght000007_webfarmdeploymentconsiderations and
http://msdn.microsoft.com/en-us/library/ms998310.aspx.
3.4 Post-Installation: Optional Configuration StepsThe 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 30].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 31].
3. Manually set up an ODBC data source for the Management
Console. See Setting Up an ODBC Data Source [page 32].
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 32].
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 33].
6. Configure the use of client certificates for authentication.
See Using Client Certificates [page 34].
3.4.1 Enabling the Management ConsoleProcedureTo 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 mode2. Create a Microsoft SQL Server
user to access AppServer as the default database. Give the
db_Owner database role to the user for AppServer database.3.
Enter the Microsoft SQL Server user information in the
BPC_ManagementDSN system DSN in
DataSource (OBDC).4. In the IIS Web site of the Planning and
Consolidation application server, modify the Active Log
Format option to use ODBC Logging. Enter the following values:
DSN is BPC_ManagementDSN Table is BPCLog The Microsoft SQL Server
Username and Password.
5. Restart IIS.
3 After Installing Planning and Consolidation Servers3.4
Post-Installation: Optional Configuration Steps
30/54 CUSTOMER 2012-06-13
-
NOTEWithout 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 Format
field in IIS to W3C Extended Log File Format.
3.4.2 Setting Up ODBC Logging in IIS for the Default Web
SiteThis procedure describes how to configure custom logging for
ODBC in IIS for the default Web site.
PrerequisitesODBC logging has been configured according to the
Microsoft Knowledge Base article 245243, How to configure ODBC
logging in IIS.
ProcedureSetting the Log File Format and customLogPluginClsidSet
the log file format and log plug-in ID for ODBC logging.In the file
ApplicationHost.config, set the property customLogPluginClsid to
the value {FF16065B-DE82-11CF-BC0A-00AA006111E0}. Set the logFormat
to 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.configConfigure 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
3 After Installing Planning and Consolidation Servers3.4
Post-Installation: Optional Configuration Steps
2012-06-13 CUSTOMER 31/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:appHostappcmd set config "Default Web Site"
/section:odbcLogging /tableName:"BPCLog" /commit:appHostappcmd set
config "Default Web Site" /section:odbcLogging /userName:"Username"
/commit:appHostappcmd set config "Default Web Site"
/section:odbcLogging /password:"mypassword" /commit:appHost
NOTEYou 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 Server 2008 or
Windows Server 2008 R2
ProcedureThis 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 Server as the driver. Choose Finish.
3. In the Name and Description fields, enter
BPC_ManagementDSN.4. In the Server field, enter the name of your
SQL Server. Choose Next.5. Leave the default settings, and choose
Next.6. Choose the Change the default database to field and enter
AppServer. Choose Next.7. Leave default settings, and choose
Next.8. Choose OK.
3.4.4 Removing Default Access to the ConsoleNOTEIf 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.
3 After Installing Planning and Consolidation Servers3.4
Post-Installation: Optional Configuration Steps
32/54 CUSTOMER 2012-06-13
-
ProcedureTo remove default access to the Management Console and
create a group that does have access to the console, use the
procedure described below.
NOTECreate 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 Computer icon, choose
Manage.2. In the Computer Management dialog box, choose Local Users
and Groups Groups .
NOTEAlternatively, you can perform analogous steps in Active
Directory.
3. In the Groups context 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 Console context menu, choose Permissions.7. Click Add,
and add the group you created earlier in this procedure.8. Click
Advanced.9. On the Permissions tab, 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.NOTEThis step is a necessary precursor to the
completion of this procedure.
10. In the Security dialog box, click Copy to ensure that the
System group retains its privileges.11. Remove access to the
Management Console from all groups that should not have it.12.
Choose Authentication in the center pane, then disable Windows
authentication.
ResultUsers 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.
3.4.5 Management Console Access ControlAfter 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 32]. 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
3 After Installing Planning and Consolidation Servers3.4
Post-Installation: Optional Configuration Steps
2012-06-13 CUSTOMER 33/54
-
Consolidation Administration Client task security. The user must
be granted View system logs task privileges. For more information,
see the SAP Library Planning and Consolidation Administrator's
Guide in 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 AreaTask Manager and Kill Process
Administrators group on application server or domainPerformance
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 Using Client CertificatesTo enable the use of client
certificates in Planning and Consolidation, you must follow several
manual steps.
NOTEPlanning and Consolidation supports client certificate
authentication in Windows Authentication Mode but 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.aspxFor more
information about configuring the client certificate mapping
authentication, see
http://technet.microsoft.com/en-us/library/cc732996(WS.10).aspxWhen
you create the client certificates, you can set the type of
certificate in the SSL Settings screen in Internet Information
Services (IIS) Manager.
Procedure1. 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
certificates section, select the Accept client certificates
option.
3 After Installing Planning and Consolidation Servers3.4
Post-Installation: Optional Configuration Steps
34/54 CUSTOMER 2012-06-13
-
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
ManagementConsole directory (/ManagementConsole) to open the
ManagementConsole home page.3. Double-click Authentication and
enable Anonymous Authentication.4. Select the BPC directory
(/SAP/BPC) and enable Anonymous Authentication the same way
as in step 3.5. Select the SBC directory (/SAP/POA/SBC) and
enable Anonymous Authentication the same
way as in step 3.3. Change the web configuration settings.
1. Open the ..\\Websrvr\Web\BPC\web.config file.2. Find the text
clientCredentialType="Windows".3. Change value of
clientCredentialType to "None" (clientCredentialType="None").4.
Open the ..\PC_MS\Websrvr\Web\POA\SBC\web.config file. Repeat steps
2 and 3.
3 After Installing Planning and Consolidation Servers3.4
Post-Installation: Optional Configuration Steps
2012-06-13 CUSTOMER 35/54
-
This page is left blank for documents that are printed on both
sides.
-
4 Installing Planning and Consolidation Administration Client
and the SAP BusinessObjects EPM solutions, Add-in for Microsoft
Office
The installation of the Planning and Consolidation
Administration Client allows administrators to build and maintain
Planning and Consolidation environments and models, and administer
security.All reporting, budgeting, publishing, and other user tasks
use the SAP BusinessObjects EPM solutions, add-in for Microsoft
Office; for more information, see the SAP BusinessObjects EPM
solutions, add-in for Microsoft Office help.
NOTE You must update the Administration Client to the same
version as the server. If your PC is on a different domain than
your server, you must set the Internet Explorer
Security Zone value of the Planning and Consolidation client to
prompt for user name and password. Otherwise, the Planning and
Consolidation Start Page does not display.
4.1 Installing the Administration ClientPrerequisites
NOTEFor a definitive list of system requirements, see the
Product Availability Matrix on SAP Service Marketplace at
http://service.sap.com/pam. Search on Planning and
Consolidation.
The following list describes the minimum software requirements:
Microsoft Internet Explorer 7.0 or 8.0 Microsoft Office 2007, or
2010 .NET Framework 2.0 or higher (install any required .NET
Framework Hotfixes by referring to:
http://support.microsoft.com/kb) Pentium IV (1 GHz CPU) 512 MB
RAM 100 MB of free hard disk space in the My Documents folder 20 MB
of free hard disk space for the installed Administration files
4 Installing Planning and Consolidation Administration Client
and the SAP BusinessObjects EPM solutions, Add-in for Microsoft
Office
4.1 Installing the Administration Client
2012-06-13 CUSTOMER 37/54
-
NOTEWe recommend that you install all of the latest Microsoft
Windows hotfixes prior to installing the Administration client. For
information about which hotfixes to install, see
http://update.microsoft.com/windowsupdate/v6/default.aspx?ln=en-us.
ProcedureThe following procedure describes how to install the
Administration Client on to an administrators machine.To install
the Administration Client, perform the following steps:1. Log on to
the machine as a member of the local administrators group.2.
Uninstall any previous versions of the SAP BusinessObjects Planning
and Consolidation
Administration Client.Use Add/Remove Programs in the Windows
Control Panel.
3. Point your browser to the Planning and Consolidation Web at
http:///sap/bpc/web.
4. Select the Download Center link or icon from the Planning and
Consolidation Launch page.5. Select Planning and Consolidation
Administration.6. Wait while the installation wizard verifies your
prerequisites, then select Next.7. From the installation wizard,
select Next.8. Select I accept the terms of the license agreement
and click Next.9. Select Next to install the program to the default
location.10. Choose Finish.
4.2 Installing the EPM Add-inThe Planning and Consolidation
installation media does not contain the EPM add.in setup program.
You must download the most recent version of the full setup (EPM
Add-in.exe) from the Service Marketplace (htp://service.sap.com)).
Copy this file to the server's ..\Websrvr\Web\BPC\Installation
folder.Individual users can install the EPM add-in on their own
machines by going to the Planning and Consolidation Home page and
choosing Install EPM Add-in for Microsoft Office from the Launch
area.
4.3 Using the Client Auto Update ProgramIf Planning and
Consolidation version 10.0 or later is installed, you can use the
Client Auto Update program to set up the server so that it
determines if an upgrade for a connecting Administration client is
necessary.The following describes the use of the auto update
program for the Administration Client and the EPM add-in.
4 Installing Planning and Consolidation Administration Client
and the SAP BusinessObjects EPM solutions, Add-in for Microsoft
Office
4.2 Installing the EPM Add-in
38/54 CUSTOMER 2012-06-13
-
ProcedureFor the Administration ClientIf Client Auto Update is
enabled and the system finds a newer version than the one
installed, it prompts the user to perform the upgrade. If Client
Auto Update is not enabled and a newer version is detected, clients
must be installed manually. For more information about manual
installation, see Installing the Administration Client [page 37].To
use the Client Auto Update program for the Administration Client,
proceed as follows:1. From the Server Manager, select Options
Client Options .2. Select Admin Update.3. If users without
administrator rights on their machines use the auto update, enter
an administrator
ID and password in the Admin ID and Admin password fields,
respectively. The Admin ID should be a member of the local
administrators group on all the computers running the auto update.
This setting is not needed if all users have administrator rights
on their machines.
4. Select Update.
For the EPM Add-inThe following types of update are possible:
User Update
In this case, the notification dialog allows a user to choose an
option that suppresses future notifications. This option is stored
in the user preferences, and may also be turned on or off using the
User Options menu item. If Auto Update is activated on the server,
this option has no effect.
Auto UpdateIn this case, the update notification is displayed as
soon as a newer version is detected. Users can choose to install
the new package now or later, but has no way to stop notifications,
whatever the Auto Update setting is.
Force UpdateIn this case, the update notification is displayed
as soon as a newer version is detected, and a user has to install
it before using the EPM add-in:
The following describes the use of the update procedure for the
EPM add-in:1. Download the add-in file from the SAP Market Place
(SMP) at http://service.sap.com.
All support packages and patches are available from the SMP as a
zip file: EPMEXCLCLNT.zip is for a support package EPMEXCLCLNTP.zip
is for a patchThe zip file includes two files. One is installation
package and the other is information file that includes version and
policy information. For a support package, these files are: EPM
Addin Support Package .msp EPM Addin Support Package .xmlFor a
patch, these files are:
4 Installing Planning and Consolidation Administration Client
and the SAP BusinessObjects EPM solutions, Add-in for Microsoft
Office
4.3 Using the Client Auto Update Program
2012-06-13 CUSTOMER 39/54
-
EPM Addin Patch .msp EPM Addin Patch .xml
2. Unzip the zip file and extract the two files to the
application server folder (\Websrvr\Web\BPC\Installation\).
3. From the Server Manager, select Options Client Options .The
system lists the available packages. Select the package that you
want to use for the autoupdate.You can set a different update
policy for each package listed.
EXAMPLEThe following table illustrates some possible situations
assuming that you have installed the first full version
(V1):Available maintenance packages
V2-user updateV3-force updateV4-force updateV5-user update
V5-user update V5-user updateV6-auto updateV7-force update
Minimum Required Version
V4 V4 V7
Notification A prompt tells the user to install maintenance
package V4 using the Forced Update behavior.
If User Update is enabled, the prompt informs the user that
maintenance package V5 is available.
A prompt tells the user to install maintenance package V7 using
the Forced Update behavior.
New Version V4 V4 or V5 V7
If you change the update policy for any package, click Update to
complete the change.
4 Installing Planning and Consolidation Administration Client
and the SAP BusinessObjects EPM solutions, Add-in for Microsoft
Office
4.3 Using the Client Auto Update Program
40/54 CUSTOMER 2012-06-13
-
5 Connection Issues
You may experience connection problems with ports, the proxy
server, or programs and settings that interact with these
components. If you have any issues related to connection, review
the following recommendations and troubleshooting tips.
5.1 Checking for Open PortsYou must ensure that all required
ports are open for inbound/outbound traffic. By default, Planning
and Consolidation requires that Ports 80 (used by http) and 1433
and 2383 (used by SQL Server 2008) are open. To test whether the
required ports are open, go to a command prompt and enter the
Telnet serveripaddress and port. For example, Telnet 43.118.18.36
80. If the system returns a blank command window, the port is open.
If it returns a message stating that it is unable to connect, the
port is not open.
NOTEYou can use the following site to scan for the normal ports.
It allows you to manually enter a port number to
test.http://www.myserver.org/portsniff.aspYou can change the name
of a port.
5.2 Proxy Server and Firewall IssuesFor questions about specific
proxy servers, contact SAP Support.
General Considerations If you connect to the Internet through a
firewall or proxy server, you need to add the IP address
of the Planning and Consolidation server as an exception. You
can do this at the client level ( Internet Explorer Tools Internet
Options Connections LAN Settings ) or at the server level.
Enabling content filtering on the proxy server or firewall may
cause connection problems. If external users are having trouble
connecting to the server, make sure the proxy server connects
using a fully qualified domain name. Fully qualified domain
names typically resolve both internal and external IP
addresses.
Each secure Planning and Consolidation server name must be
identified on the proxy server. Proxy servers may or may not
require authentication, which could conflict with Planning and
Consolidation authentication. Do not use authentication on the
proxy server. The system
5 Connection Issues5.1 Checking for Open Ports
2012-06-13 CUSTOMER 41/54
-
synchronizes the user name and password on the remote server
with the local user name and password.
NOTEFor more information about setting up an ISA proxy server,
contact SAP Support to request a copy of Setting up ISA Proxy
Server White Paper.
Internet Explorer Settings IssuesInternet Explorer settings must
be set correctly to prevent errors and problems when you attempt to
access the Planning and Consolidation server using the Connection
Wizard. Change the settings by taking the following steps:1. From
Internet Explorer, select Tools Internet Options .2. From the
General tab, delete all temporary Internet files, cookies, and
history.3. From the Security tab, set security to Default level for
Internet and local intranet.4. From the Connections tab, choose the
LAN settings button. If you select Use a proxy server for your
LAN,
insert the IP address or fully qualified server name of the
Planning and Consolidation server as an exception by choosing
Advanced.
5. From the Advanced tab, choose Restore Defaults, Apply, then
OK.
Microsoft Windows IssuesIf you have Windows XP SP2, disable the
Microsoft Windows firewall.
Norton AntiVirus IssuesHaving Script Blocking enabled in Norton
AntiVirus can cause some display and download issues.
5 Connection Issues5.2 Proxy Server and Firewall Issues
42/54 CUSTOMER 2012-06-13
-
6 Installing Planning and Consolidation with Two Active
Directory Domains
To set up a Planning and Consolidation 10 application server in
a hosted environment and use your own domain users, follow this
procedure. In general, you install Planning and Consolidation on
the host domain, use the host domain account and assign it to the
Planning and Consolidation users SysAdmin, Admin, and Users. Then,
you accept one way trust (the host domain trusts your domain).
Procedure1. Create one way trust from the host domain to your
domain. You must know the administrator
user ID and password of your domain to create this
relationship.2. Browse all of your domain users from the host
domain servers.3. On your Planning and Consolidation server, give
administrator privileges to one of your domain
accounts to promote it to a Planning and Consolidation system
account.4. Log on to your Planning and Consolidation server using
your domain user that has the
administrator privilege for the Planning and Consolidation
server.5. Install Planning and Consolidation and assign your domain
account either to the three Planning
and Consolidation administrative users SysAdmin, Admin, and
Users, or to only one of the three Planning and Consolidation
administrative users and to three of your users. Be sure you use
your own user account rather than host domain users.Planning and
Consolidation impersonation can then access your domain from the
host environment because it has the privilege of your domain
account.
6 Installing Planning and Consolidation with Two Active
Directory Domains
2012-06-13 CUSTOMER 43/54
-
This page is left blank for documents that are printed on both
sides.
-
7 Installing Planning and Consolidation in a Terminal Services
or Citrix Server Deployment
This section describes best practices and instructions for
installing Planning and Consolidation in a Terminal Services or
Citrix Server deployment.
7.1 Terminal Services Home DirectoriesWe recommend using
Terminal Server home director