SAP BusinessObjects Planning and Consolidation 10

Installation GuideDocument version: 2.4 – 2017-04-25

SAP BusinessObjects Planning and Consolidation 10.0version for the Microsoft platform

CUSTOMER

© Copyright 2016 SAP SE or an SAP affiliate company. Alle Rechte vorbehalten. All rights reserved. Tous droits réservés. Все права защищены.

Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden.

Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch SAP SE oder ein SAP-Konzernunternehmen nicht gestattet.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.

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.

Some 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 SAP’s Support Services and may not be modified or altered in any way.

2

CUSTOMER© Copyright 2016 SAP SE or an SAP affiliate company.All rights reserved. SAP BusinessObjects Planning and Consolidation 10.0

Document History

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

Table 1

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 36] 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 40] 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.7 2014-04-02 Added topics about configuring SSL in IIS and in SQL Server Reporting Services.

1.8 2015-05-28 ● Added a link to SAP Note 2089752 in the Other Requirements section of Prerequisites [page 10].

SAP BusinessObjects Planning and Consolidation 10.0Document History

CUSTOMER© Copyright 2016 SAP SE or an SAP affiliate company.

All rights reserved. 3

Version Date Description

● Added SQL Server 2014 to various sections of the table and the recommendation in Prerequisites [page 10].

● Added the location of the ADOMD.NET installation package for SQL Server 2014 in the topic Installing the Prerequisites - Basic Steps [page 17].

● Added Microsoft Internet Explorer 11.0 and Microsoft Office 2013 to the minimum software requirements in Installing the Administration Client [page 36].

● Added SQL Server 2014 in information to the topics Composition of SSIS Custom Task Installation [page 45] and Before You Modify the SSIS Packages [page 49].

● Minor editorial changes throughout the document.

1.9 2015-08-04 ● Removed Microsoft Office 2012 from the list of prerequisites in Installing the Administration Client [page 36].

● Updated the system requirements of the Citrix server to XenApp 5, XenApp 6, or XenApp 6.5 in System Requirements [page 43].

2.0 2015-08-19 Added information about creating a detailed installation log to the Optional Tasks section in Before Starting the Planning and Consolidation Server Installation [page 12].

2.1 2016-01-07 In Installing the Administration Client [page 36], updated the releases of Microsoft Internet Explorer and Microsoft Office supported with support package 20.

2.2 2016-01-11 In Installing the Administration Client [page 36], modified the list of supported Microsoft Internet Explorer releases.

2.3 2016-04-20 ● Added Windows Server 2012 and Microsoft SQL Server 2014 Business Intelligence Edition to various sections of the table in Prerequisites [page 10].

● Added Office 2016 to the minimum software requirements in Installing the Administration Client [page 36].

2.4 2017-04-25 ● In SAP Notes for the Installation [page 7], added the central note numbers 2298949

and 2379786 for support packages 22 and 23.

● In the section “Real Time MOLAP” within Installing the SQL Server [page 19], added a

link to SAP note 2408396 for more information.

4

CUSTOMER© Copyright 2016 SAP SE or an SAP affiliate company.All rights reserved.

SAP BusinessObjects Planning and Consolidation 10.0Document History

http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2F~form%2Fhandler%3F_APP%3D01100107900000000342%26_EVENT%3DREDIR%26_NNUM%3D2298949%26_NLANG%3Den%26_NVERS%3D0



Content

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.1 SAP Notes for the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.2 Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2 Installing Planning and Consolidation Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.1 Basic Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.2 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.3 Before Starting the Planning and Consolidation Server Installation . . . . . . . . . . . . . . . . . . . . . . . . . . 122.4 Logging on to Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.5 Service-level Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.6 Standard and Advanced Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.7 Installing the Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Installing the Prerequisites – Basic Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Installing the Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Installing the SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Installing Analysis Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Installing the Anti-Cross Site Scripting Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

2.8 Installing on a Single Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232.9 Installing the Server in a Multiserver Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

3 After Installing Planning and Consolidation Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263.1 Post-Installation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263.2 Connecting to Solution Manager Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273.3 Configuring the Planning and Consolidation .NET Application Servers . . . . . . . . . . . . . . . . . . . . . . . 283.4 Post-Installation: Optional Configuration Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Enabling the Management Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Setting Up ODBC Logging in IIS for the Default Web Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2 . . . . . . . . 31 Removing Default Access to the Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Management Console Access Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Configuring Planning and Consolidation to use SSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Using Client Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Configuring MS SQL Server Reporting Services to use SSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions, Add-in for Microsoft Office . . . . . . . . . . . . . . . . . . . . . . . . . . 36

4.1 Installing the Administration Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364.2 Installing the EPM Add-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374.3 Using the Client Auto Update Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

5 Connection Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405.1 Checking for Open Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405.2 Proxy Server and Firewall Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

SAP BusinessObjects Planning and Consolidation 10.0Content



6 Installing Planning and Consolidation with Two Active Directory Domains . . . . . . . . . . . . . . . . 42

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

7.1 Terminal Services Home Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437.2 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437.3 Installing Planning and Consolidation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437.4 Creating a Shortcut to the Launch Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

8 Installing SSIS Custom Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458.1 Composition of SSIS Custom Task Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458.2 Before You Modify the SSIS Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498.3 Setup of a COM+ Application on the Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

6


SAP BusinessObjects Planning and Consolidation 10.0Content

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 the SAP Help Portal at help.sap.com/bopacms100 .

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.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 on the SAP Support Portal at support.sap.com/notes

.

Table 2:

SAP Note Number Title Comments

1584890 Documentation Addendum Contains information that does not yet appear in the application help of Business Planning and Consolidation 10.0, version for the Microsoft platform.

2379786 Planning & Consolidation 10 for Microsoft SP23 Central Note

This note contains important information about the installation of support package 23.



SAP BusinessObjects Planning and Consolidation 10.0Introduction



http://help.sap.com/disclaimer?site=help.sap.com%2Fbopacms100

http://help.sap.com/disclaimer?site=support.sap.com%2Fnotes











































8



























1.2 Naming Conventions

In this document, the following naming conventions apply.

Table 3

Variable Description

<PC_server:port> Server name or IP address and port number of SAP Planning and Consolidation application location.

<drive> The drive where SAP Planning and Consolidation is installed.

The default for this is C:/PC_MS.






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 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 Guide on

the SAP Help Portal at help.sap.com/bopacms100 .

2. Perform the tasks in the Before Starting the Planning and Consolidation Server Installation [page 12] 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 23].

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 support.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 25].

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

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.

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

Matrix on the SAP Support Portal at support.sap.com/pam . Search on Planning and Consolidation.

10


SAP BusinessObjects Planning and Consolidation 10.0Installing Planning and Consolidation Servers

http://help.sap.com/disclaimer?site=help.sap.com%2Fbopacms100

http://help.sap.com/disclaimer?site=http%3A%2F%2Fsupport.sap.com%2Fswdc

http://help.sap.com/disclaimer?site=http%3A%2F%2Fsupport.sap.com%2Fswdc

http://help.sap.com/disclaimer?site=http%3A%2F%2Fsupport.sap.com%2Fpam

Table 4

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, Data Center with or without Hyper-V

● Windows Server 2012 (64-bit) Standard, Data Center

● Windows Server 2012 R2 (64-bit) Standard, Data Center

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

● Microsoft SQL Server 2014 Enterprise Edition

● Microsoft SQL Server 2014 Business Intelligence 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

● Microsoft SQL Server 2014 Enterprise Edition - Analysis Server

● Microsoft SQL Server 2014 Business Intelligence 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

● Microsoft SQL Server 2014 Enterprise Edition - SQL Service Integration Services

● Microsoft SQL Server 2014 Business Intelligence 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

○ ADOMD.NET 12.0 when running SQL Server 2014

● 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




Component Minimum Requirement

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 64-bit

● 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++ 2010 SP1 Redistributable Package (x64) are included with the installation program, but not installed automatically. For more information about installing Windows roles and

features, see SAP Note 2089752

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 values being returned

with calculated accounts. For more information, see SAP note 1429246 , which also contains download information.

● We recommend SQL Server 2008 (or R2) Enterprise Edition, SQL Server 2012 Enterprise Edition, or SQL Server 2014 Enterprise Edition for the OLAP database to support proactive cache and cube partitioning. It is technically possible to use the standard editions of each for data integration servers, but we do not recommend this.

2.3 Before Starting the Planning and Consolidation Server Installation

Required Tasks

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

● 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 40].

● Set up the required service accounts that you need to install the Planning and Consolidation server. See Service-Level Accounts [page 14].

12





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

● 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 13].

● 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 23].

Optional Tasks

● You can create a detailed installation log by performing these steps:

1. Open Registry Editor.

2. Go to the HKEY_LOCAL_MACHINE\SOFTWARE\OUTLOOKSOFT key.

3. Create a new DWORD value named LOGLEVEL with a Value Data of 1000 and a Base of Hexadecimal.

4. After you run an SBOP BPC for MS installation, the detailed installation log OSoftSetupDetail.Log can be found under the C:\ root folder.

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.

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 service.sap.com/instguidesepm-bpc 10.0, for the Microsoft Platform SBOP Plan & Consol 10.0 MS Administrator's Guide .

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.

14



http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2Finstguidesepm-bpc

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: 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 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 and SQL. 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.

NoteWhen defining server names, the name refers to the NetBIOS name, IP address, and fully qualified domain names (FQDN).

Standard Settings

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

Table 5

Server Option Value Description

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




http://help.sap.com/disclaimer?site=http%3A%2F%2Fsupport.microsoft.com%2Fkb%2F259733


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 Settings

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

Table 6


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

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

16




See the Kerberos authentication settings section in the SAP Library Server

Manager Guide on 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 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 Prerequisites [page 10] and the Product Availability

Matrix on the SAP Support Portal at support.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.

Procedure

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




http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2FinstguidesEPM-BPC


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

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

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

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

○ For SQL Server 2014 — \BPC Setup\Server\SQL_AS_ADOMD.msi or download ENU

\x64\SQL_AS_ADOMD.msi from www.microsoft.com/en-us/download/details.aspx?id=42295

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.

NoteThe 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: www.microsoft.com/downloads/en/details.aspx?

FamilyID=C06B8369-60DD-4B64-A44B-84B371EDE16D&<displaylang>=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 Support Portal at

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

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

18



http://help.sap.com/disclaimer?site=http%3A%2F%2Fwww.microsoft.com

http://help.sap.com/disclaimer?site=http%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fdownload%2Fdetails.aspx%3Fid%3D42295

http://help.sap.com/disclaimer?site=http%3A%2F%2Fwww.microsoft.com%2Fdownloads%2Fen%2Fdetails.aspx%3FFamilyID%3DC06B8369-60DD-4B64-A44B-84B371EDE16D%26%3Cdisplaylang%3E%3Den

http://help.sap.com/disclaimer?site=http%3A%2F%2Fwww.microsoft.com%2Fdownloads%2Fen%2Fdetails.aspx%3FFamilyID%3DC06B8369-60DD-4B64-A44B-84B371EDE16D%26%3Cdisplaylang%3E%3Den


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

Procedure

This section describes the general steps for installing the SQL Server, component options, and considerations when installing and configuring 2008, 2008 R2, 2012, or 2014 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 Steps

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

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 Options

For Single-Machine Installations

Install the following components from the Feature Selection screen:

● 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:

Table 7

Server Component What to Install

SQL Server Database Engine Services

SSAS Server Analysis Services

Application Server The following Shared Features:

● Client Tools Connectivity

20



Server Component What to Install

● 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, SQL Server 2012, and SQL Server 2014:

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.

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

You 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 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 tblFactWB<app> table

For more information, see SAP note 2408396 .

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, SQL Server 2012, and SQL Server 2014

● 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 <InstanceName>, 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.

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.

22



http://help.sap.com/disclaimer?site=http%3A%2F%2Fwww.microsoft.com

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.

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, SQL Server 2012, or SQL Server 2014,

follow the steps and guidelines in 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 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.DLL from the Microsoft Web site at

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




http://help.sap.com/disclaimer?site=http%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fms143219.aspx

http://help.sap.com/disclaimer?site=http%3A%2F%2Fwww.microsoft.com%2Fdownloads%2Fdetails.aspx%3FFamilyID%3D3be0488d-e7aa-4078-a050-ae39912d2e43%26displaylang%3Den

http://help.sap.com/disclaimer?site=http%3A%2F%2Fwww.microsoft.com%2Fdownloads%2Fdetails.aspx%3FFamilyID%3D3be0488d-e7aa-4078-a050-ae39912d2e43%26displaylang%3Den

http://help.sap.com/disclaimer?site=http%3A%2F%2Fwww.microsoft.com%2Fdownload%2Fen%2Fdetails.aspx%3Fid%3D28589

● Application Server

● FileShare server

Procedure

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

1. Exit all Windows programs.

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

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 archive from the Downloads SAP Installations & Upgrades area of SAP Service Marketplace.

5. Extract the files from the archive. Go to the BPC Setup folder and run the StartUp.exe file.

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

7. From the Welcome screen, choose Next.

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

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

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

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

Table 8

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.

24



13. From the Service type accounts page, enter service-level account user IDs and passwords. See Service-Level Accounts [page 14].

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

15. From the Server Information page (see Standard and Advanced Settings [page 15]), 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.

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

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 OK to restart.

21. Perform the steps in After Installing Planning and Consolidation Servers [page 26].

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 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 23]) 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.




3 After Installing Planning and Consolidation 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 allow support staff to identify, analyze, and resolve problems with your application. See Connecting to Solution Manager Diagnostics [page 27].

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

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

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

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

○ 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 36].

26


SAP BusinessObjects Planning and Consolidation 10.0After Installing Planning and Consolidation Servers

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 Diagnostics

NoteYou 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 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 systemsDIAGNOSTICS AGENT 7.11 .

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 SQLServer<Release>SQLAgentUser$<Domain or hostname>$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 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

Procedure

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

2. If you are using a Web farm, you must change the <machineKey> 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

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

and 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 29].

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

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

28



http://help.sap.com/disclaimer?site=https%3A%2F%2Fservice.sap.com%2F~sapidb%2F011000358700000074392009E

http://help.sap.com/disclaimer?site=http%3A%2F%2Fmsdn.microsoft.com%2Fen-us%2Flibrary%2Fms998288.aspx%23paght000007_webfarmdeploymentconsiderations

http://help.sap.com/disclaimer?site=http%3A%2F%2Fmsdn.microsoft.com%2Fen-us%2Flibrary%2Fms998310.aspx

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

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

8. Configure Microsoft SQL Server Reporting Services to use SSL. See Configuring MS SQL Server Reporting Services to use SSL [page 35].

3.4.1 Enabling the Management Console

Procedure

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

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 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 customLogPluginClsid to the value {FF16065B-DE82-11CF-BC0A-00AA006111E0}. Set the logFormat to Custom. You can find this in the <logFile> node in ApplicationHost.config, as shown here:

<logFile customLogPluginClsid="{FF16065B-DE82-11CF-BC0A-00AA006111E0}" logFormat="Custom" />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 <odbcLogging> node under <system.webServer>.

Example<location path="Default Web Site"><system.webServer><odbcLogging dataSource="BPC_ManagementDSN" tableName="BPCLog" userName="Username" password="mypassword" /></system.webServer></location>

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

30



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

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

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




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.

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.

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 logs task privileges. For more information, see the SAP Library

32



Planning and Consolidation Administrator's Guide in 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:

Table 9

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.

RecommendationWe 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 ProgramsAdministrative Tools Internet Information Services (IIS) Manager .

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

3. In the Actions panel on the right hand side, choose the Create Self-Signed Certificate action.

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 year’s 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 Connections panel, select the web site node.




http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2Finstguidesepm-bpc

2. In the Actions panel choose Bindings.

3. In the Site Bindings dialog that appears, choose the Add button 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 OK to create the new binding and then close the Site Bindings dialog.

6. Restart the IIS processes. To do this, choose Restart from the Actions panel.

7. In the middle panel, under the IIS section, choose SSL Settings.

8. In the SSL Settings screen select the Require SSL checkbox.

9. In the Actions panel choose to Apply these settings.

To test the SSL connection, in the Actions panel, 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 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 technet.microsoft.com/en-us/library/cc753810.aspx

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

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 certificates section, select the Accept client certificates option.

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.

34



http://help.sap.com/disclaimer?site=http%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fcc753810.aspx

http://help.sap.com/disclaimer?site=http%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fcc732996(WS.10).aspx

2. Select the ManagementConsole directory (<Website>/ManagementConsole) to open the ManagementConsole home page.

3. Double-click Authentication and enable Anonymous Authentication.

4. Select the BPC directory (<Website>/SAP/BPC) and enable Anonymous Authentication the same way as in step 3.

5. Select the SBC directory (<Website>/SAP/POA/SBC) and enable Anonymous Authentication the same way as in step 3.

3. Change the web configuration settings.

1. Open the ..\<PC_MS>\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.4.8 Configuring MS SQL Server Reporting Services to use SSL

Procedure

The procedure below describes how to configure the use of SSL in Microsoft SQL Server Reporting Services.

NoteReporting Services does not provide functionalities for generating, requesting, or installing a certificate. The server certificates that you want to use for configuring SSL must have already been installed on your computer.

1. Open the Reporting Services Configuration Manager program. To do this, open the Windows Start menu and navigate to All Programs Microsoft SQL Server <version> Configuration Tools Reporting Services Configuration Manager .

2. In the Connect panel on the left-hand side, select the Web Service URL option to open all the Report Server web service parameters.

3. Configure the parameters as follows:

○ SSL Certificate = the name of the certificate that you want to use

○ SSL Port = 4434. Choose Apply to confirm the changes.

5. In the Connect panel, choose Report Manager URL to open the list of parameters that link Reporting Services to IIS.

6. Choose Advanced to add your new SSL web URL.

7. In the section Multiple SSL Identities for Report Manager, choose Add. Configure the parameters as follows:

○ IP Address = (All IPv4)○ SSL Port = 443○ Certificate = the name of your SSL certificate

8. To test the configuration, click the URL that appears under the Report manager Site Identification section.




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 Client

Prerequisites

NoteFor a definitive list of system requirements, see the Product Availability Matrix on the SAP Support Portal at

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

The following list describes the minimum software requirements:

● Microsoft Internet Explorer 7.0, 8.0, 9.0, 10.0 or 11.0, or Mozilla Firefox Rapid Release

● Microsoft Office 2007, 2010, 2013, 2013 in Office 365, or Office 2016

● .NET Framework 2.0 or higher (Install any required .NET Framework hot fixes by referring to:

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

36


SAP BusinessObjects Planning and Consolidation 10.0Installing Planning and Consolidation Administration Client and the SAP

BusinessObjects EPM solutions, Add-in for Microsoft Office


http://help.sap.com/disclaimer?site=http%3A%2F%2Fsupport.microsoft.com%2Fkb

NoteWe recommend that you install all of the latest Microsoft Windows hot fixes prior to installing the Administration client. For information about which hot fixes to install, see update.microsoft.com/

windowsupdate/v6/default.aspx?ln=en-us .

Procedure

The following procedure describes how to install the Administration Client on to an administrator’s 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 <PC_server:port>/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-in

The 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 SAP Support Portal at

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

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

SAP BusinessObjects Planning and Consolidation 10.0Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions, Add-in for Microsoft Office



http://help.sap.com/disclaimer?site=http%3A%2F%2Fupdate.microsoft.com%2Fwindowsupdate%2Fv6%2Fdefault.aspx%3Fln%3Den-us

http://help.sap.com/disclaimer?site=http%3A%2F%2Fupdate.microsoft.com%2Fwindowsupdate%2Fv6%2Fdefault.aspx%3Fln%3Den-us

http://help.sap.com/disclaimer?site=http%3A%2F%2F%3CPC_server%3Aport%3E%2Fsap%2Fbpc%2Fweb

http://help.sap.com/disclaimer?site=http%3A%2F%2Fsupport.sap.com

Procedure

For the Administration Client

If 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 36].

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

The 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 Update

In 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 Update

In 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 Support Portal at support.sap.com .

All support packages and patches are available as a zip file:

○ EPMEXCLCLNT<SPL>.zip is for a support package

○ EPMEXCLCLNT<SPL>P<PL>.zip is for a patch

The 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 <SP version>.msp○ EPM Addin Support Package <SP version>.xmlFor a patch, these files are:

○ EPM Addin Patch <patch number>.msp○ EPM Addin Patch <patch number>.xml

2. Unzip the zip file and extract the two files to the application server folder (\Websrvr\Web\BPC\Installation\).

38


SAP BusinessObjects Planning and Consolidation 10.0Installing Planning and Consolidation Administration Client and the SAP

BusinessObjects EPM solutions, Add-in for Microsoft Office

http://help.sap.com/disclaimer?site=http%3A%2F%2Fsupport.sap.com

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

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):

Table 10

Available maintenance packages

V2-user update

V3-force update

V4-force update

V5-user update

V5-user update V5-user update

V6-auto update

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

SAP BusinessObjects Planning and Consolidation 10.0Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions, Add-in for Microsoft Office



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 Ports

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

www.myserver.org/portsniff.asp

You can change the name of a port.

5.2 Proxy Server and Firewall Issues

For 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 ExplorerTools 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 synchronizes the user name and password on the remote server with the local user name and password.

40


SAP BusinessObjects Planning and Consolidation 10.0Connection Issues

http://help.sap.com/disclaimer?site=http%3A%2F%2Fwww.myserver.org%2Fportsniff.asp

Internet Explorer Settings Issues

Internet 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 Issues

If you have Windows XP SP2, disable the Microsoft Windows firewall.

Norton AntiVirus Issues

Having Script Blocking enabled in Norton AntiVirus can cause some display and download issues.

SAP BusinessObjects Planning and Consolidation 10.0Connection Issues



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

Procedure

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

42


SAP BusinessObjects Planning and Consolidation 10.0Installing Planning and Consolidation with Two Active Directory Domains

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 Directories

We recommend using Terminal Server home directories rather than using the user’s profile directory. The profile directory downloads a minimal amount of information about the dimensions of the environment you are logging on to and may be as large as 2 MB per user. The profile directory is on the system drive and has limited space. By specifying a home directory, you can manage the disk space required.

If you have a farm of servers, put the profile information in a common home directory rather than on each individual server, so that all users consistently use the current download of dimensions.

7.2 System Requirements

The Citrix server should be one of the following systems:

● XenApp 5

● XenApp 6

● XenApp 6.5

The XenApp program must be installed on a Windows 2008 or 2008 R2 server.

The Terminal Services or Citrix Server computer requires the same client software as would be installed on the client server (see Installing Planning and Consolidation Clients [page 36]).

7.3 Installing Planning and Consolidation

Prerequisites

The server installation files have been downloaded from SAP Service Marketplace and installed.

SAP BusinessObjects Planning and Consolidation 10.0Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment



Procedure

The following steps outline how to install the Planning and Consolidation clients in a Terminal Services (TS) or Citrix Server deployment:

1. Make sure the Terminal Services or Citrix Server machine has the system requirements installed.

2. Log on to the Terminal Services or Citrix Server machine with a user ID that has the rights to install on that server.

3. At a command prompt, enter Change user/install.

4. Open a browser and connect to the URL <PC_server:port>/sap/bpc/web .

5. Log on to the Web site with the service account, password, and domain.

6. Go to the Download Center and install the Planning and Consolidation Administration client.

7. Go back to the command prompt and enter Change user/execute or Restart the server.

8. For the Citrix Server, you must publish each client application. Complete the following steps:

○ To publish the Planning and Consolidation Launch page: Iexplore.exe http(s)://<ServerName>-NetBIOS or FQDN/sap/bpc/web

○ To publish Planning and Consolidation Administration: C:\Program Files\PC_MS\BPCAdminMain.exe

7.4 Creating a Shortcut to the Launch Page

Procedure

If you use published desktops instead of published applications, the Planning and Consolidation desktop file (which is installed on the current user’s desktop) must be moved to the All Users/Desktop folder.

44


SAP BusinessObjects Planning and Consolidation 10.0Installing Planning and Consolidation in a Terminal Services or Citrix Server

Deployment

http://help.sap.com/disclaimer?site=http%3A%2F%2F%3CPC_server%3Aport%3E%2Fsap%2Fbpc%2Fweb

8 Installing SSIS Custom Tasks

This section provides background information and instructions for installing SQL Server Integration Services (SSIS) for SQL Server 2008, SQL Server 2012, and SQL Server 2014.

The Planning and Consolidation Data Manager component supports and uses SSIS. Since SQL Server 2008, SQL Server 2012, and SQL Server 2014 support the remote modification of SSIS packages, Planning and Consolidation also supports the remote modification of SSIS packages with system and custom tasks.

To successfully modify an SSIS package that contains Data Manager custom tasks, do so on the machine on which you want to modify SSIS packages.

These custom tasks reference dlls that connect to the database server and perform certain validation when users set up the parameters of each task. All the custom task reference components must also be installed in the machine on which you want to modify SSIS packages.

We provide a program that registers all the reference components of the custom tasks. This section explains the installation package and how to use it.

8.1 Composition of SSIS Custom Task Installation

You use the following elements when you install SSIS Custom tasks:

● Bin folder – This folder contains all the dlls that should be installed on the machine. There are Planning and Consolidation platform components and all of the Data Manager custom task files.

● Config folder – This folder contains only one file named Filelist.xml and lists all of the files that should be installed. If you need to add or remove certain components from the installation, you can modify this xml file.

● OSoftSetup.exe – This is the main executable file to run the installation package.

Note● If you are not installing SSIS Custom Tasks on your client machine – specifically, a machine other than the

Planning and Consolidation application server – you must first install OSoftSSIS2008_Client, OSoftSSIS2012_Client, or OSoftSSIS2014_Client on the client machine followed by the SQL Server version. If you want to use SQL 2008 Tasks under a SQL 2012 or 2014 environment, you must install

OSoftSSIS2008_Client on the application server. For detailed information, see SAP Note 1707410 .

● You can find the OSoftSSIS2008_Client, OSoftSSIS2012_Client, or OSoftSSIS2014_Client installation package by extracting OSoftSSIS2008_Client.zip, OSoftSSIS2012_Client.zip, or OSoftSSIS2014_Client.zip from the <drive>\Websrvr\Web\BPC\Installation folder on the Planning and Consolidation server.

● To modify SSIS packages on the Planning and Consolidation application server, you need to install OSoftSSIS2008_Client, OSoftSSIS2012_Client, or OSoftSSIS2014_Client for creating a COM+ application. For more information, see Before You Modify the SSIS Packages [page 49], Setup of a COM+ Application

on the Application Server [page 50], and SAP note 2122201 .

SAP BusinessObjects Planning and Consolidation 10.0Installing SSIS Custom Tasks





Bin folder

This folder contains the following components:

Table 11

Name Remark

BPCTaskAdmin.dll

BPCTaskAdmin2012.dll


Data Manager custom task for SQL 2008, 2012, and 2014, respectively

BPCTaskAudit.dll

BPCTaskAudit2012.dll



BPCTaskAvailable.dll

BPCTaskAvailable2012.dll



BPCTaskComment.dll

BPCTaskComment2012.dll



BPCTaskConvert.dll

BPCTaskConvert2012.dll



BPCTaskDumpLoad.dll

BPCTaskDumpLoad2012.dll



BPCTaskLogic.dll

BPCTaskLogic2012.dll



BPCTaskMakeDim.dll

BPCTaskMakeDim2012.dll



BPCTaskOwnership.dll

BPCTaskOwnership2012.dll



BPCTaskSendMail.dll

BPCTaskSendMail2012.dll



BPCTaskTrigger.dll

BPCTaskTrigger2012.dll



46



Name Remark

BPCCache.dll Planning and Consolidation Cache file

BPCDataFlowPackage.dll

BPCDataFlowPackage2012.dll

BPCDataFlowPackage2014.dll

BPCDM.dll

BPCDMTaskMain.dll COM+ component

BPCFilePreview.dll

BPCGacUtil_20.exe System File

BPCGacUtil_40.exe System File

BPCImpersonator.dll Planning and Consolidation Impersonator

BPCLogic.dll

BPCScript.dll

BPCServerZip.dll

BPCServiceRes.dll

BPCTransferMembers.dll

BPCWriteBack.dll

Interop.DTS.dll

OSoftAdminServer.dll

OSoftAudit.dll

OSoftComLibServer.dll

OSoftCommonResQry.dll

OSoftConfiguration.dll

OSoftCustomXMLSvr.dll

OSoftDatabaseADMIN.dll

OSoftDatabaseSYSADMIN.dll

OSoftDatabaseSYSADMINDM.dll

OSoftDatabaseUSER.dll

OSoftDMDTSXExecute.dll

OSoftDMDTSXExecute2012.dll

OSoftDMDTSXExecute2014.dll

OSoftDMTaskForm.dll

OSoftDMTaskMain.dll




Name Remark

OSoftDMTools.dll

OSoftFileManage.dll

OSoftLogging.dll

OSoftLogWriter.dll

OSoftMetaData.dll

OSoftSQE.dll

OSoftSystemConfig.dll

OutlookSoft.config Configuration file to connect DB server

Xceed.Compression.dll XceedZip file

Xceed.Compression.Formats.dll XceedZip file

Xceed.FileSystem.dll XceedZip file

Xceed.Zip.dll XceedZip file

Config folder

This folder has FileList.xml file, which contains the registration method of each component. If you need to add more components to the installation package, you can copy the new components into the Bin folder and add the proper xml tags in FileList.xml. You need to enter information for the following tags:

● RegistType – This is the registration information of the component. You can enter the following values:

○ RegAsm – For .NET component

○ Regsvr32 – For VB6 component

○ Gacutil – For .NET Framework component that should be registered into Global Assembly Cache

● FileName – Component file name

OSoftSetup.exe

This is the executable file to run the SSIS installation package. Double-click the file to start the installation. You need to enter information for the following fields:

● Set SQL server

Specify the SQL server name. If your SQL Server has an instance, specify the instance name.

NoteIf you installed the OSoftSSIS2008_Client, OSoftSSIS2012_Client, or OsoftSSIS2014_Client on the application server, the SQL server name is automatically disabled.

● Set server credential

This is the credential name of the COM+ package component. Enter the user ID and password that can access your SQL Server. This should be either the System Admin ID or Admin ID that was registered as a COM+ user when the Planning and Consolidation application server was installed.

48



Resources Folder

This folder contains the BPCServices.dll and BPCServiceUI.dll files, which contain resource text.

Only English resources are included for the SSIS custom tasks.

8.2 Before You Modify the SSIS Packages

Before you modify SSIS packages on the machine, complete the tasks outlined below. These steps are required if you remotely modify SSIS packages with Data Manager custom tasks.

1. Copy all Data Manager custom task components to the machine from which you wish to modify packages remotely. This is also true for the application server that has SSIS installed. The Planning and Consolidation Data Manager has the following custom tasks:

Table 12

Name Remark

BPCTaskAdmin.dll



Data Manager Admin custom task for SQL 2008, 2012, and 2014, respectively

BPCTaskAudit.dll



Data Manager Audit custom task for SQL 2008, 2012, and 2014, respectively

BPCTaskAvailable.dll



Data Manager System Available custom task for SQL 2008, 2012, and 2014, respectively

BPCTaskComment.dll



Data Manager Comment custom task for SQL 2008, 2012, and 2014, respectively

BPCTaskConvert.dll



Data Manager Convert custom task for SQL 2008, 2012, and 2014, respectively

BPCTaskDumpLoad.dll



Data Manager DumpLoad custom task for SQL 2008, 2012, and 2014, respectively

BPCTaskLogic.dll



Data Manager Logic custom task for SQL 2008, 2012, and 2014, respectively

BPCTaskMakeDim.dll



Data Manager Make Dimension custom task for SQL 2008, 2012, and 2014, respectively




Name Remark

BPCTaskOwnership.dll



Data Manager Ownership Calculation custom task for SQL 2008, 2012, and 2014, respectively

BPCTaskSendMail.dll



Data Manager Send Mail custom task for SQL 2008, 2012, and 2014, respectively

BPCTaskTrigger.dll



Data Manager Trigger custom task for SQL 2008, 2012, and 2014, respectively

You can find the Data Manager task files listed above in the following locations:

○ On a machine other than the Planning and Consolidation application server, based on version:

○ <…>\OSoftSSIS2008_Client\bin○ <…>\OSoftSSIS2012_Client\bin○ <…>\OSoftSSIS2014_Client\bin

○ On the Planning and Consolidation application server:

<drive>\Websrvr\bin2. Paste these files into the folder \100\DTS\Tasks for SQL Server 2008, into \110\DTS\Tasks for SQL

Server 2012, or into \120\DTS\Tasks for SQL Server 2014. For example, if you install your SQL 2008 server or R2 on C:\Program Files\Microsoft SQL Server, paste all files into the C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Tasks folder.

3. In Integration Services, set the property Run64BitRunTime to True.

8.3 Setup of a COM+ Application on the Application Server

To modify SSIS packages on a Planning and Consolidation application server, you must create a new COM+ application.

Procedure

To modify SSIS packages on a Planning and Consolidation application server, you must register a new COM+ application. To do so, install the OSoftSSIS2008_Client, OSoftSSIS2012_Client, or OSoftSSIS2014_Client on the application server.

50



Typographic Conventions

Table 13

Example Description

< > Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system, for example, Enter your <User Name>.

File Save Arrows separating the parts of a navigation path, for example, menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in the documentation

Example Textual cross-references to an internet address, for example, www.sap.com

/example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web

123456 Hyperlink to an SAP Note, for example, SAP Note 123456

Example ● Words or characters quoted from the screen. These include field labels, screen titles, pushbutton labels, menu names, and menu options.

● Cross-references to other documentation or published works

Example ● Output on the screen following a user action, for example, messages

● Source code or syntax quoted directly from a program

● File and directory names and their paths, names of variables and parameters, and names of installation, upgrade, and database tools

EXAMPLE Technical names of system objects. These include report names, program names, transaction codes, database table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE

EXAMPLE Keys on the keyboard

SAP BusinessObjects Planning and Consolidation 10.0Typographic Conventions



http://help.sap.com/disclaimer?site=Example

http://help.sap.com/disclaimer?site=http%3A%2F%2Fwww.sap.com



www.sap.com

Material Number: 725

*725*

http://www.sap.com