Top Banner
Installation Guide SAP BusinessObjects Planning and Consolidation 10.0 version for the Microsoft platform Target Audience Technical Consultants System Administrators CUSTOMER Document version: 1.37 – 2012-06-13
54

Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

Oct 28, 2014

Download

Documents

Damian Putero
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

Installation GuideSAP BusinessObjects Planning and Consolidation 100version for the Microsoft platform

Target Audience Technical Consultants System Administrators

CUSTOMERDocument version 137 ndash 2012-06-13

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2012 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

Microsoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries System i System i5 System p System p5 System x System z System z9 zOS AFP Intelligent Miner WebSphere Netfinity Tivoli Informix i5OS POWER POWER5 POWER5+ OpenPower and PowerPC are trademarks or registered trademarks of IBM CorporationAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom 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 varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressively prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguidesEPM-BPC

254 CUSTOMER 2012-06-13

Document History

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

Version Date Description

10 2012-01-31 Accompanies the General Availability release

11 2012-03-05 Revised chapters ldquoInstalling the Anti-Cross Site Scripting Libraryrdquo and ldquoInstalling on a Single ServerrdquoAdded chapter ldquoUsing Client Certificatesrdquo

115 2012-03-30 Added SAP Note 1665656 for SP6 to ldquoSAP Notes for the Installationrdquo

120 2012-04-03 In the topic ldquoInstalling the Server in a Multiserver Configurationrdquo added the recommendation to use a round robin approach to assign resources for load balancing

125 2012-04-30 In the topic ldquoInstalling the Prerequisites ‒ Basic Stepsrdquo 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

130 2012-06-07 Modified the document to incorporate SQL Server 2012 support within support package 7

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

136 2012-06-11 Updated the location of the machineconfig file in the topic ldquoConfiguring the Planning and Consolidation NET Application Serversrdquo

137 2012-06-13 Updated NET 20 to NET 40 in the topic ldquoConfiguring the Planning and Consolidation NET Application Serversrdquo

2012-06-13 CUSTOMER 354

Table of Contents

Chapter 1 Introduction 7

11 SAP Notes for the Installation 7

12 Naming Conventions 9

Chapter 2 Installing Planning and Consolidation Servers 11

21 Basic Steps 11

22 Prerequisites 11

23 Before Starting the Planning and Consolidation Server

Installation 13

24 Logging on to Servers 14

25 Service-level Accounts 15

26 Standard and Advanced Settings 16

27 Installing the Prerequisites 17

271 Installing the Prerequisites ‒ Basic Steps 17

272 Installing the Operating System 19

273 Installing the SQL Server 19

274 Installing Analysis Services 23

275 Installing the Anti-Cross Site Scripting Library 24

28 Installing on a Single Server 24

29 Installing the Server in a Multiserver Configuration 26

Chapter 3 After Installing Planning and Consolidation Servers 27

31 Post-Installation Steps 27

32 Connecting to Solution Manager Diagnostics 28

33 Configuring the Planning and Consolidation NET Application

Servers 29

34 Post-Installation Optional Configuration Steps 30

341 Enabling the Management Console 30

342 Setting Up ODBC Logging in IIS for the Default Web Site 31

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

2008 R2 32

454 CUSTOMER 2012-06-13

344 Removing Default Access to the Console 32

345 Management Console Access Control 33

346 Using Client Certificates 34

Chapter 4 Installing Planning and Consolidation Administration Client and the

SAP BusinessObjects EPM solutions Add-in for Microsoft

Office 37

41 Installing the Administration Client 37

42 Installing the EPM Add-in 38

43 Using the Client Auto Update Program 38

Chapter 5 Connection Issues 41

51 Checking for Open Ports 41

52 Proxy Server and Firewall Issues 41

Chapter 6 Installing Planning and Consolidation with Two Active Directory

Domains 43

Chapter 7 Installing Planning and Consolidation in a Terminal Services or Citrix

Server Deployment 45

71 Terminal Services Home Directories 45

72 System Requirements 45

73 Installing Planning and Consolidation 45

74 Creating a Shortcut to the Launch Page 46

Chapter 8 Installing SSIS Custom Tasks 47

81 Composition of SSIS Custom Task Installation 47

82 Before You Modify the SSIS Packages 50

83 Setup of a COM+ Application on the Application Server 51

2012-06-13 CUSTOMER 554

This page is left blank for documents that are printed on both sides

1 Introduction

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

Administrators who perform Planning and Consolidation server and Administration client

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

and the server and client software

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

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

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

servicesapcominstguidesEPM-BPC Planning and Consolidation 100 version for the Microsoft platform

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

BusinessObjects EPM solutions add-in for Microsoft Office help

New Installation Program Features in 100

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

11 SAP Notes for the Installation

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

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

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

Marketplace at the Internet address httpservicesapcomnotes

1 Introduction

11 SAP Notes for the Installation

2012-06-13 CUSTOMER 754

SAP Note Number Title Comments

1584890 Documentation Addendum Contains information that does not appear in the application help of Planning and Consolidation 100 version for the Micrososft platform

1733053 SAP Planning and Consolidation 100 SP08 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP08This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1689792 SAP Planning and Consolidation 100 SP07 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP07This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1665656 SAP Planning and Consolidation 100 SP06 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP06This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1643037 SAP Planning and Consolidation 100 SP05 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP05This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1620464 SAP Planning and Consolidation 100 SP04 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP04This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1601213 SAP Planning and Consolidation 100 SP03 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP03This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1591848 SAP Planning and Consolidation 100 SP02 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP02This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1 Introduction

11 SAP Notes for the Installation

854 CUSTOMER 2012-06-13

SAP Note Number Title Comments

1573539 SAP Planning and Consolidation 100 SP01 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP01This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

12 Naming Conventions

In this document the following naming conventions apply

Variable Description

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

ltdrivegt The drive where SAP Planning and Consolidation is installedThe default for this is CPC_MS

1 Introduction

12 Naming Conventions

2012-06-13 CUSTOMER 954

This page is left blank for documents that are printed on both sides

2 Installing Planning and Consolidation Servers

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

and what to do before during and after the server installation

21 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 at httpservicesapcominstguidesepm-bpc 100 version for the Microsoft platform

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

including installing all prerequisites

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

Consolidation on a Single Server [page 24]

NOTE

You must install both Planning and Consolidation 100 as well as the most recent Planning

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

httpservicesapcomswdc Software Downloads Support Packages and Patches A - Z Index

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

Versions SAP CPM BPC 100 M Windows Server on x64 64bit

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

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

22 Prerequisites

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

Consolidation server and the minimum versions required

NOTE

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

Availability Matrix on SAP Service Marketplace at httpservicesapcompam Search on

Planning and Consolidation

2 Installing Planning and Consolidation Servers

21 Basic Steps

2012-06-13 CUSTOMER 1154

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 or

Data Center with or without Hyper-V

NOTE

The operating system must be configured with NTFS

Relational Database Microsoft SQL Server 2008 Enterprise Edition Microsoft SQL Server 2008 R2 (Gemini) Enterprise Edition Microsoft SQL Server 2012 Enterprise Edition

OLAP Database Microsoft SQL Server 2008 Enterprise Edition ‒ Analysis Server Microsoft SQL Server 2008 R2 Enterprise Edition ‒ Analysis Server Microsoft SQL Server 2012 Enterprise Edition ‒ Analysis Server

Data Integration Microsoft SQL Server 2008 Enterprise Edition ‒ SQL Service Integration Services

Microsoft SQL Server 2008 R2 Enterprise Edition ‒ SQL Service Integration Services

Microsoft SQL Server 2012 Enterprise Edition ‒ SQL Service Integration Services

Other Requirements MSXML 40 SP2 or later ADOMDNET

ADOMDNET 100 when running SQL Server 2008 or 2008 R2 ADOMDNET 110 when running SQL Server 2012

SQL Server software components NET 40 IIS 75 or IIS 70

(Included in your Operating System IIS 75 is required for Windows 2008 R2 editions)

Anti-Cross Site Scripting Library 42This component must be downloaded before installing the server The server installation program asks for the path of each file and copies the files into the appropriate Planning and Consolidation path

Microsoft Visual C++ 2005 Runtime Libraries SP1 Microsoft Access Database Engine 2010 64bit VMWare ESX 3x or ESX 40

(Required only if a landscape deployment strategy using virtualization technologies is planned)

NOTE

MSXML 40 SP2 ADOMDNET 100 and Microsoft Visual C++ 2005 Runtime Libraries SP1 are included with the installation program but not installed automatically

RECOMMENDATION

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

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

2 Installing Planning and Consolidation Servers

22 Prerequisites

1254 CUSTOMER 2012-06-13

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

1429246 which also contains download information

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

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

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

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

23 Before Starting the Planning and Consolidation Server Installation

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

installation

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

information see Installing the Prerequisites [page 17]

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

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

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

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

Settings [page 16]

Make sure all required server ports are open and that there is communication between the physical

servers on which you are going to install the server types See Checking for Open Ports [page 41]

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

See Service-Level Accounts [page 15]

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

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

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

with the installation

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

reinstall them

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

turn off Script Blocking

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

install Planning and Consolidation 100 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 fsntfsV

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

2 Installing Planning and Consolidation Servers

23 Before Starting the Planning and Consolidation Server Installation

2012-06-13 CUSTOMER 1354

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

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

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

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

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

Consolidation We recommend that you use static IP addresses

IIS must be enabled

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

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

the following

1 Copy the EnvironmentShell database file ServerEnvironmentShelldb10 from the

Planning and Consolidation installation program to any folder on the SQL server (for example

cEnvironmentShelldb10)

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

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

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

24 Logging on to Servers

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

components

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

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

Administrator group on the local server

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

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

You can ignore these messages

NOTE

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

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

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

the SAP Planning and Consolidation Operations Guide in httpservicesapcominstguidesepm-bpc

100 for the Microsoft Platform SBOP Plan amp Consol 100 MS Administrators Guide

2 Installing Planning and Consolidation Servers

24 Logging on to Servers

1454 CUSTOMER 2012-06-13

25 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

PrerequisitesPlanning and Consolidation 100 has the following Windows services

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

and avoid deadlocks

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

and global caches

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

management system

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

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

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

with the error message

Could not start the BPC SendGovernor service

The reason for this is that the Admin account is not registered as a service

When installing a service to run under a domain user account the account must have the right to

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

and must be granted in the Local Security Policy

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

permission perform the following actions

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

2 Expand Local Policies and then click User Rights Assignment

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

4 Add the user to the policy and click OK

5 Close the Local Security Settings MMC snap-in

For more details see How to Troubleshoot Service Startup Permissions http

supportmicrosoftcomkb259733

FeaturesDuring the installation enter user IDs and passwords for the following user types

System Admin ID

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

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

2 Installing Planning and Consolidation Servers

25 Service-level Accounts

2012-06-13 CUSTOMER 1554

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

26 Standard and Advanced Settings

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

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

NOTE

When defining server names the name refers to the NetBIOS name IP address and fully qualified

domain names (FQDN)

Standard Settings

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

setting

Server Option Value Description

SQL Database server name The name of the SQL DB server

OLAP server name The name of the OLAP server

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

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

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

Server Option Value Description

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

2 Installing Planning and Consolidation Servers

26 Standard and Advanced Settings

1654 CUSTOMER 2012-06-13

Server Option Value Description

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

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

Provider The only available value is SQL

Local path for EnvironmentShell 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 CPC_MSData

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 changesSee the Kerberos authentication settings section in the SAP Library Server Manager Guide on httpservicesapcominstguidesEPM-BPC

100 for the Microsoft Platform

Scheduler Server Name The name of the server used for scheduling usually the application server for example GMPV50072862B If you have multiple application servers select the appropriate one

NOTE

If the primary server stops working you must manually configure your application server database to froward requests to another application server

27 Installing the Prerequisites

271 Installing the Prerequisites ndash Basic Steps

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

software the operating system IIS SQL server analysis services ADOMDNET and MSXML This

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

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 1754

Prerequisites [page 11] and the Product Availability Matrix on the SAP Service Marketplace at http

servicesapcompam Search on Planning and Consolidation

NOTE

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

procedure

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

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

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

Active Directory (AD)

We recommend not installing Microsoft Office on the application server

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

(UMCexe) on the Planning and Consolidation CD in a folder called UMC_100_INSTALLER When

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

1 Choose a language for the UMC install wizard to use

2 Check that the prerequisite check status is Succeeded and click Next

3 When you are ready to install the UMC click Next on the welcome screen

4 Click I accept the License Agreement and then Next

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

6 Select the languages that you wish to install

7 Select the features that you want to install (POAFHelper dotnet is mandatory for Planning

and Consolidation)

8 On Start Installation click Next to complete the installation

2 Install the required operating system on the single-server computer or on each physical server for

a multiserver configuration See Installing the Operating System [page 19]

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

wwwmicrosoftcom

4 From your operating systems media install IIS

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

Installing SQL Server [page 19]

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

packs and hot fixes See Installing Analysis Services [page 23]

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

1854 CUSTOMER 2012-06-13

7 On your application server install ADOMDNET The Planning and Consolidation zip file contains

the ADOMDNET installation package in the following locations

For SQL Server 2008 mdash BPC SetupServerSQLSERVER2008_ASADOMD10_x64msi

For SQL Server 2012 mdash BPC SetupServerSQLSERVER2012_ASADOMD11_x64msi

8 On your application server install MSXML 40 Service Pack 2 or later

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

the following location BPC SetupServermsxmlmsi

9 On your application server install Microsoft Visual C++ 2005 Runtime Libraries SP1

The Microsoft Visual C++ 2005 SP1 installation package is contained in the Planning and

Consolidation zip file at the following location BPC SetupServervcredist_x64exe

NOTE

The version of vcredist_x64exe in BPC SetupServer has been updated to 8061000 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 httpwwwmicrosoftcomdownloadsen

detailsaspxFamilyID=C06B8369-60DD-4B64-A44B-84B371EDE16Dampltdisplaylanggt=en

272 Installing the Operating System

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

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

Marketplace at httpservicesapcompam Search on Planning and Consolidation

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

NOTE

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

languages such as Hebrew

ProcedureIf you are installing IIS 70 or 75 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

273 Installing the SQL Server

PrerequisitesDuring the installation procedure you have the opportunity to specify the location of the

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

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 1954

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 CEnvironmentShelldb10) 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 a 2008 2008 R2 and 2012 SQL Server

SQL Server Considerations

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

System (Windows Server) then enable IIS and ASPNET and install any Windows Server service

packs

IIS and NET Framework 40 are required on your application server

NOTE

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

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

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

nondefault instance of SQL Server

General Installation Steps

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

terms

2 Choose Install to install the SQL support files

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

Options section below then choose Next

4 Review disc space requirements then choose Next

5 In Server Configuration Perform the following actions

1 In the Service Accounts tab enter a Planning and Consolidation sysadmin account for the SQL

Server Database Engine and the SQL Server Analysis services This is required so that the Planning

and Consolidation sysadmin can create and process the Planning and Consolidation database

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

account This account is also required during Backup Environment and Restore Environment in the

Server Manager

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

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

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

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

application server

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2054 CUSTOMER 2012-06-13

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

Consolidation sysadmin for this service account

2 In the Collation tab set the collation settings to SQL_Latin1_General_CP1_CI_AS

Choose Next

6 Set Database Engine Configuration options then choose Next

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

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

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

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

you can install the SQL Server in Windows-only mode

7 Accept the Analysis Services Configuration default options and the remaining default options of the

installation program

8 Choose Install to begin the installation with the options you have set

SQL Server Component 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

Server Component What to Install

SQL Server Database Engine Services

SSAS Server Analysis Services

Application Server The following Shared Features Client Tools Connectivity Integration Services Client Tools SDK

Custom Settings for the SQL Server

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

SQL Server 2008 R2 and SQL Server 2012

Process Dimension

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

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

dimensions and cubes in parallel

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 2154

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

NOTE

Setting 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 tblFactWBltappgt table

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 Microsoftreg SQL Servertrade

20052008 which you can download from wwwmicrosoftcom (search on ldquoTable Partitioningrdquo to find

all relevant articles)

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

From SQL Server Configuration Manager confirm that the SQL Server Browser service is

running The browser service is required for Planning and Consolidation

From SQL Server Configuration Manager do the following

1 Select Protocols for ltInstanceNamegt then double-click TCPIP from the right side of the window

2 When prompted for the TCPIP Properties select IP Addresses You see two IPs that indicate the

localhost and external network interface machine

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2254 CUSTOMER 2012-06-13

3 If you want to use IP1 which indicates Server IP set Enabled to Yes and specify the TCP Port as

desired

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

RECOMMENDATION

We do not recommend using dynamic ports

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

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

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

recommendation prevents any conflict problems

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

server

1 Select Client Protocols from the SQL Native Client Configuration folder

2 From the right side of the window double-click TCPIP The TCPIP 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

NOTE

We 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

274 Installing Analysis Services

ProcedureAfter you install SQL Server and its required service packs and hotfixes you must install SQL Server

Analysis Services and its required service packs and hotfixes

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 2354

NOTE

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

that contains the repository before installing this release

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

and guidelines in httptechnetmicrosoftcomen-uslibraryms143219aspx

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 httpwwwmicrosoftcomdownloads

detailsaspxFamilyID=3be0488d-e7aa-4078-a050- ae39912d2e43ampdisplaylang=en

275 Installing the Anti-Cross Site Scripting Library

Procedure

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

Library (version 42 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 AntiXSSLibraryDLL from the Microsoft Web

site at httpwwwmicrosoftcomdownloadendetailsaspxid=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 AntiXssLibrarydll

28 Installing on a Single Server

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

consider the following issues

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

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

times the uncompressed size of the environment files

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

components

SQL Server

SQL Server Analysis Services (SSAS)

Application Server

FileShare server

Procedure

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

1 Exit all Windows programs

2 Installing Planning and Consolidation Servers

28 Installing on a Single Server

2454 CUSTOMER 2012-06-13

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

on to servers [page 14]

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

the Prerequisites [page 17]

4 Obtain SAP Planning and Consolidation from the Downloads SAP Installations amp Upgrades area of

SAP Service Marketplace then extract the files and run StartUpexe

5 From the Server Install screen select Install the Planning and Consolidation server

6 From the Welcome screen choose Next

7 From the License Agreement page choose I accept the terms of the license agreement then choose Next

8 From the Installation Method page accept the default Single machine enter a system ID for the system

landscape directory (SLD) and choose Next

NOTE

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

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

9 From the Authentication Method page choose the desired authentication method and choose Next

10 If you have chosen SAP BusinessObjects User Management System in the previous screen on the CMS

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

The following information is required

Field Description

System name CMS system name (server nameport number) for example CMSServer6400

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

11 After entering the CMS administrator authentication details choose Next

12 From the Service type accounts page enter service-level account user IDs and passwords See Service-

Level Accounts [page 15]

13 After defining the IDs and passwords choose Next

14 From the Server Information page (see Standard and Advanced Settings [page 16]) do one of the following

Review the standard settings and choose Next

To set advanced settings choose the Advanced Settings button Enter the desired information

and choose Next

2 Installing Planning and Consolidation Servers

28 Installing on a Single Server

2012-06-13 CUSTOMER 2554

15 Specify the location and name of AntiXssLibrarydll See Installing the Anti-Cross Site Scripting Library [page

24]

Choose Next

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

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

recommendation reduces the hard disk IO time and helps to speed up SQL commands

Accept the defaults or make your selections then choose Next

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

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

and Consolidation Server Manager

18 The installation process takes a few moments When it is complete choose Exit

19 A prompt is displayed to restart your computer Select OK to restart

20 Perform the steps in After Installing Planning and Consolidation Servers [page 27]

29 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 24]) with the following

exceptions

On the Installation Method page do not accept the default instead choose Network Load Balancing

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

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

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

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

In the Virtual Name field enter the virtual IP address virtual name in the default properties

2 Installing Planning and Consolidation Servers

29 Installing the Server in a Multiserver Configuration

2654 CUSTOMER 2012-06-13

3 After Installing Planning and Consolidation Servers

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

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

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

Consolidation NET Application Server [page 29]

3 Optional configuration steps [page 30]

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

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

30]

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

custom logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web

Site [page 31]

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

Data Source [page 32]

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

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

on the server For information about removing default access and creating a group that can

access the console see Removing Default Access to the Console [page 32]

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

recommend that you only grant Management Console access to system administrators

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

Management Console Access Control [page 33]

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

34]

4 Take the following steps to set up security

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

3 After Installing Planning and Consolidation Servers

31 Post-Installation Steps

2012-06-13 CUSTOMER 2754

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

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

Administrator

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

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

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

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

Administration client See Installing the Administration Client [page 37]

6 Start Planning and Consolidation Administration from the launch page

7 Select Connection Wizard and log on to EnvironmentShell

8 Create a new environment using EnvironmentShell as the source

9 Log on to the newly created environment and set up users teams and task profiles (You must

set up task profiles since there is no access to Planning and Consolidation tasks)

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

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

NOTE

To allow users to request and query large amounts of data you can edit the metabasexml file located

at CWindowssystem32inetsrv Set the following parameters to the stated values

ASPBUFFERINGLIMIT = 10485760

MAXREQUESTENTITYALLOWED = 10485760

32 Connecting to Solution Manager Diagnostics

NOTE

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

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

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

Solution Manager Diagnostics

Procedure

1 Install the Diagnostics Agent according to SAP Note 1234387 on all servers where application servers

are installed

NOTE

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

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

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

for managed systems DIAGNOSTICS AGENT 711

3 After Installing Planning and Consolidation Servers

32 Connecting to Solution Manager Diagnostics

2854 CUSTOMER 2012-06-13

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

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

Servers where Microsoft SQL Server is installed Do the following

1 Start Computer Management then select Action New User

2 Create a new user

3 Right-click on the user then choose Properties On the Member Of tab select Add

4 Add the group SQLServerltReleasegtSQLAgentUser$ltDomain or hostnamegt$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 httpsservicesapcom~sapidb011000358700000074392009E and follow

the chapters that apply to Planning and Consolidation

33 Configuring the Planning and Consolidation NET Application Servers

Procedure

Modifying machineconfig Files

To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock

occurrences that would cause the application server to ldquosleeprdquo and not process anymore you can

modify the machineconfig file which resides in the WINDOWSMicrosoftNETFramework64

v4030319Config directory

1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to

specify whether to automatically configure settings to achieve optimal performance based on the

machine configuration You can set this attribute to True or False

For more information see httpmsdnmicrosoftcomen-uslibrary7w2sway1aspx

2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the

Planning and Consolidation application) or Machineconfig (for all applications including

Planning and Consolidation) to ensure the validationKey and decryptionKey keys have the same

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

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

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

msdnmicrosoftcomen-uslibraryms998288aspx

3 After Installing Planning and Consolidation Servers

33 Configuring the Planning and Consolidation NET Application Servers

2012-06-13 CUSTOMER 2954

paght000007_webfarmdeploymentconsiderations and httpmsdnmicrosoftcomen-us

libraryms998310aspx

34 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 30]

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

logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page

31]

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

Source [page 32]

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

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

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

see Removing Default Access to the Console [page 32]

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

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

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

Access Control [page 33]

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

341 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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3054 CUSTOMER 2012-06-13

NOTE

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

User Activity and Service Status) does not work as expected

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

Active Log Format field in IIS to W3C Extended Log File Format

342 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 ApplicationHostconfig set the property customLogPluginClsid to the value FF16065B-

DE82-11CF-BC0A-00AA006111E0 Set the logFormat to Custom You can find this in the ltlogFilegt

node in ApplicationHostconfig as shown here

ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0

logFormat=Custom gt

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

appcmd site set sitenameDefault Web Site

logFilecustomLogPluginClsidFF16065B-DE82-11CF-BC0A-00AA006111E0

appcmd site set sitenameDefault Web Site logFilelogFormatCustom

Configuring ODBC Logging Parameters in ApplicationHostconfig

Configure ApplicationHostconfig to contain the database table information as set up in the Microsoft

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

node under ltsystemwebServergt

EXAMPLE

ltlocation path=Default Web Sitegt

ltsystemwebServergt

ltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog

userName=Username password=mypassword gt

ltsystemwebServergt

ltlocationgt

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3154

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

appcmd set config Default Web Site sectionodbcLogging

dataSourceBPC_ManagementDSN commitappHost

appcmd set config Default Web Site sectionodbcLogging tableNameBPCLog

commitappHost

appcmd set config Default Web Site sectionodbcLogging userNameUsername

commitappHost

appcmd set config Default Web Site sectionodbcLogging passwordmypassword

commitappHost

NOTE

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

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

931202 The requirements for using the ODBC logging feature in IIS

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

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

Server 2008 or Windows Server 2008 R2

Proceed as follows

1 Open ODBC Connection Manager

2 On the System DSN tab page add a new DSN

Choose Add

Choose SQL Server as the driver

Choose Finish

3 In the Name and Description fields enter BPC_ManagementDSN

4 In the Server field enter the name of your SQL Server Choose Next

5 Leave the default settings and choose Next

6 Choose the Change the default database to field and enter AppServer Choose Next

7 Leave default settings and choose Next

8 Choose OK

344 Removing Default Access to the Console

NOTE

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

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

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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3254 CUSTOMER 2012-06-13

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

console use the procedure described below

NOTE

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

Management Console or in the Active Directory

1 In the context menu of the servers My Computer icon choose Manage

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

NOTE

Alternatively you can perform analogous steps in Active Directory

3 In the 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

NOTE

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

10 In the Security dialog box click Copy to ensure that the System group retains its privileges

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

12 Choose Authentication in the center pane then disable Windows authentication

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

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

would otherwise have to Planning and Consolidation

345 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 32] Their rights in

Active Directory determine what they can access in the Console

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

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

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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3354

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

privileges For more information see the SAP Library Planning and Consolidation Administrators Guide in

httpservicesapcominstguidesepm-bpc 100 version for the Microsoft platform

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

levels of Console users (read-only users for example) in your environment

To grant or limit access to users or groups you can add or remove the following privileges from the

areas described in this table

Privilege Rights Management Area

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

Performance Monitor Counters Administrators group on application server or domain Power Users group on application server or domain Performance Monitor Users group on application server

Microsoft Analysis Services performance monitoring

Administrators group on application server or domain

Microsoft SQL Server Monitoring (performance counters and statistics)

Administrators group on application server or domain

346 Using Client Certificates

To enable the use of client certificates in Planning and Consolidation you must follow several manual

steps

NOTE

Planning 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 httptechnetmicrosoftcomen-us

librarycc753810aspx

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

technetmicrosoftcomen-uslibrarycc732996(WS10)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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3454 CUSTOMER 2012-06-13

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

authentication) to connect to Planning and Consolidation

2 Enable anonymous authentication

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

2 Select the ManagementConsole directory (ltWebsitegtManagementConsole) to open the

ManagementConsole home page

3 Double-click Authentication and enable Anonymous Authentication

4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way

as in step 3

5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the same

way as in step 3

3 Change the web configuration settings

1 Open the ltPC_MSgtWebsrvrWebBPCwebconfig file

2 Find the text clientCredentialType=Windows

3 Change value of clientCredentialType to None (clientCredentialType=None)

4 Open the PC_MSWebsrvrWebPOASBCwebconfig file Repeat steps 2 and 3

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3554

This page is left blank for documents that are printed on both sides

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

The installation of the Planning and Consolidation Administration Client allows administrators to

build and maintain Planning and Consolidation environments and models and administer security

All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions

add-in for Microsoft Office for more information see the SAP BusinessObjects EPM solutions add-in for

Microsoft Office help

NOTE

You must update the Administration Client to the same version as the server

If your PC is on a different domain than your server you must set the Internet Explorer

Security Zone value of the Planning and Consolidation client to prompt for user name and

password Otherwise the Planning and Consolidation Start Page does not display

41 Installing the Administration Client

Prerequisites

NOTE

For a definitive list of system requirements see the Product Availability Matrix on SAP Service

Marketplace at httpservicesapcompam Search on Planning and Consolidation

The following list describes the minimum software requirements

Microsoft Internet Explorer 70 or 80

Microsoft Office 2007 or 2010

NET Framework 20 or higher (install any required NET Framework Hotfixes by referring to

httpsupportmicrosoftcomkb)

Pentium IV (1 GHz CPU)

512 MB RAM

100 MB of free hard disk space in the My Documents folder

20 MB of free hard disk space for the installed Administration files

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

41 Installing the Administration Client

2012-06-13 CUSTOMER 3754

NOTE

We recommend that you install all of the latest Microsoft Windows hotfixes prior to installing

the Administration client For information about which hotfixes to install see http

updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us

ProcedureThe following procedure describes how to install the Administration Client on to an administratorrsquos

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 AddRemove Programs in the Windows Control Panel

3 Point your browser to the Planning and Consolidation Web at httpltPC_serverportgtsap

bpcweb

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

42 Installing the EPM Add-in

The Planning and Consolidation installation media does not contain the EPM addin setup program

You must download the most recent version of the full setup (EPM Add-inexe) from the Service

Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPC

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

43 Using the Client Auto Update Program

If Planning and Consolidation version 100 or later is installed you can use the Client Auto Update

program to set up the server so that it determines if an upgrade for a connecting Administration client

is necessary

The following describes the use of the auto update program for the Administration Client and the EPM

add-in

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

42 Installing the EPM Add-in

3854 CUSTOMER 2012-06-13

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

To use the Client Auto Update program for the Administration Client proceed as follows

1 From the Server Manager select Options Client Options

2 Select Admin Update

3 If users without administrator rights on their machines use the auto update enter an administrator

ID and password in the Admin ID and Admin password fields respectively The Admin ID should be a

member of the local administrators group on all the computers running the auto update This

setting is not needed if all users have administrator rights on their machines

4 Select Update

For the EPM Add-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 Optionshellip 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 Market Place (SMP) at httpservicesapcom

All support packages and patches are available from the SMP as a zip file

EPMEXCLCLNTltSPLgtzip is for a support package

EPMEXCLCLNTltSPLgtPltPLgtzip 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 ltSP versiongtmsp

EPM Addin Support Package ltSP versiongtxml

For a patch these files are

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

43 Using the Client Auto Update Program

2012-06-13 CUSTOMER 3954

EPM Addin Patch ltpatch numbergtmsp

EPM Addin Patch ltpatch numbergtxml

2 Unzip the zip file and extract the two files to the application server folder (WebsrvrWebBPC

Installation)

3 From the Server Manager select Options Client Options

The system lists the available packages Select the package that you want to use for the autoupdate

You can set a different update policy for each package listed

EXAMPLE

The following table illustrates some possible situations assuming that you have installed the

first full version (V1)

Available maintenance packages

V2-user updateV3-force updateV4-force updateV5-user update

V5-user update V5-user updateV6-auto updateV7-force update

Minimum Required Version

V4 V4 V7

Notification A prompt tells the user to install maintenance package V4 using the Forced Update behavior

If User Update is enabled the prompt informs the user that maintenance package V5 is available

A prompt tells the user to install maintenance package V7 using the Forced Update behavior

New Version V4 V4 or V5 V7

If you change the update policy for any package click Update to complete the change

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

43 Using the Client Auto Update Program

4054 CUSTOMER 2012-06-13

5 Connection Issues

You may experience connection problems with ports the proxy server or programs and settings that

interact with these components If you have any issues related to connection review the following

recommendations and troubleshooting tips

51 Checking for Open Ports

You must ensure that all required ports are open for inboundoutbound 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 431181836 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

NOTE

You can use the following site to scan for the normal ports It allows you to manually enter a port

number to test

httpwwwmyserverorgportsniffasp

You can change the name of a port

52 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 Explorer Tools Internet Options Connections LAN Settings ) or at the server level

Enabling content filtering on the proxy server or firewall may cause connection problems

If external users are having trouble connecting to the server make sure the proxy server connects

using a fully qualified domain name Fully qualified domain names typically resolve both internal

and external IP addresses

Each secure Planning and Consolidation server name must be identified on the proxy server

Proxy servers may or may not require authentication which could conflict with Planning and

Consolidation authentication Do not use authentication on the proxy server The system

5 Connection Issues

51 Checking for Open Ports

2012-06-13 CUSTOMER 4154

synchronizes the user name and password on the remote server with the local user name and

password

NOTE

For more information about setting up an ISA proxy server contact SAP Support to request a

copy of Setting up ISA Proxy Server White Paper

Internet Explorer Settings 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

5 Connection Issues

52 Proxy Server and Firewall Issues

4254 CUSTOMER 2012-06-13

6 Installing Planning and Consolidation with Two Active Directory Domains

To set up a Planning and Consolidation 10 application server in a hosted environment and use your

own domain users follow this procedure In general you install Planning and Consolidation on the

host domain use the host domain account and assign it to the Planning and Consolidation users

SysAdmin Admin and Users Then you accept one way trust (the host domain trusts your domain)

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

6 Installing Planning and Consolidation with Two Active Directory Domains

2012-06-13 CUSTOMER 4354

This page is left blank for documents that are printed on both sides

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

This section describes best practices and instructions for installing Planning and Consolidation in a

Terminal Services or Citrix Server deployment

71 Terminal Services Home Directories

We recommend using Terminal Server home directories rather than using the userrsquos 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

72 System Requirements

The Citrix server should be one of the following systems

XenApp 5 Enterprise

XenApp 5 Platinum

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

73 Installing Planning and Consolidation

Prerequisites

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

Procedure

The following steps outline how to install the Planning and Consolidation clients in a Terminal Services

(TS) or Citrix Server deployment

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

71 Terminal Services Home Directories

2012-06-13 CUSTOMER 4554

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 userinstall

4 Open a browser and connect to the URL httpltPC_serverportgtsapbpcweb

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 userexecute 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 Iexploreexe http(s)

ltServerNamegt-NetBIOS or FQDNsapbpcweb

To publish Planning and Consolidation Administration CProgram FilesPC_MS

BPCAdminMainexe

74 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 userrsquos desktop) must be moved to the All UsersDesktop folder

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

74 Creating a Shortcut to the Launch Page

4654 CUSTOMER 2012-06-13

8 Installing SSIS Custom Tasks

This section provides background information and instructions for installing SQL Server Integration

Services (SSIS) for SQL Server 2008 and SQL Server 2012

The Planning and Consolidation Data Manager component supports and uses SSIS Since SQL Server

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

81 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 Filelistxml 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

OSoftSetupexe ‒ 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 or OSoftSSIS2012_Client on the client machine followed by the SQL Server

version If you want to use SQL 2008 Tasks under the SQL 2012 environment you must install

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

You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package by extracting

OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPC

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 or

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4754

OSoftSSIS2012_Client for creating a COM+ application For more information see Before You Modify

the SSIS Packages [page 50] and Setup of a COM+ Application on the Application Server [page 51]

Bin folder

This folder contains the following components

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCCachedll Planning and Consolidation Cache file

BPCDataFlowPackagedll or BPCDataFlowPackage2012dll

BPCDMdll

BPCDMTaskMaindll COM+ component

BPCFilePreviewdll

BPCGacUtil_20exe System File

BPCGacUtil_40exe System File

BPCImpersonatordll Planning and Consolidation Impersonator

BPCLogicdll

BPCScriptdll

BPCServerZipdll

BPCServiceResdll

BPCTransferMembersdll

BPCWriteBackdll

InteropDTSdll

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

4854 CUSTOMER 2012-06-13

Name Remark

OSoftAdminServerdll

OSoftAuditdll

OSoftComLibServerdll

OSoftCommonResQrydll

OSoftConfigurationdll

OSoftCustomXMLSvrdll

OSoftDatabaseADMINdll

OSoftDatabaseSYSADMINdll

OSoftDatabaseSYSADMINDMdll

OSoftDatabaseUSERdll

OSoftDMDTSXExecutedll or OSoftDMDTSXExecute2012dll

OSoftDMTaskFormdll

OSoftDMTaskMaindll

OSoftDMToolsdll

OSoftFileManagedll

OSoftLoggingdll

OSoftLogWriterdll

OSoftMetaDatadll

OSoftSQEdll

OSoftSystemConfigdll

OutlookSoftconfig Configuration file to connect DB server

XceedCompressiondll XceedZip file

XceedCompressionFormatsdll XceedZip file

XceedFileSystemdll XceedZip file

XceedZipdll XceedZip file

Config folder

This folder has FileListxml 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 FileListxml 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

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4954

OSoftSetupexe

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

NOTE

If you installed the OSoftSSIS2008_Client or OSoftSSIS2012_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

Resources Folder

This folder contains the BPCServicesdll and BPCServiceUIdll files which contain resource text

Only English resources are included for the SSIS custom tasks

82 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

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008 and 2012 respectively

8 Installing SSIS Custom Tasks

82 Before You Modify the SSIS Packages

5054 CUSTOMER 2012-06-13

Name Remark

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012 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

lthellipgtOSoftSSIS2008_Clientbin or lthellipgtOSoftSSIS2012_Clientbin

On the Planning and Consolidation application server

ltdrivegtWebsrvrbin

2 Paste these files into the folder 100DTSTasks for SQL Server 2008 or into 110DTSTasks for

SQL Server 2012 For example if you install your SQL 2008 server or R2 on CProgram Files

Microsoft SQL Server paste all files into the CProgram Files (x86)Microsoft SQL Server

100DTSTasks folder

In Integration Services set the property Run64BitRunTime to True

83 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 or OSoftSSIS2012_Client on the

application server

8 Installing SSIS Custom Tasks

83 Setup of a COM+ Application on the Application Server

2012-06-13 CUSTOMER 5154

Typographic Conventions

Example Description

ltgt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example Enter your ltUser Namegt

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 httpwwwsapcom

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

5254 CUSTOMER 2012-06-13

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

  • SAP BusinessObjects Planning and Consolidation 100
    • Table of Contents
    • 1 Introduction
      • 11 SAP Notes for the Installation
      • 12 Naming Conventions
        • 2 Installing Planning and Consolidation Servers
          • 21 Basic Steps
          • 22 Prerequisites
          • 23 Before Starting the Planning and Consolidation Server Installation
          • 24 Logging on to Servers
          • 25 Service-level Accounts
          • 26 Standard and Advanced Settings
          • 27 Installing the Prerequisites
            • 271 Installing the Prerequisites ndash Basic Steps
            • 272 Installing the Operating System
            • 273 Installing the SQL Server
            • 274 Installing Analysis Services
            • 275 Installing the Anti-Cross Site Scripting Library
              • 28 Installing on a Single Server
              • 29 Installing the Server in a Multiserver Configuration
                • 3 After Installing Planning and Consolidation Servers
                  • 31 Post-Installation Steps
                  • 32 Connecting to Solution Manager Diagnostics
                  • 33 Configuring the Planning and Consolidation NET Application Servers
                  • 34 Post-Installation Optional Configuration Steps
                    • 341 Enabling the Management Console
                    • 342 Setting Up ODBC Logging in IIS for the Default Web Site
                    • 343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2
                    • 344 Removing Default Access to the Console
                    • 345 Management Console Access Control
                    • 346 Using Client Certificates
                        • 4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office
                          • 41 Installing the Administration Client
                          • 42 Installing the EPM Add-in
                          • 43 Using the Client Auto Update Program
                            • 5 Connection Issues
                              • 51 Checking for Open Ports
                              • 52 Proxy Server and Firewall Issues
                                • 6 Installing Planning and Consolidation with Two Active Directory Domains
                                • 7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
                                  • 71 Terminal Services Home Directories
                                  • 72 System Requirements
                                  • 73 Installing Planning and Consolidation
                                  • 74 Creating a Shortcut to the Launch Page
                                    • 8 Installing SSIS Custom Tasks
                                      • 81 Composition of SSIS Custom Task Installation
                                      • 82 Before You Modify the SSIS Packages
                                      • 83 Setup of a COM+ Application on the Application Server
                                          • Copyright and trademarks
Page 2: Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2012 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

Microsoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries System i System i5 System p System p5 System x System z System z9 zOS AFP Intelligent Miner WebSphere Netfinity Tivoli Informix i5OS POWER POWER5 POWER5+ OpenPower and PowerPC are trademarks or registered trademarks of IBM CorporationAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom 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 varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressively prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguidesEPM-BPC

254 CUSTOMER 2012-06-13

Document History

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

Version Date Description

10 2012-01-31 Accompanies the General Availability release

11 2012-03-05 Revised chapters ldquoInstalling the Anti-Cross Site Scripting Libraryrdquo and ldquoInstalling on a Single ServerrdquoAdded chapter ldquoUsing Client Certificatesrdquo

115 2012-03-30 Added SAP Note 1665656 for SP6 to ldquoSAP Notes for the Installationrdquo

120 2012-04-03 In the topic ldquoInstalling the Server in a Multiserver Configurationrdquo added the recommendation to use a round robin approach to assign resources for load balancing

125 2012-04-30 In the topic ldquoInstalling the Prerequisites ‒ Basic Stepsrdquo 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

130 2012-06-07 Modified the document to incorporate SQL Server 2012 support within support package 7

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

136 2012-06-11 Updated the location of the machineconfig file in the topic ldquoConfiguring the Planning and Consolidation NET Application Serversrdquo

137 2012-06-13 Updated NET 20 to NET 40 in the topic ldquoConfiguring the Planning and Consolidation NET Application Serversrdquo

2012-06-13 CUSTOMER 354

Table of Contents

Chapter 1 Introduction 7

11 SAP Notes for the Installation 7

12 Naming Conventions 9

Chapter 2 Installing Planning and Consolidation Servers 11

21 Basic Steps 11

22 Prerequisites 11

23 Before Starting the Planning and Consolidation Server

Installation 13

24 Logging on to Servers 14

25 Service-level Accounts 15

26 Standard and Advanced Settings 16

27 Installing the Prerequisites 17

271 Installing the Prerequisites ‒ Basic Steps 17

272 Installing the Operating System 19

273 Installing the SQL Server 19

274 Installing Analysis Services 23

275 Installing the Anti-Cross Site Scripting Library 24

28 Installing on a Single Server 24

29 Installing the Server in a Multiserver Configuration 26

Chapter 3 After Installing Planning and Consolidation Servers 27

31 Post-Installation Steps 27

32 Connecting to Solution Manager Diagnostics 28

33 Configuring the Planning and Consolidation NET Application

Servers 29

34 Post-Installation Optional Configuration Steps 30

341 Enabling the Management Console 30

342 Setting Up ODBC Logging in IIS for the Default Web Site 31

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

2008 R2 32

454 CUSTOMER 2012-06-13

344 Removing Default Access to the Console 32

345 Management Console Access Control 33

346 Using Client Certificates 34

Chapter 4 Installing Planning and Consolidation Administration Client and the

SAP BusinessObjects EPM solutions Add-in for Microsoft

Office 37

41 Installing the Administration Client 37

42 Installing the EPM Add-in 38

43 Using the Client Auto Update Program 38

Chapter 5 Connection Issues 41

51 Checking for Open Ports 41

52 Proxy Server and Firewall Issues 41

Chapter 6 Installing Planning and Consolidation with Two Active Directory

Domains 43

Chapter 7 Installing Planning and Consolidation in a Terminal Services or Citrix

Server Deployment 45

71 Terminal Services Home Directories 45

72 System Requirements 45

73 Installing Planning and Consolidation 45

74 Creating a Shortcut to the Launch Page 46

Chapter 8 Installing SSIS Custom Tasks 47

81 Composition of SSIS Custom Task Installation 47

82 Before You Modify the SSIS Packages 50

83 Setup of a COM+ Application on the Application Server 51

2012-06-13 CUSTOMER 554

This page is left blank for documents that are printed on both sides

1 Introduction

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

Administrators who perform Planning and Consolidation server and Administration client

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

and the server and client software

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

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

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

servicesapcominstguidesEPM-BPC Planning and Consolidation 100 version for the Microsoft platform

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

BusinessObjects EPM solutions add-in for Microsoft Office help

New Installation Program Features in 100

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

11 SAP Notes for the Installation

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

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

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

Marketplace at the Internet address httpservicesapcomnotes

1 Introduction

11 SAP Notes for the Installation

2012-06-13 CUSTOMER 754

SAP Note Number Title Comments

1584890 Documentation Addendum Contains information that does not appear in the application help of Planning and Consolidation 100 version for the Micrososft platform

1733053 SAP Planning and Consolidation 100 SP08 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP08This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1689792 SAP Planning and Consolidation 100 SP07 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP07This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1665656 SAP Planning and Consolidation 100 SP06 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP06This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1643037 SAP Planning and Consolidation 100 SP05 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP05This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1620464 SAP Planning and Consolidation 100 SP04 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP04This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1601213 SAP Planning and Consolidation 100 SP03 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP03This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1591848 SAP Planning and Consolidation 100 SP02 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP02This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1 Introduction

11 SAP Notes for the Installation

854 CUSTOMER 2012-06-13

SAP Note Number Title Comments

1573539 SAP Planning and Consolidation 100 SP01 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP01This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

12 Naming Conventions

In this document the following naming conventions apply

Variable Description

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

ltdrivegt The drive where SAP Planning and Consolidation is installedThe default for this is CPC_MS

1 Introduction

12 Naming Conventions

2012-06-13 CUSTOMER 954

This page is left blank for documents that are printed on both sides

2 Installing Planning and Consolidation Servers

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

and what to do before during and after the server installation

21 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 at httpservicesapcominstguidesepm-bpc 100 version for the Microsoft platform

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

including installing all prerequisites

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

Consolidation on a Single Server [page 24]

NOTE

You must install both Planning and Consolidation 100 as well as the most recent Planning

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

httpservicesapcomswdc Software Downloads Support Packages and Patches A - Z Index

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

Versions SAP CPM BPC 100 M Windows Server on x64 64bit

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

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

22 Prerequisites

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

Consolidation server and the minimum versions required

NOTE

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

Availability Matrix on SAP Service Marketplace at httpservicesapcompam Search on

Planning and Consolidation

2 Installing Planning and Consolidation Servers

21 Basic Steps

2012-06-13 CUSTOMER 1154

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 or

Data Center with or without Hyper-V

NOTE

The operating system must be configured with NTFS

Relational Database Microsoft SQL Server 2008 Enterprise Edition Microsoft SQL Server 2008 R2 (Gemini) Enterprise Edition Microsoft SQL Server 2012 Enterprise Edition

OLAP Database Microsoft SQL Server 2008 Enterprise Edition ‒ Analysis Server Microsoft SQL Server 2008 R2 Enterprise Edition ‒ Analysis Server Microsoft SQL Server 2012 Enterprise Edition ‒ Analysis Server

Data Integration Microsoft SQL Server 2008 Enterprise Edition ‒ SQL Service Integration Services

Microsoft SQL Server 2008 R2 Enterprise Edition ‒ SQL Service Integration Services

Microsoft SQL Server 2012 Enterprise Edition ‒ SQL Service Integration Services

Other Requirements MSXML 40 SP2 or later ADOMDNET

ADOMDNET 100 when running SQL Server 2008 or 2008 R2 ADOMDNET 110 when running SQL Server 2012

SQL Server software components NET 40 IIS 75 or IIS 70

(Included in your Operating System IIS 75 is required for Windows 2008 R2 editions)

Anti-Cross Site Scripting Library 42This component must be downloaded before installing the server The server installation program asks for the path of each file and copies the files into the appropriate Planning and Consolidation path

Microsoft Visual C++ 2005 Runtime Libraries SP1 Microsoft Access Database Engine 2010 64bit VMWare ESX 3x or ESX 40

(Required only if a landscape deployment strategy using virtualization technologies is planned)

NOTE

MSXML 40 SP2 ADOMDNET 100 and Microsoft Visual C++ 2005 Runtime Libraries SP1 are included with the installation program but not installed automatically

RECOMMENDATION

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

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

2 Installing Planning and Consolidation Servers

22 Prerequisites

1254 CUSTOMER 2012-06-13

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

1429246 which also contains download information

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

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

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

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

23 Before Starting the Planning and Consolidation Server Installation

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

installation

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

information see Installing the Prerequisites [page 17]

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

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

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

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

Settings [page 16]

Make sure all required server ports are open and that there is communication between the physical

servers on which you are going to install the server types See Checking for Open Ports [page 41]

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

See Service-Level Accounts [page 15]

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

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

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

with the installation

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

reinstall them

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

turn off Script Blocking

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

install Planning and Consolidation 100 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 fsntfsV

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

2 Installing Planning and Consolidation Servers

23 Before Starting the Planning and Consolidation Server Installation

2012-06-13 CUSTOMER 1354

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

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

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

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

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

Consolidation We recommend that you use static IP addresses

IIS must be enabled

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

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

the following

1 Copy the EnvironmentShell database file ServerEnvironmentShelldb10 from the

Planning and Consolidation installation program to any folder on the SQL server (for example

cEnvironmentShelldb10)

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

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

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

24 Logging on to Servers

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

components

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

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

Administrator group on the local server

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

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

You can ignore these messages

NOTE

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

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

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

the SAP Planning and Consolidation Operations Guide in httpservicesapcominstguidesepm-bpc

100 for the Microsoft Platform SBOP Plan amp Consol 100 MS Administrators Guide

2 Installing Planning and Consolidation Servers

24 Logging on to Servers

1454 CUSTOMER 2012-06-13

25 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

PrerequisitesPlanning and Consolidation 100 has the following Windows services

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

and avoid deadlocks

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

and global caches

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

management system

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

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

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

with the error message

Could not start the BPC SendGovernor service

The reason for this is that the Admin account is not registered as a service

When installing a service to run under a domain user account the account must have the right to

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

and must be granted in the Local Security Policy

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

permission perform the following actions

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

2 Expand Local Policies and then click User Rights Assignment

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

4 Add the user to the policy and click OK

5 Close the Local Security Settings MMC snap-in

For more details see How to Troubleshoot Service Startup Permissions http

supportmicrosoftcomkb259733

FeaturesDuring the installation enter user IDs and passwords for the following user types

System Admin ID

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

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

2 Installing Planning and Consolidation Servers

25 Service-level Accounts

2012-06-13 CUSTOMER 1554

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

26 Standard and Advanced Settings

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

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

NOTE

When defining server names the name refers to the NetBIOS name IP address and fully qualified

domain names (FQDN)

Standard Settings

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

setting

Server Option Value Description

SQL Database server name The name of the SQL DB server

OLAP server name The name of the OLAP server

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

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

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

Server Option Value Description

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

2 Installing Planning and Consolidation Servers

26 Standard and Advanced Settings

1654 CUSTOMER 2012-06-13

Server Option Value Description

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

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

Provider The only available value is SQL

Local path for EnvironmentShell 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 CPC_MSData

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 changesSee the Kerberos authentication settings section in the SAP Library Server Manager Guide on httpservicesapcominstguidesEPM-BPC

100 for the Microsoft Platform

Scheduler Server Name The name of the server used for scheduling usually the application server for example GMPV50072862B If you have multiple application servers select the appropriate one

NOTE

If the primary server stops working you must manually configure your application server database to froward requests to another application server

27 Installing the Prerequisites

271 Installing the Prerequisites ndash Basic Steps

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

software the operating system IIS SQL server analysis services ADOMDNET and MSXML This

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

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 1754

Prerequisites [page 11] and the Product Availability Matrix on the SAP Service Marketplace at http

servicesapcompam Search on Planning and Consolidation

NOTE

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

procedure

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

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

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

Active Directory (AD)

We recommend not installing Microsoft Office on the application server

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

(UMCexe) on the Planning and Consolidation CD in a folder called UMC_100_INSTALLER When

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

1 Choose a language for the UMC install wizard to use

2 Check that the prerequisite check status is Succeeded and click Next

3 When you are ready to install the UMC click Next on the welcome screen

4 Click I accept the License Agreement and then Next

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

6 Select the languages that you wish to install

7 Select the features that you want to install (POAFHelper dotnet is mandatory for Planning

and Consolidation)

8 On Start Installation click Next to complete the installation

2 Install the required operating system on the single-server computer or on each physical server for

a multiserver configuration See Installing the Operating System [page 19]

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

wwwmicrosoftcom

4 From your operating systems media install IIS

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

Installing SQL Server [page 19]

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

packs and hot fixes See Installing Analysis Services [page 23]

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

1854 CUSTOMER 2012-06-13

7 On your application server install ADOMDNET The Planning and Consolidation zip file contains

the ADOMDNET installation package in the following locations

For SQL Server 2008 mdash BPC SetupServerSQLSERVER2008_ASADOMD10_x64msi

For SQL Server 2012 mdash BPC SetupServerSQLSERVER2012_ASADOMD11_x64msi

8 On your application server install MSXML 40 Service Pack 2 or later

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

the following location BPC SetupServermsxmlmsi

9 On your application server install Microsoft Visual C++ 2005 Runtime Libraries SP1

The Microsoft Visual C++ 2005 SP1 installation package is contained in the Planning and

Consolidation zip file at the following location BPC SetupServervcredist_x64exe

NOTE

The version of vcredist_x64exe in BPC SetupServer has been updated to 8061000 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 httpwwwmicrosoftcomdownloadsen

detailsaspxFamilyID=C06B8369-60DD-4B64-A44B-84B371EDE16Dampltdisplaylanggt=en

272 Installing the Operating System

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

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

Marketplace at httpservicesapcompam Search on Planning and Consolidation

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

NOTE

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

languages such as Hebrew

ProcedureIf you are installing IIS 70 or 75 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

273 Installing the SQL Server

PrerequisitesDuring the installation procedure you have the opportunity to specify the location of the

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

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 1954

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 CEnvironmentShelldb10) 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 a 2008 2008 R2 and 2012 SQL Server

SQL Server Considerations

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

System (Windows Server) then enable IIS and ASPNET and install any Windows Server service

packs

IIS and NET Framework 40 are required on your application server

NOTE

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

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

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

nondefault instance of SQL Server

General Installation Steps

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

terms

2 Choose Install to install the SQL support files

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

Options section below then choose Next

4 Review disc space requirements then choose Next

5 In Server Configuration Perform the following actions

1 In the Service Accounts tab enter a Planning and Consolidation sysadmin account for the SQL

Server Database Engine and the SQL Server Analysis services This is required so that the Planning

and Consolidation sysadmin can create and process the Planning and Consolidation database

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

account This account is also required during Backup Environment and Restore Environment in the

Server Manager

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

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

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

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

application server

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2054 CUSTOMER 2012-06-13

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

Consolidation sysadmin for this service account

2 In the Collation tab set the collation settings to SQL_Latin1_General_CP1_CI_AS

Choose Next

6 Set Database Engine Configuration options then choose Next

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

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

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

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

you can install the SQL Server in Windows-only mode

7 Accept the Analysis Services Configuration default options and the remaining default options of the

installation program

8 Choose Install to begin the installation with the options you have set

SQL Server Component 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

Server Component What to Install

SQL Server Database Engine Services

SSAS Server Analysis Services

Application Server The following Shared Features Client Tools Connectivity Integration Services Client Tools SDK

Custom Settings for the SQL Server

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

SQL Server 2008 R2 and SQL Server 2012

Process Dimension

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

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

dimensions and cubes in parallel

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 2154

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

NOTE

Setting 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 tblFactWBltappgt table

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 Microsoftreg SQL Servertrade

20052008 which you can download from wwwmicrosoftcom (search on ldquoTable Partitioningrdquo to find

all relevant articles)

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

From SQL Server Configuration Manager confirm that the SQL Server Browser service is

running The browser service is required for Planning and Consolidation

From SQL Server Configuration Manager do the following

1 Select Protocols for ltInstanceNamegt then double-click TCPIP from the right side of the window

2 When prompted for the TCPIP Properties select IP Addresses You see two IPs that indicate the

localhost and external network interface machine

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2254 CUSTOMER 2012-06-13

3 If you want to use IP1 which indicates Server IP set Enabled to Yes and specify the TCP Port as

desired

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

RECOMMENDATION

We do not recommend using dynamic ports

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

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

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

recommendation prevents any conflict problems

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

server

1 Select Client Protocols from the SQL Native Client Configuration folder

2 From the right side of the window double-click TCPIP The TCPIP 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

NOTE

We 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

274 Installing Analysis Services

ProcedureAfter you install SQL Server and its required service packs and hotfixes you must install SQL Server

Analysis Services and its required service packs and hotfixes

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 2354

NOTE

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

that contains the repository before installing this release

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

and guidelines in httptechnetmicrosoftcomen-uslibraryms143219aspx

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 httpwwwmicrosoftcomdownloads

detailsaspxFamilyID=3be0488d-e7aa-4078-a050- ae39912d2e43ampdisplaylang=en

275 Installing the Anti-Cross Site Scripting Library

Procedure

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

Library (version 42 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 AntiXSSLibraryDLL from the Microsoft Web

site at httpwwwmicrosoftcomdownloadendetailsaspxid=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 AntiXssLibrarydll

28 Installing on a Single Server

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

consider the following issues

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

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

times the uncompressed size of the environment files

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

components

SQL Server

SQL Server Analysis Services (SSAS)

Application Server

FileShare server

Procedure

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

1 Exit all Windows programs

2 Installing Planning and Consolidation Servers

28 Installing on a Single Server

2454 CUSTOMER 2012-06-13

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

on to servers [page 14]

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

the Prerequisites [page 17]

4 Obtain SAP Planning and Consolidation from the Downloads SAP Installations amp Upgrades area of

SAP Service Marketplace then extract the files and run StartUpexe

5 From the Server Install screen select Install the Planning and Consolidation server

6 From the Welcome screen choose Next

7 From the License Agreement page choose I accept the terms of the license agreement then choose Next

8 From the Installation Method page accept the default Single machine enter a system ID for the system

landscape directory (SLD) and choose Next

NOTE

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

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

9 From the Authentication Method page choose the desired authentication method and choose Next

10 If you have chosen SAP BusinessObjects User Management System in the previous screen on the CMS

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

The following information is required

Field Description

System name CMS system name (server nameport number) for example CMSServer6400

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

11 After entering the CMS administrator authentication details choose Next

12 From the Service type accounts page enter service-level account user IDs and passwords See Service-

Level Accounts [page 15]

13 After defining the IDs and passwords choose Next

14 From the Server Information page (see Standard and Advanced Settings [page 16]) do one of the following

Review the standard settings and choose Next

To set advanced settings choose the Advanced Settings button Enter the desired information

and choose Next

2 Installing Planning and Consolidation Servers

28 Installing on a Single Server

2012-06-13 CUSTOMER 2554

15 Specify the location and name of AntiXssLibrarydll See Installing the Anti-Cross Site Scripting Library [page

24]

Choose Next

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

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

recommendation reduces the hard disk IO time and helps to speed up SQL commands

Accept the defaults or make your selections then choose Next

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

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

and Consolidation Server Manager

18 The installation process takes a few moments When it is complete choose Exit

19 A prompt is displayed to restart your computer Select OK to restart

20 Perform the steps in After Installing Planning and Consolidation Servers [page 27]

29 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 24]) with the following

exceptions

On the Installation Method page do not accept the default instead choose Network Load Balancing

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

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

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

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

In the Virtual Name field enter the virtual IP address virtual name in the default properties

2 Installing Planning and Consolidation Servers

29 Installing the Server in a Multiserver Configuration

2654 CUSTOMER 2012-06-13

3 After Installing Planning and Consolidation Servers

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

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

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

Consolidation NET Application Server [page 29]

3 Optional configuration steps [page 30]

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

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

30]

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

custom logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web

Site [page 31]

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

Data Source [page 32]

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

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

on the server For information about removing default access and creating a group that can

access the console see Removing Default Access to the Console [page 32]

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

recommend that you only grant Management Console access to system administrators

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

Management Console Access Control [page 33]

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

34]

4 Take the following steps to set up security

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

3 After Installing Planning and Consolidation Servers

31 Post-Installation Steps

2012-06-13 CUSTOMER 2754

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

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

Administrator

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

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

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

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

Administration client See Installing the Administration Client [page 37]

6 Start Planning and Consolidation Administration from the launch page

7 Select Connection Wizard and log on to EnvironmentShell

8 Create a new environment using EnvironmentShell as the source

9 Log on to the newly created environment and set up users teams and task profiles (You must

set up task profiles since there is no access to Planning and Consolidation tasks)

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

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

NOTE

To allow users to request and query large amounts of data you can edit the metabasexml file located

at CWindowssystem32inetsrv Set the following parameters to the stated values

ASPBUFFERINGLIMIT = 10485760

MAXREQUESTENTITYALLOWED = 10485760

32 Connecting to Solution Manager Diagnostics

NOTE

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

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

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

Solution Manager Diagnostics

Procedure

1 Install the Diagnostics Agent according to SAP Note 1234387 on all servers where application servers

are installed

NOTE

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

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

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

for managed systems DIAGNOSTICS AGENT 711

3 After Installing Planning and Consolidation Servers

32 Connecting to Solution Manager Diagnostics

2854 CUSTOMER 2012-06-13

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

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

Servers where Microsoft SQL Server is installed Do the following

1 Start Computer Management then select Action New User

2 Create a new user

3 Right-click on the user then choose Properties On the Member Of tab select Add

4 Add the group SQLServerltReleasegtSQLAgentUser$ltDomain or hostnamegt$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 httpsservicesapcom~sapidb011000358700000074392009E and follow

the chapters that apply to Planning and Consolidation

33 Configuring the Planning and Consolidation NET Application Servers

Procedure

Modifying machineconfig Files

To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock

occurrences that would cause the application server to ldquosleeprdquo and not process anymore you can

modify the machineconfig file which resides in the WINDOWSMicrosoftNETFramework64

v4030319Config directory

1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to

specify whether to automatically configure settings to achieve optimal performance based on the

machine configuration You can set this attribute to True or False

For more information see httpmsdnmicrosoftcomen-uslibrary7w2sway1aspx

2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the

Planning and Consolidation application) or Machineconfig (for all applications including

Planning and Consolidation) to ensure the validationKey and decryptionKey keys have the same

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

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

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

msdnmicrosoftcomen-uslibraryms998288aspx

3 After Installing Planning and Consolidation Servers

33 Configuring the Planning and Consolidation NET Application Servers

2012-06-13 CUSTOMER 2954

paght000007_webfarmdeploymentconsiderations and httpmsdnmicrosoftcomen-us

libraryms998310aspx

34 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 30]

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

logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page

31]

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

Source [page 32]

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

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

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

see Removing Default Access to the Console [page 32]

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

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

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

Access Control [page 33]

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

341 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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3054 CUSTOMER 2012-06-13

NOTE

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

User Activity and Service Status) does not work as expected

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

Active Log Format field in IIS to W3C Extended Log File Format

342 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 ApplicationHostconfig set the property customLogPluginClsid to the value FF16065B-

DE82-11CF-BC0A-00AA006111E0 Set the logFormat to Custom You can find this in the ltlogFilegt

node in ApplicationHostconfig as shown here

ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0

logFormat=Custom gt

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

appcmd site set sitenameDefault Web Site

logFilecustomLogPluginClsidFF16065B-DE82-11CF-BC0A-00AA006111E0

appcmd site set sitenameDefault Web Site logFilelogFormatCustom

Configuring ODBC Logging Parameters in ApplicationHostconfig

Configure ApplicationHostconfig to contain the database table information as set up in the Microsoft

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

node under ltsystemwebServergt

EXAMPLE

ltlocation path=Default Web Sitegt

ltsystemwebServergt

ltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog

userName=Username password=mypassword gt

ltsystemwebServergt

ltlocationgt

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3154

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

appcmd set config Default Web Site sectionodbcLogging

dataSourceBPC_ManagementDSN commitappHost

appcmd set config Default Web Site sectionodbcLogging tableNameBPCLog

commitappHost

appcmd set config Default Web Site sectionodbcLogging userNameUsername

commitappHost

appcmd set config Default Web Site sectionodbcLogging passwordmypassword

commitappHost

NOTE

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

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

931202 The requirements for using the ODBC logging feature in IIS

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

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

Server 2008 or Windows Server 2008 R2

Proceed as follows

1 Open ODBC Connection Manager

2 On the System DSN tab page add a new DSN

Choose Add

Choose SQL Server as the driver

Choose Finish

3 In the Name and Description fields enter BPC_ManagementDSN

4 In the Server field enter the name of your SQL Server Choose Next

5 Leave the default settings and choose Next

6 Choose the Change the default database to field and enter AppServer Choose Next

7 Leave default settings and choose Next

8 Choose OK

344 Removing Default Access to the Console

NOTE

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

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

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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3254 CUSTOMER 2012-06-13

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

console use the procedure described below

NOTE

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

Management Console or in the Active Directory

1 In the context menu of the servers My Computer icon choose Manage

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

NOTE

Alternatively you can perform analogous steps in Active Directory

3 In the 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

NOTE

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

10 In the Security dialog box click Copy to ensure that the System group retains its privileges

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

12 Choose Authentication in the center pane then disable Windows authentication

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

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

would otherwise have to Planning and Consolidation

345 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 32] Their rights in

Active Directory determine what they can access in the Console

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

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

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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3354

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

privileges For more information see the SAP Library Planning and Consolidation Administrators Guide in

httpservicesapcominstguidesepm-bpc 100 version for the Microsoft platform

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

levels of Console users (read-only users for example) in your environment

To grant or limit access to users or groups you can add or remove the following privileges from the

areas described in this table

Privilege Rights Management Area

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

Performance Monitor Counters Administrators group on application server or domain Power Users group on application server or domain Performance Monitor Users group on application server

Microsoft Analysis Services performance monitoring

Administrators group on application server or domain

Microsoft SQL Server Monitoring (performance counters and statistics)

Administrators group on application server or domain

346 Using Client Certificates

To enable the use of client certificates in Planning and Consolidation you must follow several manual

steps

NOTE

Planning 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 httptechnetmicrosoftcomen-us

librarycc753810aspx

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

technetmicrosoftcomen-uslibrarycc732996(WS10)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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3454 CUSTOMER 2012-06-13

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

authentication) to connect to Planning and Consolidation

2 Enable anonymous authentication

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

2 Select the ManagementConsole directory (ltWebsitegtManagementConsole) to open the

ManagementConsole home page

3 Double-click Authentication and enable Anonymous Authentication

4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way

as in step 3

5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the same

way as in step 3

3 Change the web configuration settings

1 Open the ltPC_MSgtWebsrvrWebBPCwebconfig file

2 Find the text clientCredentialType=Windows

3 Change value of clientCredentialType to None (clientCredentialType=None)

4 Open the PC_MSWebsrvrWebPOASBCwebconfig file Repeat steps 2 and 3

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3554

This page is left blank for documents that are printed on both sides

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

The installation of the Planning and Consolidation Administration Client allows administrators to

build and maintain Planning and Consolidation environments and models and administer security

All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions

add-in for Microsoft Office for more information see the SAP BusinessObjects EPM solutions add-in for

Microsoft Office help

NOTE

You must update the Administration Client to the same version as the server

If your PC is on a different domain than your server you must set the Internet Explorer

Security Zone value of the Planning and Consolidation client to prompt for user name and

password Otherwise the Planning and Consolidation Start Page does not display

41 Installing the Administration Client

Prerequisites

NOTE

For a definitive list of system requirements see the Product Availability Matrix on SAP Service

Marketplace at httpservicesapcompam Search on Planning and Consolidation

The following list describes the minimum software requirements

Microsoft Internet Explorer 70 or 80

Microsoft Office 2007 or 2010

NET Framework 20 or higher (install any required NET Framework Hotfixes by referring to

httpsupportmicrosoftcomkb)

Pentium IV (1 GHz CPU)

512 MB RAM

100 MB of free hard disk space in the My Documents folder

20 MB of free hard disk space for the installed Administration files

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

41 Installing the Administration Client

2012-06-13 CUSTOMER 3754

NOTE

We recommend that you install all of the latest Microsoft Windows hotfixes prior to installing

the Administration client For information about which hotfixes to install see http

updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us

ProcedureThe following procedure describes how to install the Administration Client on to an administratorrsquos

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 AddRemove Programs in the Windows Control Panel

3 Point your browser to the Planning and Consolidation Web at httpltPC_serverportgtsap

bpcweb

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

42 Installing the EPM Add-in

The Planning and Consolidation installation media does not contain the EPM addin setup program

You must download the most recent version of the full setup (EPM Add-inexe) from the Service

Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPC

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

43 Using the Client Auto Update Program

If Planning and Consolidation version 100 or later is installed you can use the Client Auto Update

program to set up the server so that it determines if an upgrade for a connecting Administration client

is necessary

The following describes the use of the auto update program for the Administration Client and the EPM

add-in

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

42 Installing the EPM Add-in

3854 CUSTOMER 2012-06-13

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

To use the Client Auto Update program for the Administration Client proceed as follows

1 From the Server Manager select Options Client Options

2 Select Admin Update

3 If users without administrator rights on their machines use the auto update enter an administrator

ID and password in the Admin ID and Admin password fields respectively The Admin ID should be a

member of the local administrators group on all the computers running the auto update This

setting is not needed if all users have administrator rights on their machines

4 Select Update

For the EPM Add-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 Optionshellip 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 Market Place (SMP) at httpservicesapcom

All support packages and patches are available from the SMP as a zip file

EPMEXCLCLNTltSPLgtzip is for a support package

EPMEXCLCLNTltSPLgtPltPLgtzip 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 ltSP versiongtmsp

EPM Addin Support Package ltSP versiongtxml

For a patch these files are

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

43 Using the Client Auto Update Program

2012-06-13 CUSTOMER 3954

EPM Addin Patch ltpatch numbergtmsp

EPM Addin Patch ltpatch numbergtxml

2 Unzip the zip file and extract the two files to the application server folder (WebsrvrWebBPC

Installation)

3 From the Server Manager select Options Client Options

The system lists the available packages Select the package that you want to use for the autoupdate

You can set a different update policy for each package listed

EXAMPLE

The following table illustrates some possible situations assuming that you have installed the

first full version (V1)

Available maintenance packages

V2-user updateV3-force updateV4-force updateV5-user update

V5-user update V5-user updateV6-auto updateV7-force update

Minimum Required Version

V4 V4 V7

Notification A prompt tells the user to install maintenance package V4 using the Forced Update behavior

If User Update is enabled the prompt informs the user that maintenance package V5 is available

A prompt tells the user to install maintenance package V7 using the Forced Update behavior

New Version V4 V4 or V5 V7

If you change the update policy for any package click Update to complete the change

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

43 Using the Client Auto Update Program

4054 CUSTOMER 2012-06-13

5 Connection Issues

You may experience connection problems with ports the proxy server or programs and settings that

interact with these components If you have any issues related to connection review the following

recommendations and troubleshooting tips

51 Checking for Open Ports

You must ensure that all required ports are open for inboundoutbound 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 431181836 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

NOTE

You can use the following site to scan for the normal ports It allows you to manually enter a port

number to test

httpwwwmyserverorgportsniffasp

You can change the name of a port

52 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 Explorer Tools Internet Options Connections LAN Settings ) or at the server level

Enabling content filtering on the proxy server or firewall may cause connection problems

If external users are having trouble connecting to the server make sure the proxy server connects

using a fully qualified domain name Fully qualified domain names typically resolve both internal

and external IP addresses

Each secure Planning and Consolidation server name must be identified on the proxy server

Proxy servers may or may not require authentication which could conflict with Planning and

Consolidation authentication Do not use authentication on the proxy server The system

5 Connection Issues

51 Checking for Open Ports

2012-06-13 CUSTOMER 4154

synchronizes the user name and password on the remote server with the local user name and

password

NOTE

For more information about setting up an ISA proxy server contact SAP Support to request a

copy of Setting up ISA Proxy Server White Paper

Internet Explorer Settings 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

5 Connection Issues

52 Proxy Server and Firewall Issues

4254 CUSTOMER 2012-06-13

6 Installing Planning and Consolidation with Two Active Directory Domains

To set up a Planning and Consolidation 10 application server in a hosted environment and use your

own domain users follow this procedure In general you install Planning and Consolidation on the

host domain use the host domain account and assign it to the Planning and Consolidation users

SysAdmin Admin and Users Then you accept one way trust (the host domain trusts your domain)

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

6 Installing Planning and Consolidation with Two Active Directory Domains

2012-06-13 CUSTOMER 4354

This page is left blank for documents that are printed on both sides

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

This section describes best practices and instructions for installing Planning and Consolidation in a

Terminal Services or Citrix Server deployment

71 Terminal Services Home Directories

We recommend using Terminal Server home directories rather than using the userrsquos 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

72 System Requirements

The Citrix server should be one of the following systems

XenApp 5 Enterprise

XenApp 5 Platinum

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

73 Installing Planning and Consolidation

Prerequisites

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

Procedure

The following steps outline how to install the Planning and Consolidation clients in a Terminal Services

(TS) or Citrix Server deployment

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

71 Terminal Services Home Directories

2012-06-13 CUSTOMER 4554

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 userinstall

4 Open a browser and connect to the URL httpltPC_serverportgtsapbpcweb

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 userexecute 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 Iexploreexe http(s)

ltServerNamegt-NetBIOS or FQDNsapbpcweb

To publish Planning and Consolidation Administration CProgram FilesPC_MS

BPCAdminMainexe

74 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 userrsquos desktop) must be moved to the All UsersDesktop folder

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

74 Creating a Shortcut to the Launch Page

4654 CUSTOMER 2012-06-13

8 Installing SSIS Custom Tasks

This section provides background information and instructions for installing SQL Server Integration

Services (SSIS) for SQL Server 2008 and SQL Server 2012

The Planning and Consolidation Data Manager component supports and uses SSIS Since SQL Server

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

81 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 Filelistxml 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

OSoftSetupexe ‒ 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 or OSoftSSIS2012_Client on the client machine followed by the SQL Server

version If you want to use SQL 2008 Tasks under the SQL 2012 environment you must install

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

You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package by extracting

OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPC

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 or

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4754

OSoftSSIS2012_Client for creating a COM+ application For more information see Before You Modify

the SSIS Packages [page 50] and Setup of a COM+ Application on the Application Server [page 51]

Bin folder

This folder contains the following components

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCCachedll Planning and Consolidation Cache file

BPCDataFlowPackagedll or BPCDataFlowPackage2012dll

BPCDMdll

BPCDMTaskMaindll COM+ component

BPCFilePreviewdll

BPCGacUtil_20exe System File

BPCGacUtil_40exe System File

BPCImpersonatordll Planning and Consolidation Impersonator

BPCLogicdll

BPCScriptdll

BPCServerZipdll

BPCServiceResdll

BPCTransferMembersdll

BPCWriteBackdll

InteropDTSdll

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

4854 CUSTOMER 2012-06-13

Name Remark

OSoftAdminServerdll

OSoftAuditdll

OSoftComLibServerdll

OSoftCommonResQrydll

OSoftConfigurationdll

OSoftCustomXMLSvrdll

OSoftDatabaseADMINdll

OSoftDatabaseSYSADMINdll

OSoftDatabaseSYSADMINDMdll

OSoftDatabaseUSERdll

OSoftDMDTSXExecutedll or OSoftDMDTSXExecute2012dll

OSoftDMTaskFormdll

OSoftDMTaskMaindll

OSoftDMToolsdll

OSoftFileManagedll

OSoftLoggingdll

OSoftLogWriterdll

OSoftMetaDatadll

OSoftSQEdll

OSoftSystemConfigdll

OutlookSoftconfig Configuration file to connect DB server

XceedCompressiondll XceedZip file

XceedCompressionFormatsdll XceedZip file

XceedFileSystemdll XceedZip file

XceedZipdll XceedZip file

Config folder

This folder has FileListxml 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 FileListxml 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

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4954

OSoftSetupexe

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

NOTE

If you installed the OSoftSSIS2008_Client or OSoftSSIS2012_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

Resources Folder

This folder contains the BPCServicesdll and BPCServiceUIdll files which contain resource text

Only English resources are included for the SSIS custom tasks

82 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

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008 and 2012 respectively

8 Installing SSIS Custom Tasks

82 Before You Modify the SSIS Packages

5054 CUSTOMER 2012-06-13

Name Remark

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012 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

lthellipgtOSoftSSIS2008_Clientbin or lthellipgtOSoftSSIS2012_Clientbin

On the Planning and Consolidation application server

ltdrivegtWebsrvrbin

2 Paste these files into the folder 100DTSTasks for SQL Server 2008 or into 110DTSTasks for

SQL Server 2012 For example if you install your SQL 2008 server or R2 on CProgram Files

Microsoft SQL Server paste all files into the CProgram Files (x86)Microsoft SQL Server

100DTSTasks folder

In Integration Services set the property Run64BitRunTime to True

83 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 or OSoftSSIS2012_Client on the

application server

8 Installing SSIS Custom Tasks

83 Setup of a COM+ Application on the Application Server

2012-06-13 CUSTOMER 5154

Typographic Conventions

Example Description

ltgt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example Enter your ltUser Namegt

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 httpwwwsapcom

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

5254 CUSTOMER 2012-06-13

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

  • SAP BusinessObjects Planning and Consolidation 100
    • Table of Contents
    • 1 Introduction
      • 11 SAP Notes for the Installation
      • 12 Naming Conventions
        • 2 Installing Planning and Consolidation Servers
          • 21 Basic Steps
          • 22 Prerequisites
          • 23 Before Starting the Planning and Consolidation Server Installation
          • 24 Logging on to Servers
          • 25 Service-level Accounts
          • 26 Standard and Advanced Settings
          • 27 Installing the Prerequisites
            • 271 Installing the Prerequisites ndash Basic Steps
            • 272 Installing the Operating System
            • 273 Installing the SQL Server
            • 274 Installing Analysis Services
            • 275 Installing the Anti-Cross Site Scripting Library
              • 28 Installing on a Single Server
              • 29 Installing the Server in a Multiserver Configuration
                • 3 After Installing Planning and Consolidation Servers
                  • 31 Post-Installation Steps
                  • 32 Connecting to Solution Manager Diagnostics
                  • 33 Configuring the Planning and Consolidation NET Application Servers
                  • 34 Post-Installation Optional Configuration Steps
                    • 341 Enabling the Management Console
                    • 342 Setting Up ODBC Logging in IIS for the Default Web Site
                    • 343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2
                    • 344 Removing Default Access to the Console
                    • 345 Management Console Access Control
                    • 346 Using Client Certificates
                        • 4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office
                          • 41 Installing the Administration Client
                          • 42 Installing the EPM Add-in
                          • 43 Using the Client Auto Update Program
                            • 5 Connection Issues
                              • 51 Checking for Open Ports
                              • 52 Proxy Server and Firewall Issues
                                • 6 Installing Planning and Consolidation with Two Active Directory Domains
                                • 7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
                                  • 71 Terminal Services Home Directories
                                  • 72 System Requirements
                                  • 73 Installing Planning and Consolidation
                                  • 74 Creating a Shortcut to the Launch Page
                                    • 8 Installing SSIS Custom Tasks
                                      • 81 Composition of SSIS Custom Task Installation
                                      • 82 Before You Modify the SSIS Packages
                                      • 83 Setup of a COM+ Application on the Application Server
                                          • Copyright and trademarks
Page 3: Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

Document History

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

Version Date Description

10 2012-01-31 Accompanies the General Availability release

11 2012-03-05 Revised chapters ldquoInstalling the Anti-Cross Site Scripting Libraryrdquo and ldquoInstalling on a Single ServerrdquoAdded chapter ldquoUsing Client Certificatesrdquo

115 2012-03-30 Added SAP Note 1665656 for SP6 to ldquoSAP Notes for the Installationrdquo

120 2012-04-03 In the topic ldquoInstalling the Server in a Multiserver Configurationrdquo added the recommendation to use a round robin approach to assign resources for load balancing

125 2012-04-30 In the topic ldquoInstalling the Prerequisites ‒ Basic Stepsrdquo 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

130 2012-06-07 Modified the document to incorporate SQL Server 2012 support within support package 7

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

136 2012-06-11 Updated the location of the machineconfig file in the topic ldquoConfiguring the Planning and Consolidation NET Application Serversrdquo

137 2012-06-13 Updated NET 20 to NET 40 in the topic ldquoConfiguring the Planning and Consolidation NET Application Serversrdquo

2012-06-13 CUSTOMER 354

Table of Contents

Chapter 1 Introduction 7

11 SAP Notes for the Installation 7

12 Naming Conventions 9

Chapter 2 Installing Planning and Consolidation Servers 11

21 Basic Steps 11

22 Prerequisites 11

23 Before Starting the Planning and Consolidation Server

Installation 13

24 Logging on to Servers 14

25 Service-level Accounts 15

26 Standard and Advanced Settings 16

27 Installing the Prerequisites 17

271 Installing the Prerequisites ‒ Basic Steps 17

272 Installing the Operating System 19

273 Installing the SQL Server 19

274 Installing Analysis Services 23

275 Installing the Anti-Cross Site Scripting Library 24

28 Installing on a Single Server 24

29 Installing the Server in a Multiserver Configuration 26

Chapter 3 After Installing Planning and Consolidation Servers 27

31 Post-Installation Steps 27

32 Connecting to Solution Manager Diagnostics 28

33 Configuring the Planning and Consolidation NET Application

Servers 29

34 Post-Installation Optional Configuration Steps 30

341 Enabling the Management Console 30

342 Setting Up ODBC Logging in IIS for the Default Web Site 31

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

2008 R2 32

454 CUSTOMER 2012-06-13

344 Removing Default Access to the Console 32

345 Management Console Access Control 33

346 Using Client Certificates 34

Chapter 4 Installing Planning and Consolidation Administration Client and the

SAP BusinessObjects EPM solutions Add-in for Microsoft

Office 37

41 Installing the Administration Client 37

42 Installing the EPM Add-in 38

43 Using the Client Auto Update Program 38

Chapter 5 Connection Issues 41

51 Checking for Open Ports 41

52 Proxy Server and Firewall Issues 41

Chapter 6 Installing Planning and Consolidation with Two Active Directory

Domains 43

Chapter 7 Installing Planning and Consolidation in a Terminal Services or Citrix

Server Deployment 45

71 Terminal Services Home Directories 45

72 System Requirements 45

73 Installing Planning and Consolidation 45

74 Creating a Shortcut to the Launch Page 46

Chapter 8 Installing SSIS Custom Tasks 47

81 Composition of SSIS Custom Task Installation 47

82 Before You Modify the SSIS Packages 50

83 Setup of a COM+ Application on the Application Server 51

2012-06-13 CUSTOMER 554

This page is left blank for documents that are printed on both sides

1 Introduction

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

Administrators who perform Planning and Consolidation server and Administration client

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

and the server and client software

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

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

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

servicesapcominstguidesEPM-BPC Planning and Consolidation 100 version for the Microsoft platform

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

BusinessObjects EPM solutions add-in for Microsoft Office help

New Installation Program Features in 100

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

11 SAP Notes for the Installation

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

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

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

Marketplace at the Internet address httpservicesapcomnotes

1 Introduction

11 SAP Notes for the Installation

2012-06-13 CUSTOMER 754

SAP Note Number Title Comments

1584890 Documentation Addendum Contains information that does not appear in the application help of Planning and Consolidation 100 version for the Micrososft platform

1733053 SAP Planning and Consolidation 100 SP08 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP08This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1689792 SAP Planning and Consolidation 100 SP07 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP07This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1665656 SAP Planning and Consolidation 100 SP06 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP06This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1643037 SAP Planning and Consolidation 100 SP05 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP05This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1620464 SAP Planning and Consolidation 100 SP04 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP04This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1601213 SAP Planning and Consolidation 100 SP03 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP03This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1591848 SAP Planning and Consolidation 100 SP02 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP02This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1 Introduction

11 SAP Notes for the Installation

854 CUSTOMER 2012-06-13

SAP Note Number Title Comments

1573539 SAP Planning and Consolidation 100 SP01 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP01This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

12 Naming Conventions

In this document the following naming conventions apply

Variable Description

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

ltdrivegt The drive where SAP Planning and Consolidation is installedThe default for this is CPC_MS

1 Introduction

12 Naming Conventions

2012-06-13 CUSTOMER 954

This page is left blank for documents that are printed on both sides

2 Installing Planning and Consolidation Servers

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

and what to do before during and after the server installation

21 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 at httpservicesapcominstguidesepm-bpc 100 version for the Microsoft platform

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

including installing all prerequisites

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

Consolidation on a Single Server [page 24]

NOTE

You must install both Planning and Consolidation 100 as well as the most recent Planning

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

httpservicesapcomswdc Software Downloads Support Packages and Patches A - Z Index

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

Versions SAP CPM BPC 100 M Windows Server on x64 64bit

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

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

22 Prerequisites

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

Consolidation server and the minimum versions required

NOTE

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

Availability Matrix on SAP Service Marketplace at httpservicesapcompam Search on

Planning and Consolidation

2 Installing Planning and Consolidation Servers

21 Basic Steps

2012-06-13 CUSTOMER 1154

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 or

Data Center with or without Hyper-V

NOTE

The operating system must be configured with NTFS

Relational Database Microsoft SQL Server 2008 Enterprise Edition Microsoft SQL Server 2008 R2 (Gemini) Enterprise Edition Microsoft SQL Server 2012 Enterprise Edition

OLAP Database Microsoft SQL Server 2008 Enterprise Edition ‒ Analysis Server Microsoft SQL Server 2008 R2 Enterprise Edition ‒ Analysis Server Microsoft SQL Server 2012 Enterprise Edition ‒ Analysis Server

Data Integration Microsoft SQL Server 2008 Enterprise Edition ‒ SQL Service Integration Services

Microsoft SQL Server 2008 R2 Enterprise Edition ‒ SQL Service Integration Services

Microsoft SQL Server 2012 Enterprise Edition ‒ SQL Service Integration Services

Other Requirements MSXML 40 SP2 or later ADOMDNET

ADOMDNET 100 when running SQL Server 2008 or 2008 R2 ADOMDNET 110 when running SQL Server 2012

SQL Server software components NET 40 IIS 75 or IIS 70

(Included in your Operating System IIS 75 is required for Windows 2008 R2 editions)

Anti-Cross Site Scripting Library 42This component must be downloaded before installing the server The server installation program asks for the path of each file and copies the files into the appropriate Planning and Consolidation path

Microsoft Visual C++ 2005 Runtime Libraries SP1 Microsoft Access Database Engine 2010 64bit VMWare ESX 3x or ESX 40

(Required only if a landscape deployment strategy using virtualization technologies is planned)

NOTE

MSXML 40 SP2 ADOMDNET 100 and Microsoft Visual C++ 2005 Runtime Libraries SP1 are included with the installation program but not installed automatically

RECOMMENDATION

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

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

2 Installing Planning and Consolidation Servers

22 Prerequisites

1254 CUSTOMER 2012-06-13

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

1429246 which also contains download information

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

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

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

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

23 Before Starting the Planning and Consolidation Server Installation

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

installation

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

information see Installing the Prerequisites [page 17]

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

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

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

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

Settings [page 16]

Make sure all required server ports are open and that there is communication between the physical

servers on which you are going to install the server types See Checking for Open Ports [page 41]

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

See Service-Level Accounts [page 15]

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

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

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

with the installation

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

reinstall them

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

turn off Script Blocking

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

install Planning and Consolidation 100 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 fsntfsV

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

2 Installing Planning and Consolidation Servers

23 Before Starting the Planning and Consolidation Server Installation

2012-06-13 CUSTOMER 1354

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

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

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

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

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

Consolidation We recommend that you use static IP addresses

IIS must be enabled

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

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

the following

1 Copy the EnvironmentShell database file ServerEnvironmentShelldb10 from the

Planning and Consolidation installation program to any folder on the SQL server (for example

cEnvironmentShelldb10)

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

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

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

24 Logging on to Servers

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

components

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

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

Administrator group on the local server

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

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

You can ignore these messages

NOTE

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

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

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

the SAP Planning and Consolidation Operations Guide in httpservicesapcominstguidesepm-bpc

100 for the Microsoft Platform SBOP Plan amp Consol 100 MS Administrators Guide

2 Installing Planning and Consolidation Servers

24 Logging on to Servers

1454 CUSTOMER 2012-06-13

25 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

PrerequisitesPlanning and Consolidation 100 has the following Windows services

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

and avoid deadlocks

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

and global caches

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

management system

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

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

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

with the error message

Could not start the BPC SendGovernor service

The reason for this is that the Admin account is not registered as a service

When installing a service to run under a domain user account the account must have the right to

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

and must be granted in the Local Security Policy

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

permission perform the following actions

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

2 Expand Local Policies and then click User Rights Assignment

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

4 Add the user to the policy and click OK

5 Close the Local Security Settings MMC snap-in

For more details see How to Troubleshoot Service Startup Permissions http

supportmicrosoftcomkb259733

FeaturesDuring the installation enter user IDs and passwords for the following user types

System Admin ID

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

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

2 Installing Planning and Consolidation Servers

25 Service-level Accounts

2012-06-13 CUSTOMER 1554

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

26 Standard and Advanced Settings

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

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

NOTE

When defining server names the name refers to the NetBIOS name IP address and fully qualified

domain names (FQDN)

Standard Settings

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

setting

Server Option Value Description

SQL Database server name The name of the SQL DB server

OLAP server name The name of the OLAP server

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

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

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

Server Option Value Description

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

2 Installing Planning and Consolidation Servers

26 Standard and Advanced Settings

1654 CUSTOMER 2012-06-13

Server Option Value Description

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

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

Provider The only available value is SQL

Local path for EnvironmentShell 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 CPC_MSData

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 changesSee the Kerberos authentication settings section in the SAP Library Server Manager Guide on httpservicesapcominstguidesEPM-BPC

100 for the Microsoft Platform

Scheduler Server Name The name of the server used for scheduling usually the application server for example GMPV50072862B If you have multiple application servers select the appropriate one

NOTE

If the primary server stops working you must manually configure your application server database to froward requests to another application server

27 Installing the Prerequisites

271 Installing the Prerequisites ndash Basic Steps

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

software the operating system IIS SQL server analysis services ADOMDNET and MSXML This

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

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 1754

Prerequisites [page 11] and the Product Availability Matrix on the SAP Service Marketplace at http

servicesapcompam Search on Planning and Consolidation

NOTE

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

procedure

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

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

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

Active Directory (AD)

We recommend not installing Microsoft Office on the application server

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

(UMCexe) on the Planning and Consolidation CD in a folder called UMC_100_INSTALLER When

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

1 Choose a language for the UMC install wizard to use

2 Check that the prerequisite check status is Succeeded and click Next

3 When you are ready to install the UMC click Next on the welcome screen

4 Click I accept the License Agreement and then Next

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

6 Select the languages that you wish to install

7 Select the features that you want to install (POAFHelper dotnet is mandatory for Planning

and Consolidation)

8 On Start Installation click Next to complete the installation

2 Install the required operating system on the single-server computer or on each physical server for

a multiserver configuration See Installing the Operating System [page 19]

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

wwwmicrosoftcom

4 From your operating systems media install IIS

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

Installing SQL Server [page 19]

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

packs and hot fixes See Installing Analysis Services [page 23]

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

1854 CUSTOMER 2012-06-13

7 On your application server install ADOMDNET The Planning and Consolidation zip file contains

the ADOMDNET installation package in the following locations

For SQL Server 2008 mdash BPC SetupServerSQLSERVER2008_ASADOMD10_x64msi

For SQL Server 2012 mdash BPC SetupServerSQLSERVER2012_ASADOMD11_x64msi

8 On your application server install MSXML 40 Service Pack 2 or later

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

the following location BPC SetupServermsxmlmsi

9 On your application server install Microsoft Visual C++ 2005 Runtime Libraries SP1

The Microsoft Visual C++ 2005 SP1 installation package is contained in the Planning and

Consolidation zip file at the following location BPC SetupServervcredist_x64exe

NOTE

The version of vcredist_x64exe in BPC SetupServer has been updated to 8061000 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 httpwwwmicrosoftcomdownloadsen

detailsaspxFamilyID=C06B8369-60DD-4B64-A44B-84B371EDE16Dampltdisplaylanggt=en

272 Installing the Operating System

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

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

Marketplace at httpservicesapcompam Search on Planning and Consolidation

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

NOTE

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

languages such as Hebrew

ProcedureIf you are installing IIS 70 or 75 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

273 Installing the SQL Server

PrerequisitesDuring the installation procedure you have the opportunity to specify the location of the

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

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 1954

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 CEnvironmentShelldb10) 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 a 2008 2008 R2 and 2012 SQL Server

SQL Server Considerations

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

System (Windows Server) then enable IIS and ASPNET and install any Windows Server service

packs

IIS and NET Framework 40 are required on your application server

NOTE

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

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

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

nondefault instance of SQL Server

General Installation Steps

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

terms

2 Choose Install to install the SQL support files

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

Options section below then choose Next

4 Review disc space requirements then choose Next

5 In Server Configuration Perform the following actions

1 In the Service Accounts tab enter a Planning and Consolidation sysadmin account for the SQL

Server Database Engine and the SQL Server Analysis services This is required so that the Planning

and Consolidation sysadmin can create and process the Planning and Consolidation database

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

account This account is also required during Backup Environment and Restore Environment in the

Server Manager

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

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

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

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

application server

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2054 CUSTOMER 2012-06-13

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

Consolidation sysadmin for this service account

2 In the Collation tab set the collation settings to SQL_Latin1_General_CP1_CI_AS

Choose Next

6 Set Database Engine Configuration options then choose Next

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

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

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

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

you can install the SQL Server in Windows-only mode

7 Accept the Analysis Services Configuration default options and the remaining default options of the

installation program

8 Choose Install to begin the installation with the options you have set

SQL Server Component 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

Server Component What to Install

SQL Server Database Engine Services

SSAS Server Analysis Services

Application Server The following Shared Features Client Tools Connectivity Integration Services Client Tools SDK

Custom Settings for the SQL Server

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

SQL Server 2008 R2 and SQL Server 2012

Process Dimension

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

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

dimensions and cubes in parallel

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 2154

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

NOTE

Setting 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 tblFactWBltappgt table

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 Microsoftreg SQL Servertrade

20052008 which you can download from wwwmicrosoftcom (search on ldquoTable Partitioningrdquo to find

all relevant articles)

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

From SQL Server Configuration Manager confirm that the SQL Server Browser service is

running The browser service is required for Planning and Consolidation

From SQL Server Configuration Manager do the following

1 Select Protocols for ltInstanceNamegt then double-click TCPIP from the right side of the window

2 When prompted for the TCPIP Properties select IP Addresses You see two IPs that indicate the

localhost and external network interface machine

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2254 CUSTOMER 2012-06-13

3 If you want to use IP1 which indicates Server IP set Enabled to Yes and specify the TCP Port as

desired

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

RECOMMENDATION

We do not recommend using dynamic ports

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

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

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

recommendation prevents any conflict problems

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

server

1 Select Client Protocols from the SQL Native Client Configuration folder

2 From the right side of the window double-click TCPIP The TCPIP 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

NOTE

We 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

274 Installing Analysis Services

ProcedureAfter you install SQL Server and its required service packs and hotfixes you must install SQL Server

Analysis Services and its required service packs and hotfixes

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 2354

NOTE

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

that contains the repository before installing this release

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

and guidelines in httptechnetmicrosoftcomen-uslibraryms143219aspx

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 httpwwwmicrosoftcomdownloads

detailsaspxFamilyID=3be0488d-e7aa-4078-a050- ae39912d2e43ampdisplaylang=en

275 Installing the Anti-Cross Site Scripting Library

Procedure

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

Library (version 42 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 AntiXSSLibraryDLL from the Microsoft Web

site at httpwwwmicrosoftcomdownloadendetailsaspxid=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 AntiXssLibrarydll

28 Installing on a Single Server

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

consider the following issues

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

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

times the uncompressed size of the environment files

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

components

SQL Server

SQL Server Analysis Services (SSAS)

Application Server

FileShare server

Procedure

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

1 Exit all Windows programs

2 Installing Planning and Consolidation Servers

28 Installing on a Single Server

2454 CUSTOMER 2012-06-13

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

on to servers [page 14]

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

the Prerequisites [page 17]

4 Obtain SAP Planning and Consolidation from the Downloads SAP Installations amp Upgrades area of

SAP Service Marketplace then extract the files and run StartUpexe

5 From the Server Install screen select Install the Planning and Consolidation server

6 From the Welcome screen choose Next

7 From the License Agreement page choose I accept the terms of the license agreement then choose Next

8 From the Installation Method page accept the default Single machine enter a system ID for the system

landscape directory (SLD) and choose Next

NOTE

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

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

9 From the Authentication Method page choose the desired authentication method and choose Next

10 If you have chosen SAP BusinessObjects User Management System in the previous screen on the CMS

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

The following information is required

Field Description

System name CMS system name (server nameport number) for example CMSServer6400

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

11 After entering the CMS administrator authentication details choose Next

12 From the Service type accounts page enter service-level account user IDs and passwords See Service-

Level Accounts [page 15]

13 After defining the IDs and passwords choose Next

14 From the Server Information page (see Standard and Advanced Settings [page 16]) do one of the following

Review the standard settings and choose Next

To set advanced settings choose the Advanced Settings button Enter the desired information

and choose Next

2 Installing Planning and Consolidation Servers

28 Installing on a Single Server

2012-06-13 CUSTOMER 2554

15 Specify the location and name of AntiXssLibrarydll See Installing the Anti-Cross Site Scripting Library [page

24]

Choose Next

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

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

recommendation reduces the hard disk IO time and helps to speed up SQL commands

Accept the defaults or make your selections then choose Next

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

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

and Consolidation Server Manager

18 The installation process takes a few moments When it is complete choose Exit

19 A prompt is displayed to restart your computer Select OK to restart

20 Perform the steps in After Installing Planning and Consolidation Servers [page 27]

29 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 24]) with the following

exceptions

On the Installation Method page do not accept the default instead choose Network Load Balancing

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

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

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

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

In the Virtual Name field enter the virtual IP address virtual name in the default properties

2 Installing Planning and Consolidation Servers

29 Installing the Server in a Multiserver Configuration

2654 CUSTOMER 2012-06-13

3 After Installing Planning and Consolidation Servers

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

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

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

Consolidation NET Application Server [page 29]

3 Optional configuration steps [page 30]

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

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

30]

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

custom logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web

Site [page 31]

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

Data Source [page 32]

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

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

on the server For information about removing default access and creating a group that can

access the console see Removing Default Access to the Console [page 32]

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

recommend that you only grant Management Console access to system administrators

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

Management Console Access Control [page 33]

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

34]

4 Take the following steps to set up security

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

3 After Installing Planning and Consolidation Servers

31 Post-Installation Steps

2012-06-13 CUSTOMER 2754

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

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

Administrator

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

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

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

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

Administration client See Installing the Administration Client [page 37]

6 Start Planning and Consolidation Administration from the launch page

7 Select Connection Wizard and log on to EnvironmentShell

8 Create a new environment using EnvironmentShell as the source

9 Log on to the newly created environment and set up users teams and task profiles (You must

set up task profiles since there is no access to Planning and Consolidation tasks)

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

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

NOTE

To allow users to request and query large amounts of data you can edit the metabasexml file located

at CWindowssystem32inetsrv Set the following parameters to the stated values

ASPBUFFERINGLIMIT = 10485760

MAXREQUESTENTITYALLOWED = 10485760

32 Connecting to Solution Manager Diagnostics

NOTE

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

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

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

Solution Manager Diagnostics

Procedure

1 Install the Diagnostics Agent according to SAP Note 1234387 on all servers where application servers

are installed

NOTE

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

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

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

for managed systems DIAGNOSTICS AGENT 711

3 After Installing Planning and Consolidation Servers

32 Connecting to Solution Manager Diagnostics

2854 CUSTOMER 2012-06-13

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

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

Servers where Microsoft SQL Server is installed Do the following

1 Start Computer Management then select Action New User

2 Create a new user

3 Right-click on the user then choose Properties On the Member Of tab select Add

4 Add the group SQLServerltReleasegtSQLAgentUser$ltDomain or hostnamegt$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 httpsservicesapcom~sapidb011000358700000074392009E and follow

the chapters that apply to Planning and Consolidation

33 Configuring the Planning and Consolidation NET Application Servers

Procedure

Modifying machineconfig Files

To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock

occurrences that would cause the application server to ldquosleeprdquo and not process anymore you can

modify the machineconfig file which resides in the WINDOWSMicrosoftNETFramework64

v4030319Config directory

1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to

specify whether to automatically configure settings to achieve optimal performance based on the

machine configuration You can set this attribute to True or False

For more information see httpmsdnmicrosoftcomen-uslibrary7w2sway1aspx

2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the

Planning and Consolidation application) or Machineconfig (for all applications including

Planning and Consolidation) to ensure the validationKey and decryptionKey keys have the same

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

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

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

msdnmicrosoftcomen-uslibraryms998288aspx

3 After Installing Planning and Consolidation Servers

33 Configuring the Planning and Consolidation NET Application Servers

2012-06-13 CUSTOMER 2954

paght000007_webfarmdeploymentconsiderations and httpmsdnmicrosoftcomen-us

libraryms998310aspx

34 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 30]

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

logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page

31]

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

Source [page 32]

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

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

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

see Removing Default Access to the Console [page 32]

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

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

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

Access Control [page 33]

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

341 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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3054 CUSTOMER 2012-06-13

NOTE

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

User Activity and Service Status) does not work as expected

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

Active Log Format field in IIS to W3C Extended Log File Format

342 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 ApplicationHostconfig set the property customLogPluginClsid to the value FF16065B-

DE82-11CF-BC0A-00AA006111E0 Set the logFormat to Custom You can find this in the ltlogFilegt

node in ApplicationHostconfig as shown here

ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0

logFormat=Custom gt

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

appcmd site set sitenameDefault Web Site

logFilecustomLogPluginClsidFF16065B-DE82-11CF-BC0A-00AA006111E0

appcmd site set sitenameDefault Web Site logFilelogFormatCustom

Configuring ODBC Logging Parameters in ApplicationHostconfig

Configure ApplicationHostconfig to contain the database table information as set up in the Microsoft

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

node under ltsystemwebServergt

EXAMPLE

ltlocation path=Default Web Sitegt

ltsystemwebServergt

ltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog

userName=Username password=mypassword gt

ltsystemwebServergt

ltlocationgt

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3154

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

appcmd set config Default Web Site sectionodbcLogging

dataSourceBPC_ManagementDSN commitappHost

appcmd set config Default Web Site sectionodbcLogging tableNameBPCLog

commitappHost

appcmd set config Default Web Site sectionodbcLogging userNameUsername

commitappHost

appcmd set config Default Web Site sectionodbcLogging passwordmypassword

commitappHost

NOTE

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

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

931202 The requirements for using the ODBC logging feature in IIS

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

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

Server 2008 or Windows Server 2008 R2

Proceed as follows

1 Open ODBC Connection Manager

2 On the System DSN tab page add a new DSN

Choose Add

Choose SQL Server as the driver

Choose Finish

3 In the Name and Description fields enter BPC_ManagementDSN

4 In the Server field enter the name of your SQL Server Choose Next

5 Leave the default settings and choose Next

6 Choose the Change the default database to field and enter AppServer Choose Next

7 Leave default settings and choose Next

8 Choose OK

344 Removing Default Access to the Console

NOTE

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

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

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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3254 CUSTOMER 2012-06-13

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

console use the procedure described below

NOTE

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

Management Console or in the Active Directory

1 In the context menu of the servers My Computer icon choose Manage

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

NOTE

Alternatively you can perform analogous steps in Active Directory

3 In the 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

NOTE

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

10 In the Security dialog box click Copy to ensure that the System group retains its privileges

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

12 Choose Authentication in the center pane then disable Windows authentication

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

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

would otherwise have to Planning and Consolidation

345 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 32] Their rights in

Active Directory determine what they can access in the Console

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

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

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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3354

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

privileges For more information see the SAP Library Planning and Consolidation Administrators Guide in

httpservicesapcominstguidesepm-bpc 100 version for the Microsoft platform

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

levels of Console users (read-only users for example) in your environment

To grant or limit access to users or groups you can add or remove the following privileges from the

areas described in this table

Privilege Rights Management Area

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

Performance Monitor Counters Administrators group on application server or domain Power Users group on application server or domain Performance Monitor Users group on application server

Microsoft Analysis Services performance monitoring

Administrators group on application server or domain

Microsoft SQL Server Monitoring (performance counters and statistics)

Administrators group on application server or domain

346 Using Client Certificates

To enable the use of client certificates in Planning and Consolidation you must follow several manual

steps

NOTE

Planning 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 httptechnetmicrosoftcomen-us

librarycc753810aspx

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

technetmicrosoftcomen-uslibrarycc732996(WS10)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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3454 CUSTOMER 2012-06-13

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

authentication) to connect to Planning and Consolidation

2 Enable anonymous authentication

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

2 Select the ManagementConsole directory (ltWebsitegtManagementConsole) to open the

ManagementConsole home page

3 Double-click Authentication and enable Anonymous Authentication

4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way

as in step 3

5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the same

way as in step 3

3 Change the web configuration settings

1 Open the ltPC_MSgtWebsrvrWebBPCwebconfig file

2 Find the text clientCredentialType=Windows

3 Change value of clientCredentialType to None (clientCredentialType=None)

4 Open the PC_MSWebsrvrWebPOASBCwebconfig file Repeat steps 2 and 3

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3554

This page is left blank for documents that are printed on both sides

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

The installation of the Planning and Consolidation Administration Client allows administrators to

build and maintain Planning and Consolidation environments and models and administer security

All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions

add-in for Microsoft Office for more information see the SAP BusinessObjects EPM solutions add-in for

Microsoft Office help

NOTE

You must update the Administration Client to the same version as the server

If your PC is on a different domain than your server you must set the Internet Explorer

Security Zone value of the Planning and Consolidation client to prompt for user name and

password Otherwise the Planning and Consolidation Start Page does not display

41 Installing the Administration Client

Prerequisites

NOTE

For a definitive list of system requirements see the Product Availability Matrix on SAP Service

Marketplace at httpservicesapcompam Search on Planning and Consolidation

The following list describes the minimum software requirements

Microsoft Internet Explorer 70 or 80

Microsoft Office 2007 or 2010

NET Framework 20 or higher (install any required NET Framework Hotfixes by referring to

httpsupportmicrosoftcomkb)

Pentium IV (1 GHz CPU)

512 MB RAM

100 MB of free hard disk space in the My Documents folder

20 MB of free hard disk space for the installed Administration files

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

41 Installing the Administration Client

2012-06-13 CUSTOMER 3754

NOTE

We recommend that you install all of the latest Microsoft Windows hotfixes prior to installing

the Administration client For information about which hotfixes to install see http

updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us

ProcedureThe following procedure describes how to install the Administration Client on to an administratorrsquos

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 AddRemove Programs in the Windows Control Panel

3 Point your browser to the Planning and Consolidation Web at httpltPC_serverportgtsap

bpcweb

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

42 Installing the EPM Add-in

The Planning and Consolidation installation media does not contain the EPM addin setup program

You must download the most recent version of the full setup (EPM Add-inexe) from the Service

Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPC

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

43 Using the Client Auto Update Program

If Planning and Consolidation version 100 or later is installed you can use the Client Auto Update

program to set up the server so that it determines if an upgrade for a connecting Administration client

is necessary

The following describes the use of the auto update program for the Administration Client and the EPM

add-in

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

42 Installing the EPM Add-in

3854 CUSTOMER 2012-06-13

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

To use the Client Auto Update program for the Administration Client proceed as follows

1 From the Server Manager select Options Client Options

2 Select Admin Update

3 If users without administrator rights on their machines use the auto update enter an administrator

ID and password in the Admin ID and Admin password fields respectively The Admin ID should be a

member of the local administrators group on all the computers running the auto update This

setting is not needed if all users have administrator rights on their machines

4 Select Update

For the EPM Add-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 Optionshellip 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 Market Place (SMP) at httpservicesapcom

All support packages and patches are available from the SMP as a zip file

EPMEXCLCLNTltSPLgtzip is for a support package

EPMEXCLCLNTltSPLgtPltPLgtzip 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 ltSP versiongtmsp

EPM Addin Support Package ltSP versiongtxml

For a patch these files are

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

43 Using the Client Auto Update Program

2012-06-13 CUSTOMER 3954

EPM Addin Patch ltpatch numbergtmsp

EPM Addin Patch ltpatch numbergtxml

2 Unzip the zip file and extract the two files to the application server folder (WebsrvrWebBPC

Installation)

3 From the Server Manager select Options Client Options

The system lists the available packages Select the package that you want to use for the autoupdate

You can set a different update policy for each package listed

EXAMPLE

The following table illustrates some possible situations assuming that you have installed the

first full version (V1)

Available maintenance packages

V2-user updateV3-force updateV4-force updateV5-user update

V5-user update V5-user updateV6-auto updateV7-force update

Minimum Required Version

V4 V4 V7

Notification A prompt tells the user to install maintenance package V4 using the Forced Update behavior

If User Update is enabled the prompt informs the user that maintenance package V5 is available

A prompt tells the user to install maintenance package V7 using the Forced Update behavior

New Version V4 V4 or V5 V7

If you change the update policy for any package click Update to complete the change

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

43 Using the Client Auto Update Program

4054 CUSTOMER 2012-06-13

5 Connection Issues

You may experience connection problems with ports the proxy server or programs and settings that

interact with these components If you have any issues related to connection review the following

recommendations and troubleshooting tips

51 Checking for Open Ports

You must ensure that all required ports are open for inboundoutbound 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 431181836 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

NOTE

You can use the following site to scan for the normal ports It allows you to manually enter a port

number to test

httpwwwmyserverorgportsniffasp

You can change the name of a port

52 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 Explorer Tools Internet Options Connections LAN Settings ) or at the server level

Enabling content filtering on the proxy server or firewall may cause connection problems

If external users are having trouble connecting to the server make sure the proxy server connects

using a fully qualified domain name Fully qualified domain names typically resolve both internal

and external IP addresses

Each secure Planning and Consolidation server name must be identified on the proxy server

Proxy servers may or may not require authentication which could conflict with Planning and

Consolidation authentication Do not use authentication on the proxy server The system

5 Connection Issues

51 Checking for Open Ports

2012-06-13 CUSTOMER 4154

synchronizes the user name and password on the remote server with the local user name and

password

NOTE

For more information about setting up an ISA proxy server contact SAP Support to request a

copy of Setting up ISA Proxy Server White Paper

Internet Explorer Settings 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

5 Connection Issues

52 Proxy Server and Firewall Issues

4254 CUSTOMER 2012-06-13

6 Installing Planning and Consolidation with Two Active Directory Domains

To set up a Planning and Consolidation 10 application server in a hosted environment and use your

own domain users follow this procedure In general you install Planning and Consolidation on the

host domain use the host domain account and assign it to the Planning and Consolidation users

SysAdmin Admin and Users Then you accept one way trust (the host domain trusts your domain)

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

6 Installing Planning and Consolidation with Two Active Directory Domains

2012-06-13 CUSTOMER 4354

This page is left blank for documents that are printed on both sides

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

This section describes best practices and instructions for installing Planning and Consolidation in a

Terminal Services or Citrix Server deployment

71 Terminal Services Home Directories

We recommend using Terminal Server home directories rather than using the userrsquos 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

72 System Requirements

The Citrix server should be one of the following systems

XenApp 5 Enterprise

XenApp 5 Platinum

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

73 Installing Planning and Consolidation

Prerequisites

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

Procedure

The following steps outline how to install the Planning and Consolidation clients in a Terminal Services

(TS) or Citrix Server deployment

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

71 Terminal Services Home Directories

2012-06-13 CUSTOMER 4554

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 userinstall

4 Open a browser and connect to the URL httpltPC_serverportgtsapbpcweb

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 userexecute 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 Iexploreexe http(s)

ltServerNamegt-NetBIOS or FQDNsapbpcweb

To publish Planning and Consolidation Administration CProgram FilesPC_MS

BPCAdminMainexe

74 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 userrsquos desktop) must be moved to the All UsersDesktop folder

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

74 Creating a Shortcut to the Launch Page

4654 CUSTOMER 2012-06-13

8 Installing SSIS Custom Tasks

This section provides background information and instructions for installing SQL Server Integration

Services (SSIS) for SQL Server 2008 and SQL Server 2012

The Planning and Consolidation Data Manager component supports and uses SSIS Since SQL Server

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

81 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 Filelistxml 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

OSoftSetupexe ‒ 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 or OSoftSSIS2012_Client on the client machine followed by the SQL Server

version If you want to use SQL 2008 Tasks under the SQL 2012 environment you must install

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

You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package by extracting

OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPC

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 or

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4754

OSoftSSIS2012_Client for creating a COM+ application For more information see Before You Modify

the SSIS Packages [page 50] and Setup of a COM+ Application on the Application Server [page 51]

Bin folder

This folder contains the following components

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCCachedll Planning and Consolidation Cache file

BPCDataFlowPackagedll or BPCDataFlowPackage2012dll

BPCDMdll

BPCDMTaskMaindll COM+ component

BPCFilePreviewdll

BPCGacUtil_20exe System File

BPCGacUtil_40exe System File

BPCImpersonatordll Planning and Consolidation Impersonator

BPCLogicdll

BPCScriptdll

BPCServerZipdll

BPCServiceResdll

BPCTransferMembersdll

BPCWriteBackdll

InteropDTSdll

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

4854 CUSTOMER 2012-06-13

Name Remark

OSoftAdminServerdll

OSoftAuditdll

OSoftComLibServerdll

OSoftCommonResQrydll

OSoftConfigurationdll

OSoftCustomXMLSvrdll

OSoftDatabaseADMINdll

OSoftDatabaseSYSADMINdll

OSoftDatabaseSYSADMINDMdll

OSoftDatabaseUSERdll

OSoftDMDTSXExecutedll or OSoftDMDTSXExecute2012dll

OSoftDMTaskFormdll

OSoftDMTaskMaindll

OSoftDMToolsdll

OSoftFileManagedll

OSoftLoggingdll

OSoftLogWriterdll

OSoftMetaDatadll

OSoftSQEdll

OSoftSystemConfigdll

OutlookSoftconfig Configuration file to connect DB server

XceedCompressiondll XceedZip file

XceedCompressionFormatsdll XceedZip file

XceedFileSystemdll XceedZip file

XceedZipdll XceedZip file

Config folder

This folder has FileListxml 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 FileListxml 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

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4954

OSoftSetupexe

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

NOTE

If you installed the OSoftSSIS2008_Client or OSoftSSIS2012_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

Resources Folder

This folder contains the BPCServicesdll and BPCServiceUIdll files which contain resource text

Only English resources are included for the SSIS custom tasks

82 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

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008 and 2012 respectively

8 Installing SSIS Custom Tasks

82 Before You Modify the SSIS Packages

5054 CUSTOMER 2012-06-13

Name Remark

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012 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

lthellipgtOSoftSSIS2008_Clientbin or lthellipgtOSoftSSIS2012_Clientbin

On the Planning and Consolidation application server

ltdrivegtWebsrvrbin

2 Paste these files into the folder 100DTSTasks for SQL Server 2008 or into 110DTSTasks for

SQL Server 2012 For example if you install your SQL 2008 server or R2 on CProgram Files

Microsoft SQL Server paste all files into the CProgram Files (x86)Microsoft SQL Server

100DTSTasks folder

In Integration Services set the property Run64BitRunTime to True

83 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 or OSoftSSIS2012_Client on the

application server

8 Installing SSIS Custom Tasks

83 Setup of a COM+ Application on the Application Server

2012-06-13 CUSTOMER 5154

Typographic Conventions

Example Description

ltgt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example Enter your ltUser Namegt

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 httpwwwsapcom

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

5254 CUSTOMER 2012-06-13

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

  • SAP BusinessObjects Planning and Consolidation 100
    • Table of Contents
    • 1 Introduction
      • 11 SAP Notes for the Installation
      • 12 Naming Conventions
        • 2 Installing Planning and Consolidation Servers
          • 21 Basic Steps
          • 22 Prerequisites
          • 23 Before Starting the Planning and Consolidation Server Installation
          • 24 Logging on to Servers
          • 25 Service-level Accounts
          • 26 Standard and Advanced Settings
          • 27 Installing the Prerequisites
            • 271 Installing the Prerequisites ndash Basic Steps
            • 272 Installing the Operating System
            • 273 Installing the SQL Server
            • 274 Installing Analysis Services
            • 275 Installing the Anti-Cross Site Scripting Library
              • 28 Installing on a Single Server
              • 29 Installing the Server in a Multiserver Configuration
                • 3 After Installing Planning and Consolidation Servers
                  • 31 Post-Installation Steps
                  • 32 Connecting to Solution Manager Diagnostics
                  • 33 Configuring the Planning and Consolidation NET Application Servers
                  • 34 Post-Installation Optional Configuration Steps
                    • 341 Enabling the Management Console
                    • 342 Setting Up ODBC Logging in IIS for the Default Web Site
                    • 343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2
                    • 344 Removing Default Access to the Console
                    • 345 Management Console Access Control
                    • 346 Using Client Certificates
                        • 4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office
                          • 41 Installing the Administration Client
                          • 42 Installing the EPM Add-in
                          • 43 Using the Client Auto Update Program
                            • 5 Connection Issues
                              • 51 Checking for Open Ports
                              • 52 Proxy Server and Firewall Issues
                                • 6 Installing Planning and Consolidation with Two Active Directory Domains
                                • 7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
                                  • 71 Terminal Services Home Directories
                                  • 72 System Requirements
                                  • 73 Installing Planning and Consolidation
                                  • 74 Creating a Shortcut to the Launch Page
                                    • 8 Installing SSIS Custom Tasks
                                      • 81 Composition of SSIS Custom Task Installation
                                      • 82 Before You Modify the SSIS Packages
                                      • 83 Setup of a COM+ Application on the Application Server
                                          • Copyright and trademarks
Page 4: Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

Table of Contents

Chapter 1 Introduction 7

11 SAP Notes for the Installation 7

12 Naming Conventions 9

Chapter 2 Installing Planning and Consolidation Servers 11

21 Basic Steps 11

22 Prerequisites 11

23 Before Starting the Planning and Consolidation Server

Installation 13

24 Logging on to Servers 14

25 Service-level Accounts 15

26 Standard and Advanced Settings 16

27 Installing the Prerequisites 17

271 Installing the Prerequisites ‒ Basic Steps 17

272 Installing the Operating System 19

273 Installing the SQL Server 19

274 Installing Analysis Services 23

275 Installing the Anti-Cross Site Scripting Library 24

28 Installing on a Single Server 24

29 Installing the Server in a Multiserver Configuration 26

Chapter 3 After Installing Planning and Consolidation Servers 27

31 Post-Installation Steps 27

32 Connecting to Solution Manager Diagnostics 28

33 Configuring the Planning and Consolidation NET Application

Servers 29

34 Post-Installation Optional Configuration Steps 30

341 Enabling the Management Console 30

342 Setting Up ODBC Logging in IIS for the Default Web Site 31

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

2008 R2 32

454 CUSTOMER 2012-06-13

344 Removing Default Access to the Console 32

345 Management Console Access Control 33

346 Using Client Certificates 34

Chapter 4 Installing Planning and Consolidation Administration Client and the

SAP BusinessObjects EPM solutions Add-in for Microsoft

Office 37

41 Installing the Administration Client 37

42 Installing the EPM Add-in 38

43 Using the Client Auto Update Program 38

Chapter 5 Connection Issues 41

51 Checking for Open Ports 41

52 Proxy Server and Firewall Issues 41

Chapter 6 Installing Planning and Consolidation with Two Active Directory

Domains 43

Chapter 7 Installing Planning and Consolidation in a Terminal Services or Citrix

Server Deployment 45

71 Terminal Services Home Directories 45

72 System Requirements 45

73 Installing Planning and Consolidation 45

74 Creating a Shortcut to the Launch Page 46

Chapter 8 Installing SSIS Custom Tasks 47

81 Composition of SSIS Custom Task Installation 47

82 Before You Modify the SSIS Packages 50

83 Setup of a COM+ Application on the Application Server 51

2012-06-13 CUSTOMER 554

This page is left blank for documents that are printed on both sides

1 Introduction

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

Administrators who perform Planning and Consolidation server and Administration client

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

and the server and client software

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

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

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

servicesapcominstguidesEPM-BPC Planning and Consolidation 100 version for the Microsoft platform

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

BusinessObjects EPM solutions add-in for Microsoft Office help

New Installation Program Features in 100

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

11 SAP Notes for the Installation

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

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

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

Marketplace at the Internet address httpservicesapcomnotes

1 Introduction

11 SAP Notes for the Installation

2012-06-13 CUSTOMER 754

SAP Note Number Title Comments

1584890 Documentation Addendum Contains information that does not appear in the application help of Planning and Consolidation 100 version for the Micrososft platform

1733053 SAP Planning and Consolidation 100 SP08 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP08This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1689792 SAP Planning and Consolidation 100 SP07 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP07This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1665656 SAP Planning and Consolidation 100 SP06 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP06This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1643037 SAP Planning and Consolidation 100 SP05 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP05This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1620464 SAP Planning and Consolidation 100 SP04 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP04This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1601213 SAP Planning and Consolidation 100 SP03 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP03This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1591848 SAP Planning and Consolidation 100 SP02 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP02This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1 Introduction

11 SAP Notes for the Installation

854 CUSTOMER 2012-06-13

SAP Note Number Title Comments

1573539 SAP Planning and Consolidation 100 SP01 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP01This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

12 Naming Conventions

In this document the following naming conventions apply

Variable Description

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

ltdrivegt The drive where SAP Planning and Consolidation is installedThe default for this is CPC_MS

1 Introduction

12 Naming Conventions

2012-06-13 CUSTOMER 954

This page is left blank for documents that are printed on both sides

2 Installing Planning and Consolidation Servers

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

and what to do before during and after the server installation

21 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 at httpservicesapcominstguidesepm-bpc 100 version for the Microsoft platform

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

including installing all prerequisites

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

Consolidation on a Single Server [page 24]

NOTE

You must install both Planning and Consolidation 100 as well as the most recent Planning

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

httpservicesapcomswdc Software Downloads Support Packages and Patches A - Z Index

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

Versions SAP CPM BPC 100 M Windows Server on x64 64bit

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

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

22 Prerequisites

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

Consolidation server and the minimum versions required

NOTE

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

Availability Matrix on SAP Service Marketplace at httpservicesapcompam Search on

Planning and Consolidation

2 Installing Planning and Consolidation Servers

21 Basic Steps

2012-06-13 CUSTOMER 1154

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 or

Data Center with or without Hyper-V

NOTE

The operating system must be configured with NTFS

Relational Database Microsoft SQL Server 2008 Enterprise Edition Microsoft SQL Server 2008 R2 (Gemini) Enterprise Edition Microsoft SQL Server 2012 Enterprise Edition

OLAP Database Microsoft SQL Server 2008 Enterprise Edition ‒ Analysis Server Microsoft SQL Server 2008 R2 Enterprise Edition ‒ Analysis Server Microsoft SQL Server 2012 Enterprise Edition ‒ Analysis Server

Data Integration Microsoft SQL Server 2008 Enterprise Edition ‒ SQL Service Integration Services

Microsoft SQL Server 2008 R2 Enterprise Edition ‒ SQL Service Integration Services

Microsoft SQL Server 2012 Enterprise Edition ‒ SQL Service Integration Services

Other Requirements MSXML 40 SP2 or later ADOMDNET

ADOMDNET 100 when running SQL Server 2008 or 2008 R2 ADOMDNET 110 when running SQL Server 2012

SQL Server software components NET 40 IIS 75 or IIS 70

(Included in your Operating System IIS 75 is required for Windows 2008 R2 editions)

Anti-Cross Site Scripting Library 42This component must be downloaded before installing the server The server installation program asks for the path of each file and copies the files into the appropriate Planning and Consolidation path

Microsoft Visual C++ 2005 Runtime Libraries SP1 Microsoft Access Database Engine 2010 64bit VMWare ESX 3x or ESX 40

(Required only if a landscape deployment strategy using virtualization technologies is planned)

NOTE

MSXML 40 SP2 ADOMDNET 100 and Microsoft Visual C++ 2005 Runtime Libraries SP1 are included with the installation program but not installed automatically

RECOMMENDATION

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

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

2 Installing Planning and Consolidation Servers

22 Prerequisites

1254 CUSTOMER 2012-06-13

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

1429246 which also contains download information

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

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

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

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

23 Before Starting the Planning and Consolidation Server Installation

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

installation

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

information see Installing the Prerequisites [page 17]

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

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

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

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

Settings [page 16]

Make sure all required server ports are open and that there is communication between the physical

servers on which you are going to install the server types See Checking for Open Ports [page 41]

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

See Service-Level Accounts [page 15]

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

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

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

with the installation

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

reinstall them

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

turn off Script Blocking

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

install Planning and Consolidation 100 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 fsntfsV

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

2 Installing Planning and Consolidation Servers

23 Before Starting the Planning and Consolidation Server Installation

2012-06-13 CUSTOMER 1354

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

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

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

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

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

Consolidation We recommend that you use static IP addresses

IIS must be enabled

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

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

the following

1 Copy the EnvironmentShell database file ServerEnvironmentShelldb10 from the

Planning and Consolidation installation program to any folder on the SQL server (for example

cEnvironmentShelldb10)

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

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

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

24 Logging on to Servers

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

components

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

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

Administrator group on the local server

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

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

You can ignore these messages

NOTE

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

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

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

the SAP Planning and Consolidation Operations Guide in httpservicesapcominstguidesepm-bpc

100 for the Microsoft Platform SBOP Plan amp Consol 100 MS Administrators Guide

2 Installing Planning and Consolidation Servers

24 Logging on to Servers

1454 CUSTOMER 2012-06-13

25 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

PrerequisitesPlanning and Consolidation 100 has the following Windows services

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

and avoid deadlocks

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

and global caches

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

management system

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

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

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

with the error message

Could not start the BPC SendGovernor service

The reason for this is that the Admin account is not registered as a service

When installing a service to run under a domain user account the account must have the right to

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

and must be granted in the Local Security Policy

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

permission perform the following actions

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

2 Expand Local Policies and then click User Rights Assignment

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

4 Add the user to the policy and click OK

5 Close the Local Security Settings MMC snap-in

For more details see How to Troubleshoot Service Startup Permissions http

supportmicrosoftcomkb259733

FeaturesDuring the installation enter user IDs and passwords for the following user types

System Admin ID

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

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

2 Installing Planning and Consolidation Servers

25 Service-level Accounts

2012-06-13 CUSTOMER 1554

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

26 Standard and Advanced Settings

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

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

NOTE

When defining server names the name refers to the NetBIOS name IP address and fully qualified

domain names (FQDN)

Standard Settings

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

setting

Server Option Value Description

SQL Database server name The name of the SQL DB server

OLAP server name The name of the OLAP server

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

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

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

Server Option Value Description

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

2 Installing Planning and Consolidation Servers

26 Standard and Advanced Settings

1654 CUSTOMER 2012-06-13

Server Option Value Description

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

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

Provider The only available value is SQL

Local path for EnvironmentShell 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 CPC_MSData

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 changesSee the Kerberos authentication settings section in the SAP Library Server Manager Guide on httpservicesapcominstguidesEPM-BPC

100 for the Microsoft Platform

Scheduler Server Name The name of the server used for scheduling usually the application server for example GMPV50072862B If you have multiple application servers select the appropriate one

NOTE

If the primary server stops working you must manually configure your application server database to froward requests to another application server

27 Installing the Prerequisites

271 Installing the Prerequisites ndash Basic Steps

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

software the operating system IIS SQL server analysis services ADOMDNET and MSXML This

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

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 1754

Prerequisites [page 11] and the Product Availability Matrix on the SAP Service Marketplace at http

servicesapcompam Search on Planning and Consolidation

NOTE

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

procedure

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

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

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

Active Directory (AD)

We recommend not installing Microsoft Office on the application server

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

(UMCexe) on the Planning and Consolidation CD in a folder called UMC_100_INSTALLER When

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

1 Choose a language for the UMC install wizard to use

2 Check that the prerequisite check status is Succeeded and click Next

3 When you are ready to install the UMC click Next on the welcome screen

4 Click I accept the License Agreement and then Next

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

6 Select the languages that you wish to install

7 Select the features that you want to install (POAFHelper dotnet is mandatory for Planning

and Consolidation)

8 On Start Installation click Next to complete the installation

2 Install the required operating system on the single-server computer or on each physical server for

a multiserver configuration See Installing the Operating System [page 19]

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

wwwmicrosoftcom

4 From your operating systems media install IIS

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

Installing SQL Server [page 19]

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

packs and hot fixes See Installing Analysis Services [page 23]

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

1854 CUSTOMER 2012-06-13

7 On your application server install ADOMDNET The Planning and Consolidation zip file contains

the ADOMDNET installation package in the following locations

For SQL Server 2008 mdash BPC SetupServerSQLSERVER2008_ASADOMD10_x64msi

For SQL Server 2012 mdash BPC SetupServerSQLSERVER2012_ASADOMD11_x64msi

8 On your application server install MSXML 40 Service Pack 2 or later

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

the following location BPC SetupServermsxmlmsi

9 On your application server install Microsoft Visual C++ 2005 Runtime Libraries SP1

The Microsoft Visual C++ 2005 SP1 installation package is contained in the Planning and

Consolidation zip file at the following location BPC SetupServervcredist_x64exe

NOTE

The version of vcredist_x64exe in BPC SetupServer has been updated to 8061000 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 httpwwwmicrosoftcomdownloadsen

detailsaspxFamilyID=C06B8369-60DD-4B64-A44B-84B371EDE16Dampltdisplaylanggt=en

272 Installing the Operating System

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

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

Marketplace at httpservicesapcompam Search on Planning and Consolidation

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

NOTE

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

languages such as Hebrew

ProcedureIf you are installing IIS 70 or 75 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

273 Installing the SQL Server

PrerequisitesDuring the installation procedure you have the opportunity to specify the location of the

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

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 1954

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 CEnvironmentShelldb10) 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 a 2008 2008 R2 and 2012 SQL Server

SQL Server Considerations

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

System (Windows Server) then enable IIS and ASPNET and install any Windows Server service

packs

IIS and NET Framework 40 are required on your application server

NOTE

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

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

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

nondefault instance of SQL Server

General Installation Steps

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

terms

2 Choose Install to install the SQL support files

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

Options section below then choose Next

4 Review disc space requirements then choose Next

5 In Server Configuration Perform the following actions

1 In the Service Accounts tab enter a Planning and Consolidation sysadmin account for the SQL

Server Database Engine and the SQL Server Analysis services This is required so that the Planning

and Consolidation sysadmin can create and process the Planning and Consolidation database

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

account This account is also required during Backup Environment and Restore Environment in the

Server Manager

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

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

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

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

application server

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2054 CUSTOMER 2012-06-13

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

Consolidation sysadmin for this service account

2 In the Collation tab set the collation settings to SQL_Latin1_General_CP1_CI_AS

Choose Next

6 Set Database Engine Configuration options then choose Next

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

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

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

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

you can install the SQL Server in Windows-only mode

7 Accept the Analysis Services Configuration default options and the remaining default options of the

installation program

8 Choose Install to begin the installation with the options you have set

SQL Server Component 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

Server Component What to Install

SQL Server Database Engine Services

SSAS Server Analysis Services

Application Server The following Shared Features Client Tools Connectivity Integration Services Client Tools SDK

Custom Settings for the SQL Server

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

SQL Server 2008 R2 and SQL Server 2012

Process Dimension

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

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

dimensions and cubes in parallel

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 2154

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

NOTE

Setting 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 tblFactWBltappgt table

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 Microsoftreg SQL Servertrade

20052008 which you can download from wwwmicrosoftcom (search on ldquoTable Partitioningrdquo to find

all relevant articles)

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

From SQL Server Configuration Manager confirm that the SQL Server Browser service is

running The browser service is required for Planning and Consolidation

From SQL Server Configuration Manager do the following

1 Select Protocols for ltInstanceNamegt then double-click TCPIP from the right side of the window

2 When prompted for the TCPIP Properties select IP Addresses You see two IPs that indicate the

localhost and external network interface machine

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2254 CUSTOMER 2012-06-13

3 If you want to use IP1 which indicates Server IP set Enabled to Yes and specify the TCP Port as

desired

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

RECOMMENDATION

We do not recommend using dynamic ports

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

port 1433) However for the named instance the port on which the SQL server listens is

random and dynamically selected when the named instance of the SQL server starts This

recommendation prevents any conflict problems

From the SQL Server Configuration Manager specify the client protocol options for the application

server

1 Select Client Protocols from the SQL Native Client Configuration folder

2 From the right side of the window double-click TCPIP The TCPIP 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

NOTE

We 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

274 Installing Analysis Services

ProcedureAfter you install SQL Server and its required service packs and hotfixes you must install SQL Server

Analysis Services and its required service packs and hotfixes

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 2354

NOTE

If you have migrated your Analysis Services repository to the SQL Server back up the database

that contains the repository before installing this release

To install Analysis Services for SQL Server 2008 SQL Server 2008 R2 or SQL Server 2012 follow the steps

and guidelines in httptechnetmicrosoftcomen-uslibraryms143219aspx

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 httpwwwmicrosoftcomdownloads

detailsaspxFamilyID=3be0488d-e7aa-4078-a050- ae39912d2e43ampdisplaylang=en

275 Installing the Anti-Cross Site Scripting Library

Procedure

Before installing Planning and Consolidation servers you must download the Anti-Cross Site Scripting

Library (version 42 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 AntiXSSLibraryDLL from the Microsoft Web

site at httpwwwmicrosoftcomdownloadendetailsaspxid=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 AntiXssLibrarydll

28 Installing on a Single Server

When you install all Planning and Consolidation server components on a single server you should

consider the following issues

Make sure the server has a minimum of 800 MB of hard disk space

Additional environment installations require more free disk space which is a minimum of two

times the uncompressed size of the environment files

When you install Planning and Consolidation on a single-server the system adds the following server

components

SQL Server

SQL Server Analysis Services (SSAS)

Application Server

FileShare server

Procedure

To install Planning and Consolidation on a single server take the following steps

1 Exit all Windows programs

2 Installing Planning and Consolidation Servers

28 Installing on a Single Server

2454 CUSTOMER 2012-06-13

2 Log on to the server with a local server user ID or domain user ID For more information see Logging

on to servers [page 14]

3 Make sure all prerequisite software is installed on the server For more information see Installing

the Prerequisites [page 17]

4 Obtain SAP Planning and Consolidation from the Downloads SAP Installations amp Upgrades area of

SAP Service Marketplace then extract the files and run StartUpexe

5 From the Server Install screen select Install the Planning and Consolidation server

6 From the Welcome screen choose Next

7 From the License Agreement page choose I accept the terms of the license agreement then choose Next

8 From the Installation Method page accept the default Single machine enter a system ID for the system

landscape directory (SLD) and choose Next

NOTE

Entering a system ID of the SLD is only required if you have a SAP Solution Manager license

If you do not have a SAP Solution Manager license you can leave this field empty

9 From the Authentication Method page choose the desired authentication method and choose Next

10 If you have chosen SAP BusinessObjects User Management System in the previous screen on the CMS

Authentication page enter the information required to log on to CMS as an administrator

The following information is required

Field Description

System name CMS system name (server nameport number) for example CMSServer6400

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

11 After entering the CMS administrator authentication details choose Next

12 From the Service type accounts page enter service-level account user IDs and passwords See Service-

Level Accounts [page 15]

13 After defining the IDs and passwords choose Next

14 From the Server Information page (see Standard and Advanced Settings [page 16]) do one of the following

Review the standard settings and choose Next

To set advanced settings choose the Advanced Settings button Enter the desired information

and choose Next

2 Installing Planning and Consolidation Servers

28 Installing on a Single Server

2012-06-13 CUSTOMER 2554

15 Specify the location and name of AntiXssLibrarydll See Installing the Anti-Cross Site Scripting Library [page

24]

Choose Next

16 Select destination folders for Programs and Data The Data files include Webfolders and FileDB

(published reports) and should be installed on a separate drive in a production environment This

recommendation reduces the hard disk IO time and helps to speed up SQL commands

Accept the defaults or make your selections then choose Next

17 Select the default values for the Web client The values are used to determine the default language

and region for the Web client when you connect to it You can change the values in the Planning

and Consolidation Server Manager

18 The installation process takes a few moments When it is complete choose Exit

19 A prompt is displayed to restart your computer Select OK to restart

20 Perform the steps in After Installing Planning and Consolidation Servers [page 27]

29 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 24]) with the following

exceptions

On the Installation Method page do not accept the default instead choose Network Load Balancing

environment With this option there is an additional choice to Include sample environment (required on only

one of the application servers) This is because when you install the application server it connects to the

database server and creates the sample environment (EnvironmentShell) Installing the sample

environment is required on only one application server and you may choose which one

In the Virtual Name field enter the virtual IP address virtual name in the default properties

2 Installing Planning and Consolidation Servers

29 Installing the Server in a Multiserver Configuration

2654 CUSTOMER 2012-06-13

3 After Installing Planning and Consolidation Servers

31 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 28]

2 Configure the Planning and Consolidation NET and application server to ensure that it and its

related services function properly and reliably For more information see Configuring the Planning and

Consolidation NET Application Server [page 29]

3 Optional configuration steps [page 30]

1 To ensure proper functioning of the Management Console create an SQL user and modify

the System DSN and IIS to reflect those user credentials See Enabling Management Console [page

30]

2 Configure custom ODBC logging for the default Web site For details of how to configure

custom logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web

Site [page 31]

3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC

Data Source [page 32]

4 Modify the default access rights to the Management Console By default users in Active

Directory can access the Management Console with whatever rights they have been granted

on the server For information about removing default access and creating a group that can

access the console see Removing Default Access to the Console [page 32]

5 Add authorized users or groups to the group that can access the Management Console We

recommend that you only grant Management Console access to system administrators

Planning and Consolidation users should not have any access For more information see

Management Console Access Control [page 33]

6 Configure the use of client certificates for authentication See Using Client Certificates [page

34]

4 Take the following steps to set up security

If you are defining security and application structure continue with step 5

3 After Installing Planning and Consolidation Servers

31 Post-Installation Steps

2012-06-13 CUSTOMER 2754

If you want to designate someone other than the system administrator to manage security

and application structure log on to EnvironmentShell designate a user as a Primary

Administrator

This user must have Administration ‒ Environment and Security ‒ Define User task rights

so that he or she can add and delete environments and define user security

The Primary Administrator can continue with the next step (5)

5 From the machine on which you administer Planning and Consolidation install the

Administration client See Installing the Administration Client [page 37]

6 Start Planning and Consolidation Administration from the launch page

7 Select Connection Wizard and log on to EnvironmentShell

8 Create a new environment using EnvironmentShell as the source

9 Log on to the newly created environment and set up users teams and task profiles (You must

set up task profiles since there is no access to Planning and Consolidation tasks)

10 Set up your data access profiles and add users (or teams) to one or more data access profiles (You

must complete this step since there is no access to dimensions or members)

NOTE

To allow users to request and query large amounts of data you can edit the metabasexml file located

at CWindowssystem32inetsrv Set the following parameters to the stated values

ASPBUFFERINGLIMIT = 10485760

MAXREQUESTENTITYALLOWED = 10485760

32 Connecting to Solution Manager Diagnostics

NOTE

You only need to perform the steps in this section if you have a SAP Solution Manager licence

The diagnostics functions in SAP Solution Manager allow identification analysis and resolution of

problems This procedure provides the steps required to connect Planning and Consolidation to

Solution Manager Diagnostics

Procedure

1 Install the Diagnostics Agent according to SAP Note 1234387 on all servers where application servers

are installed

NOTE

Installation files for Diagnostics Agent are available on Service Marketplace by navigating to

Support Packages and Patches mdash Entry by Application Group SAP Technology Components SAP

SOLUTION MANAGER SAP SOLUTION MANAGER 70 EHP 1 Entry by Component Agents

for managed systems DIAGNOSTICS AGENT 711

3 After Installing Planning and Consolidation Servers

32 Connecting to Solution Manager Diagnostics

2854 CUSTOMER 2012-06-13

Download the installation file based on the 64-bit Windows Server system landscape

2 To access the DBA Cockpit you must create a user account with sufficient rights on all Windows

Servers where Microsoft SQL Server is installed Do the following

1 Start Computer Management then select Action New User

2 Create a new user

3 Right-click on the user then choose Properties On the Member Of tab select Add

4 Add the group SQLServerltReleasegtSQLAgentUser$ltDomain or hostnamegt$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 httpsservicesapcom~sapidb011000358700000074392009E and follow

the chapters that apply to Planning and Consolidation

33 Configuring the Planning and Consolidation NET Application Servers

Procedure

Modifying machineconfig Files

To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock

occurrences that would cause the application server to ldquosleeprdquo and not process anymore you can

modify the machineconfig file which resides in the WINDOWSMicrosoftNETFramework64

v4030319Config directory

1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to

specify whether to automatically configure settings to achieve optimal performance based on the

machine configuration You can set this attribute to True or False

For more information see httpmsdnmicrosoftcomen-uslibrary7w2sway1aspx

2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the

Planning and Consolidation application) or Machineconfig (for all applications including

Planning and Consolidation) to ensure the validationKey and decryptionKey keys have the same

value on all application servers This way when the authentication cookie is checked the

authentication ticket used on one server can still be valid on another server

For more information and sample Visual Basic code for generating random key values see http

msdnmicrosoftcomen-uslibraryms998288aspx

3 After Installing Planning and Consolidation Servers

33 Configuring the Planning and Consolidation NET Application Servers

2012-06-13 CUSTOMER 2954

paght000007_webfarmdeploymentconsiderations and httpmsdnmicrosoftcomen-us

libraryms998310aspx

34 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 30]

2 Configure custom ODBC logging for the default Web site For details of how to configure custom

logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page

31]

3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC Data

Source [page 32]

4 Modify the default access rights to the Management Console By default users in Active Directory

can access the Management Console with whatever rights they have been granted on the server

For information about removing default access and creating a group that can access the console

see Removing Default Access to the Console [page 32]

5 Add authorized users or groups to the group that can access the Management Console We

recommend that you only grant Management Console access to system administrators Planning

and Consolidation users should not have any access For more information see Management Console

Access Control [page 33]

6 Configure the use of client certificates for authentication See Using Client Certificates [page 34]

341 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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3054 CUSTOMER 2012-06-13

NOTE

Without these updates the Management Console does work but some functionality (specifically

User Activity and Service Status) does not work as expected

Should you need to uninstall Planning and Consolidation we recommend that you reset the

Active Log Format field in IIS to W3C Extended Log File Format

342 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 ApplicationHostconfig set the property customLogPluginClsid to the value FF16065B-

DE82-11CF-BC0A-00AA006111E0 Set the logFormat to Custom You can find this in the ltlogFilegt

node in ApplicationHostconfig as shown here

ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0

logFormat=Custom gt

Use the following AppCmds to configure IIS to use ODBC logging for the default Web site

appcmd site set sitenameDefault Web Site

logFilecustomLogPluginClsidFF16065B-DE82-11CF-BC0A-00AA006111E0

appcmd site set sitenameDefault Web Site logFilelogFormatCustom

Configuring ODBC Logging Parameters in ApplicationHostconfig

Configure ApplicationHostconfig to contain the database table information as set up in the Microsoft

Support article specified in the Prerequisites section Configure these settings in the ltodbcLogginggt

node under ltsystemwebServergt

EXAMPLE

ltlocation path=Default Web Sitegt

ltsystemwebServergt

ltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog

userName=Username password=mypassword gt

ltsystemwebServergt

ltlocationgt

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3154

Use the following AppCmds to configure these attributes for the default Web site

appcmd set config Default Web Site sectionodbcLogging

dataSourceBPC_ManagementDSN commitappHost

appcmd set config Default Web Site sectionodbcLogging tableNameBPCLog

commitappHost

appcmd set config Default Web Site sectionodbcLogging userNameUsername

commitappHost

appcmd set config Default Web Site sectionodbcLogging passwordmypassword

commitappHost

NOTE

You cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must

use the SQL Server ODBC driver For more information see the Microsoft Knowledge Base article

931202 The requirements for using the ODBC logging feature in IIS

343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2

ProcedureThis procedure describes how to set up an ODBC data source for the Management Console in Windows

Server 2008 or Windows Server 2008 R2

Proceed as follows

1 Open ODBC Connection Manager

2 On the System DSN tab page add a new DSN

Choose Add

Choose SQL Server as the driver

Choose Finish

3 In the Name and Description fields enter BPC_ManagementDSN

4 In the Server field enter the name of your SQL Server Choose Next

5 Leave the default settings and choose Next

6 Choose the Change the default database to field and enter AppServer Choose Next

7 Leave default settings and choose Next

8 Choose OK

344 Removing Default Access to the Console

NOTE

If you have chosen SAP BusinessObjects User Management System in the installation screen you

do not need to remove or configure access because the Management Console service always runs

with the System Admin ID account which is a member of the Administrators group

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3254 CUSTOMER 2012-06-13

ProcedureTo remove default access to the Management Console and create a group that does have access to the

console use the procedure described below

NOTE

Create your Management Console administrative group either on the server that hosts the

Management Console or in the Active Directory

1 In the context menu of the servers My Computer icon choose Manage

2 In the Computer Management dialog box choose Local Users and Groups Groups

NOTE

Alternatively you can perform analogous steps in Active Directory

3 In the 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

NOTE

This step is a necessary precursor to the completion of this procedure

10 In the Security dialog box click Copy to ensure that the System group retains its privileges

11 Remove access to the Management Console from all groups that should not have it

12 Choose Authentication in the center pane then disable Windows authentication

ResultUsers who have not been granted access to the Management Console can still open the Management

Console Web page but it contains no data or menu options This does not affect the access that a user

would otherwise have to Planning and Consolidation

345 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 32] Their rights in

Active Directory determine what they can access in the Console

By default any member of the Administrators Active Directory group on the application server or

domain has full access to all of the features of the Console except the Planning and Consolidation

logging area Access to Planning and Consolidation logging is controlled within the Planning and

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3354

Consolidation Administration Client task security The user must be granted View system logs task

privileges For more information see the SAP Library Planning and Consolidation Administrators Guide in

httpservicesapcominstguidesepm-bpc 100 version for the Microsoft platform

Your IT policy determines whether you grant access by group or user You may wish to create several

levels of Console users (read-only users for example) in your environment

To grant or limit access to users or groups you can add or remove the following privileges from the

areas described in this table

Privilege Rights Management Area

Task Manager and Kill Process Administrators group on application server or domain

Performance Monitor Counters Administrators group on application server or domain Power Users group on application server or domain Performance Monitor Users group on application server

Microsoft Analysis Services performance monitoring

Administrators group on application server or domain

Microsoft SQL Server Monitoring (performance counters and statistics)

Administrators group on application server or domain

346 Using Client Certificates

To enable the use of client certificates in Planning and Consolidation you must follow several manual

steps

NOTE

Planning 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 httptechnetmicrosoftcomen-us

librarycc753810aspx

For more information about configuring the client certificate mapping authentication see http

technetmicrosoftcomen-uslibrarycc732996(WS10)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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3454 CUSTOMER 2012-06-13

This option allows you to use a client certificate or username and password (Basic

authentication) to connect to Planning and Consolidation

2 Enable anonymous authentication

1 In the IIS Manager expand the node of the Planning and Consolidation web site

2 Select the ManagementConsole directory (ltWebsitegtManagementConsole) to open the

ManagementConsole home page

3 Double-click Authentication and enable Anonymous Authentication

4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way

as in step 3

5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the same

way as in step 3

3 Change the web configuration settings

1 Open the ltPC_MSgtWebsrvrWebBPCwebconfig file

2 Find the text clientCredentialType=Windows

3 Change value of clientCredentialType to None (clientCredentialType=None)

4 Open the PC_MSWebsrvrWebPOASBCwebconfig file Repeat steps 2 and 3

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3554

This page is left blank for documents that are printed on both sides

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

The installation of the Planning and Consolidation Administration Client allows administrators to

build and maintain Planning and Consolidation environments and models and administer security

All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions

add-in for Microsoft Office for more information see the SAP BusinessObjects EPM solutions add-in for

Microsoft Office help

NOTE

You must update the Administration Client to the same version as the server

If your PC is on a different domain than your server you must set the Internet Explorer

Security Zone value of the Planning and Consolidation client to prompt for user name and

password Otherwise the Planning and Consolidation Start Page does not display

41 Installing the Administration Client

Prerequisites

NOTE

For a definitive list of system requirements see the Product Availability Matrix on SAP Service

Marketplace at httpservicesapcompam Search on Planning and Consolidation

The following list describes the minimum software requirements

Microsoft Internet Explorer 70 or 80

Microsoft Office 2007 or 2010

NET Framework 20 or higher (install any required NET Framework Hotfixes by referring to

httpsupportmicrosoftcomkb)

Pentium IV (1 GHz CPU)

512 MB RAM

100 MB of free hard disk space in the My Documents folder

20 MB of free hard disk space for the installed Administration files

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

41 Installing the Administration Client

2012-06-13 CUSTOMER 3754

NOTE

We recommend that you install all of the latest Microsoft Windows hotfixes prior to installing

the Administration client For information about which hotfixes to install see http

updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us

ProcedureThe following procedure describes how to install the Administration Client on to an administratorrsquos

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 AddRemove Programs in the Windows Control Panel

3 Point your browser to the Planning and Consolidation Web at httpltPC_serverportgtsap

bpcweb

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

42 Installing the EPM Add-in

The Planning and Consolidation installation media does not contain the EPM addin setup program

You must download the most recent version of the full setup (EPM Add-inexe) from the Service

Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPC

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

43 Using the Client Auto Update Program

If Planning and Consolidation version 100 or later is installed you can use the Client Auto Update

program to set up the server so that it determines if an upgrade for a connecting Administration client

is necessary

The following describes the use of the auto update program for the Administration Client and the EPM

add-in

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

42 Installing the EPM Add-in

3854 CUSTOMER 2012-06-13

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 37]

To use the Client Auto Update program for the Administration Client proceed as follows

1 From the Server Manager select Options Client Options

2 Select Admin Update

3 If users without administrator rights on their machines use the auto update enter an administrator

ID and password in the Admin ID and Admin password fields respectively The Admin ID should be a

member of the local administrators group on all the computers running the auto update This

setting is not needed if all users have administrator rights on their machines

4 Select Update

For the EPM Add-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 Optionshellip 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 Market Place (SMP) at httpservicesapcom

All support packages and patches are available from the SMP as a zip file

EPMEXCLCLNTltSPLgtzip is for a support package

EPMEXCLCLNTltSPLgtPltPLgtzip 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 ltSP versiongtmsp

EPM Addin Support Package ltSP versiongtxml

For a patch these files are

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

2012-06-13 CUSTOMER 3954

EPM Addin Patch ltpatch numbergtmsp

EPM Addin Patch ltpatch numbergtxml

2 Unzip the zip file and extract the two files to the application server folder (WebsrvrWebBPC

Installation)

3 From the Server Manager select Options Client Options

The system lists the available packages Select the package that you want to use for the autoupdate

You can set a different update policy for each package listed

EXAMPLE

The following table illustrates some possible situations assuming that you have installed the

first full version (V1)

Available maintenance packages

V2-user updateV3-force updateV4-force updateV5-user update

V5-user update V5-user updateV6-auto updateV7-force update

Minimum Required Version

V4 V4 V7

Notification A prompt tells the user to install maintenance package V4 using the Forced Update behavior

If User Update is enabled the prompt informs the user that maintenance package V5 is available

A prompt tells the user to install maintenance package V7 using the Forced Update behavior

New Version V4 V4 or V5 V7

If you change the update policy for any package click Update to complete the change

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

4054 CUSTOMER 2012-06-13

5 Connection Issues

You may experience connection problems with ports the proxy server or programs and settings that

interact with these components If you have any issues related to connection review the following

recommendations and troubleshooting tips

51 Checking for Open Ports

You must ensure that all required ports are open for inboundoutbound 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 431181836 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

NOTE

You can use the following site to scan for the normal ports It allows you to manually enter a port

number to test

httpwwwmyserverorgportsniffasp

You can change the name of a port

52 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 Explorer Tools Internet Options Connections LAN Settings ) or at the server level

Enabling content filtering on the proxy server or firewall may cause connection problems

If external users are having trouble connecting to the server make sure the proxy server connects

using a fully qualified domain name Fully qualified domain names typically resolve both internal

and external IP addresses

Each secure Planning and Consolidation server name must be identified on the proxy server

Proxy servers may or may not require authentication which could conflict with Planning and

Consolidation authentication Do not use authentication on the proxy server The system

5 Connection Issues

51 Checking for Open Ports

2012-06-13 CUSTOMER 4154

synchronizes the user name and password on the remote server with the local user name and

password

NOTE

For more information about setting up an ISA proxy server contact SAP Support to request a

copy of Setting up ISA Proxy Server White Paper

Internet Explorer Settings 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

5 Connection Issues

52 Proxy Server and Firewall Issues

4254 CUSTOMER 2012-06-13

6 Installing Planning and Consolidation with Two Active Directory Domains

To set up a Planning and Consolidation 10 application server in a hosted environment and use your

own domain users follow this procedure In general you install Planning and Consolidation on the

host domain use the host domain account and assign it to the Planning and Consolidation users

SysAdmin Admin and Users Then you accept one way trust (the host domain trusts your domain)

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

6 Installing Planning and Consolidation with Two Active Directory Domains

2012-06-13 CUSTOMER 4354

This page is left blank for documents that are printed on both sides

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

This section describes best practices and instructions for installing Planning and Consolidation in a

Terminal Services or Citrix Server deployment

71 Terminal Services Home Directories

We recommend using Terminal Server home directories rather than using the userrsquos 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

72 System Requirements

The Citrix server should be one of the following systems

XenApp 5 Enterprise

XenApp 5 Platinum

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 37])

73 Installing Planning and Consolidation

Prerequisites

The server installation files have been downloaded from SAP Service Marketplace and installed

Procedure

The following steps outline how to install the Planning and Consolidation clients in a Terminal Services

(TS) or Citrix Server deployment

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

71 Terminal Services Home Directories

2012-06-13 CUSTOMER 4554

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 userinstall

4 Open a browser and connect to the URL httpltPC_serverportgtsapbpcweb

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 userexecute 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 Iexploreexe http(s)

ltServerNamegt-NetBIOS or FQDNsapbpcweb

To publish Planning and Consolidation Administration CProgram FilesPC_MS

BPCAdminMainexe

74 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 userrsquos desktop) must be moved to the All UsersDesktop folder

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

74 Creating a Shortcut to the Launch Page

4654 CUSTOMER 2012-06-13

8 Installing SSIS Custom Tasks

This section provides background information and instructions for installing SQL Server Integration

Services (SSIS) for SQL Server 2008 and SQL Server 2012

The Planning and Consolidation Data Manager component supports and uses SSIS Since SQL Server

2008 and SQL Server 2012 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

81 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 Filelistxml 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

OSoftSetupexe ‒ 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 or OSoftSSIS2012_Client on the client machine followed by the SQL Server

version If you want to use SQL 2008 Tasks under the SQL 2012 environment you must install

OSoftSSIS2008_Client on the application server For detailed information see SAP Note 1707410

You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package by extracting

OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPC

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 or

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4754

OSoftSSIS2012_Client for creating a COM+ application For more information see Before You Modify

the SSIS Packages [page 50] and Setup of a COM+ Application on the Application Server [page 51]

Bin folder

This folder contains the following components

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCCachedll Planning and Consolidation Cache file

BPCDataFlowPackagedll or BPCDataFlowPackage2012dll

BPCDMdll

BPCDMTaskMaindll COM+ component

BPCFilePreviewdll

BPCGacUtil_20exe System File

BPCGacUtil_40exe System File

BPCImpersonatordll Planning and Consolidation Impersonator

BPCLogicdll

BPCScriptdll

BPCServerZipdll

BPCServiceResdll

BPCTransferMembersdll

BPCWriteBackdll

InteropDTSdll

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

4854 CUSTOMER 2012-06-13

Name Remark

OSoftAdminServerdll

OSoftAuditdll

OSoftComLibServerdll

OSoftCommonResQrydll

OSoftConfigurationdll

OSoftCustomXMLSvrdll

OSoftDatabaseADMINdll

OSoftDatabaseSYSADMINdll

OSoftDatabaseSYSADMINDMdll

OSoftDatabaseUSERdll

OSoftDMDTSXExecutedll or OSoftDMDTSXExecute2012dll

OSoftDMTaskFormdll

OSoftDMTaskMaindll

OSoftDMToolsdll

OSoftFileManagedll

OSoftLoggingdll

OSoftLogWriterdll

OSoftMetaDatadll

OSoftSQEdll

OSoftSystemConfigdll

OutlookSoftconfig Configuration file to connect DB server

XceedCompressiondll XceedZip file

XceedCompressionFormatsdll XceedZip file

XceedFileSystemdll XceedZip file

XceedZipdll XceedZip file

Config folder

This folder has FileListxml 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 FileListxml 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

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4954

OSoftSetupexe

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

NOTE

If you installed the OSoftSSIS2008_Client or OSoftSSIS2012_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

Resources Folder

This folder contains the BPCServicesdll and BPCServiceUIdll files which contain resource text

Only English resources are included for the SSIS custom tasks

82 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

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008 and 2012 respectively

8 Installing SSIS Custom Tasks

82 Before You Modify the SSIS Packages

5054 CUSTOMER 2012-06-13

Name Remark

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012 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

lthellipgtOSoftSSIS2008_Clientbin or lthellipgtOSoftSSIS2012_Clientbin

On the Planning and Consolidation application server

ltdrivegtWebsrvrbin

2 Paste these files into the folder 100DTSTasks for SQL Server 2008 or into 110DTSTasks for

SQL Server 2012 For example if you install your SQL 2008 server or R2 on CProgram Files

Microsoft SQL Server paste all files into the CProgram Files (x86)Microsoft SQL Server

100DTSTasks folder

In Integration Services set the property Run64BitRunTime to True

83 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 or OSoftSSIS2012_Client on the

application server

8 Installing SSIS Custom Tasks

83 Setup of a COM+ Application on the Application Server

2012-06-13 CUSTOMER 5154

Typographic Conventions

Example Description

ltgt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example Enter your ltUser Namegt

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 httpwwwsapcom

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

5254 CUSTOMER 2012-06-13

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

  • SAP BusinessObjects Planning and Consolidation 100
    • Table of Contents
    • 1 Introduction
      • 11 SAP Notes for the Installation
      • 12 Naming Conventions
        • 2 Installing Planning and Consolidation Servers
          • 21 Basic Steps
          • 22 Prerequisites
          • 23 Before Starting the Planning and Consolidation Server Installation
          • 24 Logging on to Servers
          • 25 Service-level Accounts
          • 26 Standard and Advanced Settings
          • 27 Installing the Prerequisites
            • 271 Installing the Prerequisites ndash Basic Steps
            • 272 Installing the Operating System
            • 273 Installing the SQL Server
            • 274 Installing Analysis Services
            • 275 Installing the Anti-Cross Site Scripting Library
              • 28 Installing on a Single Server
              • 29 Installing the Server in a Multiserver Configuration
                • 3 After Installing Planning and Consolidation Servers
                  • 31 Post-Installation Steps
                  • 32 Connecting to Solution Manager Diagnostics
                  • 33 Configuring the Planning and Consolidation NET Application Servers
                  • 34 Post-Installation Optional Configuration Steps
                    • 341 Enabling the Management Console
                    • 342 Setting Up ODBC Logging in IIS for the Default Web Site
                    • 343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2
                    • 344 Removing Default Access to the Console
                    • 345 Management Console Access Control
                    • 346 Using Client Certificates
                        • 4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office
                          • 41 Installing the Administration Client
                          • 42 Installing the EPM Add-in
                          • 43 Using the Client Auto Update Program
                            • 5 Connection Issues
                              • 51 Checking for Open Ports
                              • 52 Proxy Server and Firewall Issues
                                • 6 Installing Planning and Consolidation with Two Active Directory Domains
                                • 7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
                                  • 71 Terminal Services Home Directories
                                  • 72 System Requirements
                                  • 73 Installing Planning and Consolidation
                                  • 74 Creating a Shortcut to the Launch Page
                                    • 8 Installing SSIS Custom Tasks
                                      • 81 Composition of SSIS Custom Task Installation
                                      • 82 Before You Modify the SSIS Packages
                                      • 83 Setup of a COM+ Application on the Application Server
                                          • Copyright and trademarks
Page 5: Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

344 Removing Default Access to the Console 32

345 Management Console Access Control 33

346 Using Client Certificates 34

Chapter 4 Installing Planning and Consolidation Administration Client and the

SAP BusinessObjects EPM solutions Add-in for Microsoft

Office 37

41 Installing the Administration Client 37

42 Installing the EPM Add-in 38

43 Using the Client Auto Update Program 38

Chapter 5 Connection Issues 41

51 Checking for Open Ports 41

52 Proxy Server and Firewall Issues 41

Chapter 6 Installing Planning and Consolidation with Two Active Directory

Domains 43

Chapter 7 Installing Planning and Consolidation in a Terminal Services or Citrix

Server Deployment 45

71 Terminal Services Home Directories 45

72 System Requirements 45

73 Installing Planning and Consolidation 45

74 Creating a Shortcut to the Launch Page 46

Chapter 8 Installing SSIS Custom Tasks 47

81 Composition of SSIS Custom Task Installation 47

82 Before You Modify the SSIS Packages 50

83 Setup of a COM+ Application on the Application Server 51

2012-06-13 CUSTOMER 554

This page is left blank for documents that are printed on both sides

1 Introduction

The SAP BusinessObjects Planning and Consolidation Installation Guide is intended for System

Administrators who perform Planning and Consolidation server and Administration client

installations It contains everything you need to know about installing the prerequisite components

and the server and client software

The installation package contains a full installation program While we do not offer a software upgrade

for this release we provide detailed instructions on how to migrate your existing environments For

more information see the Upgrade Guide which is available on SAP Service Marketplace at http

servicesapcominstguidesEPM-BPC Planning and Consolidation 100 version for the Microsoft platform

For more information about the Planning and Consolidation Office client software see the SAP

BusinessObjects EPM solutions add-in for Microsoft Office help

New Installation Program Features in 100

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

11 SAP Notes for the Installation

Read the following SAP Notes before you start the installation These SAP Notes contain the most

recent information on the installation as well as corrections to the installation documentation Make

sure that you have the up-to-date version of each SAP Note which you can find in the SAP Service

Marketplace at the Internet address httpservicesapcomnotes

1 Introduction

11 SAP Notes for the Installation

2012-06-13 CUSTOMER 754

SAP Note Number Title Comments

1584890 Documentation Addendum Contains information that does not appear in the application help of Planning and Consolidation 100 version for the Micrososft platform

1733053 SAP Planning and Consolidation 100 SP08 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP08This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1689792 SAP Planning and Consolidation 100 SP07 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP07This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1665656 SAP Planning and Consolidation 100 SP06 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP06This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1643037 SAP Planning and Consolidation 100 SP05 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP05This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1620464 SAP Planning and Consolidation 100 SP04 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP04This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1601213 SAP Planning and Consolidation 100 SP03 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP03This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1591848 SAP Planning and Consolidation 100 SP02 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP02This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1 Introduction

11 SAP Notes for the Installation

854 CUSTOMER 2012-06-13

SAP Note Number Title Comments

1573539 SAP Planning and Consolidation 100 SP01 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP01This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

12 Naming Conventions

In this document the following naming conventions apply

Variable Description

ltPC_serverportgt Server name or IP address and port number of SAP Planning and Consolidation application location

ltdrivegt The drive where SAP Planning and Consolidation is installedThe default for this is CPC_MS

1 Introduction

12 Naming Conventions

2012-06-13 CUSTOMER 954

This page is left blank for documents that are printed on both sides

2 Installing Planning and Consolidation Servers

This section includes the basic steps for installing a Planning and Consolidation server the prerequisites

and what to do before during and after the server installation

21 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 at httpservicesapcominstguidesepm-bpc 100 version for the Microsoft platform

2 Perform the tasks in the Before Starting the Planning and Consolidation Server Installation [page 13] section

including installing all prerequisites

3 From the application server install the Planning and Consolidation server See Installing Planning and

Consolidation on a Single Server [page 24]

NOTE

You must install both Planning and Consolidation 100 as well as the most recent Planning

and Consolidation 100 Support Package available from the SAP Service Marketplace at

httpservicesapcomswdc Software Downloads Support Packages and Patches A - Z Index

B SAP BPC FOR MICROSOFT SBOP PC 100 FOR MICROSOFT Comprised Software Component

Versions SAP CPM BPC 100 M Windows Server on x64 64bit

4 If you have multiple machines see Installing the Server in a Multiserver Configuration [page 26]

5 Perform the steps in the section After Installing Planning and Consolidation Servers [page 27]

22 Prerequisites

The following table describes the software you need to install before installing the Planning and

Consolidation server and the minimum versions required

NOTE

A list of the supported operating systems and database systems is also available in the Product

Availability Matrix on SAP Service Marketplace at httpservicesapcompam Search on

Planning and Consolidation

2 Installing Planning and Consolidation Servers

21 Basic Steps

2012-06-13 CUSTOMER 1154

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 or

Data Center with or without Hyper-V

NOTE

The operating system must be configured with NTFS

Relational Database Microsoft SQL Server 2008 Enterprise Edition Microsoft SQL Server 2008 R2 (Gemini) Enterprise Edition Microsoft SQL Server 2012 Enterprise Edition

OLAP Database Microsoft SQL Server 2008 Enterprise Edition ‒ Analysis Server Microsoft SQL Server 2008 R2 Enterprise Edition ‒ Analysis Server Microsoft SQL Server 2012 Enterprise Edition ‒ Analysis Server

Data Integration Microsoft SQL Server 2008 Enterprise Edition ‒ SQL Service Integration Services

Microsoft SQL Server 2008 R2 Enterprise Edition ‒ SQL Service Integration Services

Microsoft SQL Server 2012 Enterprise Edition ‒ SQL Service Integration Services

Other Requirements MSXML 40 SP2 or later ADOMDNET

ADOMDNET 100 when running SQL Server 2008 or 2008 R2 ADOMDNET 110 when running SQL Server 2012

SQL Server software components NET 40 IIS 75 or IIS 70

(Included in your Operating System IIS 75 is required for Windows 2008 R2 editions)

Anti-Cross Site Scripting Library 42This component must be downloaded before installing the server The server installation program asks for the path of each file and copies the files into the appropriate Planning and Consolidation path

Microsoft Visual C++ 2005 Runtime Libraries SP1 Microsoft Access Database Engine 2010 64bit VMWare ESX 3x or ESX 40

(Required only if a landscape deployment strategy using virtualization technologies is planned)

NOTE

MSXML 40 SP2 ADOMDNET 100 and Microsoft Visual C++ 2005 Runtime Libraries SP1 are included with the installation program but not installed automatically

RECOMMENDATION

For SQL Server 2008 only we recommend the installation of Microsoft SQL Server 2008 SP1

(or later) cumulative update package 6 or higher to solve a problem with incorrect periodic

2 Installing Planning and Consolidation Servers

22 Prerequisites

1254 CUSTOMER 2012-06-13

values being returned with calculated accounts For more information see SAP Note number

1429246 which also contains download information

We recommend SQL Server 2008 (or R2) Enterprise Edition or SQL Server 2012 Enterprise

Edition for the OLAP database to support proactive cache and cube partitioning It is

technically possible to use SQL Server 2008 (or R2) Standard Edition or SQL Server 2012

Standard Edition for data integration servers but we do not recommend this

23 Before Starting the Planning and Consolidation Server Installation

You must perform the following tasks before starting your Planning and Consolidation server

installation

Install all the prerequisite software including all of the latest Microsoft hotfixes For more

information see Installing the Prerequisites [page 17]

If you access your application through a firewall verify with your network administrator which

TCP ports to choose during the installation By default port 80 is the setting for standard http

access and port 443 is the setting for https access If you require a service to listen on a different

port you can specify it during the installation program in Advanced Settings See Standard and Advanced

Settings [page 16]

Make sure all required server ports are open and that there is communication between the physical

servers on which you are going to install the server types See Checking for Open Ports [page 41]

Set up the required service accounts that you need to install the Planning and Consolidation server

See Service-Level Accounts [page 15]

The sample environment EnvironmentShell has been updated in this version of Planning and

Consolidation and automatically overwrites the previous version If you have made any

modifications to EnvironmentShell that you want to keep make a copy of it before continuing

with the installation

If you have the URLScan and IIS Lockdown tools installed on your application server you must

reinstall them

Disable your anti-virus software program After the installation when you enable the program

turn off Script Blocking

If a version of Planning and Consolidation on a NetWeaver platform exists uninstall it before you

install Planning and Consolidation 100 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 fsntfsV

All servers in a multiserver environment must be members of the same domain

2 Installing Planning and Consolidation Servers

23 Before Starting the Planning and Consolidation Server Installation

2012-06-13 CUSTOMER 1354

In a multiserver environment the installing ID must be a domain user ID We recommend that

you do not log on to the servers using a local server user ID even if the user ID is a member of the

Administrator group on the server This way you have the proper authority to install software and

to modify the Component Services See Logging On to Servers [page 14]

You must determine the IP addresses or server names for all servers before installing Planning and

Consolidation We recommend that you use static IP addresses

IIS must be enabled

If the application server is not able to copy files to the database server during the installation because

of port access reasons (DMZ WORKGROUP or nontrusted domain authentication failures) do

the following

1 Copy the EnvironmentShell database file ServerEnvironmentShelldb10 from the

Planning and Consolidation installation program to any folder on the SQL server (for example

cEnvironmentShelldb10)

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 cEnvironmentShelldb10)

Install the Anti-Cross Site Scripting Library which provides protection to Web-based applications

against Cross-Site Scripting (XSS) attacks See Installing the Anti-Cross Site Scripting Library [page 24]

24 Logging on to Servers

When installing in a multiserver environment you must use a domain user ID to log on to all

components

A local server user ID is a member of the Administrator group on the server A domain user ID is a

member of the Administrator group of a domain to which the server belongs or a member of the

Administrator group on the local server

Errors may display during the installation program and in the diagnostic program if the installing user

is not assigned to the Administrator group directly but is assigned to a group with Administrator rights

You can ignore these messages

NOTE

If you change the password used to install Planning and Consolidation you must change the

password for the applicable Planning and Consolidation service To do this go to Server Manager

on the application server and select Server Reset Logon Credentials For more information see

the SAP Planning and Consolidation Operations Guide in httpservicesapcominstguidesepm-bpc

100 for the Microsoft Platform SBOP Plan amp Consol 100 MS Administrators Guide

2 Installing Planning and Consolidation Servers

24 Logging on to Servers

1454 CUSTOMER 2012-06-13

25 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

PrerequisitesPlanning and Consolidation 100 has the following Windows services

BPC SendGovernor which manages Microsoft Analysis Service locks to ensure consistent performance

and avoid deadlocks

BPC ServiceManager which manages the System Landscape Directory (SLD) service logging service

and global caches

BPC CTS ServiceManager which listens and handles CTS import requests from the CTS+ transport

management system

Since these services should be able to access to the FileShare server an Admin account is assigned

automatically to the service during the installation of the Planning and Consolidation server program

Even though an Admin account has been assigned to the server correctly the services may fail to start

with the error message

Could not start the BPC SendGovernor service

The reason for this is that the Admin account is not registered as a service

When installing a service to run under a domain user account the account must have the right to

logon as a service on the local machine This logon right strictly applies only to the local computer

and must be granted in the Local Security Policy

To edit the Local Security Policy of the computer you want to define the logon as a service

permission perform the following actions

1 Start the Local Security Settings Microsoft Management Console (MMC) snap-in

2 Expand Local Policies and then click User Rights Assignment

3 In the right-hand pane right-click Log on as a service and then click Security

4 Add the user to the policy and click OK

5 Close the Local Security Settings MMC snap-in

For more details see How to Troubleshoot Service Startup Permissions http

supportmicrosoftcomkb259733

FeaturesDuring the installation enter user IDs and passwords for the following user types

System Admin ID

This ID is read-only and is the same as the installation user ID that is the system displays the ID

on the installation screen but you cannot modify it This ID allows access to code that provides

2 Installing Planning and Consolidation Servers

25 Service-level Accounts

2012-06-13 CUSTOMER 1554

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 readwrite 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

26 Standard and Advanced Settings

The following tables describe the standard and advanced settings for the installation program After

the server is installed you can change these settings using the Server Manager

NOTE

When defining server names the name refers to the NetBIOS name IP address and fully qualified

domain names (FQDN)

Standard Settings

Standard settings are typically used for a single-server environment The following table describes each

setting

Server Option Value Description

SQL Database server name The name of the SQL DB server

OLAP server name The name of the OLAP server

File Share server name The default value is the name of the File Share server that should be the computer name

Local data path Where the data files are saved on the File Share server By default this is CPC_MSData

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

Server Option Value Description

SQL Server Name The name of the SQL DB server Defaults to the local server

2 Installing Planning and Consolidation Servers

26 Standard and Advanced Settings

1654 CUSTOMER 2012-06-13

Server Option Value Description

Instance name The SQL instance name If left blank the default instance is used

Port number The default port number for the SQL Server is 1433

Provider The only available value is SQL

Local path for EnvironmentShell 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 CPC_MSData

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 changesSee the Kerberos authentication settings section in the SAP Library Server Manager Guide on httpservicesapcominstguidesEPM-BPC

100 for the Microsoft Platform

Scheduler Server Name The name of the server used for scheduling usually the application server for example GMPV50072862B If you have multiple application servers select the appropriate one

NOTE

If the primary server stops working you must manually configure your application server database to froward requests to another application server

27 Installing the Prerequisites

271 Installing the Prerequisites ndash Basic Steps

Before installing your Planning and Consolidation server you must install the prerequisite Microsoft

software the operating system IIS SQL server analysis services ADOMDNET and MSXML This

section provides guidance on installing each component For specific versions required see

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 1754

Prerequisites [page 11] and the Product Availability Matrix on the SAP Service Marketplace at http

servicesapcompam Search on Planning and Consolidation

NOTE

To ensure a successful installation you must install the software in the order listed in this

procedure

Check all third-party infrastructure services to ensure that they are functioning and that their

authentication models are documented (stated) since you need to reference this information

during the installation These third-party services include IIS OLAP service SQL services and

Active Directory (AD)

We recommend not installing Microsoft Office on the application server

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

(UMCexe) on the Planning and Consolidation CD in a folder called UMC_100_INSTALLER When

you run the installation package the wizard guides you through the following steps

1 Choose a language for the UMC install wizard to use

2 Check that the prerequisite check status is Succeeded and click Next

3 When you are ready to install the UMC click Next on the welcome screen

4 Click I accept the License Agreement and then Next

5 Choose the destination directory for the UMC installation and click Next

6 Select the languages that you wish to install

7 Select the features that you want to install (POAFHelper dotnet is mandatory for Planning

and Consolidation)

8 On Start Installation click Next to complete the installation

2 Install the required operating system on the single-server computer or on each physical server for

a multiserver configuration See Installing the Operating System [page 19]

3 Install the latest service pack for your operating system To install this service pack go to http

wwwmicrosoftcom

4 From your operating systems media install IIS

5 From your SQL Server media install SQL Server and its required service packs and hot fixes See

Installing SQL Server [page 19]

6 From your SQL Server media install Analysis Services Enterprise Edition and its required service

packs and hot fixes See Installing Analysis Services [page 23]

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

1854 CUSTOMER 2012-06-13

7 On your application server install ADOMDNET The Planning and Consolidation zip file contains

the ADOMDNET installation package in the following locations

For SQL Server 2008 mdash BPC SetupServerSQLSERVER2008_ASADOMD10_x64msi

For SQL Server 2012 mdash BPC SetupServerSQLSERVER2012_ASADOMD11_x64msi

8 On your application server install MSXML 40 Service Pack 2 or later

The MSXML 40 SP2 installation package is contained in the Planning and Consolidation zip file at

the following location BPC SetupServermsxmlmsi

9 On your application server install Microsoft Visual C++ 2005 Runtime Libraries SP1

The Microsoft Visual C++ 2005 SP1 installation package is contained in the Planning and

Consolidation zip file at the following location BPC SetupServervcredist_x64exe

NOTE

The version of vcredist_x64exe in BPC SetupServer has been updated to 8061000 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 httpwwwmicrosoftcomdownloadsen

detailsaspxFamilyID=C06B8369-60DD-4B64-A44B-84B371EDE16Dampltdisplaylanggt=en

272 Installing the Operating System

Before installing the operating system make sure that you configure your server for NTFS

For a list of languages that are supported see the Product Availability Matrix on the SAP Service

Marketplace at httpservicesapcompam Search on Planning and Consolidation

Planning and Consolidation can support all servers with an operating system in any language

NOTE

Currently Planning and Consolidation does not support an operating system in bi-directional

languages such as Hebrew

ProcedureIf you are installing IIS 70 or 75 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

273 Installing the SQL Server

PrerequisitesDuring the installation procedure you have the opportunity to specify the location of the

EnvironmentShell database file Check that it is possible to access EnvironmentShell from the location

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 1954

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 CEnvironmentShelldb10) 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 a 2008 2008 R2 and 2012 SQL Server

SQL Server Considerations

We recommend installing all required components in sequence For example install the Operating

System (Windows Server) then enable IIS and ASPNET and install any Windows Server service

packs

IIS and NET Framework 40 are required on your application server

NOTE

If you encounter a 500 HTTP Error when trying to connect to the Planning and Consolidation

Web Client refer to Microsoft Support articles 2520479 and 2468871 for assistance

To reinforce security we recommend that you install the SQL server and SSAS components to a

nondefault instance of SQL Server

General Installation Steps

1 Launch the SQL Server Setup program entering a product key if necessary and accepting the license

terms

2 Choose Install to install the SQL support files

3 In Feature Selections select instance and shared features as indicated in the SQL Server Component

Options section below then choose Next

4 Review disc space requirements then choose Next

5 In Server Configuration Perform the following actions

1 In the Service Accounts tab enter a Planning and Consolidation sysadmin account for the SQL

Server Database Engine and the SQL Server Analysis services This is required so that the Planning

and Consolidation sysadmin can create and process the Planning and Consolidation database

because the Microsoft SQL server tries to back up or restore database with the privileged

account This account is also required during Backup Environment and Restore Environment in the

Server Manager

For a single-server environment this account is also required if the backup file is located in a

different domain machine because SQL tries to access the folders and files with this account

For the a multiple-server environment SQL server retrieves the information of backup file

from the application server and the account requires the folder access privilege for the

application server

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2054 CUSTOMER 2012-06-13

To ensure that you have the complete access privileges we recommend the Planning and

Consolidation sysadmin for this service account

2 In the Collation tab set the collation settings to SQL_Latin1_General_CP1_CI_AS

Choose Next

6 Set Database Engine Configuration options then choose Next

We recommend you choose Mixed mode (Windows authentication and SQL authentication) This allows you

to use a restrictive SQL ID that works with the drill-through feature If you must restrict SQL

authentication for security reasons you can define a specific parameter in your drill-through

queries If you do not need drill-through support or use it without leveraging SQL authentication

you can install the SQL Server in Windows-only mode

7 Accept the Analysis Services Configuration default options and the remaining default options of the

installation program

8 Choose Install to begin the installation with the options you have set

SQL Server Component 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

Server Component What to Install

SQL Server Database Engine Services

SSAS Server Analysis Services

Application Server The following Shared Features Client Tools Connectivity Integration Services Client Tools SDK

Custom Settings for the SQL Server

As of version 100 Planning and Consolidation supports the following new features for SQL Server 2008

SQL Server 2008 R2 and SQL Server 2012

Process Dimension

It is now possible to process a dimension with multiple selections At processing time the process

dimension module makes changed or added information for each dimension and process for all selected

dimensions and cubes in parallel

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 2154

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

NOTE

Setting 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 tblFactWBltappgt table

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 Microsoftreg SQL Servertrade

20052008 which you can download from wwwmicrosoftcom (search on ldquoTable Partitioningrdquo to find

all relevant articles)

After Installing SQL Server 2008 SQL Server 2008 R2 and SQL Server 2012

From SQL Server Configuration Manager confirm that the SQL Server Browser service is

running The browser service is required for Planning and Consolidation

From SQL Server Configuration Manager do the following

1 Select Protocols for ltInstanceNamegt then double-click TCPIP from the right side of the window

2 When prompted for the TCPIP Properties select IP Addresses You see two IPs that indicate the

localhost and external network interface machine

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2254 CUSTOMER 2012-06-13

3 If you want to use IP1 which indicates Server IP set Enabled to Yes and specify the TCP Port as

desired

4 Delete 0 from TCP Dynamic Ports Set IPAll - TCP Ports as desired (for example 1533)

RECOMMENDATION

We do not recommend using dynamic ports

In an SQL server the default instance has a listener which listens on a fixed port (TCP

port 1433) However for the named instance the port on which the SQL server listens is

random and dynamically selected when the named instance of the SQL server starts This

recommendation prevents any conflict problems

From the SQL Server Configuration Manager specify the client protocol options for the application

server

1 Select Client Protocols from the SQL Native Client Configuration folder

2 From the right side of the window double-click TCPIP The TCPIP 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

NOTE

We 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

274 Installing Analysis Services

ProcedureAfter you install SQL Server and its required service packs and hotfixes you must install SQL Server

Analysis Services and its required service packs and hotfixes

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 2354

NOTE

If you have migrated your Analysis Services repository to the SQL Server back up the database

that contains the repository before installing this release

To install Analysis Services for SQL Server 2008 SQL Server 2008 R2 or SQL Server 2012 follow the steps

and guidelines in httptechnetmicrosoftcomen-uslibraryms143219aspx

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 httpwwwmicrosoftcomdownloads

detailsaspxFamilyID=3be0488d-e7aa-4078-a050- ae39912d2e43ampdisplaylang=en

275 Installing the Anti-Cross Site Scripting Library

Procedure

Before installing Planning and Consolidation servers you must download the Anti-Cross Site Scripting

Library (version 42 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 AntiXSSLibraryDLL from the Microsoft Web

site at httpwwwmicrosoftcomdownloadendetailsaspxid=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 AntiXssLibrarydll

28 Installing on a Single Server

When you install all Planning and Consolidation server components on a single server you should

consider the following issues

Make sure the server has a minimum of 800 MB of hard disk space

Additional environment installations require more free disk space which is a minimum of two

times the uncompressed size of the environment files

When you install Planning and Consolidation on a single-server the system adds the following server

components

SQL Server

SQL Server Analysis Services (SSAS)

Application Server

FileShare server

Procedure

To install Planning and Consolidation on a single server take the following steps

1 Exit all Windows programs

2 Installing Planning and Consolidation Servers

28 Installing on a Single Server

2454 CUSTOMER 2012-06-13

2 Log on to the server with a local server user ID or domain user ID For more information see Logging

on to servers [page 14]

3 Make sure all prerequisite software is installed on the server For more information see Installing

the Prerequisites [page 17]

4 Obtain SAP Planning and Consolidation from the Downloads SAP Installations amp Upgrades area of

SAP Service Marketplace then extract the files and run StartUpexe

5 From the Server Install screen select Install the Planning and Consolidation server

6 From the Welcome screen choose Next

7 From the License Agreement page choose I accept the terms of the license agreement then choose Next

8 From the Installation Method page accept the default Single machine enter a system ID for the system

landscape directory (SLD) and choose Next

NOTE

Entering a system ID of the SLD is only required if you have a SAP Solution Manager license

If you do not have a SAP Solution Manager license you can leave this field empty

9 From the Authentication Method page choose the desired authentication method and choose Next

10 If you have chosen SAP BusinessObjects User Management System in the previous screen on the CMS

Authentication page enter the information required to log on to CMS as an administrator

The following information is required

Field Description

System name CMS system name (server nameport number) for example CMSServer6400

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

11 After entering the CMS administrator authentication details choose Next

12 From the Service type accounts page enter service-level account user IDs and passwords See Service-

Level Accounts [page 15]

13 After defining the IDs and passwords choose Next

14 From the Server Information page (see Standard and Advanced Settings [page 16]) do one of the following

Review the standard settings and choose Next

To set advanced settings choose the Advanced Settings button Enter the desired information

and choose Next

2 Installing Planning and Consolidation Servers

28 Installing on a Single Server

2012-06-13 CUSTOMER 2554

15 Specify the location and name of AntiXssLibrarydll See Installing the Anti-Cross Site Scripting Library [page

24]

Choose Next

16 Select destination folders for Programs and Data The Data files include Webfolders and FileDB

(published reports) and should be installed on a separate drive in a production environment This

recommendation reduces the hard disk IO time and helps to speed up SQL commands

Accept the defaults or make your selections then choose Next

17 Select the default values for the Web client The values are used to determine the default language

and region for the Web client when you connect to it You can change the values in the Planning

and Consolidation Server Manager

18 The installation process takes a few moments When it is complete choose Exit

19 A prompt is displayed to restart your computer Select OK to restart

20 Perform the steps in After Installing Planning and Consolidation Servers [page 27]

29 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 24]) with the following

exceptions

On the Installation Method page do not accept the default instead choose Network Load Balancing

environment With this option there is an additional choice to Include sample environment (required on only

one of the application servers) This is because when you install the application server it connects to the

database server and creates the sample environment (EnvironmentShell) Installing the sample

environment is required on only one application server and you may choose which one

In the Virtual Name field enter the virtual IP address virtual name in the default properties

2 Installing Planning and Consolidation Servers

29 Installing the Server in a Multiserver Configuration

2654 CUSTOMER 2012-06-13

3 After Installing Planning and Consolidation Servers

31 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 28]

2 Configure the Planning and Consolidation NET and application server to ensure that it and its

related services function properly and reliably For more information see Configuring the Planning and

Consolidation NET Application Server [page 29]

3 Optional configuration steps [page 30]

1 To ensure proper functioning of the Management Console create an SQL user and modify

the System DSN and IIS to reflect those user credentials See Enabling Management Console [page

30]

2 Configure custom ODBC logging for the default Web site For details of how to configure

custom logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web

Site [page 31]

3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC

Data Source [page 32]

4 Modify the default access rights to the Management Console By default users in Active

Directory can access the Management Console with whatever rights they have been granted

on the server For information about removing default access and creating a group that can

access the console see Removing Default Access to the Console [page 32]

5 Add authorized users or groups to the group that can access the Management Console We

recommend that you only grant Management Console access to system administrators

Planning and Consolidation users should not have any access For more information see

Management Console Access Control [page 33]

6 Configure the use of client certificates for authentication See Using Client Certificates [page

34]

4 Take the following steps to set up security

If you are defining security and application structure continue with step 5

3 After Installing Planning and Consolidation Servers

31 Post-Installation Steps

2012-06-13 CUSTOMER 2754

If you want to designate someone other than the system administrator to manage security

and application structure log on to EnvironmentShell designate a user as a Primary

Administrator

This user must have Administration ‒ Environment and Security ‒ Define User task rights

so that he or she can add and delete environments and define user security

The Primary Administrator can continue with the next step (5)

5 From the machine on which you administer Planning and Consolidation install the

Administration client See Installing the Administration Client [page 37]

6 Start Planning and Consolidation Administration from the launch page

7 Select Connection Wizard and log on to EnvironmentShell

8 Create a new environment using EnvironmentShell as the source

9 Log on to the newly created environment and set up users teams and task profiles (You must

set up task profiles since there is no access to Planning and Consolidation tasks)

10 Set up your data access profiles and add users (or teams) to one or more data access profiles (You

must complete this step since there is no access to dimensions or members)

NOTE

To allow users to request and query large amounts of data you can edit the metabasexml file located

at CWindowssystem32inetsrv Set the following parameters to the stated values

ASPBUFFERINGLIMIT = 10485760

MAXREQUESTENTITYALLOWED = 10485760

32 Connecting to Solution Manager Diagnostics

NOTE

You only need to perform the steps in this section if you have a SAP Solution Manager licence

The diagnostics functions in SAP Solution Manager allow identification analysis and resolution of

problems This procedure provides the steps required to connect Planning and Consolidation to

Solution Manager Diagnostics

Procedure

1 Install the Diagnostics Agent according to SAP Note 1234387 on all servers where application servers

are installed

NOTE

Installation files for Diagnostics Agent are available on Service Marketplace by navigating to

Support Packages and Patches mdash Entry by Application Group SAP Technology Components SAP

SOLUTION MANAGER SAP SOLUTION MANAGER 70 EHP 1 Entry by Component Agents

for managed systems DIAGNOSTICS AGENT 711

3 After Installing Planning and Consolidation Servers

32 Connecting to Solution Manager Diagnostics

2854 CUSTOMER 2012-06-13

Download the installation file based on the 64-bit Windows Server system landscape

2 To access the DBA Cockpit you must create a user account with sufficient rights on all Windows

Servers where Microsoft SQL Server is installed Do the following

1 Start Computer Management then select Action New User

2 Create a new user

3 Right-click on the user then choose Properties On the Member Of tab select Add

4 Add the group SQLServerltReleasegtSQLAgentUser$ltDomain or hostnamegt$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 httpsservicesapcom~sapidb011000358700000074392009E and follow

the chapters that apply to Planning and Consolidation

33 Configuring the Planning and Consolidation NET Application Servers

Procedure

Modifying machineconfig Files

To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock

occurrences that would cause the application server to ldquosleeprdquo and not process anymore you can

modify the machineconfig file which resides in the WINDOWSMicrosoftNETFramework64

v4030319Config directory

1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to

specify whether to automatically configure settings to achieve optimal performance based on the

machine configuration You can set this attribute to True or False

For more information see httpmsdnmicrosoftcomen-uslibrary7w2sway1aspx

2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the

Planning and Consolidation application) or Machineconfig (for all applications including

Planning and Consolidation) to ensure the validationKey and decryptionKey keys have the same

value on all application servers This way when the authentication cookie is checked the

authentication ticket used on one server can still be valid on another server

For more information and sample Visual Basic code for generating random key values see http

msdnmicrosoftcomen-uslibraryms998288aspx

3 After Installing Planning and Consolidation Servers

33 Configuring the Planning and Consolidation NET Application Servers

2012-06-13 CUSTOMER 2954

paght000007_webfarmdeploymentconsiderations and httpmsdnmicrosoftcomen-us

libraryms998310aspx

34 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 30]

2 Configure custom ODBC logging for the default Web site For details of how to configure custom

logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page

31]

3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC Data

Source [page 32]

4 Modify the default access rights to the Management Console By default users in Active Directory

can access the Management Console with whatever rights they have been granted on the server

For information about removing default access and creating a group that can access the console

see Removing Default Access to the Console [page 32]

5 Add authorized users or groups to the group that can access the Management Console We

recommend that you only grant Management Console access to system administrators Planning

and Consolidation users should not have any access For more information see Management Console

Access Control [page 33]

6 Configure the use of client certificates for authentication See Using Client Certificates [page 34]

341 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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3054 CUSTOMER 2012-06-13

NOTE

Without these updates the Management Console does work but some functionality (specifically

User Activity and Service Status) does not work as expected

Should you need to uninstall Planning and Consolidation we recommend that you reset the

Active Log Format field in IIS to W3C Extended Log File Format

342 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 ApplicationHostconfig set the property customLogPluginClsid to the value FF16065B-

DE82-11CF-BC0A-00AA006111E0 Set the logFormat to Custom You can find this in the ltlogFilegt

node in ApplicationHostconfig as shown here

ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0

logFormat=Custom gt

Use the following AppCmds to configure IIS to use ODBC logging for the default Web site

appcmd site set sitenameDefault Web Site

logFilecustomLogPluginClsidFF16065B-DE82-11CF-BC0A-00AA006111E0

appcmd site set sitenameDefault Web Site logFilelogFormatCustom

Configuring ODBC Logging Parameters in ApplicationHostconfig

Configure ApplicationHostconfig to contain the database table information as set up in the Microsoft

Support article specified in the Prerequisites section Configure these settings in the ltodbcLogginggt

node under ltsystemwebServergt

EXAMPLE

ltlocation path=Default Web Sitegt

ltsystemwebServergt

ltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog

userName=Username password=mypassword gt

ltsystemwebServergt

ltlocationgt

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3154

Use the following AppCmds to configure these attributes for the default Web site

appcmd set config Default Web Site sectionodbcLogging

dataSourceBPC_ManagementDSN commitappHost

appcmd set config Default Web Site sectionodbcLogging tableNameBPCLog

commitappHost

appcmd set config Default Web Site sectionodbcLogging userNameUsername

commitappHost

appcmd set config Default Web Site sectionodbcLogging passwordmypassword

commitappHost

NOTE

You cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must

use the SQL Server ODBC driver For more information see the Microsoft Knowledge Base article

931202 The requirements for using the ODBC logging feature in IIS

343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2

ProcedureThis procedure describes how to set up an ODBC data source for the Management Console in Windows

Server 2008 or Windows Server 2008 R2

Proceed as follows

1 Open ODBC Connection Manager

2 On the System DSN tab page add a new DSN

Choose Add

Choose SQL Server as the driver

Choose Finish

3 In the Name and Description fields enter BPC_ManagementDSN

4 In the Server field enter the name of your SQL Server Choose Next

5 Leave the default settings and choose Next

6 Choose the Change the default database to field and enter AppServer Choose Next

7 Leave default settings and choose Next

8 Choose OK

344 Removing Default Access to the Console

NOTE

If you have chosen SAP BusinessObjects User Management System in the installation screen you

do not need to remove or configure access because the Management Console service always runs

with the System Admin ID account which is a member of the Administrators group

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3254 CUSTOMER 2012-06-13

ProcedureTo remove default access to the Management Console and create a group that does have access to the

console use the procedure described below

NOTE

Create your Management Console administrative group either on the server that hosts the

Management Console or in the Active Directory

1 In the context menu of the servers My Computer icon choose Manage

2 In the Computer Management dialog box choose Local Users and Groups Groups

NOTE

Alternatively you can perform analogous steps in Active Directory

3 In the 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

NOTE

This step is a necessary precursor to the completion of this procedure

10 In the Security dialog box click Copy to ensure that the System group retains its privileges

11 Remove access to the Management Console from all groups that should not have it

12 Choose Authentication in the center pane then disable Windows authentication

ResultUsers who have not been granted access to the Management Console can still open the Management

Console Web page but it contains no data or menu options This does not affect the access that a user

would otherwise have to Planning and Consolidation

345 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 32] Their rights in

Active Directory determine what they can access in the Console

By default any member of the Administrators Active Directory group on the application server or

domain has full access to all of the features of the Console except the Planning and Consolidation

logging area Access to Planning and Consolidation logging is controlled within the Planning and

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3354

Consolidation Administration Client task security The user must be granted View system logs task

privileges For more information see the SAP Library Planning and Consolidation Administrators Guide in

httpservicesapcominstguidesepm-bpc 100 version for the Microsoft platform

Your IT policy determines whether you grant access by group or user You may wish to create several

levels of Console users (read-only users for example) in your environment

To grant or limit access to users or groups you can add or remove the following privileges from the

areas described in this table

Privilege Rights Management Area

Task Manager and Kill Process Administrators group on application server or domain

Performance Monitor Counters Administrators group on application server or domain Power Users group on application server or domain Performance Monitor Users group on application server

Microsoft Analysis Services performance monitoring

Administrators group on application server or domain

Microsoft SQL Server Monitoring (performance counters and statistics)

Administrators group on application server or domain

346 Using Client Certificates

To enable the use of client certificates in Planning and Consolidation you must follow several manual

steps

NOTE

Planning 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 httptechnetmicrosoftcomen-us

librarycc753810aspx

For more information about configuring the client certificate mapping authentication see http

technetmicrosoftcomen-uslibrarycc732996(WS10)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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3454 CUSTOMER 2012-06-13

This option allows you to use a client certificate or username and password (Basic

authentication) to connect to Planning and Consolidation

2 Enable anonymous authentication

1 In the IIS Manager expand the node of the Planning and Consolidation web site

2 Select the ManagementConsole directory (ltWebsitegtManagementConsole) to open the

ManagementConsole home page

3 Double-click Authentication and enable Anonymous Authentication

4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way

as in step 3

5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the same

way as in step 3

3 Change the web configuration settings

1 Open the ltPC_MSgtWebsrvrWebBPCwebconfig file

2 Find the text clientCredentialType=Windows

3 Change value of clientCredentialType to None (clientCredentialType=None)

4 Open the PC_MSWebsrvrWebPOASBCwebconfig file Repeat steps 2 and 3

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3554

This page is left blank for documents that are printed on both sides

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

The installation of the Planning and Consolidation Administration Client allows administrators to

build and maintain Planning and Consolidation environments and models and administer security

All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions

add-in for Microsoft Office for more information see the SAP BusinessObjects EPM solutions add-in for

Microsoft Office help

NOTE

You must update the Administration Client to the same version as the server

If your PC is on a different domain than your server you must set the Internet Explorer

Security Zone value of the Planning and Consolidation client to prompt for user name and

password Otherwise the Planning and Consolidation Start Page does not display

41 Installing the Administration Client

Prerequisites

NOTE

For a definitive list of system requirements see the Product Availability Matrix on SAP Service

Marketplace at httpservicesapcompam Search on Planning and Consolidation

The following list describes the minimum software requirements

Microsoft Internet Explorer 70 or 80

Microsoft Office 2007 or 2010

NET Framework 20 or higher (install any required NET Framework Hotfixes by referring to

httpsupportmicrosoftcomkb)

Pentium IV (1 GHz CPU)

512 MB RAM

100 MB of free hard disk space in the My Documents folder

20 MB of free hard disk space for the installed Administration files

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

41 Installing the Administration Client

2012-06-13 CUSTOMER 3754

NOTE

We recommend that you install all of the latest Microsoft Windows hotfixes prior to installing

the Administration client For information about which hotfixes to install see http

updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us

ProcedureThe following procedure describes how to install the Administration Client on to an administratorrsquos

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 AddRemove Programs in the Windows Control Panel

3 Point your browser to the Planning and Consolidation Web at httpltPC_serverportgtsap

bpcweb

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

42 Installing the EPM Add-in

The Planning and Consolidation installation media does not contain the EPM addin setup program

You must download the most recent version of the full setup (EPM Add-inexe) from the Service

Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPC

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

43 Using the Client Auto Update Program

If Planning and Consolidation version 100 or later is installed you can use the Client Auto Update

program to set up the server so that it determines if an upgrade for a connecting Administration client

is necessary

The following describes the use of the auto update program for the Administration Client and the EPM

add-in

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

42 Installing the EPM Add-in

3854 CUSTOMER 2012-06-13

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 37]

To use the Client Auto Update program for the Administration Client proceed as follows

1 From the Server Manager select Options Client Options

2 Select Admin Update

3 If users without administrator rights on their machines use the auto update enter an administrator

ID and password in the Admin ID and Admin password fields respectively The Admin ID should be a

member of the local administrators group on all the computers running the auto update This

setting is not needed if all users have administrator rights on their machines

4 Select Update

For the EPM Add-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 Optionshellip 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 Market Place (SMP) at httpservicesapcom

All support packages and patches are available from the SMP as a zip file

EPMEXCLCLNTltSPLgtzip is for a support package

EPMEXCLCLNTltSPLgtPltPLgtzip 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 ltSP versiongtmsp

EPM Addin Support Package ltSP versiongtxml

For a patch these files are

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

2012-06-13 CUSTOMER 3954

EPM Addin Patch ltpatch numbergtmsp

EPM Addin Patch ltpatch numbergtxml

2 Unzip the zip file and extract the two files to the application server folder (WebsrvrWebBPC

Installation)

3 From the Server Manager select Options Client Options

The system lists the available packages Select the package that you want to use for the autoupdate

You can set a different update policy for each package listed

EXAMPLE

The following table illustrates some possible situations assuming that you have installed the

first full version (V1)

Available maintenance packages

V2-user updateV3-force updateV4-force updateV5-user update

V5-user update V5-user updateV6-auto updateV7-force update

Minimum Required Version

V4 V4 V7

Notification A prompt tells the user to install maintenance package V4 using the Forced Update behavior

If User Update is enabled the prompt informs the user that maintenance package V5 is available

A prompt tells the user to install maintenance package V7 using the Forced Update behavior

New Version V4 V4 or V5 V7

If you change the update policy for any package click Update to complete the change

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

4054 CUSTOMER 2012-06-13

5 Connection Issues

You may experience connection problems with ports the proxy server or programs and settings that

interact with these components If you have any issues related to connection review the following

recommendations and troubleshooting tips

51 Checking for Open Ports

You must ensure that all required ports are open for inboundoutbound 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 431181836 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

NOTE

You can use the following site to scan for the normal ports It allows you to manually enter a port

number to test

httpwwwmyserverorgportsniffasp

You can change the name of a port

52 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 Explorer Tools Internet Options Connections LAN Settings ) or at the server level

Enabling content filtering on the proxy server or firewall may cause connection problems

If external users are having trouble connecting to the server make sure the proxy server connects

using a fully qualified domain name Fully qualified domain names typically resolve both internal

and external IP addresses

Each secure Planning and Consolidation server name must be identified on the proxy server

Proxy servers may or may not require authentication which could conflict with Planning and

Consolidation authentication Do not use authentication on the proxy server The system

5 Connection Issues

51 Checking for Open Ports

2012-06-13 CUSTOMER 4154

synchronizes the user name and password on the remote server with the local user name and

password

NOTE

For more information about setting up an ISA proxy server contact SAP Support to request a

copy of Setting up ISA Proxy Server White Paper

Internet Explorer Settings 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

5 Connection Issues

52 Proxy Server and Firewall Issues

4254 CUSTOMER 2012-06-13

6 Installing Planning and Consolidation with Two Active Directory Domains

To set up a Planning and Consolidation 10 application server in a hosted environment and use your

own domain users follow this procedure In general you install Planning and Consolidation on the

host domain use the host domain account and assign it to the Planning and Consolidation users

SysAdmin Admin and Users Then you accept one way trust (the host domain trusts your domain)

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

6 Installing Planning and Consolidation with Two Active Directory Domains

2012-06-13 CUSTOMER 4354

This page is left blank for documents that are printed on both sides

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

This section describes best practices and instructions for installing Planning and Consolidation in a

Terminal Services or Citrix Server deployment

71 Terminal Services Home Directories

We recommend using Terminal Server home directories rather than using the userrsquos 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

72 System Requirements

The Citrix server should be one of the following systems

XenApp 5 Enterprise

XenApp 5 Platinum

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 37])

73 Installing Planning and Consolidation

Prerequisites

The server installation files have been downloaded from SAP Service Marketplace and installed

Procedure

The following steps outline how to install the Planning and Consolidation clients in a Terminal Services

(TS) or Citrix Server deployment

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

71 Terminal Services Home Directories

2012-06-13 CUSTOMER 4554

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 userinstall

4 Open a browser and connect to the URL httpltPC_serverportgtsapbpcweb

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 userexecute 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 Iexploreexe http(s)

ltServerNamegt-NetBIOS or FQDNsapbpcweb

To publish Planning and Consolidation Administration CProgram FilesPC_MS

BPCAdminMainexe

74 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 userrsquos desktop) must be moved to the All UsersDesktop folder

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

74 Creating a Shortcut to the Launch Page

4654 CUSTOMER 2012-06-13

8 Installing SSIS Custom Tasks

This section provides background information and instructions for installing SQL Server Integration

Services (SSIS) for SQL Server 2008 and SQL Server 2012

The Planning and Consolidation Data Manager component supports and uses SSIS Since SQL Server

2008 and SQL Server 2012 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

81 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 Filelistxml 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

OSoftSetupexe ‒ 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 or OSoftSSIS2012_Client on the client machine followed by the SQL Server

version If you want to use SQL 2008 Tasks under the SQL 2012 environment you must install

OSoftSSIS2008_Client on the application server For detailed information see SAP Note 1707410

You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package by extracting

OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPC

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 or

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4754

OSoftSSIS2012_Client for creating a COM+ application For more information see Before You Modify

the SSIS Packages [page 50] and Setup of a COM+ Application on the Application Server [page 51]

Bin folder

This folder contains the following components

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCCachedll Planning and Consolidation Cache file

BPCDataFlowPackagedll or BPCDataFlowPackage2012dll

BPCDMdll

BPCDMTaskMaindll COM+ component

BPCFilePreviewdll

BPCGacUtil_20exe System File

BPCGacUtil_40exe System File

BPCImpersonatordll Planning and Consolidation Impersonator

BPCLogicdll

BPCScriptdll

BPCServerZipdll

BPCServiceResdll

BPCTransferMembersdll

BPCWriteBackdll

InteropDTSdll

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

4854 CUSTOMER 2012-06-13

Name Remark

OSoftAdminServerdll

OSoftAuditdll

OSoftComLibServerdll

OSoftCommonResQrydll

OSoftConfigurationdll

OSoftCustomXMLSvrdll

OSoftDatabaseADMINdll

OSoftDatabaseSYSADMINdll

OSoftDatabaseSYSADMINDMdll

OSoftDatabaseUSERdll

OSoftDMDTSXExecutedll or OSoftDMDTSXExecute2012dll

OSoftDMTaskFormdll

OSoftDMTaskMaindll

OSoftDMToolsdll

OSoftFileManagedll

OSoftLoggingdll

OSoftLogWriterdll

OSoftMetaDatadll

OSoftSQEdll

OSoftSystemConfigdll

OutlookSoftconfig Configuration file to connect DB server

XceedCompressiondll XceedZip file

XceedCompressionFormatsdll XceedZip file

XceedFileSystemdll XceedZip file

XceedZipdll XceedZip file

Config folder

This folder has FileListxml 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 FileListxml 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

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4954

OSoftSetupexe

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

NOTE

If you installed the OSoftSSIS2008_Client or OSoftSSIS2012_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

Resources Folder

This folder contains the BPCServicesdll and BPCServiceUIdll files which contain resource text

Only English resources are included for the SSIS custom tasks

82 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

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008 and 2012 respectively

8 Installing SSIS Custom Tasks

82 Before You Modify the SSIS Packages

5054 CUSTOMER 2012-06-13

Name Remark

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012 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

lthellipgtOSoftSSIS2008_Clientbin or lthellipgtOSoftSSIS2012_Clientbin

On the Planning and Consolidation application server

ltdrivegtWebsrvrbin

2 Paste these files into the folder 100DTSTasks for SQL Server 2008 or into 110DTSTasks for

SQL Server 2012 For example if you install your SQL 2008 server or R2 on CProgram Files

Microsoft SQL Server paste all files into the CProgram Files (x86)Microsoft SQL Server

100DTSTasks folder

In Integration Services set the property Run64BitRunTime to True

83 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 or OSoftSSIS2012_Client on the

application server

8 Installing SSIS Custom Tasks

83 Setup of a COM+ Application on the Application Server

2012-06-13 CUSTOMER 5154

Typographic Conventions

Example Description

ltgt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example Enter your ltUser Namegt

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 httpwwwsapcom

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

5254 CUSTOMER 2012-06-13

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

  • SAP BusinessObjects Planning and Consolidation 100
    • Table of Contents
    • 1 Introduction
      • 11 SAP Notes for the Installation
      • 12 Naming Conventions
        • 2 Installing Planning and Consolidation Servers
          • 21 Basic Steps
          • 22 Prerequisites
          • 23 Before Starting the Planning and Consolidation Server Installation
          • 24 Logging on to Servers
          • 25 Service-level Accounts
          • 26 Standard and Advanced Settings
          • 27 Installing the Prerequisites
            • 271 Installing the Prerequisites ndash Basic Steps
            • 272 Installing the Operating System
            • 273 Installing the SQL Server
            • 274 Installing Analysis Services
            • 275 Installing the Anti-Cross Site Scripting Library
              • 28 Installing on a Single Server
              • 29 Installing the Server in a Multiserver Configuration
                • 3 After Installing Planning and Consolidation Servers
                  • 31 Post-Installation Steps
                  • 32 Connecting to Solution Manager Diagnostics
                  • 33 Configuring the Planning and Consolidation NET Application Servers
                  • 34 Post-Installation Optional Configuration Steps
                    • 341 Enabling the Management Console
                    • 342 Setting Up ODBC Logging in IIS for the Default Web Site
                    • 343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2
                    • 344 Removing Default Access to the Console
                    • 345 Management Console Access Control
                    • 346 Using Client Certificates
                        • 4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office
                          • 41 Installing the Administration Client
                          • 42 Installing the EPM Add-in
                          • 43 Using the Client Auto Update Program
                            • 5 Connection Issues
                              • 51 Checking for Open Ports
                              • 52 Proxy Server and Firewall Issues
                                • 6 Installing Planning and Consolidation with Two Active Directory Domains
                                • 7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
                                  • 71 Terminal Services Home Directories
                                  • 72 System Requirements
                                  • 73 Installing Planning and Consolidation
                                  • 74 Creating a Shortcut to the Launch Page
                                    • 8 Installing SSIS Custom Tasks
                                      • 81 Composition of SSIS Custom Task Installation
                                      • 82 Before You Modify the SSIS Packages
                                      • 83 Setup of a COM+ Application on the Application Server
                                          • Copyright and trademarks
Page 6: Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

This page is left blank for documents that are printed on both sides

1 Introduction

The SAP BusinessObjects Planning and Consolidation Installation Guide is intended for System

Administrators who perform Planning and Consolidation server and Administration client

installations It contains everything you need to know about installing the prerequisite components

and the server and client software

The installation package contains a full installation program While we do not offer a software upgrade

for this release we provide detailed instructions on how to migrate your existing environments For

more information see the Upgrade Guide which is available on SAP Service Marketplace at http

servicesapcominstguidesEPM-BPC Planning and Consolidation 100 version for the Microsoft platform

For more information about the Planning and Consolidation Office client software see the SAP

BusinessObjects EPM solutions add-in for Microsoft Office help

New Installation Program Features in 100

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

11 SAP Notes for the Installation

Read the following SAP Notes before you start the installation These SAP Notes contain the most

recent information on the installation as well as corrections to the installation documentation Make

sure that you have the up-to-date version of each SAP Note which you can find in the SAP Service

Marketplace at the Internet address httpservicesapcomnotes

1 Introduction

11 SAP Notes for the Installation

2012-06-13 CUSTOMER 754

SAP Note Number Title Comments

1584890 Documentation Addendum Contains information that does not appear in the application help of Planning and Consolidation 100 version for the Micrososft platform

1733053 SAP Planning and Consolidation 100 SP08 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP08This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1689792 SAP Planning and Consolidation 100 SP07 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP07This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1665656 SAP Planning and Consolidation 100 SP06 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP06This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1643037 SAP Planning and Consolidation 100 SP05 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP05This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1620464 SAP Planning and Consolidation 100 SP04 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP04This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1601213 SAP Planning and Consolidation 100 SP03 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP03This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1591848 SAP Planning and Consolidation 100 SP02 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP02This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1 Introduction

11 SAP Notes for the Installation

854 CUSTOMER 2012-06-13

SAP Note Number Title Comments

1573539 SAP Planning and Consolidation 100 SP01 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP01This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

12 Naming Conventions

In this document the following naming conventions apply

Variable Description

ltPC_serverportgt Server name or IP address and port number of SAP Planning and Consolidation application location

ltdrivegt The drive where SAP Planning and Consolidation is installedThe default for this is CPC_MS

1 Introduction

12 Naming Conventions

2012-06-13 CUSTOMER 954

This page is left blank for documents that are printed on both sides

2 Installing Planning and Consolidation Servers

This section includes the basic steps for installing a Planning and Consolidation server the prerequisites

and what to do before during and after the server installation

21 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 at httpservicesapcominstguidesepm-bpc 100 version for the Microsoft platform

2 Perform the tasks in the Before Starting the Planning and Consolidation Server Installation [page 13] section

including installing all prerequisites

3 From the application server install the Planning and Consolidation server See Installing Planning and

Consolidation on a Single Server [page 24]

NOTE

You must install both Planning and Consolidation 100 as well as the most recent Planning

and Consolidation 100 Support Package available from the SAP Service Marketplace at

httpservicesapcomswdc Software Downloads Support Packages and Patches A - Z Index

B SAP BPC FOR MICROSOFT SBOP PC 100 FOR MICROSOFT Comprised Software Component

Versions SAP CPM BPC 100 M Windows Server on x64 64bit

4 If you have multiple machines see Installing the Server in a Multiserver Configuration [page 26]

5 Perform the steps in the section After Installing Planning and Consolidation Servers [page 27]

22 Prerequisites

The following table describes the software you need to install before installing the Planning and

Consolidation server and the minimum versions required

NOTE

A list of the supported operating systems and database systems is also available in the Product

Availability Matrix on SAP Service Marketplace at httpservicesapcompam Search on

Planning and Consolidation

2 Installing Planning and Consolidation Servers

21 Basic Steps

2012-06-13 CUSTOMER 1154

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 or

Data Center with or without Hyper-V

NOTE

The operating system must be configured with NTFS

Relational Database Microsoft SQL Server 2008 Enterprise Edition Microsoft SQL Server 2008 R2 (Gemini) Enterprise Edition Microsoft SQL Server 2012 Enterprise Edition

OLAP Database Microsoft SQL Server 2008 Enterprise Edition ‒ Analysis Server Microsoft SQL Server 2008 R2 Enterprise Edition ‒ Analysis Server Microsoft SQL Server 2012 Enterprise Edition ‒ Analysis Server

Data Integration Microsoft SQL Server 2008 Enterprise Edition ‒ SQL Service Integration Services

Microsoft SQL Server 2008 R2 Enterprise Edition ‒ SQL Service Integration Services

Microsoft SQL Server 2012 Enterprise Edition ‒ SQL Service Integration Services

Other Requirements MSXML 40 SP2 or later ADOMDNET

ADOMDNET 100 when running SQL Server 2008 or 2008 R2 ADOMDNET 110 when running SQL Server 2012

SQL Server software components NET 40 IIS 75 or IIS 70

(Included in your Operating System IIS 75 is required for Windows 2008 R2 editions)

Anti-Cross Site Scripting Library 42This component must be downloaded before installing the server The server installation program asks for the path of each file and copies the files into the appropriate Planning and Consolidation path

Microsoft Visual C++ 2005 Runtime Libraries SP1 Microsoft Access Database Engine 2010 64bit VMWare ESX 3x or ESX 40

(Required only if a landscape deployment strategy using virtualization technologies is planned)

NOTE

MSXML 40 SP2 ADOMDNET 100 and Microsoft Visual C++ 2005 Runtime Libraries SP1 are included with the installation program but not installed automatically

RECOMMENDATION

For SQL Server 2008 only we recommend the installation of Microsoft SQL Server 2008 SP1

(or later) cumulative update package 6 or higher to solve a problem with incorrect periodic

2 Installing Planning and Consolidation Servers

22 Prerequisites

1254 CUSTOMER 2012-06-13

values being returned with calculated accounts For more information see SAP Note number

1429246 which also contains download information

We recommend SQL Server 2008 (or R2) Enterprise Edition or SQL Server 2012 Enterprise

Edition for the OLAP database to support proactive cache and cube partitioning It is

technically possible to use SQL Server 2008 (or R2) Standard Edition or SQL Server 2012

Standard Edition for data integration servers but we do not recommend this

23 Before Starting the Planning and Consolidation Server Installation

You must perform the following tasks before starting your Planning and Consolidation server

installation

Install all the prerequisite software including all of the latest Microsoft hotfixes For more

information see Installing the Prerequisites [page 17]

If you access your application through a firewall verify with your network administrator which

TCP ports to choose during the installation By default port 80 is the setting for standard http

access and port 443 is the setting for https access If you require a service to listen on a different

port you can specify it during the installation program in Advanced Settings See Standard and Advanced

Settings [page 16]

Make sure all required server ports are open and that there is communication between the physical

servers on which you are going to install the server types See Checking for Open Ports [page 41]

Set up the required service accounts that you need to install the Planning and Consolidation server

See Service-Level Accounts [page 15]

The sample environment EnvironmentShell has been updated in this version of Planning and

Consolidation and automatically overwrites the previous version If you have made any

modifications to EnvironmentShell that you want to keep make a copy of it before continuing

with the installation

If you have the URLScan and IIS Lockdown tools installed on your application server you must

reinstall them

Disable your anti-virus software program After the installation when you enable the program

turn off Script Blocking

If a version of Planning and Consolidation on a NetWeaver platform exists uninstall it before you

install Planning and Consolidation 100 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 fsntfsV

All servers in a multiserver environment must be members of the same domain

2 Installing Planning and Consolidation Servers

23 Before Starting the Planning and Consolidation Server Installation

2012-06-13 CUSTOMER 1354

In a multiserver environment the installing ID must be a domain user ID We recommend that

you do not log on to the servers using a local server user ID even if the user ID is a member of the

Administrator group on the server This way you have the proper authority to install software and

to modify the Component Services See Logging On to Servers [page 14]

You must determine the IP addresses or server names for all servers before installing Planning and

Consolidation We recommend that you use static IP addresses

IIS must be enabled

If the application server is not able to copy files to the database server during the installation because

of port access reasons (DMZ WORKGROUP or nontrusted domain authentication failures) do

the following

1 Copy the EnvironmentShell database file ServerEnvironmentShelldb10 from the

Planning and Consolidation installation program to any folder on the SQL server (for example

cEnvironmentShelldb10)

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 cEnvironmentShelldb10)

Install the Anti-Cross Site Scripting Library which provides protection to Web-based applications

against Cross-Site Scripting (XSS) attacks See Installing the Anti-Cross Site Scripting Library [page 24]

24 Logging on to Servers

When installing in a multiserver environment you must use a domain user ID to log on to all

components

A local server user ID is a member of the Administrator group on the server A domain user ID is a

member of the Administrator group of a domain to which the server belongs or a member of the

Administrator group on the local server

Errors may display during the installation program and in the diagnostic program if the installing user

is not assigned to the Administrator group directly but is assigned to a group with Administrator rights

You can ignore these messages

NOTE

If you change the password used to install Planning and Consolidation you must change the

password for the applicable Planning and Consolidation service To do this go to Server Manager

on the application server and select Server Reset Logon Credentials For more information see

the SAP Planning and Consolidation Operations Guide in httpservicesapcominstguidesepm-bpc

100 for the Microsoft Platform SBOP Plan amp Consol 100 MS Administrators Guide

2 Installing Planning and Consolidation Servers

24 Logging on to Servers

1454 CUSTOMER 2012-06-13

25 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

PrerequisitesPlanning and Consolidation 100 has the following Windows services

BPC SendGovernor which manages Microsoft Analysis Service locks to ensure consistent performance

and avoid deadlocks

BPC ServiceManager which manages the System Landscape Directory (SLD) service logging service

and global caches

BPC CTS ServiceManager which listens and handles CTS import requests from the CTS+ transport

management system

Since these services should be able to access to the FileShare server an Admin account is assigned

automatically to the service during the installation of the Planning and Consolidation server program

Even though an Admin account has been assigned to the server correctly the services may fail to start

with the error message

Could not start the BPC SendGovernor service

The reason for this is that the Admin account is not registered as a service

When installing a service to run under a domain user account the account must have the right to

logon as a service on the local machine This logon right strictly applies only to the local computer

and must be granted in the Local Security Policy

To edit the Local Security Policy of the computer you want to define the logon as a service

permission perform the following actions

1 Start the Local Security Settings Microsoft Management Console (MMC) snap-in

2 Expand Local Policies and then click User Rights Assignment

3 In the right-hand pane right-click Log on as a service and then click Security

4 Add the user to the policy and click OK

5 Close the Local Security Settings MMC snap-in

For more details see How to Troubleshoot Service Startup Permissions http

supportmicrosoftcomkb259733

FeaturesDuring the installation enter user IDs and passwords for the following user types

System Admin ID

This ID is read-only and is the same as the installation user ID that is the system displays the ID

on the installation screen but you cannot modify it This ID allows access to code that provides

2 Installing Planning and Consolidation Servers

25 Service-level Accounts

2012-06-13 CUSTOMER 1554

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 readwrite 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

26 Standard and Advanced Settings

The following tables describe the standard and advanced settings for the installation program After

the server is installed you can change these settings using the Server Manager

NOTE

When defining server names the name refers to the NetBIOS name IP address and fully qualified

domain names (FQDN)

Standard Settings

Standard settings are typically used for a single-server environment The following table describes each

setting

Server Option Value Description

SQL Database server name The name of the SQL DB server

OLAP server name The name of the OLAP server

File Share server name The default value is the name of the File Share server that should be the computer name

Local data path Where the data files are saved on the File Share server By default this is CPC_MSData

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

Server Option Value Description

SQL Server Name The name of the SQL DB server Defaults to the local server

2 Installing Planning and Consolidation Servers

26 Standard and Advanced Settings

1654 CUSTOMER 2012-06-13

Server Option Value Description

Instance name The SQL instance name If left blank the default instance is used

Port number The default port number for the SQL Server is 1433

Provider The only available value is SQL

Local path for EnvironmentShell 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 CPC_MSData

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 changesSee the Kerberos authentication settings section in the SAP Library Server Manager Guide on httpservicesapcominstguidesEPM-BPC

100 for the Microsoft Platform

Scheduler Server Name The name of the server used for scheduling usually the application server for example GMPV50072862B If you have multiple application servers select the appropriate one

NOTE

If the primary server stops working you must manually configure your application server database to froward requests to another application server

27 Installing the Prerequisites

271 Installing the Prerequisites ndash Basic Steps

Before installing your Planning and Consolidation server you must install the prerequisite Microsoft

software the operating system IIS SQL server analysis services ADOMDNET and MSXML This

section provides guidance on installing each component For specific versions required see

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 1754

Prerequisites [page 11] and the Product Availability Matrix on the SAP Service Marketplace at http

servicesapcompam Search on Planning and Consolidation

NOTE

To ensure a successful installation you must install the software in the order listed in this

procedure

Check all third-party infrastructure services to ensure that they are functioning and that their

authentication models are documented (stated) since you need to reference this information

during the installation These third-party services include IIS OLAP service SQL services and

Active Directory (AD)

We recommend not installing Microsoft Office on the application server

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

(UMCexe) on the Planning and Consolidation CD in a folder called UMC_100_INSTALLER When

you run the installation package the wizard guides you through the following steps

1 Choose a language for the UMC install wizard to use

2 Check that the prerequisite check status is Succeeded and click Next

3 When you are ready to install the UMC click Next on the welcome screen

4 Click I accept the License Agreement and then Next

5 Choose the destination directory for the UMC installation and click Next

6 Select the languages that you wish to install

7 Select the features that you want to install (POAFHelper dotnet is mandatory for Planning

and Consolidation)

8 On Start Installation click Next to complete the installation

2 Install the required operating system on the single-server computer or on each physical server for

a multiserver configuration See Installing the Operating System [page 19]

3 Install the latest service pack for your operating system To install this service pack go to http

wwwmicrosoftcom

4 From your operating systems media install IIS

5 From your SQL Server media install SQL Server and its required service packs and hot fixes See

Installing SQL Server [page 19]

6 From your SQL Server media install Analysis Services Enterprise Edition and its required service

packs and hot fixes See Installing Analysis Services [page 23]

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

1854 CUSTOMER 2012-06-13

7 On your application server install ADOMDNET The Planning and Consolidation zip file contains

the ADOMDNET installation package in the following locations

For SQL Server 2008 mdash BPC SetupServerSQLSERVER2008_ASADOMD10_x64msi

For SQL Server 2012 mdash BPC SetupServerSQLSERVER2012_ASADOMD11_x64msi

8 On your application server install MSXML 40 Service Pack 2 or later

The MSXML 40 SP2 installation package is contained in the Planning and Consolidation zip file at

the following location BPC SetupServermsxmlmsi

9 On your application server install Microsoft Visual C++ 2005 Runtime Libraries SP1

The Microsoft Visual C++ 2005 SP1 installation package is contained in the Planning and

Consolidation zip file at the following location BPC SetupServervcredist_x64exe

NOTE

The version of vcredist_x64exe in BPC SetupServer has been updated to 8061000 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 httpwwwmicrosoftcomdownloadsen

detailsaspxFamilyID=C06B8369-60DD-4B64-A44B-84B371EDE16Dampltdisplaylanggt=en

272 Installing the Operating System

Before installing the operating system make sure that you configure your server for NTFS

For a list of languages that are supported see the Product Availability Matrix on the SAP Service

Marketplace at httpservicesapcompam Search on Planning and Consolidation

Planning and Consolidation can support all servers with an operating system in any language

NOTE

Currently Planning and Consolidation does not support an operating system in bi-directional

languages such as Hebrew

ProcedureIf you are installing IIS 70 or 75 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

273 Installing the SQL Server

PrerequisitesDuring the installation procedure you have the opportunity to specify the location of the

EnvironmentShell database file Check that it is possible to access EnvironmentShell from the location

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 1954

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 CEnvironmentShelldb10) 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 a 2008 2008 R2 and 2012 SQL Server

SQL Server Considerations

We recommend installing all required components in sequence For example install the Operating

System (Windows Server) then enable IIS and ASPNET and install any Windows Server service

packs

IIS and NET Framework 40 are required on your application server

NOTE

If you encounter a 500 HTTP Error when trying to connect to the Planning and Consolidation

Web Client refer to Microsoft Support articles 2520479 and 2468871 for assistance

To reinforce security we recommend that you install the SQL server and SSAS components to a

nondefault instance of SQL Server

General Installation Steps

1 Launch the SQL Server Setup program entering a product key if necessary and accepting the license

terms

2 Choose Install to install the SQL support files

3 In Feature Selections select instance and shared features as indicated in the SQL Server Component

Options section below then choose Next

4 Review disc space requirements then choose Next

5 In Server Configuration Perform the following actions

1 In the Service Accounts tab enter a Planning and Consolidation sysadmin account for the SQL

Server Database Engine and the SQL Server Analysis services This is required so that the Planning

and Consolidation sysadmin can create and process the Planning and Consolidation database

because the Microsoft SQL server tries to back up or restore database with the privileged

account This account is also required during Backup Environment and Restore Environment in the

Server Manager

For a single-server environment this account is also required if the backup file is located in a

different domain machine because SQL tries to access the folders and files with this account

For the a multiple-server environment SQL server retrieves the information of backup file

from the application server and the account requires the folder access privilege for the

application server

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2054 CUSTOMER 2012-06-13

To ensure that you have the complete access privileges we recommend the Planning and

Consolidation sysadmin for this service account

2 In the Collation tab set the collation settings to SQL_Latin1_General_CP1_CI_AS

Choose Next

6 Set Database Engine Configuration options then choose Next

We recommend you choose Mixed mode (Windows authentication and SQL authentication) This allows you

to use a restrictive SQL ID that works with the drill-through feature If you must restrict SQL

authentication for security reasons you can define a specific parameter in your drill-through

queries If you do not need drill-through support or use it without leveraging SQL authentication

you can install the SQL Server in Windows-only mode

7 Accept the Analysis Services Configuration default options and the remaining default options of the

installation program

8 Choose Install to begin the installation with the options you have set

SQL Server Component 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

Server Component What to Install

SQL Server Database Engine Services

SSAS Server Analysis Services

Application Server The following Shared Features Client Tools Connectivity Integration Services Client Tools SDK

Custom Settings for the SQL Server

As of version 100 Planning and Consolidation supports the following new features for SQL Server 2008

SQL Server 2008 R2 and SQL Server 2012

Process Dimension

It is now possible to process a dimension with multiple selections At processing time the process

dimension module makes changed or added information for each dimension and process for all selected

dimensions and cubes in parallel

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 2154

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

NOTE

Setting 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 tblFactWBltappgt table

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 Microsoftreg SQL Servertrade

20052008 which you can download from wwwmicrosoftcom (search on ldquoTable Partitioningrdquo to find

all relevant articles)

After Installing SQL Server 2008 SQL Server 2008 R2 and SQL Server 2012

From SQL Server Configuration Manager confirm that the SQL Server Browser service is

running The browser service is required for Planning and Consolidation

From SQL Server Configuration Manager do the following

1 Select Protocols for ltInstanceNamegt then double-click TCPIP from the right side of the window

2 When prompted for the TCPIP Properties select IP Addresses You see two IPs that indicate the

localhost and external network interface machine

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2254 CUSTOMER 2012-06-13

3 If you want to use IP1 which indicates Server IP set Enabled to Yes and specify the TCP Port as

desired

4 Delete 0 from TCP Dynamic Ports Set IPAll - TCP Ports as desired (for example 1533)

RECOMMENDATION

We do not recommend using dynamic ports

In an SQL server the default instance has a listener which listens on a fixed port (TCP

port 1433) However for the named instance the port on which the SQL server listens is

random and dynamically selected when the named instance of the SQL server starts This

recommendation prevents any conflict problems

From the SQL Server Configuration Manager specify the client protocol options for the application

server

1 Select Client Protocols from the SQL Native Client Configuration folder

2 From the right side of the window double-click TCPIP The TCPIP 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

NOTE

We 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

274 Installing Analysis Services

ProcedureAfter you install SQL Server and its required service packs and hotfixes you must install SQL Server

Analysis Services and its required service packs and hotfixes

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 2354

NOTE

If you have migrated your Analysis Services repository to the SQL Server back up the database

that contains the repository before installing this release

To install Analysis Services for SQL Server 2008 SQL Server 2008 R2 or SQL Server 2012 follow the steps

and guidelines in httptechnetmicrosoftcomen-uslibraryms143219aspx

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 httpwwwmicrosoftcomdownloads

detailsaspxFamilyID=3be0488d-e7aa-4078-a050- ae39912d2e43ampdisplaylang=en

275 Installing the Anti-Cross Site Scripting Library

Procedure

Before installing Planning and Consolidation servers you must download the Anti-Cross Site Scripting

Library (version 42 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 AntiXSSLibraryDLL from the Microsoft Web

site at httpwwwmicrosoftcomdownloadendetailsaspxid=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 AntiXssLibrarydll

28 Installing on a Single Server

When you install all Planning and Consolidation server components on a single server you should

consider the following issues

Make sure the server has a minimum of 800 MB of hard disk space

Additional environment installations require more free disk space which is a minimum of two

times the uncompressed size of the environment files

When you install Planning and Consolidation on a single-server the system adds the following server

components

SQL Server

SQL Server Analysis Services (SSAS)

Application Server

FileShare server

Procedure

To install Planning and Consolidation on a single server take the following steps

1 Exit all Windows programs

2 Installing Planning and Consolidation Servers

28 Installing on a Single Server

2454 CUSTOMER 2012-06-13

2 Log on to the server with a local server user ID or domain user ID For more information see Logging

on to servers [page 14]

3 Make sure all prerequisite software is installed on the server For more information see Installing

the Prerequisites [page 17]

4 Obtain SAP Planning and Consolidation from the Downloads SAP Installations amp Upgrades area of

SAP Service Marketplace then extract the files and run StartUpexe

5 From the Server Install screen select Install the Planning and Consolidation server

6 From the Welcome screen choose Next

7 From the License Agreement page choose I accept the terms of the license agreement then choose Next

8 From the Installation Method page accept the default Single machine enter a system ID for the system

landscape directory (SLD) and choose Next

NOTE

Entering a system ID of the SLD is only required if you have a SAP Solution Manager license

If you do not have a SAP Solution Manager license you can leave this field empty

9 From the Authentication Method page choose the desired authentication method and choose Next

10 If you have chosen SAP BusinessObjects User Management System in the previous screen on the CMS

Authentication page enter the information required to log on to CMS as an administrator

The following information is required

Field Description

System name CMS system name (server nameport number) for example CMSServer6400

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

11 After entering the CMS administrator authentication details choose Next

12 From the Service type accounts page enter service-level account user IDs and passwords See Service-

Level Accounts [page 15]

13 After defining the IDs and passwords choose Next

14 From the Server Information page (see Standard and Advanced Settings [page 16]) do one of the following

Review the standard settings and choose Next

To set advanced settings choose the Advanced Settings button Enter the desired information

and choose Next

2 Installing Planning and Consolidation Servers

28 Installing on a Single Server

2012-06-13 CUSTOMER 2554

15 Specify the location and name of AntiXssLibrarydll See Installing the Anti-Cross Site Scripting Library [page

24]

Choose Next

16 Select destination folders for Programs and Data The Data files include Webfolders and FileDB

(published reports) and should be installed on a separate drive in a production environment This

recommendation reduces the hard disk IO time and helps to speed up SQL commands

Accept the defaults or make your selections then choose Next

17 Select the default values for the Web client The values are used to determine the default language

and region for the Web client when you connect to it You can change the values in the Planning

and Consolidation Server Manager

18 The installation process takes a few moments When it is complete choose Exit

19 A prompt is displayed to restart your computer Select OK to restart

20 Perform the steps in After Installing Planning and Consolidation Servers [page 27]

29 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 24]) with the following

exceptions

On the Installation Method page do not accept the default instead choose Network Load Balancing

environment With this option there is an additional choice to Include sample environment (required on only

one of the application servers) This is because when you install the application server it connects to the

database server and creates the sample environment (EnvironmentShell) Installing the sample

environment is required on only one application server and you may choose which one

In the Virtual Name field enter the virtual IP address virtual name in the default properties

2 Installing Planning and Consolidation Servers

29 Installing the Server in a Multiserver Configuration

2654 CUSTOMER 2012-06-13

3 After Installing Planning and Consolidation Servers

31 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 28]

2 Configure the Planning and Consolidation NET and application server to ensure that it and its

related services function properly and reliably For more information see Configuring the Planning and

Consolidation NET Application Server [page 29]

3 Optional configuration steps [page 30]

1 To ensure proper functioning of the Management Console create an SQL user and modify

the System DSN and IIS to reflect those user credentials See Enabling Management Console [page

30]

2 Configure custom ODBC logging for the default Web site For details of how to configure

custom logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web

Site [page 31]

3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC

Data Source [page 32]

4 Modify the default access rights to the Management Console By default users in Active

Directory can access the Management Console with whatever rights they have been granted

on the server For information about removing default access and creating a group that can

access the console see Removing Default Access to the Console [page 32]

5 Add authorized users or groups to the group that can access the Management Console We

recommend that you only grant Management Console access to system administrators

Planning and Consolidation users should not have any access For more information see

Management Console Access Control [page 33]

6 Configure the use of client certificates for authentication See Using Client Certificates [page

34]

4 Take the following steps to set up security

If you are defining security and application structure continue with step 5

3 After Installing Planning and Consolidation Servers

31 Post-Installation Steps

2012-06-13 CUSTOMER 2754

If you want to designate someone other than the system administrator to manage security

and application structure log on to EnvironmentShell designate a user as a Primary

Administrator

This user must have Administration ‒ Environment and Security ‒ Define User task rights

so that he or she can add and delete environments and define user security

The Primary Administrator can continue with the next step (5)

5 From the machine on which you administer Planning and Consolidation install the

Administration client See Installing the Administration Client [page 37]

6 Start Planning and Consolidation Administration from the launch page

7 Select Connection Wizard and log on to EnvironmentShell

8 Create a new environment using EnvironmentShell as the source

9 Log on to the newly created environment and set up users teams and task profiles (You must

set up task profiles since there is no access to Planning and Consolidation tasks)

10 Set up your data access profiles and add users (or teams) to one or more data access profiles (You

must complete this step since there is no access to dimensions or members)

NOTE

To allow users to request and query large amounts of data you can edit the metabasexml file located

at CWindowssystem32inetsrv Set the following parameters to the stated values

ASPBUFFERINGLIMIT = 10485760

MAXREQUESTENTITYALLOWED = 10485760

32 Connecting to Solution Manager Diagnostics

NOTE

You only need to perform the steps in this section if you have a SAP Solution Manager licence

The diagnostics functions in SAP Solution Manager allow identification analysis and resolution of

problems This procedure provides the steps required to connect Planning and Consolidation to

Solution Manager Diagnostics

Procedure

1 Install the Diagnostics Agent according to SAP Note 1234387 on all servers where application servers

are installed

NOTE

Installation files for Diagnostics Agent are available on Service Marketplace by navigating to

Support Packages and Patches mdash Entry by Application Group SAP Technology Components SAP

SOLUTION MANAGER SAP SOLUTION MANAGER 70 EHP 1 Entry by Component Agents

for managed systems DIAGNOSTICS AGENT 711

3 After Installing Planning and Consolidation Servers

32 Connecting to Solution Manager Diagnostics

2854 CUSTOMER 2012-06-13

Download the installation file based on the 64-bit Windows Server system landscape

2 To access the DBA Cockpit you must create a user account with sufficient rights on all Windows

Servers where Microsoft SQL Server is installed Do the following

1 Start Computer Management then select Action New User

2 Create a new user

3 Right-click on the user then choose Properties On the Member Of tab select Add

4 Add the group SQLServerltReleasegtSQLAgentUser$ltDomain or hostnamegt$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 httpsservicesapcom~sapidb011000358700000074392009E and follow

the chapters that apply to Planning and Consolidation

33 Configuring the Planning and Consolidation NET Application Servers

Procedure

Modifying machineconfig Files

To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock

occurrences that would cause the application server to ldquosleeprdquo and not process anymore you can

modify the machineconfig file which resides in the WINDOWSMicrosoftNETFramework64

v4030319Config directory

1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to

specify whether to automatically configure settings to achieve optimal performance based on the

machine configuration You can set this attribute to True or False

For more information see httpmsdnmicrosoftcomen-uslibrary7w2sway1aspx

2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the

Planning and Consolidation application) or Machineconfig (for all applications including

Planning and Consolidation) to ensure the validationKey and decryptionKey keys have the same

value on all application servers This way when the authentication cookie is checked the

authentication ticket used on one server can still be valid on another server

For more information and sample Visual Basic code for generating random key values see http

msdnmicrosoftcomen-uslibraryms998288aspx

3 After Installing Planning and Consolidation Servers

33 Configuring the Planning and Consolidation NET Application Servers

2012-06-13 CUSTOMER 2954

paght000007_webfarmdeploymentconsiderations and httpmsdnmicrosoftcomen-us

libraryms998310aspx

34 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 30]

2 Configure custom ODBC logging for the default Web site For details of how to configure custom

logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page

31]

3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC Data

Source [page 32]

4 Modify the default access rights to the Management Console By default users in Active Directory

can access the Management Console with whatever rights they have been granted on the server

For information about removing default access and creating a group that can access the console

see Removing Default Access to the Console [page 32]

5 Add authorized users or groups to the group that can access the Management Console We

recommend that you only grant Management Console access to system administrators Planning

and Consolidation users should not have any access For more information see Management Console

Access Control [page 33]

6 Configure the use of client certificates for authentication See Using Client Certificates [page 34]

341 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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3054 CUSTOMER 2012-06-13

NOTE

Without these updates the Management Console does work but some functionality (specifically

User Activity and Service Status) does not work as expected

Should you need to uninstall Planning and Consolidation we recommend that you reset the

Active Log Format field in IIS to W3C Extended Log File Format

342 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 ApplicationHostconfig set the property customLogPluginClsid to the value FF16065B-

DE82-11CF-BC0A-00AA006111E0 Set the logFormat to Custom You can find this in the ltlogFilegt

node in ApplicationHostconfig as shown here

ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0

logFormat=Custom gt

Use the following AppCmds to configure IIS to use ODBC logging for the default Web site

appcmd site set sitenameDefault Web Site

logFilecustomLogPluginClsidFF16065B-DE82-11CF-BC0A-00AA006111E0

appcmd site set sitenameDefault Web Site logFilelogFormatCustom

Configuring ODBC Logging Parameters in ApplicationHostconfig

Configure ApplicationHostconfig to contain the database table information as set up in the Microsoft

Support article specified in the Prerequisites section Configure these settings in the ltodbcLogginggt

node under ltsystemwebServergt

EXAMPLE

ltlocation path=Default Web Sitegt

ltsystemwebServergt

ltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog

userName=Username password=mypassword gt

ltsystemwebServergt

ltlocationgt

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3154

Use the following AppCmds to configure these attributes for the default Web site

appcmd set config Default Web Site sectionodbcLogging

dataSourceBPC_ManagementDSN commitappHost

appcmd set config Default Web Site sectionodbcLogging tableNameBPCLog

commitappHost

appcmd set config Default Web Site sectionodbcLogging userNameUsername

commitappHost

appcmd set config Default Web Site sectionodbcLogging passwordmypassword

commitappHost

NOTE

You cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must

use the SQL Server ODBC driver For more information see the Microsoft Knowledge Base article

931202 The requirements for using the ODBC logging feature in IIS

343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2

ProcedureThis procedure describes how to set up an ODBC data source for the Management Console in Windows

Server 2008 or Windows Server 2008 R2

Proceed as follows

1 Open ODBC Connection Manager

2 On the System DSN tab page add a new DSN

Choose Add

Choose SQL Server as the driver

Choose Finish

3 In the Name and Description fields enter BPC_ManagementDSN

4 In the Server field enter the name of your SQL Server Choose Next

5 Leave the default settings and choose Next

6 Choose the Change the default database to field and enter AppServer Choose Next

7 Leave default settings and choose Next

8 Choose OK

344 Removing Default Access to the Console

NOTE

If you have chosen SAP BusinessObjects User Management System in the installation screen you

do not need to remove or configure access because the Management Console service always runs

with the System Admin ID account which is a member of the Administrators group

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3254 CUSTOMER 2012-06-13

ProcedureTo remove default access to the Management Console and create a group that does have access to the

console use the procedure described below

NOTE

Create your Management Console administrative group either on the server that hosts the

Management Console or in the Active Directory

1 In the context menu of the servers My Computer icon choose Manage

2 In the Computer Management dialog box choose Local Users and Groups Groups

NOTE

Alternatively you can perform analogous steps in Active Directory

3 In the 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

NOTE

This step is a necessary precursor to the completion of this procedure

10 In the Security dialog box click Copy to ensure that the System group retains its privileges

11 Remove access to the Management Console from all groups that should not have it

12 Choose Authentication in the center pane then disable Windows authentication

ResultUsers who have not been granted access to the Management Console can still open the Management

Console Web page but it contains no data or menu options This does not affect the access that a user

would otherwise have to Planning and Consolidation

345 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 32] Their rights in

Active Directory determine what they can access in the Console

By default any member of the Administrators Active Directory group on the application server or

domain has full access to all of the features of the Console except the Planning and Consolidation

logging area Access to Planning and Consolidation logging is controlled within the Planning and

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3354

Consolidation Administration Client task security The user must be granted View system logs task

privileges For more information see the SAP Library Planning and Consolidation Administrators Guide in

httpservicesapcominstguidesepm-bpc 100 version for the Microsoft platform

Your IT policy determines whether you grant access by group or user You may wish to create several

levels of Console users (read-only users for example) in your environment

To grant or limit access to users or groups you can add or remove the following privileges from the

areas described in this table

Privilege Rights Management Area

Task Manager and Kill Process Administrators group on application server or domain

Performance Monitor Counters Administrators group on application server or domain Power Users group on application server or domain Performance Monitor Users group on application server

Microsoft Analysis Services performance monitoring

Administrators group on application server or domain

Microsoft SQL Server Monitoring (performance counters and statistics)

Administrators group on application server or domain

346 Using Client Certificates

To enable the use of client certificates in Planning and Consolidation you must follow several manual

steps

NOTE

Planning 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 httptechnetmicrosoftcomen-us

librarycc753810aspx

For more information about configuring the client certificate mapping authentication see http

technetmicrosoftcomen-uslibrarycc732996(WS10)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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3454 CUSTOMER 2012-06-13

This option allows you to use a client certificate or username and password (Basic

authentication) to connect to Planning and Consolidation

2 Enable anonymous authentication

1 In the IIS Manager expand the node of the Planning and Consolidation web site

2 Select the ManagementConsole directory (ltWebsitegtManagementConsole) to open the

ManagementConsole home page

3 Double-click Authentication and enable Anonymous Authentication

4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way

as in step 3

5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the same

way as in step 3

3 Change the web configuration settings

1 Open the ltPC_MSgtWebsrvrWebBPCwebconfig file

2 Find the text clientCredentialType=Windows

3 Change value of clientCredentialType to None (clientCredentialType=None)

4 Open the PC_MSWebsrvrWebPOASBCwebconfig file Repeat steps 2 and 3

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3554

This page is left blank for documents that are printed on both sides

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

The installation of the Planning and Consolidation Administration Client allows administrators to

build and maintain Planning and Consolidation environments and models and administer security

All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions

add-in for Microsoft Office for more information see the SAP BusinessObjects EPM solutions add-in for

Microsoft Office help

NOTE

You must update the Administration Client to the same version as the server

If your PC is on a different domain than your server you must set the Internet Explorer

Security Zone value of the Planning and Consolidation client to prompt for user name and

password Otherwise the Planning and Consolidation Start Page does not display

41 Installing the Administration Client

Prerequisites

NOTE

For a definitive list of system requirements see the Product Availability Matrix on SAP Service

Marketplace at httpservicesapcompam Search on Planning and Consolidation

The following list describes the minimum software requirements

Microsoft Internet Explorer 70 or 80

Microsoft Office 2007 or 2010

NET Framework 20 or higher (install any required NET Framework Hotfixes by referring to

httpsupportmicrosoftcomkb)

Pentium IV (1 GHz CPU)

512 MB RAM

100 MB of free hard disk space in the My Documents folder

20 MB of free hard disk space for the installed Administration files

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

41 Installing the Administration Client

2012-06-13 CUSTOMER 3754

NOTE

We recommend that you install all of the latest Microsoft Windows hotfixes prior to installing

the Administration client For information about which hotfixes to install see http

updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us

ProcedureThe following procedure describes how to install the Administration Client on to an administratorrsquos

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 AddRemove Programs in the Windows Control Panel

3 Point your browser to the Planning and Consolidation Web at httpltPC_serverportgtsap

bpcweb

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

42 Installing the EPM Add-in

The Planning and Consolidation installation media does not contain the EPM addin setup program

You must download the most recent version of the full setup (EPM Add-inexe) from the Service

Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPC

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

43 Using the Client Auto Update Program

If Planning and Consolidation version 100 or later is installed you can use the Client Auto Update

program to set up the server so that it determines if an upgrade for a connecting Administration client

is necessary

The following describes the use of the auto update program for the Administration Client and the EPM

add-in

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

42 Installing the EPM Add-in

3854 CUSTOMER 2012-06-13

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 37]

To use the Client Auto Update program for the Administration Client proceed as follows

1 From the Server Manager select Options Client Options

2 Select Admin Update

3 If users without administrator rights on their machines use the auto update enter an administrator

ID and password in the Admin ID and Admin password fields respectively The Admin ID should be a

member of the local administrators group on all the computers running the auto update This

setting is not needed if all users have administrator rights on their machines

4 Select Update

For the EPM Add-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 Optionshellip 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 Market Place (SMP) at httpservicesapcom

All support packages and patches are available from the SMP as a zip file

EPMEXCLCLNTltSPLgtzip is for a support package

EPMEXCLCLNTltSPLgtPltPLgtzip 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 ltSP versiongtmsp

EPM Addin Support Package ltSP versiongtxml

For a patch these files are

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

2012-06-13 CUSTOMER 3954

EPM Addin Patch ltpatch numbergtmsp

EPM Addin Patch ltpatch numbergtxml

2 Unzip the zip file and extract the two files to the application server folder (WebsrvrWebBPC

Installation)

3 From the Server Manager select Options Client Options

The system lists the available packages Select the package that you want to use for the autoupdate

You can set a different update policy for each package listed

EXAMPLE

The following table illustrates some possible situations assuming that you have installed the

first full version (V1)

Available maintenance packages

V2-user updateV3-force updateV4-force updateV5-user update

V5-user update V5-user updateV6-auto updateV7-force update

Minimum Required Version

V4 V4 V7

Notification A prompt tells the user to install maintenance package V4 using the Forced Update behavior

If User Update is enabled the prompt informs the user that maintenance package V5 is available

A prompt tells the user to install maintenance package V7 using the Forced Update behavior

New Version V4 V4 or V5 V7

If you change the update policy for any package click Update to complete the change

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

4054 CUSTOMER 2012-06-13

5 Connection Issues

You may experience connection problems with ports the proxy server or programs and settings that

interact with these components If you have any issues related to connection review the following

recommendations and troubleshooting tips

51 Checking for Open Ports

You must ensure that all required ports are open for inboundoutbound 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 431181836 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

NOTE

You can use the following site to scan for the normal ports It allows you to manually enter a port

number to test

httpwwwmyserverorgportsniffasp

You can change the name of a port

52 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 Explorer Tools Internet Options Connections LAN Settings ) or at the server level

Enabling content filtering on the proxy server or firewall may cause connection problems

If external users are having trouble connecting to the server make sure the proxy server connects

using a fully qualified domain name Fully qualified domain names typically resolve both internal

and external IP addresses

Each secure Planning and Consolidation server name must be identified on the proxy server

Proxy servers may or may not require authentication which could conflict with Planning and

Consolidation authentication Do not use authentication on the proxy server The system

5 Connection Issues

51 Checking for Open Ports

2012-06-13 CUSTOMER 4154

synchronizes the user name and password on the remote server with the local user name and

password

NOTE

For more information about setting up an ISA proxy server contact SAP Support to request a

copy of Setting up ISA Proxy Server White Paper

Internet Explorer Settings 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

5 Connection Issues

52 Proxy Server and Firewall Issues

4254 CUSTOMER 2012-06-13

6 Installing Planning and Consolidation with Two Active Directory Domains

To set up a Planning and Consolidation 10 application server in a hosted environment and use your

own domain users follow this procedure In general you install Planning and Consolidation on the

host domain use the host domain account and assign it to the Planning and Consolidation users

SysAdmin Admin and Users Then you accept one way trust (the host domain trusts your domain)

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

6 Installing Planning and Consolidation with Two Active Directory Domains

2012-06-13 CUSTOMER 4354

This page is left blank for documents that are printed on both sides

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

This section describes best practices and instructions for installing Planning and Consolidation in a

Terminal Services or Citrix Server deployment

71 Terminal Services Home Directories

We recommend using Terminal Server home directories rather than using the userrsquos 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

72 System Requirements

The Citrix server should be one of the following systems

XenApp 5 Enterprise

XenApp 5 Platinum

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 37])

73 Installing Planning and Consolidation

Prerequisites

The server installation files have been downloaded from SAP Service Marketplace and installed

Procedure

The following steps outline how to install the Planning and Consolidation clients in a Terminal Services

(TS) or Citrix Server deployment

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

71 Terminal Services Home Directories

2012-06-13 CUSTOMER 4554

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 userinstall

4 Open a browser and connect to the URL httpltPC_serverportgtsapbpcweb

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 userexecute 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 Iexploreexe http(s)

ltServerNamegt-NetBIOS or FQDNsapbpcweb

To publish Planning and Consolidation Administration CProgram FilesPC_MS

BPCAdminMainexe

74 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 userrsquos desktop) must be moved to the All UsersDesktop folder

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

74 Creating a Shortcut to the Launch Page

4654 CUSTOMER 2012-06-13

8 Installing SSIS Custom Tasks

This section provides background information and instructions for installing SQL Server Integration

Services (SSIS) for SQL Server 2008 and SQL Server 2012

The Planning and Consolidation Data Manager component supports and uses SSIS Since SQL Server

2008 and SQL Server 2012 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

81 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 Filelistxml 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

OSoftSetupexe ‒ 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 or OSoftSSIS2012_Client on the client machine followed by the SQL Server

version If you want to use SQL 2008 Tasks under the SQL 2012 environment you must install

OSoftSSIS2008_Client on the application server For detailed information see SAP Note 1707410

You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package by extracting

OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPC

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 or

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4754

OSoftSSIS2012_Client for creating a COM+ application For more information see Before You Modify

the SSIS Packages [page 50] and Setup of a COM+ Application on the Application Server [page 51]

Bin folder

This folder contains the following components

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCCachedll Planning and Consolidation Cache file

BPCDataFlowPackagedll or BPCDataFlowPackage2012dll

BPCDMdll

BPCDMTaskMaindll COM+ component

BPCFilePreviewdll

BPCGacUtil_20exe System File

BPCGacUtil_40exe System File

BPCImpersonatordll Planning and Consolidation Impersonator

BPCLogicdll

BPCScriptdll

BPCServerZipdll

BPCServiceResdll

BPCTransferMembersdll

BPCWriteBackdll

InteropDTSdll

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

4854 CUSTOMER 2012-06-13

Name Remark

OSoftAdminServerdll

OSoftAuditdll

OSoftComLibServerdll

OSoftCommonResQrydll

OSoftConfigurationdll

OSoftCustomXMLSvrdll

OSoftDatabaseADMINdll

OSoftDatabaseSYSADMINdll

OSoftDatabaseSYSADMINDMdll

OSoftDatabaseUSERdll

OSoftDMDTSXExecutedll or OSoftDMDTSXExecute2012dll

OSoftDMTaskFormdll

OSoftDMTaskMaindll

OSoftDMToolsdll

OSoftFileManagedll

OSoftLoggingdll

OSoftLogWriterdll

OSoftMetaDatadll

OSoftSQEdll

OSoftSystemConfigdll

OutlookSoftconfig Configuration file to connect DB server

XceedCompressiondll XceedZip file

XceedCompressionFormatsdll XceedZip file

XceedFileSystemdll XceedZip file

XceedZipdll XceedZip file

Config folder

This folder has FileListxml 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 FileListxml 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

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4954

OSoftSetupexe

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

NOTE

If you installed the OSoftSSIS2008_Client or OSoftSSIS2012_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

Resources Folder

This folder contains the BPCServicesdll and BPCServiceUIdll files which contain resource text

Only English resources are included for the SSIS custom tasks

82 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

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008 and 2012 respectively

8 Installing SSIS Custom Tasks

82 Before You Modify the SSIS Packages

5054 CUSTOMER 2012-06-13

Name Remark

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012 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

lthellipgtOSoftSSIS2008_Clientbin or lthellipgtOSoftSSIS2012_Clientbin

On the Planning and Consolidation application server

ltdrivegtWebsrvrbin

2 Paste these files into the folder 100DTSTasks for SQL Server 2008 or into 110DTSTasks for

SQL Server 2012 For example if you install your SQL 2008 server or R2 on CProgram Files

Microsoft SQL Server paste all files into the CProgram Files (x86)Microsoft SQL Server

100DTSTasks folder

In Integration Services set the property Run64BitRunTime to True

83 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 or OSoftSSIS2012_Client on the

application server

8 Installing SSIS Custom Tasks

83 Setup of a COM+ Application on the Application Server

2012-06-13 CUSTOMER 5154

Typographic Conventions

Example Description

ltgt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example Enter your ltUser Namegt

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 httpwwwsapcom

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

5254 CUSTOMER 2012-06-13

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

  • SAP BusinessObjects Planning and Consolidation 100
    • Table of Contents
    • 1 Introduction
      • 11 SAP Notes for the Installation
      • 12 Naming Conventions
        • 2 Installing Planning and Consolidation Servers
          • 21 Basic Steps
          • 22 Prerequisites
          • 23 Before Starting the Planning and Consolidation Server Installation
          • 24 Logging on to Servers
          • 25 Service-level Accounts
          • 26 Standard and Advanced Settings
          • 27 Installing the Prerequisites
            • 271 Installing the Prerequisites ndash Basic Steps
            • 272 Installing the Operating System
            • 273 Installing the SQL Server
            • 274 Installing Analysis Services
            • 275 Installing the Anti-Cross Site Scripting Library
              • 28 Installing on a Single Server
              • 29 Installing the Server in a Multiserver Configuration
                • 3 After Installing Planning and Consolidation Servers
                  • 31 Post-Installation Steps
                  • 32 Connecting to Solution Manager Diagnostics
                  • 33 Configuring the Planning and Consolidation NET Application Servers
                  • 34 Post-Installation Optional Configuration Steps
                    • 341 Enabling the Management Console
                    • 342 Setting Up ODBC Logging in IIS for the Default Web Site
                    • 343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2
                    • 344 Removing Default Access to the Console
                    • 345 Management Console Access Control
                    • 346 Using Client Certificates
                        • 4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office
                          • 41 Installing the Administration Client
                          • 42 Installing the EPM Add-in
                          • 43 Using the Client Auto Update Program
                            • 5 Connection Issues
                              • 51 Checking for Open Ports
                              • 52 Proxy Server and Firewall Issues
                                • 6 Installing Planning and Consolidation with Two Active Directory Domains
                                • 7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
                                  • 71 Terminal Services Home Directories
                                  • 72 System Requirements
                                  • 73 Installing Planning and Consolidation
                                  • 74 Creating a Shortcut to the Launch Page
                                    • 8 Installing SSIS Custom Tasks
                                      • 81 Composition of SSIS Custom Task Installation
                                      • 82 Before You Modify the SSIS Packages
                                      • 83 Setup of a COM+ Application on the Application Server
                                          • Copyright and trademarks
Page 7: Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

1 Introduction

The SAP BusinessObjects Planning and Consolidation Installation Guide is intended for System

Administrators who perform Planning and Consolidation server and Administration client

installations It contains everything you need to know about installing the prerequisite components

and the server and client software

The installation package contains a full installation program While we do not offer a software upgrade

for this release we provide detailed instructions on how to migrate your existing environments For

more information see the Upgrade Guide which is available on SAP Service Marketplace at http

servicesapcominstguidesEPM-BPC Planning and Consolidation 100 version for the Microsoft platform

For more information about the Planning and Consolidation Office client software see the SAP

BusinessObjects EPM solutions add-in for Microsoft Office help

New Installation Program Features in 100

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

11 SAP Notes for the Installation

Read the following SAP Notes before you start the installation These SAP Notes contain the most

recent information on the installation as well as corrections to the installation documentation Make

sure that you have the up-to-date version of each SAP Note which you can find in the SAP Service

Marketplace at the Internet address httpservicesapcomnotes

1 Introduction

11 SAP Notes for the Installation

2012-06-13 CUSTOMER 754

SAP Note Number Title Comments

1584890 Documentation Addendum Contains information that does not appear in the application help of Planning and Consolidation 100 version for the Micrososft platform

1733053 SAP Planning and Consolidation 100 SP08 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP08This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1689792 SAP Planning and Consolidation 100 SP07 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP07This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1665656 SAP Planning and Consolidation 100 SP06 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP06This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1643037 SAP Planning and Consolidation 100 SP05 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP05This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1620464 SAP Planning and Consolidation 100 SP04 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP04This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1601213 SAP Planning and Consolidation 100 SP03 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP03This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1591848 SAP Planning and Consolidation 100 SP02 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP02This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1 Introduction

11 SAP Notes for the Installation

854 CUSTOMER 2012-06-13

SAP Note Number Title Comments

1573539 SAP Planning and Consolidation 100 SP01 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP01This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

12 Naming Conventions

In this document the following naming conventions apply

Variable Description

ltPC_serverportgt Server name or IP address and port number of SAP Planning and Consolidation application location

ltdrivegt The drive where SAP Planning and Consolidation is installedThe default for this is CPC_MS

1 Introduction

12 Naming Conventions

2012-06-13 CUSTOMER 954

This page is left blank for documents that are printed on both sides

2 Installing Planning and Consolidation Servers

This section includes the basic steps for installing a Planning and Consolidation server the prerequisites

and what to do before during and after the server installation

21 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 at httpservicesapcominstguidesepm-bpc 100 version for the Microsoft platform

2 Perform the tasks in the Before Starting the Planning and Consolidation Server Installation [page 13] section

including installing all prerequisites

3 From the application server install the Planning and Consolidation server See Installing Planning and

Consolidation on a Single Server [page 24]

NOTE

You must install both Planning and Consolidation 100 as well as the most recent Planning

and Consolidation 100 Support Package available from the SAP Service Marketplace at

httpservicesapcomswdc Software Downloads Support Packages and Patches A - Z Index

B SAP BPC FOR MICROSOFT SBOP PC 100 FOR MICROSOFT Comprised Software Component

Versions SAP CPM BPC 100 M Windows Server on x64 64bit

4 If you have multiple machines see Installing the Server in a Multiserver Configuration [page 26]

5 Perform the steps in the section After Installing Planning and Consolidation Servers [page 27]

22 Prerequisites

The following table describes the software you need to install before installing the Planning and

Consolidation server and the minimum versions required

NOTE

A list of the supported operating systems and database systems is also available in the Product

Availability Matrix on SAP Service Marketplace at httpservicesapcompam Search on

Planning and Consolidation

2 Installing Planning and Consolidation Servers

21 Basic Steps

2012-06-13 CUSTOMER 1154

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 or

Data Center with or without Hyper-V

NOTE

The operating system must be configured with NTFS

Relational Database Microsoft SQL Server 2008 Enterprise Edition Microsoft SQL Server 2008 R2 (Gemini) Enterprise Edition Microsoft SQL Server 2012 Enterprise Edition

OLAP Database Microsoft SQL Server 2008 Enterprise Edition ‒ Analysis Server Microsoft SQL Server 2008 R2 Enterprise Edition ‒ Analysis Server Microsoft SQL Server 2012 Enterprise Edition ‒ Analysis Server

Data Integration Microsoft SQL Server 2008 Enterprise Edition ‒ SQL Service Integration Services

Microsoft SQL Server 2008 R2 Enterprise Edition ‒ SQL Service Integration Services

Microsoft SQL Server 2012 Enterprise Edition ‒ SQL Service Integration Services

Other Requirements MSXML 40 SP2 or later ADOMDNET

ADOMDNET 100 when running SQL Server 2008 or 2008 R2 ADOMDNET 110 when running SQL Server 2012

SQL Server software components NET 40 IIS 75 or IIS 70

(Included in your Operating System IIS 75 is required for Windows 2008 R2 editions)

Anti-Cross Site Scripting Library 42This component must be downloaded before installing the server The server installation program asks for the path of each file and copies the files into the appropriate Planning and Consolidation path

Microsoft Visual C++ 2005 Runtime Libraries SP1 Microsoft Access Database Engine 2010 64bit VMWare ESX 3x or ESX 40

(Required only if a landscape deployment strategy using virtualization technologies is planned)

NOTE

MSXML 40 SP2 ADOMDNET 100 and Microsoft Visual C++ 2005 Runtime Libraries SP1 are included with the installation program but not installed automatically

RECOMMENDATION

For SQL Server 2008 only we recommend the installation of Microsoft SQL Server 2008 SP1

(or later) cumulative update package 6 or higher to solve a problem with incorrect periodic

2 Installing Planning and Consolidation Servers

22 Prerequisites

1254 CUSTOMER 2012-06-13

values being returned with calculated accounts For more information see SAP Note number

1429246 which also contains download information

We recommend SQL Server 2008 (or R2) Enterprise Edition or SQL Server 2012 Enterprise

Edition for the OLAP database to support proactive cache and cube partitioning It is

technically possible to use SQL Server 2008 (or R2) Standard Edition or SQL Server 2012

Standard Edition for data integration servers but we do not recommend this

23 Before Starting the Planning and Consolidation Server Installation

You must perform the following tasks before starting your Planning and Consolidation server

installation

Install all the prerequisite software including all of the latest Microsoft hotfixes For more

information see Installing the Prerequisites [page 17]

If you access your application through a firewall verify with your network administrator which

TCP ports to choose during the installation By default port 80 is the setting for standard http

access and port 443 is the setting for https access If you require a service to listen on a different

port you can specify it during the installation program in Advanced Settings See Standard and Advanced

Settings [page 16]

Make sure all required server ports are open and that there is communication between the physical

servers on which you are going to install the server types See Checking for Open Ports [page 41]

Set up the required service accounts that you need to install the Planning and Consolidation server

See Service-Level Accounts [page 15]

The sample environment EnvironmentShell has been updated in this version of Planning and

Consolidation and automatically overwrites the previous version If you have made any

modifications to EnvironmentShell that you want to keep make a copy of it before continuing

with the installation

If you have the URLScan and IIS Lockdown tools installed on your application server you must

reinstall them

Disable your anti-virus software program After the installation when you enable the program

turn off Script Blocking

If a version of Planning and Consolidation on a NetWeaver platform exists uninstall it before you

install Planning and Consolidation 100 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 fsntfsV

All servers in a multiserver environment must be members of the same domain

2 Installing Planning and Consolidation Servers

23 Before Starting the Planning and Consolidation Server Installation

2012-06-13 CUSTOMER 1354

In a multiserver environment the installing ID must be a domain user ID We recommend that

you do not log on to the servers using a local server user ID even if the user ID is a member of the

Administrator group on the server This way you have the proper authority to install software and

to modify the Component Services See Logging On to Servers [page 14]

You must determine the IP addresses or server names for all servers before installing Planning and

Consolidation We recommend that you use static IP addresses

IIS must be enabled

If the application server is not able to copy files to the database server during the installation because

of port access reasons (DMZ WORKGROUP or nontrusted domain authentication failures) do

the following

1 Copy the EnvironmentShell database file ServerEnvironmentShelldb10 from the

Planning and Consolidation installation program to any folder on the SQL server (for example

cEnvironmentShelldb10)

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 cEnvironmentShelldb10)

Install the Anti-Cross Site Scripting Library which provides protection to Web-based applications

against Cross-Site Scripting (XSS) attacks See Installing the Anti-Cross Site Scripting Library [page 24]

24 Logging on to Servers

When installing in a multiserver environment you must use a domain user ID to log on to all

components

A local server user ID is a member of the Administrator group on the server A domain user ID is a

member of the Administrator group of a domain to which the server belongs or a member of the

Administrator group on the local server

Errors may display during the installation program and in the diagnostic program if the installing user

is not assigned to the Administrator group directly but is assigned to a group with Administrator rights

You can ignore these messages

NOTE

If you change the password used to install Planning and Consolidation you must change the

password for the applicable Planning and Consolidation service To do this go to Server Manager

on the application server and select Server Reset Logon Credentials For more information see

the SAP Planning and Consolidation Operations Guide in httpservicesapcominstguidesepm-bpc

100 for the Microsoft Platform SBOP Plan amp Consol 100 MS Administrators Guide

2 Installing Planning and Consolidation Servers

24 Logging on to Servers

1454 CUSTOMER 2012-06-13

25 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

PrerequisitesPlanning and Consolidation 100 has the following Windows services

BPC SendGovernor which manages Microsoft Analysis Service locks to ensure consistent performance

and avoid deadlocks

BPC ServiceManager which manages the System Landscape Directory (SLD) service logging service

and global caches

BPC CTS ServiceManager which listens and handles CTS import requests from the CTS+ transport

management system

Since these services should be able to access to the FileShare server an Admin account is assigned

automatically to the service during the installation of the Planning and Consolidation server program

Even though an Admin account has been assigned to the server correctly the services may fail to start

with the error message

Could not start the BPC SendGovernor service

The reason for this is that the Admin account is not registered as a service

When installing a service to run under a domain user account the account must have the right to

logon as a service on the local machine This logon right strictly applies only to the local computer

and must be granted in the Local Security Policy

To edit the Local Security Policy of the computer you want to define the logon as a service

permission perform the following actions

1 Start the Local Security Settings Microsoft Management Console (MMC) snap-in

2 Expand Local Policies and then click User Rights Assignment

3 In the right-hand pane right-click Log on as a service and then click Security

4 Add the user to the policy and click OK

5 Close the Local Security Settings MMC snap-in

For more details see How to Troubleshoot Service Startup Permissions http

supportmicrosoftcomkb259733

FeaturesDuring the installation enter user IDs and passwords for the following user types

System Admin ID

This ID is read-only and is the same as the installation user ID that is the system displays the ID

on the installation screen but you cannot modify it This ID allows access to code that provides

2 Installing Planning and Consolidation Servers

25 Service-level Accounts

2012-06-13 CUSTOMER 1554

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 readwrite 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

26 Standard and Advanced Settings

The following tables describe the standard and advanced settings for the installation program After

the server is installed you can change these settings using the Server Manager

NOTE

When defining server names the name refers to the NetBIOS name IP address and fully qualified

domain names (FQDN)

Standard Settings

Standard settings are typically used for a single-server environment The following table describes each

setting

Server Option Value Description

SQL Database server name The name of the SQL DB server

OLAP server name The name of the OLAP server

File Share server name The default value is the name of the File Share server that should be the computer name

Local data path Where the data files are saved on the File Share server By default this is CPC_MSData

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

Server Option Value Description

SQL Server Name The name of the SQL DB server Defaults to the local server

2 Installing Planning and Consolidation Servers

26 Standard and Advanced Settings

1654 CUSTOMER 2012-06-13

Server Option Value Description

Instance name The SQL instance name If left blank the default instance is used

Port number The default port number for the SQL Server is 1433

Provider The only available value is SQL

Local path for EnvironmentShell 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 CPC_MSData

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 changesSee the Kerberos authentication settings section in the SAP Library Server Manager Guide on httpservicesapcominstguidesEPM-BPC

100 for the Microsoft Platform

Scheduler Server Name The name of the server used for scheduling usually the application server for example GMPV50072862B If you have multiple application servers select the appropriate one

NOTE

If the primary server stops working you must manually configure your application server database to froward requests to another application server

27 Installing the Prerequisites

271 Installing the Prerequisites ndash Basic Steps

Before installing your Planning and Consolidation server you must install the prerequisite Microsoft

software the operating system IIS SQL server analysis services ADOMDNET and MSXML This

section provides guidance on installing each component For specific versions required see

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 1754

Prerequisites [page 11] and the Product Availability Matrix on the SAP Service Marketplace at http

servicesapcompam Search on Planning and Consolidation

NOTE

To ensure a successful installation you must install the software in the order listed in this

procedure

Check all third-party infrastructure services to ensure that they are functioning and that their

authentication models are documented (stated) since you need to reference this information

during the installation These third-party services include IIS OLAP service SQL services and

Active Directory (AD)

We recommend not installing Microsoft Office on the application server

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

(UMCexe) on the Planning and Consolidation CD in a folder called UMC_100_INSTALLER When

you run the installation package the wizard guides you through the following steps

1 Choose a language for the UMC install wizard to use

2 Check that the prerequisite check status is Succeeded and click Next

3 When you are ready to install the UMC click Next on the welcome screen

4 Click I accept the License Agreement and then Next

5 Choose the destination directory for the UMC installation and click Next

6 Select the languages that you wish to install

7 Select the features that you want to install (POAFHelper dotnet is mandatory for Planning

and Consolidation)

8 On Start Installation click Next to complete the installation

2 Install the required operating system on the single-server computer or on each physical server for

a multiserver configuration See Installing the Operating System [page 19]

3 Install the latest service pack for your operating system To install this service pack go to http

wwwmicrosoftcom

4 From your operating systems media install IIS

5 From your SQL Server media install SQL Server and its required service packs and hot fixes See

Installing SQL Server [page 19]

6 From your SQL Server media install Analysis Services Enterprise Edition and its required service

packs and hot fixes See Installing Analysis Services [page 23]

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

1854 CUSTOMER 2012-06-13

7 On your application server install ADOMDNET The Planning and Consolidation zip file contains

the ADOMDNET installation package in the following locations

For SQL Server 2008 mdash BPC SetupServerSQLSERVER2008_ASADOMD10_x64msi

For SQL Server 2012 mdash BPC SetupServerSQLSERVER2012_ASADOMD11_x64msi

8 On your application server install MSXML 40 Service Pack 2 or later

The MSXML 40 SP2 installation package is contained in the Planning and Consolidation zip file at

the following location BPC SetupServermsxmlmsi

9 On your application server install Microsoft Visual C++ 2005 Runtime Libraries SP1

The Microsoft Visual C++ 2005 SP1 installation package is contained in the Planning and

Consolidation zip file at the following location BPC SetupServervcredist_x64exe

NOTE

The version of vcredist_x64exe in BPC SetupServer has been updated to 8061000 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 httpwwwmicrosoftcomdownloadsen

detailsaspxFamilyID=C06B8369-60DD-4B64-A44B-84B371EDE16Dampltdisplaylanggt=en

272 Installing the Operating System

Before installing the operating system make sure that you configure your server for NTFS

For a list of languages that are supported see the Product Availability Matrix on the SAP Service

Marketplace at httpservicesapcompam Search on Planning and Consolidation

Planning and Consolidation can support all servers with an operating system in any language

NOTE

Currently Planning and Consolidation does not support an operating system in bi-directional

languages such as Hebrew

ProcedureIf you are installing IIS 70 or 75 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

273 Installing the SQL Server

PrerequisitesDuring the installation procedure you have the opportunity to specify the location of the

EnvironmentShell database file Check that it is possible to access EnvironmentShell from the location

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 1954

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 CEnvironmentShelldb10) 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 a 2008 2008 R2 and 2012 SQL Server

SQL Server Considerations

We recommend installing all required components in sequence For example install the Operating

System (Windows Server) then enable IIS and ASPNET and install any Windows Server service

packs

IIS and NET Framework 40 are required on your application server

NOTE

If you encounter a 500 HTTP Error when trying to connect to the Planning and Consolidation

Web Client refer to Microsoft Support articles 2520479 and 2468871 for assistance

To reinforce security we recommend that you install the SQL server and SSAS components to a

nondefault instance of SQL Server

General Installation Steps

1 Launch the SQL Server Setup program entering a product key if necessary and accepting the license

terms

2 Choose Install to install the SQL support files

3 In Feature Selections select instance and shared features as indicated in the SQL Server Component

Options section below then choose Next

4 Review disc space requirements then choose Next

5 In Server Configuration Perform the following actions

1 In the Service Accounts tab enter a Planning and Consolidation sysadmin account for the SQL

Server Database Engine and the SQL Server Analysis services This is required so that the Planning

and Consolidation sysadmin can create and process the Planning and Consolidation database

because the Microsoft SQL server tries to back up or restore database with the privileged

account This account is also required during Backup Environment and Restore Environment in the

Server Manager

For a single-server environment this account is also required if the backup file is located in a

different domain machine because SQL tries to access the folders and files with this account

For the a multiple-server environment SQL server retrieves the information of backup file

from the application server and the account requires the folder access privilege for the

application server

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2054 CUSTOMER 2012-06-13

To ensure that you have the complete access privileges we recommend the Planning and

Consolidation sysadmin for this service account

2 In the Collation tab set the collation settings to SQL_Latin1_General_CP1_CI_AS

Choose Next

6 Set Database Engine Configuration options then choose Next

We recommend you choose Mixed mode (Windows authentication and SQL authentication) This allows you

to use a restrictive SQL ID that works with the drill-through feature If you must restrict SQL

authentication for security reasons you can define a specific parameter in your drill-through

queries If you do not need drill-through support or use it without leveraging SQL authentication

you can install the SQL Server in Windows-only mode

7 Accept the Analysis Services Configuration default options and the remaining default options of the

installation program

8 Choose Install to begin the installation with the options you have set

SQL Server Component 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

Server Component What to Install

SQL Server Database Engine Services

SSAS Server Analysis Services

Application Server The following Shared Features Client Tools Connectivity Integration Services Client Tools SDK

Custom Settings for the SQL Server

As of version 100 Planning and Consolidation supports the following new features for SQL Server 2008

SQL Server 2008 R2 and SQL Server 2012

Process Dimension

It is now possible to process a dimension with multiple selections At processing time the process

dimension module makes changed or added information for each dimension and process for all selected

dimensions and cubes in parallel

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 2154

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

NOTE

Setting 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 tblFactWBltappgt table

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 Microsoftreg SQL Servertrade

20052008 which you can download from wwwmicrosoftcom (search on ldquoTable Partitioningrdquo to find

all relevant articles)

After Installing SQL Server 2008 SQL Server 2008 R2 and SQL Server 2012

From SQL Server Configuration Manager confirm that the SQL Server Browser service is

running The browser service is required for Planning and Consolidation

From SQL Server Configuration Manager do the following

1 Select Protocols for ltInstanceNamegt then double-click TCPIP from the right side of the window

2 When prompted for the TCPIP Properties select IP Addresses You see two IPs that indicate the

localhost and external network interface machine

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2254 CUSTOMER 2012-06-13

3 If you want to use IP1 which indicates Server IP set Enabled to Yes and specify the TCP Port as

desired

4 Delete 0 from TCP Dynamic Ports Set IPAll - TCP Ports as desired (for example 1533)

RECOMMENDATION

We do not recommend using dynamic ports

In an SQL server the default instance has a listener which listens on a fixed port (TCP

port 1433) However for the named instance the port on which the SQL server listens is

random and dynamically selected when the named instance of the SQL server starts This

recommendation prevents any conflict problems

From the SQL Server Configuration Manager specify the client protocol options for the application

server

1 Select Client Protocols from the SQL Native Client Configuration folder

2 From the right side of the window double-click TCPIP The TCPIP 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

NOTE

We 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

274 Installing Analysis Services

ProcedureAfter you install SQL Server and its required service packs and hotfixes you must install SQL Server

Analysis Services and its required service packs and hotfixes

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 2354

NOTE

If you have migrated your Analysis Services repository to the SQL Server back up the database

that contains the repository before installing this release

To install Analysis Services for SQL Server 2008 SQL Server 2008 R2 or SQL Server 2012 follow the steps

and guidelines in httptechnetmicrosoftcomen-uslibraryms143219aspx

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 httpwwwmicrosoftcomdownloads

detailsaspxFamilyID=3be0488d-e7aa-4078-a050- ae39912d2e43ampdisplaylang=en

275 Installing the Anti-Cross Site Scripting Library

Procedure

Before installing Planning and Consolidation servers you must download the Anti-Cross Site Scripting

Library (version 42 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 AntiXSSLibraryDLL from the Microsoft Web

site at httpwwwmicrosoftcomdownloadendetailsaspxid=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 AntiXssLibrarydll

28 Installing on a Single Server

When you install all Planning and Consolidation server components on a single server you should

consider the following issues

Make sure the server has a minimum of 800 MB of hard disk space

Additional environment installations require more free disk space which is a minimum of two

times the uncompressed size of the environment files

When you install Planning and Consolidation on a single-server the system adds the following server

components

SQL Server

SQL Server Analysis Services (SSAS)

Application Server

FileShare server

Procedure

To install Planning and Consolidation on a single server take the following steps

1 Exit all Windows programs

2 Installing Planning and Consolidation Servers

28 Installing on a Single Server

2454 CUSTOMER 2012-06-13

2 Log on to the server with a local server user ID or domain user ID For more information see Logging

on to servers [page 14]

3 Make sure all prerequisite software is installed on the server For more information see Installing

the Prerequisites [page 17]

4 Obtain SAP Planning and Consolidation from the Downloads SAP Installations amp Upgrades area of

SAP Service Marketplace then extract the files and run StartUpexe

5 From the Server Install screen select Install the Planning and Consolidation server

6 From the Welcome screen choose Next

7 From the License Agreement page choose I accept the terms of the license agreement then choose Next

8 From the Installation Method page accept the default Single machine enter a system ID for the system

landscape directory (SLD) and choose Next

NOTE

Entering a system ID of the SLD is only required if you have a SAP Solution Manager license

If you do not have a SAP Solution Manager license you can leave this field empty

9 From the Authentication Method page choose the desired authentication method and choose Next

10 If you have chosen SAP BusinessObjects User Management System in the previous screen on the CMS

Authentication page enter the information required to log on to CMS as an administrator

The following information is required

Field Description

System name CMS system name (server nameport number) for example CMSServer6400

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

11 After entering the CMS administrator authentication details choose Next

12 From the Service type accounts page enter service-level account user IDs and passwords See Service-

Level Accounts [page 15]

13 After defining the IDs and passwords choose Next

14 From the Server Information page (see Standard and Advanced Settings [page 16]) do one of the following

Review the standard settings and choose Next

To set advanced settings choose the Advanced Settings button Enter the desired information

and choose Next

2 Installing Planning and Consolidation Servers

28 Installing on a Single Server

2012-06-13 CUSTOMER 2554

15 Specify the location and name of AntiXssLibrarydll See Installing the Anti-Cross Site Scripting Library [page

24]

Choose Next

16 Select destination folders for Programs and Data The Data files include Webfolders and FileDB

(published reports) and should be installed on a separate drive in a production environment This

recommendation reduces the hard disk IO time and helps to speed up SQL commands

Accept the defaults or make your selections then choose Next

17 Select the default values for the Web client The values are used to determine the default language

and region for the Web client when you connect to it You can change the values in the Planning

and Consolidation Server Manager

18 The installation process takes a few moments When it is complete choose Exit

19 A prompt is displayed to restart your computer Select OK to restart

20 Perform the steps in After Installing Planning and Consolidation Servers [page 27]

29 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 24]) with the following

exceptions

On the Installation Method page do not accept the default instead choose Network Load Balancing

environment With this option there is an additional choice to Include sample environment (required on only

one of the application servers) This is because when you install the application server it connects to the

database server and creates the sample environment (EnvironmentShell) Installing the sample

environment is required on only one application server and you may choose which one

In the Virtual Name field enter the virtual IP address virtual name in the default properties

2 Installing Planning and Consolidation Servers

29 Installing the Server in a Multiserver Configuration

2654 CUSTOMER 2012-06-13

3 After Installing Planning and Consolidation Servers

31 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 28]

2 Configure the Planning and Consolidation NET and application server to ensure that it and its

related services function properly and reliably For more information see Configuring the Planning and

Consolidation NET Application Server [page 29]

3 Optional configuration steps [page 30]

1 To ensure proper functioning of the Management Console create an SQL user and modify

the System DSN and IIS to reflect those user credentials See Enabling Management Console [page

30]

2 Configure custom ODBC logging for the default Web site For details of how to configure

custom logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web

Site [page 31]

3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC

Data Source [page 32]

4 Modify the default access rights to the Management Console By default users in Active

Directory can access the Management Console with whatever rights they have been granted

on the server For information about removing default access and creating a group that can

access the console see Removing Default Access to the Console [page 32]

5 Add authorized users or groups to the group that can access the Management Console We

recommend that you only grant Management Console access to system administrators

Planning and Consolidation users should not have any access For more information see

Management Console Access Control [page 33]

6 Configure the use of client certificates for authentication See Using Client Certificates [page

34]

4 Take the following steps to set up security

If you are defining security and application structure continue with step 5

3 After Installing Planning and Consolidation Servers

31 Post-Installation Steps

2012-06-13 CUSTOMER 2754

If you want to designate someone other than the system administrator to manage security

and application structure log on to EnvironmentShell designate a user as a Primary

Administrator

This user must have Administration ‒ Environment and Security ‒ Define User task rights

so that he or she can add and delete environments and define user security

The Primary Administrator can continue with the next step (5)

5 From the machine on which you administer Planning and Consolidation install the

Administration client See Installing the Administration Client [page 37]

6 Start Planning and Consolidation Administration from the launch page

7 Select Connection Wizard and log on to EnvironmentShell

8 Create a new environment using EnvironmentShell as the source

9 Log on to the newly created environment and set up users teams and task profiles (You must

set up task profiles since there is no access to Planning and Consolidation tasks)

10 Set up your data access profiles and add users (or teams) to one or more data access profiles (You

must complete this step since there is no access to dimensions or members)

NOTE

To allow users to request and query large amounts of data you can edit the metabasexml file located

at CWindowssystem32inetsrv Set the following parameters to the stated values

ASPBUFFERINGLIMIT = 10485760

MAXREQUESTENTITYALLOWED = 10485760

32 Connecting to Solution Manager Diagnostics

NOTE

You only need to perform the steps in this section if you have a SAP Solution Manager licence

The diagnostics functions in SAP Solution Manager allow identification analysis and resolution of

problems This procedure provides the steps required to connect Planning and Consolidation to

Solution Manager Diagnostics

Procedure

1 Install the Diagnostics Agent according to SAP Note 1234387 on all servers where application servers

are installed

NOTE

Installation files for Diagnostics Agent are available on Service Marketplace by navigating to

Support Packages and Patches mdash Entry by Application Group SAP Technology Components SAP

SOLUTION MANAGER SAP SOLUTION MANAGER 70 EHP 1 Entry by Component Agents

for managed systems DIAGNOSTICS AGENT 711

3 After Installing Planning and Consolidation Servers

32 Connecting to Solution Manager Diagnostics

2854 CUSTOMER 2012-06-13

Download the installation file based on the 64-bit Windows Server system landscape

2 To access the DBA Cockpit you must create a user account with sufficient rights on all Windows

Servers where Microsoft SQL Server is installed Do the following

1 Start Computer Management then select Action New User

2 Create a new user

3 Right-click on the user then choose Properties On the Member Of tab select Add

4 Add the group SQLServerltReleasegtSQLAgentUser$ltDomain or hostnamegt$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 httpsservicesapcom~sapidb011000358700000074392009E and follow

the chapters that apply to Planning and Consolidation

33 Configuring the Planning and Consolidation NET Application Servers

Procedure

Modifying machineconfig Files

To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock

occurrences that would cause the application server to ldquosleeprdquo and not process anymore you can

modify the machineconfig file which resides in the WINDOWSMicrosoftNETFramework64

v4030319Config directory

1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to

specify whether to automatically configure settings to achieve optimal performance based on the

machine configuration You can set this attribute to True or False

For more information see httpmsdnmicrosoftcomen-uslibrary7w2sway1aspx

2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the

Planning and Consolidation application) or Machineconfig (for all applications including

Planning and Consolidation) to ensure the validationKey and decryptionKey keys have the same

value on all application servers This way when the authentication cookie is checked the

authentication ticket used on one server can still be valid on another server

For more information and sample Visual Basic code for generating random key values see http

msdnmicrosoftcomen-uslibraryms998288aspx

3 After Installing Planning and Consolidation Servers

33 Configuring the Planning and Consolidation NET Application Servers

2012-06-13 CUSTOMER 2954

paght000007_webfarmdeploymentconsiderations and httpmsdnmicrosoftcomen-us

libraryms998310aspx

34 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 30]

2 Configure custom ODBC logging for the default Web site For details of how to configure custom

logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page

31]

3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC Data

Source [page 32]

4 Modify the default access rights to the Management Console By default users in Active Directory

can access the Management Console with whatever rights they have been granted on the server

For information about removing default access and creating a group that can access the console

see Removing Default Access to the Console [page 32]

5 Add authorized users or groups to the group that can access the Management Console We

recommend that you only grant Management Console access to system administrators Planning

and Consolidation users should not have any access For more information see Management Console

Access Control [page 33]

6 Configure the use of client certificates for authentication See Using Client Certificates [page 34]

341 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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3054 CUSTOMER 2012-06-13

NOTE

Without these updates the Management Console does work but some functionality (specifically

User Activity and Service Status) does not work as expected

Should you need to uninstall Planning and Consolidation we recommend that you reset the

Active Log Format field in IIS to W3C Extended Log File Format

342 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 ApplicationHostconfig set the property customLogPluginClsid to the value FF16065B-

DE82-11CF-BC0A-00AA006111E0 Set the logFormat to Custom You can find this in the ltlogFilegt

node in ApplicationHostconfig as shown here

ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0

logFormat=Custom gt

Use the following AppCmds to configure IIS to use ODBC logging for the default Web site

appcmd site set sitenameDefault Web Site

logFilecustomLogPluginClsidFF16065B-DE82-11CF-BC0A-00AA006111E0

appcmd site set sitenameDefault Web Site logFilelogFormatCustom

Configuring ODBC Logging Parameters in ApplicationHostconfig

Configure ApplicationHostconfig to contain the database table information as set up in the Microsoft

Support article specified in the Prerequisites section Configure these settings in the ltodbcLogginggt

node under ltsystemwebServergt

EXAMPLE

ltlocation path=Default Web Sitegt

ltsystemwebServergt

ltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog

userName=Username password=mypassword gt

ltsystemwebServergt

ltlocationgt

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3154

Use the following AppCmds to configure these attributes for the default Web site

appcmd set config Default Web Site sectionodbcLogging

dataSourceBPC_ManagementDSN commitappHost

appcmd set config Default Web Site sectionodbcLogging tableNameBPCLog

commitappHost

appcmd set config Default Web Site sectionodbcLogging userNameUsername

commitappHost

appcmd set config Default Web Site sectionodbcLogging passwordmypassword

commitappHost

NOTE

You cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must

use the SQL Server ODBC driver For more information see the Microsoft Knowledge Base article

931202 The requirements for using the ODBC logging feature in IIS

343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2

ProcedureThis procedure describes how to set up an ODBC data source for the Management Console in Windows

Server 2008 or Windows Server 2008 R2

Proceed as follows

1 Open ODBC Connection Manager

2 On the System DSN tab page add a new DSN

Choose Add

Choose SQL Server as the driver

Choose Finish

3 In the Name and Description fields enter BPC_ManagementDSN

4 In the Server field enter the name of your SQL Server Choose Next

5 Leave the default settings and choose Next

6 Choose the Change the default database to field and enter AppServer Choose Next

7 Leave default settings and choose Next

8 Choose OK

344 Removing Default Access to the Console

NOTE

If you have chosen SAP BusinessObjects User Management System in the installation screen you

do not need to remove or configure access because the Management Console service always runs

with the System Admin ID account which is a member of the Administrators group

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3254 CUSTOMER 2012-06-13

ProcedureTo remove default access to the Management Console and create a group that does have access to the

console use the procedure described below

NOTE

Create your Management Console administrative group either on the server that hosts the

Management Console or in the Active Directory

1 In the context menu of the servers My Computer icon choose Manage

2 In the Computer Management dialog box choose Local Users and Groups Groups

NOTE

Alternatively you can perform analogous steps in Active Directory

3 In the 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

NOTE

This step is a necessary precursor to the completion of this procedure

10 In the Security dialog box click Copy to ensure that the System group retains its privileges

11 Remove access to the Management Console from all groups that should not have it

12 Choose Authentication in the center pane then disable Windows authentication

ResultUsers who have not been granted access to the Management Console can still open the Management

Console Web page but it contains no data or menu options This does not affect the access that a user

would otherwise have to Planning and Consolidation

345 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 32] Their rights in

Active Directory determine what they can access in the Console

By default any member of the Administrators Active Directory group on the application server or

domain has full access to all of the features of the Console except the Planning and Consolidation

logging area Access to Planning and Consolidation logging is controlled within the Planning and

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3354

Consolidation Administration Client task security The user must be granted View system logs task

privileges For more information see the SAP Library Planning and Consolidation Administrators Guide in

httpservicesapcominstguidesepm-bpc 100 version for the Microsoft platform

Your IT policy determines whether you grant access by group or user You may wish to create several

levels of Console users (read-only users for example) in your environment

To grant or limit access to users or groups you can add or remove the following privileges from the

areas described in this table

Privilege Rights Management Area

Task Manager and Kill Process Administrators group on application server or domain

Performance Monitor Counters Administrators group on application server or domain Power Users group on application server or domain Performance Monitor Users group on application server

Microsoft Analysis Services performance monitoring

Administrators group on application server or domain

Microsoft SQL Server Monitoring (performance counters and statistics)

Administrators group on application server or domain

346 Using Client Certificates

To enable the use of client certificates in Planning and Consolidation you must follow several manual

steps

NOTE

Planning 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 httptechnetmicrosoftcomen-us

librarycc753810aspx

For more information about configuring the client certificate mapping authentication see http

technetmicrosoftcomen-uslibrarycc732996(WS10)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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3454 CUSTOMER 2012-06-13

This option allows you to use a client certificate or username and password (Basic

authentication) to connect to Planning and Consolidation

2 Enable anonymous authentication

1 In the IIS Manager expand the node of the Planning and Consolidation web site

2 Select the ManagementConsole directory (ltWebsitegtManagementConsole) to open the

ManagementConsole home page

3 Double-click Authentication and enable Anonymous Authentication

4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way

as in step 3

5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the same

way as in step 3

3 Change the web configuration settings

1 Open the ltPC_MSgtWebsrvrWebBPCwebconfig file

2 Find the text clientCredentialType=Windows

3 Change value of clientCredentialType to None (clientCredentialType=None)

4 Open the PC_MSWebsrvrWebPOASBCwebconfig file Repeat steps 2 and 3

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3554

This page is left blank for documents that are printed on both sides

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

The installation of the Planning and Consolidation Administration Client allows administrators to

build and maintain Planning and Consolidation environments and models and administer security

All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions

add-in for Microsoft Office for more information see the SAP BusinessObjects EPM solutions add-in for

Microsoft Office help

NOTE

You must update the Administration Client to the same version as the server

If your PC is on a different domain than your server you must set the Internet Explorer

Security Zone value of the Planning and Consolidation client to prompt for user name and

password Otherwise the Planning and Consolidation Start Page does not display

41 Installing the Administration Client

Prerequisites

NOTE

For a definitive list of system requirements see the Product Availability Matrix on SAP Service

Marketplace at httpservicesapcompam Search on Planning and Consolidation

The following list describes the minimum software requirements

Microsoft Internet Explorer 70 or 80

Microsoft Office 2007 or 2010

NET Framework 20 or higher (install any required NET Framework Hotfixes by referring to

httpsupportmicrosoftcomkb)

Pentium IV (1 GHz CPU)

512 MB RAM

100 MB of free hard disk space in the My Documents folder

20 MB of free hard disk space for the installed Administration files

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

41 Installing the Administration Client

2012-06-13 CUSTOMER 3754

NOTE

We recommend that you install all of the latest Microsoft Windows hotfixes prior to installing

the Administration client For information about which hotfixes to install see http

updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us

ProcedureThe following procedure describes how to install the Administration Client on to an administratorrsquos

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 AddRemove Programs in the Windows Control Panel

3 Point your browser to the Planning and Consolidation Web at httpltPC_serverportgtsap

bpcweb

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

42 Installing the EPM Add-in

The Planning and Consolidation installation media does not contain the EPM addin setup program

You must download the most recent version of the full setup (EPM Add-inexe) from the Service

Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPC

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

43 Using the Client Auto Update Program

If Planning and Consolidation version 100 or later is installed you can use the Client Auto Update

program to set up the server so that it determines if an upgrade for a connecting Administration client

is necessary

The following describes the use of the auto update program for the Administration Client and the EPM

add-in

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

42 Installing the EPM Add-in

3854 CUSTOMER 2012-06-13

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 37]

To use the Client Auto Update program for the Administration Client proceed as follows

1 From the Server Manager select Options Client Options

2 Select Admin Update

3 If users without administrator rights on their machines use the auto update enter an administrator

ID and password in the Admin ID and Admin password fields respectively The Admin ID should be a

member of the local administrators group on all the computers running the auto update This

setting is not needed if all users have administrator rights on their machines

4 Select Update

For the EPM Add-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 Optionshellip 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 Market Place (SMP) at httpservicesapcom

All support packages and patches are available from the SMP as a zip file

EPMEXCLCLNTltSPLgtzip is for a support package

EPMEXCLCLNTltSPLgtPltPLgtzip 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 ltSP versiongtmsp

EPM Addin Support Package ltSP versiongtxml

For a patch these files are

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

2012-06-13 CUSTOMER 3954

EPM Addin Patch ltpatch numbergtmsp

EPM Addin Patch ltpatch numbergtxml

2 Unzip the zip file and extract the two files to the application server folder (WebsrvrWebBPC

Installation)

3 From the Server Manager select Options Client Options

The system lists the available packages Select the package that you want to use for the autoupdate

You can set a different update policy for each package listed

EXAMPLE

The following table illustrates some possible situations assuming that you have installed the

first full version (V1)

Available maintenance packages

V2-user updateV3-force updateV4-force updateV5-user update

V5-user update V5-user updateV6-auto updateV7-force update

Minimum Required Version

V4 V4 V7

Notification A prompt tells the user to install maintenance package V4 using the Forced Update behavior

If User Update is enabled the prompt informs the user that maintenance package V5 is available

A prompt tells the user to install maintenance package V7 using the Forced Update behavior

New Version V4 V4 or V5 V7

If you change the update policy for any package click Update to complete the change

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

4054 CUSTOMER 2012-06-13

5 Connection Issues

You may experience connection problems with ports the proxy server or programs and settings that

interact with these components If you have any issues related to connection review the following

recommendations and troubleshooting tips

51 Checking for Open Ports

You must ensure that all required ports are open for inboundoutbound 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 431181836 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

NOTE

You can use the following site to scan for the normal ports It allows you to manually enter a port

number to test

httpwwwmyserverorgportsniffasp

You can change the name of a port

52 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 Explorer Tools Internet Options Connections LAN Settings ) or at the server level

Enabling content filtering on the proxy server or firewall may cause connection problems

If external users are having trouble connecting to the server make sure the proxy server connects

using a fully qualified domain name Fully qualified domain names typically resolve both internal

and external IP addresses

Each secure Planning and Consolidation server name must be identified on the proxy server

Proxy servers may or may not require authentication which could conflict with Planning and

Consolidation authentication Do not use authentication on the proxy server The system

5 Connection Issues

51 Checking for Open Ports

2012-06-13 CUSTOMER 4154

synchronizes the user name and password on the remote server with the local user name and

password

NOTE

For more information about setting up an ISA proxy server contact SAP Support to request a

copy of Setting up ISA Proxy Server White Paper

Internet Explorer Settings 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

5 Connection Issues

52 Proxy Server and Firewall Issues

4254 CUSTOMER 2012-06-13

6 Installing Planning and Consolidation with Two Active Directory Domains

To set up a Planning and Consolidation 10 application server in a hosted environment and use your

own domain users follow this procedure In general you install Planning and Consolidation on the

host domain use the host domain account and assign it to the Planning and Consolidation users

SysAdmin Admin and Users Then you accept one way trust (the host domain trusts your domain)

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

6 Installing Planning and Consolidation with Two Active Directory Domains

2012-06-13 CUSTOMER 4354

This page is left blank for documents that are printed on both sides

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

This section describes best practices and instructions for installing Planning and Consolidation in a

Terminal Services or Citrix Server deployment

71 Terminal Services Home Directories

We recommend using Terminal Server home directories rather than using the userrsquos 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

72 System Requirements

The Citrix server should be one of the following systems

XenApp 5 Enterprise

XenApp 5 Platinum

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 37])

73 Installing Planning and Consolidation

Prerequisites

The server installation files have been downloaded from SAP Service Marketplace and installed

Procedure

The following steps outline how to install the Planning and Consolidation clients in a Terminal Services

(TS) or Citrix Server deployment

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

71 Terminal Services Home Directories

2012-06-13 CUSTOMER 4554

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 userinstall

4 Open a browser and connect to the URL httpltPC_serverportgtsapbpcweb

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 userexecute 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 Iexploreexe http(s)

ltServerNamegt-NetBIOS or FQDNsapbpcweb

To publish Planning and Consolidation Administration CProgram FilesPC_MS

BPCAdminMainexe

74 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 userrsquos desktop) must be moved to the All UsersDesktop folder

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

74 Creating a Shortcut to the Launch Page

4654 CUSTOMER 2012-06-13

8 Installing SSIS Custom Tasks

This section provides background information and instructions for installing SQL Server Integration

Services (SSIS) for SQL Server 2008 and SQL Server 2012

The Planning and Consolidation Data Manager component supports and uses SSIS Since SQL Server

2008 and SQL Server 2012 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

81 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 Filelistxml 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

OSoftSetupexe ‒ 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 or OSoftSSIS2012_Client on the client machine followed by the SQL Server

version If you want to use SQL 2008 Tasks under the SQL 2012 environment you must install

OSoftSSIS2008_Client on the application server For detailed information see SAP Note 1707410

You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package by extracting

OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPC

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 or

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4754

OSoftSSIS2012_Client for creating a COM+ application For more information see Before You Modify

the SSIS Packages [page 50] and Setup of a COM+ Application on the Application Server [page 51]

Bin folder

This folder contains the following components

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCCachedll Planning and Consolidation Cache file

BPCDataFlowPackagedll or BPCDataFlowPackage2012dll

BPCDMdll

BPCDMTaskMaindll COM+ component

BPCFilePreviewdll

BPCGacUtil_20exe System File

BPCGacUtil_40exe System File

BPCImpersonatordll Planning and Consolidation Impersonator

BPCLogicdll

BPCScriptdll

BPCServerZipdll

BPCServiceResdll

BPCTransferMembersdll

BPCWriteBackdll

InteropDTSdll

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

4854 CUSTOMER 2012-06-13

Name Remark

OSoftAdminServerdll

OSoftAuditdll

OSoftComLibServerdll

OSoftCommonResQrydll

OSoftConfigurationdll

OSoftCustomXMLSvrdll

OSoftDatabaseADMINdll

OSoftDatabaseSYSADMINdll

OSoftDatabaseSYSADMINDMdll

OSoftDatabaseUSERdll

OSoftDMDTSXExecutedll or OSoftDMDTSXExecute2012dll

OSoftDMTaskFormdll

OSoftDMTaskMaindll

OSoftDMToolsdll

OSoftFileManagedll

OSoftLoggingdll

OSoftLogWriterdll

OSoftMetaDatadll

OSoftSQEdll

OSoftSystemConfigdll

OutlookSoftconfig Configuration file to connect DB server

XceedCompressiondll XceedZip file

XceedCompressionFormatsdll XceedZip file

XceedFileSystemdll XceedZip file

XceedZipdll XceedZip file

Config folder

This folder has FileListxml 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 FileListxml 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

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4954

OSoftSetupexe

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

NOTE

If you installed the OSoftSSIS2008_Client or OSoftSSIS2012_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

Resources Folder

This folder contains the BPCServicesdll and BPCServiceUIdll files which contain resource text

Only English resources are included for the SSIS custom tasks

82 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

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008 and 2012 respectively

8 Installing SSIS Custom Tasks

82 Before You Modify the SSIS Packages

5054 CUSTOMER 2012-06-13

Name Remark

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012 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

lthellipgtOSoftSSIS2008_Clientbin or lthellipgtOSoftSSIS2012_Clientbin

On the Planning and Consolidation application server

ltdrivegtWebsrvrbin

2 Paste these files into the folder 100DTSTasks for SQL Server 2008 or into 110DTSTasks for

SQL Server 2012 For example if you install your SQL 2008 server or R2 on CProgram Files

Microsoft SQL Server paste all files into the CProgram Files (x86)Microsoft SQL Server

100DTSTasks folder

In Integration Services set the property Run64BitRunTime to True

83 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 or OSoftSSIS2012_Client on the

application server

8 Installing SSIS Custom Tasks

83 Setup of a COM+ Application on the Application Server

2012-06-13 CUSTOMER 5154

Typographic Conventions

Example Description

ltgt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example Enter your ltUser Namegt

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 httpwwwsapcom

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

5254 CUSTOMER 2012-06-13

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

  • SAP BusinessObjects Planning and Consolidation 100
    • Table of Contents
    • 1 Introduction
      • 11 SAP Notes for the Installation
      • 12 Naming Conventions
        • 2 Installing Planning and Consolidation Servers
          • 21 Basic Steps
          • 22 Prerequisites
          • 23 Before Starting the Planning and Consolidation Server Installation
          • 24 Logging on to Servers
          • 25 Service-level Accounts
          • 26 Standard and Advanced Settings
          • 27 Installing the Prerequisites
            • 271 Installing the Prerequisites ndash Basic Steps
            • 272 Installing the Operating System
            • 273 Installing the SQL Server
            • 274 Installing Analysis Services
            • 275 Installing the Anti-Cross Site Scripting Library
              • 28 Installing on a Single Server
              • 29 Installing the Server in a Multiserver Configuration
                • 3 After Installing Planning and Consolidation Servers
                  • 31 Post-Installation Steps
                  • 32 Connecting to Solution Manager Diagnostics
                  • 33 Configuring the Planning and Consolidation NET Application Servers
                  • 34 Post-Installation Optional Configuration Steps
                    • 341 Enabling the Management Console
                    • 342 Setting Up ODBC Logging in IIS for the Default Web Site
                    • 343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2
                    • 344 Removing Default Access to the Console
                    • 345 Management Console Access Control
                    • 346 Using Client Certificates
                        • 4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office
                          • 41 Installing the Administration Client
                          • 42 Installing the EPM Add-in
                          • 43 Using the Client Auto Update Program
                            • 5 Connection Issues
                              • 51 Checking for Open Ports
                              • 52 Proxy Server and Firewall Issues
                                • 6 Installing Planning and Consolidation with Two Active Directory Domains
                                • 7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
                                  • 71 Terminal Services Home Directories
                                  • 72 System Requirements
                                  • 73 Installing Planning and Consolidation
                                  • 74 Creating a Shortcut to the Launch Page
                                    • 8 Installing SSIS Custom Tasks
                                      • 81 Composition of SSIS Custom Task Installation
                                      • 82 Before You Modify the SSIS Packages
                                      • 83 Setup of a COM+ Application on the Application Server
                                          • Copyright and trademarks
Page 8: Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

SAP Note Number Title Comments

1584890 Documentation Addendum Contains information that does not appear in the application help of Planning and Consolidation 100 version for the Micrososft platform

1733053 SAP Planning and Consolidation 100 SP08 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP08This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1689792 SAP Planning and Consolidation 100 SP07 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP07This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1665656 SAP Planning and Consolidation 100 SP06 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP06This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1643037 SAP Planning and Consolidation 100 SP05 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP05This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1620464 SAP Planning and Consolidation 100 SP04 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP04This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1601213 SAP Planning and Consolidation 100 SP03 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP03This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1591848 SAP Planning and Consolidation 100 SP02 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP02This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

1 Introduction

11 SAP Notes for the Installation

854 CUSTOMER 2012-06-13

SAP Note Number Title Comments

1573539 SAP Planning and Consolidation 100 SP01 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP01This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

12 Naming Conventions

In this document the following naming conventions apply

Variable Description

ltPC_serverportgt Server name or IP address and port number of SAP Planning and Consolidation application location

ltdrivegt The drive where SAP Planning and Consolidation is installedThe default for this is CPC_MS

1 Introduction

12 Naming Conventions

2012-06-13 CUSTOMER 954

This page is left blank for documents that are printed on both sides

2 Installing Planning and Consolidation Servers

This section includes the basic steps for installing a Planning and Consolidation server the prerequisites

and what to do before during and after the server installation

21 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 at httpservicesapcominstguidesepm-bpc 100 version for the Microsoft platform

2 Perform the tasks in the Before Starting the Planning and Consolidation Server Installation [page 13] section

including installing all prerequisites

3 From the application server install the Planning and Consolidation server See Installing Planning and

Consolidation on a Single Server [page 24]

NOTE

You must install both Planning and Consolidation 100 as well as the most recent Planning

and Consolidation 100 Support Package available from the SAP Service Marketplace at

httpservicesapcomswdc Software Downloads Support Packages and Patches A - Z Index

B SAP BPC FOR MICROSOFT SBOP PC 100 FOR MICROSOFT Comprised Software Component

Versions SAP CPM BPC 100 M Windows Server on x64 64bit

4 If you have multiple machines see Installing the Server in a Multiserver Configuration [page 26]

5 Perform the steps in the section After Installing Planning and Consolidation Servers [page 27]

22 Prerequisites

The following table describes the software you need to install before installing the Planning and

Consolidation server and the minimum versions required

NOTE

A list of the supported operating systems and database systems is also available in the Product

Availability Matrix on SAP Service Marketplace at httpservicesapcompam Search on

Planning and Consolidation

2 Installing Planning and Consolidation Servers

21 Basic Steps

2012-06-13 CUSTOMER 1154

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 or

Data Center with or without Hyper-V

NOTE

The operating system must be configured with NTFS

Relational Database Microsoft SQL Server 2008 Enterprise Edition Microsoft SQL Server 2008 R2 (Gemini) Enterprise Edition Microsoft SQL Server 2012 Enterprise Edition

OLAP Database Microsoft SQL Server 2008 Enterprise Edition ‒ Analysis Server Microsoft SQL Server 2008 R2 Enterprise Edition ‒ Analysis Server Microsoft SQL Server 2012 Enterprise Edition ‒ Analysis Server

Data Integration Microsoft SQL Server 2008 Enterprise Edition ‒ SQL Service Integration Services

Microsoft SQL Server 2008 R2 Enterprise Edition ‒ SQL Service Integration Services

Microsoft SQL Server 2012 Enterprise Edition ‒ SQL Service Integration Services

Other Requirements MSXML 40 SP2 or later ADOMDNET

ADOMDNET 100 when running SQL Server 2008 or 2008 R2 ADOMDNET 110 when running SQL Server 2012

SQL Server software components NET 40 IIS 75 or IIS 70

(Included in your Operating System IIS 75 is required for Windows 2008 R2 editions)

Anti-Cross Site Scripting Library 42This component must be downloaded before installing the server The server installation program asks for the path of each file and copies the files into the appropriate Planning and Consolidation path

Microsoft Visual C++ 2005 Runtime Libraries SP1 Microsoft Access Database Engine 2010 64bit VMWare ESX 3x or ESX 40

(Required only if a landscape deployment strategy using virtualization technologies is planned)

NOTE

MSXML 40 SP2 ADOMDNET 100 and Microsoft Visual C++ 2005 Runtime Libraries SP1 are included with the installation program but not installed automatically

RECOMMENDATION

For SQL Server 2008 only we recommend the installation of Microsoft SQL Server 2008 SP1

(or later) cumulative update package 6 or higher to solve a problem with incorrect periodic

2 Installing Planning and Consolidation Servers

22 Prerequisites

1254 CUSTOMER 2012-06-13

values being returned with calculated accounts For more information see SAP Note number

1429246 which also contains download information

We recommend SQL Server 2008 (or R2) Enterprise Edition or SQL Server 2012 Enterprise

Edition for the OLAP database to support proactive cache and cube partitioning It is

technically possible to use SQL Server 2008 (or R2) Standard Edition or SQL Server 2012

Standard Edition for data integration servers but we do not recommend this

23 Before Starting the Planning and Consolidation Server Installation

You must perform the following tasks before starting your Planning and Consolidation server

installation

Install all the prerequisite software including all of the latest Microsoft hotfixes For more

information see Installing the Prerequisites [page 17]

If you access your application through a firewall verify with your network administrator which

TCP ports to choose during the installation By default port 80 is the setting for standard http

access and port 443 is the setting for https access If you require a service to listen on a different

port you can specify it during the installation program in Advanced Settings See Standard and Advanced

Settings [page 16]

Make sure all required server ports are open and that there is communication between the physical

servers on which you are going to install the server types See Checking for Open Ports [page 41]

Set up the required service accounts that you need to install the Planning and Consolidation server

See Service-Level Accounts [page 15]

The sample environment EnvironmentShell has been updated in this version of Planning and

Consolidation and automatically overwrites the previous version If you have made any

modifications to EnvironmentShell that you want to keep make a copy of it before continuing

with the installation

If you have the URLScan and IIS Lockdown tools installed on your application server you must

reinstall them

Disable your anti-virus software program After the installation when you enable the program

turn off Script Blocking

If a version of Planning and Consolidation on a NetWeaver platform exists uninstall it before you

install Planning and Consolidation 100 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 fsntfsV

All servers in a multiserver environment must be members of the same domain

2 Installing Planning and Consolidation Servers

23 Before Starting the Planning and Consolidation Server Installation

2012-06-13 CUSTOMER 1354

In a multiserver environment the installing ID must be a domain user ID We recommend that

you do not log on to the servers using a local server user ID even if the user ID is a member of the

Administrator group on the server This way you have the proper authority to install software and

to modify the Component Services See Logging On to Servers [page 14]

You must determine the IP addresses or server names for all servers before installing Planning and

Consolidation We recommend that you use static IP addresses

IIS must be enabled

If the application server is not able to copy files to the database server during the installation because

of port access reasons (DMZ WORKGROUP or nontrusted domain authentication failures) do

the following

1 Copy the EnvironmentShell database file ServerEnvironmentShelldb10 from the

Planning and Consolidation installation program to any folder on the SQL server (for example

cEnvironmentShelldb10)

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 cEnvironmentShelldb10)

Install the Anti-Cross Site Scripting Library which provides protection to Web-based applications

against Cross-Site Scripting (XSS) attacks See Installing the Anti-Cross Site Scripting Library [page 24]

24 Logging on to Servers

When installing in a multiserver environment you must use a domain user ID to log on to all

components

A local server user ID is a member of the Administrator group on the server A domain user ID is a

member of the Administrator group of a domain to which the server belongs or a member of the

Administrator group on the local server

Errors may display during the installation program and in the diagnostic program if the installing user

is not assigned to the Administrator group directly but is assigned to a group with Administrator rights

You can ignore these messages

NOTE

If you change the password used to install Planning and Consolidation you must change the

password for the applicable Planning and Consolidation service To do this go to Server Manager

on the application server and select Server Reset Logon Credentials For more information see

the SAP Planning and Consolidation Operations Guide in httpservicesapcominstguidesepm-bpc

100 for the Microsoft Platform SBOP Plan amp Consol 100 MS Administrators Guide

2 Installing Planning and Consolidation Servers

24 Logging on to Servers

1454 CUSTOMER 2012-06-13

25 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

PrerequisitesPlanning and Consolidation 100 has the following Windows services

BPC SendGovernor which manages Microsoft Analysis Service locks to ensure consistent performance

and avoid deadlocks

BPC ServiceManager which manages the System Landscape Directory (SLD) service logging service

and global caches

BPC CTS ServiceManager which listens and handles CTS import requests from the CTS+ transport

management system

Since these services should be able to access to the FileShare server an Admin account is assigned

automatically to the service during the installation of the Planning and Consolidation server program

Even though an Admin account has been assigned to the server correctly the services may fail to start

with the error message

Could not start the BPC SendGovernor service

The reason for this is that the Admin account is not registered as a service

When installing a service to run under a domain user account the account must have the right to

logon as a service on the local machine This logon right strictly applies only to the local computer

and must be granted in the Local Security Policy

To edit the Local Security Policy of the computer you want to define the logon as a service

permission perform the following actions

1 Start the Local Security Settings Microsoft Management Console (MMC) snap-in

2 Expand Local Policies and then click User Rights Assignment

3 In the right-hand pane right-click Log on as a service and then click Security

4 Add the user to the policy and click OK

5 Close the Local Security Settings MMC snap-in

For more details see How to Troubleshoot Service Startup Permissions http

supportmicrosoftcomkb259733

FeaturesDuring the installation enter user IDs and passwords for the following user types

System Admin ID

This ID is read-only and is the same as the installation user ID that is the system displays the ID

on the installation screen but you cannot modify it This ID allows access to code that provides

2 Installing Planning and Consolidation Servers

25 Service-level Accounts

2012-06-13 CUSTOMER 1554

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 readwrite 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

26 Standard and Advanced Settings

The following tables describe the standard and advanced settings for the installation program After

the server is installed you can change these settings using the Server Manager

NOTE

When defining server names the name refers to the NetBIOS name IP address and fully qualified

domain names (FQDN)

Standard Settings

Standard settings are typically used for a single-server environment The following table describes each

setting

Server Option Value Description

SQL Database server name The name of the SQL DB server

OLAP server name The name of the OLAP server

File Share server name The default value is the name of the File Share server that should be the computer name

Local data path Where the data files are saved on the File Share server By default this is CPC_MSData

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

Server Option Value Description

SQL Server Name The name of the SQL DB server Defaults to the local server

2 Installing Planning and Consolidation Servers

26 Standard and Advanced Settings

1654 CUSTOMER 2012-06-13

Server Option Value Description

Instance name The SQL instance name If left blank the default instance is used

Port number The default port number for the SQL Server is 1433

Provider The only available value is SQL

Local path for EnvironmentShell 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 CPC_MSData

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 changesSee the Kerberos authentication settings section in the SAP Library Server Manager Guide on httpservicesapcominstguidesEPM-BPC

100 for the Microsoft Platform

Scheduler Server Name The name of the server used for scheduling usually the application server for example GMPV50072862B If you have multiple application servers select the appropriate one

NOTE

If the primary server stops working you must manually configure your application server database to froward requests to another application server

27 Installing the Prerequisites

271 Installing the Prerequisites ndash Basic Steps

Before installing your Planning and Consolidation server you must install the prerequisite Microsoft

software the operating system IIS SQL server analysis services ADOMDNET and MSXML This

section provides guidance on installing each component For specific versions required see

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 1754

Prerequisites [page 11] and the Product Availability Matrix on the SAP Service Marketplace at http

servicesapcompam Search on Planning and Consolidation

NOTE

To ensure a successful installation you must install the software in the order listed in this

procedure

Check all third-party infrastructure services to ensure that they are functioning and that their

authentication models are documented (stated) since you need to reference this information

during the installation These third-party services include IIS OLAP service SQL services and

Active Directory (AD)

We recommend not installing Microsoft Office on the application server

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

(UMCexe) on the Planning and Consolidation CD in a folder called UMC_100_INSTALLER When

you run the installation package the wizard guides you through the following steps

1 Choose a language for the UMC install wizard to use

2 Check that the prerequisite check status is Succeeded and click Next

3 When you are ready to install the UMC click Next on the welcome screen

4 Click I accept the License Agreement and then Next

5 Choose the destination directory for the UMC installation and click Next

6 Select the languages that you wish to install

7 Select the features that you want to install (POAFHelper dotnet is mandatory for Planning

and Consolidation)

8 On Start Installation click Next to complete the installation

2 Install the required operating system on the single-server computer or on each physical server for

a multiserver configuration See Installing the Operating System [page 19]

3 Install the latest service pack for your operating system To install this service pack go to http

wwwmicrosoftcom

4 From your operating systems media install IIS

5 From your SQL Server media install SQL Server and its required service packs and hot fixes See

Installing SQL Server [page 19]

6 From your SQL Server media install Analysis Services Enterprise Edition and its required service

packs and hot fixes See Installing Analysis Services [page 23]

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

1854 CUSTOMER 2012-06-13

7 On your application server install ADOMDNET The Planning and Consolidation zip file contains

the ADOMDNET installation package in the following locations

For SQL Server 2008 mdash BPC SetupServerSQLSERVER2008_ASADOMD10_x64msi

For SQL Server 2012 mdash BPC SetupServerSQLSERVER2012_ASADOMD11_x64msi

8 On your application server install MSXML 40 Service Pack 2 or later

The MSXML 40 SP2 installation package is contained in the Planning and Consolidation zip file at

the following location BPC SetupServermsxmlmsi

9 On your application server install Microsoft Visual C++ 2005 Runtime Libraries SP1

The Microsoft Visual C++ 2005 SP1 installation package is contained in the Planning and

Consolidation zip file at the following location BPC SetupServervcredist_x64exe

NOTE

The version of vcredist_x64exe in BPC SetupServer has been updated to 8061000 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 httpwwwmicrosoftcomdownloadsen

detailsaspxFamilyID=C06B8369-60DD-4B64-A44B-84B371EDE16Dampltdisplaylanggt=en

272 Installing the Operating System

Before installing the operating system make sure that you configure your server for NTFS

For a list of languages that are supported see the Product Availability Matrix on the SAP Service

Marketplace at httpservicesapcompam Search on Planning and Consolidation

Planning and Consolidation can support all servers with an operating system in any language

NOTE

Currently Planning and Consolidation does not support an operating system in bi-directional

languages such as Hebrew

ProcedureIf you are installing IIS 70 or 75 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

273 Installing the SQL Server

PrerequisitesDuring the installation procedure you have the opportunity to specify the location of the

EnvironmentShell database file Check that it is possible to access EnvironmentShell from the location

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 1954

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 CEnvironmentShelldb10) 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 a 2008 2008 R2 and 2012 SQL Server

SQL Server Considerations

We recommend installing all required components in sequence For example install the Operating

System (Windows Server) then enable IIS and ASPNET and install any Windows Server service

packs

IIS and NET Framework 40 are required on your application server

NOTE

If you encounter a 500 HTTP Error when trying to connect to the Planning and Consolidation

Web Client refer to Microsoft Support articles 2520479 and 2468871 for assistance

To reinforce security we recommend that you install the SQL server and SSAS components to a

nondefault instance of SQL Server

General Installation Steps

1 Launch the SQL Server Setup program entering a product key if necessary and accepting the license

terms

2 Choose Install to install the SQL support files

3 In Feature Selections select instance and shared features as indicated in the SQL Server Component

Options section below then choose Next

4 Review disc space requirements then choose Next

5 In Server Configuration Perform the following actions

1 In the Service Accounts tab enter a Planning and Consolidation sysadmin account for the SQL

Server Database Engine and the SQL Server Analysis services This is required so that the Planning

and Consolidation sysadmin can create and process the Planning and Consolidation database

because the Microsoft SQL server tries to back up or restore database with the privileged

account This account is also required during Backup Environment and Restore Environment in the

Server Manager

For a single-server environment this account is also required if the backup file is located in a

different domain machine because SQL tries to access the folders and files with this account

For the a multiple-server environment SQL server retrieves the information of backup file

from the application server and the account requires the folder access privilege for the

application server

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2054 CUSTOMER 2012-06-13

To ensure that you have the complete access privileges we recommend the Planning and

Consolidation sysadmin for this service account

2 In the Collation tab set the collation settings to SQL_Latin1_General_CP1_CI_AS

Choose Next

6 Set Database Engine Configuration options then choose Next

We recommend you choose Mixed mode (Windows authentication and SQL authentication) This allows you

to use a restrictive SQL ID that works with the drill-through feature If you must restrict SQL

authentication for security reasons you can define a specific parameter in your drill-through

queries If you do not need drill-through support or use it without leveraging SQL authentication

you can install the SQL Server in Windows-only mode

7 Accept the Analysis Services Configuration default options and the remaining default options of the

installation program

8 Choose Install to begin the installation with the options you have set

SQL Server Component 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

Server Component What to Install

SQL Server Database Engine Services

SSAS Server Analysis Services

Application Server The following Shared Features Client Tools Connectivity Integration Services Client Tools SDK

Custom Settings for the SQL Server

As of version 100 Planning and Consolidation supports the following new features for SQL Server 2008

SQL Server 2008 R2 and SQL Server 2012

Process Dimension

It is now possible to process a dimension with multiple selections At processing time the process

dimension module makes changed or added information for each dimension and process for all selected

dimensions and cubes in parallel

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 2154

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

NOTE

Setting 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 tblFactWBltappgt table

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 Microsoftreg SQL Servertrade

20052008 which you can download from wwwmicrosoftcom (search on ldquoTable Partitioningrdquo to find

all relevant articles)

After Installing SQL Server 2008 SQL Server 2008 R2 and SQL Server 2012

From SQL Server Configuration Manager confirm that the SQL Server Browser service is

running The browser service is required for Planning and Consolidation

From SQL Server Configuration Manager do the following

1 Select Protocols for ltInstanceNamegt then double-click TCPIP from the right side of the window

2 When prompted for the TCPIP Properties select IP Addresses You see two IPs that indicate the

localhost and external network interface machine

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2254 CUSTOMER 2012-06-13

3 If you want to use IP1 which indicates Server IP set Enabled to Yes and specify the TCP Port as

desired

4 Delete 0 from TCP Dynamic Ports Set IPAll - TCP Ports as desired (for example 1533)

RECOMMENDATION

We do not recommend using dynamic ports

In an SQL server the default instance has a listener which listens on a fixed port (TCP

port 1433) However for the named instance the port on which the SQL server listens is

random and dynamically selected when the named instance of the SQL server starts This

recommendation prevents any conflict problems

From the SQL Server Configuration Manager specify the client protocol options for the application

server

1 Select Client Protocols from the SQL Native Client Configuration folder

2 From the right side of the window double-click TCPIP The TCPIP 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

NOTE

We 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

274 Installing Analysis Services

ProcedureAfter you install SQL Server and its required service packs and hotfixes you must install SQL Server

Analysis Services and its required service packs and hotfixes

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 2354

NOTE

If you have migrated your Analysis Services repository to the SQL Server back up the database

that contains the repository before installing this release

To install Analysis Services for SQL Server 2008 SQL Server 2008 R2 or SQL Server 2012 follow the steps

and guidelines in httptechnetmicrosoftcomen-uslibraryms143219aspx

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 httpwwwmicrosoftcomdownloads

detailsaspxFamilyID=3be0488d-e7aa-4078-a050- ae39912d2e43ampdisplaylang=en

275 Installing the Anti-Cross Site Scripting Library

Procedure

Before installing Planning and Consolidation servers you must download the Anti-Cross Site Scripting

Library (version 42 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 AntiXSSLibraryDLL from the Microsoft Web

site at httpwwwmicrosoftcomdownloadendetailsaspxid=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 AntiXssLibrarydll

28 Installing on a Single Server

When you install all Planning and Consolidation server components on a single server you should

consider the following issues

Make sure the server has a minimum of 800 MB of hard disk space

Additional environment installations require more free disk space which is a minimum of two

times the uncompressed size of the environment files

When you install Planning and Consolidation on a single-server the system adds the following server

components

SQL Server

SQL Server Analysis Services (SSAS)

Application Server

FileShare server

Procedure

To install Planning and Consolidation on a single server take the following steps

1 Exit all Windows programs

2 Installing Planning and Consolidation Servers

28 Installing on a Single Server

2454 CUSTOMER 2012-06-13

2 Log on to the server with a local server user ID or domain user ID For more information see Logging

on to servers [page 14]

3 Make sure all prerequisite software is installed on the server For more information see Installing

the Prerequisites [page 17]

4 Obtain SAP Planning and Consolidation from the Downloads SAP Installations amp Upgrades area of

SAP Service Marketplace then extract the files and run StartUpexe

5 From the Server Install screen select Install the Planning and Consolidation server

6 From the Welcome screen choose Next

7 From the License Agreement page choose I accept the terms of the license agreement then choose Next

8 From the Installation Method page accept the default Single machine enter a system ID for the system

landscape directory (SLD) and choose Next

NOTE

Entering a system ID of the SLD is only required if you have a SAP Solution Manager license

If you do not have a SAP Solution Manager license you can leave this field empty

9 From the Authentication Method page choose the desired authentication method and choose Next

10 If you have chosen SAP BusinessObjects User Management System in the previous screen on the CMS

Authentication page enter the information required to log on to CMS as an administrator

The following information is required

Field Description

System name CMS system name (server nameport number) for example CMSServer6400

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

11 After entering the CMS administrator authentication details choose Next

12 From the Service type accounts page enter service-level account user IDs and passwords See Service-

Level Accounts [page 15]

13 After defining the IDs and passwords choose Next

14 From the Server Information page (see Standard and Advanced Settings [page 16]) do one of the following

Review the standard settings and choose Next

To set advanced settings choose the Advanced Settings button Enter the desired information

and choose Next

2 Installing Planning and Consolidation Servers

28 Installing on a Single Server

2012-06-13 CUSTOMER 2554

15 Specify the location and name of AntiXssLibrarydll See Installing the Anti-Cross Site Scripting Library [page

24]

Choose Next

16 Select destination folders for Programs and Data The Data files include Webfolders and FileDB

(published reports) and should be installed on a separate drive in a production environment This

recommendation reduces the hard disk IO time and helps to speed up SQL commands

Accept the defaults or make your selections then choose Next

17 Select the default values for the Web client The values are used to determine the default language

and region for the Web client when you connect to it You can change the values in the Planning

and Consolidation Server Manager

18 The installation process takes a few moments When it is complete choose Exit

19 A prompt is displayed to restart your computer Select OK to restart

20 Perform the steps in After Installing Planning and Consolidation Servers [page 27]

29 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 24]) with the following

exceptions

On the Installation Method page do not accept the default instead choose Network Load Balancing

environment With this option there is an additional choice to Include sample environment (required on only

one of the application servers) This is because when you install the application server it connects to the

database server and creates the sample environment (EnvironmentShell) Installing the sample

environment is required on only one application server and you may choose which one

In the Virtual Name field enter the virtual IP address virtual name in the default properties

2 Installing Planning and Consolidation Servers

29 Installing the Server in a Multiserver Configuration

2654 CUSTOMER 2012-06-13

3 After Installing Planning and Consolidation Servers

31 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 28]

2 Configure the Planning and Consolidation NET and application server to ensure that it and its

related services function properly and reliably For more information see Configuring the Planning and

Consolidation NET Application Server [page 29]

3 Optional configuration steps [page 30]

1 To ensure proper functioning of the Management Console create an SQL user and modify

the System DSN and IIS to reflect those user credentials See Enabling Management Console [page

30]

2 Configure custom ODBC logging for the default Web site For details of how to configure

custom logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web

Site [page 31]

3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC

Data Source [page 32]

4 Modify the default access rights to the Management Console By default users in Active

Directory can access the Management Console with whatever rights they have been granted

on the server For information about removing default access and creating a group that can

access the console see Removing Default Access to the Console [page 32]

5 Add authorized users or groups to the group that can access the Management Console We

recommend that you only grant Management Console access to system administrators

Planning and Consolidation users should not have any access For more information see

Management Console Access Control [page 33]

6 Configure the use of client certificates for authentication See Using Client Certificates [page

34]

4 Take the following steps to set up security

If you are defining security and application structure continue with step 5

3 After Installing Planning and Consolidation Servers

31 Post-Installation Steps

2012-06-13 CUSTOMER 2754

If you want to designate someone other than the system administrator to manage security

and application structure log on to EnvironmentShell designate a user as a Primary

Administrator

This user must have Administration ‒ Environment and Security ‒ Define User task rights

so that he or she can add and delete environments and define user security

The Primary Administrator can continue with the next step (5)

5 From the machine on which you administer Planning and Consolidation install the

Administration client See Installing the Administration Client [page 37]

6 Start Planning and Consolidation Administration from the launch page

7 Select Connection Wizard and log on to EnvironmentShell

8 Create a new environment using EnvironmentShell as the source

9 Log on to the newly created environment and set up users teams and task profiles (You must

set up task profiles since there is no access to Planning and Consolidation tasks)

10 Set up your data access profiles and add users (or teams) to one or more data access profiles (You

must complete this step since there is no access to dimensions or members)

NOTE

To allow users to request and query large amounts of data you can edit the metabasexml file located

at CWindowssystem32inetsrv Set the following parameters to the stated values

ASPBUFFERINGLIMIT = 10485760

MAXREQUESTENTITYALLOWED = 10485760

32 Connecting to Solution Manager Diagnostics

NOTE

You only need to perform the steps in this section if you have a SAP Solution Manager licence

The diagnostics functions in SAP Solution Manager allow identification analysis and resolution of

problems This procedure provides the steps required to connect Planning and Consolidation to

Solution Manager Diagnostics

Procedure

1 Install the Diagnostics Agent according to SAP Note 1234387 on all servers where application servers

are installed

NOTE

Installation files for Diagnostics Agent are available on Service Marketplace by navigating to

Support Packages and Patches mdash Entry by Application Group SAP Technology Components SAP

SOLUTION MANAGER SAP SOLUTION MANAGER 70 EHP 1 Entry by Component Agents

for managed systems DIAGNOSTICS AGENT 711

3 After Installing Planning and Consolidation Servers

32 Connecting to Solution Manager Diagnostics

2854 CUSTOMER 2012-06-13

Download the installation file based on the 64-bit Windows Server system landscape

2 To access the DBA Cockpit you must create a user account with sufficient rights on all Windows

Servers where Microsoft SQL Server is installed Do the following

1 Start Computer Management then select Action New User

2 Create a new user

3 Right-click on the user then choose Properties On the Member Of tab select Add

4 Add the group SQLServerltReleasegtSQLAgentUser$ltDomain or hostnamegt$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 httpsservicesapcom~sapidb011000358700000074392009E and follow

the chapters that apply to Planning and Consolidation

33 Configuring the Planning and Consolidation NET Application Servers

Procedure

Modifying machineconfig Files

To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock

occurrences that would cause the application server to ldquosleeprdquo and not process anymore you can

modify the machineconfig file which resides in the WINDOWSMicrosoftNETFramework64

v4030319Config directory

1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to

specify whether to automatically configure settings to achieve optimal performance based on the

machine configuration You can set this attribute to True or False

For more information see httpmsdnmicrosoftcomen-uslibrary7w2sway1aspx

2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the

Planning and Consolidation application) or Machineconfig (for all applications including

Planning and Consolidation) to ensure the validationKey and decryptionKey keys have the same

value on all application servers This way when the authentication cookie is checked the

authentication ticket used on one server can still be valid on another server

For more information and sample Visual Basic code for generating random key values see http

msdnmicrosoftcomen-uslibraryms998288aspx

3 After Installing Planning and Consolidation Servers

33 Configuring the Planning and Consolidation NET Application Servers

2012-06-13 CUSTOMER 2954

paght000007_webfarmdeploymentconsiderations and httpmsdnmicrosoftcomen-us

libraryms998310aspx

34 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 30]

2 Configure custom ODBC logging for the default Web site For details of how to configure custom

logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page

31]

3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC Data

Source [page 32]

4 Modify the default access rights to the Management Console By default users in Active Directory

can access the Management Console with whatever rights they have been granted on the server

For information about removing default access and creating a group that can access the console

see Removing Default Access to the Console [page 32]

5 Add authorized users or groups to the group that can access the Management Console We

recommend that you only grant Management Console access to system administrators Planning

and Consolidation users should not have any access For more information see Management Console

Access Control [page 33]

6 Configure the use of client certificates for authentication See Using Client Certificates [page 34]

341 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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3054 CUSTOMER 2012-06-13

NOTE

Without these updates the Management Console does work but some functionality (specifically

User Activity and Service Status) does not work as expected

Should you need to uninstall Planning and Consolidation we recommend that you reset the

Active Log Format field in IIS to W3C Extended Log File Format

342 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 ApplicationHostconfig set the property customLogPluginClsid to the value FF16065B-

DE82-11CF-BC0A-00AA006111E0 Set the logFormat to Custom You can find this in the ltlogFilegt

node in ApplicationHostconfig as shown here

ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0

logFormat=Custom gt

Use the following AppCmds to configure IIS to use ODBC logging for the default Web site

appcmd site set sitenameDefault Web Site

logFilecustomLogPluginClsidFF16065B-DE82-11CF-BC0A-00AA006111E0

appcmd site set sitenameDefault Web Site logFilelogFormatCustom

Configuring ODBC Logging Parameters in ApplicationHostconfig

Configure ApplicationHostconfig to contain the database table information as set up in the Microsoft

Support article specified in the Prerequisites section Configure these settings in the ltodbcLogginggt

node under ltsystemwebServergt

EXAMPLE

ltlocation path=Default Web Sitegt

ltsystemwebServergt

ltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog

userName=Username password=mypassword gt

ltsystemwebServergt

ltlocationgt

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3154

Use the following AppCmds to configure these attributes for the default Web site

appcmd set config Default Web Site sectionodbcLogging

dataSourceBPC_ManagementDSN commitappHost

appcmd set config Default Web Site sectionodbcLogging tableNameBPCLog

commitappHost

appcmd set config Default Web Site sectionodbcLogging userNameUsername

commitappHost

appcmd set config Default Web Site sectionodbcLogging passwordmypassword

commitappHost

NOTE

You cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must

use the SQL Server ODBC driver For more information see the Microsoft Knowledge Base article

931202 The requirements for using the ODBC logging feature in IIS

343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2

ProcedureThis procedure describes how to set up an ODBC data source for the Management Console in Windows

Server 2008 or Windows Server 2008 R2

Proceed as follows

1 Open ODBC Connection Manager

2 On the System DSN tab page add a new DSN

Choose Add

Choose SQL Server as the driver

Choose Finish

3 In the Name and Description fields enter BPC_ManagementDSN

4 In the Server field enter the name of your SQL Server Choose Next

5 Leave the default settings and choose Next

6 Choose the Change the default database to field and enter AppServer Choose Next

7 Leave default settings and choose Next

8 Choose OK

344 Removing Default Access to the Console

NOTE

If you have chosen SAP BusinessObjects User Management System in the installation screen you

do not need to remove or configure access because the Management Console service always runs

with the System Admin ID account which is a member of the Administrators group

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3254 CUSTOMER 2012-06-13

ProcedureTo remove default access to the Management Console and create a group that does have access to the

console use the procedure described below

NOTE

Create your Management Console administrative group either on the server that hosts the

Management Console or in the Active Directory

1 In the context menu of the servers My Computer icon choose Manage

2 In the Computer Management dialog box choose Local Users and Groups Groups

NOTE

Alternatively you can perform analogous steps in Active Directory

3 In the 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

NOTE

This step is a necessary precursor to the completion of this procedure

10 In the Security dialog box click Copy to ensure that the System group retains its privileges

11 Remove access to the Management Console from all groups that should not have it

12 Choose Authentication in the center pane then disable Windows authentication

ResultUsers who have not been granted access to the Management Console can still open the Management

Console Web page but it contains no data or menu options This does not affect the access that a user

would otherwise have to Planning and Consolidation

345 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 32] Their rights in

Active Directory determine what they can access in the Console

By default any member of the Administrators Active Directory group on the application server or

domain has full access to all of the features of the Console except the Planning and Consolidation

logging area Access to Planning and Consolidation logging is controlled within the Planning and

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3354

Consolidation Administration Client task security The user must be granted View system logs task

privileges For more information see the SAP Library Planning and Consolidation Administrators Guide in

httpservicesapcominstguidesepm-bpc 100 version for the Microsoft platform

Your IT policy determines whether you grant access by group or user You may wish to create several

levels of Console users (read-only users for example) in your environment

To grant or limit access to users or groups you can add or remove the following privileges from the

areas described in this table

Privilege Rights Management Area

Task Manager and Kill Process Administrators group on application server or domain

Performance Monitor Counters Administrators group on application server or domain Power Users group on application server or domain Performance Monitor Users group on application server

Microsoft Analysis Services performance monitoring

Administrators group on application server or domain

Microsoft SQL Server Monitoring (performance counters and statistics)

Administrators group on application server or domain

346 Using Client Certificates

To enable the use of client certificates in Planning and Consolidation you must follow several manual

steps

NOTE

Planning 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 httptechnetmicrosoftcomen-us

librarycc753810aspx

For more information about configuring the client certificate mapping authentication see http

technetmicrosoftcomen-uslibrarycc732996(WS10)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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3454 CUSTOMER 2012-06-13

This option allows you to use a client certificate or username and password (Basic

authentication) to connect to Planning and Consolidation

2 Enable anonymous authentication

1 In the IIS Manager expand the node of the Planning and Consolidation web site

2 Select the ManagementConsole directory (ltWebsitegtManagementConsole) to open the

ManagementConsole home page

3 Double-click Authentication and enable Anonymous Authentication

4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way

as in step 3

5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the same

way as in step 3

3 Change the web configuration settings

1 Open the ltPC_MSgtWebsrvrWebBPCwebconfig file

2 Find the text clientCredentialType=Windows

3 Change value of clientCredentialType to None (clientCredentialType=None)

4 Open the PC_MSWebsrvrWebPOASBCwebconfig file Repeat steps 2 and 3

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3554

This page is left blank for documents that are printed on both sides

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

The installation of the Planning and Consolidation Administration Client allows administrators to

build and maintain Planning and Consolidation environments and models and administer security

All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions

add-in for Microsoft Office for more information see the SAP BusinessObjects EPM solutions add-in for

Microsoft Office help

NOTE

You must update the Administration Client to the same version as the server

If your PC is on a different domain than your server you must set the Internet Explorer

Security Zone value of the Planning and Consolidation client to prompt for user name and

password Otherwise the Planning and Consolidation Start Page does not display

41 Installing the Administration Client

Prerequisites

NOTE

For a definitive list of system requirements see the Product Availability Matrix on SAP Service

Marketplace at httpservicesapcompam Search on Planning and Consolidation

The following list describes the minimum software requirements

Microsoft Internet Explorer 70 or 80

Microsoft Office 2007 or 2010

NET Framework 20 or higher (install any required NET Framework Hotfixes by referring to

httpsupportmicrosoftcomkb)

Pentium IV (1 GHz CPU)

512 MB RAM

100 MB of free hard disk space in the My Documents folder

20 MB of free hard disk space for the installed Administration files

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

41 Installing the Administration Client

2012-06-13 CUSTOMER 3754

NOTE

We recommend that you install all of the latest Microsoft Windows hotfixes prior to installing

the Administration client For information about which hotfixes to install see http

updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us

ProcedureThe following procedure describes how to install the Administration Client on to an administratorrsquos

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 AddRemove Programs in the Windows Control Panel

3 Point your browser to the Planning and Consolidation Web at httpltPC_serverportgtsap

bpcweb

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

42 Installing the EPM Add-in

The Planning and Consolidation installation media does not contain the EPM addin setup program

You must download the most recent version of the full setup (EPM Add-inexe) from the Service

Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPC

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

43 Using the Client Auto Update Program

If Planning and Consolidation version 100 or later is installed you can use the Client Auto Update

program to set up the server so that it determines if an upgrade for a connecting Administration client

is necessary

The following describes the use of the auto update program for the Administration Client and the EPM

add-in

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

42 Installing the EPM Add-in

3854 CUSTOMER 2012-06-13

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 37]

To use the Client Auto Update program for the Administration Client proceed as follows

1 From the Server Manager select Options Client Options

2 Select Admin Update

3 If users without administrator rights on their machines use the auto update enter an administrator

ID and password in the Admin ID and Admin password fields respectively The Admin ID should be a

member of the local administrators group on all the computers running the auto update This

setting is not needed if all users have administrator rights on their machines

4 Select Update

For the EPM Add-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 Optionshellip 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 Market Place (SMP) at httpservicesapcom

All support packages and patches are available from the SMP as a zip file

EPMEXCLCLNTltSPLgtzip is for a support package

EPMEXCLCLNTltSPLgtPltPLgtzip 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 ltSP versiongtmsp

EPM Addin Support Package ltSP versiongtxml

For a patch these files are

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

2012-06-13 CUSTOMER 3954

EPM Addin Patch ltpatch numbergtmsp

EPM Addin Patch ltpatch numbergtxml

2 Unzip the zip file and extract the two files to the application server folder (WebsrvrWebBPC

Installation)

3 From the Server Manager select Options Client Options

The system lists the available packages Select the package that you want to use for the autoupdate

You can set a different update policy for each package listed

EXAMPLE

The following table illustrates some possible situations assuming that you have installed the

first full version (V1)

Available maintenance packages

V2-user updateV3-force updateV4-force updateV5-user update

V5-user update V5-user updateV6-auto updateV7-force update

Minimum Required Version

V4 V4 V7

Notification A prompt tells the user to install maintenance package V4 using the Forced Update behavior

If User Update is enabled the prompt informs the user that maintenance package V5 is available

A prompt tells the user to install maintenance package V7 using the Forced Update behavior

New Version V4 V4 or V5 V7

If you change the update policy for any package click Update to complete the change

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

4054 CUSTOMER 2012-06-13

5 Connection Issues

You may experience connection problems with ports the proxy server or programs and settings that

interact with these components If you have any issues related to connection review the following

recommendations and troubleshooting tips

51 Checking for Open Ports

You must ensure that all required ports are open for inboundoutbound 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 431181836 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

NOTE

You can use the following site to scan for the normal ports It allows you to manually enter a port

number to test

httpwwwmyserverorgportsniffasp

You can change the name of a port

52 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 Explorer Tools Internet Options Connections LAN Settings ) or at the server level

Enabling content filtering on the proxy server or firewall may cause connection problems

If external users are having trouble connecting to the server make sure the proxy server connects

using a fully qualified domain name Fully qualified domain names typically resolve both internal

and external IP addresses

Each secure Planning and Consolidation server name must be identified on the proxy server

Proxy servers may or may not require authentication which could conflict with Planning and

Consolidation authentication Do not use authentication on the proxy server The system

5 Connection Issues

51 Checking for Open Ports

2012-06-13 CUSTOMER 4154

synchronizes the user name and password on the remote server with the local user name and

password

NOTE

For more information about setting up an ISA proxy server contact SAP Support to request a

copy of Setting up ISA Proxy Server White Paper

Internet Explorer Settings 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

5 Connection Issues

52 Proxy Server and Firewall Issues

4254 CUSTOMER 2012-06-13

6 Installing Planning and Consolidation with Two Active Directory Domains

To set up a Planning and Consolidation 10 application server in a hosted environment and use your

own domain users follow this procedure In general you install Planning and Consolidation on the

host domain use the host domain account and assign it to the Planning and Consolidation users

SysAdmin Admin and Users Then you accept one way trust (the host domain trusts your domain)

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

6 Installing Planning and Consolidation with Two Active Directory Domains

2012-06-13 CUSTOMER 4354

This page is left blank for documents that are printed on both sides

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

This section describes best practices and instructions for installing Planning and Consolidation in a

Terminal Services or Citrix Server deployment

71 Terminal Services Home Directories

We recommend using Terminal Server home directories rather than using the userrsquos 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

72 System Requirements

The Citrix server should be one of the following systems

XenApp 5 Enterprise

XenApp 5 Platinum

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 37])

73 Installing Planning and Consolidation

Prerequisites

The server installation files have been downloaded from SAP Service Marketplace and installed

Procedure

The following steps outline how to install the Planning and Consolidation clients in a Terminal Services

(TS) or Citrix Server deployment

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

71 Terminal Services Home Directories

2012-06-13 CUSTOMER 4554

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 userinstall

4 Open a browser and connect to the URL httpltPC_serverportgtsapbpcweb

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 userexecute 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 Iexploreexe http(s)

ltServerNamegt-NetBIOS or FQDNsapbpcweb

To publish Planning and Consolidation Administration CProgram FilesPC_MS

BPCAdminMainexe

74 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 userrsquos desktop) must be moved to the All UsersDesktop folder

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

74 Creating a Shortcut to the Launch Page

4654 CUSTOMER 2012-06-13

8 Installing SSIS Custom Tasks

This section provides background information and instructions for installing SQL Server Integration

Services (SSIS) for SQL Server 2008 and SQL Server 2012

The Planning and Consolidation Data Manager component supports and uses SSIS Since SQL Server

2008 and SQL Server 2012 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

81 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 Filelistxml 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

OSoftSetupexe ‒ 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 or OSoftSSIS2012_Client on the client machine followed by the SQL Server

version If you want to use SQL 2008 Tasks under the SQL 2012 environment you must install

OSoftSSIS2008_Client on the application server For detailed information see SAP Note 1707410

You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package by extracting

OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPC

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 or

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4754

OSoftSSIS2012_Client for creating a COM+ application For more information see Before You Modify

the SSIS Packages [page 50] and Setup of a COM+ Application on the Application Server [page 51]

Bin folder

This folder contains the following components

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCCachedll Planning and Consolidation Cache file

BPCDataFlowPackagedll or BPCDataFlowPackage2012dll

BPCDMdll

BPCDMTaskMaindll COM+ component

BPCFilePreviewdll

BPCGacUtil_20exe System File

BPCGacUtil_40exe System File

BPCImpersonatordll Planning and Consolidation Impersonator

BPCLogicdll

BPCScriptdll

BPCServerZipdll

BPCServiceResdll

BPCTransferMembersdll

BPCWriteBackdll

InteropDTSdll

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

4854 CUSTOMER 2012-06-13

Name Remark

OSoftAdminServerdll

OSoftAuditdll

OSoftComLibServerdll

OSoftCommonResQrydll

OSoftConfigurationdll

OSoftCustomXMLSvrdll

OSoftDatabaseADMINdll

OSoftDatabaseSYSADMINdll

OSoftDatabaseSYSADMINDMdll

OSoftDatabaseUSERdll

OSoftDMDTSXExecutedll or OSoftDMDTSXExecute2012dll

OSoftDMTaskFormdll

OSoftDMTaskMaindll

OSoftDMToolsdll

OSoftFileManagedll

OSoftLoggingdll

OSoftLogWriterdll

OSoftMetaDatadll

OSoftSQEdll

OSoftSystemConfigdll

OutlookSoftconfig Configuration file to connect DB server

XceedCompressiondll XceedZip file

XceedCompressionFormatsdll XceedZip file

XceedFileSystemdll XceedZip file

XceedZipdll XceedZip file

Config folder

This folder has FileListxml 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 FileListxml 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

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4954

OSoftSetupexe

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

NOTE

If you installed the OSoftSSIS2008_Client or OSoftSSIS2012_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

Resources Folder

This folder contains the BPCServicesdll and BPCServiceUIdll files which contain resource text

Only English resources are included for the SSIS custom tasks

82 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

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008 and 2012 respectively

8 Installing SSIS Custom Tasks

82 Before You Modify the SSIS Packages

5054 CUSTOMER 2012-06-13

Name Remark

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012 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

lthellipgtOSoftSSIS2008_Clientbin or lthellipgtOSoftSSIS2012_Clientbin

On the Planning and Consolidation application server

ltdrivegtWebsrvrbin

2 Paste these files into the folder 100DTSTasks for SQL Server 2008 or into 110DTSTasks for

SQL Server 2012 For example if you install your SQL 2008 server or R2 on CProgram Files

Microsoft SQL Server paste all files into the CProgram Files (x86)Microsoft SQL Server

100DTSTasks folder

In Integration Services set the property Run64BitRunTime to True

83 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 or OSoftSSIS2012_Client on the

application server

8 Installing SSIS Custom Tasks

83 Setup of a COM+ Application on the Application Server

2012-06-13 CUSTOMER 5154

Typographic Conventions

Example Description

ltgt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example Enter your ltUser Namegt

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 httpwwwsapcom

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

5254 CUSTOMER 2012-06-13

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

  • SAP BusinessObjects Planning and Consolidation 100
    • Table of Contents
    • 1 Introduction
      • 11 SAP Notes for the Installation
      • 12 Naming Conventions
        • 2 Installing Planning and Consolidation Servers
          • 21 Basic Steps
          • 22 Prerequisites
          • 23 Before Starting the Planning and Consolidation Server Installation
          • 24 Logging on to Servers
          • 25 Service-level Accounts
          • 26 Standard and Advanced Settings
          • 27 Installing the Prerequisites
            • 271 Installing the Prerequisites ndash Basic Steps
            • 272 Installing the Operating System
            • 273 Installing the SQL Server
            • 274 Installing Analysis Services
            • 275 Installing the Anti-Cross Site Scripting Library
              • 28 Installing on a Single Server
              • 29 Installing the Server in a Multiserver Configuration
                • 3 After Installing Planning and Consolidation Servers
                  • 31 Post-Installation Steps
                  • 32 Connecting to Solution Manager Diagnostics
                  • 33 Configuring the Planning and Consolidation NET Application Servers
                  • 34 Post-Installation Optional Configuration Steps
                    • 341 Enabling the Management Console
                    • 342 Setting Up ODBC Logging in IIS for the Default Web Site
                    • 343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2
                    • 344 Removing Default Access to the Console
                    • 345 Management Console Access Control
                    • 346 Using Client Certificates
                        • 4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office
                          • 41 Installing the Administration Client
                          • 42 Installing the EPM Add-in
                          • 43 Using the Client Auto Update Program
                            • 5 Connection Issues
                              • 51 Checking for Open Ports
                              • 52 Proxy Server and Firewall Issues
                                • 6 Installing Planning and Consolidation with Two Active Directory Domains
                                • 7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
                                  • 71 Terminal Services Home Directories
                                  • 72 System Requirements
                                  • 73 Installing Planning and Consolidation
                                  • 74 Creating a Shortcut to the Launch Page
                                    • 8 Installing SSIS Custom Tasks
                                      • 81 Composition of SSIS Custom Task Installation
                                      • 82 Before You Modify the SSIS Packages
                                      • 83 Setup of a COM+ Application on the Application Server
                                          • Copyright and trademarks
Page 9: Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

SAP Note Number Title Comments

1573539 SAP Planning and Consolidation 100 SP01 version for the Microsoft platform

This is the Central Note for Planning and Consolidation 100 SP01This note contains important information about the installation of SAP Planning and Consolidation 100 version for the Microsoft platform

12 Naming Conventions

In this document the following naming conventions apply

Variable Description

ltPC_serverportgt Server name or IP address and port number of SAP Planning and Consolidation application location

ltdrivegt The drive where SAP Planning and Consolidation is installedThe default for this is CPC_MS

1 Introduction

12 Naming Conventions

2012-06-13 CUSTOMER 954

This page is left blank for documents that are printed on both sides

2 Installing Planning and Consolidation Servers

This section includes the basic steps for installing a Planning and Consolidation server the prerequisites

and what to do before during and after the server installation

21 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 at httpservicesapcominstguidesepm-bpc 100 version for the Microsoft platform

2 Perform the tasks in the Before Starting the Planning and Consolidation Server Installation [page 13] section

including installing all prerequisites

3 From the application server install the Planning and Consolidation server See Installing Planning and

Consolidation on a Single Server [page 24]

NOTE

You must install both Planning and Consolidation 100 as well as the most recent Planning

and Consolidation 100 Support Package available from the SAP Service Marketplace at

httpservicesapcomswdc Software Downloads Support Packages and Patches A - Z Index

B SAP BPC FOR MICROSOFT SBOP PC 100 FOR MICROSOFT Comprised Software Component

Versions SAP CPM BPC 100 M Windows Server on x64 64bit

4 If you have multiple machines see Installing the Server in a Multiserver Configuration [page 26]

5 Perform the steps in the section After Installing Planning and Consolidation Servers [page 27]

22 Prerequisites

The following table describes the software you need to install before installing the Planning and

Consolidation server and the minimum versions required

NOTE

A list of the supported operating systems and database systems is also available in the Product

Availability Matrix on SAP Service Marketplace at httpservicesapcompam Search on

Planning and Consolidation

2 Installing Planning and Consolidation Servers

21 Basic Steps

2012-06-13 CUSTOMER 1154

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 or

Data Center with or without Hyper-V

NOTE

The operating system must be configured with NTFS

Relational Database Microsoft SQL Server 2008 Enterprise Edition Microsoft SQL Server 2008 R2 (Gemini) Enterprise Edition Microsoft SQL Server 2012 Enterprise Edition

OLAP Database Microsoft SQL Server 2008 Enterprise Edition ‒ Analysis Server Microsoft SQL Server 2008 R2 Enterprise Edition ‒ Analysis Server Microsoft SQL Server 2012 Enterprise Edition ‒ Analysis Server

Data Integration Microsoft SQL Server 2008 Enterprise Edition ‒ SQL Service Integration Services

Microsoft SQL Server 2008 R2 Enterprise Edition ‒ SQL Service Integration Services

Microsoft SQL Server 2012 Enterprise Edition ‒ SQL Service Integration Services

Other Requirements MSXML 40 SP2 or later ADOMDNET

ADOMDNET 100 when running SQL Server 2008 or 2008 R2 ADOMDNET 110 when running SQL Server 2012

SQL Server software components NET 40 IIS 75 or IIS 70

(Included in your Operating System IIS 75 is required for Windows 2008 R2 editions)

Anti-Cross Site Scripting Library 42This component must be downloaded before installing the server The server installation program asks for the path of each file and copies the files into the appropriate Planning and Consolidation path

Microsoft Visual C++ 2005 Runtime Libraries SP1 Microsoft Access Database Engine 2010 64bit VMWare ESX 3x or ESX 40

(Required only if a landscape deployment strategy using virtualization technologies is planned)

NOTE

MSXML 40 SP2 ADOMDNET 100 and Microsoft Visual C++ 2005 Runtime Libraries SP1 are included with the installation program but not installed automatically

RECOMMENDATION

For SQL Server 2008 only we recommend the installation of Microsoft SQL Server 2008 SP1

(or later) cumulative update package 6 or higher to solve a problem with incorrect periodic

2 Installing Planning and Consolidation Servers

22 Prerequisites

1254 CUSTOMER 2012-06-13

values being returned with calculated accounts For more information see SAP Note number

1429246 which also contains download information

We recommend SQL Server 2008 (or R2) Enterprise Edition or SQL Server 2012 Enterprise

Edition for the OLAP database to support proactive cache and cube partitioning It is

technically possible to use SQL Server 2008 (or R2) Standard Edition or SQL Server 2012

Standard Edition for data integration servers but we do not recommend this

23 Before Starting the Planning and Consolidation Server Installation

You must perform the following tasks before starting your Planning and Consolidation server

installation

Install all the prerequisite software including all of the latest Microsoft hotfixes For more

information see Installing the Prerequisites [page 17]

If you access your application through a firewall verify with your network administrator which

TCP ports to choose during the installation By default port 80 is the setting for standard http

access and port 443 is the setting for https access If you require a service to listen on a different

port you can specify it during the installation program in Advanced Settings See Standard and Advanced

Settings [page 16]

Make sure all required server ports are open and that there is communication between the physical

servers on which you are going to install the server types See Checking for Open Ports [page 41]

Set up the required service accounts that you need to install the Planning and Consolidation server

See Service-Level Accounts [page 15]

The sample environment EnvironmentShell has been updated in this version of Planning and

Consolidation and automatically overwrites the previous version If you have made any

modifications to EnvironmentShell that you want to keep make a copy of it before continuing

with the installation

If you have the URLScan and IIS Lockdown tools installed on your application server you must

reinstall them

Disable your anti-virus software program After the installation when you enable the program

turn off Script Blocking

If a version of Planning and Consolidation on a NetWeaver platform exists uninstall it before you

install Planning and Consolidation 100 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 fsntfsV

All servers in a multiserver environment must be members of the same domain

2 Installing Planning and Consolidation Servers

23 Before Starting the Planning and Consolidation Server Installation

2012-06-13 CUSTOMER 1354

In a multiserver environment the installing ID must be a domain user ID We recommend that

you do not log on to the servers using a local server user ID even if the user ID is a member of the

Administrator group on the server This way you have the proper authority to install software and

to modify the Component Services See Logging On to Servers [page 14]

You must determine the IP addresses or server names for all servers before installing Planning and

Consolidation We recommend that you use static IP addresses

IIS must be enabled

If the application server is not able to copy files to the database server during the installation because

of port access reasons (DMZ WORKGROUP or nontrusted domain authentication failures) do

the following

1 Copy the EnvironmentShell database file ServerEnvironmentShelldb10 from the

Planning and Consolidation installation program to any folder on the SQL server (for example

cEnvironmentShelldb10)

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 cEnvironmentShelldb10)

Install the Anti-Cross Site Scripting Library which provides protection to Web-based applications

against Cross-Site Scripting (XSS) attacks See Installing the Anti-Cross Site Scripting Library [page 24]

24 Logging on to Servers

When installing in a multiserver environment you must use a domain user ID to log on to all

components

A local server user ID is a member of the Administrator group on the server A domain user ID is a

member of the Administrator group of a domain to which the server belongs or a member of the

Administrator group on the local server

Errors may display during the installation program and in the diagnostic program if the installing user

is not assigned to the Administrator group directly but is assigned to a group with Administrator rights

You can ignore these messages

NOTE

If you change the password used to install Planning and Consolidation you must change the

password for the applicable Planning and Consolidation service To do this go to Server Manager

on the application server and select Server Reset Logon Credentials For more information see

the SAP Planning and Consolidation Operations Guide in httpservicesapcominstguidesepm-bpc

100 for the Microsoft Platform SBOP Plan amp Consol 100 MS Administrators Guide

2 Installing Planning and Consolidation Servers

24 Logging on to Servers

1454 CUSTOMER 2012-06-13

25 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

PrerequisitesPlanning and Consolidation 100 has the following Windows services

BPC SendGovernor which manages Microsoft Analysis Service locks to ensure consistent performance

and avoid deadlocks

BPC ServiceManager which manages the System Landscape Directory (SLD) service logging service

and global caches

BPC CTS ServiceManager which listens and handles CTS import requests from the CTS+ transport

management system

Since these services should be able to access to the FileShare server an Admin account is assigned

automatically to the service during the installation of the Planning and Consolidation server program

Even though an Admin account has been assigned to the server correctly the services may fail to start

with the error message

Could not start the BPC SendGovernor service

The reason for this is that the Admin account is not registered as a service

When installing a service to run under a domain user account the account must have the right to

logon as a service on the local machine This logon right strictly applies only to the local computer

and must be granted in the Local Security Policy

To edit the Local Security Policy of the computer you want to define the logon as a service

permission perform the following actions

1 Start the Local Security Settings Microsoft Management Console (MMC) snap-in

2 Expand Local Policies and then click User Rights Assignment

3 In the right-hand pane right-click Log on as a service and then click Security

4 Add the user to the policy and click OK

5 Close the Local Security Settings MMC snap-in

For more details see How to Troubleshoot Service Startup Permissions http

supportmicrosoftcomkb259733

FeaturesDuring the installation enter user IDs and passwords for the following user types

System Admin ID

This ID is read-only and is the same as the installation user ID that is the system displays the ID

on the installation screen but you cannot modify it This ID allows access to code that provides

2 Installing Planning and Consolidation Servers

25 Service-level Accounts

2012-06-13 CUSTOMER 1554

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 readwrite 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

26 Standard and Advanced Settings

The following tables describe the standard and advanced settings for the installation program After

the server is installed you can change these settings using the Server Manager

NOTE

When defining server names the name refers to the NetBIOS name IP address and fully qualified

domain names (FQDN)

Standard Settings

Standard settings are typically used for a single-server environment The following table describes each

setting

Server Option Value Description

SQL Database server name The name of the SQL DB server

OLAP server name The name of the OLAP server

File Share server name The default value is the name of the File Share server that should be the computer name

Local data path Where the data files are saved on the File Share server By default this is CPC_MSData

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

Server Option Value Description

SQL Server Name The name of the SQL DB server Defaults to the local server

2 Installing Planning and Consolidation Servers

26 Standard and Advanced Settings

1654 CUSTOMER 2012-06-13

Server Option Value Description

Instance name The SQL instance name If left blank the default instance is used

Port number The default port number for the SQL Server is 1433

Provider The only available value is SQL

Local path for EnvironmentShell 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 CPC_MSData

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 changesSee the Kerberos authentication settings section in the SAP Library Server Manager Guide on httpservicesapcominstguidesEPM-BPC

100 for the Microsoft Platform

Scheduler Server Name The name of the server used for scheduling usually the application server for example GMPV50072862B If you have multiple application servers select the appropriate one

NOTE

If the primary server stops working you must manually configure your application server database to froward requests to another application server

27 Installing the Prerequisites

271 Installing the Prerequisites ndash Basic Steps

Before installing your Planning and Consolidation server you must install the prerequisite Microsoft

software the operating system IIS SQL server analysis services ADOMDNET and MSXML This

section provides guidance on installing each component For specific versions required see

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 1754

Prerequisites [page 11] and the Product Availability Matrix on the SAP Service Marketplace at http

servicesapcompam Search on Planning and Consolidation

NOTE

To ensure a successful installation you must install the software in the order listed in this

procedure

Check all third-party infrastructure services to ensure that they are functioning and that their

authentication models are documented (stated) since you need to reference this information

during the installation These third-party services include IIS OLAP service SQL services and

Active Directory (AD)

We recommend not installing Microsoft Office on the application server

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

(UMCexe) on the Planning and Consolidation CD in a folder called UMC_100_INSTALLER When

you run the installation package the wizard guides you through the following steps

1 Choose a language for the UMC install wizard to use

2 Check that the prerequisite check status is Succeeded and click Next

3 When you are ready to install the UMC click Next on the welcome screen

4 Click I accept the License Agreement and then Next

5 Choose the destination directory for the UMC installation and click Next

6 Select the languages that you wish to install

7 Select the features that you want to install (POAFHelper dotnet is mandatory for Planning

and Consolidation)

8 On Start Installation click Next to complete the installation

2 Install the required operating system on the single-server computer or on each physical server for

a multiserver configuration See Installing the Operating System [page 19]

3 Install the latest service pack for your operating system To install this service pack go to http

wwwmicrosoftcom

4 From your operating systems media install IIS

5 From your SQL Server media install SQL Server and its required service packs and hot fixes See

Installing SQL Server [page 19]

6 From your SQL Server media install Analysis Services Enterprise Edition and its required service

packs and hot fixes See Installing Analysis Services [page 23]

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

1854 CUSTOMER 2012-06-13

7 On your application server install ADOMDNET The Planning and Consolidation zip file contains

the ADOMDNET installation package in the following locations

For SQL Server 2008 mdash BPC SetupServerSQLSERVER2008_ASADOMD10_x64msi

For SQL Server 2012 mdash BPC SetupServerSQLSERVER2012_ASADOMD11_x64msi

8 On your application server install MSXML 40 Service Pack 2 or later

The MSXML 40 SP2 installation package is contained in the Planning and Consolidation zip file at

the following location BPC SetupServermsxmlmsi

9 On your application server install Microsoft Visual C++ 2005 Runtime Libraries SP1

The Microsoft Visual C++ 2005 SP1 installation package is contained in the Planning and

Consolidation zip file at the following location BPC SetupServervcredist_x64exe

NOTE

The version of vcredist_x64exe in BPC SetupServer has been updated to 8061000 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 httpwwwmicrosoftcomdownloadsen

detailsaspxFamilyID=C06B8369-60DD-4B64-A44B-84B371EDE16Dampltdisplaylanggt=en

272 Installing the Operating System

Before installing the operating system make sure that you configure your server for NTFS

For a list of languages that are supported see the Product Availability Matrix on the SAP Service

Marketplace at httpservicesapcompam Search on Planning and Consolidation

Planning and Consolidation can support all servers with an operating system in any language

NOTE

Currently Planning and Consolidation does not support an operating system in bi-directional

languages such as Hebrew

ProcedureIf you are installing IIS 70 or 75 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

273 Installing the SQL Server

PrerequisitesDuring the installation procedure you have the opportunity to specify the location of the

EnvironmentShell database file Check that it is possible to access EnvironmentShell from the location

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 1954

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 CEnvironmentShelldb10) 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 a 2008 2008 R2 and 2012 SQL Server

SQL Server Considerations

We recommend installing all required components in sequence For example install the Operating

System (Windows Server) then enable IIS and ASPNET and install any Windows Server service

packs

IIS and NET Framework 40 are required on your application server

NOTE

If you encounter a 500 HTTP Error when trying to connect to the Planning and Consolidation

Web Client refer to Microsoft Support articles 2520479 and 2468871 for assistance

To reinforce security we recommend that you install the SQL server and SSAS components to a

nondefault instance of SQL Server

General Installation Steps

1 Launch the SQL Server Setup program entering a product key if necessary and accepting the license

terms

2 Choose Install to install the SQL support files

3 In Feature Selections select instance and shared features as indicated in the SQL Server Component

Options section below then choose Next

4 Review disc space requirements then choose Next

5 In Server Configuration Perform the following actions

1 In the Service Accounts tab enter a Planning and Consolidation sysadmin account for the SQL

Server Database Engine and the SQL Server Analysis services This is required so that the Planning

and Consolidation sysadmin can create and process the Planning and Consolidation database

because the Microsoft SQL server tries to back up or restore database with the privileged

account This account is also required during Backup Environment and Restore Environment in the

Server Manager

For a single-server environment this account is also required if the backup file is located in a

different domain machine because SQL tries to access the folders and files with this account

For the a multiple-server environment SQL server retrieves the information of backup file

from the application server and the account requires the folder access privilege for the

application server

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2054 CUSTOMER 2012-06-13

To ensure that you have the complete access privileges we recommend the Planning and

Consolidation sysadmin for this service account

2 In the Collation tab set the collation settings to SQL_Latin1_General_CP1_CI_AS

Choose Next

6 Set Database Engine Configuration options then choose Next

We recommend you choose Mixed mode (Windows authentication and SQL authentication) This allows you

to use a restrictive SQL ID that works with the drill-through feature If you must restrict SQL

authentication for security reasons you can define a specific parameter in your drill-through

queries If you do not need drill-through support or use it without leveraging SQL authentication

you can install the SQL Server in Windows-only mode

7 Accept the Analysis Services Configuration default options and the remaining default options of the

installation program

8 Choose Install to begin the installation with the options you have set

SQL Server Component 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

Server Component What to Install

SQL Server Database Engine Services

SSAS Server Analysis Services

Application Server The following Shared Features Client Tools Connectivity Integration Services Client Tools SDK

Custom Settings for the SQL Server

As of version 100 Planning and Consolidation supports the following new features for SQL Server 2008

SQL Server 2008 R2 and SQL Server 2012

Process Dimension

It is now possible to process a dimension with multiple selections At processing time the process

dimension module makes changed or added information for each dimension and process for all selected

dimensions and cubes in parallel

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 2154

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

NOTE

Setting 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 tblFactWBltappgt table

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 Microsoftreg SQL Servertrade

20052008 which you can download from wwwmicrosoftcom (search on ldquoTable Partitioningrdquo to find

all relevant articles)

After Installing SQL Server 2008 SQL Server 2008 R2 and SQL Server 2012

From SQL Server Configuration Manager confirm that the SQL Server Browser service is

running The browser service is required for Planning and Consolidation

From SQL Server Configuration Manager do the following

1 Select Protocols for ltInstanceNamegt then double-click TCPIP from the right side of the window

2 When prompted for the TCPIP Properties select IP Addresses You see two IPs that indicate the

localhost and external network interface machine

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2254 CUSTOMER 2012-06-13

3 If you want to use IP1 which indicates Server IP set Enabled to Yes and specify the TCP Port as

desired

4 Delete 0 from TCP Dynamic Ports Set IPAll - TCP Ports as desired (for example 1533)

RECOMMENDATION

We do not recommend using dynamic ports

In an SQL server the default instance has a listener which listens on a fixed port (TCP

port 1433) However for the named instance the port on which the SQL server listens is

random and dynamically selected when the named instance of the SQL server starts This

recommendation prevents any conflict problems

From the SQL Server Configuration Manager specify the client protocol options for the application

server

1 Select Client Protocols from the SQL Native Client Configuration folder

2 From the right side of the window double-click TCPIP The TCPIP 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

NOTE

We 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

274 Installing Analysis Services

ProcedureAfter you install SQL Server and its required service packs and hotfixes you must install SQL Server

Analysis Services and its required service packs and hotfixes

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 2354

NOTE

If you have migrated your Analysis Services repository to the SQL Server back up the database

that contains the repository before installing this release

To install Analysis Services for SQL Server 2008 SQL Server 2008 R2 or SQL Server 2012 follow the steps

and guidelines in httptechnetmicrosoftcomen-uslibraryms143219aspx

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 httpwwwmicrosoftcomdownloads

detailsaspxFamilyID=3be0488d-e7aa-4078-a050- ae39912d2e43ampdisplaylang=en

275 Installing the Anti-Cross Site Scripting Library

Procedure

Before installing Planning and Consolidation servers you must download the Anti-Cross Site Scripting

Library (version 42 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 AntiXSSLibraryDLL from the Microsoft Web

site at httpwwwmicrosoftcomdownloadendetailsaspxid=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 AntiXssLibrarydll

28 Installing on a Single Server

When you install all Planning and Consolidation server components on a single server you should

consider the following issues

Make sure the server has a minimum of 800 MB of hard disk space

Additional environment installations require more free disk space which is a minimum of two

times the uncompressed size of the environment files

When you install Planning and Consolidation on a single-server the system adds the following server

components

SQL Server

SQL Server Analysis Services (SSAS)

Application Server

FileShare server

Procedure

To install Planning and Consolidation on a single server take the following steps

1 Exit all Windows programs

2 Installing Planning and Consolidation Servers

28 Installing on a Single Server

2454 CUSTOMER 2012-06-13

2 Log on to the server with a local server user ID or domain user ID For more information see Logging

on to servers [page 14]

3 Make sure all prerequisite software is installed on the server For more information see Installing

the Prerequisites [page 17]

4 Obtain SAP Planning and Consolidation from the Downloads SAP Installations amp Upgrades area of

SAP Service Marketplace then extract the files and run StartUpexe

5 From the Server Install screen select Install the Planning and Consolidation server

6 From the Welcome screen choose Next

7 From the License Agreement page choose I accept the terms of the license agreement then choose Next

8 From the Installation Method page accept the default Single machine enter a system ID for the system

landscape directory (SLD) and choose Next

NOTE

Entering a system ID of the SLD is only required if you have a SAP Solution Manager license

If you do not have a SAP Solution Manager license you can leave this field empty

9 From the Authentication Method page choose the desired authentication method and choose Next

10 If you have chosen SAP BusinessObjects User Management System in the previous screen on the CMS

Authentication page enter the information required to log on to CMS as an administrator

The following information is required

Field Description

System name CMS system name (server nameport number) for example CMSServer6400

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

11 After entering the CMS administrator authentication details choose Next

12 From the Service type accounts page enter service-level account user IDs and passwords See Service-

Level Accounts [page 15]

13 After defining the IDs and passwords choose Next

14 From the Server Information page (see Standard and Advanced Settings [page 16]) do one of the following

Review the standard settings and choose Next

To set advanced settings choose the Advanced Settings button Enter the desired information

and choose Next

2 Installing Planning and Consolidation Servers

28 Installing on a Single Server

2012-06-13 CUSTOMER 2554

15 Specify the location and name of AntiXssLibrarydll See Installing the Anti-Cross Site Scripting Library [page

24]

Choose Next

16 Select destination folders for Programs and Data The Data files include Webfolders and FileDB

(published reports) and should be installed on a separate drive in a production environment This

recommendation reduces the hard disk IO time and helps to speed up SQL commands

Accept the defaults or make your selections then choose Next

17 Select the default values for the Web client The values are used to determine the default language

and region for the Web client when you connect to it You can change the values in the Planning

and Consolidation Server Manager

18 The installation process takes a few moments When it is complete choose Exit

19 A prompt is displayed to restart your computer Select OK to restart

20 Perform the steps in After Installing Planning and Consolidation Servers [page 27]

29 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 24]) with the following

exceptions

On the Installation Method page do not accept the default instead choose Network Load Balancing

environment With this option there is an additional choice to Include sample environment (required on only

one of the application servers) This is because when you install the application server it connects to the

database server and creates the sample environment (EnvironmentShell) Installing the sample

environment is required on only one application server and you may choose which one

In the Virtual Name field enter the virtual IP address virtual name in the default properties

2 Installing Planning and Consolidation Servers

29 Installing the Server in a Multiserver Configuration

2654 CUSTOMER 2012-06-13

3 After Installing Planning and Consolidation Servers

31 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 28]

2 Configure the Planning and Consolidation NET and application server to ensure that it and its

related services function properly and reliably For more information see Configuring the Planning and

Consolidation NET Application Server [page 29]

3 Optional configuration steps [page 30]

1 To ensure proper functioning of the Management Console create an SQL user and modify

the System DSN and IIS to reflect those user credentials See Enabling Management Console [page

30]

2 Configure custom ODBC logging for the default Web site For details of how to configure

custom logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web

Site [page 31]

3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC

Data Source [page 32]

4 Modify the default access rights to the Management Console By default users in Active

Directory can access the Management Console with whatever rights they have been granted

on the server For information about removing default access and creating a group that can

access the console see Removing Default Access to the Console [page 32]

5 Add authorized users or groups to the group that can access the Management Console We

recommend that you only grant Management Console access to system administrators

Planning and Consolidation users should not have any access For more information see

Management Console Access Control [page 33]

6 Configure the use of client certificates for authentication See Using Client Certificates [page

34]

4 Take the following steps to set up security

If you are defining security and application structure continue with step 5

3 After Installing Planning and Consolidation Servers

31 Post-Installation Steps

2012-06-13 CUSTOMER 2754

If you want to designate someone other than the system administrator to manage security

and application structure log on to EnvironmentShell designate a user as a Primary

Administrator

This user must have Administration ‒ Environment and Security ‒ Define User task rights

so that he or she can add and delete environments and define user security

The Primary Administrator can continue with the next step (5)

5 From the machine on which you administer Planning and Consolidation install the

Administration client See Installing the Administration Client [page 37]

6 Start Planning and Consolidation Administration from the launch page

7 Select Connection Wizard and log on to EnvironmentShell

8 Create a new environment using EnvironmentShell as the source

9 Log on to the newly created environment and set up users teams and task profiles (You must

set up task profiles since there is no access to Planning and Consolidation tasks)

10 Set up your data access profiles and add users (or teams) to one or more data access profiles (You

must complete this step since there is no access to dimensions or members)

NOTE

To allow users to request and query large amounts of data you can edit the metabasexml file located

at CWindowssystem32inetsrv Set the following parameters to the stated values

ASPBUFFERINGLIMIT = 10485760

MAXREQUESTENTITYALLOWED = 10485760

32 Connecting to Solution Manager Diagnostics

NOTE

You only need to perform the steps in this section if you have a SAP Solution Manager licence

The diagnostics functions in SAP Solution Manager allow identification analysis and resolution of

problems This procedure provides the steps required to connect Planning and Consolidation to

Solution Manager Diagnostics

Procedure

1 Install the Diagnostics Agent according to SAP Note 1234387 on all servers where application servers

are installed

NOTE

Installation files for Diagnostics Agent are available on Service Marketplace by navigating to

Support Packages and Patches mdash Entry by Application Group SAP Technology Components SAP

SOLUTION MANAGER SAP SOLUTION MANAGER 70 EHP 1 Entry by Component Agents

for managed systems DIAGNOSTICS AGENT 711

3 After Installing Planning and Consolidation Servers

32 Connecting to Solution Manager Diagnostics

2854 CUSTOMER 2012-06-13

Download the installation file based on the 64-bit Windows Server system landscape

2 To access the DBA Cockpit you must create a user account with sufficient rights on all Windows

Servers where Microsoft SQL Server is installed Do the following

1 Start Computer Management then select Action New User

2 Create a new user

3 Right-click on the user then choose Properties On the Member Of tab select Add

4 Add the group SQLServerltReleasegtSQLAgentUser$ltDomain or hostnamegt$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 httpsservicesapcom~sapidb011000358700000074392009E and follow

the chapters that apply to Planning and Consolidation

33 Configuring the Planning and Consolidation NET Application Servers

Procedure

Modifying machineconfig Files

To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock

occurrences that would cause the application server to ldquosleeprdquo and not process anymore you can

modify the machineconfig file which resides in the WINDOWSMicrosoftNETFramework64

v4030319Config directory

1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to

specify whether to automatically configure settings to achieve optimal performance based on the

machine configuration You can set this attribute to True or False

For more information see httpmsdnmicrosoftcomen-uslibrary7w2sway1aspx

2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the

Planning and Consolidation application) or Machineconfig (for all applications including

Planning and Consolidation) to ensure the validationKey and decryptionKey keys have the same

value on all application servers This way when the authentication cookie is checked the

authentication ticket used on one server can still be valid on another server

For more information and sample Visual Basic code for generating random key values see http

msdnmicrosoftcomen-uslibraryms998288aspx

3 After Installing Planning and Consolidation Servers

33 Configuring the Planning and Consolidation NET Application Servers

2012-06-13 CUSTOMER 2954

paght000007_webfarmdeploymentconsiderations and httpmsdnmicrosoftcomen-us

libraryms998310aspx

34 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 30]

2 Configure custom ODBC logging for the default Web site For details of how to configure custom

logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page

31]

3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC Data

Source [page 32]

4 Modify the default access rights to the Management Console By default users in Active Directory

can access the Management Console with whatever rights they have been granted on the server

For information about removing default access and creating a group that can access the console

see Removing Default Access to the Console [page 32]

5 Add authorized users or groups to the group that can access the Management Console We

recommend that you only grant Management Console access to system administrators Planning

and Consolidation users should not have any access For more information see Management Console

Access Control [page 33]

6 Configure the use of client certificates for authentication See Using Client Certificates [page 34]

341 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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3054 CUSTOMER 2012-06-13

NOTE

Without these updates the Management Console does work but some functionality (specifically

User Activity and Service Status) does not work as expected

Should you need to uninstall Planning and Consolidation we recommend that you reset the

Active Log Format field in IIS to W3C Extended Log File Format

342 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 ApplicationHostconfig set the property customLogPluginClsid to the value FF16065B-

DE82-11CF-BC0A-00AA006111E0 Set the logFormat to Custom You can find this in the ltlogFilegt

node in ApplicationHostconfig as shown here

ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0

logFormat=Custom gt

Use the following AppCmds to configure IIS to use ODBC logging for the default Web site

appcmd site set sitenameDefault Web Site

logFilecustomLogPluginClsidFF16065B-DE82-11CF-BC0A-00AA006111E0

appcmd site set sitenameDefault Web Site logFilelogFormatCustom

Configuring ODBC Logging Parameters in ApplicationHostconfig

Configure ApplicationHostconfig to contain the database table information as set up in the Microsoft

Support article specified in the Prerequisites section Configure these settings in the ltodbcLogginggt

node under ltsystemwebServergt

EXAMPLE

ltlocation path=Default Web Sitegt

ltsystemwebServergt

ltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog

userName=Username password=mypassword gt

ltsystemwebServergt

ltlocationgt

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3154

Use the following AppCmds to configure these attributes for the default Web site

appcmd set config Default Web Site sectionodbcLogging

dataSourceBPC_ManagementDSN commitappHost

appcmd set config Default Web Site sectionodbcLogging tableNameBPCLog

commitappHost

appcmd set config Default Web Site sectionodbcLogging userNameUsername

commitappHost

appcmd set config Default Web Site sectionodbcLogging passwordmypassword

commitappHost

NOTE

You cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must

use the SQL Server ODBC driver For more information see the Microsoft Knowledge Base article

931202 The requirements for using the ODBC logging feature in IIS

343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2

ProcedureThis procedure describes how to set up an ODBC data source for the Management Console in Windows

Server 2008 or Windows Server 2008 R2

Proceed as follows

1 Open ODBC Connection Manager

2 On the System DSN tab page add a new DSN

Choose Add

Choose SQL Server as the driver

Choose Finish

3 In the Name and Description fields enter BPC_ManagementDSN

4 In the Server field enter the name of your SQL Server Choose Next

5 Leave the default settings and choose Next

6 Choose the Change the default database to field and enter AppServer Choose Next

7 Leave default settings and choose Next

8 Choose OK

344 Removing Default Access to the Console

NOTE

If you have chosen SAP BusinessObjects User Management System in the installation screen you

do not need to remove or configure access because the Management Console service always runs

with the System Admin ID account which is a member of the Administrators group

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3254 CUSTOMER 2012-06-13

ProcedureTo remove default access to the Management Console and create a group that does have access to the

console use the procedure described below

NOTE

Create your Management Console administrative group either on the server that hosts the

Management Console or in the Active Directory

1 In the context menu of the servers My Computer icon choose Manage

2 In the Computer Management dialog box choose Local Users and Groups Groups

NOTE

Alternatively you can perform analogous steps in Active Directory

3 In the 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

NOTE

This step is a necessary precursor to the completion of this procedure

10 In the Security dialog box click Copy to ensure that the System group retains its privileges

11 Remove access to the Management Console from all groups that should not have it

12 Choose Authentication in the center pane then disable Windows authentication

ResultUsers who have not been granted access to the Management Console can still open the Management

Console Web page but it contains no data or menu options This does not affect the access that a user

would otherwise have to Planning and Consolidation

345 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 32] Their rights in

Active Directory determine what they can access in the Console

By default any member of the Administrators Active Directory group on the application server or

domain has full access to all of the features of the Console except the Planning and Consolidation

logging area Access to Planning and Consolidation logging is controlled within the Planning and

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3354

Consolidation Administration Client task security The user must be granted View system logs task

privileges For more information see the SAP Library Planning and Consolidation Administrators Guide in

httpservicesapcominstguidesepm-bpc 100 version for the Microsoft platform

Your IT policy determines whether you grant access by group or user You may wish to create several

levels of Console users (read-only users for example) in your environment

To grant or limit access to users or groups you can add or remove the following privileges from the

areas described in this table

Privilege Rights Management Area

Task Manager and Kill Process Administrators group on application server or domain

Performance Monitor Counters Administrators group on application server or domain Power Users group on application server or domain Performance Monitor Users group on application server

Microsoft Analysis Services performance monitoring

Administrators group on application server or domain

Microsoft SQL Server Monitoring (performance counters and statistics)

Administrators group on application server or domain

346 Using Client Certificates

To enable the use of client certificates in Planning and Consolidation you must follow several manual

steps

NOTE

Planning 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 httptechnetmicrosoftcomen-us

librarycc753810aspx

For more information about configuring the client certificate mapping authentication see http

technetmicrosoftcomen-uslibrarycc732996(WS10)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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3454 CUSTOMER 2012-06-13

This option allows you to use a client certificate or username and password (Basic

authentication) to connect to Planning and Consolidation

2 Enable anonymous authentication

1 In the IIS Manager expand the node of the Planning and Consolidation web site

2 Select the ManagementConsole directory (ltWebsitegtManagementConsole) to open the

ManagementConsole home page

3 Double-click Authentication and enable Anonymous Authentication

4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way

as in step 3

5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the same

way as in step 3

3 Change the web configuration settings

1 Open the ltPC_MSgtWebsrvrWebBPCwebconfig file

2 Find the text clientCredentialType=Windows

3 Change value of clientCredentialType to None (clientCredentialType=None)

4 Open the PC_MSWebsrvrWebPOASBCwebconfig file Repeat steps 2 and 3

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3554

This page is left blank for documents that are printed on both sides

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

The installation of the Planning and Consolidation Administration Client allows administrators to

build and maintain Planning and Consolidation environments and models and administer security

All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions

add-in for Microsoft Office for more information see the SAP BusinessObjects EPM solutions add-in for

Microsoft Office help

NOTE

You must update the Administration Client to the same version as the server

If your PC is on a different domain than your server you must set the Internet Explorer

Security Zone value of the Planning and Consolidation client to prompt for user name and

password Otherwise the Planning and Consolidation Start Page does not display

41 Installing the Administration Client

Prerequisites

NOTE

For a definitive list of system requirements see the Product Availability Matrix on SAP Service

Marketplace at httpservicesapcompam Search on Planning and Consolidation

The following list describes the minimum software requirements

Microsoft Internet Explorer 70 or 80

Microsoft Office 2007 or 2010

NET Framework 20 or higher (install any required NET Framework Hotfixes by referring to

httpsupportmicrosoftcomkb)

Pentium IV (1 GHz CPU)

512 MB RAM

100 MB of free hard disk space in the My Documents folder

20 MB of free hard disk space for the installed Administration files

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

41 Installing the Administration Client

2012-06-13 CUSTOMER 3754

NOTE

We recommend that you install all of the latest Microsoft Windows hotfixes prior to installing

the Administration client For information about which hotfixes to install see http

updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us

ProcedureThe following procedure describes how to install the Administration Client on to an administratorrsquos

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 AddRemove Programs in the Windows Control Panel

3 Point your browser to the Planning and Consolidation Web at httpltPC_serverportgtsap

bpcweb

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

42 Installing the EPM Add-in

The Planning and Consolidation installation media does not contain the EPM addin setup program

You must download the most recent version of the full setup (EPM Add-inexe) from the Service

Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPC

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

43 Using the Client Auto Update Program

If Planning and Consolidation version 100 or later is installed you can use the Client Auto Update

program to set up the server so that it determines if an upgrade for a connecting Administration client

is necessary

The following describes the use of the auto update program for the Administration Client and the EPM

add-in

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

42 Installing the EPM Add-in

3854 CUSTOMER 2012-06-13

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 37]

To use the Client Auto Update program for the Administration Client proceed as follows

1 From the Server Manager select Options Client Options

2 Select Admin Update

3 If users without administrator rights on their machines use the auto update enter an administrator

ID and password in the Admin ID and Admin password fields respectively The Admin ID should be a

member of the local administrators group on all the computers running the auto update This

setting is not needed if all users have administrator rights on their machines

4 Select Update

For the EPM Add-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 Optionshellip 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 Market Place (SMP) at httpservicesapcom

All support packages and patches are available from the SMP as a zip file

EPMEXCLCLNTltSPLgtzip is for a support package

EPMEXCLCLNTltSPLgtPltPLgtzip 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 ltSP versiongtmsp

EPM Addin Support Package ltSP versiongtxml

For a patch these files are

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

2012-06-13 CUSTOMER 3954

EPM Addin Patch ltpatch numbergtmsp

EPM Addin Patch ltpatch numbergtxml

2 Unzip the zip file and extract the two files to the application server folder (WebsrvrWebBPC

Installation)

3 From the Server Manager select Options Client Options

The system lists the available packages Select the package that you want to use for the autoupdate

You can set a different update policy for each package listed

EXAMPLE

The following table illustrates some possible situations assuming that you have installed the

first full version (V1)

Available maintenance packages

V2-user updateV3-force updateV4-force updateV5-user update

V5-user update V5-user updateV6-auto updateV7-force update

Minimum Required Version

V4 V4 V7

Notification A prompt tells the user to install maintenance package V4 using the Forced Update behavior

If User Update is enabled the prompt informs the user that maintenance package V5 is available

A prompt tells the user to install maintenance package V7 using the Forced Update behavior

New Version V4 V4 or V5 V7

If you change the update policy for any package click Update to complete the change

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

4054 CUSTOMER 2012-06-13

5 Connection Issues

You may experience connection problems with ports the proxy server or programs and settings that

interact with these components If you have any issues related to connection review the following

recommendations and troubleshooting tips

51 Checking for Open Ports

You must ensure that all required ports are open for inboundoutbound 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 431181836 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

NOTE

You can use the following site to scan for the normal ports It allows you to manually enter a port

number to test

httpwwwmyserverorgportsniffasp

You can change the name of a port

52 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 Explorer Tools Internet Options Connections LAN Settings ) or at the server level

Enabling content filtering on the proxy server or firewall may cause connection problems

If external users are having trouble connecting to the server make sure the proxy server connects

using a fully qualified domain name Fully qualified domain names typically resolve both internal

and external IP addresses

Each secure Planning and Consolidation server name must be identified on the proxy server

Proxy servers may or may not require authentication which could conflict with Planning and

Consolidation authentication Do not use authentication on the proxy server The system

5 Connection Issues

51 Checking for Open Ports

2012-06-13 CUSTOMER 4154

synchronizes the user name and password on the remote server with the local user name and

password

NOTE

For more information about setting up an ISA proxy server contact SAP Support to request a

copy of Setting up ISA Proxy Server White Paper

Internet Explorer Settings 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

5 Connection Issues

52 Proxy Server and Firewall Issues

4254 CUSTOMER 2012-06-13

6 Installing Planning and Consolidation with Two Active Directory Domains

To set up a Planning and Consolidation 10 application server in a hosted environment and use your

own domain users follow this procedure In general you install Planning and Consolidation on the

host domain use the host domain account and assign it to the Planning and Consolidation users

SysAdmin Admin and Users Then you accept one way trust (the host domain trusts your domain)

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

6 Installing Planning and Consolidation with Two Active Directory Domains

2012-06-13 CUSTOMER 4354

This page is left blank for documents that are printed on both sides

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

This section describes best practices and instructions for installing Planning and Consolidation in a

Terminal Services or Citrix Server deployment

71 Terminal Services Home Directories

We recommend using Terminal Server home directories rather than using the userrsquos 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

72 System Requirements

The Citrix server should be one of the following systems

XenApp 5 Enterprise

XenApp 5 Platinum

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 37])

73 Installing Planning and Consolidation

Prerequisites

The server installation files have been downloaded from SAP Service Marketplace and installed

Procedure

The following steps outline how to install the Planning and Consolidation clients in a Terminal Services

(TS) or Citrix Server deployment

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

71 Terminal Services Home Directories

2012-06-13 CUSTOMER 4554

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 userinstall

4 Open a browser and connect to the URL httpltPC_serverportgtsapbpcweb

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 userexecute 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 Iexploreexe http(s)

ltServerNamegt-NetBIOS or FQDNsapbpcweb

To publish Planning and Consolidation Administration CProgram FilesPC_MS

BPCAdminMainexe

74 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 userrsquos desktop) must be moved to the All UsersDesktop folder

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

74 Creating a Shortcut to the Launch Page

4654 CUSTOMER 2012-06-13

8 Installing SSIS Custom Tasks

This section provides background information and instructions for installing SQL Server Integration

Services (SSIS) for SQL Server 2008 and SQL Server 2012

The Planning and Consolidation Data Manager component supports and uses SSIS Since SQL Server

2008 and SQL Server 2012 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

81 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 Filelistxml 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

OSoftSetupexe ‒ 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 or OSoftSSIS2012_Client on the client machine followed by the SQL Server

version If you want to use SQL 2008 Tasks under the SQL 2012 environment you must install

OSoftSSIS2008_Client on the application server For detailed information see SAP Note 1707410

You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package by extracting

OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPC

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 or

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4754

OSoftSSIS2012_Client for creating a COM+ application For more information see Before You Modify

the SSIS Packages [page 50] and Setup of a COM+ Application on the Application Server [page 51]

Bin folder

This folder contains the following components

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCCachedll Planning and Consolidation Cache file

BPCDataFlowPackagedll or BPCDataFlowPackage2012dll

BPCDMdll

BPCDMTaskMaindll COM+ component

BPCFilePreviewdll

BPCGacUtil_20exe System File

BPCGacUtil_40exe System File

BPCImpersonatordll Planning and Consolidation Impersonator

BPCLogicdll

BPCScriptdll

BPCServerZipdll

BPCServiceResdll

BPCTransferMembersdll

BPCWriteBackdll

InteropDTSdll

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

4854 CUSTOMER 2012-06-13

Name Remark

OSoftAdminServerdll

OSoftAuditdll

OSoftComLibServerdll

OSoftCommonResQrydll

OSoftConfigurationdll

OSoftCustomXMLSvrdll

OSoftDatabaseADMINdll

OSoftDatabaseSYSADMINdll

OSoftDatabaseSYSADMINDMdll

OSoftDatabaseUSERdll

OSoftDMDTSXExecutedll or OSoftDMDTSXExecute2012dll

OSoftDMTaskFormdll

OSoftDMTaskMaindll

OSoftDMToolsdll

OSoftFileManagedll

OSoftLoggingdll

OSoftLogWriterdll

OSoftMetaDatadll

OSoftSQEdll

OSoftSystemConfigdll

OutlookSoftconfig Configuration file to connect DB server

XceedCompressiondll XceedZip file

XceedCompressionFormatsdll XceedZip file

XceedFileSystemdll XceedZip file

XceedZipdll XceedZip file

Config folder

This folder has FileListxml 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 FileListxml 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

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4954

OSoftSetupexe

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

NOTE

If you installed the OSoftSSIS2008_Client or OSoftSSIS2012_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

Resources Folder

This folder contains the BPCServicesdll and BPCServiceUIdll files which contain resource text

Only English resources are included for the SSIS custom tasks

82 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

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008 and 2012 respectively

8 Installing SSIS Custom Tasks

82 Before You Modify the SSIS Packages

5054 CUSTOMER 2012-06-13

Name Remark

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012 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

lthellipgtOSoftSSIS2008_Clientbin or lthellipgtOSoftSSIS2012_Clientbin

On the Planning and Consolidation application server

ltdrivegtWebsrvrbin

2 Paste these files into the folder 100DTSTasks for SQL Server 2008 or into 110DTSTasks for

SQL Server 2012 For example if you install your SQL 2008 server or R2 on CProgram Files

Microsoft SQL Server paste all files into the CProgram Files (x86)Microsoft SQL Server

100DTSTasks folder

In Integration Services set the property Run64BitRunTime to True

83 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 or OSoftSSIS2012_Client on the

application server

8 Installing SSIS Custom Tasks

83 Setup of a COM+ Application on the Application Server

2012-06-13 CUSTOMER 5154

Typographic Conventions

Example Description

ltgt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example Enter your ltUser Namegt

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 httpwwwsapcom

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

5254 CUSTOMER 2012-06-13

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

  • SAP BusinessObjects Planning and Consolidation 100
    • Table of Contents
    • 1 Introduction
      • 11 SAP Notes for the Installation
      • 12 Naming Conventions
        • 2 Installing Planning and Consolidation Servers
          • 21 Basic Steps
          • 22 Prerequisites
          • 23 Before Starting the Planning and Consolidation Server Installation
          • 24 Logging on to Servers
          • 25 Service-level Accounts
          • 26 Standard and Advanced Settings
          • 27 Installing the Prerequisites
            • 271 Installing the Prerequisites ndash Basic Steps
            • 272 Installing the Operating System
            • 273 Installing the SQL Server
            • 274 Installing Analysis Services
            • 275 Installing the Anti-Cross Site Scripting Library
              • 28 Installing on a Single Server
              • 29 Installing the Server in a Multiserver Configuration
                • 3 After Installing Planning and Consolidation Servers
                  • 31 Post-Installation Steps
                  • 32 Connecting to Solution Manager Diagnostics
                  • 33 Configuring the Planning and Consolidation NET Application Servers
                  • 34 Post-Installation Optional Configuration Steps
                    • 341 Enabling the Management Console
                    • 342 Setting Up ODBC Logging in IIS for the Default Web Site
                    • 343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2
                    • 344 Removing Default Access to the Console
                    • 345 Management Console Access Control
                    • 346 Using Client Certificates
                        • 4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office
                          • 41 Installing the Administration Client
                          • 42 Installing the EPM Add-in
                          • 43 Using the Client Auto Update Program
                            • 5 Connection Issues
                              • 51 Checking for Open Ports
                              • 52 Proxy Server and Firewall Issues
                                • 6 Installing Planning and Consolidation with Two Active Directory Domains
                                • 7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
                                  • 71 Terminal Services Home Directories
                                  • 72 System Requirements
                                  • 73 Installing Planning and Consolidation
                                  • 74 Creating a Shortcut to the Launch Page
                                    • 8 Installing SSIS Custom Tasks
                                      • 81 Composition of SSIS Custom Task Installation
                                      • 82 Before You Modify the SSIS Packages
                                      • 83 Setup of a COM+ Application on the Application Server
                                          • Copyright and trademarks
Page 10: Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

This page is left blank for documents that are printed on both sides

2 Installing Planning and Consolidation Servers

This section includes the basic steps for installing a Planning and Consolidation server the prerequisites

and what to do before during and after the server installation

21 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 at httpservicesapcominstguidesepm-bpc 100 version for the Microsoft platform

2 Perform the tasks in the Before Starting the Planning and Consolidation Server Installation [page 13] section

including installing all prerequisites

3 From the application server install the Planning and Consolidation server See Installing Planning and

Consolidation on a Single Server [page 24]

NOTE

You must install both Planning and Consolidation 100 as well as the most recent Planning

and Consolidation 100 Support Package available from the SAP Service Marketplace at

httpservicesapcomswdc Software Downloads Support Packages and Patches A - Z Index

B SAP BPC FOR MICROSOFT SBOP PC 100 FOR MICROSOFT Comprised Software Component

Versions SAP CPM BPC 100 M Windows Server on x64 64bit

4 If you have multiple machines see Installing the Server in a Multiserver Configuration [page 26]

5 Perform the steps in the section After Installing Planning and Consolidation Servers [page 27]

22 Prerequisites

The following table describes the software you need to install before installing the Planning and

Consolidation server and the minimum versions required

NOTE

A list of the supported operating systems and database systems is also available in the Product

Availability Matrix on SAP Service Marketplace at httpservicesapcompam Search on

Planning and Consolidation

2 Installing Planning and Consolidation Servers

21 Basic Steps

2012-06-13 CUSTOMER 1154

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 or

Data Center with or without Hyper-V

NOTE

The operating system must be configured with NTFS

Relational Database Microsoft SQL Server 2008 Enterprise Edition Microsoft SQL Server 2008 R2 (Gemini) Enterprise Edition Microsoft SQL Server 2012 Enterprise Edition

OLAP Database Microsoft SQL Server 2008 Enterprise Edition ‒ Analysis Server Microsoft SQL Server 2008 R2 Enterprise Edition ‒ Analysis Server Microsoft SQL Server 2012 Enterprise Edition ‒ Analysis Server

Data Integration Microsoft SQL Server 2008 Enterprise Edition ‒ SQL Service Integration Services

Microsoft SQL Server 2008 R2 Enterprise Edition ‒ SQL Service Integration Services

Microsoft SQL Server 2012 Enterprise Edition ‒ SQL Service Integration Services

Other Requirements MSXML 40 SP2 or later ADOMDNET

ADOMDNET 100 when running SQL Server 2008 or 2008 R2 ADOMDNET 110 when running SQL Server 2012

SQL Server software components NET 40 IIS 75 or IIS 70

(Included in your Operating System IIS 75 is required for Windows 2008 R2 editions)

Anti-Cross Site Scripting Library 42This component must be downloaded before installing the server The server installation program asks for the path of each file and copies the files into the appropriate Planning and Consolidation path

Microsoft Visual C++ 2005 Runtime Libraries SP1 Microsoft Access Database Engine 2010 64bit VMWare ESX 3x or ESX 40

(Required only if a landscape deployment strategy using virtualization technologies is planned)

NOTE

MSXML 40 SP2 ADOMDNET 100 and Microsoft Visual C++ 2005 Runtime Libraries SP1 are included with the installation program but not installed automatically

RECOMMENDATION

For SQL Server 2008 only we recommend the installation of Microsoft SQL Server 2008 SP1

(or later) cumulative update package 6 or higher to solve a problem with incorrect periodic

2 Installing Planning and Consolidation Servers

22 Prerequisites

1254 CUSTOMER 2012-06-13

values being returned with calculated accounts For more information see SAP Note number

1429246 which also contains download information

We recommend SQL Server 2008 (or R2) Enterprise Edition or SQL Server 2012 Enterprise

Edition for the OLAP database to support proactive cache and cube partitioning It is

technically possible to use SQL Server 2008 (or R2) Standard Edition or SQL Server 2012

Standard Edition for data integration servers but we do not recommend this

23 Before Starting the Planning and Consolidation Server Installation

You must perform the following tasks before starting your Planning and Consolidation server

installation

Install all the prerequisite software including all of the latest Microsoft hotfixes For more

information see Installing the Prerequisites [page 17]

If you access your application through a firewall verify with your network administrator which

TCP ports to choose during the installation By default port 80 is the setting for standard http

access and port 443 is the setting for https access If you require a service to listen on a different

port you can specify it during the installation program in Advanced Settings See Standard and Advanced

Settings [page 16]

Make sure all required server ports are open and that there is communication between the physical

servers on which you are going to install the server types See Checking for Open Ports [page 41]

Set up the required service accounts that you need to install the Planning and Consolidation server

See Service-Level Accounts [page 15]

The sample environment EnvironmentShell has been updated in this version of Planning and

Consolidation and automatically overwrites the previous version If you have made any

modifications to EnvironmentShell that you want to keep make a copy of it before continuing

with the installation

If you have the URLScan and IIS Lockdown tools installed on your application server you must

reinstall them

Disable your anti-virus software program After the installation when you enable the program

turn off Script Blocking

If a version of Planning and Consolidation on a NetWeaver platform exists uninstall it before you

install Planning and Consolidation 100 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 fsntfsV

All servers in a multiserver environment must be members of the same domain

2 Installing Planning and Consolidation Servers

23 Before Starting the Planning and Consolidation Server Installation

2012-06-13 CUSTOMER 1354

In a multiserver environment the installing ID must be a domain user ID We recommend that

you do not log on to the servers using a local server user ID even if the user ID is a member of the

Administrator group on the server This way you have the proper authority to install software and

to modify the Component Services See Logging On to Servers [page 14]

You must determine the IP addresses or server names for all servers before installing Planning and

Consolidation We recommend that you use static IP addresses

IIS must be enabled

If the application server is not able to copy files to the database server during the installation because

of port access reasons (DMZ WORKGROUP or nontrusted domain authentication failures) do

the following

1 Copy the EnvironmentShell database file ServerEnvironmentShelldb10 from the

Planning and Consolidation installation program to any folder on the SQL server (for example

cEnvironmentShelldb10)

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 cEnvironmentShelldb10)

Install the Anti-Cross Site Scripting Library which provides protection to Web-based applications

against Cross-Site Scripting (XSS) attacks See Installing the Anti-Cross Site Scripting Library [page 24]

24 Logging on to Servers

When installing in a multiserver environment you must use a domain user ID to log on to all

components

A local server user ID is a member of the Administrator group on the server A domain user ID is a

member of the Administrator group of a domain to which the server belongs or a member of the

Administrator group on the local server

Errors may display during the installation program and in the diagnostic program if the installing user

is not assigned to the Administrator group directly but is assigned to a group with Administrator rights

You can ignore these messages

NOTE

If you change the password used to install Planning and Consolidation you must change the

password for the applicable Planning and Consolidation service To do this go to Server Manager

on the application server and select Server Reset Logon Credentials For more information see

the SAP Planning and Consolidation Operations Guide in httpservicesapcominstguidesepm-bpc

100 for the Microsoft Platform SBOP Plan amp Consol 100 MS Administrators Guide

2 Installing Planning and Consolidation Servers

24 Logging on to Servers

1454 CUSTOMER 2012-06-13

25 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

PrerequisitesPlanning and Consolidation 100 has the following Windows services

BPC SendGovernor which manages Microsoft Analysis Service locks to ensure consistent performance

and avoid deadlocks

BPC ServiceManager which manages the System Landscape Directory (SLD) service logging service

and global caches

BPC CTS ServiceManager which listens and handles CTS import requests from the CTS+ transport

management system

Since these services should be able to access to the FileShare server an Admin account is assigned

automatically to the service during the installation of the Planning and Consolidation server program

Even though an Admin account has been assigned to the server correctly the services may fail to start

with the error message

Could not start the BPC SendGovernor service

The reason for this is that the Admin account is not registered as a service

When installing a service to run under a domain user account the account must have the right to

logon as a service on the local machine This logon right strictly applies only to the local computer

and must be granted in the Local Security Policy

To edit the Local Security Policy of the computer you want to define the logon as a service

permission perform the following actions

1 Start the Local Security Settings Microsoft Management Console (MMC) snap-in

2 Expand Local Policies and then click User Rights Assignment

3 In the right-hand pane right-click Log on as a service and then click Security

4 Add the user to the policy and click OK

5 Close the Local Security Settings MMC snap-in

For more details see How to Troubleshoot Service Startup Permissions http

supportmicrosoftcomkb259733

FeaturesDuring the installation enter user IDs and passwords for the following user types

System Admin ID

This ID is read-only and is the same as the installation user ID that is the system displays the ID

on the installation screen but you cannot modify it This ID allows access to code that provides

2 Installing Planning and Consolidation Servers

25 Service-level Accounts

2012-06-13 CUSTOMER 1554

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 readwrite 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

26 Standard and Advanced Settings

The following tables describe the standard and advanced settings for the installation program After

the server is installed you can change these settings using the Server Manager

NOTE

When defining server names the name refers to the NetBIOS name IP address and fully qualified

domain names (FQDN)

Standard Settings

Standard settings are typically used for a single-server environment The following table describes each

setting

Server Option Value Description

SQL Database server name The name of the SQL DB server

OLAP server name The name of the OLAP server

File Share server name The default value is the name of the File Share server that should be the computer name

Local data path Where the data files are saved on the File Share server By default this is CPC_MSData

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

Server Option Value Description

SQL Server Name The name of the SQL DB server Defaults to the local server

2 Installing Planning and Consolidation Servers

26 Standard and Advanced Settings

1654 CUSTOMER 2012-06-13

Server Option Value Description

Instance name The SQL instance name If left blank the default instance is used

Port number The default port number for the SQL Server is 1433

Provider The only available value is SQL

Local path for EnvironmentShell 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 CPC_MSData

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 changesSee the Kerberos authentication settings section in the SAP Library Server Manager Guide on httpservicesapcominstguidesEPM-BPC

100 for the Microsoft Platform

Scheduler Server Name The name of the server used for scheduling usually the application server for example GMPV50072862B If you have multiple application servers select the appropriate one

NOTE

If the primary server stops working you must manually configure your application server database to froward requests to another application server

27 Installing the Prerequisites

271 Installing the Prerequisites ndash Basic Steps

Before installing your Planning and Consolidation server you must install the prerequisite Microsoft

software the operating system IIS SQL server analysis services ADOMDNET and MSXML This

section provides guidance on installing each component For specific versions required see

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 1754

Prerequisites [page 11] and the Product Availability Matrix on the SAP Service Marketplace at http

servicesapcompam Search on Planning and Consolidation

NOTE

To ensure a successful installation you must install the software in the order listed in this

procedure

Check all third-party infrastructure services to ensure that they are functioning and that their

authentication models are documented (stated) since you need to reference this information

during the installation These third-party services include IIS OLAP service SQL services and

Active Directory (AD)

We recommend not installing Microsoft Office on the application server

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

(UMCexe) on the Planning and Consolidation CD in a folder called UMC_100_INSTALLER When

you run the installation package the wizard guides you through the following steps

1 Choose a language for the UMC install wizard to use

2 Check that the prerequisite check status is Succeeded and click Next

3 When you are ready to install the UMC click Next on the welcome screen

4 Click I accept the License Agreement and then Next

5 Choose the destination directory for the UMC installation and click Next

6 Select the languages that you wish to install

7 Select the features that you want to install (POAFHelper dotnet is mandatory for Planning

and Consolidation)

8 On Start Installation click Next to complete the installation

2 Install the required operating system on the single-server computer or on each physical server for

a multiserver configuration See Installing the Operating System [page 19]

3 Install the latest service pack for your operating system To install this service pack go to http

wwwmicrosoftcom

4 From your operating systems media install IIS

5 From your SQL Server media install SQL Server and its required service packs and hot fixes See

Installing SQL Server [page 19]

6 From your SQL Server media install Analysis Services Enterprise Edition and its required service

packs and hot fixes See Installing Analysis Services [page 23]

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

1854 CUSTOMER 2012-06-13

7 On your application server install ADOMDNET The Planning and Consolidation zip file contains

the ADOMDNET installation package in the following locations

For SQL Server 2008 mdash BPC SetupServerSQLSERVER2008_ASADOMD10_x64msi

For SQL Server 2012 mdash BPC SetupServerSQLSERVER2012_ASADOMD11_x64msi

8 On your application server install MSXML 40 Service Pack 2 or later

The MSXML 40 SP2 installation package is contained in the Planning and Consolidation zip file at

the following location BPC SetupServermsxmlmsi

9 On your application server install Microsoft Visual C++ 2005 Runtime Libraries SP1

The Microsoft Visual C++ 2005 SP1 installation package is contained in the Planning and

Consolidation zip file at the following location BPC SetupServervcredist_x64exe

NOTE

The version of vcredist_x64exe in BPC SetupServer has been updated to 8061000 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 httpwwwmicrosoftcomdownloadsen

detailsaspxFamilyID=C06B8369-60DD-4B64-A44B-84B371EDE16Dampltdisplaylanggt=en

272 Installing the Operating System

Before installing the operating system make sure that you configure your server for NTFS

For a list of languages that are supported see the Product Availability Matrix on the SAP Service

Marketplace at httpservicesapcompam Search on Planning and Consolidation

Planning and Consolidation can support all servers with an operating system in any language

NOTE

Currently Planning and Consolidation does not support an operating system in bi-directional

languages such as Hebrew

ProcedureIf you are installing IIS 70 or 75 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

273 Installing the SQL Server

PrerequisitesDuring the installation procedure you have the opportunity to specify the location of the

EnvironmentShell database file Check that it is possible to access EnvironmentShell from the location

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 1954

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 CEnvironmentShelldb10) 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 a 2008 2008 R2 and 2012 SQL Server

SQL Server Considerations

We recommend installing all required components in sequence For example install the Operating

System (Windows Server) then enable IIS and ASPNET and install any Windows Server service

packs

IIS and NET Framework 40 are required on your application server

NOTE

If you encounter a 500 HTTP Error when trying to connect to the Planning and Consolidation

Web Client refer to Microsoft Support articles 2520479 and 2468871 for assistance

To reinforce security we recommend that you install the SQL server and SSAS components to a

nondefault instance of SQL Server

General Installation Steps

1 Launch the SQL Server Setup program entering a product key if necessary and accepting the license

terms

2 Choose Install to install the SQL support files

3 In Feature Selections select instance and shared features as indicated in the SQL Server Component

Options section below then choose Next

4 Review disc space requirements then choose Next

5 In Server Configuration Perform the following actions

1 In the Service Accounts tab enter a Planning and Consolidation sysadmin account for the SQL

Server Database Engine and the SQL Server Analysis services This is required so that the Planning

and Consolidation sysadmin can create and process the Planning and Consolidation database

because the Microsoft SQL server tries to back up or restore database with the privileged

account This account is also required during Backup Environment and Restore Environment in the

Server Manager

For a single-server environment this account is also required if the backup file is located in a

different domain machine because SQL tries to access the folders and files with this account

For the a multiple-server environment SQL server retrieves the information of backup file

from the application server and the account requires the folder access privilege for the

application server

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2054 CUSTOMER 2012-06-13

To ensure that you have the complete access privileges we recommend the Planning and

Consolidation sysadmin for this service account

2 In the Collation tab set the collation settings to SQL_Latin1_General_CP1_CI_AS

Choose Next

6 Set Database Engine Configuration options then choose Next

We recommend you choose Mixed mode (Windows authentication and SQL authentication) This allows you

to use a restrictive SQL ID that works with the drill-through feature If you must restrict SQL

authentication for security reasons you can define a specific parameter in your drill-through

queries If you do not need drill-through support or use it without leveraging SQL authentication

you can install the SQL Server in Windows-only mode

7 Accept the Analysis Services Configuration default options and the remaining default options of the

installation program

8 Choose Install to begin the installation with the options you have set

SQL Server Component 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

Server Component What to Install

SQL Server Database Engine Services

SSAS Server Analysis Services

Application Server The following Shared Features Client Tools Connectivity Integration Services Client Tools SDK

Custom Settings for the SQL Server

As of version 100 Planning and Consolidation supports the following new features for SQL Server 2008

SQL Server 2008 R2 and SQL Server 2012

Process Dimension

It is now possible to process a dimension with multiple selections At processing time the process

dimension module makes changed or added information for each dimension and process for all selected

dimensions and cubes in parallel

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 2154

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

NOTE

Setting 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 tblFactWBltappgt table

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 Microsoftreg SQL Servertrade

20052008 which you can download from wwwmicrosoftcom (search on ldquoTable Partitioningrdquo to find

all relevant articles)

After Installing SQL Server 2008 SQL Server 2008 R2 and SQL Server 2012

From SQL Server Configuration Manager confirm that the SQL Server Browser service is

running The browser service is required for Planning and Consolidation

From SQL Server Configuration Manager do the following

1 Select Protocols for ltInstanceNamegt then double-click TCPIP from the right side of the window

2 When prompted for the TCPIP Properties select IP Addresses You see two IPs that indicate the

localhost and external network interface machine

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2254 CUSTOMER 2012-06-13

3 If you want to use IP1 which indicates Server IP set Enabled to Yes and specify the TCP Port as

desired

4 Delete 0 from TCP Dynamic Ports Set IPAll - TCP Ports as desired (for example 1533)

RECOMMENDATION

We do not recommend using dynamic ports

In an SQL server the default instance has a listener which listens on a fixed port (TCP

port 1433) However for the named instance the port on which the SQL server listens is

random and dynamically selected when the named instance of the SQL server starts This

recommendation prevents any conflict problems

From the SQL Server Configuration Manager specify the client protocol options for the application

server

1 Select Client Protocols from the SQL Native Client Configuration folder

2 From the right side of the window double-click TCPIP The TCPIP 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

NOTE

We 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

274 Installing Analysis Services

ProcedureAfter you install SQL Server and its required service packs and hotfixes you must install SQL Server

Analysis Services and its required service packs and hotfixes

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 2354

NOTE

If you have migrated your Analysis Services repository to the SQL Server back up the database

that contains the repository before installing this release

To install Analysis Services for SQL Server 2008 SQL Server 2008 R2 or SQL Server 2012 follow the steps

and guidelines in httptechnetmicrosoftcomen-uslibraryms143219aspx

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 httpwwwmicrosoftcomdownloads

detailsaspxFamilyID=3be0488d-e7aa-4078-a050- ae39912d2e43ampdisplaylang=en

275 Installing the Anti-Cross Site Scripting Library

Procedure

Before installing Planning and Consolidation servers you must download the Anti-Cross Site Scripting

Library (version 42 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 AntiXSSLibraryDLL from the Microsoft Web

site at httpwwwmicrosoftcomdownloadendetailsaspxid=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 AntiXssLibrarydll

28 Installing on a Single Server

When you install all Planning and Consolidation server components on a single server you should

consider the following issues

Make sure the server has a minimum of 800 MB of hard disk space

Additional environment installations require more free disk space which is a minimum of two

times the uncompressed size of the environment files

When you install Planning and Consolidation on a single-server the system adds the following server

components

SQL Server

SQL Server Analysis Services (SSAS)

Application Server

FileShare server

Procedure

To install Planning and Consolidation on a single server take the following steps

1 Exit all Windows programs

2 Installing Planning and Consolidation Servers

28 Installing on a Single Server

2454 CUSTOMER 2012-06-13

2 Log on to the server with a local server user ID or domain user ID For more information see Logging

on to servers [page 14]

3 Make sure all prerequisite software is installed on the server For more information see Installing

the Prerequisites [page 17]

4 Obtain SAP Planning and Consolidation from the Downloads SAP Installations amp Upgrades area of

SAP Service Marketplace then extract the files and run StartUpexe

5 From the Server Install screen select Install the Planning and Consolidation server

6 From the Welcome screen choose Next

7 From the License Agreement page choose I accept the terms of the license agreement then choose Next

8 From the Installation Method page accept the default Single machine enter a system ID for the system

landscape directory (SLD) and choose Next

NOTE

Entering a system ID of the SLD is only required if you have a SAP Solution Manager license

If you do not have a SAP Solution Manager license you can leave this field empty

9 From the Authentication Method page choose the desired authentication method and choose Next

10 If you have chosen SAP BusinessObjects User Management System in the previous screen on the CMS

Authentication page enter the information required to log on to CMS as an administrator

The following information is required

Field Description

System name CMS system name (server nameport number) for example CMSServer6400

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

11 After entering the CMS administrator authentication details choose Next

12 From the Service type accounts page enter service-level account user IDs and passwords See Service-

Level Accounts [page 15]

13 After defining the IDs and passwords choose Next

14 From the Server Information page (see Standard and Advanced Settings [page 16]) do one of the following

Review the standard settings and choose Next

To set advanced settings choose the Advanced Settings button Enter the desired information

and choose Next

2 Installing Planning and Consolidation Servers

28 Installing on a Single Server

2012-06-13 CUSTOMER 2554

15 Specify the location and name of AntiXssLibrarydll See Installing the Anti-Cross Site Scripting Library [page

24]

Choose Next

16 Select destination folders for Programs and Data The Data files include Webfolders and FileDB

(published reports) and should be installed on a separate drive in a production environment This

recommendation reduces the hard disk IO time and helps to speed up SQL commands

Accept the defaults or make your selections then choose Next

17 Select the default values for the Web client The values are used to determine the default language

and region for the Web client when you connect to it You can change the values in the Planning

and Consolidation Server Manager

18 The installation process takes a few moments When it is complete choose Exit

19 A prompt is displayed to restart your computer Select OK to restart

20 Perform the steps in After Installing Planning and Consolidation Servers [page 27]

29 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 24]) with the following

exceptions

On the Installation Method page do not accept the default instead choose Network Load Balancing

environment With this option there is an additional choice to Include sample environment (required on only

one of the application servers) This is because when you install the application server it connects to the

database server and creates the sample environment (EnvironmentShell) Installing the sample

environment is required on only one application server and you may choose which one

In the Virtual Name field enter the virtual IP address virtual name in the default properties

2 Installing Planning and Consolidation Servers

29 Installing the Server in a Multiserver Configuration

2654 CUSTOMER 2012-06-13

3 After Installing Planning and Consolidation Servers

31 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 28]

2 Configure the Planning and Consolidation NET and application server to ensure that it and its

related services function properly and reliably For more information see Configuring the Planning and

Consolidation NET Application Server [page 29]

3 Optional configuration steps [page 30]

1 To ensure proper functioning of the Management Console create an SQL user and modify

the System DSN and IIS to reflect those user credentials See Enabling Management Console [page

30]

2 Configure custom ODBC logging for the default Web site For details of how to configure

custom logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web

Site [page 31]

3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC

Data Source [page 32]

4 Modify the default access rights to the Management Console By default users in Active

Directory can access the Management Console with whatever rights they have been granted

on the server For information about removing default access and creating a group that can

access the console see Removing Default Access to the Console [page 32]

5 Add authorized users or groups to the group that can access the Management Console We

recommend that you only grant Management Console access to system administrators

Planning and Consolidation users should not have any access For more information see

Management Console Access Control [page 33]

6 Configure the use of client certificates for authentication See Using Client Certificates [page

34]

4 Take the following steps to set up security

If you are defining security and application structure continue with step 5

3 After Installing Planning and Consolidation Servers

31 Post-Installation Steps

2012-06-13 CUSTOMER 2754

If you want to designate someone other than the system administrator to manage security

and application structure log on to EnvironmentShell designate a user as a Primary

Administrator

This user must have Administration ‒ Environment and Security ‒ Define User task rights

so that he or she can add and delete environments and define user security

The Primary Administrator can continue with the next step (5)

5 From the machine on which you administer Planning and Consolidation install the

Administration client See Installing the Administration Client [page 37]

6 Start Planning and Consolidation Administration from the launch page

7 Select Connection Wizard and log on to EnvironmentShell

8 Create a new environment using EnvironmentShell as the source

9 Log on to the newly created environment and set up users teams and task profiles (You must

set up task profiles since there is no access to Planning and Consolidation tasks)

10 Set up your data access profiles and add users (or teams) to one or more data access profiles (You

must complete this step since there is no access to dimensions or members)

NOTE

To allow users to request and query large amounts of data you can edit the metabasexml file located

at CWindowssystem32inetsrv Set the following parameters to the stated values

ASPBUFFERINGLIMIT = 10485760

MAXREQUESTENTITYALLOWED = 10485760

32 Connecting to Solution Manager Diagnostics

NOTE

You only need to perform the steps in this section if you have a SAP Solution Manager licence

The diagnostics functions in SAP Solution Manager allow identification analysis and resolution of

problems This procedure provides the steps required to connect Planning and Consolidation to

Solution Manager Diagnostics

Procedure

1 Install the Diagnostics Agent according to SAP Note 1234387 on all servers where application servers

are installed

NOTE

Installation files for Diagnostics Agent are available on Service Marketplace by navigating to

Support Packages and Patches mdash Entry by Application Group SAP Technology Components SAP

SOLUTION MANAGER SAP SOLUTION MANAGER 70 EHP 1 Entry by Component Agents

for managed systems DIAGNOSTICS AGENT 711

3 After Installing Planning and Consolidation Servers

32 Connecting to Solution Manager Diagnostics

2854 CUSTOMER 2012-06-13

Download the installation file based on the 64-bit Windows Server system landscape

2 To access the DBA Cockpit you must create a user account with sufficient rights on all Windows

Servers where Microsoft SQL Server is installed Do the following

1 Start Computer Management then select Action New User

2 Create a new user

3 Right-click on the user then choose Properties On the Member Of tab select Add

4 Add the group SQLServerltReleasegtSQLAgentUser$ltDomain or hostnamegt$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 httpsservicesapcom~sapidb011000358700000074392009E and follow

the chapters that apply to Planning and Consolidation

33 Configuring the Planning and Consolidation NET Application Servers

Procedure

Modifying machineconfig Files

To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock

occurrences that would cause the application server to ldquosleeprdquo and not process anymore you can

modify the machineconfig file which resides in the WINDOWSMicrosoftNETFramework64

v4030319Config directory

1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to

specify whether to automatically configure settings to achieve optimal performance based on the

machine configuration You can set this attribute to True or False

For more information see httpmsdnmicrosoftcomen-uslibrary7w2sway1aspx

2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the

Planning and Consolidation application) or Machineconfig (for all applications including

Planning and Consolidation) to ensure the validationKey and decryptionKey keys have the same

value on all application servers This way when the authentication cookie is checked the

authentication ticket used on one server can still be valid on another server

For more information and sample Visual Basic code for generating random key values see http

msdnmicrosoftcomen-uslibraryms998288aspx

3 After Installing Planning and Consolidation Servers

33 Configuring the Planning and Consolidation NET Application Servers

2012-06-13 CUSTOMER 2954

paght000007_webfarmdeploymentconsiderations and httpmsdnmicrosoftcomen-us

libraryms998310aspx

34 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 30]

2 Configure custom ODBC logging for the default Web site For details of how to configure custom

logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page

31]

3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC Data

Source [page 32]

4 Modify the default access rights to the Management Console By default users in Active Directory

can access the Management Console with whatever rights they have been granted on the server

For information about removing default access and creating a group that can access the console

see Removing Default Access to the Console [page 32]

5 Add authorized users or groups to the group that can access the Management Console We

recommend that you only grant Management Console access to system administrators Planning

and Consolidation users should not have any access For more information see Management Console

Access Control [page 33]

6 Configure the use of client certificates for authentication See Using Client Certificates [page 34]

341 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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3054 CUSTOMER 2012-06-13

NOTE

Without these updates the Management Console does work but some functionality (specifically

User Activity and Service Status) does not work as expected

Should you need to uninstall Planning and Consolidation we recommend that you reset the

Active Log Format field in IIS to W3C Extended Log File Format

342 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 ApplicationHostconfig set the property customLogPluginClsid to the value FF16065B-

DE82-11CF-BC0A-00AA006111E0 Set the logFormat to Custom You can find this in the ltlogFilegt

node in ApplicationHostconfig as shown here

ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0

logFormat=Custom gt

Use the following AppCmds to configure IIS to use ODBC logging for the default Web site

appcmd site set sitenameDefault Web Site

logFilecustomLogPluginClsidFF16065B-DE82-11CF-BC0A-00AA006111E0

appcmd site set sitenameDefault Web Site logFilelogFormatCustom

Configuring ODBC Logging Parameters in ApplicationHostconfig

Configure ApplicationHostconfig to contain the database table information as set up in the Microsoft

Support article specified in the Prerequisites section Configure these settings in the ltodbcLogginggt

node under ltsystemwebServergt

EXAMPLE

ltlocation path=Default Web Sitegt

ltsystemwebServergt

ltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog

userName=Username password=mypassword gt

ltsystemwebServergt

ltlocationgt

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3154

Use the following AppCmds to configure these attributes for the default Web site

appcmd set config Default Web Site sectionodbcLogging

dataSourceBPC_ManagementDSN commitappHost

appcmd set config Default Web Site sectionodbcLogging tableNameBPCLog

commitappHost

appcmd set config Default Web Site sectionodbcLogging userNameUsername

commitappHost

appcmd set config Default Web Site sectionodbcLogging passwordmypassword

commitappHost

NOTE

You cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must

use the SQL Server ODBC driver For more information see the Microsoft Knowledge Base article

931202 The requirements for using the ODBC logging feature in IIS

343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2

ProcedureThis procedure describes how to set up an ODBC data source for the Management Console in Windows

Server 2008 or Windows Server 2008 R2

Proceed as follows

1 Open ODBC Connection Manager

2 On the System DSN tab page add a new DSN

Choose Add

Choose SQL Server as the driver

Choose Finish

3 In the Name and Description fields enter BPC_ManagementDSN

4 In the Server field enter the name of your SQL Server Choose Next

5 Leave the default settings and choose Next

6 Choose the Change the default database to field and enter AppServer Choose Next

7 Leave default settings and choose Next

8 Choose OK

344 Removing Default Access to the Console

NOTE

If you have chosen SAP BusinessObjects User Management System in the installation screen you

do not need to remove or configure access because the Management Console service always runs

with the System Admin ID account which is a member of the Administrators group

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3254 CUSTOMER 2012-06-13

ProcedureTo remove default access to the Management Console and create a group that does have access to the

console use the procedure described below

NOTE

Create your Management Console administrative group either on the server that hosts the

Management Console or in the Active Directory

1 In the context menu of the servers My Computer icon choose Manage

2 In the Computer Management dialog box choose Local Users and Groups Groups

NOTE

Alternatively you can perform analogous steps in Active Directory

3 In the 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

NOTE

This step is a necessary precursor to the completion of this procedure

10 In the Security dialog box click Copy to ensure that the System group retains its privileges

11 Remove access to the Management Console from all groups that should not have it

12 Choose Authentication in the center pane then disable Windows authentication

ResultUsers who have not been granted access to the Management Console can still open the Management

Console Web page but it contains no data or menu options This does not affect the access that a user

would otherwise have to Planning and Consolidation

345 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 32] Their rights in

Active Directory determine what they can access in the Console

By default any member of the Administrators Active Directory group on the application server or

domain has full access to all of the features of the Console except the Planning and Consolidation

logging area Access to Planning and Consolidation logging is controlled within the Planning and

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3354

Consolidation Administration Client task security The user must be granted View system logs task

privileges For more information see the SAP Library Planning and Consolidation Administrators Guide in

httpservicesapcominstguidesepm-bpc 100 version for the Microsoft platform

Your IT policy determines whether you grant access by group or user You may wish to create several

levels of Console users (read-only users for example) in your environment

To grant or limit access to users or groups you can add or remove the following privileges from the

areas described in this table

Privilege Rights Management Area

Task Manager and Kill Process Administrators group on application server or domain

Performance Monitor Counters Administrators group on application server or domain Power Users group on application server or domain Performance Monitor Users group on application server

Microsoft Analysis Services performance monitoring

Administrators group on application server or domain

Microsoft SQL Server Monitoring (performance counters and statistics)

Administrators group on application server or domain

346 Using Client Certificates

To enable the use of client certificates in Planning and Consolidation you must follow several manual

steps

NOTE

Planning 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 httptechnetmicrosoftcomen-us

librarycc753810aspx

For more information about configuring the client certificate mapping authentication see http

technetmicrosoftcomen-uslibrarycc732996(WS10)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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3454 CUSTOMER 2012-06-13

This option allows you to use a client certificate or username and password (Basic

authentication) to connect to Planning and Consolidation

2 Enable anonymous authentication

1 In the IIS Manager expand the node of the Planning and Consolidation web site

2 Select the ManagementConsole directory (ltWebsitegtManagementConsole) to open the

ManagementConsole home page

3 Double-click Authentication and enable Anonymous Authentication

4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way

as in step 3

5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the same

way as in step 3

3 Change the web configuration settings

1 Open the ltPC_MSgtWebsrvrWebBPCwebconfig file

2 Find the text clientCredentialType=Windows

3 Change value of clientCredentialType to None (clientCredentialType=None)

4 Open the PC_MSWebsrvrWebPOASBCwebconfig file Repeat steps 2 and 3

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3554

This page is left blank for documents that are printed on both sides

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

The installation of the Planning and Consolidation Administration Client allows administrators to

build and maintain Planning and Consolidation environments and models and administer security

All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions

add-in for Microsoft Office for more information see the SAP BusinessObjects EPM solutions add-in for

Microsoft Office help

NOTE

You must update the Administration Client to the same version as the server

If your PC is on a different domain than your server you must set the Internet Explorer

Security Zone value of the Planning and Consolidation client to prompt for user name and

password Otherwise the Planning and Consolidation Start Page does not display

41 Installing the Administration Client

Prerequisites

NOTE

For a definitive list of system requirements see the Product Availability Matrix on SAP Service

Marketplace at httpservicesapcompam Search on Planning and Consolidation

The following list describes the minimum software requirements

Microsoft Internet Explorer 70 or 80

Microsoft Office 2007 or 2010

NET Framework 20 or higher (install any required NET Framework Hotfixes by referring to

httpsupportmicrosoftcomkb)

Pentium IV (1 GHz CPU)

512 MB RAM

100 MB of free hard disk space in the My Documents folder

20 MB of free hard disk space for the installed Administration files

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

41 Installing the Administration Client

2012-06-13 CUSTOMER 3754

NOTE

We recommend that you install all of the latest Microsoft Windows hotfixes prior to installing

the Administration client For information about which hotfixes to install see http

updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us

ProcedureThe following procedure describes how to install the Administration Client on to an administratorrsquos

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 AddRemove Programs in the Windows Control Panel

3 Point your browser to the Planning and Consolidation Web at httpltPC_serverportgtsap

bpcweb

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

42 Installing the EPM Add-in

The Planning and Consolidation installation media does not contain the EPM addin setup program

You must download the most recent version of the full setup (EPM Add-inexe) from the Service

Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPC

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

43 Using the Client Auto Update Program

If Planning and Consolidation version 100 or later is installed you can use the Client Auto Update

program to set up the server so that it determines if an upgrade for a connecting Administration client

is necessary

The following describes the use of the auto update program for the Administration Client and the EPM

add-in

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

42 Installing the EPM Add-in

3854 CUSTOMER 2012-06-13

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 37]

To use the Client Auto Update program for the Administration Client proceed as follows

1 From the Server Manager select Options Client Options

2 Select Admin Update

3 If users without administrator rights on their machines use the auto update enter an administrator

ID and password in the Admin ID and Admin password fields respectively The Admin ID should be a

member of the local administrators group on all the computers running the auto update This

setting is not needed if all users have administrator rights on their machines

4 Select Update

For the EPM Add-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 Optionshellip 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 Market Place (SMP) at httpservicesapcom

All support packages and patches are available from the SMP as a zip file

EPMEXCLCLNTltSPLgtzip is for a support package

EPMEXCLCLNTltSPLgtPltPLgtzip 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 ltSP versiongtmsp

EPM Addin Support Package ltSP versiongtxml

For a patch these files are

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

2012-06-13 CUSTOMER 3954

EPM Addin Patch ltpatch numbergtmsp

EPM Addin Patch ltpatch numbergtxml

2 Unzip the zip file and extract the two files to the application server folder (WebsrvrWebBPC

Installation)

3 From the Server Manager select Options Client Options

The system lists the available packages Select the package that you want to use for the autoupdate

You can set a different update policy for each package listed

EXAMPLE

The following table illustrates some possible situations assuming that you have installed the

first full version (V1)

Available maintenance packages

V2-user updateV3-force updateV4-force updateV5-user update

V5-user update V5-user updateV6-auto updateV7-force update

Minimum Required Version

V4 V4 V7

Notification A prompt tells the user to install maintenance package V4 using the Forced Update behavior

If User Update is enabled the prompt informs the user that maintenance package V5 is available

A prompt tells the user to install maintenance package V7 using the Forced Update behavior

New Version V4 V4 or V5 V7

If you change the update policy for any package click Update to complete the change

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

4054 CUSTOMER 2012-06-13

5 Connection Issues

You may experience connection problems with ports the proxy server or programs and settings that

interact with these components If you have any issues related to connection review the following

recommendations and troubleshooting tips

51 Checking for Open Ports

You must ensure that all required ports are open for inboundoutbound 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 431181836 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

NOTE

You can use the following site to scan for the normal ports It allows you to manually enter a port

number to test

httpwwwmyserverorgportsniffasp

You can change the name of a port

52 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 Explorer Tools Internet Options Connections LAN Settings ) or at the server level

Enabling content filtering on the proxy server or firewall may cause connection problems

If external users are having trouble connecting to the server make sure the proxy server connects

using a fully qualified domain name Fully qualified domain names typically resolve both internal

and external IP addresses

Each secure Planning and Consolidation server name must be identified on the proxy server

Proxy servers may or may not require authentication which could conflict with Planning and

Consolidation authentication Do not use authentication on the proxy server The system

5 Connection Issues

51 Checking for Open Ports

2012-06-13 CUSTOMER 4154

synchronizes the user name and password on the remote server with the local user name and

password

NOTE

For more information about setting up an ISA proxy server contact SAP Support to request a

copy of Setting up ISA Proxy Server White Paper

Internet Explorer Settings 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

5 Connection Issues

52 Proxy Server and Firewall Issues

4254 CUSTOMER 2012-06-13

6 Installing Planning and Consolidation with Two Active Directory Domains

To set up a Planning and Consolidation 10 application server in a hosted environment and use your

own domain users follow this procedure In general you install Planning and Consolidation on the

host domain use the host domain account and assign it to the Planning and Consolidation users

SysAdmin Admin and Users Then you accept one way trust (the host domain trusts your domain)

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

6 Installing Planning and Consolidation with Two Active Directory Domains

2012-06-13 CUSTOMER 4354

This page is left blank for documents that are printed on both sides

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

This section describes best practices and instructions for installing Planning and Consolidation in a

Terminal Services or Citrix Server deployment

71 Terminal Services Home Directories

We recommend using Terminal Server home directories rather than using the userrsquos 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

72 System Requirements

The Citrix server should be one of the following systems

XenApp 5 Enterprise

XenApp 5 Platinum

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 37])

73 Installing Planning and Consolidation

Prerequisites

The server installation files have been downloaded from SAP Service Marketplace and installed

Procedure

The following steps outline how to install the Planning and Consolidation clients in a Terminal Services

(TS) or Citrix Server deployment

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

71 Terminal Services Home Directories

2012-06-13 CUSTOMER 4554

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 userinstall

4 Open a browser and connect to the URL httpltPC_serverportgtsapbpcweb

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 userexecute 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 Iexploreexe http(s)

ltServerNamegt-NetBIOS or FQDNsapbpcweb

To publish Planning and Consolidation Administration CProgram FilesPC_MS

BPCAdminMainexe

74 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 userrsquos desktop) must be moved to the All UsersDesktop folder

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

74 Creating a Shortcut to the Launch Page

4654 CUSTOMER 2012-06-13

8 Installing SSIS Custom Tasks

This section provides background information and instructions for installing SQL Server Integration

Services (SSIS) for SQL Server 2008 and SQL Server 2012

The Planning and Consolidation Data Manager component supports and uses SSIS Since SQL Server

2008 and SQL Server 2012 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

81 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 Filelistxml 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

OSoftSetupexe ‒ 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 or OSoftSSIS2012_Client on the client machine followed by the SQL Server

version If you want to use SQL 2008 Tasks under the SQL 2012 environment you must install

OSoftSSIS2008_Client on the application server For detailed information see SAP Note 1707410

You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package by extracting

OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPC

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 or

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4754

OSoftSSIS2012_Client for creating a COM+ application For more information see Before You Modify

the SSIS Packages [page 50] and Setup of a COM+ Application on the Application Server [page 51]

Bin folder

This folder contains the following components

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCCachedll Planning and Consolidation Cache file

BPCDataFlowPackagedll or BPCDataFlowPackage2012dll

BPCDMdll

BPCDMTaskMaindll COM+ component

BPCFilePreviewdll

BPCGacUtil_20exe System File

BPCGacUtil_40exe System File

BPCImpersonatordll Planning and Consolidation Impersonator

BPCLogicdll

BPCScriptdll

BPCServerZipdll

BPCServiceResdll

BPCTransferMembersdll

BPCWriteBackdll

InteropDTSdll

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

4854 CUSTOMER 2012-06-13

Name Remark

OSoftAdminServerdll

OSoftAuditdll

OSoftComLibServerdll

OSoftCommonResQrydll

OSoftConfigurationdll

OSoftCustomXMLSvrdll

OSoftDatabaseADMINdll

OSoftDatabaseSYSADMINdll

OSoftDatabaseSYSADMINDMdll

OSoftDatabaseUSERdll

OSoftDMDTSXExecutedll or OSoftDMDTSXExecute2012dll

OSoftDMTaskFormdll

OSoftDMTaskMaindll

OSoftDMToolsdll

OSoftFileManagedll

OSoftLoggingdll

OSoftLogWriterdll

OSoftMetaDatadll

OSoftSQEdll

OSoftSystemConfigdll

OutlookSoftconfig Configuration file to connect DB server

XceedCompressiondll XceedZip file

XceedCompressionFormatsdll XceedZip file

XceedFileSystemdll XceedZip file

XceedZipdll XceedZip file

Config folder

This folder has FileListxml 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 FileListxml 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

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4954

OSoftSetupexe

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

NOTE

If you installed the OSoftSSIS2008_Client or OSoftSSIS2012_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

Resources Folder

This folder contains the BPCServicesdll and BPCServiceUIdll files which contain resource text

Only English resources are included for the SSIS custom tasks

82 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

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008 and 2012 respectively

8 Installing SSIS Custom Tasks

82 Before You Modify the SSIS Packages

5054 CUSTOMER 2012-06-13

Name Remark

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012 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

lthellipgtOSoftSSIS2008_Clientbin or lthellipgtOSoftSSIS2012_Clientbin

On the Planning and Consolidation application server

ltdrivegtWebsrvrbin

2 Paste these files into the folder 100DTSTasks for SQL Server 2008 or into 110DTSTasks for

SQL Server 2012 For example if you install your SQL 2008 server or R2 on CProgram Files

Microsoft SQL Server paste all files into the CProgram Files (x86)Microsoft SQL Server

100DTSTasks folder

In Integration Services set the property Run64BitRunTime to True

83 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 or OSoftSSIS2012_Client on the

application server

8 Installing SSIS Custom Tasks

83 Setup of a COM+ Application on the Application Server

2012-06-13 CUSTOMER 5154

Typographic Conventions

Example Description

ltgt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example Enter your ltUser Namegt

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 httpwwwsapcom

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

5254 CUSTOMER 2012-06-13

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

  • SAP BusinessObjects Planning and Consolidation 100
    • Table of Contents
    • 1 Introduction
      • 11 SAP Notes for the Installation
      • 12 Naming Conventions
        • 2 Installing Planning and Consolidation Servers
          • 21 Basic Steps
          • 22 Prerequisites
          • 23 Before Starting the Planning and Consolidation Server Installation
          • 24 Logging on to Servers
          • 25 Service-level Accounts
          • 26 Standard and Advanced Settings
          • 27 Installing the Prerequisites
            • 271 Installing the Prerequisites ndash Basic Steps
            • 272 Installing the Operating System
            • 273 Installing the SQL Server
            • 274 Installing Analysis Services
            • 275 Installing the Anti-Cross Site Scripting Library
              • 28 Installing on a Single Server
              • 29 Installing the Server in a Multiserver Configuration
                • 3 After Installing Planning and Consolidation Servers
                  • 31 Post-Installation Steps
                  • 32 Connecting to Solution Manager Diagnostics
                  • 33 Configuring the Planning and Consolidation NET Application Servers
                  • 34 Post-Installation Optional Configuration Steps
                    • 341 Enabling the Management Console
                    • 342 Setting Up ODBC Logging in IIS for the Default Web Site
                    • 343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2
                    • 344 Removing Default Access to the Console
                    • 345 Management Console Access Control
                    • 346 Using Client Certificates
                        • 4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office
                          • 41 Installing the Administration Client
                          • 42 Installing the EPM Add-in
                          • 43 Using the Client Auto Update Program
                            • 5 Connection Issues
                              • 51 Checking for Open Ports
                              • 52 Proxy Server and Firewall Issues
                                • 6 Installing Planning and Consolidation with Two Active Directory Domains
                                • 7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
                                  • 71 Terminal Services Home Directories
                                  • 72 System Requirements
                                  • 73 Installing Planning and Consolidation
                                  • 74 Creating a Shortcut to the Launch Page
                                    • 8 Installing SSIS Custom Tasks
                                      • 81 Composition of SSIS Custom Task Installation
                                      • 82 Before You Modify the SSIS Packages
                                      • 83 Setup of a COM+ Application on the Application Server
                                          • Copyright and trademarks
Page 11: Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

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

21 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 at httpservicesapcominstguidesepm-bpc 100 version for the Microsoft platform

2 Perform the tasks in the Before Starting the Planning and Consolidation Server Installation [page 13] section

including installing all prerequisites

3 From the application server install the Planning and Consolidation server See Installing Planning and

Consolidation on a Single Server [page 24]

NOTE

You must install both Planning and Consolidation 100 as well as the most recent Planning

and Consolidation 100 Support Package available from the SAP Service Marketplace at

httpservicesapcomswdc Software Downloads Support Packages and Patches A - Z Index

B SAP BPC FOR MICROSOFT SBOP PC 100 FOR MICROSOFT Comprised Software Component

Versions SAP CPM BPC 100 M Windows Server on x64 64bit

4 If you have multiple machines see Installing the Server in a Multiserver Configuration [page 26]

5 Perform the steps in the section After Installing Planning and Consolidation Servers [page 27]

22 Prerequisites

The following table describes the software you need to install before installing the Planning and

Consolidation server and the minimum versions required

NOTE

A list of the supported operating systems and database systems is also available in the Product

Availability Matrix on SAP Service Marketplace at httpservicesapcompam Search on

Planning and Consolidation

2 Installing Planning and Consolidation Servers

21 Basic Steps

2012-06-13 CUSTOMER 1154

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 or

Data Center with or without Hyper-V

NOTE

The operating system must be configured with NTFS

Relational Database Microsoft SQL Server 2008 Enterprise Edition Microsoft SQL Server 2008 R2 (Gemini) Enterprise Edition Microsoft SQL Server 2012 Enterprise Edition

OLAP Database Microsoft SQL Server 2008 Enterprise Edition ‒ Analysis Server Microsoft SQL Server 2008 R2 Enterprise Edition ‒ Analysis Server Microsoft SQL Server 2012 Enterprise Edition ‒ Analysis Server

Data Integration Microsoft SQL Server 2008 Enterprise Edition ‒ SQL Service Integration Services

Microsoft SQL Server 2008 R2 Enterprise Edition ‒ SQL Service Integration Services

Microsoft SQL Server 2012 Enterprise Edition ‒ SQL Service Integration Services

Other Requirements MSXML 40 SP2 or later ADOMDNET

ADOMDNET 100 when running SQL Server 2008 or 2008 R2 ADOMDNET 110 when running SQL Server 2012

SQL Server software components NET 40 IIS 75 or IIS 70

(Included in your Operating System IIS 75 is required for Windows 2008 R2 editions)

Anti-Cross Site Scripting Library 42This component must be downloaded before installing the server The server installation program asks for the path of each file and copies the files into the appropriate Planning and Consolidation path

Microsoft Visual C++ 2005 Runtime Libraries SP1 Microsoft Access Database Engine 2010 64bit VMWare ESX 3x or ESX 40

(Required only if a landscape deployment strategy using virtualization technologies is planned)

NOTE

MSXML 40 SP2 ADOMDNET 100 and Microsoft Visual C++ 2005 Runtime Libraries SP1 are included with the installation program but not installed automatically

RECOMMENDATION

For SQL Server 2008 only we recommend the installation of Microsoft SQL Server 2008 SP1

(or later) cumulative update package 6 or higher to solve a problem with incorrect periodic

2 Installing Planning and Consolidation Servers

22 Prerequisites

1254 CUSTOMER 2012-06-13

values being returned with calculated accounts For more information see SAP Note number

1429246 which also contains download information

We recommend SQL Server 2008 (or R2) Enterprise Edition or SQL Server 2012 Enterprise

Edition for the OLAP database to support proactive cache and cube partitioning It is

technically possible to use SQL Server 2008 (or R2) Standard Edition or SQL Server 2012

Standard Edition for data integration servers but we do not recommend this

23 Before Starting the Planning and Consolidation Server Installation

You must perform the following tasks before starting your Planning and Consolidation server

installation

Install all the prerequisite software including all of the latest Microsoft hotfixes For more

information see Installing the Prerequisites [page 17]

If you access your application through a firewall verify with your network administrator which

TCP ports to choose during the installation By default port 80 is the setting for standard http

access and port 443 is the setting for https access If you require a service to listen on a different

port you can specify it during the installation program in Advanced Settings See Standard and Advanced

Settings [page 16]

Make sure all required server ports are open and that there is communication between the physical

servers on which you are going to install the server types See Checking for Open Ports [page 41]

Set up the required service accounts that you need to install the Planning and Consolidation server

See Service-Level Accounts [page 15]

The sample environment EnvironmentShell has been updated in this version of Planning and

Consolidation and automatically overwrites the previous version If you have made any

modifications to EnvironmentShell that you want to keep make a copy of it before continuing

with the installation

If you have the URLScan and IIS Lockdown tools installed on your application server you must

reinstall them

Disable your anti-virus software program After the installation when you enable the program

turn off Script Blocking

If a version of Planning and Consolidation on a NetWeaver platform exists uninstall it before you

install Planning and Consolidation 100 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 fsntfsV

All servers in a multiserver environment must be members of the same domain

2 Installing Planning and Consolidation Servers

23 Before Starting the Planning and Consolidation Server Installation

2012-06-13 CUSTOMER 1354

In a multiserver environment the installing ID must be a domain user ID We recommend that

you do not log on to the servers using a local server user ID even if the user ID is a member of the

Administrator group on the server This way you have the proper authority to install software and

to modify the Component Services See Logging On to Servers [page 14]

You must determine the IP addresses or server names for all servers before installing Planning and

Consolidation We recommend that you use static IP addresses

IIS must be enabled

If the application server is not able to copy files to the database server during the installation because

of port access reasons (DMZ WORKGROUP or nontrusted domain authentication failures) do

the following

1 Copy the EnvironmentShell database file ServerEnvironmentShelldb10 from the

Planning and Consolidation installation program to any folder on the SQL server (for example

cEnvironmentShelldb10)

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 cEnvironmentShelldb10)

Install the Anti-Cross Site Scripting Library which provides protection to Web-based applications

against Cross-Site Scripting (XSS) attacks See Installing the Anti-Cross Site Scripting Library [page 24]

24 Logging on to Servers

When installing in a multiserver environment you must use a domain user ID to log on to all

components

A local server user ID is a member of the Administrator group on the server A domain user ID is a

member of the Administrator group of a domain to which the server belongs or a member of the

Administrator group on the local server

Errors may display during the installation program and in the diagnostic program if the installing user

is not assigned to the Administrator group directly but is assigned to a group with Administrator rights

You can ignore these messages

NOTE

If you change the password used to install Planning and Consolidation you must change the

password for the applicable Planning and Consolidation service To do this go to Server Manager

on the application server and select Server Reset Logon Credentials For more information see

the SAP Planning and Consolidation Operations Guide in httpservicesapcominstguidesepm-bpc

100 for the Microsoft Platform SBOP Plan amp Consol 100 MS Administrators Guide

2 Installing Planning and Consolidation Servers

24 Logging on to Servers

1454 CUSTOMER 2012-06-13

25 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

PrerequisitesPlanning and Consolidation 100 has the following Windows services

BPC SendGovernor which manages Microsoft Analysis Service locks to ensure consistent performance

and avoid deadlocks

BPC ServiceManager which manages the System Landscape Directory (SLD) service logging service

and global caches

BPC CTS ServiceManager which listens and handles CTS import requests from the CTS+ transport

management system

Since these services should be able to access to the FileShare server an Admin account is assigned

automatically to the service during the installation of the Planning and Consolidation server program

Even though an Admin account has been assigned to the server correctly the services may fail to start

with the error message

Could not start the BPC SendGovernor service

The reason for this is that the Admin account is not registered as a service

When installing a service to run under a domain user account the account must have the right to

logon as a service on the local machine This logon right strictly applies only to the local computer

and must be granted in the Local Security Policy

To edit the Local Security Policy of the computer you want to define the logon as a service

permission perform the following actions

1 Start the Local Security Settings Microsoft Management Console (MMC) snap-in

2 Expand Local Policies and then click User Rights Assignment

3 In the right-hand pane right-click Log on as a service and then click Security

4 Add the user to the policy and click OK

5 Close the Local Security Settings MMC snap-in

For more details see How to Troubleshoot Service Startup Permissions http

supportmicrosoftcomkb259733

FeaturesDuring the installation enter user IDs and passwords for the following user types

System Admin ID

This ID is read-only and is the same as the installation user ID that is the system displays the ID

on the installation screen but you cannot modify it This ID allows access to code that provides

2 Installing Planning and Consolidation Servers

25 Service-level Accounts

2012-06-13 CUSTOMER 1554

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 readwrite 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

26 Standard and Advanced Settings

The following tables describe the standard and advanced settings for the installation program After

the server is installed you can change these settings using the Server Manager

NOTE

When defining server names the name refers to the NetBIOS name IP address and fully qualified

domain names (FQDN)

Standard Settings

Standard settings are typically used for a single-server environment The following table describes each

setting

Server Option Value Description

SQL Database server name The name of the SQL DB server

OLAP server name The name of the OLAP server

File Share server name The default value is the name of the File Share server that should be the computer name

Local data path Where the data files are saved on the File Share server By default this is CPC_MSData

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

Server Option Value Description

SQL Server Name The name of the SQL DB server Defaults to the local server

2 Installing Planning and Consolidation Servers

26 Standard and Advanced Settings

1654 CUSTOMER 2012-06-13

Server Option Value Description

Instance name The SQL instance name If left blank the default instance is used

Port number The default port number for the SQL Server is 1433

Provider The only available value is SQL

Local path for EnvironmentShell 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 CPC_MSData

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 changesSee the Kerberos authentication settings section in the SAP Library Server Manager Guide on httpservicesapcominstguidesEPM-BPC

100 for the Microsoft Platform

Scheduler Server Name The name of the server used for scheduling usually the application server for example GMPV50072862B If you have multiple application servers select the appropriate one

NOTE

If the primary server stops working you must manually configure your application server database to froward requests to another application server

27 Installing the Prerequisites

271 Installing the Prerequisites ndash Basic Steps

Before installing your Planning and Consolidation server you must install the prerequisite Microsoft

software the operating system IIS SQL server analysis services ADOMDNET and MSXML This

section provides guidance on installing each component For specific versions required see

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 1754

Prerequisites [page 11] and the Product Availability Matrix on the SAP Service Marketplace at http

servicesapcompam Search on Planning and Consolidation

NOTE

To ensure a successful installation you must install the software in the order listed in this

procedure

Check all third-party infrastructure services to ensure that they are functioning and that their

authentication models are documented (stated) since you need to reference this information

during the installation These third-party services include IIS OLAP service SQL services and

Active Directory (AD)

We recommend not installing Microsoft Office on the application server

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

(UMCexe) on the Planning and Consolidation CD in a folder called UMC_100_INSTALLER When

you run the installation package the wizard guides you through the following steps

1 Choose a language for the UMC install wizard to use

2 Check that the prerequisite check status is Succeeded and click Next

3 When you are ready to install the UMC click Next on the welcome screen

4 Click I accept the License Agreement and then Next

5 Choose the destination directory for the UMC installation and click Next

6 Select the languages that you wish to install

7 Select the features that you want to install (POAFHelper dotnet is mandatory for Planning

and Consolidation)

8 On Start Installation click Next to complete the installation

2 Install the required operating system on the single-server computer or on each physical server for

a multiserver configuration See Installing the Operating System [page 19]

3 Install the latest service pack for your operating system To install this service pack go to http

wwwmicrosoftcom

4 From your operating systems media install IIS

5 From your SQL Server media install SQL Server and its required service packs and hot fixes See

Installing SQL Server [page 19]

6 From your SQL Server media install Analysis Services Enterprise Edition and its required service

packs and hot fixes See Installing Analysis Services [page 23]

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

1854 CUSTOMER 2012-06-13

7 On your application server install ADOMDNET The Planning and Consolidation zip file contains

the ADOMDNET installation package in the following locations

For SQL Server 2008 mdash BPC SetupServerSQLSERVER2008_ASADOMD10_x64msi

For SQL Server 2012 mdash BPC SetupServerSQLSERVER2012_ASADOMD11_x64msi

8 On your application server install MSXML 40 Service Pack 2 or later

The MSXML 40 SP2 installation package is contained in the Planning and Consolidation zip file at

the following location BPC SetupServermsxmlmsi

9 On your application server install Microsoft Visual C++ 2005 Runtime Libraries SP1

The Microsoft Visual C++ 2005 SP1 installation package is contained in the Planning and

Consolidation zip file at the following location BPC SetupServervcredist_x64exe

NOTE

The version of vcredist_x64exe in BPC SetupServer has been updated to 8061000 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 httpwwwmicrosoftcomdownloadsen

detailsaspxFamilyID=C06B8369-60DD-4B64-A44B-84B371EDE16Dampltdisplaylanggt=en

272 Installing the Operating System

Before installing the operating system make sure that you configure your server for NTFS

For a list of languages that are supported see the Product Availability Matrix on the SAP Service

Marketplace at httpservicesapcompam Search on Planning and Consolidation

Planning and Consolidation can support all servers with an operating system in any language

NOTE

Currently Planning and Consolidation does not support an operating system in bi-directional

languages such as Hebrew

ProcedureIf you are installing IIS 70 or 75 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

273 Installing the SQL Server

PrerequisitesDuring the installation procedure you have the opportunity to specify the location of the

EnvironmentShell database file Check that it is possible to access EnvironmentShell from the location

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 1954

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 CEnvironmentShelldb10) 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 a 2008 2008 R2 and 2012 SQL Server

SQL Server Considerations

We recommend installing all required components in sequence For example install the Operating

System (Windows Server) then enable IIS and ASPNET and install any Windows Server service

packs

IIS and NET Framework 40 are required on your application server

NOTE

If you encounter a 500 HTTP Error when trying to connect to the Planning and Consolidation

Web Client refer to Microsoft Support articles 2520479 and 2468871 for assistance

To reinforce security we recommend that you install the SQL server and SSAS components to a

nondefault instance of SQL Server

General Installation Steps

1 Launch the SQL Server Setup program entering a product key if necessary and accepting the license

terms

2 Choose Install to install the SQL support files

3 In Feature Selections select instance and shared features as indicated in the SQL Server Component

Options section below then choose Next

4 Review disc space requirements then choose Next

5 In Server Configuration Perform the following actions

1 In the Service Accounts tab enter a Planning and Consolidation sysadmin account for the SQL

Server Database Engine and the SQL Server Analysis services This is required so that the Planning

and Consolidation sysadmin can create and process the Planning and Consolidation database

because the Microsoft SQL server tries to back up or restore database with the privileged

account This account is also required during Backup Environment and Restore Environment in the

Server Manager

For a single-server environment this account is also required if the backup file is located in a

different domain machine because SQL tries to access the folders and files with this account

For the a multiple-server environment SQL server retrieves the information of backup file

from the application server and the account requires the folder access privilege for the

application server

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2054 CUSTOMER 2012-06-13

To ensure that you have the complete access privileges we recommend the Planning and

Consolidation sysadmin for this service account

2 In the Collation tab set the collation settings to SQL_Latin1_General_CP1_CI_AS

Choose Next

6 Set Database Engine Configuration options then choose Next

We recommend you choose Mixed mode (Windows authentication and SQL authentication) This allows you

to use a restrictive SQL ID that works with the drill-through feature If you must restrict SQL

authentication for security reasons you can define a specific parameter in your drill-through

queries If you do not need drill-through support or use it without leveraging SQL authentication

you can install the SQL Server in Windows-only mode

7 Accept the Analysis Services Configuration default options and the remaining default options of the

installation program

8 Choose Install to begin the installation with the options you have set

SQL Server Component 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

Server Component What to Install

SQL Server Database Engine Services

SSAS Server Analysis Services

Application Server The following Shared Features Client Tools Connectivity Integration Services Client Tools SDK

Custom Settings for the SQL Server

As of version 100 Planning and Consolidation supports the following new features for SQL Server 2008

SQL Server 2008 R2 and SQL Server 2012

Process Dimension

It is now possible to process a dimension with multiple selections At processing time the process

dimension module makes changed or added information for each dimension and process for all selected

dimensions and cubes in parallel

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 2154

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

NOTE

Setting 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 tblFactWBltappgt table

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 Microsoftreg SQL Servertrade

20052008 which you can download from wwwmicrosoftcom (search on ldquoTable Partitioningrdquo to find

all relevant articles)

After Installing SQL Server 2008 SQL Server 2008 R2 and SQL Server 2012

From SQL Server Configuration Manager confirm that the SQL Server Browser service is

running The browser service is required for Planning and Consolidation

From SQL Server Configuration Manager do the following

1 Select Protocols for ltInstanceNamegt then double-click TCPIP from the right side of the window

2 When prompted for the TCPIP Properties select IP Addresses You see two IPs that indicate the

localhost and external network interface machine

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2254 CUSTOMER 2012-06-13

3 If you want to use IP1 which indicates Server IP set Enabled to Yes and specify the TCP Port as

desired

4 Delete 0 from TCP Dynamic Ports Set IPAll - TCP Ports as desired (for example 1533)

RECOMMENDATION

We do not recommend using dynamic ports

In an SQL server the default instance has a listener which listens on a fixed port (TCP

port 1433) However for the named instance the port on which the SQL server listens is

random and dynamically selected when the named instance of the SQL server starts This

recommendation prevents any conflict problems

From the SQL Server Configuration Manager specify the client protocol options for the application

server

1 Select Client Protocols from the SQL Native Client Configuration folder

2 From the right side of the window double-click TCPIP The TCPIP 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

NOTE

We 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

274 Installing Analysis Services

ProcedureAfter you install SQL Server and its required service packs and hotfixes you must install SQL Server

Analysis Services and its required service packs and hotfixes

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 2354

NOTE

If you have migrated your Analysis Services repository to the SQL Server back up the database

that contains the repository before installing this release

To install Analysis Services for SQL Server 2008 SQL Server 2008 R2 or SQL Server 2012 follow the steps

and guidelines in httptechnetmicrosoftcomen-uslibraryms143219aspx

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 httpwwwmicrosoftcomdownloads

detailsaspxFamilyID=3be0488d-e7aa-4078-a050- ae39912d2e43ampdisplaylang=en

275 Installing the Anti-Cross Site Scripting Library

Procedure

Before installing Planning and Consolidation servers you must download the Anti-Cross Site Scripting

Library (version 42 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 AntiXSSLibraryDLL from the Microsoft Web

site at httpwwwmicrosoftcomdownloadendetailsaspxid=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 AntiXssLibrarydll

28 Installing on a Single Server

When you install all Planning and Consolidation server components on a single server you should

consider the following issues

Make sure the server has a minimum of 800 MB of hard disk space

Additional environment installations require more free disk space which is a minimum of two

times the uncompressed size of the environment files

When you install Planning and Consolidation on a single-server the system adds the following server

components

SQL Server

SQL Server Analysis Services (SSAS)

Application Server

FileShare server

Procedure

To install Planning and Consolidation on a single server take the following steps

1 Exit all Windows programs

2 Installing Planning and Consolidation Servers

28 Installing on a Single Server

2454 CUSTOMER 2012-06-13

2 Log on to the server with a local server user ID or domain user ID For more information see Logging

on to servers [page 14]

3 Make sure all prerequisite software is installed on the server For more information see Installing

the Prerequisites [page 17]

4 Obtain SAP Planning and Consolidation from the Downloads SAP Installations amp Upgrades area of

SAP Service Marketplace then extract the files and run StartUpexe

5 From the Server Install screen select Install the Planning and Consolidation server

6 From the Welcome screen choose Next

7 From the License Agreement page choose I accept the terms of the license agreement then choose Next

8 From the Installation Method page accept the default Single machine enter a system ID for the system

landscape directory (SLD) and choose Next

NOTE

Entering a system ID of the SLD is only required if you have a SAP Solution Manager license

If you do not have a SAP Solution Manager license you can leave this field empty

9 From the Authentication Method page choose the desired authentication method and choose Next

10 If you have chosen SAP BusinessObjects User Management System in the previous screen on the CMS

Authentication page enter the information required to log on to CMS as an administrator

The following information is required

Field Description

System name CMS system name (server nameport number) for example CMSServer6400

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

11 After entering the CMS administrator authentication details choose Next

12 From the Service type accounts page enter service-level account user IDs and passwords See Service-

Level Accounts [page 15]

13 After defining the IDs and passwords choose Next

14 From the Server Information page (see Standard and Advanced Settings [page 16]) do one of the following

Review the standard settings and choose Next

To set advanced settings choose the Advanced Settings button Enter the desired information

and choose Next

2 Installing Planning and Consolidation Servers

28 Installing on a Single Server

2012-06-13 CUSTOMER 2554

15 Specify the location and name of AntiXssLibrarydll See Installing the Anti-Cross Site Scripting Library [page

24]

Choose Next

16 Select destination folders for Programs and Data The Data files include Webfolders and FileDB

(published reports) and should be installed on a separate drive in a production environment This

recommendation reduces the hard disk IO time and helps to speed up SQL commands

Accept the defaults or make your selections then choose Next

17 Select the default values for the Web client The values are used to determine the default language

and region for the Web client when you connect to it You can change the values in the Planning

and Consolidation Server Manager

18 The installation process takes a few moments When it is complete choose Exit

19 A prompt is displayed to restart your computer Select OK to restart

20 Perform the steps in After Installing Planning and Consolidation Servers [page 27]

29 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 24]) with the following

exceptions

On the Installation Method page do not accept the default instead choose Network Load Balancing

environment With this option there is an additional choice to Include sample environment (required on only

one of the application servers) This is because when you install the application server it connects to the

database server and creates the sample environment (EnvironmentShell) Installing the sample

environment is required on only one application server and you may choose which one

In the Virtual Name field enter the virtual IP address virtual name in the default properties

2 Installing Planning and Consolidation Servers

29 Installing the Server in a Multiserver Configuration

2654 CUSTOMER 2012-06-13

3 After Installing Planning and Consolidation Servers

31 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 28]

2 Configure the Planning and Consolidation NET and application server to ensure that it and its

related services function properly and reliably For more information see Configuring the Planning and

Consolidation NET Application Server [page 29]

3 Optional configuration steps [page 30]

1 To ensure proper functioning of the Management Console create an SQL user and modify

the System DSN and IIS to reflect those user credentials See Enabling Management Console [page

30]

2 Configure custom ODBC logging for the default Web site For details of how to configure

custom logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web

Site [page 31]

3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC

Data Source [page 32]

4 Modify the default access rights to the Management Console By default users in Active

Directory can access the Management Console with whatever rights they have been granted

on the server For information about removing default access and creating a group that can

access the console see Removing Default Access to the Console [page 32]

5 Add authorized users or groups to the group that can access the Management Console We

recommend that you only grant Management Console access to system administrators

Planning and Consolidation users should not have any access For more information see

Management Console Access Control [page 33]

6 Configure the use of client certificates for authentication See Using Client Certificates [page

34]

4 Take the following steps to set up security

If you are defining security and application structure continue with step 5

3 After Installing Planning and Consolidation Servers

31 Post-Installation Steps

2012-06-13 CUSTOMER 2754

If you want to designate someone other than the system administrator to manage security

and application structure log on to EnvironmentShell designate a user as a Primary

Administrator

This user must have Administration ‒ Environment and Security ‒ Define User task rights

so that he or she can add and delete environments and define user security

The Primary Administrator can continue with the next step (5)

5 From the machine on which you administer Planning and Consolidation install the

Administration client See Installing the Administration Client [page 37]

6 Start Planning and Consolidation Administration from the launch page

7 Select Connection Wizard and log on to EnvironmentShell

8 Create a new environment using EnvironmentShell as the source

9 Log on to the newly created environment and set up users teams and task profiles (You must

set up task profiles since there is no access to Planning and Consolidation tasks)

10 Set up your data access profiles and add users (or teams) to one or more data access profiles (You

must complete this step since there is no access to dimensions or members)

NOTE

To allow users to request and query large amounts of data you can edit the metabasexml file located

at CWindowssystem32inetsrv Set the following parameters to the stated values

ASPBUFFERINGLIMIT = 10485760

MAXREQUESTENTITYALLOWED = 10485760

32 Connecting to Solution Manager Diagnostics

NOTE

You only need to perform the steps in this section if you have a SAP Solution Manager licence

The diagnostics functions in SAP Solution Manager allow identification analysis and resolution of

problems This procedure provides the steps required to connect Planning and Consolidation to

Solution Manager Diagnostics

Procedure

1 Install the Diagnostics Agent according to SAP Note 1234387 on all servers where application servers

are installed

NOTE

Installation files for Diagnostics Agent are available on Service Marketplace by navigating to

Support Packages and Patches mdash Entry by Application Group SAP Technology Components SAP

SOLUTION MANAGER SAP SOLUTION MANAGER 70 EHP 1 Entry by Component Agents

for managed systems DIAGNOSTICS AGENT 711

3 After Installing Planning and Consolidation Servers

32 Connecting to Solution Manager Diagnostics

2854 CUSTOMER 2012-06-13

Download the installation file based on the 64-bit Windows Server system landscape

2 To access the DBA Cockpit you must create a user account with sufficient rights on all Windows

Servers where Microsoft SQL Server is installed Do the following

1 Start Computer Management then select Action New User

2 Create a new user

3 Right-click on the user then choose Properties On the Member Of tab select Add

4 Add the group SQLServerltReleasegtSQLAgentUser$ltDomain or hostnamegt$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 httpsservicesapcom~sapidb011000358700000074392009E and follow

the chapters that apply to Planning and Consolidation

33 Configuring the Planning and Consolidation NET Application Servers

Procedure

Modifying machineconfig Files

To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock

occurrences that would cause the application server to ldquosleeprdquo and not process anymore you can

modify the machineconfig file which resides in the WINDOWSMicrosoftNETFramework64

v4030319Config directory

1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to

specify whether to automatically configure settings to achieve optimal performance based on the

machine configuration You can set this attribute to True or False

For more information see httpmsdnmicrosoftcomen-uslibrary7w2sway1aspx

2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the

Planning and Consolidation application) or Machineconfig (for all applications including

Planning and Consolidation) to ensure the validationKey and decryptionKey keys have the same

value on all application servers This way when the authentication cookie is checked the

authentication ticket used on one server can still be valid on another server

For more information and sample Visual Basic code for generating random key values see http

msdnmicrosoftcomen-uslibraryms998288aspx

3 After Installing Planning and Consolidation Servers

33 Configuring the Planning and Consolidation NET Application Servers

2012-06-13 CUSTOMER 2954

paght000007_webfarmdeploymentconsiderations and httpmsdnmicrosoftcomen-us

libraryms998310aspx

34 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 30]

2 Configure custom ODBC logging for the default Web site For details of how to configure custom

logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page

31]

3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC Data

Source [page 32]

4 Modify the default access rights to the Management Console By default users in Active Directory

can access the Management Console with whatever rights they have been granted on the server

For information about removing default access and creating a group that can access the console

see Removing Default Access to the Console [page 32]

5 Add authorized users or groups to the group that can access the Management Console We

recommend that you only grant Management Console access to system administrators Planning

and Consolidation users should not have any access For more information see Management Console

Access Control [page 33]

6 Configure the use of client certificates for authentication See Using Client Certificates [page 34]

341 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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3054 CUSTOMER 2012-06-13

NOTE

Without these updates the Management Console does work but some functionality (specifically

User Activity and Service Status) does not work as expected

Should you need to uninstall Planning and Consolidation we recommend that you reset the

Active Log Format field in IIS to W3C Extended Log File Format

342 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 ApplicationHostconfig set the property customLogPluginClsid to the value FF16065B-

DE82-11CF-BC0A-00AA006111E0 Set the logFormat to Custom You can find this in the ltlogFilegt

node in ApplicationHostconfig as shown here

ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0

logFormat=Custom gt

Use the following AppCmds to configure IIS to use ODBC logging for the default Web site

appcmd site set sitenameDefault Web Site

logFilecustomLogPluginClsidFF16065B-DE82-11CF-BC0A-00AA006111E0

appcmd site set sitenameDefault Web Site logFilelogFormatCustom

Configuring ODBC Logging Parameters in ApplicationHostconfig

Configure ApplicationHostconfig to contain the database table information as set up in the Microsoft

Support article specified in the Prerequisites section Configure these settings in the ltodbcLogginggt

node under ltsystemwebServergt

EXAMPLE

ltlocation path=Default Web Sitegt

ltsystemwebServergt

ltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog

userName=Username password=mypassword gt

ltsystemwebServergt

ltlocationgt

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3154

Use the following AppCmds to configure these attributes for the default Web site

appcmd set config Default Web Site sectionodbcLogging

dataSourceBPC_ManagementDSN commitappHost

appcmd set config Default Web Site sectionodbcLogging tableNameBPCLog

commitappHost

appcmd set config Default Web Site sectionodbcLogging userNameUsername

commitappHost

appcmd set config Default Web Site sectionodbcLogging passwordmypassword

commitappHost

NOTE

You cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must

use the SQL Server ODBC driver For more information see the Microsoft Knowledge Base article

931202 The requirements for using the ODBC logging feature in IIS

343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2

ProcedureThis procedure describes how to set up an ODBC data source for the Management Console in Windows

Server 2008 or Windows Server 2008 R2

Proceed as follows

1 Open ODBC Connection Manager

2 On the System DSN tab page add a new DSN

Choose Add

Choose SQL Server as the driver

Choose Finish

3 In the Name and Description fields enter BPC_ManagementDSN

4 In the Server field enter the name of your SQL Server Choose Next

5 Leave the default settings and choose Next

6 Choose the Change the default database to field and enter AppServer Choose Next

7 Leave default settings and choose Next

8 Choose OK

344 Removing Default Access to the Console

NOTE

If you have chosen SAP BusinessObjects User Management System in the installation screen you

do not need to remove or configure access because the Management Console service always runs

with the System Admin ID account which is a member of the Administrators group

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3254 CUSTOMER 2012-06-13

ProcedureTo remove default access to the Management Console and create a group that does have access to the

console use the procedure described below

NOTE

Create your Management Console administrative group either on the server that hosts the

Management Console or in the Active Directory

1 In the context menu of the servers My Computer icon choose Manage

2 In the Computer Management dialog box choose Local Users and Groups Groups

NOTE

Alternatively you can perform analogous steps in Active Directory

3 In the 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

NOTE

This step is a necessary precursor to the completion of this procedure

10 In the Security dialog box click Copy to ensure that the System group retains its privileges

11 Remove access to the Management Console from all groups that should not have it

12 Choose Authentication in the center pane then disable Windows authentication

ResultUsers who have not been granted access to the Management Console can still open the Management

Console Web page but it contains no data or menu options This does not affect the access that a user

would otherwise have to Planning and Consolidation

345 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 32] Their rights in

Active Directory determine what they can access in the Console

By default any member of the Administrators Active Directory group on the application server or

domain has full access to all of the features of the Console except the Planning and Consolidation

logging area Access to Planning and Consolidation logging is controlled within the Planning and

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3354

Consolidation Administration Client task security The user must be granted View system logs task

privileges For more information see the SAP Library Planning and Consolidation Administrators Guide in

httpservicesapcominstguidesepm-bpc 100 version for the Microsoft platform

Your IT policy determines whether you grant access by group or user You may wish to create several

levels of Console users (read-only users for example) in your environment

To grant or limit access to users or groups you can add or remove the following privileges from the

areas described in this table

Privilege Rights Management Area

Task Manager and Kill Process Administrators group on application server or domain

Performance Monitor Counters Administrators group on application server or domain Power Users group on application server or domain Performance Monitor Users group on application server

Microsoft Analysis Services performance monitoring

Administrators group on application server or domain

Microsoft SQL Server Monitoring (performance counters and statistics)

Administrators group on application server or domain

346 Using Client Certificates

To enable the use of client certificates in Planning and Consolidation you must follow several manual

steps

NOTE

Planning 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 httptechnetmicrosoftcomen-us

librarycc753810aspx

For more information about configuring the client certificate mapping authentication see http

technetmicrosoftcomen-uslibrarycc732996(WS10)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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3454 CUSTOMER 2012-06-13

This option allows you to use a client certificate or username and password (Basic

authentication) to connect to Planning and Consolidation

2 Enable anonymous authentication

1 In the IIS Manager expand the node of the Planning and Consolidation web site

2 Select the ManagementConsole directory (ltWebsitegtManagementConsole) to open the

ManagementConsole home page

3 Double-click Authentication and enable Anonymous Authentication

4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way

as in step 3

5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the same

way as in step 3

3 Change the web configuration settings

1 Open the ltPC_MSgtWebsrvrWebBPCwebconfig file

2 Find the text clientCredentialType=Windows

3 Change value of clientCredentialType to None (clientCredentialType=None)

4 Open the PC_MSWebsrvrWebPOASBCwebconfig file Repeat steps 2 and 3

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3554

This page is left blank for documents that are printed on both sides

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

The installation of the Planning and Consolidation Administration Client allows administrators to

build and maintain Planning and Consolidation environments and models and administer security

All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions

add-in for Microsoft Office for more information see the SAP BusinessObjects EPM solutions add-in for

Microsoft Office help

NOTE

You must update the Administration Client to the same version as the server

If your PC is on a different domain than your server you must set the Internet Explorer

Security Zone value of the Planning and Consolidation client to prompt for user name and

password Otherwise the Planning and Consolidation Start Page does not display

41 Installing the Administration Client

Prerequisites

NOTE

For a definitive list of system requirements see the Product Availability Matrix on SAP Service

Marketplace at httpservicesapcompam Search on Planning and Consolidation

The following list describes the minimum software requirements

Microsoft Internet Explorer 70 or 80

Microsoft Office 2007 or 2010

NET Framework 20 or higher (install any required NET Framework Hotfixes by referring to

httpsupportmicrosoftcomkb)

Pentium IV (1 GHz CPU)

512 MB RAM

100 MB of free hard disk space in the My Documents folder

20 MB of free hard disk space for the installed Administration files

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

41 Installing the Administration Client

2012-06-13 CUSTOMER 3754

NOTE

We recommend that you install all of the latest Microsoft Windows hotfixes prior to installing

the Administration client For information about which hotfixes to install see http

updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us

ProcedureThe following procedure describes how to install the Administration Client on to an administratorrsquos

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 AddRemove Programs in the Windows Control Panel

3 Point your browser to the Planning and Consolidation Web at httpltPC_serverportgtsap

bpcweb

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

42 Installing the EPM Add-in

The Planning and Consolidation installation media does not contain the EPM addin setup program

You must download the most recent version of the full setup (EPM Add-inexe) from the Service

Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPC

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

43 Using the Client Auto Update Program

If Planning and Consolidation version 100 or later is installed you can use the Client Auto Update

program to set up the server so that it determines if an upgrade for a connecting Administration client

is necessary

The following describes the use of the auto update program for the Administration Client and the EPM

add-in

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

42 Installing the EPM Add-in

3854 CUSTOMER 2012-06-13

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 37]

To use the Client Auto Update program for the Administration Client proceed as follows

1 From the Server Manager select Options Client Options

2 Select Admin Update

3 If users without administrator rights on their machines use the auto update enter an administrator

ID and password in the Admin ID and Admin password fields respectively The Admin ID should be a

member of the local administrators group on all the computers running the auto update This

setting is not needed if all users have administrator rights on their machines

4 Select Update

For the EPM Add-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 Optionshellip 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 Market Place (SMP) at httpservicesapcom

All support packages and patches are available from the SMP as a zip file

EPMEXCLCLNTltSPLgtzip is for a support package

EPMEXCLCLNTltSPLgtPltPLgtzip 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 ltSP versiongtmsp

EPM Addin Support Package ltSP versiongtxml

For a patch these files are

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

2012-06-13 CUSTOMER 3954

EPM Addin Patch ltpatch numbergtmsp

EPM Addin Patch ltpatch numbergtxml

2 Unzip the zip file and extract the two files to the application server folder (WebsrvrWebBPC

Installation)

3 From the Server Manager select Options Client Options

The system lists the available packages Select the package that you want to use for the autoupdate

You can set a different update policy for each package listed

EXAMPLE

The following table illustrates some possible situations assuming that you have installed the

first full version (V1)

Available maintenance packages

V2-user updateV3-force updateV4-force updateV5-user update

V5-user update V5-user updateV6-auto updateV7-force update

Minimum Required Version

V4 V4 V7

Notification A prompt tells the user to install maintenance package V4 using the Forced Update behavior

If User Update is enabled the prompt informs the user that maintenance package V5 is available

A prompt tells the user to install maintenance package V7 using the Forced Update behavior

New Version V4 V4 or V5 V7

If you change the update policy for any package click Update to complete the change

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

4054 CUSTOMER 2012-06-13

5 Connection Issues

You may experience connection problems with ports the proxy server or programs and settings that

interact with these components If you have any issues related to connection review the following

recommendations and troubleshooting tips

51 Checking for Open Ports

You must ensure that all required ports are open for inboundoutbound 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 431181836 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

NOTE

You can use the following site to scan for the normal ports It allows you to manually enter a port

number to test

httpwwwmyserverorgportsniffasp

You can change the name of a port

52 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 Explorer Tools Internet Options Connections LAN Settings ) or at the server level

Enabling content filtering on the proxy server or firewall may cause connection problems

If external users are having trouble connecting to the server make sure the proxy server connects

using a fully qualified domain name Fully qualified domain names typically resolve both internal

and external IP addresses

Each secure Planning and Consolidation server name must be identified on the proxy server

Proxy servers may or may not require authentication which could conflict with Planning and

Consolidation authentication Do not use authentication on the proxy server The system

5 Connection Issues

51 Checking for Open Ports

2012-06-13 CUSTOMER 4154

synchronizes the user name and password on the remote server with the local user name and

password

NOTE

For more information about setting up an ISA proxy server contact SAP Support to request a

copy of Setting up ISA Proxy Server White Paper

Internet Explorer Settings 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

5 Connection Issues

52 Proxy Server and Firewall Issues

4254 CUSTOMER 2012-06-13

6 Installing Planning and Consolidation with Two Active Directory Domains

To set up a Planning and Consolidation 10 application server in a hosted environment and use your

own domain users follow this procedure In general you install Planning and Consolidation on the

host domain use the host domain account and assign it to the Planning and Consolidation users

SysAdmin Admin and Users Then you accept one way trust (the host domain trusts your domain)

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

6 Installing Planning and Consolidation with Two Active Directory Domains

2012-06-13 CUSTOMER 4354

This page is left blank for documents that are printed on both sides

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

This section describes best practices and instructions for installing Planning and Consolidation in a

Terminal Services or Citrix Server deployment

71 Terminal Services Home Directories

We recommend using Terminal Server home directories rather than using the userrsquos 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

72 System Requirements

The Citrix server should be one of the following systems

XenApp 5 Enterprise

XenApp 5 Platinum

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 37])

73 Installing Planning and Consolidation

Prerequisites

The server installation files have been downloaded from SAP Service Marketplace and installed

Procedure

The following steps outline how to install the Planning and Consolidation clients in a Terminal Services

(TS) or Citrix Server deployment

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

71 Terminal Services Home Directories

2012-06-13 CUSTOMER 4554

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 userinstall

4 Open a browser and connect to the URL httpltPC_serverportgtsapbpcweb

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 userexecute 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 Iexploreexe http(s)

ltServerNamegt-NetBIOS or FQDNsapbpcweb

To publish Planning and Consolidation Administration CProgram FilesPC_MS

BPCAdminMainexe

74 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 userrsquos desktop) must be moved to the All UsersDesktop folder

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

74 Creating a Shortcut to the Launch Page

4654 CUSTOMER 2012-06-13

8 Installing SSIS Custom Tasks

This section provides background information and instructions for installing SQL Server Integration

Services (SSIS) for SQL Server 2008 and SQL Server 2012

The Planning and Consolidation Data Manager component supports and uses SSIS Since SQL Server

2008 and SQL Server 2012 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

81 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 Filelistxml 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

OSoftSetupexe ‒ 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 or OSoftSSIS2012_Client on the client machine followed by the SQL Server

version If you want to use SQL 2008 Tasks under the SQL 2012 environment you must install

OSoftSSIS2008_Client on the application server For detailed information see SAP Note 1707410

You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package by extracting

OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPC

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 or

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4754

OSoftSSIS2012_Client for creating a COM+ application For more information see Before You Modify

the SSIS Packages [page 50] and Setup of a COM+ Application on the Application Server [page 51]

Bin folder

This folder contains the following components

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCCachedll Planning and Consolidation Cache file

BPCDataFlowPackagedll or BPCDataFlowPackage2012dll

BPCDMdll

BPCDMTaskMaindll COM+ component

BPCFilePreviewdll

BPCGacUtil_20exe System File

BPCGacUtil_40exe System File

BPCImpersonatordll Planning and Consolidation Impersonator

BPCLogicdll

BPCScriptdll

BPCServerZipdll

BPCServiceResdll

BPCTransferMembersdll

BPCWriteBackdll

InteropDTSdll

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

4854 CUSTOMER 2012-06-13

Name Remark

OSoftAdminServerdll

OSoftAuditdll

OSoftComLibServerdll

OSoftCommonResQrydll

OSoftConfigurationdll

OSoftCustomXMLSvrdll

OSoftDatabaseADMINdll

OSoftDatabaseSYSADMINdll

OSoftDatabaseSYSADMINDMdll

OSoftDatabaseUSERdll

OSoftDMDTSXExecutedll or OSoftDMDTSXExecute2012dll

OSoftDMTaskFormdll

OSoftDMTaskMaindll

OSoftDMToolsdll

OSoftFileManagedll

OSoftLoggingdll

OSoftLogWriterdll

OSoftMetaDatadll

OSoftSQEdll

OSoftSystemConfigdll

OutlookSoftconfig Configuration file to connect DB server

XceedCompressiondll XceedZip file

XceedCompressionFormatsdll XceedZip file

XceedFileSystemdll XceedZip file

XceedZipdll XceedZip file

Config folder

This folder has FileListxml 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 FileListxml 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

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4954

OSoftSetupexe

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

NOTE

If you installed the OSoftSSIS2008_Client or OSoftSSIS2012_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

Resources Folder

This folder contains the BPCServicesdll and BPCServiceUIdll files which contain resource text

Only English resources are included for the SSIS custom tasks

82 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

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008 and 2012 respectively

8 Installing SSIS Custom Tasks

82 Before You Modify the SSIS Packages

5054 CUSTOMER 2012-06-13

Name Remark

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012 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

lthellipgtOSoftSSIS2008_Clientbin or lthellipgtOSoftSSIS2012_Clientbin

On the Planning and Consolidation application server

ltdrivegtWebsrvrbin

2 Paste these files into the folder 100DTSTasks for SQL Server 2008 or into 110DTSTasks for

SQL Server 2012 For example if you install your SQL 2008 server or R2 on CProgram Files

Microsoft SQL Server paste all files into the CProgram Files (x86)Microsoft SQL Server

100DTSTasks folder

In Integration Services set the property Run64BitRunTime to True

83 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 or OSoftSSIS2012_Client on the

application server

8 Installing SSIS Custom Tasks

83 Setup of a COM+ Application on the Application Server

2012-06-13 CUSTOMER 5154

Typographic Conventions

Example Description

ltgt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example Enter your ltUser Namegt

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 httpwwwsapcom

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

5254 CUSTOMER 2012-06-13

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

  • SAP BusinessObjects Planning and Consolidation 100
    • Table of Contents
    • 1 Introduction
      • 11 SAP Notes for the Installation
      • 12 Naming Conventions
        • 2 Installing Planning and Consolidation Servers
          • 21 Basic Steps
          • 22 Prerequisites
          • 23 Before Starting the Planning and Consolidation Server Installation
          • 24 Logging on to Servers
          • 25 Service-level Accounts
          • 26 Standard and Advanced Settings
          • 27 Installing the Prerequisites
            • 271 Installing the Prerequisites ndash Basic Steps
            • 272 Installing the Operating System
            • 273 Installing the SQL Server
            • 274 Installing Analysis Services
            • 275 Installing the Anti-Cross Site Scripting Library
              • 28 Installing on a Single Server
              • 29 Installing the Server in a Multiserver Configuration
                • 3 After Installing Planning and Consolidation Servers
                  • 31 Post-Installation Steps
                  • 32 Connecting to Solution Manager Diagnostics
                  • 33 Configuring the Planning and Consolidation NET Application Servers
                  • 34 Post-Installation Optional Configuration Steps
                    • 341 Enabling the Management Console
                    • 342 Setting Up ODBC Logging in IIS for the Default Web Site
                    • 343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2
                    • 344 Removing Default Access to the Console
                    • 345 Management Console Access Control
                    • 346 Using Client Certificates
                        • 4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office
                          • 41 Installing the Administration Client
                          • 42 Installing the EPM Add-in
                          • 43 Using the Client Auto Update Program
                            • 5 Connection Issues
                              • 51 Checking for Open Ports
                              • 52 Proxy Server and Firewall Issues
                                • 6 Installing Planning and Consolidation with Two Active Directory Domains
                                • 7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
                                  • 71 Terminal Services Home Directories
                                  • 72 System Requirements
                                  • 73 Installing Planning and Consolidation
                                  • 74 Creating a Shortcut to the Launch Page
                                    • 8 Installing SSIS Custom Tasks
                                      • 81 Composition of SSIS Custom Task Installation
                                      • 82 Before You Modify the SSIS Packages
                                      • 83 Setup of a COM+ Application on the Application Server
                                          • Copyright and trademarks
Page 12: Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

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 or

Data Center with or without Hyper-V

NOTE

The operating system must be configured with NTFS

Relational Database Microsoft SQL Server 2008 Enterprise Edition Microsoft SQL Server 2008 R2 (Gemini) Enterprise Edition Microsoft SQL Server 2012 Enterprise Edition

OLAP Database Microsoft SQL Server 2008 Enterprise Edition ‒ Analysis Server Microsoft SQL Server 2008 R2 Enterprise Edition ‒ Analysis Server Microsoft SQL Server 2012 Enterprise Edition ‒ Analysis Server

Data Integration Microsoft SQL Server 2008 Enterprise Edition ‒ SQL Service Integration Services

Microsoft SQL Server 2008 R2 Enterprise Edition ‒ SQL Service Integration Services

Microsoft SQL Server 2012 Enterprise Edition ‒ SQL Service Integration Services

Other Requirements MSXML 40 SP2 or later ADOMDNET

ADOMDNET 100 when running SQL Server 2008 or 2008 R2 ADOMDNET 110 when running SQL Server 2012

SQL Server software components NET 40 IIS 75 or IIS 70

(Included in your Operating System IIS 75 is required for Windows 2008 R2 editions)

Anti-Cross Site Scripting Library 42This component must be downloaded before installing the server The server installation program asks for the path of each file and copies the files into the appropriate Planning and Consolidation path

Microsoft Visual C++ 2005 Runtime Libraries SP1 Microsoft Access Database Engine 2010 64bit VMWare ESX 3x or ESX 40

(Required only if a landscape deployment strategy using virtualization technologies is planned)

NOTE

MSXML 40 SP2 ADOMDNET 100 and Microsoft Visual C++ 2005 Runtime Libraries SP1 are included with the installation program but not installed automatically

RECOMMENDATION

For SQL Server 2008 only we recommend the installation of Microsoft SQL Server 2008 SP1

(or later) cumulative update package 6 or higher to solve a problem with incorrect periodic

2 Installing Planning and Consolidation Servers

22 Prerequisites

1254 CUSTOMER 2012-06-13

values being returned with calculated accounts For more information see SAP Note number

1429246 which also contains download information

We recommend SQL Server 2008 (or R2) Enterprise Edition or SQL Server 2012 Enterprise

Edition for the OLAP database to support proactive cache and cube partitioning It is

technically possible to use SQL Server 2008 (or R2) Standard Edition or SQL Server 2012

Standard Edition for data integration servers but we do not recommend this

23 Before Starting the Planning and Consolidation Server Installation

You must perform the following tasks before starting your Planning and Consolidation server

installation

Install all the prerequisite software including all of the latest Microsoft hotfixes For more

information see Installing the Prerequisites [page 17]

If you access your application through a firewall verify with your network administrator which

TCP ports to choose during the installation By default port 80 is the setting for standard http

access and port 443 is the setting for https access If you require a service to listen on a different

port you can specify it during the installation program in Advanced Settings See Standard and Advanced

Settings [page 16]

Make sure all required server ports are open and that there is communication between the physical

servers on which you are going to install the server types See Checking for Open Ports [page 41]

Set up the required service accounts that you need to install the Planning and Consolidation server

See Service-Level Accounts [page 15]

The sample environment EnvironmentShell has been updated in this version of Planning and

Consolidation and automatically overwrites the previous version If you have made any

modifications to EnvironmentShell that you want to keep make a copy of it before continuing

with the installation

If you have the URLScan and IIS Lockdown tools installed on your application server you must

reinstall them

Disable your anti-virus software program After the installation when you enable the program

turn off Script Blocking

If a version of Planning and Consolidation on a NetWeaver platform exists uninstall it before you

install Planning and Consolidation 100 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 fsntfsV

All servers in a multiserver environment must be members of the same domain

2 Installing Planning and Consolidation Servers

23 Before Starting the Planning and Consolidation Server Installation

2012-06-13 CUSTOMER 1354

In a multiserver environment the installing ID must be a domain user ID We recommend that

you do not log on to the servers using a local server user ID even if the user ID is a member of the

Administrator group on the server This way you have the proper authority to install software and

to modify the Component Services See Logging On to Servers [page 14]

You must determine the IP addresses or server names for all servers before installing Planning and

Consolidation We recommend that you use static IP addresses

IIS must be enabled

If the application server is not able to copy files to the database server during the installation because

of port access reasons (DMZ WORKGROUP or nontrusted domain authentication failures) do

the following

1 Copy the EnvironmentShell database file ServerEnvironmentShelldb10 from the

Planning and Consolidation installation program to any folder on the SQL server (for example

cEnvironmentShelldb10)

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 cEnvironmentShelldb10)

Install the Anti-Cross Site Scripting Library which provides protection to Web-based applications

against Cross-Site Scripting (XSS) attacks See Installing the Anti-Cross Site Scripting Library [page 24]

24 Logging on to Servers

When installing in a multiserver environment you must use a domain user ID to log on to all

components

A local server user ID is a member of the Administrator group on the server A domain user ID is a

member of the Administrator group of a domain to which the server belongs or a member of the

Administrator group on the local server

Errors may display during the installation program and in the diagnostic program if the installing user

is not assigned to the Administrator group directly but is assigned to a group with Administrator rights

You can ignore these messages

NOTE

If you change the password used to install Planning and Consolidation you must change the

password for the applicable Planning and Consolidation service To do this go to Server Manager

on the application server and select Server Reset Logon Credentials For more information see

the SAP Planning and Consolidation Operations Guide in httpservicesapcominstguidesepm-bpc

100 for the Microsoft Platform SBOP Plan amp Consol 100 MS Administrators Guide

2 Installing Planning and Consolidation Servers

24 Logging on to Servers

1454 CUSTOMER 2012-06-13

25 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

PrerequisitesPlanning and Consolidation 100 has the following Windows services

BPC SendGovernor which manages Microsoft Analysis Service locks to ensure consistent performance

and avoid deadlocks

BPC ServiceManager which manages the System Landscape Directory (SLD) service logging service

and global caches

BPC CTS ServiceManager which listens and handles CTS import requests from the CTS+ transport

management system

Since these services should be able to access to the FileShare server an Admin account is assigned

automatically to the service during the installation of the Planning and Consolidation server program

Even though an Admin account has been assigned to the server correctly the services may fail to start

with the error message

Could not start the BPC SendGovernor service

The reason for this is that the Admin account is not registered as a service

When installing a service to run under a domain user account the account must have the right to

logon as a service on the local machine This logon right strictly applies only to the local computer

and must be granted in the Local Security Policy

To edit the Local Security Policy of the computer you want to define the logon as a service

permission perform the following actions

1 Start the Local Security Settings Microsoft Management Console (MMC) snap-in

2 Expand Local Policies and then click User Rights Assignment

3 In the right-hand pane right-click Log on as a service and then click Security

4 Add the user to the policy and click OK

5 Close the Local Security Settings MMC snap-in

For more details see How to Troubleshoot Service Startup Permissions http

supportmicrosoftcomkb259733

FeaturesDuring the installation enter user IDs and passwords for the following user types

System Admin ID

This ID is read-only and is the same as the installation user ID that is the system displays the ID

on the installation screen but you cannot modify it This ID allows access to code that provides

2 Installing Planning and Consolidation Servers

25 Service-level Accounts

2012-06-13 CUSTOMER 1554

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 readwrite 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

26 Standard and Advanced Settings

The following tables describe the standard and advanced settings for the installation program After

the server is installed you can change these settings using the Server Manager

NOTE

When defining server names the name refers to the NetBIOS name IP address and fully qualified

domain names (FQDN)

Standard Settings

Standard settings are typically used for a single-server environment The following table describes each

setting

Server Option Value Description

SQL Database server name The name of the SQL DB server

OLAP server name The name of the OLAP server

File Share server name The default value is the name of the File Share server that should be the computer name

Local data path Where the data files are saved on the File Share server By default this is CPC_MSData

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

Server Option Value Description

SQL Server Name The name of the SQL DB server Defaults to the local server

2 Installing Planning and Consolidation Servers

26 Standard and Advanced Settings

1654 CUSTOMER 2012-06-13

Server Option Value Description

Instance name The SQL instance name If left blank the default instance is used

Port number The default port number for the SQL Server is 1433

Provider The only available value is SQL

Local path for EnvironmentShell 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 CPC_MSData

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 changesSee the Kerberos authentication settings section in the SAP Library Server Manager Guide on httpservicesapcominstguidesEPM-BPC

100 for the Microsoft Platform

Scheduler Server Name The name of the server used for scheduling usually the application server for example GMPV50072862B If you have multiple application servers select the appropriate one

NOTE

If the primary server stops working you must manually configure your application server database to froward requests to another application server

27 Installing the Prerequisites

271 Installing the Prerequisites ndash Basic Steps

Before installing your Planning and Consolidation server you must install the prerequisite Microsoft

software the operating system IIS SQL server analysis services ADOMDNET and MSXML This

section provides guidance on installing each component For specific versions required see

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 1754

Prerequisites [page 11] and the Product Availability Matrix on the SAP Service Marketplace at http

servicesapcompam Search on Planning and Consolidation

NOTE

To ensure a successful installation you must install the software in the order listed in this

procedure

Check all third-party infrastructure services to ensure that they are functioning and that their

authentication models are documented (stated) since you need to reference this information

during the installation These third-party services include IIS OLAP service SQL services and

Active Directory (AD)

We recommend not installing Microsoft Office on the application server

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

(UMCexe) on the Planning and Consolidation CD in a folder called UMC_100_INSTALLER When

you run the installation package the wizard guides you through the following steps

1 Choose a language for the UMC install wizard to use

2 Check that the prerequisite check status is Succeeded and click Next

3 When you are ready to install the UMC click Next on the welcome screen

4 Click I accept the License Agreement and then Next

5 Choose the destination directory for the UMC installation and click Next

6 Select the languages that you wish to install

7 Select the features that you want to install (POAFHelper dotnet is mandatory for Planning

and Consolidation)

8 On Start Installation click Next to complete the installation

2 Install the required operating system on the single-server computer or on each physical server for

a multiserver configuration See Installing the Operating System [page 19]

3 Install the latest service pack for your operating system To install this service pack go to http

wwwmicrosoftcom

4 From your operating systems media install IIS

5 From your SQL Server media install SQL Server and its required service packs and hot fixes See

Installing SQL Server [page 19]

6 From your SQL Server media install Analysis Services Enterprise Edition and its required service

packs and hot fixes See Installing Analysis Services [page 23]

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

1854 CUSTOMER 2012-06-13

7 On your application server install ADOMDNET The Planning and Consolidation zip file contains

the ADOMDNET installation package in the following locations

For SQL Server 2008 mdash BPC SetupServerSQLSERVER2008_ASADOMD10_x64msi

For SQL Server 2012 mdash BPC SetupServerSQLSERVER2012_ASADOMD11_x64msi

8 On your application server install MSXML 40 Service Pack 2 or later

The MSXML 40 SP2 installation package is contained in the Planning and Consolidation zip file at

the following location BPC SetupServermsxmlmsi

9 On your application server install Microsoft Visual C++ 2005 Runtime Libraries SP1

The Microsoft Visual C++ 2005 SP1 installation package is contained in the Planning and

Consolidation zip file at the following location BPC SetupServervcredist_x64exe

NOTE

The version of vcredist_x64exe in BPC SetupServer has been updated to 8061000 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 httpwwwmicrosoftcomdownloadsen

detailsaspxFamilyID=C06B8369-60DD-4B64-A44B-84B371EDE16Dampltdisplaylanggt=en

272 Installing the Operating System

Before installing the operating system make sure that you configure your server for NTFS

For a list of languages that are supported see the Product Availability Matrix on the SAP Service

Marketplace at httpservicesapcompam Search on Planning and Consolidation

Planning and Consolidation can support all servers with an operating system in any language

NOTE

Currently Planning and Consolidation does not support an operating system in bi-directional

languages such as Hebrew

ProcedureIf you are installing IIS 70 or 75 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

273 Installing the SQL Server

PrerequisitesDuring the installation procedure you have the opportunity to specify the location of the

EnvironmentShell database file Check that it is possible to access EnvironmentShell from the location

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 1954

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 CEnvironmentShelldb10) 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 a 2008 2008 R2 and 2012 SQL Server

SQL Server Considerations

We recommend installing all required components in sequence For example install the Operating

System (Windows Server) then enable IIS and ASPNET and install any Windows Server service

packs

IIS and NET Framework 40 are required on your application server

NOTE

If you encounter a 500 HTTP Error when trying to connect to the Planning and Consolidation

Web Client refer to Microsoft Support articles 2520479 and 2468871 for assistance

To reinforce security we recommend that you install the SQL server and SSAS components to a

nondefault instance of SQL Server

General Installation Steps

1 Launch the SQL Server Setup program entering a product key if necessary and accepting the license

terms

2 Choose Install to install the SQL support files

3 In Feature Selections select instance and shared features as indicated in the SQL Server Component

Options section below then choose Next

4 Review disc space requirements then choose Next

5 In Server Configuration Perform the following actions

1 In the Service Accounts tab enter a Planning and Consolidation sysadmin account for the SQL

Server Database Engine and the SQL Server Analysis services This is required so that the Planning

and Consolidation sysadmin can create and process the Planning and Consolidation database

because the Microsoft SQL server tries to back up or restore database with the privileged

account This account is also required during Backup Environment and Restore Environment in the

Server Manager

For a single-server environment this account is also required if the backup file is located in a

different domain machine because SQL tries to access the folders and files with this account

For the a multiple-server environment SQL server retrieves the information of backup file

from the application server and the account requires the folder access privilege for the

application server

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2054 CUSTOMER 2012-06-13

To ensure that you have the complete access privileges we recommend the Planning and

Consolidation sysadmin for this service account

2 In the Collation tab set the collation settings to SQL_Latin1_General_CP1_CI_AS

Choose Next

6 Set Database Engine Configuration options then choose Next

We recommend you choose Mixed mode (Windows authentication and SQL authentication) This allows you

to use a restrictive SQL ID that works with the drill-through feature If you must restrict SQL

authentication for security reasons you can define a specific parameter in your drill-through

queries If you do not need drill-through support or use it without leveraging SQL authentication

you can install the SQL Server in Windows-only mode

7 Accept the Analysis Services Configuration default options and the remaining default options of the

installation program

8 Choose Install to begin the installation with the options you have set

SQL Server Component 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

Server Component What to Install

SQL Server Database Engine Services

SSAS Server Analysis Services

Application Server The following Shared Features Client Tools Connectivity Integration Services Client Tools SDK

Custom Settings for the SQL Server

As of version 100 Planning and Consolidation supports the following new features for SQL Server 2008

SQL Server 2008 R2 and SQL Server 2012

Process Dimension

It is now possible to process a dimension with multiple selections At processing time the process

dimension module makes changed or added information for each dimension and process for all selected

dimensions and cubes in parallel

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 2154

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

NOTE

Setting 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 tblFactWBltappgt table

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 Microsoftreg SQL Servertrade

20052008 which you can download from wwwmicrosoftcom (search on ldquoTable Partitioningrdquo to find

all relevant articles)

After Installing SQL Server 2008 SQL Server 2008 R2 and SQL Server 2012

From SQL Server Configuration Manager confirm that the SQL Server Browser service is

running The browser service is required for Planning and Consolidation

From SQL Server Configuration Manager do the following

1 Select Protocols for ltInstanceNamegt then double-click TCPIP from the right side of the window

2 When prompted for the TCPIP Properties select IP Addresses You see two IPs that indicate the

localhost and external network interface machine

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2254 CUSTOMER 2012-06-13

3 If you want to use IP1 which indicates Server IP set Enabled to Yes and specify the TCP Port as

desired

4 Delete 0 from TCP Dynamic Ports Set IPAll - TCP Ports as desired (for example 1533)

RECOMMENDATION

We do not recommend using dynamic ports

In an SQL server the default instance has a listener which listens on a fixed port (TCP

port 1433) However for the named instance the port on which the SQL server listens is

random and dynamically selected when the named instance of the SQL server starts This

recommendation prevents any conflict problems

From the SQL Server Configuration Manager specify the client protocol options for the application

server

1 Select Client Protocols from the SQL Native Client Configuration folder

2 From the right side of the window double-click TCPIP The TCPIP 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

NOTE

We 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

274 Installing Analysis Services

ProcedureAfter you install SQL Server and its required service packs and hotfixes you must install SQL Server

Analysis Services and its required service packs and hotfixes

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 2354

NOTE

If you have migrated your Analysis Services repository to the SQL Server back up the database

that contains the repository before installing this release

To install Analysis Services for SQL Server 2008 SQL Server 2008 R2 or SQL Server 2012 follow the steps

and guidelines in httptechnetmicrosoftcomen-uslibraryms143219aspx

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 httpwwwmicrosoftcomdownloads

detailsaspxFamilyID=3be0488d-e7aa-4078-a050- ae39912d2e43ampdisplaylang=en

275 Installing the Anti-Cross Site Scripting Library

Procedure

Before installing Planning and Consolidation servers you must download the Anti-Cross Site Scripting

Library (version 42 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 AntiXSSLibraryDLL from the Microsoft Web

site at httpwwwmicrosoftcomdownloadendetailsaspxid=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 AntiXssLibrarydll

28 Installing on a Single Server

When you install all Planning and Consolidation server components on a single server you should

consider the following issues

Make sure the server has a minimum of 800 MB of hard disk space

Additional environment installations require more free disk space which is a minimum of two

times the uncompressed size of the environment files

When you install Planning and Consolidation on a single-server the system adds the following server

components

SQL Server

SQL Server Analysis Services (SSAS)

Application Server

FileShare server

Procedure

To install Planning and Consolidation on a single server take the following steps

1 Exit all Windows programs

2 Installing Planning and Consolidation Servers

28 Installing on a Single Server

2454 CUSTOMER 2012-06-13

2 Log on to the server with a local server user ID or domain user ID For more information see Logging

on to servers [page 14]

3 Make sure all prerequisite software is installed on the server For more information see Installing

the Prerequisites [page 17]

4 Obtain SAP Planning and Consolidation from the Downloads SAP Installations amp Upgrades area of

SAP Service Marketplace then extract the files and run StartUpexe

5 From the Server Install screen select Install the Planning and Consolidation server

6 From the Welcome screen choose Next

7 From the License Agreement page choose I accept the terms of the license agreement then choose Next

8 From the Installation Method page accept the default Single machine enter a system ID for the system

landscape directory (SLD) and choose Next

NOTE

Entering a system ID of the SLD is only required if you have a SAP Solution Manager license

If you do not have a SAP Solution Manager license you can leave this field empty

9 From the Authentication Method page choose the desired authentication method and choose Next

10 If you have chosen SAP BusinessObjects User Management System in the previous screen on the CMS

Authentication page enter the information required to log on to CMS as an administrator

The following information is required

Field Description

System name CMS system name (server nameport number) for example CMSServer6400

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

11 After entering the CMS administrator authentication details choose Next

12 From the Service type accounts page enter service-level account user IDs and passwords See Service-

Level Accounts [page 15]

13 After defining the IDs and passwords choose Next

14 From the Server Information page (see Standard and Advanced Settings [page 16]) do one of the following

Review the standard settings and choose Next

To set advanced settings choose the Advanced Settings button Enter the desired information

and choose Next

2 Installing Planning and Consolidation Servers

28 Installing on a Single Server

2012-06-13 CUSTOMER 2554

15 Specify the location and name of AntiXssLibrarydll See Installing the Anti-Cross Site Scripting Library [page

24]

Choose Next

16 Select destination folders for Programs and Data The Data files include Webfolders and FileDB

(published reports) and should be installed on a separate drive in a production environment This

recommendation reduces the hard disk IO time and helps to speed up SQL commands

Accept the defaults or make your selections then choose Next

17 Select the default values for the Web client The values are used to determine the default language

and region for the Web client when you connect to it You can change the values in the Planning

and Consolidation Server Manager

18 The installation process takes a few moments When it is complete choose Exit

19 A prompt is displayed to restart your computer Select OK to restart

20 Perform the steps in After Installing Planning and Consolidation Servers [page 27]

29 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 24]) with the following

exceptions

On the Installation Method page do not accept the default instead choose Network Load Balancing

environment With this option there is an additional choice to Include sample environment (required on only

one of the application servers) This is because when you install the application server it connects to the

database server and creates the sample environment (EnvironmentShell) Installing the sample

environment is required on only one application server and you may choose which one

In the Virtual Name field enter the virtual IP address virtual name in the default properties

2 Installing Planning and Consolidation Servers

29 Installing the Server in a Multiserver Configuration

2654 CUSTOMER 2012-06-13

3 After Installing Planning and Consolidation Servers

31 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 28]

2 Configure the Planning and Consolidation NET and application server to ensure that it and its

related services function properly and reliably For more information see Configuring the Planning and

Consolidation NET Application Server [page 29]

3 Optional configuration steps [page 30]

1 To ensure proper functioning of the Management Console create an SQL user and modify

the System DSN and IIS to reflect those user credentials See Enabling Management Console [page

30]

2 Configure custom ODBC logging for the default Web site For details of how to configure

custom logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web

Site [page 31]

3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC

Data Source [page 32]

4 Modify the default access rights to the Management Console By default users in Active

Directory can access the Management Console with whatever rights they have been granted

on the server For information about removing default access and creating a group that can

access the console see Removing Default Access to the Console [page 32]

5 Add authorized users or groups to the group that can access the Management Console We

recommend that you only grant Management Console access to system administrators

Planning and Consolidation users should not have any access For more information see

Management Console Access Control [page 33]

6 Configure the use of client certificates for authentication See Using Client Certificates [page

34]

4 Take the following steps to set up security

If you are defining security and application structure continue with step 5

3 After Installing Planning and Consolidation Servers

31 Post-Installation Steps

2012-06-13 CUSTOMER 2754

If you want to designate someone other than the system administrator to manage security

and application structure log on to EnvironmentShell designate a user as a Primary

Administrator

This user must have Administration ‒ Environment and Security ‒ Define User task rights

so that he or she can add and delete environments and define user security

The Primary Administrator can continue with the next step (5)

5 From the machine on which you administer Planning and Consolidation install the

Administration client See Installing the Administration Client [page 37]

6 Start Planning and Consolidation Administration from the launch page

7 Select Connection Wizard and log on to EnvironmentShell

8 Create a new environment using EnvironmentShell as the source

9 Log on to the newly created environment and set up users teams and task profiles (You must

set up task profiles since there is no access to Planning and Consolidation tasks)

10 Set up your data access profiles and add users (or teams) to one or more data access profiles (You

must complete this step since there is no access to dimensions or members)

NOTE

To allow users to request and query large amounts of data you can edit the metabasexml file located

at CWindowssystem32inetsrv Set the following parameters to the stated values

ASPBUFFERINGLIMIT = 10485760

MAXREQUESTENTITYALLOWED = 10485760

32 Connecting to Solution Manager Diagnostics

NOTE

You only need to perform the steps in this section if you have a SAP Solution Manager licence

The diagnostics functions in SAP Solution Manager allow identification analysis and resolution of

problems This procedure provides the steps required to connect Planning and Consolidation to

Solution Manager Diagnostics

Procedure

1 Install the Diagnostics Agent according to SAP Note 1234387 on all servers where application servers

are installed

NOTE

Installation files for Diagnostics Agent are available on Service Marketplace by navigating to

Support Packages and Patches mdash Entry by Application Group SAP Technology Components SAP

SOLUTION MANAGER SAP SOLUTION MANAGER 70 EHP 1 Entry by Component Agents

for managed systems DIAGNOSTICS AGENT 711

3 After Installing Planning and Consolidation Servers

32 Connecting to Solution Manager Diagnostics

2854 CUSTOMER 2012-06-13

Download the installation file based on the 64-bit Windows Server system landscape

2 To access the DBA Cockpit you must create a user account with sufficient rights on all Windows

Servers where Microsoft SQL Server is installed Do the following

1 Start Computer Management then select Action New User

2 Create a new user

3 Right-click on the user then choose Properties On the Member Of tab select Add

4 Add the group SQLServerltReleasegtSQLAgentUser$ltDomain or hostnamegt$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 httpsservicesapcom~sapidb011000358700000074392009E and follow

the chapters that apply to Planning and Consolidation

33 Configuring the Planning and Consolidation NET Application Servers

Procedure

Modifying machineconfig Files

To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock

occurrences that would cause the application server to ldquosleeprdquo and not process anymore you can

modify the machineconfig file which resides in the WINDOWSMicrosoftNETFramework64

v4030319Config directory

1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to

specify whether to automatically configure settings to achieve optimal performance based on the

machine configuration You can set this attribute to True or False

For more information see httpmsdnmicrosoftcomen-uslibrary7w2sway1aspx

2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the

Planning and Consolidation application) or Machineconfig (for all applications including

Planning and Consolidation) to ensure the validationKey and decryptionKey keys have the same

value on all application servers This way when the authentication cookie is checked the

authentication ticket used on one server can still be valid on another server

For more information and sample Visual Basic code for generating random key values see http

msdnmicrosoftcomen-uslibraryms998288aspx

3 After Installing Planning and Consolidation Servers

33 Configuring the Planning and Consolidation NET Application Servers

2012-06-13 CUSTOMER 2954

paght000007_webfarmdeploymentconsiderations and httpmsdnmicrosoftcomen-us

libraryms998310aspx

34 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 30]

2 Configure custom ODBC logging for the default Web site For details of how to configure custom

logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page

31]

3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC Data

Source [page 32]

4 Modify the default access rights to the Management Console By default users in Active Directory

can access the Management Console with whatever rights they have been granted on the server

For information about removing default access and creating a group that can access the console

see Removing Default Access to the Console [page 32]

5 Add authorized users or groups to the group that can access the Management Console We

recommend that you only grant Management Console access to system administrators Planning

and Consolidation users should not have any access For more information see Management Console

Access Control [page 33]

6 Configure the use of client certificates for authentication See Using Client Certificates [page 34]

341 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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3054 CUSTOMER 2012-06-13

NOTE

Without these updates the Management Console does work but some functionality (specifically

User Activity and Service Status) does not work as expected

Should you need to uninstall Planning and Consolidation we recommend that you reset the

Active Log Format field in IIS to W3C Extended Log File Format

342 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 ApplicationHostconfig set the property customLogPluginClsid to the value FF16065B-

DE82-11CF-BC0A-00AA006111E0 Set the logFormat to Custom You can find this in the ltlogFilegt

node in ApplicationHostconfig as shown here

ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0

logFormat=Custom gt

Use the following AppCmds to configure IIS to use ODBC logging for the default Web site

appcmd site set sitenameDefault Web Site

logFilecustomLogPluginClsidFF16065B-DE82-11CF-BC0A-00AA006111E0

appcmd site set sitenameDefault Web Site logFilelogFormatCustom

Configuring ODBC Logging Parameters in ApplicationHostconfig

Configure ApplicationHostconfig to contain the database table information as set up in the Microsoft

Support article specified in the Prerequisites section Configure these settings in the ltodbcLogginggt

node under ltsystemwebServergt

EXAMPLE

ltlocation path=Default Web Sitegt

ltsystemwebServergt

ltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog

userName=Username password=mypassword gt

ltsystemwebServergt

ltlocationgt

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3154

Use the following AppCmds to configure these attributes for the default Web site

appcmd set config Default Web Site sectionodbcLogging

dataSourceBPC_ManagementDSN commitappHost

appcmd set config Default Web Site sectionodbcLogging tableNameBPCLog

commitappHost

appcmd set config Default Web Site sectionodbcLogging userNameUsername

commitappHost

appcmd set config Default Web Site sectionodbcLogging passwordmypassword

commitappHost

NOTE

You cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must

use the SQL Server ODBC driver For more information see the Microsoft Knowledge Base article

931202 The requirements for using the ODBC logging feature in IIS

343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2

ProcedureThis procedure describes how to set up an ODBC data source for the Management Console in Windows

Server 2008 or Windows Server 2008 R2

Proceed as follows

1 Open ODBC Connection Manager

2 On the System DSN tab page add a new DSN

Choose Add

Choose SQL Server as the driver

Choose Finish

3 In the Name and Description fields enter BPC_ManagementDSN

4 In the Server field enter the name of your SQL Server Choose Next

5 Leave the default settings and choose Next

6 Choose the Change the default database to field and enter AppServer Choose Next

7 Leave default settings and choose Next

8 Choose OK

344 Removing Default Access to the Console

NOTE

If you have chosen SAP BusinessObjects User Management System in the installation screen you

do not need to remove or configure access because the Management Console service always runs

with the System Admin ID account which is a member of the Administrators group

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3254 CUSTOMER 2012-06-13

ProcedureTo remove default access to the Management Console and create a group that does have access to the

console use the procedure described below

NOTE

Create your Management Console administrative group either on the server that hosts the

Management Console or in the Active Directory

1 In the context menu of the servers My Computer icon choose Manage

2 In the Computer Management dialog box choose Local Users and Groups Groups

NOTE

Alternatively you can perform analogous steps in Active Directory

3 In the 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

NOTE

This step is a necessary precursor to the completion of this procedure

10 In the Security dialog box click Copy to ensure that the System group retains its privileges

11 Remove access to the Management Console from all groups that should not have it

12 Choose Authentication in the center pane then disable Windows authentication

ResultUsers who have not been granted access to the Management Console can still open the Management

Console Web page but it contains no data or menu options This does not affect the access that a user

would otherwise have to Planning and Consolidation

345 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 32] Their rights in

Active Directory determine what they can access in the Console

By default any member of the Administrators Active Directory group on the application server or

domain has full access to all of the features of the Console except the Planning and Consolidation

logging area Access to Planning and Consolidation logging is controlled within the Planning and

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3354

Consolidation Administration Client task security The user must be granted View system logs task

privileges For more information see the SAP Library Planning and Consolidation Administrators Guide in

httpservicesapcominstguidesepm-bpc 100 version for the Microsoft platform

Your IT policy determines whether you grant access by group or user You may wish to create several

levels of Console users (read-only users for example) in your environment

To grant or limit access to users or groups you can add or remove the following privileges from the

areas described in this table

Privilege Rights Management Area

Task Manager and Kill Process Administrators group on application server or domain

Performance Monitor Counters Administrators group on application server or domain Power Users group on application server or domain Performance Monitor Users group on application server

Microsoft Analysis Services performance monitoring

Administrators group on application server or domain

Microsoft SQL Server Monitoring (performance counters and statistics)

Administrators group on application server or domain

346 Using Client Certificates

To enable the use of client certificates in Planning and Consolidation you must follow several manual

steps

NOTE

Planning 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 httptechnetmicrosoftcomen-us

librarycc753810aspx

For more information about configuring the client certificate mapping authentication see http

technetmicrosoftcomen-uslibrarycc732996(WS10)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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3454 CUSTOMER 2012-06-13

This option allows you to use a client certificate or username and password (Basic

authentication) to connect to Planning and Consolidation

2 Enable anonymous authentication

1 In the IIS Manager expand the node of the Planning and Consolidation web site

2 Select the ManagementConsole directory (ltWebsitegtManagementConsole) to open the

ManagementConsole home page

3 Double-click Authentication and enable Anonymous Authentication

4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way

as in step 3

5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the same

way as in step 3

3 Change the web configuration settings

1 Open the ltPC_MSgtWebsrvrWebBPCwebconfig file

2 Find the text clientCredentialType=Windows

3 Change value of clientCredentialType to None (clientCredentialType=None)

4 Open the PC_MSWebsrvrWebPOASBCwebconfig file Repeat steps 2 and 3

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3554

This page is left blank for documents that are printed on both sides

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

The installation of the Planning and Consolidation Administration Client allows administrators to

build and maintain Planning and Consolidation environments and models and administer security

All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions

add-in for Microsoft Office for more information see the SAP BusinessObjects EPM solutions add-in for

Microsoft Office help

NOTE

You must update the Administration Client to the same version as the server

If your PC is on a different domain than your server you must set the Internet Explorer

Security Zone value of the Planning and Consolidation client to prompt for user name and

password Otherwise the Planning and Consolidation Start Page does not display

41 Installing the Administration Client

Prerequisites

NOTE

For a definitive list of system requirements see the Product Availability Matrix on SAP Service

Marketplace at httpservicesapcompam Search on Planning and Consolidation

The following list describes the minimum software requirements

Microsoft Internet Explorer 70 or 80

Microsoft Office 2007 or 2010

NET Framework 20 or higher (install any required NET Framework Hotfixes by referring to

httpsupportmicrosoftcomkb)

Pentium IV (1 GHz CPU)

512 MB RAM

100 MB of free hard disk space in the My Documents folder

20 MB of free hard disk space for the installed Administration files

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

41 Installing the Administration Client

2012-06-13 CUSTOMER 3754

NOTE

We recommend that you install all of the latest Microsoft Windows hotfixes prior to installing

the Administration client For information about which hotfixes to install see http

updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us

ProcedureThe following procedure describes how to install the Administration Client on to an administratorrsquos

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 AddRemove Programs in the Windows Control Panel

3 Point your browser to the Planning and Consolidation Web at httpltPC_serverportgtsap

bpcweb

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

42 Installing the EPM Add-in

The Planning and Consolidation installation media does not contain the EPM addin setup program

You must download the most recent version of the full setup (EPM Add-inexe) from the Service

Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPC

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

43 Using the Client Auto Update Program

If Planning and Consolidation version 100 or later is installed you can use the Client Auto Update

program to set up the server so that it determines if an upgrade for a connecting Administration client

is necessary

The following describes the use of the auto update program for the Administration Client and the EPM

add-in

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

42 Installing the EPM Add-in

3854 CUSTOMER 2012-06-13

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 37]

To use the Client Auto Update program for the Administration Client proceed as follows

1 From the Server Manager select Options Client Options

2 Select Admin Update

3 If users without administrator rights on their machines use the auto update enter an administrator

ID and password in the Admin ID and Admin password fields respectively The Admin ID should be a

member of the local administrators group on all the computers running the auto update This

setting is not needed if all users have administrator rights on their machines

4 Select Update

For the EPM Add-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 Optionshellip 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 Market Place (SMP) at httpservicesapcom

All support packages and patches are available from the SMP as a zip file

EPMEXCLCLNTltSPLgtzip is for a support package

EPMEXCLCLNTltSPLgtPltPLgtzip 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 ltSP versiongtmsp

EPM Addin Support Package ltSP versiongtxml

For a patch these files are

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

2012-06-13 CUSTOMER 3954

EPM Addin Patch ltpatch numbergtmsp

EPM Addin Patch ltpatch numbergtxml

2 Unzip the zip file and extract the two files to the application server folder (WebsrvrWebBPC

Installation)

3 From the Server Manager select Options Client Options

The system lists the available packages Select the package that you want to use for the autoupdate

You can set a different update policy for each package listed

EXAMPLE

The following table illustrates some possible situations assuming that you have installed the

first full version (V1)

Available maintenance packages

V2-user updateV3-force updateV4-force updateV5-user update

V5-user update V5-user updateV6-auto updateV7-force update

Minimum Required Version

V4 V4 V7

Notification A prompt tells the user to install maintenance package V4 using the Forced Update behavior

If User Update is enabled the prompt informs the user that maintenance package V5 is available

A prompt tells the user to install maintenance package V7 using the Forced Update behavior

New Version V4 V4 or V5 V7

If you change the update policy for any package click Update to complete the change

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

4054 CUSTOMER 2012-06-13

5 Connection Issues

You may experience connection problems with ports the proxy server or programs and settings that

interact with these components If you have any issues related to connection review the following

recommendations and troubleshooting tips

51 Checking for Open Ports

You must ensure that all required ports are open for inboundoutbound 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 431181836 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

NOTE

You can use the following site to scan for the normal ports It allows you to manually enter a port

number to test

httpwwwmyserverorgportsniffasp

You can change the name of a port

52 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 Explorer Tools Internet Options Connections LAN Settings ) or at the server level

Enabling content filtering on the proxy server or firewall may cause connection problems

If external users are having trouble connecting to the server make sure the proxy server connects

using a fully qualified domain name Fully qualified domain names typically resolve both internal

and external IP addresses

Each secure Planning and Consolidation server name must be identified on the proxy server

Proxy servers may or may not require authentication which could conflict with Planning and

Consolidation authentication Do not use authentication on the proxy server The system

5 Connection Issues

51 Checking for Open Ports

2012-06-13 CUSTOMER 4154

synchronizes the user name and password on the remote server with the local user name and

password

NOTE

For more information about setting up an ISA proxy server contact SAP Support to request a

copy of Setting up ISA Proxy Server White Paper

Internet Explorer Settings 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

5 Connection Issues

52 Proxy Server and Firewall Issues

4254 CUSTOMER 2012-06-13

6 Installing Planning and Consolidation with Two Active Directory Domains

To set up a Planning and Consolidation 10 application server in a hosted environment and use your

own domain users follow this procedure In general you install Planning and Consolidation on the

host domain use the host domain account and assign it to the Planning and Consolidation users

SysAdmin Admin and Users Then you accept one way trust (the host domain trusts your domain)

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

6 Installing Planning and Consolidation with Two Active Directory Domains

2012-06-13 CUSTOMER 4354

This page is left blank for documents that are printed on both sides

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

This section describes best practices and instructions for installing Planning and Consolidation in a

Terminal Services or Citrix Server deployment

71 Terminal Services Home Directories

We recommend using Terminal Server home directories rather than using the userrsquos 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

72 System Requirements

The Citrix server should be one of the following systems

XenApp 5 Enterprise

XenApp 5 Platinum

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 37])

73 Installing Planning and Consolidation

Prerequisites

The server installation files have been downloaded from SAP Service Marketplace and installed

Procedure

The following steps outline how to install the Planning and Consolidation clients in a Terminal Services

(TS) or Citrix Server deployment

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

71 Terminal Services Home Directories

2012-06-13 CUSTOMER 4554

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 userinstall

4 Open a browser and connect to the URL httpltPC_serverportgtsapbpcweb

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 userexecute 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 Iexploreexe http(s)

ltServerNamegt-NetBIOS or FQDNsapbpcweb

To publish Planning and Consolidation Administration CProgram FilesPC_MS

BPCAdminMainexe

74 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 userrsquos desktop) must be moved to the All UsersDesktop folder

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

74 Creating a Shortcut to the Launch Page

4654 CUSTOMER 2012-06-13

8 Installing SSIS Custom Tasks

This section provides background information and instructions for installing SQL Server Integration

Services (SSIS) for SQL Server 2008 and SQL Server 2012

The Planning and Consolidation Data Manager component supports and uses SSIS Since SQL Server

2008 and SQL Server 2012 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

81 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 Filelistxml 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

OSoftSetupexe ‒ 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 or OSoftSSIS2012_Client on the client machine followed by the SQL Server

version If you want to use SQL 2008 Tasks under the SQL 2012 environment you must install

OSoftSSIS2008_Client on the application server For detailed information see SAP Note 1707410

You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package by extracting

OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPC

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 or

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4754

OSoftSSIS2012_Client for creating a COM+ application For more information see Before You Modify

the SSIS Packages [page 50] and Setup of a COM+ Application on the Application Server [page 51]

Bin folder

This folder contains the following components

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCCachedll Planning and Consolidation Cache file

BPCDataFlowPackagedll or BPCDataFlowPackage2012dll

BPCDMdll

BPCDMTaskMaindll COM+ component

BPCFilePreviewdll

BPCGacUtil_20exe System File

BPCGacUtil_40exe System File

BPCImpersonatordll Planning and Consolidation Impersonator

BPCLogicdll

BPCScriptdll

BPCServerZipdll

BPCServiceResdll

BPCTransferMembersdll

BPCWriteBackdll

InteropDTSdll

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

4854 CUSTOMER 2012-06-13

Name Remark

OSoftAdminServerdll

OSoftAuditdll

OSoftComLibServerdll

OSoftCommonResQrydll

OSoftConfigurationdll

OSoftCustomXMLSvrdll

OSoftDatabaseADMINdll

OSoftDatabaseSYSADMINdll

OSoftDatabaseSYSADMINDMdll

OSoftDatabaseUSERdll

OSoftDMDTSXExecutedll or OSoftDMDTSXExecute2012dll

OSoftDMTaskFormdll

OSoftDMTaskMaindll

OSoftDMToolsdll

OSoftFileManagedll

OSoftLoggingdll

OSoftLogWriterdll

OSoftMetaDatadll

OSoftSQEdll

OSoftSystemConfigdll

OutlookSoftconfig Configuration file to connect DB server

XceedCompressiondll XceedZip file

XceedCompressionFormatsdll XceedZip file

XceedFileSystemdll XceedZip file

XceedZipdll XceedZip file

Config folder

This folder has FileListxml 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 FileListxml 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

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4954

OSoftSetupexe

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

NOTE

If you installed the OSoftSSIS2008_Client or OSoftSSIS2012_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

Resources Folder

This folder contains the BPCServicesdll and BPCServiceUIdll files which contain resource text

Only English resources are included for the SSIS custom tasks

82 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

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008 and 2012 respectively

8 Installing SSIS Custom Tasks

82 Before You Modify the SSIS Packages

5054 CUSTOMER 2012-06-13

Name Remark

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012 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

lthellipgtOSoftSSIS2008_Clientbin or lthellipgtOSoftSSIS2012_Clientbin

On the Planning and Consolidation application server

ltdrivegtWebsrvrbin

2 Paste these files into the folder 100DTSTasks for SQL Server 2008 or into 110DTSTasks for

SQL Server 2012 For example if you install your SQL 2008 server or R2 on CProgram Files

Microsoft SQL Server paste all files into the CProgram Files (x86)Microsoft SQL Server

100DTSTasks folder

In Integration Services set the property Run64BitRunTime to True

83 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 or OSoftSSIS2012_Client on the

application server

8 Installing SSIS Custom Tasks

83 Setup of a COM+ Application on the Application Server

2012-06-13 CUSTOMER 5154

Typographic Conventions

Example Description

ltgt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example Enter your ltUser Namegt

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 httpwwwsapcom

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

5254 CUSTOMER 2012-06-13

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

  • SAP BusinessObjects Planning and Consolidation 100
    • Table of Contents
    • 1 Introduction
      • 11 SAP Notes for the Installation
      • 12 Naming Conventions
        • 2 Installing Planning and Consolidation Servers
          • 21 Basic Steps
          • 22 Prerequisites
          • 23 Before Starting the Planning and Consolidation Server Installation
          • 24 Logging on to Servers
          • 25 Service-level Accounts
          • 26 Standard and Advanced Settings
          • 27 Installing the Prerequisites
            • 271 Installing the Prerequisites ndash Basic Steps
            • 272 Installing the Operating System
            • 273 Installing the SQL Server
            • 274 Installing Analysis Services
            • 275 Installing the Anti-Cross Site Scripting Library
              • 28 Installing on a Single Server
              • 29 Installing the Server in a Multiserver Configuration
                • 3 After Installing Planning and Consolidation Servers
                  • 31 Post-Installation Steps
                  • 32 Connecting to Solution Manager Diagnostics
                  • 33 Configuring the Planning and Consolidation NET Application Servers
                  • 34 Post-Installation Optional Configuration Steps
                    • 341 Enabling the Management Console
                    • 342 Setting Up ODBC Logging in IIS for the Default Web Site
                    • 343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2
                    • 344 Removing Default Access to the Console
                    • 345 Management Console Access Control
                    • 346 Using Client Certificates
                        • 4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office
                          • 41 Installing the Administration Client
                          • 42 Installing the EPM Add-in
                          • 43 Using the Client Auto Update Program
                            • 5 Connection Issues
                              • 51 Checking for Open Ports
                              • 52 Proxy Server and Firewall Issues
                                • 6 Installing Planning and Consolidation with Two Active Directory Domains
                                • 7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
                                  • 71 Terminal Services Home Directories
                                  • 72 System Requirements
                                  • 73 Installing Planning and Consolidation
                                  • 74 Creating a Shortcut to the Launch Page
                                    • 8 Installing SSIS Custom Tasks
                                      • 81 Composition of SSIS Custom Task Installation
                                      • 82 Before You Modify the SSIS Packages
                                      • 83 Setup of a COM+ Application on the Application Server
                                          • Copyright and trademarks
Page 13: Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

values being returned with calculated accounts For more information see SAP Note number

1429246 which also contains download information

We recommend SQL Server 2008 (or R2) Enterprise Edition or SQL Server 2012 Enterprise

Edition for the OLAP database to support proactive cache and cube partitioning It is

technically possible to use SQL Server 2008 (or R2) Standard Edition or SQL Server 2012

Standard Edition for data integration servers but we do not recommend this

23 Before Starting the Planning and Consolidation Server Installation

You must perform the following tasks before starting your Planning and Consolidation server

installation

Install all the prerequisite software including all of the latest Microsoft hotfixes For more

information see Installing the Prerequisites [page 17]

If you access your application through a firewall verify with your network administrator which

TCP ports to choose during the installation By default port 80 is the setting for standard http

access and port 443 is the setting for https access If you require a service to listen on a different

port you can specify it during the installation program in Advanced Settings See Standard and Advanced

Settings [page 16]

Make sure all required server ports are open and that there is communication between the physical

servers on which you are going to install the server types See Checking for Open Ports [page 41]

Set up the required service accounts that you need to install the Planning and Consolidation server

See Service-Level Accounts [page 15]

The sample environment EnvironmentShell has been updated in this version of Planning and

Consolidation and automatically overwrites the previous version If you have made any

modifications to EnvironmentShell that you want to keep make a copy of it before continuing

with the installation

If you have the URLScan and IIS Lockdown tools installed on your application server you must

reinstall them

Disable your anti-virus software program After the installation when you enable the program

turn off Script Blocking

If a version of Planning and Consolidation on a NetWeaver platform exists uninstall it before you

install Planning and Consolidation 100 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 fsntfsV

All servers in a multiserver environment must be members of the same domain

2 Installing Planning and Consolidation Servers

23 Before Starting the Planning and Consolidation Server Installation

2012-06-13 CUSTOMER 1354

In a multiserver environment the installing ID must be a domain user ID We recommend that

you do not log on to the servers using a local server user ID even if the user ID is a member of the

Administrator group on the server This way you have the proper authority to install software and

to modify the Component Services See Logging On to Servers [page 14]

You must determine the IP addresses or server names for all servers before installing Planning and

Consolidation We recommend that you use static IP addresses

IIS must be enabled

If the application server is not able to copy files to the database server during the installation because

of port access reasons (DMZ WORKGROUP or nontrusted domain authentication failures) do

the following

1 Copy the EnvironmentShell database file ServerEnvironmentShelldb10 from the

Planning and Consolidation installation program to any folder on the SQL server (for example

cEnvironmentShelldb10)

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 cEnvironmentShelldb10)

Install the Anti-Cross Site Scripting Library which provides protection to Web-based applications

against Cross-Site Scripting (XSS) attacks See Installing the Anti-Cross Site Scripting Library [page 24]

24 Logging on to Servers

When installing in a multiserver environment you must use a domain user ID to log on to all

components

A local server user ID is a member of the Administrator group on the server A domain user ID is a

member of the Administrator group of a domain to which the server belongs or a member of the

Administrator group on the local server

Errors may display during the installation program and in the diagnostic program if the installing user

is not assigned to the Administrator group directly but is assigned to a group with Administrator rights

You can ignore these messages

NOTE

If you change the password used to install Planning and Consolidation you must change the

password for the applicable Planning and Consolidation service To do this go to Server Manager

on the application server and select Server Reset Logon Credentials For more information see

the SAP Planning and Consolidation Operations Guide in httpservicesapcominstguidesepm-bpc

100 for the Microsoft Platform SBOP Plan amp Consol 100 MS Administrators Guide

2 Installing Planning and Consolidation Servers

24 Logging on to Servers

1454 CUSTOMER 2012-06-13

25 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

PrerequisitesPlanning and Consolidation 100 has the following Windows services

BPC SendGovernor which manages Microsoft Analysis Service locks to ensure consistent performance

and avoid deadlocks

BPC ServiceManager which manages the System Landscape Directory (SLD) service logging service

and global caches

BPC CTS ServiceManager which listens and handles CTS import requests from the CTS+ transport

management system

Since these services should be able to access to the FileShare server an Admin account is assigned

automatically to the service during the installation of the Planning and Consolidation server program

Even though an Admin account has been assigned to the server correctly the services may fail to start

with the error message

Could not start the BPC SendGovernor service

The reason for this is that the Admin account is not registered as a service

When installing a service to run under a domain user account the account must have the right to

logon as a service on the local machine This logon right strictly applies only to the local computer

and must be granted in the Local Security Policy

To edit the Local Security Policy of the computer you want to define the logon as a service

permission perform the following actions

1 Start the Local Security Settings Microsoft Management Console (MMC) snap-in

2 Expand Local Policies and then click User Rights Assignment

3 In the right-hand pane right-click Log on as a service and then click Security

4 Add the user to the policy and click OK

5 Close the Local Security Settings MMC snap-in

For more details see How to Troubleshoot Service Startup Permissions http

supportmicrosoftcomkb259733

FeaturesDuring the installation enter user IDs and passwords for the following user types

System Admin ID

This ID is read-only and is the same as the installation user ID that is the system displays the ID

on the installation screen but you cannot modify it This ID allows access to code that provides

2 Installing Planning and Consolidation Servers

25 Service-level Accounts

2012-06-13 CUSTOMER 1554

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 readwrite 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

26 Standard and Advanced Settings

The following tables describe the standard and advanced settings for the installation program After

the server is installed you can change these settings using the Server Manager

NOTE

When defining server names the name refers to the NetBIOS name IP address and fully qualified

domain names (FQDN)

Standard Settings

Standard settings are typically used for a single-server environment The following table describes each

setting

Server Option Value Description

SQL Database server name The name of the SQL DB server

OLAP server name The name of the OLAP server

File Share server name The default value is the name of the File Share server that should be the computer name

Local data path Where the data files are saved on the File Share server By default this is CPC_MSData

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

Server Option Value Description

SQL Server Name The name of the SQL DB server Defaults to the local server

2 Installing Planning and Consolidation Servers

26 Standard and Advanced Settings

1654 CUSTOMER 2012-06-13

Server Option Value Description

Instance name The SQL instance name If left blank the default instance is used

Port number The default port number for the SQL Server is 1433

Provider The only available value is SQL

Local path for EnvironmentShell 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 CPC_MSData

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 changesSee the Kerberos authentication settings section in the SAP Library Server Manager Guide on httpservicesapcominstguidesEPM-BPC

100 for the Microsoft Platform

Scheduler Server Name The name of the server used for scheduling usually the application server for example GMPV50072862B If you have multiple application servers select the appropriate one

NOTE

If the primary server stops working you must manually configure your application server database to froward requests to another application server

27 Installing the Prerequisites

271 Installing the Prerequisites ndash Basic Steps

Before installing your Planning and Consolidation server you must install the prerequisite Microsoft

software the operating system IIS SQL server analysis services ADOMDNET and MSXML This

section provides guidance on installing each component For specific versions required see

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 1754

Prerequisites [page 11] and the Product Availability Matrix on the SAP Service Marketplace at http

servicesapcompam Search on Planning and Consolidation

NOTE

To ensure a successful installation you must install the software in the order listed in this

procedure

Check all third-party infrastructure services to ensure that they are functioning and that their

authentication models are documented (stated) since you need to reference this information

during the installation These third-party services include IIS OLAP service SQL services and

Active Directory (AD)

We recommend not installing Microsoft Office on the application server

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

(UMCexe) on the Planning and Consolidation CD in a folder called UMC_100_INSTALLER When

you run the installation package the wizard guides you through the following steps

1 Choose a language for the UMC install wizard to use

2 Check that the prerequisite check status is Succeeded and click Next

3 When you are ready to install the UMC click Next on the welcome screen

4 Click I accept the License Agreement and then Next

5 Choose the destination directory for the UMC installation and click Next

6 Select the languages that you wish to install

7 Select the features that you want to install (POAFHelper dotnet is mandatory for Planning

and Consolidation)

8 On Start Installation click Next to complete the installation

2 Install the required operating system on the single-server computer or on each physical server for

a multiserver configuration See Installing the Operating System [page 19]

3 Install the latest service pack for your operating system To install this service pack go to http

wwwmicrosoftcom

4 From your operating systems media install IIS

5 From your SQL Server media install SQL Server and its required service packs and hot fixes See

Installing SQL Server [page 19]

6 From your SQL Server media install Analysis Services Enterprise Edition and its required service

packs and hot fixes See Installing Analysis Services [page 23]

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

1854 CUSTOMER 2012-06-13

7 On your application server install ADOMDNET The Planning and Consolidation zip file contains

the ADOMDNET installation package in the following locations

For SQL Server 2008 mdash BPC SetupServerSQLSERVER2008_ASADOMD10_x64msi

For SQL Server 2012 mdash BPC SetupServerSQLSERVER2012_ASADOMD11_x64msi

8 On your application server install MSXML 40 Service Pack 2 or later

The MSXML 40 SP2 installation package is contained in the Planning and Consolidation zip file at

the following location BPC SetupServermsxmlmsi

9 On your application server install Microsoft Visual C++ 2005 Runtime Libraries SP1

The Microsoft Visual C++ 2005 SP1 installation package is contained in the Planning and

Consolidation zip file at the following location BPC SetupServervcredist_x64exe

NOTE

The version of vcredist_x64exe in BPC SetupServer has been updated to 8061000 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 httpwwwmicrosoftcomdownloadsen

detailsaspxFamilyID=C06B8369-60DD-4B64-A44B-84B371EDE16Dampltdisplaylanggt=en

272 Installing the Operating System

Before installing the operating system make sure that you configure your server for NTFS

For a list of languages that are supported see the Product Availability Matrix on the SAP Service

Marketplace at httpservicesapcompam Search on Planning and Consolidation

Planning and Consolidation can support all servers with an operating system in any language

NOTE

Currently Planning and Consolidation does not support an operating system in bi-directional

languages such as Hebrew

ProcedureIf you are installing IIS 70 or 75 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

273 Installing the SQL Server

PrerequisitesDuring the installation procedure you have the opportunity to specify the location of the

EnvironmentShell database file Check that it is possible to access EnvironmentShell from the location

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 1954

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 CEnvironmentShelldb10) 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 a 2008 2008 R2 and 2012 SQL Server

SQL Server Considerations

We recommend installing all required components in sequence For example install the Operating

System (Windows Server) then enable IIS and ASPNET and install any Windows Server service

packs

IIS and NET Framework 40 are required on your application server

NOTE

If you encounter a 500 HTTP Error when trying to connect to the Planning and Consolidation

Web Client refer to Microsoft Support articles 2520479 and 2468871 for assistance

To reinforce security we recommend that you install the SQL server and SSAS components to a

nondefault instance of SQL Server

General Installation Steps

1 Launch the SQL Server Setup program entering a product key if necessary and accepting the license

terms

2 Choose Install to install the SQL support files

3 In Feature Selections select instance and shared features as indicated in the SQL Server Component

Options section below then choose Next

4 Review disc space requirements then choose Next

5 In Server Configuration Perform the following actions

1 In the Service Accounts tab enter a Planning and Consolidation sysadmin account for the SQL

Server Database Engine and the SQL Server Analysis services This is required so that the Planning

and Consolidation sysadmin can create and process the Planning and Consolidation database

because the Microsoft SQL server tries to back up or restore database with the privileged

account This account is also required during Backup Environment and Restore Environment in the

Server Manager

For a single-server environment this account is also required if the backup file is located in a

different domain machine because SQL tries to access the folders and files with this account

For the a multiple-server environment SQL server retrieves the information of backup file

from the application server and the account requires the folder access privilege for the

application server

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2054 CUSTOMER 2012-06-13

To ensure that you have the complete access privileges we recommend the Planning and

Consolidation sysadmin for this service account

2 In the Collation tab set the collation settings to SQL_Latin1_General_CP1_CI_AS

Choose Next

6 Set Database Engine Configuration options then choose Next

We recommend you choose Mixed mode (Windows authentication and SQL authentication) This allows you

to use a restrictive SQL ID that works with the drill-through feature If you must restrict SQL

authentication for security reasons you can define a specific parameter in your drill-through

queries If you do not need drill-through support or use it without leveraging SQL authentication

you can install the SQL Server in Windows-only mode

7 Accept the Analysis Services Configuration default options and the remaining default options of the

installation program

8 Choose Install to begin the installation with the options you have set

SQL Server Component 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

Server Component What to Install

SQL Server Database Engine Services

SSAS Server Analysis Services

Application Server The following Shared Features Client Tools Connectivity Integration Services Client Tools SDK

Custom Settings for the SQL Server

As of version 100 Planning and Consolidation supports the following new features for SQL Server 2008

SQL Server 2008 R2 and SQL Server 2012

Process Dimension

It is now possible to process a dimension with multiple selections At processing time the process

dimension module makes changed or added information for each dimension and process for all selected

dimensions and cubes in parallel

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 2154

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

NOTE

Setting 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 tblFactWBltappgt table

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 Microsoftreg SQL Servertrade

20052008 which you can download from wwwmicrosoftcom (search on ldquoTable Partitioningrdquo to find

all relevant articles)

After Installing SQL Server 2008 SQL Server 2008 R2 and SQL Server 2012

From SQL Server Configuration Manager confirm that the SQL Server Browser service is

running The browser service is required for Planning and Consolidation

From SQL Server Configuration Manager do the following

1 Select Protocols for ltInstanceNamegt then double-click TCPIP from the right side of the window

2 When prompted for the TCPIP Properties select IP Addresses You see two IPs that indicate the

localhost and external network interface machine

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2254 CUSTOMER 2012-06-13

3 If you want to use IP1 which indicates Server IP set Enabled to Yes and specify the TCP Port as

desired

4 Delete 0 from TCP Dynamic Ports Set IPAll - TCP Ports as desired (for example 1533)

RECOMMENDATION

We do not recommend using dynamic ports

In an SQL server the default instance has a listener which listens on a fixed port (TCP

port 1433) However for the named instance the port on which the SQL server listens is

random and dynamically selected when the named instance of the SQL server starts This

recommendation prevents any conflict problems

From the SQL Server Configuration Manager specify the client protocol options for the application

server

1 Select Client Protocols from the SQL Native Client Configuration folder

2 From the right side of the window double-click TCPIP The TCPIP 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

NOTE

We 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

274 Installing Analysis Services

ProcedureAfter you install SQL Server and its required service packs and hotfixes you must install SQL Server

Analysis Services and its required service packs and hotfixes

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 2354

NOTE

If you have migrated your Analysis Services repository to the SQL Server back up the database

that contains the repository before installing this release

To install Analysis Services for SQL Server 2008 SQL Server 2008 R2 or SQL Server 2012 follow the steps

and guidelines in httptechnetmicrosoftcomen-uslibraryms143219aspx

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 httpwwwmicrosoftcomdownloads

detailsaspxFamilyID=3be0488d-e7aa-4078-a050- ae39912d2e43ampdisplaylang=en

275 Installing the Anti-Cross Site Scripting Library

Procedure

Before installing Planning and Consolidation servers you must download the Anti-Cross Site Scripting

Library (version 42 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 AntiXSSLibraryDLL from the Microsoft Web

site at httpwwwmicrosoftcomdownloadendetailsaspxid=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 AntiXssLibrarydll

28 Installing on a Single Server

When you install all Planning and Consolidation server components on a single server you should

consider the following issues

Make sure the server has a minimum of 800 MB of hard disk space

Additional environment installations require more free disk space which is a minimum of two

times the uncompressed size of the environment files

When you install Planning and Consolidation on a single-server the system adds the following server

components

SQL Server

SQL Server Analysis Services (SSAS)

Application Server

FileShare server

Procedure

To install Planning and Consolidation on a single server take the following steps

1 Exit all Windows programs

2 Installing Planning and Consolidation Servers

28 Installing on a Single Server

2454 CUSTOMER 2012-06-13

2 Log on to the server with a local server user ID or domain user ID For more information see Logging

on to servers [page 14]

3 Make sure all prerequisite software is installed on the server For more information see Installing

the Prerequisites [page 17]

4 Obtain SAP Planning and Consolidation from the Downloads SAP Installations amp Upgrades area of

SAP Service Marketplace then extract the files and run StartUpexe

5 From the Server Install screen select Install the Planning and Consolidation server

6 From the Welcome screen choose Next

7 From the License Agreement page choose I accept the terms of the license agreement then choose Next

8 From the Installation Method page accept the default Single machine enter a system ID for the system

landscape directory (SLD) and choose Next

NOTE

Entering a system ID of the SLD is only required if you have a SAP Solution Manager license

If you do not have a SAP Solution Manager license you can leave this field empty

9 From the Authentication Method page choose the desired authentication method and choose Next

10 If you have chosen SAP BusinessObjects User Management System in the previous screen on the CMS

Authentication page enter the information required to log on to CMS as an administrator

The following information is required

Field Description

System name CMS system name (server nameport number) for example CMSServer6400

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

11 After entering the CMS administrator authentication details choose Next

12 From the Service type accounts page enter service-level account user IDs and passwords See Service-

Level Accounts [page 15]

13 After defining the IDs and passwords choose Next

14 From the Server Information page (see Standard and Advanced Settings [page 16]) do one of the following

Review the standard settings and choose Next

To set advanced settings choose the Advanced Settings button Enter the desired information

and choose Next

2 Installing Planning and Consolidation Servers

28 Installing on a Single Server

2012-06-13 CUSTOMER 2554

15 Specify the location and name of AntiXssLibrarydll See Installing the Anti-Cross Site Scripting Library [page

24]

Choose Next

16 Select destination folders for Programs and Data The Data files include Webfolders and FileDB

(published reports) and should be installed on a separate drive in a production environment This

recommendation reduces the hard disk IO time and helps to speed up SQL commands

Accept the defaults or make your selections then choose Next

17 Select the default values for the Web client The values are used to determine the default language

and region for the Web client when you connect to it You can change the values in the Planning

and Consolidation Server Manager

18 The installation process takes a few moments When it is complete choose Exit

19 A prompt is displayed to restart your computer Select OK to restart

20 Perform the steps in After Installing Planning and Consolidation Servers [page 27]

29 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 24]) with the following

exceptions

On the Installation Method page do not accept the default instead choose Network Load Balancing

environment With this option there is an additional choice to Include sample environment (required on only

one of the application servers) This is because when you install the application server it connects to the

database server and creates the sample environment (EnvironmentShell) Installing the sample

environment is required on only one application server and you may choose which one

In the Virtual Name field enter the virtual IP address virtual name in the default properties

2 Installing Planning and Consolidation Servers

29 Installing the Server in a Multiserver Configuration

2654 CUSTOMER 2012-06-13

3 After Installing Planning and Consolidation Servers

31 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 28]

2 Configure the Planning and Consolidation NET and application server to ensure that it and its

related services function properly and reliably For more information see Configuring the Planning and

Consolidation NET Application Server [page 29]

3 Optional configuration steps [page 30]

1 To ensure proper functioning of the Management Console create an SQL user and modify

the System DSN and IIS to reflect those user credentials See Enabling Management Console [page

30]

2 Configure custom ODBC logging for the default Web site For details of how to configure

custom logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web

Site [page 31]

3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC

Data Source [page 32]

4 Modify the default access rights to the Management Console By default users in Active

Directory can access the Management Console with whatever rights they have been granted

on the server For information about removing default access and creating a group that can

access the console see Removing Default Access to the Console [page 32]

5 Add authorized users or groups to the group that can access the Management Console We

recommend that you only grant Management Console access to system administrators

Planning and Consolidation users should not have any access For more information see

Management Console Access Control [page 33]

6 Configure the use of client certificates for authentication See Using Client Certificates [page

34]

4 Take the following steps to set up security

If you are defining security and application structure continue with step 5

3 After Installing Planning and Consolidation Servers

31 Post-Installation Steps

2012-06-13 CUSTOMER 2754

If you want to designate someone other than the system administrator to manage security

and application structure log on to EnvironmentShell designate a user as a Primary

Administrator

This user must have Administration ‒ Environment and Security ‒ Define User task rights

so that he or she can add and delete environments and define user security

The Primary Administrator can continue with the next step (5)

5 From the machine on which you administer Planning and Consolidation install the

Administration client See Installing the Administration Client [page 37]

6 Start Planning and Consolidation Administration from the launch page

7 Select Connection Wizard and log on to EnvironmentShell

8 Create a new environment using EnvironmentShell as the source

9 Log on to the newly created environment and set up users teams and task profiles (You must

set up task profiles since there is no access to Planning and Consolidation tasks)

10 Set up your data access profiles and add users (or teams) to one or more data access profiles (You

must complete this step since there is no access to dimensions or members)

NOTE

To allow users to request and query large amounts of data you can edit the metabasexml file located

at CWindowssystem32inetsrv Set the following parameters to the stated values

ASPBUFFERINGLIMIT = 10485760

MAXREQUESTENTITYALLOWED = 10485760

32 Connecting to Solution Manager Diagnostics

NOTE

You only need to perform the steps in this section if you have a SAP Solution Manager licence

The diagnostics functions in SAP Solution Manager allow identification analysis and resolution of

problems This procedure provides the steps required to connect Planning and Consolidation to

Solution Manager Diagnostics

Procedure

1 Install the Diagnostics Agent according to SAP Note 1234387 on all servers where application servers

are installed

NOTE

Installation files for Diagnostics Agent are available on Service Marketplace by navigating to

Support Packages and Patches mdash Entry by Application Group SAP Technology Components SAP

SOLUTION MANAGER SAP SOLUTION MANAGER 70 EHP 1 Entry by Component Agents

for managed systems DIAGNOSTICS AGENT 711

3 After Installing Planning and Consolidation Servers

32 Connecting to Solution Manager Diagnostics

2854 CUSTOMER 2012-06-13

Download the installation file based on the 64-bit Windows Server system landscape

2 To access the DBA Cockpit you must create a user account with sufficient rights on all Windows

Servers where Microsoft SQL Server is installed Do the following

1 Start Computer Management then select Action New User

2 Create a new user

3 Right-click on the user then choose Properties On the Member Of tab select Add

4 Add the group SQLServerltReleasegtSQLAgentUser$ltDomain or hostnamegt$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 httpsservicesapcom~sapidb011000358700000074392009E and follow

the chapters that apply to Planning and Consolidation

33 Configuring the Planning and Consolidation NET Application Servers

Procedure

Modifying machineconfig Files

To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock

occurrences that would cause the application server to ldquosleeprdquo and not process anymore you can

modify the machineconfig file which resides in the WINDOWSMicrosoftNETFramework64

v4030319Config directory

1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to

specify whether to automatically configure settings to achieve optimal performance based on the

machine configuration You can set this attribute to True or False

For more information see httpmsdnmicrosoftcomen-uslibrary7w2sway1aspx

2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the

Planning and Consolidation application) or Machineconfig (for all applications including

Planning and Consolidation) to ensure the validationKey and decryptionKey keys have the same

value on all application servers This way when the authentication cookie is checked the

authentication ticket used on one server can still be valid on another server

For more information and sample Visual Basic code for generating random key values see http

msdnmicrosoftcomen-uslibraryms998288aspx

3 After Installing Planning and Consolidation Servers

33 Configuring the Planning and Consolidation NET Application Servers

2012-06-13 CUSTOMER 2954

paght000007_webfarmdeploymentconsiderations and httpmsdnmicrosoftcomen-us

libraryms998310aspx

34 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 30]

2 Configure custom ODBC logging for the default Web site For details of how to configure custom

logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page

31]

3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC Data

Source [page 32]

4 Modify the default access rights to the Management Console By default users in Active Directory

can access the Management Console with whatever rights they have been granted on the server

For information about removing default access and creating a group that can access the console

see Removing Default Access to the Console [page 32]

5 Add authorized users or groups to the group that can access the Management Console We

recommend that you only grant Management Console access to system administrators Planning

and Consolidation users should not have any access For more information see Management Console

Access Control [page 33]

6 Configure the use of client certificates for authentication See Using Client Certificates [page 34]

341 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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3054 CUSTOMER 2012-06-13

NOTE

Without these updates the Management Console does work but some functionality (specifically

User Activity and Service Status) does not work as expected

Should you need to uninstall Planning and Consolidation we recommend that you reset the

Active Log Format field in IIS to W3C Extended Log File Format

342 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 ApplicationHostconfig set the property customLogPluginClsid to the value FF16065B-

DE82-11CF-BC0A-00AA006111E0 Set the logFormat to Custom You can find this in the ltlogFilegt

node in ApplicationHostconfig as shown here

ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0

logFormat=Custom gt

Use the following AppCmds to configure IIS to use ODBC logging for the default Web site

appcmd site set sitenameDefault Web Site

logFilecustomLogPluginClsidFF16065B-DE82-11CF-BC0A-00AA006111E0

appcmd site set sitenameDefault Web Site logFilelogFormatCustom

Configuring ODBC Logging Parameters in ApplicationHostconfig

Configure ApplicationHostconfig to contain the database table information as set up in the Microsoft

Support article specified in the Prerequisites section Configure these settings in the ltodbcLogginggt

node under ltsystemwebServergt

EXAMPLE

ltlocation path=Default Web Sitegt

ltsystemwebServergt

ltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog

userName=Username password=mypassword gt

ltsystemwebServergt

ltlocationgt

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3154

Use the following AppCmds to configure these attributes for the default Web site

appcmd set config Default Web Site sectionodbcLogging

dataSourceBPC_ManagementDSN commitappHost

appcmd set config Default Web Site sectionodbcLogging tableNameBPCLog

commitappHost

appcmd set config Default Web Site sectionodbcLogging userNameUsername

commitappHost

appcmd set config Default Web Site sectionodbcLogging passwordmypassword

commitappHost

NOTE

You cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must

use the SQL Server ODBC driver For more information see the Microsoft Knowledge Base article

931202 The requirements for using the ODBC logging feature in IIS

343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2

ProcedureThis procedure describes how to set up an ODBC data source for the Management Console in Windows

Server 2008 or Windows Server 2008 R2

Proceed as follows

1 Open ODBC Connection Manager

2 On the System DSN tab page add a new DSN

Choose Add

Choose SQL Server as the driver

Choose Finish

3 In the Name and Description fields enter BPC_ManagementDSN

4 In the Server field enter the name of your SQL Server Choose Next

5 Leave the default settings and choose Next

6 Choose the Change the default database to field and enter AppServer Choose Next

7 Leave default settings and choose Next

8 Choose OK

344 Removing Default Access to the Console

NOTE

If you have chosen SAP BusinessObjects User Management System in the installation screen you

do not need to remove or configure access because the Management Console service always runs

with the System Admin ID account which is a member of the Administrators group

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3254 CUSTOMER 2012-06-13

ProcedureTo remove default access to the Management Console and create a group that does have access to the

console use the procedure described below

NOTE

Create your Management Console administrative group either on the server that hosts the

Management Console or in the Active Directory

1 In the context menu of the servers My Computer icon choose Manage

2 In the Computer Management dialog box choose Local Users and Groups Groups

NOTE

Alternatively you can perform analogous steps in Active Directory

3 In the 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

NOTE

This step is a necessary precursor to the completion of this procedure

10 In the Security dialog box click Copy to ensure that the System group retains its privileges

11 Remove access to the Management Console from all groups that should not have it

12 Choose Authentication in the center pane then disable Windows authentication

ResultUsers who have not been granted access to the Management Console can still open the Management

Console Web page but it contains no data or menu options This does not affect the access that a user

would otherwise have to Planning and Consolidation

345 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 32] Their rights in

Active Directory determine what they can access in the Console

By default any member of the Administrators Active Directory group on the application server or

domain has full access to all of the features of the Console except the Planning and Consolidation

logging area Access to Planning and Consolidation logging is controlled within the Planning and

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3354

Consolidation Administration Client task security The user must be granted View system logs task

privileges For more information see the SAP Library Planning and Consolidation Administrators Guide in

httpservicesapcominstguidesepm-bpc 100 version for the Microsoft platform

Your IT policy determines whether you grant access by group or user You may wish to create several

levels of Console users (read-only users for example) in your environment

To grant or limit access to users or groups you can add or remove the following privileges from the

areas described in this table

Privilege Rights Management Area

Task Manager and Kill Process Administrators group on application server or domain

Performance Monitor Counters Administrators group on application server or domain Power Users group on application server or domain Performance Monitor Users group on application server

Microsoft Analysis Services performance monitoring

Administrators group on application server or domain

Microsoft SQL Server Monitoring (performance counters and statistics)

Administrators group on application server or domain

346 Using Client Certificates

To enable the use of client certificates in Planning and Consolidation you must follow several manual

steps

NOTE

Planning 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 httptechnetmicrosoftcomen-us

librarycc753810aspx

For more information about configuring the client certificate mapping authentication see http

technetmicrosoftcomen-uslibrarycc732996(WS10)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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3454 CUSTOMER 2012-06-13

This option allows you to use a client certificate or username and password (Basic

authentication) to connect to Planning and Consolidation

2 Enable anonymous authentication

1 In the IIS Manager expand the node of the Planning and Consolidation web site

2 Select the ManagementConsole directory (ltWebsitegtManagementConsole) to open the

ManagementConsole home page

3 Double-click Authentication and enable Anonymous Authentication

4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way

as in step 3

5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the same

way as in step 3

3 Change the web configuration settings

1 Open the ltPC_MSgtWebsrvrWebBPCwebconfig file

2 Find the text clientCredentialType=Windows

3 Change value of clientCredentialType to None (clientCredentialType=None)

4 Open the PC_MSWebsrvrWebPOASBCwebconfig file Repeat steps 2 and 3

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3554

This page is left blank for documents that are printed on both sides

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

The installation of the Planning and Consolidation Administration Client allows administrators to

build and maintain Planning and Consolidation environments and models and administer security

All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions

add-in for Microsoft Office for more information see the SAP BusinessObjects EPM solutions add-in for

Microsoft Office help

NOTE

You must update the Administration Client to the same version as the server

If your PC is on a different domain than your server you must set the Internet Explorer

Security Zone value of the Planning and Consolidation client to prompt for user name and

password Otherwise the Planning and Consolidation Start Page does not display

41 Installing the Administration Client

Prerequisites

NOTE

For a definitive list of system requirements see the Product Availability Matrix on SAP Service

Marketplace at httpservicesapcompam Search on Planning and Consolidation

The following list describes the minimum software requirements

Microsoft Internet Explorer 70 or 80

Microsoft Office 2007 or 2010

NET Framework 20 or higher (install any required NET Framework Hotfixes by referring to

httpsupportmicrosoftcomkb)

Pentium IV (1 GHz CPU)

512 MB RAM

100 MB of free hard disk space in the My Documents folder

20 MB of free hard disk space for the installed Administration files

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

41 Installing the Administration Client

2012-06-13 CUSTOMER 3754

NOTE

We recommend that you install all of the latest Microsoft Windows hotfixes prior to installing

the Administration client For information about which hotfixes to install see http

updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us

ProcedureThe following procedure describes how to install the Administration Client on to an administratorrsquos

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 AddRemove Programs in the Windows Control Panel

3 Point your browser to the Planning and Consolidation Web at httpltPC_serverportgtsap

bpcweb

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

42 Installing the EPM Add-in

The Planning and Consolidation installation media does not contain the EPM addin setup program

You must download the most recent version of the full setup (EPM Add-inexe) from the Service

Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPC

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

43 Using the Client Auto Update Program

If Planning and Consolidation version 100 or later is installed you can use the Client Auto Update

program to set up the server so that it determines if an upgrade for a connecting Administration client

is necessary

The following describes the use of the auto update program for the Administration Client and the EPM

add-in

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

42 Installing the EPM Add-in

3854 CUSTOMER 2012-06-13

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 37]

To use the Client Auto Update program for the Administration Client proceed as follows

1 From the Server Manager select Options Client Options

2 Select Admin Update

3 If users without administrator rights on their machines use the auto update enter an administrator

ID and password in the Admin ID and Admin password fields respectively The Admin ID should be a

member of the local administrators group on all the computers running the auto update This

setting is not needed if all users have administrator rights on their machines

4 Select Update

For the EPM Add-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 Optionshellip 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 Market Place (SMP) at httpservicesapcom

All support packages and patches are available from the SMP as a zip file

EPMEXCLCLNTltSPLgtzip is for a support package

EPMEXCLCLNTltSPLgtPltPLgtzip 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 ltSP versiongtmsp

EPM Addin Support Package ltSP versiongtxml

For a patch these files are

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

2012-06-13 CUSTOMER 3954

EPM Addin Patch ltpatch numbergtmsp

EPM Addin Patch ltpatch numbergtxml

2 Unzip the zip file and extract the two files to the application server folder (WebsrvrWebBPC

Installation)

3 From the Server Manager select Options Client Options

The system lists the available packages Select the package that you want to use for the autoupdate

You can set a different update policy for each package listed

EXAMPLE

The following table illustrates some possible situations assuming that you have installed the

first full version (V1)

Available maintenance packages

V2-user updateV3-force updateV4-force updateV5-user update

V5-user update V5-user updateV6-auto updateV7-force update

Minimum Required Version

V4 V4 V7

Notification A prompt tells the user to install maintenance package V4 using the Forced Update behavior

If User Update is enabled the prompt informs the user that maintenance package V5 is available

A prompt tells the user to install maintenance package V7 using the Forced Update behavior

New Version V4 V4 or V5 V7

If you change the update policy for any package click Update to complete the change

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

4054 CUSTOMER 2012-06-13

5 Connection Issues

You may experience connection problems with ports the proxy server or programs and settings that

interact with these components If you have any issues related to connection review the following

recommendations and troubleshooting tips

51 Checking for Open Ports

You must ensure that all required ports are open for inboundoutbound 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 431181836 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

NOTE

You can use the following site to scan for the normal ports It allows you to manually enter a port

number to test

httpwwwmyserverorgportsniffasp

You can change the name of a port

52 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 Explorer Tools Internet Options Connections LAN Settings ) or at the server level

Enabling content filtering on the proxy server or firewall may cause connection problems

If external users are having trouble connecting to the server make sure the proxy server connects

using a fully qualified domain name Fully qualified domain names typically resolve both internal

and external IP addresses

Each secure Planning and Consolidation server name must be identified on the proxy server

Proxy servers may or may not require authentication which could conflict with Planning and

Consolidation authentication Do not use authentication on the proxy server The system

5 Connection Issues

51 Checking for Open Ports

2012-06-13 CUSTOMER 4154

synchronizes the user name and password on the remote server with the local user name and

password

NOTE

For more information about setting up an ISA proxy server contact SAP Support to request a

copy of Setting up ISA Proxy Server White Paper

Internet Explorer Settings 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

5 Connection Issues

52 Proxy Server and Firewall Issues

4254 CUSTOMER 2012-06-13

6 Installing Planning and Consolidation with Two Active Directory Domains

To set up a Planning and Consolidation 10 application server in a hosted environment and use your

own domain users follow this procedure In general you install Planning and Consolidation on the

host domain use the host domain account and assign it to the Planning and Consolidation users

SysAdmin Admin and Users Then you accept one way trust (the host domain trusts your domain)

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

6 Installing Planning and Consolidation with Two Active Directory Domains

2012-06-13 CUSTOMER 4354

This page is left blank for documents that are printed on both sides

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

This section describes best practices and instructions for installing Planning and Consolidation in a

Terminal Services or Citrix Server deployment

71 Terminal Services Home Directories

We recommend using Terminal Server home directories rather than using the userrsquos 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

72 System Requirements

The Citrix server should be one of the following systems

XenApp 5 Enterprise

XenApp 5 Platinum

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 37])

73 Installing Planning and Consolidation

Prerequisites

The server installation files have been downloaded from SAP Service Marketplace and installed

Procedure

The following steps outline how to install the Planning and Consolidation clients in a Terminal Services

(TS) or Citrix Server deployment

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

71 Terminal Services Home Directories

2012-06-13 CUSTOMER 4554

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 userinstall

4 Open a browser and connect to the URL httpltPC_serverportgtsapbpcweb

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 userexecute 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 Iexploreexe http(s)

ltServerNamegt-NetBIOS or FQDNsapbpcweb

To publish Planning and Consolidation Administration CProgram FilesPC_MS

BPCAdminMainexe

74 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 userrsquos desktop) must be moved to the All UsersDesktop folder

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

74 Creating a Shortcut to the Launch Page

4654 CUSTOMER 2012-06-13

8 Installing SSIS Custom Tasks

This section provides background information and instructions for installing SQL Server Integration

Services (SSIS) for SQL Server 2008 and SQL Server 2012

The Planning and Consolidation Data Manager component supports and uses SSIS Since SQL Server

2008 and SQL Server 2012 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

81 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 Filelistxml 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

OSoftSetupexe ‒ 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 or OSoftSSIS2012_Client on the client machine followed by the SQL Server

version If you want to use SQL 2008 Tasks under the SQL 2012 environment you must install

OSoftSSIS2008_Client on the application server For detailed information see SAP Note 1707410

You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package by extracting

OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPC

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 or

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4754

OSoftSSIS2012_Client for creating a COM+ application For more information see Before You Modify

the SSIS Packages [page 50] and Setup of a COM+ Application on the Application Server [page 51]

Bin folder

This folder contains the following components

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCCachedll Planning and Consolidation Cache file

BPCDataFlowPackagedll or BPCDataFlowPackage2012dll

BPCDMdll

BPCDMTaskMaindll COM+ component

BPCFilePreviewdll

BPCGacUtil_20exe System File

BPCGacUtil_40exe System File

BPCImpersonatordll Planning and Consolidation Impersonator

BPCLogicdll

BPCScriptdll

BPCServerZipdll

BPCServiceResdll

BPCTransferMembersdll

BPCWriteBackdll

InteropDTSdll

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

4854 CUSTOMER 2012-06-13

Name Remark

OSoftAdminServerdll

OSoftAuditdll

OSoftComLibServerdll

OSoftCommonResQrydll

OSoftConfigurationdll

OSoftCustomXMLSvrdll

OSoftDatabaseADMINdll

OSoftDatabaseSYSADMINdll

OSoftDatabaseSYSADMINDMdll

OSoftDatabaseUSERdll

OSoftDMDTSXExecutedll or OSoftDMDTSXExecute2012dll

OSoftDMTaskFormdll

OSoftDMTaskMaindll

OSoftDMToolsdll

OSoftFileManagedll

OSoftLoggingdll

OSoftLogWriterdll

OSoftMetaDatadll

OSoftSQEdll

OSoftSystemConfigdll

OutlookSoftconfig Configuration file to connect DB server

XceedCompressiondll XceedZip file

XceedCompressionFormatsdll XceedZip file

XceedFileSystemdll XceedZip file

XceedZipdll XceedZip file

Config folder

This folder has FileListxml 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 FileListxml 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

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4954

OSoftSetupexe

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

NOTE

If you installed the OSoftSSIS2008_Client or OSoftSSIS2012_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

Resources Folder

This folder contains the BPCServicesdll and BPCServiceUIdll files which contain resource text

Only English resources are included for the SSIS custom tasks

82 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

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008 and 2012 respectively

8 Installing SSIS Custom Tasks

82 Before You Modify the SSIS Packages

5054 CUSTOMER 2012-06-13

Name Remark

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012 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

lthellipgtOSoftSSIS2008_Clientbin or lthellipgtOSoftSSIS2012_Clientbin

On the Planning and Consolidation application server

ltdrivegtWebsrvrbin

2 Paste these files into the folder 100DTSTasks for SQL Server 2008 or into 110DTSTasks for

SQL Server 2012 For example if you install your SQL 2008 server or R2 on CProgram Files

Microsoft SQL Server paste all files into the CProgram Files (x86)Microsoft SQL Server

100DTSTasks folder

In Integration Services set the property Run64BitRunTime to True

83 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 or OSoftSSIS2012_Client on the

application server

8 Installing SSIS Custom Tasks

83 Setup of a COM+ Application on the Application Server

2012-06-13 CUSTOMER 5154

Typographic Conventions

Example Description

ltgt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example Enter your ltUser Namegt

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 httpwwwsapcom

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

5254 CUSTOMER 2012-06-13

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

  • SAP BusinessObjects Planning and Consolidation 100
    • Table of Contents
    • 1 Introduction
      • 11 SAP Notes for the Installation
      • 12 Naming Conventions
        • 2 Installing Planning and Consolidation Servers
          • 21 Basic Steps
          • 22 Prerequisites
          • 23 Before Starting the Planning and Consolidation Server Installation
          • 24 Logging on to Servers
          • 25 Service-level Accounts
          • 26 Standard and Advanced Settings
          • 27 Installing the Prerequisites
            • 271 Installing the Prerequisites ndash Basic Steps
            • 272 Installing the Operating System
            • 273 Installing the SQL Server
            • 274 Installing Analysis Services
            • 275 Installing the Anti-Cross Site Scripting Library
              • 28 Installing on a Single Server
              • 29 Installing the Server in a Multiserver Configuration
                • 3 After Installing Planning and Consolidation Servers
                  • 31 Post-Installation Steps
                  • 32 Connecting to Solution Manager Diagnostics
                  • 33 Configuring the Planning and Consolidation NET Application Servers
                  • 34 Post-Installation Optional Configuration Steps
                    • 341 Enabling the Management Console
                    • 342 Setting Up ODBC Logging in IIS for the Default Web Site
                    • 343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2
                    • 344 Removing Default Access to the Console
                    • 345 Management Console Access Control
                    • 346 Using Client Certificates
                        • 4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office
                          • 41 Installing the Administration Client
                          • 42 Installing the EPM Add-in
                          • 43 Using the Client Auto Update Program
                            • 5 Connection Issues
                              • 51 Checking for Open Ports
                              • 52 Proxy Server and Firewall Issues
                                • 6 Installing Planning and Consolidation with Two Active Directory Domains
                                • 7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
                                  • 71 Terminal Services Home Directories
                                  • 72 System Requirements
                                  • 73 Installing Planning and Consolidation
                                  • 74 Creating a Shortcut to the Launch Page
                                    • 8 Installing SSIS Custom Tasks
                                      • 81 Composition of SSIS Custom Task Installation
                                      • 82 Before You Modify the SSIS Packages
                                      • 83 Setup of a COM+ Application on the Application Server
                                          • Copyright and trademarks
Page 14: Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

In a multiserver environment the installing ID must be a domain user ID We recommend that

you do not log on to the servers using a local server user ID even if the user ID is a member of the

Administrator group on the server This way you have the proper authority to install software and

to modify the Component Services See Logging On to Servers [page 14]

You must determine the IP addresses or server names for all servers before installing Planning and

Consolidation We recommend that you use static IP addresses

IIS must be enabled

If the application server is not able to copy files to the database server during the installation because

of port access reasons (DMZ WORKGROUP or nontrusted domain authentication failures) do

the following

1 Copy the EnvironmentShell database file ServerEnvironmentShelldb10 from the

Planning and Consolidation installation program to any folder on the SQL server (for example

cEnvironmentShelldb10)

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 cEnvironmentShelldb10)

Install the Anti-Cross Site Scripting Library which provides protection to Web-based applications

against Cross-Site Scripting (XSS) attacks See Installing the Anti-Cross Site Scripting Library [page 24]

24 Logging on to Servers

When installing in a multiserver environment you must use a domain user ID to log on to all

components

A local server user ID is a member of the Administrator group on the server A domain user ID is a

member of the Administrator group of a domain to which the server belongs or a member of the

Administrator group on the local server

Errors may display during the installation program and in the diagnostic program if the installing user

is not assigned to the Administrator group directly but is assigned to a group with Administrator rights

You can ignore these messages

NOTE

If you change the password used to install Planning and Consolidation you must change the

password for the applicable Planning and Consolidation service To do this go to Server Manager

on the application server and select Server Reset Logon Credentials For more information see

the SAP Planning and Consolidation Operations Guide in httpservicesapcominstguidesepm-bpc

100 for the Microsoft Platform SBOP Plan amp Consol 100 MS Administrators Guide

2 Installing Planning and Consolidation Servers

24 Logging on to Servers

1454 CUSTOMER 2012-06-13

25 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

PrerequisitesPlanning and Consolidation 100 has the following Windows services

BPC SendGovernor which manages Microsoft Analysis Service locks to ensure consistent performance

and avoid deadlocks

BPC ServiceManager which manages the System Landscape Directory (SLD) service logging service

and global caches

BPC CTS ServiceManager which listens and handles CTS import requests from the CTS+ transport

management system

Since these services should be able to access to the FileShare server an Admin account is assigned

automatically to the service during the installation of the Planning and Consolidation server program

Even though an Admin account has been assigned to the server correctly the services may fail to start

with the error message

Could not start the BPC SendGovernor service

The reason for this is that the Admin account is not registered as a service

When installing a service to run under a domain user account the account must have the right to

logon as a service on the local machine This logon right strictly applies only to the local computer

and must be granted in the Local Security Policy

To edit the Local Security Policy of the computer you want to define the logon as a service

permission perform the following actions

1 Start the Local Security Settings Microsoft Management Console (MMC) snap-in

2 Expand Local Policies and then click User Rights Assignment

3 In the right-hand pane right-click Log on as a service and then click Security

4 Add the user to the policy and click OK

5 Close the Local Security Settings MMC snap-in

For more details see How to Troubleshoot Service Startup Permissions http

supportmicrosoftcomkb259733

FeaturesDuring the installation enter user IDs and passwords for the following user types

System Admin ID

This ID is read-only and is the same as the installation user ID that is the system displays the ID

on the installation screen but you cannot modify it This ID allows access to code that provides

2 Installing Planning and Consolidation Servers

25 Service-level Accounts

2012-06-13 CUSTOMER 1554

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 readwrite 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

26 Standard and Advanced Settings

The following tables describe the standard and advanced settings for the installation program After

the server is installed you can change these settings using the Server Manager

NOTE

When defining server names the name refers to the NetBIOS name IP address and fully qualified

domain names (FQDN)

Standard Settings

Standard settings are typically used for a single-server environment The following table describes each

setting

Server Option Value Description

SQL Database server name The name of the SQL DB server

OLAP server name The name of the OLAP server

File Share server name The default value is the name of the File Share server that should be the computer name

Local data path Where the data files are saved on the File Share server By default this is CPC_MSData

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

Server Option Value Description

SQL Server Name The name of the SQL DB server Defaults to the local server

2 Installing Planning and Consolidation Servers

26 Standard and Advanced Settings

1654 CUSTOMER 2012-06-13

Server Option Value Description

Instance name The SQL instance name If left blank the default instance is used

Port number The default port number for the SQL Server is 1433

Provider The only available value is SQL

Local path for EnvironmentShell 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 CPC_MSData

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 changesSee the Kerberos authentication settings section in the SAP Library Server Manager Guide on httpservicesapcominstguidesEPM-BPC

100 for the Microsoft Platform

Scheduler Server Name The name of the server used for scheduling usually the application server for example GMPV50072862B If you have multiple application servers select the appropriate one

NOTE

If the primary server stops working you must manually configure your application server database to froward requests to another application server

27 Installing the Prerequisites

271 Installing the Prerequisites ndash Basic Steps

Before installing your Planning and Consolidation server you must install the prerequisite Microsoft

software the operating system IIS SQL server analysis services ADOMDNET and MSXML This

section provides guidance on installing each component For specific versions required see

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 1754

Prerequisites [page 11] and the Product Availability Matrix on the SAP Service Marketplace at http

servicesapcompam Search on Planning and Consolidation

NOTE

To ensure a successful installation you must install the software in the order listed in this

procedure

Check all third-party infrastructure services to ensure that they are functioning and that their

authentication models are documented (stated) since you need to reference this information

during the installation These third-party services include IIS OLAP service SQL services and

Active Directory (AD)

We recommend not installing Microsoft Office on the application server

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

(UMCexe) on the Planning and Consolidation CD in a folder called UMC_100_INSTALLER When

you run the installation package the wizard guides you through the following steps

1 Choose a language for the UMC install wizard to use

2 Check that the prerequisite check status is Succeeded and click Next

3 When you are ready to install the UMC click Next on the welcome screen

4 Click I accept the License Agreement and then Next

5 Choose the destination directory for the UMC installation and click Next

6 Select the languages that you wish to install

7 Select the features that you want to install (POAFHelper dotnet is mandatory for Planning

and Consolidation)

8 On Start Installation click Next to complete the installation

2 Install the required operating system on the single-server computer or on each physical server for

a multiserver configuration See Installing the Operating System [page 19]

3 Install the latest service pack for your operating system To install this service pack go to http

wwwmicrosoftcom

4 From your operating systems media install IIS

5 From your SQL Server media install SQL Server and its required service packs and hot fixes See

Installing SQL Server [page 19]

6 From your SQL Server media install Analysis Services Enterprise Edition and its required service

packs and hot fixes See Installing Analysis Services [page 23]

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

1854 CUSTOMER 2012-06-13

7 On your application server install ADOMDNET The Planning and Consolidation zip file contains

the ADOMDNET installation package in the following locations

For SQL Server 2008 mdash BPC SetupServerSQLSERVER2008_ASADOMD10_x64msi

For SQL Server 2012 mdash BPC SetupServerSQLSERVER2012_ASADOMD11_x64msi

8 On your application server install MSXML 40 Service Pack 2 or later

The MSXML 40 SP2 installation package is contained in the Planning and Consolidation zip file at

the following location BPC SetupServermsxmlmsi

9 On your application server install Microsoft Visual C++ 2005 Runtime Libraries SP1

The Microsoft Visual C++ 2005 SP1 installation package is contained in the Planning and

Consolidation zip file at the following location BPC SetupServervcredist_x64exe

NOTE

The version of vcredist_x64exe in BPC SetupServer has been updated to 8061000 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 httpwwwmicrosoftcomdownloadsen

detailsaspxFamilyID=C06B8369-60DD-4B64-A44B-84B371EDE16Dampltdisplaylanggt=en

272 Installing the Operating System

Before installing the operating system make sure that you configure your server for NTFS

For a list of languages that are supported see the Product Availability Matrix on the SAP Service

Marketplace at httpservicesapcompam Search on Planning and Consolidation

Planning and Consolidation can support all servers with an operating system in any language

NOTE

Currently Planning and Consolidation does not support an operating system in bi-directional

languages such as Hebrew

ProcedureIf you are installing IIS 70 or 75 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

273 Installing the SQL Server

PrerequisitesDuring the installation procedure you have the opportunity to specify the location of the

EnvironmentShell database file Check that it is possible to access EnvironmentShell from the location

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 1954

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 CEnvironmentShelldb10) 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 a 2008 2008 R2 and 2012 SQL Server

SQL Server Considerations

We recommend installing all required components in sequence For example install the Operating

System (Windows Server) then enable IIS and ASPNET and install any Windows Server service

packs

IIS and NET Framework 40 are required on your application server

NOTE

If you encounter a 500 HTTP Error when trying to connect to the Planning and Consolidation

Web Client refer to Microsoft Support articles 2520479 and 2468871 for assistance

To reinforce security we recommend that you install the SQL server and SSAS components to a

nondefault instance of SQL Server

General Installation Steps

1 Launch the SQL Server Setup program entering a product key if necessary and accepting the license

terms

2 Choose Install to install the SQL support files

3 In Feature Selections select instance and shared features as indicated in the SQL Server Component

Options section below then choose Next

4 Review disc space requirements then choose Next

5 In Server Configuration Perform the following actions

1 In the Service Accounts tab enter a Planning and Consolidation sysadmin account for the SQL

Server Database Engine and the SQL Server Analysis services This is required so that the Planning

and Consolidation sysadmin can create and process the Planning and Consolidation database

because the Microsoft SQL server tries to back up or restore database with the privileged

account This account is also required during Backup Environment and Restore Environment in the

Server Manager

For a single-server environment this account is also required if the backup file is located in a

different domain machine because SQL tries to access the folders and files with this account

For the a multiple-server environment SQL server retrieves the information of backup file

from the application server and the account requires the folder access privilege for the

application server

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2054 CUSTOMER 2012-06-13

To ensure that you have the complete access privileges we recommend the Planning and

Consolidation sysadmin for this service account

2 In the Collation tab set the collation settings to SQL_Latin1_General_CP1_CI_AS

Choose Next

6 Set Database Engine Configuration options then choose Next

We recommend you choose Mixed mode (Windows authentication and SQL authentication) This allows you

to use a restrictive SQL ID that works with the drill-through feature If you must restrict SQL

authentication for security reasons you can define a specific parameter in your drill-through

queries If you do not need drill-through support or use it without leveraging SQL authentication

you can install the SQL Server in Windows-only mode

7 Accept the Analysis Services Configuration default options and the remaining default options of the

installation program

8 Choose Install to begin the installation with the options you have set

SQL Server Component 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

Server Component What to Install

SQL Server Database Engine Services

SSAS Server Analysis Services

Application Server The following Shared Features Client Tools Connectivity Integration Services Client Tools SDK

Custom Settings for the SQL Server

As of version 100 Planning and Consolidation supports the following new features for SQL Server 2008

SQL Server 2008 R2 and SQL Server 2012

Process Dimension

It is now possible to process a dimension with multiple selections At processing time the process

dimension module makes changed or added information for each dimension and process for all selected

dimensions and cubes in parallel

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 2154

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

NOTE

Setting 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 tblFactWBltappgt table

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 Microsoftreg SQL Servertrade

20052008 which you can download from wwwmicrosoftcom (search on ldquoTable Partitioningrdquo to find

all relevant articles)

After Installing SQL Server 2008 SQL Server 2008 R2 and SQL Server 2012

From SQL Server Configuration Manager confirm that the SQL Server Browser service is

running The browser service is required for Planning and Consolidation

From SQL Server Configuration Manager do the following

1 Select Protocols for ltInstanceNamegt then double-click TCPIP from the right side of the window

2 When prompted for the TCPIP Properties select IP Addresses You see two IPs that indicate the

localhost and external network interface machine

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2254 CUSTOMER 2012-06-13

3 If you want to use IP1 which indicates Server IP set Enabled to Yes and specify the TCP Port as

desired

4 Delete 0 from TCP Dynamic Ports Set IPAll - TCP Ports as desired (for example 1533)

RECOMMENDATION

We do not recommend using dynamic ports

In an SQL server the default instance has a listener which listens on a fixed port (TCP

port 1433) However for the named instance the port on which the SQL server listens is

random and dynamically selected when the named instance of the SQL server starts This

recommendation prevents any conflict problems

From the SQL Server Configuration Manager specify the client protocol options for the application

server

1 Select Client Protocols from the SQL Native Client Configuration folder

2 From the right side of the window double-click TCPIP The TCPIP 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

NOTE

We 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

274 Installing Analysis Services

ProcedureAfter you install SQL Server and its required service packs and hotfixes you must install SQL Server

Analysis Services and its required service packs and hotfixes

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 2354

NOTE

If you have migrated your Analysis Services repository to the SQL Server back up the database

that contains the repository before installing this release

To install Analysis Services for SQL Server 2008 SQL Server 2008 R2 or SQL Server 2012 follow the steps

and guidelines in httptechnetmicrosoftcomen-uslibraryms143219aspx

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 httpwwwmicrosoftcomdownloads

detailsaspxFamilyID=3be0488d-e7aa-4078-a050- ae39912d2e43ampdisplaylang=en

275 Installing the Anti-Cross Site Scripting Library

Procedure

Before installing Planning and Consolidation servers you must download the Anti-Cross Site Scripting

Library (version 42 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 AntiXSSLibraryDLL from the Microsoft Web

site at httpwwwmicrosoftcomdownloadendetailsaspxid=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 AntiXssLibrarydll

28 Installing on a Single Server

When you install all Planning and Consolidation server components on a single server you should

consider the following issues

Make sure the server has a minimum of 800 MB of hard disk space

Additional environment installations require more free disk space which is a minimum of two

times the uncompressed size of the environment files

When you install Planning and Consolidation on a single-server the system adds the following server

components

SQL Server

SQL Server Analysis Services (SSAS)

Application Server

FileShare server

Procedure

To install Planning and Consolidation on a single server take the following steps

1 Exit all Windows programs

2 Installing Planning and Consolidation Servers

28 Installing on a Single Server

2454 CUSTOMER 2012-06-13

2 Log on to the server with a local server user ID or domain user ID For more information see Logging

on to servers [page 14]

3 Make sure all prerequisite software is installed on the server For more information see Installing

the Prerequisites [page 17]

4 Obtain SAP Planning and Consolidation from the Downloads SAP Installations amp Upgrades area of

SAP Service Marketplace then extract the files and run StartUpexe

5 From the Server Install screen select Install the Planning and Consolidation server

6 From the Welcome screen choose Next

7 From the License Agreement page choose I accept the terms of the license agreement then choose Next

8 From the Installation Method page accept the default Single machine enter a system ID for the system

landscape directory (SLD) and choose Next

NOTE

Entering a system ID of the SLD is only required if you have a SAP Solution Manager license

If you do not have a SAP Solution Manager license you can leave this field empty

9 From the Authentication Method page choose the desired authentication method and choose Next

10 If you have chosen SAP BusinessObjects User Management System in the previous screen on the CMS

Authentication page enter the information required to log on to CMS as an administrator

The following information is required

Field Description

System name CMS system name (server nameport number) for example CMSServer6400

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

11 After entering the CMS administrator authentication details choose Next

12 From the Service type accounts page enter service-level account user IDs and passwords See Service-

Level Accounts [page 15]

13 After defining the IDs and passwords choose Next

14 From the Server Information page (see Standard and Advanced Settings [page 16]) do one of the following

Review the standard settings and choose Next

To set advanced settings choose the Advanced Settings button Enter the desired information

and choose Next

2 Installing Planning and Consolidation Servers

28 Installing on a Single Server

2012-06-13 CUSTOMER 2554

15 Specify the location and name of AntiXssLibrarydll See Installing the Anti-Cross Site Scripting Library [page

24]

Choose Next

16 Select destination folders for Programs and Data The Data files include Webfolders and FileDB

(published reports) and should be installed on a separate drive in a production environment This

recommendation reduces the hard disk IO time and helps to speed up SQL commands

Accept the defaults or make your selections then choose Next

17 Select the default values for the Web client The values are used to determine the default language

and region for the Web client when you connect to it You can change the values in the Planning

and Consolidation Server Manager

18 The installation process takes a few moments When it is complete choose Exit

19 A prompt is displayed to restart your computer Select OK to restart

20 Perform the steps in After Installing Planning and Consolidation Servers [page 27]

29 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 24]) with the following

exceptions

On the Installation Method page do not accept the default instead choose Network Load Balancing

environment With this option there is an additional choice to Include sample environment (required on only

one of the application servers) This is because when you install the application server it connects to the

database server and creates the sample environment (EnvironmentShell) Installing the sample

environment is required on only one application server and you may choose which one

In the Virtual Name field enter the virtual IP address virtual name in the default properties

2 Installing Planning and Consolidation Servers

29 Installing the Server in a Multiserver Configuration

2654 CUSTOMER 2012-06-13

3 After Installing Planning and Consolidation Servers

31 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 28]

2 Configure the Planning and Consolidation NET and application server to ensure that it and its

related services function properly and reliably For more information see Configuring the Planning and

Consolidation NET Application Server [page 29]

3 Optional configuration steps [page 30]

1 To ensure proper functioning of the Management Console create an SQL user and modify

the System DSN and IIS to reflect those user credentials See Enabling Management Console [page

30]

2 Configure custom ODBC logging for the default Web site For details of how to configure

custom logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web

Site [page 31]

3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC

Data Source [page 32]

4 Modify the default access rights to the Management Console By default users in Active

Directory can access the Management Console with whatever rights they have been granted

on the server For information about removing default access and creating a group that can

access the console see Removing Default Access to the Console [page 32]

5 Add authorized users or groups to the group that can access the Management Console We

recommend that you only grant Management Console access to system administrators

Planning and Consolidation users should not have any access For more information see

Management Console Access Control [page 33]

6 Configure the use of client certificates for authentication See Using Client Certificates [page

34]

4 Take the following steps to set up security

If you are defining security and application structure continue with step 5

3 After Installing Planning and Consolidation Servers

31 Post-Installation Steps

2012-06-13 CUSTOMER 2754

If you want to designate someone other than the system administrator to manage security

and application structure log on to EnvironmentShell designate a user as a Primary

Administrator

This user must have Administration ‒ Environment and Security ‒ Define User task rights

so that he or she can add and delete environments and define user security

The Primary Administrator can continue with the next step (5)

5 From the machine on which you administer Planning and Consolidation install the

Administration client See Installing the Administration Client [page 37]

6 Start Planning and Consolidation Administration from the launch page

7 Select Connection Wizard and log on to EnvironmentShell

8 Create a new environment using EnvironmentShell as the source

9 Log on to the newly created environment and set up users teams and task profiles (You must

set up task profiles since there is no access to Planning and Consolidation tasks)

10 Set up your data access profiles and add users (or teams) to one or more data access profiles (You

must complete this step since there is no access to dimensions or members)

NOTE

To allow users to request and query large amounts of data you can edit the metabasexml file located

at CWindowssystem32inetsrv Set the following parameters to the stated values

ASPBUFFERINGLIMIT = 10485760

MAXREQUESTENTITYALLOWED = 10485760

32 Connecting to Solution Manager Diagnostics

NOTE

You only need to perform the steps in this section if you have a SAP Solution Manager licence

The diagnostics functions in SAP Solution Manager allow identification analysis and resolution of

problems This procedure provides the steps required to connect Planning and Consolidation to

Solution Manager Diagnostics

Procedure

1 Install the Diagnostics Agent according to SAP Note 1234387 on all servers where application servers

are installed

NOTE

Installation files for Diagnostics Agent are available on Service Marketplace by navigating to

Support Packages and Patches mdash Entry by Application Group SAP Technology Components SAP

SOLUTION MANAGER SAP SOLUTION MANAGER 70 EHP 1 Entry by Component Agents

for managed systems DIAGNOSTICS AGENT 711

3 After Installing Planning and Consolidation Servers

32 Connecting to Solution Manager Diagnostics

2854 CUSTOMER 2012-06-13

Download the installation file based on the 64-bit Windows Server system landscape

2 To access the DBA Cockpit you must create a user account with sufficient rights on all Windows

Servers where Microsoft SQL Server is installed Do the following

1 Start Computer Management then select Action New User

2 Create a new user

3 Right-click on the user then choose Properties On the Member Of tab select Add

4 Add the group SQLServerltReleasegtSQLAgentUser$ltDomain or hostnamegt$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 httpsservicesapcom~sapidb011000358700000074392009E and follow

the chapters that apply to Planning and Consolidation

33 Configuring the Planning and Consolidation NET Application Servers

Procedure

Modifying machineconfig Files

To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock

occurrences that would cause the application server to ldquosleeprdquo and not process anymore you can

modify the machineconfig file which resides in the WINDOWSMicrosoftNETFramework64

v4030319Config directory

1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to

specify whether to automatically configure settings to achieve optimal performance based on the

machine configuration You can set this attribute to True or False

For more information see httpmsdnmicrosoftcomen-uslibrary7w2sway1aspx

2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the

Planning and Consolidation application) or Machineconfig (for all applications including

Planning and Consolidation) to ensure the validationKey and decryptionKey keys have the same

value on all application servers This way when the authentication cookie is checked the

authentication ticket used on one server can still be valid on another server

For more information and sample Visual Basic code for generating random key values see http

msdnmicrosoftcomen-uslibraryms998288aspx

3 After Installing Planning and Consolidation Servers

33 Configuring the Planning and Consolidation NET Application Servers

2012-06-13 CUSTOMER 2954

paght000007_webfarmdeploymentconsiderations and httpmsdnmicrosoftcomen-us

libraryms998310aspx

34 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 30]

2 Configure custom ODBC logging for the default Web site For details of how to configure custom

logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page

31]

3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC Data

Source [page 32]

4 Modify the default access rights to the Management Console By default users in Active Directory

can access the Management Console with whatever rights they have been granted on the server

For information about removing default access and creating a group that can access the console

see Removing Default Access to the Console [page 32]

5 Add authorized users or groups to the group that can access the Management Console We

recommend that you only grant Management Console access to system administrators Planning

and Consolidation users should not have any access For more information see Management Console

Access Control [page 33]

6 Configure the use of client certificates for authentication See Using Client Certificates [page 34]

341 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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3054 CUSTOMER 2012-06-13

NOTE

Without these updates the Management Console does work but some functionality (specifically

User Activity and Service Status) does not work as expected

Should you need to uninstall Planning and Consolidation we recommend that you reset the

Active Log Format field in IIS to W3C Extended Log File Format

342 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 ApplicationHostconfig set the property customLogPluginClsid to the value FF16065B-

DE82-11CF-BC0A-00AA006111E0 Set the logFormat to Custom You can find this in the ltlogFilegt

node in ApplicationHostconfig as shown here

ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0

logFormat=Custom gt

Use the following AppCmds to configure IIS to use ODBC logging for the default Web site

appcmd site set sitenameDefault Web Site

logFilecustomLogPluginClsidFF16065B-DE82-11CF-BC0A-00AA006111E0

appcmd site set sitenameDefault Web Site logFilelogFormatCustom

Configuring ODBC Logging Parameters in ApplicationHostconfig

Configure ApplicationHostconfig to contain the database table information as set up in the Microsoft

Support article specified in the Prerequisites section Configure these settings in the ltodbcLogginggt

node under ltsystemwebServergt

EXAMPLE

ltlocation path=Default Web Sitegt

ltsystemwebServergt

ltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog

userName=Username password=mypassword gt

ltsystemwebServergt

ltlocationgt

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3154

Use the following AppCmds to configure these attributes for the default Web site

appcmd set config Default Web Site sectionodbcLogging

dataSourceBPC_ManagementDSN commitappHost

appcmd set config Default Web Site sectionodbcLogging tableNameBPCLog

commitappHost

appcmd set config Default Web Site sectionodbcLogging userNameUsername

commitappHost

appcmd set config Default Web Site sectionodbcLogging passwordmypassword

commitappHost

NOTE

You cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must

use the SQL Server ODBC driver For more information see the Microsoft Knowledge Base article

931202 The requirements for using the ODBC logging feature in IIS

343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2

ProcedureThis procedure describes how to set up an ODBC data source for the Management Console in Windows

Server 2008 or Windows Server 2008 R2

Proceed as follows

1 Open ODBC Connection Manager

2 On the System DSN tab page add a new DSN

Choose Add

Choose SQL Server as the driver

Choose Finish

3 In the Name and Description fields enter BPC_ManagementDSN

4 In the Server field enter the name of your SQL Server Choose Next

5 Leave the default settings and choose Next

6 Choose the Change the default database to field and enter AppServer Choose Next

7 Leave default settings and choose Next

8 Choose OK

344 Removing Default Access to the Console

NOTE

If you have chosen SAP BusinessObjects User Management System in the installation screen you

do not need to remove or configure access because the Management Console service always runs

with the System Admin ID account which is a member of the Administrators group

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3254 CUSTOMER 2012-06-13

ProcedureTo remove default access to the Management Console and create a group that does have access to the

console use the procedure described below

NOTE

Create your Management Console administrative group either on the server that hosts the

Management Console or in the Active Directory

1 In the context menu of the servers My Computer icon choose Manage

2 In the Computer Management dialog box choose Local Users and Groups Groups

NOTE

Alternatively you can perform analogous steps in Active Directory

3 In the 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

NOTE

This step is a necessary precursor to the completion of this procedure

10 In the Security dialog box click Copy to ensure that the System group retains its privileges

11 Remove access to the Management Console from all groups that should not have it

12 Choose Authentication in the center pane then disable Windows authentication

ResultUsers who have not been granted access to the Management Console can still open the Management

Console Web page but it contains no data or menu options This does not affect the access that a user

would otherwise have to Planning and Consolidation

345 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 32] Their rights in

Active Directory determine what they can access in the Console

By default any member of the Administrators Active Directory group on the application server or

domain has full access to all of the features of the Console except the Planning and Consolidation

logging area Access to Planning and Consolidation logging is controlled within the Planning and

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3354

Consolidation Administration Client task security The user must be granted View system logs task

privileges For more information see the SAP Library Planning and Consolidation Administrators Guide in

httpservicesapcominstguidesepm-bpc 100 version for the Microsoft platform

Your IT policy determines whether you grant access by group or user You may wish to create several

levels of Console users (read-only users for example) in your environment

To grant or limit access to users or groups you can add or remove the following privileges from the

areas described in this table

Privilege Rights Management Area

Task Manager and Kill Process Administrators group on application server or domain

Performance Monitor Counters Administrators group on application server or domain Power Users group on application server or domain Performance Monitor Users group on application server

Microsoft Analysis Services performance monitoring

Administrators group on application server or domain

Microsoft SQL Server Monitoring (performance counters and statistics)

Administrators group on application server or domain

346 Using Client Certificates

To enable the use of client certificates in Planning and Consolidation you must follow several manual

steps

NOTE

Planning 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 httptechnetmicrosoftcomen-us

librarycc753810aspx

For more information about configuring the client certificate mapping authentication see http

technetmicrosoftcomen-uslibrarycc732996(WS10)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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3454 CUSTOMER 2012-06-13

This option allows you to use a client certificate or username and password (Basic

authentication) to connect to Planning and Consolidation

2 Enable anonymous authentication

1 In the IIS Manager expand the node of the Planning and Consolidation web site

2 Select the ManagementConsole directory (ltWebsitegtManagementConsole) to open the

ManagementConsole home page

3 Double-click Authentication and enable Anonymous Authentication

4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way

as in step 3

5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the same

way as in step 3

3 Change the web configuration settings

1 Open the ltPC_MSgtWebsrvrWebBPCwebconfig file

2 Find the text clientCredentialType=Windows

3 Change value of clientCredentialType to None (clientCredentialType=None)

4 Open the PC_MSWebsrvrWebPOASBCwebconfig file Repeat steps 2 and 3

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3554

This page is left blank for documents that are printed on both sides

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

The installation of the Planning and Consolidation Administration Client allows administrators to

build and maintain Planning and Consolidation environments and models and administer security

All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions

add-in for Microsoft Office for more information see the SAP BusinessObjects EPM solutions add-in for

Microsoft Office help

NOTE

You must update the Administration Client to the same version as the server

If your PC is on a different domain than your server you must set the Internet Explorer

Security Zone value of the Planning and Consolidation client to prompt for user name and

password Otherwise the Planning and Consolidation Start Page does not display

41 Installing the Administration Client

Prerequisites

NOTE

For a definitive list of system requirements see the Product Availability Matrix on SAP Service

Marketplace at httpservicesapcompam Search on Planning and Consolidation

The following list describes the minimum software requirements

Microsoft Internet Explorer 70 or 80

Microsoft Office 2007 or 2010

NET Framework 20 or higher (install any required NET Framework Hotfixes by referring to

httpsupportmicrosoftcomkb)

Pentium IV (1 GHz CPU)

512 MB RAM

100 MB of free hard disk space in the My Documents folder

20 MB of free hard disk space for the installed Administration files

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

41 Installing the Administration Client

2012-06-13 CUSTOMER 3754

NOTE

We recommend that you install all of the latest Microsoft Windows hotfixes prior to installing

the Administration client For information about which hotfixes to install see http

updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us

ProcedureThe following procedure describes how to install the Administration Client on to an administratorrsquos

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 AddRemove Programs in the Windows Control Panel

3 Point your browser to the Planning and Consolidation Web at httpltPC_serverportgtsap

bpcweb

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

42 Installing the EPM Add-in

The Planning and Consolidation installation media does not contain the EPM addin setup program

You must download the most recent version of the full setup (EPM Add-inexe) from the Service

Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPC

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

43 Using the Client Auto Update Program

If Planning and Consolidation version 100 or later is installed you can use the Client Auto Update

program to set up the server so that it determines if an upgrade for a connecting Administration client

is necessary

The following describes the use of the auto update program for the Administration Client and the EPM

add-in

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

42 Installing the EPM Add-in

3854 CUSTOMER 2012-06-13

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 37]

To use the Client Auto Update program for the Administration Client proceed as follows

1 From the Server Manager select Options Client Options

2 Select Admin Update

3 If users without administrator rights on their machines use the auto update enter an administrator

ID and password in the Admin ID and Admin password fields respectively The Admin ID should be a

member of the local administrators group on all the computers running the auto update This

setting is not needed if all users have administrator rights on their machines

4 Select Update

For the EPM Add-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 Optionshellip 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 Market Place (SMP) at httpservicesapcom

All support packages and patches are available from the SMP as a zip file

EPMEXCLCLNTltSPLgtzip is for a support package

EPMEXCLCLNTltSPLgtPltPLgtzip 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 ltSP versiongtmsp

EPM Addin Support Package ltSP versiongtxml

For a patch these files are

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

2012-06-13 CUSTOMER 3954

EPM Addin Patch ltpatch numbergtmsp

EPM Addin Patch ltpatch numbergtxml

2 Unzip the zip file and extract the two files to the application server folder (WebsrvrWebBPC

Installation)

3 From the Server Manager select Options Client Options

The system lists the available packages Select the package that you want to use for the autoupdate

You can set a different update policy for each package listed

EXAMPLE

The following table illustrates some possible situations assuming that you have installed the

first full version (V1)

Available maintenance packages

V2-user updateV3-force updateV4-force updateV5-user update

V5-user update V5-user updateV6-auto updateV7-force update

Minimum Required Version

V4 V4 V7

Notification A prompt tells the user to install maintenance package V4 using the Forced Update behavior

If User Update is enabled the prompt informs the user that maintenance package V5 is available

A prompt tells the user to install maintenance package V7 using the Forced Update behavior

New Version V4 V4 or V5 V7

If you change the update policy for any package click Update to complete the change

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

4054 CUSTOMER 2012-06-13

5 Connection Issues

You may experience connection problems with ports the proxy server or programs and settings that

interact with these components If you have any issues related to connection review the following

recommendations and troubleshooting tips

51 Checking for Open Ports

You must ensure that all required ports are open for inboundoutbound 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 431181836 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

NOTE

You can use the following site to scan for the normal ports It allows you to manually enter a port

number to test

httpwwwmyserverorgportsniffasp

You can change the name of a port

52 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 Explorer Tools Internet Options Connections LAN Settings ) or at the server level

Enabling content filtering on the proxy server or firewall may cause connection problems

If external users are having trouble connecting to the server make sure the proxy server connects

using a fully qualified domain name Fully qualified domain names typically resolve both internal

and external IP addresses

Each secure Planning and Consolidation server name must be identified on the proxy server

Proxy servers may or may not require authentication which could conflict with Planning and

Consolidation authentication Do not use authentication on the proxy server The system

5 Connection Issues

51 Checking for Open Ports

2012-06-13 CUSTOMER 4154

synchronizes the user name and password on the remote server with the local user name and

password

NOTE

For more information about setting up an ISA proxy server contact SAP Support to request a

copy of Setting up ISA Proxy Server White Paper

Internet Explorer Settings 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

5 Connection Issues

52 Proxy Server and Firewall Issues

4254 CUSTOMER 2012-06-13

6 Installing Planning and Consolidation with Two Active Directory Domains

To set up a Planning and Consolidation 10 application server in a hosted environment and use your

own domain users follow this procedure In general you install Planning and Consolidation on the

host domain use the host domain account and assign it to the Planning and Consolidation users

SysAdmin Admin and Users Then you accept one way trust (the host domain trusts your domain)

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

6 Installing Planning and Consolidation with Two Active Directory Domains

2012-06-13 CUSTOMER 4354

This page is left blank for documents that are printed on both sides

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

This section describes best practices and instructions for installing Planning and Consolidation in a

Terminal Services or Citrix Server deployment

71 Terminal Services Home Directories

We recommend using Terminal Server home directories rather than using the userrsquos 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

72 System Requirements

The Citrix server should be one of the following systems

XenApp 5 Enterprise

XenApp 5 Platinum

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 37])

73 Installing Planning and Consolidation

Prerequisites

The server installation files have been downloaded from SAP Service Marketplace and installed

Procedure

The following steps outline how to install the Planning and Consolidation clients in a Terminal Services

(TS) or Citrix Server deployment

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

71 Terminal Services Home Directories

2012-06-13 CUSTOMER 4554

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 userinstall

4 Open a browser and connect to the URL httpltPC_serverportgtsapbpcweb

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 userexecute 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 Iexploreexe http(s)

ltServerNamegt-NetBIOS or FQDNsapbpcweb

To publish Planning and Consolidation Administration CProgram FilesPC_MS

BPCAdminMainexe

74 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 userrsquos desktop) must be moved to the All UsersDesktop folder

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

74 Creating a Shortcut to the Launch Page

4654 CUSTOMER 2012-06-13

8 Installing SSIS Custom Tasks

This section provides background information and instructions for installing SQL Server Integration

Services (SSIS) for SQL Server 2008 and SQL Server 2012

The Planning and Consolidation Data Manager component supports and uses SSIS Since SQL Server

2008 and SQL Server 2012 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

81 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 Filelistxml 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

OSoftSetupexe ‒ 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 or OSoftSSIS2012_Client on the client machine followed by the SQL Server

version If you want to use SQL 2008 Tasks under the SQL 2012 environment you must install

OSoftSSIS2008_Client on the application server For detailed information see SAP Note 1707410

You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package by extracting

OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPC

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 or

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4754

OSoftSSIS2012_Client for creating a COM+ application For more information see Before You Modify

the SSIS Packages [page 50] and Setup of a COM+ Application on the Application Server [page 51]

Bin folder

This folder contains the following components

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCCachedll Planning and Consolidation Cache file

BPCDataFlowPackagedll or BPCDataFlowPackage2012dll

BPCDMdll

BPCDMTaskMaindll COM+ component

BPCFilePreviewdll

BPCGacUtil_20exe System File

BPCGacUtil_40exe System File

BPCImpersonatordll Planning and Consolidation Impersonator

BPCLogicdll

BPCScriptdll

BPCServerZipdll

BPCServiceResdll

BPCTransferMembersdll

BPCWriteBackdll

InteropDTSdll

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

4854 CUSTOMER 2012-06-13

Name Remark

OSoftAdminServerdll

OSoftAuditdll

OSoftComLibServerdll

OSoftCommonResQrydll

OSoftConfigurationdll

OSoftCustomXMLSvrdll

OSoftDatabaseADMINdll

OSoftDatabaseSYSADMINdll

OSoftDatabaseSYSADMINDMdll

OSoftDatabaseUSERdll

OSoftDMDTSXExecutedll or OSoftDMDTSXExecute2012dll

OSoftDMTaskFormdll

OSoftDMTaskMaindll

OSoftDMToolsdll

OSoftFileManagedll

OSoftLoggingdll

OSoftLogWriterdll

OSoftMetaDatadll

OSoftSQEdll

OSoftSystemConfigdll

OutlookSoftconfig Configuration file to connect DB server

XceedCompressiondll XceedZip file

XceedCompressionFormatsdll XceedZip file

XceedFileSystemdll XceedZip file

XceedZipdll XceedZip file

Config folder

This folder has FileListxml 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 FileListxml 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

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4954

OSoftSetupexe

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

NOTE

If you installed the OSoftSSIS2008_Client or OSoftSSIS2012_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

Resources Folder

This folder contains the BPCServicesdll and BPCServiceUIdll files which contain resource text

Only English resources are included for the SSIS custom tasks

82 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

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008 and 2012 respectively

8 Installing SSIS Custom Tasks

82 Before You Modify the SSIS Packages

5054 CUSTOMER 2012-06-13

Name Remark

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012 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

lthellipgtOSoftSSIS2008_Clientbin or lthellipgtOSoftSSIS2012_Clientbin

On the Planning and Consolidation application server

ltdrivegtWebsrvrbin

2 Paste these files into the folder 100DTSTasks for SQL Server 2008 or into 110DTSTasks for

SQL Server 2012 For example if you install your SQL 2008 server or R2 on CProgram Files

Microsoft SQL Server paste all files into the CProgram Files (x86)Microsoft SQL Server

100DTSTasks folder

In Integration Services set the property Run64BitRunTime to True

83 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 or OSoftSSIS2012_Client on the

application server

8 Installing SSIS Custom Tasks

83 Setup of a COM+ Application on the Application Server

2012-06-13 CUSTOMER 5154

Typographic Conventions

Example Description

ltgt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example Enter your ltUser Namegt

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 httpwwwsapcom

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

5254 CUSTOMER 2012-06-13

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

  • SAP BusinessObjects Planning and Consolidation 100
    • Table of Contents
    • 1 Introduction
      • 11 SAP Notes for the Installation
      • 12 Naming Conventions
        • 2 Installing Planning and Consolidation Servers
          • 21 Basic Steps
          • 22 Prerequisites
          • 23 Before Starting the Planning and Consolidation Server Installation
          • 24 Logging on to Servers
          • 25 Service-level Accounts
          • 26 Standard and Advanced Settings
          • 27 Installing the Prerequisites
            • 271 Installing the Prerequisites ndash Basic Steps
            • 272 Installing the Operating System
            • 273 Installing the SQL Server
            • 274 Installing Analysis Services
            • 275 Installing the Anti-Cross Site Scripting Library
              • 28 Installing on a Single Server
              • 29 Installing the Server in a Multiserver Configuration
                • 3 After Installing Planning and Consolidation Servers
                  • 31 Post-Installation Steps
                  • 32 Connecting to Solution Manager Diagnostics
                  • 33 Configuring the Planning and Consolidation NET Application Servers
                  • 34 Post-Installation Optional Configuration Steps
                    • 341 Enabling the Management Console
                    • 342 Setting Up ODBC Logging in IIS for the Default Web Site
                    • 343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2
                    • 344 Removing Default Access to the Console
                    • 345 Management Console Access Control
                    • 346 Using Client Certificates
                        • 4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office
                          • 41 Installing the Administration Client
                          • 42 Installing the EPM Add-in
                          • 43 Using the Client Auto Update Program
                            • 5 Connection Issues
                              • 51 Checking for Open Ports
                              • 52 Proxy Server and Firewall Issues
                                • 6 Installing Planning and Consolidation with Two Active Directory Domains
                                • 7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
                                  • 71 Terminal Services Home Directories
                                  • 72 System Requirements
                                  • 73 Installing Planning and Consolidation
                                  • 74 Creating a Shortcut to the Launch Page
                                    • 8 Installing SSIS Custom Tasks
                                      • 81 Composition of SSIS Custom Task Installation
                                      • 82 Before You Modify the SSIS Packages
                                      • 83 Setup of a COM+ Application on the Application Server
                                          • Copyright and trademarks
Page 15: Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

25 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

PrerequisitesPlanning and Consolidation 100 has the following Windows services

BPC SendGovernor which manages Microsoft Analysis Service locks to ensure consistent performance

and avoid deadlocks

BPC ServiceManager which manages the System Landscape Directory (SLD) service logging service

and global caches

BPC CTS ServiceManager which listens and handles CTS import requests from the CTS+ transport

management system

Since these services should be able to access to the FileShare server an Admin account is assigned

automatically to the service during the installation of the Planning and Consolidation server program

Even though an Admin account has been assigned to the server correctly the services may fail to start

with the error message

Could not start the BPC SendGovernor service

The reason for this is that the Admin account is not registered as a service

When installing a service to run under a domain user account the account must have the right to

logon as a service on the local machine This logon right strictly applies only to the local computer

and must be granted in the Local Security Policy

To edit the Local Security Policy of the computer you want to define the logon as a service

permission perform the following actions

1 Start the Local Security Settings Microsoft Management Console (MMC) snap-in

2 Expand Local Policies and then click User Rights Assignment

3 In the right-hand pane right-click Log on as a service and then click Security

4 Add the user to the policy and click OK

5 Close the Local Security Settings MMC snap-in

For more details see How to Troubleshoot Service Startup Permissions http

supportmicrosoftcomkb259733

FeaturesDuring the installation enter user IDs and passwords for the following user types

System Admin ID

This ID is read-only and is the same as the installation user ID that is the system displays the ID

on the installation screen but you cannot modify it This ID allows access to code that provides

2 Installing Planning and Consolidation Servers

25 Service-level Accounts

2012-06-13 CUSTOMER 1554

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 readwrite 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

26 Standard and Advanced Settings

The following tables describe the standard and advanced settings for the installation program After

the server is installed you can change these settings using the Server Manager

NOTE

When defining server names the name refers to the NetBIOS name IP address and fully qualified

domain names (FQDN)

Standard Settings

Standard settings are typically used for a single-server environment The following table describes each

setting

Server Option Value Description

SQL Database server name The name of the SQL DB server

OLAP server name The name of the OLAP server

File Share server name The default value is the name of the File Share server that should be the computer name

Local data path Where the data files are saved on the File Share server By default this is CPC_MSData

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

Server Option Value Description

SQL Server Name The name of the SQL DB server Defaults to the local server

2 Installing Planning and Consolidation Servers

26 Standard and Advanced Settings

1654 CUSTOMER 2012-06-13

Server Option Value Description

Instance name The SQL instance name If left blank the default instance is used

Port number The default port number for the SQL Server is 1433

Provider The only available value is SQL

Local path for EnvironmentShell 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 CPC_MSData

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 changesSee the Kerberos authentication settings section in the SAP Library Server Manager Guide on httpservicesapcominstguidesEPM-BPC

100 for the Microsoft Platform

Scheduler Server Name The name of the server used for scheduling usually the application server for example GMPV50072862B If you have multiple application servers select the appropriate one

NOTE

If the primary server stops working you must manually configure your application server database to froward requests to another application server

27 Installing the Prerequisites

271 Installing the Prerequisites ndash Basic Steps

Before installing your Planning and Consolidation server you must install the prerequisite Microsoft

software the operating system IIS SQL server analysis services ADOMDNET and MSXML This

section provides guidance on installing each component For specific versions required see

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 1754

Prerequisites [page 11] and the Product Availability Matrix on the SAP Service Marketplace at http

servicesapcompam Search on Planning and Consolidation

NOTE

To ensure a successful installation you must install the software in the order listed in this

procedure

Check all third-party infrastructure services to ensure that they are functioning and that their

authentication models are documented (stated) since you need to reference this information

during the installation These third-party services include IIS OLAP service SQL services and

Active Directory (AD)

We recommend not installing Microsoft Office on the application server

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

(UMCexe) on the Planning and Consolidation CD in a folder called UMC_100_INSTALLER When

you run the installation package the wizard guides you through the following steps

1 Choose a language for the UMC install wizard to use

2 Check that the prerequisite check status is Succeeded and click Next

3 When you are ready to install the UMC click Next on the welcome screen

4 Click I accept the License Agreement and then Next

5 Choose the destination directory for the UMC installation and click Next

6 Select the languages that you wish to install

7 Select the features that you want to install (POAFHelper dotnet is mandatory for Planning

and Consolidation)

8 On Start Installation click Next to complete the installation

2 Install the required operating system on the single-server computer or on each physical server for

a multiserver configuration See Installing the Operating System [page 19]

3 Install the latest service pack for your operating system To install this service pack go to http

wwwmicrosoftcom

4 From your operating systems media install IIS

5 From your SQL Server media install SQL Server and its required service packs and hot fixes See

Installing SQL Server [page 19]

6 From your SQL Server media install Analysis Services Enterprise Edition and its required service

packs and hot fixes See Installing Analysis Services [page 23]

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

1854 CUSTOMER 2012-06-13

7 On your application server install ADOMDNET The Planning and Consolidation zip file contains

the ADOMDNET installation package in the following locations

For SQL Server 2008 mdash BPC SetupServerSQLSERVER2008_ASADOMD10_x64msi

For SQL Server 2012 mdash BPC SetupServerSQLSERVER2012_ASADOMD11_x64msi

8 On your application server install MSXML 40 Service Pack 2 or later

The MSXML 40 SP2 installation package is contained in the Planning and Consolidation zip file at

the following location BPC SetupServermsxmlmsi

9 On your application server install Microsoft Visual C++ 2005 Runtime Libraries SP1

The Microsoft Visual C++ 2005 SP1 installation package is contained in the Planning and

Consolidation zip file at the following location BPC SetupServervcredist_x64exe

NOTE

The version of vcredist_x64exe in BPC SetupServer has been updated to 8061000 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 httpwwwmicrosoftcomdownloadsen

detailsaspxFamilyID=C06B8369-60DD-4B64-A44B-84B371EDE16Dampltdisplaylanggt=en

272 Installing the Operating System

Before installing the operating system make sure that you configure your server for NTFS

For a list of languages that are supported see the Product Availability Matrix on the SAP Service

Marketplace at httpservicesapcompam Search on Planning and Consolidation

Planning and Consolidation can support all servers with an operating system in any language

NOTE

Currently Planning and Consolidation does not support an operating system in bi-directional

languages such as Hebrew

ProcedureIf you are installing IIS 70 or 75 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

273 Installing the SQL Server

PrerequisitesDuring the installation procedure you have the opportunity to specify the location of the

EnvironmentShell database file Check that it is possible to access EnvironmentShell from the location

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 1954

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 CEnvironmentShelldb10) 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 a 2008 2008 R2 and 2012 SQL Server

SQL Server Considerations

We recommend installing all required components in sequence For example install the Operating

System (Windows Server) then enable IIS and ASPNET and install any Windows Server service

packs

IIS and NET Framework 40 are required on your application server

NOTE

If you encounter a 500 HTTP Error when trying to connect to the Planning and Consolidation

Web Client refer to Microsoft Support articles 2520479 and 2468871 for assistance

To reinforce security we recommend that you install the SQL server and SSAS components to a

nondefault instance of SQL Server

General Installation Steps

1 Launch the SQL Server Setup program entering a product key if necessary and accepting the license

terms

2 Choose Install to install the SQL support files

3 In Feature Selections select instance and shared features as indicated in the SQL Server Component

Options section below then choose Next

4 Review disc space requirements then choose Next

5 In Server Configuration Perform the following actions

1 In the Service Accounts tab enter a Planning and Consolidation sysadmin account for the SQL

Server Database Engine and the SQL Server Analysis services This is required so that the Planning

and Consolidation sysadmin can create and process the Planning and Consolidation database

because the Microsoft SQL server tries to back up or restore database with the privileged

account This account is also required during Backup Environment and Restore Environment in the

Server Manager

For a single-server environment this account is also required if the backup file is located in a

different domain machine because SQL tries to access the folders and files with this account

For the a multiple-server environment SQL server retrieves the information of backup file

from the application server and the account requires the folder access privilege for the

application server

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2054 CUSTOMER 2012-06-13

To ensure that you have the complete access privileges we recommend the Planning and

Consolidation sysadmin for this service account

2 In the Collation tab set the collation settings to SQL_Latin1_General_CP1_CI_AS

Choose Next

6 Set Database Engine Configuration options then choose Next

We recommend you choose Mixed mode (Windows authentication and SQL authentication) This allows you

to use a restrictive SQL ID that works with the drill-through feature If you must restrict SQL

authentication for security reasons you can define a specific parameter in your drill-through

queries If you do not need drill-through support or use it without leveraging SQL authentication

you can install the SQL Server in Windows-only mode

7 Accept the Analysis Services Configuration default options and the remaining default options of the

installation program

8 Choose Install to begin the installation with the options you have set

SQL Server Component 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

Server Component What to Install

SQL Server Database Engine Services

SSAS Server Analysis Services

Application Server The following Shared Features Client Tools Connectivity Integration Services Client Tools SDK

Custom Settings for the SQL Server

As of version 100 Planning and Consolidation supports the following new features for SQL Server 2008

SQL Server 2008 R2 and SQL Server 2012

Process Dimension

It is now possible to process a dimension with multiple selections At processing time the process

dimension module makes changed or added information for each dimension and process for all selected

dimensions and cubes in parallel

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 2154

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

NOTE

Setting 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 tblFactWBltappgt table

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 Microsoftreg SQL Servertrade

20052008 which you can download from wwwmicrosoftcom (search on ldquoTable Partitioningrdquo to find

all relevant articles)

After Installing SQL Server 2008 SQL Server 2008 R2 and SQL Server 2012

From SQL Server Configuration Manager confirm that the SQL Server Browser service is

running The browser service is required for Planning and Consolidation

From SQL Server Configuration Manager do the following

1 Select Protocols for ltInstanceNamegt then double-click TCPIP from the right side of the window

2 When prompted for the TCPIP Properties select IP Addresses You see two IPs that indicate the

localhost and external network interface machine

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2254 CUSTOMER 2012-06-13

3 If you want to use IP1 which indicates Server IP set Enabled to Yes and specify the TCP Port as

desired

4 Delete 0 from TCP Dynamic Ports Set IPAll - TCP Ports as desired (for example 1533)

RECOMMENDATION

We do not recommend using dynamic ports

In an SQL server the default instance has a listener which listens on a fixed port (TCP

port 1433) However for the named instance the port on which the SQL server listens is

random and dynamically selected when the named instance of the SQL server starts This

recommendation prevents any conflict problems

From the SQL Server Configuration Manager specify the client protocol options for the application

server

1 Select Client Protocols from the SQL Native Client Configuration folder

2 From the right side of the window double-click TCPIP The TCPIP 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

NOTE

We 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

274 Installing Analysis Services

ProcedureAfter you install SQL Server and its required service packs and hotfixes you must install SQL Server

Analysis Services and its required service packs and hotfixes

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 2354

NOTE

If you have migrated your Analysis Services repository to the SQL Server back up the database

that contains the repository before installing this release

To install Analysis Services for SQL Server 2008 SQL Server 2008 R2 or SQL Server 2012 follow the steps

and guidelines in httptechnetmicrosoftcomen-uslibraryms143219aspx

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 httpwwwmicrosoftcomdownloads

detailsaspxFamilyID=3be0488d-e7aa-4078-a050- ae39912d2e43ampdisplaylang=en

275 Installing the Anti-Cross Site Scripting Library

Procedure

Before installing Planning and Consolidation servers you must download the Anti-Cross Site Scripting

Library (version 42 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 AntiXSSLibraryDLL from the Microsoft Web

site at httpwwwmicrosoftcomdownloadendetailsaspxid=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 AntiXssLibrarydll

28 Installing on a Single Server

When you install all Planning and Consolidation server components on a single server you should

consider the following issues

Make sure the server has a minimum of 800 MB of hard disk space

Additional environment installations require more free disk space which is a minimum of two

times the uncompressed size of the environment files

When you install Planning and Consolidation on a single-server the system adds the following server

components

SQL Server

SQL Server Analysis Services (SSAS)

Application Server

FileShare server

Procedure

To install Planning and Consolidation on a single server take the following steps

1 Exit all Windows programs

2 Installing Planning and Consolidation Servers

28 Installing on a Single Server

2454 CUSTOMER 2012-06-13

2 Log on to the server with a local server user ID or domain user ID For more information see Logging

on to servers [page 14]

3 Make sure all prerequisite software is installed on the server For more information see Installing

the Prerequisites [page 17]

4 Obtain SAP Planning and Consolidation from the Downloads SAP Installations amp Upgrades area of

SAP Service Marketplace then extract the files and run StartUpexe

5 From the Server Install screen select Install the Planning and Consolidation server

6 From the Welcome screen choose Next

7 From the License Agreement page choose I accept the terms of the license agreement then choose Next

8 From the Installation Method page accept the default Single machine enter a system ID for the system

landscape directory (SLD) and choose Next

NOTE

Entering a system ID of the SLD is only required if you have a SAP Solution Manager license

If you do not have a SAP Solution Manager license you can leave this field empty

9 From the Authentication Method page choose the desired authentication method and choose Next

10 If you have chosen SAP BusinessObjects User Management System in the previous screen on the CMS

Authentication page enter the information required to log on to CMS as an administrator

The following information is required

Field Description

System name CMS system name (server nameport number) for example CMSServer6400

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

11 After entering the CMS administrator authentication details choose Next

12 From the Service type accounts page enter service-level account user IDs and passwords See Service-

Level Accounts [page 15]

13 After defining the IDs and passwords choose Next

14 From the Server Information page (see Standard and Advanced Settings [page 16]) do one of the following

Review the standard settings and choose Next

To set advanced settings choose the Advanced Settings button Enter the desired information

and choose Next

2 Installing Planning and Consolidation Servers

28 Installing on a Single Server

2012-06-13 CUSTOMER 2554

15 Specify the location and name of AntiXssLibrarydll See Installing the Anti-Cross Site Scripting Library [page

24]

Choose Next

16 Select destination folders for Programs and Data The Data files include Webfolders and FileDB

(published reports) and should be installed on a separate drive in a production environment This

recommendation reduces the hard disk IO time and helps to speed up SQL commands

Accept the defaults or make your selections then choose Next

17 Select the default values for the Web client The values are used to determine the default language

and region for the Web client when you connect to it You can change the values in the Planning

and Consolidation Server Manager

18 The installation process takes a few moments When it is complete choose Exit

19 A prompt is displayed to restart your computer Select OK to restart

20 Perform the steps in After Installing Planning and Consolidation Servers [page 27]

29 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 24]) with the following

exceptions

On the Installation Method page do not accept the default instead choose Network Load Balancing

environment With this option there is an additional choice to Include sample environment (required on only

one of the application servers) This is because when you install the application server it connects to the

database server and creates the sample environment (EnvironmentShell) Installing the sample

environment is required on only one application server and you may choose which one

In the Virtual Name field enter the virtual IP address virtual name in the default properties

2 Installing Planning and Consolidation Servers

29 Installing the Server in a Multiserver Configuration

2654 CUSTOMER 2012-06-13

3 After Installing Planning and Consolidation Servers

31 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 28]

2 Configure the Planning and Consolidation NET and application server to ensure that it and its

related services function properly and reliably For more information see Configuring the Planning and

Consolidation NET Application Server [page 29]

3 Optional configuration steps [page 30]

1 To ensure proper functioning of the Management Console create an SQL user and modify

the System DSN and IIS to reflect those user credentials See Enabling Management Console [page

30]

2 Configure custom ODBC logging for the default Web site For details of how to configure

custom logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web

Site [page 31]

3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC

Data Source [page 32]

4 Modify the default access rights to the Management Console By default users in Active

Directory can access the Management Console with whatever rights they have been granted

on the server For information about removing default access and creating a group that can

access the console see Removing Default Access to the Console [page 32]

5 Add authorized users or groups to the group that can access the Management Console We

recommend that you only grant Management Console access to system administrators

Planning and Consolidation users should not have any access For more information see

Management Console Access Control [page 33]

6 Configure the use of client certificates for authentication See Using Client Certificates [page

34]

4 Take the following steps to set up security

If you are defining security and application structure continue with step 5

3 After Installing Planning and Consolidation Servers

31 Post-Installation Steps

2012-06-13 CUSTOMER 2754

If you want to designate someone other than the system administrator to manage security

and application structure log on to EnvironmentShell designate a user as a Primary

Administrator

This user must have Administration ‒ Environment and Security ‒ Define User task rights

so that he or she can add and delete environments and define user security

The Primary Administrator can continue with the next step (5)

5 From the machine on which you administer Planning and Consolidation install the

Administration client See Installing the Administration Client [page 37]

6 Start Planning and Consolidation Administration from the launch page

7 Select Connection Wizard and log on to EnvironmentShell

8 Create a new environment using EnvironmentShell as the source

9 Log on to the newly created environment and set up users teams and task profiles (You must

set up task profiles since there is no access to Planning and Consolidation tasks)

10 Set up your data access profiles and add users (or teams) to one or more data access profiles (You

must complete this step since there is no access to dimensions or members)

NOTE

To allow users to request and query large amounts of data you can edit the metabasexml file located

at CWindowssystem32inetsrv Set the following parameters to the stated values

ASPBUFFERINGLIMIT = 10485760

MAXREQUESTENTITYALLOWED = 10485760

32 Connecting to Solution Manager Diagnostics

NOTE

You only need to perform the steps in this section if you have a SAP Solution Manager licence

The diagnostics functions in SAP Solution Manager allow identification analysis and resolution of

problems This procedure provides the steps required to connect Planning and Consolidation to

Solution Manager Diagnostics

Procedure

1 Install the Diagnostics Agent according to SAP Note 1234387 on all servers where application servers

are installed

NOTE

Installation files for Diagnostics Agent are available on Service Marketplace by navigating to

Support Packages and Patches mdash Entry by Application Group SAP Technology Components SAP

SOLUTION MANAGER SAP SOLUTION MANAGER 70 EHP 1 Entry by Component Agents

for managed systems DIAGNOSTICS AGENT 711

3 After Installing Planning and Consolidation Servers

32 Connecting to Solution Manager Diagnostics

2854 CUSTOMER 2012-06-13

Download the installation file based on the 64-bit Windows Server system landscape

2 To access the DBA Cockpit you must create a user account with sufficient rights on all Windows

Servers where Microsoft SQL Server is installed Do the following

1 Start Computer Management then select Action New User

2 Create a new user

3 Right-click on the user then choose Properties On the Member Of tab select Add

4 Add the group SQLServerltReleasegtSQLAgentUser$ltDomain or hostnamegt$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 httpsservicesapcom~sapidb011000358700000074392009E and follow

the chapters that apply to Planning and Consolidation

33 Configuring the Planning and Consolidation NET Application Servers

Procedure

Modifying machineconfig Files

To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock

occurrences that would cause the application server to ldquosleeprdquo and not process anymore you can

modify the machineconfig file which resides in the WINDOWSMicrosoftNETFramework64

v4030319Config directory

1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to

specify whether to automatically configure settings to achieve optimal performance based on the

machine configuration You can set this attribute to True or False

For more information see httpmsdnmicrosoftcomen-uslibrary7w2sway1aspx

2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the

Planning and Consolidation application) or Machineconfig (for all applications including

Planning and Consolidation) to ensure the validationKey and decryptionKey keys have the same

value on all application servers This way when the authentication cookie is checked the

authentication ticket used on one server can still be valid on another server

For more information and sample Visual Basic code for generating random key values see http

msdnmicrosoftcomen-uslibraryms998288aspx

3 After Installing Planning and Consolidation Servers

33 Configuring the Planning and Consolidation NET Application Servers

2012-06-13 CUSTOMER 2954

paght000007_webfarmdeploymentconsiderations and httpmsdnmicrosoftcomen-us

libraryms998310aspx

34 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 30]

2 Configure custom ODBC logging for the default Web site For details of how to configure custom

logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page

31]

3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC Data

Source [page 32]

4 Modify the default access rights to the Management Console By default users in Active Directory

can access the Management Console with whatever rights they have been granted on the server

For information about removing default access and creating a group that can access the console

see Removing Default Access to the Console [page 32]

5 Add authorized users or groups to the group that can access the Management Console We

recommend that you only grant Management Console access to system administrators Planning

and Consolidation users should not have any access For more information see Management Console

Access Control [page 33]

6 Configure the use of client certificates for authentication See Using Client Certificates [page 34]

341 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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3054 CUSTOMER 2012-06-13

NOTE

Without these updates the Management Console does work but some functionality (specifically

User Activity and Service Status) does not work as expected

Should you need to uninstall Planning and Consolidation we recommend that you reset the

Active Log Format field in IIS to W3C Extended Log File Format

342 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 ApplicationHostconfig set the property customLogPluginClsid to the value FF16065B-

DE82-11CF-BC0A-00AA006111E0 Set the logFormat to Custom You can find this in the ltlogFilegt

node in ApplicationHostconfig as shown here

ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0

logFormat=Custom gt

Use the following AppCmds to configure IIS to use ODBC logging for the default Web site

appcmd site set sitenameDefault Web Site

logFilecustomLogPluginClsidFF16065B-DE82-11CF-BC0A-00AA006111E0

appcmd site set sitenameDefault Web Site logFilelogFormatCustom

Configuring ODBC Logging Parameters in ApplicationHostconfig

Configure ApplicationHostconfig to contain the database table information as set up in the Microsoft

Support article specified in the Prerequisites section Configure these settings in the ltodbcLogginggt

node under ltsystemwebServergt

EXAMPLE

ltlocation path=Default Web Sitegt

ltsystemwebServergt

ltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog

userName=Username password=mypassword gt

ltsystemwebServergt

ltlocationgt

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3154

Use the following AppCmds to configure these attributes for the default Web site

appcmd set config Default Web Site sectionodbcLogging

dataSourceBPC_ManagementDSN commitappHost

appcmd set config Default Web Site sectionodbcLogging tableNameBPCLog

commitappHost

appcmd set config Default Web Site sectionodbcLogging userNameUsername

commitappHost

appcmd set config Default Web Site sectionodbcLogging passwordmypassword

commitappHost

NOTE

You cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must

use the SQL Server ODBC driver For more information see the Microsoft Knowledge Base article

931202 The requirements for using the ODBC logging feature in IIS

343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2

ProcedureThis procedure describes how to set up an ODBC data source for the Management Console in Windows

Server 2008 or Windows Server 2008 R2

Proceed as follows

1 Open ODBC Connection Manager

2 On the System DSN tab page add a new DSN

Choose Add

Choose SQL Server as the driver

Choose Finish

3 In the Name and Description fields enter BPC_ManagementDSN

4 In the Server field enter the name of your SQL Server Choose Next

5 Leave the default settings and choose Next

6 Choose the Change the default database to field and enter AppServer Choose Next

7 Leave default settings and choose Next

8 Choose OK

344 Removing Default Access to the Console

NOTE

If you have chosen SAP BusinessObjects User Management System in the installation screen you

do not need to remove or configure access because the Management Console service always runs

with the System Admin ID account which is a member of the Administrators group

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3254 CUSTOMER 2012-06-13

ProcedureTo remove default access to the Management Console and create a group that does have access to the

console use the procedure described below

NOTE

Create your Management Console administrative group either on the server that hosts the

Management Console or in the Active Directory

1 In the context menu of the servers My Computer icon choose Manage

2 In the Computer Management dialog box choose Local Users and Groups Groups

NOTE

Alternatively you can perform analogous steps in Active Directory

3 In the 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

NOTE

This step is a necessary precursor to the completion of this procedure

10 In the Security dialog box click Copy to ensure that the System group retains its privileges

11 Remove access to the Management Console from all groups that should not have it

12 Choose Authentication in the center pane then disable Windows authentication

ResultUsers who have not been granted access to the Management Console can still open the Management

Console Web page but it contains no data or menu options This does not affect the access that a user

would otherwise have to Planning and Consolidation

345 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 32] Their rights in

Active Directory determine what they can access in the Console

By default any member of the Administrators Active Directory group on the application server or

domain has full access to all of the features of the Console except the Planning and Consolidation

logging area Access to Planning and Consolidation logging is controlled within the Planning and

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3354

Consolidation Administration Client task security The user must be granted View system logs task

privileges For more information see the SAP Library Planning and Consolidation Administrators Guide in

httpservicesapcominstguidesepm-bpc 100 version for the Microsoft platform

Your IT policy determines whether you grant access by group or user You may wish to create several

levels of Console users (read-only users for example) in your environment

To grant or limit access to users or groups you can add or remove the following privileges from the

areas described in this table

Privilege Rights Management Area

Task Manager and Kill Process Administrators group on application server or domain

Performance Monitor Counters Administrators group on application server or domain Power Users group on application server or domain Performance Monitor Users group on application server

Microsoft Analysis Services performance monitoring

Administrators group on application server or domain

Microsoft SQL Server Monitoring (performance counters and statistics)

Administrators group on application server or domain

346 Using Client Certificates

To enable the use of client certificates in Planning and Consolidation you must follow several manual

steps

NOTE

Planning 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 httptechnetmicrosoftcomen-us

librarycc753810aspx

For more information about configuring the client certificate mapping authentication see http

technetmicrosoftcomen-uslibrarycc732996(WS10)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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3454 CUSTOMER 2012-06-13

This option allows you to use a client certificate or username and password (Basic

authentication) to connect to Planning and Consolidation

2 Enable anonymous authentication

1 In the IIS Manager expand the node of the Planning and Consolidation web site

2 Select the ManagementConsole directory (ltWebsitegtManagementConsole) to open the

ManagementConsole home page

3 Double-click Authentication and enable Anonymous Authentication

4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way

as in step 3

5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the same

way as in step 3

3 Change the web configuration settings

1 Open the ltPC_MSgtWebsrvrWebBPCwebconfig file

2 Find the text clientCredentialType=Windows

3 Change value of clientCredentialType to None (clientCredentialType=None)

4 Open the PC_MSWebsrvrWebPOASBCwebconfig file Repeat steps 2 and 3

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3554

This page is left blank for documents that are printed on both sides

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

The installation of the Planning and Consolidation Administration Client allows administrators to

build and maintain Planning and Consolidation environments and models and administer security

All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions

add-in for Microsoft Office for more information see the SAP BusinessObjects EPM solutions add-in for

Microsoft Office help

NOTE

You must update the Administration Client to the same version as the server

If your PC is on a different domain than your server you must set the Internet Explorer

Security Zone value of the Planning and Consolidation client to prompt for user name and

password Otherwise the Planning and Consolidation Start Page does not display

41 Installing the Administration Client

Prerequisites

NOTE

For a definitive list of system requirements see the Product Availability Matrix on SAP Service

Marketplace at httpservicesapcompam Search on Planning and Consolidation

The following list describes the minimum software requirements

Microsoft Internet Explorer 70 or 80

Microsoft Office 2007 or 2010

NET Framework 20 or higher (install any required NET Framework Hotfixes by referring to

httpsupportmicrosoftcomkb)

Pentium IV (1 GHz CPU)

512 MB RAM

100 MB of free hard disk space in the My Documents folder

20 MB of free hard disk space for the installed Administration files

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

41 Installing the Administration Client

2012-06-13 CUSTOMER 3754

NOTE

We recommend that you install all of the latest Microsoft Windows hotfixes prior to installing

the Administration client For information about which hotfixes to install see http

updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us

ProcedureThe following procedure describes how to install the Administration Client on to an administratorrsquos

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 AddRemove Programs in the Windows Control Panel

3 Point your browser to the Planning and Consolidation Web at httpltPC_serverportgtsap

bpcweb

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

42 Installing the EPM Add-in

The Planning and Consolidation installation media does not contain the EPM addin setup program

You must download the most recent version of the full setup (EPM Add-inexe) from the Service

Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPC

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

43 Using the Client Auto Update Program

If Planning and Consolidation version 100 or later is installed you can use the Client Auto Update

program to set up the server so that it determines if an upgrade for a connecting Administration client

is necessary

The following describes the use of the auto update program for the Administration Client and the EPM

add-in

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

42 Installing the EPM Add-in

3854 CUSTOMER 2012-06-13

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 37]

To use the Client Auto Update program for the Administration Client proceed as follows

1 From the Server Manager select Options Client Options

2 Select Admin Update

3 If users without administrator rights on their machines use the auto update enter an administrator

ID and password in the Admin ID and Admin password fields respectively The Admin ID should be a

member of the local administrators group on all the computers running the auto update This

setting is not needed if all users have administrator rights on their machines

4 Select Update

For the EPM Add-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 Optionshellip 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 Market Place (SMP) at httpservicesapcom

All support packages and patches are available from the SMP as a zip file

EPMEXCLCLNTltSPLgtzip is for a support package

EPMEXCLCLNTltSPLgtPltPLgtzip 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 ltSP versiongtmsp

EPM Addin Support Package ltSP versiongtxml

For a patch these files are

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

2012-06-13 CUSTOMER 3954

EPM Addin Patch ltpatch numbergtmsp

EPM Addin Patch ltpatch numbergtxml

2 Unzip the zip file and extract the two files to the application server folder (WebsrvrWebBPC

Installation)

3 From the Server Manager select Options Client Options

The system lists the available packages Select the package that you want to use for the autoupdate

You can set a different update policy for each package listed

EXAMPLE

The following table illustrates some possible situations assuming that you have installed the

first full version (V1)

Available maintenance packages

V2-user updateV3-force updateV4-force updateV5-user update

V5-user update V5-user updateV6-auto updateV7-force update

Minimum Required Version

V4 V4 V7

Notification A prompt tells the user to install maintenance package V4 using the Forced Update behavior

If User Update is enabled the prompt informs the user that maintenance package V5 is available

A prompt tells the user to install maintenance package V7 using the Forced Update behavior

New Version V4 V4 or V5 V7

If you change the update policy for any package click Update to complete the change

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

4054 CUSTOMER 2012-06-13

5 Connection Issues

You may experience connection problems with ports the proxy server or programs and settings that

interact with these components If you have any issues related to connection review the following

recommendations and troubleshooting tips

51 Checking for Open Ports

You must ensure that all required ports are open for inboundoutbound 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 431181836 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

NOTE

You can use the following site to scan for the normal ports It allows you to manually enter a port

number to test

httpwwwmyserverorgportsniffasp

You can change the name of a port

52 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 Explorer Tools Internet Options Connections LAN Settings ) or at the server level

Enabling content filtering on the proxy server or firewall may cause connection problems

If external users are having trouble connecting to the server make sure the proxy server connects

using a fully qualified domain name Fully qualified domain names typically resolve both internal

and external IP addresses

Each secure Planning and Consolidation server name must be identified on the proxy server

Proxy servers may or may not require authentication which could conflict with Planning and

Consolidation authentication Do not use authentication on the proxy server The system

5 Connection Issues

51 Checking for Open Ports

2012-06-13 CUSTOMER 4154

synchronizes the user name and password on the remote server with the local user name and

password

NOTE

For more information about setting up an ISA proxy server contact SAP Support to request a

copy of Setting up ISA Proxy Server White Paper

Internet Explorer Settings 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

5 Connection Issues

52 Proxy Server and Firewall Issues

4254 CUSTOMER 2012-06-13

6 Installing Planning and Consolidation with Two Active Directory Domains

To set up a Planning and Consolidation 10 application server in a hosted environment and use your

own domain users follow this procedure In general you install Planning and Consolidation on the

host domain use the host domain account and assign it to the Planning and Consolidation users

SysAdmin Admin and Users Then you accept one way trust (the host domain trusts your domain)

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

6 Installing Planning and Consolidation with Two Active Directory Domains

2012-06-13 CUSTOMER 4354

This page is left blank for documents that are printed on both sides

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

This section describes best practices and instructions for installing Planning and Consolidation in a

Terminal Services or Citrix Server deployment

71 Terminal Services Home Directories

We recommend using Terminal Server home directories rather than using the userrsquos 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

72 System Requirements

The Citrix server should be one of the following systems

XenApp 5 Enterprise

XenApp 5 Platinum

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 37])

73 Installing Planning and Consolidation

Prerequisites

The server installation files have been downloaded from SAP Service Marketplace and installed

Procedure

The following steps outline how to install the Planning and Consolidation clients in a Terminal Services

(TS) or Citrix Server deployment

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

71 Terminal Services Home Directories

2012-06-13 CUSTOMER 4554

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 userinstall

4 Open a browser and connect to the URL httpltPC_serverportgtsapbpcweb

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 userexecute 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 Iexploreexe http(s)

ltServerNamegt-NetBIOS or FQDNsapbpcweb

To publish Planning and Consolidation Administration CProgram FilesPC_MS

BPCAdminMainexe

74 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 userrsquos desktop) must be moved to the All UsersDesktop folder

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

74 Creating a Shortcut to the Launch Page

4654 CUSTOMER 2012-06-13

8 Installing SSIS Custom Tasks

This section provides background information and instructions for installing SQL Server Integration

Services (SSIS) for SQL Server 2008 and SQL Server 2012

The Planning and Consolidation Data Manager component supports and uses SSIS Since SQL Server

2008 and SQL Server 2012 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

81 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 Filelistxml 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

OSoftSetupexe ‒ 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 or OSoftSSIS2012_Client on the client machine followed by the SQL Server

version If you want to use SQL 2008 Tasks under the SQL 2012 environment you must install

OSoftSSIS2008_Client on the application server For detailed information see SAP Note 1707410

You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package by extracting

OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPC

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 or

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4754

OSoftSSIS2012_Client for creating a COM+ application For more information see Before You Modify

the SSIS Packages [page 50] and Setup of a COM+ Application on the Application Server [page 51]

Bin folder

This folder contains the following components

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCCachedll Planning and Consolidation Cache file

BPCDataFlowPackagedll or BPCDataFlowPackage2012dll

BPCDMdll

BPCDMTaskMaindll COM+ component

BPCFilePreviewdll

BPCGacUtil_20exe System File

BPCGacUtil_40exe System File

BPCImpersonatordll Planning and Consolidation Impersonator

BPCLogicdll

BPCScriptdll

BPCServerZipdll

BPCServiceResdll

BPCTransferMembersdll

BPCWriteBackdll

InteropDTSdll

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

4854 CUSTOMER 2012-06-13

Name Remark

OSoftAdminServerdll

OSoftAuditdll

OSoftComLibServerdll

OSoftCommonResQrydll

OSoftConfigurationdll

OSoftCustomXMLSvrdll

OSoftDatabaseADMINdll

OSoftDatabaseSYSADMINdll

OSoftDatabaseSYSADMINDMdll

OSoftDatabaseUSERdll

OSoftDMDTSXExecutedll or OSoftDMDTSXExecute2012dll

OSoftDMTaskFormdll

OSoftDMTaskMaindll

OSoftDMToolsdll

OSoftFileManagedll

OSoftLoggingdll

OSoftLogWriterdll

OSoftMetaDatadll

OSoftSQEdll

OSoftSystemConfigdll

OutlookSoftconfig Configuration file to connect DB server

XceedCompressiondll XceedZip file

XceedCompressionFormatsdll XceedZip file

XceedFileSystemdll XceedZip file

XceedZipdll XceedZip file

Config folder

This folder has FileListxml 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 FileListxml 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

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4954

OSoftSetupexe

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

NOTE

If you installed the OSoftSSIS2008_Client or OSoftSSIS2012_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

Resources Folder

This folder contains the BPCServicesdll and BPCServiceUIdll files which contain resource text

Only English resources are included for the SSIS custom tasks

82 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

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008 and 2012 respectively

8 Installing SSIS Custom Tasks

82 Before You Modify the SSIS Packages

5054 CUSTOMER 2012-06-13

Name Remark

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012 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

lthellipgtOSoftSSIS2008_Clientbin or lthellipgtOSoftSSIS2012_Clientbin

On the Planning and Consolidation application server

ltdrivegtWebsrvrbin

2 Paste these files into the folder 100DTSTasks for SQL Server 2008 or into 110DTSTasks for

SQL Server 2012 For example if you install your SQL 2008 server or R2 on CProgram Files

Microsoft SQL Server paste all files into the CProgram Files (x86)Microsoft SQL Server

100DTSTasks folder

In Integration Services set the property Run64BitRunTime to True

83 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 or OSoftSSIS2012_Client on the

application server

8 Installing SSIS Custom Tasks

83 Setup of a COM+ Application on the Application Server

2012-06-13 CUSTOMER 5154

Typographic Conventions

Example Description

ltgt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example Enter your ltUser Namegt

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 httpwwwsapcom

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

5254 CUSTOMER 2012-06-13

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

  • SAP BusinessObjects Planning and Consolidation 100
    • Table of Contents
    • 1 Introduction
      • 11 SAP Notes for the Installation
      • 12 Naming Conventions
        • 2 Installing Planning and Consolidation Servers
          • 21 Basic Steps
          • 22 Prerequisites
          • 23 Before Starting the Planning and Consolidation Server Installation
          • 24 Logging on to Servers
          • 25 Service-level Accounts
          • 26 Standard and Advanced Settings
          • 27 Installing the Prerequisites
            • 271 Installing the Prerequisites ndash Basic Steps
            • 272 Installing the Operating System
            • 273 Installing the SQL Server
            • 274 Installing Analysis Services
            • 275 Installing the Anti-Cross Site Scripting Library
              • 28 Installing on a Single Server
              • 29 Installing the Server in a Multiserver Configuration
                • 3 After Installing Planning and Consolidation Servers
                  • 31 Post-Installation Steps
                  • 32 Connecting to Solution Manager Diagnostics
                  • 33 Configuring the Planning and Consolidation NET Application Servers
                  • 34 Post-Installation Optional Configuration Steps
                    • 341 Enabling the Management Console
                    • 342 Setting Up ODBC Logging in IIS for the Default Web Site
                    • 343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2
                    • 344 Removing Default Access to the Console
                    • 345 Management Console Access Control
                    • 346 Using Client Certificates
                        • 4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office
                          • 41 Installing the Administration Client
                          • 42 Installing the EPM Add-in
                          • 43 Using the Client Auto Update Program
                            • 5 Connection Issues
                              • 51 Checking for Open Ports
                              • 52 Proxy Server and Firewall Issues
                                • 6 Installing Planning and Consolidation with Two Active Directory Domains
                                • 7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
                                  • 71 Terminal Services Home Directories
                                  • 72 System Requirements
                                  • 73 Installing Planning and Consolidation
                                  • 74 Creating a Shortcut to the Launch Page
                                    • 8 Installing SSIS Custom Tasks
                                      • 81 Composition of SSIS Custom Task Installation
                                      • 82 Before You Modify the SSIS Packages
                                      • 83 Setup of a COM+ Application on the Application Server
                                          • Copyright and trademarks
Page 16: Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

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 readwrite 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

26 Standard and Advanced Settings

The following tables describe the standard and advanced settings for the installation program After

the server is installed you can change these settings using the Server Manager

NOTE

When defining server names the name refers to the NetBIOS name IP address and fully qualified

domain names (FQDN)

Standard Settings

Standard settings are typically used for a single-server environment The following table describes each

setting

Server Option Value Description

SQL Database server name The name of the SQL DB server

OLAP server name The name of the OLAP server

File Share server name The default value is the name of the File Share server that should be the computer name

Local data path Where the data files are saved on the File Share server By default this is CPC_MSData

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

Server Option Value Description

SQL Server Name The name of the SQL DB server Defaults to the local server

2 Installing Planning and Consolidation Servers

26 Standard and Advanced Settings

1654 CUSTOMER 2012-06-13

Server Option Value Description

Instance name The SQL instance name If left blank the default instance is used

Port number The default port number for the SQL Server is 1433

Provider The only available value is SQL

Local path for EnvironmentShell 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 CPC_MSData

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 changesSee the Kerberos authentication settings section in the SAP Library Server Manager Guide on httpservicesapcominstguidesEPM-BPC

100 for the Microsoft Platform

Scheduler Server Name The name of the server used for scheduling usually the application server for example GMPV50072862B If you have multiple application servers select the appropriate one

NOTE

If the primary server stops working you must manually configure your application server database to froward requests to another application server

27 Installing the Prerequisites

271 Installing the Prerequisites ndash Basic Steps

Before installing your Planning and Consolidation server you must install the prerequisite Microsoft

software the operating system IIS SQL server analysis services ADOMDNET and MSXML This

section provides guidance on installing each component For specific versions required see

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 1754

Prerequisites [page 11] and the Product Availability Matrix on the SAP Service Marketplace at http

servicesapcompam Search on Planning and Consolidation

NOTE

To ensure a successful installation you must install the software in the order listed in this

procedure

Check all third-party infrastructure services to ensure that they are functioning and that their

authentication models are documented (stated) since you need to reference this information

during the installation These third-party services include IIS OLAP service SQL services and

Active Directory (AD)

We recommend not installing Microsoft Office on the application server

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

(UMCexe) on the Planning and Consolidation CD in a folder called UMC_100_INSTALLER When

you run the installation package the wizard guides you through the following steps

1 Choose a language for the UMC install wizard to use

2 Check that the prerequisite check status is Succeeded and click Next

3 When you are ready to install the UMC click Next on the welcome screen

4 Click I accept the License Agreement and then Next

5 Choose the destination directory for the UMC installation and click Next

6 Select the languages that you wish to install

7 Select the features that you want to install (POAFHelper dotnet is mandatory for Planning

and Consolidation)

8 On Start Installation click Next to complete the installation

2 Install the required operating system on the single-server computer or on each physical server for

a multiserver configuration See Installing the Operating System [page 19]

3 Install the latest service pack for your operating system To install this service pack go to http

wwwmicrosoftcom

4 From your operating systems media install IIS

5 From your SQL Server media install SQL Server and its required service packs and hot fixes See

Installing SQL Server [page 19]

6 From your SQL Server media install Analysis Services Enterprise Edition and its required service

packs and hot fixes See Installing Analysis Services [page 23]

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

1854 CUSTOMER 2012-06-13

7 On your application server install ADOMDNET The Planning and Consolidation zip file contains

the ADOMDNET installation package in the following locations

For SQL Server 2008 mdash BPC SetupServerSQLSERVER2008_ASADOMD10_x64msi

For SQL Server 2012 mdash BPC SetupServerSQLSERVER2012_ASADOMD11_x64msi

8 On your application server install MSXML 40 Service Pack 2 or later

The MSXML 40 SP2 installation package is contained in the Planning and Consolidation zip file at

the following location BPC SetupServermsxmlmsi

9 On your application server install Microsoft Visual C++ 2005 Runtime Libraries SP1

The Microsoft Visual C++ 2005 SP1 installation package is contained in the Planning and

Consolidation zip file at the following location BPC SetupServervcredist_x64exe

NOTE

The version of vcredist_x64exe in BPC SetupServer has been updated to 8061000 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 httpwwwmicrosoftcomdownloadsen

detailsaspxFamilyID=C06B8369-60DD-4B64-A44B-84B371EDE16Dampltdisplaylanggt=en

272 Installing the Operating System

Before installing the operating system make sure that you configure your server for NTFS

For a list of languages that are supported see the Product Availability Matrix on the SAP Service

Marketplace at httpservicesapcompam Search on Planning and Consolidation

Planning and Consolidation can support all servers with an operating system in any language

NOTE

Currently Planning and Consolidation does not support an operating system in bi-directional

languages such as Hebrew

ProcedureIf you are installing IIS 70 or 75 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

273 Installing the SQL Server

PrerequisitesDuring the installation procedure you have the opportunity to specify the location of the

EnvironmentShell database file Check that it is possible to access EnvironmentShell from the location

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 1954

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 CEnvironmentShelldb10) 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 a 2008 2008 R2 and 2012 SQL Server

SQL Server Considerations

We recommend installing all required components in sequence For example install the Operating

System (Windows Server) then enable IIS and ASPNET and install any Windows Server service

packs

IIS and NET Framework 40 are required on your application server

NOTE

If you encounter a 500 HTTP Error when trying to connect to the Planning and Consolidation

Web Client refer to Microsoft Support articles 2520479 and 2468871 for assistance

To reinforce security we recommend that you install the SQL server and SSAS components to a

nondefault instance of SQL Server

General Installation Steps

1 Launch the SQL Server Setup program entering a product key if necessary and accepting the license

terms

2 Choose Install to install the SQL support files

3 In Feature Selections select instance and shared features as indicated in the SQL Server Component

Options section below then choose Next

4 Review disc space requirements then choose Next

5 In Server Configuration Perform the following actions

1 In the Service Accounts tab enter a Planning and Consolidation sysadmin account for the SQL

Server Database Engine and the SQL Server Analysis services This is required so that the Planning

and Consolidation sysadmin can create and process the Planning and Consolidation database

because the Microsoft SQL server tries to back up or restore database with the privileged

account This account is also required during Backup Environment and Restore Environment in the

Server Manager

For a single-server environment this account is also required if the backup file is located in a

different domain machine because SQL tries to access the folders and files with this account

For the a multiple-server environment SQL server retrieves the information of backup file

from the application server and the account requires the folder access privilege for the

application server

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2054 CUSTOMER 2012-06-13

To ensure that you have the complete access privileges we recommend the Planning and

Consolidation sysadmin for this service account

2 In the Collation tab set the collation settings to SQL_Latin1_General_CP1_CI_AS

Choose Next

6 Set Database Engine Configuration options then choose Next

We recommend you choose Mixed mode (Windows authentication and SQL authentication) This allows you

to use a restrictive SQL ID that works with the drill-through feature If you must restrict SQL

authentication for security reasons you can define a specific parameter in your drill-through

queries If you do not need drill-through support or use it without leveraging SQL authentication

you can install the SQL Server in Windows-only mode

7 Accept the Analysis Services Configuration default options and the remaining default options of the

installation program

8 Choose Install to begin the installation with the options you have set

SQL Server Component 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

Server Component What to Install

SQL Server Database Engine Services

SSAS Server Analysis Services

Application Server The following Shared Features Client Tools Connectivity Integration Services Client Tools SDK

Custom Settings for the SQL Server

As of version 100 Planning and Consolidation supports the following new features for SQL Server 2008

SQL Server 2008 R2 and SQL Server 2012

Process Dimension

It is now possible to process a dimension with multiple selections At processing time the process

dimension module makes changed or added information for each dimension and process for all selected

dimensions and cubes in parallel

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 2154

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

NOTE

Setting 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 tblFactWBltappgt table

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 Microsoftreg SQL Servertrade

20052008 which you can download from wwwmicrosoftcom (search on ldquoTable Partitioningrdquo to find

all relevant articles)

After Installing SQL Server 2008 SQL Server 2008 R2 and SQL Server 2012

From SQL Server Configuration Manager confirm that the SQL Server Browser service is

running The browser service is required for Planning and Consolidation

From SQL Server Configuration Manager do the following

1 Select Protocols for ltInstanceNamegt then double-click TCPIP from the right side of the window

2 When prompted for the TCPIP Properties select IP Addresses You see two IPs that indicate the

localhost and external network interface machine

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2254 CUSTOMER 2012-06-13

3 If you want to use IP1 which indicates Server IP set Enabled to Yes and specify the TCP Port as

desired

4 Delete 0 from TCP Dynamic Ports Set IPAll - TCP Ports as desired (for example 1533)

RECOMMENDATION

We do not recommend using dynamic ports

In an SQL server the default instance has a listener which listens on a fixed port (TCP

port 1433) However for the named instance the port on which the SQL server listens is

random and dynamically selected when the named instance of the SQL server starts This

recommendation prevents any conflict problems

From the SQL Server Configuration Manager specify the client protocol options for the application

server

1 Select Client Protocols from the SQL Native Client Configuration folder

2 From the right side of the window double-click TCPIP The TCPIP 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

NOTE

We 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

274 Installing Analysis Services

ProcedureAfter you install SQL Server and its required service packs and hotfixes you must install SQL Server

Analysis Services and its required service packs and hotfixes

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 2354

NOTE

If you have migrated your Analysis Services repository to the SQL Server back up the database

that contains the repository before installing this release

To install Analysis Services for SQL Server 2008 SQL Server 2008 R2 or SQL Server 2012 follow the steps

and guidelines in httptechnetmicrosoftcomen-uslibraryms143219aspx

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 httpwwwmicrosoftcomdownloads

detailsaspxFamilyID=3be0488d-e7aa-4078-a050- ae39912d2e43ampdisplaylang=en

275 Installing the Anti-Cross Site Scripting Library

Procedure

Before installing Planning and Consolidation servers you must download the Anti-Cross Site Scripting

Library (version 42 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 AntiXSSLibraryDLL from the Microsoft Web

site at httpwwwmicrosoftcomdownloadendetailsaspxid=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 AntiXssLibrarydll

28 Installing on a Single Server

When you install all Planning and Consolidation server components on a single server you should

consider the following issues

Make sure the server has a minimum of 800 MB of hard disk space

Additional environment installations require more free disk space which is a minimum of two

times the uncompressed size of the environment files

When you install Planning and Consolidation on a single-server the system adds the following server

components

SQL Server

SQL Server Analysis Services (SSAS)

Application Server

FileShare server

Procedure

To install Planning and Consolidation on a single server take the following steps

1 Exit all Windows programs

2 Installing Planning and Consolidation Servers

28 Installing on a Single Server

2454 CUSTOMER 2012-06-13

2 Log on to the server with a local server user ID or domain user ID For more information see Logging

on to servers [page 14]

3 Make sure all prerequisite software is installed on the server For more information see Installing

the Prerequisites [page 17]

4 Obtain SAP Planning and Consolidation from the Downloads SAP Installations amp Upgrades area of

SAP Service Marketplace then extract the files and run StartUpexe

5 From the Server Install screen select Install the Planning and Consolidation server

6 From the Welcome screen choose Next

7 From the License Agreement page choose I accept the terms of the license agreement then choose Next

8 From the Installation Method page accept the default Single machine enter a system ID for the system

landscape directory (SLD) and choose Next

NOTE

Entering a system ID of the SLD is only required if you have a SAP Solution Manager license

If you do not have a SAP Solution Manager license you can leave this field empty

9 From the Authentication Method page choose the desired authentication method and choose Next

10 If you have chosen SAP BusinessObjects User Management System in the previous screen on the CMS

Authentication page enter the information required to log on to CMS as an administrator

The following information is required

Field Description

System name CMS system name (server nameport number) for example CMSServer6400

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

11 After entering the CMS administrator authentication details choose Next

12 From the Service type accounts page enter service-level account user IDs and passwords See Service-

Level Accounts [page 15]

13 After defining the IDs and passwords choose Next

14 From the Server Information page (see Standard and Advanced Settings [page 16]) do one of the following

Review the standard settings and choose Next

To set advanced settings choose the Advanced Settings button Enter the desired information

and choose Next

2 Installing Planning and Consolidation Servers

28 Installing on a Single Server

2012-06-13 CUSTOMER 2554

15 Specify the location and name of AntiXssLibrarydll See Installing the Anti-Cross Site Scripting Library [page

24]

Choose Next

16 Select destination folders for Programs and Data The Data files include Webfolders and FileDB

(published reports) and should be installed on a separate drive in a production environment This

recommendation reduces the hard disk IO time and helps to speed up SQL commands

Accept the defaults or make your selections then choose Next

17 Select the default values for the Web client The values are used to determine the default language

and region for the Web client when you connect to it You can change the values in the Planning

and Consolidation Server Manager

18 The installation process takes a few moments When it is complete choose Exit

19 A prompt is displayed to restart your computer Select OK to restart

20 Perform the steps in After Installing Planning and Consolidation Servers [page 27]

29 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 24]) with the following

exceptions

On the Installation Method page do not accept the default instead choose Network Load Balancing

environment With this option there is an additional choice to Include sample environment (required on only

one of the application servers) This is because when you install the application server it connects to the

database server and creates the sample environment (EnvironmentShell) Installing the sample

environment is required on only one application server and you may choose which one

In the Virtual Name field enter the virtual IP address virtual name in the default properties

2 Installing Planning and Consolidation Servers

29 Installing the Server in a Multiserver Configuration

2654 CUSTOMER 2012-06-13

3 After Installing Planning and Consolidation Servers

31 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 28]

2 Configure the Planning and Consolidation NET and application server to ensure that it and its

related services function properly and reliably For more information see Configuring the Planning and

Consolidation NET Application Server [page 29]

3 Optional configuration steps [page 30]

1 To ensure proper functioning of the Management Console create an SQL user and modify

the System DSN and IIS to reflect those user credentials See Enabling Management Console [page

30]

2 Configure custom ODBC logging for the default Web site For details of how to configure

custom logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web

Site [page 31]

3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC

Data Source [page 32]

4 Modify the default access rights to the Management Console By default users in Active

Directory can access the Management Console with whatever rights they have been granted

on the server For information about removing default access and creating a group that can

access the console see Removing Default Access to the Console [page 32]

5 Add authorized users or groups to the group that can access the Management Console We

recommend that you only grant Management Console access to system administrators

Planning and Consolidation users should not have any access For more information see

Management Console Access Control [page 33]

6 Configure the use of client certificates for authentication See Using Client Certificates [page

34]

4 Take the following steps to set up security

If you are defining security and application structure continue with step 5

3 After Installing Planning and Consolidation Servers

31 Post-Installation Steps

2012-06-13 CUSTOMER 2754

If you want to designate someone other than the system administrator to manage security

and application structure log on to EnvironmentShell designate a user as a Primary

Administrator

This user must have Administration ‒ Environment and Security ‒ Define User task rights

so that he or she can add and delete environments and define user security

The Primary Administrator can continue with the next step (5)

5 From the machine on which you administer Planning and Consolidation install the

Administration client See Installing the Administration Client [page 37]

6 Start Planning and Consolidation Administration from the launch page

7 Select Connection Wizard and log on to EnvironmentShell

8 Create a new environment using EnvironmentShell as the source

9 Log on to the newly created environment and set up users teams and task profiles (You must

set up task profiles since there is no access to Planning and Consolidation tasks)

10 Set up your data access profiles and add users (or teams) to one or more data access profiles (You

must complete this step since there is no access to dimensions or members)

NOTE

To allow users to request and query large amounts of data you can edit the metabasexml file located

at CWindowssystem32inetsrv Set the following parameters to the stated values

ASPBUFFERINGLIMIT = 10485760

MAXREQUESTENTITYALLOWED = 10485760

32 Connecting to Solution Manager Diagnostics

NOTE

You only need to perform the steps in this section if you have a SAP Solution Manager licence

The diagnostics functions in SAP Solution Manager allow identification analysis and resolution of

problems This procedure provides the steps required to connect Planning and Consolidation to

Solution Manager Diagnostics

Procedure

1 Install the Diagnostics Agent according to SAP Note 1234387 on all servers where application servers

are installed

NOTE

Installation files for Diagnostics Agent are available on Service Marketplace by navigating to

Support Packages and Patches mdash Entry by Application Group SAP Technology Components SAP

SOLUTION MANAGER SAP SOLUTION MANAGER 70 EHP 1 Entry by Component Agents

for managed systems DIAGNOSTICS AGENT 711

3 After Installing Planning and Consolidation Servers

32 Connecting to Solution Manager Diagnostics

2854 CUSTOMER 2012-06-13

Download the installation file based on the 64-bit Windows Server system landscape

2 To access the DBA Cockpit you must create a user account with sufficient rights on all Windows

Servers where Microsoft SQL Server is installed Do the following

1 Start Computer Management then select Action New User

2 Create a new user

3 Right-click on the user then choose Properties On the Member Of tab select Add

4 Add the group SQLServerltReleasegtSQLAgentUser$ltDomain or hostnamegt$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 httpsservicesapcom~sapidb011000358700000074392009E and follow

the chapters that apply to Planning and Consolidation

33 Configuring the Planning and Consolidation NET Application Servers

Procedure

Modifying machineconfig Files

To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock

occurrences that would cause the application server to ldquosleeprdquo and not process anymore you can

modify the machineconfig file which resides in the WINDOWSMicrosoftNETFramework64

v4030319Config directory

1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to

specify whether to automatically configure settings to achieve optimal performance based on the

machine configuration You can set this attribute to True or False

For more information see httpmsdnmicrosoftcomen-uslibrary7w2sway1aspx

2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the

Planning and Consolidation application) or Machineconfig (for all applications including

Planning and Consolidation) to ensure the validationKey and decryptionKey keys have the same

value on all application servers This way when the authentication cookie is checked the

authentication ticket used on one server can still be valid on another server

For more information and sample Visual Basic code for generating random key values see http

msdnmicrosoftcomen-uslibraryms998288aspx

3 After Installing Planning and Consolidation Servers

33 Configuring the Planning and Consolidation NET Application Servers

2012-06-13 CUSTOMER 2954

paght000007_webfarmdeploymentconsiderations and httpmsdnmicrosoftcomen-us

libraryms998310aspx

34 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 30]

2 Configure custom ODBC logging for the default Web site For details of how to configure custom

logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page

31]

3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC Data

Source [page 32]

4 Modify the default access rights to the Management Console By default users in Active Directory

can access the Management Console with whatever rights they have been granted on the server

For information about removing default access and creating a group that can access the console

see Removing Default Access to the Console [page 32]

5 Add authorized users or groups to the group that can access the Management Console We

recommend that you only grant Management Console access to system administrators Planning

and Consolidation users should not have any access For more information see Management Console

Access Control [page 33]

6 Configure the use of client certificates for authentication See Using Client Certificates [page 34]

341 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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3054 CUSTOMER 2012-06-13

NOTE

Without these updates the Management Console does work but some functionality (specifically

User Activity and Service Status) does not work as expected

Should you need to uninstall Planning and Consolidation we recommend that you reset the

Active Log Format field in IIS to W3C Extended Log File Format

342 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 ApplicationHostconfig set the property customLogPluginClsid to the value FF16065B-

DE82-11CF-BC0A-00AA006111E0 Set the logFormat to Custom You can find this in the ltlogFilegt

node in ApplicationHostconfig as shown here

ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0

logFormat=Custom gt

Use the following AppCmds to configure IIS to use ODBC logging for the default Web site

appcmd site set sitenameDefault Web Site

logFilecustomLogPluginClsidFF16065B-DE82-11CF-BC0A-00AA006111E0

appcmd site set sitenameDefault Web Site logFilelogFormatCustom

Configuring ODBC Logging Parameters in ApplicationHostconfig

Configure ApplicationHostconfig to contain the database table information as set up in the Microsoft

Support article specified in the Prerequisites section Configure these settings in the ltodbcLogginggt

node under ltsystemwebServergt

EXAMPLE

ltlocation path=Default Web Sitegt

ltsystemwebServergt

ltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog

userName=Username password=mypassword gt

ltsystemwebServergt

ltlocationgt

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3154

Use the following AppCmds to configure these attributes for the default Web site

appcmd set config Default Web Site sectionodbcLogging

dataSourceBPC_ManagementDSN commitappHost

appcmd set config Default Web Site sectionodbcLogging tableNameBPCLog

commitappHost

appcmd set config Default Web Site sectionodbcLogging userNameUsername

commitappHost

appcmd set config Default Web Site sectionodbcLogging passwordmypassword

commitappHost

NOTE

You cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must

use the SQL Server ODBC driver For more information see the Microsoft Knowledge Base article

931202 The requirements for using the ODBC logging feature in IIS

343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2

ProcedureThis procedure describes how to set up an ODBC data source for the Management Console in Windows

Server 2008 or Windows Server 2008 R2

Proceed as follows

1 Open ODBC Connection Manager

2 On the System DSN tab page add a new DSN

Choose Add

Choose SQL Server as the driver

Choose Finish

3 In the Name and Description fields enter BPC_ManagementDSN

4 In the Server field enter the name of your SQL Server Choose Next

5 Leave the default settings and choose Next

6 Choose the Change the default database to field and enter AppServer Choose Next

7 Leave default settings and choose Next

8 Choose OK

344 Removing Default Access to the Console

NOTE

If you have chosen SAP BusinessObjects User Management System in the installation screen you

do not need to remove or configure access because the Management Console service always runs

with the System Admin ID account which is a member of the Administrators group

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3254 CUSTOMER 2012-06-13

ProcedureTo remove default access to the Management Console and create a group that does have access to the

console use the procedure described below

NOTE

Create your Management Console administrative group either on the server that hosts the

Management Console or in the Active Directory

1 In the context menu of the servers My Computer icon choose Manage

2 In the Computer Management dialog box choose Local Users and Groups Groups

NOTE

Alternatively you can perform analogous steps in Active Directory

3 In the 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

NOTE

This step is a necessary precursor to the completion of this procedure

10 In the Security dialog box click Copy to ensure that the System group retains its privileges

11 Remove access to the Management Console from all groups that should not have it

12 Choose Authentication in the center pane then disable Windows authentication

ResultUsers who have not been granted access to the Management Console can still open the Management

Console Web page but it contains no data or menu options This does not affect the access that a user

would otherwise have to Planning and Consolidation

345 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 32] Their rights in

Active Directory determine what they can access in the Console

By default any member of the Administrators Active Directory group on the application server or

domain has full access to all of the features of the Console except the Planning and Consolidation

logging area Access to Planning and Consolidation logging is controlled within the Planning and

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3354

Consolidation Administration Client task security The user must be granted View system logs task

privileges For more information see the SAP Library Planning and Consolidation Administrators Guide in

httpservicesapcominstguidesepm-bpc 100 version for the Microsoft platform

Your IT policy determines whether you grant access by group or user You may wish to create several

levels of Console users (read-only users for example) in your environment

To grant or limit access to users or groups you can add or remove the following privileges from the

areas described in this table

Privilege Rights Management Area

Task Manager and Kill Process Administrators group on application server or domain

Performance Monitor Counters Administrators group on application server or domain Power Users group on application server or domain Performance Monitor Users group on application server

Microsoft Analysis Services performance monitoring

Administrators group on application server or domain

Microsoft SQL Server Monitoring (performance counters and statistics)

Administrators group on application server or domain

346 Using Client Certificates

To enable the use of client certificates in Planning and Consolidation you must follow several manual

steps

NOTE

Planning 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 httptechnetmicrosoftcomen-us

librarycc753810aspx

For more information about configuring the client certificate mapping authentication see http

technetmicrosoftcomen-uslibrarycc732996(WS10)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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3454 CUSTOMER 2012-06-13

This option allows you to use a client certificate or username and password (Basic

authentication) to connect to Planning and Consolidation

2 Enable anonymous authentication

1 In the IIS Manager expand the node of the Planning and Consolidation web site

2 Select the ManagementConsole directory (ltWebsitegtManagementConsole) to open the

ManagementConsole home page

3 Double-click Authentication and enable Anonymous Authentication

4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way

as in step 3

5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the same

way as in step 3

3 Change the web configuration settings

1 Open the ltPC_MSgtWebsrvrWebBPCwebconfig file

2 Find the text clientCredentialType=Windows

3 Change value of clientCredentialType to None (clientCredentialType=None)

4 Open the PC_MSWebsrvrWebPOASBCwebconfig file Repeat steps 2 and 3

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3554

This page is left blank for documents that are printed on both sides

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

The installation of the Planning and Consolidation Administration Client allows administrators to

build and maintain Planning and Consolidation environments and models and administer security

All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions

add-in for Microsoft Office for more information see the SAP BusinessObjects EPM solutions add-in for

Microsoft Office help

NOTE

You must update the Administration Client to the same version as the server

If your PC is on a different domain than your server you must set the Internet Explorer

Security Zone value of the Planning and Consolidation client to prompt for user name and

password Otherwise the Planning and Consolidation Start Page does not display

41 Installing the Administration Client

Prerequisites

NOTE

For a definitive list of system requirements see the Product Availability Matrix on SAP Service

Marketplace at httpservicesapcompam Search on Planning and Consolidation

The following list describes the minimum software requirements

Microsoft Internet Explorer 70 or 80

Microsoft Office 2007 or 2010

NET Framework 20 or higher (install any required NET Framework Hotfixes by referring to

httpsupportmicrosoftcomkb)

Pentium IV (1 GHz CPU)

512 MB RAM

100 MB of free hard disk space in the My Documents folder

20 MB of free hard disk space for the installed Administration files

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

41 Installing the Administration Client

2012-06-13 CUSTOMER 3754

NOTE

We recommend that you install all of the latest Microsoft Windows hotfixes prior to installing

the Administration client For information about which hotfixes to install see http

updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us

ProcedureThe following procedure describes how to install the Administration Client on to an administratorrsquos

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 AddRemove Programs in the Windows Control Panel

3 Point your browser to the Planning and Consolidation Web at httpltPC_serverportgtsap

bpcweb

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

42 Installing the EPM Add-in

The Planning and Consolidation installation media does not contain the EPM addin setup program

You must download the most recent version of the full setup (EPM Add-inexe) from the Service

Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPC

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

43 Using the Client Auto Update Program

If Planning and Consolidation version 100 or later is installed you can use the Client Auto Update

program to set up the server so that it determines if an upgrade for a connecting Administration client

is necessary

The following describes the use of the auto update program for the Administration Client and the EPM

add-in

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

42 Installing the EPM Add-in

3854 CUSTOMER 2012-06-13

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 37]

To use the Client Auto Update program for the Administration Client proceed as follows

1 From the Server Manager select Options Client Options

2 Select Admin Update

3 If users without administrator rights on their machines use the auto update enter an administrator

ID and password in the Admin ID and Admin password fields respectively The Admin ID should be a

member of the local administrators group on all the computers running the auto update This

setting is not needed if all users have administrator rights on their machines

4 Select Update

For the EPM Add-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 Optionshellip 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 Market Place (SMP) at httpservicesapcom

All support packages and patches are available from the SMP as a zip file

EPMEXCLCLNTltSPLgtzip is for a support package

EPMEXCLCLNTltSPLgtPltPLgtzip 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 ltSP versiongtmsp

EPM Addin Support Package ltSP versiongtxml

For a patch these files are

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

2012-06-13 CUSTOMER 3954

EPM Addin Patch ltpatch numbergtmsp

EPM Addin Patch ltpatch numbergtxml

2 Unzip the zip file and extract the two files to the application server folder (WebsrvrWebBPC

Installation)

3 From the Server Manager select Options Client Options

The system lists the available packages Select the package that you want to use for the autoupdate

You can set a different update policy for each package listed

EXAMPLE

The following table illustrates some possible situations assuming that you have installed the

first full version (V1)

Available maintenance packages

V2-user updateV3-force updateV4-force updateV5-user update

V5-user update V5-user updateV6-auto updateV7-force update

Minimum Required Version

V4 V4 V7

Notification A prompt tells the user to install maintenance package V4 using the Forced Update behavior

If User Update is enabled the prompt informs the user that maintenance package V5 is available

A prompt tells the user to install maintenance package V7 using the Forced Update behavior

New Version V4 V4 or V5 V7

If you change the update policy for any package click Update to complete the change

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

4054 CUSTOMER 2012-06-13

5 Connection Issues

You may experience connection problems with ports the proxy server or programs and settings that

interact with these components If you have any issues related to connection review the following

recommendations and troubleshooting tips

51 Checking for Open Ports

You must ensure that all required ports are open for inboundoutbound 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 431181836 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

NOTE

You can use the following site to scan for the normal ports It allows you to manually enter a port

number to test

httpwwwmyserverorgportsniffasp

You can change the name of a port

52 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 Explorer Tools Internet Options Connections LAN Settings ) or at the server level

Enabling content filtering on the proxy server or firewall may cause connection problems

If external users are having trouble connecting to the server make sure the proxy server connects

using a fully qualified domain name Fully qualified domain names typically resolve both internal

and external IP addresses

Each secure Planning and Consolidation server name must be identified on the proxy server

Proxy servers may or may not require authentication which could conflict with Planning and

Consolidation authentication Do not use authentication on the proxy server The system

5 Connection Issues

51 Checking for Open Ports

2012-06-13 CUSTOMER 4154

synchronizes the user name and password on the remote server with the local user name and

password

NOTE

For more information about setting up an ISA proxy server contact SAP Support to request a

copy of Setting up ISA Proxy Server White Paper

Internet Explorer Settings 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

5 Connection Issues

52 Proxy Server and Firewall Issues

4254 CUSTOMER 2012-06-13

6 Installing Planning and Consolidation with Two Active Directory Domains

To set up a Planning and Consolidation 10 application server in a hosted environment and use your

own domain users follow this procedure In general you install Planning and Consolidation on the

host domain use the host domain account and assign it to the Planning and Consolidation users

SysAdmin Admin and Users Then you accept one way trust (the host domain trusts your domain)

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

6 Installing Planning and Consolidation with Two Active Directory Domains

2012-06-13 CUSTOMER 4354

This page is left blank for documents that are printed on both sides

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

This section describes best practices and instructions for installing Planning and Consolidation in a

Terminal Services or Citrix Server deployment

71 Terminal Services Home Directories

We recommend using Terminal Server home directories rather than using the userrsquos 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

72 System Requirements

The Citrix server should be one of the following systems

XenApp 5 Enterprise

XenApp 5 Platinum

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 37])

73 Installing Planning and Consolidation

Prerequisites

The server installation files have been downloaded from SAP Service Marketplace and installed

Procedure

The following steps outline how to install the Planning and Consolidation clients in a Terminal Services

(TS) or Citrix Server deployment

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

71 Terminal Services Home Directories

2012-06-13 CUSTOMER 4554

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 userinstall

4 Open a browser and connect to the URL httpltPC_serverportgtsapbpcweb

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 userexecute 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 Iexploreexe http(s)

ltServerNamegt-NetBIOS or FQDNsapbpcweb

To publish Planning and Consolidation Administration CProgram FilesPC_MS

BPCAdminMainexe

74 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 userrsquos desktop) must be moved to the All UsersDesktop folder

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

74 Creating a Shortcut to the Launch Page

4654 CUSTOMER 2012-06-13

8 Installing SSIS Custom Tasks

This section provides background information and instructions for installing SQL Server Integration

Services (SSIS) for SQL Server 2008 and SQL Server 2012

The Planning and Consolidation Data Manager component supports and uses SSIS Since SQL Server

2008 and SQL Server 2012 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

81 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 Filelistxml 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

OSoftSetupexe ‒ 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 or OSoftSSIS2012_Client on the client machine followed by the SQL Server

version If you want to use SQL 2008 Tasks under the SQL 2012 environment you must install

OSoftSSIS2008_Client on the application server For detailed information see SAP Note 1707410

You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package by extracting

OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPC

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 or

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4754

OSoftSSIS2012_Client for creating a COM+ application For more information see Before You Modify

the SSIS Packages [page 50] and Setup of a COM+ Application on the Application Server [page 51]

Bin folder

This folder contains the following components

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCCachedll Planning and Consolidation Cache file

BPCDataFlowPackagedll or BPCDataFlowPackage2012dll

BPCDMdll

BPCDMTaskMaindll COM+ component

BPCFilePreviewdll

BPCGacUtil_20exe System File

BPCGacUtil_40exe System File

BPCImpersonatordll Planning and Consolidation Impersonator

BPCLogicdll

BPCScriptdll

BPCServerZipdll

BPCServiceResdll

BPCTransferMembersdll

BPCWriteBackdll

InteropDTSdll

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

4854 CUSTOMER 2012-06-13

Name Remark

OSoftAdminServerdll

OSoftAuditdll

OSoftComLibServerdll

OSoftCommonResQrydll

OSoftConfigurationdll

OSoftCustomXMLSvrdll

OSoftDatabaseADMINdll

OSoftDatabaseSYSADMINdll

OSoftDatabaseSYSADMINDMdll

OSoftDatabaseUSERdll

OSoftDMDTSXExecutedll or OSoftDMDTSXExecute2012dll

OSoftDMTaskFormdll

OSoftDMTaskMaindll

OSoftDMToolsdll

OSoftFileManagedll

OSoftLoggingdll

OSoftLogWriterdll

OSoftMetaDatadll

OSoftSQEdll

OSoftSystemConfigdll

OutlookSoftconfig Configuration file to connect DB server

XceedCompressiondll XceedZip file

XceedCompressionFormatsdll XceedZip file

XceedFileSystemdll XceedZip file

XceedZipdll XceedZip file

Config folder

This folder has FileListxml 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 FileListxml 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

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4954

OSoftSetupexe

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

NOTE

If you installed the OSoftSSIS2008_Client or OSoftSSIS2012_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

Resources Folder

This folder contains the BPCServicesdll and BPCServiceUIdll files which contain resource text

Only English resources are included for the SSIS custom tasks

82 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

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008 and 2012 respectively

8 Installing SSIS Custom Tasks

82 Before You Modify the SSIS Packages

5054 CUSTOMER 2012-06-13

Name Remark

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012 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

lthellipgtOSoftSSIS2008_Clientbin or lthellipgtOSoftSSIS2012_Clientbin

On the Planning and Consolidation application server

ltdrivegtWebsrvrbin

2 Paste these files into the folder 100DTSTasks for SQL Server 2008 or into 110DTSTasks for

SQL Server 2012 For example if you install your SQL 2008 server or R2 on CProgram Files

Microsoft SQL Server paste all files into the CProgram Files (x86)Microsoft SQL Server

100DTSTasks folder

In Integration Services set the property Run64BitRunTime to True

83 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 or OSoftSSIS2012_Client on the

application server

8 Installing SSIS Custom Tasks

83 Setup of a COM+ Application on the Application Server

2012-06-13 CUSTOMER 5154

Typographic Conventions

Example Description

ltgt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example Enter your ltUser Namegt

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 httpwwwsapcom

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

5254 CUSTOMER 2012-06-13

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

  • SAP BusinessObjects Planning and Consolidation 100
    • Table of Contents
    • 1 Introduction
      • 11 SAP Notes for the Installation
      • 12 Naming Conventions
        • 2 Installing Planning and Consolidation Servers
          • 21 Basic Steps
          • 22 Prerequisites
          • 23 Before Starting the Planning and Consolidation Server Installation
          • 24 Logging on to Servers
          • 25 Service-level Accounts
          • 26 Standard and Advanced Settings
          • 27 Installing the Prerequisites
            • 271 Installing the Prerequisites ndash Basic Steps
            • 272 Installing the Operating System
            • 273 Installing the SQL Server
            • 274 Installing Analysis Services
            • 275 Installing the Anti-Cross Site Scripting Library
              • 28 Installing on a Single Server
              • 29 Installing the Server in a Multiserver Configuration
                • 3 After Installing Planning and Consolidation Servers
                  • 31 Post-Installation Steps
                  • 32 Connecting to Solution Manager Diagnostics
                  • 33 Configuring the Planning and Consolidation NET Application Servers
                  • 34 Post-Installation Optional Configuration Steps
                    • 341 Enabling the Management Console
                    • 342 Setting Up ODBC Logging in IIS for the Default Web Site
                    • 343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2
                    • 344 Removing Default Access to the Console
                    • 345 Management Console Access Control
                    • 346 Using Client Certificates
                        • 4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office
                          • 41 Installing the Administration Client
                          • 42 Installing the EPM Add-in
                          • 43 Using the Client Auto Update Program
                            • 5 Connection Issues
                              • 51 Checking for Open Ports
                              • 52 Proxy Server and Firewall Issues
                                • 6 Installing Planning and Consolidation with Two Active Directory Domains
                                • 7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
                                  • 71 Terminal Services Home Directories
                                  • 72 System Requirements
                                  • 73 Installing Planning and Consolidation
                                  • 74 Creating a Shortcut to the Launch Page
                                    • 8 Installing SSIS Custom Tasks
                                      • 81 Composition of SSIS Custom Task Installation
                                      • 82 Before You Modify the SSIS Packages
                                      • 83 Setup of a COM+ Application on the Application Server
                                          • Copyright and trademarks
Page 17: Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

Server Option Value Description

Instance name The SQL instance name If left blank the default instance is used

Port number The default port number for the SQL Server is 1433

Provider The only available value is SQL

Local path for EnvironmentShell 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 CPC_MSData

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 changesSee the Kerberos authentication settings section in the SAP Library Server Manager Guide on httpservicesapcominstguidesEPM-BPC

100 for the Microsoft Platform

Scheduler Server Name The name of the server used for scheduling usually the application server for example GMPV50072862B If you have multiple application servers select the appropriate one

NOTE

If the primary server stops working you must manually configure your application server database to froward requests to another application server

27 Installing the Prerequisites

271 Installing the Prerequisites ndash Basic Steps

Before installing your Planning and Consolidation server you must install the prerequisite Microsoft

software the operating system IIS SQL server analysis services ADOMDNET and MSXML This

section provides guidance on installing each component For specific versions required see

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 1754

Prerequisites [page 11] and the Product Availability Matrix on the SAP Service Marketplace at http

servicesapcompam Search on Planning and Consolidation

NOTE

To ensure a successful installation you must install the software in the order listed in this

procedure

Check all third-party infrastructure services to ensure that they are functioning and that their

authentication models are documented (stated) since you need to reference this information

during the installation These third-party services include IIS OLAP service SQL services and

Active Directory (AD)

We recommend not installing Microsoft Office on the application server

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

(UMCexe) on the Planning and Consolidation CD in a folder called UMC_100_INSTALLER When

you run the installation package the wizard guides you through the following steps

1 Choose a language for the UMC install wizard to use

2 Check that the prerequisite check status is Succeeded and click Next

3 When you are ready to install the UMC click Next on the welcome screen

4 Click I accept the License Agreement and then Next

5 Choose the destination directory for the UMC installation and click Next

6 Select the languages that you wish to install

7 Select the features that you want to install (POAFHelper dotnet is mandatory for Planning

and Consolidation)

8 On Start Installation click Next to complete the installation

2 Install the required operating system on the single-server computer or on each physical server for

a multiserver configuration See Installing the Operating System [page 19]

3 Install the latest service pack for your operating system To install this service pack go to http

wwwmicrosoftcom

4 From your operating systems media install IIS

5 From your SQL Server media install SQL Server and its required service packs and hot fixes See

Installing SQL Server [page 19]

6 From your SQL Server media install Analysis Services Enterprise Edition and its required service

packs and hot fixes See Installing Analysis Services [page 23]

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

1854 CUSTOMER 2012-06-13

7 On your application server install ADOMDNET The Planning and Consolidation zip file contains

the ADOMDNET installation package in the following locations

For SQL Server 2008 mdash BPC SetupServerSQLSERVER2008_ASADOMD10_x64msi

For SQL Server 2012 mdash BPC SetupServerSQLSERVER2012_ASADOMD11_x64msi

8 On your application server install MSXML 40 Service Pack 2 or later

The MSXML 40 SP2 installation package is contained in the Planning and Consolidation zip file at

the following location BPC SetupServermsxmlmsi

9 On your application server install Microsoft Visual C++ 2005 Runtime Libraries SP1

The Microsoft Visual C++ 2005 SP1 installation package is contained in the Planning and

Consolidation zip file at the following location BPC SetupServervcredist_x64exe

NOTE

The version of vcredist_x64exe in BPC SetupServer has been updated to 8061000 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 httpwwwmicrosoftcomdownloadsen

detailsaspxFamilyID=C06B8369-60DD-4B64-A44B-84B371EDE16Dampltdisplaylanggt=en

272 Installing the Operating System

Before installing the operating system make sure that you configure your server for NTFS

For a list of languages that are supported see the Product Availability Matrix on the SAP Service

Marketplace at httpservicesapcompam Search on Planning and Consolidation

Planning and Consolidation can support all servers with an operating system in any language

NOTE

Currently Planning and Consolidation does not support an operating system in bi-directional

languages such as Hebrew

ProcedureIf you are installing IIS 70 or 75 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

273 Installing the SQL Server

PrerequisitesDuring the installation procedure you have the opportunity to specify the location of the

EnvironmentShell database file Check that it is possible to access EnvironmentShell from the location

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 1954

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 CEnvironmentShelldb10) 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 a 2008 2008 R2 and 2012 SQL Server

SQL Server Considerations

We recommend installing all required components in sequence For example install the Operating

System (Windows Server) then enable IIS and ASPNET and install any Windows Server service

packs

IIS and NET Framework 40 are required on your application server

NOTE

If you encounter a 500 HTTP Error when trying to connect to the Planning and Consolidation

Web Client refer to Microsoft Support articles 2520479 and 2468871 for assistance

To reinforce security we recommend that you install the SQL server and SSAS components to a

nondefault instance of SQL Server

General Installation Steps

1 Launch the SQL Server Setup program entering a product key if necessary and accepting the license

terms

2 Choose Install to install the SQL support files

3 In Feature Selections select instance and shared features as indicated in the SQL Server Component

Options section below then choose Next

4 Review disc space requirements then choose Next

5 In Server Configuration Perform the following actions

1 In the Service Accounts tab enter a Planning and Consolidation sysadmin account for the SQL

Server Database Engine and the SQL Server Analysis services This is required so that the Planning

and Consolidation sysadmin can create and process the Planning and Consolidation database

because the Microsoft SQL server tries to back up or restore database with the privileged

account This account is also required during Backup Environment and Restore Environment in the

Server Manager

For a single-server environment this account is also required if the backup file is located in a

different domain machine because SQL tries to access the folders and files with this account

For the a multiple-server environment SQL server retrieves the information of backup file

from the application server and the account requires the folder access privilege for the

application server

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2054 CUSTOMER 2012-06-13

To ensure that you have the complete access privileges we recommend the Planning and

Consolidation sysadmin for this service account

2 In the Collation tab set the collation settings to SQL_Latin1_General_CP1_CI_AS

Choose Next

6 Set Database Engine Configuration options then choose Next

We recommend you choose Mixed mode (Windows authentication and SQL authentication) This allows you

to use a restrictive SQL ID that works with the drill-through feature If you must restrict SQL

authentication for security reasons you can define a specific parameter in your drill-through

queries If you do not need drill-through support or use it without leveraging SQL authentication

you can install the SQL Server in Windows-only mode

7 Accept the Analysis Services Configuration default options and the remaining default options of the

installation program

8 Choose Install to begin the installation with the options you have set

SQL Server Component 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

Server Component What to Install

SQL Server Database Engine Services

SSAS Server Analysis Services

Application Server The following Shared Features Client Tools Connectivity Integration Services Client Tools SDK

Custom Settings for the SQL Server

As of version 100 Planning and Consolidation supports the following new features for SQL Server 2008

SQL Server 2008 R2 and SQL Server 2012

Process Dimension

It is now possible to process a dimension with multiple selections At processing time the process

dimension module makes changed or added information for each dimension and process for all selected

dimensions and cubes in parallel

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 2154

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

NOTE

Setting 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 tblFactWBltappgt table

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 Microsoftreg SQL Servertrade

20052008 which you can download from wwwmicrosoftcom (search on ldquoTable Partitioningrdquo to find

all relevant articles)

After Installing SQL Server 2008 SQL Server 2008 R2 and SQL Server 2012

From SQL Server Configuration Manager confirm that the SQL Server Browser service is

running The browser service is required for Planning and Consolidation

From SQL Server Configuration Manager do the following

1 Select Protocols for ltInstanceNamegt then double-click TCPIP from the right side of the window

2 When prompted for the TCPIP Properties select IP Addresses You see two IPs that indicate the

localhost and external network interface machine

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2254 CUSTOMER 2012-06-13

3 If you want to use IP1 which indicates Server IP set Enabled to Yes and specify the TCP Port as

desired

4 Delete 0 from TCP Dynamic Ports Set IPAll - TCP Ports as desired (for example 1533)

RECOMMENDATION

We do not recommend using dynamic ports

In an SQL server the default instance has a listener which listens on a fixed port (TCP

port 1433) However for the named instance the port on which the SQL server listens is

random and dynamically selected when the named instance of the SQL server starts This

recommendation prevents any conflict problems

From the SQL Server Configuration Manager specify the client protocol options for the application

server

1 Select Client Protocols from the SQL Native Client Configuration folder

2 From the right side of the window double-click TCPIP The TCPIP 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

NOTE

We 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

274 Installing Analysis Services

ProcedureAfter you install SQL Server and its required service packs and hotfixes you must install SQL Server

Analysis Services and its required service packs and hotfixes

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 2354

NOTE

If you have migrated your Analysis Services repository to the SQL Server back up the database

that contains the repository before installing this release

To install Analysis Services for SQL Server 2008 SQL Server 2008 R2 or SQL Server 2012 follow the steps

and guidelines in httptechnetmicrosoftcomen-uslibraryms143219aspx

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 httpwwwmicrosoftcomdownloads

detailsaspxFamilyID=3be0488d-e7aa-4078-a050- ae39912d2e43ampdisplaylang=en

275 Installing the Anti-Cross Site Scripting Library

Procedure

Before installing Planning and Consolidation servers you must download the Anti-Cross Site Scripting

Library (version 42 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 AntiXSSLibraryDLL from the Microsoft Web

site at httpwwwmicrosoftcomdownloadendetailsaspxid=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 AntiXssLibrarydll

28 Installing on a Single Server

When you install all Planning and Consolidation server components on a single server you should

consider the following issues

Make sure the server has a minimum of 800 MB of hard disk space

Additional environment installations require more free disk space which is a minimum of two

times the uncompressed size of the environment files

When you install Planning and Consolidation on a single-server the system adds the following server

components

SQL Server

SQL Server Analysis Services (SSAS)

Application Server

FileShare server

Procedure

To install Planning and Consolidation on a single server take the following steps

1 Exit all Windows programs

2 Installing Planning and Consolidation Servers

28 Installing on a Single Server

2454 CUSTOMER 2012-06-13

2 Log on to the server with a local server user ID or domain user ID For more information see Logging

on to servers [page 14]

3 Make sure all prerequisite software is installed on the server For more information see Installing

the Prerequisites [page 17]

4 Obtain SAP Planning and Consolidation from the Downloads SAP Installations amp Upgrades area of

SAP Service Marketplace then extract the files and run StartUpexe

5 From the Server Install screen select Install the Planning and Consolidation server

6 From the Welcome screen choose Next

7 From the License Agreement page choose I accept the terms of the license agreement then choose Next

8 From the Installation Method page accept the default Single machine enter a system ID for the system

landscape directory (SLD) and choose Next

NOTE

Entering a system ID of the SLD is only required if you have a SAP Solution Manager license

If you do not have a SAP Solution Manager license you can leave this field empty

9 From the Authentication Method page choose the desired authentication method and choose Next

10 If you have chosen SAP BusinessObjects User Management System in the previous screen on the CMS

Authentication page enter the information required to log on to CMS as an administrator

The following information is required

Field Description

System name CMS system name (server nameport number) for example CMSServer6400

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

11 After entering the CMS administrator authentication details choose Next

12 From the Service type accounts page enter service-level account user IDs and passwords See Service-

Level Accounts [page 15]

13 After defining the IDs and passwords choose Next

14 From the Server Information page (see Standard and Advanced Settings [page 16]) do one of the following

Review the standard settings and choose Next

To set advanced settings choose the Advanced Settings button Enter the desired information

and choose Next

2 Installing Planning and Consolidation Servers

28 Installing on a Single Server

2012-06-13 CUSTOMER 2554

15 Specify the location and name of AntiXssLibrarydll See Installing the Anti-Cross Site Scripting Library [page

24]

Choose Next

16 Select destination folders for Programs and Data The Data files include Webfolders and FileDB

(published reports) and should be installed on a separate drive in a production environment This

recommendation reduces the hard disk IO time and helps to speed up SQL commands

Accept the defaults or make your selections then choose Next

17 Select the default values for the Web client The values are used to determine the default language

and region for the Web client when you connect to it You can change the values in the Planning

and Consolidation Server Manager

18 The installation process takes a few moments When it is complete choose Exit

19 A prompt is displayed to restart your computer Select OK to restart

20 Perform the steps in After Installing Planning and Consolidation Servers [page 27]

29 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 24]) with the following

exceptions

On the Installation Method page do not accept the default instead choose Network Load Balancing

environment With this option there is an additional choice to Include sample environment (required on only

one of the application servers) This is because when you install the application server it connects to the

database server and creates the sample environment (EnvironmentShell) Installing the sample

environment is required on only one application server and you may choose which one

In the Virtual Name field enter the virtual IP address virtual name in the default properties

2 Installing Planning and Consolidation Servers

29 Installing the Server in a Multiserver Configuration

2654 CUSTOMER 2012-06-13

3 After Installing Planning and Consolidation Servers

31 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 28]

2 Configure the Planning and Consolidation NET and application server to ensure that it and its

related services function properly and reliably For more information see Configuring the Planning and

Consolidation NET Application Server [page 29]

3 Optional configuration steps [page 30]

1 To ensure proper functioning of the Management Console create an SQL user and modify

the System DSN and IIS to reflect those user credentials See Enabling Management Console [page

30]

2 Configure custom ODBC logging for the default Web site For details of how to configure

custom logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web

Site [page 31]

3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC

Data Source [page 32]

4 Modify the default access rights to the Management Console By default users in Active

Directory can access the Management Console with whatever rights they have been granted

on the server For information about removing default access and creating a group that can

access the console see Removing Default Access to the Console [page 32]

5 Add authorized users or groups to the group that can access the Management Console We

recommend that you only grant Management Console access to system administrators

Planning and Consolidation users should not have any access For more information see

Management Console Access Control [page 33]

6 Configure the use of client certificates for authentication See Using Client Certificates [page

34]

4 Take the following steps to set up security

If you are defining security and application structure continue with step 5

3 After Installing Planning and Consolidation Servers

31 Post-Installation Steps

2012-06-13 CUSTOMER 2754

If you want to designate someone other than the system administrator to manage security

and application structure log on to EnvironmentShell designate a user as a Primary

Administrator

This user must have Administration ‒ Environment and Security ‒ Define User task rights

so that he or she can add and delete environments and define user security

The Primary Administrator can continue with the next step (5)

5 From the machine on which you administer Planning and Consolidation install the

Administration client See Installing the Administration Client [page 37]

6 Start Planning and Consolidation Administration from the launch page

7 Select Connection Wizard and log on to EnvironmentShell

8 Create a new environment using EnvironmentShell as the source

9 Log on to the newly created environment and set up users teams and task profiles (You must

set up task profiles since there is no access to Planning and Consolidation tasks)

10 Set up your data access profiles and add users (or teams) to one or more data access profiles (You

must complete this step since there is no access to dimensions or members)

NOTE

To allow users to request and query large amounts of data you can edit the metabasexml file located

at CWindowssystem32inetsrv Set the following parameters to the stated values

ASPBUFFERINGLIMIT = 10485760

MAXREQUESTENTITYALLOWED = 10485760

32 Connecting to Solution Manager Diagnostics

NOTE

You only need to perform the steps in this section if you have a SAP Solution Manager licence

The diagnostics functions in SAP Solution Manager allow identification analysis and resolution of

problems This procedure provides the steps required to connect Planning and Consolidation to

Solution Manager Diagnostics

Procedure

1 Install the Diagnostics Agent according to SAP Note 1234387 on all servers where application servers

are installed

NOTE

Installation files for Diagnostics Agent are available on Service Marketplace by navigating to

Support Packages and Patches mdash Entry by Application Group SAP Technology Components SAP

SOLUTION MANAGER SAP SOLUTION MANAGER 70 EHP 1 Entry by Component Agents

for managed systems DIAGNOSTICS AGENT 711

3 After Installing Planning and Consolidation Servers

32 Connecting to Solution Manager Diagnostics

2854 CUSTOMER 2012-06-13

Download the installation file based on the 64-bit Windows Server system landscape

2 To access the DBA Cockpit you must create a user account with sufficient rights on all Windows

Servers where Microsoft SQL Server is installed Do the following

1 Start Computer Management then select Action New User

2 Create a new user

3 Right-click on the user then choose Properties On the Member Of tab select Add

4 Add the group SQLServerltReleasegtSQLAgentUser$ltDomain or hostnamegt$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 httpsservicesapcom~sapidb011000358700000074392009E and follow

the chapters that apply to Planning and Consolidation

33 Configuring the Planning and Consolidation NET Application Servers

Procedure

Modifying machineconfig Files

To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock

occurrences that would cause the application server to ldquosleeprdquo and not process anymore you can

modify the machineconfig file which resides in the WINDOWSMicrosoftNETFramework64

v4030319Config directory

1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to

specify whether to automatically configure settings to achieve optimal performance based on the

machine configuration You can set this attribute to True or False

For more information see httpmsdnmicrosoftcomen-uslibrary7w2sway1aspx

2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the

Planning and Consolidation application) or Machineconfig (for all applications including

Planning and Consolidation) to ensure the validationKey and decryptionKey keys have the same

value on all application servers This way when the authentication cookie is checked the

authentication ticket used on one server can still be valid on another server

For more information and sample Visual Basic code for generating random key values see http

msdnmicrosoftcomen-uslibraryms998288aspx

3 After Installing Planning and Consolidation Servers

33 Configuring the Planning and Consolidation NET Application Servers

2012-06-13 CUSTOMER 2954

paght000007_webfarmdeploymentconsiderations and httpmsdnmicrosoftcomen-us

libraryms998310aspx

34 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 30]

2 Configure custom ODBC logging for the default Web site For details of how to configure custom

logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page

31]

3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC Data

Source [page 32]

4 Modify the default access rights to the Management Console By default users in Active Directory

can access the Management Console with whatever rights they have been granted on the server

For information about removing default access and creating a group that can access the console

see Removing Default Access to the Console [page 32]

5 Add authorized users or groups to the group that can access the Management Console We

recommend that you only grant Management Console access to system administrators Planning

and Consolidation users should not have any access For more information see Management Console

Access Control [page 33]

6 Configure the use of client certificates for authentication See Using Client Certificates [page 34]

341 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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3054 CUSTOMER 2012-06-13

NOTE

Without these updates the Management Console does work but some functionality (specifically

User Activity and Service Status) does not work as expected

Should you need to uninstall Planning and Consolidation we recommend that you reset the

Active Log Format field in IIS to W3C Extended Log File Format

342 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 ApplicationHostconfig set the property customLogPluginClsid to the value FF16065B-

DE82-11CF-BC0A-00AA006111E0 Set the logFormat to Custom You can find this in the ltlogFilegt

node in ApplicationHostconfig as shown here

ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0

logFormat=Custom gt

Use the following AppCmds to configure IIS to use ODBC logging for the default Web site

appcmd site set sitenameDefault Web Site

logFilecustomLogPluginClsidFF16065B-DE82-11CF-BC0A-00AA006111E0

appcmd site set sitenameDefault Web Site logFilelogFormatCustom

Configuring ODBC Logging Parameters in ApplicationHostconfig

Configure ApplicationHostconfig to contain the database table information as set up in the Microsoft

Support article specified in the Prerequisites section Configure these settings in the ltodbcLogginggt

node under ltsystemwebServergt

EXAMPLE

ltlocation path=Default Web Sitegt

ltsystemwebServergt

ltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog

userName=Username password=mypassword gt

ltsystemwebServergt

ltlocationgt

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3154

Use the following AppCmds to configure these attributes for the default Web site

appcmd set config Default Web Site sectionodbcLogging

dataSourceBPC_ManagementDSN commitappHost

appcmd set config Default Web Site sectionodbcLogging tableNameBPCLog

commitappHost

appcmd set config Default Web Site sectionodbcLogging userNameUsername

commitappHost

appcmd set config Default Web Site sectionodbcLogging passwordmypassword

commitappHost

NOTE

You cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must

use the SQL Server ODBC driver For more information see the Microsoft Knowledge Base article

931202 The requirements for using the ODBC logging feature in IIS

343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2

ProcedureThis procedure describes how to set up an ODBC data source for the Management Console in Windows

Server 2008 or Windows Server 2008 R2

Proceed as follows

1 Open ODBC Connection Manager

2 On the System DSN tab page add a new DSN

Choose Add

Choose SQL Server as the driver

Choose Finish

3 In the Name and Description fields enter BPC_ManagementDSN

4 In the Server field enter the name of your SQL Server Choose Next

5 Leave the default settings and choose Next

6 Choose the Change the default database to field and enter AppServer Choose Next

7 Leave default settings and choose Next

8 Choose OK

344 Removing Default Access to the Console

NOTE

If you have chosen SAP BusinessObjects User Management System in the installation screen you

do not need to remove or configure access because the Management Console service always runs

with the System Admin ID account which is a member of the Administrators group

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3254 CUSTOMER 2012-06-13

ProcedureTo remove default access to the Management Console and create a group that does have access to the

console use the procedure described below

NOTE

Create your Management Console administrative group either on the server that hosts the

Management Console or in the Active Directory

1 In the context menu of the servers My Computer icon choose Manage

2 In the Computer Management dialog box choose Local Users and Groups Groups

NOTE

Alternatively you can perform analogous steps in Active Directory

3 In the 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

NOTE

This step is a necessary precursor to the completion of this procedure

10 In the Security dialog box click Copy to ensure that the System group retains its privileges

11 Remove access to the Management Console from all groups that should not have it

12 Choose Authentication in the center pane then disable Windows authentication

ResultUsers who have not been granted access to the Management Console can still open the Management

Console Web page but it contains no data or menu options This does not affect the access that a user

would otherwise have to Planning and Consolidation

345 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 32] Their rights in

Active Directory determine what they can access in the Console

By default any member of the Administrators Active Directory group on the application server or

domain has full access to all of the features of the Console except the Planning and Consolidation

logging area Access to Planning and Consolidation logging is controlled within the Planning and

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3354

Consolidation Administration Client task security The user must be granted View system logs task

privileges For more information see the SAP Library Planning and Consolidation Administrators Guide in

httpservicesapcominstguidesepm-bpc 100 version for the Microsoft platform

Your IT policy determines whether you grant access by group or user You may wish to create several

levels of Console users (read-only users for example) in your environment

To grant or limit access to users or groups you can add or remove the following privileges from the

areas described in this table

Privilege Rights Management Area

Task Manager and Kill Process Administrators group on application server or domain

Performance Monitor Counters Administrators group on application server or domain Power Users group on application server or domain Performance Monitor Users group on application server

Microsoft Analysis Services performance monitoring

Administrators group on application server or domain

Microsoft SQL Server Monitoring (performance counters and statistics)

Administrators group on application server or domain

346 Using Client Certificates

To enable the use of client certificates in Planning and Consolidation you must follow several manual

steps

NOTE

Planning 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 httptechnetmicrosoftcomen-us

librarycc753810aspx

For more information about configuring the client certificate mapping authentication see http

technetmicrosoftcomen-uslibrarycc732996(WS10)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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3454 CUSTOMER 2012-06-13

This option allows you to use a client certificate or username and password (Basic

authentication) to connect to Planning and Consolidation

2 Enable anonymous authentication

1 In the IIS Manager expand the node of the Planning and Consolidation web site

2 Select the ManagementConsole directory (ltWebsitegtManagementConsole) to open the

ManagementConsole home page

3 Double-click Authentication and enable Anonymous Authentication

4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way

as in step 3

5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the same

way as in step 3

3 Change the web configuration settings

1 Open the ltPC_MSgtWebsrvrWebBPCwebconfig file

2 Find the text clientCredentialType=Windows

3 Change value of clientCredentialType to None (clientCredentialType=None)

4 Open the PC_MSWebsrvrWebPOASBCwebconfig file Repeat steps 2 and 3

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3554

This page is left blank for documents that are printed on both sides

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

The installation of the Planning and Consolidation Administration Client allows administrators to

build and maintain Planning and Consolidation environments and models and administer security

All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions

add-in for Microsoft Office for more information see the SAP BusinessObjects EPM solutions add-in for

Microsoft Office help

NOTE

You must update the Administration Client to the same version as the server

If your PC is on a different domain than your server you must set the Internet Explorer

Security Zone value of the Planning and Consolidation client to prompt for user name and

password Otherwise the Planning and Consolidation Start Page does not display

41 Installing the Administration Client

Prerequisites

NOTE

For a definitive list of system requirements see the Product Availability Matrix on SAP Service

Marketplace at httpservicesapcompam Search on Planning and Consolidation

The following list describes the minimum software requirements

Microsoft Internet Explorer 70 or 80

Microsoft Office 2007 or 2010

NET Framework 20 or higher (install any required NET Framework Hotfixes by referring to

httpsupportmicrosoftcomkb)

Pentium IV (1 GHz CPU)

512 MB RAM

100 MB of free hard disk space in the My Documents folder

20 MB of free hard disk space for the installed Administration files

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

41 Installing the Administration Client

2012-06-13 CUSTOMER 3754

NOTE

We recommend that you install all of the latest Microsoft Windows hotfixes prior to installing

the Administration client For information about which hotfixes to install see http

updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us

ProcedureThe following procedure describes how to install the Administration Client on to an administratorrsquos

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 AddRemove Programs in the Windows Control Panel

3 Point your browser to the Planning and Consolidation Web at httpltPC_serverportgtsap

bpcweb

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

42 Installing the EPM Add-in

The Planning and Consolidation installation media does not contain the EPM addin setup program

You must download the most recent version of the full setup (EPM Add-inexe) from the Service

Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPC

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

43 Using the Client Auto Update Program

If Planning and Consolidation version 100 or later is installed you can use the Client Auto Update

program to set up the server so that it determines if an upgrade for a connecting Administration client

is necessary

The following describes the use of the auto update program for the Administration Client and the EPM

add-in

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

42 Installing the EPM Add-in

3854 CUSTOMER 2012-06-13

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 37]

To use the Client Auto Update program for the Administration Client proceed as follows

1 From the Server Manager select Options Client Options

2 Select Admin Update

3 If users without administrator rights on their machines use the auto update enter an administrator

ID and password in the Admin ID and Admin password fields respectively The Admin ID should be a

member of the local administrators group on all the computers running the auto update This

setting is not needed if all users have administrator rights on their machines

4 Select Update

For the EPM Add-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 Optionshellip 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 Market Place (SMP) at httpservicesapcom

All support packages and patches are available from the SMP as a zip file

EPMEXCLCLNTltSPLgtzip is for a support package

EPMEXCLCLNTltSPLgtPltPLgtzip 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 ltSP versiongtmsp

EPM Addin Support Package ltSP versiongtxml

For a patch these files are

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

2012-06-13 CUSTOMER 3954

EPM Addin Patch ltpatch numbergtmsp

EPM Addin Patch ltpatch numbergtxml

2 Unzip the zip file and extract the two files to the application server folder (WebsrvrWebBPC

Installation)

3 From the Server Manager select Options Client Options

The system lists the available packages Select the package that you want to use for the autoupdate

You can set a different update policy for each package listed

EXAMPLE

The following table illustrates some possible situations assuming that you have installed the

first full version (V1)

Available maintenance packages

V2-user updateV3-force updateV4-force updateV5-user update

V5-user update V5-user updateV6-auto updateV7-force update

Minimum Required Version

V4 V4 V7

Notification A prompt tells the user to install maintenance package V4 using the Forced Update behavior

If User Update is enabled the prompt informs the user that maintenance package V5 is available

A prompt tells the user to install maintenance package V7 using the Forced Update behavior

New Version V4 V4 or V5 V7

If you change the update policy for any package click Update to complete the change

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

4054 CUSTOMER 2012-06-13

5 Connection Issues

You may experience connection problems with ports the proxy server or programs and settings that

interact with these components If you have any issues related to connection review the following

recommendations and troubleshooting tips

51 Checking for Open Ports

You must ensure that all required ports are open for inboundoutbound 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 431181836 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

NOTE

You can use the following site to scan for the normal ports It allows you to manually enter a port

number to test

httpwwwmyserverorgportsniffasp

You can change the name of a port

52 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 Explorer Tools Internet Options Connections LAN Settings ) or at the server level

Enabling content filtering on the proxy server or firewall may cause connection problems

If external users are having trouble connecting to the server make sure the proxy server connects

using a fully qualified domain name Fully qualified domain names typically resolve both internal

and external IP addresses

Each secure Planning and Consolidation server name must be identified on the proxy server

Proxy servers may or may not require authentication which could conflict with Planning and

Consolidation authentication Do not use authentication on the proxy server The system

5 Connection Issues

51 Checking for Open Ports

2012-06-13 CUSTOMER 4154

synchronizes the user name and password on the remote server with the local user name and

password

NOTE

For more information about setting up an ISA proxy server contact SAP Support to request a

copy of Setting up ISA Proxy Server White Paper

Internet Explorer Settings 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

5 Connection Issues

52 Proxy Server and Firewall Issues

4254 CUSTOMER 2012-06-13

6 Installing Planning and Consolidation with Two Active Directory Domains

To set up a Planning and Consolidation 10 application server in a hosted environment and use your

own domain users follow this procedure In general you install Planning and Consolidation on the

host domain use the host domain account and assign it to the Planning and Consolidation users

SysAdmin Admin and Users Then you accept one way trust (the host domain trusts your domain)

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

6 Installing Planning and Consolidation with Two Active Directory Domains

2012-06-13 CUSTOMER 4354

This page is left blank for documents that are printed on both sides

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

This section describes best practices and instructions for installing Planning and Consolidation in a

Terminal Services or Citrix Server deployment

71 Terminal Services Home Directories

We recommend using Terminal Server home directories rather than using the userrsquos 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

72 System Requirements

The Citrix server should be one of the following systems

XenApp 5 Enterprise

XenApp 5 Platinum

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 37])

73 Installing Planning and Consolidation

Prerequisites

The server installation files have been downloaded from SAP Service Marketplace and installed

Procedure

The following steps outline how to install the Planning and Consolidation clients in a Terminal Services

(TS) or Citrix Server deployment

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

71 Terminal Services Home Directories

2012-06-13 CUSTOMER 4554

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 userinstall

4 Open a browser and connect to the URL httpltPC_serverportgtsapbpcweb

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 userexecute 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 Iexploreexe http(s)

ltServerNamegt-NetBIOS or FQDNsapbpcweb

To publish Planning and Consolidation Administration CProgram FilesPC_MS

BPCAdminMainexe

74 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 userrsquos desktop) must be moved to the All UsersDesktop folder

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

74 Creating a Shortcut to the Launch Page

4654 CUSTOMER 2012-06-13

8 Installing SSIS Custom Tasks

This section provides background information and instructions for installing SQL Server Integration

Services (SSIS) for SQL Server 2008 and SQL Server 2012

The Planning and Consolidation Data Manager component supports and uses SSIS Since SQL Server

2008 and SQL Server 2012 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

81 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 Filelistxml 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

OSoftSetupexe ‒ 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 or OSoftSSIS2012_Client on the client machine followed by the SQL Server

version If you want to use SQL 2008 Tasks under the SQL 2012 environment you must install

OSoftSSIS2008_Client on the application server For detailed information see SAP Note 1707410

You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package by extracting

OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPC

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 or

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4754

OSoftSSIS2012_Client for creating a COM+ application For more information see Before You Modify

the SSIS Packages [page 50] and Setup of a COM+ Application on the Application Server [page 51]

Bin folder

This folder contains the following components

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCCachedll Planning and Consolidation Cache file

BPCDataFlowPackagedll or BPCDataFlowPackage2012dll

BPCDMdll

BPCDMTaskMaindll COM+ component

BPCFilePreviewdll

BPCGacUtil_20exe System File

BPCGacUtil_40exe System File

BPCImpersonatordll Planning and Consolidation Impersonator

BPCLogicdll

BPCScriptdll

BPCServerZipdll

BPCServiceResdll

BPCTransferMembersdll

BPCWriteBackdll

InteropDTSdll

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

4854 CUSTOMER 2012-06-13

Name Remark

OSoftAdminServerdll

OSoftAuditdll

OSoftComLibServerdll

OSoftCommonResQrydll

OSoftConfigurationdll

OSoftCustomXMLSvrdll

OSoftDatabaseADMINdll

OSoftDatabaseSYSADMINdll

OSoftDatabaseSYSADMINDMdll

OSoftDatabaseUSERdll

OSoftDMDTSXExecutedll or OSoftDMDTSXExecute2012dll

OSoftDMTaskFormdll

OSoftDMTaskMaindll

OSoftDMToolsdll

OSoftFileManagedll

OSoftLoggingdll

OSoftLogWriterdll

OSoftMetaDatadll

OSoftSQEdll

OSoftSystemConfigdll

OutlookSoftconfig Configuration file to connect DB server

XceedCompressiondll XceedZip file

XceedCompressionFormatsdll XceedZip file

XceedFileSystemdll XceedZip file

XceedZipdll XceedZip file

Config folder

This folder has FileListxml 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 FileListxml 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

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4954

OSoftSetupexe

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

NOTE

If you installed the OSoftSSIS2008_Client or OSoftSSIS2012_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

Resources Folder

This folder contains the BPCServicesdll and BPCServiceUIdll files which contain resource text

Only English resources are included for the SSIS custom tasks

82 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

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008 and 2012 respectively

8 Installing SSIS Custom Tasks

82 Before You Modify the SSIS Packages

5054 CUSTOMER 2012-06-13

Name Remark

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012 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

lthellipgtOSoftSSIS2008_Clientbin or lthellipgtOSoftSSIS2012_Clientbin

On the Planning and Consolidation application server

ltdrivegtWebsrvrbin

2 Paste these files into the folder 100DTSTasks for SQL Server 2008 or into 110DTSTasks for

SQL Server 2012 For example if you install your SQL 2008 server or R2 on CProgram Files

Microsoft SQL Server paste all files into the CProgram Files (x86)Microsoft SQL Server

100DTSTasks folder

In Integration Services set the property Run64BitRunTime to True

83 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 or OSoftSSIS2012_Client on the

application server

8 Installing SSIS Custom Tasks

83 Setup of a COM+ Application on the Application Server

2012-06-13 CUSTOMER 5154

Typographic Conventions

Example Description

ltgt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example Enter your ltUser Namegt

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 httpwwwsapcom

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

5254 CUSTOMER 2012-06-13

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

  • SAP BusinessObjects Planning and Consolidation 100
    • Table of Contents
    • 1 Introduction
      • 11 SAP Notes for the Installation
      • 12 Naming Conventions
        • 2 Installing Planning and Consolidation Servers
          • 21 Basic Steps
          • 22 Prerequisites
          • 23 Before Starting the Planning and Consolidation Server Installation
          • 24 Logging on to Servers
          • 25 Service-level Accounts
          • 26 Standard and Advanced Settings
          • 27 Installing the Prerequisites
            • 271 Installing the Prerequisites ndash Basic Steps
            • 272 Installing the Operating System
            • 273 Installing the SQL Server
            • 274 Installing Analysis Services
            • 275 Installing the Anti-Cross Site Scripting Library
              • 28 Installing on a Single Server
              • 29 Installing the Server in a Multiserver Configuration
                • 3 After Installing Planning and Consolidation Servers
                  • 31 Post-Installation Steps
                  • 32 Connecting to Solution Manager Diagnostics
                  • 33 Configuring the Planning and Consolidation NET Application Servers
                  • 34 Post-Installation Optional Configuration Steps
                    • 341 Enabling the Management Console
                    • 342 Setting Up ODBC Logging in IIS for the Default Web Site
                    • 343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2
                    • 344 Removing Default Access to the Console
                    • 345 Management Console Access Control
                    • 346 Using Client Certificates
                        • 4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office
                          • 41 Installing the Administration Client
                          • 42 Installing the EPM Add-in
                          • 43 Using the Client Auto Update Program
                            • 5 Connection Issues
                              • 51 Checking for Open Ports
                              • 52 Proxy Server and Firewall Issues
                                • 6 Installing Planning and Consolidation with Two Active Directory Domains
                                • 7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
                                  • 71 Terminal Services Home Directories
                                  • 72 System Requirements
                                  • 73 Installing Planning and Consolidation
                                  • 74 Creating a Shortcut to the Launch Page
                                    • 8 Installing SSIS Custom Tasks
                                      • 81 Composition of SSIS Custom Task Installation
                                      • 82 Before You Modify the SSIS Packages
                                      • 83 Setup of a COM+ Application on the Application Server
                                          • Copyright and trademarks
Page 18: Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

Prerequisites [page 11] and the Product Availability Matrix on the SAP Service Marketplace at http

servicesapcompam Search on Planning and Consolidation

NOTE

To ensure a successful installation you must install the software in the order listed in this

procedure

Check all third-party infrastructure services to ensure that they are functioning and that their

authentication models are documented (stated) since you need to reference this information

during the installation These third-party services include IIS OLAP service SQL services and

Active Directory (AD)

We recommend not installing Microsoft Office on the application server

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

(UMCexe) on the Planning and Consolidation CD in a folder called UMC_100_INSTALLER When

you run the installation package the wizard guides you through the following steps

1 Choose a language for the UMC install wizard to use

2 Check that the prerequisite check status is Succeeded and click Next

3 When you are ready to install the UMC click Next on the welcome screen

4 Click I accept the License Agreement and then Next

5 Choose the destination directory for the UMC installation and click Next

6 Select the languages that you wish to install

7 Select the features that you want to install (POAFHelper dotnet is mandatory for Planning

and Consolidation)

8 On Start Installation click Next to complete the installation

2 Install the required operating system on the single-server computer or on each physical server for

a multiserver configuration See Installing the Operating System [page 19]

3 Install the latest service pack for your operating system To install this service pack go to http

wwwmicrosoftcom

4 From your operating systems media install IIS

5 From your SQL Server media install SQL Server and its required service packs and hot fixes See

Installing SQL Server [page 19]

6 From your SQL Server media install Analysis Services Enterprise Edition and its required service

packs and hot fixes See Installing Analysis Services [page 23]

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

1854 CUSTOMER 2012-06-13

7 On your application server install ADOMDNET The Planning and Consolidation zip file contains

the ADOMDNET installation package in the following locations

For SQL Server 2008 mdash BPC SetupServerSQLSERVER2008_ASADOMD10_x64msi

For SQL Server 2012 mdash BPC SetupServerSQLSERVER2012_ASADOMD11_x64msi

8 On your application server install MSXML 40 Service Pack 2 or later

The MSXML 40 SP2 installation package is contained in the Planning and Consolidation zip file at

the following location BPC SetupServermsxmlmsi

9 On your application server install Microsoft Visual C++ 2005 Runtime Libraries SP1

The Microsoft Visual C++ 2005 SP1 installation package is contained in the Planning and

Consolidation zip file at the following location BPC SetupServervcredist_x64exe

NOTE

The version of vcredist_x64exe in BPC SetupServer has been updated to 8061000 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 httpwwwmicrosoftcomdownloadsen

detailsaspxFamilyID=C06B8369-60DD-4B64-A44B-84B371EDE16Dampltdisplaylanggt=en

272 Installing the Operating System

Before installing the operating system make sure that you configure your server for NTFS

For a list of languages that are supported see the Product Availability Matrix on the SAP Service

Marketplace at httpservicesapcompam Search on Planning and Consolidation

Planning and Consolidation can support all servers with an operating system in any language

NOTE

Currently Planning and Consolidation does not support an operating system in bi-directional

languages such as Hebrew

ProcedureIf you are installing IIS 70 or 75 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

273 Installing the SQL Server

PrerequisitesDuring the installation procedure you have the opportunity to specify the location of the

EnvironmentShell database file Check that it is possible to access EnvironmentShell from the location

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 1954

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 CEnvironmentShelldb10) 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 a 2008 2008 R2 and 2012 SQL Server

SQL Server Considerations

We recommend installing all required components in sequence For example install the Operating

System (Windows Server) then enable IIS and ASPNET and install any Windows Server service

packs

IIS and NET Framework 40 are required on your application server

NOTE

If you encounter a 500 HTTP Error when trying to connect to the Planning and Consolidation

Web Client refer to Microsoft Support articles 2520479 and 2468871 for assistance

To reinforce security we recommend that you install the SQL server and SSAS components to a

nondefault instance of SQL Server

General Installation Steps

1 Launch the SQL Server Setup program entering a product key if necessary and accepting the license

terms

2 Choose Install to install the SQL support files

3 In Feature Selections select instance and shared features as indicated in the SQL Server Component

Options section below then choose Next

4 Review disc space requirements then choose Next

5 In Server Configuration Perform the following actions

1 In the Service Accounts tab enter a Planning and Consolidation sysadmin account for the SQL

Server Database Engine and the SQL Server Analysis services This is required so that the Planning

and Consolidation sysadmin can create and process the Planning and Consolidation database

because the Microsoft SQL server tries to back up or restore database with the privileged

account This account is also required during Backup Environment and Restore Environment in the

Server Manager

For a single-server environment this account is also required if the backup file is located in a

different domain machine because SQL tries to access the folders and files with this account

For the a multiple-server environment SQL server retrieves the information of backup file

from the application server and the account requires the folder access privilege for the

application server

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2054 CUSTOMER 2012-06-13

To ensure that you have the complete access privileges we recommend the Planning and

Consolidation sysadmin for this service account

2 In the Collation tab set the collation settings to SQL_Latin1_General_CP1_CI_AS

Choose Next

6 Set Database Engine Configuration options then choose Next

We recommend you choose Mixed mode (Windows authentication and SQL authentication) This allows you

to use a restrictive SQL ID that works with the drill-through feature If you must restrict SQL

authentication for security reasons you can define a specific parameter in your drill-through

queries If you do not need drill-through support or use it without leveraging SQL authentication

you can install the SQL Server in Windows-only mode

7 Accept the Analysis Services Configuration default options and the remaining default options of the

installation program

8 Choose Install to begin the installation with the options you have set

SQL Server Component 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

Server Component What to Install

SQL Server Database Engine Services

SSAS Server Analysis Services

Application Server The following Shared Features Client Tools Connectivity Integration Services Client Tools SDK

Custom Settings for the SQL Server

As of version 100 Planning and Consolidation supports the following new features for SQL Server 2008

SQL Server 2008 R2 and SQL Server 2012

Process Dimension

It is now possible to process a dimension with multiple selections At processing time the process

dimension module makes changed or added information for each dimension and process for all selected

dimensions and cubes in parallel

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 2154

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

NOTE

Setting 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 tblFactWBltappgt table

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 Microsoftreg SQL Servertrade

20052008 which you can download from wwwmicrosoftcom (search on ldquoTable Partitioningrdquo to find

all relevant articles)

After Installing SQL Server 2008 SQL Server 2008 R2 and SQL Server 2012

From SQL Server Configuration Manager confirm that the SQL Server Browser service is

running The browser service is required for Planning and Consolidation

From SQL Server Configuration Manager do the following

1 Select Protocols for ltInstanceNamegt then double-click TCPIP from the right side of the window

2 When prompted for the TCPIP Properties select IP Addresses You see two IPs that indicate the

localhost and external network interface machine

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2254 CUSTOMER 2012-06-13

3 If you want to use IP1 which indicates Server IP set Enabled to Yes and specify the TCP Port as

desired

4 Delete 0 from TCP Dynamic Ports Set IPAll - TCP Ports as desired (for example 1533)

RECOMMENDATION

We do not recommend using dynamic ports

In an SQL server the default instance has a listener which listens on a fixed port (TCP

port 1433) However for the named instance the port on which the SQL server listens is

random and dynamically selected when the named instance of the SQL server starts This

recommendation prevents any conflict problems

From the SQL Server Configuration Manager specify the client protocol options for the application

server

1 Select Client Protocols from the SQL Native Client Configuration folder

2 From the right side of the window double-click TCPIP The TCPIP 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

NOTE

We 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

274 Installing Analysis Services

ProcedureAfter you install SQL Server and its required service packs and hotfixes you must install SQL Server

Analysis Services and its required service packs and hotfixes

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 2354

NOTE

If you have migrated your Analysis Services repository to the SQL Server back up the database

that contains the repository before installing this release

To install Analysis Services for SQL Server 2008 SQL Server 2008 R2 or SQL Server 2012 follow the steps

and guidelines in httptechnetmicrosoftcomen-uslibraryms143219aspx

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 httpwwwmicrosoftcomdownloads

detailsaspxFamilyID=3be0488d-e7aa-4078-a050- ae39912d2e43ampdisplaylang=en

275 Installing the Anti-Cross Site Scripting Library

Procedure

Before installing Planning and Consolidation servers you must download the Anti-Cross Site Scripting

Library (version 42 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 AntiXSSLibraryDLL from the Microsoft Web

site at httpwwwmicrosoftcomdownloadendetailsaspxid=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 AntiXssLibrarydll

28 Installing on a Single Server

When you install all Planning and Consolidation server components on a single server you should

consider the following issues

Make sure the server has a minimum of 800 MB of hard disk space

Additional environment installations require more free disk space which is a minimum of two

times the uncompressed size of the environment files

When you install Planning and Consolidation on a single-server the system adds the following server

components

SQL Server

SQL Server Analysis Services (SSAS)

Application Server

FileShare server

Procedure

To install Planning and Consolidation on a single server take the following steps

1 Exit all Windows programs

2 Installing Planning and Consolidation Servers

28 Installing on a Single Server

2454 CUSTOMER 2012-06-13

2 Log on to the server with a local server user ID or domain user ID For more information see Logging

on to servers [page 14]

3 Make sure all prerequisite software is installed on the server For more information see Installing

the Prerequisites [page 17]

4 Obtain SAP Planning and Consolidation from the Downloads SAP Installations amp Upgrades area of

SAP Service Marketplace then extract the files and run StartUpexe

5 From the Server Install screen select Install the Planning and Consolidation server

6 From the Welcome screen choose Next

7 From the License Agreement page choose I accept the terms of the license agreement then choose Next

8 From the Installation Method page accept the default Single machine enter a system ID for the system

landscape directory (SLD) and choose Next

NOTE

Entering a system ID of the SLD is only required if you have a SAP Solution Manager license

If you do not have a SAP Solution Manager license you can leave this field empty

9 From the Authentication Method page choose the desired authentication method and choose Next

10 If you have chosen SAP BusinessObjects User Management System in the previous screen on the CMS

Authentication page enter the information required to log on to CMS as an administrator

The following information is required

Field Description

System name CMS system name (server nameport number) for example CMSServer6400

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

11 After entering the CMS administrator authentication details choose Next

12 From the Service type accounts page enter service-level account user IDs and passwords See Service-

Level Accounts [page 15]

13 After defining the IDs and passwords choose Next

14 From the Server Information page (see Standard and Advanced Settings [page 16]) do one of the following

Review the standard settings and choose Next

To set advanced settings choose the Advanced Settings button Enter the desired information

and choose Next

2 Installing Planning and Consolidation Servers

28 Installing on a Single Server

2012-06-13 CUSTOMER 2554

15 Specify the location and name of AntiXssLibrarydll See Installing the Anti-Cross Site Scripting Library [page

24]

Choose Next

16 Select destination folders for Programs and Data The Data files include Webfolders and FileDB

(published reports) and should be installed on a separate drive in a production environment This

recommendation reduces the hard disk IO time and helps to speed up SQL commands

Accept the defaults or make your selections then choose Next

17 Select the default values for the Web client The values are used to determine the default language

and region for the Web client when you connect to it You can change the values in the Planning

and Consolidation Server Manager

18 The installation process takes a few moments When it is complete choose Exit

19 A prompt is displayed to restart your computer Select OK to restart

20 Perform the steps in After Installing Planning and Consolidation Servers [page 27]

29 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 24]) with the following

exceptions

On the Installation Method page do not accept the default instead choose Network Load Balancing

environment With this option there is an additional choice to Include sample environment (required on only

one of the application servers) This is because when you install the application server it connects to the

database server and creates the sample environment (EnvironmentShell) Installing the sample

environment is required on only one application server and you may choose which one

In the Virtual Name field enter the virtual IP address virtual name in the default properties

2 Installing Planning and Consolidation Servers

29 Installing the Server in a Multiserver Configuration

2654 CUSTOMER 2012-06-13

3 After Installing Planning and Consolidation Servers

31 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 28]

2 Configure the Planning and Consolidation NET and application server to ensure that it and its

related services function properly and reliably For more information see Configuring the Planning and

Consolidation NET Application Server [page 29]

3 Optional configuration steps [page 30]

1 To ensure proper functioning of the Management Console create an SQL user and modify

the System DSN and IIS to reflect those user credentials See Enabling Management Console [page

30]

2 Configure custom ODBC logging for the default Web site For details of how to configure

custom logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web

Site [page 31]

3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC

Data Source [page 32]

4 Modify the default access rights to the Management Console By default users in Active

Directory can access the Management Console with whatever rights they have been granted

on the server For information about removing default access and creating a group that can

access the console see Removing Default Access to the Console [page 32]

5 Add authorized users or groups to the group that can access the Management Console We

recommend that you only grant Management Console access to system administrators

Planning and Consolidation users should not have any access For more information see

Management Console Access Control [page 33]

6 Configure the use of client certificates for authentication See Using Client Certificates [page

34]

4 Take the following steps to set up security

If you are defining security and application structure continue with step 5

3 After Installing Planning and Consolidation Servers

31 Post-Installation Steps

2012-06-13 CUSTOMER 2754

If you want to designate someone other than the system administrator to manage security

and application structure log on to EnvironmentShell designate a user as a Primary

Administrator

This user must have Administration ‒ Environment and Security ‒ Define User task rights

so that he or she can add and delete environments and define user security

The Primary Administrator can continue with the next step (5)

5 From the machine on which you administer Planning and Consolidation install the

Administration client See Installing the Administration Client [page 37]

6 Start Planning and Consolidation Administration from the launch page

7 Select Connection Wizard and log on to EnvironmentShell

8 Create a new environment using EnvironmentShell as the source

9 Log on to the newly created environment and set up users teams and task profiles (You must

set up task profiles since there is no access to Planning and Consolidation tasks)

10 Set up your data access profiles and add users (or teams) to one or more data access profiles (You

must complete this step since there is no access to dimensions or members)

NOTE

To allow users to request and query large amounts of data you can edit the metabasexml file located

at CWindowssystem32inetsrv Set the following parameters to the stated values

ASPBUFFERINGLIMIT = 10485760

MAXREQUESTENTITYALLOWED = 10485760

32 Connecting to Solution Manager Diagnostics

NOTE

You only need to perform the steps in this section if you have a SAP Solution Manager licence

The diagnostics functions in SAP Solution Manager allow identification analysis and resolution of

problems This procedure provides the steps required to connect Planning and Consolidation to

Solution Manager Diagnostics

Procedure

1 Install the Diagnostics Agent according to SAP Note 1234387 on all servers where application servers

are installed

NOTE

Installation files for Diagnostics Agent are available on Service Marketplace by navigating to

Support Packages and Patches mdash Entry by Application Group SAP Technology Components SAP

SOLUTION MANAGER SAP SOLUTION MANAGER 70 EHP 1 Entry by Component Agents

for managed systems DIAGNOSTICS AGENT 711

3 After Installing Planning and Consolidation Servers

32 Connecting to Solution Manager Diagnostics

2854 CUSTOMER 2012-06-13

Download the installation file based on the 64-bit Windows Server system landscape

2 To access the DBA Cockpit you must create a user account with sufficient rights on all Windows

Servers where Microsoft SQL Server is installed Do the following

1 Start Computer Management then select Action New User

2 Create a new user

3 Right-click on the user then choose Properties On the Member Of tab select Add

4 Add the group SQLServerltReleasegtSQLAgentUser$ltDomain or hostnamegt$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 httpsservicesapcom~sapidb011000358700000074392009E and follow

the chapters that apply to Planning and Consolidation

33 Configuring the Planning and Consolidation NET Application Servers

Procedure

Modifying machineconfig Files

To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock

occurrences that would cause the application server to ldquosleeprdquo and not process anymore you can

modify the machineconfig file which resides in the WINDOWSMicrosoftNETFramework64

v4030319Config directory

1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to

specify whether to automatically configure settings to achieve optimal performance based on the

machine configuration You can set this attribute to True or False

For more information see httpmsdnmicrosoftcomen-uslibrary7w2sway1aspx

2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the

Planning and Consolidation application) or Machineconfig (for all applications including

Planning and Consolidation) to ensure the validationKey and decryptionKey keys have the same

value on all application servers This way when the authentication cookie is checked the

authentication ticket used on one server can still be valid on another server

For more information and sample Visual Basic code for generating random key values see http

msdnmicrosoftcomen-uslibraryms998288aspx

3 After Installing Planning and Consolidation Servers

33 Configuring the Planning and Consolidation NET Application Servers

2012-06-13 CUSTOMER 2954

paght000007_webfarmdeploymentconsiderations and httpmsdnmicrosoftcomen-us

libraryms998310aspx

34 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 30]

2 Configure custom ODBC logging for the default Web site For details of how to configure custom

logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page

31]

3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC Data

Source [page 32]

4 Modify the default access rights to the Management Console By default users in Active Directory

can access the Management Console with whatever rights they have been granted on the server

For information about removing default access and creating a group that can access the console

see Removing Default Access to the Console [page 32]

5 Add authorized users or groups to the group that can access the Management Console We

recommend that you only grant Management Console access to system administrators Planning

and Consolidation users should not have any access For more information see Management Console

Access Control [page 33]

6 Configure the use of client certificates for authentication See Using Client Certificates [page 34]

341 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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3054 CUSTOMER 2012-06-13

NOTE

Without these updates the Management Console does work but some functionality (specifically

User Activity and Service Status) does not work as expected

Should you need to uninstall Planning and Consolidation we recommend that you reset the

Active Log Format field in IIS to W3C Extended Log File Format

342 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 ApplicationHostconfig set the property customLogPluginClsid to the value FF16065B-

DE82-11CF-BC0A-00AA006111E0 Set the logFormat to Custom You can find this in the ltlogFilegt

node in ApplicationHostconfig as shown here

ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0

logFormat=Custom gt

Use the following AppCmds to configure IIS to use ODBC logging for the default Web site

appcmd site set sitenameDefault Web Site

logFilecustomLogPluginClsidFF16065B-DE82-11CF-BC0A-00AA006111E0

appcmd site set sitenameDefault Web Site logFilelogFormatCustom

Configuring ODBC Logging Parameters in ApplicationHostconfig

Configure ApplicationHostconfig to contain the database table information as set up in the Microsoft

Support article specified in the Prerequisites section Configure these settings in the ltodbcLogginggt

node under ltsystemwebServergt

EXAMPLE

ltlocation path=Default Web Sitegt

ltsystemwebServergt

ltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog

userName=Username password=mypassword gt

ltsystemwebServergt

ltlocationgt

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3154

Use the following AppCmds to configure these attributes for the default Web site

appcmd set config Default Web Site sectionodbcLogging

dataSourceBPC_ManagementDSN commitappHost

appcmd set config Default Web Site sectionodbcLogging tableNameBPCLog

commitappHost

appcmd set config Default Web Site sectionodbcLogging userNameUsername

commitappHost

appcmd set config Default Web Site sectionodbcLogging passwordmypassword

commitappHost

NOTE

You cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must

use the SQL Server ODBC driver For more information see the Microsoft Knowledge Base article

931202 The requirements for using the ODBC logging feature in IIS

343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2

ProcedureThis procedure describes how to set up an ODBC data source for the Management Console in Windows

Server 2008 or Windows Server 2008 R2

Proceed as follows

1 Open ODBC Connection Manager

2 On the System DSN tab page add a new DSN

Choose Add

Choose SQL Server as the driver

Choose Finish

3 In the Name and Description fields enter BPC_ManagementDSN

4 In the Server field enter the name of your SQL Server Choose Next

5 Leave the default settings and choose Next

6 Choose the Change the default database to field and enter AppServer Choose Next

7 Leave default settings and choose Next

8 Choose OK

344 Removing Default Access to the Console

NOTE

If you have chosen SAP BusinessObjects User Management System in the installation screen you

do not need to remove or configure access because the Management Console service always runs

with the System Admin ID account which is a member of the Administrators group

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3254 CUSTOMER 2012-06-13

ProcedureTo remove default access to the Management Console and create a group that does have access to the

console use the procedure described below

NOTE

Create your Management Console administrative group either on the server that hosts the

Management Console or in the Active Directory

1 In the context menu of the servers My Computer icon choose Manage

2 In the Computer Management dialog box choose Local Users and Groups Groups

NOTE

Alternatively you can perform analogous steps in Active Directory

3 In the 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

NOTE

This step is a necessary precursor to the completion of this procedure

10 In the Security dialog box click Copy to ensure that the System group retains its privileges

11 Remove access to the Management Console from all groups that should not have it

12 Choose Authentication in the center pane then disable Windows authentication

ResultUsers who have not been granted access to the Management Console can still open the Management

Console Web page but it contains no data or menu options This does not affect the access that a user

would otherwise have to Planning and Consolidation

345 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 32] Their rights in

Active Directory determine what they can access in the Console

By default any member of the Administrators Active Directory group on the application server or

domain has full access to all of the features of the Console except the Planning and Consolidation

logging area Access to Planning and Consolidation logging is controlled within the Planning and

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3354

Consolidation Administration Client task security The user must be granted View system logs task

privileges For more information see the SAP Library Planning and Consolidation Administrators Guide in

httpservicesapcominstguidesepm-bpc 100 version for the Microsoft platform

Your IT policy determines whether you grant access by group or user You may wish to create several

levels of Console users (read-only users for example) in your environment

To grant or limit access to users or groups you can add or remove the following privileges from the

areas described in this table

Privilege Rights Management Area

Task Manager and Kill Process Administrators group on application server or domain

Performance Monitor Counters Administrators group on application server or domain Power Users group on application server or domain Performance Monitor Users group on application server

Microsoft Analysis Services performance monitoring

Administrators group on application server or domain

Microsoft SQL Server Monitoring (performance counters and statistics)

Administrators group on application server or domain

346 Using Client Certificates

To enable the use of client certificates in Planning and Consolidation you must follow several manual

steps

NOTE

Planning 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 httptechnetmicrosoftcomen-us

librarycc753810aspx

For more information about configuring the client certificate mapping authentication see http

technetmicrosoftcomen-uslibrarycc732996(WS10)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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3454 CUSTOMER 2012-06-13

This option allows you to use a client certificate or username and password (Basic

authentication) to connect to Planning and Consolidation

2 Enable anonymous authentication

1 In the IIS Manager expand the node of the Planning and Consolidation web site

2 Select the ManagementConsole directory (ltWebsitegtManagementConsole) to open the

ManagementConsole home page

3 Double-click Authentication and enable Anonymous Authentication

4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way

as in step 3

5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the same

way as in step 3

3 Change the web configuration settings

1 Open the ltPC_MSgtWebsrvrWebBPCwebconfig file

2 Find the text clientCredentialType=Windows

3 Change value of clientCredentialType to None (clientCredentialType=None)

4 Open the PC_MSWebsrvrWebPOASBCwebconfig file Repeat steps 2 and 3

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3554

This page is left blank for documents that are printed on both sides

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

The installation of the Planning and Consolidation Administration Client allows administrators to

build and maintain Planning and Consolidation environments and models and administer security

All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions

add-in for Microsoft Office for more information see the SAP BusinessObjects EPM solutions add-in for

Microsoft Office help

NOTE

You must update the Administration Client to the same version as the server

If your PC is on a different domain than your server you must set the Internet Explorer

Security Zone value of the Planning and Consolidation client to prompt for user name and

password Otherwise the Planning and Consolidation Start Page does not display

41 Installing the Administration Client

Prerequisites

NOTE

For a definitive list of system requirements see the Product Availability Matrix on SAP Service

Marketplace at httpservicesapcompam Search on Planning and Consolidation

The following list describes the minimum software requirements

Microsoft Internet Explorer 70 or 80

Microsoft Office 2007 or 2010

NET Framework 20 or higher (install any required NET Framework Hotfixes by referring to

httpsupportmicrosoftcomkb)

Pentium IV (1 GHz CPU)

512 MB RAM

100 MB of free hard disk space in the My Documents folder

20 MB of free hard disk space for the installed Administration files

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

41 Installing the Administration Client

2012-06-13 CUSTOMER 3754

NOTE

We recommend that you install all of the latest Microsoft Windows hotfixes prior to installing

the Administration client For information about which hotfixes to install see http

updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us

ProcedureThe following procedure describes how to install the Administration Client on to an administratorrsquos

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 AddRemove Programs in the Windows Control Panel

3 Point your browser to the Planning and Consolidation Web at httpltPC_serverportgtsap

bpcweb

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

42 Installing the EPM Add-in

The Planning and Consolidation installation media does not contain the EPM addin setup program

You must download the most recent version of the full setup (EPM Add-inexe) from the Service

Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPC

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

43 Using the Client Auto Update Program

If Planning and Consolidation version 100 or later is installed you can use the Client Auto Update

program to set up the server so that it determines if an upgrade for a connecting Administration client

is necessary

The following describes the use of the auto update program for the Administration Client and the EPM

add-in

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

42 Installing the EPM Add-in

3854 CUSTOMER 2012-06-13

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 37]

To use the Client Auto Update program for the Administration Client proceed as follows

1 From the Server Manager select Options Client Options

2 Select Admin Update

3 If users without administrator rights on their machines use the auto update enter an administrator

ID and password in the Admin ID and Admin password fields respectively The Admin ID should be a

member of the local administrators group on all the computers running the auto update This

setting is not needed if all users have administrator rights on their machines

4 Select Update

For the EPM Add-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 Optionshellip 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 Market Place (SMP) at httpservicesapcom

All support packages and patches are available from the SMP as a zip file

EPMEXCLCLNTltSPLgtzip is for a support package

EPMEXCLCLNTltSPLgtPltPLgtzip 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 ltSP versiongtmsp

EPM Addin Support Package ltSP versiongtxml

For a patch these files are

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

2012-06-13 CUSTOMER 3954

EPM Addin Patch ltpatch numbergtmsp

EPM Addin Patch ltpatch numbergtxml

2 Unzip the zip file and extract the two files to the application server folder (WebsrvrWebBPC

Installation)

3 From the Server Manager select Options Client Options

The system lists the available packages Select the package that you want to use for the autoupdate

You can set a different update policy for each package listed

EXAMPLE

The following table illustrates some possible situations assuming that you have installed the

first full version (V1)

Available maintenance packages

V2-user updateV3-force updateV4-force updateV5-user update

V5-user update V5-user updateV6-auto updateV7-force update

Minimum Required Version

V4 V4 V7

Notification A prompt tells the user to install maintenance package V4 using the Forced Update behavior

If User Update is enabled the prompt informs the user that maintenance package V5 is available

A prompt tells the user to install maintenance package V7 using the Forced Update behavior

New Version V4 V4 or V5 V7

If you change the update policy for any package click Update to complete the change

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

4054 CUSTOMER 2012-06-13

5 Connection Issues

You may experience connection problems with ports the proxy server or programs and settings that

interact with these components If you have any issues related to connection review the following

recommendations and troubleshooting tips

51 Checking for Open Ports

You must ensure that all required ports are open for inboundoutbound 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 431181836 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

NOTE

You can use the following site to scan for the normal ports It allows you to manually enter a port

number to test

httpwwwmyserverorgportsniffasp

You can change the name of a port

52 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 Explorer Tools Internet Options Connections LAN Settings ) or at the server level

Enabling content filtering on the proxy server or firewall may cause connection problems

If external users are having trouble connecting to the server make sure the proxy server connects

using a fully qualified domain name Fully qualified domain names typically resolve both internal

and external IP addresses

Each secure Planning and Consolidation server name must be identified on the proxy server

Proxy servers may or may not require authentication which could conflict with Planning and

Consolidation authentication Do not use authentication on the proxy server The system

5 Connection Issues

51 Checking for Open Ports

2012-06-13 CUSTOMER 4154

synchronizes the user name and password on the remote server with the local user name and

password

NOTE

For more information about setting up an ISA proxy server contact SAP Support to request a

copy of Setting up ISA Proxy Server White Paper

Internet Explorer Settings 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

5 Connection Issues

52 Proxy Server and Firewall Issues

4254 CUSTOMER 2012-06-13

6 Installing Planning and Consolidation with Two Active Directory Domains

To set up a Planning and Consolidation 10 application server in a hosted environment and use your

own domain users follow this procedure In general you install Planning and Consolidation on the

host domain use the host domain account and assign it to the Planning and Consolidation users

SysAdmin Admin and Users Then you accept one way trust (the host domain trusts your domain)

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

6 Installing Planning and Consolidation with Two Active Directory Domains

2012-06-13 CUSTOMER 4354

This page is left blank for documents that are printed on both sides

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

This section describes best practices and instructions for installing Planning and Consolidation in a

Terminal Services or Citrix Server deployment

71 Terminal Services Home Directories

We recommend using Terminal Server home directories rather than using the userrsquos 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

72 System Requirements

The Citrix server should be one of the following systems

XenApp 5 Enterprise

XenApp 5 Platinum

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 37])

73 Installing Planning and Consolidation

Prerequisites

The server installation files have been downloaded from SAP Service Marketplace and installed

Procedure

The following steps outline how to install the Planning and Consolidation clients in a Terminal Services

(TS) or Citrix Server deployment

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

71 Terminal Services Home Directories

2012-06-13 CUSTOMER 4554

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 userinstall

4 Open a browser and connect to the URL httpltPC_serverportgtsapbpcweb

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 userexecute 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 Iexploreexe http(s)

ltServerNamegt-NetBIOS or FQDNsapbpcweb

To publish Planning and Consolidation Administration CProgram FilesPC_MS

BPCAdminMainexe

74 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 userrsquos desktop) must be moved to the All UsersDesktop folder

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

74 Creating a Shortcut to the Launch Page

4654 CUSTOMER 2012-06-13

8 Installing SSIS Custom Tasks

This section provides background information and instructions for installing SQL Server Integration

Services (SSIS) for SQL Server 2008 and SQL Server 2012

The Planning and Consolidation Data Manager component supports and uses SSIS Since SQL Server

2008 and SQL Server 2012 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

81 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 Filelistxml 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

OSoftSetupexe ‒ 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 or OSoftSSIS2012_Client on the client machine followed by the SQL Server

version If you want to use SQL 2008 Tasks under the SQL 2012 environment you must install

OSoftSSIS2008_Client on the application server For detailed information see SAP Note 1707410

You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package by extracting

OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPC

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 or

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4754

OSoftSSIS2012_Client for creating a COM+ application For more information see Before You Modify

the SSIS Packages [page 50] and Setup of a COM+ Application on the Application Server [page 51]

Bin folder

This folder contains the following components

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCCachedll Planning and Consolidation Cache file

BPCDataFlowPackagedll or BPCDataFlowPackage2012dll

BPCDMdll

BPCDMTaskMaindll COM+ component

BPCFilePreviewdll

BPCGacUtil_20exe System File

BPCGacUtil_40exe System File

BPCImpersonatordll Planning and Consolidation Impersonator

BPCLogicdll

BPCScriptdll

BPCServerZipdll

BPCServiceResdll

BPCTransferMembersdll

BPCWriteBackdll

InteropDTSdll

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

4854 CUSTOMER 2012-06-13

Name Remark

OSoftAdminServerdll

OSoftAuditdll

OSoftComLibServerdll

OSoftCommonResQrydll

OSoftConfigurationdll

OSoftCustomXMLSvrdll

OSoftDatabaseADMINdll

OSoftDatabaseSYSADMINdll

OSoftDatabaseSYSADMINDMdll

OSoftDatabaseUSERdll

OSoftDMDTSXExecutedll or OSoftDMDTSXExecute2012dll

OSoftDMTaskFormdll

OSoftDMTaskMaindll

OSoftDMToolsdll

OSoftFileManagedll

OSoftLoggingdll

OSoftLogWriterdll

OSoftMetaDatadll

OSoftSQEdll

OSoftSystemConfigdll

OutlookSoftconfig Configuration file to connect DB server

XceedCompressiondll XceedZip file

XceedCompressionFormatsdll XceedZip file

XceedFileSystemdll XceedZip file

XceedZipdll XceedZip file

Config folder

This folder has FileListxml 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 FileListxml 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

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4954

OSoftSetupexe

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

NOTE

If you installed the OSoftSSIS2008_Client or OSoftSSIS2012_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

Resources Folder

This folder contains the BPCServicesdll and BPCServiceUIdll files which contain resource text

Only English resources are included for the SSIS custom tasks

82 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

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008 and 2012 respectively

8 Installing SSIS Custom Tasks

82 Before You Modify the SSIS Packages

5054 CUSTOMER 2012-06-13

Name Remark

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012 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

lthellipgtOSoftSSIS2008_Clientbin or lthellipgtOSoftSSIS2012_Clientbin

On the Planning and Consolidation application server

ltdrivegtWebsrvrbin

2 Paste these files into the folder 100DTSTasks for SQL Server 2008 or into 110DTSTasks for

SQL Server 2012 For example if you install your SQL 2008 server or R2 on CProgram Files

Microsoft SQL Server paste all files into the CProgram Files (x86)Microsoft SQL Server

100DTSTasks folder

In Integration Services set the property Run64BitRunTime to True

83 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 or OSoftSSIS2012_Client on the

application server

8 Installing SSIS Custom Tasks

83 Setup of a COM+ Application on the Application Server

2012-06-13 CUSTOMER 5154

Typographic Conventions

Example Description

ltgt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example Enter your ltUser Namegt

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 httpwwwsapcom

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

5254 CUSTOMER 2012-06-13

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

  • SAP BusinessObjects Planning and Consolidation 100
    • Table of Contents
    • 1 Introduction
      • 11 SAP Notes for the Installation
      • 12 Naming Conventions
        • 2 Installing Planning and Consolidation Servers
          • 21 Basic Steps
          • 22 Prerequisites
          • 23 Before Starting the Planning and Consolidation Server Installation
          • 24 Logging on to Servers
          • 25 Service-level Accounts
          • 26 Standard and Advanced Settings
          • 27 Installing the Prerequisites
            • 271 Installing the Prerequisites ndash Basic Steps
            • 272 Installing the Operating System
            • 273 Installing the SQL Server
            • 274 Installing Analysis Services
            • 275 Installing the Anti-Cross Site Scripting Library
              • 28 Installing on a Single Server
              • 29 Installing the Server in a Multiserver Configuration
                • 3 After Installing Planning and Consolidation Servers
                  • 31 Post-Installation Steps
                  • 32 Connecting to Solution Manager Diagnostics
                  • 33 Configuring the Planning and Consolidation NET Application Servers
                  • 34 Post-Installation Optional Configuration Steps
                    • 341 Enabling the Management Console
                    • 342 Setting Up ODBC Logging in IIS for the Default Web Site
                    • 343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2
                    • 344 Removing Default Access to the Console
                    • 345 Management Console Access Control
                    • 346 Using Client Certificates
                        • 4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office
                          • 41 Installing the Administration Client
                          • 42 Installing the EPM Add-in
                          • 43 Using the Client Auto Update Program
                            • 5 Connection Issues
                              • 51 Checking for Open Ports
                              • 52 Proxy Server and Firewall Issues
                                • 6 Installing Planning and Consolidation with Two Active Directory Domains
                                • 7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
                                  • 71 Terminal Services Home Directories
                                  • 72 System Requirements
                                  • 73 Installing Planning and Consolidation
                                  • 74 Creating a Shortcut to the Launch Page
                                    • 8 Installing SSIS Custom Tasks
                                      • 81 Composition of SSIS Custom Task Installation
                                      • 82 Before You Modify the SSIS Packages
                                      • 83 Setup of a COM+ Application on the Application Server
                                          • Copyright and trademarks
Page 19: Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

7 On your application server install ADOMDNET The Planning and Consolidation zip file contains

the ADOMDNET installation package in the following locations

For SQL Server 2008 mdash BPC SetupServerSQLSERVER2008_ASADOMD10_x64msi

For SQL Server 2012 mdash BPC SetupServerSQLSERVER2012_ASADOMD11_x64msi

8 On your application server install MSXML 40 Service Pack 2 or later

The MSXML 40 SP2 installation package is contained in the Planning and Consolidation zip file at

the following location BPC SetupServermsxmlmsi

9 On your application server install Microsoft Visual C++ 2005 Runtime Libraries SP1

The Microsoft Visual C++ 2005 SP1 installation package is contained in the Planning and

Consolidation zip file at the following location BPC SetupServervcredist_x64exe

NOTE

The version of vcredist_x64exe in BPC SetupServer has been updated to 8061000 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 httpwwwmicrosoftcomdownloadsen

detailsaspxFamilyID=C06B8369-60DD-4B64-A44B-84B371EDE16Dampltdisplaylanggt=en

272 Installing the Operating System

Before installing the operating system make sure that you configure your server for NTFS

For a list of languages that are supported see the Product Availability Matrix on the SAP Service

Marketplace at httpservicesapcompam Search on Planning and Consolidation

Planning and Consolidation can support all servers with an operating system in any language

NOTE

Currently Planning and Consolidation does not support an operating system in bi-directional

languages such as Hebrew

ProcedureIf you are installing IIS 70 or 75 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

273 Installing the SQL Server

PrerequisitesDuring the installation procedure you have the opportunity to specify the location of the

EnvironmentShell database file Check that it is possible to access EnvironmentShell from the location

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 1954

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 CEnvironmentShelldb10) 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 a 2008 2008 R2 and 2012 SQL Server

SQL Server Considerations

We recommend installing all required components in sequence For example install the Operating

System (Windows Server) then enable IIS and ASPNET and install any Windows Server service

packs

IIS and NET Framework 40 are required on your application server

NOTE

If you encounter a 500 HTTP Error when trying to connect to the Planning and Consolidation

Web Client refer to Microsoft Support articles 2520479 and 2468871 for assistance

To reinforce security we recommend that you install the SQL server and SSAS components to a

nondefault instance of SQL Server

General Installation Steps

1 Launch the SQL Server Setup program entering a product key if necessary and accepting the license

terms

2 Choose Install to install the SQL support files

3 In Feature Selections select instance and shared features as indicated in the SQL Server Component

Options section below then choose Next

4 Review disc space requirements then choose Next

5 In Server Configuration Perform the following actions

1 In the Service Accounts tab enter a Planning and Consolidation sysadmin account for the SQL

Server Database Engine and the SQL Server Analysis services This is required so that the Planning

and Consolidation sysadmin can create and process the Planning and Consolidation database

because the Microsoft SQL server tries to back up or restore database with the privileged

account This account is also required during Backup Environment and Restore Environment in the

Server Manager

For a single-server environment this account is also required if the backup file is located in a

different domain machine because SQL tries to access the folders and files with this account

For the a multiple-server environment SQL server retrieves the information of backup file

from the application server and the account requires the folder access privilege for the

application server

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2054 CUSTOMER 2012-06-13

To ensure that you have the complete access privileges we recommend the Planning and

Consolidation sysadmin for this service account

2 In the Collation tab set the collation settings to SQL_Latin1_General_CP1_CI_AS

Choose Next

6 Set Database Engine Configuration options then choose Next

We recommend you choose Mixed mode (Windows authentication and SQL authentication) This allows you

to use a restrictive SQL ID that works with the drill-through feature If you must restrict SQL

authentication for security reasons you can define a specific parameter in your drill-through

queries If you do not need drill-through support or use it without leveraging SQL authentication

you can install the SQL Server in Windows-only mode

7 Accept the Analysis Services Configuration default options and the remaining default options of the

installation program

8 Choose Install to begin the installation with the options you have set

SQL Server Component 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

Server Component What to Install

SQL Server Database Engine Services

SSAS Server Analysis Services

Application Server The following Shared Features Client Tools Connectivity Integration Services Client Tools SDK

Custom Settings for the SQL Server

As of version 100 Planning and Consolidation supports the following new features for SQL Server 2008

SQL Server 2008 R2 and SQL Server 2012

Process Dimension

It is now possible to process a dimension with multiple selections At processing time the process

dimension module makes changed or added information for each dimension and process for all selected

dimensions and cubes in parallel

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 2154

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

NOTE

Setting 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 tblFactWBltappgt table

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 Microsoftreg SQL Servertrade

20052008 which you can download from wwwmicrosoftcom (search on ldquoTable Partitioningrdquo to find

all relevant articles)

After Installing SQL Server 2008 SQL Server 2008 R2 and SQL Server 2012

From SQL Server Configuration Manager confirm that the SQL Server Browser service is

running The browser service is required for Planning and Consolidation

From SQL Server Configuration Manager do the following

1 Select Protocols for ltInstanceNamegt then double-click TCPIP from the right side of the window

2 When prompted for the TCPIP Properties select IP Addresses You see two IPs that indicate the

localhost and external network interface machine

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2254 CUSTOMER 2012-06-13

3 If you want to use IP1 which indicates Server IP set Enabled to Yes and specify the TCP Port as

desired

4 Delete 0 from TCP Dynamic Ports Set IPAll - TCP Ports as desired (for example 1533)

RECOMMENDATION

We do not recommend using dynamic ports

In an SQL server the default instance has a listener which listens on a fixed port (TCP

port 1433) However for the named instance the port on which the SQL server listens is

random and dynamically selected when the named instance of the SQL server starts This

recommendation prevents any conflict problems

From the SQL Server Configuration Manager specify the client protocol options for the application

server

1 Select Client Protocols from the SQL Native Client Configuration folder

2 From the right side of the window double-click TCPIP The TCPIP 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

NOTE

We 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

274 Installing Analysis Services

ProcedureAfter you install SQL Server and its required service packs and hotfixes you must install SQL Server

Analysis Services and its required service packs and hotfixes

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 2354

NOTE

If you have migrated your Analysis Services repository to the SQL Server back up the database

that contains the repository before installing this release

To install Analysis Services for SQL Server 2008 SQL Server 2008 R2 or SQL Server 2012 follow the steps

and guidelines in httptechnetmicrosoftcomen-uslibraryms143219aspx

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 httpwwwmicrosoftcomdownloads

detailsaspxFamilyID=3be0488d-e7aa-4078-a050- ae39912d2e43ampdisplaylang=en

275 Installing the Anti-Cross Site Scripting Library

Procedure

Before installing Planning and Consolidation servers you must download the Anti-Cross Site Scripting

Library (version 42 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 AntiXSSLibraryDLL from the Microsoft Web

site at httpwwwmicrosoftcomdownloadendetailsaspxid=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 AntiXssLibrarydll

28 Installing on a Single Server

When you install all Planning and Consolidation server components on a single server you should

consider the following issues

Make sure the server has a minimum of 800 MB of hard disk space

Additional environment installations require more free disk space which is a minimum of two

times the uncompressed size of the environment files

When you install Planning and Consolidation on a single-server the system adds the following server

components

SQL Server

SQL Server Analysis Services (SSAS)

Application Server

FileShare server

Procedure

To install Planning and Consolidation on a single server take the following steps

1 Exit all Windows programs

2 Installing Planning and Consolidation Servers

28 Installing on a Single Server

2454 CUSTOMER 2012-06-13

2 Log on to the server with a local server user ID or domain user ID For more information see Logging

on to servers [page 14]

3 Make sure all prerequisite software is installed on the server For more information see Installing

the Prerequisites [page 17]

4 Obtain SAP Planning and Consolidation from the Downloads SAP Installations amp Upgrades area of

SAP Service Marketplace then extract the files and run StartUpexe

5 From the Server Install screen select Install the Planning and Consolidation server

6 From the Welcome screen choose Next

7 From the License Agreement page choose I accept the terms of the license agreement then choose Next

8 From the Installation Method page accept the default Single machine enter a system ID for the system

landscape directory (SLD) and choose Next

NOTE

Entering a system ID of the SLD is only required if you have a SAP Solution Manager license

If you do not have a SAP Solution Manager license you can leave this field empty

9 From the Authentication Method page choose the desired authentication method and choose Next

10 If you have chosen SAP BusinessObjects User Management System in the previous screen on the CMS

Authentication page enter the information required to log on to CMS as an administrator

The following information is required

Field Description

System name CMS system name (server nameport number) for example CMSServer6400

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

11 After entering the CMS administrator authentication details choose Next

12 From the Service type accounts page enter service-level account user IDs and passwords See Service-

Level Accounts [page 15]

13 After defining the IDs and passwords choose Next

14 From the Server Information page (see Standard and Advanced Settings [page 16]) do one of the following

Review the standard settings and choose Next

To set advanced settings choose the Advanced Settings button Enter the desired information

and choose Next

2 Installing Planning and Consolidation Servers

28 Installing on a Single Server

2012-06-13 CUSTOMER 2554

15 Specify the location and name of AntiXssLibrarydll See Installing the Anti-Cross Site Scripting Library [page

24]

Choose Next

16 Select destination folders for Programs and Data The Data files include Webfolders and FileDB

(published reports) and should be installed on a separate drive in a production environment This

recommendation reduces the hard disk IO time and helps to speed up SQL commands

Accept the defaults or make your selections then choose Next

17 Select the default values for the Web client The values are used to determine the default language

and region for the Web client when you connect to it You can change the values in the Planning

and Consolidation Server Manager

18 The installation process takes a few moments When it is complete choose Exit

19 A prompt is displayed to restart your computer Select OK to restart

20 Perform the steps in After Installing Planning and Consolidation Servers [page 27]

29 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 24]) with the following

exceptions

On the Installation Method page do not accept the default instead choose Network Load Balancing

environment With this option there is an additional choice to Include sample environment (required on only

one of the application servers) This is because when you install the application server it connects to the

database server and creates the sample environment (EnvironmentShell) Installing the sample

environment is required on only one application server and you may choose which one

In the Virtual Name field enter the virtual IP address virtual name in the default properties

2 Installing Planning and Consolidation Servers

29 Installing the Server in a Multiserver Configuration

2654 CUSTOMER 2012-06-13

3 After Installing Planning and Consolidation Servers

31 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 28]

2 Configure the Planning and Consolidation NET and application server to ensure that it and its

related services function properly and reliably For more information see Configuring the Planning and

Consolidation NET Application Server [page 29]

3 Optional configuration steps [page 30]

1 To ensure proper functioning of the Management Console create an SQL user and modify

the System DSN and IIS to reflect those user credentials See Enabling Management Console [page

30]

2 Configure custom ODBC logging for the default Web site For details of how to configure

custom logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web

Site [page 31]

3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC

Data Source [page 32]

4 Modify the default access rights to the Management Console By default users in Active

Directory can access the Management Console with whatever rights they have been granted

on the server For information about removing default access and creating a group that can

access the console see Removing Default Access to the Console [page 32]

5 Add authorized users or groups to the group that can access the Management Console We

recommend that you only grant Management Console access to system administrators

Planning and Consolidation users should not have any access For more information see

Management Console Access Control [page 33]

6 Configure the use of client certificates for authentication See Using Client Certificates [page

34]

4 Take the following steps to set up security

If you are defining security and application structure continue with step 5

3 After Installing Planning and Consolidation Servers

31 Post-Installation Steps

2012-06-13 CUSTOMER 2754

If you want to designate someone other than the system administrator to manage security

and application structure log on to EnvironmentShell designate a user as a Primary

Administrator

This user must have Administration ‒ Environment and Security ‒ Define User task rights

so that he or she can add and delete environments and define user security

The Primary Administrator can continue with the next step (5)

5 From the machine on which you administer Planning and Consolidation install the

Administration client See Installing the Administration Client [page 37]

6 Start Planning and Consolidation Administration from the launch page

7 Select Connection Wizard and log on to EnvironmentShell

8 Create a new environment using EnvironmentShell as the source

9 Log on to the newly created environment and set up users teams and task profiles (You must

set up task profiles since there is no access to Planning and Consolidation tasks)

10 Set up your data access profiles and add users (or teams) to one or more data access profiles (You

must complete this step since there is no access to dimensions or members)

NOTE

To allow users to request and query large amounts of data you can edit the metabasexml file located

at CWindowssystem32inetsrv Set the following parameters to the stated values

ASPBUFFERINGLIMIT = 10485760

MAXREQUESTENTITYALLOWED = 10485760

32 Connecting to Solution Manager Diagnostics

NOTE

You only need to perform the steps in this section if you have a SAP Solution Manager licence

The diagnostics functions in SAP Solution Manager allow identification analysis and resolution of

problems This procedure provides the steps required to connect Planning and Consolidation to

Solution Manager Diagnostics

Procedure

1 Install the Diagnostics Agent according to SAP Note 1234387 on all servers where application servers

are installed

NOTE

Installation files for Diagnostics Agent are available on Service Marketplace by navigating to

Support Packages and Patches mdash Entry by Application Group SAP Technology Components SAP

SOLUTION MANAGER SAP SOLUTION MANAGER 70 EHP 1 Entry by Component Agents

for managed systems DIAGNOSTICS AGENT 711

3 After Installing Planning and Consolidation Servers

32 Connecting to Solution Manager Diagnostics

2854 CUSTOMER 2012-06-13

Download the installation file based on the 64-bit Windows Server system landscape

2 To access the DBA Cockpit you must create a user account with sufficient rights on all Windows

Servers where Microsoft SQL Server is installed Do the following

1 Start Computer Management then select Action New User

2 Create a new user

3 Right-click on the user then choose Properties On the Member Of tab select Add

4 Add the group SQLServerltReleasegtSQLAgentUser$ltDomain or hostnamegt$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 httpsservicesapcom~sapidb011000358700000074392009E and follow

the chapters that apply to Planning and Consolidation

33 Configuring the Planning and Consolidation NET Application Servers

Procedure

Modifying machineconfig Files

To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock

occurrences that would cause the application server to ldquosleeprdquo and not process anymore you can

modify the machineconfig file which resides in the WINDOWSMicrosoftNETFramework64

v4030319Config directory

1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to

specify whether to automatically configure settings to achieve optimal performance based on the

machine configuration You can set this attribute to True or False

For more information see httpmsdnmicrosoftcomen-uslibrary7w2sway1aspx

2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the

Planning and Consolidation application) or Machineconfig (for all applications including

Planning and Consolidation) to ensure the validationKey and decryptionKey keys have the same

value on all application servers This way when the authentication cookie is checked the

authentication ticket used on one server can still be valid on another server

For more information and sample Visual Basic code for generating random key values see http

msdnmicrosoftcomen-uslibraryms998288aspx

3 After Installing Planning and Consolidation Servers

33 Configuring the Planning and Consolidation NET Application Servers

2012-06-13 CUSTOMER 2954

paght000007_webfarmdeploymentconsiderations and httpmsdnmicrosoftcomen-us

libraryms998310aspx

34 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 30]

2 Configure custom ODBC logging for the default Web site For details of how to configure custom

logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page

31]

3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC Data

Source [page 32]

4 Modify the default access rights to the Management Console By default users in Active Directory

can access the Management Console with whatever rights they have been granted on the server

For information about removing default access and creating a group that can access the console

see Removing Default Access to the Console [page 32]

5 Add authorized users or groups to the group that can access the Management Console We

recommend that you only grant Management Console access to system administrators Planning

and Consolidation users should not have any access For more information see Management Console

Access Control [page 33]

6 Configure the use of client certificates for authentication See Using Client Certificates [page 34]

341 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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3054 CUSTOMER 2012-06-13

NOTE

Without these updates the Management Console does work but some functionality (specifically

User Activity and Service Status) does not work as expected

Should you need to uninstall Planning and Consolidation we recommend that you reset the

Active Log Format field in IIS to W3C Extended Log File Format

342 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 ApplicationHostconfig set the property customLogPluginClsid to the value FF16065B-

DE82-11CF-BC0A-00AA006111E0 Set the logFormat to Custom You can find this in the ltlogFilegt

node in ApplicationHostconfig as shown here

ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0

logFormat=Custom gt

Use the following AppCmds to configure IIS to use ODBC logging for the default Web site

appcmd site set sitenameDefault Web Site

logFilecustomLogPluginClsidFF16065B-DE82-11CF-BC0A-00AA006111E0

appcmd site set sitenameDefault Web Site logFilelogFormatCustom

Configuring ODBC Logging Parameters in ApplicationHostconfig

Configure ApplicationHostconfig to contain the database table information as set up in the Microsoft

Support article specified in the Prerequisites section Configure these settings in the ltodbcLogginggt

node under ltsystemwebServergt

EXAMPLE

ltlocation path=Default Web Sitegt

ltsystemwebServergt

ltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog

userName=Username password=mypassword gt

ltsystemwebServergt

ltlocationgt

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3154

Use the following AppCmds to configure these attributes for the default Web site

appcmd set config Default Web Site sectionodbcLogging

dataSourceBPC_ManagementDSN commitappHost

appcmd set config Default Web Site sectionodbcLogging tableNameBPCLog

commitappHost

appcmd set config Default Web Site sectionodbcLogging userNameUsername

commitappHost

appcmd set config Default Web Site sectionodbcLogging passwordmypassword

commitappHost

NOTE

You cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must

use the SQL Server ODBC driver For more information see the Microsoft Knowledge Base article

931202 The requirements for using the ODBC logging feature in IIS

343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2

ProcedureThis procedure describes how to set up an ODBC data source for the Management Console in Windows

Server 2008 or Windows Server 2008 R2

Proceed as follows

1 Open ODBC Connection Manager

2 On the System DSN tab page add a new DSN

Choose Add

Choose SQL Server as the driver

Choose Finish

3 In the Name and Description fields enter BPC_ManagementDSN

4 In the Server field enter the name of your SQL Server Choose Next

5 Leave the default settings and choose Next

6 Choose the Change the default database to field and enter AppServer Choose Next

7 Leave default settings and choose Next

8 Choose OK

344 Removing Default Access to the Console

NOTE

If you have chosen SAP BusinessObjects User Management System in the installation screen you

do not need to remove or configure access because the Management Console service always runs

with the System Admin ID account which is a member of the Administrators group

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3254 CUSTOMER 2012-06-13

ProcedureTo remove default access to the Management Console and create a group that does have access to the

console use the procedure described below

NOTE

Create your Management Console administrative group either on the server that hosts the

Management Console or in the Active Directory

1 In the context menu of the servers My Computer icon choose Manage

2 In the Computer Management dialog box choose Local Users and Groups Groups

NOTE

Alternatively you can perform analogous steps in Active Directory

3 In the 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

NOTE

This step is a necessary precursor to the completion of this procedure

10 In the Security dialog box click Copy to ensure that the System group retains its privileges

11 Remove access to the Management Console from all groups that should not have it

12 Choose Authentication in the center pane then disable Windows authentication

ResultUsers who have not been granted access to the Management Console can still open the Management

Console Web page but it contains no data or menu options This does not affect the access that a user

would otherwise have to Planning and Consolidation

345 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 32] Their rights in

Active Directory determine what they can access in the Console

By default any member of the Administrators Active Directory group on the application server or

domain has full access to all of the features of the Console except the Planning and Consolidation

logging area Access to Planning and Consolidation logging is controlled within the Planning and

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3354

Consolidation Administration Client task security The user must be granted View system logs task

privileges For more information see the SAP Library Planning and Consolidation Administrators Guide in

httpservicesapcominstguidesepm-bpc 100 version for the Microsoft platform

Your IT policy determines whether you grant access by group or user You may wish to create several

levels of Console users (read-only users for example) in your environment

To grant or limit access to users or groups you can add or remove the following privileges from the

areas described in this table

Privilege Rights Management Area

Task Manager and Kill Process Administrators group on application server or domain

Performance Monitor Counters Administrators group on application server or domain Power Users group on application server or domain Performance Monitor Users group on application server

Microsoft Analysis Services performance monitoring

Administrators group on application server or domain

Microsoft SQL Server Monitoring (performance counters and statistics)

Administrators group on application server or domain

346 Using Client Certificates

To enable the use of client certificates in Planning and Consolidation you must follow several manual

steps

NOTE

Planning 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 httptechnetmicrosoftcomen-us

librarycc753810aspx

For more information about configuring the client certificate mapping authentication see http

technetmicrosoftcomen-uslibrarycc732996(WS10)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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3454 CUSTOMER 2012-06-13

This option allows you to use a client certificate or username and password (Basic

authentication) to connect to Planning and Consolidation

2 Enable anonymous authentication

1 In the IIS Manager expand the node of the Planning and Consolidation web site

2 Select the ManagementConsole directory (ltWebsitegtManagementConsole) to open the

ManagementConsole home page

3 Double-click Authentication and enable Anonymous Authentication

4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way

as in step 3

5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the same

way as in step 3

3 Change the web configuration settings

1 Open the ltPC_MSgtWebsrvrWebBPCwebconfig file

2 Find the text clientCredentialType=Windows

3 Change value of clientCredentialType to None (clientCredentialType=None)

4 Open the PC_MSWebsrvrWebPOASBCwebconfig file Repeat steps 2 and 3

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3554

This page is left blank for documents that are printed on both sides

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

The installation of the Planning and Consolidation Administration Client allows administrators to

build and maintain Planning and Consolidation environments and models and administer security

All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions

add-in for Microsoft Office for more information see the SAP BusinessObjects EPM solutions add-in for

Microsoft Office help

NOTE

You must update the Administration Client to the same version as the server

If your PC is on a different domain than your server you must set the Internet Explorer

Security Zone value of the Planning and Consolidation client to prompt for user name and

password Otherwise the Planning and Consolidation Start Page does not display

41 Installing the Administration Client

Prerequisites

NOTE

For a definitive list of system requirements see the Product Availability Matrix on SAP Service

Marketplace at httpservicesapcompam Search on Planning and Consolidation

The following list describes the minimum software requirements

Microsoft Internet Explorer 70 or 80

Microsoft Office 2007 or 2010

NET Framework 20 or higher (install any required NET Framework Hotfixes by referring to

httpsupportmicrosoftcomkb)

Pentium IV (1 GHz CPU)

512 MB RAM

100 MB of free hard disk space in the My Documents folder

20 MB of free hard disk space for the installed Administration files

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

41 Installing the Administration Client

2012-06-13 CUSTOMER 3754

NOTE

We recommend that you install all of the latest Microsoft Windows hotfixes prior to installing

the Administration client For information about which hotfixes to install see http

updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us

ProcedureThe following procedure describes how to install the Administration Client on to an administratorrsquos

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 AddRemove Programs in the Windows Control Panel

3 Point your browser to the Planning and Consolidation Web at httpltPC_serverportgtsap

bpcweb

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

42 Installing the EPM Add-in

The Planning and Consolidation installation media does not contain the EPM addin setup program

You must download the most recent version of the full setup (EPM Add-inexe) from the Service

Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPC

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

43 Using the Client Auto Update Program

If Planning and Consolidation version 100 or later is installed you can use the Client Auto Update

program to set up the server so that it determines if an upgrade for a connecting Administration client

is necessary

The following describes the use of the auto update program for the Administration Client and the EPM

add-in

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

42 Installing the EPM Add-in

3854 CUSTOMER 2012-06-13

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 37]

To use the Client Auto Update program for the Administration Client proceed as follows

1 From the Server Manager select Options Client Options

2 Select Admin Update

3 If users without administrator rights on their machines use the auto update enter an administrator

ID and password in the Admin ID and Admin password fields respectively The Admin ID should be a

member of the local administrators group on all the computers running the auto update This

setting is not needed if all users have administrator rights on their machines

4 Select Update

For the EPM Add-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 Optionshellip 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 Market Place (SMP) at httpservicesapcom

All support packages and patches are available from the SMP as a zip file

EPMEXCLCLNTltSPLgtzip is for a support package

EPMEXCLCLNTltSPLgtPltPLgtzip 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 ltSP versiongtmsp

EPM Addin Support Package ltSP versiongtxml

For a patch these files are

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

2012-06-13 CUSTOMER 3954

EPM Addin Patch ltpatch numbergtmsp

EPM Addin Patch ltpatch numbergtxml

2 Unzip the zip file and extract the two files to the application server folder (WebsrvrWebBPC

Installation)

3 From the Server Manager select Options Client Options

The system lists the available packages Select the package that you want to use for the autoupdate

You can set a different update policy for each package listed

EXAMPLE

The following table illustrates some possible situations assuming that you have installed the

first full version (V1)

Available maintenance packages

V2-user updateV3-force updateV4-force updateV5-user update

V5-user update V5-user updateV6-auto updateV7-force update

Minimum Required Version

V4 V4 V7

Notification A prompt tells the user to install maintenance package V4 using the Forced Update behavior

If User Update is enabled the prompt informs the user that maintenance package V5 is available

A prompt tells the user to install maintenance package V7 using the Forced Update behavior

New Version V4 V4 or V5 V7

If you change the update policy for any package click Update to complete the change

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

4054 CUSTOMER 2012-06-13

5 Connection Issues

You may experience connection problems with ports the proxy server or programs and settings that

interact with these components If you have any issues related to connection review the following

recommendations and troubleshooting tips

51 Checking for Open Ports

You must ensure that all required ports are open for inboundoutbound 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 431181836 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

NOTE

You can use the following site to scan for the normal ports It allows you to manually enter a port

number to test

httpwwwmyserverorgportsniffasp

You can change the name of a port

52 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 Explorer Tools Internet Options Connections LAN Settings ) or at the server level

Enabling content filtering on the proxy server or firewall may cause connection problems

If external users are having trouble connecting to the server make sure the proxy server connects

using a fully qualified domain name Fully qualified domain names typically resolve both internal

and external IP addresses

Each secure Planning and Consolidation server name must be identified on the proxy server

Proxy servers may or may not require authentication which could conflict with Planning and

Consolidation authentication Do not use authentication on the proxy server The system

5 Connection Issues

51 Checking for Open Ports

2012-06-13 CUSTOMER 4154

synchronizes the user name and password on the remote server with the local user name and

password

NOTE

For more information about setting up an ISA proxy server contact SAP Support to request a

copy of Setting up ISA Proxy Server White Paper

Internet Explorer Settings 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

5 Connection Issues

52 Proxy Server and Firewall Issues

4254 CUSTOMER 2012-06-13

6 Installing Planning and Consolidation with Two Active Directory Domains

To set up a Planning and Consolidation 10 application server in a hosted environment and use your

own domain users follow this procedure In general you install Planning and Consolidation on the

host domain use the host domain account and assign it to the Planning and Consolidation users

SysAdmin Admin and Users Then you accept one way trust (the host domain trusts your domain)

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

6 Installing Planning and Consolidation with Two Active Directory Domains

2012-06-13 CUSTOMER 4354

This page is left blank for documents that are printed on both sides

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

This section describes best practices and instructions for installing Planning and Consolidation in a

Terminal Services or Citrix Server deployment

71 Terminal Services Home Directories

We recommend using Terminal Server home directories rather than using the userrsquos 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

72 System Requirements

The Citrix server should be one of the following systems

XenApp 5 Enterprise

XenApp 5 Platinum

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 37])

73 Installing Planning and Consolidation

Prerequisites

The server installation files have been downloaded from SAP Service Marketplace and installed

Procedure

The following steps outline how to install the Planning and Consolidation clients in a Terminal Services

(TS) or Citrix Server deployment

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

71 Terminal Services Home Directories

2012-06-13 CUSTOMER 4554

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 userinstall

4 Open a browser and connect to the URL httpltPC_serverportgtsapbpcweb

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 userexecute 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 Iexploreexe http(s)

ltServerNamegt-NetBIOS or FQDNsapbpcweb

To publish Planning and Consolidation Administration CProgram FilesPC_MS

BPCAdminMainexe

74 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 userrsquos desktop) must be moved to the All UsersDesktop folder

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

74 Creating a Shortcut to the Launch Page

4654 CUSTOMER 2012-06-13

8 Installing SSIS Custom Tasks

This section provides background information and instructions for installing SQL Server Integration

Services (SSIS) for SQL Server 2008 and SQL Server 2012

The Planning and Consolidation Data Manager component supports and uses SSIS Since SQL Server

2008 and SQL Server 2012 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

81 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 Filelistxml 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

OSoftSetupexe ‒ 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 or OSoftSSIS2012_Client on the client machine followed by the SQL Server

version If you want to use SQL 2008 Tasks under the SQL 2012 environment you must install

OSoftSSIS2008_Client on the application server For detailed information see SAP Note 1707410

You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package by extracting

OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPC

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 or

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4754

OSoftSSIS2012_Client for creating a COM+ application For more information see Before You Modify

the SSIS Packages [page 50] and Setup of a COM+ Application on the Application Server [page 51]

Bin folder

This folder contains the following components

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCCachedll Planning and Consolidation Cache file

BPCDataFlowPackagedll or BPCDataFlowPackage2012dll

BPCDMdll

BPCDMTaskMaindll COM+ component

BPCFilePreviewdll

BPCGacUtil_20exe System File

BPCGacUtil_40exe System File

BPCImpersonatordll Planning and Consolidation Impersonator

BPCLogicdll

BPCScriptdll

BPCServerZipdll

BPCServiceResdll

BPCTransferMembersdll

BPCWriteBackdll

InteropDTSdll

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

4854 CUSTOMER 2012-06-13

Name Remark

OSoftAdminServerdll

OSoftAuditdll

OSoftComLibServerdll

OSoftCommonResQrydll

OSoftConfigurationdll

OSoftCustomXMLSvrdll

OSoftDatabaseADMINdll

OSoftDatabaseSYSADMINdll

OSoftDatabaseSYSADMINDMdll

OSoftDatabaseUSERdll

OSoftDMDTSXExecutedll or OSoftDMDTSXExecute2012dll

OSoftDMTaskFormdll

OSoftDMTaskMaindll

OSoftDMToolsdll

OSoftFileManagedll

OSoftLoggingdll

OSoftLogWriterdll

OSoftMetaDatadll

OSoftSQEdll

OSoftSystemConfigdll

OutlookSoftconfig Configuration file to connect DB server

XceedCompressiondll XceedZip file

XceedCompressionFormatsdll XceedZip file

XceedFileSystemdll XceedZip file

XceedZipdll XceedZip file

Config folder

This folder has FileListxml 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 FileListxml 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

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4954

OSoftSetupexe

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

NOTE

If you installed the OSoftSSIS2008_Client or OSoftSSIS2012_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

Resources Folder

This folder contains the BPCServicesdll and BPCServiceUIdll files which contain resource text

Only English resources are included for the SSIS custom tasks

82 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

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008 and 2012 respectively

8 Installing SSIS Custom Tasks

82 Before You Modify the SSIS Packages

5054 CUSTOMER 2012-06-13

Name Remark

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012 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

lthellipgtOSoftSSIS2008_Clientbin or lthellipgtOSoftSSIS2012_Clientbin

On the Planning and Consolidation application server

ltdrivegtWebsrvrbin

2 Paste these files into the folder 100DTSTasks for SQL Server 2008 or into 110DTSTasks for

SQL Server 2012 For example if you install your SQL 2008 server or R2 on CProgram Files

Microsoft SQL Server paste all files into the CProgram Files (x86)Microsoft SQL Server

100DTSTasks folder

In Integration Services set the property Run64BitRunTime to True

83 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 or OSoftSSIS2012_Client on the

application server

8 Installing SSIS Custom Tasks

83 Setup of a COM+ Application on the Application Server

2012-06-13 CUSTOMER 5154

Typographic Conventions

Example Description

ltgt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example Enter your ltUser Namegt

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 httpwwwsapcom

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

5254 CUSTOMER 2012-06-13

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

  • SAP BusinessObjects Planning and Consolidation 100
    • Table of Contents
    • 1 Introduction
      • 11 SAP Notes for the Installation
      • 12 Naming Conventions
        • 2 Installing Planning and Consolidation Servers
          • 21 Basic Steps
          • 22 Prerequisites
          • 23 Before Starting the Planning and Consolidation Server Installation
          • 24 Logging on to Servers
          • 25 Service-level Accounts
          • 26 Standard and Advanced Settings
          • 27 Installing the Prerequisites
            • 271 Installing the Prerequisites ndash Basic Steps
            • 272 Installing the Operating System
            • 273 Installing the SQL Server
            • 274 Installing Analysis Services
            • 275 Installing the Anti-Cross Site Scripting Library
              • 28 Installing on a Single Server
              • 29 Installing the Server in a Multiserver Configuration
                • 3 After Installing Planning and Consolidation Servers
                  • 31 Post-Installation Steps
                  • 32 Connecting to Solution Manager Diagnostics
                  • 33 Configuring the Planning and Consolidation NET Application Servers
                  • 34 Post-Installation Optional Configuration Steps
                    • 341 Enabling the Management Console
                    • 342 Setting Up ODBC Logging in IIS for the Default Web Site
                    • 343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2
                    • 344 Removing Default Access to the Console
                    • 345 Management Console Access Control
                    • 346 Using Client Certificates
                        • 4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office
                          • 41 Installing the Administration Client
                          • 42 Installing the EPM Add-in
                          • 43 Using the Client Auto Update Program
                            • 5 Connection Issues
                              • 51 Checking for Open Ports
                              • 52 Proxy Server and Firewall Issues
                                • 6 Installing Planning and Consolidation with Two Active Directory Domains
                                • 7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
                                  • 71 Terminal Services Home Directories
                                  • 72 System Requirements
                                  • 73 Installing Planning and Consolidation
                                  • 74 Creating a Shortcut to the Launch Page
                                    • 8 Installing SSIS Custom Tasks
                                      • 81 Composition of SSIS Custom Task Installation
                                      • 82 Before You Modify the SSIS Packages
                                      • 83 Setup of a COM+ Application on the Application Server
                                          • Copyright and trademarks
Page 20: Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

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 CEnvironmentShelldb10) 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 a 2008 2008 R2 and 2012 SQL Server

SQL Server Considerations

We recommend installing all required components in sequence For example install the Operating

System (Windows Server) then enable IIS and ASPNET and install any Windows Server service

packs

IIS and NET Framework 40 are required on your application server

NOTE

If you encounter a 500 HTTP Error when trying to connect to the Planning and Consolidation

Web Client refer to Microsoft Support articles 2520479 and 2468871 for assistance

To reinforce security we recommend that you install the SQL server and SSAS components to a

nondefault instance of SQL Server

General Installation Steps

1 Launch the SQL Server Setup program entering a product key if necessary and accepting the license

terms

2 Choose Install to install the SQL support files

3 In Feature Selections select instance and shared features as indicated in the SQL Server Component

Options section below then choose Next

4 Review disc space requirements then choose Next

5 In Server Configuration Perform the following actions

1 In the Service Accounts tab enter a Planning and Consolidation sysadmin account for the SQL

Server Database Engine and the SQL Server Analysis services This is required so that the Planning

and Consolidation sysadmin can create and process the Planning and Consolidation database

because the Microsoft SQL server tries to back up or restore database with the privileged

account This account is also required during Backup Environment and Restore Environment in the

Server Manager

For a single-server environment this account is also required if the backup file is located in a

different domain machine because SQL tries to access the folders and files with this account

For the a multiple-server environment SQL server retrieves the information of backup file

from the application server and the account requires the folder access privilege for the

application server

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2054 CUSTOMER 2012-06-13

To ensure that you have the complete access privileges we recommend the Planning and

Consolidation sysadmin for this service account

2 In the Collation tab set the collation settings to SQL_Latin1_General_CP1_CI_AS

Choose Next

6 Set Database Engine Configuration options then choose Next

We recommend you choose Mixed mode (Windows authentication and SQL authentication) This allows you

to use a restrictive SQL ID that works with the drill-through feature If you must restrict SQL

authentication for security reasons you can define a specific parameter in your drill-through

queries If you do not need drill-through support or use it without leveraging SQL authentication

you can install the SQL Server in Windows-only mode

7 Accept the Analysis Services Configuration default options and the remaining default options of the

installation program

8 Choose Install to begin the installation with the options you have set

SQL Server Component 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

Server Component What to Install

SQL Server Database Engine Services

SSAS Server Analysis Services

Application Server The following Shared Features Client Tools Connectivity Integration Services Client Tools SDK

Custom Settings for the SQL Server

As of version 100 Planning and Consolidation supports the following new features for SQL Server 2008

SQL Server 2008 R2 and SQL Server 2012

Process Dimension

It is now possible to process a dimension with multiple selections At processing time the process

dimension module makes changed or added information for each dimension and process for all selected

dimensions and cubes in parallel

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 2154

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

NOTE

Setting 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 tblFactWBltappgt table

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 Microsoftreg SQL Servertrade

20052008 which you can download from wwwmicrosoftcom (search on ldquoTable Partitioningrdquo to find

all relevant articles)

After Installing SQL Server 2008 SQL Server 2008 R2 and SQL Server 2012

From SQL Server Configuration Manager confirm that the SQL Server Browser service is

running The browser service is required for Planning and Consolidation

From SQL Server Configuration Manager do the following

1 Select Protocols for ltInstanceNamegt then double-click TCPIP from the right side of the window

2 When prompted for the TCPIP Properties select IP Addresses You see two IPs that indicate the

localhost and external network interface machine

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2254 CUSTOMER 2012-06-13

3 If you want to use IP1 which indicates Server IP set Enabled to Yes and specify the TCP Port as

desired

4 Delete 0 from TCP Dynamic Ports Set IPAll - TCP Ports as desired (for example 1533)

RECOMMENDATION

We do not recommend using dynamic ports

In an SQL server the default instance has a listener which listens on a fixed port (TCP

port 1433) However for the named instance the port on which the SQL server listens is

random and dynamically selected when the named instance of the SQL server starts This

recommendation prevents any conflict problems

From the SQL Server Configuration Manager specify the client protocol options for the application

server

1 Select Client Protocols from the SQL Native Client Configuration folder

2 From the right side of the window double-click TCPIP The TCPIP 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

NOTE

We 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

274 Installing Analysis Services

ProcedureAfter you install SQL Server and its required service packs and hotfixes you must install SQL Server

Analysis Services and its required service packs and hotfixes

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 2354

NOTE

If you have migrated your Analysis Services repository to the SQL Server back up the database

that contains the repository before installing this release

To install Analysis Services for SQL Server 2008 SQL Server 2008 R2 or SQL Server 2012 follow the steps

and guidelines in httptechnetmicrosoftcomen-uslibraryms143219aspx

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 httpwwwmicrosoftcomdownloads

detailsaspxFamilyID=3be0488d-e7aa-4078-a050- ae39912d2e43ampdisplaylang=en

275 Installing the Anti-Cross Site Scripting Library

Procedure

Before installing Planning and Consolidation servers you must download the Anti-Cross Site Scripting

Library (version 42 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 AntiXSSLibraryDLL from the Microsoft Web

site at httpwwwmicrosoftcomdownloadendetailsaspxid=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 AntiXssLibrarydll

28 Installing on a Single Server

When you install all Planning and Consolidation server components on a single server you should

consider the following issues

Make sure the server has a minimum of 800 MB of hard disk space

Additional environment installations require more free disk space which is a minimum of two

times the uncompressed size of the environment files

When you install Planning and Consolidation on a single-server the system adds the following server

components

SQL Server

SQL Server Analysis Services (SSAS)

Application Server

FileShare server

Procedure

To install Planning and Consolidation on a single server take the following steps

1 Exit all Windows programs

2 Installing Planning and Consolidation Servers

28 Installing on a Single Server

2454 CUSTOMER 2012-06-13

2 Log on to the server with a local server user ID or domain user ID For more information see Logging

on to servers [page 14]

3 Make sure all prerequisite software is installed on the server For more information see Installing

the Prerequisites [page 17]

4 Obtain SAP Planning and Consolidation from the Downloads SAP Installations amp Upgrades area of

SAP Service Marketplace then extract the files and run StartUpexe

5 From the Server Install screen select Install the Planning and Consolidation server

6 From the Welcome screen choose Next

7 From the License Agreement page choose I accept the terms of the license agreement then choose Next

8 From the Installation Method page accept the default Single machine enter a system ID for the system

landscape directory (SLD) and choose Next

NOTE

Entering a system ID of the SLD is only required if you have a SAP Solution Manager license

If you do not have a SAP Solution Manager license you can leave this field empty

9 From the Authentication Method page choose the desired authentication method and choose Next

10 If you have chosen SAP BusinessObjects User Management System in the previous screen on the CMS

Authentication page enter the information required to log on to CMS as an administrator

The following information is required

Field Description

System name CMS system name (server nameport number) for example CMSServer6400

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

11 After entering the CMS administrator authentication details choose Next

12 From the Service type accounts page enter service-level account user IDs and passwords See Service-

Level Accounts [page 15]

13 After defining the IDs and passwords choose Next

14 From the Server Information page (see Standard and Advanced Settings [page 16]) do one of the following

Review the standard settings and choose Next

To set advanced settings choose the Advanced Settings button Enter the desired information

and choose Next

2 Installing Planning and Consolidation Servers

28 Installing on a Single Server

2012-06-13 CUSTOMER 2554

15 Specify the location and name of AntiXssLibrarydll See Installing the Anti-Cross Site Scripting Library [page

24]

Choose Next

16 Select destination folders for Programs and Data The Data files include Webfolders and FileDB

(published reports) and should be installed on a separate drive in a production environment This

recommendation reduces the hard disk IO time and helps to speed up SQL commands

Accept the defaults or make your selections then choose Next

17 Select the default values for the Web client The values are used to determine the default language

and region for the Web client when you connect to it You can change the values in the Planning

and Consolidation Server Manager

18 The installation process takes a few moments When it is complete choose Exit

19 A prompt is displayed to restart your computer Select OK to restart

20 Perform the steps in After Installing Planning and Consolidation Servers [page 27]

29 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 24]) with the following

exceptions

On the Installation Method page do not accept the default instead choose Network Load Balancing

environment With this option there is an additional choice to Include sample environment (required on only

one of the application servers) This is because when you install the application server it connects to the

database server and creates the sample environment (EnvironmentShell) Installing the sample

environment is required on only one application server and you may choose which one

In the Virtual Name field enter the virtual IP address virtual name in the default properties

2 Installing Planning and Consolidation Servers

29 Installing the Server in a Multiserver Configuration

2654 CUSTOMER 2012-06-13

3 After Installing Planning and Consolidation Servers

31 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 28]

2 Configure the Planning and Consolidation NET and application server to ensure that it and its

related services function properly and reliably For more information see Configuring the Planning and

Consolidation NET Application Server [page 29]

3 Optional configuration steps [page 30]

1 To ensure proper functioning of the Management Console create an SQL user and modify

the System DSN and IIS to reflect those user credentials See Enabling Management Console [page

30]

2 Configure custom ODBC logging for the default Web site For details of how to configure

custom logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web

Site [page 31]

3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC

Data Source [page 32]

4 Modify the default access rights to the Management Console By default users in Active

Directory can access the Management Console with whatever rights they have been granted

on the server For information about removing default access and creating a group that can

access the console see Removing Default Access to the Console [page 32]

5 Add authorized users or groups to the group that can access the Management Console We

recommend that you only grant Management Console access to system administrators

Planning and Consolidation users should not have any access For more information see

Management Console Access Control [page 33]

6 Configure the use of client certificates for authentication See Using Client Certificates [page

34]

4 Take the following steps to set up security

If you are defining security and application structure continue with step 5

3 After Installing Planning and Consolidation Servers

31 Post-Installation Steps

2012-06-13 CUSTOMER 2754

If you want to designate someone other than the system administrator to manage security

and application structure log on to EnvironmentShell designate a user as a Primary

Administrator

This user must have Administration ‒ Environment and Security ‒ Define User task rights

so that he or she can add and delete environments and define user security

The Primary Administrator can continue with the next step (5)

5 From the machine on which you administer Planning and Consolidation install the

Administration client See Installing the Administration Client [page 37]

6 Start Planning and Consolidation Administration from the launch page

7 Select Connection Wizard and log on to EnvironmentShell

8 Create a new environment using EnvironmentShell as the source

9 Log on to the newly created environment and set up users teams and task profiles (You must

set up task profiles since there is no access to Planning and Consolidation tasks)

10 Set up your data access profiles and add users (or teams) to one or more data access profiles (You

must complete this step since there is no access to dimensions or members)

NOTE

To allow users to request and query large amounts of data you can edit the metabasexml file located

at CWindowssystem32inetsrv Set the following parameters to the stated values

ASPBUFFERINGLIMIT = 10485760

MAXREQUESTENTITYALLOWED = 10485760

32 Connecting to Solution Manager Diagnostics

NOTE

You only need to perform the steps in this section if you have a SAP Solution Manager licence

The diagnostics functions in SAP Solution Manager allow identification analysis and resolution of

problems This procedure provides the steps required to connect Planning and Consolidation to

Solution Manager Diagnostics

Procedure

1 Install the Diagnostics Agent according to SAP Note 1234387 on all servers where application servers

are installed

NOTE

Installation files for Diagnostics Agent are available on Service Marketplace by navigating to

Support Packages and Patches mdash Entry by Application Group SAP Technology Components SAP

SOLUTION MANAGER SAP SOLUTION MANAGER 70 EHP 1 Entry by Component Agents

for managed systems DIAGNOSTICS AGENT 711

3 After Installing Planning and Consolidation Servers

32 Connecting to Solution Manager Diagnostics

2854 CUSTOMER 2012-06-13

Download the installation file based on the 64-bit Windows Server system landscape

2 To access the DBA Cockpit you must create a user account with sufficient rights on all Windows

Servers where Microsoft SQL Server is installed Do the following

1 Start Computer Management then select Action New User

2 Create a new user

3 Right-click on the user then choose Properties On the Member Of tab select Add

4 Add the group SQLServerltReleasegtSQLAgentUser$ltDomain or hostnamegt$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 httpsservicesapcom~sapidb011000358700000074392009E and follow

the chapters that apply to Planning and Consolidation

33 Configuring the Planning and Consolidation NET Application Servers

Procedure

Modifying machineconfig Files

To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock

occurrences that would cause the application server to ldquosleeprdquo and not process anymore you can

modify the machineconfig file which resides in the WINDOWSMicrosoftNETFramework64

v4030319Config directory

1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to

specify whether to automatically configure settings to achieve optimal performance based on the

machine configuration You can set this attribute to True or False

For more information see httpmsdnmicrosoftcomen-uslibrary7w2sway1aspx

2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the

Planning and Consolidation application) or Machineconfig (for all applications including

Planning and Consolidation) to ensure the validationKey and decryptionKey keys have the same

value on all application servers This way when the authentication cookie is checked the

authentication ticket used on one server can still be valid on another server

For more information and sample Visual Basic code for generating random key values see http

msdnmicrosoftcomen-uslibraryms998288aspx

3 After Installing Planning and Consolidation Servers

33 Configuring the Planning and Consolidation NET Application Servers

2012-06-13 CUSTOMER 2954

paght000007_webfarmdeploymentconsiderations and httpmsdnmicrosoftcomen-us

libraryms998310aspx

34 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 30]

2 Configure custom ODBC logging for the default Web site For details of how to configure custom

logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page

31]

3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC Data

Source [page 32]

4 Modify the default access rights to the Management Console By default users in Active Directory

can access the Management Console with whatever rights they have been granted on the server

For information about removing default access and creating a group that can access the console

see Removing Default Access to the Console [page 32]

5 Add authorized users or groups to the group that can access the Management Console We

recommend that you only grant Management Console access to system administrators Planning

and Consolidation users should not have any access For more information see Management Console

Access Control [page 33]

6 Configure the use of client certificates for authentication See Using Client Certificates [page 34]

341 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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3054 CUSTOMER 2012-06-13

NOTE

Without these updates the Management Console does work but some functionality (specifically

User Activity and Service Status) does not work as expected

Should you need to uninstall Planning and Consolidation we recommend that you reset the

Active Log Format field in IIS to W3C Extended Log File Format

342 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 ApplicationHostconfig set the property customLogPluginClsid to the value FF16065B-

DE82-11CF-BC0A-00AA006111E0 Set the logFormat to Custom You can find this in the ltlogFilegt

node in ApplicationHostconfig as shown here

ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0

logFormat=Custom gt

Use the following AppCmds to configure IIS to use ODBC logging for the default Web site

appcmd site set sitenameDefault Web Site

logFilecustomLogPluginClsidFF16065B-DE82-11CF-BC0A-00AA006111E0

appcmd site set sitenameDefault Web Site logFilelogFormatCustom

Configuring ODBC Logging Parameters in ApplicationHostconfig

Configure ApplicationHostconfig to contain the database table information as set up in the Microsoft

Support article specified in the Prerequisites section Configure these settings in the ltodbcLogginggt

node under ltsystemwebServergt

EXAMPLE

ltlocation path=Default Web Sitegt

ltsystemwebServergt

ltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog

userName=Username password=mypassword gt

ltsystemwebServergt

ltlocationgt

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3154

Use the following AppCmds to configure these attributes for the default Web site

appcmd set config Default Web Site sectionodbcLogging

dataSourceBPC_ManagementDSN commitappHost

appcmd set config Default Web Site sectionodbcLogging tableNameBPCLog

commitappHost

appcmd set config Default Web Site sectionodbcLogging userNameUsername

commitappHost

appcmd set config Default Web Site sectionodbcLogging passwordmypassword

commitappHost

NOTE

You cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must

use the SQL Server ODBC driver For more information see the Microsoft Knowledge Base article

931202 The requirements for using the ODBC logging feature in IIS

343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2

ProcedureThis procedure describes how to set up an ODBC data source for the Management Console in Windows

Server 2008 or Windows Server 2008 R2

Proceed as follows

1 Open ODBC Connection Manager

2 On the System DSN tab page add a new DSN

Choose Add

Choose SQL Server as the driver

Choose Finish

3 In the Name and Description fields enter BPC_ManagementDSN

4 In the Server field enter the name of your SQL Server Choose Next

5 Leave the default settings and choose Next

6 Choose the Change the default database to field and enter AppServer Choose Next

7 Leave default settings and choose Next

8 Choose OK

344 Removing Default Access to the Console

NOTE

If you have chosen SAP BusinessObjects User Management System in the installation screen you

do not need to remove or configure access because the Management Console service always runs

with the System Admin ID account which is a member of the Administrators group

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3254 CUSTOMER 2012-06-13

ProcedureTo remove default access to the Management Console and create a group that does have access to the

console use the procedure described below

NOTE

Create your Management Console administrative group either on the server that hosts the

Management Console or in the Active Directory

1 In the context menu of the servers My Computer icon choose Manage

2 In the Computer Management dialog box choose Local Users and Groups Groups

NOTE

Alternatively you can perform analogous steps in Active Directory

3 In the 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

NOTE

This step is a necessary precursor to the completion of this procedure

10 In the Security dialog box click Copy to ensure that the System group retains its privileges

11 Remove access to the Management Console from all groups that should not have it

12 Choose Authentication in the center pane then disable Windows authentication

ResultUsers who have not been granted access to the Management Console can still open the Management

Console Web page but it contains no data or menu options This does not affect the access that a user

would otherwise have to Planning and Consolidation

345 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 32] Their rights in

Active Directory determine what they can access in the Console

By default any member of the Administrators Active Directory group on the application server or

domain has full access to all of the features of the Console except the Planning and Consolidation

logging area Access to Planning and Consolidation logging is controlled within the Planning and

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3354

Consolidation Administration Client task security The user must be granted View system logs task

privileges For more information see the SAP Library Planning and Consolidation Administrators Guide in

httpservicesapcominstguidesepm-bpc 100 version for the Microsoft platform

Your IT policy determines whether you grant access by group or user You may wish to create several

levels of Console users (read-only users for example) in your environment

To grant or limit access to users or groups you can add or remove the following privileges from the

areas described in this table

Privilege Rights Management Area

Task Manager and Kill Process Administrators group on application server or domain

Performance Monitor Counters Administrators group on application server or domain Power Users group on application server or domain Performance Monitor Users group on application server

Microsoft Analysis Services performance monitoring

Administrators group on application server or domain

Microsoft SQL Server Monitoring (performance counters and statistics)

Administrators group on application server or domain

346 Using Client Certificates

To enable the use of client certificates in Planning and Consolidation you must follow several manual

steps

NOTE

Planning 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 httptechnetmicrosoftcomen-us

librarycc753810aspx

For more information about configuring the client certificate mapping authentication see http

technetmicrosoftcomen-uslibrarycc732996(WS10)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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3454 CUSTOMER 2012-06-13

This option allows you to use a client certificate or username and password (Basic

authentication) to connect to Planning and Consolidation

2 Enable anonymous authentication

1 In the IIS Manager expand the node of the Planning and Consolidation web site

2 Select the ManagementConsole directory (ltWebsitegtManagementConsole) to open the

ManagementConsole home page

3 Double-click Authentication and enable Anonymous Authentication

4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way

as in step 3

5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the same

way as in step 3

3 Change the web configuration settings

1 Open the ltPC_MSgtWebsrvrWebBPCwebconfig file

2 Find the text clientCredentialType=Windows

3 Change value of clientCredentialType to None (clientCredentialType=None)

4 Open the PC_MSWebsrvrWebPOASBCwebconfig file Repeat steps 2 and 3

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3554

This page is left blank for documents that are printed on both sides

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

The installation of the Planning and Consolidation Administration Client allows administrators to

build and maintain Planning and Consolidation environments and models and administer security

All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions

add-in for Microsoft Office for more information see the SAP BusinessObjects EPM solutions add-in for

Microsoft Office help

NOTE

You must update the Administration Client to the same version as the server

If your PC is on a different domain than your server you must set the Internet Explorer

Security Zone value of the Planning and Consolidation client to prompt for user name and

password Otherwise the Planning and Consolidation Start Page does not display

41 Installing the Administration Client

Prerequisites

NOTE

For a definitive list of system requirements see the Product Availability Matrix on SAP Service

Marketplace at httpservicesapcompam Search on Planning and Consolidation

The following list describes the minimum software requirements

Microsoft Internet Explorer 70 or 80

Microsoft Office 2007 or 2010

NET Framework 20 or higher (install any required NET Framework Hotfixes by referring to

httpsupportmicrosoftcomkb)

Pentium IV (1 GHz CPU)

512 MB RAM

100 MB of free hard disk space in the My Documents folder

20 MB of free hard disk space for the installed Administration files

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

41 Installing the Administration Client

2012-06-13 CUSTOMER 3754

NOTE

We recommend that you install all of the latest Microsoft Windows hotfixes prior to installing

the Administration client For information about which hotfixes to install see http

updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us

ProcedureThe following procedure describes how to install the Administration Client on to an administratorrsquos

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 AddRemove Programs in the Windows Control Panel

3 Point your browser to the Planning and Consolidation Web at httpltPC_serverportgtsap

bpcweb

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

42 Installing the EPM Add-in

The Planning and Consolidation installation media does not contain the EPM addin setup program

You must download the most recent version of the full setup (EPM Add-inexe) from the Service

Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPC

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

43 Using the Client Auto Update Program

If Planning and Consolidation version 100 or later is installed you can use the Client Auto Update

program to set up the server so that it determines if an upgrade for a connecting Administration client

is necessary

The following describes the use of the auto update program for the Administration Client and the EPM

add-in

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

42 Installing the EPM Add-in

3854 CUSTOMER 2012-06-13

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 37]

To use the Client Auto Update program for the Administration Client proceed as follows

1 From the Server Manager select Options Client Options

2 Select Admin Update

3 If users without administrator rights on their machines use the auto update enter an administrator

ID and password in the Admin ID and Admin password fields respectively The Admin ID should be a

member of the local administrators group on all the computers running the auto update This

setting is not needed if all users have administrator rights on their machines

4 Select Update

For the EPM Add-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 Optionshellip 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 Market Place (SMP) at httpservicesapcom

All support packages and patches are available from the SMP as a zip file

EPMEXCLCLNTltSPLgtzip is for a support package

EPMEXCLCLNTltSPLgtPltPLgtzip 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 ltSP versiongtmsp

EPM Addin Support Package ltSP versiongtxml

For a patch these files are

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

2012-06-13 CUSTOMER 3954

EPM Addin Patch ltpatch numbergtmsp

EPM Addin Patch ltpatch numbergtxml

2 Unzip the zip file and extract the two files to the application server folder (WebsrvrWebBPC

Installation)

3 From the Server Manager select Options Client Options

The system lists the available packages Select the package that you want to use for the autoupdate

You can set a different update policy for each package listed

EXAMPLE

The following table illustrates some possible situations assuming that you have installed the

first full version (V1)

Available maintenance packages

V2-user updateV3-force updateV4-force updateV5-user update

V5-user update V5-user updateV6-auto updateV7-force update

Minimum Required Version

V4 V4 V7

Notification A prompt tells the user to install maintenance package V4 using the Forced Update behavior

If User Update is enabled the prompt informs the user that maintenance package V5 is available

A prompt tells the user to install maintenance package V7 using the Forced Update behavior

New Version V4 V4 or V5 V7

If you change the update policy for any package click Update to complete the change

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

4054 CUSTOMER 2012-06-13

5 Connection Issues

You may experience connection problems with ports the proxy server or programs and settings that

interact with these components If you have any issues related to connection review the following

recommendations and troubleshooting tips

51 Checking for Open Ports

You must ensure that all required ports are open for inboundoutbound 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 431181836 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

NOTE

You can use the following site to scan for the normal ports It allows you to manually enter a port

number to test

httpwwwmyserverorgportsniffasp

You can change the name of a port

52 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 Explorer Tools Internet Options Connections LAN Settings ) or at the server level

Enabling content filtering on the proxy server or firewall may cause connection problems

If external users are having trouble connecting to the server make sure the proxy server connects

using a fully qualified domain name Fully qualified domain names typically resolve both internal

and external IP addresses

Each secure Planning and Consolidation server name must be identified on the proxy server

Proxy servers may or may not require authentication which could conflict with Planning and

Consolidation authentication Do not use authentication on the proxy server The system

5 Connection Issues

51 Checking for Open Ports

2012-06-13 CUSTOMER 4154

synchronizes the user name and password on the remote server with the local user name and

password

NOTE

For more information about setting up an ISA proxy server contact SAP Support to request a

copy of Setting up ISA Proxy Server White Paper

Internet Explorer Settings 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

5 Connection Issues

52 Proxy Server and Firewall Issues

4254 CUSTOMER 2012-06-13

6 Installing Planning and Consolidation with Two Active Directory Domains

To set up a Planning and Consolidation 10 application server in a hosted environment and use your

own domain users follow this procedure In general you install Planning and Consolidation on the

host domain use the host domain account and assign it to the Planning and Consolidation users

SysAdmin Admin and Users Then you accept one way trust (the host domain trusts your domain)

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

6 Installing Planning and Consolidation with Two Active Directory Domains

2012-06-13 CUSTOMER 4354

This page is left blank for documents that are printed on both sides

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

This section describes best practices and instructions for installing Planning and Consolidation in a

Terminal Services or Citrix Server deployment

71 Terminal Services Home Directories

We recommend using Terminal Server home directories rather than using the userrsquos 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

72 System Requirements

The Citrix server should be one of the following systems

XenApp 5 Enterprise

XenApp 5 Platinum

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 37])

73 Installing Planning and Consolidation

Prerequisites

The server installation files have been downloaded from SAP Service Marketplace and installed

Procedure

The following steps outline how to install the Planning and Consolidation clients in a Terminal Services

(TS) or Citrix Server deployment

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

71 Terminal Services Home Directories

2012-06-13 CUSTOMER 4554

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 userinstall

4 Open a browser and connect to the URL httpltPC_serverportgtsapbpcweb

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 userexecute 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 Iexploreexe http(s)

ltServerNamegt-NetBIOS or FQDNsapbpcweb

To publish Planning and Consolidation Administration CProgram FilesPC_MS

BPCAdminMainexe

74 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 userrsquos desktop) must be moved to the All UsersDesktop folder

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

74 Creating a Shortcut to the Launch Page

4654 CUSTOMER 2012-06-13

8 Installing SSIS Custom Tasks

This section provides background information and instructions for installing SQL Server Integration

Services (SSIS) for SQL Server 2008 and SQL Server 2012

The Planning and Consolidation Data Manager component supports and uses SSIS Since SQL Server

2008 and SQL Server 2012 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

81 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 Filelistxml 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

OSoftSetupexe ‒ 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 or OSoftSSIS2012_Client on the client machine followed by the SQL Server

version If you want to use SQL 2008 Tasks under the SQL 2012 environment you must install

OSoftSSIS2008_Client on the application server For detailed information see SAP Note 1707410

You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package by extracting

OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPC

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 or

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4754

OSoftSSIS2012_Client for creating a COM+ application For more information see Before You Modify

the SSIS Packages [page 50] and Setup of a COM+ Application on the Application Server [page 51]

Bin folder

This folder contains the following components

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCCachedll Planning and Consolidation Cache file

BPCDataFlowPackagedll or BPCDataFlowPackage2012dll

BPCDMdll

BPCDMTaskMaindll COM+ component

BPCFilePreviewdll

BPCGacUtil_20exe System File

BPCGacUtil_40exe System File

BPCImpersonatordll Planning and Consolidation Impersonator

BPCLogicdll

BPCScriptdll

BPCServerZipdll

BPCServiceResdll

BPCTransferMembersdll

BPCWriteBackdll

InteropDTSdll

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

4854 CUSTOMER 2012-06-13

Name Remark

OSoftAdminServerdll

OSoftAuditdll

OSoftComLibServerdll

OSoftCommonResQrydll

OSoftConfigurationdll

OSoftCustomXMLSvrdll

OSoftDatabaseADMINdll

OSoftDatabaseSYSADMINdll

OSoftDatabaseSYSADMINDMdll

OSoftDatabaseUSERdll

OSoftDMDTSXExecutedll or OSoftDMDTSXExecute2012dll

OSoftDMTaskFormdll

OSoftDMTaskMaindll

OSoftDMToolsdll

OSoftFileManagedll

OSoftLoggingdll

OSoftLogWriterdll

OSoftMetaDatadll

OSoftSQEdll

OSoftSystemConfigdll

OutlookSoftconfig Configuration file to connect DB server

XceedCompressiondll XceedZip file

XceedCompressionFormatsdll XceedZip file

XceedFileSystemdll XceedZip file

XceedZipdll XceedZip file

Config folder

This folder has FileListxml 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 FileListxml 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

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4954

OSoftSetupexe

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

NOTE

If you installed the OSoftSSIS2008_Client or OSoftSSIS2012_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

Resources Folder

This folder contains the BPCServicesdll and BPCServiceUIdll files which contain resource text

Only English resources are included for the SSIS custom tasks

82 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

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008 and 2012 respectively

8 Installing SSIS Custom Tasks

82 Before You Modify the SSIS Packages

5054 CUSTOMER 2012-06-13

Name Remark

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012 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

lthellipgtOSoftSSIS2008_Clientbin or lthellipgtOSoftSSIS2012_Clientbin

On the Planning and Consolidation application server

ltdrivegtWebsrvrbin

2 Paste these files into the folder 100DTSTasks for SQL Server 2008 or into 110DTSTasks for

SQL Server 2012 For example if you install your SQL 2008 server or R2 on CProgram Files

Microsoft SQL Server paste all files into the CProgram Files (x86)Microsoft SQL Server

100DTSTasks folder

In Integration Services set the property Run64BitRunTime to True

83 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 or OSoftSSIS2012_Client on the

application server

8 Installing SSIS Custom Tasks

83 Setup of a COM+ Application on the Application Server

2012-06-13 CUSTOMER 5154

Typographic Conventions

Example Description

ltgt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example Enter your ltUser Namegt

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 httpwwwsapcom

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

5254 CUSTOMER 2012-06-13

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

  • SAP BusinessObjects Planning and Consolidation 100
    • Table of Contents
    • 1 Introduction
      • 11 SAP Notes for the Installation
      • 12 Naming Conventions
        • 2 Installing Planning and Consolidation Servers
          • 21 Basic Steps
          • 22 Prerequisites
          • 23 Before Starting the Planning and Consolidation Server Installation
          • 24 Logging on to Servers
          • 25 Service-level Accounts
          • 26 Standard and Advanced Settings
          • 27 Installing the Prerequisites
            • 271 Installing the Prerequisites ndash Basic Steps
            • 272 Installing the Operating System
            • 273 Installing the SQL Server
            • 274 Installing Analysis Services
            • 275 Installing the Anti-Cross Site Scripting Library
              • 28 Installing on a Single Server
              • 29 Installing the Server in a Multiserver Configuration
                • 3 After Installing Planning and Consolidation Servers
                  • 31 Post-Installation Steps
                  • 32 Connecting to Solution Manager Diagnostics
                  • 33 Configuring the Planning and Consolidation NET Application Servers
                  • 34 Post-Installation Optional Configuration Steps
                    • 341 Enabling the Management Console
                    • 342 Setting Up ODBC Logging in IIS for the Default Web Site
                    • 343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2
                    • 344 Removing Default Access to the Console
                    • 345 Management Console Access Control
                    • 346 Using Client Certificates
                        • 4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office
                          • 41 Installing the Administration Client
                          • 42 Installing the EPM Add-in
                          • 43 Using the Client Auto Update Program
                            • 5 Connection Issues
                              • 51 Checking for Open Ports
                              • 52 Proxy Server and Firewall Issues
                                • 6 Installing Planning and Consolidation with Two Active Directory Domains
                                • 7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
                                  • 71 Terminal Services Home Directories
                                  • 72 System Requirements
                                  • 73 Installing Planning and Consolidation
                                  • 74 Creating a Shortcut to the Launch Page
                                    • 8 Installing SSIS Custom Tasks
                                      • 81 Composition of SSIS Custom Task Installation
                                      • 82 Before You Modify the SSIS Packages
                                      • 83 Setup of a COM+ Application on the Application Server
                                          • Copyright and trademarks
Page 21: Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

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

Server Component What to Install

SQL Server Database Engine Services

SSAS Server Analysis Services

Application Server The following Shared Features Client Tools Connectivity Integration Services Client Tools SDK

Custom Settings for the SQL Server

As of version 100 Planning and Consolidation supports the following new features for SQL Server 2008

SQL Server 2008 R2 and SQL Server 2012

Process Dimension

It is now possible to process a dimension with multiple selections At processing time the process

dimension module makes changed or added information for each dimension and process for all selected

dimensions and cubes in parallel

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 2154

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

NOTE

Setting 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 tblFactWBltappgt table

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 Microsoftreg SQL Servertrade

20052008 which you can download from wwwmicrosoftcom (search on ldquoTable Partitioningrdquo to find

all relevant articles)

After Installing SQL Server 2008 SQL Server 2008 R2 and SQL Server 2012

From SQL Server Configuration Manager confirm that the SQL Server Browser service is

running The browser service is required for Planning and Consolidation

From SQL Server Configuration Manager do the following

1 Select Protocols for ltInstanceNamegt then double-click TCPIP from the right side of the window

2 When prompted for the TCPIP Properties select IP Addresses You see two IPs that indicate the

localhost and external network interface machine

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2254 CUSTOMER 2012-06-13

3 If you want to use IP1 which indicates Server IP set Enabled to Yes and specify the TCP Port as

desired

4 Delete 0 from TCP Dynamic Ports Set IPAll - TCP Ports as desired (for example 1533)

RECOMMENDATION

We do not recommend using dynamic ports

In an SQL server the default instance has a listener which listens on a fixed port (TCP

port 1433) However for the named instance the port on which the SQL server listens is

random and dynamically selected when the named instance of the SQL server starts This

recommendation prevents any conflict problems

From the SQL Server Configuration Manager specify the client protocol options for the application

server

1 Select Client Protocols from the SQL Native Client Configuration folder

2 From the right side of the window double-click TCPIP The TCPIP 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

NOTE

We 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

274 Installing Analysis Services

ProcedureAfter you install SQL Server and its required service packs and hotfixes you must install SQL Server

Analysis Services and its required service packs and hotfixes

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 2354

NOTE

If you have migrated your Analysis Services repository to the SQL Server back up the database

that contains the repository before installing this release

To install Analysis Services for SQL Server 2008 SQL Server 2008 R2 or SQL Server 2012 follow the steps

and guidelines in httptechnetmicrosoftcomen-uslibraryms143219aspx

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 httpwwwmicrosoftcomdownloads

detailsaspxFamilyID=3be0488d-e7aa-4078-a050- ae39912d2e43ampdisplaylang=en

275 Installing the Anti-Cross Site Scripting Library

Procedure

Before installing Planning and Consolidation servers you must download the Anti-Cross Site Scripting

Library (version 42 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 AntiXSSLibraryDLL from the Microsoft Web

site at httpwwwmicrosoftcomdownloadendetailsaspxid=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 AntiXssLibrarydll

28 Installing on a Single Server

When you install all Planning and Consolidation server components on a single server you should

consider the following issues

Make sure the server has a minimum of 800 MB of hard disk space

Additional environment installations require more free disk space which is a minimum of two

times the uncompressed size of the environment files

When you install Planning and Consolidation on a single-server the system adds the following server

components

SQL Server

SQL Server Analysis Services (SSAS)

Application Server

FileShare server

Procedure

To install Planning and Consolidation on a single server take the following steps

1 Exit all Windows programs

2 Installing Planning and Consolidation Servers

28 Installing on a Single Server

2454 CUSTOMER 2012-06-13

2 Log on to the server with a local server user ID or domain user ID For more information see Logging

on to servers [page 14]

3 Make sure all prerequisite software is installed on the server For more information see Installing

the Prerequisites [page 17]

4 Obtain SAP Planning and Consolidation from the Downloads SAP Installations amp Upgrades area of

SAP Service Marketplace then extract the files and run StartUpexe

5 From the Server Install screen select Install the Planning and Consolidation server

6 From the Welcome screen choose Next

7 From the License Agreement page choose I accept the terms of the license agreement then choose Next

8 From the Installation Method page accept the default Single machine enter a system ID for the system

landscape directory (SLD) and choose Next

NOTE

Entering a system ID of the SLD is only required if you have a SAP Solution Manager license

If you do not have a SAP Solution Manager license you can leave this field empty

9 From the Authentication Method page choose the desired authentication method and choose Next

10 If you have chosen SAP BusinessObjects User Management System in the previous screen on the CMS

Authentication page enter the information required to log on to CMS as an administrator

The following information is required

Field Description

System name CMS system name (server nameport number) for example CMSServer6400

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

11 After entering the CMS administrator authentication details choose Next

12 From the Service type accounts page enter service-level account user IDs and passwords See Service-

Level Accounts [page 15]

13 After defining the IDs and passwords choose Next

14 From the Server Information page (see Standard and Advanced Settings [page 16]) do one of the following

Review the standard settings and choose Next

To set advanced settings choose the Advanced Settings button Enter the desired information

and choose Next

2 Installing Planning and Consolidation Servers

28 Installing on a Single Server

2012-06-13 CUSTOMER 2554

15 Specify the location and name of AntiXssLibrarydll See Installing the Anti-Cross Site Scripting Library [page

24]

Choose Next

16 Select destination folders for Programs and Data The Data files include Webfolders and FileDB

(published reports) and should be installed on a separate drive in a production environment This

recommendation reduces the hard disk IO time and helps to speed up SQL commands

Accept the defaults or make your selections then choose Next

17 Select the default values for the Web client The values are used to determine the default language

and region for the Web client when you connect to it You can change the values in the Planning

and Consolidation Server Manager

18 The installation process takes a few moments When it is complete choose Exit

19 A prompt is displayed to restart your computer Select OK to restart

20 Perform the steps in After Installing Planning and Consolidation Servers [page 27]

29 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 24]) with the following

exceptions

On the Installation Method page do not accept the default instead choose Network Load Balancing

environment With this option there is an additional choice to Include sample environment (required on only

one of the application servers) This is because when you install the application server it connects to the

database server and creates the sample environment (EnvironmentShell) Installing the sample

environment is required on only one application server and you may choose which one

In the Virtual Name field enter the virtual IP address virtual name in the default properties

2 Installing Planning and Consolidation Servers

29 Installing the Server in a Multiserver Configuration

2654 CUSTOMER 2012-06-13

3 After Installing Planning and Consolidation Servers

31 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 28]

2 Configure the Planning and Consolidation NET and application server to ensure that it and its

related services function properly and reliably For more information see Configuring the Planning and

Consolidation NET Application Server [page 29]

3 Optional configuration steps [page 30]

1 To ensure proper functioning of the Management Console create an SQL user and modify

the System DSN and IIS to reflect those user credentials See Enabling Management Console [page

30]

2 Configure custom ODBC logging for the default Web site For details of how to configure

custom logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web

Site [page 31]

3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC

Data Source [page 32]

4 Modify the default access rights to the Management Console By default users in Active

Directory can access the Management Console with whatever rights they have been granted

on the server For information about removing default access and creating a group that can

access the console see Removing Default Access to the Console [page 32]

5 Add authorized users or groups to the group that can access the Management Console We

recommend that you only grant Management Console access to system administrators

Planning and Consolidation users should not have any access For more information see

Management Console Access Control [page 33]

6 Configure the use of client certificates for authentication See Using Client Certificates [page

34]

4 Take the following steps to set up security

If you are defining security and application structure continue with step 5

3 After Installing Planning and Consolidation Servers

31 Post-Installation Steps

2012-06-13 CUSTOMER 2754

If you want to designate someone other than the system administrator to manage security

and application structure log on to EnvironmentShell designate a user as a Primary

Administrator

This user must have Administration ‒ Environment and Security ‒ Define User task rights

so that he or she can add and delete environments and define user security

The Primary Administrator can continue with the next step (5)

5 From the machine on which you administer Planning and Consolidation install the

Administration client See Installing the Administration Client [page 37]

6 Start Planning and Consolidation Administration from the launch page

7 Select Connection Wizard and log on to EnvironmentShell

8 Create a new environment using EnvironmentShell as the source

9 Log on to the newly created environment and set up users teams and task profiles (You must

set up task profiles since there is no access to Planning and Consolidation tasks)

10 Set up your data access profiles and add users (or teams) to one or more data access profiles (You

must complete this step since there is no access to dimensions or members)

NOTE

To allow users to request and query large amounts of data you can edit the metabasexml file located

at CWindowssystem32inetsrv Set the following parameters to the stated values

ASPBUFFERINGLIMIT = 10485760

MAXREQUESTENTITYALLOWED = 10485760

32 Connecting to Solution Manager Diagnostics

NOTE

You only need to perform the steps in this section if you have a SAP Solution Manager licence

The diagnostics functions in SAP Solution Manager allow identification analysis and resolution of

problems This procedure provides the steps required to connect Planning and Consolidation to

Solution Manager Diagnostics

Procedure

1 Install the Diagnostics Agent according to SAP Note 1234387 on all servers where application servers

are installed

NOTE

Installation files for Diagnostics Agent are available on Service Marketplace by navigating to

Support Packages and Patches mdash Entry by Application Group SAP Technology Components SAP

SOLUTION MANAGER SAP SOLUTION MANAGER 70 EHP 1 Entry by Component Agents

for managed systems DIAGNOSTICS AGENT 711

3 After Installing Planning and Consolidation Servers

32 Connecting to Solution Manager Diagnostics

2854 CUSTOMER 2012-06-13

Download the installation file based on the 64-bit Windows Server system landscape

2 To access the DBA Cockpit you must create a user account with sufficient rights on all Windows

Servers where Microsoft SQL Server is installed Do the following

1 Start Computer Management then select Action New User

2 Create a new user

3 Right-click on the user then choose Properties On the Member Of tab select Add

4 Add the group SQLServerltReleasegtSQLAgentUser$ltDomain or hostnamegt$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 httpsservicesapcom~sapidb011000358700000074392009E and follow

the chapters that apply to Planning and Consolidation

33 Configuring the Planning and Consolidation NET Application Servers

Procedure

Modifying machineconfig Files

To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock

occurrences that would cause the application server to ldquosleeprdquo and not process anymore you can

modify the machineconfig file which resides in the WINDOWSMicrosoftNETFramework64

v4030319Config directory

1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to

specify whether to automatically configure settings to achieve optimal performance based on the

machine configuration You can set this attribute to True or False

For more information see httpmsdnmicrosoftcomen-uslibrary7w2sway1aspx

2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the

Planning and Consolidation application) or Machineconfig (for all applications including

Planning and Consolidation) to ensure the validationKey and decryptionKey keys have the same

value on all application servers This way when the authentication cookie is checked the

authentication ticket used on one server can still be valid on another server

For more information and sample Visual Basic code for generating random key values see http

msdnmicrosoftcomen-uslibraryms998288aspx

3 After Installing Planning and Consolidation Servers

33 Configuring the Planning and Consolidation NET Application Servers

2012-06-13 CUSTOMER 2954

paght000007_webfarmdeploymentconsiderations and httpmsdnmicrosoftcomen-us

libraryms998310aspx

34 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 30]

2 Configure custom ODBC logging for the default Web site For details of how to configure custom

logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page

31]

3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC Data

Source [page 32]

4 Modify the default access rights to the Management Console By default users in Active Directory

can access the Management Console with whatever rights they have been granted on the server

For information about removing default access and creating a group that can access the console

see Removing Default Access to the Console [page 32]

5 Add authorized users or groups to the group that can access the Management Console We

recommend that you only grant Management Console access to system administrators Planning

and Consolidation users should not have any access For more information see Management Console

Access Control [page 33]

6 Configure the use of client certificates for authentication See Using Client Certificates [page 34]

341 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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3054 CUSTOMER 2012-06-13

NOTE

Without these updates the Management Console does work but some functionality (specifically

User Activity and Service Status) does not work as expected

Should you need to uninstall Planning and Consolidation we recommend that you reset the

Active Log Format field in IIS to W3C Extended Log File Format

342 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 ApplicationHostconfig set the property customLogPluginClsid to the value FF16065B-

DE82-11CF-BC0A-00AA006111E0 Set the logFormat to Custom You can find this in the ltlogFilegt

node in ApplicationHostconfig as shown here

ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0

logFormat=Custom gt

Use the following AppCmds to configure IIS to use ODBC logging for the default Web site

appcmd site set sitenameDefault Web Site

logFilecustomLogPluginClsidFF16065B-DE82-11CF-BC0A-00AA006111E0

appcmd site set sitenameDefault Web Site logFilelogFormatCustom

Configuring ODBC Logging Parameters in ApplicationHostconfig

Configure ApplicationHostconfig to contain the database table information as set up in the Microsoft

Support article specified in the Prerequisites section Configure these settings in the ltodbcLogginggt

node under ltsystemwebServergt

EXAMPLE

ltlocation path=Default Web Sitegt

ltsystemwebServergt

ltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog

userName=Username password=mypassword gt

ltsystemwebServergt

ltlocationgt

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3154

Use the following AppCmds to configure these attributes for the default Web site

appcmd set config Default Web Site sectionodbcLogging

dataSourceBPC_ManagementDSN commitappHost

appcmd set config Default Web Site sectionodbcLogging tableNameBPCLog

commitappHost

appcmd set config Default Web Site sectionodbcLogging userNameUsername

commitappHost

appcmd set config Default Web Site sectionodbcLogging passwordmypassword

commitappHost

NOTE

You cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must

use the SQL Server ODBC driver For more information see the Microsoft Knowledge Base article

931202 The requirements for using the ODBC logging feature in IIS

343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2

ProcedureThis procedure describes how to set up an ODBC data source for the Management Console in Windows

Server 2008 or Windows Server 2008 R2

Proceed as follows

1 Open ODBC Connection Manager

2 On the System DSN tab page add a new DSN

Choose Add

Choose SQL Server as the driver

Choose Finish

3 In the Name and Description fields enter BPC_ManagementDSN

4 In the Server field enter the name of your SQL Server Choose Next

5 Leave the default settings and choose Next

6 Choose the Change the default database to field and enter AppServer Choose Next

7 Leave default settings and choose Next

8 Choose OK

344 Removing Default Access to the Console

NOTE

If you have chosen SAP BusinessObjects User Management System in the installation screen you

do not need to remove or configure access because the Management Console service always runs

with the System Admin ID account which is a member of the Administrators group

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3254 CUSTOMER 2012-06-13

ProcedureTo remove default access to the Management Console and create a group that does have access to the

console use the procedure described below

NOTE

Create your Management Console administrative group either on the server that hosts the

Management Console or in the Active Directory

1 In the context menu of the servers My Computer icon choose Manage

2 In the Computer Management dialog box choose Local Users and Groups Groups

NOTE

Alternatively you can perform analogous steps in Active Directory

3 In the 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

NOTE

This step is a necessary precursor to the completion of this procedure

10 In the Security dialog box click Copy to ensure that the System group retains its privileges

11 Remove access to the Management Console from all groups that should not have it

12 Choose Authentication in the center pane then disable Windows authentication

ResultUsers who have not been granted access to the Management Console can still open the Management

Console Web page but it contains no data or menu options This does not affect the access that a user

would otherwise have to Planning and Consolidation

345 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 32] Their rights in

Active Directory determine what they can access in the Console

By default any member of the Administrators Active Directory group on the application server or

domain has full access to all of the features of the Console except the Planning and Consolidation

logging area Access to Planning and Consolidation logging is controlled within the Planning and

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3354

Consolidation Administration Client task security The user must be granted View system logs task

privileges For more information see the SAP Library Planning and Consolidation Administrators Guide in

httpservicesapcominstguidesepm-bpc 100 version for the Microsoft platform

Your IT policy determines whether you grant access by group or user You may wish to create several

levels of Console users (read-only users for example) in your environment

To grant or limit access to users or groups you can add or remove the following privileges from the

areas described in this table

Privilege Rights Management Area

Task Manager and Kill Process Administrators group on application server or domain

Performance Monitor Counters Administrators group on application server or domain Power Users group on application server or domain Performance Monitor Users group on application server

Microsoft Analysis Services performance monitoring

Administrators group on application server or domain

Microsoft SQL Server Monitoring (performance counters and statistics)

Administrators group on application server or domain

346 Using Client Certificates

To enable the use of client certificates in Planning and Consolidation you must follow several manual

steps

NOTE

Planning 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 httptechnetmicrosoftcomen-us

librarycc753810aspx

For more information about configuring the client certificate mapping authentication see http

technetmicrosoftcomen-uslibrarycc732996(WS10)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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3454 CUSTOMER 2012-06-13

This option allows you to use a client certificate or username and password (Basic

authentication) to connect to Planning and Consolidation

2 Enable anonymous authentication

1 In the IIS Manager expand the node of the Planning and Consolidation web site

2 Select the ManagementConsole directory (ltWebsitegtManagementConsole) to open the

ManagementConsole home page

3 Double-click Authentication and enable Anonymous Authentication

4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way

as in step 3

5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the same

way as in step 3

3 Change the web configuration settings

1 Open the ltPC_MSgtWebsrvrWebBPCwebconfig file

2 Find the text clientCredentialType=Windows

3 Change value of clientCredentialType to None (clientCredentialType=None)

4 Open the PC_MSWebsrvrWebPOASBCwebconfig file Repeat steps 2 and 3

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3554

This page is left blank for documents that are printed on both sides

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

The installation of the Planning and Consolidation Administration Client allows administrators to

build and maintain Planning and Consolidation environments and models and administer security

All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions

add-in for Microsoft Office for more information see the SAP BusinessObjects EPM solutions add-in for

Microsoft Office help

NOTE

You must update the Administration Client to the same version as the server

If your PC is on a different domain than your server you must set the Internet Explorer

Security Zone value of the Planning and Consolidation client to prompt for user name and

password Otherwise the Planning and Consolidation Start Page does not display

41 Installing the Administration Client

Prerequisites

NOTE

For a definitive list of system requirements see the Product Availability Matrix on SAP Service

Marketplace at httpservicesapcompam Search on Planning and Consolidation

The following list describes the minimum software requirements

Microsoft Internet Explorer 70 or 80

Microsoft Office 2007 or 2010

NET Framework 20 or higher (install any required NET Framework Hotfixes by referring to

httpsupportmicrosoftcomkb)

Pentium IV (1 GHz CPU)

512 MB RAM

100 MB of free hard disk space in the My Documents folder

20 MB of free hard disk space for the installed Administration files

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

41 Installing the Administration Client

2012-06-13 CUSTOMER 3754

NOTE

We recommend that you install all of the latest Microsoft Windows hotfixes prior to installing

the Administration client For information about which hotfixes to install see http

updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us

ProcedureThe following procedure describes how to install the Administration Client on to an administratorrsquos

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 AddRemove Programs in the Windows Control Panel

3 Point your browser to the Planning and Consolidation Web at httpltPC_serverportgtsap

bpcweb

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

42 Installing the EPM Add-in

The Planning and Consolidation installation media does not contain the EPM addin setup program

You must download the most recent version of the full setup (EPM Add-inexe) from the Service

Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPC

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

43 Using the Client Auto Update Program

If Planning and Consolidation version 100 or later is installed you can use the Client Auto Update

program to set up the server so that it determines if an upgrade for a connecting Administration client

is necessary

The following describes the use of the auto update program for the Administration Client and the EPM

add-in

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

42 Installing the EPM Add-in

3854 CUSTOMER 2012-06-13

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 37]

To use the Client Auto Update program for the Administration Client proceed as follows

1 From the Server Manager select Options Client Options

2 Select Admin Update

3 If users without administrator rights on their machines use the auto update enter an administrator

ID and password in the Admin ID and Admin password fields respectively The Admin ID should be a

member of the local administrators group on all the computers running the auto update This

setting is not needed if all users have administrator rights on their machines

4 Select Update

For the EPM Add-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 Optionshellip 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 Market Place (SMP) at httpservicesapcom

All support packages and patches are available from the SMP as a zip file

EPMEXCLCLNTltSPLgtzip is for a support package

EPMEXCLCLNTltSPLgtPltPLgtzip 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 ltSP versiongtmsp

EPM Addin Support Package ltSP versiongtxml

For a patch these files are

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

2012-06-13 CUSTOMER 3954

EPM Addin Patch ltpatch numbergtmsp

EPM Addin Patch ltpatch numbergtxml

2 Unzip the zip file and extract the two files to the application server folder (WebsrvrWebBPC

Installation)

3 From the Server Manager select Options Client Options

The system lists the available packages Select the package that you want to use for the autoupdate

You can set a different update policy for each package listed

EXAMPLE

The following table illustrates some possible situations assuming that you have installed the

first full version (V1)

Available maintenance packages

V2-user updateV3-force updateV4-force updateV5-user update

V5-user update V5-user updateV6-auto updateV7-force update

Minimum Required Version

V4 V4 V7

Notification A prompt tells the user to install maintenance package V4 using the Forced Update behavior

If User Update is enabled the prompt informs the user that maintenance package V5 is available

A prompt tells the user to install maintenance package V7 using the Forced Update behavior

New Version V4 V4 or V5 V7

If you change the update policy for any package click Update to complete the change

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

4054 CUSTOMER 2012-06-13

5 Connection Issues

You may experience connection problems with ports the proxy server or programs and settings that

interact with these components If you have any issues related to connection review the following

recommendations and troubleshooting tips

51 Checking for Open Ports

You must ensure that all required ports are open for inboundoutbound 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 431181836 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

NOTE

You can use the following site to scan for the normal ports It allows you to manually enter a port

number to test

httpwwwmyserverorgportsniffasp

You can change the name of a port

52 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 Explorer Tools Internet Options Connections LAN Settings ) or at the server level

Enabling content filtering on the proxy server or firewall may cause connection problems

If external users are having trouble connecting to the server make sure the proxy server connects

using a fully qualified domain name Fully qualified domain names typically resolve both internal

and external IP addresses

Each secure Planning and Consolidation server name must be identified on the proxy server

Proxy servers may or may not require authentication which could conflict with Planning and

Consolidation authentication Do not use authentication on the proxy server The system

5 Connection Issues

51 Checking for Open Ports

2012-06-13 CUSTOMER 4154

synchronizes the user name and password on the remote server with the local user name and

password

NOTE

For more information about setting up an ISA proxy server contact SAP Support to request a

copy of Setting up ISA Proxy Server White Paper

Internet Explorer Settings 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

5 Connection Issues

52 Proxy Server and Firewall Issues

4254 CUSTOMER 2012-06-13

6 Installing Planning and Consolidation with Two Active Directory Domains

To set up a Planning and Consolidation 10 application server in a hosted environment and use your

own domain users follow this procedure In general you install Planning and Consolidation on the

host domain use the host domain account and assign it to the Planning and Consolidation users

SysAdmin Admin and Users Then you accept one way trust (the host domain trusts your domain)

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

6 Installing Planning and Consolidation with Two Active Directory Domains

2012-06-13 CUSTOMER 4354

This page is left blank for documents that are printed on both sides

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

This section describes best practices and instructions for installing Planning and Consolidation in a

Terminal Services or Citrix Server deployment

71 Terminal Services Home Directories

We recommend using Terminal Server home directories rather than using the userrsquos 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

72 System Requirements

The Citrix server should be one of the following systems

XenApp 5 Enterprise

XenApp 5 Platinum

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 37])

73 Installing Planning and Consolidation

Prerequisites

The server installation files have been downloaded from SAP Service Marketplace and installed

Procedure

The following steps outline how to install the Planning and Consolidation clients in a Terminal Services

(TS) or Citrix Server deployment

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

71 Terminal Services Home Directories

2012-06-13 CUSTOMER 4554

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 userinstall

4 Open a browser and connect to the URL httpltPC_serverportgtsapbpcweb

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 userexecute 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 Iexploreexe http(s)

ltServerNamegt-NetBIOS or FQDNsapbpcweb

To publish Planning and Consolidation Administration CProgram FilesPC_MS

BPCAdminMainexe

74 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 userrsquos desktop) must be moved to the All UsersDesktop folder

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

74 Creating a Shortcut to the Launch Page

4654 CUSTOMER 2012-06-13

8 Installing SSIS Custom Tasks

This section provides background information and instructions for installing SQL Server Integration

Services (SSIS) for SQL Server 2008 and SQL Server 2012

The Planning and Consolidation Data Manager component supports and uses SSIS Since SQL Server

2008 and SQL Server 2012 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

81 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 Filelistxml 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

OSoftSetupexe ‒ 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 or OSoftSSIS2012_Client on the client machine followed by the SQL Server

version If you want to use SQL 2008 Tasks under the SQL 2012 environment you must install

OSoftSSIS2008_Client on the application server For detailed information see SAP Note 1707410

You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package by extracting

OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPC

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 or

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4754

OSoftSSIS2012_Client for creating a COM+ application For more information see Before You Modify

the SSIS Packages [page 50] and Setup of a COM+ Application on the Application Server [page 51]

Bin folder

This folder contains the following components

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCCachedll Planning and Consolidation Cache file

BPCDataFlowPackagedll or BPCDataFlowPackage2012dll

BPCDMdll

BPCDMTaskMaindll COM+ component

BPCFilePreviewdll

BPCGacUtil_20exe System File

BPCGacUtil_40exe System File

BPCImpersonatordll Planning and Consolidation Impersonator

BPCLogicdll

BPCScriptdll

BPCServerZipdll

BPCServiceResdll

BPCTransferMembersdll

BPCWriteBackdll

InteropDTSdll

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

4854 CUSTOMER 2012-06-13

Name Remark

OSoftAdminServerdll

OSoftAuditdll

OSoftComLibServerdll

OSoftCommonResQrydll

OSoftConfigurationdll

OSoftCustomXMLSvrdll

OSoftDatabaseADMINdll

OSoftDatabaseSYSADMINdll

OSoftDatabaseSYSADMINDMdll

OSoftDatabaseUSERdll

OSoftDMDTSXExecutedll or OSoftDMDTSXExecute2012dll

OSoftDMTaskFormdll

OSoftDMTaskMaindll

OSoftDMToolsdll

OSoftFileManagedll

OSoftLoggingdll

OSoftLogWriterdll

OSoftMetaDatadll

OSoftSQEdll

OSoftSystemConfigdll

OutlookSoftconfig Configuration file to connect DB server

XceedCompressiondll XceedZip file

XceedCompressionFormatsdll XceedZip file

XceedFileSystemdll XceedZip file

XceedZipdll XceedZip file

Config folder

This folder has FileListxml 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 FileListxml 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

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4954

OSoftSetupexe

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

NOTE

If you installed the OSoftSSIS2008_Client or OSoftSSIS2012_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

Resources Folder

This folder contains the BPCServicesdll and BPCServiceUIdll files which contain resource text

Only English resources are included for the SSIS custom tasks

82 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

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008 and 2012 respectively

8 Installing SSIS Custom Tasks

82 Before You Modify the SSIS Packages

5054 CUSTOMER 2012-06-13

Name Remark

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012 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

lthellipgtOSoftSSIS2008_Clientbin or lthellipgtOSoftSSIS2012_Clientbin

On the Planning and Consolidation application server

ltdrivegtWebsrvrbin

2 Paste these files into the folder 100DTSTasks for SQL Server 2008 or into 110DTSTasks for

SQL Server 2012 For example if you install your SQL 2008 server or R2 on CProgram Files

Microsoft SQL Server paste all files into the CProgram Files (x86)Microsoft SQL Server

100DTSTasks folder

In Integration Services set the property Run64BitRunTime to True

83 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 or OSoftSSIS2012_Client on the

application server

8 Installing SSIS Custom Tasks

83 Setup of a COM+ Application on the Application Server

2012-06-13 CUSTOMER 5154

Typographic Conventions

Example Description

ltgt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example Enter your ltUser Namegt

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 httpwwwsapcom

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

5254 CUSTOMER 2012-06-13

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

  • SAP BusinessObjects Planning and Consolidation 100
    • Table of Contents
    • 1 Introduction
      • 11 SAP Notes for the Installation
      • 12 Naming Conventions
        • 2 Installing Planning and Consolidation Servers
          • 21 Basic Steps
          • 22 Prerequisites
          • 23 Before Starting the Planning and Consolidation Server Installation
          • 24 Logging on to Servers
          • 25 Service-level Accounts
          • 26 Standard and Advanced Settings
          • 27 Installing the Prerequisites
            • 271 Installing the Prerequisites ndash Basic Steps
            • 272 Installing the Operating System
            • 273 Installing the SQL Server
            • 274 Installing Analysis Services
            • 275 Installing the Anti-Cross Site Scripting Library
              • 28 Installing on a Single Server
              • 29 Installing the Server in a Multiserver Configuration
                • 3 After Installing Planning and Consolidation Servers
                  • 31 Post-Installation Steps
                  • 32 Connecting to Solution Manager Diagnostics
                  • 33 Configuring the Planning and Consolidation NET Application Servers
                  • 34 Post-Installation Optional Configuration Steps
                    • 341 Enabling the Management Console
                    • 342 Setting Up ODBC Logging in IIS for the Default Web Site
                    • 343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2
                    • 344 Removing Default Access to the Console
                    • 345 Management Console Access Control
                    • 346 Using Client Certificates
                        • 4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office
                          • 41 Installing the Administration Client
                          • 42 Installing the EPM Add-in
                          • 43 Using the Client Auto Update Program
                            • 5 Connection Issues
                              • 51 Checking for Open Ports
                              • 52 Proxy Server and Firewall Issues
                                • 6 Installing Planning and Consolidation with Two Active Directory Domains
                                • 7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
                                  • 71 Terminal Services Home Directories
                                  • 72 System Requirements
                                  • 73 Installing Planning and Consolidation
                                  • 74 Creating a Shortcut to the Launch Page
                                    • 8 Installing SSIS Custom Tasks
                                      • 81 Composition of SSIS Custom Task Installation
                                      • 82 Before You Modify the SSIS Packages
                                      • 83 Setup of a COM+ Application on the Application Server
                                          • Copyright and trademarks
Page 22: Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

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

NOTE

Setting 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 tblFactWBltappgt table

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 Microsoftreg SQL Servertrade

20052008 which you can download from wwwmicrosoftcom (search on ldquoTable Partitioningrdquo to find

all relevant articles)

After Installing SQL Server 2008 SQL Server 2008 R2 and SQL Server 2012

From SQL Server Configuration Manager confirm that the SQL Server Browser service is

running The browser service is required for Planning and Consolidation

From SQL Server Configuration Manager do the following

1 Select Protocols for ltInstanceNamegt then double-click TCPIP from the right side of the window

2 When prompted for the TCPIP Properties select IP Addresses You see two IPs that indicate the

localhost and external network interface machine

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2254 CUSTOMER 2012-06-13

3 If you want to use IP1 which indicates Server IP set Enabled to Yes and specify the TCP Port as

desired

4 Delete 0 from TCP Dynamic Ports Set IPAll - TCP Ports as desired (for example 1533)

RECOMMENDATION

We do not recommend using dynamic ports

In an SQL server the default instance has a listener which listens on a fixed port (TCP

port 1433) However for the named instance the port on which the SQL server listens is

random and dynamically selected when the named instance of the SQL server starts This

recommendation prevents any conflict problems

From the SQL Server Configuration Manager specify the client protocol options for the application

server

1 Select Client Protocols from the SQL Native Client Configuration folder

2 From the right side of the window double-click TCPIP The TCPIP 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

NOTE

We 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

274 Installing Analysis Services

ProcedureAfter you install SQL Server and its required service packs and hotfixes you must install SQL Server

Analysis Services and its required service packs and hotfixes

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 2354

NOTE

If you have migrated your Analysis Services repository to the SQL Server back up the database

that contains the repository before installing this release

To install Analysis Services for SQL Server 2008 SQL Server 2008 R2 or SQL Server 2012 follow the steps

and guidelines in httptechnetmicrosoftcomen-uslibraryms143219aspx

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 httpwwwmicrosoftcomdownloads

detailsaspxFamilyID=3be0488d-e7aa-4078-a050- ae39912d2e43ampdisplaylang=en

275 Installing the Anti-Cross Site Scripting Library

Procedure

Before installing Planning and Consolidation servers you must download the Anti-Cross Site Scripting

Library (version 42 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 AntiXSSLibraryDLL from the Microsoft Web

site at httpwwwmicrosoftcomdownloadendetailsaspxid=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 AntiXssLibrarydll

28 Installing on a Single Server

When you install all Planning and Consolidation server components on a single server you should

consider the following issues

Make sure the server has a minimum of 800 MB of hard disk space

Additional environment installations require more free disk space which is a minimum of two

times the uncompressed size of the environment files

When you install Planning and Consolidation on a single-server the system adds the following server

components

SQL Server

SQL Server Analysis Services (SSAS)

Application Server

FileShare server

Procedure

To install Planning and Consolidation on a single server take the following steps

1 Exit all Windows programs

2 Installing Planning and Consolidation Servers

28 Installing on a Single Server

2454 CUSTOMER 2012-06-13

2 Log on to the server with a local server user ID or domain user ID For more information see Logging

on to servers [page 14]

3 Make sure all prerequisite software is installed on the server For more information see Installing

the Prerequisites [page 17]

4 Obtain SAP Planning and Consolidation from the Downloads SAP Installations amp Upgrades area of

SAP Service Marketplace then extract the files and run StartUpexe

5 From the Server Install screen select Install the Planning and Consolidation server

6 From the Welcome screen choose Next

7 From the License Agreement page choose I accept the terms of the license agreement then choose Next

8 From the Installation Method page accept the default Single machine enter a system ID for the system

landscape directory (SLD) and choose Next

NOTE

Entering a system ID of the SLD is only required if you have a SAP Solution Manager license

If you do not have a SAP Solution Manager license you can leave this field empty

9 From the Authentication Method page choose the desired authentication method and choose Next

10 If you have chosen SAP BusinessObjects User Management System in the previous screen on the CMS

Authentication page enter the information required to log on to CMS as an administrator

The following information is required

Field Description

System name CMS system name (server nameport number) for example CMSServer6400

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

11 After entering the CMS administrator authentication details choose Next

12 From the Service type accounts page enter service-level account user IDs and passwords See Service-

Level Accounts [page 15]

13 After defining the IDs and passwords choose Next

14 From the Server Information page (see Standard and Advanced Settings [page 16]) do one of the following

Review the standard settings and choose Next

To set advanced settings choose the Advanced Settings button Enter the desired information

and choose Next

2 Installing Planning and Consolidation Servers

28 Installing on a Single Server

2012-06-13 CUSTOMER 2554

15 Specify the location and name of AntiXssLibrarydll See Installing the Anti-Cross Site Scripting Library [page

24]

Choose Next

16 Select destination folders for Programs and Data The Data files include Webfolders and FileDB

(published reports) and should be installed on a separate drive in a production environment This

recommendation reduces the hard disk IO time and helps to speed up SQL commands

Accept the defaults or make your selections then choose Next

17 Select the default values for the Web client The values are used to determine the default language

and region for the Web client when you connect to it You can change the values in the Planning

and Consolidation Server Manager

18 The installation process takes a few moments When it is complete choose Exit

19 A prompt is displayed to restart your computer Select OK to restart

20 Perform the steps in After Installing Planning and Consolidation Servers [page 27]

29 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 24]) with the following

exceptions

On the Installation Method page do not accept the default instead choose Network Load Balancing

environment With this option there is an additional choice to Include sample environment (required on only

one of the application servers) This is because when you install the application server it connects to the

database server and creates the sample environment (EnvironmentShell) Installing the sample

environment is required on only one application server and you may choose which one

In the Virtual Name field enter the virtual IP address virtual name in the default properties

2 Installing Planning and Consolidation Servers

29 Installing the Server in a Multiserver Configuration

2654 CUSTOMER 2012-06-13

3 After Installing Planning and Consolidation Servers

31 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 28]

2 Configure the Planning and Consolidation NET and application server to ensure that it and its

related services function properly and reliably For more information see Configuring the Planning and

Consolidation NET Application Server [page 29]

3 Optional configuration steps [page 30]

1 To ensure proper functioning of the Management Console create an SQL user and modify

the System DSN and IIS to reflect those user credentials See Enabling Management Console [page

30]

2 Configure custom ODBC logging for the default Web site For details of how to configure

custom logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web

Site [page 31]

3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC

Data Source [page 32]

4 Modify the default access rights to the Management Console By default users in Active

Directory can access the Management Console with whatever rights they have been granted

on the server For information about removing default access and creating a group that can

access the console see Removing Default Access to the Console [page 32]

5 Add authorized users or groups to the group that can access the Management Console We

recommend that you only grant Management Console access to system administrators

Planning and Consolidation users should not have any access For more information see

Management Console Access Control [page 33]

6 Configure the use of client certificates for authentication See Using Client Certificates [page

34]

4 Take the following steps to set up security

If you are defining security and application structure continue with step 5

3 After Installing Planning and Consolidation Servers

31 Post-Installation Steps

2012-06-13 CUSTOMER 2754

If you want to designate someone other than the system administrator to manage security

and application structure log on to EnvironmentShell designate a user as a Primary

Administrator

This user must have Administration ‒ Environment and Security ‒ Define User task rights

so that he or she can add and delete environments and define user security

The Primary Administrator can continue with the next step (5)

5 From the machine on which you administer Planning and Consolidation install the

Administration client See Installing the Administration Client [page 37]

6 Start Planning and Consolidation Administration from the launch page

7 Select Connection Wizard and log on to EnvironmentShell

8 Create a new environment using EnvironmentShell as the source

9 Log on to the newly created environment and set up users teams and task profiles (You must

set up task profiles since there is no access to Planning and Consolidation tasks)

10 Set up your data access profiles and add users (or teams) to one or more data access profiles (You

must complete this step since there is no access to dimensions or members)

NOTE

To allow users to request and query large amounts of data you can edit the metabasexml file located

at CWindowssystem32inetsrv Set the following parameters to the stated values

ASPBUFFERINGLIMIT = 10485760

MAXREQUESTENTITYALLOWED = 10485760

32 Connecting to Solution Manager Diagnostics

NOTE

You only need to perform the steps in this section if you have a SAP Solution Manager licence

The diagnostics functions in SAP Solution Manager allow identification analysis and resolution of

problems This procedure provides the steps required to connect Planning and Consolidation to

Solution Manager Diagnostics

Procedure

1 Install the Diagnostics Agent according to SAP Note 1234387 on all servers where application servers

are installed

NOTE

Installation files for Diagnostics Agent are available on Service Marketplace by navigating to

Support Packages and Patches mdash Entry by Application Group SAP Technology Components SAP

SOLUTION MANAGER SAP SOLUTION MANAGER 70 EHP 1 Entry by Component Agents

for managed systems DIAGNOSTICS AGENT 711

3 After Installing Planning and Consolidation Servers

32 Connecting to Solution Manager Diagnostics

2854 CUSTOMER 2012-06-13

Download the installation file based on the 64-bit Windows Server system landscape

2 To access the DBA Cockpit you must create a user account with sufficient rights on all Windows

Servers where Microsoft SQL Server is installed Do the following

1 Start Computer Management then select Action New User

2 Create a new user

3 Right-click on the user then choose Properties On the Member Of tab select Add

4 Add the group SQLServerltReleasegtSQLAgentUser$ltDomain or hostnamegt$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 httpsservicesapcom~sapidb011000358700000074392009E and follow

the chapters that apply to Planning and Consolidation

33 Configuring the Planning and Consolidation NET Application Servers

Procedure

Modifying machineconfig Files

To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock

occurrences that would cause the application server to ldquosleeprdquo and not process anymore you can

modify the machineconfig file which resides in the WINDOWSMicrosoftNETFramework64

v4030319Config directory

1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to

specify whether to automatically configure settings to achieve optimal performance based on the

machine configuration You can set this attribute to True or False

For more information see httpmsdnmicrosoftcomen-uslibrary7w2sway1aspx

2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the

Planning and Consolidation application) or Machineconfig (for all applications including

Planning and Consolidation) to ensure the validationKey and decryptionKey keys have the same

value on all application servers This way when the authentication cookie is checked the

authentication ticket used on one server can still be valid on another server

For more information and sample Visual Basic code for generating random key values see http

msdnmicrosoftcomen-uslibraryms998288aspx

3 After Installing Planning and Consolidation Servers

33 Configuring the Planning and Consolidation NET Application Servers

2012-06-13 CUSTOMER 2954

paght000007_webfarmdeploymentconsiderations and httpmsdnmicrosoftcomen-us

libraryms998310aspx

34 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 30]

2 Configure custom ODBC logging for the default Web site For details of how to configure custom

logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page

31]

3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC Data

Source [page 32]

4 Modify the default access rights to the Management Console By default users in Active Directory

can access the Management Console with whatever rights they have been granted on the server

For information about removing default access and creating a group that can access the console

see Removing Default Access to the Console [page 32]

5 Add authorized users or groups to the group that can access the Management Console We

recommend that you only grant Management Console access to system administrators Planning

and Consolidation users should not have any access For more information see Management Console

Access Control [page 33]

6 Configure the use of client certificates for authentication See Using Client Certificates [page 34]

341 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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3054 CUSTOMER 2012-06-13

NOTE

Without these updates the Management Console does work but some functionality (specifically

User Activity and Service Status) does not work as expected

Should you need to uninstall Planning and Consolidation we recommend that you reset the

Active Log Format field in IIS to W3C Extended Log File Format

342 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 ApplicationHostconfig set the property customLogPluginClsid to the value FF16065B-

DE82-11CF-BC0A-00AA006111E0 Set the logFormat to Custom You can find this in the ltlogFilegt

node in ApplicationHostconfig as shown here

ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0

logFormat=Custom gt

Use the following AppCmds to configure IIS to use ODBC logging for the default Web site

appcmd site set sitenameDefault Web Site

logFilecustomLogPluginClsidFF16065B-DE82-11CF-BC0A-00AA006111E0

appcmd site set sitenameDefault Web Site logFilelogFormatCustom

Configuring ODBC Logging Parameters in ApplicationHostconfig

Configure ApplicationHostconfig to contain the database table information as set up in the Microsoft

Support article specified in the Prerequisites section Configure these settings in the ltodbcLogginggt

node under ltsystemwebServergt

EXAMPLE

ltlocation path=Default Web Sitegt

ltsystemwebServergt

ltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog

userName=Username password=mypassword gt

ltsystemwebServergt

ltlocationgt

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3154

Use the following AppCmds to configure these attributes for the default Web site

appcmd set config Default Web Site sectionodbcLogging

dataSourceBPC_ManagementDSN commitappHost

appcmd set config Default Web Site sectionodbcLogging tableNameBPCLog

commitappHost

appcmd set config Default Web Site sectionodbcLogging userNameUsername

commitappHost

appcmd set config Default Web Site sectionodbcLogging passwordmypassword

commitappHost

NOTE

You cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must

use the SQL Server ODBC driver For more information see the Microsoft Knowledge Base article

931202 The requirements for using the ODBC logging feature in IIS

343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2

ProcedureThis procedure describes how to set up an ODBC data source for the Management Console in Windows

Server 2008 or Windows Server 2008 R2

Proceed as follows

1 Open ODBC Connection Manager

2 On the System DSN tab page add a new DSN

Choose Add

Choose SQL Server as the driver

Choose Finish

3 In the Name and Description fields enter BPC_ManagementDSN

4 In the Server field enter the name of your SQL Server Choose Next

5 Leave the default settings and choose Next

6 Choose the Change the default database to field and enter AppServer Choose Next

7 Leave default settings and choose Next

8 Choose OK

344 Removing Default Access to the Console

NOTE

If you have chosen SAP BusinessObjects User Management System in the installation screen you

do not need to remove or configure access because the Management Console service always runs

with the System Admin ID account which is a member of the Administrators group

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3254 CUSTOMER 2012-06-13

ProcedureTo remove default access to the Management Console and create a group that does have access to the

console use the procedure described below

NOTE

Create your Management Console administrative group either on the server that hosts the

Management Console or in the Active Directory

1 In the context menu of the servers My Computer icon choose Manage

2 In the Computer Management dialog box choose Local Users and Groups Groups

NOTE

Alternatively you can perform analogous steps in Active Directory

3 In the 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

NOTE

This step is a necessary precursor to the completion of this procedure

10 In the Security dialog box click Copy to ensure that the System group retains its privileges

11 Remove access to the Management Console from all groups that should not have it

12 Choose Authentication in the center pane then disable Windows authentication

ResultUsers who have not been granted access to the Management Console can still open the Management

Console Web page but it contains no data or menu options This does not affect the access that a user

would otherwise have to Planning and Consolidation

345 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 32] Their rights in

Active Directory determine what they can access in the Console

By default any member of the Administrators Active Directory group on the application server or

domain has full access to all of the features of the Console except the Planning and Consolidation

logging area Access to Planning and Consolidation logging is controlled within the Planning and

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3354

Consolidation Administration Client task security The user must be granted View system logs task

privileges For more information see the SAP Library Planning and Consolidation Administrators Guide in

httpservicesapcominstguidesepm-bpc 100 version for the Microsoft platform

Your IT policy determines whether you grant access by group or user You may wish to create several

levels of Console users (read-only users for example) in your environment

To grant or limit access to users or groups you can add or remove the following privileges from the

areas described in this table

Privilege Rights Management Area

Task Manager and Kill Process Administrators group on application server or domain

Performance Monitor Counters Administrators group on application server or domain Power Users group on application server or domain Performance Monitor Users group on application server

Microsoft Analysis Services performance monitoring

Administrators group on application server or domain

Microsoft SQL Server Monitoring (performance counters and statistics)

Administrators group on application server or domain

346 Using Client Certificates

To enable the use of client certificates in Planning and Consolidation you must follow several manual

steps

NOTE

Planning 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 httptechnetmicrosoftcomen-us

librarycc753810aspx

For more information about configuring the client certificate mapping authentication see http

technetmicrosoftcomen-uslibrarycc732996(WS10)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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3454 CUSTOMER 2012-06-13

This option allows you to use a client certificate or username and password (Basic

authentication) to connect to Planning and Consolidation

2 Enable anonymous authentication

1 In the IIS Manager expand the node of the Planning and Consolidation web site

2 Select the ManagementConsole directory (ltWebsitegtManagementConsole) to open the

ManagementConsole home page

3 Double-click Authentication and enable Anonymous Authentication

4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way

as in step 3

5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the same

way as in step 3

3 Change the web configuration settings

1 Open the ltPC_MSgtWebsrvrWebBPCwebconfig file

2 Find the text clientCredentialType=Windows

3 Change value of clientCredentialType to None (clientCredentialType=None)

4 Open the PC_MSWebsrvrWebPOASBCwebconfig file Repeat steps 2 and 3

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3554

This page is left blank for documents that are printed on both sides

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

The installation of the Planning and Consolidation Administration Client allows administrators to

build and maintain Planning and Consolidation environments and models and administer security

All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions

add-in for Microsoft Office for more information see the SAP BusinessObjects EPM solutions add-in for

Microsoft Office help

NOTE

You must update the Administration Client to the same version as the server

If your PC is on a different domain than your server you must set the Internet Explorer

Security Zone value of the Planning and Consolidation client to prompt for user name and

password Otherwise the Planning and Consolidation Start Page does not display

41 Installing the Administration Client

Prerequisites

NOTE

For a definitive list of system requirements see the Product Availability Matrix on SAP Service

Marketplace at httpservicesapcompam Search on Planning and Consolidation

The following list describes the minimum software requirements

Microsoft Internet Explorer 70 or 80

Microsoft Office 2007 or 2010

NET Framework 20 or higher (install any required NET Framework Hotfixes by referring to

httpsupportmicrosoftcomkb)

Pentium IV (1 GHz CPU)

512 MB RAM

100 MB of free hard disk space in the My Documents folder

20 MB of free hard disk space for the installed Administration files

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

41 Installing the Administration Client

2012-06-13 CUSTOMER 3754

NOTE

We recommend that you install all of the latest Microsoft Windows hotfixes prior to installing

the Administration client For information about which hotfixes to install see http

updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us

ProcedureThe following procedure describes how to install the Administration Client on to an administratorrsquos

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 AddRemove Programs in the Windows Control Panel

3 Point your browser to the Planning and Consolidation Web at httpltPC_serverportgtsap

bpcweb

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

42 Installing the EPM Add-in

The Planning and Consolidation installation media does not contain the EPM addin setup program

You must download the most recent version of the full setup (EPM Add-inexe) from the Service

Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPC

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

43 Using the Client Auto Update Program

If Planning and Consolidation version 100 or later is installed you can use the Client Auto Update

program to set up the server so that it determines if an upgrade for a connecting Administration client

is necessary

The following describes the use of the auto update program for the Administration Client and the EPM

add-in

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

42 Installing the EPM Add-in

3854 CUSTOMER 2012-06-13

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 37]

To use the Client Auto Update program for the Administration Client proceed as follows

1 From the Server Manager select Options Client Options

2 Select Admin Update

3 If users without administrator rights on their machines use the auto update enter an administrator

ID and password in the Admin ID and Admin password fields respectively The Admin ID should be a

member of the local administrators group on all the computers running the auto update This

setting is not needed if all users have administrator rights on their machines

4 Select Update

For the EPM Add-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 Optionshellip 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 Market Place (SMP) at httpservicesapcom

All support packages and patches are available from the SMP as a zip file

EPMEXCLCLNTltSPLgtzip is for a support package

EPMEXCLCLNTltSPLgtPltPLgtzip 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 ltSP versiongtmsp

EPM Addin Support Package ltSP versiongtxml

For a patch these files are

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

2012-06-13 CUSTOMER 3954

EPM Addin Patch ltpatch numbergtmsp

EPM Addin Patch ltpatch numbergtxml

2 Unzip the zip file and extract the two files to the application server folder (WebsrvrWebBPC

Installation)

3 From the Server Manager select Options Client Options

The system lists the available packages Select the package that you want to use for the autoupdate

You can set a different update policy for each package listed

EXAMPLE

The following table illustrates some possible situations assuming that you have installed the

first full version (V1)

Available maintenance packages

V2-user updateV3-force updateV4-force updateV5-user update

V5-user update V5-user updateV6-auto updateV7-force update

Minimum Required Version

V4 V4 V7

Notification A prompt tells the user to install maintenance package V4 using the Forced Update behavior

If User Update is enabled the prompt informs the user that maintenance package V5 is available

A prompt tells the user to install maintenance package V7 using the Forced Update behavior

New Version V4 V4 or V5 V7

If you change the update policy for any package click Update to complete the change

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

4054 CUSTOMER 2012-06-13

5 Connection Issues

You may experience connection problems with ports the proxy server or programs and settings that

interact with these components If you have any issues related to connection review the following

recommendations and troubleshooting tips

51 Checking for Open Ports

You must ensure that all required ports are open for inboundoutbound 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 431181836 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

NOTE

You can use the following site to scan for the normal ports It allows you to manually enter a port

number to test

httpwwwmyserverorgportsniffasp

You can change the name of a port

52 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 Explorer Tools Internet Options Connections LAN Settings ) or at the server level

Enabling content filtering on the proxy server or firewall may cause connection problems

If external users are having trouble connecting to the server make sure the proxy server connects

using a fully qualified domain name Fully qualified domain names typically resolve both internal

and external IP addresses

Each secure Planning and Consolidation server name must be identified on the proxy server

Proxy servers may or may not require authentication which could conflict with Planning and

Consolidation authentication Do not use authentication on the proxy server The system

5 Connection Issues

51 Checking for Open Ports

2012-06-13 CUSTOMER 4154

synchronizes the user name and password on the remote server with the local user name and

password

NOTE

For more information about setting up an ISA proxy server contact SAP Support to request a

copy of Setting up ISA Proxy Server White Paper

Internet Explorer Settings 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

5 Connection Issues

52 Proxy Server and Firewall Issues

4254 CUSTOMER 2012-06-13

6 Installing Planning and Consolidation with Two Active Directory Domains

To set up a Planning and Consolidation 10 application server in a hosted environment and use your

own domain users follow this procedure In general you install Planning and Consolidation on the

host domain use the host domain account and assign it to the Planning and Consolidation users

SysAdmin Admin and Users Then you accept one way trust (the host domain trusts your domain)

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

6 Installing Planning and Consolidation with Two Active Directory Domains

2012-06-13 CUSTOMER 4354

This page is left blank for documents that are printed on both sides

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

This section describes best practices and instructions for installing Planning and Consolidation in a

Terminal Services or Citrix Server deployment

71 Terminal Services Home Directories

We recommend using Terminal Server home directories rather than using the userrsquos 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

72 System Requirements

The Citrix server should be one of the following systems

XenApp 5 Enterprise

XenApp 5 Platinum

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 37])

73 Installing Planning and Consolidation

Prerequisites

The server installation files have been downloaded from SAP Service Marketplace and installed

Procedure

The following steps outline how to install the Planning and Consolidation clients in a Terminal Services

(TS) or Citrix Server deployment

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

71 Terminal Services Home Directories

2012-06-13 CUSTOMER 4554

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 userinstall

4 Open a browser and connect to the URL httpltPC_serverportgtsapbpcweb

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 userexecute 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 Iexploreexe http(s)

ltServerNamegt-NetBIOS or FQDNsapbpcweb

To publish Planning and Consolidation Administration CProgram FilesPC_MS

BPCAdminMainexe

74 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 userrsquos desktop) must be moved to the All UsersDesktop folder

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

74 Creating a Shortcut to the Launch Page

4654 CUSTOMER 2012-06-13

8 Installing SSIS Custom Tasks

This section provides background information and instructions for installing SQL Server Integration

Services (SSIS) for SQL Server 2008 and SQL Server 2012

The Planning and Consolidation Data Manager component supports and uses SSIS Since SQL Server

2008 and SQL Server 2012 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

81 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 Filelistxml 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

OSoftSetupexe ‒ 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 or OSoftSSIS2012_Client on the client machine followed by the SQL Server

version If you want to use SQL 2008 Tasks under the SQL 2012 environment you must install

OSoftSSIS2008_Client on the application server For detailed information see SAP Note 1707410

You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package by extracting

OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPC

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 or

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4754

OSoftSSIS2012_Client for creating a COM+ application For more information see Before You Modify

the SSIS Packages [page 50] and Setup of a COM+ Application on the Application Server [page 51]

Bin folder

This folder contains the following components

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCCachedll Planning and Consolidation Cache file

BPCDataFlowPackagedll or BPCDataFlowPackage2012dll

BPCDMdll

BPCDMTaskMaindll COM+ component

BPCFilePreviewdll

BPCGacUtil_20exe System File

BPCGacUtil_40exe System File

BPCImpersonatordll Planning and Consolidation Impersonator

BPCLogicdll

BPCScriptdll

BPCServerZipdll

BPCServiceResdll

BPCTransferMembersdll

BPCWriteBackdll

InteropDTSdll

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

4854 CUSTOMER 2012-06-13

Name Remark

OSoftAdminServerdll

OSoftAuditdll

OSoftComLibServerdll

OSoftCommonResQrydll

OSoftConfigurationdll

OSoftCustomXMLSvrdll

OSoftDatabaseADMINdll

OSoftDatabaseSYSADMINdll

OSoftDatabaseSYSADMINDMdll

OSoftDatabaseUSERdll

OSoftDMDTSXExecutedll or OSoftDMDTSXExecute2012dll

OSoftDMTaskFormdll

OSoftDMTaskMaindll

OSoftDMToolsdll

OSoftFileManagedll

OSoftLoggingdll

OSoftLogWriterdll

OSoftMetaDatadll

OSoftSQEdll

OSoftSystemConfigdll

OutlookSoftconfig Configuration file to connect DB server

XceedCompressiondll XceedZip file

XceedCompressionFormatsdll XceedZip file

XceedFileSystemdll XceedZip file

XceedZipdll XceedZip file

Config folder

This folder has FileListxml 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 FileListxml 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

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4954

OSoftSetupexe

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

NOTE

If you installed the OSoftSSIS2008_Client or OSoftSSIS2012_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

Resources Folder

This folder contains the BPCServicesdll and BPCServiceUIdll files which contain resource text

Only English resources are included for the SSIS custom tasks

82 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

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008 and 2012 respectively

8 Installing SSIS Custom Tasks

82 Before You Modify the SSIS Packages

5054 CUSTOMER 2012-06-13

Name Remark

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012 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

lthellipgtOSoftSSIS2008_Clientbin or lthellipgtOSoftSSIS2012_Clientbin

On the Planning and Consolidation application server

ltdrivegtWebsrvrbin

2 Paste these files into the folder 100DTSTasks for SQL Server 2008 or into 110DTSTasks for

SQL Server 2012 For example if you install your SQL 2008 server or R2 on CProgram Files

Microsoft SQL Server paste all files into the CProgram Files (x86)Microsoft SQL Server

100DTSTasks folder

In Integration Services set the property Run64BitRunTime to True

83 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 or OSoftSSIS2012_Client on the

application server

8 Installing SSIS Custom Tasks

83 Setup of a COM+ Application on the Application Server

2012-06-13 CUSTOMER 5154

Typographic Conventions

Example Description

ltgt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example Enter your ltUser Namegt

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 httpwwwsapcom

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

5254 CUSTOMER 2012-06-13

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

  • SAP BusinessObjects Planning and Consolidation 100
    • Table of Contents
    • 1 Introduction
      • 11 SAP Notes for the Installation
      • 12 Naming Conventions
        • 2 Installing Planning and Consolidation Servers
          • 21 Basic Steps
          • 22 Prerequisites
          • 23 Before Starting the Planning and Consolidation Server Installation
          • 24 Logging on to Servers
          • 25 Service-level Accounts
          • 26 Standard and Advanced Settings
          • 27 Installing the Prerequisites
            • 271 Installing the Prerequisites ndash Basic Steps
            • 272 Installing the Operating System
            • 273 Installing the SQL Server
            • 274 Installing Analysis Services
            • 275 Installing the Anti-Cross Site Scripting Library
              • 28 Installing on a Single Server
              • 29 Installing the Server in a Multiserver Configuration
                • 3 After Installing Planning and Consolidation Servers
                  • 31 Post-Installation Steps
                  • 32 Connecting to Solution Manager Diagnostics
                  • 33 Configuring the Planning and Consolidation NET Application Servers
                  • 34 Post-Installation Optional Configuration Steps
                    • 341 Enabling the Management Console
                    • 342 Setting Up ODBC Logging in IIS for the Default Web Site
                    • 343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2
                    • 344 Removing Default Access to the Console
                    • 345 Management Console Access Control
                    • 346 Using Client Certificates
                        • 4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office
                          • 41 Installing the Administration Client
                          • 42 Installing the EPM Add-in
                          • 43 Using the Client Auto Update Program
                            • 5 Connection Issues
                              • 51 Checking for Open Ports
                              • 52 Proxy Server and Firewall Issues
                                • 6 Installing Planning and Consolidation with Two Active Directory Domains
                                • 7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
                                  • 71 Terminal Services Home Directories
                                  • 72 System Requirements
                                  • 73 Installing Planning and Consolidation
                                  • 74 Creating a Shortcut to the Launch Page
                                    • 8 Installing SSIS Custom Tasks
                                      • 81 Composition of SSIS Custom Task Installation
                                      • 82 Before You Modify the SSIS Packages
                                      • 83 Setup of a COM+ Application on the Application Server
                                          • Copyright and trademarks
Page 23: Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

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)

RECOMMENDATION

We do not recommend using dynamic ports

In an SQL server the default instance has a listener which listens on a fixed port (TCP

port 1433) However for the named instance the port on which the SQL server listens is

random and dynamically selected when the named instance of the SQL server starts This

recommendation prevents any conflict problems

From the SQL Server Configuration Manager specify the client protocol options for the application

server

1 Select Client Protocols from the SQL Native Client Configuration folder

2 From the right side of the window double-click TCPIP The TCPIP 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

NOTE

We 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

274 Installing Analysis Services

ProcedureAfter you install SQL Server and its required service packs and hotfixes you must install SQL Server

Analysis Services and its required service packs and hotfixes

2 Installing Planning and Consolidation Servers

27 Installing the Prerequisites

2012-06-13 CUSTOMER 2354

NOTE

If you have migrated your Analysis Services repository to the SQL Server back up the database

that contains the repository before installing this release

To install Analysis Services for SQL Server 2008 SQL Server 2008 R2 or SQL Server 2012 follow the steps

and guidelines in httptechnetmicrosoftcomen-uslibraryms143219aspx

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 httpwwwmicrosoftcomdownloads

detailsaspxFamilyID=3be0488d-e7aa-4078-a050- ae39912d2e43ampdisplaylang=en

275 Installing the Anti-Cross Site Scripting Library

Procedure

Before installing Planning and Consolidation servers you must download the Anti-Cross Site Scripting

Library (version 42 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 AntiXSSLibraryDLL from the Microsoft Web

site at httpwwwmicrosoftcomdownloadendetailsaspxid=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 AntiXssLibrarydll

28 Installing on a Single Server

When you install all Planning and Consolidation server components on a single server you should

consider the following issues

Make sure the server has a minimum of 800 MB of hard disk space

Additional environment installations require more free disk space which is a minimum of two

times the uncompressed size of the environment files

When you install Planning and Consolidation on a single-server the system adds the following server

components

SQL Server

SQL Server Analysis Services (SSAS)

Application Server

FileShare server

Procedure

To install Planning and Consolidation on a single server take the following steps

1 Exit all Windows programs

2 Installing Planning and Consolidation Servers

28 Installing on a Single Server

2454 CUSTOMER 2012-06-13

2 Log on to the server with a local server user ID or domain user ID For more information see Logging

on to servers [page 14]

3 Make sure all prerequisite software is installed on the server For more information see Installing

the Prerequisites [page 17]

4 Obtain SAP Planning and Consolidation from the Downloads SAP Installations amp Upgrades area of

SAP Service Marketplace then extract the files and run StartUpexe

5 From the Server Install screen select Install the Planning and Consolidation server

6 From the Welcome screen choose Next

7 From the License Agreement page choose I accept the terms of the license agreement then choose Next

8 From the Installation Method page accept the default Single machine enter a system ID for the system

landscape directory (SLD) and choose Next

NOTE

Entering a system ID of the SLD is only required if you have a SAP Solution Manager license

If you do not have a SAP Solution Manager license you can leave this field empty

9 From the Authentication Method page choose the desired authentication method and choose Next

10 If you have chosen SAP BusinessObjects User Management System in the previous screen on the CMS

Authentication page enter the information required to log on to CMS as an administrator

The following information is required

Field Description

System name CMS system name (server nameport number) for example CMSServer6400

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

11 After entering the CMS administrator authentication details choose Next

12 From the Service type accounts page enter service-level account user IDs and passwords See Service-

Level Accounts [page 15]

13 After defining the IDs and passwords choose Next

14 From the Server Information page (see Standard and Advanced Settings [page 16]) do one of the following

Review the standard settings and choose Next

To set advanced settings choose the Advanced Settings button Enter the desired information

and choose Next

2 Installing Planning and Consolidation Servers

28 Installing on a Single Server

2012-06-13 CUSTOMER 2554

15 Specify the location and name of AntiXssLibrarydll See Installing the Anti-Cross Site Scripting Library [page

24]

Choose Next

16 Select destination folders for Programs and Data The Data files include Webfolders and FileDB

(published reports) and should be installed on a separate drive in a production environment This

recommendation reduces the hard disk IO time and helps to speed up SQL commands

Accept the defaults or make your selections then choose Next

17 Select the default values for the Web client The values are used to determine the default language

and region for the Web client when you connect to it You can change the values in the Planning

and Consolidation Server Manager

18 The installation process takes a few moments When it is complete choose Exit

19 A prompt is displayed to restart your computer Select OK to restart

20 Perform the steps in After Installing Planning and Consolidation Servers [page 27]

29 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 24]) with the following

exceptions

On the Installation Method page do not accept the default instead choose Network Load Balancing

environment With this option there is an additional choice to Include sample environment (required on only

one of the application servers) This is because when you install the application server it connects to the

database server and creates the sample environment (EnvironmentShell) Installing the sample

environment is required on only one application server and you may choose which one

In the Virtual Name field enter the virtual IP address virtual name in the default properties

2 Installing Planning and Consolidation Servers

29 Installing the Server in a Multiserver Configuration

2654 CUSTOMER 2012-06-13

3 After Installing Planning and Consolidation Servers

31 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 28]

2 Configure the Planning and Consolidation NET and application server to ensure that it and its

related services function properly and reliably For more information see Configuring the Planning and

Consolidation NET Application Server [page 29]

3 Optional configuration steps [page 30]

1 To ensure proper functioning of the Management Console create an SQL user and modify

the System DSN and IIS to reflect those user credentials See Enabling Management Console [page

30]

2 Configure custom ODBC logging for the default Web site For details of how to configure

custom logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web

Site [page 31]

3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC

Data Source [page 32]

4 Modify the default access rights to the Management Console By default users in Active

Directory can access the Management Console with whatever rights they have been granted

on the server For information about removing default access and creating a group that can

access the console see Removing Default Access to the Console [page 32]

5 Add authorized users or groups to the group that can access the Management Console We

recommend that you only grant Management Console access to system administrators

Planning and Consolidation users should not have any access For more information see

Management Console Access Control [page 33]

6 Configure the use of client certificates for authentication See Using Client Certificates [page

34]

4 Take the following steps to set up security

If you are defining security and application structure continue with step 5

3 After Installing Planning and Consolidation Servers

31 Post-Installation Steps

2012-06-13 CUSTOMER 2754

If you want to designate someone other than the system administrator to manage security

and application structure log on to EnvironmentShell designate a user as a Primary

Administrator

This user must have Administration ‒ Environment and Security ‒ Define User task rights

so that he or she can add and delete environments and define user security

The Primary Administrator can continue with the next step (5)

5 From the machine on which you administer Planning and Consolidation install the

Administration client See Installing the Administration Client [page 37]

6 Start Planning and Consolidation Administration from the launch page

7 Select Connection Wizard and log on to EnvironmentShell

8 Create a new environment using EnvironmentShell as the source

9 Log on to the newly created environment and set up users teams and task profiles (You must

set up task profiles since there is no access to Planning and Consolidation tasks)

10 Set up your data access profiles and add users (or teams) to one or more data access profiles (You

must complete this step since there is no access to dimensions or members)

NOTE

To allow users to request and query large amounts of data you can edit the metabasexml file located

at CWindowssystem32inetsrv Set the following parameters to the stated values

ASPBUFFERINGLIMIT = 10485760

MAXREQUESTENTITYALLOWED = 10485760

32 Connecting to Solution Manager Diagnostics

NOTE

You only need to perform the steps in this section if you have a SAP Solution Manager licence

The diagnostics functions in SAP Solution Manager allow identification analysis and resolution of

problems This procedure provides the steps required to connect Planning and Consolidation to

Solution Manager Diagnostics

Procedure

1 Install the Diagnostics Agent according to SAP Note 1234387 on all servers where application servers

are installed

NOTE

Installation files for Diagnostics Agent are available on Service Marketplace by navigating to

Support Packages and Patches mdash Entry by Application Group SAP Technology Components SAP

SOLUTION MANAGER SAP SOLUTION MANAGER 70 EHP 1 Entry by Component Agents

for managed systems DIAGNOSTICS AGENT 711

3 After Installing Planning and Consolidation Servers

32 Connecting to Solution Manager Diagnostics

2854 CUSTOMER 2012-06-13

Download the installation file based on the 64-bit Windows Server system landscape

2 To access the DBA Cockpit you must create a user account with sufficient rights on all Windows

Servers where Microsoft SQL Server is installed Do the following

1 Start Computer Management then select Action New User

2 Create a new user

3 Right-click on the user then choose Properties On the Member Of tab select Add

4 Add the group SQLServerltReleasegtSQLAgentUser$ltDomain or hostnamegt$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 httpsservicesapcom~sapidb011000358700000074392009E and follow

the chapters that apply to Planning and Consolidation

33 Configuring the Planning and Consolidation NET Application Servers

Procedure

Modifying machineconfig Files

To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock

occurrences that would cause the application server to ldquosleeprdquo and not process anymore you can

modify the machineconfig file which resides in the WINDOWSMicrosoftNETFramework64

v4030319Config directory

1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to

specify whether to automatically configure settings to achieve optimal performance based on the

machine configuration You can set this attribute to True or False

For more information see httpmsdnmicrosoftcomen-uslibrary7w2sway1aspx

2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the

Planning and Consolidation application) or Machineconfig (for all applications including

Planning and Consolidation) to ensure the validationKey and decryptionKey keys have the same

value on all application servers This way when the authentication cookie is checked the

authentication ticket used on one server can still be valid on another server

For more information and sample Visual Basic code for generating random key values see http

msdnmicrosoftcomen-uslibraryms998288aspx

3 After Installing Planning and Consolidation Servers

33 Configuring the Planning and Consolidation NET Application Servers

2012-06-13 CUSTOMER 2954

paght000007_webfarmdeploymentconsiderations and httpmsdnmicrosoftcomen-us

libraryms998310aspx

34 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 30]

2 Configure custom ODBC logging for the default Web site For details of how to configure custom

logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page

31]

3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC Data

Source [page 32]

4 Modify the default access rights to the Management Console By default users in Active Directory

can access the Management Console with whatever rights they have been granted on the server

For information about removing default access and creating a group that can access the console

see Removing Default Access to the Console [page 32]

5 Add authorized users or groups to the group that can access the Management Console We

recommend that you only grant Management Console access to system administrators Planning

and Consolidation users should not have any access For more information see Management Console

Access Control [page 33]

6 Configure the use of client certificates for authentication See Using Client Certificates [page 34]

341 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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3054 CUSTOMER 2012-06-13

NOTE

Without these updates the Management Console does work but some functionality (specifically

User Activity and Service Status) does not work as expected

Should you need to uninstall Planning and Consolidation we recommend that you reset the

Active Log Format field in IIS to W3C Extended Log File Format

342 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 ApplicationHostconfig set the property customLogPluginClsid to the value FF16065B-

DE82-11CF-BC0A-00AA006111E0 Set the logFormat to Custom You can find this in the ltlogFilegt

node in ApplicationHostconfig as shown here

ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0

logFormat=Custom gt

Use the following AppCmds to configure IIS to use ODBC logging for the default Web site

appcmd site set sitenameDefault Web Site

logFilecustomLogPluginClsidFF16065B-DE82-11CF-BC0A-00AA006111E0

appcmd site set sitenameDefault Web Site logFilelogFormatCustom

Configuring ODBC Logging Parameters in ApplicationHostconfig

Configure ApplicationHostconfig to contain the database table information as set up in the Microsoft

Support article specified in the Prerequisites section Configure these settings in the ltodbcLogginggt

node under ltsystemwebServergt

EXAMPLE

ltlocation path=Default Web Sitegt

ltsystemwebServergt

ltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog

userName=Username password=mypassword gt

ltsystemwebServergt

ltlocationgt

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3154

Use the following AppCmds to configure these attributes for the default Web site

appcmd set config Default Web Site sectionodbcLogging

dataSourceBPC_ManagementDSN commitappHost

appcmd set config Default Web Site sectionodbcLogging tableNameBPCLog

commitappHost

appcmd set config Default Web Site sectionodbcLogging userNameUsername

commitappHost

appcmd set config Default Web Site sectionodbcLogging passwordmypassword

commitappHost

NOTE

You cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must

use the SQL Server ODBC driver For more information see the Microsoft Knowledge Base article

931202 The requirements for using the ODBC logging feature in IIS

343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2

ProcedureThis procedure describes how to set up an ODBC data source for the Management Console in Windows

Server 2008 or Windows Server 2008 R2

Proceed as follows

1 Open ODBC Connection Manager

2 On the System DSN tab page add a new DSN

Choose Add

Choose SQL Server as the driver

Choose Finish

3 In the Name and Description fields enter BPC_ManagementDSN

4 In the Server field enter the name of your SQL Server Choose Next

5 Leave the default settings and choose Next

6 Choose the Change the default database to field and enter AppServer Choose Next

7 Leave default settings and choose Next

8 Choose OK

344 Removing Default Access to the Console

NOTE

If you have chosen SAP BusinessObjects User Management System in the installation screen you

do not need to remove or configure access because the Management Console service always runs

with the System Admin ID account which is a member of the Administrators group

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3254 CUSTOMER 2012-06-13

ProcedureTo remove default access to the Management Console and create a group that does have access to the

console use the procedure described below

NOTE

Create your Management Console administrative group either on the server that hosts the

Management Console or in the Active Directory

1 In the context menu of the servers My Computer icon choose Manage

2 In the Computer Management dialog box choose Local Users and Groups Groups

NOTE

Alternatively you can perform analogous steps in Active Directory

3 In the 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

NOTE

This step is a necessary precursor to the completion of this procedure

10 In the Security dialog box click Copy to ensure that the System group retains its privileges

11 Remove access to the Management Console from all groups that should not have it

12 Choose Authentication in the center pane then disable Windows authentication

ResultUsers who have not been granted access to the Management Console can still open the Management

Console Web page but it contains no data or menu options This does not affect the access that a user

would otherwise have to Planning and Consolidation

345 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 32] Their rights in

Active Directory determine what they can access in the Console

By default any member of the Administrators Active Directory group on the application server or

domain has full access to all of the features of the Console except the Planning and Consolidation

logging area Access to Planning and Consolidation logging is controlled within the Planning and

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3354

Consolidation Administration Client task security The user must be granted View system logs task

privileges For more information see the SAP Library Planning and Consolidation Administrators Guide in

httpservicesapcominstguidesepm-bpc 100 version for the Microsoft platform

Your IT policy determines whether you grant access by group or user You may wish to create several

levels of Console users (read-only users for example) in your environment

To grant or limit access to users or groups you can add or remove the following privileges from the

areas described in this table

Privilege Rights Management Area

Task Manager and Kill Process Administrators group on application server or domain

Performance Monitor Counters Administrators group on application server or domain Power Users group on application server or domain Performance Monitor Users group on application server

Microsoft Analysis Services performance monitoring

Administrators group on application server or domain

Microsoft SQL Server Monitoring (performance counters and statistics)

Administrators group on application server or domain

346 Using Client Certificates

To enable the use of client certificates in Planning and Consolidation you must follow several manual

steps

NOTE

Planning 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 httptechnetmicrosoftcomen-us

librarycc753810aspx

For more information about configuring the client certificate mapping authentication see http

technetmicrosoftcomen-uslibrarycc732996(WS10)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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3454 CUSTOMER 2012-06-13

This option allows you to use a client certificate or username and password (Basic

authentication) to connect to Planning and Consolidation

2 Enable anonymous authentication

1 In the IIS Manager expand the node of the Planning and Consolidation web site

2 Select the ManagementConsole directory (ltWebsitegtManagementConsole) to open the

ManagementConsole home page

3 Double-click Authentication and enable Anonymous Authentication

4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way

as in step 3

5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the same

way as in step 3

3 Change the web configuration settings

1 Open the ltPC_MSgtWebsrvrWebBPCwebconfig file

2 Find the text clientCredentialType=Windows

3 Change value of clientCredentialType to None (clientCredentialType=None)

4 Open the PC_MSWebsrvrWebPOASBCwebconfig file Repeat steps 2 and 3

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3554

This page is left blank for documents that are printed on both sides

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

The installation of the Planning and Consolidation Administration Client allows administrators to

build and maintain Planning and Consolidation environments and models and administer security

All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions

add-in for Microsoft Office for more information see the SAP BusinessObjects EPM solutions add-in for

Microsoft Office help

NOTE

You must update the Administration Client to the same version as the server

If your PC is on a different domain than your server you must set the Internet Explorer

Security Zone value of the Planning and Consolidation client to prompt for user name and

password Otherwise the Planning and Consolidation Start Page does not display

41 Installing the Administration Client

Prerequisites

NOTE

For a definitive list of system requirements see the Product Availability Matrix on SAP Service

Marketplace at httpservicesapcompam Search on Planning and Consolidation

The following list describes the minimum software requirements

Microsoft Internet Explorer 70 or 80

Microsoft Office 2007 or 2010

NET Framework 20 or higher (install any required NET Framework Hotfixes by referring to

httpsupportmicrosoftcomkb)

Pentium IV (1 GHz CPU)

512 MB RAM

100 MB of free hard disk space in the My Documents folder

20 MB of free hard disk space for the installed Administration files

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

41 Installing the Administration Client

2012-06-13 CUSTOMER 3754

NOTE

We recommend that you install all of the latest Microsoft Windows hotfixes prior to installing

the Administration client For information about which hotfixes to install see http

updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us

ProcedureThe following procedure describes how to install the Administration Client on to an administratorrsquos

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 AddRemove Programs in the Windows Control Panel

3 Point your browser to the Planning and Consolidation Web at httpltPC_serverportgtsap

bpcweb

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

42 Installing the EPM Add-in

The Planning and Consolidation installation media does not contain the EPM addin setup program

You must download the most recent version of the full setup (EPM Add-inexe) from the Service

Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPC

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

43 Using the Client Auto Update Program

If Planning and Consolidation version 100 or later is installed you can use the Client Auto Update

program to set up the server so that it determines if an upgrade for a connecting Administration client

is necessary

The following describes the use of the auto update program for the Administration Client and the EPM

add-in

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

42 Installing the EPM Add-in

3854 CUSTOMER 2012-06-13

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 37]

To use the Client Auto Update program for the Administration Client proceed as follows

1 From the Server Manager select Options Client Options

2 Select Admin Update

3 If users without administrator rights on their machines use the auto update enter an administrator

ID and password in the Admin ID and Admin password fields respectively The Admin ID should be a

member of the local administrators group on all the computers running the auto update This

setting is not needed if all users have administrator rights on their machines

4 Select Update

For the EPM Add-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 Optionshellip 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 Market Place (SMP) at httpservicesapcom

All support packages and patches are available from the SMP as a zip file

EPMEXCLCLNTltSPLgtzip is for a support package

EPMEXCLCLNTltSPLgtPltPLgtzip 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 ltSP versiongtmsp

EPM Addin Support Package ltSP versiongtxml

For a patch these files are

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

2012-06-13 CUSTOMER 3954

EPM Addin Patch ltpatch numbergtmsp

EPM Addin Patch ltpatch numbergtxml

2 Unzip the zip file and extract the two files to the application server folder (WebsrvrWebBPC

Installation)

3 From the Server Manager select Options Client Options

The system lists the available packages Select the package that you want to use for the autoupdate

You can set a different update policy for each package listed

EXAMPLE

The following table illustrates some possible situations assuming that you have installed the

first full version (V1)

Available maintenance packages

V2-user updateV3-force updateV4-force updateV5-user update

V5-user update V5-user updateV6-auto updateV7-force update

Minimum Required Version

V4 V4 V7

Notification A prompt tells the user to install maintenance package V4 using the Forced Update behavior

If User Update is enabled the prompt informs the user that maintenance package V5 is available

A prompt tells the user to install maintenance package V7 using the Forced Update behavior

New Version V4 V4 or V5 V7

If you change the update policy for any package click Update to complete the change

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

4054 CUSTOMER 2012-06-13

5 Connection Issues

You may experience connection problems with ports the proxy server or programs and settings that

interact with these components If you have any issues related to connection review the following

recommendations and troubleshooting tips

51 Checking for Open Ports

You must ensure that all required ports are open for inboundoutbound 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 431181836 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

NOTE

You can use the following site to scan for the normal ports It allows you to manually enter a port

number to test

httpwwwmyserverorgportsniffasp

You can change the name of a port

52 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 Explorer Tools Internet Options Connections LAN Settings ) or at the server level

Enabling content filtering on the proxy server or firewall may cause connection problems

If external users are having trouble connecting to the server make sure the proxy server connects

using a fully qualified domain name Fully qualified domain names typically resolve both internal

and external IP addresses

Each secure Planning and Consolidation server name must be identified on the proxy server

Proxy servers may or may not require authentication which could conflict with Planning and

Consolidation authentication Do not use authentication on the proxy server The system

5 Connection Issues

51 Checking for Open Ports

2012-06-13 CUSTOMER 4154

synchronizes the user name and password on the remote server with the local user name and

password

NOTE

For more information about setting up an ISA proxy server contact SAP Support to request a

copy of Setting up ISA Proxy Server White Paper

Internet Explorer Settings 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

5 Connection Issues

52 Proxy Server and Firewall Issues

4254 CUSTOMER 2012-06-13

6 Installing Planning and Consolidation with Two Active Directory Domains

To set up a Planning and Consolidation 10 application server in a hosted environment and use your

own domain users follow this procedure In general you install Planning and Consolidation on the

host domain use the host domain account and assign it to the Planning and Consolidation users

SysAdmin Admin and Users Then you accept one way trust (the host domain trusts your domain)

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

6 Installing Planning and Consolidation with Two Active Directory Domains

2012-06-13 CUSTOMER 4354

This page is left blank for documents that are printed on both sides

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

This section describes best practices and instructions for installing Planning and Consolidation in a

Terminal Services or Citrix Server deployment

71 Terminal Services Home Directories

We recommend using Terminal Server home directories rather than using the userrsquos 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

72 System Requirements

The Citrix server should be one of the following systems

XenApp 5 Enterprise

XenApp 5 Platinum

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 37])

73 Installing Planning and Consolidation

Prerequisites

The server installation files have been downloaded from SAP Service Marketplace and installed

Procedure

The following steps outline how to install the Planning and Consolidation clients in a Terminal Services

(TS) or Citrix Server deployment

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

71 Terminal Services Home Directories

2012-06-13 CUSTOMER 4554

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 userinstall

4 Open a browser and connect to the URL httpltPC_serverportgtsapbpcweb

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 userexecute 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 Iexploreexe http(s)

ltServerNamegt-NetBIOS or FQDNsapbpcweb

To publish Planning and Consolidation Administration CProgram FilesPC_MS

BPCAdminMainexe

74 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 userrsquos desktop) must be moved to the All UsersDesktop folder

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

74 Creating a Shortcut to the Launch Page

4654 CUSTOMER 2012-06-13

8 Installing SSIS Custom Tasks

This section provides background information and instructions for installing SQL Server Integration

Services (SSIS) for SQL Server 2008 and SQL Server 2012

The Planning and Consolidation Data Manager component supports and uses SSIS Since SQL Server

2008 and SQL Server 2012 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

81 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 Filelistxml 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

OSoftSetupexe ‒ 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 or OSoftSSIS2012_Client on the client machine followed by the SQL Server

version If you want to use SQL 2008 Tasks under the SQL 2012 environment you must install

OSoftSSIS2008_Client on the application server For detailed information see SAP Note 1707410

You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package by extracting

OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPC

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 or

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4754

OSoftSSIS2012_Client for creating a COM+ application For more information see Before You Modify

the SSIS Packages [page 50] and Setup of a COM+ Application on the Application Server [page 51]

Bin folder

This folder contains the following components

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCCachedll Planning and Consolidation Cache file

BPCDataFlowPackagedll or BPCDataFlowPackage2012dll

BPCDMdll

BPCDMTaskMaindll COM+ component

BPCFilePreviewdll

BPCGacUtil_20exe System File

BPCGacUtil_40exe System File

BPCImpersonatordll Planning and Consolidation Impersonator

BPCLogicdll

BPCScriptdll

BPCServerZipdll

BPCServiceResdll

BPCTransferMembersdll

BPCWriteBackdll

InteropDTSdll

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

4854 CUSTOMER 2012-06-13

Name Remark

OSoftAdminServerdll

OSoftAuditdll

OSoftComLibServerdll

OSoftCommonResQrydll

OSoftConfigurationdll

OSoftCustomXMLSvrdll

OSoftDatabaseADMINdll

OSoftDatabaseSYSADMINdll

OSoftDatabaseSYSADMINDMdll

OSoftDatabaseUSERdll

OSoftDMDTSXExecutedll or OSoftDMDTSXExecute2012dll

OSoftDMTaskFormdll

OSoftDMTaskMaindll

OSoftDMToolsdll

OSoftFileManagedll

OSoftLoggingdll

OSoftLogWriterdll

OSoftMetaDatadll

OSoftSQEdll

OSoftSystemConfigdll

OutlookSoftconfig Configuration file to connect DB server

XceedCompressiondll XceedZip file

XceedCompressionFormatsdll XceedZip file

XceedFileSystemdll XceedZip file

XceedZipdll XceedZip file

Config folder

This folder has FileListxml 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 FileListxml 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

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4954

OSoftSetupexe

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

NOTE

If you installed the OSoftSSIS2008_Client or OSoftSSIS2012_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

Resources Folder

This folder contains the BPCServicesdll and BPCServiceUIdll files which contain resource text

Only English resources are included for the SSIS custom tasks

82 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

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008 and 2012 respectively

8 Installing SSIS Custom Tasks

82 Before You Modify the SSIS Packages

5054 CUSTOMER 2012-06-13

Name Remark

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012 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

lthellipgtOSoftSSIS2008_Clientbin or lthellipgtOSoftSSIS2012_Clientbin

On the Planning and Consolidation application server

ltdrivegtWebsrvrbin

2 Paste these files into the folder 100DTSTasks for SQL Server 2008 or into 110DTSTasks for

SQL Server 2012 For example if you install your SQL 2008 server or R2 on CProgram Files

Microsoft SQL Server paste all files into the CProgram Files (x86)Microsoft SQL Server

100DTSTasks folder

In Integration Services set the property Run64BitRunTime to True

83 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 or OSoftSSIS2012_Client on the

application server

8 Installing SSIS Custom Tasks

83 Setup of a COM+ Application on the Application Server

2012-06-13 CUSTOMER 5154

Typographic Conventions

Example Description

ltgt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example Enter your ltUser Namegt

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 httpwwwsapcom

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

5254 CUSTOMER 2012-06-13

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

  • SAP BusinessObjects Planning and Consolidation 100
    • Table of Contents
    • 1 Introduction
      • 11 SAP Notes for the Installation
      • 12 Naming Conventions
        • 2 Installing Planning and Consolidation Servers
          • 21 Basic Steps
          • 22 Prerequisites
          • 23 Before Starting the Planning and Consolidation Server Installation
          • 24 Logging on to Servers
          • 25 Service-level Accounts
          • 26 Standard and Advanced Settings
          • 27 Installing the Prerequisites
            • 271 Installing the Prerequisites ndash Basic Steps
            • 272 Installing the Operating System
            • 273 Installing the SQL Server
            • 274 Installing Analysis Services
            • 275 Installing the Anti-Cross Site Scripting Library
              • 28 Installing on a Single Server
              • 29 Installing the Server in a Multiserver Configuration
                • 3 After Installing Planning and Consolidation Servers
                  • 31 Post-Installation Steps
                  • 32 Connecting to Solution Manager Diagnostics
                  • 33 Configuring the Planning and Consolidation NET Application Servers
                  • 34 Post-Installation Optional Configuration Steps
                    • 341 Enabling the Management Console
                    • 342 Setting Up ODBC Logging in IIS for the Default Web Site
                    • 343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2
                    • 344 Removing Default Access to the Console
                    • 345 Management Console Access Control
                    • 346 Using Client Certificates
                        • 4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office
                          • 41 Installing the Administration Client
                          • 42 Installing the EPM Add-in
                          • 43 Using the Client Auto Update Program
                            • 5 Connection Issues
                              • 51 Checking for Open Ports
                              • 52 Proxy Server and Firewall Issues
                                • 6 Installing Planning and Consolidation with Two Active Directory Domains
                                • 7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
                                  • 71 Terminal Services Home Directories
                                  • 72 System Requirements
                                  • 73 Installing Planning and Consolidation
                                  • 74 Creating a Shortcut to the Launch Page
                                    • 8 Installing SSIS Custom Tasks
                                      • 81 Composition of SSIS Custom Task Installation
                                      • 82 Before You Modify the SSIS Packages
                                      • 83 Setup of a COM+ Application on the Application Server
                                          • Copyright and trademarks
Page 24: Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

NOTE

If you have migrated your Analysis Services repository to the SQL Server back up the database

that contains the repository before installing this release

To install Analysis Services for SQL Server 2008 SQL Server 2008 R2 or SQL Server 2012 follow the steps

and guidelines in httptechnetmicrosoftcomen-uslibraryms143219aspx

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 httpwwwmicrosoftcomdownloads

detailsaspxFamilyID=3be0488d-e7aa-4078-a050- ae39912d2e43ampdisplaylang=en

275 Installing the Anti-Cross Site Scripting Library

Procedure

Before installing Planning and Consolidation servers you must download the Anti-Cross Site Scripting

Library (version 42 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 AntiXSSLibraryDLL from the Microsoft Web

site at httpwwwmicrosoftcomdownloadendetailsaspxid=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 AntiXssLibrarydll

28 Installing on a Single Server

When you install all Planning and Consolidation server components on a single server you should

consider the following issues

Make sure the server has a minimum of 800 MB of hard disk space

Additional environment installations require more free disk space which is a minimum of two

times the uncompressed size of the environment files

When you install Planning and Consolidation on a single-server the system adds the following server

components

SQL Server

SQL Server Analysis Services (SSAS)

Application Server

FileShare server

Procedure

To install Planning and Consolidation on a single server take the following steps

1 Exit all Windows programs

2 Installing Planning and Consolidation Servers

28 Installing on a Single Server

2454 CUSTOMER 2012-06-13

2 Log on to the server with a local server user ID or domain user ID For more information see Logging

on to servers [page 14]

3 Make sure all prerequisite software is installed on the server For more information see Installing

the Prerequisites [page 17]

4 Obtain SAP Planning and Consolidation from the Downloads SAP Installations amp Upgrades area of

SAP Service Marketplace then extract the files and run StartUpexe

5 From the Server Install screen select Install the Planning and Consolidation server

6 From the Welcome screen choose Next

7 From the License Agreement page choose I accept the terms of the license agreement then choose Next

8 From the Installation Method page accept the default Single machine enter a system ID for the system

landscape directory (SLD) and choose Next

NOTE

Entering a system ID of the SLD is only required if you have a SAP Solution Manager license

If you do not have a SAP Solution Manager license you can leave this field empty

9 From the Authentication Method page choose the desired authentication method and choose Next

10 If you have chosen SAP BusinessObjects User Management System in the previous screen on the CMS

Authentication page enter the information required to log on to CMS as an administrator

The following information is required

Field Description

System name CMS system name (server nameport number) for example CMSServer6400

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

11 After entering the CMS administrator authentication details choose Next

12 From the Service type accounts page enter service-level account user IDs and passwords See Service-

Level Accounts [page 15]

13 After defining the IDs and passwords choose Next

14 From the Server Information page (see Standard and Advanced Settings [page 16]) do one of the following

Review the standard settings and choose Next

To set advanced settings choose the Advanced Settings button Enter the desired information

and choose Next

2 Installing Planning and Consolidation Servers

28 Installing on a Single Server

2012-06-13 CUSTOMER 2554

15 Specify the location and name of AntiXssLibrarydll See Installing the Anti-Cross Site Scripting Library [page

24]

Choose Next

16 Select destination folders for Programs and Data The Data files include Webfolders and FileDB

(published reports) and should be installed on a separate drive in a production environment This

recommendation reduces the hard disk IO time and helps to speed up SQL commands

Accept the defaults or make your selections then choose Next

17 Select the default values for the Web client The values are used to determine the default language

and region for the Web client when you connect to it You can change the values in the Planning

and Consolidation Server Manager

18 The installation process takes a few moments When it is complete choose Exit

19 A prompt is displayed to restart your computer Select OK to restart

20 Perform the steps in After Installing Planning and Consolidation Servers [page 27]

29 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 24]) with the following

exceptions

On the Installation Method page do not accept the default instead choose Network Load Balancing

environment With this option there is an additional choice to Include sample environment (required on only

one of the application servers) This is because when you install the application server it connects to the

database server and creates the sample environment (EnvironmentShell) Installing the sample

environment is required on only one application server and you may choose which one

In the Virtual Name field enter the virtual IP address virtual name in the default properties

2 Installing Planning and Consolidation Servers

29 Installing the Server in a Multiserver Configuration

2654 CUSTOMER 2012-06-13

3 After Installing Planning and Consolidation Servers

31 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 28]

2 Configure the Planning and Consolidation NET and application server to ensure that it and its

related services function properly and reliably For more information see Configuring the Planning and

Consolidation NET Application Server [page 29]

3 Optional configuration steps [page 30]

1 To ensure proper functioning of the Management Console create an SQL user and modify

the System DSN and IIS to reflect those user credentials See Enabling Management Console [page

30]

2 Configure custom ODBC logging for the default Web site For details of how to configure

custom logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web

Site [page 31]

3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC

Data Source [page 32]

4 Modify the default access rights to the Management Console By default users in Active

Directory can access the Management Console with whatever rights they have been granted

on the server For information about removing default access and creating a group that can

access the console see Removing Default Access to the Console [page 32]

5 Add authorized users or groups to the group that can access the Management Console We

recommend that you only grant Management Console access to system administrators

Planning and Consolidation users should not have any access For more information see

Management Console Access Control [page 33]

6 Configure the use of client certificates for authentication See Using Client Certificates [page

34]

4 Take the following steps to set up security

If you are defining security and application structure continue with step 5

3 After Installing Planning and Consolidation Servers

31 Post-Installation Steps

2012-06-13 CUSTOMER 2754

If you want to designate someone other than the system administrator to manage security

and application structure log on to EnvironmentShell designate a user as a Primary

Administrator

This user must have Administration ‒ Environment and Security ‒ Define User task rights

so that he or she can add and delete environments and define user security

The Primary Administrator can continue with the next step (5)

5 From the machine on which you administer Planning and Consolidation install the

Administration client See Installing the Administration Client [page 37]

6 Start Planning and Consolidation Administration from the launch page

7 Select Connection Wizard and log on to EnvironmentShell

8 Create a new environment using EnvironmentShell as the source

9 Log on to the newly created environment and set up users teams and task profiles (You must

set up task profiles since there is no access to Planning and Consolidation tasks)

10 Set up your data access profiles and add users (or teams) to one or more data access profiles (You

must complete this step since there is no access to dimensions or members)

NOTE

To allow users to request and query large amounts of data you can edit the metabasexml file located

at CWindowssystem32inetsrv Set the following parameters to the stated values

ASPBUFFERINGLIMIT = 10485760

MAXREQUESTENTITYALLOWED = 10485760

32 Connecting to Solution Manager Diagnostics

NOTE

You only need to perform the steps in this section if you have a SAP Solution Manager licence

The diagnostics functions in SAP Solution Manager allow identification analysis and resolution of

problems This procedure provides the steps required to connect Planning and Consolidation to

Solution Manager Diagnostics

Procedure

1 Install the Diagnostics Agent according to SAP Note 1234387 on all servers where application servers

are installed

NOTE

Installation files for Diagnostics Agent are available on Service Marketplace by navigating to

Support Packages and Patches mdash Entry by Application Group SAP Technology Components SAP

SOLUTION MANAGER SAP SOLUTION MANAGER 70 EHP 1 Entry by Component Agents

for managed systems DIAGNOSTICS AGENT 711

3 After Installing Planning and Consolidation Servers

32 Connecting to Solution Manager Diagnostics

2854 CUSTOMER 2012-06-13

Download the installation file based on the 64-bit Windows Server system landscape

2 To access the DBA Cockpit you must create a user account with sufficient rights on all Windows

Servers where Microsoft SQL Server is installed Do the following

1 Start Computer Management then select Action New User

2 Create a new user

3 Right-click on the user then choose Properties On the Member Of tab select Add

4 Add the group SQLServerltReleasegtSQLAgentUser$ltDomain or hostnamegt$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 httpsservicesapcom~sapidb011000358700000074392009E and follow

the chapters that apply to Planning and Consolidation

33 Configuring the Planning and Consolidation NET Application Servers

Procedure

Modifying machineconfig Files

To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock

occurrences that would cause the application server to ldquosleeprdquo and not process anymore you can

modify the machineconfig file which resides in the WINDOWSMicrosoftNETFramework64

v4030319Config directory

1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to

specify whether to automatically configure settings to achieve optimal performance based on the

machine configuration You can set this attribute to True or False

For more information see httpmsdnmicrosoftcomen-uslibrary7w2sway1aspx

2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the

Planning and Consolidation application) or Machineconfig (for all applications including

Planning and Consolidation) to ensure the validationKey and decryptionKey keys have the same

value on all application servers This way when the authentication cookie is checked the

authentication ticket used on one server can still be valid on another server

For more information and sample Visual Basic code for generating random key values see http

msdnmicrosoftcomen-uslibraryms998288aspx

3 After Installing Planning and Consolidation Servers

33 Configuring the Planning and Consolidation NET Application Servers

2012-06-13 CUSTOMER 2954

paght000007_webfarmdeploymentconsiderations and httpmsdnmicrosoftcomen-us

libraryms998310aspx

34 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 30]

2 Configure custom ODBC logging for the default Web site For details of how to configure custom

logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page

31]

3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC Data

Source [page 32]

4 Modify the default access rights to the Management Console By default users in Active Directory

can access the Management Console with whatever rights they have been granted on the server

For information about removing default access and creating a group that can access the console

see Removing Default Access to the Console [page 32]

5 Add authorized users or groups to the group that can access the Management Console We

recommend that you only grant Management Console access to system administrators Planning

and Consolidation users should not have any access For more information see Management Console

Access Control [page 33]

6 Configure the use of client certificates for authentication See Using Client Certificates [page 34]

341 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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3054 CUSTOMER 2012-06-13

NOTE

Without these updates the Management Console does work but some functionality (specifically

User Activity and Service Status) does not work as expected

Should you need to uninstall Planning and Consolidation we recommend that you reset the

Active Log Format field in IIS to W3C Extended Log File Format

342 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 ApplicationHostconfig set the property customLogPluginClsid to the value FF16065B-

DE82-11CF-BC0A-00AA006111E0 Set the logFormat to Custom You can find this in the ltlogFilegt

node in ApplicationHostconfig as shown here

ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0

logFormat=Custom gt

Use the following AppCmds to configure IIS to use ODBC logging for the default Web site

appcmd site set sitenameDefault Web Site

logFilecustomLogPluginClsidFF16065B-DE82-11CF-BC0A-00AA006111E0

appcmd site set sitenameDefault Web Site logFilelogFormatCustom

Configuring ODBC Logging Parameters in ApplicationHostconfig

Configure ApplicationHostconfig to contain the database table information as set up in the Microsoft

Support article specified in the Prerequisites section Configure these settings in the ltodbcLogginggt

node under ltsystemwebServergt

EXAMPLE

ltlocation path=Default Web Sitegt

ltsystemwebServergt

ltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog

userName=Username password=mypassword gt

ltsystemwebServergt

ltlocationgt

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3154

Use the following AppCmds to configure these attributes for the default Web site

appcmd set config Default Web Site sectionodbcLogging

dataSourceBPC_ManagementDSN commitappHost

appcmd set config Default Web Site sectionodbcLogging tableNameBPCLog

commitappHost

appcmd set config Default Web Site sectionodbcLogging userNameUsername

commitappHost

appcmd set config Default Web Site sectionodbcLogging passwordmypassword

commitappHost

NOTE

You cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must

use the SQL Server ODBC driver For more information see the Microsoft Knowledge Base article

931202 The requirements for using the ODBC logging feature in IIS

343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2

ProcedureThis procedure describes how to set up an ODBC data source for the Management Console in Windows

Server 2008 or Windows Server 2008 R2

Proceed as follows

1 Open ODBC Connection Manager

2 On the System DSN tab page add a new DSN

Choose Add

Choose SQL Server as the driver

Choose Finish

3 In the Name and Description fields enter BPC_ManagementDSN

4 In the Server field enter the name of your SQL Server Choose Next

5 Leave the default settings and choose Next

6 Choose the Change the default database to field and enter AppServer Choose Next

7 Leave default settings and choose Next

8 Choose OK

344 Removing Default Access to the Console

NOTE

If you have chosen SAP BusinessObjects User Management System in the installation screen you

do not need to remove or configure access because the Management Console service always runs

with the System Admin ID account which is a member of the Administrators group

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3254 CUSTOMER 2012-06-13

ProcedureTo remove default access to the Management Console and create a group that does have access to the

console use the procedure described below

NOTE

Create your Management Console administrative group either on the server that hosts the

Management Console or in the Active Directory

1 In the context menu of the servers My Computer icon choose Manage

2 In the Computer Management dialog box choose Local Users and Groups Groups

NOTE

Alternatively you can perform analogous steps in Active Directory

3 In the 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

NOTE

This step is a necessary precursor to the completion of this procedure

10 In the Security dialog box click Copy to ensure that the System group retains its privileges

11 Remove access to the Management Console from all groups that should not have it

12 Choose Authentication in the center pane then disable Windows authentication

ResultUsers who have not been granted access to the Management Console can still open the Management

Console Web page but it contains no data or menu options This does not affect the access that a user

would otherwise have to Planning and Consolidation

345 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 32] Their rights in

Active Directory determine what they can access in the Console

By default any member of the Administrators Active Directory group on the application server or

domain has full access to all of the features of the Console except the Planning and Consolidation

logging area Access to Planning and Consolidation logging is controlled within the Planning and

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3354

Consolidation Administration Client task security The user must be granted View system logs task

privileges For more information see the SAP Library Planning and Consolidation Administrators Guide in

httpservicesapcominstguidesepm-bpc 100 version for the Microsoft platform

Your IT policy determines whether you grant access by group or user You may wish to create several

levels of Console users (read-only users for example) in your environment

To grant or limit access to users or groups you can add or remove the following privileges from the

areas described in this table

Privilege Rights Management Area

Task Manager and Kill Process Administrators group on application server or domain

Performance Monitor Counters Administrators group on application server or domain Power Users group on application server or domain Performance Monitor Users group on application server

Microsoft Analysis Services performance monitoring

Administrators group on application server or domain

Microsoft SQL Server Monitoring (performance counters and statistics)

Administrators group on application server or domain

346 Using Client Certificates

To enable the use of client certificates in Planning and Consolidation you must follow several manual

steps

NOTE

Planning 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 httptechnetmicrosoftcomen-us

librarycc753810aspx

For more information about configuring the client certificate mapping authentication see http

technetmicrosoftcomen-uslibrarycc732996(WS10)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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3454 CUSTOMER 2012-06-13

This option allows you to use a client certificate or username and password (Basic

authentication) to connect to Planning and Consolidation

2 Enable anonymous authentication

1 In the IIS Manager expand the node of the Planning and Consolidation web site

2 Select the ManagementConsole directory (ltWebsitegtManagementConsole) to open the

ManagementConsole home page

3 Double-click Authentication and enable Anonymous Authentication

4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way

as in step 3

5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the same

way as in step 3

3 Change the web configuration settings

1 Open the ltPC_MSgtWebsrvrWebBPCwebconfig file

2 Find the text clientCredentialType=Windows

3 Change value of clientCredentialType to None (clientCredentialType=None)

4 Open the PC_MSWebsrvrWebPOASBCwebconfig file Repeat steps 2 and 3

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3554

This page is left blank for documents that are printed on both sides

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

The installation of the Planning and Consolidation Administration Client allows administrators to

build and maintain Planning and Consolidation environments and models and administer security

All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions

add-in for Microsoft Office for more information see the SAP BusinessObjects EPM solutions add-in for

Microsoft Office help

NOTE

You must update the Administration Client to the same version as the server

If your PC is on a different domain than your server you must set the Internet Explorer

Security Zone value of the Planning and Consolidation client to prompt for user name and

password Otherwise the Planning and Consolidation Start Page does not display

41 Installing the Administration Client

Prerequisites

NOTE

For a definitive list of system requirements see the Product Availability Matrix on SAP Service

Marketplace at httpservicesapcompam Search on Planning and Consolidation

The following list describes the minimum software requirements

Microsoft Internet Explorer 70 or 80

Microsoft Office 2007 or 2010

NET Framework 20 or higher (install any required NET Framework Hotfixes by referring to

httpsupportmicrosoftcomkb)

Pentium IV (1 GHz CPU)

512 MB RAM

100 MB of free hard disk space in the My Documents folder

20 MB of free hard disk space for the installed Administration files

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

41 Installing the Administration Client

2012-06-13 CUSTOMER 3754

NOTE

We recommend that you install all of the latest Microsoft Windows hotfixes prior to installing

the Administration client For information about which hotfixes to install see http

updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us

ProcedureThe following procedure describes how to install the Administration Client on to an administratorrsquos

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 AddRemove Programs in the Windows Control Panel

3 Point your browser to the Planning and Consolidation Web at httpltPC_serverportgtsap

bpcweb

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

42 Installing the EPM Add-in

The Planning and Consolidation installation media does not contain the EPM addin setup program

You must download the most recent version of the full setup (EPM Add-inexe) from the Service

Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPC

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

43 Using the Client Auto Update Program

If Planning and Consolidation version 100 or later is installed you can use the Client Auto Update

program to set up the server so that it determines if an upgrade for a connecting Administration client

is necessary

The following describes the use of the auto update program for the Administration Client and the EPM

add-in

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

42 Installing the EPM Add-in

3854 CUSTOMER 2012-06-13

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 37]

To use the Client Auto Update program for the Administration Client proceed as follows

1 From the Server Manager select Options Client Options

2 Select Admin Update

3 If users without administrator rights on their machines use the auto update enter an administrator

ID and password in the Admin ID and Admin password fields respectively The Admin ID should be a

member of the local administrators group on all the computers running the auto update This

setting is not needed if all users have administrator rights on their machines

4 Select Update

For the EPM Add-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 Optionshellip 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 Market Place (SMP) at httpservicesapcom

All support packages and patches are available from the SMP as a zip file

EPMEXCLCLNTltSPLgtzip is for a support package

EPMEXCLCLNTltSPLgtPltPLgtzip 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 ltSP versiongtmsp

EPM Addin Support Package ltSP versiongtxml

For a patch these files are

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

2012-06-13 CUSTOMER 3954

EPM Addin Patch ltpatch numbergtmsp

EPM Addin Patch ltpatch numbergtxml

2 Unzip the zip file and extract the two files to the application server folder (WebsrvrWebBPC

Installation)

3 From the Server Manager select Options Client Options

The system lists the available packages Select the package that you want to use for the autoupdate

You can set a different update policy for each package listed

EXAMPLE

The following table illustrates some possible situations assuming that you have installed the

first full version (V1)

Available maintenance packages

V2-user updateV3-force updateV4-force updateV5-user update

V5-user update V5-user updateV6-auto updateV7-force update

Minimum Required Version

V4 V4 V7

Notification A prompt tells the user to install maintenance package V4 using the Forced Update behavior

If User Update is enabled the prompt informs the user that maintenance package V5 is available

A prompt tells the user to install maintenance package V7 using the Forced Update behavior

New Version V4 V4 or V5 V7

If you change the update policy for any package click Update to complete the change

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

4054 CUSTOMER 2012-06-13

5 Connection Issues

You may experience connection problems with ports the proxy server or programs and settings that

interact with these components If you have any issues related to connection review the following

recommendations and troubleshooting tips

51 Checking for Open Ports

You must ensure that all required ports are open for inboundoutbound 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 431181836 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

NOTE

You can use the following site to scan for the normal ports It allows you to manually enter a port

number to test

httpwwwmyserverorgportsniffasp

You can change the name of a port

52 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 Explorer Tools Internet Options Connections LAN Settings ) or at the server level

Enabling content filtering on the proxy server or firewall may cause connection problems

If external users are having trouble connecting to the server make sure the proxy server connects

using a fully qualified domain name Fully qualified domain names typically resolve both internal

and external IP addresses

Each secure Planning and Consolidation server name must be identified on the proxy server

Proxy servers may or may not require authentication which could conflict with Planning and

Consolidation authentication Do not use authentication on the proxy server The system

5 Connection Issues

51 Checking for Open Ports

2012-06-13 CUSTOMER 4154

synchronizes the user name and password on the remote server with the local user name and

password

NOTE

For more information about setting up an ISA proxy server contact SAP Support to request a

copy of Setting up ISA Proxy Server White Paper

Internet Explorer Settings 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

5 Connection Issues

52 Proxy Server and Firewall Issues

4254 CUSTOMER 2012-06-13

6 Installing Planning and Consolidation with Two Active Directory Domains

To set up a Planning and Consolidation 10 application server in a hosted environment and use your

own domain users follow this procedure In general you install Planning and Consolidation on the

host domain use the host domain account and assign it to the Planning and Consolidation users

SysAdmin Admin and Users Then you accept one way trust (the host domain trusts your domain)

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

6 Installing Planning and Consolidation with Two Active Directory Domains

2012-06-13 CUSTOMER 4354

This page is left blank for documents that are printed on both sides

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

This section describes best practices and instructions for installing Planning and Consolidation in a

Terminal Services or Citrix Server deployment

71 Terminal Services Home Directories

We recommend using Terminal Server home directories rather than using the userrsquos 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

72 System Requirements

The Citrix server should be one of the following systems

XenApp 5 Enterprise

XenApp 5 Platinum

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 37])

73 Installing Planning and Consolidation

Prerequisites

The server installation files have been downloaded from SAP Service Marketplace and installed

Procedure

The following steps outline how to install the Planning and Consolidation clients in a Terminal Services

(TS) or Citrix Server deployment

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

71 Terminal Services Home Directories

2012-06-13 CUSTOMER 4554

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 userinstall

4 Open a browser and connect to the URL httpltPC_serverportgtsapbpcweb

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 userexecute 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 Iexploreexe http(s)

ltServerNamegt-NetBIOS or FQDNsapbpcweb

To publish Planning and Consolidation Administration CProgram FilesPC_MS

BPCAdminMainexe

74 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 userrsquos desktop) must be moved to the All UsersDesktop folder

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

74 Creating a Shortcut to the Launch Page

4654 CUSTOMER 2012-06-13

8 Installing SSIS Custom Tasks

This section provides background information and instructions for installing SQL Server Integration

Services (SSIS) for SQL Server 2008 and SQL Server 2012

The Planning and Consolidation Data Manager component supports and uses SSIS Since SQL Server

2008 and SQL Server 2012 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

81 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 Filelistxml 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

OSoftSetupexe ‒ 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 or OSoftSSIS2012_Client on the client machine followed by the SQL Server

version If you want to use SQL 2008 Tasks under the SQL 2012 environment you must install

OSoftSSIS2008_Client on the application server For detailed information see SAP Note 1707410

You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package by extracting

OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPC

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 or

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4754

OSoftSSIS2012_Client for creating a COM+ application For more information see Before You Modify

the SSIS Packages [page 50] and Setup of a COM+ Application on the Application Server [page 51]

Bin folder

This folder contains the following components

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCCachedll Planning and Consolidation Cache file

BPCDataFlowPackagedll or BPCDataFlowPackage2012dll

BPCDMdll

BPCDMTaskMaindll COM+ component

BPCFilePreviewdll

BPCGacUtil_20exe System File

BPCGacUtil_40exe System File

BPCImpersonatordll Planning and Consolidation Impersonator

BPCLogicdll

BPCScriptdll

BPCServerZipdll

BPCServiceResdll

BPCTransferMembersdll

BPCWriteBackdll

InteropDTSdll

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

4854 CUSTOMER 2012-06-13

Name Remark

OSoftAdminServerdll

OSoftAuditdll

OSoftComLibServerdll

OSoftCommonResQrydll

OSoftConfigurationdll

OSoftCustomXMLSvrdll

OSoftDatabaseADMINdll

OSoftDatabaseSYSADMINdll

OSoftDatabaseSYSADMINDMdll

OSoftDatabaseUSERdll

OSoftDMDTSXExecutedll or OSoftDMDTSXExecute2012dll

OSoftDMTaskFormdll

OSoftDMTaskMaindll

OSoftDMToolsdll

OSoftFileManagedll

OSoftLoggingdll

OSoftLogWriterdll

OSoftMetaDatadll

OSoftSQEdll

OSoftSystemConfigdll

OutlookSoftconfig Configuration file to connect DB server

XceedCompressiondll XceedZip file

XceedCompressionFormatsdll XceedZip file

XceedFileSystemdll XceedZip file

XceedZipdll XceedZip file

Config folder

This folder has FileListxml 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 FileListxml 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

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4954

OSoftSetupexe

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

NOTE

If you installed the OSoftSSIS2008_Client or OSoftSSIS2012_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

Resources Folder

This folder contains the BPCServicesdll and BPCServiceUIdll files which contain resource text

Only English resources are included for the SSIS custom tasks

82 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

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008 and 2012 respectively

8 Installing SSIS Custom Tasks

82 Before You Modify the SSIS Packages

5054 CUSTOMER 2012-06-13

Name Remark

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012 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

lthellipgtOSoftSSIS2008_Clientbin or lthellipgtOSoftSSIS2012_Clientbin

On the Planning and Consolidation application server

ltdrivegtWebsrvrbin

2 Paste these files into the folder 100DTSTasks for SQL Server 2008 or into 110DTSTasks for

SQL Server 2012 For example if you install your SQL 2008 server or R2 on CProgram Files

Microsoft SQL Server paste all files into the CProgram Files (x86)Microsoft SQL Server

100DTSTasks folder

In Integration Services set the property Run64BitRunTime to True

83 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 or OSoftSSIS2012_Client on the

application server

8 Installing SSIS Custom Tasks

83 Setup of a COM+ Application on the Application Server

2012-06-13 CUSTOMER 5154

Typographic Conventions

Example Description

ltgt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example Enter your ltUser Namegt

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 httpwwwsapcom

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

5254 CUSTOMER 2012-06-13

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

  • SAP BusinessObjects Planning and Consolidation 100
    • Table of Contents
    • 1 Introduction
      • 11 SAP Notes for the Installation
      • 12 Naming Conventions
        • 2 Installing Planning and Consolidation Servers
          • 21 Basic Steps
          • 22 Prerequisites
          • 23 Before Starting the Planning and Consolidation Server Installation
          • 24 Logging on to Servers
          • 25 Service-level Accounts
          • 26 Standard and Advanced Settings
          • 27 Installing the Prerequisites
            • 271 Installing the Prerequisites ndash Basic Steps
            • 272 Installing the Operating System
            • 273 Installing the SQL Server
            • 274 Installing Analysis Services
            • 275 Installing the Anti-Cross Site Scripting Library
              • 28 Installing on a Single Server
              • 29 Installing the Server in a Multiserver Configuration
                • 3 After Installing Planning and Consolidation Servers
                  • 31 Post-Installation Steps
                  • 32 Connecting to Solution Manager Diagnostics
                  • 33 Configuring the Planning and Consolidation NET Application Servers
                  • 34 Post-Installation Optional Configuration Steps
                    • 341 Enabling the Management Console
                    • 342 Setting Up ODBC Logging in IIS for the Default Web Site
                    • 343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2
                    • 344 Removing Default Access to the Console
                    • 345 Management Console Access Control
                    • 346 Using Client Certificates
                        • 4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office
                          • 41 Installing the Administration Client
                          • 42 Installing the EPM Add-in
                          • 43 Using the Client Auto Update Program
                            • 5 Connection Issues
                              • 51 Checking for Open Ports
                              • 52 Proxy Server and Firewall Issues
                                • 6 Installing Planning and Consolidation with Two Active Directory Domains
                                • 7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
                                  • 71 Terminal Services Home Directories
                                  • 72 System Requirements
                                  • 73 Installing Planning and Consolidation
                                  • 74 Creating a Shortcut to the Launch Page
                                    • 8 Installing SSIS Custom Tasks
                                      • 81 Composition of SSIS Custom Task Installation
                                      • 82 Before You Modify the SSIS Packages
                                      • 83 Setup of a COM+ Application on the Application Server
                                          • Copyright and trademarks
Page 25: Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

2 Log on to the server with a local server user ID or domain user ID For more information see Logging

on to servers [page 14]

3 Make sure all prerequisite software is installed on the server For more information see Installing

the Prerequisites [page 17]

4 Obtain SAP Planning and Consolidation from the Downloads SAP Installations amp Upgrades area of

SAP Service Marketplace then extract the files and run StartUpexe

5 From the Server Install screen select Install the Planning and Consolidation server

6 From the Welcome screen choose Next

7 From the License Agreement page choose I accept the terms of the license agreement then choose Next

8 From the Installation Method page accept the default Single machine enter a system ID for the system

landscape directory (SLD) and choose Next

NOTE

Entering a system ID of the SLD is only required if you have a SAP Solution Manager license

If you do not have a SAP Solution Manager license you can leave this field empty

9 From the Authentication Method page choose the desired authentication method and choose Next

10 If you have chosen SAP BusinessObjects User Management System in the previous screen on the CMS

Authentication page enter the information required to log on to CMS as an administrator

The following information is required

Field Description

System name CMS system name (server nameport number) for example CMSServer6400

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

11 After entering the CMS administrator authentication details choose Next

12 From the Service type accounts page enter service-level account user IDs and passwords See Service-

Level Accounts [page 15]

13 After defining the IDs and passwords choose Next

14 From the Server Information page (see Standard and Advanced Settings [page 16]) do one of the following

Review the standard settings and choose Next

To set advanced settings choose the Advanced Settings button Enter the desired information

and choose Next

2 Installing Planning and Consolidation Servers

28 Installing on a Single Server

2012-06-13 CUSTOMER 2554

15 Specify the location and name of AntiXssLibrarydll See Installing the Anti-Cross Site Scripting Library [page

24]

Choose Next

16 Select destination folders for Programs and Data The Data files include Webfolders and FileDB

(published reports) and should be installed on a separate drive in a production environment This

recommendation reduces the hard disk IO time and helps to speed up SQL commands

Accept the defaults or make your selections then choose Next

17 Select the default values for the Web client The values are used to determine the default language

and region for the Web client when you connect to it You can change the values in the Planning

and Consolidation Server Manager

18 The installation process takes a few moments When it is complete choose Exit

19 A prompt is displayed to restart your computer Select OK to restart

20 Perform the steps in After Installing Planning and Consolidation Servers [page 27]

29 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 24]) with the following

exceptions

On the Installation Method page do not accept the default instead choose Network Load Balancing

environment With this option there is an additional choice to Include sample environment (required on only

one of the application servers) This is because when you install the application server it connects to the

database server and creates the sample environment (EnvironmentShell) Installing the sample

environment is required on only one application server and you may choose which one

In the Virtual Name field enter the virtual IP address virtual name in the default properties

2 Installing Planning and Consolidation Servers

29 Installing the Server in a Multiserver Configuration

2654 CUSTOMER 2012-06-13

3 After Installing Planning and Consolidation Servers

31 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 28]

2 Configure the Planning and Consolidation NET and application server to ensure that it and its

related services function properly and reliably For more information see Configuring the Planning and

Consolidation NET Application Server [page 29]

3 Optional configuration steps [page 30]

1 To ensure proper functioning of the Management Console create an SQL user and modify

the System DSN and IIS to reflect those user credentials See Enabling Management Console [page

30]

2 Configure custom ODBC logging for the default Web site For details of how to configure

custom logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web

Site [page 31]

3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC

Data Source [page 32]

4 Modify the default access rights to the Management Console By default users in Active

Directory can access the Management Console with whatever rights they have been granted

on the server For information about removing default access and creating a group that can

access the console see Removing Default Access to the Console [page 32]

5 Add authorized users or groups to the group that can access the Management Console We

recommend that you only grant Management Console access to system administrators

Planning and Consolidation users should not have any access For more information see

Management Console Access Control [page 33]

6 Configure the use of client certificates for authentication See Using Client Certificates [page

34]

4 Take the following steps to set up security

If you are defining security and application structure continue with step 5

3 After Installing Planning and Consolidation Servers

31 Post-Installation Steps

2012-06-13 CUSTOMER 2754

If you want to designate someone other than the system administrator to manage security

and application structure log on to EnvironmentShell designate a user as a Primary

Administrator

This user must have Administration ‒ Environment and Security ‒ Define User task rights

so that he or she can add and delete environments and define user security

The Primary Administrator can continue with the next step (5)

5 From the machine on which you administer Planning and Consolidation install the

Administration client See Installing the Administration Client [page 37]

6 Start Planning and Consolidation Administration from the launch page

7 Select Connection Wizard and log on to EnvironmentShell

8 Create a new environment using EnvironmentShell as the source

9 Log on to the newly created environment and set up users teams and task profiles (You must

set up task profiles since there is no access to Planning and Consolidation tasks)

10 Set up your data access profiles and add users (or teams) to one or more data access profiles (You

must complete this step since there is no access to dimensions or members)

NOTE

To allow users to request and query large amounts of data you can edit the metabasexml file located

at CWindowssystem32inetsrv Set the following parameters to the stated values

ASPBUFFERINGLIMIT = 10485760

MAXREQUESTENTITYALLOWED = 10485760

32 Connecting to Solution Manager Diagnostics

NOTE

You only need to perform the steps in this section if you have a SAP Solution Manager licence

The diagnostics functions in SAP Solution Manager allow identification analysis and resolution of

problems This procedure provides the steps required to connect Planning and Consolidation to

Solution Manager Diagnostics

Procedure

1 Install the Diagnostics Agent according to SAP Note 1234387 on all servers where application servers

are installed

NOTE

Installation files for Diagnostics Agent are available on Service Marketplace by navigating to

Support Packages and Patches mdash Entry by Application Group SAP Technology Components SAP

SOLUTION MANAGER SAP SOLUTION MANAGER 70 EHP 1 Entry by Component Agents

for managed systems DIAGNOSTICS AGENT 711

3 After Installing Planning and Consolidation Servers

32 Connecting to Solution Manager Diagnostics

2854 CUSTOMER 2012-06-13

Download the installation file based on the 64-bit Windows Server system landscape

2 To access the DBA Cockpit you must create a user account with sufficient rights on all Windows

Servers where Microsoft SQL Server is installed Do the following

1 Start Computer Management then select Action New User

2 Create a new user

3 Right-click on the user then choose Properties On the Member Of tab select Add

4 Add the group SQLServerltReleasegtSQLAgentUser$ltDomain or hostnamegt$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 httpsservicesapcom~sapidb011000358700000074392009E and follow

the chapters that apply to Planning and Consolidation

33 Configuring the Planning and Consolidation NET Application Servers

Procedure

Modifying machineconfig Files

To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock

occurrences that would cause the application server to ldquosleeprdquo and not process anymore you can

modify the machineconfig file which resides in the WINDOWSMicrosoftNETFramework64

v4030319Config directory

1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to

specify whether to automatically configure settings to achieve optimal performance based on the

machine configuration You can set this attribute to True or False

For more information see httpmsdnmicrosoftcomen-uslibrary7w2sway1aspx

2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the

Planning and Consolidation application) or Machineconfig (for all applications including

Planning and Consolidation) to ensure the validationKey and decryptionKey keys have the same

value on all application servers This way when the authentication cookie is checked the

authentication ticket used on one server can still be valid on another server

For more information and sample Visual Basic code for generating random key values see http

msdnmicrosoftcomen-uslibraryms998288aspx

3 After Installing Planning and Consolidation Servers

33 Configuring the Planning and Consolidation NET Application Servers

2012-06-13 CUSTOMER 2954

paght000007_webfarmdeploymentconsiderations and httpmsdnmicrosoftcomen-us

libraryms998310aspx

34 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 30]

2 Configure custom ODBC logging for the default Web site For details of how to configure custom

logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page

31]

3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC Data

Source [page 32]

4 Modify the default access rights to the Management Console By default users in Active Directory

can access the Management Console with whatever rights they have been granted on the server

For information about removing default access and creating a group that can access the console

see Removing Default Access to the Console [page 32]

5 Add authorized users or groups to the group that can access the Management Console We

recommend that you only grant Management Console access to system administrators Planning

and Consolidation users should not have any access For more information see Management Console

Access Control [page 33]

6 Configure the use of client certificates for authentication See Using Client Certificates [page 34]

341 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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3054 CUSTOMER 2012-06-13

NOTE

Without these updates the Management Console does work but some functionality (specifically

User Activity and Service Status) does not work as expected

Should you need to uninstall Planning and Consolidation we recommend that you reset the

Active Log Format field in IIS to W3C Extended Log File Format

342 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 ApplicationHostconfig set the property customLogPluginClsid to the value FF16065B-

DE82-11CF-BC0A-00AA006111E0 Set the logFormat to Custom You can find this in the ltlogFilegt

node in ApplicationHostconfig as shown here

ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0

logFormat=Custom gt

Use the following AppCmds to configure IIS to use ODBC logging for the default Web site

appcmd site set sitenameDefault Web Site

logFilecustomLogPluginClsidFF16065B-DE82-11CF-BC0A-00AA006111E0

appcmd site set sitenameDefault Web Site logFilelogFormatCustom

Configuring ODBC Logging Parameters in ApplicationHostconfig

Configure ApplicationHostconfig to contain the database table information as set up in the Microsoft

Support article specified in the Prerequisites section Configure these settings in the ltodbcLogginggt

node under ltsystemwebServergt

EXAMPLE

ltlocation path=Default Web Sitegt

ltsystemwebServergt

ltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog

userName=Username password=mypassword gt

ltsystemwebServergt

ltlocationgt

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3154

Use the following AppCmds to configure these attributes for the default Web site

appcmd set config Default Web Site sectionodbcLogging

dataSourceBPC_ManagementDSN commitappHost

appcmd set config Default Web Site sectionodbcLogging tableNameBPCLog

commitappHost

appcmd set config Default Web Site sectionodbcLogging userNameUsername

commitappHost

appcmd set config Default Web Site sectionodbcLogging passwordmypassword

commitappHost

NOTE

You cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must

use the SQL Server ODBC driver For more information see the Microsoft Knowledge Base article

931202 The requirements for using the ODBC logging feature in IIS

343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2

ProcedureThis procedure describes how to set up an ODBC data source for the Management Console in Windows

Server 2008 or Windows Server 2008 R2

Proceed as follows

1 Open ODBC Connection Manager

2 On the System DSN tab page add a new DSN

Choose Add

Choose SQL Server as the driver

Choose Finish

3 In the Name and Description fields enter BPC_ManagementDSN

4 In the Server field enter the name of your SQL Server Choose Next

5 Leave the default settings and choose Next

6 Choose the Change the default database to field and enter AppServer Choose Next

7 Leave default settings and choose Next

8 Choose OK

344 Removing Default Access to the Console

NOTE

If you have chosen SAP BusinessObjects User Management System in the installation screen you

do not need to remove or configure access because the Management Console service always runs

with the System Admin ID account which is a member of the Administrators group

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3254 CUSTOMER 2012-06-13

ProcedureTo remove default access to the Management Console and create a group that does have access to the

console use the procedure described below

NOTE

Create your Management Console administrative group either on the server that hosts the

Management Console or in the Active Directory

1 In the context menu of the servers My Computer icon choose Manage

2 In the Computer Management dialog box choose Local Users and Groups Groups

NOTE

Alternatively you can perform analogous steps in Active Directory

3 In the 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

NOTE

This step is a necessary precursor to the completion of this procedure

10 In the Security dialog box click Copy to ensure that the System group retains its privileges

11 Remove access to the Management Console from all groups that should not have it

12 Choose Authentication in the center pane then disable Windows authentication

ResultUsers who have not been granted access to the Management Console can still open the Management

Console Web page but it contains no data or menu options This does not affect the access that a user

would otherwise have to Planning and Consolidation

345 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 32] Their rights in

Active Directory determine what they can access in the Console

By default any member of the Administrators Active Directory group on the application server or

domain has full access to all of the features of the Console except the Planning and Consolidation

logging area Access to Planning and Consolidation logging is controlled within the Planning and

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3354

Consolidation Administration Client task security The user must be granted View system logs task

privileges For more information see the SAP Library Planning and Consolidation Administrators Guide in

httpservicesapcominstguidesepm-bpc 100 version for the Microsoft platform

Your IT policy determines whether you grant access by group or user You may wish to create several

levels of Console users (read-only users for example) in your environment

To grant or limit access to users or groups you can add or remove the following privileges from the

areas described in this table

Privilege Rights Management Area

Task Manager and Kill Process Administrators group on application server or domain

Performance Monitor Counters Administrators group on application server or domain Power Users group on application server or domain Performance Monitor Users group on application server

Microsoft Analysis Services performance monitoring

Administrators group on application server or domain

Microsoft SQL Server Monitoring (performance counters and statistics)

Administrators group on application server or domain

346 Using Client Certificates

To enable the use of client certificates in Planning and Consolidation you must follow several manual

steps

NOTE

Planning 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 httptechnetmicrosoftcomen-us

librarycc753810aspx

For more information about configuring the client certificate mapping authentication see http

technetmicrosoftcomen-uslibrarycc732996(WS10)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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3454 CUSTOMER 2012-06-13

This option allows you to use a client certificate or username and password (Basic

authentication) to connect to Planning and Consolidation

2 Enable anonymous authentication

1 In the IIS Manager expand the node of the Planning and Consolidation web site

2 Select the ManagementConsole directory (ltWebsitegtManagementConsole) to open the

ManagementConsole home page

3 Double-click Authentication and enable Anonymous Authentication

4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way

as in step 3

5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the same

way as in step 3

3 Change the web configuration settings

1 Open the ltPC_MSgtWebsrvrWebBPCwebconfig file

2 Find the text clientCredentialType=Windows

3 Change value of clientCredentialType to None (clientCredentialType=None)

4 Open the PC_MSWebsrvrWebPOASBCwebconfig file Repeat steps 2 and 3

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3554

This page is left blank for documents that are printed on both sides

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

The installation of the Planning and Consolidation Administration Client allows administrators to

build and maintain Planning and Consolidation environments and models and administer security

All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions

add-in for Microsoft Office for more information see the SAP BusinessObjects EPM solutions add-in for

Microsoft Office help

NOTE

You must update the Administration Client to the same version as the server

If your PC is on a different domain than your server you must set the Internet Explorer

Security Zone value of the Planning and Consolidation client to prompt for user name and

password Otherwise the Planning and Consolidation Start Page does not display

41 Installing the Administration Client

Prerequisites

NOTE

For a definitive list of system requirements see the Product Availability Matrix on SAP Service

Marketplace at httpservicesapcompam Search on Planning and Consolidation

The following list describes the minimum software requirements

Microsoft Internet Explorer 70 or 80

Microsoft Office 2007 or 2010

NET Framework 20 or higher (install any required NET Framework Hotfixes by referring to

httpsupportmicrosoftcomkb)

Pentium IV (1 GHz CPU)

512 MB RAM

100 MB of free hard disk space in the My Documents folder

20 MB of free hard disk space for the installed Administration files

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

41 Installing the Administration Client

2012-06-13 CUSTOMER 3754

NOTE

We recommend that you install all of the latest Microsoft Windows hotfixes prior to installing

the Administration client For information about which hotfixes to install see http

updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us

ProcedureThe following procedure describes how to install the Administration Client on to an administratorrsquos

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 AddRemove Programs in the Windows Control Panel

3 Point your browser to the Planning and Consolidation Web at httpltPC_serverportgtsap

bpcweb

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

42 Installing the EPM Add-in

The Planning and Consolidation installation media does not contain the EPM addin setup program

You must download the most recent version of the full setup (EPM Add-inexe) from the Service

Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPC

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

43 Using the Client Auto Update Program

If Planning and Consolidation version 100 or later is installed you can use the Client Auto Update

program to set up the server so that it determines if an upgrade for a connecting Administration client

is necessary

The following describes the use of the auto update program for the Administration Client and the EPM

add-in

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

42 Installing the EPM Add-in

3854 CUSTOMER 2012-06-13

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 37]

To use the Client Auto Update program for the Administration Client proceed as follows

1 From the Server Manager select Options Client Options

2 Select Admin Update

3 If users without administrator rights on their machines use the auto update enter an administrator

ID and password in the Admin ID and Admin password fields respectively The Admin ID should be a

member of the local administrators group on all the computers running the auto update This

setting is not needed if all users have administrator rights on their machines

4 Select Update

For the EPM Add-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 Optionshellip 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 Market Place (SMP) at httpservicesapcom

All support packages and patches are available from the SMP as a zip file

EPMEXCLCLNTltSPLgtzip is for a support package

EPMEXCLCLNTltSPLgtPltPLgtzip 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 ltSP versiongtmsp

EPM Addin Support Package ltSP versiongtxml

For a patch these files are

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

2012-06-13 CUSTOMER 3954

EPM Addin Patch ltpatch numbergtmsp

EPM Addin Patch ltpatch numbergtxml

2 Unzip the zip file and extract the two files to the application server folder (WebsrvrWebBPC

Installation)

3 From the Server Manager select Options Client Options

The system lists the available packages Select the package that you want to use for the autoupdate

You can set a different update policy for each package listed

EXAMPLE

The following table illustrates some possible situations assuming that you have installed the

first full version (V1)

Available maintenance packages

V2-user updateV3-force updateV4-force updateV5-user update

V5-user update V5-user updateV6-auto updateV7-force update

Minimum Required Version

V4 V4 V7

Notification A prompt tells the user to install maintenance package V4 using the Forced Update behavior

If User Update is enabled the prompt informs the user that maintenance package V5 is available

A prompt tells the user to install maintenance package V7 using the Forced Update behavior

New Version V4 V4 or V5 V7

If you change the update policy for any package click Update to complete the change

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

4054 CUSTOMER 2012-06-13

5 Connection Issues

You may experience connection problems with ports the proxy server or programs and settings that

interact with these components If you have any issues related to connection review the following

recommendations and troubleshooting tips

51 Checking for Open Ports

You must ensure that all required ports are open for inboundoutbound 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 431181836 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

NOTE

You can use the following site to scan for the normal ports It allows you to manually enter a port

number to test

httpwwwmyserverorgportsniffasp

You can change the name of a port

52 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 Explorer Tools Internet Options Connections LAN Settings ) or at the server level

Enabling content filtering on the proxy server or firewall may cause connection problems

If external users are having trouble connecting to the server make sure the proxy server connects

using a fully qualified domain name Fully qualified domain names typically resolve both internal

and external IP addresses

Each secure Planning and Consolidation server name must be identified on the proxy server

Proxy servers may or may not require authentication which could conflict with Planning and

Consolidation authentication Do not use authentication on the proxy server The system

5 Connection Issues

51 Checking for Open Ports

2012-06-13 CUSTOMER 4154

synchronizes the user name and password on the remote server with the local user name and

password

NOTE

For more information about setting up an ISA proxy server contact SAP Support to request a

copy of Setting up ISA Proxy Server White Paper

Internet Explorer Settings 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

5 Connection Issues

52 Proxy Server and Firewall Issues

4254 CUSTOMER 2012-06-13

6 Installing Planning and Consolidation with Two Active Directory Domains

To set up a Planning and Consolidation 10 application server in a hosted environment and use your

own domain users follow this procedure In general you install Planning and Consolidation on the

host domain use the host domain account and assign it to the Planning and Consolidation users

SysAdmin Admin and Users Then you accept one way trust (the host domain trusts your domain)

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

6 Installing Planning and Consolidation with Two Active Directory Domains

2012-06-13 CUSTOMER 4354

This page is left blank for documents that are printed on both sides

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

This section describes best practices and instructions for installing Planning and Consolidation in a

Terminal Services or Citrix Server deployment

71 Terminal Services Home Directories

We recommend using Terminal Server home directories rather than using the userrsquos 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

72 System Requirements

The Citrix server should be one of the following systems

XenApp 5 Enterprise

XenApp 5 Platinum

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 37])

73 Installing Planning and Consolidation

Prerequisites

The server installation files have been downloaded from SAP Service Marketplace and installed

Procedure

The following steps outline how to install the Planning and Consolidation clients in a Terminal Services

(TS) or Citrix Server deployment

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

71 Terminal Services Home Directories

2012-06-13 CUSTOMER 4554

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 userinstall

4 Open a browser and connect to the URL httpltPC_serverportgtsapbpcweb

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 userexecute 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 Iexploreexe http(s)

ltServerNamegt-NetBIOS or FQDNsapbpcweb

To publish Planning and Consolidation Administration CProgram FilesPC_MS

BPCAdminMainexe

74 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 userrsquos desktop) must be moved to the All UsersDesktop folder

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

74 Creating a Shortcut to the Launch Page

4654 CUSTOMER 2012-06-13

8 Installing SSIS Custom Tasks

This section provides background information and instructions for installing SQL Server Integration

Services (SSIS) for SQL Server 2008 and SQL Server 2012

The Planning and Consolidation Data Manager component supports and uses SSIS Since SQL Server

2008 and SQL Server 2012 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

81 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 Filelistxml 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

OSoftSetupexe ‒ 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 or OSoftSSIS2012_Client on the client machine followed by the SQL Server

version If you want to use SQL 2008 Tasks under the SQL 2012 environment you must install

OSoftSSIS2008_Client on the application server For detailed information see SAP Note 1707410

You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package by extracting

OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPC

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 or

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4754

OSoftSSIS2012_Client for creating a COM+ application For more information see Before You Modify

the SSIS Packages [page 50] and Setup of a COM+ Application on the Application Server [page 51]

Bin folder

This folder contains the following components

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCCachedll Planning and Consolidation Cache file

BPCDataFlowPackagedll or BPCDataFlowPackage2012dll

BPCDMdll

BPCDMTaskMaindll COM+ component

BPCFilePreviewdll

BPCGacUtil_20exe System File

BPCGacUtil_40exe System File

BPCImpersonatordll Planning and Consolidation Impersonator

BPCLogicdll

BPCScriptdll

BPCServerZipdll

BPCServiceResdll

BPCTransferMembersdll

BPCWriteBackdll

InteropDTSdll

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

4854 CUSTOMER 2012-06-13

Name Remark

OSoftAdminServerdll

OSoftAuditdll

OSoftComLibServerdll

OSoftCommonResQrydll

OSoftConfigurationdll

OSoftCustomXMLSvrdll

OSoftDatabaseADMINdll

OSoftDatabaseSYSADMINdll

OSoftDatabaseSYSADMINDMdll

OSoftDatabaseUSERdll

OSoftDMDTSXExecutedll or OSoftDMDTSXExecute2012dll

OSoftDMTaskFormdll

OSoftDMTaskMaindll

OSoftDMToolsdll

OSoftFileManagedll

OSoftLoggingdll

OSoftLogWriterdll

OSoftMetaDatadll

OSoftSQEdll

OSoftSystemConfigdll

OutlookSoftconfig Configuration file to connect DB server

XceedCompressiondll XceedZip file

XceedCompressionFormatsdll XceedZip file

XceedFileSystemdll XceedZip file

XceedZipdll XceedZip file

Config folder

This folder has FileListxml 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 FileListxml 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

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4954

OSoftSetupexe

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

NOTE

If you installed the OSoftSSIS2008_Client or OSoftSSIS2012_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

Resources Folder

This folder contains the BPCServicesdll and BPCServiceUIdll files which contain resource text

Only English resources are included for the SSIS custom tasks

82 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

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008 and 2012 respectively

8 Installing SSIS Custom Tasks

82 Before You Modify the SSIS Packages

5054 CUSTOMER 2012-06-13

Name Remark

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012 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

lthellipgtOSoftSSIS2008_Clientbin or lthellipgtOSoftSSIS2012_Clientbin

On the Planning and Consolidation application server

ltdrivegtWebsrvrbin

2 Paste these files into the folder 100DTSTasks for SQL Server 2008 or into 110DTSTasks for

SQL Server 2012 For example if you install your SQL 2008 server or R2 on CProgram Files

Microsoft SQL Server paste all files into the CProgram Files (x86)Microsoft SQL Server

100DTSTasks folder

In Integration Services set the property Run64BitRunTime to True

83 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 or OSoftSSIS2012_Client on the

application server

8 Installing SSIS Custom Tasks

83 Setup of a COM+ Application on the Application Server

2012-06-13 CUSTOMER 5154

Typographic Conventions

Example Description

ltgt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example Enter your ltUser Namegt

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 httpwwwsapcom

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

5254 CUSTOMER 2012-06-13

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

  • SAP BusinessObjects Planning and Consolidation 100
    • Table of Contents
    • 1 Introduction
      • 11 SAP Notes for the Installation
      • 12 Naming Conventions
        • 2 Installing Planning and Consolidation Servers
          • 21 Basic Steps
          • 22 Prerequisites
          • 23 Before Starting the Planning and Consolidation Server Installation
          • 24 Logging on to Servers
          • 25 Service-level Accounts
          • 26 Standard and Advanced Settings
          • 27 Installing the Prerequisites
            • 271 Installing the Prerequisites ndash Basic Steps
            • 272 Installing the Operating System
            • 273 Installing the SQL Server
            • 274 Installing Analysis Services
            • 275 Installing the Anti-Cross Site Scripting Library
              • 28 Installing on a Single Server
              • 29 Installing the Server in a Multiserver Configuration
                • 3 After Installing Planning and Consolidation Servers
                  • 31 Post-Installation Steps
                  • 32 Connecting to Solution Manager Diagnostics
                  • 33 Configuring the Planning and Consolidation NET Application Servers
                  • 34 Post-Installation Optional Configuration Steps
                    • 341 Enabling the Management Console
                    • 342 Setting Up ODBC Logging in IIS for the Default Web Site
                    • 343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2
                    • 344 Removing Default Access to the Console
                    • 345 Management Console Access Control
                    • 346 Using Client Certificates
                        • 4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office
                          • 41 Installing the Administration Client
                          • 42 Installing the EPM Add-in
                          • 43 Using the Client Auto Update Program
                            • 5 Connection Issues
                              • 51 Checking for Open Ports
                              • 52 Proxy Server and Firewall Issues
                                • 6 Installing Planning and Consolidation with Two Active Directory Domains
                                • 7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
                                  • 71 Terminal Services Home Directories
                                  • 72 System Requirements
                                  • 73 Installing Planning and Consolidation
                                  • 74 Creating a Shortcut to the Launch Page
                                    • 8 Installing SSIS Custom Tasks
                                      • 81 Composition of SSIS Custom Task Installation
                                      • 82 Before You Modify the SSIS Packages
                                      • 83 Setup of a COM+ Application on the Application Server
                                          • Copyright and trademarks
Page 26: Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

15 Specify the location and name of AntiXssLibrarydll See Installing the Anti-Cross Site Scripting Library [page

24]

Choose Next

16 Select destination folders for Programs and Data The Data files include Webfolders and FileDB

(published reports) and should be installed on a separate drive in a production environment This

recommendation reduces the hard disk IO time and helps to speed up SQL commands

Accept the defaults or make your selections then choose Next

17 Select the default values for the Web client The values are used to determine the default language

and region for the Web client when you connect to it You can change the values in the Planning

and Consolidation Server Manager

18 The installation process takes a few moments When it is complete choose Exit

19 A prompt is displayed to restart your computer Select OK to restart

20 Perform the steps in After Installing Planning and Consolidation Servers [page 27]

29 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 24]) with the following

exceptions

On the Installation Method page do not accept the default instead choose Network Load Balancing

environment With this option there is an additional choice to Include sample environment (required on only

one of the application servers) This is because when you install the application server it connects to the

database server and creates the sample environment (EnvironmentShell) Installing the sample

environment is required on only one application server and you may choose which one

In the Virtual Name field enter the virtual IP address virtual name in the default properties

2 Installing Planning and Consolidation Servers

29 Installing the Server in a Multiserver Configuration

2654 CUSTOMER 2012-06-13

3 After Installing Planning and Consolidation Servers

31 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 28]

2 Configure the Planning and Consolidation NET and application server to ensure that it and its

related services function properly and reliably For more information see Configuring the Planning and

Consolidation NET Application Server [page 29]

3 Optional configuration steps [page 30]

1 To ensure proper functioning of the Management Console create an SQL user and modify

the System DSN and IIS to reflect those user credentials See Enabling Management Console [page

30]

2 Configure custom ODBC logging for the default Web site For details of how to configure

custom logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web

Site [page 31]

3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC

Data Source [page 32]

4 Modify the default access rights to the Management Console By default users in Active

Directory can access the Management Console with whatever rights they have been granted

on the server For information about removing default access and creating a group that can

access the console see Removing Default Access to the Console [page 32]

5 Add authorized users or groups to the group that can access the Management Console We

recommend that you only grant Management Console access to system administrators

Planning and Consolidation users should not have any access For more information see

Management Console Access Control [page 33]

6 Configure the use of client certificates for authentication See Using Client Certificates [page

34]

4 Take the following steps to set up security

If you are defining security and application structure continue with step 5

3 After Installing Planning and Consolidation Servers

31 Post-Installation Steps

2012-06-13 CUSTOMER 2754

If you want to designate someone other than the system administrator to manage security

and application structure log on to EnvironmentShell designate a user as a Primary

Administrator

This user must have Administration ‒ Environment and Security ‒ Define User task rights

so that he or she can add and delete environments and define user security

The Primary Administrator can continue with the next step (5)

5 From the machine on which you administer Planning and Consolidation install the

Administration client See Installing the Administration Client [page 37]

6 Start Planning and Consolidation Administration from the launch page

7 Select Connection Wizard and log on to EnvironmentShell

8 Create a new environment using EnvironmentShell as the source

9 Log on to the newly created environment and set up users teams and task profiles (You must

set up task profiles since there is no access to Planning and Consolidation tasks)

10 Set up your data access profiles and add users (or teams) to one or more data access profiles (You

must complete this step since there is no access to dimensions or members)

NOTE

To allow users to request and query large amounts of data you can edit the metabasexml file located

at CWindowssystem32inetsrv Set the following parameters to the stated values

ASPBUFFERINGLIMIT = 10485760

MAXREQUESTENTITYALLOWED = 10485760

32 Connecting to Solution Manager Diagnostics

NOTE

You only need to perform the steps in this section if you have a SAP Solution Manager licence

The diagnostics functions in SAP Solution Manager allow identification analysis and resolution of

problems This procedure provides the steps required to connect Planning and Consolidation to

Solution Manager Diagnostics

Procedure

1 Install the Diagnostics Agent according to SAP Note 1234387 on all servers where application servers

are installed

NOTE

Installation files for Diagnostics Agent are available on Service Marketplace by navigating to

Support Packages and Patches mdash Entry by Application Group SAP Technology Components SAP

SOLUTION MANAGER SAP SOLUTION MANAGER 70 EHP 1 Entry by Component Agents

for managed systems DIAGNOSTICS AGENT 711

3 After Installing Planning and Consolidation Servers

32 Connecting to Solution Manager Diagnostics

2854 CUSTOMER 2012-06-13

Download the installation file based on the 64-bit Windows Server system landscape

2 To access the DBA Cockpit you must create a user account with sufficient rights on all Windows

Servers where Microsoft SQL Server is installed Do the following

1 Start Computer Management then select Action New User

2 Create a new user

3 Right-click on the user then choose Properties On the Member Of tab select Add

4 Add the group SQLServerltReleasegtSQLAgentUser$ltDomain or hostnamegt$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 httpsservicesapcom~sapidb011000358700000074392009E and follow

the chapters that apply to Planning and Consolidation

33 Configuring the Planning and Consolidation NET Application Servers

Procedure

Modifying machineconfig Files

To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock

occurrences that would cause the application server to ldquosleeprdquo and not process anymore you can

modify the machineconfig file which resides in the WINDOWSMicrosoftNETFramework64

v4030319Config directory

1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to

specify whether to automatically configure settings to achieve optimal performance based on the

machine configuration You can set this attribute to True or False

For more information see httpmsdnmicrosoftcomen-uslibrary7w2sway1aspx

2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the

Planning and Consolidation application) or Machineconfig (for all applications including

Planning and Consolidation) to ensure the validationKey and decryptionKey keys have the same

value on all application servers This way when the authentication cookie is checked the

authentication ticket used on one server can still be valid on another server

For more information and sample Visual Basic code for generating random key values see http

msdnmicrosoftcomen-uslibraryms998288aspx

3 After Installing Planning and Consolidation Servers

33 Configuring the Planning and Consolidation NET Application Servers

2012-06-13 CUSTOMER 2954

paght000007_webfarmdeploymentconsiderations and httpmsdnmicrosoftcomen-us

libraryms998310aspx

34 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 30]

2 Configure custom ODBC logging for the default Web site For details of how to configure custom

logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page

31]

3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC Data

Source [page 32]

4 Modify the default access rights to the Management Console By default users in Active Directory

can access the Management Console with whatever rights they have been granted on the server

For information about removing default access and creating a group that can access the console

see Removing Default Access to the Console [page 32]

5 Add authorized users or groups to the group that can access the Management Console We

recommend that you only grant Management Console access to system administrators Planning

and Consolidation users should not have any access For more information see Management Console

Access Control [page 33]

6 Configure the use of client certificates for authentication See Using Client Certificates [page 34]

341 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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3054 CUSTOMER 2012-06-13

NOTE

Without these updates the Management Console does work but some functionality (specifically

User Activity and Service Status) does not work as expected

Should you need to uninstall Planning and Consolidation we recommend that you reset the

Active Log Format field in IIS to W3C Extended Log File Format

342 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 ApplicationHostconfig set the property customLogPluginClsid to the value FF16065B-

DE82-11CF-BC0A-00AA006111E0 Set the logFormat to Custom You can find this in the ltlogFilegt

node in ApplicationHostconfig as shown here

ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0

logFormat=Custom gt

Use the following AppCmds to configure IIS to use ODBC logging for the default Web site

appcmd site set sitenameDefault Web Site

logFilecustomLogPluginClsidFF16065B-DE82-11CF-BC0A-00AA006111E0

appcmd site set sitenameDefault Web Site logFilelogFormatCustom

Configuring ODBC Logging Parameters in ApplicationHostconfig

Configure ApplicationHostconfig to contain the database table information as set up in the Microsoft

Support article specified in the Prerequisites section Configure these settings in the ltodbcLogginggt

node under ltsystemwebServergt

EXAMPLE

ltlocation path=Default Web Sitegt

ltsystemwebServergt

ltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog

userName=Username password=mypassword gt

ltsystemwebServergt

ltlocationgt

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3154

Use the following AppCmds to configure these attributes for the default Web site

appcmd set config Default Web Site sectionodbcLogging

dataSourceBPC_ManagementDSN commitappHost

appcmd set config Default Web Site sectionodbcLogging tableNameBPCLog

commitappHost

appcmd set config Default Web Site sectionodbcLogging userNameUsername

commitappHost

appcmd set config Default Web Site sectionodbcLogging passwordmypassword

commitappHost

NOTE

You cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must

use the SQL Server ODBC driver For more information see the Microsoft Knowledge Base article

931202 The requirements for using the ODBC logging feature in IIS

343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2

ProcedureThis procedure describes how to set up an ODBC data source for the Management Console in Windows

Server 2008 or Windows Server 2008 R2

Proceed as follows

1 Open ODBC Connection Manager

2 On the System DSN tab page add a new DSN

Choose Add

Choose SQL Server as the driver

Choose Finish

3 In the Name and Description fields enter BPC_ManagementDSN

4 In the Server field enter the name of your SQL Server Choose Next

5 Leave the default settings and choose Next

6 Choose the Change the default database to field and enter AppServer Choose Next

7 Leave default settings and choose Next

8 Choose OK

344 Removing Default Access to the Console

NOTE

If you have chosen SAP BusinessObjects User Management System in the installation screen you

do not need to remove or configure access because the Management Console service always runs

with the System Admin ID account which is a member of the Administrators group

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3254 CUSTOMER 2012-06-13

ProcedureTo remove default access to the Management Console and create a group that does have access to the

console use the procedure described below

NOTE

Create your Management Console administrative group either on the server that hosts the

Management Console or in the Active Directory

1 In the context menu of the servers My Computer icon choose Manage

2 In the Computer Management dialog box choose Local Users and Groups Groups

NOTE

Alternatively you can perform analogous steps in Active Directory

3 In the 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

NOTE

This step is a necessary precursor to the completion of this procedure

10 In the Security dialog box click Copy to ensure that the System group retains its privileges

11 Remove access to the Management Console from all groups that should not have it

12 Choose Authentication in the center pane then disable Windows authentication

ResultUsers who have not been granted access to the Management Console can still open the Management

Console Web page but it contains no data or menu options This does not affect the access that a user

would otherwise have to Planning and Consolidation

345 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 32] Their rights in

Active Directory determine what they can access in the Console

By default any member of the Administrators Active Directory group on the application server or

domain has full access to all of the features of the Console except the Planning and Consolidation

logging area Access to Planning and Consolidation logging is controlled within the Planning and

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3354

Consolidation Administration Client task security The user must be granted View system logs task

privileges For more information see the SAP Library Planning and Consolidation Administrators Guide in

httpservicesapcominstguidesepm-bpc 100 version for the Microsoft platform

Your IT policy determines whether you grant access by group or user You may wish to create several

levels of Console users (read-only users for example) in your environment

To grant or limit access to users or groups you can add or remove the following privileges from the

areas described in this table

Privilege Rights Management Area

Task Manager and Kill Process Administrators group on application server or domain

Performance Monitor Counters Administrators group on application server or domain Power Users group on application server or domain Performance Monitor Users group on application server

Microsoft Analysis Services performance monitoring

Administrators group on application server or domain

Microsoft SQL Server Monitoring (performance counters and statistics)

Administrators group on application server or domain

346 Using Client Certificates

To enable the use of client certificates in Planning and Consolidation you must follow several manual

steps

NOTE

Planning 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 httptechnetmicrosoftcomen-us

librarycc753810aspx

For more information about configuring the client certificate mapping authentication see http

technetmicrosoftcomen-uslibrarycc732996(WS10)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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3454 CUSTOMER 2012-06-13

This option allows you to use a client certificate or username and password (Basic

authentication) to connect to Planning and Consolidation

2 Enable anonymous authentication

1 In the IIS Manager expand the node of the Planning and Consolidation web site

2 Select the ManagementConsole directory (ltWebsitegtManagementConsole) to open the

ManagementConsole home page

3 Double-click Authentication and enable Anonymous Authentication

4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way

as in step 3

5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the same

way as in step 3

3 Change the web configuration settings

1 Open the ltPC_MSgtWebsrvrWebBPCwebconfig file

2 Find the text clientCredentialType=Windows

3 Change value of clientCredentialType to None (clientCredentialType=None)

4 Open the PC_MSWebsrvrWebPOASBCwebconfig file Repeat steps 2 and 3

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3554

This page is left blank for documents that are printed on both sides

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

The installation of the Planning and Consolidation Administration Client allows administrators to

build and maintain Planning and Consolidation environments and models and administer security

All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions

add-in for Microsoft Office for more information see the SAP BusinessObjects EPM solutions add-in for

Microsoft Office help

NOTE

You must update the Administration Client to the same version as the server

If your PC is on a different domain than your server you must set the Internet Explorer

Security Zone value of the Planning and Consolidation client to prompt for user name and

password Otherwise the Planning and Consolidation Start Page does not display

41 Installing the Administration Client

Prerequisites

NOTE

For a definitive list of system requirements see the Product Availability Matrix on SAP Service

Marketplace at httpservicesapcompam Search on Planning and Consolidation

The following list describes the minimum software requirements

Microsoft Internet Explorer 70 or 80

Microsoft Office 2007 or 2010

NET Framework 20 or higher (install any required NET Framework Hotfixes by referring to

httpsupportmicrosoftcomkb)

Pentium IV (1 GHz CPU)

512 MB RAM

100 MB of free hard disk space in the My Documents folder

20 MB of free hard disk space for the installed Administration files

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

41 Installing the Administration Client

2012-06-13 CUSTOMER 3754

NOTE

We recommend that you install all of the latest Microsoft Windows hotfixes prior to installing

the Administration client For information about which hotfixes to install see http

updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us

ProcedureThe following procedure describes how to install the Administration Client on to an administratorrsquos

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 AddRemove Programs in the Windows Control Panel

3 Point your browser to the Planning and Consolidation Web at httpltPC_serverportgtsap

bpcweb

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

42 Installing the EPM Add-in

The Planning and Consolidation installation media does not contain the EPM addin setup program

You must download the most recent version of the full setup (EPM Add-inexe) from the Service

Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPC

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

43 Using the Client Auto Update Program

If Planning and Consolidation version 100 or later is installed you can use the Client Auto Update

program to set up the server so that it determines if an upgrade for a connecting Administration client

is necessary

The following describes the use of the auto update program for the Administration Client and the EPM

add-in

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

42 Installing the EPM Add-in

3854 CUSTOMER 2012-06-13

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 37]

To use the Client Auto Update program for the Administration Client proceed as follows

1 From the Server Manager select Options Client Options

2 Select Admin Update

3 If users without administrator rights on their machines use the auto update enter an administrator

ID and password in the Admin ID and Admin password fields respectively The Admin ID should be a

member of the local administrators group on all the computers running the auto update This

setting is not needed if all users have administrator rights on their machines

4 Select Update

For the EPM Add-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 Optionshellip 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 Market Place (SMP) at httpservicesapcom

All support packages and patches are available from the SMP as a zip file

EPMEXCLCLNTltSPLgtzip is for a support package

EPMEXCLCLNTltSPLgtPltPLgtzip 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 ltSP versiongtmsp

EPM Addin Support Package ltSP versiongtxml

For a patch these files are

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

2012-06-13 CUSTOMER 3954

EPM Addin Patch ltpatch numbergtmsp

EPM Addin Patch ltpatch numbergtxml

2 Unzip the zip file and extract the two files to the application server folder (WebsrvrWebBPC

Installation)

3 From the Server Manager select Options Client Options

The system lists the available packages Select the package that you want to use for the autoupdate

You can set a different update policy for each package listed

EXAMPLE

The following table illustrates some possible situations assuming that you have installed the

first full version (V1)

Available maintenance packages

V2-user updateV3-force updateV4-force updateV5-user update

V5-user update V5-user updateV6-auto updateV7-force update

Minimum Required Version

V4 V4 V7

Notification A prompt tells the user to install maintenance package V4 using the Forced Update behavior

If User Update is enabled the prompt informs the user that maintenance package V5 is available

A prompt tells the user to install maintenance package V7 using the Forced Update behavior

New Version V4 V4 or V5 V7

If you change the update policy for any package click Update to complete the change

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

4054 CUSTOMER 2012-06-13

5 Connection Issues

You may experience connection problems with ports the proxy server or programs and settings that

interact with these components If you have any issues related to connection review the following

recommendations and troubleshooting tips

51 Checking for Open Ports

You must ensure that all required ports are open for inboundoutbound 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 431181836 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

NOTE

You can use the following site to scan for the normal ports It allows you to manually enter a port

number to test

httpwwwmyserverorgportsniffasp

You can change the name of a port

52 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 Explorer Tools Internet Options Connections LAN Settings ) or at the server level

Enabling content filtering on the proxy server or firewall may cause connection problems

If external users are having trouble connecting to the server make sure the proxy server connects

using a fully qualified domain name Fully qualified domain names typically resolve both internal

and external IP addresses

Each secure Planning and Consolidation server name must be identified on the proxy server

Proxy servers may or may not require authentication which could conflict with Planning and

Consolidation authentication Do not use authentication on the proxy server The system

5 Connection Issues

51 Checking for Open Ports

2012-06-13 CUSTOMER 4154

synchronizes the user name and password on the remote server with the local user name and

password

NOTE

For more information about setting up an ISA proxy server contact SAP Support to request a

copy of Setting up ISA Proxy Server White Paper

Internet Explorer Settings 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

5 Connection Issues

52 Proxy Server and Firewall Issues

4254 CUSTOMER 2012-06-13

6 Installing Planning and Consolidation with Two Active Directory Domains

To set up a Planning and Consolidation 10 application server in a hosted environment and use your

own domain users follow this procedure In general you install Planning and Consolidation on the

host domain use the host domain account and assign it to the Planning and Consolidation users

SysAdmin Admin and Users Then you accept one way trust (the host domain trusts your domain)

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

6 Installing Planning and Consolidation with Two Active Directory Domains

2012-06-13 CUSTOMER 4354

This page is left blank for documents that are printed on both sides

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

This section describes best practices and instructions for installing Planning and Consolidation in a

Terminal Services or Citrix Server deployment

71 Terminal Services Home Directories

We recommend using Terminal Server home directories rather than using the userrsquos 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

72 System Requirements

The Citrix server should be one of the following systems

XenApp 5 Enterprise

XenApp 5 Platinum

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 37])

73 Installing Planning and Consolidation

Prerequisites

The server installation files have been downloaded from SAP Service Marketplace and installed

Procedure

The following steps outline how to install the Planning and Consolidation clients in a Terminal Services

(TS) or Citrix Server deployment

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

71 Terminal Services Home Directories

2012-06-13 CUSTOMER 4554

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 userinstall

4 Open a browser and connect to the URL httpltPC_serverportgtsapbpcweb

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 userexecute 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 Iexploreexe http(s)

ltServerNamegt-NetBIOS or FQDNsapbpcweb

To publish Planning and Consolidation Administration CProgram FilesPC_MS

BPCAdminMainexe

74 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 userrsquos desktop) must be moved to the All UsersDesktop folder

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

74 Creating a Shortcut to the Launch Page

4654 CUSTOMER 2012-06-13

8 Installing SSIS Custom Tasks

This section provides background information and instructions for installing SQL Server Integration

Services (SSIS) for SQL Server 2008 and SQL Server 2012

The Planning and Consolidation Data Manager component supports and uses SSIS Since SQL Server

2008 and SQL Server 2012 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

81 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 Filelistxml 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

OSoftSetupexe ‒ 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 or OSoftSSIS2012_Client on the client machine followed by the SQL Server

version If you want to use SQL 2008 Tasks under the SQL 2012 environment you must install

OSoftSSIS2008_Client on the application server For detailed information see SAP Note 1707410

You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package by extracting

OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPC

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 or

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4754

OSoftSSIS2012_Client for creating a COM+ application For more information see Before You Modify

the SSIS Packages [page 50] and Setup of a COM+ Application on the Application Server [page 51]

Bin folder

This folder contains the following components

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCCachedll Planning and Consolidation Cache file

BPCDataFlowPackagedll or BPCDataFlowPackage2012dll

BPCDMdll

BPCDMTaskMaindll COM+ component

BPCFilePreviewdll

BPCGacUtil_20exe System File

BPCGacUtil_40exe System File

BPCImpersonatordll Planning and Consolidation Impersonator

BPCLogicdll

BPCScriptdll

BPCServerZipdll

BPCServiceResdll

BPCTransferMembersdll

BPCWriteBackdll

InteropDTSdll

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

4854 CUSTOMER 2012-06-13

Name Remark

OSoftAdminServerdll

OSoftAuditdll

OSoftComLibServerdll

OSoftCommonResQrydll

OSoftConfigurationdll

OSoftCustomXMLSvrdll

OSoftDatabaseADMINdll

OSoftDatabaseSYSADMINdll

OSoftDatabaseSYSADMINDMdll

OSoftDatabaseUSERdll

OSoftDMDTSXExecutedll or OSoftDMDTSXExecute2012dll

OSoftDMTaskFormdll

OSoftDMTaskMaindll

OSoftDMToolsdll

OSoftFileManagedll

OSoftLoggingdll

OSoftLogWriterdll

OSoftMetaDatadll

OSoftSQEdll

OSoftSystemConfigdll

OutlookSoftconfig Configuration file to connect DB server

XceedCompressiondll XceedZip file

XceedCompressionFormatsdll XceedZip file

XceedFileSystemdll XceedZip file

XceedZipdll XceedZip file

Config folder

This folder has FileListxml 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 FileListxml 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

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4954

OSoftSetupexe

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

NOTE

If you installed the OSoftSSIS2008_Client or OSoftSSIS2012_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

Resources Folder

This folder contains the BPCServicesdll and BPCServiceUIdll files which contain resource text

Only English resources are included for the SSIS custom tasks

82 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

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008 and 2012 respectively

8 Installing SSIS Custom Tasks

82 Before You Modify the SSIS Packages

5054 CUSTOMER 2012-06-13

Name Remark

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012 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

lthellipgtOSoftSSIS2008_Clientbin or lthellipgtOSoftSSIS2012_Clientbin

On the Planning and Consolidation application server

ltdrivegtWebsrvrbin

2 Paste these files into the folder 100DTSTasks for SQL Server 2008 or into 110DTSTasks for

SQL Server 2012 For example if you install your SQL 2008 server or R2 on CProgram Files

Microsoft SQL Server paste all files into the CProgram Files (x86)Microsoft SQL Server

100DTSTasks folder

In Integration Services set the property Run64BitRunTime to True

83 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 or OSoftSSIS2012_Client on the

application server

8 Installing SSIS Custom Tasks

83 Setup of a COM+ Application on the Application Server

2012-06-13 CUSTOMER 5154

Typographic Conventions

Example Description

ltgt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example Enter your ltUser Namegt

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 httpwwwsapcom

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

5254 CUSTOMER 2012-06-13

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

  • SAP BusinessObjects Planning and Consolidation 100
    • Table of Contents
    • 1 Introduction
      • 11 SAP Notes for the Installation
      • 12 Naming Conventions
        • 2 Installing Planning and Consolidation Servers
          • 21 Basic Steps
          • 22 Prerequisites
          • 23 Before Starting the Planning and Consolidation Server Installation
          • 24 Logging on to Servers
          • 25 Service-level Accounts
          • 26 Standard and Advanced Settings
          • 27 Installing the Prerequisites
            • 271 Installing the Prerequisites ndash Basic Steps
            • 272 Installing the Operating System
            • 273 Installing the SQL Server
            • 274 Installing Analysis Services
            • 275 Installing the Anti-Cross Site Scripting Library
              • 28 Installing on a Single Server
              • 29 Installing the Server in a Multiserver Configuration
                • 3 After Installing Planning and Consolidation Servers
                  • 31 Post-Installation Steps
                  • 32 Connecting to Solution Manager Diagnostics
                  • 33 Configuring the Planning and Consolidation NET Application Servers
                  • 34 Post-Installation Optional Configuration Steps
                    • 341 Enabling the Management Console
                    • 342 Setting Up ODBC Logging in IIS for the Default Web Site
                    • 343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2
                    • 344 Removing Default Access to the Console
                    • 345 Management Console Access Control
                    • 346 Using Client Certificates
                        • 4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office
                          • 41 Installing the Administration Client
                          • 42 Installing the EPM Add-in
                          • 43 Using the Client Auto Update Program
                            • 5 Connection Issues
                              • 51 Checking for Open Ports
                              • 52 Proxy Server and Firewall Issues
                                • 6 Installing Planning and Consolidation with Two Active Directory Domains
                                • 7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
                                  • 71 Terminal Services Home Directories
                                  • 72 System Requirements
                                  • 73 Installing Planning and Consolidation
                                  • 74 Creating a Shortcut to the Launch Page
                                    • 8 Installing SSIS Custom Tasks
                                      • 81 Composition of SSIS Custom Task Installation
                                      • 82 Before You Modify the SSIS Packages
                                      • 83 Setup of a COM+ Application on the Application Server
                                          • Copyright and trademarks
Page 27: Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

3 After Installing Planning and Consolidation Servers

31 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 28]

2 Configure the Planning and Consolidation NET and application server to ensure that it and its

related services function properly and reliably For more information see Configuring the Planning and

Consolidation NET Application Server [page 29]

3 Optional configuration steps [page 30]

1 To ensure proper functioning of the Management Console create an SQL user and modify

the System DSN and IIS to reflect those user credentials See Enabling Management Console [page

30]

2 Configure custom ODBC logging for the default Web site For details of how to configure

custom logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web

Site [page 31]

3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC

Data Source [page 32]

4 Modify the default access rights to the Management Console By default users in Active

Directory can access the Management Console with whatever rights they have been granted

on the server For information about removing default access and creating a group that can

access the console see Removing Default Access to the Console [page 32]

5 Add authorized users or groups to the group that can access the Management Console We

recommend that you only grant Management Console access to system administrators

Planning and Consolidation users should not have any access For more information see

Management Console Access Control [page 33]

6 Configure the use of client certificates for authentication See Using Client Certificates [page

34]

4 Take the following steps to set up security

If you are defining security and application structure continue with step 5

3 After Installing Planning and Consolidation Servers

31 Post-Installation Steps

2012-06-13 CUSTOMER 2754

If you want to designate someone other than the system administrator to manage security

and application structure log on to EnvironmentShell designate a user as a Primary

Administrator

This user must have Administration ‒ Environment and Security ‒ Define User task rights

so that he or she can add and delete environments and define user security

The Primary Administrator can continue with the next step (5)

5 From the machine on which you administer Planning and Consolidation install the

Administration client See Installing the Administration Client [page 37]

6 Start Planning and Consolidation Administration from the launch page

7 Select Connection Wizard and log on to EnvironmentShell

8 Create a new environment using EnvironmentShell as the source

9 Log on to the newly created environment and set up users teams and task profiles (You must

set up task profiles since there is no access to Planning and Consolidation tasks)

10 Set up your data access profiles and add users (or teams) to one or more data access profiles (You

must complete this step since there is no access to dimensions or members)

NOTE

To allow users to request and query large amounts of data you can edit the metabasexml file located

at CWindowssystem32inetsrv Set the following parameters to the stated values

ASPBUFFERINGLIMIT = 10485760

MAXREQUESTENTITYALLOWED = 10485760

32 Connecting to Solution Manager Diagnostics

NOTE

You only need to perform the steps in this section if you have a SAP Solution Manager licence

The diagnostics functions in SAP Solution Manager allow identification analysis and resolution of

problems This procedure provides the steps required to connect Planning and Consolidation to

Solution Manager Diagnostics

Procedure

1 Install the Diagnostics Agent according to SAP Note 1234387 on all servers where application servers

are installed

NOTE

Installation files for Diagnostics Agent are available on Service Marketplace by navigating to

Support Packages and Patches mdash Entry by Application Group SAP Technology Components SAP

SOLUTION MANAGER SAP SOLUTION MANAGER 70 EHP 1 Entry by Component Agents

for managed systems DIAGNOSTICS AGENT 711

3 After Installing Planning and Consolidation Servers

32 Connecting to Solution Manager Diagnostics

2854 CUSTOMER 2012-06-13

Download the installation file based on the 64-bit Windows Server system landscape

2 To access the DBA Cockpit you must create a user account with sufficient rights on all Windows

Servers where Microsoft SQL Server is installed Do the following

1 Start Computer Management then select Action New User

2 Create a new user

3 Right-click on the user then choose Properties On the Member Of tab select Add

4 Add the group SQLServerltReleasegtSQLAgentUser$ltDomain or hostnamegt$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 httpsservicesapcom~sapidb011000358700000074392009E and follow

the chapters that apply to Planning and Consolidation

33 Configuring the Planning and Consolidation NET Application Servers

Procedure

Modifying machineconfig Files

To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock

occurrences that would cause the application server to ldquosleeprdquo and not process anymore you can

modify the machineconfig file which resides in the WINDOWSMicrosoftNETFramework64

v4030319Config directory

1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to

specify whether to automatically configure settings to achieve optimal performance based on the

machine configuration You can set this attribute to True or False

For more information see httpmsdnmicrosoftcomen-uslibrary7w2sway1aspx

2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the

Planning and Consolidation application) or Machineconfig (for all applications including

Planning and Consolidation) to ensure the validationKey and decryptionKey keys have the same

value on all application servers This way when the authentication cookie is checked the

authentication ticket used on one server can still be valid on another server

For more information and sample Visual Basic code for generating random key values see http

msdnmicrosoftcomen-uslibraryms998288aspx

3 After Installing Planning and Consolidation Servers

33 Configuring the Planning and Consolidation NET Application Servers

2012-06-13 CUSTOMER 2954

paght000007_webfarmdeploymentconsiderations and httpmsdnmicrosoftcomen-us

libraryms998310aspx

34 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 30]

2 Configure custom ODBC logging for the default Web site For details of how to configure custom

logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page

31]

3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC Data

Source [page 32]

4 Modify the default access rights to the Management Console By default users in Active Directory

can access the Management Console with whatever rights they have been granted on the server

For information about removing default access and creating a group that can access the console

see Removing Default Access to the Console [page 32]

5 Add authorized users or groups to the group that can access the Management Console We

recommend that you only grant Management Console access to system administrators Planning

and Consolidation users should not have any access For more information see Management Console

Access Control [page 33]

6 Configure the use of client certificates for authentication See Using Client Certificates [page 34]

341 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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3054 CUSTOMER 2012-06-13

NOTE

Without these updates the Management Console does work but some functionality (specifically

User Activity and Service Status) does not work as expected

Should you need to uninstall Planning and Consolidation we recommend that you reset the

Active Log Format field in IIS to W3C Extended Log File Format

342 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 ApplicationHostconfig set the property customLogPluginClsid to the value FF16065B-

DE82-11CF-BC0A-00AA006111E0 Set the logFormat to Custom You can find this in the ltlogFilegt

node in ApplicationHostconfig as shown here

ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0

logFormat=Custom gt

Use the following AppCmds to configure IIS to use ODBC logging for the default Web site

appcmd site set sitenameDefault Web Site

logFilecustomLogPluginClsidFF16065B-DE82-11CF-BC0A-00AA006111E0

appcmd site set sitenameDefault Web Site logFilelogFormatCustom

Configuring ODBC Logging Parameters in ApplicationHostconfig

Configure ApplicationHostconfig to contain the database table information as set up in the Microsoft

Support article specified in the Prerequisites section Configure these settings in the ltodbcLogginggt

node under ltsystemwebServergt

EXAMPLE

ltlocation path=Default Web Sitegt

ltsystemwebServergt

ltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog

userName=Username password=mypassword gt

ltsystemwebServergt

ltlocationgt

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3154

Use the following AppCmds to configure these attributes for the default Web site

appcmd set config Default Web Site sectionodbcLogging

dataSourceBPC_ManagementDSN commitappHost

appcmd set config Default Web Site sectionodbcLogging tableNameBPCLog

commitappHost

appcmd set config Default Web Site sectionodbcLogging userNameUsername

commitappHost

appcmd set config Default Web Site sectionodbcLogging passwordmypassword

commitappHost

NOTE

You cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must

use the SQL Server ODBC driver For more information see the Microsoft Knowledge Base article

931202 The requirements for using the ODBC logging feature in IIS

343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2

ProcedureThis procedure describes how to set up an ODBC data source for the Management Console in Windows

Server 2008 or Windows Server 2008 R2

Proceed as follows

1 Open ODBC Connection Manager

2 On the System DSN tab page add a new DSN

Choose Add

Choose SQL Server as the driver

Choose Finish

3 In the Name and Description fields enter BPC_ManagementDSN

4 In the Server field enter the name of your SQL Server Choose Next

5 Leave the default settings and choose Next

6 Choose the Change the default database to field and enter AppServer Choose Next

7 Leave default settings and choose Next

8 Choose OK

344 Removing Default Access to the Console

NOTE

If you have chosen SAP BusinessObjects User Management System in the installation screen you

do not need to remove or configure access because the Management Console service always runs

with the System Admin ID account which is a member of the Administrators group

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3254 CUSTOMER 2012-06-13

ProcedureTo remove default access to the Management Console and create a group that does have access to the

console use the procedure described below

NOTE

Create your Management Console administrative group either on the server that hosts the

Management Console or in the Active Directory

1 In the context menu of the servers My Computer icon choose Manage

2 In the Computer Management dialog box choose Local Users and Groups Groups

NOTE

Alternatively you can perform analogous steps in Active Directory

3 In the 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

NOTE

This step is a necessary precursor to the completion of this procedure

10 In the Security dialog box click Copy to ensure that the System group retains its privileges

11 Remove access to the Management Console from all groups that should not have it

12 Choose Authentication in the center pane then disable Windows authentication

ResultUsers who have not been granted access to the Management Console can still open the Management

Console Web page but it contains no data or menu options This does not affect the access that a user

would otherwise have to Planning and Consolidation

345 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 32] Their rights in

Active Directory determine what they can access in the Console

By default any member of the Administrators Active Directory group on the application server or

domain has full access to all of the features of the Console except the Planning and Consolidation

logging area Access to Planning and Consolidation logging is controlled within the Planning and

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3354

Consolidation Administration Client task security The user must be granted View system logs task

privileges For more information see the SAP Library Planning and Consolidation Administrators Guide in

httpservicesapcominstguidesepm-bpc 100 version for the Microsoft platform

Your IT policy determines whether you grant access by group or user You may wish to create several

levels of Console users (read-only users for example) in your environment

To grant or limit access to users or groups you can add or remove the following privileges from the

areas described in this table

Privilege Rights Management Area

Task Manager and Kill Process Administrators group on application server or domain

Performance Monitor Counters Administrators group on application server or domain Power Users group on application server or domain Performance Monitor Users group on application server

Microsoft Analysis Services performance monitoring

Administrators group on application server or domain

Microsoft SQL Server Monitoring (performance counters and statistics)

Administrators group on application server or domain

346 Using Client Certificates

To enable the use of client certificates in Planning and Consolidation you must follow several manual

steps

NOTE

Planning 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 httptechnetmicrosoftcomen-us

librarycc753810aspx

For more information about configuring the client certificate mapping authentication see http

technetmicrosoftcomen-uslibrarycc732996(WS10)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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3454 CUSTOMER 2012-06-13

This option allows you to use a client certificate or username and password (Basic

authentication) to connect to Planning and Consolidation

2 Enable anonymous authentication

1 In the IIS Manager expand the node of the Planning and Consolidation web site

2 Select the ManagementConsole directory (ltWebsitegtManagementConsole) to open the

ManagementConsole home page

3 Double-click Authentication and enable Anonymous Authentication

4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way

as in step 3

5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the same

way as in step 3

3 Change the web configuration settings

1 Open the ltPC_MSgtWebsrvrWebBPCwebconfig file

2 Find the text clientCredentialType=Windows

3 Change value of clientCredentialType to None (clientCredentialType=None)

4 Open the PC_MSWebsrvrWebPOASBCwebconfig file Repeat steps 2 and 3

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3554

This page is left blank for documents that are printed on both sides

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

The installation of the Planning and Consolidation Administration Client allows administrators to

build and maintain Planning and Consolidation environments and models and administer security

All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions

add-in for Microsoft Office for more information see the SAP BusinessObjects EPM solutions add-in for

Microsoft Office help

NOTE

You must update the Administration Client to the same version as the server

If your PC is on a different domain than your server you must set the Internet Explorer

Security Zone value of the Planning and Consolidation client to prompt for user name and

password Otherwise the Planning and Consolidation Start Page does not display

41 Installing the Administration Client

Prerequisites

NOTE

For a definitive list of system requirements see the Product Availability Matrix on SAP Service

Marketplace at httpservicesapcompam Search on Planning and Consolidation

The following list describes the minimum software requirements

Microsoft Internet Explorer 70 or 80

Microsoft Office 2007 or 2010

NET Framework 20 or higher (install any required NET Framework Hotfixes by referring to

httpsupportmicrosoftcomkb)

Pentium IV (1 GHz CPU)

512 MB RAM

100 MB of free hard disk space in the My Documents folder

20 MB of free hard disk space for the installed Administration files

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

41 Installing the Administration Client

2012-06-13 CUSTOMER 3754

NOTE

We recommend that you install all of the latest Microsoft Windows hotfixes prior to installing

the Administration client For information about which hotfixes to install see http

updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us

ProcedureThe following procedure describes how to install the Administration Client on to an administratorrsquos

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 AddRemove Programs in the Windows Control Panel

3 Point your browser to the Planning and Consolidation Web at httpltPC_serverportgtsap

bpcweb

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

42 Installing the EPM Add-in

The Planning and Consolidation installation media does not contain the EPM addin setup program

You must download the most recent version of the full setup (EPM Add-inexe) from the Service

Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPC

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

43 Using the Client Auto Update Program

If Planning and Consolidation version 100 or later is installed you can use the Client Auto Update

program to set up the server so that it determines if an upgrade for a connecting Administration client

is necessary

The following describes the use of the auto update program for the Administration Client and the EPM

add-in

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

42 Installing the EPM Add-in

3854 CUSTOMER 2012-06-13

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 37]

To use the Client Auto Update program for the Administration Client proceed as follows

1 From the Server Manager select Options Client Options

2 Select Admin Update

3 If users without administrator rights on their machines use the auto update enter an administrator

ID and password in the Admin ID and Admin password fields respectively The Admin ID should be a

member of the local administrators group on all the computers running the auto update This

setting is not needed if all users have administrator rights on their machines

4 Select Update

For the EPM Add-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 Optionshellip 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 Market Place (SMP) at httpservicesapcom

All support packages and patches are available from the SMP as a zip file

EPMEXCLCLNTltSPLgtzip is for a support package

EPMEXCLCLNTltSPLgtPltPLgtzip 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 ltSP versiongtmsp

EPM Addin Support Package ltSP versiongtxml

For a patch these files are

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

2012-06-13 CUSTOMER 3954

EPM Addin Patch ltpatch numbergtmsp

EPM Addin Patch ltpatch numbergtxml

2 Unzip the zip file and extract the two files to the application server folder (WebsrvrWebBPC

Installation)

3 From the Server Manager select Options Client Options

The system lists the available packages Select the package that you want to use for the autoupdate

You can set a different update policy for each package listed

EXAMPLE

The following table illustrates some possible situations assuming that you have installed the

first full version (V1)

Available maintenance packages

V2-user updateV3-force updateV4-force updateV5-user update

V5-user update V5-user updateV6-auto updateV7-force update

Minimum Required Version

V4 V4 V7

Notification A prompt tells the user to install maintenance package V4 using the Forced Update behavior

If User Update is enabled the prompt informs the user that maintenance package V5 is available

A prompt tells the user to install maintenance package V7 using the Forced Update behavior

New Version V4 V4 or V5 V7

If you change the update policy for any package click Update to complete the change

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

4054 CUSTOMER 2012-06-13

5 Connection Issues

You may experience connection problems with ports the proxy server or programs and settings that

interact with these components If you have any issues related to connection review the following

recommendations and troubleshooting tips

51 Checking for Open Ports

You must ensure that all required ports are open for inboundoutbound 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 431181836 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

NOTE

You can use the following site to scan for the normal ports It allows you to manually enter a port

number to test

httpwwwmyserverorgportsniffasp

You can change the name of a port

52 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 Explorer Tools Internet Options Connections LAN Settings ) or at the server level

Enabling content filtering on the proxy server or firewall may cause connection problems

If external users are having trouble connecting to the server make sure the proxy server connects

using a fully qualified domain name Fully qualified domain names typically resolve both internal

and external IP addresses

Each secure Planning and Consolidation server name must be identified on the proxy server

Proxy servers may or may not require authentication which could conflict with Planning and

Consolidation authentication Do not use authentication on the proxy server The system

5 Connection Issues

51 Checking for Open Ports

2012-06-13 CUSTOMER 4154

synchronizes the user name and password on the remote server with the local user name and

password

NOTE

For more information about setting up an ISA proxy server contact SAP Support to request a

copy of Setting up ISA Proxy Server White Paper

Internet Explorer Settings 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

5 Connection Issues

52 Proxy Server and Firewall Issues

4254 CUSTOMER 2012-06-13

6 Installing Planning and Consolidation with Two Active Directory Domains

To set up a Planning and Consolidation 10 application server in a hosted environment and use your

own domain users follow this procedure In general you install Planning and Consolidation on the

host domain use the host domain account and assign it to the Planning and Consolidation users

SysAdmin Admin and Users Then you accept one way trust (the host domain trusts your domain)

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

6 Installing Planning and Consolidation with Two Active Directory Domains

2012-06-13 CUSTOMER 4354

This page is left blank for documents that are printed on both sides

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

This section describes best practices and instructions for installing Planning and Consolidation in a

Terminal Services or Citrix Server deployment

71 Terminal Services Home Directories

We recommend using Terminal Server home directories rather than using the userrsquos 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

72 System Requirements

The Citrix server should be one of the following systems

XenApp 5 Enterprise

XenApp 5 Platinum

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 37])

73 Installing Planning and Consolidation

Prerequisites

The server installation files have been downloaded from SAP Service Marketplace and installed

Procedure

The following steps outline how to install the Planning and Consolidation clients in a Terminal Services

(TS) or Citrix Server deployment

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

71 Terminal Services Home Directories

2012-06-13 CUSTOMER 4554

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 userinstall

4 Open a browser and connect to the URL httpltPC_serverportgtsapbpcweb

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 userexecute 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 Iexploreexe http(s)

ltServerNamegt-NetBIOS or FQDNsapbpcweb

To publish Planning and Consolidation Administration CProgram FilesPC_MS

BPCAdminMainexe

74 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 userrsquos desktop) must be moved to the All UsersDesktop folder

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

74 Creating a Shortcut to the Launch Page

4654 CUSTOMER 2012-06-13

8 Installing SSIS Custom Tasks

This section provides background information and instructions for installing SQL Server Integration

Services (SSIS) for SQL Server 2008 and SQL Server 2012

The Planning and Consolidation Data Manager component supports and uses SSIS Since SQL Server

2008 and SQL Server 2012 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

81 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 Filelistxml 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

OSoftSetupexe ‒ 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 or OSoftSSIS2012_Client on the client machine followed by the SQL Server

version If you want to use SQL 2008 Tasks under the SQL 2012 environment you must install

OSoftSSIS2008_Client on the application server For detailed information see SAP Note 1707410

You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package by extracting

OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPC

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 or

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4754

OSoftSSIS2012_Client for creating a COM+ application For more information see Before You Modify

the SSIS Packages [page 50] and Setup of a COM+ Application on the Application Server [page 51]

Bin folder

This folder contains the following components

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCCachedll Planning and Consolidation Cache file

BPCDataFlowPackagedll or BPCDataFlowPackage2012dll

BPCDMdll

BPCDMTaskMaindll COM+ component

BPCFilePreviewdll

BPCGacUtil_20exe System File

BPCGacUtil_40exe System File

BPCImpersonatordll Planning and Consolidation Impersonator

BPCLogicdll

BPCScriptdll

BPCServerZipdll

BPCServiceResdll

BPCTransferMembersdll

BPCWriteBackdll

InteropDTSdll

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

4854 CUSTOMER 2012-06-13

Name Remark

OSoftAdminServerdll

OSoftAuditdll

OSoftComLibServerdll

OSoftCommonResQrydll

OSoftConfigurationdll

OSoftCustomXMLSvrdll

OSoftDatabaseADMINdll

OSoftDatabaseSYSADMINdll

OSoftDatabaseSYSADMINDMdll

OSoftDatabaseUSERdll

OSoftDMDTSXExecutedll or OSoftDMDTSXExecute2012dll

OSoftDMTaskFormdll

OSoftDMTaskMaindll

OSoftDMToolsdll

OSoftFileManagedll

OSoftLoggingdll

OSoftLogWriterdll

OSoftMetaDatadll

OSoftSQEdll

OSoftSystemConfigdll

OutlookSoftconfig Configuration file to connect DB server

XceedCompressiondll XceedZip file

XceedCompressionFormatsdll XceedZip file

XceedFileSystemdll XceedZip file

XceedZipdll XceedZip file

Config folder

This folder has FileListxml 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 FileListxml 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

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4954

OSoftSetupexe

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

NOTE

If you installed the OSoftSSIS2008_Client or OSoftSSIS2012_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

Resources Folder

This folder contains the BPCServicesdll and BPCServiceUIdll files which contain resource text

Only English resources are included for the SSIS custom tasks

82 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

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008 and 2012 respectively

8 Installing SSIS Custom Tasks

82 Before You Modify the SSIS Packages

5054 CUSTOMER 2012-06-13

Name Remark

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012 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

lthellipgtOSoftSSIS2008_Clientbin or lthellipgtOSoftSSIS2012_Clientbin

On the Planning and Consolidation application server

ltdrivegtWebsrvrbin

2 Paste these files into the folder 100DTSTasks for SQL Server 2008 or into 110DTSTasks for

SQL Server 2012 For example if you install your SQL 2008 server or R2 on CProgram Files

Microsoft SQL Server paste all files into the CProgram Files (x86)Microsoft SQL Server

100DTSTasks folder

In Integration Services set the property Run64BitRunTime to True

83 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 or OSoftSSIS2012_Client on the

application server

8 Installing SSIS Custom Tasks

83 Setup of a COM+ Application on the Application Server

2012-06-13 CUSTOMER 5154

Typographic Conventions

Example Description

ltgt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example Enter your ltUser Namegt

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 httpwwwsapcom

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

5254 CUSTOMER 2012-06-13

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

  • SAP BusinessObjects Planning and Consolidation 100
    • Table of Contents
    • 1 Introduction
      • 11 SAP Notes for the Installation
      • 12 Naming Conventions
        • 2 Installing Planning and Consolidation Servers
          • 21 Basic Steps
          • 22 Prerequisites
          • 23 Before Starting the Planning and Consolidation Server Installation
          • 24 Logging on to Servers
          • 25 Service-level Accounts
          • 26 Standard and Advanced Settings
          • 27 Installing the Prerequisites
            • 271 Installing the Prerequisites ndash Basic Steps
            • 272 Installing the Operating System
            • 273 Installing the SQL Server
            • 274 Installing Analysis Services
            • 275 Installing the Anti-Cross Site Scripting Library
              • 28 Installing on a Single Server
              • 29 Installing the Server in a Multiserver Configuration
                • 3 After Installing Planning and Consolidation Servers
                  • 31 Post-Installation Steps
                  • 32 Connecting to Solution Manager Diagnostics
                  • 33 Configuring the Planning and Consolidation NET Application Servers
                  • 34 Post-Installation Optional Configuration Steps
                    • 341 Enabling the Management Console
                    • 342 Setting Up ODBC Logging in IIS for the Default Web Site
                    • 343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2
                    • 344 Removing Default Access to the Console
                    • 345 Management Console Access Control
                    • 346 Using Client Certificates
                        • 4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office
                          • 41 Installing the Administration Client
                          • 42 Installing the EPM Add-in
                          • 43 Using the Client Auto Update Program
                            • 5 Connection Issues
                              • 51 Checking for Open Ports
                              • 52 Proxy Server and Firewall Issues
                                • 6 Installing Planning and Consolidation with Two Active Directory Domains
                                • 7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
                                  • 71 Terminal Services Home Directories
                                  • 72 System Requirements
                                  • 73 Installing Planning and Consolidation
                                  • 74 Creating a Shortcut to the Launch Page
                                    • 8 Installing SSIS Custom Tasks
                                      • 81 Composition of SSIS Custom Task Installation
                                      • 82 Before You Modify the SSIS Packages
                                      • 83 Setup of a COM+ Application on the Application Server
                                          • Copyright and trademarks
Page 28: Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

If you want to designate someone other than the system administrator to manage security

and application structure log on to EnvironmentShell designate a user as a Primary

Administrator

This user must have Administration ‒ Environment and Security ‒ Define User task rights

so that he or she can add and delete environments and define user security

The Primary Administrator can continue with the next step (5)

5 From the machine on which you administer Planning and Consolidation install the

Administration client See Installing the Administration Client [page 37]

6 Start Planning and Consolidation Administration from the launch page

7 Select Connection Wizard and log on to EnvironmentShell

8 Create a new environment using EnvironmentShell as the source

9 Log on to the newly created environment and set up users teams and task profiles (You must

set up task profiles since there is no access to Planning and Consolidation tasks)

10 Set up your data access profiles and add users (or teams) to one or more data access profiles (You

must complete this step since there is no access to dimensions or members)

NOTE

To allow users to request and query large amounts of data you can edit the metabasexml file located

at CWindowssystem32inetsrv Set the following parameters to the stated values

ASPBUFFERINGLIMIT = 10485760

MAXREQUESTENTITYALLOWED = 10485760

32 Connecting to Solution Manager Diagnostics

NOTE

You only need to perform the steps in this section if you have a SAP Solution Manager licence

The diagnostics functions in SAP Solution Manager allow identification analysis and resolution of

problems This procedure provides the steps required to connect Planning and Consolidation to

Solution Manager Diagnostics

Procedure

1 Install the Diagnostics Agent according to SAP Note 1234387 on all servers where application servers

are installed

NOTE

Installation files for Diagnostics Agent are available on Service Marketplace by navigating to

Support Packages and Patches mdash Entry by Application Group SAP Technology Components SAP

SOLUTION MANAGER SAP SOLUTION MANAGER 70 EHP 1 Entry by Component Agents

for managed systems DIAGNOSTICS AGENT 711

3 After Installing Planning and Consolidation Servers

32 Connecting to Solution Manager Diagnostics

2854 CUSTOMER 2012-06-13

Download the installation file based on the 64-bit Windows Server system landscape

2 To access the DBA Cockpit you must create a user account with sufficient rights on all Windows

Servers where Microsoft SQL Server is installed Do the following

1 Start Computer Management then select Action New User

2 Create a new user

3 Right-click on the user then choose Properties On the Member Of tab select Add

4 Add the group SQLServerltReleasegtSQLAgentUser$ltDomain or hostnamegt$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 httpsservicesapcom~sapidb011000358700000074392009E and follow

the chapters that apply to Planning and Consolidation

33 Configuring the Planning and Consolidation NET Application Servers

Procedure

Modifying machineconfig Files

To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock

occurrences that would cause the application server to ldquosleeprdquo and not process anymore you can

modify the machineconfig file which resides in the WINDOWSMicrosoftNETFramework64

v4030319Config directory

1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to

specify whether to automatically configure settings to achieve optimal performance based on the

machine configuration You can set this attribute to True or False

For more information see httpmsdnmicrosoftcomen-uslibrary7w2sway1aspx

2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the

Planning and Consolidation application) or Machineconfig (for all applications including

Planning and Consolidation) to ensure the validationKey and decryptionKey keys have the same

value on all application servers This way when the authentication cookie is checked the

authentication ticket used on one server can still be valid on another server

For more information and sample Visual Basic code for generating random key values see http

msdnmicrosoftcomen-uslibraryms998288aspx

3 After Installing Planning and Consolidation Servers

33 Configuring the Planning and Consolidation NET Application Servers

2012-06-13 CUSTOMER 2954

paght000007_webfarmdeploymentconsiderations and httpmsdnmicrosoftcomen-us

libraryms998310aspx

34 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 30]

2 Configure custom ODBC logging for the default Web site For details of how to configure custom

logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page

31]

3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC Data

Source [page 32]

4 Modify the default access rights to the Management Console By default users in Active Directory

can access the Management Console with whatever rights they have been granted on the server

For information about removing default access and creating a group that can access the console

see Removing Default Access to the Console [page 32]

5 Add authorized users or groups to the group that can access the Management Console We

recommend that you only grant Management Console access to system administrators Planning

and Consolidation users should not have any access For more information see Management Console

Access Control [page 33]

6 Configure the use of client certificates for authentication See Using Client Certificates [page 34]

341 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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3054 CUSTOMER 2012-06-13

NOTE

Without these updates the Management Console does work but some functionality (specifically

User Activity and Service Status) does not work as expected

Should you need to uninstall Planning and Consolidation we recommend that you reset the

Active Log Format field in IIS to W3C Extended Log File Format

342 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 ApplicationHostconfig set the property customLogPluginClsid to the value FF16065B-

DE82-11CF-BC0A-00AA006111E0 Set the logFormat to Custom You can find this in the ltlogFilegt

node in ApplicationHostconfig as shown here

ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0

logFormat=Custom gt

Use the following AppCmds to configure IIS to use ODBC logging for the default Web site

appcmd site set sitenameDefault Web Site

logFilecustomLogPluginClsidFF16065B-DE82-11CF-BC0A-00AA006111E0

appcmd site set sitenameDefault Web Site logFilelogFormatCustom

Configuring ODBC Logging Parameters in ApplicationHostconfig

Configure ApplicationHostconfig to contain the database table information as set up in the Microsoft

Support article specified in the Prerequisites section Configure these settings in the ltodbcLogginggt

node under ltsystemwebServergt

EXAMPLE

ltlocation path=Default Web Sitegt

ltsystemwebServergt

ltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog

userName=Username password=mypassword gt

ltsystemwebServergt

ltlocationgt

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3154

Use the following AppCmds to configure these attributes for the default Web site

appcmd set config Default Web Site sectionodbcLogging

dataSourceBPC_ManagementDSN commitappHost

appcmd set config Default Web Site sectionodbcLogging tableNameBPCLog

commitappHost

appcmd set config Default Web Site sectionodbcLogging userNameUsername

commitappHost

appcmd set config Default Web Site sectionodbcLogging passwordmypassword

commitappHost

NOTE

You cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must

use the SQL Server ODBC driver For more information see the Microsoft Knowledge Base article

931202 The requirements for using the ODBC logging feature in IIS

343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2

ProcedureThis procedure describes how to set up an ODBC data source for the Management Console in Windows

Server 2008 or Windows Server 2008 R2

Proceed as follows

1 Open ODBC Connection Manager

2 On the System DSN tab page add a new DSN

Choose Add

Choose SQL Server as the driver

Choose Finish

3 In the Name and Description fields enter BPC_ManagementDSN

4 In the Server field enter the name of your SQL Server Choose Next

5 Leave the default settings and choose Next

6 Choose the Change the default database to field and enter AppServer Choose Next

7 Leave default settings and choose Next

8 Choose OK

344 Removing Default Access to the Console

NOTE

If you have chosen SAP BusinessObjects User Management System in the installation screen you

do not need to remove or configure access because the Management Console service always runs

with the System Admin ID account which is a member of the Administrators group

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3254 CUSTOMER 2012-06-13

ProcedureTo remove default access to the Management Console and create a group that does have access to the

console use the procedure described below

NOTE

Create your Management Console administrative group either on the server that hosts the

Management Console or in the Active Directory

1 In the context menu of the servers My Computer icon choose Manage

2 In the Computer Management dialog box choose Local Users and Groups Groups

NOTE

Alternatively you can perform analogous steps in Active Directory

3 In the 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

NOTE

This step is a necessary precursor to the completion of this procedure

10 In the Security dialog box click Copy to ensure that the System group retains its privileges

11 Remove access to the Management Console from all groups that should not have it

12 Choose Authentication in the center pane then disable Windows authentication

ResultUsers who have not been granted access to the Management Console can still open the Management

Console Web page but it contains no data or menu options This does not affect the access that a user

would otherwise have to Planning and Consolidation

345 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 32] Their rights in

Active Directory determine what they can access in the Console

By default any member of the Administrators Active Directory group on the application server or

domain has full access to all of the features of the Console except the Planning and Consolidation

logging area Access to Planning and Consolidation logging is controlled within the Planning and

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3354

Consolidation Administration Client task security The user must be granted View system logs task

privileges For more information see the SAP Library Planning and Consolidation Administrators Guide in

httpservicesapcominstguidesepm-bpc 100 version for the Microsoft platform

Your IT policy determines whether you grant access by group or user You may wish to create several

levels of Console users (read-only users for example) in your environment

To grant or limit access to users or groups you can add or remove the following privileges from the

areas described in this table

Privilege Rights Management Area

Task Manager and Kill Process Administrators group on application server or domain

Performance Monitor Counters Administrators group on application server or domain Power Users group on application server or domain Performance Monitor Users group on application server

Microsoft Analysis Services performance monitoring

Administrators group on application server or domain

Microsoft SQL Server Monitoring (performance counters and statistics)

Administrators group on application server or domain

346 Using Client Certificates

To enable the use of client certificates in Planning and Consolidation you must follow several manual

steps

NOTE

Planning 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 httptechnetmicrosoftcomen-us

librarycc753810aspx

For more information about configuring the client certificate mapping authentication see http

technetmicrosoftcomen-uslibrarycc732996(WS10)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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3454 CUSTOMER 2012-06-13

This option allows you to use a client certificate or username and password (Basic

authentication) to connect to Planning and Consolidation

2 Enable anonymous authentication

1 In the IIS Manager expand the node of the Planning and Consolidation web site

2 Select the ManagementConsole directory (ltWebsitegtManagementConsole) to open the

ManagementConsole home page

3 Double-click Authentication and enable Anonymous Authentication

4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way

as in step 3

5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the same

way as in step 3

3 Change the web configuration settings

1 Open the ltPC_MSgtWebsrvrWebBPCwebconfig file

2 Find the text clientCredentialType=Windows

3 Change value of clientCredentialType to None (clientCredentialType=None)

4 Open the PC_MSWebsrvrWebPOASBCwebconfig file Repeat steps 2 and 3

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3554

This page is left blank for documents that are printed on both sides

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

The installation of the Planning and Consolidation Administration Client allows administrators to

build and maintain Planning and Consolidation environments and models and administer security

All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions

add-in for Microsoft Office for more information see the SAP BusinessObjects EPM solutions add-in for

Microsoft Office help

NOTE

You must update the Administration Client to the same version as the server

If your PC is on a different domain than your server you must set the Internet Explorer

Security Zone value of the Planning and Consolidation client to prompt for user name and

password Otherwise the Planning and Consolidation Start Page does not display

41 Installing the Administration Client

Prerequisites

NOTE

For a definitive list of system requirements see the Product Availability Matrix on SAP Service

Marketplace at httpservicesapcompam Search on Planning and Consolidation

The following list describes the minimum software requirements

Microsoft Internet Explorer 70 or 80

Microsoft Office 2007 or 2010

NET Framework 20 or higher (install any required NET Framework Hotfixes by referring to

httpsupportmicrosoftcomkb)

Pentium IV (1 GHz CPU)

512 MB RAM

100 MB of free hard disk space in the My Documents folder

20 MB of free hard disk space for the installed Administration files

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

41 Installing the Administration Client

2012-06-13 CUSTOMER 3754

NOTE

We recommend that you install all of the latest Microsoft Windows hotfixes prior to installing

the Administration client For information about which hotfixes to install see http

updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us

ProcedureThe following procedure describes how to install the Administration Client on to an administratorrsquos

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 AddRemove Programs in the Windows Control Panel

3 Point your browser to the Planning and Consolidation Web at httpltPC_serverportgtsap

bpcweb

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

42 Installing the EPM Add-in

The Planning and Consolidation installation media does not contain the EPM addin setup program

You must download the most recent version of the full setup (EPM Add-inexe) from the Service

Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPC

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

43 Using the Client Auto Update Program

If Planning and Consolidation version 100 or later is installed you can use the Client Auto Update

program to set up the server so that it determines if an upgrade for a connecting Administration client

is necessary

The following describes the use of the auto update program for the Administration Client and the EPM

add-in

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

42 Installing the EPM Add-in

3854 CUSTOMER 2012-06-13

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 37]

To use the Client Auto Update program for the Administration Client proceed as follows

1 From the Server Manager select Options Client Options

2 Select Admin Update

3 If users without administrator rights on their machines use the auto update enter an administrator

ID and password in the Admin ID and Admin password fields respectively The Admin ID should be a

member of the local administrators group on all the computers running the auto update This

setting is not needed if all users have administrator rights on their machines

4 Select Update

For the EPM Add-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 Optionshellip 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 Market Place (SMP) at httpservicesapcom

All support packages and patches are available from the SMP as a zip file

EPMEXCLCLNTltSPLgtzip is for a support package

EPMEXCLCLNTltSPLgtPltPLgtzip 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 ltSP versiongtmsp

EPM Addin Support Package ltSP versiongtxml

For a patch these files are

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

2012-06-13 CUSTOMER 3954

EPM Addin Patch ltpatch numbergtmsp

EPM Addin Patch ltpatch numbergtxml

2 Unzip the zip file and extract the two files to the application server folder (WebsrvrWebBPC

Installation)

3 From the Server Manager select Options Client Options

The system lists the available packages Select the package that you want to use for the autoupdate

You can set a different update policy for each package listed

EXAMPLE

The following table illustrates some possible situations assuming that you have installed the

first full version (V1)

Available maintenance packages

V2-user updateV3-force updateV4-force updateV5-user update

V5-user update V5-user updateV6-auto updateV7-force update

Minimum Required Version

V4 V4 V7

Notification A prompt tells the user to install maintenance package V4 using the Forced Update behavior

If User Update is enabled the prompt informs the user that maintenance package V5 is available

A prompt tells the user to install maintenance package V7 using the Forced Update behavior

New Version V4 V4 or V5 V7

If you change the update policy for any package click Update to complete the change

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

4054 CUSTOMER 2012-06-13

5 Connection Issues

You may experience connection problems with ports the proxy server or programs and settings that

interact with these components If you have any issues related to connection review the following

recommendations and troubleshooting tips

51 Checking for Open Ports

You must ensure that all required ports are open for inboundoutbound 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 431181836 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

NOTE

You can use the following site to scan for the normal ports It allows you to manually enter a port

number to test

httpwwwmyserverorgportsniffasp

You can change the name of a port

52 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 Explorer Tools Internet Options Connections LAN Settings ) or at the server level

Enabling content filtering on the proxy server or firewall may cause connection problems

If external users are having trouble connecting to the server make sure the proxy server connects

using a fully qualified domain name Fully qualified domain names typically resolve both internal

and external IP addresses

Each secure Planning and Consolidation server name must be identified on the proxy server

Proxy servers may or may not require authentication which could conflict with Planning and

Consolidation authentication Do not use authentication on the proxy server The system

5 Connection Issues

51 Checking for Open Ports

2012-06-13 CUSTOMER 4154

synchronizes the user name and password on the remote server with the local user name and

password

NOTE

For more information about setting up an ISA proxy server contact SAP Support to request a

copy of Setting up ISA Proxy Server White Paper

Internet Explorer Settings 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

5 Connection Issues

52 Proxy Server and Firewall Issues

4254 CUSTOMER 2012-06-13

6 Installing Planning and Consolidation with Two Active Directory Domains

To set up a Planning and Consolidation 10 application server in a hosted environment and use your

own domain users follow this procedure In general you install Planning and Consolidation on the

host domain use the host domain account and assign it to the Planning and Consolidation users

SysAdmin Admin and Users Then you accept one way trust (the host domain trusts your domain)

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

6 Installing Planning and Consolidation with Two Active Directory Domains

2012-06-13 CUSTOMER 4354

This page is left blank for documents that are printed on both sides

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

This section describes best practices and instructions for installing Planning and Consolidation in a

Terminal Services or Citrix Server deployment

71 Terminal Services Home Directories

We recommend using Terminal Server home directories rather than using the userrsquos 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

72 System Requirements

The Citrix server should be one of the following systems

XenApp 5 Enterprise

XenApp 5 Platinum

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 37])

73 Installing Planning and Consolidation

Prerequisites

The server installation files have been downloaded from SAP Service Marketplace and installed

Procedure

The following steps outline how to install the Planning and Consolidation clients in a Terminal Services

(TS) or Citrix Server deployment

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

71 Terminal Services Home Directories

2012-06-13 CUSTOMER 4554

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 userinstall

4 Open a browser and connect to the URL httpltPC_serverportgtsapbpcweb

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 userexecute 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 Iexploreexe http(s)

ltServerNamegt-NetBIOS or FQDNsapbpcweb

To publish Planning and Consolidation Administration CProgram FilesPC_MS

BPCAdminMainexe

74 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 userrsquos desktop) must be moved to the All UsersDesktop folder

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

74 Creating a Shortcut to the Launch Page

4654 CUSTOMER 2012-06-13

8 Installing SSIS Custom Tasks

This section provides background information and instructions for installing SQL Server Integration

Services (SSIS) for SQL Server 2008 and SQL Server 2012

The Planning and Consolidation Data Manager component supports and uses SSIS Since SQL Server

2008 and SQL Server 2012 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

81 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 Filelistxml 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

OSoftSetupexe ‒ 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 or OSoftSSIS2012_Client on the client machine followed by the SQL Server

version If you want to use SQL 2008 Tasks under the SQL 2012 environment you must install

OSoftSSIS2008_Client on the application server For detailed information see SAP Note 1707410

You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package by extracting

OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPC

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 or

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4754

OSoftSSIS2012_Client for creating a COM+ application For more information see Before You Modify

the SSIS Packages [page 50] and Setup of a COM+ Application on the Application Server [page 51]

Bin folder

This folder contains the following components

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCCachedll Planning and Consolidation Cache file

BPCDataFlowPackagedll or BPCDataFlowPackage2012dll

BPCDMdll

BPCDMTaskMaindll COM+ component

BPCFilePreviewdll

BPCGacUtil_20exe System File

BPCGacUtil_40exe System File

BPCImpersonatordll Planning and Consolidation Impersonator

BPCLogicdll

BPCScriptdll

BPCServerZipdll

BPCServiceResdll

BPCTransferMembersdll

BPCWriteBackdll

InteropDTSdll

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

4854 CUSTOMER 2012-06-13

Name Remark

OSoftAdminServerdll

OSoftAuditdll

OSoftComLibServerdll

OSoftCommonResQrydll

OSoftConfigurationdll

OSoftCustomXMLSvrdll

OSoftDatabaseADMINdll

OSoftDatabaseSYSADMINdll

OSoftDatabaseSYSADMINDMdll

OSoftDatabaseUSERdll

OSoftDMDTSXExecutedll or OSoftDMDTSXExecute2012dll

OSoftDMTaskFormdll

OSoftDMTaskMaindll

OSoftDMToolsdll

OSoftFileManagedll

OSoftLoggingdll

OSoftLogWriterdll

OSoftMetaDatadll

OSoftSQEdll

OSoftSystemConfigdll

OutlookSoftconfig Configuration file to connect DB server

XceedCompressiondll XceedZip file

XceedCompressionFormatsdll XceedZip file

XceedFileSystemdll XceedZip file

XceedZipdll XceedZip file

Config folder

This folder has FileListxml 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 FileListxml 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

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4954

OSoftSetupexe

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

NOTE

If you installed the OSoftSSIS2008_Client or OSoftSSIS2012_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

Resources Folder

This folder contains the BPCServicesdll and BPCServiceUIdll files which contain resource text

Only English resources are included for the SSIS custom tasks

82 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

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008 and 2012 respectively

8 Installing SSIS Custom Tasks

82 Before You Modify the SSIS Packages

5054 CUSTOMER 2012-06-13

Name Remark

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012 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

lthellipgtOSoftSSIS2008_Clientbin or lthellipgtOSoftSSIS2012_Clientbin

On the Planning and Consolidation application server

ltdrivegtWebsrvrbin

2 Paste these files into the folder 100DTSTasks for SQL Server 2008 or into 110DTSTasks for

SQL Server 2012 For example if you install your SQL 2008 server or R2 on CProgram Files

Microsoft SQL Server paste all files into the CProgram Files (x86)Microsoft SQL Server

100DTSTasks folder

In Integration Services set the property Run64BitRunTime to True

83 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 or OSoftSSIS2012_Client on the

application server

8 Installing SSIS Custom Tasks

83 Setup of a COM+ Application on the Application Server

2012-06-13 CUSTOMER 5154

Typographic Conventions

Example Description

ltgt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example Enter your ltUser Namegt

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 httpwwwsapcom

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

5254 CUSTOMER 2012-06-13

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

  • SAP BusinessObjects Planning and Consolidation 100
    • Table of Contents
    • 1 Introduction
      • 11 SAP Notes for the Installation
      • 12 Naming Conventions
        • 2 Installing Planning and Consolidation Servers
          • 21 Basic Steps
          • 22 Prerequisites
          • 23 Before Starting the Planning and Consolidation Server Installation
          • 24 Logging on to Servers
          • 25 Service-level Accounts
          • 26 Standard and Advanced Settings
          • 27 Installing the Prerequisites
            • 271 Installing the Prerequisites ndash Basic Steps
            • 272 Installing the Operating System
            • 273 Installing the SQL Server
            • 274 Installing Analysis Services
            • 275 Installing the Anti-Cross Site Scripting Library
              • 28 Installing on a Single Server
              • 29 Installing the Server in a Multiserver Configuration
                • 3 After Installing Planning and Consolidation Servers
                  • 31 Post-Installation Steps
                  • 32 Connecting to Solution Manager Diagnostics
                  • 33 Configuring the Planning and Consolidation NET Application Servers
                  • 34 Post-Installation Optional Configuration Steps
                    • 341 Enabling the Management Console
                    • 342 Setting Up ODBC Logging in IIS for the Default Web Site
                    • 343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2
                    • 344 Removing Default Access to the Console
                    • 345 Management Console Access Control
                    • 346 Using Client Certificates
                        • 4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office
                          • 41 Installing the Administration Client
                          • 42 Installing the EPM Add-in
                          • 43 Using the Client Auto Update Program
                            • 5 Connection Issues
                              • 51 Checking for Open Ports
                              • 52 Proxy Server and Firewall Issues
                                • 6 Installing Planning and Consolidation with Two Active Directory Domains
                                • 7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
                                  • 71 Terminal Services Home Directories
                                  • 72 System Requirements
                                  • 73 Installing Planning and Consolidation
                                  • 74 Creating a Shortcut to the Launch Page
                                    • 8 Installing SSIS Custom Tasks
                                      • 81 Composition of SSIS Custom Task Installation
                                      • 82 Before You Modify the SSIS Packages
                                      • 83 Setup of a COM+ Application on the Application Server
                                          • Copyright and trademarks
Page 29: Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

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 SQLServerltReleasegtSQLAgentUser$ltDomain or hostnamegt$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 httpsservicesapcom~sapidb011000358700000074392009E and follow

the chapters that apply to Planning and Consolidation

33 Configuring the Planning and Consolidation NET Application Servers

Procedure

Modifying machineconfig Files

To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock

occurrences that would cause the application server to ldquosleeprdquo and not process anymore you can

modify the machineconfig file which resides in the WINDOWSMicrosoftNETFramework64

v4030319Config directory

1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to

specify whether to automatically configure settings to achieve optimal performance based on the

machine configuration You can set this attribute to True or False

For more information see httpmsdnmicrosoftcomen-uslibrary7w2sway1aspx

2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the

Planning and Consolidation application) or Machineconfig (for all applications including

Planning and Consolidation) to ensure the validationKey and decryptionKey keys have the same

value on all application servers This way when the authentication cookie is checked the

authentication ticket used on one server can still be valid on another server

For more information and sample Visual Basic code for generating random key values see http

msdnmicrosoftcomen-uslibraryms998288aspx

3 After Installing Planning and Consolidation Servers

33 Configuring the Planning and Consolidation NET Application Servers

2012-06-13 CUSTOMER 2954

paght000007_webfarmdeploymentconsiderations and httpmsdnmicrosoftcomen-us

libraryms998310aspx

34 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 30]

2 Configure custom ODBC logging for the default Web site For details of how to configure custom

logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page

31]

3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC Data

Source [page 32]

4 Modify the default access rights to the Management Console By default users in Active Directory

can access the Management Console with whatever rights they have been granted on the server

For information about removing default access and creating a group that can access the console

see Removing Default Access to the Console [page 32]

5 Add authorized users or groups to the group that can access the Management Console We

recommend that you only grant Management Console access to system administrators Planning

and Consolidation users should not have any access For more information see Management Console

Access Control [page 33]

6 Configure the use of client certificates for authentication See Using Client Certificates [page 34]

341 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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3054 CUSTOMER 2012-06-13

NOTE

Without these updates the Management Console does work but some functionality (specifically

User Activity and Service Status) does not work as expected

Should you need to uninstall Planning and Consolidation we recommend that you reset the

Active Log Format field in IIS to W3C Extended Log File Format

342 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 ApplicationHostconfig set the property customLogPluginClsid to the value FF16065B-

DE82-11CF-BC0A-00AA006111E0 Set the logFormat to Custom You can find this in the ltlogFilegt

node in ApplicationHostconfig as shown here

ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0

logFormat=Custom gt

Use the following AppCmds to configure IIS to use ODBC logging for the default Web site

appcmd site set sitenameDefault Web Site

logFilecustomLogPluginClsidFF16065B-DE82-11CF-BC0A-00AA006111E0

appcmd site set sitenameDefault Web Site logFilelogFormatCustom

Configuring ODBC Logging Parameters in ApplicationHostconfig

Configure ApplicationHostconfig to contain the database table information as set up in the Microsoft

Support article specified in the Prerequisites section Configure these settings in the ltodbcLogginggt

node under ltsystemwebServergt

EXAMPLE

ltlocation path=Default Web Sitegt

ltsystemwebServergt

ltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog

userName=Username password=mypassword gt

ltsystemwebServergt

ltlocationgt

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3154

Use the following AppCmds to configure these attributes for the default Web site

appcmd set config Default Web Site sectionodbcLogging

dataSourceBPC_ManagementDSN commitappHost

appcmd set config Default Web Site sectionodbcLogging tableNameBPCLog

commitappHost

appcmd set config Default Web Site sectionodbcLogging userNameUsername

commitappHost

appcmd set config Default Web Site sectionodbcLogging passwordmypassword

commitappHost

NOTE

You cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must

use the SQL Server ODBC driver For more information see the Microsoft Knowledge Base article

931202 The requirements for using the ODBC logging feature in IIS

343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2

ProcedureThis procedure describes how to set up an ODBC data source for the Management Console in Windows

Server 2008 or Windows Server 2008 R2

Proceed as follows

1 Open ODBC Connection Manager

2 On the System DSN tab page add a new DSN

Choose Add

Choose SQL Server as the driver

Choose Finish

3 In the Name and Description fields enter BPC_ManagementDSN

4 In the Server field enter the name of your SQL Server Choose Next

5 Leave the default settings and choose Next

6 Choose the Change the default database to field and enter AppServer Choose Next

7 Leave default settings and choose Next

8 Choose OK

344 Removing Default Access to the Console

NOTE

If you have chosen SAP BusinessObjects User Management System in the installation screen you

do not need to remove or configure access because the Management Console service always runs

with the System Admin ID account which is a member of the Administrators group

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3254 CUSTOMER 2012-06-13

ProcedureTo remove default access to the Management Console and create a group that does have access to the

console use the procedure described below

NOTE

Create your Management Console administrative group either on the server that hosts the

Management Console or in the Active Directory

1 In the context menu of the servers My Computer icon choose Manage

2 In the Computer Management dialog box choose Local Users and Groups Groups

NOTE

Alternatively you can perform analogous steps in Active Directory

3 In the 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

NOTE

This step is a necessary precursor to the completion of this procedure

10 In the Security dialog box click Copy to ensure that the System group retains its privileges

11 Remove access to the Management Console from all groups that should not have it

12 Choose Authentication in the center pane then disable Windows authentication

ResultUsers who have not been granted access to the Management Console can still open the Management

Console Web page but it contains no data or menu options This does not affect the access that a user

would otherwise have to Planning and Consolidation

345 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 32] Their rights in

Active Directory determine what they can access in the Console

By default any member of the Administrators Active Directory group on the application server or

domain has full access to all of the features of the Console except the Planning and Consolidation

logging area Access to Planning and Consolidation logging is controlled within the Planning and

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3354

Consolidation Administration Client task security The user must be granted View system logs task

privileges For more information see the SAP Library Planning and Consolidation Administrators Guide in

httpservicesapcominstguidesepm-bpc 100 version for the Microsoft platform

Your IT policy determines whether you grant access by group or user You may wish to create several

levels of Console users (read-only users for example) in your environment

To grant or limit access to users or groups you can add or remove the following privileges from the

areas described in this table

Privilege Rights Management Area

Task Manager and Kill Process Administrators group on application server or domain

Performance Monitor Counters Administrators group on application server or domain Power Users group on application server or domain Performance Monitor Users group on application server

Microsoft Analysis Services performance monitoring

Administrators group on application server or domain

Microsoft SQL Server Monitoring (performance counters and statistics)

Administrators group on application server or domain

346 Using Client Certificates

To enable the use of client certificates in Planning and Consolidation you must follow several manual

steps

NOTE

Planning 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 httptechnetmicrosoftcomen-us

librarycc753810aspx

For more information about configuring the client certificate mapping authentication see http

technetmicrosoftcomen-uslibrarycc732996(WS10)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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3454 CUSTOMER 2012-06-13

This option allows you to use a client certificate or username and password (Basic

authentication) to connect to Planning and Consolidation

2 Enable anonymous authentication

1 In the IIS Manager expand the node of the Planning and Consolidation web site

2 Select the ManagementConsole directory (ltWebsitegtManagementConsole) to open the

ManagementConsole home page

3 Double-click Authentication and enable Anonymous Authentication

4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way

as in step 3

5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the same

way as in step 3

3 Change the web configuration settings

1 Open the ltPC_MSgtWebsrvrWebBPCwebconfig file

2 Find the text clientCredentialType=Windows

3 Change value of clientCredentialType to None (clientCredentialType=None)

4 Open the PC_MSWebsrvrWebPOASBCwebconfig file Repeat steps 2 and 3

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3554

This page is left blank for documents that are printed on both sides

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

The installation of the Planning and Consolidation Administration Client allows administrators to

build and maintain Planning and Consolidation environments and models and administer security

All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions

add-in for Microsoft Office for more information see the SAP BusinessObjects EPM solutions add-in for

Microsoft Office help

NOTE

You must update the Administration Client to the same version as the server

If your PC is on a different domain than your server you must set the Internet Explorer

Security Zone value of the Planning and Consolidation client to prompt for user name and

password Otherwise the Planning and Consolidation Start Page does not display

41 Installing the Administration Client

Prerequisites

NOTE

For a definitive list of system requirements see the Product Availability Matrix on SAP Service

Marketplace at httpservicesapcompam Search on Planning and Consolidation

The following list describes the minimum software requirements

Microsoft Internet Explorer 70 or 80

Microsoft Office 2007 or 2010

NET Framework 20 or higher (install any required NET Framework Hotfixes by referring to

httpsupportmicrosoftcomkb)

Pentium IV (1 GHz CPU)

512 MB RAM

100 MB of free hard disk space in the My Documents folder

20 MB of free hard disk space for the installed Administration files

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

41 Installing the Administration Client

2012-06-13 CUSTOMER 3754

NOTE

We recommend that you install all of the latest Microsoft Windows hotfixes prior to installing

the Administration client For information about which hotfixes to install see http

updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us

ProcedureThe following procedure describes how to install the Administration Client on to an administratorrsquos

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 AddRemove Programs in the Windows Control Panel

3 Point your browser to the Planning and Consolidation Web at httpltPC_serverportgtsap

bpcweb

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

42 Installing the EPM Add-in

The Planning and Consolidation installation media does not contain the EPM addin setup program

You must download the most recent version of the full setup (EPM Add-inexe) from the Service

Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPC

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

43 Using the Client Auto Update Program

If Planning and Consolidation version 100 or later is installed you can use the Client Auto Update

program to set up the server so that it determines if an upgrade for a connecting Administration client

is necessary

The following describes the use of the auto update program for the Administration Client and the EPM

add-in

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

42 Installing the EPM Add-in

3854 CUSTOMER 2012-06-13

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 37]

To use the Client Auto Update program for the Administration Client proceed as follows

1 From the Server Manager select Options Client Options

2 Select Admin Update

3 If users without administrator rights on their machines use the auto update enter an administrator

ID and password in the Admin ID and Admin password fields respectively The Admin ID should be a

member of the local administrators group on all the computers running the auto update This

setting is not needed if all users have administrator rights on their machines

4 Select Update

For the EPM Add-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 Optionshellip 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 Market Place (SMP) at httpservicesapcom

All support packages and patches are available from the SMP as a zip file

EPMEXCLCLNTltSPLgtzip is for a support package

EPMEXCLCLNTltSPLgtPltPLgtzip 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 ltSP versiongtmsp

EPM Addin Support Package ltSP versiongtxml

For a patch these files are

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

2012-06-13 CUSTOMER 3954

EPM Addin Patch ltpatch numbergtmsp

EPM Addin Patch ltpatch numbergtxml

2 Unzip the zip file and extract the two files to the application server folder (WebsrvrWebBPC

Installation)

3 From the Server Manager select Options Client Options

The system lists the available packages Select the package that you want to use for the autoupdate

You can set a different update policy for each package listed

EXAMPLE

The following table illustrates some possible situations assuming that you have installed the

first full version (V1)

Available maintenance packages

V2-user updateV3-force updateV4-force updateV5-user update

V5-user update V5-user updateV6-auto updateV7-force update

Minimum Required Version

V4 V4 V7

Notification A prompt tells the user to install maintenance package V4 using the Forced Update behavior

If User Update is enabled the prompt informs the user that maintenance package V5 is available

A prompt tells the user to install maintenance package V7 using the Forced Update behavior

New Version V4 V4 or V5 V7

If you change the update policy for any package click Update to complete the change

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

4054 CUSTOMER 2012-06-13

5 Connection Issues

You may experience connection problems with ports the proxy server or programs and settings that

interact with these components If you have any issues related to connection review the following

recommendations and troubleshooting tips

51 Checking for Open Ports

You must ensure that all required ports are open for inboundoutbound 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 431181836 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

NOTE

You can use the following site to scan for the normal ports It allows you to manually enter a port

number to test

httpwwwmyserverorgportsniffasp

You can change the name of a port

52 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 Explorer Tools Internet Options Connections LAN Settings ) or at the server level

Enabling content filtering on the proxy server or firewall may cause connection problems

If external users are having trouble connecting to the server make sure the proxy server connects

using a fully qualified domain name Fully qualified domain names typically resolve both internal

and external IP addresses

Each secure Planning and Consolidation server name must be identified on the proxy server

Proxy servers may or may not require authentication which could conflict with Planning and

Consolidation authentication Do not use authentication on the proxy server The system

5 Connection Issues

51 Checking for Open Ports

2012-06-13 CUSTOMER 4154

synchronizes the user name and password on the remote server with the local user name and

password

NOTE

For more information about setting up an ISA proxy server contact SAP Support to request a

copy of Setting up ISA Proxy Server White Paper

Internet Explorer Settings 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

5 Connection Issues

52 Proxy Server and Firewall Issues

4254 CUSTOMER 2012-06-13

6 Installing Planning and Consolidation with Two Active Directory Domains

To set up a Planning and Consolidation 10 application server in a hosted environment and use your

own domain users follow this procedure In general you install Planning and Consolidation on the

host domain use the host domain account and assign it to the Planning and Consolidation users

SysAdmin Admin and Users Then you accept one way trust (the host domain trusts your domain)

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

6 Installing Planning and Consolidation with Two Active Directory Domains

2012-06-13 CUSTOMER 4354

This page is left blank for documents that are printed on both sides

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

This section describes best practices and instructions for installing Planning and Consolidation in a

Terminal Services or Citrix Server deployment

71 Terminal Services Home Directories

We recommend using Terminal Server home directories rather than using the userrsquos 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

72 System Requirements

The Citrix server should be one of the following systems

XenApp 5 Enterprise

XenApp 5 Platinum

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 37])

73 Installing Planning and Consolidation

Prerequisites

The server installation files have been downloaded from SAP Service Marketplace and installed

Procedure

The following steps outline how to install the Planning and Consolidation clients in a Terminal Services

(TS) or Citrix Server deployment

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

71 Terminal Services Home Directories

2012-06-13 CUSTOMER 4554

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 userinstall

4 Open a browser and connect to the URL httpltPC_serverportgtsapbpcweb

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 userexecute 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 Iexploreexe http(s)

ltServerNamegt-NetBIOS or FQDNsapbpcweb

To publish Planning and Consolidation Administration CProgram FilesPC_MS

BPCAdminMainexe

74 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 userrsquos desktop) must be moved to the All UsersDesktop folder

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

74 Creating a Shortcut to the Launch Page

4654 CUSTOMER 2012-06-13

8 Installing SSIS Custom Tasks

This section provides background information and instructions for installing SQL Server Integration

Services (SSIS) for SQL Server 2008 and SQL Server 2012

The Planning and Consolidation Data Manager component supports and uses SSIS Since SQL Server

2008 and SQL Server 2012 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

81 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 Filelistxml 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

OSoftSetupexe ‒ 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 or OSoftSSIS2012_Client on the client machine followed by the SQL Server

version If you want to use SQL 2008 Tasks under the SQL 2012 environment you must install

OSoftSSIS2008_Client on the application server For detailed information see SAP Note 1707410

You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package by extracting

OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPC

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 or

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4754

OSoftSSIS2012_Client for creating a COM+ application For more information see Before You Modify

the SSIS Packages [page 50] and Setup of a COM+ Application on the Application Server [page 51]

Bin folder

This folder contains the following components

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCCachedll Planning and Consolidation Cache file

BPCDataFlowPackagedll or BPCDataFlowPackage2012dll

BPCDMdll

BPCDMTaskMaindll COM+ component

BPCFilePreviewdll

BPCGacUtil_20exe System File

BPCGacUtil_40exe System File

BPCImpersonatordll Planning and Consolidation Impersonator

BPCLogicdll

BPCScriptdll

BPCServerZipdll

BPCServiceResdll

BPCTransferMembersdll

BPCWriteBackdll

InteropDTSdll

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

4854 CUSTOMER 2012-06-13

Name Remark

OSoftAdminServerdll

OSoftAuditdll

OSoftComLibServerdll

OSoftCommonResQrydll

OSoftConfigurationdll

OSoftCustomXMLSvrdll

OSoftDatabaseADMINdll

OSoftDatabaseSYSADMINdll

OSoftDatabaseSYSADMINDMdll

OSoftDatabaseUSERdll

OSoftDMDTSXExecutedll or OSoftDMDTSXExecute2012dll

OSoftDMTaskFormdll

OSoftDMTaskMaindll

OSoftDMToolsdll

OSoftFileManagedll

OSoftLoggingdll

OSoftLogWriterdll

OSoftMetaDatadll

OSoftSQEdll

OSoftSystemConfigdll

OutlookSoftconfig Configuration file to connect DB server

XceedCompressiondll XceedZip file

XceedCompressionFormatsdll XceedZip file

XceedFileSystemdll XceedZip file

XceedZipdll XceedZip file

Config folder

This folder has FileListxml 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 FileListxml 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

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4954

OSoftSetupexe

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

NOTE

If you installed the OSoftSSIS2008_Client or OSoftSSIS2012_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

Resources Folder

This folder contains the BPCServicesdll and BPCServiceUIdll files which contain resource text

Only English resources are included for the SSIS custom tasks

82 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

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008 and 2012 respectively

8 Installing SSIS Custom Tasks

82 Before You Modify the SSIS Packages

5054 CUSTOMER 2012-06-13

Name Remark

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012 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

lthellipgtOSoftSSIS2008_Clientbin or lthellipgtOSoftSSIS2012_Clientbin

On the Planning and Consolidation application server

ltdrivegtWebsrvrbin

2 Paste these files into the folder 100DTSTasks for SQL Server 2008 or into 110DTSTasks for

SQL Server 2012 For example if you install your SQL 2008 server or R2 on CProgram Files

Microsoft SQL Server paste all files into the CProgram Files (x86)Microsoft SQL Server

100DTSTasks folder

In Integration Services set the property Run64BitRunTime to True

83 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 or OSoftSSIS2012_Client on the

application server

8 Installing SSIS Custom Tasks

83 Setup of a COM+ Application on the Application Server

2012-06-13 CUSTOMER 5154

Typographic Conventions

Example Description

ltgt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example Enter your ltUser Namegt

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 httpwwwsapcom

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

5254 CUSTOMER 2012-06-13

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

  • SAP BusinessObjects Planning and Consolidation 100
    • Table of Contents
    • 1 Introduction
      • 11 SAP Notes for the Installation
      • 12 Naming Conventions
        • 2 Installing Planning and Consolidation Servers
          • 21 Basic Steps
          • 22 Prerequisites
          • 23 Before Starting the Planning and Consolidation Server Installation
          • 24 Logging on to Servers
          • 25 Service-level Accounts
          • 26 Standard and Advanced Settings
          • 27 Installing the Prerequisites
            • 271 Installing the Prerequisites ndash Basic Steps
            • 272 Installing the Operating System
            • 273 Installing the SQL Server
            • 274 Installing Analysis Services
            • 275 Installing the Anti-Cross Site Scripting Library
              • 28 Installing on a Single Server
              • 29 Installing the Server in a Multiserver Configuration
                • 3 After Installing Planning and Consolidation Servers
                  • 31 Post-Installation Steps
                  • 32 Connecting to Solution Manager Diagnostics
                  • 33 Configuring the Planning and Consolidation NET Application Servers
                  • 34 Post-Installation Optional Configuration Steps
                    • 341 Enabling the Management Console
                    • 342 Setting Up ODBC Logging in IIS for the Default Web Site
                    • 343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2
                    • 344 Removing Default Access to the Console
                    • 345 Management Console Access Control
                    • 346 Using Client Certificates
                        • 4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office
                          • 41 Installing the Administration Client
                          • 42 Installing the EPM Add-in
                          • 43 Using the Client Auto Update Program
                            • 5 Connection Issues
                              • 51 Checking for Open Ports
                              • 52 Proxy Server and Firewall Issues
                                • 6 Installing Planning and Consolidation with Two Active Directory Domains
                                • 7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
                                  • 71 Terminal Services Home Directories
                                  • 72 System Requirements
                                  • 73 Installing Planning and Consolidation
                                  • 74 Creating a Shortcut to the Launch Page
                                    • 8 Installing SSIS Custom Tasks
                                      • 81 Composition of SSIS Custom Task Installation
                                      • 82 Before You Modify the SSIS Packages
                                      • 83 Setup of a COM+ Application on the Application Server
                                          • Copyright and trademarks
Page 30: Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

paght000007_webfarmdeploymentconsiderations and httpmsdnmicrosoftcomen-us

libraryms998310aspx

34 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 30]

2 Configure custom ODBC logging for the default Web site For details of how to configure custom

logging for ODBC in IIS 70 or 75 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page

31]

3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC Data

Source [page 32]

4 Modify the default access rights to the Management Console By default users in Active Directory

can access the Management Console with whatever rights they have been granted on the server

For information about removing default access and creating a group that can access the console

see Removing Default Access to the Console [page 32]

5 Add authorized users or groups to the group that can access the Management Console We

recommend that you only grant Management Console access to system administrators Planning

and Consolidation users should not have any access For more information see Management Console

Access Control [page 33]

6 Configure the use of client certificates for authentication See Using Client Certificates [page 34]

341 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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3054 CUSTOMER 2012-06-13

NOTE

Without these updates the Management Console does work but some functionality (specifically

User Activity and Service Status) does not work as expected

Should you need to uninstall Planning and Consolidation we recommend that you reset the

Active Log Format field in IIS to W3C Extended Log File Format

342 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 ApplicationHostconfig set the property customLogPluginClsid to the value FF16065B-

DE82-11CF-BC0A-00AA006111E0 Set the logFormat to Custom You can find this in the ltlogFilegt

node in ApplicationHostconfig as shown here

ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0

logFormat=Custom gt

Use the following AppCmds to configure IIS to use ODBC logging for the default Web site

appcmd site set sitenameDefault Web Site

logFilecustomLogPluginClsidFF16065B-DE82-11CF-BC0A-00AA006111E0

appcmd site set sitenameDefault Web Site logFilelogFormatCustom

Configuring ODBC Logging Parameters in ApplicationHostconfig

Configure ApplicationHostconfig to contain the database table information as set up in the Microsoft

Support article specified in the Prerequisites section Configure these settings in the ltodbcLogginggt

node under ltsystemwebServergt

EXAMPLE

ltlocation path=Default Web Sitegt

ltsystemwebServergt

ltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog

userName=Username password=mypassword gt

ltsystemwebServergt

ltlocationgt

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3154

Use the following AppCmds to configure these attributes for the default Web site

appcmd set config Default Web Site sectionodbcLogging

dataSourceBPC_ManagementDSN commitappHost

appcmd set config Default Web Site sectionodbcLogging tableNameBPCLog

commitappHost

appcmd set config Default Web Site sectionodbcLogging userNameUsername

commitappHost

appcmd set config Default Web Site sectionodbcLogging passwordmypassword

commitappHost

NOTE

You cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must

use the SQL Server ODBC driver For more information see the Microsoft Knowledge Base article

931202 The requirements for using the ODBC logging feature in IIS

343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2

ProcedureThis procedure describes how to set up an ODBC data source for the Management Console in Windows

Server 2008 or Windows Server 2008 R2

Proceed as follows

1 Open ODBC Connection Manager

2 On the System DSN tab page add a new DSN

Choose Add

Choose SQL Server as the driver

Choose Finish

3 In the Name and Description fields enter BPC_ManagementDSN

4 In the Server field enter the name of your SQL Server Choose Next

5 Leave the default settings and choose Next

6 Choose the Change the default database to field and enter AppServer Choose Next

7 Leave default settings and choose Next

8 Choose OK

344 Removing Default Access to the Console

NOTE

If you have chosen SAP BusinessObjects User Management System in the installation screen you

do not need to remove or configure access because the Management Console service always runs

with the System Admin ID account which is a member of the Administrators group

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3254 CUSTOMER 2012-06-13

ProcedureTo remove default access to the Management Console and create a group that does have access to the

console use the procedure described below

NOTE

Create your Management Console administrative group either on the server that hosts the

Management Console or in the Active Directory

1 In the context menu of the servers My Computer icon choose Manage

2 In the Computer Management dialog box choose Local Users and Groups Groups

NOTE

Alternatively you can perform analogous steps in Active Directory

3 In the 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

NOTE

This step is a necessary precursor to the completion of this procedure

10 In the Security dialog box click Copy to ensure that the System group retains its privileges

11 Remove access to the Management Console from all groups that should not have it

12 Choose Authentication in the center pane then disable Windows authentication

ResultUsers who have not been granted access to the Management Console can still open the Management

Console Web page but it contains no data or menu options This does not affect the access that a user

would otherwise have to Planning and Consolidation

345 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 32] Their rights in

Active Directory determine what they can access in the Console

By default any member of the Administrators Active Directory group on the application server or

domain has full access to all of the features of the Console except the Planning and Consolidation

logging area Access to Planning and Consolidation logging is controlled within the Planning and

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3354

Consolidation Administration Client task security The user must be granted View system logs task

privileges For more information see the SAP Library Planning and Consolidation Administrators Guide in

httpservicesapcominstguidesepm-bpc 100 version for the Microsoft platform

Your IT policy determines whether you grant access by group or user You may wish to create several

levels of Console users (read-only users for example) in your environment

To grant or limit access to users or groups you can add or remove the following privileges from the

areas described in this table

Privilege Rights Management Area

Task Manager and Kill Process Administrators group on application server or domain

Performance Monitor Counters Administrators group on application server or domain Power Users group on application server or domain Performance Monitor Users group on application server

Microsoft Analysis Services performance monitoring

Administrators group on application server or domain

Microsoft SQL Server Monitoring (performance counters and statistics)

Administrators group on application server or domain

346 Using Client Certificates

To enable the use of client certificates in Planning and Consolidation you must follow several manual

steps

NOTE

Planning 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 httptechnetmicrosoftcomen-us

librarycc753810aspx

For more information about configuring the client certificate mapping authentication see http

technetmicrosoftcomen-uslibrarycc732996(WS10)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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3454 CUSTOMER 2012-06-13

This option allows you to use a client certificate or username and password (Basic

authentication) to connect to Planning and Consolidation

2 Enable anonymous authentication

1 In the IIS Manager expand the node of the Planning and Consolidation web site

2 Select the ManagementConsole directory (ltWebsitegtManagementConsole) to open the

ManagementConsole home page

3 Double-click Authentication and enable Anonymous Authentication

4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way

as in step 3

5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the same

way as in step 3

3 Change the web configuration settings

1 Open the ltPC_MSgtWebsrvrWebBPCwebconfig file

2 Find the text clientCredentialType=Windows

3 Change value of clientCredentialType to None (clientCredentialType=None)

4 Open the PC_MSWebsrvrWebPOASBCwebconfig file Repeat steps 2 and 3

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3554

This page is left blank for documents that are printed on both sides

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

The installation of the Planning and Consolidation Administration Client allows administrators to

build and maintain Planning and Consolidation environments and models and administer security

All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions

add-in for Microsoft Office for more information see the SAP BusinessObjects EPM solutions add-in for

Microsoft Office help

NOTE

You must update the Administration Client to the same version as the server

If your PC is on a different domain than your server you must set the Internet Explorer

Security Zone value of the Planning and Consolidation client to prompt for user name and

password Otherwise the Planning and Consolidation Start Page does not display

41 Installing the Administration Client

Prerequisites

NOTE

For a definitive list of system requirements see the Product Availability Matrix on SAP Service

Marketplace at httpservicesapcompam Search on Planning and Consolidation

The following list describes the minimum software requirements

Microsoft Internet Explorer 70 or 80

Microsoft Office 2007 or 2010

NET Framework 20 or higher (install any required NET Framework Hotfixes by referring to

httpsupportmicrosoftcomkb)

Pentium IV (1 GHz CPU)

512 MB RAM

100 MB of free hard disk space in the My Documents folder

20 MB of free hard disk space for the installed Administration files

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

41 Installing the Administration Client

2012-06-13 CUSTOMER 3754

NOTE

We recommend that you install all of the latest Microsoft Windows hotfixes prior to installing

the Administration client For information about which hotfixes to install see http

updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us

ProcedureThe following procedure describes how to install the Administration Client on to an administratorrsquos

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 AddRemove Programs in the Windows Control Panel

3 Point your browser to the Planning and Consolidation Web at httpltPC_serverportgtsap

bpcweb

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

42 Installing the EPM Add-in

The Planning and Consolidation installation media does not contain the EPM addin setup program

You must download the most recent version of the full setup (EPM Add-inexe) from the Service

Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPC

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

43 Using the Client Auto Update Program

If Planning and Consolidation version 100 or later is installed you can use the Client Auto Update

program to set up the server so that it determines if an upgrade for a connecting Administration client

is necessary

The following describes the use of the auto update program for the Administration Client and the EPM

add-in

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

42 Installing the EPM Add-in

3854 CUSTOMER 2012-06-13

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 37]

To use the Client Auto Update program for the Administration Client proceed as follows

1 From the Server Manager select Options Client Options

2 Select Admin Update

3 If users without administrator rights on their machines use the auto update enter an administrator

ID and password in the Admin ID and Admin password fields respectively The Admin ID should be a

member of the local administrators group on all the computers running the auto update This

setting is not needed if all users have administrator rights on their machines

4 Select Update

For the EPM Add-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 Optionshellip 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 Market Place (SMP) at httpservicesapcom

All support packages and patches are available from the SMP as a zip file

EPMEXCLCLNTltSPLgtzip is for a support package

EPMEXCLCLNTltSPLgtPltPLgtzip 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 ltSP versiongtmsp

EPM Addin Support Package ltSP versiongtxml

For a patch these files are

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

2012-06-13 CUSTOMER 3954

EPM Addin Patch ltpatch numbergtmsp

EPM Addin Patch ltpatch numbergtxml

2 Unzip the zip file and extract the two files to the application server folder (WebsrvrWebBPC

Installation)

3 From the Server Manager select Options Client Options

The system lists the available packages Select the package that you want to use for the autoupdate

You can set a different update policy for each package listed

EXAMPLE

The following table illustrates some possible situations assuming that you have installed the

first full version (V1)

Available maintenance packages

V2-user updateV3-force updateV4-force updateV5-user update

V5-user update V5-user updateV6-auto updateV7-force update

Minimum Required Version

V4 V4 V7

Notification A prompt tells the user to install maintenance package V4 using the Forced Update behavior

If User Update is enabled the prompt informs the user that maintenance package V5 is available

A prompt tells the user to install maintenance package V7 using the Forced Update behavior

New Version V4 V4 or V5 V7

If you change the update policy for any package click Update to complete the change

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

4054 CUSTOMER 2012-06-13

5 Connection Issues

You may experience connection problems with ports the proxy server or programs and settings that

interact with these components If you have any issues related to connection review the following

recommendations and troubleshooting tips

51 Checking for Open Ports

You must ensure that all required ports are open for inboundoutbound 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 431181836 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

NOTE

You can use the following site to scan for the normal ports It allows you to manually enter a port

number to test

httpwwwmyserverorgportsniffasp

You can change the name of a port

52 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 Explorer Tools Internet Options Connections LAN Settings ) or at the server level

Enabling content filtering on the proxy server or firewall may cause connection problems

If external users are having trouble connecting to the server make sure the proxy server connects

using a fully qualified domain name Fully qualified domain names typically resolve both internal

and external IP addresses

Each secure Planning and Consolidation server name must be identified on the proxy server

Proxy servers may or may not require authentication which could conflict with Planning and

Consolidation authentication Do not use authentication on the proxy server The system

5 Connection Issues

51 Checking for Open Ports

2012-06-13 CUSTOMER 4154

synchronizes the user name and password on the remote server with the local user name and

password

NOTE

For more information about setting up an ISA proxy server contact SAP Support to request a

copy of Setting up ISA Proxy Server White Paper

Internet Explorer Settings 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

5 Connection Issues

52 Proxy Server and Firewall Issues

4254 CUSTOMER 2012-06-13

6 Installing Planning and Consolidation with Two Active Directory Domains

To set up a Planning and Consolidation 10 application server in a hosted environment and use your

own domain users follow this procedure In general you install Planning and Consolidation on the

host domain use the host domain account and assign it to the Planning and Consolidation users

SysAdmin Admin and Users Then you accept one way trust (the host domain trusts your domain)

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

6 Installing Planning and Consolidation with Two Active Directory Domains

2012-06-13 CUSTOMER 4354

This page is left blank for documents that are printed on both sides

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

This section describes best practices and instructions for installing Planning and Consolidation in a

Terminal Services or Citrix Server deployment

71 Terminal Services Home Directories

We recommend using Terminal Server home directories rather than using the userrsquos 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

72 System Requirements

The Citrix server should be one of the following systems

XenApp 5 Enterprise

XenApp 5 Platinum

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 37])

73 Installing Planning and Consolidation

Prerequisites

The server installation files have been downloaded from SAP Service Marketplace and installed

Procedure

The following steps outline how to install the Planning and Consolidation clients in a Terminal Services

(TS) or Citrix Server deployment

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

71 Terminal Services Home Directories

2012-06-13 CUSTOMER 4554

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 userinstall

4 Open a browser and connect to the URL httpltPC_serverportgtsapbpcweb

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 userexecute 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 Iexploreexe http(s)

ltServerNamegt-NetBIOS or FQDNsapbpcweb

To publish Planning and Consolidation Administration CProgram FilesPC_MS

BPCAdminMainexe

74 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 userrsquos desktop) must be moved to the All UsersDesktop folder

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

74 Creating a Shortcut to the Launch Page

4654 CUSTOMER 2012-06-13

8 Installing SSIS Custom Tasks

This section provides background information and instructions for installing SQL Server Integration

Services (SSIS) for SQL Server 2008 and SQL Server 2012

The Planning and Consolidation Data Manager component supports and uses SSIS Since SQL Server

2008 and SQL Server 2012 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

81 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 Filelistxml 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

OSoftSetupexe ‒ 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 or OSoftSSIS2012_Client on the client machine followed by the SQL Server

version If you want to use SQL 2008 Tasks under the SQL 2012 environment you must install

OSoftSSIS2008_Client on the application server For detailed information see SAP Note 1707410

You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package by extracting

OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPC

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 or

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4754

OSoftSSIS2012_Client for creating a COM+ application For more information see Before You Modify

the SSIS Packages [page 50] and Setup of a COM+ Application on the Application Server [page 51]

Bin folder

This folder contains the following components

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCCachedll Planning and Consolidation Cache file

BPCDataFlowPackagedll or BPCDataFlowPackage2012dll

BPCDMdll

BPCDMTaskMaindll COM+ component

BPCFilePreviewdll

BPCGacUtil_20exe System File

BPCGacUtil_40exe System File

BPCImpersonatordll Planning and Consolidation Impersonator

BPCLogicdll

BPCScriptdll

BPCServerZipdll

BPCServiceResdll

BPCTransferMembersdll

BPCWriteBackdll

InteropDTSdll

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

4854 CUSTOMER 2012-06-13

Name Remark

OSoftAdminServerdll

OSoftAuditdll

OSoftComLibServerdll

OSoftCommonResQrydll

OSoftConfigurationdll

OSoftCustomXMLSvrdll

OSoftDatabaseADMINdll

OSoftDatabaseSYSADMINdll

OSoftDatabaseSYSADMINDMdll

OSoftDatabaseUSERdll

OSoftDMDTSXExecutedll or OSoftDMDTSXExecute2012dll

OSoftDMTaskFormdll

OSoftDMTaskMaindll

OSoftDMToolsdll

OSoftFileManagedll

OSoftLoggingdll

OSoftLogWriterdll

OSoftMetaDatadll

OSoftSQEdll

OSoftSystemConfigdll

OutlookSoftconfig Configuration file to connect DB server

XceedCompressiondll XceedZip file

XceedCompressionFormatsdll XceedZip file

XceedFileSystemdll XceedZip file

XceedZipdll XceedZip file

Config folder

This folder has FileListxml 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 FileListxml 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

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4954

OSoftSetupexe

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

NOTE

If you installed the OSoftSSIS2008_Client or OSoftSSIS2012_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

Resources Folder

This folder contains the BPCServicesdll and BPCServiceUIdll files which contain resource text

Only English resources are included for the SSIS custom tasks

82 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

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008 and 2012 respectively

8 Installing SSIS Custom Tasks

82 Before You Modify the SSIS Packages

5054 CUSTOMER 2012-06-13

Name Remark

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012 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

lthellipgtOSoftSSIS2008_Clientbin or lthellipgtOSoftSSIS2012_Clientbin

On the Planning and Consolidation application server

ltdrivegtWebsrvrbin

2 Paste these files into the folder 100DTSTasks for SQL Server 2008 or into 110DTSTasks for

SQL Server 2012 For example if you install your SQL 2008 server or R2 on CProgram Files

Microsoft SQL Server paste all files into the CProgram Files (x86)Microsoft SQL Server

100DTSTasks folder

In Integration Services set the property Run64BitRunTime to True

83 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 or OSoftSSIS2012_Client on the

application server

8 Installing SSIS Custom Tasks

83 Setup of a COM+ Application on the Application Server

2012-06-13 CUSTOMER 5154

Typographic Conventions

Example Description

ltgt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example Enter your ltUser Namegt

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 httpwwwsapcom

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

5254 CUSTOMER 2012-06-13

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

  • SAP BusinessObjects Planning and Consolidation 100
    • Table of Contents
    • 1 Introduction
      • 11 SAP Notes for the Installation
      • 12 Naming Conventions
        • 2 Installing Planning and Consolidation Servers
          • 21 Basic Steps
          • 22 Prerequisites
          • 23 Before Starting the Planning and Consolidation Server Installation
          • 24 Logging on to Servers
          • 25 Service-level Accounts
          • 26 Standard and Advanced Settings
          • 27 Installing the Prerequisites
            • 271 Installing the Prerequisites ndash Basic Steps
            • 272 Installing the Operating System
            • 273 Installing the SQL Server
            • 274 Installing Analysis Services
            • 275 Installing the Anti-Cross Site Scripting Library
              • 28 Installing on a Single Server
              • 29 Installing the Server in a Multiserver Configuration
                • 3 After Installing Planning and Consolidation Servers
                  • 31 Post-Installation Steps
                  • 32 Connecting to Solution Manager Diagnostics
                  • 33 Configuring the Planning and Consolidation NET Application Servers
                  • 34 Post-Installation Optional Configuration Steps
                    • 341 Enabling the Management Console
                    • 342 Setting Up ODBC Logging in IIS for the Default Web Site
                    • 343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2
                    • 344 Removing Default Access to the Console
                    • 345 Management Console Access Control
                    • 346 Using Client Certificates
                        • 4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office
                          • 41 Installing the Administration Client
                          • 42 Installing the EPM Add-in
                          • 43 Using the Client Auto Update Program
                            • 5 Connection Issues
                              • 51 Checking for Open Ports
                              • 52 Proxy Server and Firewall Issues
                                • 6 Installing Planning and Consolidation with Two Active Directory Domains
                                • 7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
                                  • 71 Terminal Services Home Directories
                                  • 72 System Requirements
                                  • 73 Installing Planning and Consolidation
                                  • 74 Creating a Shortcut to the Launch Page
                                    • 8 Installing SSIS Custom Tasks
                                      • 81 Composition of SSIS Custom Task Installation
                                      • 82 Before You Modify the SSIS Packages
                                      • 83 Setup of a COM+ Application on the Application Server
                                          • Copyright and trademarks
Page 31: Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

NOTE

Without these updates the Management Console does work but some functionality (specifically

User Activity and Service Status) does not work as expected

Should you need to uninstall Planning and Consolidation we recommend that you reset the

Active Log Format field in IIS to W3C Extended Log File Format

342 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 ApplicationHostconfig set the property customLogPluginClsid to the value FF16065B-

DE82-11CF-BC0A-00AA006111E0 Set the logFormat to Custom You can find this in the ltlogFilegt

node in ApplicationHostconfig as shown here

ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0

logFormat=Custom gt

Use the following AppCmds to configure IIS to use ODBC logging for the default Web site

appcmd site set sitenameDefault Web Site

logFilecustomLogPluginClsidFF16065B-DE82-11CF-BC0A-00AA006111E0

appcmd site set sitenameDefault Web Site logFilelogFormatCustom

Configuring ODBC Logging Parameters in ApplicationHostconfig

Configure ApplicationHostconfig to contain the database table information as set up in the Microsoft

Support article specified in the Prerequisites section Configure these settings in the ltodbcLogginggt

node under ltsystemwebServergt

EXAMPLE

ltlocation path=Default Web Sitegt

ltsystemwebServergt

ltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog

userName=Username password=mypassword gt

ltsystemwebServergt

ltlocationgt

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3154

Use the following AppCmds to configure these attributes for the default Web site

appcmd set config Default Web Site sectionodbcLogging

dataSourceBPC_ManagementDSN commitappHost

appcmd set config Default Web Site sectionodbcLogging tableNameBPCLog

commitappHost

appcmd set config Default Web Site sectionodbcLogging userNameUsername

commitappHost

appcmd set config Default Web Site sectionodbcLogging passwordmypassword

commitappHost

NOTE

You cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must

use the SQL Server ODBC driver For more information see the Microsoft Knowledge Base article

931202 The requirements for using the ODBC logging feature in IIS

343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2

ProcedureThis procedure describes how to set up an ODBC data source for the Management Console in Windows

Server 2008 or Windows Server 2008 R2

Proceed as follows

1 Open ODBC Connection Manager

2 On the System DSN tab page add a new DSN

Choose Add

Choose SQL Server as the driver

Choose Finish

3 In the Name and Description fields enter BPC_ManagementDSN

4 In the Server field enter the name of your SQL Server Choose Next

5 Leave the default settings and choose Next

6 Choose the Change the default database to field and enter AppServer Choose Next

7 Leave default settings and choose Next

8 Choose OK

344 Removing Default Access to the Console

NOTE

If you have chosen SAP BusinessObjects User Management System in the installation screen you

do not need to remove or configure access because the Management Console service always runs

with the System Admin ID account which is a member of the Administrators group

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3254 CUSTOMER 2012-06-13

ProcedureTo remove default access to the Management Console and create a group that does have access to the

console use the procedure described below

NOTE

Create your Management Console administrative group either on the server that hosts the

Management Console or in the Active Directory

1 In the context menu of the servers My Computer icon choose Manage

2 In the Computer Management dialog box choose Local Users and Groups Groups

NOTE

Alternatively you can perform analogous steps in Active Directory

3 In the 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

NOTE

This step is a necessary precursor to the completion of this procedure

10 In the Security dialog box click Copy to ensure that the System group retains its privileges

11 Remove access to the Management Console from all groups that should not have it

12 Choose Authentication in the center pane then disable Windows authentication

ResultUsers who have not been granted access to the Management Console can still open the Management

Console Web page but it contains no data or menu options This does not affect the access that a user

would otherwise have to Planning and Consolidation

345 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 32] Their rights in

Active Directory determine what they can access in the Console

By default any member of the Administrators Active Directory group on the application server or

domain has full access to all of the features of the Console except the Planning and Consolidation

logging area Access to Planning and Consolidation logging is controlled within the Planning and

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3354

Consolidation Administration Client task security The user must be granted View system logs task

privileges For more information see the SAP Library Planning and Consolidation Administrators Guide in

httpservicesapcominstguidesepm-bpc 100 version for the Microsoft platform

Your IT policy determines whether you grant access by group or user You may wish to create several

levels of Console users (read-only users for example) in your environment

To grant or limit access to users or groups you can add or remove the following privileges from the

areas described in this table

Privilege Rights Management Area

Task Manager and Kill Process Administrators group on application server or domain

Performance Monitor Counters Administrators group on application server or domain Power Users group on application server or domain Performance Monitor Users group on application server

Microsoft Analysis Services performance monitoring

Administrators group on application server or domain

Microsoft SQL Server Monitoring (performance counters and statistics)

Administrators group on application server or domain

346 Using Client Certificates

To enable the use of client certificates in Planning and Consolidation you must follow several manual

steps

NOTE

Planning 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 httptechnetmicrosoftcomen-us

librarycc753810aspx

For more information about configuring the client certificate mapping authentication see http

technetmicrosoftcomen-uslibrarycc732996(WS10)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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3454 CUSTOMER 2012-06-13

This option allows you to use a client certificate or username and password (Basic

authentication) to connect to Planning and Consolidation

2 Enable anonymous authentication

1 In the IIS Manager expand the node of the Planning and Consolidation web site

2 Select the ManagementConsole directory (ltWebsitegtManagementConsole) to open the

ManagementConsole home page

3 Double-click Authentication and enable Anonymous Authentication

4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way

as in step 3

5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the same

way as in step 3

3 Change the web configuration settings

1 Open the ltPC_MSgtWebsrvrWebBPCwebconfig file

2 Find the text clientCredentialType=Windows

3 Change value of clientCredentialType to None (clientCredentialType=None)

4 Open the PC_MSWebsrvrWebPOASBCwebconfig file Repeat steps 2 and 3

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3554

This page is left blank for documents that are printed on both sides

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

The installation of the Planning and Consolidation Administration Client allows administrators to

build and maintain Planning and Consolidation environments and models and administer security

All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions

add-in for Microsoft Office for more information see the SAP BusinessObjects EPM solutions add-in for

Microsoft Office help

NOTE

You must update the Administration Client to the same version as the server

If your PC is on a different domain than your server you must set the Internet Explorer

Security Zone value of the Planning and Consolidation client to prompt for user name and

password Otherwise the Planning and Consolidation Start Page does not display

41 Installing the Administration Client

Prerequisites

NOTE

For a definitive list of system requirements see the Product Availability Matrix on SAP Service

Marketplace at httpservicesapcompam Search on Planning and Consolidation

The following list describes the minimum software requirements

Microsoft Internet Explorer 70 or 80

Microsoft Office 2007 or 2010

NET Framework 20 or higher (install any required NET Framework Hotfixes by referring to

httpsupportmicrosoftcomkb)

Pentium IV (1 GHz CPU)

512 MB RAM

100 MB of free hard disk space in the My Documents folder

20 MB of free hard disk space for the installed Administration files

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

41 Installing the Administration Client

2012-06-13 CUSTOMER 3754

NOTE

We recommend that you install all of the latest Microsoft Windows hotfixes prior to installing

the Administration client For information about which hotfixes to install see http

updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us

ProcedureThe following procedure describes how to install the Administration Client on to an administratorrsquos

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 AddRemove Programs in the Windows Control Panel

3 Point your browser to the Planning and Consolidation Web at httpltPC_serverportgtsap

bpcweb

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

42 Installing the EPM Add-in

The Planning and Consolidation installation media does not contain the EPM addin setup program

You must download the most recent version of the full setup (EPM Add-inexe) from the Service

Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPC

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

43 Using the Client Auto Update Program

If Planning and Consolidation version 100 or later is installed you can use the Client Auto Update

program to set up the server so that it determines if an upgrade for a connecting Administration client

is necessary

The following describes the use of the auto update program for the Administration Client and the EPM

add-in

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

42 Installing the EPM Add-in

3854 CUSTOMER 2012-06-13

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 37]

To use the Client Auto Update program for the Administration Client proceed as follows

1 From the Server Manager select Options Client Options

2 Select Admin Update

3 If users without administrator rights on their machines use the auto update enter an administrator

ID and password in the Admin ID and Admin password fields respectively The Admin ID should be a

member of the local administrators group on all the computers running the auto update This

setting is not needed if all users have administrator rights on their machines

4 Select Update

For the EPM Add-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 Optionshellip 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 Market Place (SMP) at httpservicesapcom

All support packages and patches are available from the SMP as a zip file

EPMEXCLCLNTltSPLgtzip is for a support package

EPMEXCLCLNTltSPLgtPltPLgtzip 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 ltSP versiongtmsp

EPM Addin Support Package ltSP versiongtxml

For a patch these files are

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

2012-06-13 CUSTOMER 3954

EPM Addin Patch ltpatch numbergtmsp

EPM Addin Patch ltpatch numbergtxml

2 Unzip the zip file and extract the two files to the application server folder (WebsrvrWebBPC

Installation)

3 From the Server Manager select Options Client Options

The system lists the available packages Select the package that you want to use for the autoupdate

You can set a different update policy for each package listed

EXAMPLE

The following table illustrates some possible situations assuming that you have installed the

first full version (V1)

Available maintenance packages

V2-user updateV3-force updateV4-force updateV5-user update

V5-user update V5-user updateV6-auto updateV7-force update

Minimum Required Version

V4 V4 V7

Notification A prompt tells the user to install maintenance package V4 using the Forced Update behavior

If User Update is enabled the prompt informs the user that maintenance package V5 is available

A prompt tells the user to install maintenance package V7 using the Forced Update behavior

New Version V4 V4 or V5 V7

If you change the update policy for any package click Update to complete the change

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

4054 CUSTOMER 2012-06-13

5 Connection Issues

You may experience connection problems with ports the proxy server or programs and settings that

interact with these components If you have any issues related to connection review the following

recommendations and troubleshooting tips

51 Checking for Open Ports

You must ensure that all required ports are open for inboundoutbound 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 431181836 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

NOTE

You can use the following site to scan for the normal ports It allows you to manually enter a port

number to test

httpwwwmyserverorgportsniffasp

You can change the name of a port

52 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 Explorer Tools Internet Options Connections LAN Settings ) or at the server level

Enabling content filtering on the proxy server or firewall may cause connection problems

If external users are having trouble connecting to the server make sure the proxy server connects

using a fully qualified domain name Fully qualified domain names typically resolve both internal

and external IP addresses

Each secure Planning and Consolidation server name must be identified on the proxy server

Proxy servers may or may not require authentication which could conflict with Planning and

Consolidation authentication Do not use authentication on the proxy server The system

5 Connection Issues

51 Checking for Open Ports

2012-06-13 CUSTOMER 4154

synchronizes the user name and password on the remote server with the local user name and

password

NOTE

For more information about setting up an ISA proxy server contact SAP Support to request a

copy of Setting up ISA Proxy Server White Paper

Internet Explorer Settings 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

5 Connection Issues

52 Proxy Server and Firewall Issues

4254 CUSTOMER 2012-06-13

6 Installing Planning and Consolidation with Two Active Directory Domains

To set up a Planning and Consolidation 10 application server in a hosted environment and use your

own domain users follow this procedure In general you install Planning and Consolidation on the

host domain use the host domain account and assign it to the Planning and Consolidation users

SysAdmin Admin and Users Then you accept one way trust (the host domain trusts your domain)

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

6 Installing Planning and Consolidation with Two Active Directory Domains

2012-06-13 CUSTOMER 4354

This page is left blank for documents that are printed on both sides

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

This section describes best practices and instructions for installing Planning and Consolidation in a

Terminal Services or Citrix Server deployment

71 Terminal Services Home Directories

We recommend using Terminal Server home directories rather than using the userrsquos 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

72 System Requirements

The Citrix server should be one of the following systems

XenApp 5 Enterprise

XenApp 5 Platinum

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 37])

73 Installing Planning and Consolidation

Prerequisites

The server installation files have been downloaded from SAP Service Marketplace and installed

Procedure

The following steps outline how to install the Planning and Consolidation clients in a Terminal Services

(TS) or Citrix Server deployment

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

71 Terminal Services Home Directories

2012-06-13 CUSTOMER 4554

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 userinstall

4 Open a browser and connect to the URL httpltPC_serverportgtsapbpcweb

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 userexecute 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 Iexploreexe http(s)

ltServerNamegt-NetBIOS or FQDNsapbpcweb

To publish Planning and Consolidation Administration CProgram FilesPC_MS

BPCAdminMainexe

74 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 userrsquos desktop) must be moved to the All UsersDesktop folder

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

74 Creating a Shortcut to the Launch Page

4654 CUSTOMER 2012-06-13

8 Installing SSIS Custom Tasks

This section provides background information and instructions for installing SQL Server Integration

Services (SSIS) for SQL Server 2008 and SQL Server 2012

The Planning and Consolidation Data Manager component supports and uses SSIS Since SQL Server

2008 and SQL Server 2012 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

81 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 Filelistxml 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

OSoftSetupexe ‒ 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 or OSoftSSIS2012_Client on the client machine followed by the SQL Server

version If you want to use SQL 2008 Tasks under the SQL 2012 environment you must install

OSoftSSIS2008_Client on the application server For detailed information see SAP Note 1707410

You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package by extracting

OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPC

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 or

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4754

OSoftSSIS2012_Client for creating a COM+ application For more information see Before You Modify

the SSIS Packages [page 50] and Setup of a COM+ Application on the Application Server [page 51]

Bin folder

This folder contains the following components

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCCachedll Planning and Consolidation Cache file

BPCDataFlowPackagedll or BPCDataFlowPackage2012dll

BPCDMdll

BPCDMTaskMaindll COM+ component

BPCFilePreviewdll

BPCGacUtil_20exe System File

BPCGacUtil_40exe System File

BPCImpersonatordll Planning and Consolidation Impersonator

BPCLogicdll

BPCScriptdll

BPCServerZipdll

BPCServiceResdll

BPCTransferMembersdll

BPCWriteBackdll

InteropDTSdll

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

4854 CUSTOMER 2012-06-13

Name Remark

OSoftAdminServerdll

OSoftAuditdll

OSoftComLibServerdll

OSoftCommonResQrydll

OSoftConfigurationdll

OSoftCustomXMLSvrdll

OSoftDatabaseADMINdll

OSoftDatabaseSYSADMINdll

OSoftDatabaseSYSADMINDMdll

OSoftDatabaseUSERdll

OSoftDMDTSXExecutedll or OSoftDMDTSXExecute2012dll

OSoftDMTaskFormdll

OSoftDMTaskMaindll

OSoftDMToolsdll

OSoftFileManagedll

OSoftLoggingdll

OSoftLogWriterdll

OSoftMetaDatadll

OSoftSQEdll

OSoftSystemConfigdll

OutlookSoftconfig Configuration file to connect DB server

XceedCompressiondll XceedZip file

XceedCompressionFormatsdll XceedZip file

XceedFileSystemdll XceedZip file

XceedZipdll XceedZip file

Config folder

This folder has FileListxml 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 FileListxml 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

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4954

OSoftSetupexe

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

NOTE

If you installed the OSoftSSIS2008_Client or OSoftSSIS2012_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

Resources Folder

This folder contains the BPCServicesdll and BPCServiceUIdll files which contain resource text

Only English resources are included for the SSIS custom tasks

82 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

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008 and 2012 respectively

8 Installing SSIS Custom Tasks

82 Before You Modify the SSIS Packages

5054 CUSTOMER 2012-06-13

Name Remark

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012 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

lthellipgtOSoftSSIS2008_Clientbin or lthellipgtOSoftSSIS2012_Clientbin

On the Planning and Consolidation application server

ltdrivegtWebsrvrbin

2 Paste these files into the folder 100DTSTasks for SQL Server 2008 or into 110DTSTasks for

SQL Server 2012 For example if you install your SQL 2008 server or R2 on CProgram Files

Microsoft SQL Server paste all files into the CProgram Files (x86)Microsoft SQL Server

100DTSTasks folder

In Integration Services set the property Run64BitRunTime to True

83 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 or OSoftSSIS2012_Client on the

application server

8 Installing SSIS Custom Tasks

83 Setup of a COM+ Application on the Application Server

2012-06-13 CUSTOMER 5154

Typographic Conventions

Example Description

ltgt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example Enter your ltUser Namegt

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 httpwwwsapcom

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

5254 CUSTOMER 2012-06-13

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

  • SAP BusinessObjects Planning and Consolidation 100
    • Table of Contents
    • 1 Introduction
      • 11 SAP Notes for the Installation
      • 12 Naming Conventions
        • 2 Installing Planning and Consolidation Servers
          • 21 Basic Steps
          • 22 Prerequisites
          • 23 Before Starting the Planning and Consolidation Server Installation
          • 24 Logging on to Servers
          • 25 Service-level Accounts
          • 26 Standard and Advanced Settings
          • 27 Installing the Prerequisites
            • 271 Installing the Prerequisites ndash Basic Steps
            • 272 Installing the Operating System
            • 273 Installing the SQL Server
            • 274 Installing Analysis Services
            • 275 Installing the Anti-Cross Site Scripting Library
              • 28 Installing on a Single Server
              • 29 Installing the Server in a Multiserver Configuration
                • 3 After Installing Planning and Consolidation Servers
                  • 31 Post-Installation Steps
                  • 32 Connecting to Solution Manager Diagnostics
                  • 33 Configuring the Planning and Consolidation NET Application Servers
                  • 34 Post-Installation Optional Configuration Steps
                    • 341 Enabling the Management Console
                    • 342 Setting Up ODBC Logging in IIS for the Default Web Site
                    • 343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2
                    • 344 Removing Default Access to the Console
                    • 345 Management Console Access Control
                    • 346 Using Client Certificates
                        • 4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office
                          • 41 Installing the Administration Client
                          • 42 Installing the EPM Add-in
                          • 43 Using the Client Auto Update Program
                            • 5 Connection Issues
                              • 51 Checking for Open Ports
                              • 52 Proxy Server and Firewall Issues
                                • 6 Installing Planning and Consolidation with Two Active Directory Domains
                                • 7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
                                  • 71 Terminal Services Home Directories
                                  • 72 System Requirements
                                  • 73 Installing Planning and Consolidation
                                  • 74 Creating a Shortcut to the Launch Page
                                    • 8 Installing SSIS Custom Tasks
                                      • 81 Composition of SSIS Custom Task Installation
                                      • 82 Before You Modify the SSIS Packages
                                      • 83 Setup of a COM+ Application on the Application Server
                                          • Copyright and trademarks
Page 32: Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

Use the following AppCmds to configure these attributes for the default Web site

appcmd set config Default Web Site sectionodbcLogging

dataSourceBPC_ManagementDSN commitappHost

appcmd set config Default Web Site sectionodbcLogging tableNameBPCLog

commitappHost

appcmd set config Default Web Site sectionodbcLogging userNameUsername

commitappHost

appcmd set config Default Web Site sectionodbcLogging passwordmypassword

commitappHost

NOTE

You cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must

use the SQL Server ODBC driver For more information see the Microsoft Knowledge Base article

931202 The requirements for using the ODBC logging feature in IIS

343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2

ProcedureThis procedure describes how to set up an ODBC data source for the Management Console in Windows

Server 2008 or Windows Server 2008 R2

Proceed as follows

1 Open ODBC Connection Manager

2 On the System DSN tab page add a new DSN

Choose Add

Choose SQL Server as the driver

Choose Finish

3 In the Name and Description fields enter BPC_ManagementDSN

4 In the Server field enter the name of your SQL Server Choose Next

5 Leave the default settings and choose Next

6 Choose the Change the default database to field and enter AppServer Choose Next

7 Leave default settings and choose Next

8 Choose OK

344 Removing Default Access to the Console

NOTE

If you have chosen SAP BusinessObjects User Management System in the installation screen you

do not need to remove or configure access because the Management Console service always runs

with the System Admin ID account which is a member of the Administrators group

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3254 CUSTOMER 2012-06-13

ProcedureTo remove default access to the Management Console and create a group that does have access to the

console use the procedure described below

NOTE

Create your Management Console administrative group either on the server that hosts the

Management Console or in the Active Directory

1 In the context menu of the servers My Computer icon choose Manage

2 In the Computer Management dialog box choose Local Users and Groups Groups

NOTE

Alternatively you can perform analogous steps in Active Directory

3 In the 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

NOTE

This step is a necessary precursor to the completion of this procedure

10 In the Security dialog box click Copy to ensure that the System group retains its privileges

11 Remove access to the Management Console from all groups that should not have it

12 Choose Authentication in the center pane then disable Windows authentication

ResultUsers who have not been granted access to the Management Console can still open the Management

Console Web page but it contains no data or menu options This does not affect the access that a user

would otherwise have to Planning and Consolidation

345 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 32] Their rights in

Active Directory determine what they can access in the Console

By default any member of the Administrators Active Directory group on the application server or

domain has full access to all of the features of the Console except the Planning and Consolidation

logging area Access to Planning and Consolidation logging is controlled within the Planning and

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3354

Consolidation Administration Client task security The user must be granted View system logs task

privileges For more information see the SAP Library Planning and Consolidation Administrators Guide in

httpservicesapcominstguidesepm-bpc 100 version for the Microsoft platform

Your IT policy determines whether you grant access by group or user You may wish to create several

levels of Console users (read-only users for example) in your environment

To grant or limit access to users or groups you can add or remove the following privileges from the

areas described in this table

Privilege Rights Management Area

Task Manager and Kill Process Administrators group on application server or domain

Performance Monitor Counters Administrators group on application server or domain Power Users group on application server or domain Performance Monitor Users group on application server

Microsoft Analysis Services performance monitoring

Administrators group on application server or domain

Microsoft SQL Server Monitoring (performance counters and statistics)

Administrators group on application server or domain

346 Using Client Certificates

To enable the use of client certificates in Planning and Consolidation you must follow several manual

steps

NOTE

Planning 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 httptechnetmicrosoftcomen-us

librarycc753810aspx

For more information about configuring the client certificate mapping authentication see http

technetmicrosoftcomen-uslibrarycc732996(WS10)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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3454 CUSTOMER 2012-06-13

This option allows you to use a client certificate or username and password (Basic

authentication) to connect to Planning and Consolidation

2 Enable anonymous authentication

1 In the IIS Manager expand the node of the Planning and Consolidation web site

2 Select the ManagementConsole directory (ltWebsitegtManagementConsole) to open the

ManagementConsole home page

3 Double-click Authentication and enable Anonymous Authentication

4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way

as in step 3

5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the same

way as in step 3

3 Change the web configuration settings

1 Open the ltPC_MSgtWebsrvrWebBPCwebconfig file

2 Find the text clientCredentialType=Windows

3 Change value of clientCredentialType to None (clientCredentialType=None)

4 Open the PC_MSWebsrvrWebPOASBCwebconfig file Repeat steps 2 and 3

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3554

This page is left blank for documents that are printed on both sides

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

The installation of the Planning and Consolidation Administration Client allows administrators to

build and maintain Planning and Consolidation environments and models and administer security

All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions

add-in for Microsoft Office for more information see the SAP BusinessObjects EPM solutions add-in for

Microsoft Office help

NOTE

You must update the Administration Client to the same version as the server

If your PC is on a different domain than your server you must set the Internet Explorer

Security Zone value of the Planning and Consolidation client to prompt for user name and

password Otherwise the Planning and Consolidation Start Page does not display

41 Installing the Administration Client

Prerequisites

NOTE

For a definitive list of system requirements see the Product Availability Matrix on SAP Service

Marketplace at httpservicesapcompam Search on Planning and Consolidation

The following list describes the minimum software requirements

Microsoft Internet Explorer 70 or 80

Microsoft Office 2007 or 2010

NET Framework 20 or higher (install any required NET Framework Hotfixes by referring to

httpsupportmicrosoftcomkb)

Pentium IV (1 GHz CPU)

512 MB RAM

100 MB of free hard disk space in the My Documents folder

20 MB of free hard disk space for the installed Administration files

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

41 Installing the Administration Client

2012-06-13 CUSTOMER 3754

NOTE

We recommend that you install all of the latest Microsoft Windows hotfixes prior to installing

the Administration client For information about which hotfixes to install see http

updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us

ProcedureThe following procedure describes how to install the Administration Client on to an administratorrsquos

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 AddRemove Programs in the Windows Control Panel

3 Point your browser to the Planning and Consolidation Web at httpltPC_serverportgtsap

bpcweb

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

42 Installing the EPM Add-in

The Planning and Consolidation installation media does not contain the EPM addin setup program

You must download the most recent version of the full setup (EPM Add-inexe) from the Service

Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPC

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

43 Using the Client Auto Update Program

If Planning and Consolidation version 100 or later is installed you can use the Client Auto Update

program to set up the server so that it determines if an upgrade for a connecting Administration client

is necessary

The following describes the use of the auto update program for the Administration Client and the EPM

add-in

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

42 Installing the EPM Add-in

3854 CUSTOMER 2012-06-13

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 37]

To use the Client Auto Update program for the Administration Client proceed as follows

1 From the Server Manager select Options Client Options

2 Select Admin Update

3 If users without administrator rights on their machines use the auto update enter an administrator

ID and password in the Admin ID and Admin password fields respectively The Admin ID should be a

member of the local administrators group on all the computers running the auto update This

setting is not needed if all users have administrator rights on their machines

4 Select Update

For the EPM Add-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 Optionshellip 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 Market Place (SMP) at httpservicesapcom

All support packages and patches are available from the SMP as a zip file

EPMEXCLCLNTltSPLgtzip is for a support package

EPMEXCLCLNTltSPLgtPltPLgtzip 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 ltSP versiongtmsp

EPM Addin Support Package ltSP versiongtxml

For a patch these files are

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

2012-06-13 CUSTOMER 3954

EPM Addin Patch ltpatch numbergtmsp

EPM Addin Patch ltpatch numbergtxml

2 Unzip the zip file and extract the two files to the application server folder (WebsrvrWebBPC

Installation)

3 From the Server Manager select Options Client Options

The system lists the available packages Select the package that you want to use for the autoupdate

You can set a different update policy for each package listed

EXAMPLE

The following table illustrates some possible situations assuming that you have installed the

first full version (V1)

Available maintenance packages

V2-user updateV3-force updateV4-force updateV5-user update

V5-user update V5-user updateV6-auto updateV7-force update

Minimum Required Version

V4 V4 V7

Notification A prompt tells the user to install maintenance package V4 using the Forced Update behavior

If User Update is enabled the prompt informs the user that maintenance package V5 is available

A prompt tells the user to install maintenance package V7 using the Forced Update behavior

New Version V4 V4 or V5 V7

If you change the update policy for any package click Update to complete the change

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

4054 CUSTOMER 2012-06-13

5 Connection Issues

You may experience connection problems with ports the proxy server or programs and settings that

interact with these components If you have any issues related to connection review the following

recommendations and troubleshooting tips

51 Checking for Open Ports

You must ensure that all required ports are open for inboundoutbound 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 431181836 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

NOTE

You can use the following site to scan for the normal ports It allows you to manually enter a port

number to test

httpwwwmyserverorgportsniffasp

You can change the name of a port

52 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 Explorer Tools Internet Options Connections LAN Settings ) or at the server level

Enabling content filtering on the proxy server or firewall may cause connection problems

If external users are having trouble connecting to the server make sure the proxy server connects

using a fully qualified domain name Fully qualified domain names typically resolve both internal

and external IP addresses

Each secure Planning and Consolidation server name must be identified on the proxy server

Proxy servers may or may not require authentication which could conflict with Planning and

Consolidation authentication Do not use authentication on the proxy server The system

5 Connection Issues

51 Checking for Open Ports

2012-06-13 CUSTOMER 4154

synchronizes the user name and password on the remote server with the local user name and

password

NOTE

For more information about setting up an ISA proxy server contact SAP Support to request a

copy of Setting up ISA Proxy Server White Paper

Internet Explorer Settings 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

5 Connection Issues

52 Proxy Server and Firewall Issues

4254 CUSTOMER 2012-06-13

6 Installing Planning and Consolidation with Two Active Directory Domains

To set up a Planning and Consolidation 10 application server in a hosted environment and use your

own domain users follow this procedure In general you install Planning and Consolidation on the

host domain use the host domain account and assign it to the Planning and Consolidation users

SysAdmin Admin and Users Then you accept one way trust (the host domain trusts your domain)

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

6 Installing Planning and Consolidation with Two Active Directory Domains

2012-06-13 CUSTOMER 4354

This page is left blank for documents that are printed on both sides

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

This section describes best practices and instructions for installing Planning and Consolidation in a

Terminal Services or Citrix Server deployment

71 Terminal Services Home Directories

We recommend using Terminal Server home directories rather than using the userrsquos 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

72 System Requirements

The Citrix server should be one of the following systems

XenApp 5 Enterprise

XenApp 5 Platinum

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 37])

73 Installing Planning and Consolidation

Prerequisites

The server installation files have been downloaded from SAP Service Marketplace and installed

Procedure

The following steps outline how to install the Planning and Consolidation clients in a Terminal Services

(TS) or Citrix Server deployment

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

71 Terminal Services Home Directories

2012-06-13 CUSTOMER 4554

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 userinstall

4 Open a browser and connect to the URL httpltPC_serverportgtsapbpcweb

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 userexecute 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 Iexploreexe http(s)

ltServerNamegt-NetBIOS or FQDNsapbpcweb

To publish Planning and Consolidation Administration CProgram FilesPC_MS

BPCAdminMainexe

74 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 userrsquos desktop) must be moved to the All UsersDesktop folder

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

74 Creating a Shortcut to the Launch Page

4654 CUSTOMER 2012-06-13

8 Installing SSIS Custom Tasks

This section provides background information and instructions for installing SQL Server Integration

Services (SSIS) for SQL Server 2008 and SQL Server 2012

The Planning and Consolidation Data Manager component supports and uses SSIS Since SQL Server

2008 and SQL Server 2012 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

81 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 Filelistxml 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

OSoftSetupexe ‒ 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 or OSoftSSIS2012_Client on the client machine followed by the SQL Server

version If you want to use SQL 2008 Tasks under the SQL 2012 environment you must install

OSoftSSIS2008_Client on the application server For detailed information see SAP Note 1707410

You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package by extracting

OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPC

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 or

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4754

OSoftSSIS2012_Client for creating a COM+ application For more information see Before You Modify

the SSIS Packages [page 50] and Setup of a COM+ Application on the Application Server [page 51]

Bin folder

This folder contains the following components

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCCachedll Planning and Consolidation Cache file

BPCDataFlowPackagedll or BPCDataFlowPackage2012dll

BPCDMdll

BPCDMTaskMaindll COM+ component

BPCFilePreviewdll

BPCGacUtil_20exe System File

BPCGacUtil_40exe System File

BPCImpersonatordll Planning and Consolidation Impersonator

BPCLogicdll

BPCScriptdll

BPCServerZipdll

BPCServiceResdll

BPCTransferMembersdll

BPCWriteBackdll

InteropDTSdll

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

4854 CUSTOMER 2012-06-13

Name Remark

OSoftAdminServerdll

OSoftAuditdll

OSoftComLibServerdll

OSoftCommonResQrydll

OSoftConfigurationdll

OSoftCustomXMLSvrdll

OSoftDatabaseADMINdll

OSoftDatabaseSYSADMINdll

OSoftDatabaseSYSADMINDMdll

OSoftDatabaseUSERdll

OSoftDMDTSXExecutedll or OSoftDMDTSXExecute2012dll

OSoftDMTaskFormdll

OSoftDMTaskMaindll

OSoftDMToolsdll

OSoftFileManagedll

OSoftLoggingdll

OSoftLogWriterdll

OSoftMetaDatadll

OSoftSQEdll

OSoftSystemConfigdll

OutlookSoftconfig Configuration file to connect DB server

XceedCompressiondll XceedZip file

XceedCompressionFormatsdll XceedZip file

XceedFileSystemdll XceedZip file

XceedZipdll XceedZip file

Config folder

This folder has FileListxml 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 FileListxml 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

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4954

OSoftSetupexe

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

NOTE

If you installed the OSoftSSIS2008_Client or OSoftSSIS2012_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

Resources Folder

This folder contains the BPCServicesdll and BPCServiceUIdll files which contain resource text

Only English resources are included for the SSIS custom tasks

82 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

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008 and 2012 respectively

8 Installing SSIS Custom Tasks

82 Before You Modify the SSIS Packages

5054 CUSTOMER 2012-06-13

Name Remark

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012 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

lthellipgtOSoftSSIS2008_Clientbin or lthellipgtOSoftSSIS2012_Clientbin

On the Planning and Consolidation application server

ltdrivegtWebsrvrbin

2 Paste these files into the folder 100DTSTasks for SQL Server 2008 or into 110DTSTasks for

SQL Server 2012 For example if you install your SQL 2008 server or R2 on CProgram Files

Microsoft SQL Server paste all files into the CProgram Files (x86)Microsoft SQL Server

100DTSTasks folder

In Integration Services set the property Run64BitRunTime to True

83 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 or OSoftSSIS2012_Client on the

application server

8 Installing SSIS Custom Tasks

83 Setup of a COM+ Application on the Application Server

2012-06-13 CUSTOMER 5154

Typographic Conventions

Example Description

ltgt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example Enter your ltUser Namegt

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 httpwwwsapcom

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

5254 CUSTOMER 2012-06-13

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

  • SAP BusinessObjects Planning and Consolidation 100
    • Table of Contents
    • 1 Introduction
      • 11 SAP Notes for the Installation
      • 12 Naming Conventions
        • 2 Installing Planning and Consolidation Servers
          • 21 Basic Steps
          • 22 Prerequisites
          • 23 Before Starting the Planning and Consolidation Server Installation
          • 24 Logging on to Servers
          • 25 Service-level Accounts
          • 26 Standard and Advanced Settings
          • 27 Installing the Prerequisites
            • 271 Installing the Prerequisites ndash Basic Steps
            • 272 Installing the Operating System
            • 273 Installing the SQL Server
            • 274 Installing Analysis Services
            • 275 Installing the Anti-Cross Site Scripting Library
              • 28 Installing on a Single Server
              • 29 Installing the Server in a Multiserver Configuration
                • 3 After Installing Planning and Consolidation Servers
                  • 31 Post-Installation Steps
                  • 32 Connecting to Solution Manager Diagnostics
                  • 33 Configuring the Planning and Consolidation NET Application Servers
                  • 34 Post-Installation Optional Configuration Steps
                    • 341 Enabling the Management Console
                    • 342 Setting Up ODBC Logging in IIS for the Default Web Site
                    • 343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2
                    • 344 Removing Default Access to the Console
                    • 345 Management Console Access Control
                    • 346 Using Client Certificates
                        • 4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office
                          • 41 Installing the Administration Client
                          • 42 Installing the EPM Add-in
                          • 43 Using the Client Auto Update Program
                            • 5 Connection Issues
                              • 51 Checking for Open Ports
                              • 52 Proxy Server and Firewall Issues
                                • 6 Installing Planning and Consolidation with Two Active Directory Domains
                                • 7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
                                  • 71 Terminal Services Home Directories
                                  • 72 System Requirements
                                  • 73 Installing Planning and Consolidation
                                  • 74 Creating a Shortcut to the Launch Page
                                    • 8 Installing SSIS Custom Tasks
                                      • 81 Composition of SSIS Custom Task Installation
                                      • 82 Before You Modify the SSIS Packages
                                      • 83 Setup of a COM+ Application on the Application Server
                                          • Copyright and trademarks
Page 33: Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

ProcedureTo remove default access to the Management Console and create a group that does have access to the

console use the procedure described below

NOTE

Create your Management Console administrative group either on the server that hosts the

Management Console or in the Active Directory

1 In the context menu of the servers My Computer icon choose Manage

2 In the Computer Management dialog box choose Local Users and Groups Groups

NOTE

Alternatively you can perform analogous steps in Active Directory

3 In the 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

NOTE

This step is a necessary precursor to the completion of this procedure

10 In the Security dialog box click Copy to ensure that the System group retains its privileges

11 Remove access to the Management Console from all groups that should not have it

12 Choose Authentication in the center pane then disable Windows authentication

ResultUsers who have not been granted access to the Management Console can still open the Management

Console Web page but it contains no data or menu options This does not affect the access that a user

would otherwise have to Planning and Consolidation

345 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 32] Their rights in

Active Directory determine what they can access in the Console

By default any member of the Administrators Active Directory group on the application server or

domain has full access to all of the features of the Console except the Planning and Consolidation

logging area Access to Planning and Consolidation logging is controlled within the Planning and

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3354

Consolidation Administration Client task security The user must be granted View system logs task

privileges For more information see the SAP Library Planning and Consolidation Administrators Guide in

httpservicesapcominstguidesepm-bpc 100 version for the Microsoft platform

Your IT policy determines whether you grant access by group or user You may wish to create several

levels of Console users (read-only users for example) in your environment

To grant or limit access to users or groups you can add or remove the following privileges from the

areas described in this table

Privilege Rights Management Area

Task Manager and Kill Process Administrators group on application server or domain

Performance Monitor Counters Administrators group on application server or domain Power Users group on application server or domain Performance Monitor Users group on application server

Microsoft Analysis Services performance monitoring

Administrators group on application server or domain

Microsoft SQL Server Monitoring (performance counters and statistics)

Administrators group on application server or domain

346 Using Client Certificates

To enable the use of client certificates in Planning and Consolidation you must follow several manual

steps

NOTE

Planning 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 httptechnetmicrosoftcomen-us

librarycc753810aspx

For more information about configuring the client certificate mapping authentication see http

technetmicrosoftcomen-uslibrarycc732996(WS10)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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3454 CUSTOMER 2012-06-13

This option allows you to use a client certificate or username and password (Basic

authentication) to connect to Planning and Consolidation

2 Enable anonymous authentication

1 In the IIS Manager expand the node of the Planning and Consolidation web site

2 Select the ManagementConsole directory (ltWebsitegtManagementConsole) to open the

ManagementConsole home page

3 Double-click Authentication and enable Anonymous Authentication

4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way

as in step 3

5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the same

way as in step 3

3 Change the web configuration settings

1 Open the ltPC_MSgtWebsrvrWebBPCwebconfig file

2 Find the text clientCredentialType=Windows

3 Change value of clientCredentialType to None (clientCredentialType=None)

4 Open the PC_MSWebsrvrWebPOASBCwebconfig file Repeat steps 2 and 3

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3554

This page is left blank for documents that are printed on both sides

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

The installation of the Planning and Consolidation Administration Client allows administrators to

build and maintain Planning and Consolidation environments and models and administer security

All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions

add-in for Microsoft Office for more information see the SAP BusinessObjects EPM solutions add-in for

Microsoft Office help

NOTE

You must update the Administration Client to the same version as the server

If your PC is on a different domain than your server you must set the Internet Explorer

Security Zone value of the Planning and Consolidation client to prompt for user name and

password Otherwise the Planning and Consolidation Start Page does not display

41 Installing the Administration Client

Prerequisites

NOTE

For a definitive list of system requirements see the Product Availability Matrix on SAP Service

Marketplace at httpservicesapcompam Search on Planning and Consolidation

The following list describes the minimum software requirements

Microsoft Internet Explorer 70 or 80

Microsoft Office 2007 or 2010

NET Framework 20 or higher (install any required NET Framework Hotfixes by referring to

httpsupportmicrosoftcomkb)

Pentium IV (1 GHz CPU)

512 MB RAM

100 MB of free hard disk space in the My Documents folder

20 MB of free hard disk space for the installed Administration files

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

41 Installing the Administration Client

2012-06-13 CUSTOMER 3754

NOTE

We recommend that you install all of the latest Microsoft Windows hotfixes prior to installing

the Administration client For information about which hotfixes to install see http

updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us

ProcedureThe following procedure describes how to install the Administration Client on to an administratorrsquos

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 AddRemove Programs in the Windows Control Panel

3 Point your browser to the Planning and Consolidation Web at httpltPC_serverportgtsap

bpcweb

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

42 Installing the EPM Add-in

The Planning and Consolidation installation media does not contain the EPM addin setup program

You must download the most recent version of the full setup (EPM Add-inexe) from the Service

Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPC

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

43 Using the Client Auto Update Program

If Planning and Consolidation version 100 or later is installed you can use the Client Auto Update

program to set up the server so that it determines if an upgrade for a connecting Administration client

is necessary

The following describes the use of the auto update program for the Administration Client and the EPM

add-in

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

42 Installing the EPM Add-in

3854 CUSTOMER 2012-06-13

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 37]

To use the Client Auto Update program for the Administration Client proceed as follows

1 From the Server Manager select Options Client Options

2 Select Admin Update

3 If users without administrator rights on their machines use the auto update enter an administrator

ID and password in the Admin ID and Admin password fields respectively The Admin ID should be a

member of the local administrators group on all the computers running the auto update This

setting is not needed if all users have administrator rights on their machines

4 Select Update

For the EPM Add-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 Optionshellip 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 Market Place (SMP) at httpservicesapcom

All support packages and patches are available from the SMP as a zip file

EPMEXCLCLNTltSPLgtzip is for a support package

EPMEXCLCLNTltSPLgtPltPLgtzip 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 ltSP versiongtmsp

EPM Addin Support Package ltSP versiongtxml

For a patch these files are

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

2012-06-13 CUSTOMER 3954

EPM Addin Patch ltpatch numbergtmsp

EPM Addin Patch ltpatch numbergtxml

2 Unzip the zip file and extract the two files to the application server folder (WebsrvrWebBPC

Installation)

3 From the Server Manager select Options Client Options

The system lists the available packages Select the package that you want to use for the autoupdate

You can set a different update policy for each package listed

EXAMPLE

The following table illustrates some possible situations assuming that you have installed the

first full version (V1)

Available maintenance packages

V2-user updateV3-force updateV4-force updateV5-user update

V5-user update V5-user updateV6-auto updateV7-force update

Minimum Required Version

V4 V4 V7

Notification A prompt tells the user to install maintenance package V4 using the Forced Update behavior

If User Update is enabled the prompt informs the user that maintenance package V5 is available

A prompt tells the user to install maintenance package V7 using the Forced Update behavior

New Version V4 V4 or V5 V7

If you change the update policy for any package click Update to complete the change

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

4054 CUSTOMER 2012-06-13

5 Connection Issues

You may experience connection problems with ports the proxy server or programs and settings that

interact with these components If you have any issues related to connection review the following

recommendations and troubleshooting tips

51 Checking for Open Ports

You must ensure that all required ports are open for inboundoutbound 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 431181836 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

NOTE

You can use the following site to scan for the normal ports It allows you to manually enter a port

number to test

httpwwwmyserverorgportsniffasp

You can change the name of a port

52 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 Explorer Tools Internet Options Connections LAN Settings ) or at the server level

Enabling content filtering on the proxy server or firewall may cause connection problems

If external users are having trouble connecting to the server make sure the proxy server connects

using a fully qualified domain name Fully qualified domain names typically resolve both internal

and external IP addresses

Each secure Planning and Consolidation server name must be identified on the proxy server

Proxy servers may or may not require authentication which could conflict with Planning and

Consolidation authentication Do not use authentication on the proxy server The system

5 Connection Issues

51 Checking for Open Ports

2012-06-13 CUSTOMER 4154

synchronizes the user name and password on the remote server with the local user name and

password

NOTE

For more information about setting up an ISA proxy server contact SAP Support to request a

copy of Setting up ISA Proxy Server White Paper

Internet Explorer Settings 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

5 Connection Issues

52 Proxy Server and Firewall Issues

4254 CUSTOMER 2012-06-13

6 Installing Planning and Consolidation with Two Active Directory Domains

To set up a Planning and Consolidation 10 application server in a hosted environment and use your

own domain users follow this procedure In general you install Planning and Consolidation on the

host domain use the host domain account and assign it to the Planning and Consolidation users

SysAdmin Admin and Users Then you accept one way trust (the host domain trusts your domain)

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

6 Installing Planning and Consolidation with Two Active Directory Domains

2012-06-13 CUSTOMER 4354

This page is left blank for documents that are printed on both sides

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

This section describes best practices and instructions for installing Planning and Consolidation in a

Terminal Services or Citrix Server deployment

71 Terminal Services Home Directories

We recommend using Terminal Server home directories rather than using the userrsquos 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

72 System Requirements

The Citrix server should be one of the following systems

XenApp 5 Enterprise

XenApp 5 Platinum

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 37])

73 Installing Planning and Consolidation

Prerequisites

The server installation files have been downloaded from SAP Service Marketplace and installed

Procedure

The following steps outline how to install the Planning and Consolidation clients in a Terminal Services

(TS) or Citrix Server deployment

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

71 Terminal Services Home Directories

2012-06-13 CUSTOMER 4554

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 userinstall

4 Open a browser and connect to the URL httpltPC_serverportgtsapbpcweb

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 userexecute 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 Iexploreexe http(s)

ltServerNamegt-NetBIOS or FQDNsapbpcweb

To publish Planning and Consolidation Administration CProgram FilesPC_MS

BPCAdminMainexe

74 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 userrsquos desktop) must be moved to the All UsersDesktop folder

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

74 Creating a Shortcut to the Launch Page

4654 CUSTOMER 2012-06-13

8 Installing SSIS Custom Tasks

This section provides background information and instructions for installing SQL Server Integration

Services (SSIS) for SQL Server 2008 and SQL Server 2012

The Planning and Consolidation Data Manager component supports and uses SSIS Since SQL Server

2008 and SQL Server 2012 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

81 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 Filelistxml 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

OSoftSetupexe ‒ 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 or OSoftSSIS2012_Client on the client machine followed by the SQL Server

version If you want to use SQL 2008 Tasks under the SQL 2012 environment you must install

OSoftSSIS2008_Client on the application server For detailed information see SAP Note 1707410

You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package by extracting

OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPC

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 or

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4754

OSoftSSIS2012_Client for creating a COM+ application For more information see Before You Modify

the SSIS Packages [page 50] and Setup of a COM+ Application on the Application Server [page 51]

Bin folder

This folder contains the following components

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCCachedll Planning and Consolidation Cache file

BPCDataFlowPackagedll or BPCDataFlowPackage2012dll

BPCDMdll

BPCDMTaskMaindll COM+ component

BPCFilePreviewdll

BPCGacUtil_20exe System File

BPCGacUtil_40exe System File

BPCImpersonatordll Planning and Consolidation Impersonator

BPCLogicdll

BPCScriptdll

BPCServerZipdll

BPCServiceResdll

BPCTransferMembersdll

BPCWriteBackdll

InteropDTSdll

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

4854 CUSTOMER 2012-06-13

Name Remark

OSoftAdminServerdll

OSoftAuditdll

OSoftComLibServerdll

OSoftCommonResQrydll

OSoftConfigurationdll

OSoftCustomXMLSvrdll

OSoftDatabaseADMINdll

OSoftDatabaseSYSADMINdll

OSoftDatabaseSYSADMINDMdll

OSoftDatabaseUSERdll

OSoftDMDTSXExecutedll or OSoftDMDTSXExecute2012dll

OSoftDMTaskFormdll

OSoftDMTaskMaindll

OSoftDMToolsdll

OSoftFileManagedll

OSoftLoggingdll

OSoftLogWriterdll

OSoftMetaDatadll

OSoftSQEdll

OSoftSystemConfigdll

OutlookSoftconfig Configuration file to connect DB server

XceedCompressiondll XceedZip file

XceedCompressionFormatsdll XceedZip file

XceedFileSystemdll XceedZip file

XceedZipdll XceedZip file

Config folder

This folder has FileListxml 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 FileListxml 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

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4954

OSoftSetupexe

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

NOTE

If you installed the OSoftSSIS2008_Client or OSoftSSIS2012_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

Resources Folder

This folder contains the BPCServicesdll and BPCServiceUIdll files which contain resource text

Only English resources are included for the SSIS custom tasks

82 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

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008 and 2012 respectively

8 Installing SSIS Custom Tasks

82 Before You Modify the SSIS Packages

5054 CUSTOMER 2012-06-13

Name Remark

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012 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

lthellipgtOSoftSSIS2008_Clientbin or lthellipgtOSoftSSIS2012_Clientbin

On the Planning and Consolidation application server

ltdrivegtWebsrvrbin

2 Paste these files into the folder 100DTSTasks for SQL Server 2008 or into 110DTSTasks for

SQL Server 2012 For example if you install your SQL 2008 server or R2 on CProgram Files

Microsoft SQL Server paste all files into the CProgram Files (x86)Microsoft SQL Server

100DTSTasks folder

In Integration Services set the property Run64BitRunTime to True

83 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 or OSoftSSIS2012_Client on the

application server

8 Installing SSIS Custom Tasks

83 Setup of a COM+ Application on the Application Server

2012-06-13 CUSTOMER 5154

Typographic Conventions

Example Description

ltgt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example Enter your ltUser Namegt

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 httpwwwsapcom

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

5254 CUSTOMER 2012-06-13

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

  • SAP BusinessObjects Planning and Consolidation 100
    • Table of Contents
    • 1 Introduction
      • 11 SAP Notes for the Installation
      • 12 Naming Conventions
        • 2 Installing Planning and Consolidation Servers
          • 21 Basic Steps
          • 22 Prerequisites
          • 23 Before Starting the Planning and Consolidation Server Installation
          • 24 Logging on to Servers
          • 25 Service-level Accounts
          • 26 Standard and Advanced Settings
          • 27 Installing the Prerequisites
            • 271 Installing the Prerequisites ndash Basic Steps
            • 272 Installing the Operating System
            • 273 Installing the SQL Server
            • 274 Installing Analysis Services
            • 275 Installing the Anti-Cross Site Scripting Library
              • 28 Installing on a Single Server
              • 29 Installing the Server in a Multiserver Configuration
                • 3 After Installing Planning and Consolidation Servers
                  • 31 Post-Installation Steps
                  • 32 Connecting to Solution Manager Diagnostics
                  • 33 Configuring the Planning and Consolidation NET Application Servers
                  • 34 Post-Installation Optional Configuration Steps
                    • 341 Enabling the Management Console
                    • 342 Setting Up ODBC Logging in IIS for the Default Web Site
                    • 343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2
                    • 344 Removing Default Access to the Console
                    • 345 Management Console Access Control
                    • 346 Using Client Certificates
                        • 4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office
                          • 41 Installing the Administration Client
                          • 42 Installing the EPM Add-in
                          • 43 Using the Client Auto Update Program
                            • 5 Connection Issues
                              • 51 Checking for Open Ports
                              • 52 Proxy Server and Firewall Issues
                                • 6 Installing Planning and Consolidation with Two Active Directory Domains
                                • 7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
                                  • 71 Terminal Services Home Directories
                                  • 72 System Requirements
                                  • 73 Installing Planning and Consolidation
                                  • 74 Creating a Shortcut to the Launch Page
                                    • 8 Installing SSIS Custom Tasks
                                      • 81 Composition of SSIS Custom Task Installation
                                      • 82 Before You Modify the SSIS Packages
                                      • 83 Setup of a COM+ Application on the Application Server
                                          • Copyright and trademarks
Page 34: Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

Consolidation Administration Client task security The user must be granted View system logs task

privileges For more information see the SAP Library Planning and Consolidation Administrators Guide in

httpservicesapcominstguidesepm-bpc 100 version for the Microsoft platform

Your IT policy determines whether you grant access by group or user You may wish to create several

levels of Console users (read-only users for example) in your environment

To grant or limit access to users or groups you can add or remove the following privileges from the

areas described in this table

Privilege Rights Management Area

Task Manager and Kill Process Administrators group on application server or domain

Performance Monitor Counters Administrators group on application server or domain Power Users group on application server or domain Performance Monitor Users group on application server

Microsoft Analysis Services performance monitoring

Administrators group on application server or domain

Microsoft SQL Server Monitoring (performance counters and statistics)

Administrators group on application server or domain

346 Using Client Certificates

To enable the use of client certificates in Planning and Consolidation you must follow several manual

steps

NOTE

Planning 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 httptechnetmicrosoftcomen-us

librarycc753810aspx

For more information about configuring the client certificate mapping authentication see http

technetmicrosoftcomen-uslibrarycc732996(WS10)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

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

3454 CUSTOMER 2012-06-13

This option allows you to use a client certificate or username and password (Basic

authentication) to connect to Planning and Consolidation

2 Enable anonymous authentication

1 In the IIS Manager expand the node of the Planning and Consolidation web site

2 Select the ManagementConsole directory (ltWebsitegtManagementConsole) to open the

ManagementConsole home page

3 Double-click Authentication and enable Anonymous Authentication

4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way

as in step 3

5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the same

way as in step 3

3 Change the web configuration settings

1 Open the ltPC_MSgtWebsrvrWebBPCwebconfig file

2 Find the text clientCredentialType=Windows

3 Change value of clientCredentialType to None (clientCredentialType=None)

4 Open the PC_MSWebsrvrWebPOASBCwebconfig file Repeat steps 2 and 3

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3554

This page is left blank for documents that are printed on both sides

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

The installation of the Planning and Consolidation Administration Client allows administrators to

build and maintain Planning and Consolidation environments and models and administer security

All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions

add-in for Microsoft Office for more information see the SAP BusinessObjects EPM solutions add-in for

Microsoft Office help

NOTE

You must update the Administration Client to the same version as the server

If your PC is on a different domain than your server you must set the Internet Explorer

Security Zone value of the Planning and Consolidation client to prompt for user name and

password Otherwise the Planning and Consolidation Start Page does not display

41 Installing the Administration Client

Prerequisites

NOTE

For a definitive list of system requirements see the Product Availability Matrix on SAP Service

Marketplace at httpservicesapcompam Search on Planning and Consolidation

The following list describes the minimum software requirements

Microsoft Internet Explorer 70 or 80

Microsoft Office 2007 or 2010

NET Framework 20 or higher (install any required NET Framework Hotfixes by referring to

httpsupportmicrosoftcomkb)

Pentium IV (1 GHz CPU)

512 MB RAM

100 MB of free hard disk space in the My Documents folder

20 MB of free hard disk space for the installed Administration files

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

41 Installing the Administration Client

2012-06-13 CUSTOMER 3754

NOTE

We recommend that you install all of the latest Microsoft Windows hotfixes prior to installing

the Administration client For information about which hotfixes to install see http

updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us

ProcedureThe following procedure describes how to install the Administration Client on to an administratorrsquos

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 AddRemove Programs in the Windows Control Panel

3 Point your browser to the Planning and Consolidation Web at httpltPC_serverportgtsap

bpcweb

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

42 Installing the EPM Add-in

The Planning and Consolidation installation media does not contain the EPM addin setup program

You must download the most recent version of the full setup (EPM Add-inexe) from the Service

Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPC

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

43 Using the Client Auto Update Program

If Planning and Consolidation version 100 or later is installed you can use the Client Auto Update

program to set up the server so that it determines if an upgrade for a connecting Administration client

is necessary

The following describes the use of the auto update program for the Administration Client and the EPM

add-in

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

42 Installing the EPM Add-in

3854 CUSTOMER 2012-06-13

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 37]

To use the Client Auto Update program for the Administration Client proceed as follows

1 From the Server Manager select Options Client Options

2 Select Admin Update

3 If users without administrator rights on their machines use the auto update enter an administrator

ID and password in the Admin ID and Admin password fields respectively The Admin ID should be a

member of the local administrators group on all the computers running the auto update This

setting is not needed if all users have administrator rights on their machines

4 Select Update

For the EPM Add-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 Optionshellip 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 Market Place (SMP) at httpservicesapcom

All support packages and patches are available from the SMP as a zip file

EPMEXCLCLNTltSPLgtzip is for a support package

EPMEXCLCLNTltSPLgtPltPLgtzip 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 ltSP versiongtmsp

EPM Addin Support Package ltSP versiongtxml

For a patch these files are

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

2012-06-13 CUSTOMER 3954

EPM Addin Patch ltpatch numbergtmsp

EPM Addin Patch ltpatch numbergtxml

2 Unzip the zip file and extract the two files to the application server folder (WebsrvrWebBPC

Installation)

3 From the Server Manager select Options Client Options

The system lists the available packages Select the package that you want to use for the autoupdate

You can set a different update policy for each package listed

EXAMPLE

The following table illustrates some possible situations assuming that you have installed the

first full version (V1)

Available maintenance packages

V2-user updateV3-force updateV4-force updateV5-user update

V5-user update V5-user updateV6-auto updateV7-force update

Minimum Required Version

V4 V4 V7

Notification A prompt tells the user to install maintenance package V4 using the Forced Update behavior

If User Update is enabled the prompt informs the user that maintenance package V5 is available

A prompt tells the user to install maintenance package V7 using the Forced Update behavior

New Version V4 V4 or V5 V7

If you change the update policy for any package click Update to complete the change

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

4054 CUSTOMER 2012-06-13

5 Connection Issues

You may experience connection problems with ports the proxy server or programs and settings that

interact with these components If you have any issues related to connection review the following

recommendations and troubleshooting tips

51 Checking for Open Ports

You must ensure that all required ports are open for inboundoutbound 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 431181836 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

NOTE

You can use the following site to scan for the normal ports It allows you to manually enter a port

number to test

httpwwwmyserverorgportsniffasp

You can change the name of a port

52 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 Explorer Tools Internet Options Connections LAN Settings ) or at the server level

Enabling content filtering on the proxy server or firewall may cause connection problems

If external users are having trouble connecting to the server make sure the proxy server connects

using a fully qualified domain name Fully qualified domain names typically resolve both internal

and external IP addresses

Each secure Planning and Consolidation server name must be identified on the proxy server

Proxy servers may or may not require authentication which could conflict with Planning and

Consolidation authentication Do not use authentication on the proxy server The system

5 Connection Issues

51 Checking for Open Ports

2012-06-13 CUSTOMER 4154

synchronizes the user name and password on the remote server with the local user name and

password

NOTE

For more information about setting up an ISA proxy server contact SAP Support to request a

copy of Setting up ISA Proxy Server White Paper

Internet Explorer Settings 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

5 Connection Issues

52 Proxy Server and Firewall Issues

4254 CUSTOMER 2012-06-13

6 Installing Planning and Consolidation with Two Active Directory Domains

To set up a Planning and Consolidation 10 application server in a hosted environment and use your

own domain users follow this procedure In general you install Planning and Consolidation on the

host domain use the host domain account and assign it to the Planning and Consolidation users

SysAdmin Admin and Users Then you accept one way trust (the host domain trusts your domain)

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

6 Installing Planning and Consolidation with Two Active Directory Domains

2012-06-13 CUSTOMER 4354

This page is left blank for documents that are printed on both sides

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

This section describes best practices and instructions for installing Planning and Consolidation in a

Terminal Services or Citrix Server deployment

71 Terminal Services Home Directories

We recommend using Terminal Server home directories rather than using the userrsquos 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

72 System Requirements

The Citrix server should be one of the following systems

XenApp 5 Enterprise

XenApp 5 Platinum

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 37])

73 Installing Planning and Consolidation

Prerequisites

The server installation files have been downloaded from SAP Service Marketplace and installed

Procedure

The following steps outline how to install the Planning and Consolidation clients in a Terminal Services

(TS) or Citrix Server deployment

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

71 Terminal Services Home Directories

2012-06-13 CUSTOMER 4554

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 userinstall

4 Open a browser and connect to the URL httpltPC_serverportgtsapbpcweb

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 userexecute 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 Iexploreexe http(s)

ltServerNamegt-NetBIOS or FQDNsapbpcweb

To publish Planning and Consolidation Administration CProgram FilesPC_MS

BPCAdminMainexe

74 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 userrsquos desktop) must be moved to the All UsersDesktop folder

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

74 Creating a Shortcut to the Launch Page

4654 CUSTOMER 2012-06-13

8 Installing SSIS Custom Tasks

This section provides background information and instructions for installing SQL Server Integration

Services (SSIS) for SQL Server 2008 and SQL Server 2012

The Planning and Consolidation Data Manager component supports and uses SSIS Since SQL Server

2008 and SQL Server 2012 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

81 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 Filelistxml 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

OSoftSetupexe ‒ 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 or OSoftSSIS2012_Client on the client machine followed by the SQL Server

version If you want to use SQL 2008 Tasks under the SQL 2012 environment you must install

OSoftSSIS2008_Client on the application server For detailed information see SAP Note 1707410

You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package by extracting

OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPC

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 or

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4754

OSoftSSIS2012_Client for creating a COM+ application For more information see Before You Modify

the SSIS Packages [page 50] and Setup of a COM+ Application on the Application Server [page 51]

Bin folder

This folder contains the following components

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCCachedll Planning and Consolidation Cache file

BPCDataFlowPackagedll or BPCDataFlowPackage2012dll

BPCDMdll

BPCDMTaskMaindll COM+ component

BPCFilePreviewdll

BPCGacUtil_20exe System File

BPCGacUtil_40exe System File

BPCImpersonatordll Planning and Consolidation Impersonator

BPCLogicdll

BPCScriptdll

BPCServerZipdll

BPCServiceResdll

BPCTransferMembersdll

BPCWriteBackdll

InteropDTSdll

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

4854 CUSTOMER 2012-06-13

Name Remark

OSoftAdminServerdll

OSoftAuditdll

OSoftComLibServerdll

OSoftCommonResQrydll

OSoftConfigurationdll

OSoftCustomXMLSvrdll

OSoftDatabaseADMINdll

OSoftDatabaseSYSADMINdll

OSoftDatabaseSYSADMINDMdll

OSoftDatabaseUSERdll

OSoftDMDTSXExecutedll or OSoftDMDTSXExecute2012dll

OSoftDMTaskFormdll

OSoftDMTaskMaindll

OSoftDMToolsdll

OSoftFileManagedll

OSoftLoggingdll

OSoftLogWriterdll

OSoftMetaDatadll

OSoftSQEdll

OSoftSystemConfigdll

OutlookSoftconfig Configuration file to connect DB server

XceedCompressiondll XceedZip file

XceedCompressionFormatsdll XceedZip file

XceedFileSystemdll XceedZip file

XceedZipdll XceedZip file

Config folder

This folder has FileListxml 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 FileListxml 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

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4954

OSoftSetupexe

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

NOTE

If you installed the OSoftSSIS2008_Client or OSoftSSIS2012_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

Resources Folder

This folder contains the BPCServicesdll and BPCServiceUIdll files which contain resource text

Only English resources are included for the SSIS custom tasks

82 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

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008 and 2012 respectively

8 Installing SSIS Custom Tasks

82 Before You Modify the SSIS Packages

5054 CUSTOMER 2012-06-13

Name Remark

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012 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

lthellipgtOSoftSSIS2008_Clientbin or lthellipgtOSoftSSIS2012_Clientbin

On the Planning and Consolidation application server

ltdrivegtWebsrvrbin

2 Paste these files into the folder 100DTSTasks for SQL Server 2008 or into 110DTSTasks for

SQL Server 2012 For example if you install your SQL 2008 server or R2 on CProgram Files

Microsoft SQL Server paste all files into the CProgram Files (x86)Microsoft SQL Server

100DTSTasks folder

In Integration Services set the property Run64BitRunTime to True

83 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 or OSoftSSIS2012_Client on the

application server

8 Installing SSIS Custom Tasks

83 Setup of a COM+ Application on the Application Server

2012-06-13 CUSTOMER 5154

Typographic Conventions

Example Description

ltgt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example Enter your ltUser Namegt

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 httpwwwsapcom

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

5254 CUSTOMER 2012-06-13

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

  • SAP BusinessObjects Planning and Consolidation 100
    • Table of Contents
    • 1 Introduction
      • 11 SAP Notes for the Installation
      • 12 Naming Conventions
        • 2 Installing Planning and Consolidation Servers
          • 21 Basic Steps
          • 22 Prerequisites
          • 23 Before Starting the Planning and Consolidation Server Installation
          • 24 Logging on to Servers
          • 25 Service-level Accounts
          • 26 Standard and Advanced Settings
          • 27 Installing the Prerequisites
            • 271 Installing the Prerequisites ndash Basic Steps
            • 272 Installing the Operating System
            • 273 Installing the SQL Server
            • 274 Installing Analysis Services
            • 275 Installing the Anti-Cross Site Scripting Library
              • 28 Installing on a Single Server
              • 29 Installing the Server in a Multiserver Configuration
                • 3 After Installing Planning and Consolidation Servers
                  • 31 Post-Installation Steps
                  • 32 Connecting to Solution Manager Diagnostics
                  • 33 Configuring the Planning and Consolidation NET Application Servers
                  • 34 Post-Installation Optional Configuration Steps
                    • 341 Enabling the Management Console
                    • 342 Setting Up ODBC Logging in IIS for the Default Web Site
                    • 343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2
                    • 344 Removing Default Access to the Console
                    • 345 Management Console Access Control
                    • 346 Using Client Certificates
                        • 4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office
                          • 41 Installing the Administration Client
                          • 42 Installing the EPM Add-in
                          • 43 Using the Client Auto Update Program
                            • 5 Connection Issues
                              • 51 Checking for Open Ports
                              • 52 Proxy Server and Firewall Issues
                                • 6 Installing Planning and Consolidation with Two Active Directory Domains
                                • 7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
                                  • 71 Terminal Services Home Directories
                                  • 72 System Requirements
                                  • 73 Installing Planning and Consolidation
                                  • 74 Creating a Shortcut to the Launch Page
                                    • 8 Installing SSIS Custom Tasks
                                      • 81 Composition of SSIS Custom Task Installation
                                      • 82 Before You Modify the SSIS Packages
                                      • 83 Setup of a COM+ Application on the Application Server
                                          • Copyright and trademarks
Page 35: Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

This option allows you to use a client certificate or username and password (Basic

authentication) to connect to Planning and Consolidation

2 Enable anonymous authentication

1 In the IIS Manager expand the node of the Planning and Consolidation web site

2 Select the ManagementConsole directory (ltWebsitegtManagementConsole) to open the

ManagementConsole home page

3 Double-click Authentication and enable Anonymous Authentication

4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way

as in step 3

5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the same

way as in step 3

3 Change the web configuration settings

1 Open the ltPC_MSgtWebsrvrWebBPCwebconfig file

2 Find the text clientCredentialType=Windows

3 Change value of clientCredentialType to None (clientCredentialType=None)

4 Open the PC_MSWebsrvrWebPOASBCwebconfig file Repeat steps 2 and 3

3 After Installing Planning and Consolidation Servers

34 Post-Installation Optional Configuration Steps

2012-06-13 CUSTOMER 3554

This page is left blank for documents that are printed on both sides

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

The installation of the Planning and Consolidation Administration Client allows administrators to

build and maintain Planning and Consolidation environments and models and administer security

All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions

add-in for Microsoft Office for more information see the SAP BusinessObjects EPM solutions add-in for

Microsoft Office help

NOTE

You must update the Administration Client to the same version as the server

If your PC is on a different domain than your server you must set the Internet Explorer

Security Zone value of the Planning and Consolidation client to prompt for user name and

password Otherwise the Planning and Consolidation Start Page does not display

41 Installing the Administration Client

Prerequisites

NOTE

For a definitive list of system requirements see the Product Availability Matrix on SAP Service

Marketplace at httpservicesapcompam Search on Planning and Consolidation

The following list describes the minimum software requirements

Microsoft Internet Explorer 70 or 80

Microsoft Office 2007 or 2010

NET Framework 20 or higher (install any required NET Framework Hotfixes by referring to

httpsupportmicrosoftcomkb)

Pentium IV (1 GHz CPU)

512 MB RAM

100 MB of free hard disk space in the My Documents folder

20 MB of free hard disk space for the installed Administration files

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

41 Installing the Administration Client

2012-06-13 CUSTOMER 3754

NOTE

We recommend that you install all of the latest Microsoft Windows hotfixes prior to installing

the Administration client For information about which hotfixes to install see http

updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us

ProcedureThe following procedure describes how to install the Administration Client on to an administratorrsquos

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 AddRemove Programs in the Windows Control Panel

3 Point your browser to the Planning and Consolidation Web at httpltPC_serverportgtsap

bpcweb

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

42 Installing the EPM Add-in

The Planning and Consolidation installation media does not contain the EPM addin setup program

You must download the most recent version of the full setup (EPM Add-inexe) from the Service

Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPC

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

43 Using the Client Auto Update Program

If Planning and Consolidation version 100 or later is installed you can use the Client Auto Update

program to set up the server so that it determines if an upgrade for a connecting Administration client

is necessary

The following describes the use of the auto update program for the Administration Client and the EPM

add-in

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

42 Installing the EPM Add-in

3854 CUSTOMER 2012-06-13

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 37]

To use the Client Auto Update program for the Administration Client proceed as follows

1 From the Server Manager select Options Client Options

2 Select Admin Update

3 If users without administrator rights on their machines use the auto update enter an administrator

ID and password in the Admin ID and Admin password fields respectively The Admin ID should be a

member of the local administrators group on all the computers running the auto update This

setting is not needed if all users have administrator rights on their machines

4 Select Update

For the EPM Add-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 Optionshellip 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 Market Place (SMP) at httpservicesapcom

All support packages and patches are available from the SMP as a zip file

EPMEXCLCLNTltSPLgtzip is for a support package

EPMEXCLCLNTltSPLgtPltPLgtzip 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 ltSP versiongtmsp

EPM Addin Support Package ltSP versiongtxml

For a patch these files are

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

2012-06-13 CUSTOMER 3954

EPM Addin Patch ltpatch numbergtmsp

EPM Addin Patch ltpatch numbergtxml

2 Unzip the zip file and extract the two files to the application server folder (WebsrvrWebBPC

Installation)

3 From the Server Manager select Options Client Options

The system lists the available packages Select the package that you want to use for the autoupdate

You can set a different update policy for each package listed

EXAMPLE

The following table illustrates some possible situations assuming that you have installed the

first full version (V1)

Available maintenance packages

V2-user updateV3-force updateV4-force updateV5-user update

V5-user update V5-user updateV6-auto updateV7-force update

Minimum Required Version

V4 V4 V7

Notification A prompt tells the user to install maintenance package V4 using the Forced Update behavior

If User Update is enabled the prompt informs the user that maintenance package V5 is available

A prompt tells the user to install maintenance package V7 using the Forced Update behavior

New Version V4 V4 or V5 V7

If you change the update policy for any package click Update to complete the change

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

4054 CUSTOMER 2012-06-13

5 Connection Issues

You may experience connection problems with ports the proxy server or programs and settings that

interact with these components If you have any issues related to connection review the following

recommendations and troubleshooting tips

51 Checking for Open Ports

You must ensure that all required ports are open for inboundoutbound 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 431181836 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

NOTE

You can use the following site to scan for the normal ports It allows you to manually enter a port

number to test

httpwwwmyserverorgportsniffasp

You can change the name of a port

52 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 Explorer Tools Internet Options Connections LAN Settings ) or at the server level

Enabling content filtering on the proxy server or firewall may cause connection problems

If external users are having trouble connecting to the server make sure the proxy server connects

using a fully qualified domain name Fully qualified domain names typically resolve both internal

and external IP addresses

Each secure Planning and Consolidation server name must be identified on the proxy server

Proxy servers may or may not require authentication which could conflict with Planning and

Consolidation authentication Do not use authentication on the proxy server The system

5 Connection Issues

51 Checking for Open Ports

2012-06-13 CUSTOMER 4154

synchronizes the user name and password on the remote server with the local user name and

password

NOTE

For more information about setting up an ISA proxy server contact SAP Support to request a

copy of Setting up ISA Proxy Server White Paper

Internet Explorer Settings 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

5 Connection Issues

52 Proxy Server and Firewall Issues

4254 CUSTOMER 2012-06-13

6 Installing Planning and Consolidation with Two Active Directory Domains

To set up a Planning and Consolidation 10 application server in a hosted environment and use your

own domain users follow this procedure In general you install Planning and Consolidation on the

host domain use the host domain account and assign it to the Planning and Consolidation users

SysAdmin Admin and Users Then you accept one way trust (the host domain trusts your domain)

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

6 Installing Planning and Consolidation with Two Active Directory Domains

2012-06-13 CUSTOMER 4354

This page is left blank for documents that are printed on both sides

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

This section describes best practices and instructions for installing Planning and Consolidation in a

Terminal Services or Citrix Server deployment

71 Terminal Services Home Directories

We recommend using Terminal Server home directories rather than using the userrsquos 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

72 System Requirements

The Citrix server should be one of the following systems

XenApp 5 Enterprise

XenApp 5 Platinum

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 37])

73 Installing Planning and Consolidation

Prerequisites

The server installation files have been downloaded from SAP Service Marketplace and installed

Procedure

The following steps outline how to install the Planning and Consolidation clients in a Terminal Services

(TS) or Citrix Server deployment

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

71 Terminal Services Home Directories

2012-06-13 CUSTOMER 4554

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 userinstall

4 Open a browser and connect to the URL httpltPC_serverportgtsapbpcweb

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 userexecute 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 Iexploreexe http(s)

ltServerNamegt-NetBIOS or FQDNsapbpcweb

To publish Planning and Consolidation Administration CProgram FilesPC_MS

BPCAdminMainexe

74 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 userrsquos desktop) must be moved to the All UsersDesktop folder

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

74 Creating a Shortcut to the Launch Page

4654 CUSTOMER 2012-06-13

8 Installing SSIS Custom Tasks

This section provides background information and instructions for installing SQL Server Integration

Services (SSIS) for SQL Server 2008 and SQL Server 2012

The Planning and Consolidation Data Manager component supports and uses SSIS Since SQL Server

2008 and SQL Server 2012 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

81 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 Filelistxml 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

OSoftSetupexe ‒ 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 or OSoftSSIS2012_Client on the client machine followed by the SQL Server

version If you want to use SQL 2008 Tasks under the SQL 2012 environment you must install

OSoftSSIS2008_Client on the application server For detailed information see SAP Note 1707410

You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package by extracting

OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPC

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 or

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4754

OSoftSSIS2012_Client for creating a COM+ application For more information see Before You Modify

the SSIS Packages [page 50] and Setup of a COM+ Application on the Application Server [page 51]

Bin folder

This folder contains the following components

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCCachedll Planning and Consolidation Cache file

BPCDataFlowPackagedll or BPCDataFlowPackage2012dll

BPCDMdll

BPCDMTaskMaindll COM+ component

BPCFilePreviewdll

BPCGacUtil_20exe System File

BPCGacUtil_40exe System File

BPCImpersonatordll Planning and Consolidation Impersonator

BPCLogicdll

BPCScriptdll

BPCServerZipdll

BPCServiceResdll

BPCTransferMembersdll

BPCWriteBackdll

InteropDTSdll

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

4854 CUSTOMER 2012-06-13

Name Remark

OSoftAdminServerdll

OSoftAuditdll

OSoftComLibServerdll

OSoftCommonResQrydll

OSoftConfigurationdll

OSoftCustomXMLSvrdll

OSoftDatabaseADMINdll

OSoftDatabaseSYSADMINdll

OSoftDatabaseSYSADMINDMdll

OSoftDatabaseUSERdll

OSoftDMDTSXExecutedll or OSoftDMDTSXExecute2012dll

OSoftDMTaskFormdll

OSoftDMTaskMaindll

OSoftDMToolsdll

OSoftFileManagedll

OSoftLoggingdll

OSoftLogWriterdll

OSoftMetaDatadll

OSoftSQEdll

OSoftSystemConfigdll

OutlookSoftconfig Configuration file to connect DB server

XceedCompressiondll XceedZip file

XceedCompressionFormatsdll XceedZip file

XceedFileSystemdll XceedZip file

XceedZipdll XceedZip file

Config folder

This folder has FileListxml 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 FileListxml 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

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4954

OSoftSetupexe

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

NOTE

If you installed the OSoftSSIS2008_Client or OSoftSSIS2012_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

Resources Folder

This folder contains the BPCServicesdll and BPCServiceUIdll files which contain resource text

Only English resources are included for the SSIS custom tasks

82 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

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008 and 2012 respectively

8 Installing SSIS Custom Tasks

82 Before You Modify the SSIS Packages

5054 CUSTOMER 2012-06-13

Name Remark

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012 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

lthellipgtOSoftSSIS2008_Clientbin or lthellipgtOSoftSSIS2012_Clientbin

On the Planning and Consolidation application server

ltdrivegtWebsrvrbin

2 Paste these files into the folder 100DTSTasks for SQL Server 2008 or into 110DTSTasks for

SQL Server 2012 For example if you install your SQL 2008 server or R2 on CProgram Files

Microsoft SQL Server paste all files into the CProgram Files (x86)Microsoft SQL Server

100DTSTasks folder

In Integration Services set the property Run64BitRunTime to True

83 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 or OSoftSSIS2012_Client on the

application server

8 Installing SSIS Custom Tasks

83 Setup of a COM+ Application on the Application Server

2012-06-13 CUSTOMER 5154

Typographic Conventions

Example Description

ltgt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example Enter your ltUser Namegt

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 httpwwwsapcom

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

5254 CUSTOMER 2012-06-13

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

  • SAP BusinessObjects Planning and Consolidation 100
    • Table of Contents
    • 1 Introduction
      • 11 SAP Notes for the Installation
      • 12 Naming Conventions
        • 2 Installing Planning and Consolidation Servers
          • 21 Basic Steps
          • 22 Prerequisites
          • 23 Before Starting the Planning and Consolidation Server Installation
          • 24 Logging on to Servers
          • 25 Service-level Accounts
          • 26 Standard and Advanced Settings
          • 27 Installing the Prerequisites
            • 271 Installing the Prerequisites ndash Basic Steps
            • 272 Installing the Operating System
            • 273 Installing the SQL Server
            • 274 Installing Analysis Services
            • 275 Installing the Anti-Cross Site Scripting Library
              • 28 Installing on a Single Server
              • 29 Installing the Server in a Multiserver Configuration
                • 3 After Installing Planning and Consolidation Servers
                  • 31 Post-Installation Steps
                  • 32 Connecting to Solution Manager Diagnostics
                  • 33 Configuring the Planning and Consolidation NET Application Servers
                  • 34 Post-Installation Optional Configuration Steps
                    • 341 Enabling the Management Console
                    • 342 Setting Up ODBC Logging in IIS for the Default Web Site
                    • 343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2
                    • 344 Removing Default Access to the Console
                    • 345 Management Console Access Control
                    • 346 Using Client Certificates
                        • 4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office
                          • 41 Installing the Administration Client
                          • 42 Installing the EPM Add-in
                          • 43 Using the Client Auto Update Program
                            • 5 Connection Issues
                              • 51 Checking for Open Ports
                              • 52 Proxy Server and Firewall Issues
                                • 6 Installing Planning and Consolidation with Two Active Directory Domains
                                • 7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
                                  • 71 Terminal Services Home Directories
                                  • 72 System Requirements
                                  • 73 Installing Planning and Consolidation
                                  • 74 Creating a Shortcut to the Launch Page
                                    • 8 Installing SSIS Custom Tasks
                                      • 81 Composition of SSIS Custom Task Installation
                                      • 82 Before You Modify the SSIS Packages
                                      • 83 Setup of a COM+ Application on the Application Server
                                          • Copyright and trademarks
Page 36: Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

This page is left blank for documents that are printed on both sides

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

The installation of the Planning and Consolidation Administration Client allows administrators to

build and maintain Planning and Consolidation environments and models and administer security

All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions

add-in for Microsoft Office for more information see the SAP BusinessObjects EPM solutions add-in for

Microsoft Office help

NOTE

You must update the Administration Client to the same version as the server

If your PC is on a different domain than your server you must set the Internet Explorer

Security Zone value of the Planning and Consolidation client to prompt for user name and

password Otherwise the Planning and Consolidation Start Page does not display

41 Installing the Administration Client

Prerequisites

NOTE

For a definitive list of system requirements see the Product Availability Matrix on SAP Service

Marketplace at httpservicesapcompam Search on Planning and Consolidation

The following list describes the minimum software requirements

Microsoft Internet Explorer 70 or 80

Microsoft Office 2007 or 2010

NET Framework 20 or higher (install any required NET Framework Hotfixes by referring to

httpsupportmicrosoftcomkb)

Pentium IV (1 GHz CPU)

512 MB RAM

100 MB of free hard disk space in the My Documents folder

20 MB of free hard disk space for the installed Administration files

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

41 Installing the Administration Client

2012-06-13 CUSTOMER 3754

NOTE

We recommend that you install all of the latest Microsoft Windows hotfixes prior to installing

the Administration client For information about which hotfixes to install see http

updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us

ProcedureThe following procedure describes how to install the Administration Client on to an administratorrsquos

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 AddRemove Programs in the Windows Control Panel

3 Point your browser to the Planning and Consolidation Web at httpltPC_serverportgtsap

bpcweb

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

42 Installing the EPM Add-in

The Planning and Consolidation installation media does not contain the EPM addin setup program

You must download the most recent version of the full setup (EPM Add-inexe) from the Service

Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPC

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

43 Using the Client Auto Update Program

If Planning and Consolidation version 100 or later is installed you can use the Client Auto Update

program to set up the server so that it determines if an upgrade for a connecting Administration client

is necessary

The following describes the use of the auto update program for the Administration Client and the EPM

add-in

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

42 Installing the EPM Add-in

3854 CUSTOMER 2012-06-13

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 37]

To use the Client Auto Update program for the Administration Client proceed as follows

1 From the Server Manager select Options Client Options

2 Select Admin Update

3 If users without administrator rights on their machines use the auto update enter an administrator

ID and password in the Admin ID and Admin password fields respectively The Admin ID should be a

member of the local administrators group on all the computers running the auto update This

setting is not needed if all users have administrator rights on their machines

4 Select Update

For the EPM Add-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 Optionshellip 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 Market Place (SMP) at httpservicesapcom

All support packages and patches are available from the SMP as a zip file

EPMEXCLCLNTltSPLgtzip is for a support package

EPMEXCLCLNTltSPLgtPltPLgtzip 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 ltSP versiongtmsp

EPM Addin Support Package ltSP versiongtxml

For a patch these files are

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

2012-06-13 CUSTOMER 3954

EPM Addin Patch ltpatch numbergtmsp

EPM Addin Patch ltpatch numbergtxml

2 Unzip the zip file and extract the two files to the application server folder (WebsrvrWebBPC

Installation)

3 From the Server Manager select Options Client Options

The system lists the available packages Select the package that you want to use for the autoupdate

You can set a different update policy for each package listed

EXAMPLE

The following table illustrates some possible situations assuming that you have installed the

first full version (V1)

Available maintenance packages

V2-user updateV3-force updateV4-force updateV5-user update

V5-user update V5-user updateV6-auto updateV7-force update

Minimum Required Version

V4 V4 V7

Notification A prompt tells the user to install maintenance package V4 using the Forced Update behavior

If User Update is enabled the prompt informs the user that maintenance package V5 is available

A prompt tells the user to install maintenance package V7 using the Forced Update behavior

New Version V4 V4 or V5 V7

If you change the update policy for any package click Update to complete the change

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

4054 CUSTOMER 2012-06-13

5 Connection Issues

You may experience connection problems with ports the proxy server or programs and settings that

interact with these components If you have any issues related to connection review the following

recommendations and troubleshooting tips

51 Checking for Open Ports

You must ensure that all required ports are open for inboundoutbound 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 431181836 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

NOTE

You can use the following site to scan for the normal ports It allows you to manually enter a port

number to test

httpwwwmyserverorgportsniffasp

You can change the name of a port

52 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 Explorer Tools Internet Options Connections LAN Settings ) or at the server level

Enabling content filtering on the proxy server or firewall may cause connection problems

If external users are having trouble connecting to the server make sure the proxy server connects

using a fully qualified domain name Fully qualified domain names typically resolve both internal

and external IP addresses

Each secure Planning and Consolidation server name must be identified on the proxy server

Proxy servers may or may not require authentication which could conflict with Planning and

Consolidation authentication Do not use authentication on the proxy server The system

5 Connection Issues

51 Checking for Open Ports

2012-06-13 CUSTOMER 4154

synchronizes the user name and password on the remote server with the local user name and

password

NOTE

For more information about setting up an ISA proxy server contact SAP Support to request a

copy of Setting up ISA Proxy Server White Paper

Internet Explorer Settings 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

5 Connection Issues

52 Proxy Server and Firewall Issues

4254 CUSTOMER 2012-06-13

6 Installing Planning and Consolidation with Two Active Directory Domains

To set up a Planning and Consolidation 10 application server in a hosted environment and use your

own domain users follow this procedure In general you install Planning and Consolidation on the

host domain use the host domain account and assign it to the Planning and Consolidation users

SysAdmin Admin and Users Then you accept one way trust (the host domain trusts your domain)

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

6 Installing Planning and Consolidation with Two Active Directory Domains

2012-06-13 CUSTOMER 4354

This page is left blank for documents that are printed on both sides

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

This section describes best practices and instructions for installing Planning and Consolidation in a

Terminal Services or Citrix Server deployment

71 Terminal Services Home Directories

We recommend using Terminal Server home directories rather than using the userrsquos 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

72 System Requirements

The Citrix server should be one of the following systems

XenApp 5 Enterprise

XenApp 5 Platinum

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 37])

73 Installing Planning and Consolidation

Prerequisites

The server installation files have been downloaded from SAP Service Marketplace and installed

Procedure

The following steps outline how to install the Planning and Consolidation clients in a Terminal Services

(TS) or Citrix Server deployment

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

71 Terminal Services Home Directories

2012-06-13 CUSTOMER 4554

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 userinstall

4 Open a browser and connect to the URL httpltPC_serverportgtsapbpcweb

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 userexecute 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 Iexploreexe http(s)

ltServerNamegt-NetBIOS or FQDNsapbpcweb

To publish Planning and Consolidation Administration CProgram FilesPC_MS

BPCAdminMainexe

74 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 userrsquos desktop) must be moved to the All UsersDesktop folder

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

74 Creating a Shortcut to the Launch Page

4654 CUSTOMER 2012-06-13

8 Installing SSIS Custom Tasks

This section provides background information and instructions for installing SQL Server Integration

Services (SSIS) for SQL Server 2008 and SQL Server 2012

The Planning and Consolidation Data Manager component supports and uses SSIS Since SQL Server

2008 and SQL Server 2012 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

81 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 Filelistxml 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

OSoftSetupexe ‒ 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 or OSoftSSIS2012_Client on the client machine followed by the SQL Server

version If you want to use SQL 2008 Tasks under the SQL 2012 environment you must install

OSoftSSIS2008_Client on the application server For detailed information see SAP Note 1707410

You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package by extracting

OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPC

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 or

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4754

OSoftSSIS2012_Client for creating a COM+ application For more information see Before You Modify

the SSIS Packages [page 50] and Setup of a COM+ Application on the Application Server [page 51]

Bin folder

This folder contains the following components

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCCachedll Planning and Consolidation Cache file

BPCDataFlowPackagedll or BPCDataFlowPackage2012dll

BPCDMdll

BPCDMTaskMaindll COM+ component

BPCFilePreviewdll

BPCGacUtil_20exe System File

BPCGacUtil_40exe System File

BPCImpersonatordll Planning and Consolidation Impersonator

BPCLogicdll

BPCScriptdll

BPCServerZipdll

BPCServiceResdll

BPCTransferMembersdll

BPCWriteBackdll

InteropDTSdll

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

4854 CUSTOMER 2012-06-13

Name Remark

OSoftAdminServerdll

OSoftAuditdll

OSoftComLibServerdll

OSoftCommonResQrydll

OSoftConfigurationdll

OSoftCustomXMLSvrdll

OSoftDatabaseADMINdll

OSoftDatabaseSYSADMINdll

OSoftDatabaseSYSADMINDMdll

OSoftDatabaseUSERdll

OSoftDMDTSXExecutedll or OSoftDMDTSXExecute2012dll

OSoftDMTaskFormdll

OSoftDMTaskMaindll

OSoftDMToolsdll

OSoftFileManagedll

OSoftLoggingdll

OSoftLogWriterdll

OSoftMetaDatadll

OSoftSQEdll

OSoftSystemConfigdll

OutlookSoftconfig Configuration file to connect DB server

XceedCompressiondll XceedZip file

XceedCompressionFormatsdll XceedZip file

XceedFileSystemdll XceedZip file

XceedZipdll XceedZip file

Config folder

This folder has FileListxml 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 FileListxml 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

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4954

OSoftSetupexe

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

NOTE

If you installed the OSoftSSIS2008_Client or OSoftSSIS2012_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

Resources Folder

This folder contains the BPCServicesdll and BPCServiceUIdll files which contain resource text

Only English resources are included for the SSIS custom tasks

82 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

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008 and 2012 respectively

8 Installing SSIS Custom Tasks

82 Before You Modify the SSIS Packages

5054 CUSTOMER 2012-06-13

Name Remark

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012 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

lthellipgtOSoftSSIS2008_Clientbin or lthellipgtOSoftSSIS2012_Clientbin

On the Planning and Consolidation application server

ltdrivegtWebsrvrbin

2 Paste these files into the folder 100DTSTasks for SQL Server 2008 or into 110DTSTasks for

SQL Server 2012 For example if you install your SQL 2008 server or R2 on CProgram Files

Microsoft SQL Server paste all files into the CProgram Files (x86)Microsoft SQL Server

100DTSTasks folder

In Integration Services set the property Run64BitRunTime to True

83 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 or OSoftSSIS2012_Client on the

application server

8 Installing SSIS Custom Tasks

83 Setup of a COM+ Application on the Application Server

2012-06-13 CUSTOMER 5154

Typographic Conventions

Example Description

ltgt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example Enter your ltUser Namegt

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 httpwwwsapcom

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

5254 CUSTOMER 2012-06-13

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

  • SAP BusinessObjects Planning and Consolidation 100
    • Table of Contents
    • 1 Introduction
      • 11 SAP Notes for the Installation
      • 12 Naming Conventions
        • 2 Installing Planning and Consolidation Servers
          • 21 Basic Steps
          • 22 Prerequisites
          • 23 Before Starting the Planning and Consolidation Server Installation
          • 24 Logging on to Servers
          • 25 Service-level Accounts
          • 26 Standard and Advanced Settings
          • 27 Installing the Prerequisites
            • 271 Installing the Prerequisites ndash Basic Steps
            • 272 Installing the Operating System
            • 273 Installing the SQL Server
            • 274 Installing Analysis Services
            • 275 Installing the Anti-Cross Site Scripting Library
              • 28 Installing on a Single Server
              • 29 Installing the Server in a Multiserver Configuration
                • 3 After Installing Planning and Consolidation Servers
                  • 31 Post-Installation Steps
                  • 32 Connecting to Solution Manager Diagnostics
                  • 33 Configuring the Planning and Consolidation NET Application Servers
                  • 34 Post-Installation Optional Configuration Steps
                    • 341 Enabling the Management Console
                    • 342 Setting Up ODBC Logging in IIS for the Default Web Site
                    • 343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2
                    • 344 Removing Default Access to the Console
                    • 345 Management Console Access Control
                    • 346 Using Client Certificates
                        • 4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office
                          • 41 Installing the Administration Client
                          • 42 Installing the EPM Add-in
                          • 43 Using the Client Auto Update Program
                            • 5 Connection Issues
                              • 51 Checking for Open Ports
                              • 52 Proxy Server and Firewall Issues
                                • 6 Installing Planning and Consolidation with Two Active Directory Domains
                                • 7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
                                  • 71 Terminal Services Home Directories
                                  • 72 System Requirements
                                  • 73 Installing Planning and Consolidation
                                  • 74 Creating a Shortcut to the Launch Page
                                    • 8 Installing SSIS Custom Tasks
                                      • 81 Composition of SSIS Custom Task Installation
                                      • 82 Before You Modify the SSIS Packages
                                      • 83 Setup of a COM+ Application on the Application Server
                                          • Copyright and trademarks
Page 37: Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

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

41 Installing the Administration Client

Prerequisites

NOTE

For a definitive list of system requirements see the Product Availability Matrix on SAP Service

Marketplace at httpservicesapcompam Search on Planning and Consolidation

The following list describes the minimum software requirements

Microsoft Internet Explorer 70 or 80

Microsoft Office 2007 or 2010

NET Framework 20 or higher (install any required NET Framework Hotfixes by referring to

httpsupportmicrosoftcomkb)

Pentium IV (1 GHz CPU)

512 MB RAM

100 MB of free hard disk space in the My Documents folder

20 MB of free hard disk space for the installed Administration files

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

41 Installing the Administration Client

2012-06-13 CUSTOMER 3754

NOTE

We recommend that you install all of the latest Microsoft Windows hotfixes prior to installing

the Administration client For information about which hotfixes to install see http

updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us

ProcedureThe following procedure describes how to install the Administration Client on to an administratorrsquos

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 AddRemove Programs in the Windows Control Panel

3 Point your browser to the Planning and Consolidation Web at httpltPC_serverportgtsap

bpcweb

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

42 Installing the EPM Add-in

The Planning and Consolidation installation media does not contain the EPM addin setup program

You must download the most recent version of the full setup (EPM Add-inexe) from the Service

Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPC

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

43 Using the Client Auto Update Program

If Planning and Consolidation version 100 or later is installed you can use the Client Auto Update

program to set up the server so that it determines if an upgrade for a connecting Administration client

is necessary

The following describes the use of the auto update program for the Administration Client and the EPM

add-in

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

42 Installing the EPM Add-in

3854 CUSTOMER 2012-06-13

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 37]

To use the Client Auto Update program for the Administration Client proceed as follows

1 From the Server Manager select Options Client Options

2 Select Admin Update

3 If users without administrator rights on their machines use the auto update enter an administrator

ID and password in the Admin ID and Admin password fields respectively The Admin ID should be a

member of the local administrators group on all the computers running the auto update This

setting is not needed if all users have administrator rights on their machines

4 Select Update

For the EPM Add-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 Optionshellip 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 Market Place (SMP) at httpservicesapcom

All support packages and patches are available from the SMP as a zip file

EPMEXCLCLNTltSPLgtzip is for a support package

EPMEXCLCLNTltSPLgtPltPLgtzip 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 ltSP versiongtmsp

EPM Addin Support Package ltSP versiongtxml

For a patch these files are

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

2012-06-13 CUSTOMER 3954

EPM Addin Patch ltpatch numbergtmsp

EPM Addin Patch ltpatch numbergtxml

2 Unzip the zip file and extract the two files to the application server folder (WebsrvrWebBPC

Installation)

3 From the Server Manager select Options Client Options

The system lists the available packages Select the package that you want to use for the autoupdate

You can set a different update policy for each package listed

EXAMPLE

The following table illustrates some possible situations assuming that you have installed the

first full version (V1)

Available maintenance packages

V2-user updateV3-force updateV4-force updateV5-user update

V5-user update V5-user updateV6-auto updateV7-force update

Minimum Required Version

V4 V4 V7

Notification A prompt tells the user to install maintenance package V4 using the Forced Update behavior

If User Update is enabled the prompt informs the user that maintenance package V5 is available

A prompt tells the user to install maintenance package V7 using the Forced Update behavior

New Version V4 V4 or V5 V7

If you change the update policy for any package click Update to complete the change

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

4054 CUSTOMER 2012-06-13

5 Connection Issues

You may experience connection problems with ports the proxy server or programs and settings that

interact with these components If you have any issues related to connection review the following

recommendations and troubleshooting tips

51 Checking for Open Ports

You must ensure that all required ports are open for inboundoutbound 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 431181836 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

NOTE

You can use the following site to scan for the normal ports It allows you to manually enter a port

number to test

httpwwwmyserverorgportsniffasp

You can change the name of a port

52 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 Explorer Tools Internet Options Connections LAN Settings ) or at the server level

Enabling content filtering on the proxy server or firewall may cause connection problems

If external users are having trouble connecting to the server make sure the proxy server connects

using a fully qualified domain name Fully qualified domain names typically resolve both internal

and external IP addresses

Each secure Planning and Consolidation server name must be identified on the proxy server

Proxy servers may or may not require authentication which could conflict with Planning and

Consolidation authentication Do not use authentication on the proxy server The system

5 Connection Issues

51 Checking for Open Ports

2012-06-13 CUSTOMER 4154

synchronizes the user name and password on the remote server with the local user name and

password

NOTE

For more information about setting up an ISA proxy server contact SAP Support to request a

copy of Setting up ISA Proxy Server White Paper

Internet Explorer Settings 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

5 Connection Issues

52 Proxy Server and Firewall Issues

4254 CUSTOMER 2012-06-13

6 Installing Planning and Consolidation with Two Active Directory Domains

To set up a Planning and Consolidation 10 application server in a hosted environment and use your

own domain users follow this procedure In general you install Planning and Consolidation on the

host domain use the host domain account and assign it to the Planning and Consolidation users

SysAdmin Admin and Users Then you accept one way trust (the host domain trusts your domain)

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

6 Installing Planning and Consolidation with Two Active Directory Domains

2012-06-13 CUSTOMER 4354

This page is left blank for documents that are printed on both sides

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

This section describes best practices and instructions for installing Planning and Consolidation in a

Terminal Services or Citrix Server deployment

71 Terminal Services Home Directories

We recommend using Terminal Server home directories rather than using the userrsquos 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

72 System Requirements

The Citrix server should be one of the following systems

XenApp 5 Enterprise

XenApp 5 Platinum

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 37])

73 Installing Planning and Consolidation

Prerequisites

The server installation files have been downloaded from SAP Service Marketplace and installed

Procedure

The following steps outline how to install the Planning and Consolidation clients in a Terminal Services

(TS) or Citrix Server deployment

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

71 Terminal Services Home Directories

2012-06-13 CUSTOMER 4554

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 userinstall

4 Open a browser and connect to the URL httpltPC_serverportgtsapbpcweb

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 userexecute 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 Iexploreexe http(s)

ltServerNamegt-NetBIOS or FQDNsapbpcweb

To publish Planning and Consolidation Administration CProgram FilesPC_MS

BPCAdminMainexe

74 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 userrsquos desktop) must be moved to the All UsersDesktop folder

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

74 Creating a Shortcut to the Launch Page

4654 CUSTOMER 2012-06-13

8 Installing SSIS Custom Tasks

This section provides background information and instructions for installing SQL Server Integration

Services (SSIS) for SQL Server 2008 and SQL Server 2012

The Planning and Consolidation Data Manager component supports and uses SSIS Since SQL Server

2008 and SQL Server 2012 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

81 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 Filelistxml 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

OSoftSetupexe ‒ 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 or OSoftSSIS2012_Client on the client machine followed by the SQL Server

version If you want to use SQL 2008 Tasks under the SQL 2012 environment you must install

OSoftSSIS2008_Client on the application server For detailed information see SAP Note 1707410

You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package by extracting

OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPC

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 or

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4754

OSoftSSIS2012_Client for creating a COM+ application For more information see Before You Modify

the SSIS Packages [page 50] and Setup of a COM+ Application on the Application Server [page 51]

Bin folder

This folder contains the following components

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCCachedll Planning and Consolidation Cache file

BPCDataFlowPackagedll or BPCDataFlowPackage2012dll

BPCDMdll

BPCDMTaskMaindll COM+ component

BPCFilePreviewdll

BPCGacUtil_20exe System File

BPCGacUtil_40exe System File

BPCImpersonatordll Planning and Consolidation Impersonator

BPCLogicdll

BPCScriptdll

BPCServerZipdll

BPCServiceResdll

BPCTransferMembersdll

BPCWriteBackdll

InteropDTSdll

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

4854 CUSTOMER 2012-06-13

Name Remark

OSoftAdminServerdll

OSoftAuditdll

OSoftComLibServerdll

OSoftCommonResQrydll

OSoftConfigurationdll

OSoftCustomXMLSvrdll

OSoftDatabaseADMINdll

OSoftDatabaseSYSADMINdll

OSoftDatabaseSYSADMINDMdll

OSoftDatabaseUSERdll

OSoftDMDTSXExecutedll or OSoftDMDTSXExecute2012dll

OSoftDMTaskFormdll

OSoftDMTaskMaindll

OSoftDMToolsdll

OSoftFileManagedll

OSoftLoggingdll

OSoftLogWriterdll

OSoftMetaDatadll

OSoftSQEdll

OSoftSystemConfigdll

OutlookSoftconfig Configuration file to connect DB server

XceedCompressiondll XceedZip file

XceedCompressionFormatsdll XceedZip file

XceedFileSystemdll XceedZip file

XceedZipdll XceedZip file

Config folder

This folder has FileListxml 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 FileListxml 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

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4954

OSoftSetupexe

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

NOTE

If you installed the OSoftSSIS2008_Client or OSoftSSIS2012_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

Resources Folder

This folder contains the BPCServicesdll and BPCServiceUIdll files which contain resource text

Only English resources are included for the SSIS custom tasks

82 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

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008 and 2012 respectively

8 Installing SSIS Custom Tasks

82 Before You Modify the SSIS Packages

5054 CUSTOMER 2012-06-13

Name Remark

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012 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

lthellipgtOSoftSSIS2008_Clientbin or lthellipgtOSoftSSIS2012_Clientbin

On the Planning and Consolidation application server

ltdrivegtWebsrvrbin

2 Paste these files into the folder 100DTSTasks for SQL Server 2008 or into 110DTSTasks for

SQL Server 2012 For example if you install your SQL 2008 server or R2 on CProgram Files

Microsoft SQL Server paste all files into the CProgram Files (x86)Microsoft SQL Server

100DTSTasks folder

In Integration Services set the property Run64BitRunTime to True

83 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 or OSoftSSIS2012_Client on the

application server

8 Installing SSIS Custom Tasks

83 Setup of a COM+ Application on the Application Server

2012-06-13 CUSTOMER 5154

Typographic Conventions

Example Description

ltgt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example Enter your ltUser Namegt

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 httpwwwsapcom

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

5254 CUSTOMER 2012-06-13

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

  • SAP BusinessObjects Planning and Consolidation 100
    • Table of Contents
    • 1 Introduction
      • 11 SAP Notes for the Installation
      • 12 Naming Conventions
        • 2 Installing Planning and Consolidation Servers
          • 21 Basic Steps
          • 22 Prerequisites
          • 23 Before Starting the Planning and Consolidation Server Installation
          • 24 Logging on to Servers
          • 25 Service-level Accounts
          • 26 Standard and Advanced Settings
          • 27 Installing the Prerequisites
            • 271 Installing the Prerequisites ndash Basic Steps
            • 272 Installing the Operating System
            • 273 Installing the SQL Server
            • 274 Installing Analysis Services
            • 275 Installing the Anti-Cross Site Scripting Library
              • 28 Installing on a Single Server
              • 29 Installing the Server in a Multiserver Configuration
                • 3 After Installing Planning and Consolidation Servers
                  • 31 Post-Installation Steps
                  • 32 Connecting to Solution Manager Diagnostics
                  • 33 Configuring the Planning and Consolidation NET Application Servers
                  • 34 Post-Installation Optional Configuration Steps
                    • 341 Enabling the Management Console
                    • 342 Setting Up ODBC Logging in IIS for the Default Web Site
                    • 343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2
                    • 344 Removing Default Access to the Console
                    • 345 Management Console Access Control
                    • 346 Using Client Certificates
                        • 4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office
                          • 41 Installing the Administration Client
                          • 42 Installing the EPM Add-in
                          • 43 Using the Client Auto Update Program
                            • 5 Connection Issues
                              • 51 Checking for Open Ports
                              • 52 Proxy Server and Firewall Issues
                                • 6 Installing Planning and Consolidation with Two Active Directory Domains
                                • 7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
                                  • 71 Terminal Services Home Directories
                                  • 72 System Requirements
                                  • 73 Installing Planning and Consolidation
                                  • 74 Creating a Shortcut to the Launch Page
                                    • 8 Installing SSIS Custom Tasks
                                      • 81 Composition of SSIS Custom Task Installation
                                      • 82 Before You Modify the SSIS Packages
                                      • 83 Setup of a COM+ Application on the Application Server
                                          • Copyright and trademarks
Page 38: Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

NOTE

We recommend that you install all of the latest Microsoft Windows hotfixes prior to installing

the Administration client For information about which hotfixes to install see http

updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us

ProcedureThe following procedure describes how to install the Administration Client on to an administratorrsquos

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 AddRemove Programs in the Windows Control Panel

3 Point your browser to the Planning and Consolidation Web at httpltPC_serverportgtsap

bpcweb

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

42 Installing the EPM Add-in

The Planning and Consolidation installation media does not contain the EPM addin setup program

You must download the most recent version of the full setup (EPM Add-inexe) from the Service

Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPC

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

43 Using the Client Auto Update Program

If Planning and Consolidation version 100 or later is installed you can use the Client Auto Update

program to set up the server so that it determines if an upgrade for a connecting Administration client

is necessary

The following describes the use of the auto update program for the Administration Client and the EPM

add-in

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

42 Installing the EPM Add-in

3854 CUSTOMER 2012-06-13

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 37]

To use the Client Auto Update program for the Administration Client proceed as follows

1 From the Server Manager select Options Client Options

2 Select Admin Update

3 If users without administrator rights on their machines use the auto update enter an administrator

ID and password in the Admin ID and Admin password fields respectively The Admin ID should be a

member of the local administrators group on all the computers running the auto update This

setting is not needed if all users have administrator rights on their machines

4 Select Update

For the EPM Add-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 Optionshellip 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 Market Place (SMP) at httpservicesapcom

All support packages and patches are available from the SMP as a zip file

EPMEXCLCLNTltSPLgtzip is for a support package

EPMEXCLCLNTltSPLgtPltPLgtzip 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 ltSP versiongtmsp

EPM Addin Support Package ltSP versiongtxml

For a patch these files are

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

2012-06-13 CUSTOMER 3954

EPM Addin Patch ltpatch numbergtmsp

EPM Addin Patch ltpatch numbergtxml

2 Unzip the zip file and extract the two files to the application server folder (WebsrvrWebBPC

Installation)

3 From the Server Manager select Options Client Options

The system lists the available packages Select the package that you want to use for the autoupdate

You can set a different update policy for each package listed

EXAMPLE

The following table illustrates some possible situations assuming that you have installed the

first full version (V1)

Available maintenance packages

V2-user updateV3-force updateV4-force updateV5-user update

V5-user update V5-user updateV6-auto updateV7-force update

Minimum Required Version

V4 V4 V7

Notification A prompt tells the user to install maintenance package V4 using the Forced Update behavior

If User Update is enabled the prompt informs the user that maintenance package V5 is available

A prompt tells the user to install maintenance package V7 using the Forced Update behavior

New Version V4 V4 or V5 V7

If you change the update policy for any package click Update to complete the change

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

4054 CUSTOMER 2012-06-13

5 Connection Issues

You may experience connection problems with ports the proxy server or programs and settings that

interact with these components If you have any issues related to connection review the following

recommendations and troubleshooting tips

51 Checking for Open Ports

You must ensure that all required ports are open for inboundoutbound 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 431181836 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

NOTE

You can use the following site to scan for the normal ports It allows you to manually enter a port

number to test

httpwwwmyserverorgportsniffasp

You can change the name of a port

52 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 Explorer Tools Internet Options Connections LAN Settings ) or at the server level

Enabling content filtering on the proxy server or firewall may cause connection problems

If external users are having trouble connecting to the server make sure the proxy server connects

using a fully qualified domain name Fully qualified domain names typically resolve both internal

and external IP addresses

Each secure Planning and Consolidation server name must be identified on the proxy server

Proxy servers may or may not require authentication which could conflict with Planning and

Consolidation authentication Do not use authentication on the proxy server The system

5 Connection Issues

51 Checking for Open Ports

2012-06-13 CUSTOMER 4154

synchronizes the user name and password on the remote server with the local user name and

password

NOTE

For more information about setting up an ISA proxy server contact SAP Support to request a

copy of Setting up ISA Proxy Server White Paper

Internet Explorer Settings 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

5 Connection Issues

52 Proxy Server and Firewall Issues

4254 CUSTOMER 2012-06-13

6 Installing Planning and Consolidation with Two Active Directory Domains

To set up a Planning and Consolidation 10 application server in a hosted environment and use your

own domain users follow this procedure In general you install Planning and Consolidation on the

host domain use the host domain account and assign it to the Planning and Consolidation users

SysAdmin Admin and Users Then you accept one way trust (the host domain trusts your domain)

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

6 Installing Planning and Consolidation with Two Active Directory Domains

2012-06-13 CUSTOMER 4354

This page is left blank for documents that are printed on both sides

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

This section describes best practices and instructions for installing Planning and Consolidation in a

Terminal Services or Citrix Server deployment

71 Terminal Services Home Directories

We recommend using Terminal Server home directories rather than using the userrsquos 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

72 System Requirements

The Citrix server should be one of the following systems

XenApp 5 Enterprise

XenApp 5 Platinum

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 37])

73 Installing Planning and Consolidation

Prerequisites

The server installation files have been downloaded from SAP Service Marketplace and installed

Procedure

The following steps outline how to install the Planning and Consolidation clients in a Terminal Services

(TS) or Citrix Server deployment

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

71 Terminal Services Home Directories

2012-06-13 CUSTOMER 4554

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 userinstall

4 Open a browser and connect to the URL httpltPC_serverportgtsapbpcweb

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 userexecute 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 Iexploreexe http(s)

ltServerNamegt-NetBIOS or FQDNsapbpcweb

To publish Planning and Consolidation Administration CProgram FilesPC_MS

BPCAdminMainexe

74 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 userrsquos desktop) must be moved to the All UsersDesktop folder

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

74 Creating a Shortcut to the Launch Page

4654 CUSTOMER 2012-06-13

8 Installing SSIS Custom Tasks

This section provides background information and instructions for installing SQL Server Integration

Services (SSIS) for SQL Server 2008 and SQL Server 2012

The Planning and Consolidation Data Manager component supports and uses SSIS Since SQL Server

2008 and SQL Server 2012 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

81 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 Filelistxml 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

OSoftSetupexe ‒ 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 or OSoftSSIS2012_Client on the client machine followed by the SQL Server

version If you want to use SQL 2008 Tasks under the SQL 2012 environment you must install

OSoftSSIS2008_Client on the application server For detailed information see SAP Note 1707410

You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package by extracting

OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPC

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 or

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4754

OSoftSSIS2012_Client for creating a COM+ application For more information see Before You Modify

the SSIS Packages [page 50] and Setup of a COM+ Application on the Application Server [page 51]

Bin folder

This folder contains the following components

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCCachedll Planning and Consolidation Cache file

BPCDataFlowPackagedll or BPCDataFlowPackage2012dll

BPCDMdll

BPCDMTaskMaindll COM+ component

BPCFilePreviewdll

BPCGacUtil_20exe System File

BPCGacUtil_40exe System File

BPCImpersonatordll Planning and Consolidation Impersonator

BPCLogicdll

BPCScriptdll

BPCServerZipdll

BPCServiceResdll

BPCTransferMembersdll

BPCWriteBackdll

InteropDTSdll

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

4854 CUSTOMER 2012-06-13

Name Remark

OSoftAdminServerdll

OSoftAuditdll

OSoftComLibServerdll

OSoftCommonResQrydll

OSoftConfigurationdll

OSoftCustomXMLSvrdll

OSoftDatabaseADMINdll

OSoftDatabaseSYSADMINdll

OSoftDatabaseSYSADMINDMdll

OSoftDatabaseUSERdll

OSoftDMDTSXExecutedll or OSoftDMDTSXExecute2012dll

OSoftDMTaskFormdll

OSoftDMTaskMaindll

OSoftDMToolsdll

OSoftFileManagedll

OSoftLoggingdll

OSoftLogWriterdll

OSoftMetaDatadll

OSoftSQEdll

OSoftSystemConfigdll

OutlookSoftconfig Configuration file to connect DB server

XceedCompressiondll XceedZip file

XceedCompressionFormatsdll XceedZip file

XceedFileSystemdll XceedZip file

XceedZipdll XceedZip file

Config folder

This folder has FileListxml 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 FileListxml 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

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4954

OSoftSetupexe

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

NOTE

If you installed the OSoftSSIS2008_Client or OSoftSSIS2012_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

Resources Folder

This folder contains the BPCServicesdll and BPCServiceUIdll files which contain resource text

Only English resources are included for the SSIS custom tasks

82 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

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008 and 2012 respectively

8 Installing SSIS Custom Tasks

82 Before You Modify the SSIS Packages

5054 CUSTOMER 2012-06-13

Name Remark

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012 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

lthellipgtOSoftSSIS2008_Clientbin or lthellipgtOSoftSSIS2012_Clientbin

On the Planning and Consolidation application server

ltdrivegtWebsrvrbin

2 Paste these files into the folder 100DTSTasks for SQL Server 2008 or into 110DTSTasks for

SQL Server 2012 For example if you install your SQL 2008 server or R2 on CProgram Files

Microsoft SQL Server paste all files into the CProgram Files (x86)Microsoft SQL Server

100DTSTasks folder

In Integration Services set the property Run64BitRunTime to True

83 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 or OSoftSSIS2012_Client on the

application server

8 Installing SSIS Custom Tasks

83 Setup of a COM+ Application on the Application Server

2012-06-13 CUSTOMER 5154

Typographic Conventions

Example Description

ltgt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example Enter your ltUser Namegt

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 httpwwwsapcom

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

5254 CUSTOMER 2012-06-13

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

  • SAP BusinessObjects Planning and Consolidation 100
    • Table of Contents
    • 1 Introduction
      • 11 SAP Notes for the Installation
      • 12 Naming Conventions
        • 2 Installing Planning and Consolidation Servers
          • 21 Basic Steps
          • 22 Prerequisites
          • 23 Before Starting the Planning and Consolidation Server Installation
          • 24 Logging on to Servers
          • 25 Service-level Accounts
          • 26 Standard and Advanced Settings
          • 27 Installing the Prerequisites
            • 271 Installing the Prerequisites ndash Basic Steps
            • 272 Installing the Operating System
            • 273 Installing the SQL Server
            • 274 Installing Analysis Services
            • 275 Installing the Anti-Cross Site Scripting Library
              • 28 Installing on a Single Server
              • 29 Installing the Server in a Multiserver Configuration
                • 3 After Installing Planning and Consolidation Servers
                  • 31 Post-Installation Steps
                  • 32 Connecting to Solution Manager Diagnostics
                  • 33 Configuring the Planning and Consolidation NET Application Servers
                  • 34 Post-Installation Optional Configuration Steps
                    • 341 Enabling the Management Console
                    • 342 Setting Up ODBC Logging in IIS for the Default Web Site
                    • 343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2
                    • 344 Removing Default Access to the Console
                    • 345 Management Console Access Control
                    • 346 Using Client Certificates
                        • 4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office
                          • 41 Installing the Administration Client
                          • 42 Installing the EPM Add-in
                          • 43 Using the Client Auto Update Program
                            • 5 Connection Issues
                              • 51 Checking for Open Ports
                              • 52 Proxy Server and Firewall Issues
                                • 6 Installing Planning and Consolidation with Two Active Directory Domains
                                • 7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
                                  • 71 Terminal Services Home Directories
                                  • 72 System Requirements
                                  • 73 Installing Planning and Consolidation
                                  • 74 Creating a Shortcut to the Launch Page
                                    • 8 Installing SSIS Custom Tasks
                                      • 81 Composition of SSIS Custom Task Installation
                                      • 82 Before You Modify the SSIS Packages
                                      • 83 Setup of a COM+ Application on the Application Server
                                          • Copyright and trademarks
Page 39: Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

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 37]

To use the Client Auto Update program for the Administration Client proceed as follows

1 From the Server Manager select Options Client Options

2 Select Admin Update

3 If users without administrator rights on their machines use the auto update enter an administrator

ID and password in the Admin ID and Admin password fields respectively The Admin ID should be a

member of the local administrators group on all the computers running the auto update This

setting is not needed if all users have administrator rights on their machines

4 Select Update

For the EPM Add-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 Optionshellip 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 Market Place (SMP) at httpservicesapcom

All support packages and patches are available from the SMP as a zip file

EPMEXCLCLNTltSPLgtzip is for a support package

EPMEXCLCLNTltSPLgtPltPLgtzip 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 ltSP versiongtmsp

EPM Addin Support Package ltSP versiongtxml

For a patch these files are

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

2012-06-13 CUSTOMER 3954

EPM Addin Patch ltpatch numbergtmsp

EPM Addin Patch ltpatch numbergtxml

2 Unzip the zip file and extract the two files to the application server folder (WebsrvrWebBPC

Installation)

3 From the Server Manager select Options Client Options

The system lists the available packages Select the package that you want to use for the autoupdate

You can set a different update policy for each package listed

EXAMPLE

The following table illustrates some possible situations assuming that you have installed the

first full version (V1)

Available maintenance packages

V2-user updateV3-force updateV4-force updateV5-user update

V5-user update V5-user updateV6-auto updateV7-force update

Minimum Required Version

V4 V4 V7

Notification A prompt tells the user to install maintenance package V4 using the Forced Update behavior

If User Update is enabled the prompt informs the user that maintenance package V5 is available

A prompt tells the user to install maintenance package V7 using the Forced Update behavior

New Version V4 V4 or V5 V7

If you change the update policy for any package click Update to complete the change

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

4054 CUSTOMER 2012-06-13

5 Connection Issues

You may experience connection problems with ports the proxy server or programs and settings that

interact with these components If you have any issues related to connection review the following

recommendations and troubleshooting tips

51 Checking for Open Ports

You must ensure that all required ports are open for inboundoutbound 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 431181836 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

NOTE

You can use the following site to scan for the normal ports It allows you to manually enter a port

number to test

httpwwwmyserverorgportsniffasp

You can change the name of a port

52 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 Explorer Tools Internet Options Connections LAN Settings ) or at the server level

Enabling content filtering on the proxy server or firewall may cause connection problems

If external users are having trouble connecting to the server make sure the proxy server connects

using a fully qualified domain name Fully qualified domain names typically resolve both internal

and external IP addresses

Each secure Planning and Consolidation server name must be identified on the proxy server

Proxy servers may or may not require authentication which could conflict with Planning and

Consolidation authentication Do not use authentication on the proxy server The system

5 Connection Issues

51 Checking for Open Ports

2012-06-13 CUSTOMER 4154

synchronizes the user name and password on the remote server with the local user name and

password

NOTE

For more information about setting up an ISA proxy server contact SAP Support to request a

copy of Setting up ISA Proxy Server White Paper

Internet Explorer Settings 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

5 Connection Issues

52 Proxy Server and Firewall Issues

4254 CUSTOMER 2012-06-13

6 Installing Planning and Consolidation with Two Active Directory Domains

To set up a Planning and Consolidation 10 application server in a hosted environment and use your

own domain users follow this procedure In general you install Planning and Consolidation on the

host domain use the host domain account and assign it to the Planning and Consolidation users

SysAdmin Admin and Users Then you accept one way trust (the host domain trusts your domain)

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

6 Installing Planning and Consolidation with Two Active Directory Domains

2012-06-13 CUSTOMER 4354

This page is left blank for documents that are printed on both sides

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

This section describes best practices and instructions for installing Planning and Consolidation in a

Terminal Services or Citrix Server deployment

71 Terminal Services Home Directories

We recommend using Terminal Server home directories rather than using the userrsquos 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

72 System Requirements

The Citrix server should be one of the following systems

XenApp 5 Enterprise

XenApp 5 Platinum

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 37])

73 Installing Planning and Consolidation

Prerequisites

The server installation files have been downloaded from SAP Service Marketplace and installed

Procedure

The following steps outline how to install the Planning and Consolidation clients in a Terminal Services

(TS) or Citrix Server deployment

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

71 Terminal Services Home Directories

2012-06-13 CUSTOMER 4554

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 userinstall

4 Open a browser and connect to the URL httpltPC_serverportgtsapbpcweb

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 userexecute 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 Iexploreexe http(s)

ltServerNamegt-NetBIOS or FQDNsapbpcweb

To publish Planning and Consolidation Administration CProgram FilesPC_MS

BPCAdminMainexe

74 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 userrsquos desktop) must be moved to the All UsersDesktop folder

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

74 Creating a Shortcut to the Launch Page

4654 CUSTOMER 2012-06-13

8 Installing SSIS Custom Tasks

This section provides background information and instructions for installing SQL Server Integration

Services (SSIS) for SQL Server 2008 and SQL Server 2012

The Planning and Consolidation Data Manager component supports and uses SSIS Since SQL Server

2008 and SQL Server 2012 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

81 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 Filelistxml 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

OSoftSetupexe ‒ 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 or OSoftSSIS2012_Client on the client machine followed by the SQL Server

version If you want to use SQL 2008 Tasks under the SQL 2012 environment you must install

OSoftSSIS2008_Client on the application server For detailed information see SAP Note 1707410

You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package by extracting

OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPC

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 or

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4754

OSoftSSIS2012_Client for creating a COM+ application For more information see Before You Modify

the SSIS Packages [page 50] and Setup of a COM+ Application on the Application Server [page 51]

Bin folder

This folder contains the following components

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCCachedll Planning and Consolidation Cache file

BPCDataFlowPackagedll or BPCDataFlowPackage2012dll

BPCDMdll

BPCDMTaskMaindll COM+ component

BPCFilePreviewdll

BPCGacUtil_20exe System File

BPCGacUtil_40exe System File

BPCImpersonatordll Planning and Consolidation Impersonator

BPCLogicdll

BPCScriptdll

BPCServerZipdll

BPCServiceResdll

BPCTransferMembersdll

BPCWriteBackdll

InteropDTSdll

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

4854 CUSTOMER 2012-06-13

Name Remark

OSoftAdminServerdll

OSoftAuditdll

OSoftComLibServerdll

OSoftCommonResQrydll

OSoftConfigurationdll

OSoftCustomXMLSvrdll

OSoftDatabaseADMINdll

OSoftDatabaseSYSADMINdll

OSoftDatabaseSYSADMINDMdll

OSoftDatabaseUSERdll

OSoftDMDTSXExecutedll or OSoftDMDTSXExecute2012dll

OSoftDMTaskFormdll

OSoftDMTaskMaindll

OSoftDMToolsdll

OSoftFileManagedll

OSoftLoggingdll

OSoftLogWriterdll

OSoftMetaDatadll

OSoftSQEdll

OSoftSystemConfigdll

OutlookSoftconfig Configuration file to connect DB server

XceedCompressiondll XceedZip file

XceedCompressionFormatsdll XceedZip file

XceedFileSystemdll XceedZip file

XceedZipdll XceedZip file

Config folder

This folder has FileListxml 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 FileListxml 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

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4954

OSoftSetupexe

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

NOTE

If you installed the OSoftSSIS2008_Client or OSoftSSIS2012_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

Resources Folder

This folder contains the BPCServicesdll and BPCServiceUIdll files which contain resource text

Only English resources are included for the SSIS custom tasks

82 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

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008 and 2012 respectively

8 Installing SSIS Custom Tasks

82 Before You Modify the SSIS Packages

5054 CUSTOMER 2012-06-13

Name Remark

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012 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

lthellipgtOSoftSSIS2008_Clientbin or lthellipgtOSoftSSIS2012_Clientbin

On the Planning and Consolidation application server

ltdrivegtWebsrvrbin

2 Paste these files into the folder 100DTSTasks for SQL Server 2008 or into 110DTSTasks for

SQL Server 2012 For example if you install your SQL 2008 server or R2 on CProgram Files

Microsoft SQL Server paste all files into the CProgram Files (x86)Microsoft SQL Server

100DTSTasks folder

In Integration Services set the property Run64BitRunTime to True

83 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 or OSoftSSIS2012_Client on the

application server

8 Installing SSIS Custom Tasks

83 Setup of a COM+ Application on the Application Server

2012-06-13 CUSTOMER 5154

Typographic Conventions

Example Description

ltgt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example Enter your ltUser Namegt

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 httpwwwsapcom

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

5254 CUSTOMER 2012-06-13

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

  • SAP BusinessObjects Planning and Consolidation 100
    • Table of Contents
    • 1 Introduction
      • 11 SAP Notes for the Installation
      • 12 Naming Conventions
        • 2 Installing Planning and Consolidation Servers
          • 21 Basic Steps
          • 22 Prerequisites
          • 23 Before Starting the Planning and Consolidation Server Installation
          • 24 Logging on to Servers
          • 25 Service-level Accounts
          • 26 Standard and Advanced Settings
          • 27 Installing the Prerequisites
            • 271 Installing the Prerequisites ndash Basic Steps
            • 272 Installing the Operating System
            • 273 Installing the SQL Server
            • 274 Installing Analysis Services
            • 275 Installing the Anti-Cross Site Scripting Library
              • 28 Installing on a Single Server
              • 29 Installing the Server in a Multiserver Configuration
                • 3 After Installing Planning and Consolidation Servers
                  • 31 Post-Installation Steps
                  • 32 Connecting to Solution Manager Diagnostics
                  • 33 Configuring the Planning and Consolidation NET Application Servers
                  • 34 Post-Installation Optional Configuration Steps
                    • 341 Enabling the Management Console
                    • 342 Setting Up ODBC Logging in IIS for the Default Web Site
                    • 343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2
                    • 344 Removing Default Access to the Console
                    • 345 Management Console Access Control
                    • 346 Using Client Certificates
                        • 4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office
                          • 41 Installing the Administration Client
                          • 42 Installing the EPM Add-in
                          • 43 Using the Client Auto Update Program
                            • 5 Connection Issues
                              • 51 Checking for Open Ports
                              • 52 Proxy Server and Firewall Issues
                                • 6 Installing Planning and Consolidation with Two Active Directory Domains
                                • 7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
                                  • 71 Terminal Services Home Directories
                                  • 72 System Requirements
                                  • 73 Installing Planning and Consolidation
                                  • 74 Creating a Shortcut to the Launch Page
                                    • 8 Installing SSIS Custom Tasks
                                      • 81 Composition of SSIS Custom Task Installation
                                      • 82 Before You Modify the SSIS Packages
                                      • 83 Setup of a COM+ Application on the Application Server
                                          • Copyright and trademarks
Page 40: Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

EPM Addin Patch ltpatch numbergtmsp

EPM Addin Patch ltpatch numbergtxml

2 Unzip the zip file and extract the two files to the application server folder (WebsrvrWebBPC

Installation)

3 From the Server Manager select Options Client Options

The system lists the available packages Select the package that you want to use for the autoupdate

You can set a different update policy for each package listed

EXAMPLE

The following table illustrates some possible situations assuming that you have installed the

first full version (V1)

Available maintenance packages

V2-user updateV3-force updateV4-force updateV5-user update

V5-user update V5-user updateV6-auto updateV7-force update

Minimum Required Version

V4 V4 V7

Notification A prompt tells the user to install maintenance package V4 using the Forced Update behavior

If User Update is enabled the prompt informs the user that maintenance package V5 is available

A prompt tells the user to install maintenance package V7 using the Forced Update behavior

New Version V4 V4 or V5 V7

If you change the update policy for any package click Update to complete the change

4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office

43 Using the Client Auto Update Program

4054 CUSTOMER 2012-06-13

5 Connection Issues

You may experience connection problems with ports the proxy server or programs and settings that

interact with these components If you have any issues related to connection review the following

recommendations and troubleshooting tips

51 Checking for Open Ports

You must ensure that all required ports are open for inboundoutbound 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 431181836 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

NOTE

You can use the following site to scan for the normal ports It allows you to manually enter a port

number to test

httpwwwmyserverorgportsniffasp

You can change the name of a port

52 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 Explorer Tools Internet Options Connections LAN Settings ) or at the server level

Enabling content filtering on the proxy server or firewall may cause connection problems

If external users are having trouble connecting to the server make sure the proxy server connects

using a fully qualified domain name Fully qualified domain names typically resolve both internal

and external IP addresses

Each secure Planning and Consolidation server name must be identified on the proxy server

Proxy servers may or may not require authentication which could conflict with Planning and

Consolidation authentication Do not use authentication on the proxy server The system

5 Connection Issues

51 Checking for Open Ports

2012-06-13 CUSTOMER 4154

synchronizes the user name and password on the remote server with the local user name and

password

NOTE

For more information about setting up an ISA proxy server contact SAP Support to request a

copy of Setting up ISA Proxy Server White Paper

Internet Explorer Settings 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

5 Connection Issues

52 Proxy Server and Firewall Issues

4254 CUSTOMER 2012-06-13

6 Installing Planning and Consolidation with Two Active Directory Domains

To set up a Planning and Consolidation 10 application server in a hosted environment and use your

own domain users follow this procedure In general you install Planning and Consolidation on the

host domain use the host domain account and assign it to the Planning and Consolidation users

SysAdmin Admin and Users Then you accept one way trust (the host domain trusts your domain)

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

6 Installing Planning and Consolidation with Two Active Directory Domains

2012-06-13 CUSTOMER 4354

This page is left blank for documents that are printed on both sides

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

This section describes best practices and instructions for installing Planning and Consolidation in a

Terminal Services or Citrix Server deployment

71 Terminal Services Home Directories

We recommend using Terminal Server home directories rather than using the userrsquos 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

72 System Requirements

The Citrix server should be one of the following systems

XenApp 5 Enterprise

XenApp 5 Platinum

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 37])

73 Installing Planning and Consolidation

Prerequisites

The server installation files have been downloaded from SAP Service Marketplace and installed

Procedure

The following steps outline how to install the Planning and Consolidation clients in a Terminal Services

(TS) or Citrix Server deployment

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

71 Terminal Services Home Directories

2012-06-13 CUSTOMER 4554

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 userinstall

4 Open a browser and connect to the URL httpltPC_serverportgtsapbpcweb

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 userexecute 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 Iexploreexe http(s)

ltServerNamegt-NetBIOS or FQDNsapbpcweb

To publish Planning and Consolidation Administration CProgram FilesPC_MS

BPCAdminMainexe

74 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 userrsquos desktop) must be moved to the All UsersDesktop folder

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

74 Creating a Shortcut to the Launch Page

4654 CUSTOMER 2012-06-13

8 Installing SSIS Custom Tasks

This section provides background information and instructions for installing SQL Server Integration

Services (SSIS) for SQL Server 2008 and SQL Server 2012

The Planning and Consolidation Data Manager component supports and uses SSIS Since SQL Server

2008 and SQL Server 2012 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

81 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 Filelistxml 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

OSoftSetupexe ‒ 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 or OSoftSSIS2012_Client on the client machine followed by the SQL Server

version If you want to use SQL 2008 Tasks under the SQL 2012 environment you must install

OSoftSSIS2008_Client on the application server For detailed information see SAP Note 1707410

You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package by extracting

OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPC

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 or

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4754

OSoftSSIS2012_Client for creating a COM+ application For more information see Before You Modify

the SSIS Packages [page 50] and Setup of a COM+ Application on the Application Server [page 51]

Bin folder

This folder contains the following components

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCCachedll Planning and Consolidation Cache file

BPCDataFlowPackagedll or BPCDataFlowPackage2012dll

BPCDMdll

BPCDMTaskMaindll COM+ component

BPCFilePreviewdll

BPCGacUtil_20exe System File

BPCGacUtil_40exe System File

BPCImpersonatordll Planning and Consolidation Impersonator

BPCLogicdll

BPCScriptdll

BPCServerZipdll

BPCServiceResdll

BPCTransferMembersdll

BPCWriteBackdll

InteropDTSdll

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

4854 CUSTOMER 2012-06-13

Name Remark

OSoftAdminServerdll

OSoftAuditdll

OSoftComLibServerdll

OSoftCommonResQrydll

OSoftConfigurationdll

OSoftCustomXMLSvrdll

OSoftDatabaseADMINdll

OSoftDatabaseSYSADMINdll

OSoftDatabaseSYSADMINDMdll

OSoftDatabaseUSERdll

OSoftDMDTSXExecutedll or OSoftDMDTSXExecute2012dll

OSoftDMTaskFormdll

OSoftDMTaskMaindll

OSoftDMToolsdll

OSoftFileManagedll

OSoftLoggingdll

OSoftLogWriterdll

OSoftMetaDatadll

OSoftSQEdll

OSoftSystemConfigdll

OutlookSoftconfig Configuration file to connect DB server

XceedCompressiondll XceedZip file

XceedCompressionFormatsdll XceedZip file

XceedFileSystemdll XceedZip file

XceedZipdll XceedZip file

Config folder

This folder has FileListxml 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 FileListxml 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

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4954

OSoftSetupexe

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

NOTE

If you installed the OSoftSSIS2008_Client or OSoftSSIS2012_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

Resources Folder

This folder contains the BPCServicesdll and BPCServiceUIdll files which contain resource text

Only English resources are included for the SSIS custom tasks

82 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

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008 and 2012 respectively

8 Installing SSIS Custom Tasks

82 Before You Modify the SSIS Packages

5054 CUSTOMER 2012-06-13

Name Remark

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012 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

lthellipgtOSoftSSIS2008_Clientbin or lthellipgtOSoftSSIS2012_Clientbin

On the Planning and Consolidation application server

ltdrivegtWebsrvrbin

2 Paste these files into the folder 100DTSTasks for SQL Server 2008 or into 110DTSTasks for

SQL Server 2012 For example if you install your SQL 2008 server or R2 on CProgram Files

Microsoft SQL Server paste all files into the CProgram Files (x86)Microsoft SQL Server

100DTSTasks folder

In Integration Services set the property Run64BitRunTime to True

83 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 or OSoftSSIS2012_Client on the

application server

8 Installing SSIS Custom Tasks

83 Setup of a COM+ Application on the Application Server

2012-06-13 CUSTOMER 5154

Typographic Conventions

Example Description

ltgt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example Enter your ltUser Namegt

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 httpwwwsapcom

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

5254 CUSTOMER 2012-06-13

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

  • SAP BusinessObjects Planning and Consolidation 100
    • Table of Contents
    • 1 Introduction
      • 11 SAP Notes for the Installation
      • 12 Naming Conventions
        • 2 Installing Planning and Consolidation Servers
          • 21 Basic Steps
          • 22 Prerequisites
          • 23 Before Starting the Planning and Consolidation Server Installation
          • 24 Logging on to Servers
          • 25 Service-level Accounts
          • 26 Standard and Advanced Settings
          • 27 Installing the Prerequisites
            • 271 Installing the Prerequisites ndash Basic Steps
            • 272 Installing the Operating System
            • 273 Installing the SQL Server
            • 274 Installing Analysis Services
            • 275 Installing the Anti-Cross Site Scripting Library
              • 28 Installing on a Single Server
              • 29 Installing the Server in a Multiserver Configuration
                • 3 After Installing Planning and Consolidation Servers
                  • 31 Post-Installation Steps
                  • 32 Connecting to Solution Manager Diagnostics
                  • 33 Configuring the Planning and Consolidation NET Application Servers
                  • 34 Post-Installation Optional Configuration Steps
                    • 341 Enabling the Management Console
                    • 342 Setting Up ODBC Logging in IIS for the Default Web Site
                    • 343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2
                    • 344 Removing Default Access to the Console
                    • 345 Management Console Access Control
                    • 346 Using Client Certificates
                        • 4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office
                          • 41 Installing the Administration Client
                          • 42 Installing the EPM Add-in
                          • 43 Using the Client Auto Update Program
                            • 5 Connection Issues
                              • 51 Checking for Open Ports
                              • 52 Proxy Server and Firewall Issues
                                • 6 Installing Planning and Consolidation with Two Active Directory Domains
                                • 7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
                                  • 71 Terminal Services Home Directories
                                  • 72 System Requirements
                                  • 73 Installing Planning and Consolidation
                                  • 74 Creating a Shortcut to the Launch Page
                                    • 8 Installing SSIS Custom Tasks
                                      • 81 Composition of SSIS Custom Task Installation
                                      • 82 Before You Modify the SSIS Packages
                                      • 83 Setup of a COM+ Application on the Application Server
                                          • Copyright and trademarks
Page 41: Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

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

51 Checking for Open Ports

You must ensure that all required ports are open for inboundoutbound 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 431181836 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

NOTE

You can use the following site to scan for the normal ports It allows you to manually enter a port

number to test

httpwwwmyserverorgportsniffasp

You can change the name of a port

52 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 Explorer Tools Internet Options Connections LAN Settings ) or at the server level

Enabling content filtering on the proxy server or firewall may cause connection problems

If external users are having trouble connecting to the server make sure the proxy server connects

using a fully qualified domain name Fully qualified domain names typically resolve both internal

and external IP addresses

Each secure Planning and Consolidation server name must be identified on the proxy server

Proxy servers may or may not require authentication which could conflict with Planning and

Consolidation authentication Do not use authentication on the proxy server The system

5 Connection Issues

51 Checking for Open Ports

2012-06-13 CUSTOMER 4154

synchronizes the user name and password on the remote server with the local user name and

password

NOTE

For more information about setting up an ISA proxy server contact SAP Support to request a

copy of Setting up ISA Proxy Server White Paper

Internet Explorer Settings 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

5 Connection Issues

52 Proxy Server and Firewall Issues

4254 CUSTOMER 2012-06-13

6 Installing Planning and Consolidation with Two Active Directory Domains

To set up a Planning and Consolidation 10 application server in a hosted environment and use your

own domain users follow this procedure In general you install Planning and Consolidation on the

host domain use the host domain account and assign it to the Planning and Consolidation users

SysAdmin Admin and Users Then you accept one way trust (the host domain trusts your domain)

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

6 Installing Planning and Consolidation with Two Active Directory Domains

2012-06-13 CUSTOMER 4354

This page is left blank for documents that are printed on both sides

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

This section describes best practices and instructions for installing Planning and Consolidation in a

Terminal Services or Citrix Server deployment

71 Terminal Services Home Directories

We recommend using Terminal Server home directories rather than using the userrsquos 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

72 System Requirements

The Citrix server should be one of the following systems

XenApp 5 Enterprise

XenApp 5 Platinum

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 37])

73 Installing Planning and Consolidation

Prerequisites

The server installation files have been downloaded from SAP Service Marketplace and installed

Procedure

The following steps outline how to install the Planning and Consolidation clients in a Terminal Services

(TS) or Citrix Server deployment

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

71 Terminal Services Home Directories

2012-06-13 CUSTOMER 4554

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 userinstall

4 Open a browser and connect to the URL httpltPC_serverportgtsapbpcweb

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 userexecute 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 Iexploreexe http(s)

ltServerNamegt-NetBIOS or FQDNsapbpcweb

To publish Planning and Consolidation Administration CProgram FilesPC_MS

BPCAdminMainexe

74 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 userrsquos desktop) must be moved to the All UsersDesktop folder

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

74 Creating a Shortcut to the Launch Page

4654 CUSTOMER 2012-06-13

8 Installing SSIS Custom Tasks

This section provides background information and instructions for installing SQL Server Integration

Services (SSIS) for SQL Server 2008 and SQL Server 2012

The Planning and Consolidation Data Manager component supports and uses SSIS Since SQL Server

2008 and SQL Server 2012 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

81 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 Filelistxml 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

OSoftSetupexe ‒ 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 or OSoftSSIS2012_Client on the client machine followed by the SQL Server

version If you want to use SQL 2008 Tasks under the SQL 2012 environment you must install

OSoftSSIS2008_Client on the application server For detailed information see SAP Note 1707410

You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package by extracting

OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPC

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 or

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4754

OSoftSSIS2012_Client for creating a COM+ application For more information see Before You Modify

the SSIS Packages [page 50] and Setup of a COM+ Application on the Application Server [page 51]

Bin folder

This folder contains the following components

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCCachedll Planning and Consolidation Cache file

BPCDataFlowPackagedll or BPCDataFlowPackage2012dll

BPCDMdll

BPCDMTaskMaindll COM+ component

BPCFilePreviewdll

BPCGacUtil_20exe System File

BPCGacUtil_40exe System File

BPCImpersonatordll Planning and Consolidation Impersonator

BPCLogicdll

BPCScriptdll

BPCServerZipdll

BPCServiceResdll

BPCTransferMembersdll

BPCWriteBackdll

InteropDTSdll

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

4854 CUSTOMER 2012-06-13

Name Remark

OSoftAdminServerdll

OSoftAuditdll

OSoftComLibServerdll

OSoftCommonResQrydll

OSoftConfigurationdll

OSoftCustomXMLSvrdll

OSoftDatabaseADMINdll

OSoftDatabaseSYSADMINdll

OSoftDatabaseSYSADMINDMdll

OSoftDatabaseUSERdll

OSoftDMDTSXExecutedll or OSoftDMDTSXExecute2012dll

OSoftDMTaskFormdll

OSoftDMTaskMaindll

OSoftDMToolsdll

OSoftFileManagedll

OSoftLoggingdll

OSoftLogWriterdll

OSoftMetaDatadll

OSoftSQEdll

OSoftSystemConfigdll

OutlookSoftconfig Configuration file to connect DB server

XceedCompressiondll XceedZip file

XceedCompressionFormatsdll XceedZip file

XceedFileSystemdll XceedZip file

XceedZipdll XceedZip file

Config folder

This folder has FileListxml 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 FileListxml 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

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4954

OSoftSetupexe

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

NOTE

If you installed the OSoftSSIS2008_Client or OSoftSSIS2012_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

Resources Folder

This folder contains the BPCServicesdll and BPCServiceUIdll files which contain resource text

Only English resources are included for the SSIS custom tasks

82 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

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008 and 2012 respectively

8 Installing SSIS Custom Tasks

82 Before You Modify the SSIS Packages

5054 CUSTOMER 2012-06-13

Name Remark

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012 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

lthellipgtOSoftSSIS2008_Clientbin or lthellipgtOSoftSSIS2012_Clientbin

On the Planning and Consolidation application server

ltdrivegtWebsrvrbin

2 Paste these files into the folder 100DTSTasks for SQL Server 2008 or into 110DTSTasks for

SQL Server 2012 For example if you install your SQL 2008 server or R2 on CProgram Files

Microsoft SQL Server paste all files into the CProgram Files (x86)Microsoft SQL Server

100DTSTasks folder

In Integration Services set the property Run64BitRunTime to True

83 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 or OSoftSSIS2012_Client on the

application server

8 Installing SSIS Custom Tasks

83 Setup of a COM+ Application on the Application Server

2012-06-13 CUSTOMER 5154

Typographic Conventions

Example Description

ltgt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example Enter your ltUser Namegt

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 httpwwwsapcom

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

5254 CUSTOMER 2012-06-13

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

  • SAP BusinessObjects Planning and Consolidation 100
    • Table of Contents
    • 1 Introduction
      • 11 SAP Notes for the Installation
      • 12 Naming Conventions
        • 2 Installing Planning and Consolidation Servers
          • 21 Basic Steps
          • 22 Prerequisites
          • 23 Before Starting the Planning and Consolidation Server Installation
          • 24 Logging on to Servers
          • 25 Service-level Accounts
          • 26 Standard and Advanced Settings
          • 27 Installing the Prerequisites
            • 271 Installing the Prerequisites ndash Basic Steps
            • 272 Installing the Operating System
            • 273 Installing the SQL Server
            • 274 Installing Analysis Services
            • 275 Installing the Anti-Cross Site Scripting Library
              • 28 Installing on a Single Server
              • 29 Installing the Server in a Multiserver Configuration
                • 3 After Installing Planning and Consolidation Servers
                  • 31 Post-Installation Steps
                  • 32 Connecting to Solution Manager Diagnostics
                  • 33 Configuring the Planning and Consolidation NET Application Servers
                  • 34 Post-Installation Optional Configuration Steps
                    • 341 Enabling the Management Console
                    • 342 Setting Up ODBC Logging in IIS for the Default Web Site
                    • 343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2
                    • 344 Removing Default Access to the Console
                    • 345 Management Console Access Control
                    • 346 Using Client Certificates
                        • 4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office
                          • 41 Installing the Administration Client
                          • 42 Installing the EPM Add-in
                          • 43 Using the Client Auto Update Program
                            • 5 Connection Issues
                              • 51 Checking for Open Ports
                              • 52 Proxy Server and Firewall Issues
                                • 6 Installing Planning and Consolidation with Two Active Directory Domains
                                • 7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
                                  • 71 Terminal Services Home Directories
                                  • 72 System Requirements
                                  • 73 Installing Planning and Consolidation
                                  • 74 Creating a Shortcut to the Launch Page
                                    • 8 Installing SSIS Custom Tasks
                                      • 81 Composition of SSIS Custom Task Installation
                                      • 82 Before You Modify the SSIS Packages
                                      • 83 Setup of a COM+ Application on the Application Server
                                          • Copyright and trademarks
Page 42: Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

synchronizes the user name and password on the remote server with the local user name and

password

NOTE

For more information about setting up an ISA proxy server contact SAP Support to request a

copy of Setting up ISA Proxy Server White Paper

Internet Explorer Settings 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

5 Connection Issues

52 Proxy Server and Firewall Issues

4254 CUSTOMER 2012-06-13

6 Installing Planning and Consolidation with Two Active Directory Domains

To set up a Planning and Consolidation 10 application server in a hosted environment and use your

own domain users follow this procedure In general you install Planning and Consolidation on the

host domain use the host domain account and assign it to the Planning and Consolidation users

SysAdmin Admin and Users Then you accept one way trust (the host domain trusts your domain)

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

6 Installing Planning and Consolidation with Two Active Directory Domains

2012-06-13 CUSTOMER 4354

This page is left blank for documents that are printed on both sides

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

This section describes best practices and instructions for installing Planning and Consolidation in a

Terminal Services or Citrix Server deployment

71 Terminal Services Home Directories

We recommend using Terminal Server home directories rather than using the userrsquos 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

72 System Requirements

The Citrix server should be one of the following systems

XenApp 5 Enterprise

XenApp 5 Platinum

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 37])

73 Installing Planning and Consolidation

Prerequisites

The server installation files have been downloaded from SAP Service Marketplace and installed

Procedure

The following steps outline how to install the Planning and Consolidation clients in a Terminal Services

(TS) or Citrix Server deployment

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

71 Terminal Services Home Directories

2012-06-13 CUSTOMER 4554

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 userinstall

4 Open a browser and connect to the URL httpltPC_serverportgtsapbpcweb

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 userexecute 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 Iexploreexe http(s)

ltServerNamegt-NetBIOS or FQDNsapbpcweb

To publish Planning and Consolidation Administration CProgram FilesPC_MS

BPCAdminMainexe

74 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 userrsquos desktop) must be moved to the All UsersDesktop folder

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

74 Creating a Shortcut to the Launch Page

4654 CUSTOMER 2012-06-13

8 Installing SSIS Custom Tasks

This section provides background information and instructions for installing SQL Server Integration

Services (SSIS) for SQL Server 2008 and SQL Server 2012

The Planning and Consolidation Data Manager component supports and uses SSIS Since SQL Server

2008 and SQL Server 2012 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

81 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 Filelistxml 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

OSoftSetupexe ‒ 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 or OSoftSSIS2012_Client on the client machine followed by the SQL Server

version If you want to use SQL 2008 Tasks under the SQL 2012 environment you must install

OSoftSSIS2008_Client on the application server For detailed information see SAP Note 1707410

You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package by extracting

OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPC

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 or

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4754

OSoftSSIS2012_Client for creating a COM+ application For more information see Before You Modify

the SSIS Packages [page 50] and Setup of a COM+ Application on the Application Server [page 51]

Bin folder

This folder contains the following components

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCCachedll Planning and Consolidation Cache file

BPCDataFlowPackagedll or BPCDataFlowPackage2012dll

BPCDMdll

BPCDMTaskMaindll COM+ component

BPCFilePreviewdll

BPCGacUtil_20exe System File

BPCGacUtil_40exe System File

BPCImpersonatordll Planning and Consolidation Impersonator

BPCLogicdll

BPCScriptdll

BPCServerZipdll

BPCServiceResdll

BPCTransferMembersdll

BPCWriteBackdll

InteropDTSdll

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

4854 CUSTOMER 2012-06-13

Name Remark

OSoftAdminServerdll

OSoftAuditdll

OSoftComLibServerdll

OSoftCommonResQrydll

OSoftConfigurationdll

OSoftCustomXMLSvrdll

OSoftDatabaseADMINdll

OSoftDatabaseSYSADMINdll

OSoftDatabaseSYSADMINDMdll

OSoftDatabaseUSERdll

OSoftDMDTSXExecutedll or OSoftDMDTSXExecute2012dll

OSoftDMTaskFormdll

OSoftDMTaskMaindll

OSoftDMToolsdll

OSoftFileManagedll

OSoftLoggingdll

OSoftLogWriterdll

OSoftMetaDatadll

OSoftSQEdll

OSoftSystemConfigdll

OutlookSoftconfig Configuration file to connect DB server

XceedCompressiondll XceedZip file

XceedCompressionFormatsdll XceedZip file

XceedFileSystemdll XceedZip file

XceedZipdll XceedZip file

Config folder

This folder has FileListxml 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 FileListxml 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

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4954

OSoftSetupexe

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

NOTE

If you installed the OSoftSSIS2008_Client or OSoftSSIS2012_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

Resources Folder

This folder contains the BPCServicesdll and BPCServiceUIdll files which contain resource text

Only English resources are included for the SSIS custom tasks

82 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

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008 and 2012 respectively

8 Installing SSIS Custom Tasks

82 Before You Modify the SSIS Packages

5054 CUSTOMER 2012-06-13

Name Remark

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012 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

lthellipgtOSoftSSIS2008_Clientbin or lthellipgtOSoftSSIS2012_Clientbin

On the Planning and Consolidation application server

ltdrivegtWebsrvrbin

2 Paste these files into the folder 100DTSTasks for SQL Server 2008 or into 110DTSTasks for

SQL Server 2012 For example if you install your SQL 2008 server or R2 on CProgram Files

Microsoft SQL Server paste all files into the CProgram Files (x86)Microsoft SQL Server

100DTSTasks folder

In Integration Services set the property Run64BitRunTime to True

83 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 or OSoftSSIS2012_Client on the

application server

8 Installing SSIS Custom Tasks

83 Setup of a COM+ Application on the Application Server

2012-06-13 CUSTOMER 5154

Typographic Conventions

Example Description

ltgt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example Enter your ltUser Namegt

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 httpwwwsapcom

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

5254 CUSTOMER 2012-06-13

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

  • SAP BusinessObjects Planning and Consolidation 100
    • Table of Contents
    • 1 Introduction
      • 11 SAP Notes for the Installation
      • 12 Naming Conventions
        • 2 Installing Planning and Consolidation Servers
          • 21 Basic Steps
          • 22 Prerequisites
          • 23 Before Starting the Planning and Consolidation Server Installation
          • 24 Logging on to Servers
          • 25 Service-level Accounts
          • 26 Standard and Advanced Settings
          • 27 Installing the Prerequisites
            • 271 Installing the Prerequisites ndash Basic Steps
            • 272 Installing the Operating System
            • 273 Installing the SQL Server
            • 274 Installing Analysis Services
            • 275 Installing the Anti-Cross Site Scripting Library
              • 28 Installing on a Single Server
              • 29 Installing the Server in a Multiserver Configuration
                • 3 After Installing Planning and Consolidation Servers
                  • 31 Post-Installation Steps
                  • 32 Connecting to Solution Manager Diagnostics
                  • 33 Configuring the Planning and Consolidation NET Application Servers
                  • 34 Post-Installation Optional Configuration Steps
                    • 341 Enabling the Management Console
                    • 342 Setting Up ODBC Logging in IIS for the Default Web Site
                    • 343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2
                    • 344 Removing Default Access to the Console
                    • 345 Management Console Access Control
                    • 346 Using Client Certificates
                        • 4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office
                          • 41 Installing the Administration Client
                          • 42 Installing the EPM Add-in
                          • 43 Using the Client Auto Update Program
                            • 5 Connection Issues
                              • 51 Checking for Open Ports
                              • 52 Proxy Server and Firewall Issues
                                • 6 Installing Planning and Consolidation with Two Active Directory Domains
                                • 7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
                                  • 71 Terminal Services Home Directories
                                  • 72 System Requirements
                                  • 73 Installing Planning and Consolidation
                                  • 74 Creating a Shortcut to the Launch Page
                                    • 8 Installing SSIS Custom Tasks
                                      • 81 Composition of SSIS Custom Task Installation
                                      • 82 Before You Modify the SSIS Packages
                                      • 83 Setup of a COM+ Application on the Application Server
                                          • Copyright and trademarks
Page 43: Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

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

6 Installing Planning and Consolidation with Two Active Directory Domains

2012-06-13 CUSTOMER 4354

This page is left blank for documents that are printed on both sides

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

This section describes best practices and instructions for installing Planning and Consolidation in a

Terminal Services or Citrix Server deployment

71 Terminal Services Home Directories

We recommend using Terminal Server home directories rather than using the userrsquos 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

72 System Requirements

The Citrix server should be one of the following systems

XenApp 5 Enterprise

XenApp 5 Platinum

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 37])

73 Installing Planning and Consolidation

Prerequisites

The server installation files have been downloaded from SAP Service Marketplace and installed

Procedure

The following steps outline how to install the Planning and Consolidation clients in a Terminal Services

(TS) or Citrix Server deployment

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

71 Terminal Services Home Directories

2012-06-13 CUSTOMER 4554

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 userinstall

4 Open a browser and connect to the URL httpltPC_serverportgtsapbpcweb

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 userexecute 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 Iexploreexe http(s)

ltServerNamegt-NetBIOS or FQDNsapbpcweb

To publish Planning and Consolidation Administration CProgram FilesPC_MS

BPCAdminMainexe

74 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 userrsquos desktop) must be moved to the All UsersDesktop folder

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

74 Creating a Shortcut to the Launch Page

4654 CUSTOMER 2012-06-13

8 Installing SSIS Custom Tasks

This section provides background information and instructions for installing SQL Server Integration

Services (SSIS) for SQL Server 2008 and SQL Server 2012

The Planning and Consolidation Data Manager component supports and uses SSIS Since SQL Server

2008 and SQL Server 2012 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

81 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 Filelistxml 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

OSoftSetupexe ‒ 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 or OSoftSSIS2012_Client on the client machine followed by the SQL Server

version If you want to use SQL 2008 Tasks under the SQL 2012 environment you must install

OSoftSSIS2008_Client on the application server For detailed information see SAP Note 1707410

You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package by extracting

OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPC

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 or

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4754

OSoftSSIS2012_Client for creating a COM+ application For more information see Before You Modify

the SSIS Packages [page 50] and Setup of a COM+ Application on the Application Server [page 51]

Bin folder

This folder contains the following components

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCCachedll Planning and Consolidation Cache file

BPCDataFlowPackagedll or BPCDataFlowPackage2012dll

BPCDMdll

BPCDMTaskMaindll COM+ component

BPCFilePreviewdll

BPCGacUtil_20exe System File

BPCGacUtil_40exe System File

BPCImpersonatordll Planning and Consolidation Impersonator

BPCLogicdll

BPCScriptdll

BPCServerZipdll

BPCServiceResdll

BPCTransferMembersdll

BPCWriteBackdll

InteropDTSdll

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

4854 CUSTOMER 2012-06-13

Name Remark

OSoftAdminServerdll

OSoftAuditdll

OSoftComLibServerdll

OSoftCommonResQrydll

OSoftConfigurationdll

OSoftCustomXMLSvrdll

OSoftDatabaseADMINdll

OSoftDatabaseSYSADMINdll

OSoftDatabaseSYSADMINDMdll

OSoftDatabaseUSERdll

OSoftDMDTSXExecutedll or OSoftDMDTSXExecute2012dll

OSoftDMTaskFormdll

OSoftDMTaskMaindll

OSoftDMToolsdll

OSoftFileManagedll

OSoftLoggingdll

OSoftLogWriterdll

OSoftMetaDatadll

OSoftSQEdll

OSoftSystemConfigdll

OutlookSoftconfig Configuration file to connect DB server

XceedCompressiondll XceedZip file

XceedCompressionFormatsdll XceedZip file

XceedFileSystemdll XceedZip file

XceedZipdll XceedZip file

Config folder

This folder has FileListxml 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 FileListxml 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

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4954

OSoftSetupexe

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

NOTE

If you installed the OSoftSSIS2008_Client or OSoftSSIS2012_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

Resources Folder

This folder contains the BPCServicesdll and BPCServiceUIdll files which contain resource text

Only English resources are included for the SSIS custom tasks

82 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

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008 and 2012 respectively

8 Installing SSIS Custom Tasks

82 Before You Modify the SSIS Packages

5054 CUSTOMER 2012-06-13

Name Remark

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012 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

lthellipgtOSoftSSIS2008_Clientbin or lthellipgtOSoftSSIS2012_Clientbin

On the Planning and Consolidation application server

ltdrivegtWebsrvrbin

2 Paste these files into the folder 100DTSTasks for SQL Server 2008 or into 110DTSTasks for

SQL Server 2012 For example if you install your SQL 2008 server or R2 on CProgram Files

Microsoft SQL Server paste all files into the CProgram Files (x86)Microsoft SQL Server

100DTSTasks folder

In Integration Services set the property Run64BitRunTime to True

83 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 or OSoftSSIS2012_Client on the

application server

8 Installing SSIS Custom Tasks

83 Setup of a COM+ Application on the Application Server

2012-06-13 CUSTOMER 5154

Typographic Conventions

Example Description

ltgt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example Enter your ltUser Namegt

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 httpwwwsapcom

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

5254 CUSTOMER 2012-06-13

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

  • SAP BusinessObjects Planning and Consolidation 100
    • Table of Contents
    • 1 Introduction
      • 11 SAP Notes for the Installation
      • 12 Naming Conventions
        • 2 Installing Planning and Consolidation Servers
          • 21 Basic Steps
          • 22 Prerequisites
          • 23 Before Starting the Planning and Consolidation Server Installation
          • 24 Logging on to Servers
          • 25 Service-level Accounts
          • 26 Standard and Advanced Settings
          • 27 Installing the Prerequisites
            • 271 Installing the Prerequisites ndash Basic Steps
            • 272 Installing the Operating System
            • 273 Installing the SQL Server
            • 274 Installing Analysis Services
            • 275 Installing the Anti-Cross Site Scripting Library
              • 28 Installing on a Single Server
              • 29 Installing the Server in a Multiserver Configuration
                • 3 After Installing Planning and Consolidation Servers
                  • 31 Post-Installation Steps
                  • 32 Connecting to Solution Manager Diagnostics
                  • 33 Configuring the Planning and Consolidation NET Application Servers
                  • 34 Post-Installation Optional Configuration Steps
                    • 341 Enabling the Management Console
                    • 342 Setting Up ODBC Logging in IIS for the Default Web Site
                    • 343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2
                    • 344 Removing Default Access to the Console
                    • 345 Management Console Access Control
                    • 346 Using Client Certificates
                        • 4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office
                          • 41 Installing the Administration Client
                          • 42 Installing the EPM Add-in
                          • 43 Using the Client Auto Update Program
                            • 5 Connection Issues
                              • 51 Checking for Open Ports
                              • 52 Proxy Server and Firewall Issues
                                • 6 Installing Planning and Consolidation with Two Active Directory Domains
                                • 7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
                                  • 71 Terminal Services Home Directories
                                  • 72 System Requirements
                                  • 73 Installing Planning and Consolidation
                                  • 74 Creating a Shortcut to the Launch Page
                                    • 8 Installing SSIS Custom Tasks
                                      • 81 Composition of SSIS Custom Task Installation
                                      • 82 Before You Modify the SSIS Packages
                                      • 83 Setup of a COM+ Application on the Application Server
                                          • Copyright and trademarks
Page 44: Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

This page is left blank for documents that are printed on both sides

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

This section describes best practices and instructions for installing Planning and Consolidation in a

Terminal Services or Citrix Server deployment

71 Terminal Services Home Directories

We recommend using Terminal Server home directories rather than using the userrsquos 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

72 System Requirements

The Citrix server should be one of the following systems

XenApp 5 Enterprise

XenApp 5 Platinum

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 37])

73 Installing Planning and Consolidation

Prerequisites

The server installation files have been downloaded from SAP Service Marketplace and installed

Procedure

The following steps outline how to install the Planning and Consolidation clients in a Terminal Services

(TS) or Citrix Server deployment

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

71 Terminal Services Home Directories

2012-06-13 CUSTOMER 4554

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 userinstall

4 Open a browser and connect to the URL httpltPC_serverportgtsapbpcweb

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 userexecute 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 Iexploreexe http(s)

ltServerNamegt-NetBIOS or FQDNsapbpcweb

To publish Planning and Consolidation Administration CProgram FilesPC_MS

BPCAdminMainexe

74 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 userrsquos desktop) must be moved to the All UsersDesktop folder

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

74 Creating a Shortcut to the Launch Page

4654 CUSTOMER 2012-06-13

8 Installing SSIS Custom Tasks

This section provides background information and instructions for installing SQL Server Integration

Services (SSIS) for SQL Server 2008 and SQL Server 2012

The Planning and Consolidation Data Manager component supports and uses SSIS Since SQL Server

2008 and SQL Server 2012 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

81 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 Filelistxml 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

OSoftSetupexe ‒ 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 or OSoftSSIS2012_Client on the client machine followed by the SQL Server

version If you want to use SQL 2008 Tasks under the SQL 2012 environment you must install

OSoftSSIS2008_Client on the application server For detailed information see SAP Note 1707410

You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package by extracting

OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPC

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 or

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4754

OSoftSSIS2012_Client for creating a COM+ application For more information see Before You Modify

the SSIS Packages [page 50] and Setup of a COM+ Application on the Application Server [page 51]

Bin folder

This folder contains the following components

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCCachedll Planning and Consolidation Cache file

BPCDataFlowPackagedll or BPCDataFlowPackage2012dll

BPCDMdll

BPCDMTaskMaindll COM+ component

BPCFilePreviewdll

BPCGacUtil_20exe System File

BPCGacUtil_40exe System File

BPCImpersonatordll Planning and Consolidation Impersonator

BPCLogicdll

BPCScriptdll

BPCServerZipdll

BPCServiceResdll

BPCTransferMembersdll

BPCWriteBackdll

InteropDTSdll

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

4854 CUSTOMER 2012-06-13

Name Remark

OSoftAdminServerdll

OSoftAuditdll

OSoftComLibServerdll

OSoftCommonResQrydll

OSoftConfigurationdll

OSoftCustomXMLSvrdll

OSoftDatabaseADMINdll

OSoftDatabaseSYSADMINdll

OSoftDatabaseSYSADMINDMdll

OSoftDatabaseUSERdll

OSoftDMDTSXExecutedll or OSoftDMDTSXExecute2012dll

OSoftDMTaskFormdll

OSoftDMTaskMaindll

OSoftDMToolsdll

OSoftFileManagedll

OSoftLoggingdll

OSoftLogWriterdll

OSoftMetaDatadll

OSoftSQEdll

OSoftSystemConfigdll

OutlookSoftconfig Configuration file to connect DB server

XceedCompressiondll XceedZip file

XceedCompressionFormatsdll XceedZip file

XceedFileSystemdll XceedZip file

XceedZipdll XceedZip file

Config folder

This folder has FileListxml 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 FileListxml 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

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4954

OSoftSetupexe

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

NOTE

If you installed the OSoftSSIS2008_Client or OSoftSSIS2012_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

Resources Folder

This folder contains the BPCServicesdll and BPCServiceUIdll files which contain resource text

Only English resources are included for the SSIS custom tasks

82 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

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008 and 2012 respectively

8 Installing SSIS Custom Tasks

82 Before You Modify the SSIS Packages

5054 CUSTOMER 2012-06-13

Name Remark

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012 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

lthellipgtOSoftSSIS2008_Clientbin or lthellipgtOSoftSSIS2012_Clientbin

On the Planning and Consolidation application server

ltdrivegtWebsrvrbin

2 Paste these files into the folder 100DTSTasks for SQL Server 2008 or into 110DTSTasks for

SQL Server 2012 For example if you install your SQL 2008 server or R2 on CProgram Files

Microsoft SQL Server paste all files into the CProgram Files (x86)Microsoft SQL Server

100DTSTasks folder

In Integration Services set the property Run64BitRunTime to True

83 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 or OSoftSSIS2012_Client on the

application server

8 Installing SSIS Custom Tasks

83 Setup of a COM+ Application on the Application Server

2012-06-13 CUSTOMER 5154

Typographic Conventions

Example Description

ltgt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example Enter your ltUser Namegt

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 httpwwwsapcom

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

5254 CUSTOMER 2012-06-13

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

  • SAP BusinessObjects Planning and Consolidation 100
    • Table of Contents
    • 1 Introduction
      • 11 SAP Notes for the Installation
      • 12 Naming Conventions
        • 2 Installing Planning and Consolidation Servers
          • 21 Basic Steps
          • 22 Prerequisites
          • 23 Before Starting the Planning and Consolidation Server Installation
          • 24 Logging on to Servers
          • 25 Service-level Accounts
          • 26 Standard and Advanced Settings
          • 27 Installing the Prerequisites
            • 271 Installing the Prerequisites ndash Basic Steps
            • 272 Installing the Operating System
            • 273 Installing the SQL Server
            • 274 Installing Analysis Services
            • 275 Installing the Anti-Cross Site Scripting Library
              • 28 Installing on a Single Server
              • 29 Installing the Server in a Multiserver Configuration
                • 3 After Installing Planning and Consolidation Servers
                  • 31 Post-Installation Steps
                  • 32 Connecting to Solution Manager Diagnostics
                  • 33 Configuring the Planning and Consolidation NET Application Servers
                  • 34 Post-Installation Optional Configuration Steps
                    • 341 Enabling the Management Console
                    • 342 Setting Up ODBC Logging in IIS for the Default Web Site
                    • 343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2
                    • 344 Removing Default Access to the Console
                    • 345 Management Console Access Control
                    • 346 Using Client Certificates
                        • 4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office
                          • 41 Installing the Administration Client
                          • 42 Installing the EPM Add-in
                          • 43 Using the Client Auto Update Program
                            • 5 Connection Issues
                              • 51 Checking for Open Ports
                              • 52 Proxy Server and Firewall Issues
                                • 6 Installing Planning and Consolidation with Two Active Directory Domains
                                • 7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
                                  • 71 Terminal Services Home Directories
                                  • 72 System Requirements
                                  • 73 Installing Planning and Consolidation
                                  • 74 Creating a Shortcut to the Launch Page
                                    • 8 Installing SSIS Custom Tasks
                                      • 81 Composition of SSIS Custom Task Installation
                                      • 82 Before You Modify the SSIS Packages
                                      • 83 Setup of a COM+ Application on the Application Server
                                          • Copyright and trademarks
Page 45: Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

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

71 Terminal Services Home Directories

We recommend using Terminal Server home directories rather than using the userrsquos 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

72 System Requirements

The Citrix server should be one of the following systems

XenApp 5 Enterprise

XenApp 5 Platinum

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 37])

73 Installing Planning and Consolidation

Prerequisites

The server installation files have been downloaded from SAP Service Marketplace and installed

Procedure

The following steps outline how to install the Planning and Consolidation clients in a Terminal Services

(TS) or Citrix Server deployment

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

71 Terminal Services Home Directories

2012-06-13 CUSTOMER 4554

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 userinstall

4 Open a browser and connect to the URL httpltPC_serverportgtsapbpcweb

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 userexecute 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 Iexploreexe http(s)

ltServerNamegt-NetBIOS or FQDNsapbpcweb

To publish Planning and Consolidation Administration CProgram FilesPC_MS

BPCAdminMainexe

74 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 userrsquos desktop) must be moved to the All UsersDesktop folder

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

74 Creating a Shortcut to the Launch Page

4654 CUSTOMER 2012-06-13

8 Installing SSIS Custom Tasks

This section provides background information and instructions for installing SQL Server Integration

Services (SSIS) for SQL Server 2008 and SQL Server 2012

The Planning and Consolidation Data Manager component supports and uses SSIS Since SQL Server

2008 and SQL Server 2012 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

81 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 Filelistxml 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

OSoftSetupexe ‒ 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 or OSoftSSIS2012_Client on the client machine followed by the SQL Server

version If you want to use SQL 2008 Tasks under the SQL 2012 environment you must install

OSoftSSIS2008_Client on the application server For detailed information see SAP Note 1707410

You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package by extracting

OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPC

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 or

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4754

OSoftSSIS2012_Client for creating a COM+ application For more information see Before You Modify

the SSIS Packages [page 50] and Setup of a COM+ Application on the Application Server [page 51]

Bin folder

This folder contains the following components

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCCachedll Planning and Consolidation Cache file

BPCDataFlowPackagedll or BPCDataFlowPackage2012dll

BPCDMdll

BPCDMTaskMaindll COM+ component

BPCFilePreviewdll

BPCGacUtil_20exe System File

BPCGacUtil_40exe System File

BPCImpersonatordll Planning and Consolidation Impersonator

BPCLogicdll

BPCScriptdll

BPCServerZipdll

BPCServiceResdll

BPCTransferMembersdll

BPCWriteBackdll

InteropDTSdll

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

4854 CUSTOMER 2012-06-13

Name Remark

OSoftAdminServerdll

OSoftAuditdll

OSoftComLibServerdll

OSoftCommonResQrydll

OSoftConfigurationdll

OSoftCustomXMLSvrdll

OSoftDatabaseADMINdll

OSoftDatabaseSYSADMINdll

OSoftDatabaseSYSADMINDMdll

OSoftDatabaseUSERdll

OSoftDMDTSXExecutedll or OSoftDMDTSXExecute2012dll

OSoftDMTaskFormdll

OSoftDMTaskMaindll

OSoftDMToolsdll

OSoftFileManagedll

OSoftLoggingdll

OSoftLogWriterdll

OSoftMetaDatadll

OSoftSQEdll

OSoftSystemConfigdll

OutlookSoftconfig Configuration file to connect DB server

XceedCompressiondll XceedZip file

XceedCompressionFormatsdll XceedZip file

XceedFileSystemdll XceedZip file

XceedZipdll XceedZip file

Config folder

This folder has FileListxml 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 FileListxml 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

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4954

OSoftSetupexe

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

NOTE

If you installed the OSoftSSIS2008_Client or OSoftSSIS2012_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

Resources Folder

This folder contains the BPCServicesdll and BPCServiceUIdll files which contain resource text

Only English resources are included for the SSIS custom tasks

82 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

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008 and 2012 respectively

8 Installing SSIS Custom Tasks

82 Before You Modify the SSIS Packages

5054 CUSTOMER 2012-06-13

Name Remark

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012 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

lthellipgtOSoftSSIS2008_Clientbin or lthellipgtOSoftSSIS2012_Clientbin

On the Planning and Consolidation application server

ltdrivegtWebsrvrbin

2 Paste these files into the folder 100DTSTasks for SQL Server 2008 or into 110DTSTasks for

SQL Server 2012 For example if you install your SQL 2008 server or R2 on CProgram Files

Microsoft SQL Server paste all files into the CProgram Files (x86)Microsoft SQL Server

100DTSTasks folder

In Integration Services set the property Run64BitRunTime to True

83 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 or OSoftSSIS2012_Client on the

application server

8 Installing SSIS Custom Tasks

83 Setup of a COM+ Application on the Application Server

2012-06-13 CUSTOMER 5154

Typographic Conventions

Example Description

ltgt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example Enter your ltUser Namegt

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 httpwwwsapcom

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

5254 CUSTOMER 2012-06-13

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

  • SAP BusinessObjects Planning and Consolidation 100
    • Table of Contents
    • 1 Introduction
      • 11 SAP Notes for the Installation
      • 12 Naming Conventions
        • 2 Installing Planning and Consolidation Servers
          • 21 Basic Steps
          • 22 Prerequisites
          • 23 Before Starting the Planning and Consolidation Server Installation
          • 24 Logging on to Servers
          • 25 Service-level Accounts
          • 26 Standard and Advanced Settings
          • 27 Installing the Prerequisites
            • 271 Installing the Prerequisites ndash Basic Steps
            • 272 Installing the Operating System
            • 273 Installing the SQL Server
            • 274 Installing Analysis Services
            • 275 Installing the Anti-Cross Site Scripting Library
              • 28 Installing on a Single Server
              • 29 Installing the Server in a Multiserver Configuration
                • 3 After Installing Planning and Consolidation Servers
                  • 31 Post-Installation Steps
                  • 32 Connecting to Solution Manager Diagnostics
                  • 33 Configuring the Planning and Consolidation NET Application Servers
                  • 34 Post-Installation Optional Configuration Steps
                    • 341 Enabling the Management Console
                    • 342 Setting Up ODBC Logging in IIS for the Default Web Site
                    • 343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2
                    • 344 Removing Default Access to the Console
                    • 345 Management Console Access Control
                    • 346 Using Client Certificates
                        • 4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office
                          • 41 Installing the Administration Client
                          • 42 Installing the EPM Add-in
                          • 43 Using the Client Auto Update Program
                            • 5 Connection Issues
                              • 51 Checking for Open Ports
                              • 52 Proxy Server and Firewall Issues
                                • 6 Installing Planning and Consolidation with Two Active Directory Domains
                                • 7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
                                  • 71 Terminal Services Home Directories
                                  • 72 System Requirements
                                  • 73 Installing Planning and Consolidation
                                  • 74 Creating a Shortcut to the Launch Page
                                    • 8 Installing SSIS Custom Tasks
                                      • 81 Composition of SSIS Custom Task Installation
                                      • 82 Before You Modify the SSIS Packages
                                      • 83 Setup of a COM+ Application on the Application Server
                                          • Copyright and trademarks
Page 46: Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

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 userinstall

4 Open a browser and connect to the URL httpltPC_serverportgtsapbpcweb

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 userexecute 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 Iexploreexe http(s)

ltServerNamegt-NetBIOS or FQDNsapbpcweb

To publish Planning and Consolidation Administration CProgram FilesPC_MS

BPCAdminMainexe

74 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 userrsquos desktop) must be moved to the All UsersDesktop folder

7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment

74 Creating a Shortcut to the Launch Page

4654 CUSTOMER 2012-06-13

8 Installing SSIS Custom Tasks

This section provides background information and instructions for installing SQL Server Integration

Services (SSIS) for SQL Server 2008 and SQL Server 2012

The Planning and Consolidation Data Manager component supports and uses SSIS Since SQL Server

2008 and SQL Server 2012 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

81 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 Filelistxml 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

OSoftSetupexe ‒ 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 or OSoftSSIS2012_Client on the client machine followed by the SQL Server

version If you want to use SQL 2008 Tasks under the SQL 2012 environment you must install

OSoftSSIS2008_Client on the application server For detailed information see SAP Note 1707410

You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package by extracting

OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPC

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 or

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4754

OSoftSSIS2012_Client for creating a COM+ application For more information see Before You Modify

the SSIS Packages [page 50] and Setup of a COM+ Application on the Application Server [page 51]

Bin folder

This folder contains the following components

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCCachedll Planning and Consolidation Cache file

BPCDataFlowPackagedll or BPCDataFlowPackage2012dll

BPCDMdll

BPCDMTaskMaindll COM+ component

BPCFilePreviewdll

BPCGacUtil_20exe System File

BPCGacUtil_40exe System File

BPCImpersonatordll Planning and Consolidation Impersonator

BPCLogicdll

BPCScriptdll

BPCServerZipdll

BPCServiceResdll

BPCTransferMembersdll

BPCWriteBackdll

InteropDTSdll

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

4854 CUSTOMER 2012-06-13

Name Remark

OSoftAdminServerdll

OSoftAuditdll

OSoftComLibServerdll

OSoftCommonResQrydll

OSoftConfigurationdll

OSoftCustomXMLSvrdll

OSoftDatabaseADMINdll

OSoftDatabaseSYSADMINdll

OSoftDatabaseSYSADMINDMdll

OSoftDatabaseUSERdll

OSoftDMDTSXExecutedll or OSoftDMDTSXExecute2012dll

OSoftDMTaskFormdll

OSoftDMTaskMaindll

OSoftDMToolsdll

OSoftFileManagedll

OSoftLoggingdll

OSoftLogWriterdll

OSoftMetaDatadll

OSoftSQEdll

OSoftSystemConfigdll

OutlookSoftconfig Configuration file to connect DB server

XceedCompressiondll XceedZip file

XceedCompressionFormatsdll XceedZip file

XceedFileSystemdll XceedZip file

XceedZipdll XceedZip file

Config folder

This folder has FileListxml 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 FileListxml 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

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4954

OSoftSetupexe

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

NOTE

If you installed the OSoftSSIS2008_Client or OSoftSSIS2012_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

Resources Folder

This folder contains the BPCServicesdll and BPCServiceUIdll files which contain resource text

Only English resources are included for the SSIS custom tasks

82 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

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008 and 2012 respectively

8 Installing SSIS Custom Tasks

82 Before You Modify the SSIS Packages

5054 CUSTOMER 2012-06-13

Name Remark

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012 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

lthellipgtOSoftSSIS2008_Clientbin or lthellipgtOSoftSSIS2012_Clientbin

On the Planning and Consolidation application server

ltdrivegtWebsrvrbin

2 Paste these files into the folder 100DTSTasks for SQL Server 2008 or into 110DTSTasks for

SQL Server 2012 For example if you install your SQL 2008 server or R2 on CProgram Files

Microsoft SQL Server paste all files into the CProgram Files (x86)Microsoft SQL Server

100DTSTasks folder

In Integration Services set the property Run64BitRunTime to True

83 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 or OSoftSSIS2012_Client on the

application server

8 Installing SSIS Custom Tasks

83 Setup of a COM+ Application on the Application Server

2012-06-13 CUSTOMER 5154

Typographic Conventions

Example Description

ltgt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example Enter your ltUser Namegt

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 httpwwwsapcom

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

5254 CUSTOMER 2012-06-13

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

  • SAP BusinessObjects Planning and Consolidation 100
    • Table of Contents
    • 1 Introduction
      • 11 SAP Notes for the Installation
      • 12 Naming Conventions
        • 2 Installing Planning and Consolidation Servers
          • 21 Basic Steps
          • 22 Prerequisites
          • 23 Before Starting the Planning and Consolidation Server Installation
          • 24 Logging on to Servers
          • 25 Service-level Accounts
          • 26 Standard and Advanced Settings
          • 27 Installing the Prerequisites
            • 271 Installing the Prerequisites ndash Basic Steps
            • 272 Installing the Operating System
            • 273 Installing the SQL Server
            • 274 Installing Analysis Services
            • 275 Installing the Anti-Cross Site Scripting Library
              • 28 Installing on a Single Server
              • 29 Installing the Server in a Multiserver Configuration
                • 3 After Installing Planning and Consolidation Servers
                  • 31 Post-Installation Steps
                  • 32 Connecting to Solution Manager Diagnostics
                  • 33 Configuring the Planning and Consolidation NET Application Servers
                  • 34 Post-Installation Optional Configuration Steps
                    • 341 Enabling the Management Console
                    • 342 Setting Up ODBC Logging in IIS for the Default Web Site
                    • 343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2
                    • 344 Removing Default Access to the Console
                    • 345 Management Console Access Control
                    • 346 Using Client Certificates
                        • 4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office
                          • 41 Installing the Administration Client
                          • 42 Installing the EPM Add-in
                          • 43 Using the Client Auto Update Program
                            • 5 Connection Issues
                              • 51 Checking for Open Ports
                              • 52 Proxy Server and Firewall Issues
                                • 6 Installing Planning and Consolidation with Two Active Directory Domains
                                • 7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
                                  • 71 Terminal Services Home Directories
                                  • 72 System Requirements
                                  • 73 Installing Planning and Consolidation
                                  • 74 Creating a Shortcut to the Launch Page
                                    • 8 Installing SSIS Custom Tasks
                                      • 81 Composition of SSIS Custom Task Installation
                                      • 82 Before You Modify the SSIS Packages
                                      • 83 Setup of a COM+ Application on the Application Server
                                          • Copyright and trademarks
Page 47: Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

8 Installing SSIS Custom Tasks

This section provides background information and instructions for installing SQL Server Integration

Services (SSIS) for SQL Server 2008 and SQL Server 2012

The Planning and Consolidation Data Manager component supports and uses SSIS Since SQL Server

2008 and SQL Server 2012 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

81 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 Filelistxml 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

OSoftSetupexe ‒ 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 or OSoftSSIS2012_Client on the client machine followed by the SQL Server

version If you want to use SQL 2008 Tasks under the SQL 2012 environment you must install

OSoftSSIS2008_Client on the application server For detailed information see SAP Note 1707410

You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package by extracting

OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPC

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 or

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4754

OSoftSSIS2012_Client for creating a COM+ application For more information see Before You Modify

the SSIS Packages [page 50] and Setup of a COM+ Application on the Application Server [page 51]

Bin folder

This folder contains the following components

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCCachedll Planning and Consolidation Cache file

BPCDataFlowPackagedll or BPCDataFlowPackage2012dll

BPCDMdll

BPCDMTaskMaindll COM+ component

BPCFilePreviewdll

BPCGacUtil_20exe System File

BPCGacUtil_40exe System File

BPCImpersonatordll Planning and Consolidation Impersonator

BPCLogicdll

BPCScriptdll

BPCServerZipdll

BPCServiceResdll

BPCTransferMembersdll

BPCWriteBackdll

InteropDTSdll

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

4854 CUSTOMER 2012-06-13

Name Remark

OSoftAdminServerdll

OSoftAuditdll

OSoftComLibServerdll

OSoftCommonResQrydll

OSoftConfigurationdll

OSoftCustomXMLSvrdll

OSoftDatabaseADMINdll

OSoftDatabaseSYSADMINdll

OSoftDatabaseSYSADMINDMdll

OSoftDatabaseUSERdll

OSoftDMDTSXExecutedll or OSoftDMDTSXExecute2012dll

OSoftDMTaskFormdll

OSoftDMTaskMaindll

OSoftDMToolsdll

OSoftFileManagedll

OSoftLoggingdll

OSoftLogWriterdll

OSoftMetaDatadll

OSoftSQEdll

OSoftSystemConfigdll

OutlookSoftconfig Configuration file to connect DB server

XceedCompressiondll XceedZip file

XceedCompressionFormatsdll XceedZip file

XceedFileSystemdll XceedZip file

XceedZipdll XceedZip file

Config folder

This folder has FileListxml 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 FileListxml 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

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4954

OSoftSetupexe

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

NOTE

If you installed the OSoftSSIS2008_Client or OSoftSSIS2012_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

Resources Folder

This folder contains the BPCServicesdll and BPCServiceUIdll files which contain resource text

Only English resources are included for the SSIS custom tasks

82 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

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008 and 2012 respectively

8 Installing SSIS Custom Tasks

82 Before You Modify the SSIS Packages

5054 CUSTOMER 2012-06-13

Name Remark

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012 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

lthellipgtOSoftSSIS2008_Clientbin or lthellipgtOSoftSSIS2012_Clientbin

On the Planning and Consolidation application server

ltdrivegtWebsrvrbin

2 Paste these files into the folder 100DTSTasks for SQL Server 2008 or into 110DTSTasks for

SQL Server 2012 For example if you install your SQL 2008 server or R2 on CProgram Files

Microsoft SQL Server paste all files into the CProgram Files (x86)Microsoft SQL Server

100DTSTasks folder

In Integration Services set the property Run64BitRunTime to True

83 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 or OSoftSSIS2012_Client on the

application server

8 Installing SSIS Custom Tasks

83 Setup of a COM+ Application on the Application Server

2012-06-13 CUSTOMER 5154

Typographic Conventions

Example Description

ltgt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example Enter your ltUser Namegt

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 httpwwwsapcom

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

5254 CUSTOMER 2012-06-13

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

  • SAP BusinessObjects Planning and Consolidation 100
    • Table of Contents
    • 1 Introduction
      • 11 SAP Notes for the Installation
      • 12 Naming Conventions
        • 2 Installing Planning and Consolidation Servers
          • 21 Basic Steps
          • 22 Prerequisites
          • 23 Before Starting the Planning and Consolidation Server Installation
          • 24 Logging on to Servers
          • 25 Service-level Accounts
          • 26 Standard and Advanced Settings
          • 27 Installing the Prerequisites
            • 271 Installing the Prerequisites ndash Basic Steps
            • 272 Installing the Operating System
            • 273 Installing the SQL Server
            • 274 Installing Analysis Services
            • 275 Installing the Anti-Cross Site Scripting Library
              • 28 Installing on a Single Server
              • 29 Installing the Server in a Multiserver Configuration
                • 3 After Installing Planning and Consolidation Servers
                  • 31 Post-Installation Steps
                  • 32 Connecting to Solution Manager Diagnostics
                  • 33 Configuring the Planning and Consolidation NET Application Servers
                  • 34 Post-Installation Optional Configuration Steps
                    • 341 Enabling the Management Console
                    • 342 Setting Up ODBC Logging in IIS for the Default Web Site
                    • 343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2
                    • 344 Removing Default Access to the Console
                    • 345 Management Console Access Control
                    • 346 Using Client Certificates
                        • 4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office
                          • 41 Installing the Administration Client
                          • 42 Installing the EPM Add-in
                          • 43 Using the Client Auto Update Program
                            • 5 Connection Issues
                              • 51 Checking for Open Ports
                              • 52 Proxy Server and Firewall Issues
                                • 6 Installing Planning and Consolidation with Two Active Directory Domains
                                • 7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
                                  • 71 Terminal Services Home Directories
                                  • 72 System Requirements
                                  • 73 Installing Planning and Consolidation
                                  • 74 Creating a Shortcut to the Launch Page
                                    • 8 Installing SSIS Custom Tasks
                                      • 81 Composition of SSIS Custom Task Installation
                                      • 82 Before You Modify the SSIS Packages
                                      • 83 Setup of a COM+ Application on the Application Server
                                          • Copyright and trademarks
Page 48: Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

OSoftSSIS2012_Client for creating a COM+ application For more information see Before You Modify

the SSIS Packages [page 50] and Setup of a COM+ Application on the Application Server [page 51]

Bin folder

This folder contains the following components

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012 respectively

BPCCachedll Planning and Consolidation Cache file

BPCDataFlowPackagedll or BPCDataFlowPackage2012dll

BPCDMdll

BPCDMTaskMaindll COM+ component

BPCFilePreviewdll

BPCGacUtil_20exe System File

BPCGacUtil_40exe System File

BPCImpersonatordll Planning and Consolidation Impersonator

BPCLogicdll

BPCScriptdll

BPCServerZipdll

BPCServiceResdll

BPCTransferMembersdll

BPCWriteBackdll

InteropDTSdll

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

4854 CUSTOMER 2012-06-13

Name Remark

OSoftAdminServerdll

OSoftAuditdll

OSoftComLibServerdll

OSoftCommonResQrydll

OSoftConfigurationdll

OSoftCustomXMLSvrdll

OSoftDatabaseADMINdll

OSoftDatabaseSYSADMINdll

OSoftDatabaseSYSADMINDMdll

OSoftDatabaseUSERdll

OSoftDMDTSXExecutedll or OSoftDMDTSXExecute2012dll

OSoftDMTaskFormdll

OSoftDMTaskMaindll

OSoftDMToolsdll

OSoftFileManagedll

OSoftLoggingdll

OSoftLogWriterdll

OSoftMetaDatadll

OSoftSQEdll

OSoftSystemConfigdll

OutlookSoftconfig Configuration file to connect DB server

XceedCompressiondll XceedZip file

XceedCompressionFormatsdll XceedZip file

XceedFileSystemdll XceedZip file

XceedZipdll XceedZip file

Config folder

This folder has FileListxml 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 FileListxml 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

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4954

OSoftSetupexe

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

NOTE

If you installed the OSoftSSIS2008_Client or OSoftSSIS2012_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

Resources Folder

This folder contains the BPCServicesdll and BPCServiceUIdll files which contain resource text

Only English resources are included for the SSIS custom tasks

82 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

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008 and 2012 respectively

8 Installing SSIS Custom Tasks

82 Before You Modify the SSIS Packages

5054 CUSTOMER 2012-06-13

Name Remark

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012 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

lthellipgtOSoftSSIS2008_Clientbin or lthellipgtOSoftSSIS2012_Clientbin

On the Planning and Consolidation application server

ltdrivegtWebsrvrbin

2 Paste these files into the folder 100DTSTasks for SQL Server 2008 or into 110DTSTasks for

SQL Server 2012 For example if you install your SQL 2008 server or R2 on CProgram Files

Microsoft SQL Server paste all files into the CProgram Files (x86)Microsoft SQL Server

100DTSTasks folder

In Integration Services set the property Run64BitRunTime to True

83 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 or OSoftSSIS2012_Client on the

application server

8 Installing SSIS Custom Tasks

83 Setup of a COM+ Application on the Application Server

2012-06-13 CUSTOMER 5154

Typographic Conventions

Example Description

ltgt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example Enter your ltUser Namegt

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 httpwwwsapcom

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

5254 CUSTOMER 2012-06-13

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

  • SAP BusinessObjects Planning and Consolidation 100
    • Table of Contents
    • 1 Introduction
      • 11 SAP Notes for the Installation
      • 12 Naming Conventions
        • 2 Installing Planning and Consolidation Servers
          • 21 Basic Steps
          • 22 Prerequisites
          • 23 Before Starting the Planning and Consolidation Server Installation
          • 24 Logging on to Servers
          • 25 Service-level Accounts
          • 26 Standard and Advanced Settings
          • 27 Installing the Prerequisites
            • 271 Installing the Prerequisites ndash Basic Steps
            • 272 Installing the Operating System
            • 273 Installing the SQL Server
            • 274 Installing Analysis Services
            • 275 Installing the Anti-Cross Site Scripting Library
              • 28 Installing on a Single Server
              • 29 Installing the Server in a Multiserver Configuration
                • 3 After Installing Planning and Consolidation Servers
                  • 31 Post-Installation Steps
                  • 32 Connecting to Solution Manager Diagnostics
                  • 33 Configuring the Planning and Consolidation NET Application Servers
                  • 34 Post-Installation Optional Configuration Steps
                    • 341 Enabling the Management Console
                    • 342 Setting Up ODBC Logging in IIS for the Default Web Site
                    • 343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2
                    • 344 Removing Default Access to the Console
                    • 345 Management Console Access Control
                    • 346 Using Client Certificates
                        • 4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office
                          • 41 Installing the Administration Client
                          • 42 Installing the EPM Add-in
                          • 43 Using the Client Auto Update Program
                            • 5 Connection Issues
                              • 51 Checking for Open Ports
                              • 52 Proxy Server and Firewall Issues
                                • 6 Installing Planning and Consolidation with Two Active Directory Domains
                                • 7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
                                  • 71 Terminal Services Home Directories
                                  • 72 System Requirements
                                  • 73 Installing Planning and Consolidation
                                  • 74 Creating a Shortcut to the Launch Page
                                    • 8 Installing SSIS Custom Tasks
                                      • 81 Composition of SSIS Custom Task Installation
                                      • 82 Before You Modify the SSIS Packages
                                      • 83 Setup of a COM+ Application on the Application Server
                                          • Copyright and trademarks
Page 49: Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

Name Remark

OSoftAdminServerdll

OSoftAuditdll

OSoftComLibServerdll

OSoftCommonResQrydll

OSoftConfigurationdll

OSoftCustomXMLSvrdll

OSoftDatabaseADMINdll

OSoftDatabaseSYSADMINdll

OSoftDatabaseSYSADMINDMdll

OSoftDatabaseUSERdll

OSoftDMDTSXExecutedll or OSoftDMDTSXExecute2012dll

OSoftDMTaskFormdll

OSoftDMTaskMaindll

OSoftDMToolsdll

OSoftFileManagedll

OSoftLoggingdll

OSoftLogWriterdll

OSoftMetaDatadll

OSoftSQEdll

OSoftSystemConfigdll

OutlookSoftconfig Configuration file to connect DB server

XceedCompressiondll XceedZip file

XceedCompressionFormatsdll XceedZip file

XceedFileSystemdll XceedZip file

XceedZipdll XceedZip file

Config folder

This folder has FileListxml 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 FileListxml 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

8 Installing SSIS Custom Tasks

81 Composition of SSIS Custom Task Installation

2012-06-13 CUSTOMER 4954

OSoftSetupexe

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

NOTE

If you installed the OSoftSSIS2008_Client or OSoftSSIS2012_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

Resources Folder

This folder contains the BPCServicesdll and BPCServiceUIdll files which contain resource text

Only English resources are included for the SSIS custom tasks

82 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

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008 and 2012 respectively

8 Installing SSIS Custom Tasks

82 Before You Modify the SSIS Packages

5054 CUSTOMER 2012-06-13

Name Remark

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012 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

lthellipgtOSoftSSIS2008_Clientbin or lthellipgtOSoftSSIS2012_Clientbin

On the Planning and Consolidation application server

ltdrivegtWebsrvrbin

2 Paste these files into the folder 100DTSTasks for SQL Server 2008 or into 110DTSTasks for

SQL Server 2012 For example if you install your SQL 2008 server or R2 on CProgram Files

Microsoft SQL Server paste all files into the CProgram Files (x86)Microsoft SQL Server

100DTSTasks folder

In Integration Services set the property Run64BitRunTime to True

83 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 or OSoftSSIS2012_Client on the

application server

8 Installing SSIS Custom Tasks

83 Setup of a COM+ Application on the Application Server

2012-06-13 CUSTOMER 5154

Typographic Conventions

Example Description

ltgt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example Enter your ltUser Namegt

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 httpwwwsapcom

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

5254 CUSTOMER 2012-06-13

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

  • SAP BusinessObjects Planning and Consolidation 100
    • Table of Contents
    • 1 Introduction
      • 11 SAP Notes for the Installation
      • 12 Naming Conventions
        • 2 Installing Planning and Consolidation Servers
          • 21 Basic Steps
          • 22 Prerequisites
          • 23 Before Starting the Planning and Consolidation Server Installation
          • 24 Logging on to Servers
          • 25 Service-level Accounts
          • 26 Standard and Advanced Settings
          • 27 Installing the Prerequisites
            • 271 Installing the Prerequisites ndash Basic Steps
            • 272 Installing the Operating System
            • 273 Installing the SQL Server
            • 274 Installing Analysis Services
            • 275 Installing the Anti-Cross Site Scripting Library
              • 28 Installing on a Single Server
              • 29 Installing the Server in a Multiserver Configuration
                • 3 After Installing Planning and Consolidation Servers
                  • 31 Post-Installation Steps
                  • 32 Connecting to Solution Manager Diagnostics
                  • 33 Configuring the Planning and Consolidation NET Application Servers
                  • 34 Post-Installation Optional Configuration Steps
                    • 341 Enabling the Management Console
                    • 342 Setting Up ODBC Logging in IIS for the Default Web Site
                    • 343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2
                    • 344 Removing Default Access to the Console
                    • 345 Management Console Access Control
                    • 346 Using Client Certificates
                        • 4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office
                          • 41 Installing the Administration Client
                          • 42 Installing the EPM Add-in
                          • 43 Using the Client Auto Update Program
                            • 5 Connection Issues
                              • 51 Checking for Open Ports
                              • 52 Proxy Server and Firewall Issues
                                • 6 Installing Planning and Consolidation with Two Active Directory Domains
                                • 7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
                                  • 71 Terminal Services Home Directories
                                  • 72 System Requirements
                                  • 73 Installing Planning and Consolidation
                                  • 74 Creating a Shortcut to the Launch Page
                                    • 8 Installing SSIS Custom Tasks
                                      • 81 Composition of SSIS Custom Task Installation
                                      • 82 Before You Modify the SSIS Packages
                                      • 83 Setup of a COM+ Application on the Application Server
                                          • Copyright and trademarks
Page 50: Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

OSoftSetupexe

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

NOTE

If you installed the OSoftSSIS2008_Client or OSoftSSIS2012_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

Resources Folder

This folder contains the BPCServicesdll and BPCServiceUIdll files which contain resource text

Only English resources are included for the SSIS custom tasks

82 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

Name Remark

BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012 respectively

BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012 respectively

BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008 and 2012 respectively

BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and 2012 respectively

BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012 respectively

BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and 2012 respectively

BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012 respectively

BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008 and 2012 respectively

8 Installing SSIS Custom Tasks

82 Before You Modify the SSIS Packages

5054 CUSTOMER 2012-06-13

Name Remark

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012 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

lthellipgtOSoftSSIS2008_Clientbin or lthellipgtOSoftSSIS2012_Clientbin

On the Planning and Consolidation application server

ltdrivegtWebsrvrbin

2 Paste these files into the folder 100DTSTasks for SQL Server 2008 or into 110DTSTasks for

SQL Server 2012 For example if you install your SQL 2008 server or R2 on CProgram Files

Microsoft SQL Server paste all files into the CProgram Files (x86)Microsoft SQL Server

100DTSTasks folder

In Integration Services set the property Run64BitRunTime to True

83 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 or OSoftSSIS2012_Client on the

application server

8 Installing SSIS Custom Tasks

83 Setup of a COM+ Application on the Application Server

2012-06-13 CUSTOMER 5154

Typographic Conventions

Example Description

ltgt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example Enter your ltUser Namegt

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 httpwwwsapcom

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

5254 CUSTOMER 2012-06-13

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

  • SAP BusinessObjects Planning and Consolidation 100
    • Table of Contents
    • 1 Introduction
      • 11 SAP Notes for the Installation
      • 12 Naming Conventions
        • 2 Installing Planning and Consolidation Servers
          • 21 Basic Steps
          • 22 Prerequisites
          • 23 Before Starting the Planning and Consolidation Server Installation
          • 24 Logging on to Servers
          • 25 Service-level Accounts
          • 26 Standard and Advanced Settings
          • 27 Installing the Prerequisites
            • 271 Installing the Prerequisites ndash Basic Steps
            • 272 Installing the Operating System
            • 273 Installing the SQL Server
            • 274 Installing Analysis Services
            • 275 Installing the Anti-Cross Site Scripting Library
              • 28 Installing on a Single Server
              • 29 Installing the Server in a Multiserver Configuration
                • 3 After Installing Planning and Consolidation Servers
                  • 31 Post-Installation Steps
                  • 32 Connecting to Solution Manager Diagnostics
                  • 33 Configuring the Planning and Consolidation NET Application Servers
                  • 34 Post-Installation Optional Configuration Steps
                    • 341 Enabling the Management Console
                    • 342 Setting Up ODBC Logging in IIS for the Default Web Site
                    • 343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2
                    • 344 Removing Default Access to the Console
                    • 345 Management Console Access Control
                    • 346 Using Client Certificates
                        • 4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office
                          • 41 Installing the Administration Client
                          • 42 Installing the EPM Add-in
                          • 43 Using the Client Auto Update Program
                            • 5 Connection Issues
                              • 51 Checking for Open Ports
                              • 52 Proxy Server and Firewall Issues
                                • 6 Installing Planning and Consolidation with Two Active Directory Domains
                                • 7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
                                  • 71 Terminal Services Home Directories
                                  • 72 System Requirements
                                  • 73 Installing Planning and Consolidation
                                  • 74 Creating a Shortcut to the Launch Page
                                    • 8 Installing SSIS Custom Tasks
                                      • 81 Composition of SSIS Custom Task Installation
                                      • 82 Before You Modify the SSIS Packages
                                      • 83 Setup of a COM+ Application on the Application Server
                                          • Copyright and trademarks
Page 51: Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

Name Remark

BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL 2008 and 2012 respectively

BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and 2012 respectively

BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012 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

lthellipgtOSoftSSIS2008_Clientbin or lthellipgtOSoftSSIS2012_Clientbin

On the Planning and Consolidation application server

ltdrivegtWebsrvrbin

2 Paste these files into the folder 100DTSTasks for SQL Server 2008 or into 110DTSTasks for

SQL Server 2012 For example if you install your SQL 2008 server or R2 on CProgram Files

Microsoft SQL Server paste all files into the CProgram Files (x86)Microsoft SQL Server

100DTSTasks folder

In Integration Services set the property Run64BitRunTime to True

83 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 or OSoftSSIS2012_Client on the

application server

8 Installing SSIS Custom Tasks

83 Setup of a COM+ Application on the Application Server

2012-06-13 CUSTOMER 5154

Typographic Conventions

Example Description

ltgt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example Enter your ltUser Namegt

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 httpwwwsapcom

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

5254 CUSTOMER 2012-06-13

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

  • SAP BusinessObjects Planning and Consolidation 100
    • Table of Contents
    • 1 Introduction
      • 11 SAP Notes for the Installation
      • 12 Naming Conventions
        • 2 Installing Planning and Consolidation Servers
          • 21 Basic Steps
          • 22 Prerequisites
          • 23 Before Starting the Planning and Consolidation Server Installation
          • 24 Logging on to Servers
          • 25 Service-level Accounts
          • 26 Standard and Advanced Settings
          • 27 Installing the Prerequisites
            • 271 Installing the Prerequisites ndash Basic Steps
            • 272 Installing the Operating System
            • 273 Installing the SQL Server
            • 274 Installing Analysis Services
            • 275 Installing the Anti-Cross Site Scripting Library
              • 28 Installing on a Single Server
              • 29 Installing the Server in a Multiserver Configuration
                • 3 After Installing Planning and Consolidation Servers
                  • 31 Post-Installation Steps
                  • 32 Connecting to Solution Manager Diagnostics
                  • 33 Configuring the Planning and Consolidation NET Application Servers
                  • 34 Post-Installation Optional Configuration Steps
                    • 341 Enabling the Management Console
                    • 342 Setting Up ODBC Logging in IIS for the Default Web Site
                    • 343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2
                    • 344 Removing Default Access to the Console
                    • 345 Management Console Access Control
                    • 346 Using Client Certificates
                        • 4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office
                          • 41 Installing the Administration Client
                          • 42 Installing the EPM Add-in
                          • 43 Using the Client Auto Update Program
                            • 5 Connection Issues
                              • 51 Checking for Open Ports
                              • 52 Proxy Server and Firewall Issues
                                • 6 Installing Planning and Consolidation with Two Active Directory Domains
                                • 7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
                                  • 71 Terminal Services Home Directories
                                  • 72 System Requirements
                                  • 73 Installing Planning and Consolidation
                                  • 74 Creating a Shortcut to the Launch Page
                                    • 8 Installing SSIS Custom Tasks
                                      • 81 Composition of SSIS Custom Task Installation
                                      • 82 Before You Modify the SSIS Packages
                                      • 83 Setup of a COM+ Application on the Application Server
                                          • Copyright and trademarks
Page 52: Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

Typographic Conventions

Example Description

ltgt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example Enter your ltUser Namegt

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 httpwwwsapcom

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

5254 CUSTOMER 2012-06-13

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

  • SAP BusinessObjects Planning and Consolidation 100
    • Table of Contents
    • 1 Introduction
      • 11 SAP Notes for the Installation
      • 12 Naming Conventions
        • 2 Installing Planning and Consolidation Servers
          • 21 Basic Steps
          • 22 Prerequisites
          • 23 Before Starting the Planning and Consolidation Server Installation
          • 24 Logging on to Servers
          • 25 Service-level Accounts
          • 26 Standard and Advanced Settings
          • 27 Installing the Prerequisites
            • 271 Installing the Prerequisites ndash Basic Steps
            • 272 Installing the Operating System
            • 273 Installing the SQL Server
            • 274 Installing Analysis Services
            • 275 Installing the Anti-Cross Site Scripting Library
              • 28 Installing on a Single Server
              • 29 Installing the Server in a Multiserver Configuration
                • 3 After Installing Planning and Consolidation Servers
                  • 31 Post-Installation Steps
                  • 32 Connecting to Solution Manager Diagnostics
                  • 33 Configuring the Planning and Consolidation NET Application Servers
                  • 34 Post-Installation Optional Configuration Steps
                    • 341 Enabling the Management Console
                    • 342 Setting Up ODBC Logging in IIS for the Default Web Site
                    • 343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2
                    • 344 Removing Default Access to the Console
                    • 345 Management Console Access Control
                    • 346 Using Client Certificates
                        • 4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office
                          • 41 Installing the Administration Client
                          • 42 Installing the EPM Add-in
                          • 43 Using the Client Auto Update Program
                            • 5 Connection Issues
                              • 51 Checking for Open Ports
                              • 52 Proxy Server and Firewall Issues
                                • 6 Installing Planning and Consolidation with Two Active Directory Domains
                                • 7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
                                  • 71 Terminal Services Home Directories
                                  • 72 System Requirements
                                  • 73 Installing Planning and Consolidation
                                  • 74 Creating a Shortcut to the Launch Page
                                    • 8 Installing SSIS Custom Tasks
                                      • 81 Composition of SSIS Custom Task Installation
                                      • 82 Before You Modify the SSIS Packages
                                      • 83 Setup of a COM+ Application on the Application Server
                                          • Copyright and trademarks
Page 53: Installation Guide SAP BusinessObjects Planning and Consolidation 10.0

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

  • SAP BusinessObjects Planning and Consolidation 100
    • Table of Contents
    • 1 Introduction
      • 11 SAP Notes for the Installation
      • 12 Naming Conventions
        • 2 Installing Planning and Consolidation Servers
          • 21 Basic Steps
          • 22 Prerequisites
          • 23 Before Starting the Planning and Consolidation Server Installation
          • 24 Logging on to Servers
          • 25 Service-level Accounts
          • 26 Standard and Advanced Settings
          • 27 Installing the Prerequisites
            • 271 Installing the Prerequisites ndash Basic Steps
            • 272 Installing the Operating System
            • 273 Installing the SQL Server
            • 274 Installing Analysis Services
            • 275 Installing the Anti-Cross Site Scripting Library
              • 28 Installing on a Single Server
              • 29 Installing the Server in a Multiserver Configuration
                • 3 After Installing Planning and Consolidation Servers
                  • 31 Post-Installation Steps
                  • 32 Connecting to Solution Manager Diagnostics
                  • 33 Configuring the Planning and Consolidation NET Application Servers
                  • 34 Post-Installation Optional Configuration Steps
                    • 341 Enabling the Management Console
                    • 342 Setting Up ODBC Logging in IIS for the Default Web Site
                    • 343 Setting Up an ODBC Data Source in Windows Server 2008 or Windows Server 2008 R2
                    • 344 Removing Default Access to the Console
                    • 345 Management Console Access Control
                    • 346 Using Client Certificates
                        • 4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjects EPM solutions Add-in for Microsoft Office
                          • 41 Installing the Administration Client
                          • 42 Installing the EPM Add-in
                          • 43 Using the Client Auto Update Program
                            • 5 Connection Issues
                              • 51 Checking for Open Ports
                              • 52 Proxy Server and Firewall Issues
                                • 6 Installing Planning and Consolidation with Two Active Directory Domains
                                • 7 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
                                  • 71 Terminal Services Home Directories
                                  • 72 System Requirements
                                  • 73 Installing Planning and Consolidation
                                  • 74 Creating a Shortcut to the Launch Page
                                    • 8 Installing SSIS Custom Tasks
                                      • 81 Composition of SSIS Custom Task Installation
                                      • 82 Before You Modify the SSIS Packages
                                      • 83 Setup of a COM+ Application on the Application Server
                                          • Copyright and trademarks