Überblick und Einblick in die neue SAP Planungslösung BPC 10.1.
Installation Guide BPC MS 10.pdf
-
Upload
david-ilich-madrid-oyanadel -
Category
Documents
-
view
126 -
download
5
Transcript of Installation Guide BPC MS 10.pdf
Installation GuideDocument version 18 ndash 2014-08-08
SAP Business Planning and Consolidation 100version for the Microsoft platform
CUSTOMER
copy Copyright 2014 SAP AG or an SAP affiliate company Alle Rechte vorbehalten All rights reserved Tous droitsreacuteserveacutes Все права защищены
Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcherForm auch immer ohne die ausdruumlckliche schriftliche Genehmigung durch SAP AG nicht gestattet In dieserPublikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werden
Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcherForm auch immer ohne die ausdruumlckliche schriftliche Genehmigung durch SAP AG nicht gestattet In dieserPublikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werden
No part of this publication may be reproduced or transmitted in any form or for any purpose without the expresspermission of SAP AG The information contained herein may be changed without prior notice
Microsoft Windows Outlook and PowerPoint are registered trademarks of Microsoft Corporation
IBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400iSeries pSeries xSeries zSeries System i System i5 System p System p5 System x System z System z9 zOSAFP Intelligent Miner WebSphere Netfinity Tivoli Informix i5OS POWER POWER5 POWER5+ OpenPower andPowerPC are trademarks or registered trademarks of IBM Corporation
Adobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of AdobeSystems Incorporated in the United States andor other countries
Oracle is a registered trademark of Oracle Corporation
UNIX XOpen OSF1 and Motif are registered trademarks of the Open Group
Citrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems Inc
HTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of Technology
Java is a registered trademark of Sun Microsystems Inc
JavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented andimplemented by Netscape
MaxDB is a trademark of MySQL AB Sweden
SAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentionedherein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in severalother countries all over the world All other product and service names mentioned are the trademarks of theirrespective companies Data contained in this document serves informational purposes only National productspecifications may vary
These materials are subject to change without notice These materials are provided by SAP AG and its affiliatedcompanies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAPGroup shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Groupproducts and services are those that are set forth in the express warranty statements accompanying such productsand services if any Nothing herein should be construed as constituting an additional warranty
Some components of this product are based on Javatrade Any code change in these components may causeunpredictable and severe malfunctions and is therefore expressively prohibited as is any decompilation of thesecomponents
Any Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not bemodified or altered in any way
2
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
Documentation on the SAP Service Marketplace
You can find this document at the following address servicesapcominstguidesEPM-BPC
SAP Business Planning and Consolidation 100Documentation on the SAP Service Marketplace
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 3
Document History
The following table provides an overview of the most important document changes
Table 1
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 SingleServerrdquo
Added 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 recommendationto 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 recommendinstalling Microsoft Office on the application server Also removed the note at the end of theprocedure that discussed launching the installation of a Microsoft ACE OLEDB Provider on amachine 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 andConsolidation NET Application Serversrdquo
137 2012-06-13 Updated NET 20 to NET 40 in the topic ldquoConfiguring the Planning and Consolidation NETApplication Serversrdquo
138 2012-10-17 Improved the installation procedure in the topic ldquoInstalling on a Single Serverrdquo
139 2012-12-05 Changes in the topics ldquoPrerequisitesrdquo and ldquoInstalling the Prerequisites ndash Basic Stepsrdquo mdashupdated the required version of Microsoft Visual C++ and vcredist_x64exe
14 2013-04-30 Updated the topic Installing the Administration Client [page 37] with versions of MicrosoftInternet Explorer and Microsoft Office supported as of support package 10
15 2013-09-09 Updated the topic ldquoSAP Notes for the Installationrdquo with the central note number for supportpackage 11
16 2013-10-17 Updated the topic Proxy Server and Firewall Issues [page 41] with a note to refer to SAP Note1505250 for information about firewall ports
165 2014-01-10 Updated the topic ldquoSAP Notes for the Installationrdquo with the central note number for supportpackage 12
17 2014-04-02 Added topics about configuring SSL in IIS and in SQL Server Reporting Services
18 2014-08-08 For support package 14
4
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Document History
Version Date Description
Updated the topic ldquoImportant SAP Notesrdquo with the central note number for supportpackage 14
In the topic Prerequisites [page 11] added Windows 2012 to the list of possibleoperating systems and added IIS 80 IIS 85 NET 35 and NET 45 to OtherRequirements
Updated the topic Setting Up an ODBC Data Source in Windows Server 2008 2008R2 [page 32] to include Windows 2012
SAP Business Planning and Consolidation 100Document History
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 5
Content
1 Introduction 911 SAP Notes for the Installation 912 Naming Conventions 10
2 Installing Planning and Consolidation Servers 1121 Basic Steps 1122 Prerequisites 1123 Before Starting the Planning and Consolidation Server Installation 1324 Logging on to Servers 1425 Service-level Accounts 1526 Standard and Advanced Settings 1627 Installing the Prerequisites 17
Installing the Prerequisites ndash Basic Steps 17 Installing the Operating System 19 Installing the SQL Server 19 Installing Analysis Services 23 Installing the Anti-Cross Site Scripting Library 23
28 Installing on a Single Server 2429 Installing the Server in a Multiserver Configuration 25
3 After Installing Planning and Consolidation Servers 2731 Post-Installation Steps 2732 Connecting to Solution Manager Diagnostics 2833 Configuring the Planning and Consolidation NET Application Servers 2934 Post-Installation Optional Configuration Steps 29
Enabling the Management Console 30 Setting Up ODBC Logging in IIS for the Default Web Site 30 Setting Up an ODBC Data Source in Windows Server 2008 2008 R2 2012 or 2012
R2 32 Removing Default Access to the Console 32 Management Console Access Control 33 Configuring Planning and Consolidation to use SSL 34 Using Client Certificates 35 Configuring MS SQL Server Reporting Services to use SSL 36
4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjectsEPM solutions Add-in for Microsoft Office 37
41 Installing the Administration Client 3742 Installing the EPM Add-in 3843 Using the Client Auto Update Program 38
5 Connection Issues 4151 Checking for Open Ports 4152 Proxy Server and Firewall Issues 41
6
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Content
6 Installing Planning and Consolidation with Two Active Directory Domains 43
7 Installing Planning and Consolidation in a Terminal Services or Citrix ServerDeployment 44
71 Terminal Services Home Directories 4472 System Requirements 4473 Installing Planning and Consolidation 4474 Creating a Shortcut to the Launch Page 45
8 Installing SSIS Custom Tasks 4681 Composition of SSIS Custom Task Installation 4682 Before You Modify the SSIS Packages 4983 Setup of a COM+ Application on the Application Server 50
SAP Business Planning and Consolidation 100Content
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 7
8
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
1 Introduction
The SAP BusinessObjects Planning and Consolidation Installation Guide is intended for System Administrators whoperform Planning and Consolidation server and Administration client installations It contains everything you needto 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 releasewe provide detailed instructions on how to migrate your existing environments For more information see theUpgrade Guide which is available on SAP Service Marketplace at servicesapcominstguidesEPM-BPC Planningand Consolidation 100 version for the Microsoft platform
For more information about the Planning and Consolidation Office client software see the SAP BusinessObjects EPMsolutions 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 FileOLAP 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 2008or Windows Server 2008 R2 for remote desktop access
Planning and Consolidation no longer requires a separate Web server only an application server You can installthe application server on a single machine or on multiple machines with network load balancing (NLB) If youuse 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 informationon the installation as well as corrections to the installation documentation Make sure that you have the up-to-dateversion of each SAP Note which you can find in the SAP Service Marketplace at the Internet addressservicesapcomnotes
Table 2
SAP Note Number Title Comments
1584890 Documentation Addendum Contains information that does not yet appear in theapplication help of Business Planning and Consolidation100 version for the Microsoft platform Application helpis available at helpsapcombopacms100
2000499 Business Planning amp Consolidation 10 forMicrosoft SP14 Central Note
This note contains important information about theinstallation of support package 14
SAP Business Planning and Consolidation 100Introduction
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 9
SAP Note Number Title Comments
1961655 Business Planning amp Consolidation 10 forMicrosoft SP13 Central Note
This note contains important information about theinstallation of support package 13
1897745 Business Planning amp Consolidation 10 forMicrosoft SP12 Central Note
This note contains important information about theinstallation of support package 12
1846917 Business Planning amp Consolidation 10 forMicrosoft SP11 Central Note
This note contains important information about theinstallation of support package 11
1804918 Business Planning amp Consolidation 10 forMicrosoft SP10 Central Note
This note contains important information about theinstallation of support package 10
1755355 Business Planning amp Consolidation 10 forMicrosoft SP09 Central Note
This note contains important information about theinstallation of support package 9
1733053 Business Planning amp Consolidation 10 forMicrosoft SP08 Central Note
This note contains important information about theinstallation of support package 8
1689792 Business Planning amp Consolidation 10 forMicrosoft SP07 Central Note
This note contains important information about theinstallation of support package 7
1665656 Business Planning amp Consolidation 10 forMicrosoft SP06 Central Note
This note contains important information about theinstallation of support package 6
1643037 Business Planning amp Consolidation 10 forMicrosoft SP05 Central Note
This note contains important information about theinstallation of support package 5
1620464 Business Planning amp Consolidation 10 forMicrosoft SP04 Central Note
This note contains important information about theinstallation of support package 4
1601213 Business Planning amp Consolidation 10 forMicrosoft SP03 Central Note
This note contains important information about theinstallation of support package 3
1591848 Business Planning amp Consolidation 10 forMicrosoft SP02 Central Note
This note contains important information about theinstallation of support package 2
1573539 Business Planning amp Consolidation 10 forMicrosoft SP01 Central Note
This note contains important information about theinstallation of support package 1
12 Naming Conventions
In this document the following naming conventions apply
Table 3
Variable Description
ltPC_serverportgt Server name or IP address and port number of SAP Planningand Consolidation application location
ltdrivegt The drive where SAP Planning and Consolidation is installed
The default for this is CPC_MS
10
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Introduction
2 Installing Planning and ConsolidationServers
This section includes the basic steps for installing a Planning and Consolidation server the prerequisites and whatto 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 atservicesapcominstguidesepm-bpc 100 version for the Microsoft platform
2 Perform the tasks in the Before Starting the Planning and Consolidation Server Installation [page 13] sectionincluding installing all prerequisites
3 From the application server install the Planning and Consolidation server See Installing Planning andConsolidation on a Single Server [page 24]
NoteYou must install both Planning and Consolidation 100 as well as the most recent Planning and Consolidation100 Support Package available from the SAP Service Marketplace at servicesapcomswdc SoftwareDownloads Support Packages and Patches A - Z Index B SAP BPC FOR MICROSOFT SBOP PC 100FOR MICROSOFT Comprised Software Component Versions SAP CPM BPC 100 M Windows Server onx64 64bit
4 If you have multiple machines see Installing the Server in a Multiserver Configuration [page 25]
5 Perform the steps in the section After Installing Planning and Consolidation Servers [page 27]
22 Prerequisites
The following table describes the software you need to install before installing the Planning and Consolidation serverand the minimum versions required
NoteA list of the supported operating systems and database systems is also available in the Product Availability Matrixon SAP Service Marketplace at servicesapcompam Search on Planning and Consolidation
Table 4
Component Minimum Requirement
Operating System The requirements outlined below are for the following operating systems
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 11
Component Minimum Requirement
Windows Server 2008 (64-bit) Standard Enterprise or Data Center with or withoutHyper-V
Windows Server 2008 R2 (64-bit) Foundation Standard Enterprise or DataCenter with or without Hyper-V
Windows Server 2012 (64-bit) Standard Data Center
Windows Server 2012 R2 (64-bit) Standard Data Center
NoteThe operating system must be configured with NTFS
Relational Database Microsoft SQL Server 2008 Enterprise Edition
Microsoft SQL Server 2008 R2 (Gemini) Enterprise Edition
Microsoft SQL Server 2012 Enterprise Edition
OLAP Database Microsoft SQL Server 2008 Enterprise Edition ndash Analysis Server
Microsoft SQL Server 2008 R2 Enterprise Edition ndash Analysis Server
Microsoft SQL Server 2012 Enterprise Edition ndash Analysis Server
Data Integration Microsoft SQL Server 2008 Enterprise Edition ndash SQL Service Integration Services
Microsoft SQL Server 2008 R2 Enterprise Edition ndash SQL Service IntegrationServices
Microsoft SQL Server 2012 Enterprise Edition ndash 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
NET 35 and NET 45 are required for Windows 2012 and 2012 R2
NET 40 is required for all other operating systems
IIS
IIS 75 or IIS 70
(Included in your Operating System IIS 75 is required for Windows 2008 R2editions)
IIS 80 or IIS 85
(Included in your Operating System IIS 85 is required for Windows 2012 R2editions)
Anti-Cross Site Scripting Library 42
This component must be downloaded before installing the server The serverinstallation program asks for the path of each file and copies the files into theappropriate Planning and Consolidation path
Microsoft Visual C++ 2010 SP1 Redistributable Package (x64)
Microsoft Access Database Engine 2010 64bit
12
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
Component Minimum Requirement
VMWare ESX 3x or ESX 40
(Required only if a landscape deployment strategy using virtualizationtechnologies is planned)
NoteMSXML 40 SP2 ADOMDNET 100 and Microsoft Visual C++ 2010 SP1Redistributable Package (x64) are included with the installation program but notinstalled 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 values being returned withcalculated accounts For more information see SAP Note number 1429246 which also contains downloadinformation
We recommend SQL Server 2008 (or R2) Enterprise Edition or SQL Server 2012 Enterprise Edition for theOLAP database to support proactive cache and cube partitioning It is technically possible to use SQL Server2008 (or R2) Standard Edition or SQL Server 2012 Standard Edition for data integration servers but we donot recommend this
23 Before Starting the Planning and Consolidation ServerInstallation
You must perform the following tasks before starting your Planning and Consolidation server installation
Install all the prerequisite software including all of the latest Microsoft hotfixes For more information seeInstalling the Prerequisites [page 17]
If you access your application through a firewall verify with your network administrator which TCP ports tochoose during the installation By default port 80 is the setting for standard http access and port 443 is thesetting for https access If you require a service to listen on a different port you can specify it during theinstallation 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 onwhich 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 Consolidationand automatically overwrites the previous version If you have made any modifications to EnvironmentShellthat 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 ScriptBlocking
If a version of Planning and Consolidation on a NetWeaver platform exists uninstall it before you install Planningand Consolidation 100 version for the Microsoft platform
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 13
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 enterconvert c fsntfsV
All servers in a multiserver environment must be members of the same domain
In a multiserver environment the installing ID must be a domain user ID We recommend that you do not logon to the servers using a local server user ID even if the user ID is a member of the Administrator group on theserver This way you have the proper authority to install software and to modify the Component Services SeeLogging On to Servers [page 14]
You must determine the IP addresses or server names for all servers before installing Planning andConsolidation 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 portaccess reasons (DMZ WORKGROUP or nontrusted domain authentication failures) do the following
1 Copy the EnvironmentShell database file ServerEnvironmentShelldb10 from the Planning andConsolidation 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 theEnvironmentShell database file in the Server Information Advanced Options Local path forEnvironmentShell DB field (for example cEnvironmentShelldb10)
Install the Anti-Cross Site Scripting Library which provides protection to Web-based applications againstCross-Site Scripting (XSS) attacks See Installing the Anti-Cross Site Scripting Library [page 23]
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 theAdministrator group of a domain to which the server belongs or a member of the Administrator group on the localserver
Errors may display during the installation program and in the diagnostic program if the installing user is not assignedto the Administrator group directly but is assigned to a group with Administrator rights You can ignore thesemessages
NoteIf you change the password used to install Planning and Consolidation you must change the password for theapplicable Planning and Consolidation service To do this go to Server Manager on the application server andselect Server Reset Logon Credentials For more information see the SAP Planning and ConsolidationOperations Guide in servicesapcominstguidesepm-bpc 100 for the Microsoft Platform SBOP Plan amp Consol100 MS Administrators Guide
14
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
25 Service-level Accounts
Service accounts are Windows domain IDs with access to all Planning and Consolidation servers with varying levelsof privileges They allow the software to use the minimum amount of privilege required for each job making it moresecure
You must define these user IDs on the Windows machine For security purposes they should not be used to definePlanning and Consolidation users
Prerequisites
Planning and Consolidation 100 has the following Windows services
BPC SendGovernor which manages Microsoft Analysis Service locks to ensure consistent performance andavoid deadlocks
BPC ServiceManager which manages the System Landscape Directory (SLD) service logging service andglobal caches
BPC CTS ServiceManager which listens and handles CTS import requests from the CTS+ transportmanagement system
Since these services should be able to access to the FileShare server an Admin account is assigned automaticallyto the service during the installation of the Planning and Consolidation server program Even though an Adminaccount 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 serviceon the local machine This logon right strictly applies only to the local computer and must be granted in the LocalSecurity Policy
To edit the Local Security Policy of the computer you want to define the logon as a service permission performthe 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 supportmicrosoftcomkb259733
Features
During the installation enter user IDs and passwords for the following user types
System Admin ID
This ID is read-only and is the same as the installation user ID that is the system displays the ID on theinstallation screen but you cannot modify it This ID allows access to code that provides system administrator-level functionality For example this ID can write to the Windows registry has full access to the FileShare server
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 15
and can create remove backup and restore OLAP and SQL databases The system administrator should be amember 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 createsubdirectory access on the FileShare server readwrite metadata and application set database data in OLAPand can create and remove tables in SQL The Administrator should be a member of the domain users groupand 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 theservers has write access to FileShare data and can read metadata and data in OLAP and SQL The User IDmust 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 isinstalled you can change these settings using the Server Manager
NoteWhen defining server names the name refers to the NetBIOS name IP address and fully qualified domain names(FQDN)
Standard Settings
Standard settings are typically used for a single-server environment The following table describes each setting
Table 5
Server Option Value Description
SQL Database server name The name of the SQL DB server
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 computername
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
Table 6
Server Option Value Description
SQL Server Name The name of the SQL DB server Defaults to the local server
Instance name The SQL instance name If left blank the default instance is used
16
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
Server Option Value Description
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 computername
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 forhttp and 443 is the default for https
Authentication type Note If you have chosen SAP BusinessObjects User Management System in theinstallation screen Authentication type does not appear in Advanced settings (asthat IIS authentication type is Anonymous in CMS mode)
Windows or Kerberos The default is Windows If you change this value fromWindows to Kerberos you must make some additional changes
See the Kerberos authentication settings section in the SAP Library ServerManager Guide on servicesapcominstguidesEPM-BPC 100 for theMicrosoft Platform
Scheduler Server Name The name of the server used for scheduling usually the application server forexample GMPV50072862B If you have multiple application servers select theappropriate one
NoteIf the primary server stops working you must manually configure yourapplication 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 theoperating system IIS SQL server analysis services ADOMDNET and MSXML This section provides guidance on
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 17
installing each component For specific versions required see Prerequisites [page 11] and the Product AvailabilityMatrix on the SAP Service Marketplace at servicesapcompam Search on Planning and Consolidation
NoteTo ensure a successful installation you must install the software in the order listed in this procedure
Check all third-party infrastructure services to ensure that they are functioning and that their authenticationmodels 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 itsown 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 applicationserver before you start the installation You can find the UMC installation package (UMCexe) on the Planningand Consolidation CD in a folder called UMC_100_INSTALLER When you run the installation package the wizardguides 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 andConsolidation)
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 multiserverconfiguration See Installing the Operating System [page 19]
3 Install the latest service pack for your operating system To install this service pack go towwwmicrosoftcom
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 SQLServer [page 19]
6 From your SQL Server media install Analysis Services Enterprise Edition and its required service packs and hotfixes See Installing Analysis Services [page 23]
7 On your application server install ADOMDNET The Planning and Consolidation zip file contains theADOMDNET 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 followinglocation BPC SetupServermsxmlmsi
18
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
9 On your application server install Microsoft Visual C++ 2010 SP1 Redistributable Package (x64)
The Microsoft Visual C++ 2010 SP1 Redistributable Package (x64) installation package is contained in thePlanning and Consolidation zip file at the following location BPC SetupServervcredist_x64exe
NoteThe version of vcredist_x64exe in BPC SetupServer has been updated to 10040219 If you have aprevious 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 wwwmicrosoftcomdownloadsendetailsaspxFamilyID=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 Marketplaceat servicesapcompam Search on Planning and Consolidation
Business Planning and Consolidation can support all servers with an operating system in any language
NoteCurrently Business Planning and Consolidation does not support an operating system in bi-directionallanguages such as Hebrew
Procedure
If you are installing IIS 70 75 80 or 85 you must enable the following features
Enable Basic Authentication and Windows Authentication these are not installed by default
Install IIS 6 Metabase Compatibility role
Business Planning and Consolidation uses the ADSI provider to handle IIS administration such as virtualdirectory and security but IIS 7 does not install the ADSI provider by default
273 Installing the SQL Server
Prerequisites
During the installation procedure you have the opportunity to specify the location of the EnvironmentShell databasefile Check that it is possible to access EnvironmentShell from the location where you intend to install the SQL serverIf it is not possible for port access reasons (DMZ WORKGROUP or nontrusted domain authentication failures) copyEnvironmentShell to a location on the SQL server (for example CEnvironmentShelldb10) You specify thislocation on the Server Information page by choosing Server Information Advanced Options Local Path forEnvironmentShell DB
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 19
Procedure
This section describes the general steps for installing the SQL Server component options and considerations wheninstalling 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
NoteIf you encounter a 500 HTTP Error when trying to connect to the Planning and Consolidation Web Client referto Microsoft Support articles 2520479 and 2468871 for assistance
To reinforce security we recommend that you install the SQL server and SSAS components to a nondefaultinstance 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 Optionssection below then choose Next
4 Review disc space requirements then choose Next
5 In Server Configuration Perform the following actions
1 In the Service Accounts tab enter a Planning and Consolidation sysadmin account for the SQL ServerDatabase Engine and the SQL Server Analysis services This is required so that the Planning andConsolidation sysadmin can create and process the Planning and Consolidation database because theMicrosoft SQL server tries to back up or restore database with the privileged account This account is alsorequired 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 differentdomain 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 theapplication server and the account requires the folder access privilege for the application server
To ensure that you have the complete access privileges we recommend the Planning and Consolidationsysadmin 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 touse a restrictive SQL ID that works with the drill-through feature If you must restrict SQL authentication forsecurity 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 installationprogram
20
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
8 Choose Install to begin the installation with the options you have set
SQL Server Component Options
For Single-Machine Installations
Install the following components from the Feature Selection screen
Database Engine Services
Analysis Services
Integration Service which is listed as one of the Shared Features
For Multiple Machine Installations
For multiple machine installations install the following components on each server
Table 7
Server Component What to Install
SQL Server Database Engine Services
SSAS Server Analysis Services
Application Server The following Shared Features
Client Tools Connectivity
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 Server2008 R2 and SQL Server 2012
Process Dimension
It is now possible to process a dimension with multiple selections At processing time the process dimension modulemakes changed or added information for each dimension and process for all selected dimensions and cubes inparallel
Optimize Model
If there are custom partitions for a FACT partition in the OLAP database an optimization module can process custompartitions in parallel when Full or Incremental Optimize is performed However if a full optimize is performed withthe 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 parallelbecause 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 applicationserver and application set databases
NoteSetting the SQL isolation level to be Read Committed Snapshot mode for a database can only be done once andcannot be reversed
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 21
Real Time MOLAP
You can set the OLAP storage model of the write-back partition to be MOLAP (Multidimensional OLAP) This settingremains 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 asfollows
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 Servertrade20052008 which you can download from wwwmicrosoftcom (search on ldquoTable Partitioningrdquo to find all relevantarticles)
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 Thebrowser 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 localhostand external network interface machine
3 If you want to use IP1 which indicates Server IP set Enabled to Yes and specify the TCP Port as desired
4 Delete 0 from TCP Dynamic Ports Set IPAll - TCP Ports as desired (for example 1533)
RecommendationWe do not recommend using dynamic ports
In an SQL server the default instance has a listener which listens on a fixed port (TCP port 1433)However for the named instance the port on which the SQL server listens is random and dynamicallyselected when the named instance of the SQL server starts This recommendation prevents any conflictproblems
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 Setthe 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 thatthe user identified as the Log on as user has the sysadmin SQL Server role defined under Server Roles in theSQL Server Management Studio This is required so Analysis Services can process the SQL Server
From SQL Server Management Studio do the following tasks
22
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
1 If you want to use a port with a named instance select the server type Analysis Services select the servername (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 ServerProperties window displays which shows all configurable properties
3 For enhanced security change the default value to your port number (for example 2724) This means thatyou use a fixed port as for the SQL Server option Then choose OK
NoteWe do not support a nondefault port with the default instance in this release If you want to use the defaultinstance do not change the port number
Restart SQL and OLAP
Confirm that the installation has completed successfully by checking that there are no installation relatedproblems on the event viewer You can now install Planning and Consolidation
274 Installing Analysis Services
Procedure
After you install SQL Server and its required service packs and hotfixes you must install SQL Server Analysis Servicesand its required service packs and hotfixes
NoteIf you have migrated your Analysis Services repository to the SQL Server back up the database that contains therepository before installing this release
To install Analysis Services for SQL Server 2008 SQL Server 2008 R2 or SQL Server 2012 follow the steps andguidelines in technetmicrosoftcomen-uslibraryms143219aspx
To avoid slow performance when a user has more than six OLAP databases follow the steps and guidelines in thePerformance Guide for SQL 2008 at wwwmicrosoftcomdownloadsdetailsaspxFamilyID=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 tohave it available for the Planning and Consolidation installation program
1 Download the Anti-Cross Site Scripting Library file AntiXSSLibraryDLL from the Microsoft Web site atwwwmicrosoftcomdownloadendetailsaspxid=28589
2 Save the extracted file locally
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 23
When you install Planning and Consolidation Server a step in the process requires you to identify the path toAntiXssLibrarydll
28 Installing on a Single Server
When you install all Planning and Consolidation server components on a single server you should consider thefollowing 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 theuncompressed 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 Log on to the server with a local server user ID or domain user ID For more information see Logging on toservers [page 14]
3 Make sure all prerequisite software is installed on the server For more information see Installing thePrerequisites [page 17]
4 Obtain SAP Planning and Consolidation archive from the Downloads SAP Installations amp Upgrades areaof SAP Service Marketplace
5 Extract the files from the archive Go to the BPC Setup folder and run the StartUpexe file
6 From the Server Install screen select Install the Planning and Consolidation server
7 From the Welcome screen choose Next
8 From the License Agreement page choose I accept the terms of the license agreement then choose Next
9 From the Installation Method page accept the default Single machine enter a system ID for the systemlandscape directory (SLD) and choose Next
NoteEntering a system ID of the SLD is only required if you have a SAP Solution Manager license If you do nothave a SAP Solution Manager license you can leave this field empty
10 From the Authentication Method page choose the desired authentication method and choose Next
11 If you have chosen SAP BusinessObjects User Management System in the previous screen on the CMSAuthentication page enter the information required to log on to CMS as an administrator
The following information is required
24
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
Table 8
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 Thisgroup name is filtered as the default when adding a user in Planning andConsolidation Administration Use a comma ( ) to separate multiple names
12 After entering the CMS administrator authentication details choose Next
13 From the Service type accounts page enter service-level account user IDs and passwords See Service-LevelAccounts [page 15]
14 After defining the IDs and passwords choose Next
15 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 chooseNext
16 Specify the location and name of AntiXssLibrarydll See Installing the Anti-Cross Site ScriptingLibrary [page 23]
Choose Next
17 Select destination folders for Programs and Data The Data files include Webfolders and FileDB (publishedreports) and should be installed on a separate drive in a production environment This recommendation reducesthe hard disk IO time and helps to speed up SQL commands
Accept the defaults or make your selections then choose Next
18 Select the default values for the Web client The values are used to determine the default language and regionfor the Web client when you connect to it You can change the values in the Planning and Consolidation ServerManager
19 The installation process takes a few moments When it is complete choose Exit
20 A prompt is displayed to restart your computer Select OK to restart
21 Perform the steps in After Installing Planning and Consolidation Servers [page 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 avariety of ways and configure the servers as a Network Load Balancing (NLB) environment
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 25
The recommended Planning and Consolidation practice is to assign resources using a round robin approach for loadbalancing
You can install the SQL OLAP and FileShare types remotely from the application server You need to performadditional server installations if you have multiple application servers
Installing each Planning and Consolidation application server in a multiserver (NLB) configuration is identical to theprocedure 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 Balancingenvironment With this option there is an additional choice to Include sample environment (required on only oneof the application servers) This is because when you install the application server it connects to the databaseserver and creates the sample environment (EnvironmentShell) Installing the sample environment is requiredon 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
26
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
3 After Installing Planning and ConsolidationServers
31 Post-Installation Steps
Procedure
Perform these steps after installing the Planning and Consolidation servers for new installations of Planning andConsolidation
1 Connect your Planning and Consolidation system to Solution Manager Diagnostics (SMD) to allow support staffto identify analyze and resolve problems with your application See Connecting to Solution ManagerDiagnostics [page 28]
2 Configure the Planning and Consolidation NET and application server to ensure that it and its related servicesfunction properly and reliably For more information see Configuring the Planning and Consolidation NETApplication Server [page 29]
3 Optional configuration steps [page 29]
1 To ensure proper functioning of the Management Console create an SQL user and modify the System DSNand 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 loggingfor ODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default WebSite [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory canaccess the Management Console with whatever rights they have been granted on the server Forinformation about removing default access and creating a group that can access the console see RemovingDefault Access to the Console [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommendthat you only grant Management Console access to system administrators Planning and Consolidationusers should not have any access For more information see Management Console AccessControl [page 33]
6 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
4 Take the following steps to set up security
If you are defining security and application structure continue with step 5
If you want to designate someone other than the system administrator to manage security and applicationstructure log on to EnvironmentShell designate a user as a Primary Administrator
This user must have Administration ndash Environment and Security ‒ Define User task rights so that he or shecan 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 SeeInstalling the Administration Client [page 37]
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 27
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 taskprofiles 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 mustcomplete this step since there is no access to dimensions or members)
NoteTo allow users to request and query large amounts of data you can edit the metabasexml file located at CWindowssystem32inetsrv Set the following parameters to the stated values
ASPBUFFERINGLIMIT = 10485760
MAXREQUESTENTITYALLOWED = 10485760
32 Connecting to Solution Manager Diagnostics
NoteYou only need to perform the steps in this section if you have a SAP Solution Manager licence
The diagnostics functions in SAP Solution Manager allow identification analysis and resolution of problems Thisprocedure 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 areinstalled
NoteInstallation files for Diagnostics Agent are available on Service Marketplace by navigating to SupportPackages and Patches mdash Entry by Application Group SAP Technology Components SAP SOLUTIONMANAGER SAP SOLUTION MANAGER 70 EHP 1 Entry by Component Agents for managed systemsDIAGNOSTICS AGENT 711
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 whereMicrosoft 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
28
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
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 ServiceMarketplace at servicesapcom~sapidb011000358700000074392009E and follow the chapters that applyto Planning and Consolidation
33 Configuring the Planning and Consolidation NETApplication Servers
Procedure
Modifying machineconfig Files
To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock occurrences that wouldcause the application server to ldquosleeprdquo and not process anymore you can modify the machineconfig file whichresides in the WINDOWSMicrosoftNETFramework64v4030319Config directory
1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to specifywhether to automatically configure settings to achieve optimal performance based on the machineconfiguration You can set this attribute to True or False
For more information see msdnmicrosoftcomen-uslibrary7w2sway1aspx
2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the Planning andConsolidation application) or Machineconfig (for all applications including Planning and Consolidation) toensure the validationKey and decryptionKey keys have the same value on all application servers Thisway when the authentication cookie is checked the authentication ticket used on one server can still be validon another server
For more information and sample Visual Basic code for generating random key values seemsdnmicrosoftcomen-uslibraryms998288aspxpaght000007_webfarmdeploymentconsiderationsand msdnmicrosoftcomen-uslibraryms998310aspx
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 DSNand 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 forODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory can accessthe Management Console with whatever rights they have been granted on the server For information about
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 29
removing default access and creating a group that can access the console see Removing Default Access to theConsole [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommend thatyou only grant Management Console access to system administrators Planning and Consolidation users shouldnot have any access For more information see Management Console Access Control [page 33]
6 Configure the use of SSL in Planning and Consolidation See Configuring Planning and Consolidation to useSSL [page 34]
7 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
8 Configure Microsoft SQL Server Reporting Services to use SSL See Configuring MS SQL Server ReportingServices to use SSL [page 36]
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 databaserole 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 optionto use ODBC Logging Enter the following values
DSN is BPC_ManagementDSN Table is BPCLog The Microsoft SQL Server Username and Password
5 Restart IIS
NoteWithout these updates the Management Console does work but some functionality (specifically User Activityand Service Status) does not work as expected
Should you need to uninstall Planning and Consolidation we recommend that you reset the Active Log Formatfield in IIS to W3C Extended Log File Format
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
30
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
Prerequisites
ODBC logging has been configured according to the Microsoft Knowledge Base article 245243 How to configureODBC 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 inApplicationHostconfig as shown here
ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0logFormat=Custom gtUse 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-00AA006111E0appcmd 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 articlespecified in the Prerequisites section Configure these settings in the ltodbcLogginggt node underltsystemwebServergt
Exampleltlocation path=Default Web SitegtltsystemwebServergtltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog userName=Usernamepassword=mypassword gtltsystemwebServergtltlocationgt
Use the following AppCmds to configure these attributes for the default Web site
appcmd set config Default Web Site sectionodbcLogging dataSourceBPC_ManagementDSN commitappHostappcmd set config Default Web Site sectionodbcLogging tableNameBPCLog commitappHostappcmd set config Default Web Site sectionodbcLogging userNameUsername commitappHostappcmd set config Default Web Site sectionodbcLogging passwordmypassword commitappHost
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 31
NoteYou cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must use the SQL ServerODBC driver For more information see the Microsoft Knowledge Base article 931202 The requirements for usingthe ODBC logging feature in IIS
343 Setting Up an ODBC Data Source in Windows Server2008 2008 R2 2012 or 2012 R2
Procedure
This procedure describes how to set up an ODBC data source for the Management Console in Windows Server 20082008 R2 2012 or 2012 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
NoteIf you have chosen SAP BusinessObjects User Management System in the installation screen you do not needto remove or configure access because the Management Console service always runs with the System Admin IDaccount which is a member of the Administrators group
Procedure
To remove default access to the Management Console and create a group that does have access to the console usethe procedure described below
32
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
NoteCreate your Management Console administrative group either on the server that hosts the Management Consoleor 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
NoteAlternatively you can perform analogous steps in Active Directory
3 In the Groups context menu choose New Group
4 Enter data as required Click Create
5 In the Computer Management dialog box choose Services and Applications Internet InformationServices 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 objectand all child objects Include these with entries explicitly defined here checkbox
NoteThis step is a necessary precursor to the completion of this procedure
10 In the Security dialog box click Copy to ensure that the System group retains its privileges
11 Remove access to the Management Console from all groups that should not have it
12 Choose Authentication in the center pane then disable Windows authentication
Result
Users who have not been granted access to the Management Console can still open the Management Console Webpage but it contains no data or menu options This does not affect the access that a user would otherwise have toPlanning and Consolidation
345 Management Console Access Control
After establishing the Management Console group you can add users or groups to it For more information aboutcreating this group see Removing Default Access to the Console [page 32] Their rights in Active Directory determinewhat they can access in the Console
By default any member of the Administrators Active Directory group on the application server or domain has fullaccess to all of the features of the Console except the Planning and Consolidation logging area Access to Planningand Consolidation logging is controlled within the Planning and Consolidation Administration Client task securityThe user must be granted View system logs task privileges For more information see the SAP Library Planning and
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 33
Consolidation Administrators Guide in servicesapcominstguidesepm-bpc 100 version for the Microsoftplatform
Your IT policy determines whether you grant access by group or user You may wish to create several levels of Consoleusers (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 describedin this table
Table 9
Privilege Rights Management Area
Task Manager and Kill Process Administrators group on application server or domain
Performance Monitor Counters Administrators group on application server or domain
Power Users group on application server or domain
Performance Monitor Users group on application server
Microsoft Analysis Services performance monitoring Administrators group on application server or domain
Microsoft SQL Server Monitoring (performance counters andstatistics)
Administrators group on application server or domain
346 Configuring Planning and Consolidation to use SSL
Procedure
Creating a Certificate for the Server
During the handshake phase of the SSL communication the server must send its certificate to the client The clientthen uses the certificate to encrypt information and send it back to the server
The procedure below describes how to create a self-signed certificate for the server
RecommendationWe recommend that you limit the use of self-signed certificates to testing only For a productive system you shouldobtain a certificate signed by a well-known certification authority (CA)
1 Start the Internet Information Services (IIS) Manager To do that go to Start All Programs AdministrativeTools Internet Information Services (IIS) Manager
2 In the Connections panel on the left-hand side select the server node and then choose Server Certificates
3 In the Actions panel on the right hand side choose the Create Self-Signed Certificate action
4 Enter the name that you want the certificate to be identified by for example MyTestSSLCertificate
IIS generates a new SSL certificate for you that has one yearrsquos expiry lease The certificate is issued to the local servername
Binding the Certificate to the Web Site
The procedure below describes how to bind the certificate to the web site for which SSL connections must be used
1 In the Connections panel select the web site node
2 In the Actions panel choose Bindings
34
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
3 In the Site Bindings dialog that appears choose the Add button to create a new binding
4 Configure the parameters as follows
Type = https IP Address = [1] - this is a shorthand expression for the local server name
Port = 443 - this is the default SSL port
SSL Certificate = enter your newly created certificate name
5 Choose OK to create the new binding and then close the Site Bindings dialog
6 Restart the IIS processes To do this choose Restart from the Actions panel
7 In the middle panel under the IIS section choose SSL Settings
8 In the SSL Settings screen select the Require SSL checkbox
9 In the Actions panel choose to Apply these settings
To test the SSL connection in the Actions panel choose the Browse [1] 443 (https) link
347 Using Client Certificates
To enable the use of client certificates in Planning and Consolidation you must follow several manual steps
NotePlanning and Consolidation supports client certificate authentication in Windows Authentication Mode butdoes 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 technetmicrosoftcomen-uslibrarycc753810aspx
For more information about configuring the client certificate mapping authentication see technetmicrosoftcomen-uslibrarycc732996(WS10)aspx
When you create the client certificates you can set the type of certificate in the SSL Settings screen in InternetInformation Services (IIS) Manager
Procedure
1 Set the options for client certificates
1 In the IIS Manager select the web site where you installed Planning and Consolidation
2 Choose SSL Settings
3 In the Client certificates section select the Accept client certificates option
This option allows you to use a client certificate or username and password (Basic authentication) toconnect 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 theManagementConsole home page
3 Double-click Authentication and enable Anonymous Authentication
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 35
4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way asin step 3
5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the sameway 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
348 Configuring MS SQL Server Reporting Services to useSSL
Procedure
The procedure below describes how to configure the use of SSL in Microsoft SQL Server Reporting Services
NoteReporting Services does not provide functionalities for generating requesting or installing a certificate Theserver certificates that you want to use for configuring SSL must have already been installed on your computer
1 Open the Reporting Services Configuration Manager program To do this open the Windows Start menu andnavigate to All Programs Microsoft SQL Server ltversiongt Configuration Tools Reporting ServicesConfiguration Manager
2 In the Connect panel on the left-hand side select the Web Service URL option to open all the Report Server webservice parameters
3 Configure the parameters as follows
SSL Certificate = the name of the certificate that you want to use
SSL Port = 4434 Choose Apply to confirm the changes
5 In the Connect panel choose Report Manager URL to open the list of parameters that link Reporting Servicesto IIS
6 Choose Advanced to add your new SSL web URL
7 In the section Multiple SSL Identities for Report Manager choose Add Configure the parameters as follows
IP Address = (All IPv4) SSL Port = 443 Certificate = the name of your SSL certificate
8 To test the configuration click the URL that appears under the Report manager Site Identification section
36
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
4 Installing Planning and ConsolidationAdministration Client and the SAPBusinessObjects EPM solutions Add-in forMicrosoft Office
The installation of the Planning and Consolidation Administration Client allows administrators to build and maintainPlanning and Consolidation environments and models and administer security
All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions add-in forMicrosoft 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 valueof the Planning and Consolidation client to prompt for user name and password Otherwise the Planning andConsolidation Start Page does not display
41 Installing the Administration Client
Prerequisites
NoteFor a definitive list of system requirements see the Product Availability Matrix on SAP Service Marketplace atservicesapcompam Search on Planning and Consolidation
The following list describes the minimum software requirements
Microsoft Internet Explorer 70 80 90 or 10
Microsoft Office 2003 2007 2010 or 2012
NET Framework 20 or higher (install any required NET Framework Hotfixes by referring tosupportmicrosoftcomkb)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 37
NoteWe recommend that you install all of the latest Microsoft Windows hotfixes prior to installing the Administrationclient For information about which hotfixes to install see updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us
Procedure
The 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 ltPC_serverportgtsapbpcweb
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 mustdownload the most recent version of the full setup (EPM Add-inexe) from the Service Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPCInstallation folder
Individual users can install the EPM add-in on their own machines by going to the Planning and Consolidation Homepage 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 upthe 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
38
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
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 toperform the upgrade If Client Auto Update is not enabled and a newer version is detected clients must be installedmanually 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 andpassword in the Admin ID and Admin password fields respectively The Admin ID should be a member of thelocal administrators group on all the computers running the auto update This setting is not needed if all usershave 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 Thisoption is stored in the user preferences and may also be turned on or off using the User Optionshellip menu itemIf 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 toinstall 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 installit 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 servicesapcom
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 versionand policy information For a support package these files are
EPM Addin Support Package ltSP versiongtmsp EPM Addin Support Package ltSP versiongtxmlFor a patch these files are
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 (WebsrvrWebBPCInstallation)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 39
You can set a different update policy for each package listed
ExampleThe following table illustrates some possible situations assuming that you have installed the first full version(V1)
Table 10
Available maintenancepackages
V2-user update
V3-force update
V4-force update
V5-user update
V5-user update V5-user update
V6-auto update
V7-force update
Minimum RequiredVersion
V4 V4 V7
Notification A prompt tells the user toinstall maintenancepackage V4 using theForced Update behavior
If User Update is enabledthe prompt informs theuser that maintenancepackage V5 is available
A prompt tells the user toinstall maintenancepackage V7 using theForced Update behavior
New Version V4 V4 or V5 V7
If you change the update policy for any package click Update to complete the change
40
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
5 Connection Issues
You may experience connection problems with ports the proxy server or programs and settings that interact withthese components If you have any issues related to connection review the following recommendations andtroubleshooting tips
51 Checking for Open Ports
You must ensure that all required ports are open for inboundoutbound traffic By default Planning andConsolidation requires that Ports 80 (used by http) and 1433 and 2383 (used by SQL Server 2008) are open Totest whether the required ports are open go to a command prompt and enter the Telnet serveripaddress and portFor example Telnet 431181836 80 If the system returns a blank command window the port is open If it returnsa message stating that it is unable to connect the port is not open
NoteYou can use the following site to scan for the normal ports It allows you to manually enter a port number to test
wwwmyserverorgportsniffasp
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 Planningand Consolidation server as an exception You can do this at the client level ( Internet Explorer ToolsInternet 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 fullyqualified 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 Consolidationauthentication Do not use authentication on the proxy server The system synchronizes the user name andpassword on the remote server with the local user name and password
SAP Business Planning and Consolidation 100Connection Issues
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 41
NoteFor more information about setting up an ISA proxy server contact SAP Support to request a copy of Setting upISA Proxy Server White Paper For more information about Business Planning and Consolidation firewall portssee SAP Note 1505250
Internet Explorer Settings Issues
Internet Explorer settings must be set correctly to prevent errors and problems when you attempt to access thePlanning 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 insertthe IP address or fully qualified server name of the Planning and Consolidation server as an exception bychoosing 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
42
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Connection Issues
6 Installing Planning and Consolidation withTwo Active Directory Domains
To set up a Planning and Consolidation 10 application server in a hosted environment and use your own domainusers follow this procedure In general you install Planning and Consolidation on the host domain use the hostdomain account and assign it to the Planning and Consolidation users SysAdmin Admin and Users Then you acceptone 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 andpassword 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 topromote 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 privilegefor the Planning and Consolidation server
5 Install Planning and Consolidation and assign your domain account either to the three Planning andConsolidation administrative users SysAdmin Admin and Users or to only one of the three Planning andConsolidation administrative users and to three of your users Be sure you use your own user account ratherthan host domain users
Planning and Consolidation impersonation can then access your domain from the host environment becauseit has the privilege of your domain account
SAP Business Planning and Consolidation 100Installing Planning and Consolidation with Two Active Directory Domains
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 43
7 Installing Planning and Consolidation in aTerminal Services or Citrix ServerDeployment
This section describes best practices and instructions for installing Planning and Consolidation in a Terminal Servicesor Citrix Server deployment
71 Terminal Services Home Directories
We recommend using Terminal Server home directories rather than using the userrsquos profile directory The profiledirectory downloads a minimal amount of information about the dimensions of the environment you are logging onto and may be as large as 2 MB per user The profile directory is on the system drive and has limited space Byspecifying 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 individualserver 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 clientserver (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
44
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
Procedure
The following steps outline how to install the Planning and Consolidation clients in a Terminal Services (TS) or CitrixServer deployment
1 Make sure the Terminal Services or Citrix Server machine has the system requirements installed
2 Log on to the Terminal Services or Citrix Server machine with a user ID that has the rights to install on thatserver
3 At a command prompt enter Change userinstall
4 Open a browser and connect to the URL ltPC_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_MSBPCAdminMainexe
74 Creating a Shortcut to the Launch Page
Procedure
If you use published desktops instead of published applications the Planning and Consolidation desktop file (whichis installed on the current userrsquos desktop) must be moved to the All UsersDesktop folder
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 45
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 SQLServer 2012 support the remote modification of SSIS packages Planning and Consolidation also supports theremote 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 whichyou want to modify SSIS packages
These custom tasks reference dlls that connect to the database server and perform certain validation when usersset up the parameters of each task All the custom task reference components must also be installed in the machineon which you want to modify SSIS packages
We provide a program that registers all the reference components of the custom tasks This section explains theinstallation 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 ndash This folder contains all the dlls that should be installed on the machine There are Planning andConsolidation platform components and all of the Data Manager custom task files
Config folder ndash This folder contains only one file named Filelistxml and lists all of the files that should be installedIf you need to add or remove certain components from the installation you can modify this xml file
OSoftSetupexe ndash This is the main executable file to run the installation package
NoteIf you are not installing SSIS Custom Tasks on your client machine ndash specifically a machine other than the Planningand Consolidation application server ndash you must first install OSoftSSIS2008_Client or OSoftSSIS2012_Client onthe client machine followed by the SQL Server version If you want to use SQL 2008 Tasks under the SQL 2012environment you must install OSoftSSIS2008_Client on the application server For detailed information see SAPNote 1707410 You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package byextracting OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPCInstallation folder on the Planning and Consolidation server To modify SSIS packages on the Planning andConsolidation application server you need to install OSoftSSIS2008_Client or OSoftSSIS2012_Client for creatinga COM+ application For more information see Before You Modify the SSIS Packages [page 49] and Setup ofa COM+ Application on the Application Server [page 50]
Bin folder
This folder contains the following components
46
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Table 11
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012respectively
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
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 47
Name Remark
BPCWriteBackdll
InteropDTSdll
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 addmore components to the installation package you can copy the new components into the Bin folder and add theproper xml tags in FileListxml You need to enter information for the following tags
RegistType ndash This is the registration information of the component You can enter the following values
RegAsm ndash For NET component
48
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Regsvr32 ndash For VB6 component
Gacutil ndash For NET Framework component that should be registered into Global Assembly Cache
FileName ndash Component file name
OSoftSetupexe
This is the executable file to run the SSIS installation package Double-click the file to start the installation You needto enter information for the following fields
Set SQL server
Specify the SQL server name If your SQL Server has an instance specify the instance name
NoteIf you installed the OSoftSSIS2008_Client or OSoftSSIS2012_Client on the application server the SQL servername is automatically disabled
Set server credential
This is the credential name of the COM+ package component Enter the user ID and password that can accessyour SQL Server This should be either the System Admin ID or Admin ID that was registered as a COM+ userwhen 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 ifyou 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 packagesremotely This is also true for the application server that has SSIS installed The Planning and ConsolidationData Manager has the following custom tasks
Table 12
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008and 2012 respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and2012 respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012respectively
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 49
Name Remark
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and2012 respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008and 2012 respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL2008 and 2012 respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and2012 respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012respectively
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
ltdrivegtWebsrvrbin2 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 FilesMicrosoft SQLServer paste all files into the CProgram Files (x86)Microsoft SQL Server100DTSTasksfolder
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
50
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Typographic Conventions
Table 13
Example Description
lt gt Angle brackets indicate that you replace these words or characters with appropriate entries tomake entries in the system for example Enter your ltUser Namegt
File Save Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
Example Textual cross-references to an internet address for example wwwsapcom
example Quicklinks added to the internet address of a homepage to enable quick access to specificcontent 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 titlespushbutton 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 namesof installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transactioncodes database table names and key concepts of a programming language when they aresurrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
SAP Business Planning and Consolidation 100Typographic Conventions
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 51
52
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
wwwsapcom
Material Number
- SAP Business 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 2008 R2 2012 or 2012 R2
- 344 Removing Default Access to the Console
- 345 Management Console Access Control
- 346 Configuring Planning and Consolidation to use SSL
- 347 Using Client Certificates
- 348 Configuring MS SQL Server Reporting Services to use SSL
-
- 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
-
copy Copyright 2014 SAP AG or an SAP affiliate company Alle Rechte vorbehalten All rights reserved Tous droitsreacuteserveacutes Все права защищены
Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcherForm auch immer ohne die ausdruumlckliche schriftliche Genehmigung durch SAP AG nicht gestattet In dieserPublikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werden
Weitergabe und Vervielfaumlltigung dieser Publikation oder von Teilen daraus sind zu welchem Zweck und in welcherForm auch immer ohne die ausdruumlckliche schriftliche Genehmigung durch SAP AG nicht gestattet In dieserPublikation enthaltene Informationen koumlnnen ohne vorherige Ankuumlndigung geaumlndert werden
No part of this publication may be reproduced or transmitted in any form or for any purpose without the expresspermission of SAP AG The information contained herein may be changed without prior notice
Microsoft Windows Outlook and PowerPoint are registered trademarks of Microsoft Corporation
IBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400iSeries pSeries xSeries zSeries System i System i5 System p System p5 System x System z System z9 zOSAFP Intelligent Miner WebSphere Netfinity Tivoli Informix i5OS POWER POWER5 POWER5+ OpenPower andPowerPC are trademarks or registered trademarks of IBM Corporation
Adobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of AdobeSystems Incorporated in the United States andor other countries
Oracle is a registered trademark of Oracle Corporation
UNIX XOpen OSF1 and Motif are registered trademarks of the Open Group
Citrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems Inc
HTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of Technology
Java is a registered trademark of Sun Microsystems Inc
JavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented andimplemented by Netscape
MaxDB is a trademark of MySQL AB Sweden
SAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentionedherein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in severalother countries all over the world All other product and service names mentioned are the trademarks of theirrespective companies Data contained in this document serves informational purposes only National productspecifications may vary
These materials are subject to change without notice These materials are provided by SAP AG and its affiliatedcompanies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAPGroup shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Groupproducts and services are those that are set forth in the express warranty statements accompanying such productsand services if any Nothing herein should be construed as constituting an additional warranty
Some components of this product are based on Javatrade Any code change in these components may causeunpredictable and severe malfunctions and is therefore expressively prohibited as is any decompilation of thesecomponents
Any Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not bemodified or altered in any way
2
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
Documentation on the SAP Service Marketplace
You can find this document at the following address servicesapcominstguidesEPM-BPC
SAP Business Planning and Consolidation 100Documentation on the SAP Service Marketplace
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 3
Document History
The following table provides an overview of the most important document changes
Table 1
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 SingleServerrdquo
Added 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 recommendationto 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 recommendinstalling Microsoft Office on the application server Also removed the note at the end of theprocedure that discussed launching the installation of a Microsoft ACE OLEDB Provider on amachine 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 andConsolidation NET Application Serversrdquo
137 2012-06-13 Updated NET 20 to NET 40 in the topic ldquoConfiguring the Planning and Consolidation NETApplication Serversrdquo
138 2012-10-17 Improved the installation procedure in the topic ldquoInstalling on a Single Serverrdquo
139 2012-12-05 Changes in the topics ldquoPrerequisitesrdquo and ldquoInstalling the Prerequisites ndash Basic Stepsrdquo mdashupdated the required version of Microsoft Visual C++ and vcredist_x64exe
14 2013-04-30 Updated the topic Installing the Administration Client [page 37] with versions of MicrosoftInternet Explorer and Microsoft Office supported as of support package 10
15 2013-09-09 Updated the topic ldquoSAP Notes for the Installationrdquo with the central note number for supportpackage 11
16 2013-10-17 Updated the topic Proxy Server and Firewall Issues [page 41] with a note to refer to SAP Note1505250 for information about firewall ports
165 2014-01-10 Updated the topic ldquoSAP Notes for the Installationrdquo with the central note number for supportpackage 12
17 2014-04-02 Added topics about configuring SSL in IIS and in SQL Server Reporting Services
18 2014-08-08 For support package 14
4
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Document History
Version Date Description
Updated the topic ldquoImportant SAP Notesrdquo with the central note number for supportpackage 14
In the topic Prerequisites [page 11] added Windows 2012 to the list of possibleoperating systems and added IIS 80 IIS 85 NET 35 and NET 45 to OtherRequirements
Updated the topic Setting Up an ODBC Data Source in Windows Server 2008 2008R2 [page 32] to include Windows 2012
SAP Business Planning and Consolidation 100Document History
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 5
Content
1 Introduction 911 SAP Notes for the Installation 912 Naming Conventions 10
2 Installing Planning and Consolidation Servers 1121 Basic Steps 1122 Prerequisites 1123 Before Starting the Planning and Consolidation Server Installation 1324 Logging on to Servers 1425 Service-level Accounts 1526 Standard and Advanced Settings 1627 Installing the Prerequisites 17
Installing the Prerequisites ndash Basic Steps 17 Installing the Operating System 19 Installing the SQL Server 19 Installing Analysis Services 23 Installing the Anti-Cross Site Scripting Library 23
28 Installing on a Single Server 2429 Installing the Server in a Multiserver Configuration 25
3 After Installing Planning and Consolidation Servers 2731 Post-Installation Steps 2732 Connecting to Solution Manager Diagnostics 2833 Configuring the Planning and Consolidation NET Application Servers 2934 Post-Installation Optional Configuration Steps 29
Enabling the Management Console 30 Setting Up ODBC Logging in IIS for the Default Web Site 30 Setting Up an ODBC Data Source in Windows Server 2008 2008 R2 2012 or 2012
R2 32 Removing Default Access to the Console 32 Management Console Access Control 33 Configuring Planning and Consolidation to use SSL 34 Using Client Certificates 35 Configuring MS SQL Server Reporting Services to use SSL 36
4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjectsEPM solutions Add-in for Microsoft Office 37
41 Installing the Administration Client 3742 Installing the EPM Add-in 3843 Using the Client Auto Update Program 38
5 Connection Issues 4151 Checking for Open Ports 4152 Proxy Server and Firewall Issues 41
6
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Content
6 Installing Planning and Consolidation with Two Active Directory Domains 43
7 Installing Planning and Consolidation in a Terminal Services or Citrix ServerDeployment 44
71 Terminal Services Home Directories 4472 System Requirements 4473 Installing Planning and Consolidation 4474 Creating a Shortcut to the Launch Page 45
8 Installing SSIS Custom Tasks 4681 Composition of SSIS Custom Task Installation 4682 Before You Modify the SSIS Packages 4983 Setup of a COM+ Application on the Application Server 50
SAP Business Planning and Consolidation 100Content
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 7
8
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
1 Introduction
The SAP BusinessObjects Planning and Consolidation Installation Guide is intended for System Administrators whoperform Planning and Consolidation server and Administration client installations It contains everything you needto 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 releasewe provide detailed instructions on how to migrate your existing environments For more information see theUpgrade Guide which is available on SAP Service Marketplace at servicesapcominstguidesEPM-BPC Planningand Consolidation 100 version for the Microsoft platform
For more information about the Planning and Consolidation Office client software see the SAP BusinessObjects EPMsolutions 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 FileOLAP 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 2008or Windows Server 2008 R2 for remote desktop access
Planning and Consolidation no longer requires a separate Web server only an application server You can installthe application server on a single machine or on multiple machines with network load balancing (NLB) If youuse 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 informationon the installation as well as corrections to the installation documentation Make sure that you have the up-to-dateversion of each SAP Note which you can find in the SAP Service Marketplace at the Internet addressservicesapcomnotes
Table 2
SAP Note Number Title Comments
1584890 Documentation Addendum Contains information that does not yet appear in theapplication help of Business Planning and Consolidation100 version for the Microsoft platform Application helpis available at helpsapcombopacms100
2000499 Business Planning amp Consolidation 10 forMicrosoft SP14 Central Note
This note contains important information about theinstallation of support package 14
SAP Business Planning and Consolidation 100Introduction
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 9
SAP Note Number Title Comments
1961655 Business Planning amp Consolidation 10 forMicrosoft SP13 Central Note
This note contains important information about theinstallation of support package 13
1897745 Business Planning amp Consolidation 10 forMicrosoft SP12 Central Note
This note contains important information about theinstallation of support package 12
1846917 Business Planning amp Consolidation 10 forMicrosoft SP11 Central Note
This note contains important information about theinstallation of support package 11
1804918 Business Planning amp Consolidation 10 forMicrosoft SP10 Central Note
This note contains important information about theinstallation of support package 10
1755355 Business Planning amp Consolidation 10 forMicrosoft SP09 Central Note
This note contains important information about theinstallation of support package 9
1733053 Business Planning amp Consolidation 10 forMicrosoft SP08 Central Note
This note contains important information about theinstallation of support package 8
1689792 Business Planning amp Consolidation 10 forMicrosoft SP07 Central Note
This note contains important information about theinstallation of support package 7
1665656 Business Planning amp Consolidation 10 forMicrosoft SP06 Central Note
This note contains important information about theinstallation of support package 6
1643037 Business Planning amp Consolidation 10 forMicrosoft SP05 Central Note
This note contains important information about theinstallation of support package 5
1620464 Business Planning amp Consolidation 10 forMicrosoft SP04 Central Note
This note contains important information about theinstallation of support package 4
1601213 Business Planning amp Consolidation 10 forMicrosoft SP03 Central Note
This note contains important information about theinstallation of support package 3
1591848 Business Planning amp Consolidation 10 forMicrosoft SP02 Central Note
This note contains important information about theinstallation of support package 2
1573539 Business Planning amp Consolidation 10 forMicrosoft SP01 Central Note
This note contains important information about theinstallation of support package 1
12 Naming Conventions
In this document the following naming conventions apply
Table 3
Variable Description
ltPC_serverportgt Server name or IP address and port number of SAP Planningand Consolidation application location
ltdrivegt The drive where SAP Planning and Consolidation is installed
The default for this is CPC_MS
10
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Introduction
2 Installing Planning and ConsolidationServers
This section includes the basic steps for installing a Planning and Consolidation server the prerequisites and whatto 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 atservicesapcominstguidesepm-bpc 100 version for the Microsoft platform
2 Perform the tasks in the Before Starting the Planning and Consolidation Server Installation [page 13] sectionincluding installing all prerequisites
3 From the application server install the Planning and Consolidation server See Installing Planning andConsolidation on a Single Server [page 24]
NoteYou must install both Planning and Consolidation 100 as well as the most recent Planning and Consolidation100 Support Package available from the SAP Service Marketplace at servicesapcomswdc SoftwareDownloads Support Packages and Patches A - Z Index B SAP BPC FOR MICROSOFT SBOP PC 100FOR MICROSOFT Comprised Software Component Versions SAP CPM BPC 100 M Windows Server onx64 64bit
4 If you have multiple machines see Installing the Server in a Multiserver Configuration [page 25]
5 Perform the steps in the section After Installing Planning and Consolidation Servers [page 27]
22 Prerequisites
The following table describes the software you need to install before installing the Planning and Consolidation serverand the minimum versions required
NoteA list of the supported operating systems and database systems is also available in the Product Availability Matrixon SAP Service Marketplace at servicesapcompam Search on Planning and Consolidation
Table 4
Component Minimum Requirement
Operating System The requirements outlined below are for the following operating systems
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 11
Component Minimum Requirement
Windows Server 2008 (64-bit) Standard Enterprise or Data Center with or withoutHyper-V
Windows Server 2008 R2 (64-bit) Foundation Standard Enterprise or DataCenter with or without Hyper-V
Windows Server 2012 (64-bit) Standard Data Center
Windows Server 2012 R2 (64-bit) Standard Data Center
NoteThe operating system must be configured with NTFS
Relational Database Microsoft SQL Server 2008 Enterprise Edition
Microsoft SQL Server 2008 R2 (Gemini) Enterprise Edition
Microsoft SQL Server 2012 Enterprise Edition
OLAP Database Microsoft SQL Server 2008 Enterprise Edition ndash Analysis Server
Microsoft SQL Server 2008 R2 Enterprise Edition ndash Analysis Server
Microsoft SQL Server 2012 Enterprise Edition ndash Analysis Server
Data Integration Microsoft SQL Server 2008 Enterprise Edition ndash SQL Service Integration Services
Microsoft SQL Server 2008 R2 Enterprise Edition ndash SQL Service IntegrationServices
Microsoft SQL Server 2012 Enterprise Edition ndash 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
NET 35 and NET 45 are required for Windows 2012 and 2012 R2
NET 40 is required for all other operating systems
IIS
IIS 75 or IIS 70
(Included in your Operating System IIS 75 is required for Windows 2008 R2editions)
IIS 80 or IIS 85
(Included in your Operating System IIS 85 is required for Windows 2012 R2editions)
Anti-Cross Site Scripting Library 42
This component must be downloaded before installing the server The serverinstallation program asks for the path of each file and copies the files into theappropriate Planning and Consolidation path
Microsoft Visual C++ 2010 SP1 Redistributable Package (x64)
Microsoft Access Database Engine 2010 64bit
12
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
Component Minimum Requirement
VMWare ESX 3x or ESX 40
(Required only if a landscape deployment strategy using virtualizationtechnologies is planned)
NoteMSXML 40 SP2 ADOMDNET 100 and Microsoft Visual C++ 2010 SP1Redistributable Package (x64) are included with the installation program but notinstalled 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 values being returned withcalculated accounts For more information see SAP Note number 1429246 which also contains downloadinformation
We recommend SQL Server 2008 (or R2) Enterprise Edition or SQL Server 2012 Enterprise Edition for theOLAP database to support proactive cache and cube partitioning It is technically possible to use SQL Server2008 (or R2) Standard Edition or SQL Server 2012 Standard Edition for data integration servers but we donot recommend this
23 Before Starting the Planning and Consolidation ServerInstallation
You must perform the following tasks before starting your Planning and Consolidation server installation
Install all the prerequisite software including all of the latest Microsoft hotfixes For more information seeInstalling the Prerequisites [page 17]
If you access your application through a firewall verify with your network administrator which TCP ports tochoose during the installation By default port 80 is the setting for standard http access and port 443 is thesetting for https access If you require a service to listen on a different port you can specify it during theinstallation 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 onwhich 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 Consolidationand automatically overwrites the previous version If you have made any modifications to EnvironmentShellthat 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 ScriptBlocking
If a version of Planning and Consolidation on a NetWeaver platform exists uninstall it before you install Planningand Consolidation 100 version for the Microsoft platform
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 13
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 enterconvert c fsntfsV
All servers in a multiserver environment must be members of the same domain
In a multiserver environment the installing ID must be a domain user ID We recommend that you do not logon to the servers using a local server user ID even if the user ID is a member of the Administrator group on theserver This way you have the proper authority to install software and to modify the Component Services SeeLogging On to Servers [page 14]
You must determine the IP addresses or server names for all servers before installing Planning andConsolidation 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 portaccess reasons (DMZ WORKGROUP or nontrusted domain authentication failures) do the following
1 Copy the EnvironmentShell database file ServerEnvironmentShelldb10 from the Planning andConsolidation 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 theEnvironmentShell database file in the Server Information Advanced Options Local path forEnvironmentShell DB field (for example cEnvironmentShelldb10)
Install the Anti-Cross Site Scripting Library which provides protection to Web-based applications againstCross-Site Scripting (XSS) attacks See Installing the Anti-Cross Site Scripting Library [page 23]
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 theAdministrator group of a domain to which the server belongs or a member of the Administrator group on the localserver
Errors may display during the installation program and in the diagnostic program if the installing user is not assignedto the Administrator group directly but is assigned to a group with Administrator rights You can ignore thesemessages
NoteIf you change the password used to install Planning and Consolidation you must change the password for theapplicable Planning and Consolidation service To do this go to Server Manager on the application server andselect Server Reset Logon Credentials For more information see the SAP Planning and ConsolidationOperations Guide in servicesapcominstguidesepm-bpc 100 for the Microsoft Platform SBOP Plan amp Consol100 MS Administrators Guide
14
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
25 Service-level Accounts
Service accounts are Windows domain IDs with access to all Planning and Consolidation servers with varying levelsof privileges They allow the software to use the minimum amount of privilege required for each job making it moresecure
You must define these user IDs on the Windows machine For security purposes they should not be used to definePlanning and Consolidation users
Prerequisites
Planning and Consolidation 100 has the following Windows services
BPC SendGovernor which manages Microsoft Analysis Service locks to ensure consistent performance andavoid deadlocks
BPC ServiceManager which manages the System Landscape Directory (SLD) service logging service andglobal caches
BPC CTS ServiceManager which listens and handles CTS import requests from the CTS+ transportmanagement system
Since these services should be able to access to the FileShare server an Admin account is assigned automaticallyto the service during the installation of the Planning and Consolidation server program Even though an Adminaccount 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 serviceon the local machine This logon right strictly applies only to the local computer and must be granted in the LocalSecurity Policy
To edit the Local Security Policy of the computer you want to define the logon as a service permission performthe 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 supportmicrosoftcomkb259733
Features
During the installation enter user IDs and passwords for the following user types
System Admin ID
This ID is read-only and is the same as the installation user ID that is the system displays the ID on theinstallation screen but you cannot modify it This ID allows access to code that provides system administrator-level functionality For example this ID can write to the Windows registry has full access to the FileShare server
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 15
and can create remove backup and restore OLAP and SQL databases The system administrator should be amember 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 createsubdirectory access on the FileShare server readwrite metadata and application set database data in OLAPand can create and remove tables in SQL The Administrator should be a member of the domain users groupand 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 theservers has write access to FileShare data and can read metadata and data in OLAP and SQL The User IDmust 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 isinstalled you can change these settings using the Server Manager
NoteWhen defining server names the name refers to the NetBIOS name IP address and fully qualified domain names(FQDN)
Standard Settings
Standard settings are typically used for a single-server environment The following table describes each setting
Table 5
Server Option Value Description
SQL Database server name The name of the SQL DB server
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 computername
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
Table 6
Server Option Value Description
SQL Server Name The name of the SQL DB server Defaults to the local server
Instance name The SQL instance name If left blank the default instance is used
16
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
Server Option Value Description
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 computername
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 forhttp and 443 is the default for https
Authentication type Note If you have chosen SAP BusinessObjects User Management System in theinstallation screen Authentication type does not appear in Advanced settings (asthat IIS authentication type is Anonymous in CMS mode)
Windows or Kerberos The default is Windows If you change this value fromWindows to Kerberos you must make some additional changes
See the Kerberos authentication settings section in the SAP Library ServerManager Guide on servicesapcominstguidesEPM-BPC 100 for theMicrosoft Platform
Scheduler Server Name The name of the server used for scheduling usually the application server forexample GMPV50072862B If you have multiple application servers select theappropriate one
NoteIf the primary server stops working you must manually configure yourapplication 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 theoperating system IIS SQL server analysis services ADOMDNET and MSXML This section provides guidance on
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 17
installing each component For specific versions required see Prerequisites [page 11] and the Product AvailabilityMatrix on the SAP Service Marketplace at servicesapcompam Search on Planning and Consolidation
NoteTo ensure a successful installation you must install the software in the order listed in this procedure
Check all third-party infrastructure services to ensure that they are functioning and that their authenticationmodels 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 itsown 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 applicationserver before you start the installation You can find the UMC installation package (UMCexe) on the Planningand Consolidation CD in a folder called UMC_100_INSTALLER When you run the installation package the wizardguides 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 andConsolidation)
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 multiserverconfiguration See Installing the Operating System [page 19]
3 Install the latest service pack for your operating system To install this service pack go towwwmicrosoftcom
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 SQLServer [page 19]
6 From your SQL Server media install Analysis Services Enterprise Edition and its required service packs and hotfixes See Installing Analysis Services [page 23]
7 On your application server install ADOMDNET The Planning and Consolidation zip file contains theADOMDNET 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 followinglocation BPC SetupServermsxmlmsi
18
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
9 On your application server install Microsoft Visual C++ 2010 SP1 Redistributable Package (x64)
The Microsoft Visual C++ 2010 SP1 Redistributable Package (x64) installation package is contained in thePlanning and Consolidation zip file at the following location BPC SetupServervcredist_x64exe
NoteThe version of vcredist_x64exe in BPC SetupServer has been updated to 10040219 If you have aprevious 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 wwwmicrosoftcomdownloadsendetailsaspxFamilyID=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 Marketplaceat servicesapcompam Search on Planning and Consolidation
Business Planning and Consolidation can support all servers with an operating system in any language
NoteCurrently Business Planning and Consolidation does not support an operating system in bi-directionallanguages such as Hebrew
Procedure
If you are installing IIS 70 75 80 or 85 you must enable the following features
Enable Basic Authentication and Windows Authentication these are not installed by default
Install IIS 6 Metabase Compatibility role
Business Planning and Consolidation uses the ADSI provider to handle IIS administration such as virtualdirectory and security but IIS 7 does not install the ADSI provider by default
273 Installing the SQL Server
Prerequisites
During the installation procedure you have the opportunity to specify the location of the EnvironmentShell databasefile Check that it is possible to access EnvironmentShell from the location where you intend to install the SQL serverIf it is not possible for port access reasons (DMZ WORKGROUP or nontrusted domain authentication failures) copyEnvironmentShell to a location on the SQL server (for example CEnvironmentShelldb10) You specify thislocation on the Server Information page by choosing Server Information Advanced Options Local Path forEnvironmentShell DB
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 19
Procedure
This section describes the general steps for installing the SQL Server component options and considerations wheninstalling 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
NoteIf you encounter a 500 HTTP Error when trying to connect to the Planning and Consolidation Web Client referto Microsoft Support articles 2520479 and 2468871 for assistance
To reinforce security we recommend that you install the SQL server and SSAS components to a nondefaultinstance 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 Optionssection below then choose Next
4 Review disc space requirements then choose Next
5 In Server Configuration Perform the following actions
1 In the Service Accounts tab enter a Planning and Consolidation sysadmin account for the SQL ServerDatabase Engine and the SQL Server Analysis services This is required so that the Planning andConsolidation sysadmin can create and process the Planning and Consolidation database because theMicrosoft SQL server tries to back up or restore database with the privileged account This account is alsorequired 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 differentdomain 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 theapplication server and the account requires the folder access privilege for the application server
To ensure that you have the complete access privileges we recommend the Planning and Consolidationsysadmin 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 touse a restrictive SQL ID that works with the drill-through feature If you must restrict SQL authentication forsecurity 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 installationprogram
20
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
8 Choose Install to begin the installation with the options you have set
SQL Server Component Options
For Single-Machine Installations
Install the following components from the Feature Selection screen
Database Engine Services
Analysis Services
Integration Service which is listed as one of the Shared Features
For Multiple Machine Installations
For multiple machine installations install the following components on each server
Table 7
Server Component What to Install
SQL Server Database Engine Services
SSAS Server Analysis Services
Application Server The following Shared Features
Client Tools Connectivity
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 Server2008 R2 and SQL Server 2012
Process Dimension
It is now possible to process a dimension with multiple selections At processing time the process dimension modulemakes changed or added information for each dimension and process for all selected dimensions and cubes inparallel
Optimize Model
If there are custom partitions for a FACT partition in the OLAP database an optimization module can process custompartitions in parallel when Full or Incremental Optimize is performed However if a full optimize is performed withthe 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 parallelbecause 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 applicationserver and application set databases
NoteSetting the SQL isolation level to be Read Committed Snapshot mode for a database can only be done once andcannot be reversed
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 21
Real Time MOLAP
You can set the OLAP storage model of the write-back partition to be MOLAP (Multidimensional OLAP) This settingremains 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 asfollows
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 Servertrade20052008 which you can download from wwwmicrosoftcom (search on ldquoTable Partitioningrdquo to find all relevantarticles)
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 Thebrowser 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 localhostand external network interface machine
3 If you want to use IP1 which indicates Server IP set Enabled to Yes and specify the TCP Port as desired
4 Delete 0 from TCP Dynamic Ports Set IPAll - TCP Ports as desired (for example 1533)
RecommendationWe do not recommend using dynamic ports
In an SQL server the default instance has a listener which listens on a fixed port (TCP port 1433)However for the named instance the port on which the SQL server listens is random and dynamicallyselected when the named instance of the SQL server starts This recommendation prevents any conflictproblems
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 Setthe 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 thatthe user identified as the Log on as user has the sysadmin SQL Server role defined under Server Roles in theSQL Server Management Studio This is required so Analysis Services can process the SQL Server
From SQL Server Management Studio do the following tasks
22
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
1 If you want to use a port with a named instance select the server type Analysis Services select the servername (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 ServerProperties window displays which shows all configurable properties
3 For enhanced security change the default value to your port number (for example 2724) This means thatyou use a fixed port as for the SQL Server option Then choose OK
NoteWe do not support a nondefault port with the default instance in this release If you want to use the defaultinstance do not change the port number
Restart SQL and OLAP
Confirm that the installation has completed successfully by checking that there are no installation relatedproblems on the event viewer You can now install Planning and Consolidation
274 Installing Analysis Services
Procedure
After you install SQL Server and its required service packs and hotfixes you must install SQL Server Analysis Servicesand its required service packs and hotfixes
NoteIf you have migrated your Analysis Services repository to the SQL Server back up the database that contains therepository before installing this release
To install Analysis Services for SQL Server 2008 SQL Server 2008 R2 or SQL Server 2012 follow the steps andguidelines in technetmicrosoftcomen-uslibraryms143219aspx
To avoid slow performance when a user has more than six OLAP databases follow the steps and guidelines in thePerformance Guide for SQL 2008 at wwwmicrosoftcomdownloadsdetailsaspxFamilyID=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 tohave it available for the Planning and Consolidation installation program
1 Download the Anti-Cross Site Scripting Library file AntiXSSLibraryDLL from the Microsoft Web site atwwwmicrosoftcomdownloadendetailsaspxid=28589
2 Save the extracted file locally
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 23
When you install Planning and Consolidation Server a step in the process requires you to identify the path toAntiXssLibrarydll
28 Installing on a Single Server
When you install all Planning and Consolidation server components on a single server you should consider thefollowing 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 theuncompressed 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 Log on to the server with a local server user ID or domain user ID For more information see Logging on toservers [page 14]
3 Make sure all prerequisite software is installed on the server For more information see Installing thePrerequisites [page 17]
4 Obtain SAP Planning and Consolidation archive from the Downloads SAP Installations amp Upgrades areaof SAP Service Marketplace
5 Extract the files from the archive Go to the BPC Setup folder and run the StartUpexe file
6 From the Server Install screen select Install the Planning and Consolidation server
7 From the Welcome screen choose Next
8 From the License Agreement page choose I accept the terms of the license agreement then choose Next
9 From the Installation Method page accept the default Single machine enter a system ID for the systemlandscape directory (SLD) and choose Next
NoteEntering a system ID of the SLD is only required if you have a SAP Solution Manager license If you do nothave a SAP Solution Manager license you can leave this field empty
10 From the Authentication Method page choose the desired authentication method and choose Next
11 If you have chosen SAP BusinessObjects User Management System in the previous screen on the CMSAuthentication page enter the information required to log on to CMS as an administrator
The following information is required
24
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
Table 8
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 Thisgroup name is filtered as the default when adding a user in Planning andConsolidation Administration Use a comma ( ) to separate multiple names
12 After entering the CMS administrator authentication details choose Next
13 From the Service type accounts page enter service-level account user IDs and passwords See Service-LevelAccounts [page 15]
14 After defining the IDs and passwords choose Next
15 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 chooseNext
16 Specify the location and name of AntiXssLibrarydll See Installing the Anti-Cross Site ScriptingLibrary [page 23]
Choose Next
17 Select destination folders for Programs and Data The Data files include Webfolders and FileDB (publishedreports) and should be installed on a separate drive in a production environment This recommendation reducesthe hard disk IO time and helps to speed up SQL commands
Accept the defaults or make your selections then choose Next
18 Select the default values for the Web client The values are used to determine the default language and regionfor the Web client when you connect to it You can change the values in the Planning and Consolidation ServerManager
19 The installation process takes a few moments When it is complete choose Exit
20 A prompt is displayed to restart your computer Select OK to restart
21 Perform the steps in After Installing Planning and Consolidation Servers [page 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 avariety of ways and configure the servers as a Network Load Balancing (NLB) environment
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 25
The recommended Planning and Consolidation practice is to assign resources using a round robin approach for loadbalancing
You can install the SQL OLAP and FileShare types remotely from the application server You need to performadditional server installations if you have multiple application servers
Installing each Planning and Consolidation application server in a multiserver (NLB) configuration is identical to theprocedure 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 Balancingenvironment With this option there is an additional choice to Include sample environment (required on only oneof the application servers) This is because when you install the application server it connects to the databaseserver and creates the sample environment (EnvironmentShell) Installing the sample environment is requiredon 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
26
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
3 After Installing Planning and ConsolidationServers
31 Post-Installation Steps
Procedure
Perform these steps after installing the Planning and Consolidation servers for new installations of Planning andConsolidation
1 Connect your Planning and Consolidation system to Solution Manager Diagnostics (SMD) to allow support staffto identify analyze and resolve problems with your application See Connecting to Solution ManagerDiagnostics [page 28]
2 Configure the Planning and Consolidation NET and application server to ensure that it and its related servicesfunction properly and reliably For more information see Configuring the Planning and Consolidation NETApplication Server [page 29]
3 Optional configuration steps [page 29]
1 To ensure proper functioning of the Management Console create an SQL user and modify the System DSNand 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 loggingfor ODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default WebSite [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory canaccess the Management Console with whatever rights they have been granted on the server Forinformation about removing default access and creating a group that can access the console see RemovingDefault Access to the Console [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommendthat you only grant Management Console access to system administrators Planning and Consolidationusers should not have any access For more information see Management Console AccessControl [page 33]
6 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
4 Take the following steps to set up security
If you are defining security and application structure continue with step 5
If you want to designate someone other than the system administrator to manage security and applicationstructure log on to EnvironmentShell designate a user as a Primary Administrator
This user must have Administration ndash Environment and Security ‒ Define User task rights so that he or shecan 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 SeeInstalling the Administration Client [page 37]
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 27
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 taskprofiles 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 mustcomplete this step since there is no access to dimensions or members)
NoteTo allow users to request and query large amounts of data you can edit the metabasexml file located at CWindowssystem32inetsrv Set the following parameters to the stated values
ASPBUFFERINGLIMIT = 10485760
MAXREQUESTENTITYALLOWED = 10485760
32 Connecting to Solution Manager Diagnostics
NoteYou only need to perform the steps in this section if you have a SAP Solution Manager licence
The diagnostics functions in SAP Solution Manager allow identification analysis and resolution of problems Thisprocedure 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 areinstalled
NoteInstallation files for Diagnostics Agent are available on Service Marketplace by navigating to SupportPackages and Patches mdash Entry by Application Group SAP Technology Components SAP SOLUTIONMANAGER SAP SOLUTION MANAGER 70 EHP 1 Entry by Component Agents for managed systemsDIAGNOSTICS AGENT 711
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 whereMicrosoft 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
28
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
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 ServiceMarketplace at servicesapcom~sapidb011000358700000074392009E and follow the chapters that applyto Planning and Consolidation
33 Configuring the Planning and Consolidation NETApplication Servers
Procedure
Modifying machineconfig Files
To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock occurrences that wouldcause the application server to ldquosleeprdquo and not process anymore you can modify the machineconfig file whichresides in the WINDOWSMicrosoftNETFramework64v4030319Config directory
1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to specifywhether to automatically configure settings to achieve optimal performance based on the machineconfiguration You can set this attribute to True or False
For more information see msdnmicrosoftcomen-uslibrary7w2sway1aspx
2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the Planning andConsolidation application) or Machineconfig (for all applications including Planning and Consolidation) toensure the validationKey and decryptionKey keys have the same value on all application servers Thisway when the authentication cookie is checked the authentication ticket used on one server can still be validon another server
For more information and sample Visual Basic code for generating random key values seemsdnmicrosoftcomen-uslibraryms998288aspxpaght000007_webfarmdeploymentconsiderationsand msdnmicrosoftcomen-uslibraryms998310aspx
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 DSNand 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 forODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory can accessthe Management Console with whatever rights they have been granted on the server For information about
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 29
removing default access and creating a group that can access the console see Removing Default Access to theConsole [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommend thatyou only grant Management Console access to system administrators Planning and Consolidation users shouldnot have any access For more information see Management Console Access Control [page 33]
6 Configure the use of SSL in Planning and Consolidation See Configuring Planning and Consolidation to useSSL [page 34]
7 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
8 Configure Microsoft SQL Server Reporting Services to use SSL See Configuring MS SQL Server ReportingServices to use SSL [page 36]
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 databaserole 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 optionto use ODBC Logging Enter the following values
DSN is BPC_ManagementDSN Table is BPCLog The Microsoft SQL Server Username and Password
5 Restart IIS
NoteWithout these updates the Management Console does work but some functionality (specifically User Activityand Service Status) does not work as expected
Should you need to uninstall Planning and Consolidation we recommend that you reset the Active Log Formatfield in IIS to W3C Extended Log File Format
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
30
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
Prerequisites
ODBC logging has been configured according to the Microsoft Knowledge Base article 245243 How to configureODBC 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 inApplicationHostconfig as shown here
ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0logFormat=Custom gtUse 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-00AA006111E0appcmd 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 articlespecified in the Prerequisites section Configure these settings in the ltodbcLogginggt node underltsystemwebServergt
Exampleltlocation path=Default Web SitegtltsystemwebServergtltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog userName=Usernamepassword=mypassword gtltsystemwebServergtltlocationgt
Use the following AppCmds to configure these attributes for the default Web site
appcmd set config Default Web Site sectionodbcLogging dataSourceBPC_ManagementDSN commitappHostappcmd set config Default Web Site sectionodbcLogging tableNameBPCLog commitappHostappcmd set config Default Web Site sectionodbcLogging userNameUsername commitappHostappcmd set config Default Web Site sectionodbcLogging passwordmypassword commitappHost
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 31
NoteYou cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must use the SQL ServerODBC driver For more information see the Microsoft Knowledge Base article 931202 The requirements for usingthe ODBC logging feature in IIS
343 Setting Up an ODBC Data Source in Windows Server2008 2008 R2 2012 or 2012 R2
Procedure
This procedure describes how to set up an ODBC data source for the Management Console in Windows Server 20082008 R2 2012 or 2012 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
NoteIf you have chosen SAP BusinessObjects User Management System in the installation screen you do not needto remove or configure access because the Management Console service always runs with the System Admin IDaccount which is a member of the Administrators group
Procedure
To remove default access to the Management Console and create a group that does have access to the console usethe procedure described below
32
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
NoteCreate your Management Console administrative group either on the server that hosts the Management Consoleor 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
NoteAlternatively you can perform analogous steps in Active Directory
3 In the Groups context menu choose New Group
4 Enter data as required Click Create
5 In the Computer Management dialog box choose Services and Applications Internet InformationServices 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 objectand all child objects Include these with entries explicitly defined here checkbox
NoteThis step is a necessary precursor to the completion of this procedure
10 In the Security dialog box click Copy to ensure that the System group retains its privileges
11 Remove access to the Management Console from all groups that should not have it
12 Choose Authentication in the center pane then disable Windows authentication
Result
Users who have not been granted access to the Management Console can still open the Management Console Webpage but it contains no data or menu options This does not affect the access that a user would otherwise have toPlanning and Consolidation
345 Management Console Access Control
After establishing the Management Console group you can add users or groups to it For more information aboutcreating this group see Removing Default Access to the Console [page 32] Their rights in Active Directory determinewhat they can access in the Console
By default any member of the Administrators Active Directory group on the application server or domain has fullaccess to all of the features of the Console except the Planning and Consolidation logging area Access to Planningand Consolidation logging is controlled within the Planning and Consolidation Administration Client task securityThe user must be granted View system logs task privileges For more information see the SAP Library Planning and
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 33
Consolidation Administrators Guide in servicesapcominstguidesepm-bpc 100 version for the Microsoftplatform
Your IT policy determines whether you grant access by group or user You may wish to create several levels of Consoleusers (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 describedin this table
Table 9
Privilege Rights Management Area
Task Manager and Kill Process Administrators group on application server or domain
Performance Monitor Counters Administrators group on application server or domain
Power Users group on application server or domain
Performance Monitor Users group on application server
Microsoft Analysis Services performance monitoring Administrators group on application server or domain
Microsoft SQL Server Monitoring (performance counters andstatistics)
Administrators group on application server or domain
346 Configuring Planning and Consolidation to use SSL
Procedure
Creating a Certificate for the Server
During the handshake phase of the SSL communication the server must send its certificate to the client The clientthen uses the certificate to encrypt information and send it back to the server
The procedure below describes how to create a self-signed certificate for the server
RecommendationWe recommend that you limit the use of self-signed certificates to testing only For a productive system you shouldobtain a certificate signed by a well-known certification authority (CA)
1 Start the Internet Information Services (IIS) Manager To do that go to Start All Programs AdministrativeTools Internet Information Services (IIS) Manager
2 In the Connections panel on the left-hand side select the server node and then choose Server Certificates
3 In the Actions panel on the right hand side choose the Create Self-Signed Certificate action
4 Enter the name that you want the certificate to be identified by for example MyTestSSLCertificate
IIS generates a new SSL certificate for you that has one yearrsquos expiry lease The certificate is issued to the local servername
Binding the Certificate to the Web Site
The procedure below describes how to bind the certificate to the web site for which SSL connections must be used
1 In the Connections panel select the web site node
2 In the Actions panel choose Bindings
34
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
3 In the Site Bindings dialog that appears choose the Add button to create a new binding
4 Configure the parameters as follows
Type = https IP Address = [1] - this is a shorthand expression for the local server name
Port = 443 - this is the default SSL port
SSL Certificate = enter your newly created certificate name
5 Choose OK to create the new binding and then close the Site Bindings dialog
6 Restart the IIS processes To do this choose Restart from the Actions panel
7 In the middle panel under the IIS section choose SSL Settings
8 In the SSL Settings screen select the Require SSL checkbox
9 In the Actions panel choose to Apply these settings
To test the SSL connection in the Actions panel choose the Browse [1] 443 (https) link
347 Using Client Certificates
To enable the use of client certificates in Planning and Consolidation you must follow several manual steps
NotePlanning and Consolidation supports client certificate authentication in Windows Authentication Mode butdoes 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 technetmicrosoftcomen-uslibrarycc753810aspx
For more information about configuring the client certificate mapping authentication see technetmicrosoftcomen-uslibrarycc732996(WS10)aspx
When you create the client certificates you can set the type of certificate in the SSL Settings screen in InternetInformation Services (IIS) Manager
Procedure
1 Set the options for client certificates
1 In the IIS Manager select the web site where you installed Planning and Consolidation
2 Choose SSL Settings
3 In the Client certificates section select the Accept client certificates option
This option allows you to use a client certificate or username and password (Basic authentication) toconnect 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 theManagementConsole home page
3 Double-click Authentication and enable Anonymous Authentication
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 35
4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way asin step 3
5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the sameway 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
348 Configuring MS SQL Server Reporting Services to useSSL
Procedure
The procedure below describes how to configure the use of SSL in Microsoft SQL Server Reporting Services
NoteReporting Services does not provide functionalities for generating requesting or installing a certificate Theserver certificates that you want to use for configuring SSL must have already been installed on your computer
1 Open the Reporting Services Configuration Manager program To do this open the Windows Start menu andnavigate to All Programs Microsoft SQL Server ltversiongt Configuration Tools Reporting ServicesConfiguration Manager
2 In the Connect panel on the left-hand side select the Web Service URL option to open all the Report Server webservice parameters
3 Configure the parameters as follows
SSL Certificate = the name of the certificate that you want to use
SSL Port = 4434 Choose Apply to confirm the changes
5 In the Connect panel choose Report Manager URL to open the list of parameters that link Reporting Servicesto IIS
6 Choose Advanced to add your new SSL web URL
7 In the section Multiple SSL Identities for Report Manager choose Add Configure the parameters as follows
IP Address = (All IPv4) SSL Port = 443 Certificate = the name of your SSL certificate
8 To test the configuration click the URL that appears under the Report manager Site Identification section
36
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
4 Installing Planning and ConsolidationAdministration Client and the SAPBusinessObjects EPM solutions Add-in forMicrosoft Office
The installation of the Planning and Consolidation Administration Client allows administrators to build and maintainPlanning and Consolidation environments and models and administer security
All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions add-in forMicrosoft 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 valueof the Planning and Consolidation client to prompt for user name and password Otherwise the Planning andConsolidation Start Page does not display
41 Installing the Administration Client
Prerequisites
NoteFor a definitive list of system requirements see the Product Availability Matrix on SAP Service Marketplace atservicesapcompam Search on Planning and Consolidation
The following list describes the minimum software requirements
Microsoft Internet Explorer 70 80 90 or 10
Microsoft Office 2003 2007 2010 or 2012
NET Framework 20 or higher (install any required NET Framework Hotfixes by referring tosupportmicrosoftcomkb)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 37
NoteWe recommend that you install all of the latest Microsoft Windows hotfixes prior to installing the Administrationclient For information about which hotfixes to install see updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us
Procedure
The 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 ltPC_serverportgtsapbpcweb
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 mustdownload the most recent version of the full setup (EPM Add-inexe) from the Service Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPCInstallation folder
Individual users can install the EPM add-in on their own machines by going to the Planning and Consolidation Homepage 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 upthe 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
38
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
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 toperform the upgrade If Client Auto Update is not enabled and a newer version is detected clients must be installedmanually 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 andpassword in the Admin ID and Admin password fields respectively The Admin ID should be a member of thelocal administrators group on all the computers running the auto update This setting is not needed if all usershave 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 Thisoption is stored in the user preferences and may also be turned on or off using the User Optionshellip menu itemIf 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 toinstall 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 installit 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 servicesapcom
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 versionand policy information For a support package these files are
EPM Addin Support Package ltSP versiongtmsp EPM Addin Support Package ltSP versiongtxmlFor a patch these files are
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 (WebsrvrWebBPCInstallation)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 39
You can set a different update policy for each package listed
ExampleThe following table illustrates some possible situations assuming that you have installed the first full version(V1)
Table 10
Available maintenancepackages
V2-user update
V3-force update
V4-force update
V5-user update
V5-user update V5-user update
V6-auto update
V7-force update
Minimum RequiredVersion
V4 V4 V7
Notification A prompt tells the user toinstall maintenancepackage V4 using theForced Update behavior
If User Update is enabledthe prompt informs theuser that maintenancepackage V5 is available
A prompt tells the user toinstall maintenancepackage V7 using theForced Update behavior
New Version V4 V4 or V5 V7
If you change the update policy for any package click Update to complete the change
40
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
5 Connection Issues
You may experience connection problems with ports the proxy server or programs and settings that interact withthese components If you have any issues related to connection review the following recommendations andtroubleshooting tips
51 Checking for Open Ports
You must ensure that all required ports are open for inboundoutbound traffic By default Planning andConsolidation requires that Ports 80 (used by http) and 1433 and 2383 (used by SQL Server 2008) are open Totest whether the required ports are open go to a command prompt and enter the Telnet serveripaddress and portFor example Telnet 431181836 80 If the system returns a blank command window the port is open If it returnsa message stating that it is unable to connect the port is not open
NoteYou can use the following site to scan for the normal ports It allows you to manually enter a port number to test
wwwmyserverorgportsniffasp
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 Planningand Consolidation server as an exception You can do this at the client level ( Internet Explorer ToolsInternet 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 fullyqualified 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 Consolidationauthentication Do not use authentication on the proxy server The system synchronizes the user name andpassword on the remote server with the local user name and password
SAP Business Planning and Consolidation 100Connection Issues
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 41
NoteFor more information about setting up an ISA proxy server contact SAP Support to request a copy of Setting upISA Proxy Server White Paper For more information about Business Planning and Consolidation firewall portssee SAP Note 1505250
Internet Explorer Settings Issues
Internet Explorer settings must be set correctly to prevent errors and problems when you attempt to access thePlanning 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 insertthe IP address or fully qualified server name of the Planning and Consolidation server as an exception bychoosing 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
42
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Connection Issues
6 Installing Planning and Consolidation withTwo Active Directory Domains
To set up a Planning and Consolidation 10 application server in a hosted environment and use your own domainusers follow this procedure In general you install Planning and Consolidation on the host domain use the hostdomain account and assign it to the Planning and Consolidation users SysAdmin Admin and Users Then you acceptone 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 andpassword 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 topromote 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 privilegefor the Planning and Consolidation server
5 Install Planning and Consolidation and assign your domain account either to the three Planning andConsolidation administrative users SysAdmin Admin and Users or to only one of the three Planning andConsolidation administrative users and to three of your users Be sure you use your own user account ratherthan host domain users
Planning and Consolidation impersonation can then access your domain from the host environment becauseit has the privilege of your domain account
SAP Business Planning and Consolidation 100Installing Planning and Consolidation with Two Active Directory Domains
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 43
7 Installing Planning and Consolidation in aTerminal Services or Citrix ServerDeployment
This section describes best practices and instructions for installing Planning and Consolidation in a Terminal Servicesor Citrix Server deployment
71 Terminal Services Home Directories
We recommend using Terminal Server home directories rather than using the userrsquos profile directory The profiledirectory downloads a minimal amount of information about the dimensions of the environment you are logging onto and may be as large as 2 MB per user The profile directory is on the system drive and has limited space Byspecifying 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 individualserver 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 clientserver (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
44
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
Procedure
The following steps outline how to install the Planning and Consolidation clients in a Terminal Services (TS) or CitrixServer deployment
1 Make sure the Terminal Services or Citrix Server machine has the system requirements installed
2 Log on to the Terminal Services or Citrix Server machine with a user ID that has the rights to install on thatserver
3 At a command prompt enter Change userinstall
4 Open a browser and connect to the URL ltPC_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_MSBPCAdminMainexe
74 Creating a Shortcut to the Launch Page
Procedure
If you use published desktops instead of published applications the Planning and Consolidation desktop file (whichis installed on the current userrsquos desktop) must be moved to the All UsersDesktop folder
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 45
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 SQLServer 2012 support the remote modification of SSIS packages Planning and Consolidation also supports theremote 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 whichyou want to modify SSIS packages
These custom tasks reference dlls that connect to the database server and perform certain validation when usersset up the parameters of each task All the custom task reference components must also be installed in the machineon which you want to modify SSIS packages
We provide a program that registers all the reference components of the custom tasks This section explains theinstallation 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 ndash This folder contains all the dlls that should be installed on the machine There are Planning andConsolidation platform components and all of the Data Manager custom task files
Config folder ndash This folder contains only one file named Filelistxml and lists all of the files that should be installedIf you need to add or remove certain components from the installation you can modify this xml file
OSoftSetupexe ndash This is the main executable file to run the installation package
NoteIf you are not installing SSIS Custom Tasks on your client machine ndash specifically a machine other than the Planningand Consolidation application server ndash you must first install OSoftSSIS2008_Client or OSoftSSIS2012_Client onthe client machine followed by the SQL Server version If you want to use SQL 2008 Tasks under the SQL 2012environment you must install OSoftSSIS2008_Client on the application server For detailed information see SAPNote 1707410 You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package byextracting OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPCInstallation folder on the Planning and Consolidation server To modify SSIS packages on the Planning andConsolidation application server you need to install OSoftSSIS2008_Client or OSoftSSIS2012_Client for creatinga COM+ application For more information see Before You Modify the SSIS Packages [page 49] and Setup ofa COM+ Application on the Application Server [page 50]
Bin folder
This folder contains the following components
46
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Table 11
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012respectively
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
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 47
Name Remark
BPCWriteBackdll
InteropDTSdll
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 addmore components to the installation package you can copy the new components into the Bin folder and add theproper xml tags in FileListxml You need to enter information for the following tags
RegistType ndash This is the registration information of the component You can enter the following values
RegAsm ndash For NET component
48
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Regsvr32 ndash For VB6 component
Gacutil ndash For NET Framework component that should be registered into Global Assembly Cache
FileName ndash Component file name
OSoftSetupexe
This is the executable file to run the SSIS installation package Double-click the file to start the installation You needto enter information for the following fields
Set SQL server
Specify the SQL server name If your SQL Server has an instance specify the instance name
NoteIf you installed the OSoftSSIS2008_Client or OSoftSSIS2012_Client on the application server the SQL servername is automatically disabled
Set server credential
This is the credential name of the COM+ package component Enter the user ID and password that can accessyour SQL Server This should be either the System Admin ID or Admin ID that was registered as a COM+ userwhen 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 ifyou 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 packagesremotely This is also true for the application server that has SSIS installed The Planning and ConsolidationData Manager has the following custom tasks
Table 12
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008and 2012 respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and2012 respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012respectively
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 49
Name Remark
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and2012 respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008and 2012 respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL2008 and 2012 respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and2012 respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012respectively
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
ltdrivegtWebsrvrbin2 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 FilesMicrosoft SQLServer paste all files into the CProgram Files (x86)Microsoft SQL Server100DTSTasksfolder
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
50
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Typographic Conventions
Table 13
Example Description
lt gt Angle brackets indicate that you replace these words or characters with appropriate entries tomake entries in the system for example Enter your ltUser Namegt
File Save Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
Example Textual cross-references to an internet address for example wwwsapcom
example Quicklinks added to the internet address of a homepage to enable quick access to specificcontent 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 titlespushbutton 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 namesof installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transactioncodes database table names and key concepts of a programming language when they aresurrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
SAP Business Planning and Consolidation 100Typographic Conventions
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 51
52
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
wwwsapcom
Material Number
- SAP Business 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 2008 R2 2012 or 2012 R2
- 344 Removing Default Access to the Console
- 345 Management Console Access Control
- 346 Configuring Planning and Consolidation to use SSL
- 347 Using Client Certificates
- 348 Configuring MS SQL Server Reporting Services to use SSL
-
- 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
-
Documentation on the SAP Service Marketplace
You can find this document at the following address servicesapcominstguidesEPM-BPC
SAP Business Planning and Consolidation 100Documentation on the SAP Service Marketplace
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 3
Document History
The following table provides an overview of the most important document changes
Table 1
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 SingleServerrdquo
Added 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 recommendationto 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 recommendinstalling Microsoft Office on the application server Also removed the note at the end of theprocedure that discussed launching the installation of a Microsoft ACE OLEDB Provider on amachine 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 andConsolidation NET Application Serversrdquo
137 2012-06-13 Updated NET 20 to NET 40 in the topic ldquoConfiguring the Planning and Consolidation NETApplication Serversrdquo
138 2012-10-17 Improved the installation procedure in the topic ldquoInstalling on a Single Serverrdquo
139 2012-12-05 Changes in the topics ldquoPrerequisitesrdquo and ldquoInstalling the Prerequisites ndash Basic Stepsrdquo mdashupdated the required version of Microsoft Visual C++ and vcredist_x64exe
14 2013-04-30 Updated the topic Installing the Administration Client [page 37] with versions of MicrosoftInternet Explorer and Microsoft Office supported as of support package 10
15 2013-09-09 Updated the topic ldquoSAP Notes for the Installationrdquo with the central note number for supportpackage 11
16 2013-10-17 Updated the topic Proxy Server and Firewall Issues [page 41] with a note to refer to SAP Note1505250 for information about firewall ports
165 2014-01-10 Updated the topic ldquoSAP Notes for the Installationrdquo with the central note number for supportpackage 12
17 2014-04-02 Added topics about configuring SSL in IIS and in SQL Server Reporting Services
18 2014-08-08 For support package 14
4
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Document History
Version Date Description
Updated the topic ldquoImportant SAP Notesrdquo with the central note number for supportpackage 14
In the topic Prerequisites [page 11] added Windows 2012 to the list of possibleoperating systems and added IIS 80 IIS 85 NET 35 and NET 45 to OtherRequirements
Updated the topic Setting Up an ODBC Data Source in Windows Server 2008 2008R2 [page 32] to include Windows 2012
SAP Business Planning and Consolidation 100Document History
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 5
Content
1 Introduction 911 SAP Notes for the Installation 912 Naming Conventions 10
2 Installing Planning and Consolidation Servers 1121 Basic Steps 1122 Prerequisites 1123 Before Starting the Planning and Consolidation Server Installation 1324 Logging on to Servers 1425 Service-level Accounts 1526 Standard and Advanced Settings 1627 Installing the Prerequisites 17
Installing the Prerequisites ndash Basic Steps 17 Installing the Operating System 19 Installing the SQL Server 19 Installing Analysis Services 23 Installing the Anti-Cross Site Scripting Library 23
28 Installing on a Single Server 2429 Installing the Server in a Multiserver Configuration 25
3 After Installing Planning and Consolidation Servers 2731 Post-Installation Steps 2732 Connecting to Solution Manager Diagnostics 2833 Configuring the Planning and Consolidation NET Application Servers 2934 Post-Installation Optional Configuration Steps 29
Enabling the Management Console 30 Setting Up ODBC Logging in IIS for the Default Web Site 30 Setting Up an ODBC Data Source in Windows Server 2008 2008 R2 2012 or 2012
R2 32 Removing Default Access to the Console 32 Management Console Access Control 33 Configuring Planning and Consolidation to use SSL 34 Using Client Certificates 35 Configuring MS SQL Server Reporting Services to use SSL 36
4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjectsEPM solutions Add-in for Microsoft Office 37
41 Installing the Administration Client 3742 Installing the EPM Add-in 3843 Using the Client Auto Update Program 38
5 Connection Issues 4151 Checking for Open Ports 4152 Proxy Server and Firewall Issues 41
6
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Content
6 Installing Planning and Consolidation with Two Active Directory Domains 43
7 Installing Planning and Consolidation in a Terminal Services or Citrix ServerDeployment 44
71 Terminal Services Home Directories 4472 System Requirements 4473 Installing Planning and Consolidation 4474 Creating a Shortcut to the Launch Page 45
8 Installing SSIS Custom Tasks 4681 Composition of SSIS Custom Task Installation 4682 Before You Modify the SSIS Packages 4983 Setup of a COM+ Application on the Application Server 50
SAP Business Planning and Consolidation 100Content
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 7
8
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
1 Introduction
The SAP BusinessObjects Planning and Consolidation Installation Guide is intended for System Administrators whoperform Planning and Consolidation server and Administration client installations It contains everything you needto 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 releasewe provide detailed instructions on how to migrate your existing environments For more information see theUpgrade Guide which is available on SAP Service Marketplace at servicesapcominstguidesEPM-BPC Planningand Consolidation 100 version for the Microsoft platform
For more information about the Planning and Consolidation Office client software see the SAP BusinessObjects EPMsolutions 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 FileOLAP 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 2008or Windows Server 2008 R2 for remote desktop access
Planning and Consolidation no longer requires a separate Web server only an application server You can installthe application server on a single machine or on multiple machines with network load balancing (NLB) If youuse 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 informationon the installation as well as corrections to the installation documentation Make sure that you have the up-to-dateversion of each SAP Note which you can find in the SAP Service Marketplace at the Internet addressservicesapcomnotes
Table 2
SAP Note Number Title Comments
1584890 Documentation Addendum Contains information that does not yet appear in theapplication help of Business Planning and Consolidation100 version for the Microsoft platform Application helpis available at helpsapcombopacms100
2000499 Business Planning amp Consolidation 10 forMicrosoft SP14 Central Note
This note contains important information about theinstallation of support package 14
SAP Business Planning and Consolidation 100Introduction
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 9
SAP Note Number Title Comments
1961655 Business Planning amp Consolidation 10 forMicrosoft SP13 Central Note
This note contains important information about theinstallation of support package 13
1897745 Business Planning amp Consolidation 10 forMicrosoft SP12 Central Note
This note contains important information about theinstallation of support package 12
1846917 Business Planning amp Consolidation 10 forMicrosoft SP11 Central Note
This note contains important information about theinstallation of support package 11
1804918 Business Planning amp Consolidation 10 forMicrosoft SP10 Central Note
This note contains important information about theinstallation of support package 10
1755355 Business Planning amp Consolidation 10 forMicrosoft SP09 Central Note
This note contains important information about theinstallation of support package 9
1733053 Business Planning amp Consolidation 10 forMicrosoft SP08 Central Note
This note contains important information about theinstallation of support package 8
1689792 Business Planning amp Consolidation 10 forMicrosoft SP07 Central Note
This note contains important information about theinstallation of support package 7
1665656 Business Planning amp Consolidation 10 forMicrosoft SP06 Central Note
This note contains important information about theinstallation of support package 6
1643037 Business Planning amp Consolidation 10 forMicrosoft SP05 Central Note
This note contains important information about theinstallation of support package 5
1620464 Business Planning amp Consolidation 10 forMicrosoft SP04 Central Note
This note contains important information about theinstallation of support package 4
1601213 Business Planning amp Consolidation 10 forMicrosoft SP03 Central Note
This note contains important information about theinstallation of support package 3
1591848 Business Planning amp Consolidation 10 forMicrosoft SP02 Central Note
This note contains important information about theinstallation of support package 2
1573539 Business Planning amp Consolidation 10 forMicrosoft SP01 Central Note
This note contains important information about theinstallation of support package 1
12 Naming Conventions
In this document the following naming conventions apply
Table 3
Variable Description
ltPC_serverportgt Server name or IP address and port number of SAP Planningand Consolidation application location
ltdrivegt The drive where SAP Planning and Consolidation is installed
The default for this is CPC_MS
10
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Introduction
2 Installing Planning and ConsolidationServers
This section includes the basic steps for installing a Planning and Consolidation server the prerequisites and whatto 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 atservicesapcominstguidesepm-bpc 100 version for the Microsoft platform
2 Perform the tasks in the Before Starting the Planning and Consolidation Server Installation [page 13] sectionincluding installing all prerequisites
3 From the application server install the Planning and Consolidation server See Installing Planning andConsolidation on a Single Server [page 24]
NoteYou must install both Planning and Consolidation 100 as well as the most recent Planning and Consolidation100 Support Package available from the SAP Service Marketplace at servicesapcomswdc SoftwareDownloads Support Packages and Patches A - Z Index B SAP BPC FOR MICROSOFT SBOP PC 100FOR MICROSOFT Comprised Software Component Versions SAP CPM BPC 100 M Windows Server onx64 64bit
4 If you have multiple machines see Installing the Server in a Multiserver Configuration [page 25]
5 Perform the steps in the section After Installing Planning and Consolidation Servers [page 27]
22 Prerequisites
The following table describes the software you need to install before installing the Planning and Consolidation serverand the minimum versions required
NoteA list of the supported operating systems and database systems is also available in the Product Availability Matrixon SAP Service Marketplace at servicesapcompam Search on Planning and Consolidation
Table 4
Component Minimum Requirement
Operating System The requirements outlined below are for the following operating systems
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 11
Component Minimum Requirement
Windows Server 2008 (64-bit) Standard Enterprise or Data Center with or withoutHyper-V
Windows Server 2008 R2 (64-bit) Foundation Standard Enterprise or DataCenter with or without Hyper-V
Windows Server 2012 (64-bit) Standard Data Center
Windows Server 2012 R2 (64-bit) Standard Data Center
NoteThe operating system must be configured with NTFS
Relational Database Microsoft SQL Server 2008 Enterprise Edition
Microsoft SQL Server 2008 R2 (Gemini) Enterprise Edition
Microsoft SQL Server 2012 Enterprise Edition
OLAP Database Microsoft SQL Server 2008 Enterprise Edition ndash Analysis Server
Microsoft SQL Server 2008 R2 Enterprise Edition ndash Analysis Server
Microsoft SQL Server 2012 Enterprise Edition ndash Analysis Server
Data Integration Microsoft SQL Server 2008 Enterprise Edition ndash SQL Service Integration Services
Microsoft SQL Server 2008 R2 Enterprise Edition ndash SQL Service IntegrationServices
Microsoft SQL Server 2012 Enterprise Edition ndash 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
NET 35 and NET 45 are required for Windows 2012 and 2012 R2
NET 40 is required for all other operating systems
IIS
IIS 75 or IIS 70
(Included in your Operating System IIS 75 is required for Windows 2008 R2editions)
IIS 80 or IIS 85
(Included in your Operating System IIS 85 is required for Windows 2012 R2editions)
Anti-Cross Site Scripting Library 42
This component must be downloaded before installing the server The serverinstallation program asks for the path of each file and copies the files into theappropriate Planning and Consolidation path
Microsoft Visual C++ 2010 SP1 Redistributable Package (x64)
Microsoft Access Database Engine 2010 64bit
12
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
Component Minimum Requirement
VMWare ESX 3x or ESX 40
(Required only if a landscape deployment strategy using virtualizationtechnologies is planned)
NoteMSXML 40 SP2 ADOMDNET 100 and Microsoft Visual C++ 2010 SP1Redistributable Package (x64) are included with the installation program but notinstalled 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 values being returned withcalculated accounts For more information see SAP Note number 1429246 which also contains downloadinformation
We recommend SQL Server 2008 (or R2) Enterprise Edition or SQL Server 2012 Enterprise Edition for theOLAP database to support proactive cache and cube partitioning It is technically possible to use SQL Server2008 (or R2) Standard Edition or SQL Server 2012 Standard Edition for data integration servers but we donot recommend this
23 Before Starting the Planning and Consolidation ServerInstallation
You must perform the following tasks before starting your Planning and Consolidation server installation
Install all the prerequisite software including all of the latest Microsoft hotfixes For more information seeInstalling the Prerequisites [page 17]
If you access your application through a firewall verify with your network administrator which TCP ports tochoose during the installation By default port 80 is the setting for standard http access and port 443 is thesetting for https access If you require a service to listen on a different port you can specify it during theinstallation 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 onwhich 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 Consolidationand automatically overwrites the previous version If you have made any modifications to EnvironmentShellthat 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 ScriptBlocking
If a version of Planning and Consolidation on a NetWeaver platform exists uninstall it before you install Planningand Consolidation 100 version for the Microsoft platform
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 13
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 enterconvert c fsntfsV
All servers in a multiserver environment must be members of the same domain
In a multiserver environment the installing ID must be a domain user ID We recommend that you do not logon to the servers using a local server user ID even if the user ID is a member of the Administrator group on theserver This way you have the proper authority to install software and to modify the Component Services SeeLogging On to Servers [page 14]
You must determine the IP addresses or server names for all servers before installing Planning andConsolidation 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 portaccess reasons (DMZ WORKGROUP or nontrusted domain authentication failures) do the following
1 Copy the EnvironmentShell database file ServerEnvironmentShelldb10 from the Planning andConsolidation 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 theEnvironmentShell database file in the Server Information Advanced Options Local path forEnvironmentShell DB field (for example cEnvironmentShelldb10)
Install the Anti-Cross Site Scripting Library which provides protection to Web-based applications againstCross-Site Scripting (XSS) attacks See Installing the Anti-Cross Site Scripting Library [page 23]
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 theAdministrator group of a domain to which the server belongs or a member of the Administrator group on the localserver
Errors may display during the installation program and in the diagnostic program if the installing user is not assignedto the Administrator group directly but is assigned to a group with Administrator rights You can ignore thesemessages
NoteIf you change the password used to install Planning and Consolidation you must change the password for theapplicable Planning and Consolidation service To do this go to Server Manager on the application server andselect Server Reset Logon Credentials For more information see the SAP Planning and ConsolidationOperations Guide in servicesapcominstguidesepm-bpc 100 for the Microsoft Platform SBOP Plan amp Consol100 MS Administrators Guide
14
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
25 Service-level Accounts
Service accounts are Windows domain IDs with access to all Planning and Consolidation servers with varying levelsof privileges They allow the software to use the minimum amount of privilege required for each job making it moresecure
You must define these user IDs on the Windows machine For security purposes they should not be used to definePlanning and Consolidation users
Prerequisites
Planning and Consolidation 100 has the following Windows services
BPC SendGovernor which manages Microsoft Analysis Service locks to ensure consistent performance andavoid deadlocks
BPC ServiceManager which manages the System Landscape Directory (SLD) service logging service andglobal caches
BPC CTS ServiceManager which listens and handles CTS import requests from the CTS+ transportmanagement system
Since these services should be able to access to the FileShare server an Admin account is assigned automaticallyto the service during the installation of the Planning and Consolidation server program Even though an Adminaccount 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 serviceon the local machine This logon right strictly applies only to the local computer and must be granted in the LocalSecurity Policy
To edit the Local Security Policy of the computer you want to define the logon as a service permission performthe 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 supportmicrosoftcomkb259733
Features
During the installation enter user IDs and passwords for the following user types
System Admin ID
This ID is read-only and is the same as the installation user ID that is the system displays the ID on theinstallation screen but you cannot modify it This ID allows access to code that provides system administrator-level functionality For example this ID can write to the Windows registry has full access to the FileShare server
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 15
and can create remove backup and restore OLAP and SQL databases The system administrator should be amember 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 createsubdirectory access on the FileShare server readwrite metadata and application set database data in OLAPand can create and remove tables in SQL The Administrator should be a member of the domain users groupand 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 theservers has write access to FileShare data and can read metadata and data in OLAP and SQL The User IDmust 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 isinstalled you can change these settings using the Server Manager
NoteWhen defining server names the name refers to the NetBIOS name IP address and fully qualified domain names(FQDN)
Standard Settings
Standard settings are typically used for a single-server environment The following table describes each setting
Table 5
Server Option Value Description
SQL Database server name The name of the SQL DB server
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 computername
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
Table 6
Server Option Value Description
SQL Server Name The name of the SQL DB server Defaults to the local server
Instance name The SQL instance name If left blank the default instance is used
16
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
Server Option Value Description
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 computername
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 forhttp and 443 is the default for https
Authentication type Note If you have chosen SAP BusinessObjects User Management System in theinstallation screen Authentication type does not appear in Advanced settings (asthat IIS authentication type is Anonymous in CMS mode)
Windows or Kerberos The default is Windows If you change this value fromWindows to Kerberos you must make some additional changes
See the Kerberos authentication settings section in the SAP Library ServerManager Guide on servicesapcominstguidesEPM-BPC 100 for theMicrosoft Platform
Scheduler Server Name The name of the server used for scheduling usually the application server forexample GMPV50072862B If you have multiple application servers select theappropriate one
NoteIf the primary server stops working you must manually configure yourapplication 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 theoperating system IIS SQL server analysis services ADOMDNET and MSXML This section provides guidance on
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 17
installing each component For specific versions required see Prerequisites [page 11] and the Product AvailabilityMatrix on the SAP Service Marketplace at servicesapcompam Search on Planning and Consolidation
NoteTo ensure a successful installation you must install the software in the order listed in this procedure
Check all third-party infrastructure services to ensure that they are functioning and that their authenticationmodels 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 itsown 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 applicationserver before you start the installation You can find the UMC installation package (UMCexe) on the Planningand Consolidation CD in a folder called UMC_100_INSTALLER When you run the installation package the wizardguides 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 andConsolidation)
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 multiserverconfiguration See Installing the Operating System [page 19]
3 Install the latest service pack for your operating system To install this service pack go towwwmicrosoftcom
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 SQLServer [page 19]
6 From your SQL Server media install Analysis Services Enterprise Edition and its required service packs and hotfixes See Installing Analysis Services [page 23]
7 On your application server install ADOMDNET The Planning and Consolidation zip file contains theADOMDNET 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 followinglocation BPC SetupServermsxmlmsi
18
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
9 On your application server install Microsoft Visual C++ 2010 SP1 Redistributable Package (x64)
The Microsoft Visual C++ 2010 SP1 Redistributable Package (x64) installation package is contained in thePlanning and Consolidation zip file at the following location BPC SetupServervcredist_x64exe
NoteThe version of vcredist_x64exe in BPC SetupServer has been updated to 10040219 If you have aprevious 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 wwwmicrosoftcomdownloadsendetailsaspxFamilyID=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 Marketplaceat servicesapcompam Search on Planning and Consolidation
Business Planning and Consolidation can support all servers with an operating system in any language
NoteCurrently Business Planning and Consolidation does not support an operating system in bi-directionallanguages such as Hebrew
Procedure
If you are installing IIS 70 75 80 or 85 you must enable the following features
Enable Basic Authentication and Windows Authentication these are not installed by default
Install IIS 6 Metabase Compatibility role
Business Planning and Consolidation uses the ADSI provider to handle IIS administration such as virtualdirectory and security but IIS 7 does not install the ADSI provider by default
273 Installing the SQL Server
Prerequisites
During the installation procedure you have the opportunity to specify the location of the EnvironmentShell databasefile Check that it is possible to access EnvironmentShell from the location where you intend to install the SQL serverIf it is not possible for port access reasons (DMZ WORKGROUP or nontrusted domain authentication failures) copyEnvironmentShell to a location on the SQL server (for example CEnvironmentShelldb10) You specify thislocation on the Server Information page by choosing Server Information Advanced Options Local Path forEnvironmentShell DB
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 19
Procedure
This section describes the general steps for installing the SQL Server component options and considerations wheninstalling 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
NoteIf you encounter a 500 HTTP Error when trying to connect to the Planning and Consolidation Web Client referto Microsoft Support articles 2520479 and 2468871 for assistance
To reinforce security we recommend that you install the SQL server and SSAS components to a nondefaultinstance 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 Optionssection below then choose Next
4 Review disc space requirements then choose Next
5 In Server Configuration Perform the following actions
1 In the Service Accounts tab enter a Planning and Consolidation sysadmin account for the SQL ServerDatabase Engine and the SQL Server Analysis services This is required so that the Planning andConsolidation sysadmin can create and process the Planning and Consolidation database because theMicrosoft SQL server tries to back up or restore database with the privileged account This account is alsorequired 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 differentdomain 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 theapplication server and the account requires the folder access privilege for the application server
To ensure that you have the complete access privileges we recommend the Planning and Consolidationsysadmin 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 touse a restrictive SQL ID that works with the drill-through feature If you must restrict SQL authentication forsecurity 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 installationprogram
20
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
8 Choose Install to begin the installation with the options you have set
SQL Server Component Options
For Single-Machine Installations
Install the following components from the Feature Selection screen
Database Engine Services
Analysis Services
Integration Service which is listed as one of the Shared Features
For Multiple Machine Installations
For multiple machine installations install the following components on each server
Table 7
Server Component What to Install
SQL Server Database Engine Services
SSAS Server Analysis Services
Application Server The following Shared Features
Client Tools Connectivity
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 Server2008 R2 and SQL Server 2012
Process Dimension
It is now possible to process a dimension with multiple selections At processing time the process dimension modulemakes changed or added information for each dimension and process for all selected dimensions and cubes inparallel
Optimize Model
If there are custom partitions for a FACT partition in the OLAP database an optimization module can process custompartitions in parallel when Full or Incremental Optimize is performed However if a full optimize is performed withthe 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 parallelbecause 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 applicationserver and application set databases
NoteSetting the SQL isolation level to be Read Committed Snapshot mode for a database can only be done once andcannot be reversed
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 21
Real Time MOLAP
You can set the OLAP storage model of the write-back partition to be MOLAP (Multidimensional OLAP) This settingremains 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 asfollows
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 Servertrade20052008 which you can download from wwwmicrosoftcom (search on ldquoTable Partitioningrdquo to find all relevantarticles)
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 Thebrowser 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 localhostand external network interface machine
3 If you want to use IP1 which indicates Server IP set Enabled to Yes and specify the TCP Port as desired
4 Delete 0 from TCP Dynamic Ports Set IPAll - TCP Ports as desired (for example 1533)
RecommendationWe do not recommend using dynamic ports
In an SQL server the default instance has a listener which listens on a fixed port (TCP port 1433)However for the named instance the port on which the SQL server listens is random and dynamicallyselected when the named instance of the SQL server starts This recommendation prevents any conflictproblems
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 Setthe 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 thatthe user identified as the Log on as user has the sysadmin SQL Server role defined under Server Roles in theSQL Server Management Studio This is required so Analysis Services can process the SQL Server
From SQL Server Management Studio do the following tasks
22
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
1 If you want to use a port with a named instance select the server type Analysis Services select the servername (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 ServerProperties window displays which shows all configurable properties
3 For enhanced security change the default value to your port number (for example 2724) This means thatyou use a fixed port as for the SQL Server option Then choose OK
NoteWe do not support a nondefault port with the default instance in this release If you want to use the defaultinstance do not change the port number
Restart SQL and OLAP
Confirm that the installation has completed successfully by checking that there are no installation relatedproblems on the event viewer You can now install Planning and Consolidation
274 Installing Analysis Services
Procedure
After you install SQL Server and its required service packs and hotfixes you must install SQL Server Analysis Servicesand its required service packs and hotfixes
NoteIf you have migrated your Analysis Services repository to the SQL Server back up the database that contains therepository before installing this release
To install Analysis Services for SQL Server 2008 SQL Server 2008 R2 or SQL Server 2012 follow the steps andguidelines in technetmicrosoftcomen-uslibraryms143219aspx
To avoid slow performance when a user has more than six OLAP databases follow the steps and guidelines in thePerformance Guide for SQL 2008 at wwwmicrosoftcomdownloadsdetailsaspxFamilyID=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 tohave it available for the Planning and Consolidation installation program
1 Download the Anti-Cross Site Scripting Library file AntiXSSLibraryDLL from the Microsoft Web site atwwwmicrosoftcomdownloadendetailsaspxid=28589
2 Save the extracted file locally
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 23
When you install Planning and Consolidation Server a step in the process requires you to identify the path toAntiXssLibrarydll
28 Installing on a Single Server
When you install all Planning and Consolidation server components on a single server you should consider thefollowing 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 theuncompressed 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 Log on to the server with a local server user ID or domain user ID For more information see Logging on toservers [page 14]
3 Make sure all prerequisite software is installed on the server For more information see Installing thePrerequisites [page 17]
4 Obtain SAP Planning and Consolidation archive from the Downloads SAP Installations amp Upgrades areaof SAP Service Marketplace
5 Extract the files from the archive Go to the BPC Setup folder and run the StartUpexe file
6 From the Server Install screen select Install the Planning and Consolidation server
7 From the Welcome screen choose Next
8 From the License Agreement page choose I accept the terms of the license agreement then choose Next
9 From the Installation Method page accept the default Single machine enter a system ID for the systemlandscape directory (SLD) and choose Next
NoteEntering a system ID of the SLD is only required if you have a SAP Solution Manager license If you do nothave a SAP Solution Manager license you can leave this field empty
10 From the Authentication Method page choose the desired authentication method and choose Next
11 If you have chosen SAP BusinessObjects User Management System in the previous screen on the CMSAuthentication page enter the information required to log on to CMS as an administrator
The following information is required
24
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
Table 8
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 Thisgroup name is filtered as the default when adding a user in Planning andConsolidation Administration Use a comma ( ) to separate multiple names
12 After entering the CMS administrator authentication details choose Next
13 From the Service type accounts page enter service-level account user IDs and passwords See Service-LevelAccounts [page 15]
14 After defining the IDs and passwords choose Next
15 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 chooseNext
16 Specify the location and name of AntiXssLibrarydll See Installing the Anti-Cross Site ScriptingLibrary [page 23]
Choose Next
17 Select destination folders for Programs and Data The Data files include Webfolders and FileDB (publishedreports) and should be installed on a separate drive in a production environment This recommendation reducesthe hard disk IO time and helps to speed up SQL commands
Accept the defaults or make your selections then choose Next
18 Select the default values for the Web client The values are used to determine the default language and regionfor the Web client when you connect to it You can change the values in the Planning and Consolidation ServerManager
19 The installation process takes a few moments When it is complete choose Exit
20 A prompt is displayed to restart your computer Select OK to restart
21 Perform the steps in After Installing Planning and Consolidation Servers [page 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 avariety of ways and configure the servers as a Network Load Balancing (NLB) environment
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 25
The recommended Planning and Consolidation practice is to assign resources using a round robin approach for loadbalancing
You can install the SQL OLAP and FileShare types remotely from the application server You need to performadditional server installations if you have multiple application servers
Installing each Planning and Consolidation application server in a multiserver (NLB) configuration is identical to theprocedure 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 Balancingenvironment With this option there is an additional choice to Include sample environment (required on only oneof the application servers) This is because when you install the application server it connects to the databaseserver and creates the sample environment (EnvironmentShell) Installing the sample environment is requiredon 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
26
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
3 After Installing Planning and ConsolidationServers
31 Post-Installation Steps
Procedure
Perform these steps after installing the Planning and Consolidation servers for new installations of Planning andConsolidation
1 Connect your Planning and Consolidation system to Solution Manager Diagnostics (SMD) to allow support staffto identify analyze and resolve problems with your application See Connecting to Solution ManagerDiagnostics [page 28]
2 Configure the Planning and Consolidation NET and application server to ensure that it and its related servicesfunction properly and reliably For more information see Configuring the Planning and Consolidation NETApplication Server [page 29]
3 Optional configuration steps [page 29]
1 To ensure proper functioning of the Management Console create an SQL user and modify the System DSNand 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 loggingfor ODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default WebSite [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory canaccess the Management Console with whatever rights they have been granted on the server Forinformation about removing default access and creating a group that can access the console see RemovingDefault Access to the Console [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommendthat you only grant Management Console access to system administrators Planning and Consolidationusers should not have any access For more information see Management Console AccessControl [page 33]
6 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
4 Take the following steps to set up security
If you are defining security and application structure continue with step 5
If you want to designate someone other than the system administrator to manage security and applicationstructure log on to EnvironmentShell designate a user as a Primary Administrator
This user must have Administration ndash Environment and Security ‒ Define User task rights so that he or shecan 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 SeeInstalling the Administration Client [page 37]
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 27
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 taskprofiles 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 mustcomplete this step since there is no access to dimensions or members)
NoteTo allow users to request and query large amounts of data you can edit the metabasexml file located at CWindowssystem32inetsrv Set the following parameters to the stated values
ASPBUFFERINGLIMIT = 10485760
MAXREQUESTENTITYALLOWED = 10485760
32 Connecting to Solution Manager Diagnostics
NoteYou only need to perform the steps in this section if you have a SAP Solution Manager licence
The diagnostics functions in SAP Solution Manager allow identification analysis and resolution of problems Thisprocedure 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 areinstalled
NoteInstallation files for Diagnostics Agent are available on Service Marketplace by navigating to SupportPackages and Patches mdash Entry by Application Group SAP Technology Components SAP SOLUTIONMANAGER SAP SOLUTION MANAGER 70 EHP 1 Entry by Component Agents for managed systemsDIAGNOSTICS AGENT 711
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 whereMicrosoft 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
28
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
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 ServiceMarketplace at servicesapcom~sapidb011000358700000074392009E and follow the chapters that applyto Planning and Consolidation
33 Configuring the Planning and Consolidation NETApplication Servers
Procedure
Modifying machineconfig Files
To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock occurrences that wouldcause the application server to ldquosleeprdquo and not process anymore you can modify the machineconfig file whichresides in the WINDOWSMicrosoftNETFramework64v4030319Config directory
1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to specifywhether to automatically configure settings to achieve optimal performance based on the machineconfiguration You can set this attribute to True or False
For more information see msdnmicrosoftcomen-uslibrary7w2sway1aspx
2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the Planning andConsolidation application) or Machineconfig (for all applications including Planning and Consolidation) toensure the validationKey and decryptionKey keys have the same value on all application servers Thisway when the authentication cookie is checked the authentication ticket used on one server can still be validon another server
For more information and sample Visual Basic code for generating random key values seemsdnmicrosoftcomen-uslibraryms998288aspxpaght000007_webfarmdeploymentconsiderationsand msdnmicrosoftcomen-uslibraryms998310aspx
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 DSNand 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 forODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory can accessthe Management Console with whatever rights they have been granted on the server For information about
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 29
removing default access and creating a group that can access the console see Removing Default Access to theConsole [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommend thatyou only grant Management Console access to system administrators Planning and Consolidation users shouldnot have any access For more information see Management Console Access Control [page 33]
6 Configure the use of SSL in Planning and Consolidation See Configuring Planning and Consolidation to useSSL [page 34]
7 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
8 Configure Microsoft SQL Server Reporting Services to use SSL See Configuring MS SQL Server ReportingServices to use SSL [page 36]
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 databaserole 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 optionto use ODBC Logging Enter the following values
DSN is BPC_ManagementDSN Table is BPCLog The Microsoft SQL Server Username and Password
5 Restart IIS
NoteWithout these updates the Management Console does work but some functionality (specifically User Activityand Service Status) does not work as expected
Should you need to uninstall Planning and Consolidation we recommend that you reset the Active Log Formatfield in IIS to W3C Extended Log File Format
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
30
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
Prerequisites
ODBC logging has been configured according to the Microsoft Knowledge Base article 245243 How to configureODBC 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 inApplicationHostconfig as shown here
ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0logFormat=Custom gtUse 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-00AA006111E0appcmd 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 articlespecified in the Prerequisites section Configure these settings in the ltodbcLogginggt node underltsystemwebServergt
Exampleltlocation path=Default Web SitegtltsystemwebServergtltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog userName=Usernamepassword=mypassword gtltsystemwebServergtltlocationgt
Use the following AppCmds to configure these attributes for the default Web site
appcmd set config Default Web Site sectionodbcLogging dataSourceBPC_ManagementDSN commitappHostappcmd set config Default Web Site sectionodbcLogging tableNameBPCLog commitappHostappcmd set config Default Web Site sectionodbcLogging userNameUsername commitappHostappcmd set config Default Web Site sectionodbcLogging passwordmypassword commitappHost
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 31
NoteYou cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must use the SQL ServerODBC driver For more information see the Microsoft Knowledge Base article 931202 The requirements for usingthe ODBC logging feature in IIS
343 Setting Up an ODBC Data Source in Windows Server2008 2008 R2 2012 or 2012 R2
Procedure
This procedure describes how to set up an ODBC data source for the Management Console in Windows Server 20082008 R2 2012 or 2012 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
NoteIf you have chosen SAP BusinessObjects User Management System in the installation screen you do not needto remove or configure access because the Management Console service always runs with the System Admin IDaccount which is a member of the Administrators group
Procedure
To remove default access to the Management Console and create a group that does have access to the console usethe procedure described below
32
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
NoteCreate your Management Console administrative group either on the server that hosts the Management Consoleor 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
NoteAlternatively you can perform analogous steps in Active Directory
3 In the Groups context menu choose New Group
4 Enter data as required Click Create
5 In the Computer Management dialog box choose Services and Applications Internet InformationServices 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 objectand all child objects Include these with entries explicitly defined here checkbox
NoteThis step is a necessary precursor to the completion of this procedure
10 In the Security dialog box click Copy to ensure that the System group retains its privileges
11 Remove access to the Management Console from all groups that should not have it
12 Choose Authentication in the center pane then disable Windows authentication
Result
Users who have not been granted access to the Management Console can still open the Management Console Webpage but it contains no data or menu options This does not affect the access that a user would otherwise have toPlanning and Consolidation
345 Management Console Access Control
After establishing the Management Console group you can add users or groups to it For more information aboutcreating this group see Removing Default Access to the Console [page 32] Their rights in Active Directory determinewhat they can access in the Console
By default any member of the Administrators Active Directory group on the application server or domain has fullaccess to all of the features of the Console except the Planning and Consolidation logging area Access to Planningand Consolidation logging is controlled within the Planning and Consolidation Administration Client task securityThe user must be granted View system logs task privileges For more information see the SAP Library Planning and
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 33
Consolidation Administrators Guide in servicesapcominstguidesepm-bpc 100 version for the Microsoftplatform
Your IT policy determines whether you grant access by group or user You may wish to create several levels of Consoleusers (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 describedin this table
Table 9
Privilege Rights Management Area
Task Manager and Kill Process Administrators group on application server or domain
Performance Monitor Counters Administrators group on application server or domain
Power Users group on application server or domain
Performance Monitor Users group on application server
Microsoft Analysis Services performance monitoring Administrators group on application server or domain
Microsoft SQL Server Monitoring (performance counters andstatistics)
Administrators group on application server or domain
346 Configuring Planning and Consolidation to use SSL
Procedure
Creating a Certificate for the Server
During the handshake phase of the SSL communication the server must send its certificate to the client The clientthen uses the certificate to encrypt information and send it back to the server
The procedure below describes how to create a self-signed certificate for the server
RecommendationWe recommend that you limit the use of self-signed certificates to testing only For a productive system you shouldobtain a certificate signed by a well-known certification authority (CA)
1 Start the Internet Information Services (IIS) Manager To do that go to Start All Programs AdministrativeTools Internet Information Services (IIS) Manager
2 In the Connections panel on the left-hand side select the server node and then choose Server Certificates
3 In the Actions panel on the right hand side choose the Create Self-Signed Certificate action
4 Enter the name that you want the certificate to be identified by for example MyTestSSLCertificate
IIS generates a new SSL certificate for you that has one yearrsquos expiry lease The certificate is issued to the local servername
Binding the Certificate to the Web Site
The procedure below describes how to bind the certificate to the web site for which SSL connections must be used
1 In the Connections panel select the web site node
2 In the Actions panel choose Bindings
34
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
3 In the Site Bindings dialog that appears choose the Add button to create a new binding
4 Configure the parameters as follows
Type = https IP Address = [1] - this is a shorthand expression for the local server name
Port = 443 - this is the default SSL port
SSL Certificate = enter your newly created certificate name
5 Choose OK to create the new binding and then close the Site Bindings dialog
6 Restart the IIS processes To do this choose Restart from the Actions panel
7 In the middle panel under the IIS section choose SSL Settings
8 In the SSL Settings screen select the Require SSL checkbox
9 In the Actions panel choose to Apply these settings
To test the SSL connection in the Actions panel choose the Browse [1] 443 (https) link
347 Using Client Certificates
To enable the use of client certificates in Planning and Consolidation you must follow several manual steps
NotePlanning and Consolidation supports client certificate authentication in Windows Authentication Mode butdoes 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 technetmicrosoftcomen-uslibrarycc753810aspx
For more information about configuring the client certificate mapping authentication see technetmicrosoftcomen-uslibrarycc732996(WS10)aspx
When you create the client certificates you can set the type of certificate in the SSL Settings screen in InternetInformation Services (IIS) Manager
Procedure
1 Set the options for client certificates
1 In the IIS Manager select the web site where you installed Planning and Consolidation
2 Choose SSL Settings
3 In the Client certificates section select the Accept client certificates option
This option allows you to use a client certificate or username and password (Basic authentication) toconnect 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 theManagementConsole home page
3 Double-click Authentication and enable Anonymous Authentication
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 35
4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way asin step 3
5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the sameway 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
348 Configuring MS SQL Server Reporting Services to useSSL
Procedure
The procedure below describes how to configure the use of SSL in Microsoft SQL Server Reporting Services
NoteReporting Services does not provide functionalities for generating requesting or installing a certificate Theserver certificates that you want to use for configuring SSL must have already been installed on your computer
1 Open the Reporting Services Configuration Manager program To do this open the Windows Start menu andnavigate to All Programs Microsoft SQL Server ltversiongt Configuration Tools Reporting ServicesConfiguration Manager
2 In the Connect panel on the left-hand side select the Web Service URL option to open all the Report Server webservice parameters
3 Configure the parameters as follows
SSL Certificate = the name of the certificate that you want to use
SSL Port = 4434 Choose Apply to confirm the changes
5 In the Connect panel choose Report Manager URL to open the list of parameters that link Reporting Servicesto IIS
6 Choose Advanced to add your new SSL web URL
7 In the section Multiple SSL Identities for Report Manager choose Add Configure the parameters as follows
IP Address = (All IPv4) SSL Port = 443 Certificate = the name of your SSL certificate
8 To test the configuration click the URL that appears under the Report manager Site Identification section
36
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
4 Installing Planning and ConsolidationAdministration Client and the SAPBusinessObjects EPM solutions Add-in forMicrosoft Office
The installation of the Planning and Consolidation Administration Client allows administrators to build and maintainPlanning and Consolidation environments and models and administer security
All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions add-in forMicrosoft 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 valueof the Planning and Consolidation client to prompt for user name and password Otherwise the Planning andConsolidation Start Page does not display
41 Installing the Administration Client
Prerequisites
NoteFor a definitive list of system requirements see the Product Availability Matrix on SAP Service Marketplace atservicesapcompam Search on Planning and Consolidation
The following list describes the minimum software requirements
Microsoft Internet Explorer 70 80 90 or 10
Microsoft Office 2003 2007 2010 or 2012
NET Framework 20 or higher (install any required NET Framework Hotfixes by referring tosupportmicrosoftcomkb)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 37
NoteWe recommend that you install all of the latest Microsoft Windows hotfixes prior to installing the Administrationclient For information about which hotfixes to install see updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us
Procedure
The 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 ltPC_serverportgtsapbpcweb
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 mustdownload the most recent version of the full setup (EPM Add-inexe) from the Service Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPCInstallation folder
Individual users can install the EPM add-in on their own machines by going to the Planning and Consolidation Homepage 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 upthe 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
38
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
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 toperform the upgrade If Client Auto Update is not enabled and a newer version is detected clients must be installedmanually 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 andpassword in the Admin ID and Admin password fields respectively The Admin ID should be a member of thelocal administrators group on all the computers running the auto update This setting is not needed if all usershave 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 Thisoption is stored in the user preferences and may also be turned on or off using the User Optionshellip menu itemIf 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 toinstall 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 installit 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 servicesapcom
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 versionand policy information For a support package these files are
EPM Addin Support Package ltSP versiongtmsp EPM Addin Support Package ltSP versiongtxmlFor a patch these files are
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 (WebsrvrWebBPCInstallation)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 39
You can set a different update policy for each package listed
ExampleThe following table illustrates some possible situations assuming that you have installed the first full version(V1)
Table 10
Available maintenancepackages
V2-user update
V3-force update
V4-force update
V5-user update
V5-user update V5-user update
V6-auto update
V7-force update
Minimum RequiredVersion
V4 V4 V7
Notification A prompt tells the user toinstall maintenancepackage V4 using theForced Update behavior
If User Update is enabledthe prompt informs theuser that maintenancepackage V5 is available
A prompt tells the user toinstall maintenancepackage V7 using theForced Update behavior
New Version V4 V4 or V5 V7
If you change the update policy for any package click Update to complete the change
40
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
5 Connection Issues
You may experience connection problems with ports the proxy server or programs and settings that interact withthese components If you have any issues related to connection review the following recommendations andtroubleshooting tips
51 Checking for Open Ports
You must ensure that all required ports are open for inboundoutbound traffic By default Planning andConsolidation requires that Ports 80 (used by http) and 1433 and 2383 (used by SQL Server 2008) are open Totest whether the required ports are open go to a command prompt and enter the Telnet serveripaddress and portFor example Telnet 431181836 80 If the system returns a blank command window the port is open If it returnsa message stating that it is unable to connect the port is not open
NoteYou can use the following site to scan for the normal ports It allows you to manually enter a port number to test
wwwmyserverorgportsniffasp
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 Planningand Consolidation server as an exception You can do this at the client level ( Internet Explorer ToolsInternet 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 fullyqualified 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 Consolidationauthentication Do not use authentication on the proxy server The system synchronizes the user name andpassword on the remote server with the local user name and password
SAP Business Planning and Consolidation 100Connection Issues
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 41
NoteFor more information about setting up an ISA proxy server contact SAP Support to request a copy of Setting upISA Proxy Server White Paper For more information about Business Planning and Consolidation firewall portssee SAP Note 1505250
Internet Explorer Settings Issues
Internet Explorer settings must be set correctly to prevent errors and problems when you attempt to access thePlanning 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 insertthe IP address or fully qualified server name of the Planning and Consolidation server as an exception bychoosing 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
42
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Connection Issues
6 Installing Planning and Consolidation withTwo Active Directory Domains
To set up a Planning and Consolidation 10 application server in a hosted environment and use your own domainusers follow this procedure In general you install Planning and Consolidation on the host domain use the hostdomain account and assign it to the Planning and Consolidation users SysAdmin Admin and Users Then you acceptone 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 andpassword 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 topromote 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 privilegefor the Planning and Consolidation server
5 Install Planning and Consolidation and assign your domain account either to the three Planning andConsolidation administrative users SysAdmin Admin and Users or to only one of the three Planning andConsolidation administrative users and to three of your users Be sure you use your own user account ratherthan host domain users
Planning and Consolidation impersonation can then access your domain from the host environment becauseit has the privilege of your domain account
SAP Business Planning and Consolidation 100Installing Planning and Consolidation with Two Active Directory Domains
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 43
7 Installing Planning and Consolidation in aTerminal Services or Citrix ServerDeployment
This section describes best practices and instructions for installing Planning and Consolidation in a Terminal Servicesor Citrix Server deployment
71 Terminal Services Home Directories
We recommend using Terminal Server home directories rather than using the userrsquos profile directory The profiledirectory downloads a minimal amount of information about the dimensions of the environment you are logging onto and may be as large as 2 MB per user The profile directory is on the system drive and has limited space Byspecifying 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 individualserver 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 clientserver (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
44
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
Procedure
The following steps outline how to install the Planning and Consolidation clients in a Terminal Services (TS) or CitrixServer deployment
1 Make sure the Terminal Services or Citrix Server machine has the system requirements installed
2 Log on to the Terminal Services or Citrix Server machine with a user ID that has the rights to install on thatserver
3 At a command prompt enter Change userinstall
4 Open a browser and connect to the URL ltPC_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_MSBPCAdminMainexe
74 Creating a Shortcut to the Launch Page
Procedure
If you use published desktops instead of published applications the Planning and Consolidation desktop file (whichis installed on the current userrsquos desktop) must be moved to the All UsersDesktop folder
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 45
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 SQLServer 2012 support the remote modification of SSIS packages Planning and Consolidation also supports theremote 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 whichyou want to modify SSIS packages
These custom tasks reference dlls that connect to the database server and perform certain validation when usersset up the parameters of each task All the custom task reference components must also be installed in the machineon which you want to modify SSIS packages
We provide a program that registers all the reference components of the custom tasks This section explains theinstallation 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 ndash This folder contains all the dlls that should be installed on the machine There are Planning andConsolidation platform components and all of the Data Manager custom task files
Config folder ndash This folder contains only one file named Filelistxml and lists all of the files that should be installedIf you need to add or remove certain components from the installation you can modify this xml file
OSoftSetupexe ndash This is the main executable file to run the installation package
NoteIf you are not installing SSIS Custom Tasks on your client machine ndash specifically a machine other than the Planningand Consolidation application server ndash you must first install OSoftSSIS2008_Client or OSoftSSIS2012_Client onthe client machine followed by the SQL Server version If you want to use SQL 2008 Tasks under the SQL 2012environment you must install OSoftSSIS2008_Client on the application server For detailed information see SAPNote 1707410 You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package byextracting OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPCInstallation folder on the Planning and Consolidation server To modify SSIS packages on the Planning andConsolidation application server you need to install OSoftSSIS2008_Client or OSoftSSIS2012_Client for creatinga COM+ application For more information see Before You Modify the SSIS Packages [page 49] and Setup ofa COM+ Application on the Application Server [page 50]
Bin folder
This folder contains the following components
46
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Table 11
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012respectively
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
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 47
Name Remark
BPCWriteBackdll
InteropDTSdll
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 addmore components to the installation package you can copy the new components into the Bin folder and add theproper xml tags in FileListxml You need to enter information for the following tags
RegistType ndash This is the registration information of the component You can enter the following values
RegAsm ndash For NET component
48
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Regsvr32 ndash For VB6 component
Gacutil ndash For NET Framework component that should be registered into Global Assembly Cache
FileName ndash Component file name
OSoftSetupexe
This is the executable file to run the SSIS installation package Double-click the file to start the installation You needto enter information for the following fields
Set SQL server
Specify the SQL server name If your SQL Server has an instance specify the instance name
NoteIf you installed the OSoftSSIS2008_Client or OSoftSSIS2012_Client on the application server the SQL servername is automatically disabled
Set server credential
This is the credential name of the COM+ package component Enter the user ID and password that can accessyour SQL Server This should be either the System Admin ID or Admin ID that was registered as a COM+ userwhen 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 ifyou 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 packagesremotely This is also true for the application server that has SSIS installed The Planning and ConsolidationData Manager has the following custom tasks
Table 12
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008and 2012 respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and2012 respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012respectively
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 49
Name Remark
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and2012 respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008and 2012 respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL2008 and 2012 respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and2012 respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012respectively
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
ltdrivegtWebsrvrbin2 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 FilesMicrosoft SQLServer paste all files into the CProgram Files (x86)Microsoft SQL Server100DTSTasksfolder
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
50
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Typographic Conventions
Table 13
Example Description
lt gt Angle brackets indicate that you replace these words or characters with appropriate entries tomake entries in the system for example Enter your ltUser Namegt
File Save Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
Example Textual cross-references to an internet address for example wwwsapcom
example Quicklinks added to the internet address of a homepage to enable quick access to specificcontent 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 titlespushbutton 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 namesof installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transactioncodes database table names and key concepts of a programming language when they aresurrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
SAP Business Planning and Consolidation 100Typographic Conventions
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 51
52
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
wwwsapcom
Material Number
- SAP Business 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 2008 R2 2012 or 2012 R2
- 344 Removing Default Access to the Console
- 345 Management Console Access Control
- 346 Configuring Planning and Consolidation to use SSL
- 347 Using Client Certificates
- 348 Configuring MS SQL Server Reporting Services to use SSL
-
- 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
-
Document History
The following table provides an overview of the most important document changes
Table 1
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 SingleServerrdquo
Added 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 recommendationto 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 recommendinstalling Microsoft Office on the application server Also removed the note at the end of theprocedure that discussed launching the installation of a Microsoft ACE OLEDB Provider on amachine 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 andConsolidation NET Application Serversrdquo
137 2012-06-13 Updated NET 20 to NET 40 in the topic ldquoConfiguring the Planning and Consolidation NETApplication Serversrdquo
138 2012-10-17 Improved the installation procedure in the topic ldquoInstalling on a Single Serverrdquo
139 2012-12-05 Changes in the topics ldquoPrerequisitesrdquo and ldquoInstalling the Prerequisites ndash Basic Stepsrdquo mdashupdated the required version of Microsoft Visual C++ and vcredist_x64exe
14 2013-04-30 Updated the topic Installing the Administration Client [page 37] with versions of MicrosoftInternet Explorer and Microsoft Office supported as of support package 10
15 2013-09-09 Updated the topic ldquoSAP Notes for the Installationrdquo with the central note number for supportpackage 11
16 2013-10-17 Updated the topic Proxy Server and Firewall Issues [page 41] with a note to refer to SAP Note1505250 for information about firewall ports
165 2014-01-10 Updated the topic ldquoSAP Notes for the Installationrdquo with the central note number for supportpackage 12
17 2014-04-02 Added topics about configuring SSL in IIS and in SQL Server Reporting Services
18 2014-08-08 For support package 14
4
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Document History
Version Date Description
Updated the topic ldquoImportant SAP Notesrdquo with the central note number for supportpackage 14
In the topic Prerequisites [page 11] added Windows 2012 to the list of possibleoperating systems and added IIS 80 IIS 85 NET 35 and NET 45 to OtherRequirements
Updated the topic Setting Up an ODBC Data Source in Windows Server 2008 2008R2 [page 32] to include Windows 2012
SAP Business Planning and Consolidation 100Document History
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 5
Content
1 Introduction 911 SAP Notes for the Installation 912 Naming Conventions 10
2 Installing Planning and Consolidation Servers 1121 Basic Steps 1122 Prerequisites 1123 Before Starting the Planning and Consolidation Server Installation 1324 Logging on to Servers 1425 Service-level Accounts 1526 Standard and Advanced Settings 1627 Installing the Prerequisites 17
Installing the Prerequisites ndash Basic Steps 17 Installing the Operating System 19 Installing the SQL Server 19 Installing Analysis Services 23 Installing the Anti-Cross Site Scripting Library 23
28 Installing on a Single Server 2429 Installing the Server in a Multiserver Configuration 25
3 After Installing Planning and Consolidation Servers 2731 Post-Installation Steps 2732 Connecting to Solution Manager Diagnostics 2833 Configuring the Planning and Consolidation NET Application Servers 2934 Post-Installation Optional Configuration Steps 29
Enabling the Management Console 30 Setting Up ODBC Logging in IIS for the Default Web Site 30 Setting Up an ODBC Data Source in Windows Server 2008 2008 R2 2012 or 2012
R2 32 Removing Default Access to the Console 32 Management Console Access Control 33 Configuring Planning and Consolidation to use SSL 34 Using Client Certificates 35 Configuring MS SQL Server Reporting Services to use SSL 36
4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjectsEPM solutions Add-in for Microsoft Office 37
41 Installing the Administration Client 3742 Installing the EPM Add-in 3843 Using the Client Auto Update Program 38
5 Connection Issues 4151 Checking for Open Ports 4152 Proxy Server and Firewall Issues 41
6
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Content
6 Installing Planning and Consolidation with Two Active Directory Domains 43
7 Installing Planning and Consolidation in a Terminal Services or Citrix ServerDeployment 44
71 Terminal Services Home Directories 4472 System Requirements 4473 Installing Planning and Consolidation 4474 Creating a Shortcut to the Launch Page 45
8 Installing SSIS Custom Tasks 4681 Composition of SSIS Custom Task Installation 4682 Before You Modify the SSIS Packages 4983 Setup of a COM+ Application on the Application Server 50
SAP Business Planning and Consolidation 100Content
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 7
8
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
1 Introduction
The SAP BusinessObjects Planning and Consolidation Installation Guide is intended for System Administrators whoperform Planning and Consolidation server and Administration client installations It contains everything you needto 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 releasewe provide detailed instructions on how to migrate your existing environments For more information see theUpgrade Guide which is available on SAP Service Marketplace at servicesapcominstguidesEPM-BPC Planningand Consolidation 100 version for the Microsoft platform
For more information about the Planning and Consolidation Office client software see the SAP BusinessObjects EPMsolutions 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 FileOLAP 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 2008or Windows Server 2008 R2 for remote desktop access
Planning and Consolidation no longer requires a separate Web server only an application server You can installthe application server on a single machine or on multiple machines with network load balancing (NLB) If youuse 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 informationon the installation as well as corrections to the installation documentation Make sure that you have the up-to-dateversion of each SAP Note which you can find in the SAP Service Marketplace at the Internet addressservicesapcomnotes
Table 2
SAP Note Number Title Comments
1584890 Documentation Addendum Contains information that does not yet appear in theapplication help of Business Planning and Consolidation100 version for the Microsoft platform Application helpis available at helpsapcombopacms100
2000499 Business Planning amp Consolidation 10 forMicrosoft SP14 Central Note
This note contains important information about theinstallation of support package 14
SAP Business Planning and Consolidation 100Introduction
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 9
SAP Note Number Title Comments
1961655 Business Planning amp Consolidation 10 forMicrosoft SP13 Central Note
This note contains important information about theinstallation of support package 13
1897745 Business Planning amp Consolidation 10 forMicrosoft SP12 Central Note
This note contains important information about theinstallation of support package 12
1846917 Business Planning amp Consolidation 10 forMicrosoft SP11 Central Note
This note contains important information about theinstallation of support package 11
1804918 Business Planning amp Consolidation 10 forMicrosoft SP10 Central Note
This note contains important information about theinstallation of support package 10
1755355 Business Planning amp Consolidation 10 forMicrosoft SP09 Central Note
This note contains important information about theinstallation of support package 9
1733053 Business Planning amp Consolidation 10 forMicrosoft SP08 Central Note
This note contains important information about theinstallation of support package 8
1689792 Business Planning amp Consolidation 10 forMicrosoft SP07 Central Note
This note contains important information about theinstallation of support package 7
1665656 Business Planning amp Consolidation 10 forMicrosoft SP06 Central Note
This note contains important information about theinstallation of support package 6
1643037 Business Planning amp Consolidation 10 forMicrosoft SP05 Central Note
This note contains important information about theinstallation of support package 5
1620464 Business Planning amp Consolidation 10 forMicrosoft SP04 Central Note
This note contains important information about theinstallation of support package 4
1601213 Business Planning amp Consolidation 10 forMicrosoft SP03 Central Note
This note contains important information about theinstallation of support package 3
1591848 Business Planning amp Consolidation 10 forMicrosoft SP02 Central Note
This note contains important information about theinstallation of support package 2
1573539 Business Planning amp Consolidation 10 forMicrosoft SP01 Central Note
This note contains important information about theinstallation of support package 1
12 Naming Conventions
In this document the following naming conventions apply
Table 3
Variable Description
ltPC_serverportgt Server name or IP address and port number of SAP Planningand Consolidation application location
ltdrivegt The drive where SAP Planning and Consolidation is installed
The default for this is CPC_MS
10
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Introduction
2 Installing Planning and ConsolidationServers
This section includes the basic steps for installing a Planning and Consolidation server the prerequisites and whatto 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 atservicesapcominstguidesepm-bpc 100 version for the Microsoft platform
2 Perform the tasks in the Before Starting the Planning and Consolidation Server Installation [page 13] sectionincluding installing all prerequisites
3 From the application server install the Planning and Consolidation server See Installing Planning andConsolidation on a Single Server [page 24]
NoteYou must install both Planning and Consolidation 100 as well as the most recent Planning and Consolidation100 Support Package available from the SAP Service Marketplace at servicesapcomswdc SoftwareDownloads Support Packages and Patches A - Z Index B SAP BPC FOR MICROSOFT SBOP PC 100FOR MICROSOFT Comprised Software Component Versions SAP CPM BPC 100 M Windows Server onx64 64bit
4 If you have multiple machines see Installing the Server in a Multiserver Configuration [page 25]
5 Perform the steps in the section After Installing Planning and Consolidation Servers [page 27]
22 Prerequisites
The following table describes the software you need to install before installing the Planning and Consolidation serverand the minimum versions required
NoteA list of the supported operating systems and database systems is also available in the Product Availability Matrixon SAP Service Marketplace at servicesapcompam Search on Planning and Consolidation
Table 4
Component Minimum Requirement
Operating System The requirements outlined below are for the following operating systems
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 11
Component Minimum Requirement
Windows Server 2008 (64-bit) Standard Enterprise or Data Center with or withoutHyper-V
Windows Server 2008 R2 (64-bit) Foundation Standard Enterprise or DataCenter with or without Hyper-V
Windows Server 2012 (64-bit) Standard Data Center
Windows Server 2012 R2 (64-bit) Standard Data Center
NoteThe operating system must be configured with NTFS
Relational Database Microsoft SQL Server 2008 Enterprise Edition
Microsoft SQL Server 2008 R2 (Gemini) Enterprise Edition
Microsoft SQL Server 2012 Enterprise Edition
OLAP Database Microsoft SQL Server 2008 Enterprise Edition ndash Analysis Server
Microsoft SQL Server 2008 R2 Enterprise Edition ndash Analysis Server
Microsoft SQL Server 2012 Enterprise Edition ndash Analysis Server
Data Integration Microsoft SQL Server 2008 Enterprise Edition ndash SQL Service Integration Services
Microsoft SQL Server 2008 R2 Enterprise Edition ndash SQL Service IntegrationServices
Microsoft SQL Server 2012 Enterprise Edition ndash 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
NET 35 and NET 45 are required for Windows 2012 and 2012 R2
NET 40 is required for all other operating systems
IIS
IIS 75 or IIS 70
(Included in your Operating System IIS 75 is required for Windows 2008 R2editions)
IIS 80 or IIS 85
(Included in your Operating System IIS 85 is required for Windows 2012 R2editions)
Anti-Cross Site Scripting Library 42
This component must be downloaded before installing the server The serverinstallation program asks for the path of each file and copies the files into theappropriate Planning and Consolidation path
Microsoft Visual C++ 2010 SP1 Redistributable Package (x64)
Microsoft Access Database Engine 2010 64bit
12
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
Component Minimum Requirement
VMWare ESX 3x or ESX 40
(Required only if a landscape deployment strategy using virtualizationtechnologies is planned)
NoteMSXML 40 SP2 ADOMDNET 100 and Microsoft Visual C++ 2010 SP1Redistributable Package (x64) are included with the installation program but notinstalled 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 values being returned withcalculated accounts For more information see SAP Note number 1429246 which also contains downloadinformation
We recommend SQL Server 2008 (or R2) Enterprise Edition or SQL Server 2012 Enterprise Edition for theOLAP database to support proactive cache and cube partitioning It is technically possible to use SQL Server2008 (or R2) Standard Edition or SQL Server 2012 Standard Edition for data integration servers but we donot recommend this
23 Before Starting the Planning and Consolidation ServerInstallation
You must perform the following tasks before starting your Planning and Consolidation server installation
Install all the prerequisite software including all of the latest Microsoft hotfixes For more information seeInstalling the Prerequisites [page 17]
If you access your application through a firewall verify with your network administrator which TCP ports tochoose during the installation By default port 80 is the setting for standard http access and port 443 is thesetting for https access If you require a service to listen on a different port you can specify it during theinstallation 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 onwhich 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 Consolidationand automatically overwrites the previous version If you have made any modifications to EnvironmentShellthat 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 ScriptBlocking
If a version of Planning and Consolidation on a NetWeaver platform exists uninstall it before you install Planningand Consolidation 100 version for the Microsoft platform
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 13
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 enterconvert c fsntfsV
All servers in a multiserver environment must be members of the same domain
In a multiserver environment the installing ID must be a domain user ID We recommend that you do not logon to the servers using a local server user ID even if the user ID is a member of the Administrator group on theserver This way you have the proper authority to install software and to modify the Component Services SeeLogging On to Servers [page 14]
You must determine the IP addresses or server names for all servers before installing Planning andConsolidation 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 portaccess reasons (DMZ WORKGROUP or nontrusted domain authentication failures) do the following
1 Copy the EnvironmentShell database file ServerEnvironmentShelldb10 from the Planning andConsolidation 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 theEnvironmentShell database file in the Server Information Advanced Options Local path forEnvironmentShell DB field (for example cEnvironmentShelldb10)
Install the Anti-Cross Site Scripting Library which provides protection to Web-based applications againstCross-Site Scripting (XSS) attacks See Installing the Anti-Cross Site Scripting Library [page 23]
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 theAdministrator group of a domain to which the server belongs or a member of the Administrator group on the localserver
Errors may display during the installation program and in the diagnostic program if the installing user is not assignedto the Administrator group directly but is assigned to a group with Administrator rights You can ignore thesemessages
NoteIf you change the password used to install Planning and Consolidation you must change the password for theapplicable Planning and Consolidation service To do this go to Server Manager on the application server andselect Server Reset Logon Credentials For more information see the SAP Planning and ConsolidationOperations Guide in servicesapcominstguidesepm-bpc 100 for the Microsoft Platform SBOP Plan amp Consol100 MS Administrators Guide
14
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
25 Service-level Accounts
Service accounts are Windows domain IDs with access to all Planning and Consolidation servers with varying levelsof privileges They allow the software to use the minimum amount of privilege required for each job making it moresecure
You must define these user IDs on the Windows machine For security purposes they should not be used to definePlanning and Consolidation users
Prerequisites
Planning and Consolidation 100 has the following Windows services
BPC SendGovernor which manages Microsoft Analysis Service locks to ensure consistent performance andavoid deadlocks
BPC ServiceManager which manages the System Landscape Directory (SLD) service logging service andglobal caches
BPC CTS ServiceManager which listens and handles CTS import requests from the CTS+ transportmanagement system
Since these services should be able to access to the FileShare server an Admin account is assigned automaticallyto the service during the installation of the Planning and Consolidation server program Even though an Adminaccount 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 serviceon the local machine This logon right strictly applies only to the local computer and must be granted in the LocalSecurity Policy
To edit the Local Security Policy of the computer you want to define the logon as a service permission performthe 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 supportmicrosoftcomkb259733
Features
During the installation enter user IDs and passwords for the following user types
System Admin ID
This ID is read-only and is the same as the installation user ID that is the system displays the ID on theinstallation screen but you cannot modify it This ID allows access to code that provides system administrator-level functionality For example this ID can write to the Windows registry has full access to the FileShare server
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 15
and can create remove backup and restore OLAP and SQL databases The system administrator should be amember 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 createsubdirectory access on the FileShare server readwrite metadata and application set database data in OLAPand can create and remove tables in SQL The Administrator should be a member of the domain users groupand 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 theservers has write access to FileShare data and can read metadata and data in OLAP and SQL The User IDmust 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 isinstalled you can change these settings using the Server Manager
NoteWhen defining server names the name refers to the NetBIOS name IP address and fully qualified domain names(FQDN)
Standard Settings
Standard settings are typically used for a single-server environment The following table describes each setting
Table 5
Server Option Value Description
SQL Database server name The name of the SQL DB server
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 computername
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
Table 6
Server Option Value Description
SQL Server Name The name of the SQL DB server Defaults to the local server
Instance name The SQL instance name If left blank the default instance is used
16
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
Server Option Value Description
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 computername
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 forhttp and 443 is the default for https
Authentication type Note If you have chosen SAP BusinessObjects User Management System in theinstallation screen Authentication type does not appear in Advanced settings (asthat IIS authentication type is Anonymous in CMS mode)
Windows or Kerberos The default is Windows If you change this value fromWindows to Kerberos you must make some additional changes
See the Kerberos authentication settings section in the SAP Library ServerManager Guide on servicesapcominstguidesEPM-BPC 100 for theMicrosoft Platform
Scheduler Server Name The name of the server used for scheduling usually the application server forexample GMPV50072862B If you have multiple application servers select theappropriate one
NoteIf the primary server stops working you must manually configure yourapplication 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 theoperating system IIS SQL server analysis services ADOMDNET and MSXML This section provides guidance on
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 17
installing each component For specific versions required see Prerequisites [page 11] and the Product AvailabilityMatrix on the SAP Service Marketplace at servicesapcompam Search on Planning and Consolidation
NoteTo ensure a successful installation you must install the software in the order listed in this procedure
Check all third-party infrastructure services to ensure that they are functioning and that their authenticationmodels 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 itsown 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 applicationserver before you start the installation You can find the UMC installation package (UMCexe) on the Planningand Consolidation CD in a folder called UMC_100_INSTALLER When you run the installation package the wizardguides 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 andConsolidation)
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 multiserverconfiguration See Installing the Operating System [page 19]
3 Install the latest service pack for your operating system To install this service pack go towwwmicrosoftcom
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 SQLServer [page 19]
6 From your SQL Server media install Analysis Services Enterprise Edition and its required service packs and hotfixes See Installing Analysis Services [page 23]
7 On your application server install ADOMDNET The Planning and Consolidation zip file contains theADOMDNET 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 followinglocation BPC SetupServermsxmlmsi
18
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
9 On your application server install Microsoft Visual C++ 2010 SP1 Redistributable Package (x64)
The Microsoft Visual C++ 2010 SP1 Redistributable Package (x64) installation package is contained in thePlanning and Consolidation zip file at the following location BPC SetupServervcredist_x64exe
NoteThe version of vcredist_x64exe in BPC SetupServer has been updated to 10040219 If you have aprevious 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 wwwmicrosoftcomdownloadsendetailsaspxFamilyID=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 Marketplaceat servicesapcompam Search on Planning and Consolidation
Business Planning and Consolidation can support all servers with an operating system in any language
NoteCurrently Business Planning and Consolidation does not support an operating system in bi-directionallanguages such as Hebrew
Procedure
If you are installing IIS 70 75 80 or 85 you must enable the following features
Enable Basic Authentication and Windows Authentication these are not installed by default
Install IIS 6 Metabase Compatibility role
Business Planning and Consolidation uses the ADSI provider to handle IIS administration such as virtualdirectory and security but IIS 7 does not install the ADSI provider by default
273 Installing the SQL Server
Prerequisites
During the installation procedure you have the opportunity to specify the location of the EnvironmentShell databasefile Check that it is possible to access EnvironmentShell from the location where you intend to install the SQL serverIf it is not possible for port access reasons (DMZ WORKGROUP or nontrusted domain authentication failures) copyEnvironmentShell to a location on the SQL server (for example CEnvironmentShelldb10) You specify thislocation on the Server Information page by choosing Server Information Advanced Options Local Path forEnvironmentShell DB
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 19
Procedure
This section describes the general steps for installing the SQL Server component options and considerations wheninstalling 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
NoteIf you encounter a 500 HTTP Error when trying to connect to the Planning and Consolidation Web Client referto Microsoft Support articles 2520479 and 2468871 for assistance
To reinforce security we recommend that you install the SQL server and SSAS components to a nondefaultinstance 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 Optionssection below then choose Next
4 Review disc space requirements then choose Next
5 In Server Configuration Perform the following actions
1 In the Service Accounts tab enter a Planning and Consolidation sysadmin account for the SQL ServerDatabase Engine and the SQL Server Analysis services This is required so that the Planning andConsolidation sysadmin can create and process the Planning and Consolidation database because theMicrosoft SQL server tries to back up or restore database with the privileged account This account is alsorequired 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 differentdomain 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 theapplication server and the account requires the folder access privilege for the application server
To ensure that you have the complete access privileges we recommend the Planning and Consolidationsysadmin 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 touse a restrictive SQL ID that works with the drill-through feature If you must restrict SQL authentication forsecurity 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 installationprogram
20
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
8 Choose Install to begin the installation with the options you have set
SQL Server Component Options
For Single-Machine Installations
Install the following components from the Feature Selection screen
Database Engine Services
Analysis Services
Integration Service which is listed as one of the Shared Features
For Multiple Machine Installations
For multiple machine installations install the following components on each server
Table 7
Server Component What to Install
SQL Server Database Engine Services
SSAS Server Analysis Services
Application Server The following Shared Features
Client Tools Connectivity
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 Server2008 R2 and SQL Server 2012
Process Dimension
It is now possible to process a dimension with multiple selections At processing time the process dimension modulemakes changed or added information for each dimension and process for all selected dimensions and cubes inparallel
Optimize Model
If there are custom partitions for a FACT partition in the OLAP database an optimization module can process custompartitions in parallel when Full or Incremental Optimize is performed However if a full optimize is performed withthe 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 parallelbecause 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 applicationserver and application set databases
NoteSetting the SQL isolation level to be Read Committed Snapshot mode for a database can only be done once andcannot be reversed
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 21
Real Time MOLAP
You can set the OLAP storage model of the write-back partition to be MOLAP (Multidimensional OLAP) This settingremains 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 asfollows
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 Servertrade20052008 which you can download from wwwmicrosoftcom (search on ldquoTable Partitioningrdquo to find all relevantarticles)
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 Thebrowser 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 localhostand external network interface machine
3 If you want to use IP1 which indicates Server IP set Enabled to Yes and specify the TCP Port as desired
4 Delete 0 from TCP Dynamic Ports Set IPAll - TCP Ports as desired (for example 1533)
RecommendationWe do not recommend using dynamic ports
In an SQL server the default instance has a listener which listens on a fixed port (TCP port 1433)However for the named instance the port on which the SQL server listens is random and dynamicallyselected when the named instance of the SQL server starts This recommendation prevents any conflictproblems
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 Setthe 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 thatthe user identified as the Log on as user has the sysadmin SQL Server role defined under Server Roles in theSQL Server Management Studio This is required so Analysis Services can process the SQL Server
From SQL Server Management Studio do the following tasks
22
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
1 If you want to use a port with a named instance select the server type Analysis Services select the servername (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 ServerProperties window displays which shows all configurable properties
3 For enhanced security change the default value to your port number (for example 2724) This means thatyou use a fixed port as for the SQL Server option Then choose OK
NoteWe do not support a nondefault port with the default instance in this release If you want to use the defaultinstance do not change the port number
Restart SQL and OLAP
Confirm that the installation has completed successfully by checking that there are no installation relatedproblems on the event viewer You can now install Planning and Consolidation
274 Installing Analysis Services
Procedure
After you install SQL Server and its required service packs and hotfixes you must install SQL Server Analysis Servicesand its required service packs and hotfixes
NoteIf you have migrated your Analysis Services repository to the SQL Server back up the database that contains therepository before installing this release
To install Analysis Services for SQL Server 2008 SQL Server 2008 R2 or SQL Server 2012 follow the steps andguidelines in technetmicrosoftcomen-uslibraryms143219aspx
To avoid slow performance when a user has more than six OLAP databases follow the steps and guidelines in thePerformance Guide for SQL 2008 at wwwmicrosoftcomdownloadsdetailsaspxFamilyID=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 tohave it available for the Planning and Consolidation installation program
1 Download the Anti-Cross Site Scripting Library file AntiXSSLibraryDLL from the Microsoft Web site atwwwmicrosoftcomdownloadendetailsaspxid=28589
2 Save the extracted file locally
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 23
When you install Planning and Consolidation Server a step in the process requires you to identify the path toAntiXssLibrarydll
28 Installing on a Single Server
When you install all Planning and Consolidation server components on a single server you should consider thefollowing 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 theuncompressed 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 Log on to the server with a local server user ID or domain user ID For more information see Logging on toservers [page 14]
3 Make sure all prerequisite software is installed on the server For more information see Installing thePrerequisites [page 17]
4 Obtain SAP Planning and Consolidation archive from the Downloads SAP Installations amp Upgrades areaof SAP Service Marketplace
5 Extract the files from the archive Go to the BPC Setup folder and run the StartUpexe file
6 From the Server Install screen select Install the Planning and Consolidation server
7 From the Welcome screen choose Next
8 From the License Agreement page choose I accept the terms of the license agreement then choose Next
9 From the Installation Method page accept the default Single machine enter a system ID for the systemlandscape directory (SLD) and choose Next
NoteEntering a system ID of the SLD is only required if you have a SAP Solution Manager license If you do nothave a SAP Solution Manager license you can leave this field empty
10 From the Authentication Method page choose the desired authentication method and choose Next
11 If you have chosen SAP BusinessObjects User Management System in the previous screen on the CMSAuthentication page enter the information required to log on to CMS as an administrator
The following information is required
24
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
Table 8
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 Thisgroup name is filtered as the default when adding a user in Planning andConsolidation Administration Use a comma ( ) to separate multiple names
12 After entering the CMS administrator authentication details choose Next
13 From the Service type accounts page enter service-level account user IDs and passwords See Service-LevelAccounts [page 15]
14 After defining the IDs and passwords choose Next
15 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 chooseNext
16 Specify the location and name of AntiXssLibrarydll See Installing the Anti-Cross Site ScriptingLibrary [page 23]
Choose Next
17 Select destination folders for Programs and Data The Data files include Webfolders and FileDB (publishedreports) and should be installed on a separate drive in a production environment This recommendation reducesthe hard disk IO time and helps to speed up SQL commands
Accept the defaults or make your selections then choose Next
18 Select the default values for the Web client The values are used to determine the default language and regionfor the Web client when you connect to it You can change the values in the Planning and Consolidation ServerManager
19 The installation process takes a few moments When it is complete choose Exit
20 A prompt is displayed to restart your computer Select OK to restart
21 Perform the steps in After Installing Planning and Consolidation Servers [page 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 avariety of ways and configure the servers as a Network Load Balancing (NLB) environment
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 25
The recommended Planning and Consolidation practice is to assign resources using a round robin approach for loadbalancing
You can install the SQL OLAP and FileShare types remotely from the application server You need to performadditional server installations if you have multiple application servers
Installing each Planning and Consolidation application server in a multiserver (NLB) configuration is identical to theprocedure 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 Balancingenvironment With this option there is an additional choice to Include sample environment (required on only oneof the application servers) This is because when you install the application server it connects to the databaseserver and creates the sample environment (EnvironmentShell) Installing the sample environment is requiredon 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
26
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
3 After Installing Planning and ConsolidationServers
31 Post-Installation Steps
Procedure
Perform these steps after installing the Planning and Consolidation servers for new installations of Planning andConsolidation
1 Connect your Planning and Consolidation system to Solution Manager Diagnostics (SMD) to allow support staffto identify analyze and resolve problems with your application See Connecting to Solution ManagerDiagnostics [page 28]
2 Configure the Planning and Consolidation NET and application server to ensure that it and its related servicesfunction properly and reliably For more information see Configuring the Planning and Consolidation NETApplication Server [page 29]
3 Optional configuration steps [page 29]
1 To ensure proper functioning of the Management Console create an SQL user and modify the System DSNand 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 loggingfor ODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default WebSite [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory canaccess the Management Console with whatever rights they have been granted on the server Forinformation about removing default access and creating a group that can access the console see RemovingDefault Access to the Console [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommendthat you only grant Management Console access to system administrators Planning and Consolidationusers should not have any access For more information see Management Console AccessControl [page 33]
6 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
4 Take the following steps to set up security
If you are defining security and application structure continue with step 5
If you want to designate someone other than the system administrator to manage security and applicationstructure log on to EnvironmentShell designate a user as a Primary Administrator
This user must have Administration ndash Environment and Security ‒ Define User task rights so that he or shecan 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 SeeInstalling the Administration Client [page 37]
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 27
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 taskprofiles 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 mustcomplete this step since there is no access to dimensions or members)
NoteTo allow users to request and query large amounts of data you can edit the metabasexml file located at CWindowssystem32inetsrv Set the following parameters to the stated values
ASPBUFFERINGLIMIT = 10485760
MAXREQUESTENTITYALLOWED = 10485760
32 Connecting to Solution Manager Diagnostics
NoteYou only need to perform the steps in this section if you have a SAP Solution Manager licence
The diagnostics functions in SAP Solution Manager allow identification analysis and resolution of problems Thisprocedure 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 areinstalled
NoteInstallation files for Diagnostics Agent are available on Service Marketplace by navigating to SupportPackages and Patches mdash Entry by Application Group SAP Technology Components SAP SOLUTIONMANAGER SAP SOLUTION MANAGER 70 EHP 1 Entry by Component Agents for managed systemsDIAGNOSTICS AGENT 711
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 whereMicrosoft 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
28
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
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 ServiceMarketplace at servicesapcom~sapidb011000358700000074392009E and follow the chapters that applyto Planning and Consolidation
33 Configuring the Planning and Consolidation NETApplication Servers
Procedure
Modifying machineconfig Files
To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock occurrences that wouldcause the application server to ldquosleeprdquo and not process anymore you can modify the machineconfig file whichresides in the WINDOWSMicrosoftNETFramework64v4030319Config directory
1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to specifywhether to automatically configure settings to achieve optimal performance based on the machineconfiguration You can set this attribute to True or False
For more information see msdnmicrosoftcomen-uslibrary7w2sway1aspx
2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the Planning andConsolidation application) or Machineconfig (for all applications including Planning and Consolidation) toensure the validationKey and decryptionKey keys have the same value on all application servers Thisway when the authentication cookie is checked the authentication ticket used on one server can still be validon another server
For more information and sample Visual Basic code for generating random key values seemsdnmicrosoftcomen-uslibraryms998288aspxpaght000007_webfarmdeploymentconsiderationsand msdnmicrosoftcomen-uslibraryms998310aspx
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 DSNand 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 forODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory can accessthe Management Console with whatever rights they have been granted on the server For information about
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 29
removing default access and creating a group that can access the console see Removing Default Access to theConsole [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommend thatyou only grant Management Console access to system administrators Planning and Consolidation users shouldnot have any access For more information see Management Console Access Control [page 33]
6 Configure the use of SSL in Planning and Consolidation See Configuring Planning and Consolidation to useSSL [page 34]
7 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
8 Configure Microsoft SQL Server Reporting Services to use SSL See Configuring MS SQL Server ReportingServices to use SSL [page 36]
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 databaserole 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 optionto use ODBC Logging Enter the following values
DSN is BPC_ManagementDSN Table is BPCLog The Microsoft SQL Server Username and Password
5 Restart IIS
NoteWithout these updates the Management Console does work but some functionality (specifically User Activityand Service Status) does not work as expected
Should you need to uninstall Planning and Consolidation we recommend that you reset the Active Log Formatfield in IIS to W3C Extended Log File Format
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
30
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
Prerequisites
ODBC logging has been configured according to the Microsoft Knowledge Base article 245243 How to configureODBC 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 inApplicationHostconfig as shown here
ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0logFormat=Custom gtUse 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-00AA006111E0appcmd 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 articlespecified in the Prerequisites section Configure these settings in the ltodbcLogginggt node underltsystemwebServergt
Exampleltlocation path=Default Web SitegtltsystemwebServergtltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog userName=Usernamepassword=mypassword gtltsystemwebServergtltlocationgt
Use the following AppCmds to configure these attributes for the default Web site
appcmd set config Default Web Site sectionodbcLogging dataSourceBPC_ManagementDSN commitappHostappcmd set config Default Web Site sectionodbcLogging tableNameBPCLog commitappHostappcmd set config Default Web Site sectionodbcLogging userNameUsername commitappHostappcmd set config Default Web Site sectionodbcLogging passwordmypassword commitappHost
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 31
NoteYou cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must use the SQL ServerODBC driver For more information see the Microsoft Knowledge Base article 931202 The requirements for usingthe ODBC logging feature in IIS
343 Setting Up an ODBC Data Source in Windows Server2008 2008 R2 2012 or 2012 R2
Procedure
This procedure describes how to set up an ODBC data source for the Management Console in Windows Server 20082008 R2 2012 or 2012 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
NoteIf you have chosen SAP BusinessObjects User Management System in the installation screen you do not needto remove or configure access because the Management Console service always runs with the System Admin IDaccount which is a member of the Administrators group
Procedure
To remove default access to the Management Console and create a group that does have access to the console usethe procedure described below
32
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
NoteCreate your Management Console administrative group either on the server that hosts the Management Consoleor 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
NoteAlternatively you can perform analogous steps in Active Directory
3 In the Groups context menu choose New Group
4 Enter data as required Click Create
5 In the Computer Management dialog box choose Services and Applications Internet InformationServices 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 objectand all child objects Include these with entries explicitly defined here checkbox
NoteThis step is a necessary precursor to the completion of this procedure
10 In the Security dialog box click Copy to ensure that the System group retains its privileges
11 Remove access to the Management Console from all groups that should not have it
12 Choose Authentication in the center pane then disable Windows authentication
Result
Users who have not been granted access to the Management Console can still open the Management Console Webpage but it contains no data or menu options This does not affect the access that a user would otherwise have toPlanning and Consolidation
345 Management Console Access Control
After establishing the Management Console group you can add users or groups to it For more information aboutcreating this group see Removing Default Access to the Console [page 32] Their rights in Active Directory determinewhat they can access in the Console
By default any member of the Administrators Active Directory group on the application server or domain has fullaccess to all of the features of the Console except the Planning and Consolidation logging area Access to Planningand Consolidation logging is controlled within the Planning and Consolidation Administration Client task securityThe user must be granted View system logs task privileges For more information see the SAP Library Planning and
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 33
Consolidation Administrators Guide in servicesapcominstguidesepm-bpc 100 version for the Microsoftplatform
Your IT policy determines whether you grant access by group or user You may wish to create several levels of Consoleusers (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 describedin this table
Table 9
Privilege Rights Management Area
Task Manager and Kill Process Administrators group on application server or domain
Performance Monitor Counters Administrators group on application server or domain
Power Users group on application server or domain
Performance Monitor Users group on application server
Microsoft Analysis Services performance monitoring Administrators group on application server or domain
Microsoft SQL Server Monitoring (performance counters andstatistics)
Administrators group on application server or domain
346 Configuring Planning and Consolidation to use SSL
Procedure
Creating a Certificate for the Server
During the handshake phase of the SSL communication the server must send its certificate to the client The clientthen uses the certificate to encrypt information and send it back to the server
The procedure below describes how to create a self-signed certificate for the server
RecommendationWe recommend that you limit the use of self-signed certificates to testing only For a productive system you shouldobtain a certificate signed by a well-known certification authority (CA)
1 Start the Internet Information Services (IIS) Manager To do that go to Start All Programs AdministrativeTools Internet Information Services (IIS) Manager
2 In the Connections panel on the left-hand side select the server node and then choose Server Certificates
3 In the Actions panel on the right hand side choose the Create Self-Signed Certificate action
4 Enter the name that you want the certificate to be identified by for example MyTestSSLCertificate
IIS generates a new SSL certificate for you that has one yearrsquos expiry lease The certificate is issued to the local servername
Binding the Certificate to the Web Site
The procedure below describes how to bind the certificate to the web site for which SSL connections must be used
1 In the Connections panel select the web site node
2 In the Actions panel choose Bindings
34
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
3 In the Site Bindings dialog that appears choose the Add button to create a new binding
4 Configure the parameters as follows
Type = https IP Address = [1] - this is a shorthand expression for the local server name
Port = 443 - this is the default SSL port
SSL Certificate = enter your newly created certificate name
5 Choose OK to create the new binding and then close the Site Bindings dialog
6 Restart the IIS processes To do this choose Restart from the Actions panel
7 In the middle panel under the IIS section choose SSL Settings
8 In the SSL Settings screen select the Require SSL checkbox
9 In the Actions panel choose to Apply these settings
To test the SSL connection in the Actions panel choose the Browse [1] 443 (https) link
347 Using Client Certificates
To enable the use of client certificates in Planning and Consolidation you must follow several manual steps
NotePlanning and Consolidation supports client certificate authentication in Windows Authentication Mode butdoes 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 technetmicrosoftcomen-uslibrarycc753810aspx
For more information about configuring the client certificate mapping authentication see technetmicrosoftcomen-uslibrarycc732996(WS10)aspx
When you create the client certificates you can set the type of certificate in the SSL Settings screen in InternetInformation Services (IIS) Manager
Procedure
1 Set the options for client certificates
1 In the IIS Manager select the web site where you installed Planning and Consolidation
2 Choose SSL Settings
3 In the Client certificates section select the Accept client certificates option
This option allows you to use a client certificate or username and password (Basic authentication) toconnect 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 theManagementConsole home page
3 Double-click Authentication and enable Anonymous Authentication
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 35
4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way asin step 3
5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the sameway 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
348 Configuring MS SQL Server Reporting Services to useSSL
Procedure
The procedure below describes how to configure the use of SSL in Microsoft SQL Server Reporting Services
NoteReporting Services does not provide functionalities for generating requesting or installing a certificate Theserver certificates that you want to use for configuring SSL must have already been installed on your computer
1 Open the Reporting Services Configuration Manager program To do this open the Windows Start menu andnavigate to All Programs Microsoft SQL Server ltversiongt Configuration Tools Reporting ServicesConfiguration Manager
2 In the Connect panel on the left-hand side select the Web Service URL option to open all the Report Server webservice parameters
3 Configure the parameters as follows
SSL Certificate = the name of the certificate that you want to use
SSL Port = 4434 Choose Apply to confirm the changes
5 In the Connect panel choose Report Manager URL to open the list of parameters that link Reporting Servicesto IIS
6 Choose Advanced to add your new SSL web URL
7 In the section Multiple SSL Identities for Report Manager choose Add Configure the parameters as follows
IP Address = (All IPv4) SSL Port = 443 Certificate = the name of your SSL certificate
8 To test the configuration click the URL that appears under the Report manager Site Identification section
36
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
4 Installing Planning and ConsolidationAdministration Client and the SAPBusinessObjects EPM solutions Add-in forMicrosoft Office
The installation of the Planning and Consolidation Administration Client allows administrators to build and maintainPlanning and Consolidation environments and models and administer security
All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions add-in forMicrosoft 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 valueof the Planning and Consolidation client to prompt for user name and password Otherwise the Planning andConsolidation Start Page does not display
41 Installing the Administration Client
Prerequisites
NoteFor a definitive list of system requirements see the Product Availability Matrix on SAP Service Marketplace atservicesapcompam Search on Planning and Consolidation
The following list describes the minimum software requirements
Microsoft Internet Explorer 70 80 90 or 10
Microsoft Office 2003 2007 2010 or 2012
NET Framework 20 or higher (install any required NET Framework Hotfixes by referring tosupportmicrosoftcomkb)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 37
NoteWe recommend that you install all of the latest Microsoft Windows hotfixes prior to installing the Administrationclient For information about which hotfixes to install see updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us
Procedure
The 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 ltPC_serverportgtsapbpcweb
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 mustdownload the most recent version of the full setup (EPM Add-inexe) from the Service Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPCInstallation folder
Individual users can install the EPM add-in on their own machines by going to the Planning and Consolidation Homepage 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 upthe 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
38
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
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 toperform the upgrade If Client Auto Update is not enabled and a newer version is detected clients must be installedmanually 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 andpassword in the Admin ID and Admin password fields respectively The Admin ID should be a member of thelocal administrators group on all the computers running the auto update This setting is not needed if all usershave 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 Thisoption is stored in the user preferences and may also be turned on or off using the User Optionshellip menu itemIf 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 toinstall 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 installit 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 servicesapcom
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 versionand policy information For a support package these files are
EPM Addin Support Package ltSP versiongtmsp EPM Addin Support Package ltSP versiongtxmlFor a patch these files are
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 (WebsrvrWebBPCInstallation)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 39
You can set a different update policy for each package listed
ExampleThe following table illustrates some possible situations assuming that you have installed the first full version(V1)
Table 10
Available maintenancepackages
V2-user update
V3-force update
V4-force update
V5-user update
V5-user update V5-user update
V6-auto update
V7-force update
Minimum RequiredVersion
V4 V4 V7
Notification A prompt tells the user toinstall maintenancepackage V4 using theForced Update behavior
If User Update is enabledthe prompt informs theuser that maintenancepackage V5 is available
A prompt tells the user toinstall maintenancepackage V7 using theForced Update behavior
New Version V4 V4 or V5 V7
If you change the update policy for any package click Update to complete the change
40
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
5 Connection Issues
You may experience connection problems with ports the proxy server or programs and settings that interact withthese components If you have any issues related to connection review the following recommendations andtroubleshooting tips
51 Checking for Open Ports
You must ensure that all required ports are open for inboundoutbound traffic By default Planning andConsolidation requires that Ports 80 (used by http) and 1433 and 2383 (used by SQL Server 2008) are open Totest whether the required ports are open go to a command prompt and enter the Telnet serveripaddress and portFor example Telnet 431181836 80 If the system returns a blank command window the port is open If it returnsa message stating that it is unable to connect the port is not open
NoteYou can use the following site to scan for the normal ports It allows you to manually enter a port number to test
wwwmyserverorgportsniffasp
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 Planningand Consolidation server as an exception You can do this at the client level ( Internet Explorer ToolsInternet 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 fullyqualified 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 Consolidationauthentication Do not use authentication on the proxy server The system synchronizes the user name andpassword on the remote server with the local user name and password
SAP Business Planning and Consolidation 100Connection Issues
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 41
NoteFor more information about setting up an ISA proxy server contact SAP Support to request a copy of Setting upISA Proxy Server White Paper For more information about Business Planning and Consolidation firewall portssee SAP Note 1505250
Internet Explorer Settings Issues
Internet Explorer settings must be set correctly to prevent errors and problems when you attempt to access thePlanning 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 insertthe IP address or fully qualified server name of the Planning and Consolidation server as an exception bychoosing 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
42
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Connection Issues
6 Installing Planning and Consolidation withTwo Active Directory Domains
To set up a Planning and Consolidation 10 application server in a hosted environment and use your own domainusers follow this procedure In general you install Planning and Consolidation on the host domain use the hostdomain account and assign it to the Planning and Consolidation users SysAdmin Admin and Users Then you acceptone 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 andpassword 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 topromote 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 privilegefor the Planning and Consolidation server
5 Install Planning and Consolidation and assign your domain account either to the three Planning andConsolidation administrative users SysAdmin Admin and Users or to only one of the three Planning andConsolidation administrative users and to three of your users Be sure you use your own user account ratherthan host domain users
Planning and Consolidation impersonation can then access your domain from the host environment becauseit has the privilege of your domain account
SAP Business Planning and Consolidation 100Installing Planning and Consolidation with Two Active Directory Domains
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 43
7 Installing Planning and Consolidation in aTerminal Services or Citrix ServerDeployment
This section describes best practices and instructions for installing Planning and Consolidation in a Terminal Servicesor Citrix Server deployment
71 Terminal Services Home Directories
We recommend using Terminal Server home directories rather than using the userrsquos profile directory The profiledirectory downloads a minimal amount of information about the dimensions of the environment you are logging onto and may be as large as 2 MB per user The profile directory is on the system drive and has limited space Byspecifying 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 individualserver 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 clientserver (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
44
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
Procedure
The following steps outline how to install the Planning and Consolidation clients in a Terminal Services (TS) or CitrixServer deployment
1 Make sure the Terminal Services or Citrix Server machine has the system requirements installed
2 Log on to the Terminal Services or Citrix Server machine with a user ID that has the rights to install on thatserver
3 At a command prompt enter Change userinstall
4 Open a browser and connect to the URL ltPC_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_MSBPCAdminMainexe
74 Creating a Shortcut to the Launch Page
Procedure
If you use published desktops instead of published applications the Planning and Consolidation desktop file (whichis installed on the current userrsquos desktop) must be moved to the All UsersDesktop folder
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 45
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 SQLServer 2012 support the remote modification of SSIS packages Planning and Consolidation also supports theremote 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 whichyou want to modify SSIS packages
These custom tasks reference dlls that connect to the database server and perform certain validation when usersset up the parameters of each task All the custom task reference components must also be installed in the machineon which you want to modify SSIS packages
We provide a program that registers all the reference components of the custom tasks This section explains theinstallation 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 ndash This folder contains all the dlls that should be installed on the machine There are Planning andConsolidation platform components and all of the Data Manager custom task files
Config folder ndash This folder contains only one file named Filelistxml and lists all of the files that should be installedIf you need to add or remove certain components from the installation you can modify this xml file
OSoftSetupexe ndash This is the main executable file to run the installation package
NoteIf you are not installing SSIS Custom Tasks on your client machine ndash specifically a machine other than the Planningand Consolidation application server ndash you must first install OSoftSSIS2008_Client or OSoftSSIS2012_Client onthe client machine followed by the SQL Server version If you want to use SQL 2008 Tasks under the SQL 2012environment you must install OSoftSSIS2008_Client on the application server For detailed information see SAPNote 1707410 You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package byextracting OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPCInstallation folder on the Planning and Consolidation server To modify SSIS packages on the Planning andConsolidation application server you need to install OSoftSSIS2008_Client or OSoftSSIS2012_Client for creatinga COM+ application For more information see Before You Modify the SSIS Packages [page 49] and Setup ofa COM+ Application on the Application Server [page 50]
Bin folder
This folder contains the following components
46
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Table 11
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012respectively
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
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 47
Name Remark
BPCWriteBackdll
InteropDTSdll
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 addmore components to the installation package you can copy the new components into the Bin folder and add theproper xml tags in FileListxml You need to enter information for the following tags
RegistType ndash This is the registration information of the component You can enter the following values
RegAsm ndash For NET component
48
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Regsvr32 ndash For VB6 component
Gacutil ndash For NET Framework component that should be registered into Global Assembly Cache
FileName ndash Component file name
OSoftSetupexe
This is the executable file to run the SSIS installation package Double-click the file to start the installation You needto enter information for the following fields
Set SQL server
Specify the SQL server name If your SQL Server has an instance specify the instance name
NoteIf you installed the OSoftSSIS2008_Client or OSoftSSIS2012_Client on the application server the SQL servername is automatically disabled
Set server credential
This is the credential name of the COM+ package component Enter the user ID and password that can accessyour SQL Server This should be either the System Admin ID or Admin ID that was registered as a COM+ userwhen 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 ifyou 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 packagesremotely This is also true for the application server that has SSIS installed The Planning and ConsolidationData Manager has the following custom tasks
Table 12
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008and 2012 respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and2012 respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012respectively
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 49
Name Remark
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and2012 respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008and 2012 respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL2008 and 2012 respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and2012 respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012respectively
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
ltdrivegtWebsrvrbin2 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 FilesMicrosoft SQLServer paste all files into the CProgram Files (x86)Microsoft SQL Server100DTSTasksfolder
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
50
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Typographic Conventions
Table 13
Example Description
lt gt Angle brackets indicate that you replace these words or characters with appropriate entries tomake entries in the system for example Enter your ltUser Namegt
File Save Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
Example Textual cross-references to an internet address for example wwwsapcom
example Quicklinks added to the internet address of a homepage to enable quick access to specificcontent 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 titlespushbutton 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 namesof installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transactioncodes database table names and key concepts of a programming language when they aresurrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
SAP Business Planning and Consolidation 100Typographic Conventions
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 51
52
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
wwwsapcom
Material Number
- SAP Business 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 2008 R2 2012 or 2012 R2
- 344 Removing Default Access to the Console
- 345 Management Console Access Control
- 346 Configuring Planning and Consolidation to use SSL
- 347 Using Client Certificates
- 348 Configuring MS SQL Server Reporting Services to use SSL
-
- 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
-
Version Date Description
Updated the topic ldquoImportant SAP Notesrdquo with the central note number for supportpackage 14
In the topic Prerequisites [page 11] added Windows 2012 to the list of possibleoperating systems and added IIS 80 IIS 85 NET 35 and NET 45 to OtherRequirements
Updated the topic Setting Up an ODBC Data Source in Windows Server 2008 2008R2 [page 32] to include Windows 2012
SAP Business Planning and Consolidation 100Document History
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 5
Content
1 Introduction 911 SAP Notes for the Installation 912 Naming Conventions 10
2 Installing Planning and Consolidation Servers 1121 Basic Steps 1122 Prerequisites 1123 Before Starting the Planning and Consolidation Server Installation 1324 Logging on to Servers 1425 Service-level Accounts 1526 Standard and Advanced Settings 1627 Installing the Prerequisites 17
Installing the Prerequisites ndash Basic Steps 17 Installing the Operating System 19 Installing the SQL Server 19 Installing Analysis Services 23 Installing the Anti-Cross Site Scripting Library 23
28 Installing on a Single Server 2429 Installing the Server in a Multiserver Configuration 25
3 After Installing Planning and Consolidation Servers 2731 Post-Installation Steps 2732 Connecting to Solution Manager Diagnostics 2833 Configuring the Planning and Consolidation NET Application Servers 2934 Post-Installation Optional Configuration Steps 29
Enabling the Management Console 30 Setting Up ODBC Logging in IIS for the Default Web Site 30 Setting Up an ODBC Data Source in Windows Server 2008 2008 R2 2012 or 2012
R2 32 Removing Default Access to the Console 32 Management Console Access Control 33 Configuring Planning and Consolidation to use SSL 34 Using Client Certificates 35 Configuring MS SQL Server Reporting Services to use SSL 36
4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjectsEPM solutions Add-in for Microsoft Office 37
41 Installing the Administration Client 3742 Installing the EPM Add-in 3843 Using the Client Auto Update Program 38
5 Connection Issues 4151 Checking for Open Ports 4152 Proxy Server and Firewall Issues 41
6
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Content
6 Installing Planning and Consolidation with Two Active Directory Domains 43
7 Installing Planning and Consolidation in a Terminal Services or Citrix ServerDeployment 44
71 Terminal Services Home Directories 4472 System Requirements 4473 Installing Planning and Consolidation 4474 Creating a Shortcut to the Launch Page 45
8 Installing SSIS Custom Tasks 4681 Composition of SSIS Custom Task Installation 4682 Before You Modify the SSIS Packages 4983 Setup of a COM+ Application on the Application Server 50
SAP Business Planning and Consolidation 100Content
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 7
8
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
1 Introduction
The SAP BusinessObjects Planning and Consolidation Installation Guide is intended for System Administrators whoperform Planning and Consolidation server and Administration client installations It contains everything you needto 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 releasewe provide detailed instructions on how to migrate your existing environments For more information see theUpgrade Guide which is available on SAP Service Marketplace at servicesapcominstguidesEPM-BPC Planningand Consolidation 100 version for the Microsoft platform
For more information about the Planning and Consolidation Office client software see the SAP BusinessObjects EPMsolutions 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 FileOLAP 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 2008or Windows Server 2008 R2 for remote desktop access
Planning and Consolidation no longer requires a separate Web server only an application server You can installthe application server on a single machine or on multiple machines with network load balancing (NLB) If youuse 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 informationon the installation as well as corrections to the installation documentation Make sure that you have the up-to-dateversion of each SAP Note which you can find in the SAP Service Marketplace at the Internet addressservicesapcomnotes
Table 2
SAP Note Number Title Comments
1584890 Documentation Addendum Contains information that does not yet appear in theapplication help of Business Planning and Consolidation100 version for the Microsoft platform Application helpis available at helpsapcombopacms100
2000499 Business Planning amp Consolidation 10 forMicrosoft SP14 Central Note
This note contains important information about theinstallation of support package 14
SAP Business Planning and Consolidation 100Introduction
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 9
SAP Note Number Title Comments
1961655 Business Planning amp Consolidation 10 forMicrosoft SP13 Central Note
This note contains important information about theinstallation of support package 13
1897745 Business Planning amp Consolidation 10 forMicrosoft SP12 Central Note
This note contains important information about theinstallation of support package 12
1846917 Business Planning amp Consolidation 10 forMicrosoft SP11 Central Note
This note contains important information about theinstallation of support package 11
1804918 Business Planning amp Consolidation 10 forMicrosoft SP10 Central Note
This note contains important information about theinstallation of support package 10
1755355 Business Planning amp Consolidation 10 forMicrosoft SP09 Central Note
This note contains important information about theinstallation of support package 9
1733053 Business Planning amp Consolidation 10 forMicrosoft SP08 Central Note
This note contains important information about theinstallation of support package 8
1689792 Business Planning amp Consolidation 10 forMicrosoft SP07 Central Note
This note contains important information about theinstallation of support package 7
1665656 Business Planning amp Consolidation 10 forMicrosoft SP06 Central Note
This note contains important information about theinstallation of support package 6
1643037 Business Planning amp Consolidation 10 forMicrosoft SP05 Central Note
This note contains important information about theinstallation of support package 5
1620464 Business Planning amp Consolidation 10 forMicrosoft SP04 Central Note
This note contains important information about theinstallation of support package 4
1601213 Business Planning amp Consolidation 10 forMicrosoft SP03 Central Note
This note contains important information about theinstallation of support package 3
1591848 Business Planning amp Consolidation 10 forMicrosoft SP02 Central Note
This note contains important information about theinstallation of support package 2
1573539 Business Planning amp Consolidation 10 forMicrosoft SP01 Central Note
This note contains important information about theinstallation of support package 1
12 Naming Conventions
In this document the following naming conventions apply
Table 3
Variable Description
ltPC_serverportgt Server name or IP address and port number of SAP Planningand Consolidation application location
ltdrivegt The drive where SAP Planning and Consolidation is installed
The default for this is CPC_MS
10
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Introduction
2 Installing Planning and ConsolidationServers
This section includes the basic steps for installing a Planning and Consolidation server the prerequisites and whatto 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 atservicesapcominstguidesepm-bpc 100 version for the Microsoft platform
2 Perform the tasks in the Before Starting the Planning and Consolidation Server Installation [page 13] sectionincluding installing all prerequisites
3 From the application server install the Planning and Consolidation server See Installing Planning andConsolidation on a Single Server [page 24]
NoteYou must install both Planning and Consolidation 100 as well as the most recent Planning and Consolidation100 Support Package available from the SAP Service Marketplace at servicesapcomswdc SoftwareDownloads Support Packages and Patches A - Z Index B SAP BPC FOR MICROSOFT SBOP PC 100FOR MICROSOFT Comprised Software Component Versions SAP CPM BPC 100 M Windows Server onx64 64bit
4 If you have multiple machines see Installing the Server in a Multiserver Configuration [page 25]
5 Perform the steps in the section After Installing Planning and Consolidation Servers [page 27]
22 Prerequisites
The following table describes the software you need to install before installing the Planning and Consolidation serverand the minimum versions required
NoteA list of the supported operating systems and database systems is also available in the Product Availability Matrixon SAP Service Marketplace at servicesapcompam Search on Planning and Consolidation
Table 4
Component Minimum Requirement
Operating System The requirements outlined below are for the following operating systems
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 11
Component Minimum Requirement
Windows Server 2008 (64-bit) Standard Enterprise or Data Center with or withoutHyper-V
Windows Server 2008 R2 (64-bit) Foundation Standard Enterprise or DataCenter with or without Hyper-V
Windows Server 2012 (64-bit) Standard Data Center
Windows Server 2012 R2 (64-bit) Standard Data Center
NoteThe operating system must be configured with NTFS
Relational Database Microsoft SQL Server 2008 Enterprise Edition
Microsoft SQL Server 2008 R2 (Gemini) Enterprise Edition
Microsoft SQL Server 2012 Enterprise Edition
OLAP Database Microsoft SQL Server 2008 Enterprise Edition ndash Analysis Server
Microsoft SQL Server 2008 R2 Enterprise Edition ndash Analysis Server
Microsoft SQL Server 2012 Enterprise Edition ndash Analysis Server
Data Integration Microsoft SQL Server 2008 Enterprise Edition ndash SQL Service Integration Services
Microsoft SQL Server 2008 R2 Enterprise Edition ndash SQL Service IntegrationServices
Microsoft SQL Server 2012 Enterprise Edition ndash 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
NET 35 and NET 45 are required for Windows 2012 and 2012 R2
NET 40 is required for all other operating systems
IIS
IIS 75 or IIS 70
(Included in your Operating System IIS 75 is required for Windows 2008 R2editions)
IIS 80 or IIS 85
(Included in your Operating System IIS 85 is required for Windows 2012 R2editions)
Anti-Cross Site Scripting Library 42
This component must be downloaded before installing the server The serverinstallation program asks for the path of each file and copies the files into theappropriate Planning and Consolidation path
Microsoft Visual C++ 2010 SP1 Redistributable Package (x64)
Microsoft Access Database Engine 2010 64bit
12
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
Component Minimum Requirement
VMWare ESX 3x or ESX 40
(Required only if a landscape deployment strategy using virtualizationtechnologies is planned)
NoteMSXML 40 SP2 ADOMDNET 100 and Microsoft Visual C++ 2010 SP1Redistributable Package (x64) are included with the installation program but notinstalled 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 values being returned withcalculated accounts For more information see SAP Note number 1429246 which also contains downloadinformation
We recommend SQL Server 2008 (or R2) Enterprise Edition or SQL Server 2012 Enterprise Edition for theOLAP database to support proactive cache and cube partitioning It is technically possible to use SQL Server2008 (or R2) Standard Edition or SQL Server 2012 Standard Edition for data integration servers but we donot recommend this
23 Before Starting the Planning and Consolidation ServerInstallation
You must perform the following tasks before starting your Planning and Consolidation server installation
Install all the prerequisite software including all of the latest Microsoft hotfixes For more information seeInstalling the Prerequisites [page 17]
If you access your application through a firewall verify with your network administrator which TCP ports tochoose during the installation By default port 80 is the setting for standard http access and port 443 is thesetting for https access If you require a service to listen on a different port you can specify it during theinstallation 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 onwhich 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 Consolidationand automatically overwrites the previous version If you have made any modifications to EnvironmentShellthat 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 ScriptBlocking
If a version of Planning and Consolidation on a NetWeaver platform exists uninstall it before you install Planningand Consolidation 100 version for the Microsoft platform
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 13
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 enterconvert c fsntfsV
All servers in a multiserver environment must be members of the same domain
In a multiserver environment the installing ID must be a domain user ID We recommend that you do not logon to the servers using a local server user ID even if the user ID is a member of the Administrator group on theserver This way you have the proper authority to install software and to modify the Component Services SeeLogging On to Servers [page 14]
You must determine the IP addresses or server names for all servers before installing Planning andConsolidation 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 portaccess reasons (DMZ WORKGROUP or nontrusted domain authentication failures) do the following
1 Copy the EnvironmentShell database file ServerEnvironmentShelldb10 from the Planning andConsolidation 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 theEnvironmentShell database file in the Server Information Advanced Options Local path forEnvironmentShell DB field (for example cEnvironmentShelldb10)
Install the Anti-Cross Site Scripting Library which provides protection to Web-based applications againstCross-Site Scripting (XSS) attacks See Installing the Anti-Cross Site Scripting Library [page 23]
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 theAdministrator group of a domain to which the server belongs or a member of the Administrator group on the localserver
Errors may display during the installation program and in the diagnostic program if the installing user is not assignedto the Administrator group directly but is assigned to a group with Administrator rights You can ignore thesemessages
NoteIf you change the password used to install Planning and Consolidation you must change the password for theapplicable Planning and Consolidation service To do this go to Server Manager on the application server andselect Server Reset Logon Credentials For more information see the SAP Planning and ConsolidationOperations Guide in servicesapcominstguidesepm-bpc 100 for the Microsoft Platform SBOP Plan amp Consol100 MS Administrators Guide
14
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
25 Service-level Accounts
Service accounts are Windows domain IDs with access to all Planning and Consolidation servers with varying levelsof privileges They allow the software to use the minimum amount of privilege required for each job making it moresecure
You must define these user IDs on the Windows machine For security purposes they should not be used to definePlanning and Consolidation users
Prerequisites
Planning and Consolidation 100 has the following Windows services
BPC SendGovernor which manages Microsoft Analysis Service locks to ensure consistent performance andavoid deadlocks
BPC ServiceManager which manages the System Landscape Directory (SLD) service logging service andglobal caches
BPC CTS ServiceManager which listens and handles CTS import requests from the CTS+ transportmanagement system
Since these services should be able to access to the FileShare server an Admin account is assigned automaticallyto the service during the installation of the Planning and Consolidation server program Even though an Adminaccount 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 serviceon the local machine This logon right strictly applies only to the local computer and must be granted in the LocalSecurity Policy
To edit the Local Security Policy of the computer you want to define the logon as a service permission performthe 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 supportmicrosoftcomkb259733
Features
During the installation enter user IDs and passwords for the following user types
System Admin ID
This ID is read-only and is the same as the installation user ID that is the system displays the ID on theinstallation screen but you cannot modify it This ID allows access to code that provides system administrator-level functionality For example this ID can write to the Windows registry has full access to the FileShare server
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 15
and can create remove backup and restore OLAP and SQL databases The system administrator should be amember 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 createsubdirectory access on the FileShare server readwrite metadata and application set database data in OLAPand can create and remove tables in SQL The Administrator should be a member of the domain users groupand 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 theservers has write access to FileShare data and can read metadata and data in OLAP and SQL The User IDmust 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 isinstalled you can change these settings using the Server Manager
NoteWhen defining server names the name refers to the NetBIOS name IP address and fully qualified domain names(FQDN)
Standard Settings
Standard settings are typically used for a single-server environment The following table describes each setting
Table 5
Server Option Value Description
SQL Database server name The name of the SQL DB server
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 computername
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
Table 6
Server Option Value Description
SQL Server Name The name of the SQL DB server Defaults to the local server
Instance name The SQL instance name If left blank the default instance is used
16
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
Server Option Value Description
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 computername
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 forhttp and 443 is the default for https
Authentication type Note If you have chosen SAP BusinessObjects User Management System in theinstallation screen Authentication type does not appear in Advanced settings (asthat IIS authentication type is Anonymous in CMS mode)
Windows or Kerberos The default is Windows If you change this value fromWindows to Kerberos you must make some additional changes
See the Kerberos authentication settings section in the SAP Library ServerManager Guide on servicesapcominstguidesEPM-BPC 100 for theMicrosoft Platform
Scheduler Server Name The name of the server used for scheduling usually the application server forexample GMPV50072862B If you have multiple application servers select theappropriate one
NoteIf the primary server stops working you must manually configure yourapplication 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 theoperating system IIS SQL server analysis services ADOMDNET and MSXML This section provides guidance on
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 17
installing each component For specific versions required see Prerequisites [page 11] and the Product AvailabilityMatrix on the SAP Service Marketplace at servicesapcompam Search on Planning and Consolidation
NoteTo ensure a successful installation you must install the software in the order listed in this procedure
Check all third-party infrastructure services to ensure that they are functioning and that their authenticationmodels 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 itsown 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 applicationserver before you start the installation You can find the UMC installation package (UMCexe) on the Planningand Consolidation CD in a folder called UMC_100_INSTALLER When you run the installation package the wizardguides 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 andConsolidation)
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 multiserverconfiguration See Installing the Operating System [page 19]
3 Install the latest service pack for your operating system To install this service pack go towwwmicrosoftcom
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 SQLServer [page 19]
6 From your SQL Server media install Analysis Services Enterprise Edition and its required service packs and hotfixes See Installing Analysis Services [page 23]
7 On your application server install ADOMDNET The Planning and Consolidation zip file contains theADOMDNET 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 followinglocation BPC SetupServermsxmlmsi
18
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
9 On your application server install Microsoft Visual C++ 2010 SP1 Redistributable Package (x64)
The Microsoft Visual C++ 2010 SP1 Redistributable Package (x64) installation package is contained in thePlanning and Consolidation zip file at the following location BPC SetupServervcredist_x64exe
NoteThe version of vcredist_x64exe in BPC SetupServer has been updated to 10040219 If you have aprevious 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 wwwmicrosoftcomdownloadsendetailsaspxFamilyID=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 Marketplaceat servicesapcompam Search on Planning and Consolidation
Business Planning and Consolidation can support all servers with an operating system in any language
NoteCurrently Business Planning and Consolidation does not support an operating system in bi-directionallanguages such as Hebrew
Procedure
If you are installing IIS 70 75 80 or 85 you must enable the following features
Enable Basic Authentication and Windows Authentication these are not installed by default
Install IIS 6 Metabase Compatibility role
Business Planning and Consolidation uses the ADSI provider to handle IIS administration such as virtualdirectory and security but IIS 7 does not install the ADSI provider by default
273 Installing the SQL Server
Prerequisites
During the installation procedure you have the opportunity to specify the location of the EnvironmentShell databasefile Check that it is possible to access EnvironmentShell from the location where you intend to install the SQL serverIf it is not possible for port access reasons (DMZ WORKGROUP or nontrusted domain authentication failures) copyEnvironmentShell to a location on the SQL server (for example CEnvironmentShelldb10) You specify thislocation on the Server Information page by choosing Server Information Advanced Options Local Path forEnvironmentShell DB
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 19
Procedure
This section describes the general steps for installing the SQL Server component options and considerations wheninstalling 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
NoteIf you encounter a 500 HTTP Error when trying to connect to the Planning and Consolidation Web Client referto Microsoft Support articles 2520479 and 2468871 for assistance
To reinforce security we recommend that you install the SQL server and SSAS components to a nondefaultinstance 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 Optionssection below then choose Next
4 Review disc space requirements then choose Next
5 In Server Configuration Perform the following actions
1 In the Service Accounts tab enter a Planning and Consolidation sysadmin account for the SQL ServerDatabase Engine and the SQL Server Analysis services This is required so that the Planning andConsolidation sysadmin can create and process the Planning and Consolidation database because theMicrosoft SQL server tries to back up or restore database with the privileged account This account is alsorequired 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 differentdomain 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 theapplication server and the account requires the folder access privilege for the application server
To ensure that you have the complete access privileges we recommend the Planning and Consolidationsysadmin 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 touse a restrictive SQL ID that works with the drill-through feature If you must restrict SQL authentication forsecurity 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 installationprogram
20
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
8 Choose Install to begin the installation with the options you have set
SQL Server Component Options
For Single-Machine Installations
Install the following components from the Feature Selection screen
Database Engine Services
Analysis Services
Integration Service which is listed as one of the Shared Features
For Multiple Machine Installations
For multiple machine installations install the following components on each server
Table 7
Server Component What to Install
SQL Server Database Engine Services
SSAS Server Analysis Services
Application Server The following Shared Features
Client Tools Connectivity
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 Server2008 R2 and SQL Server 2012
Process Dimension
It is now possible to process a dimension with multiple selections At processing time the process dimension modulemakes changed or added information for each dimension and process for all selected dimensions and cubes inparallel
Optimize Model
If there are custom partitions for a FACT partition in the OLAP database an optimization module can process custompartitions in parallel when Full or Incremental Optimize is performed However if a full optimize is performed withthe 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 parallelbecause 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 applicationserver and application set databases
NoteSetting the SQL isolation level to be Read Committed Snapshot mode for a database can only be done once andcannot be reversed
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 21
Real Time MOLAP
You can set the OLAP storage model of the write-back partition to be MOLAP (Multidimensional OLAP) This settingremains 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 asfollows
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 Servertrade20052008 which you can download from wwwmicrosoftcom (search on ldquoTable Partitioningrdquo to find all relevantarticles)
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 Thebrowser 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 localhostand external network interface machine
3 If you want to use IP1 which indicates Server IP set Enabled to Yes and specify the TCP Port as desired
4 Delete 0 from TCP Dynamic Ports Set IPAll - TCP Ports as desired (for example 1533)
RecommendationWe do not recommend using dynamic ports
In an SQL server the default instance has a listener which listens on a fixed port (TCP port 1433)However for the named instance the port on which the SQL server listens is random and dynamicallyselected when the named instance of the SQL server starts This recommendation prevents any conflictproblems
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 Setthe 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 thatthe user identified as the Log on as user has the sysadmin SQL Server role defined under Server Roles in theSQL Server Management Studio This is required so Analysis Services can process the SQL Server
From SQL Server Management Studio do the following tasks
22
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
1 If you want to use a port with a named instance select the server type Analysis Services select the servername (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 ServerProperties window displays which shows all configurable properties
3 For enhanced security change the default value to your port number (for example 2724) This means thatyou use a fixed port as for the SQL Server option Then choose OK
NoteWe do not support a nondefault port with the default instance in this release If you want to use the defaultinstance do not change the port number
Restart SQL and OLAP
Confirm that the installation has completed successfully by checking that there are no installation relatedproblems on the event viewer You can now install Planning and Consolidation
274 Installing Analysis Services
Procedure
After you install SQL Server and its required service packs and hotfixes you must install SQL Server Analysis Servicesand its required service packs and hotfixes
NoteIf you have migrated your Analysis Services repository to the SQL Server back up the database that contains therepository before installing this release
To install Analysis Services for SQL Server 2008 SQL Server 2008 R2 or SQL Server 2012 follow the steps andguidelines in technetmicrosoftcomen-uslibraryms143219aspx
To avoid slow performance when a user has more than six OLAP databases follow the steps and guidelines in thePerformance Guide for SQL 2008 at wwwmicrosoftcomdownloadsdetailsaspxFamilyID=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 tohave it available for the Planning and Consolidation installation program
1 Download the Anti-Cross Site Scripting Library file AntiXSSLibraryDLL from the Microsoft Web site atwwwmicrosoftcomdownloadendetailsaspxid=28589
2 Save the extracted file locally
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 23
When you install Planning and Consolidation Server a step in the process requires you to identify the path toAntiXssLibrarydll
28 Installing on a Single Server
When you install all Planning and Consolidation server components on a single server you should consider thefollowing 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 theuncompressed 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 Log on to the server with a local server user ID or domain user ID For more information see Logging on toservers [page 14]
3 Make sure all prerequisite software is installed on the server For more information see Installing thePrerequisites [page 17]
4 Obtain SAP Planning and Consolidation archive from the Downloads SAP Installations amp Upgrades areaof SAP Service Marketplace
5 Extract the files from the archive Go to the BPC Setup folder and run the StartUpexe file
6 From the Server Install screen select Install the Planning and Consolidation server
7 From the Welcome screen choose Next
8 From the License Agreement page choose I accept the terms of the license agreement then choose Next
9 From the Installation Method page accept the default Single machine enter a system ID for the systemlandscape directory (SLD) and choose Next
NoteEntering a system ID of the SLD is only required if you have a SAP Solution Manager license If you do nothave a SAP Solution Manager license you can leave this field empty
10 From the Authentication Method page choose the desired authentication method and choose Next
11 If you have chosen SAP BusinessObjects User Management System in the previous screen on the CMSAuthentication page enter the information required to log on to CMS as an administrator
The following information is required
24
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
Table 8
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 Thisgroup name is filtered as the default when adding a user in Planning andConsolidation Administration Use a comma ( ) to separate multiple names
12 After entering the CMS administrator authentication details choose Next
13 From the Service type accounts page enter service-level account user IDs and passwords See Service-LevelAccounts [page 15]
14 After defining the IDs and passwords choose Next
15 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 chooseNext
16 Specify the location and name of AntiXssLibrarydll See Installing the Anti-Cross Site ScriptingLibrary [page 23]
Choose Next
17 Select destination folders for Programs and Data The Data files include Webfolders and FileDB (publishedreports) and should be installed on a separate drive in a production environment This recommendation reducesthe hard disk IO time and helps to speed up SQL commands
Accept the defaults or make your selections then choose Next
18 Select the default values for the Web client The values are used to determine the default language and regionfor the Web client when you connect to it You can change the values in the Planning and Consolidation ServerManager
19 The installation process takes a few moments When it is complete choose Exit
20 A prompt is displayed to restart your computer Select OK to restart
21 Perform the steps in After Installing Planning and Consolidation Servers [page 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 avariety of ways and configure the servers as a Network Load Balancing (NLB) environment
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 25
The recommended Planning and Consolidation practice is to assign resources using a round robin approach for loadbalancing
You can install the SQL OLAP and FileShare types remotely from the application server You need to performadditional server installations if you have multiple application servers
Installing each Planning and Consolidation application server in a multiserver (NLB) configuration is identical to theprocedure 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 Balancingenvironment With this option there is an additional choice to Include sample environment (required on only oneof the application servers) This is because when you install the application server it connects to the databaseserver and creates the sample environment (EnvironmentShell) Installing the sample environment is requiredon 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
26
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
3 After Installing Planning and ConsolidationServers
31 Post-Installation Steps
Procedure
Perform these steps after installing the Planning and Consolidation servers for new installations of Planning andConsolidation
1 Connect your Planning and Consolidation system to Solution Manager Diagnostics (SMD) to allow support staffto identify analyze and resolve problems with your application See Connecting to Solution ManagerDiagnostics [page 28]
2 Configure the Planning and Consolidation NET and application server to ensure that it and its related servicesfunction properly and reliably For more information see Configuring the Planning and Consolidation NETApplication Server [page 29]
3 Optional configuration steps [page 29]
1 To ensure proper functioning of the Management Console create an SQL user and modify the System DSNand 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 loggingfor ODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default WebSite [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory canaccess the Management Console with whatever rights they have been granted on the server Forinformation about removing default access and creating a group that can access the console see RemovingDefault Access to the Console [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommendthat you only grant Management Console access to system administrators Planning and Consolidationusers should not have any access For more information see Management Console AccessControl [page 33]
6 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
4 Take the following steps to set up security
If you are defining security and application structure continue with step 5
If you want to designate someone other than the system administrator to manage security and applicationstructure log on to EnvironmentShell designate a user as a Primary Administrator
This user must have Administration ndash Environment and Security ‒ Define User task rights so that he or shecan 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 SeeInstalling the Administration Client [page 37]
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 27
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 taskprofiles 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 mustcomplete this step since there is no access to dimensions or members)
NoteTo allow users to request and query large amounts of data you can edit the metabasexml file located at CWindowssystem32inetsrv Set the following parameters to the stated values
ASPBUFFERINGLIMIT = 10485760
MAXREQUESTENTITYALLOWED = 10485760
32 Connecting to Solution Manager Diagnostics
NoteYou only need to perform the steps in this section if you have a SAP Solution Manager licence
The diagnostics functions in SAP Solution Manager allow identification analysis and resolution of problems Thisprocedure 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 areinstalled
NoteInstallation files for Diagnostics Agent are available on Service Marketplace by navigating to SupportPackages and Patches mdash Entry by Application Group SAP Technology Components SAP SOLUTIONMANAGER SAP SOLUTION MANAGER 70 EHP 1 Entry by Component Agents for managed systemsDIAGNOSTICS AGENT 711
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 whereMicrosoft 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
28
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
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 ServiceMarketplace at servicesapcom~sapidb011000358700000074392009E and follow the chapters that applyto Planning and Consolidation
33 Configuring the Planning and Consolidation NETApplication Servers
Procedure
Modifying machineconfig Files
To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock occurrences that wouldcause the application server to ldquosleeprdquo and not process anymore you can modify the machineconfig file whichresides in the WINDOWSMicrosoftNETFramework64v4030319Config directory
1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to specifywhether to automatically configure settings to achieve optimal performance based on the machineconfiguration You can set this attribute to True or False
For more information see msdnmicrosoftcomen-uslibrary7w2sway1aspx
2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the Planning andConsolidation application) or Machineconfig (for all applications including Planning and Consolidation) toensure the validationKey and decryptionKey keys have the same value on all application servers Thisway when the authentication cookie is checked the authentication ticket used on one server can still be validon another server
For more information and sample Visual Basic code for generating random key values seemsdnmicrosoftcomen-uslibraryms998288aspxpaght000007_webfarmdeploymentconsiderationsand msdnmicrosoftcomen-uslibraryms998310aspx
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 DSNand 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 forODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory can accessthe Management Console with whatever rights they have been granted on the server For information about
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 29
removing default access and creating a group that can access the console see Removing Default Access to theConsole [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommend thatyou only grant Management Console access to system administrators Planning and Consolidation users shouldnot have any access For more information see Management Console Access Control [page 33]
6 Configure the use of SSL in Planning and Consolidation See Configuring Planning and Consolidation to useSSL [page 34]
7 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
8 Configure Microsoft SQL Server Reporting Services to use SSL See Configuring MS SQL Server ReportingServices to use SSL [page 36]
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 databaserole 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 optionto use ODBC Logging Enter the following values
DSN is BPC_ManagementDSN Table is BPCLog The Microsoft SQL Server Username and Password
5 Restart IIS
NoteWithout these updates the Management Console does work but some functionality (specifically User Activityand Service Status) does not work as expected
Should you need to uninstall Planning and Consolidation we recommend that you reset the Active Log Formatfield in IIS to W3C Extended Log File Format
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
30
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
Prerequisites
ODBC logging has been configured according to the Microsoft Knowledge Base article 245243 How to configureODBC 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 inApplicationHostconfig as shown here
ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0logFormat=Custom gtUse 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-00AA006111E0appcmd 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 articlespecified in the Prerequisites section Configure these settings in the ltodbcLogginggt node underltsystemwebServergt
Exampleltlocation path=Default Web SitegtltsystemwebServergtltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog userName=Usernamepassword=mypassword gtltsystemwebServergtltlocationgt
Use the following AppCmds to configure these attributes for the default Web site
appcmd set config Default Web Site sectionodbcLogging dataSourceBPC_ManagementDSN commitappHostappcmd set config Default Web Site sectionodbcLogging tableNameBPCLog commitappHostappcmd set config Default Web Site sectionodbcLogging userNameUsername commitappHostappcmd set config Default Web Site sectionodbcLogging passwordmypassword commitappHost
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 31
NoteYou cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must use the SQL ServerODBC driver For more information see the Microsoft Knowledge Base article 931202 The requirements for usingthe ODBC logging feature in IIS
343 Setting Up an ODBC Data Source in Windows Server2008 2008 R2 2012 or 2012 R2
Procedure
This procedure describes how to set up an ODBC data source for the Management Console in Windows Server 20082008 R2 2012 or 2012 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
NoteIf you have chosen SAP BusinessObjects User Management System in the installation screen you do not needto remove or configure access because the Management Console service always runs with the System Admin IDaccount which is a member of the Administrators group
Procedure
To remove default access to the Management Console and create a group that does have access to the console usethe procedure described below
32
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
NoteCreate your Management Console administrative group either on the server that hosts the Management Consoleor 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
NoteAlternatively you can perform analogous steps in Active Directory
3 In the Groups context menu choose New Group
4 Enter data as required Click Create
5 In the Computer Management dialog box choose Services and Applications Internet InformationServices 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 objectand all child objects Include these with entries explicitly defined here checkbox
NoteThis step is a necessary precursor to the completion of this procedure
10 In the Security dialog box click Copy to ensure that the System group retains its privileges
11 Remove access to the Management Console from all groups that should not have it
12 Choose Authentication in the center pane then disable Windows authentication
Result
Users who have not been granted access to the Management Console can still open the Management Console Webpage but it contains no data or menu options This does not affect the access that a user would otherwise have toPlanning and Consolidation
345 Management Console Access Control
After establishing the Management Console group you can add users or groups to it For more information aboutcreating this group see Removing Default Access to the Console [page 32] Their rights in Active Directory determinewhat they can access in the Console
By default any member of the Administrators Active Directory group on the application server or domain has fullaccess to all of the features of the Console except the Planning and Consolidation logging area Access to Planningand Consolidation logging is controlled within the Planning and Consolidation Administration Client task securityThe user must be granted View system logs task privileges For more information see the SAP Library Planning and
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 33
Consolidation Administrators Guide in servicesapcominstguidesepm-bpc 100 version for the Microsoftplatform
Your IT policy determines whether you grant access by group or user You may wish to create several levels of Consoleusers (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 describedin this table
Table 9
Privilege Rights Management Area
Task Manager and Kill Process Administrators group on application server or domain
Performance Monitor Counters Administrators group on application server or domain
Power Users group on application server or domain
Performance Monitor Users group on application server
Microsoft Analysis Services performance monitoring Administrators group on application server or domain
Microsoft SQL Server Monitoring (performance counters andstatistics)
Administrators group on application server or domain
346 Configuring Planning and Consolidation to use SSL
Procedure
Creating a Certificate for the Server
During the handshake phase of the SSL communication the server must send its certificate to the client The clientthen uses the certificate to encrypt information and send it back to the server
The procedure below describes how to create a self-signed certificate for the server
RecommendationWe recommend that you limit the use of self-signed certificates to testing only For a productive system you shouldobtain a certificate signed by a well-known certification authority (CA)
1 Start the Internet Information Services (IIS) Manager To do that go to Start All Programs AdministrativeTools Internet Information Services (IIS) Manager
2 In the Connections panel on the left-hand side select the server node and then choose Server Certificates
3 In the Actions panel on the right hand side choose the Create Self-Signed Certificate action
4 Enter the name that you want the certificate to be identified by for example MyTestSSLCertificate
IIS generates a new SSL certificate for you that has one yearrsquos expiry lease The certificate is issued to the local servername
Binding the Certificate to the Web Site
The procedure below describes how to bind the certificate to the web site for which SSL connections must be used
1 In the Connections panel select the web site node
2 In the Actions panel choose Bindings
34
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
3 In the Site Bindings dialog that appears choose the Add button to create a new binding
4 Configure the parameters as follows
Type = https IP Address = [1] - this is a shorthand expression for the local server name
Port = 443 - this is the default SSL port
SSL Certificate = enter your newly created certificate name
5 Choose OK to create the new binding and then close the Site Bindings dialog
6 Restart the IIS processes To do this choose Restart from the Actions panel
7 In the middle panel under the IIS section choose SSL Settings
8 In the SSL Settings screen select the Require SSL checkbox
9 In the Actions panel choose to Apply these settings
To test the SSL connection in the Actions panel choose the Browse [1] 443 (https) link
347 Using Client Certificates
To enable the use of client certificates in Planning and Consolidation you must follow several manual steps
NotePlanning and Consolidation supports client certificate authentication in Windows Authentication Mode butdoes 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 technetmicrosoftcomen-uslibrarycc753810aspx
For more information about configuring the client certificate mapping authentication see technetmicrosoftcomen-uslibrarycc732996(WS10)aspx
When you create the client certificates you can set the type of certificate in the SSL Settings screen in InternetInformation Services (IIS) Manager
Procedure
1 Set the options for client certificates
1 In the IIS Manager select the web site where you installed Planning and Consolidation
2 Choose SSL Settings
3 In the Client certificates section select the Accept client certificates option
This option allows you to use a client certificate or username and password (Basic authentication) toconnect 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 theManagementConsole home page
3 Double-click Authentication and enable Anonymous Authentication
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 35
4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way asin step 3
5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the sameway 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
348 Configuring MS SQL Server Reporting Services to useSSL
Procedure
The procedure below describes how to configure the use of SSL in Microsoft SQL Server Reporting Services
NoteReporting Services does not provide functionalities for generating requesting or installing a certificate Theserver certificates that you want to use for configuring SSL must have already been installed on your computer
1 Open the Reporting Services Configuration Manager program To do this open the Windows Start menu andnavigate to All Programs Microsoft SQL Server ltversiongt Configuration Tools Reporting ServicesConfiguration Manager
2 In the Connect panel on the left-hand side select the Web Service URL option to open all the Report Server webservice parameters
3 Configure the parameters as follows
SSL Certificate = the name of the certificate that you want to use
SSL Port = 4434 Choose Apply to confirm the changes
5 In the Connect panel choose Report Manager URL to open the list of parameters that link Reporting Servicesto IIS
6 Choose Advanced to add your new SSL web URL
7 In the section Multiple SSL Identities for Report Manager choose Add Configure the parameters as follows
IP Address = (All IPv4) SSL Port = 443 Certificate = the name of your SSL certificate
8 To test the configuration click the URL that appears under the Report manager Site Identification section
36
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
4 Installing Planning and ConsolidationAdministration Client and the SAPBusinessObjects EPM solutions Add-in forMicrosoft Office
The installation of the Planning and Consolidation Administration Client allows administrators to build and maintainPlanning and Consolidation environments and models and administer security
All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions add-in forMicrosoft 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 valueof the Planning and Consolidation client to prompt for user name and password Otherwise the Planning andConsolidation Start Page does not display
41 Installing the Administration Client
Prerequisites
NoteFor a definitive list of system requirements see the Product Availability Matrix on SAP Service Marketplace atservicesapcompam Search on Planning and Consolidation
The following list describes the minimum software requirements
Microsoft Internet Explorer 70 80 90 or 10
Microsoft Office 2003 2007 2010 or 2012
NET Framework 20 or higher (install any required NET Framework Hotfixes by referring tosupportmicrosoftcomkb)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 37
NoteWe recommend that you install all of the latest Microsoft Windows hotfixes prior to installing the Administrationclient For information about which hotfixes to install see updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us
Procedure
The 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 ltPC_serverportgtsapbpcweb
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 mustdownload the most recent version of the full setup (EPM Add-inexe) from the Service Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPCInstallation folder
Individual users can install the EPM add-in on their own machines by going to the Planning and Consolidation Homepage 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 upthe 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
38
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
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 toperform the upgrade If Client Auto Update is not enabled and a newer version is detected clients must be installedmanually 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 andpassword in the Admin ID and Admin password fields respectively The Admin ID should be a member of thelocal administrators group on all the computers running the auto update This setting is not needed if all usershave 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 Thisoption is stored in the user preferences and may also be turned on or off using the User Optionshellip menu itemIf 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 toinstall 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 installit 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 servicesapcom
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 versionand policy information For a support package these files are
EPM Addin Support Package ltSP versiongtmsp EPM Addin Support Package ltSP versiongtxmlFor a patch these files are
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 (WebsrvrWebBPCInstallation)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 39
You can set a different update policy for each package listed
ExampleThe following table illustrates some possible situations assuming that you have installed the first full version(V1)
Table 10
Available maintenancepackages
V2-user update
V3-force update
V4-force update
V5-user update
V5-user update V5-user update
V6-auto update
V7-force update
Minimum RequiredVersion
V4 V4 V7
Notification A prompt tells the user toinstall maintenancepackage V4 using theForced Update behavior
If User Update is enabledthe prompt informs theuser that maintenancepackage V5 is available
A prompt tells the user toinstall maintenancepackage V7 using theForced Update behavior
New Version V4 V4 or V5 V7
If you change the update policy for any package click Update to complete the change
40
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
5 Connection Issues
You may experience connection problems with ports the proxy server or programs and settings that interact withthese components If you have any issues related to connection review the following recommendations andtroubleshooting tips
51 Checking for Open Ports
You must ensure that all required ports are open for inboundoutbound traffic By default Planning andConsolidation requires that Ports 80 (used by http) and 1433 and 2383 (used by SQL Server 2008) are open Totest whether the required ports are open go to a command prompt and enter the Telnet serveripaddress and portFor example Telnet 431181836 80 If the system returns a blank command window the port is open If it returnsa message stating that it is unable to connect the port is not open
NoteYou can use the following site to scan for the normal ports It allows you to manually enter a port number to test
wwwmyserverorgportsniffasp
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 Planningand Consolidation server as an exception You can do this at the client level ( Internet Explorer ToolsInternet 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 fullyqualified 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 Consolidationauthentication Do not use authentication on the proxy server The system synchronizes the user name andpassword on the remote server with the local user name and password
SAP Business Planning and Consolidation 100Connection Issues
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 41
NoteFor more information about setting up an ISA proxy server contact SAP Support to request a copy of Setting upISA Proxy Server White Paper For more information about Business Planning and Consolidation firewall portssee SAP Note 1505250
Internet Explorer Settings Issues
Internet Explorer settings must be set correctly to prevent errors and problems when you attempt to access thePlanning 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 insertthe IP address or fully qualified server name of the Planning and Consolidation server as an exception bychoosing 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
42
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Connection Issues
6 Installing Planning and Consolidation withTwo Active Directory Domains
To set up a Planning and Consolidation 10 application server in a hosted environment and use your own domainusers follow this procedure In general you install Planning and Consolidation on the host domain use the hostdomain account and assign it to the Planning and Consolidation users SysAdmin Admin and Users Then you acceptone 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 andpassword 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 topromote 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 privilegefor the Planning and Consolidation server
5 Install Planning and Consolidation and assign your domain account either to the three Planning andConsolidation administrative users SysAdmin Admin and Users or to only one of the three Planning andConsolidation administrative users and to three of your users Be sure you use your own user account ratherthan host domain users
Planning and Consolidation impersonation can then access your domain from the host environment becauseit has the privilege of your domain account
SAP Business Planning and Consolidation 100Installing Planning and Consolidation with Two Active Directory Domains
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 43
7 Installing Planning and Consolidation in aTerminal Services or Citrix ServerDeployment
This section describes best practices and instructions for installing Planning and Consolidation in a Terminal Servicesor Citrix Server deployment
71 Terminal Services Home Directories
We recommend using Terminal Server home directories rather than using the userrsquos profile directory The profiledirectory downloads a minimal amount of information about the dimensions of the environment you are logging onto and may be as large as 2 MB per user The profile directory is on the system drive and has limited space Byspecifying 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 individualserver 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 clientserver (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
44
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
Procedure
The following steps outline how to install the Planning and Consolidation clients in a Terminal Services (TS) or CitrixServer deployment
1 Make sure the Terminal Services or Citrix Server machine has the system requirements installed
2 Log on to the Terminal Services or Citrix Server machine with a user ID that has the rights to install on thatserver
3 At a command prompt enter Change userinstall
4 Open a browser and connect to the URL ltPC_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_MSBPCAdminMainexe
74 Creating a Shortcut to the Launch Page
Procedure
If you use published desktops instead of published applications the Planning and Consolidation desktop file (whichis installed on the current userrsquos desktop) must be moved to the All UsersDesktop folder
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 45
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 SQLServer 2012 support the remote modification of SSIS packages Planning and Consolidation also supports theremote 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 whichyou want to modify SSIS packages
These custom tasks reference dlls that connect to the database server and perform certain validation when usersset up the parameters of each task All the custom task reference components must also be installed in the machineon which you want to modify SSIS packages
We provide a program that registers all the reference components of the custom tasks This section explains theinstallation 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 ndash This folder contains all the dlls that should be installed on the machine There are Planning andConsolidation platform components and all of the Data Manager custom task files
Config folder ndash This folder contains only one file named Filelistxml and lists all of the files that should be installedIf you need to add or remove certain components from the installation you can modify this xml file
OSoftSetupexe ndash This is the main executable file to run the installation package
NoteIf you are not installing SSIS Custom Tasks on your client machine ndash specifically a machine other than the Planningand Consolidation application server ndash you must first install OSoftSSIS2008_Client or OSoftSSIS2012_Client onthe client machine followed by the SQL Server version If you want to use SQL 2008 Tasks under the SQL 2012environment you must install OSoftSSIS2008_Client on the application server For detailed information see SAPNote 1707410 You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package byextracting OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPCInstallation folder on the Planning and Consolidation server To modify SSIS packages on the Planning andConsolidation application server you need to install OSoftSSIS2008_Client or OSoftSSIS2012_Client for creatinga COM+ application For more information see Before You Modify the SSIS Packages [page 49] and Setup ofa COM+ Application on the Application Server [page 50]
Bin folder
This folder contains the following components
46
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Table 11
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012respectively
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
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 47
Name Remark
BPCWriteBackdll
InteropDTSdll
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 addmore components to the installation package you can copy the new components into the Bin folder and add theproper xml tags in FileListxml You need to enter information for the following tags
RegistType ndash This is the registration information of the component You can enter the following values
RegAsm ndash For NET component
48
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Regsvr32 ndash For VB6 component
Gacutil ndash For NET Framework component that should be registered into Global Assembly Cache
FileName ndash Component file name
OSoftSetupexe
This is the executable file to run the SSIS installation package Double-click the file to start the installation You needto enter information for the following fields
Set SQL server
Specify the SQL server name If your SQL Server has an instance specify the instance name
NoteIf you installed the OSoftSSIS2008_Client or OSoftSSIS2012_Client on the application server the SQL servername is automatically disabled
Set server credential
This is the credential name of the COM+ package component Enter the user ID and password that can accessyour SQL Server This should be either the System Admin ID or Admin ID that was registered as a COM+ userwhen 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 ifyou 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 packagesremotely This is also true for the application server that has SSIS installed The Planning and ConsolidationData Manager has the following custom tasks
Table 12
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008and 2012 respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and2012 respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012respectively
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 49
Name Remark
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and2012 respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008and 2012 respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL2008 and 2012 respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and2012 respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012respectively
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
ltdrivegtWebsrvrbin2 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 FilesMicrosoft SQLServer paste all files into the CProgram Files (x86)Microsoft SQL Server100DTSTasksfolder
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
50
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Typographic Conventions
Table 13
Example Description
lt gt Angle brackets indicate that you replace these words or characters with appropriate entries tomake entries in the system for example Enter your ltUser Namegt
File Save Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
Example Textual cross-references to an internet address for example wwwsapcom
example Quicklinks added to the internet address of a homepage to enable quick access to specificcontent 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 titlespushbutton 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 namesof installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transactioncodes database table names and key concepts of a programming language when they aresurrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
SAP Business Planning and Consolidation 100Typographic Conventions
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 51
52
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
wwwsapcom
Material Number
- SAP Business 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 2008 R2 2012 or 2012 R2
- 344 Removing Default Access to the Console
- 345 Management Console Access Control
- 346 Configuring Planning and Consolidation to use SSL
- 347 Using Client Certificates
- 348 Configuring MS SQL Server Reporting Services to use SSL
-
- 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
-
Content
1 Introduction 911 SAP Notes for the Installation 912 Naming Conventions 10
2 Installing Planning and Consolidation Servers 1121 Basic Steps 1122 Prerequisites 1123 Before Starting the Planning and Consolidation Server Installation 1324 Logging on to Servers 1425 Service-level Accounts 1526 Standard and Advanced Settings 1627 Installing the Prerequisites 17
Installing the Prerequisites ndash Basic Steps 17 Installing the Operating System 19 Installing the SQL Server 19 Installing Analysis Services 23 Installing the Anti-Cross Site Scripting Library 23
28 Installing on a Single Server 2429 Installing the Server in a Multiserver Configuration 25
3 After Installing Planning and Consolidation Servers 2731 Post-Installation Steps 2732 Connecting to Solution Manager Diagnostics 2833 Configuring the Planning and Consolidation NET Application Servers 2934 Post-Installation Optional Configuration Steps 29
Enabling the Management Console 30 Setting Up ODBC Logging in IIS for the Default Web Site 30 Setting Up an ODBC Data Source in Windows Server 2008 2008 R2 2012 or 2012
R2 32 Removing Default Access to the Console 32 Management Console Access Control 33 Configuring Planning and Consolidation to use SSL 34 Using Client Certificates 35 Configuring MS SQL Server Reporting Services to use SSL 36
4 Installing Planning and Consolidation Administration Client and the SAP BusinessObjectsEPM solutions Add-in for Microsoft Office 37
41 Installing the Administration Client 3742 Installing the EPM Add-in 3843 Using the Client Auto Update Program 38
5 Connection Issues 4151 Checking for Open Ports 4152 Proxy Server and Firewall Issues 41
6
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Content
6 Installing Planning and Consolidation with Two Active Directory Domains 43
7 Installing Planning and Consolidation in a Terminal Services or Citrix ServerDeployment 44
71 Terminal Services Home Directories 4472 System Requirements 4473 Installing Planning and Consolidation 4474 Creating a Shortcut to the Launch Page 45
8 Installing SSIS Custom Tasks 4681 Composition of SSIS Custom Task Installation 4682 Before You Modify the SSIS Packages 4983 Setup of a COM+ Application on the Application Server 50
SAP Business Planning and Consolidation 100Content
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 7
8
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
1 Introduction
The SAP BusinessObjects Planning and Consolidation Installation Guide is intended for System Administrators whoperform Planning and Consolidation server and Administration client installations It contains everything you needto 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 releasewe provide detailed instructions on how to migrate your existing environments For more information see theUpgrade Guide which is available on SAP Service Marketplace at servicesapcominstguidesEPM-BPC Planningand Consolidation 100 version for the Microsoft platform
For more information about the Planning and Consolidation Office client software see the SAP BusinessObjects EPMsolutions 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 FileOLAP 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 2008or Windows Server 2008 R2 for remote desktop access
Planning and Consolidation no longer requires a separate Web server only an application server You can installthe application server on a single machine or on multiple machines with network load balancing (NLB) If youuse 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 informationon the installation as well as corrections to the installation documentation Make sure that you have the up-to-dateversion of each SAP Note which you can find in the SAP Service Marketplace at the Internet addressservicesapcomnotes
Table 2
SAP Note Number Title Comments
1584890 Documentation Addendum Contains information that does not yet appear in theapplication help of Business Planning and Consolidation100 version for the Microsoft platform Application helpis available at helpsapcombopacms100
2000499 Business Planning amp Consolidation 10 forMicrosoft SP14 Central Note
This note contains important information about theinstallation of support package 14
SAP Business Planning and Consolidation 100Introduction
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 9
SAP Note Number Title Comments
1961655 Business Planning amp Consolidation 10 forMicrosoft SP13 Central Note
This note contains important information about theinstallation of support package 13
1897745 Business Planning amp Consolidation 10 forMicrosoft SP12 Central Note
This note contains important information about theinstallation of support package 12
1846917 Business Planning amp Consolidation 10 forMicrosoft SP11 Central Note
This note contains important information about theinstallation of support package 11
1804918 Business Planning amp Consolidation 10 forMicrosoft SP10 Central Note
This note contains important information about theinstallation of support package 10
1755355 Business Planning amp Consolidation 10 forMicrosoft SP09 Central Note
This note contains important information about theinstallation of support package 9
1733053 Business Planning amp Consolidation 10 forMicrosoft SP08 Central Note
This note contains important information about theinstallation of support package 8
1689792 Business Planning amp Consolidation 10 forMicrosoft SP07 Central Note
This note contains important information about theinstallation of support package 7
1665656 Business Planning amp Consolidation 10 forMicrosoft SP06 Central Note
This note contains important information about theinstallation of support package 6
1643037 Business Planning amp Consolidation 10 forMicrosoft SP05 Central Note
This note contains important information about theinstallation of support package 5
1620464 Business Planning amp Consolidation 10 forMicrosoft SP04 Central Note
This note contains important information about theinstallation of support package 4
1601213 Business Planning amp Consolidation 10 forMicrosoft SP03 Central Note
This note contains important information about theinstallation of support package 3
1591848 Business Planning amp Consolidation 10 forMicrosoft SP02 Central Note
This note contains important information about theinstallation of support package 2
1573539 Business Planning amp Consolidation 10 forMicrosoft SP01 Central Note
This note contains important information about theinstallation of support package 1
12 Naming Conventions
In this document the following naming conventions apply
Table 3
Variable Description
ltPC_serverportgt Server name or IP address and port number of SAP Planningand Consolidation application location
ltdrivegt The drive where SAP Planning and Consolidation is installed
The default for this is CPC_MS
10
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Introduction
2 Installing Planning and ConsolidationServers
This section includes the basic steps for installing a Planning and Consolidation server the prerequisites and whatto 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 atservicesapcominstguidesepm-bpc 100 version for the Microsoft platform
2 Perform the tasks in the Before Starting the Planning and Consolidation Server Installation [page 13] sectionincluding installing all prerequisites
3 From the application server install the Planning and Consolidation server See Installing Planning andConsolidation on a Single Server [page 24]
NoteYou must install both Planning and Consolidation 100 as well as the most recent Planning and Consolidation100 Support Package available from the SAP Service Marketplace at servicesapcomswdc SoftwareDownloads Support Packages and Patches A - Z Index B SAP BPC FOR MICROSOFT SBOP PC 100FOR MICROSOFT Comprised Software Component Versions SAP CPM BPC 100 M Windows Server onx64 64bit
4 If you have multiple machines see Installing the Server in a Multiserver Configuration [page 25]
5 Perform the steps in the section After Installing Planning and Consolidation Servers [page 27]
22 Prerequisites
The following table describes the software you need to install before installing the Planning and Consolidation serverand the minimum versions required
NoteA list of the supported operating systems and database systems is also available in the Product Availability Matrixon SAP Service Marketplace at servicesapcompam Search on Planning and Consolidation
Table 4
Component Minimum Requirement
Operating System The requirements outlined below are for the following operating systems
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 11
Component Minimum Requirement
Windows Server 2008 (64-bit) Standard Enterprise or Data Center with or withoutHyper-V
Windows Server 2008 R2 (64-bit) Foundation Standard Enterprise or DataCenter with or without Hyper-V
Windows Server 2012 (64-bit) Standard Data Center
Windows Server 2012 R2 (64-bit) Standard Data Center
NoteThe operating system must be configured with NTFS
Relational Database Microsoft SQL Server 2008 Enterprise Edition
Microsoft SQL Server 2008 R2 (Gemini) Enterprise Edition
Microsoft SQL Server 2012 Enterprise Edition
OLAP Database Microsoft SQL Server 2008 Enterprise Edition ndash Analysis Server
Microsoft SQL Server 2008 R2 Enterprise Edition ndash Analysis Server
Microsoft SQL Server 2012 Enterprise Edition ndash Analysis Server
Data Integration Microsoft SQL Server 2008 Enterprise Edition ndash SQL Service Integration Services
Microsoft SQL Server 2008 R2 Enterprise Edition ndash SQL Service IntegrationServices
Microsoft SQL Server 2012 Enterprise Edition ndash 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
NET 35 and NET 45 are required for Windows 2012 and 2012 R2
NET 40 is required for all other operating systems
IIS
IIS 75 or IIS 70
(Included in your Operating System IIS 75 is required for Windows 2008 R2editions)
IIS 80 or IIS 85
(Included in your Operating System IIS 85 is required for Windows 2012 R2editions)
Anti-Cross Site Scripting Library 42
This component must be downloaded before installing the server The serverinstallation program asks for the path of each file and copies the files into theappropriate Planning and Consolidation path
Microsoft Visual C++ 2010 SP1 Redistributable Package (x64)
Microsoft Access Database Engine 2010 64bit
12
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
Component Minimum Requirement
VMWare ESX 3x or ESX 40
(Required only if a landscape deployment strategy using virtualizationtechnologies is planned)
NoteMSXML 40 SP2 ADOMDNET 100 and Microsoft Visual C++ 2010 SP1Redistributable Package (x64) are included with the installation program but notinstalled 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 values being returned withcalculated accounts For more information see SAP Note number 1429246 which also contains downloadinformation
We recommend SQL Server 2008 (or R2) Enterprise Edition or SQL Server 2012 Enterprise Edition for theOLAP database to support proactive cache and cube partitioning It is technically possible to use SQL Server2008 (or R2) Standard Edition or SQL Server 2012 Standard Edition for data integration servers but we donot recommend this
23 Before Starting the Planning and Consolidation ServerInstallation
You must perform the following tasks before starting your Planning and Consolidation server installation
Install all the prerequisite software including all of the latest Microsoft hotfixes For more information seeInstalling the Prerequisites [page 17]
If you access your application through a firewall verify with your network administrator which TCP ports tochoose during the installation By default port 80 is the setting for standard http access and port 443 is thesetting for https access If you require a service to listen on a different port you can specify it during theinstallation 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 onwhich 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 Consolidationand automatically overwrites the previous version If you have made any modifications to EnvironmentShellthat 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 ScriptBlocking
If a version of Planning and Consolidation on a NetWeaver platform exists uninstall it before you install Planningand Consolidation 100 version for the Microsoft platform
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 13
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 enterconvert c fsntfsV
All servers in a multiserver environment must be members of the same domain
In a multiserver environment the installing ID must be a domain user ID We recommend that you do not logon to the servers using a local server user ID even if the user ID is a member of the Administrator group on theserver This way you have the proper authority to install software and to modify the Component Services SeeLogging On to Servers [page 14]
You must determine the IP addresses or server names for all servers before installing Planning andConsolidation 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 portaccess reasons (DMZ WORKGROUP or nontrusted domain authentication failures) do the following
1 Copy the EnvironmentShell database file ServerEnvironmentShelldb10 from the Planning andConsolidation 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 theEnvironmentShell database file in the Server Information Advanced Options Local path forEnvironmentShell DB field (for example cEnvironmentShelldb10)
Install the Anti-Cross Site Scripting Library which provides protection to Web-based applications againstCross-Site Scripting (XSS) attacks See Installing the Anti-Cross Site Scripting Library [page 23]
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 theAdministrator group of a domain to which the server belongs or a member of the Administrator group on the localserver
Errors may display during the installation program and in the diagnostic program if the installing user is not assignedto the Administrator group directly but is assigned to a group with Administrator rights You can ignore thesemessages
NoteIf you change the password used to install Planning and Consolidation you must change the password for theapplicable Planning and Consolidation service To do this go to Server Manager on the application server andselect Server Reset Logon Credentials For more information see the SAP Planning and ConsolidationOperations Guide in servicesapcominstguidesepm-bpc 100 for the Microsoft Platform SBOP Plan amp Consol100 MS Administrators Guide
14
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
25 Service-level Accounts
Service accounts are Windows domain IDs with access to all Planning and Consolidation servers with varying levelsof privileges They allow the software to use the minimum amount of privilege required for each job making it moresecure
You must define these user IDs on the Windows machine For security purposes they should not be used to definePlanning and Consolidation users
Prerequisites
Planning and Consolidation 100 has the following Windows services
BPC SendGovernor which manages Microsoft Analysis Service locks to ensure consistent performance andavoid deadlocks
BPC ServiceManager which manages the System Landscape Directory (SLD) service logging service andglobal caches
BPC CTS ServiceManager which listens and handles CTS import requests from the CTS+ transportmanagement system
Since these services should be able to access to the FileShare server an Admin account is assigned automaticallyto the service during the installation of the Planning and Consolidation server program Even though an Adminaccount 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 serviceon the local machine This logon right strictly applies only to the local computer and must be granted in the LocalSecurity Policy
To edit the Local Security Policy of the computer you want to define the logon as a service permission performthe 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 supportmicrosoftcomkb259733
Features
During the installation enter user IDs and passwords for the following user types
System Admin ID
This ID is read-only and is the same as the installation user ID that is the system displays the ID on theinstallation screen but you cannot modify it This ID allows access to code that provides system administrator-level functionality For example this ID can write to the Windows registry has full access to the FileShare server
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 15
and can create remove backup and restore OLAP and SQL databases The system administrator should be amember 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 createsubdirectory access on the FileShare server readwrite metadata and application set database data in OLAPand can create and remove tables in SQL The Administrator should be a member of the domain users groupand 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 theservers has write access to FileShare data and can read metadata and data in OLAP and SQL The User IDmust 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 isinstalled you can change these settings using the Server Manager
NoteWhen defining server names the name refers to the NetBIOS name IP address and fully qualified domain names(FQDN)
Standard Settings
Standard settings are typically used for a single-server environment The following table describes each setting
Table 5
Server Option Value Description
SQL Database server name The name of the SQL DB server
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 computername
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
Table 6
Server Option Value Description
SQL Server Name The name of the SQL DB server Defaults to the local server
Instance name The SQL instance name If left blank the default instance is used
16
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
Server Option Value Description
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 computername
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 forhttp and 443 is the default for https
Authentication type Note If you have chosen SAP BusinessObjects User Management System in theinstallation screen Authentication type does not appear in Advanced settings (asthat IIS authentication type is Anonymous in CMS mode)
Windows or Kerberos The default is Windows If you change this value fromWindows to Kerberos you must make some additional changes
See the Kerberos authentication settings section in the SAP Library ServerManager Guide on servicesapcominstguidesEPM-BPC 100 for theMicrosoft Platform
Scheduler Server Name The name of the server used for scheduling usually the application server forexample GMPV50072862B If you have multiple application servers select theappropriate one
NoteIf the primary server stops working you must manually configure yourapplication 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 theoperating system IIS SQL server analysis services ADOMDNET and MSXML This section provides guidance on
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 17
installing each component For specific versions required see Prerequisites [page 11] and the Product AvailabilityMatrix on the SAP Service Marketplace at servicesapcompam Search on Planning and Consolidation
NoteTo ensure a successful installation you must install the software in the order listed in this procedure
Check all third-party infrastructure services to ensure that they are functioning and that their authenticationmodels 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 itsown 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 applicationserver before you start the installation You can find the UMC installation package (UMCexe) on the Planningand Consolidation CD in a folder called UMC_100_INSTALLER When you run the installation package the wizardguides 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 andConsolidation)
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 multiserverconfiguration See Installing the Operating System [page 19]
3 Install the latest service pack for your operating system To install this service pack go towwwmicrosoftcom
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 SQLServer [page 19]
6 From your SQL Server media install Analysis Services Enterprise Edition and its required service packs and hotfixes See Installing Analysis Services [page 23]
7 On your application server install ADOMDNET The Planning and Consolidation zip file contains theADOMDNET 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 followinglocation BPC SetupServermsxmlmsi
18
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
9 On your application server install Microsoft Visual C++ 2010 SP1 Redistributable Package (x64)
The Microsoft Visual C++ 2010 SP1 Redistributable Package (x64) installation package is contained in thePlanning and Consolidation zip file at the following location BPC SetupServervcredist_x64exe
NoteThe version of vcredist_x64exe in BPC SetupServer has been updated to 10040219 If you have aprevious 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 wwwmicrosoftcomdownloadsendetailsaspxFamilyID=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 Marketplaceat servicesapcompam Search on Planning and Consolidation
Business Planning and Consolidation can support all servers with an operating system in any language
NoteCurrently Business Planning and Consolidation does not support an operating system in bi-directionallanguages such as Hebrew
Procedure
If you are installing IIS 70 75 80 or 85 you must enable the following features
Enable Basic Authentication and Windows Authentication these are not installed by default
Install IIS 6 Metabase Compatibility role
Business Planning and Consolidation uses the ADSI provider to handle IIS administration such as virtualdirectory and security but IIS 7 does not install the ADSI provider by default
273 Installing the SQL Server
Prerequisites
During the installation procedure you have the opportunity to specify the location of the EnvironmentShell databasefile Check that it is possible to access EnvironmentShell from the location where you intend to install the SQL serverIf it is not possible for port access reasons (DMZ WORKGROUP or nontrusted domain authentication failures) copyEnvironmentShell to a location on the SQL server (for example CEnvironmentShelldb10) You specify thislocation on the Server Information page by choosing Server Information Advanced Options Local Path forEnvironmentShell DB
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 19
Procedure
This section describes the general steps for installing the SQL Server component options and considerations wheninstalling 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
NoteIf you encounter a 500 HTTP Error when trying to connect to the Planning and Consolidation Web Client referto Microsoft Support articles 2520479 and 2468871 for assistance
To reinforce security we recommend that you install the SQL server and SSAS components to a nondefaultinstance 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 Optionssection below then choose Next
4 Review disc space requirements then choose Next
5 In Server Configuration Perform the following actions
1 In the Service Accounts tab enter a Planning and Consolidation sysadmin account for the SQL ServerDatabase Engine and the SQL Server Analysis services This is required so that the Planning andConsolidation sysadmin can create and process the Planning and Consolidation database because theMicrosoft SQL server tries to back up or restore database with the privileged account This account is alsorequired 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 differentdomain 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 theapplication server and the account requires the folder access privilege for the application server
To ensure that you have the complete access privileges we recommend the Planning and Consolidationsysadmin 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 touse a restrictive SQL ID that works with the drill-through feature If you must restrict SQL authentication forsecurity 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 installationprogram
20
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
8 Choose Install to begin the installation with the options you have set
SQL Server Component Options
For Single-Machine Installations
Install the following components from the Feature Selection screen
Database Engine Services
Analysis Services
Integration Service which is listed as one of the Shared Features
For Multiple Machine Installations
For multiple machine installations install the following components on each server
Table 7
Server Component What to Install
SQL Server Database Engine Services
SSAS Server Analysis Services
Application Server The following Shared Features
Client Tools Connectivity
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 Server2008 R2 and SQL Server 2012
Process Dimension
It is now possible to process a dimension with multiple selections At processing time the process dimension modulemakes changed or added information for each dimension and process for all selected dimensions and cubes inparallel
Optimize Model
If there are custom partitions for a FACT partition in the OLAP database an optimization module can process custompartitions in parallel when Full or Incremental Optimize is performed However if a full optimize is performed withthe 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 parallelbecause 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 applicationserver and application set databases
NoteSetting the SQL isolation level to be Read Committed Snapshot mode for a database can only be done once andcannot be reversed
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 21
Real Time MOLAP
You can set the OLAP storage model of the write-back partition to be MOLAP (Multidimensional OLAP) This settingremains 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 asfollows
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 Servertrade20052008 which you can download from wwwmicrosoftcom (search on ldquoTable Partitioningrdquo to find all relevantarticles)
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 Thebrowser 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 localhostand external network interface machine
3 If you want to use IP1 which indicates Server IP set Enabled to Yes and specify the TCP Port as desired
4 Delete 0 from TCP Dynamic Ports Set IPAll - TCP Ports as desired (for example 1533)
RecommendationWe do not recommend using dynamic ports
In an SQL server the default instance has a listener which listens on a fixed port (TCP port 1433)However for the named instance the port on which the SQL server listens is random and dynamicallyselected when the named instance of the SQL server starts This recommendation prevents any conflictproblems
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 Setthe 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 thatthe user identified as the Log on as user has the sysadmin SQL Server role defined under Server Roles in theSQL Server Management Studio This is required so Analysis Services can process the SQL Server
From SQL Server Management Studio do the following tasks
22
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
1 If you want to use a port with a named instance select the server type Analysis Services select the servername (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 ServerProperties window displays which shows all configurable properties
3 For enhanced security change the default value to your port number (for example 2724) This means thatyou use a fixed port as for the SQL Server option Then choose OK
NoteWe do not support a nondefault port with the default instance in this release If you want to use the defaultinstance do not change the port number
Restart SQL and OLAP
Confirm that the installation has completed successfully by checking that there are no installation relatedproblems on the event viewer You can now install Planning and Consolidation
274 Installing Analysis Services
Procedure
After you install SQL Server and its required service packs and hotfixes you must install SQL Server Analysis Servicesand its required service packs and hotfixes
NoteIf you have migrated your Analysis Services repository to the SQL Server back up the database that contains therepository before installing this release
To install Analysis Services for SQL Server 2008 SQL Server 2008 R2 or SQL Server 2012 follow the steps andguidelines in technetmicrosoftcomen-uslibraryms143219aspx
To avoid slow performance when a user has more than six OLAP databases follow the steps and guidelines in thePerformance Guide for SQL 2008 at wwwmicrosoftcomdownloadsdetailsaspxFamilyID=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 tohave it available for the Planning and Consolidation installation program
1 Download the Anti-Cross Site Scripting Library file AntiXSSLibraryDLL from the Microsoft Web site atwwwmicrosoftcomdownloadendetailsaspxid=28589
2 Save the extracted file locally
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 23
When you install Planning and Consolidation Server a step in the process requires you to identify the path toAntiXssLibrarydll
28 Installing on a Single Server
When you install all Planning and Consolidation server components on a single server you should consider thefollowing 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 theuncompressed 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 Log on to the server with a local server user ID or domain user ID For more information see Logging on toservers [page 14]
3 Make sure all prerequisite software is installed on the server For more information see Installing thePrerequisites [page 17]
4 Obtain SAP Planning and Consolidation archive from the Downloads SAP Installations amp Upgrades areaof SAP Service Marketplace
5 Extract the files from the archive Go to the BPC Setup folder and run the StartUpexe file
6 From the Server Install screen select Install the Planning and Consolidation server
7 From the Welcome screen choose Next
8 From the License Agreement page choose I accept the terms of the license agreement then choose Next
9 From the Installation Method page accept the default Single machine enter a system ID for the systemlandscape directory (SLD) and choose Next
NoteEntering a system ID of the SLD is only required if you have a SAP Solution Manager license If you do nothave a SAP Solution Manager license you can leave this field empty
10 From the Authentication Method page choose the desired authentication method and choose Next
11 If you have chosen SAP BusinessObjects User Management System in the previous screen on the CMSAuthentication page enter the information required to log on to CMS as an administrator
The following information is required
24
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
Table 8
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 Thisgroup name is filtered as the default when adding a user in Planning andConsolidation Administration Use a comma ( ) to separate multiple names
12 After entering the CMS administrator authentication details choose Next
13 From the Service type accounts page enter service-level account user IDs and passwords See Service-LevelAccounts [page 15]
14 After defining the IDs and passwords choose Next
15 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 chooseNext
16 Specify the location and name of AntiXssLibrarydll See Installing the Anti-Cross Site ScriptingLibrary [page 23]
Choose Next
17 Select destination folders for Programs and Data The Data files include Webfolders and FileDB (publishedreports) and should be installed on a separate drive in a production environment This recommendation reducesthe hard disk IO time and helps to speed up SQL commands
Accept the defaults or make your selections then choose Next
18 Select the default values for the Web client The values are used to determine the default language and regionfor the Web client when you connect to it You can change the values in the Planning and Consolidation ServerManager
19 The installation process takes a few moments When it is complete choose Exit
20 A prompt is displayed to restart your computer Select OK to restart
21 Perform the steps in After Installing Planning and Consolidation Servers [page 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 avariety of ways and configure the servers as a Network Load Balancing (NLB) environment
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 25
The recommended Planning and Consolidation practice is to assign resources using a round robin approach for loadbalancing
You can install the SQL OLAP and FileShare types remotely from the application server You need to performadditional server installations if you have multiple application servers
Installing each Planning and Consolidation application server in a multiserver (NLB) configuration is identical to theprocedure 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 Balancingenvironment With this option there is an additional choice to Include sample environment (required on only oneof the application servers) This is because when you install the application server it connects to the databaseserver and creates the sample environment (EnvironmentShell) Installing the sample environment is requiredon 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
26
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
3 After Installing Planning and ConsolidationServers
31 Post-Installation Steps
Procedure
Perform these steps after installing the Planning and Consolidation servers for new installations of Planning andConsolidation
1 Connect your Planning and Consolidation system to Solution Manager Diagnostics (SMD) to allow support staffto identify analyze and resolve problems with your application See Connecting to Solution ManagerDiagnostics [page 28]
2 Configure the Planning and Consolidation NET and application server to ensure that it and its related servicesfunction properly and reliably For more information see Configuring the Planning and Consolidation NETApplication Server [page 29]
3 Optional configuration steps [page 29]
1 To ensure proper functioning of the Management Console create an SQL user and modify the System DSNand 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 loggingfor ODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default WebSite [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory canaccess the Management Console with whatever rights they have been granted on the server Forinformation about removing default access and creating a group that can access the console see RemovingDefault Access to the Console [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommendthat you only grant Management Console access to system administrators Planning and Consolidationusers should not have any access For more information see Management Console AccessControl [page 33]
6 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
4 Take the following steps to set up security
If you are defining security and application structure continue with step 5
If you want to designate someone other than the system administrator to manage security and applicationstructure log on to EnvironmentShell designate a user as a Primary Administrator
This user must have Administration ndash Environment and Security ‒ Define User task rights so that he or shecan 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 SeeInstalling the Administration Client [page 37]
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 27
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 taskprofiles 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 mustcomplete this step since there is no access to dimensions or members)
NoteTo allow users to request and query large amounts of data you can edit the metabasexml file located at CWindowssystem32inetsrv Set the following parameters to the stated values
ASPBUFFERINGLIMIT = 10485760
MAXREQUESTENTITYALLOWED = 10485760
32 Connecting to Solution Manager Diagnostics
NoteYou only need to perform the steps in this section if you have a SAP Solution Manager licence
The diagnostics functions in SAP Solution Manager allow identification analysis and resolution of problems Thisprocedure 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 areinstalled
NoteInstallation files for Diagnostics Agent are available on Service Marketplace by navigating to SupportPackages and Patches mdash Entry by Application Group SAP Technology Components SAP SOLUTIONMANAGER SAP SOLUTION MANAGER 70 EHP 1 Entry by Component Agents for managed systemsDIAGNOSTICS AGENT 711
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 whereMicrosoft 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
28
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
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 ServiceMarketplace at servicesapcom~sapidb011000358700000074392009E and follow the chapters that applyto Planning and Consolidation
33 Configuring the Planning and Consolidation NETApplication Servers
Procedure
Modifying machineconfig Files
To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock occurrences that wouldcause the application server to ldquosleeprdquo and not process anymore you can modify the machineconfig file whichresides in the WINDOWSMicrosoftNETFramework64v4030319Config directory
1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to specifywhether to automatically configure settings to achieve optimal performance based on the machineconfiguration You can set this attribute to True or False
For more information see msdnmicrosoftcomen-uslibrary7w2sway1aspx
2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the Planning andConsolidation application) or Machineconfig (for all applications including Planning and Consolidation) toensure the validationKey and decryptionKey keys have the same value on all application servers Thisway when the authentication cookie is checked the authentication ticket used on one server can still be validon another server
For more information and sample Visual Basic code for generating random key values seemsdnmicrosoftcomen-uslibraryms998288aspxpaght000007_webfarmdeploymentconsiderationsand msdnmicrosoftcomen-uslibraryms998310aspx
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 DSNand 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 forODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory can accessthe Management Console with whatever rights they have been granted on the server For information about
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 29
removing default access and creating a group that can access the console see Removing Default Access to theConsole [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommend thatyou only grant Management Console access to system administrators Planning and Consolidation users shouldnot have any access For more information see Management Console Access Control [page 33]
6 Configure the use of SSL in Planning and Consolidation See Configuring Planning and Consolidation to useSSL [page 34]
7 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
8 Configure Microsoft SQL Server Reporting Services to use SSL See Configuring MS SQL Server ReportingServices to use SSL [page 36]
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 databaserole 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 optionto use ODBC Logging Enter the following values
DSN is BPC_ManagementDSN Table is BPCLog The Microsoft SQL Server Username and Password
5 Restart IIS
NoteWithout these updates the Management Console does work but some functionality (specifically User Activityand Service Status) does not work as expected
Should you need to uninstall Planning and Consolidation we recommend that you reset the Active Log Formatfield in IIS to W3C Extended Log File Format
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
30
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
Prerequisites
ODBC logging has been configured according to the Microsoft Knowledge Base article 245243 How to configureODBC 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 inApplicationHostconfig as shown here
ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0logFormat=Custom gtUse 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-00AA006111E0appcmd 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 articlespecified in the Prerequisites section Configure these settings in the ltodbcLogginggt node underltsystemwebServergt
Exampleltlocation path=Default Web SitegtltsystemwebServergtltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog userName=Usernamepassword=mypassword gtltsystemwebServergtltlocationgt
Use the following AppCmds to configure these attributes for the default Web site
appcmd set config Default Web Site sectionodbcLogging dataSourceBPC_ManagementDSN commitappHostappcmd set config Default Web Site sectionodbcLogging tableNameBPCLog commitappHostappcmd set config Default Web Site sectionodbcLogging userNameUsername commitappHostappcmd set config Default Web Site sectionodbcLogging passwordmypassword commitappHost
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 31
NoteYou cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must use the SQL ServerODBC driver For more information see the Microsoft Knowledge Base article 931202 The requirements for usingthe ODBC logging feature in IIS
343 Setting Up an ODBC Data Source in Windows Server2008 2008 R2 2012 or 2012 R2
Procedure
This procedure describes how to set up an ODBC data source for the Management Console in Windows Server 20082008 R2 2012 or 2012 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
NoteIf you have chosen SAP BusinessObjects User Management System in the installation screen you do not needto remove or configure access because the Management Console service always runs with the System Admin IDaccount which is a member of the Administrators group
Procedure
To remove default access to the Management Console and create a group that does have access to the console usethe procedure described below
32
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
NoteCreate your Management Console administrative group either on the server that hosts the Management Consoleor 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
NoteAlternatively you can perform analogous steps in Active Directory
3 In the Groups context menu choose New Group
4 Enter data as required Click Create
5 In the Computer Management dialog box choose Services and Applications Internet InformationServices 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 objectand all child objects Include these with entries explicitly defined here checkbox
NoteThis step is a necessary precursor to the completion of this procedure
10 In the Security dialog box click Copy to ensure that the System group retains its privileges
11 Remove access to the Management Console from all groups that should not have it
12 Choose Authentication in the center pane then disable Windows authentication
Result
Users who have not been granted access to the Management Console can still open the Management Console Webpage but it contains no data or menu options This does not affect the access that a user would otherwise have toPlanning and Consolidation
345 Management Console Access Control
After establishing the Management Console group you can add users or groups to it For more information aboutcreating this group see Removing Default Access to the Console [page 32] Their rights in Active Directory determinewhat they can access in the Console
By default any member of the Administrators Active Directory group on the application server or domain has fullaccess to all of the features of the Console except the Planning and Consolidation logging area Access to Planningand Consolidation logging is controlled within the Planning and Consolidation Administration Client task securityThe user must be granted View system logs task privileges For more information see the SAP Library Planning and
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 33
Consolidation Administrators Guide in servicesapcominstguidesepm-bpc 100 version for the Microsoftplatform
Your IT policy determines whether you grant access by group or user You may wish to create several levels of Consoleusers (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 describedin this table
Table 9
Privilege Rights Management Area
Task Manager and Kill Process Administrators group on application server or domain
Performance Monitor Counters Administrators group on application server or domain
Power Users group on application server or domain
Performance Monitor Users group on application server
Microsoft Analysis Services performance monitoring Administrators group on application server or domain
Microsoft SQL Server Monitoring (performance counters andstatistics)
Administrators group on application server or domain
346 Configuring Planning and Consolidation to use SSL
Procedure
Creating a Certificate for the Server
During the handshake phase of the SSL communication the server must send its certificate to the client The clientthen uses the certificate to encrypt information and send it back to the server
The procedure below describes how to create a self-signed certificate for the server
RecommendationWe recommend that you limit the use of self-signed certificates to testing only For a productive system you shouldobtain a certificate signed by a well-known certification authority (CA)
1 Start the Internet Information Services (IIS) Manager To do that go to Start All Programs AdministrativeTools Internet Information Services (IIS) Manager
2 In the Connections panel on the left-hand side select the server node and then choose Server Certificates
3 In the Actions panel on the right hand side choose the Create Self-Signed Certificate action
4 Enter the name that you want the certificate to be identified by for example MyTestSSLCertificate
IIS generates a new SSL certificate for you that has one yearrsquos expiry lease The certificate is issued to the local servername
Binding the Certificate to the Web Site
The procedure below describes how to bind the certificate to the web site for which SSL connections must be used
1 In the Connections panel select the web site node
2 In the Actions panel choose Bindings
34
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
3 In the Site Bindings dialog that appears choose the Add button to create a new binding
4 Configure the parameters as follows
Type = https IP Address = [1] - this is a shorthand expression for the local server name
Port = 443 - this is the default SSL port
SSL Certificate = enter your newly created certificate name
5 Choose OK to create the new binding and then close the Site Bindings dialog
6 Restart the IIS processes To do this choose Restart from the Actions panel
7 In the middle panel under the IIS section choose SSL Settings
8 In the SSL Settings screen select the Require SSL checkbox
9 In the Actions panel choose to Apply these settings
To test the SSL connection in the Actions panel choose the Browse [1] 443 (https) link
347 Using Client Certificates
To enable the use of client certificates in Planning and Consolidation you must follow several manual steps
NotePlanning and Consolidation supports client certificate authentication in Windows Authentication Mode butdoes 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 technetmicrosoftcomen-uslibrarycc753810aspx
For more information about configuring the client certificate mapping authentication see technetmicrosoftcomen-uslibrarycc732996(WS10)aspx
When you create the client certificates you can set the type of certificate in the SSL Settings screen in InternetInformation Services (IIS) Manager
Procedure
1 Set the options for client certificates
1 In the IIS Manager select the web site where you installed Planning and Consolidation
2 Choose SSL Settings
3 In the Client certificates section select the Accept client certificates option
This option allows you to use a client certificate or username and password (Basic authentication) toconnect 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 theManagementConsole home page
3 Double-click Authentication and enable Anonymous Authentication
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 35
4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way asin step 3
5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the sameway 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
348 Configuring MS SQL Server Reporting Services to useSSL
Procedure
The procedure below describes how to configure the use of SSL in Microsoft SQL Server Reporting Services
NoteReporting Services does not provide functionalities for generating requesting or installing a certificate Theserver certificates that you want to use for configuring SSL must have already been installed on your computer
1 Open the Reporting Services Configuration Manager program To do this open the Windows Start menu andnavigate to All Programs Microsoft SQL Server ltversiongt Configuration Tools Reporting ServicesConfiguration Manager
2 In the Connect panel on the left-hand side select the Web Service URL option to open all the Report Server webservice parameters
3 Configure the parameters as follows
SSL Certificate = the name of the certificate that you want to use
SSL Port = 4434 Choose Apply to confirm the changes
5 In the Connect panel choose Report Manager URL to open the list of parameters that link Reporting Servicesto IIS
6 Choose Advanced to add your new SSL web URL
7 In the section Multiple SSL Identities for Report Manager choose Add Configure the parameters as follows
IP Address = (All IPv4) SSL Port = 443 Certificate = the name of your SSL certificate
8 To test the configuration click the URL that appears under the Report manager Site Identification section
36
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
4 Installing Planning and ConsolidationAdministration Client and the SAPBusinessObjects EPM solutions Add-in forMicrosoft Office
The installation of the Planning and Consolidation Administration Client allows administrators to build and maintainPlanning and Consolidation environments and models and administer security
All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions add-in forMicrosoft 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 valueof the Planning and Consolidation client to prompt for user name and password Otherwise the Planning andConsolidation Start Page does not display
41 Installing the Administration Client
Prerequisites
NoteFor a definitive list of system requirements see the Product Availability Matrix on SAP Service Marketplace atservicesapcompam Search on Planning and Consolidation
The following list describes the minimum software requirements
Microsoft Internet Explorer 70 80 90 or 10
Microsoft Office 2003 2007 2010 or 2012
NET Framework 20 or higher (install any required NET Framework Hotfixes by referring tosupportmicrosoftcomkb)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 37
NoteWe recommend that you install all of the latest Microsoft Windows hotfixes prior to installing the Administrationclient For information about which hotfixes to install see updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us
Procedure
The 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 ltPC_serverportgtsapbpcweb
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 mustdownload the most recent version of the full setup (EPM Add-inexe) from the Service Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPCInstallation folder
Individual users can install the EPM add-in on their own machines by going to the Planning and Consolidation Homepage 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 upthe 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
38
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
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 toperform the upgrade If Client Auto Update is not enabled and a newer version is detected clients must be installedmanually 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 andpassword in the Admin ID and Admin password fields respectively The Admin ID should be a member of thelocal administrators group on all the computers running the auto update This setting is not needed if all usershave 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 Thisoption is stored in the user preferences and may also be turned on or off using the User Optionshellip menu itemIf 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 toinstall 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 installit 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 servicesapcom
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 versionand policy information For a support package these files are
EPM Addin Support Package ltSP versiongtmsp EPM Addin Support Package ltSP versiongtxmlFor a patch these files are
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 (WebsrvrWebBPCInstallation)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 39
You can set a different update policy for each package listed
ExampleThe following table illustrates some possible situations assuming that you have installed the first full version(V1)
Table 10
Available maintenancepackages
V2-user update
V3-force update
V4-force update
V5-user update
V5-user update V5-user update
V6-auto update
V7-force update
Minimum RequiredVersion
V4 V4 V7
Notification A prompt tells the user toinstall maintenancepackage V4 using theForced Update behavior
If User Update is enabledthe prompt informs theuser that maintenancepackage V5 is available
A prompt tells the user toinstall maintenancepackage V7 using theForced Update behavior
New Version V4 V4 or V5 V7
If you change the update policy for any package click Update to complete the change
40
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
5 Connection Issues
You may experience connection problems with ports the proxy server or programs and settings that interact withthese components If you have any issues related to connection review the following recommendations andtroubleshooting tips
51 Checking for Open Ports
You must ensure that all required ports are open for inboundoutbound traffic By default Planning andConsolidation requires that Ports 80 (used by http) and 1433 and 2383 (used by SQL Server 2008) are open Totest whether the required ports are open go to a command prompt and enter the Telnet serveripaddress and portFor example Telnet 431181836 80 If the system returns a blank command window the port is open If it returnsa message stating that it is unable to connect the port is not open
NoteYou can use the following site to scan for the normal ports It allows you to manually enter a port number to test
wwwmyserverorgportsniffasp
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 Planningand Consolidation server as an exception You can do this at the client level ( Internet Explorer ToolsInternet 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 fullyqualified 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 Consolidationauthentication Do not use authentication on the proxy server The system synchronizes the user name andpassword on the remote server with the local user name and password
SAP Business Planning and Consolidation 100Connection Issues
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 41
NoteFor more information about setting up an ISA proxy server contact SAP Support to request a copy of Setting upISA Proxy Server White Paper For more information about Business Planning and Consolidation firewall portssee SAP Note 1505250
Internet Explorer Settings Issues
Internet Explorer settings must be set correctly to prevent errors and problems when you attempt to access thePlanning 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 insertthe IP address or fully qualified server name of the Planning and Consolidation server as an exception bychoosing 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
42
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Connection Issues
6 Installing Planning and Consolidation withTwo Active Directory Domains
To set up a Planning and Consolidation 10 application server in a hosted environment and use your own domainusers follow this procedure In general you install Planning and Consolidation on the host domain use the hostdomain account and assign it to the Planning and Consolidation users SysAdmin Admin and Users Then you acceptone 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 andpassword 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 topromote 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 privilegefor the Planning and Consolidation server
5 Install Planning and Consolidation and assign your domain account either to the three Planning andConsolidation administrative users SysAdmin Admin and Users or to only one of the three Planning andConsolidation administrative users and to three of your users Be sure you use your own user account ratherthan host domain users
Planning and Consolidation impersonation can then access your domain from the host environment becauseit has the privilege of your domain account
SAP Business Planning and Consolidation 100Installing Planning and Consolidation with Two Active Directory Domains
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 43
7 Installing Planning and Consolidation in aTerminal Services or Citrix ServerDeployment
This section describes best practices and instructions for installing Planning and Consolidation in a Terminal Servicesor Citrix Server deployment
71 Terminal Services Home Directories
We recommend using Terminal Server home directories rather than using the userrsquos profile directory The profiledirectory downloads a minimal amount of information about the dimensions of the environment you are logging onto and may be as large as 2 MB per user The profile directory is on the system drive and has limited space Byspecifying 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 individualserver 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 clientserver (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
44
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
Procedure
The following steps outline how to install the Planning and Consolidation clients in a Terminal Services (TS) or CitrixServer deployment
1 Make sure the Terminal Services or Citrix Server machine has the system requirements installed
2 Log on to the Terminal Services or Citrix Server machine with a user ID that has the rights to install on thatserver
3 At a command prompt enter Change userinstall
4 Open a browser and connect to the URL ltPC_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_MSBPCAdminMainexe
74 Creating a Shortcut to the Launch Page
Procedure
If you use published desktops instead of published applications the Planning and Consolidation desktop file (whichis installed on the current userrsquos desktop) must be moved to the All UsersDesktop folder
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 45
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 SQLServer 2012 support the remote modification of SSIS packages Planning and Consolidation also supports theremote 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 whichyou want to modify SSIS packages
These custom tasks reference dlls that connect to the database server and perform certain validation when usersset up the parameters of each task All the custom task reference components must also be installed in the machineon which you want to modify SSIS packages
We provide a program that registers all the reference components of the custom tasks This section explains theinstallation 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 ndash This folder contains all the dlls that should be installed on the machine There are Planning andConsolidation platform components and all of the Data Manager custom task files
Config folder ndash This folder contains only one file named Filelistxml and lists all of the files that should be installedIf you need to add or remove certain components from the installation you can modify this xml file
OSoftSetupexe ndash This is the main executable file to run the installation package
NoteIf you are not installing SSIS Custom Tasks on your client machine ndash specifically a machine other than the Planningand Consolidation application server ndash you must first install OSoftSSIS2008_Client or OSoftSSIS2012_Client onthe client machine followed by the SQL Server version If you want to use SQL 2008 Tasks under the SQL 2012environment you must install OSoftSSIS2008_Client on the application server For detailed information see SAPNote 1707410 You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package byextracting OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPCInstallation folder on the Planning and Consolidation server To modify SSIS packages on the Planning andConsolidation application server you need to install OSoftSSIS2008_Client or OSoftSSIS2012_Client for creatinga COM+ application For more information see Before You Modify the SSIS Packages [page 49] and Setup ofa COM+ Application on the Application Server [page 50]
Bin folder
This folder contains the following components
46
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Table 11
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012respectively
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
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 47
Name Remark
BPCWriteBackdll
InteropDTSdll
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 addmore components to the installation package you can copy the new components into the Bin folder and add theproper xml tags in FileListxml You need to enter information for the following tags
RegistType ndash This is the registration information of the component You can enter the following values
RegAsm ndash For NET component
48
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Regsvr32 ndash For VB6 component
Gacutil ndash For NET Framework component that should be registered into Global Assembly Cache
FileName ndash Component file name
OSoftSetupexe
This is the executable file to run the SSIS installation package Double-click the file to start the installation You needto enter information for the following fields
Set SQL server
Specify the SQL server name If your SQL Server has an instance specify the instance name
NoteIf you installed the OSoftSSIS2008_Client or OSoftSSIS2012_Client on the application server the SQL servername is automatically disabled
Set server credential
This is the credential name of the COM+ package component Enter the user ID and password that can accessyour SQL Server This should be either the System Admin ID or Admin ID that was registered as a COM+ userwhen 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 ifyou 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 packagesremotely This is also true for the application server that has SSIS installed The Planning and ConsolidationData Manager has the following custom tasks
Table 12
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008and 2012 respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and2012 respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012respectively
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 49
Name Remark
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and2012 respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008and 2012 respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL2008 and 2012 respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and2012 respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012respectively
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
ltdrivegtWebsrvrbin2 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 FilesMicrosoft SQLServer paste all files into the CProgram Files (x86)Microsoft SQL Server100DTSTasksfolder
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
50
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Typographic Conventions
Table 13
Example Description
lt gt Angle brackets indicate that you replace these words or characters with appropriate entries tomake entries in the system for example Enter your ltUser Namegt
File Save Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
Example Textual cross-references to an internet address for example wwwsapcom
example Quicklinks added to the internet address of a homepage to enable quick access to specificcontent 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 titlespushbutton 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 namesof installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transactioncodes database table names and key concepts of a programming language when they aresurrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
SAP Business Planning and Consolidation 100Typographic Conventions
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 51
52
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
wwwsapcom
Material Number
- SAP Business 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 2008 R2 2012 or 2012 R2
- 344 Removing Default Access to the Console
- 345 Management Console Access Control
- 346 Configuring Planning and Consolidation to use SSL
- 347 Using Client Certificates
- 348 Configuring MS SQL Server Reporting Services to use SSL
-
- 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
-
6 Installing Planning and Consolidation with Two Active Directory Domains 43
7 Installing Planning and Consolidation in a Terminal Services or Citrix ServerDeployment 44
71 Terminal Services Home Directories 4472 System Requirements 4473 Installing Planning and Consolidation 4474 Creating a Shortcut to the Launch Page 45
8 Installing SSIS Custom Tasks 4681 Composition of SSIS Custom Task Installation 4682 Before You Modify the SSIS Packages 4983 Setup of a COM+ Application on the Application Server 50
SAP Business Planning and Consolidation 100Content
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 7
8
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
1 Introduction
The SAP BusinessObjects Planning and Consolidation Installation Guide is intended for System Administrators whoperform Planning and Consolidation server and Administration client installations It contains everything you needto 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 releasewe provide detailed instructions on how to migrate your existing environments For more information see theUpgrade Guide which is available on SAP Service Marketplace at servicesapcominstguidesEPM-BPC Planningand Consolidation 100 version for the Microsoft platform
For more information about the Planning and Consolidation Office client software see the SAP BusinessObjects EPMsolutions 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 FileOLAP 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 2008or Windows Server 2008 R2 for remote desktop access
Planning and Consolidation no longer requires a separate Web server only an application server You can installthe application server on a single machine or on multiple machines with network load balancing (NLB) If youuse 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 informationon the installation as well as corrections to the installation documentation Make sure that you have the up-to-dateversion of each SAP Note which you can find in the SAP Service Marketplace at the Internet addressservicesapcomnotes
Table 2
SAP Note Number Title Comments
1584890 Documentation Addendum Contains information that does not yet appear in theapplication help of Business Planning and Consolidation100 version for the Microsoft platform Application helpis available at helpsapcombopacms100
2000499 Business Planning amp Consolidation 10 forMicrosoft SP14 Central Note
This note contains important information about theinstallation of support package 14
SAP Business Planning and Consolidation 100Introduction
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 9
SAP Note Number Title Comments
1961655 Business Planning amp Consolidation 10 forMicrosoft SP13 Central Note
This note contains important information about theinstallation of support package 13
1897745 Business Planning amp Consolidation 10 forMicrosoft SP12 Central Note
This note contains important information about theinstallation of support package 12
1846917 Business Planning amp Consolidation 10 forMicrosoft SP11 Central Note
This note contains important information about theinstallation of support package 11
1804918 Business Planning amp Consolidation 10 forMicrosoft SP10 Central Note
This note contains important information about theinstallation of support package 10
1755355 Business Planning amp Consolidation 10 forMicrosoft SP09 Central Note
This note contains important information about theinstallation of support package 9
1733053 Business Planning amp Consolidation 10 forMicrosoft SP08 Central Note
This note contains important information about theinstallation of support package 8
1689792 Business Planning amp Consolidation 10 forMicrosoft SP07 Central Note
This note contains important information about theinstallation of support package 7
1665656 Business Planning amp Consolidation 10 forMicrosoft SP06 Central Note
This note contains important information about theinstallation of support package 6
1643037 Business Planning amp Consolidation 10 forMicrosoft SP05 Central Note
This note contains important information about theinstallation of support package 5
1620464 Business Planning amp Consolidation 10 forMicrosoft SP04 Central Note
This note contains important information about theinstallation of support package 4
1601213 Business Planning amp Consolidation 10 forMicrosoft SP03 Central Note
This note contains important information about theinstallation of support package 3
1591848 Business Planning amp Consolidation 10 forMicrosoft SP02 Central Note
This note contains important information about theinstallation of support package 2
1573539 Business Planning amp Consolidation 10 forMicrosoft SP01 Central Note
This note contains important information about theinstallation of support package 1
12 Naming Conventions
In this document the following naming conventions apply
Table 3
Variable Description
ltPC_serverportgt Server name or IP address and port number of SAP Planningand Consolidation application location
ltdrivegt The drive where SAP Planning and Consolidation is installed
The default for this is CPC_MS
10
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Introduction
2 Installing Planning and ConsolidationServers
This section includes the basic steps for installing a Planning and Consolidation server the prerequisites and whatto 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 atservicesapcominstguidesepm-bpc 100 version for the Microsoft platform
2 Perform the tasks in the Before Starting the Planning and Consolidation Server Installation [page 13] sectionincluding installing all prerequisites
3 From the application server install the Planning and Consolidation server See Installing Planning andConsolidation on a Single Server [page 24]
NoteYou must install both Planning and Consolidation 100 as well as the most recent Planning and Consolidation100 Support Package available from the SAP Service Marketplace at servicesapcomswdc SoftwareDownloads Support Packages and Patches A - Z Index B SAP BPC FOR MICROSOFT SBOP PC 100FOR MICROSOFT Comprised Software Component Versions SAP CPM BPC 100 M Windows Server onx64 64bit
4 If you have multiple machines see Installing the Server in a Multiserver Configuration [page 25]
5 Perform the steps in the section After Installing Planning and Consolidation Servers [page 27]
22 Prerequisites
The following table describes the software you need to install before installing the Planning and Consolidation serverand the minimum versions required
NoteA list of the supported operating systems and database systems is also available in the Product Availability Matrixon SAP Service Marketplace at servicesapcompam Search on Planning and Consolidation
Table 4
Component Minimum Requirement
Operating System The requirements outlined below are for the following operating systems
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 11
Component Minimum Requirement
Windows Server 2008 (64-bit) Standard Enterprise or Data Center with or withoutHyper-V
Windows Server 2008 R2 (64-bit) Foundation Standard Enterprise or DataCenter with or without Hyper-V
Windows Server 2012 (64-bit) Standard Data Center
Windows Server 2012 R2 (64-bit) Standard Data Center
NoteThe operating system must be configured with NTFS
Relational Database Microsoft SQL Server 2008 Enterprise Edition
Microsoft SQL Server 2008 R2 (Gemini) Enterprise Edition
Microsoft SQL Server 2012 Enterprise Edition
OLAP Database Microsoft SQL Server 2008 Enterprise Edition ndash Analysis Server
Microsoft SQL Server 2008 R2 Enterprise Edition ndash Analysis Server
Microsoft SQL Server 2012 Enterprise Edition ndash Analysis Server
Data Integration Microsoft SQL Server 2008 Enterprise Edition ndash SQL Service Integration Services
Microsoft SQL Server 2008 R2 Enterprise Edition ndash SQL Service IntegrationServices
Microsoft SQL Server 2012 Enterprise Edition ndash 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
NET 35 and NET 45 are required for Windows 2012 and 2012 R2
NET 40 is required for all other operating systems
IIS
IIS 75 or IIS 70
(Included in your Operating System IIS 75 is required for Windows 2008 R2editions)
IIS 80 or IIS 85
(Included in your Operating System IIS 85 is required for Windows 2012 R2editions)
Anti-Cross Site Scripting Library 42
This component must be downloaded before installing the server The serverinstallation program asks for the path of each file and copies the files into theappropriate Planning and Consolidation path
Microsoft Visual C++ 2010 SP1 Redistributable Package (x64)
Microsoft Access Database Engine 2010 64bit
12
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
Component Minimum Requirement
VMWare ESX 3x or ESX 40
(Required only if a landscape deployment strategy using virtualizationtechnologies is planned)
NoteMSXML 40 SP2 ADOMDNET 100 and Microsoft Visual C++ 2010 SP1Redistributable Package (x64) are included with the installation program but notinstalled 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 values being returned withcalculated accounts For more information see SAP Note number 1429246 which also contains downloadinformation
We recommend SQL Server 2008 (or R2) Enterprise Edition or SQL Server 2012 Enterprise Edition for theOLAP database to support proactive cache and cube partitioning It is technically possible to use SQL Server2008 (or R2) Standard Edition or SQL Server 2012 Standard Edition for data integration servers but we donot recommend this
23 Before Starting the Planning and Consolidation ServerInstallation
You must perform the following tasks before starting your Planning and Consolidation server installation
Install all the prerequisite software including all of the latest Microsoft hotfixes For more information seeInstalling the Prerequisites [page 17]
If you access your application through a firewall verify with your network administrator which TCP ports tochoose during the installation By default port 80 is the setting for standard http access and port 443 is thesetting for https access If you require a service to listen on a different port you can specify it during theinstallation 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 onwhich 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 Consolidationand automatically overwrites the previous version If you have made any modifications to EnvironmentShellthat 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 ScriptBlocking
If a version of Planning and Consolidation on a NetWeaver platform exists uninstall it before you install Planningand Consolidation 100 version for the Microsoft platform
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 13
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 enterconvert c fsntfsV
All servers in a multiserver environment must be members of the same domain
In a multiserver environment the installing ID must be a domain user ID We recommend that you do not logon to the servers using a local server user ID even if the user ID is a member of the Administrator group on theserver This way you have the proper authority to install software and to modify the Component Services SeeLogging On to Servers [page 14]
You must determine the IP addresses or server names for all servers before installing Planning andConsolidation 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 portaccess reasons (DMZ WORKGROUP or nontrusted domain authentication failures) do the following
1 Copy the EnvironmentShell database file ServerEnvironmentShelldb10 from the Planning andConsolidation 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 theEnvironmentShell database file in the Server Information Advanced Options Local path forEnvironmentShell DB field (for example cEnvironmentShelldb10)
Install the Anti-Cross Site Scripting Library which provides protection to Web-based applications againstCross-Site Scripting (XSS) attacks See Installing the Anti-Cross Site Scripting Library [page 23]
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 theAdministrator group of a domain to which the server belongs or a member of the Administrator group on the localserver
Errors may display during the installation program and in the diagnostic program if the installing user is not assignedto the Administrator group directly but is assigned to a group with Administrator rights You can ignore thesemessages
NoteIf you change the password used to install Planning and Consolidation you must change the password for theapplicable Planning and Consolidation service To do this go to Server Manager on the application server andselect Server Reset Logon Credentials For more information see the SAP Planning and ConsolidationOperations Guide in servicesapcominstguidesepm-bpc 100 for the Microsoft Platform SBOP Plan amp Consol100 MS Administrators Guide
14
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
25 Service-level Accounts
Service accounts are Windows domain IDs with access to all Planning and Consolidation servers with varying levelsof privileges They allow the software to use the minimum amount of privilege required for each job making it moresecure
You must define these user IDs on the Windows machine For security purposes they should not be used to definePlanning and Consolidation users
Prerequisites
Planning and Consolidation 100 has the following Windows services
BPC SendGovernor which manages Microsoft Analysis Service locks to ensure consistent performance andavoid deadlocks
BPC ServiceManager which manages the System Landscape Directory (SLD) service logging service andglobal caches
BPC CTS ServiceManager which listens and handles CTS import requests from the CTS+ transportmanagement system
Since these services should be able to access to the FileShare server an Admin account is assigned automaticallyto the service during the installation of the Planning and Consolidation server program Even though an Adminaccount 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 serviceon the local machine This logon right strictly applies only to the local computer and must be granted in the LocalSecurity Policy
To edit the Local Security Policy of the computer you want to define the logon as a service permission performthe 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 supportmicrosoftcomkb259733
Features
During the installation enter user IDs and passwords for the following user types
System Admin ID
This ID is read-only and is the same as the installation user ID that is the system displays the ID on theinstallation screen but you cannot modify it This ID allows access to code that provides system administrator-level functionality For example this ID can write to the Windows registry has full access to the FileShare server
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 15
and can create remove backup and restore OLAP and SQL databases The system administrator should be amember 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 createsubdirectory access on the FileShare server readwrite metadata and application set database data in OLAPand can create and remove tables in SQL The Administrator should be a member of the domain users groupand 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 theservers has write access to FileShare data and can read metadata and data in OLAP and SQL The User IDmust 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 isinstalled you can change these settings using the Server Manager
NoteWhen defining server names the name refers to the NetBIOS name IP address and fully qualified domain names(FQDN)
Standard Settings
Standard settings are typically used for a single-server environment The following table describes each setting
Table 5
Server Option Value Description
SQL Database server name The name of the SQL DB server
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 computername
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
Table 6
Server Option Value Description
SQL Server Name The name of the SQL DB server Defaults to the local server
Instance name The SQL instance name If left blank the default instance is used
16
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
Server Option Value Description
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 computername
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 forhttp and 443 is the default for https
Authentication type Note If you have chosen SAP BusinessObjects User Management System in theinstallation screen Authentication type does not appear in Advanced settings (asthat IIS authentication type is Anonymous in CMS mode)
Windows or Kerberos The default is Windows If you change this value fromWindows to Kerberos you must make some additional changes
See the Kerberos authentication settings section in the SAP Library ServerManager Guide on servicesapcominstguidesEPM-BPC 100 for theMicrosoft Platform
Scheduler Server Name The name of the server used for scheduling usually the application server forexample GMPV50072862B If you have multiple application servers select theappropriate one
NoteIf the primary server stops working you must manually configure yourapplication 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 theoperating system IIS SQL server analysis services ADOMDNET and MSXML This section provides guidance on
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 17
installing each component For specific versions required see Prerequisites [page 11] and the Product AvailabilityMatrix on the SAP Service Marketplace at servicesapcompam Search on Planning and Consolidation
NoteTo ensure a successful installation you must install the software in the order listed in this procedure
Check all third-party infrastructure services to ensure that they are functioning and that their authenticationmodels 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 itsown 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 applicationserver before you start the installation You can find the UMC installation package (UMCexe) on the Planningand Consolidation CD in a folder called UMC_100_INSTALLER When you run the installation package the wizardguides 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 andConsolidation)
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 multiserverconfiguration See Installing the Operating System [page 19]
3 Install the latest service pack for your operating system To install this service pack go towwwmicrosoftcom
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 SQLServer [page 19]
6 From your SQL Server media install Analysis Services Enterprise Edition and its required service packs and hotfixes See Installing Analysis Services [page 23]
7 On your application server install ADOMDNET The Planning and Consolidation zip file contains theADOMDNET 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 followinglocation BPC SetupServermsxmlmsi
18
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
9 On your application server install Microsoft Visual C++ 2010 SP1 Redistributable Package (x64)
The Microsoft Visual C++ 2010 SP1 Redistributable Package (x64) installation package is contained in thePlanning and Consolidation zip file at the following location BPC SetupServervcredist_x64exe
NoteThe version of vcredist_x64exe in BPC SetupServer has been updated to 10040219 If you have aprevious 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 wwwmicrosoftcomdownloadsendetailsaspxFamilyID=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 Marketplaceat servicesapcompam Search on Planning and Consolidation
Business Planning and Consolidation can support all servers with an operating system in any language
NoteCurrently Business Planning and Consolidation does not support an operating system in bi-directionallanguages such as Hebrew
Procedure
If you are installing IIS 70 75 80 or 85 you must enable the following features
Enable Basic Authentication and Windows Authentication these are not installed by default
Install IIS 6 Metabase Compatibility role
Business Planning and Consolidation uses the ADSI provider to handle IIS administration such as virtualdirectory and security but IIS 7 does not install the ADSI provider by default
273 Installing the SQL Server
Prerequisites
During the installation procedure you have the opportunity to specify the location of the EnvironmentShell databasefile Check that it is possible to access EnvironmentShell from the location where you intend to install the SQL serverIf it is not possible for port access reasons (DMZ WORKGROUP or nontrusted domain authentication failures) copyEnvironmentShell to a location on the SQL server (for example CEnvironmentShelldb10) You specify thislocation on the Server Information page by choosing Server Information Advanced Options Local Path forEnvironmentShell DB
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 19
Procedure
This section describes the general steps for installing the SQL Server component options and considerations wheninstalling 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
NoteIf you encounter a 500 HTTP Error when trying to connect to the Planning and Consolidation Web Client referto Microsoft Support articles 2520479 and 2468871 for assistance
To reinforce security we recommend that you install the SQL server and SSAS components to a nondefaultinstance 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 Optionssection below then choose Next
4 Review disc space requirements then choose Next
5 In Server Configuration Perform the following actions
1 In the Service Accounts tab enter a Planning and Consolidation sysadmin account for the SQL ServerDatabase Engine and the SQL Server Analysis services This is required so that the Planning andConsolidation sysadmin can create and process the Planning and Consolidation database because theMicrosoft SQL server tries to back up or restore database with the privileged account This account is alsorequired 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 differentdomain 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 theapplication server and the account requires the folder access privilege for the application server
To ensure that you have the complete access privileges we recommend the Planning and Consolidationsysadmin 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 touse a restrictive SQL ID that works with the drill-through feature If you must restrict SQL authentication forsecurity 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 installationprogram
20
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
8 Choose Install to begin the installation with the options you have set
SQL Server Component Options
For Single-Machine Installations
Install the following components from the Feature Selection screen
Database Engine Services
Analysis Services
Integration Service which is listed as one of the Shared Features
For Multiple Machine Installations
For multiple machine installations install the following components on each server
Table 7
Server Component What to Install
SQL Server Database Engine Services
SSAS Server Analysis Services
Application Server The following Shared Features
Client Tools Connectivity
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 Server2008 R2 and SQL Server 2012
Process Dimension
It is now possible to process a dimension with multiple selections At processing time the process dimension modulemakes changed or added information for each dimension and process for all selected dimensions and cubes inparallel
Optimize Model
If there are custom partitions for a FACT partition in the OLAP database an optimization module can process custompartitions in parallel when Full or Incremental Optimize is performed However if a full optimize is performed withthe 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 parallelbecause 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 applicationserver and application set databases
NoteSetting the SQL isolation level to be Read Committed Snapshot mode for a database can only be done once andcannot be reversed
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 21
Real Time MOLAP
You can set the OLAP storage model of the write-back partition to be MOLAP (Multidimensional OLAP) This settingremains 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 asfollows
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 Servertrade20052008 which you can download from wwwmicrosoftcom (search on ldquoTable Partitioningrdquo to find all relevantarticles)
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 Thebrowser 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 localhostand external network interface machine
3 If you want to use IP1 which indicates Server IP set Enabled to Yes and specify the TCP Port as desired
4 Delete 0 from TCP Dynamic Ports Set IPAll - TCP Ports as desired (for example 1533)
RecommendationWe do not recommend using dynamic ports
In an SQL server the default instance has a listener which listens on a fixed port (TCP port 1433)However for the named instance the port on which the SQL server listens is random and dynamicallyselected when the named instance of the SQL server starts This recommendation prevents any conflictproblems
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 Setthe 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 thatthe user identified as the Log on as user has the sysadmin SQL Server role defined under Server Roles in theSQL Server Management Studio This is required so Analysis Services can process the SQL Server
From SQL Server Management Studio do the following tasks
22
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
1 If you want to use a port with a named instance select the server type Analysis Services select the servername (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 ServerProperties window displays which shows all configurable properties
3 For enhanced security change the default value to your port number (for example 2724) This means thatyou use a fixed port as for the SQL Server option Then choose OK
NoteWe do not support a nondefault port with the default instance in this release If you want to use the defaultinstance do not change the port number
Restart SQL and OLAP
Confirm that the installation has completed successfully by checking that there are no installation relatedproblems on the event viewer You can now install Planning and Consolidation
274 Installing Analysis Services
Procedure
After you install SQL Server and its required service packs and hotfixes you must install SQL Server Analysis Servicesand its required service packs and hotfixes
NoteIf you have migrated your Analysis Services repository to the SQL Server back up the database that contains therepository before installing this release
To install Analysis Services for SQL Server 2008 SQL Server 2008 R2 or SQL Server 2012 follow the steps andguidelines in technetmicrosoftcomen-uslibraryms143219aspx
To avoid slow performance when a user has more than six OLAP databases follow the steps and guidelines in thePerformance Guide for SQL 2008 at wwwmicrosoftcomdownloadsdetailsaspxFamilyID=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 tohave it available for the Planning and Consolidation installation program
1 Download the Anti-Cross Site Scripting Library file AntiXSSLibraryDLL from the Microsoft Web site atwwwmicrosoftcomdownloadendetailsaspxid=28589
2 Save the extracted file locally
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 23
When you install Planning and Consolidation Server a step in the process requires you to identify the path toAntiXssLibrarydll
28 Installing on a Single Server
When you install all Planning and Consolidation server components on a single server you should consider thefollowing 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 theuncompressed 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 Log on to the server with a local server user ID or domain user ID For more information see Logging on toservers [page 14]
3 Make sure all prerequisite software is installed on the server For more information see Installing thePrerequisites [page 17]
4 Obtain SAP Planning and Consolidation archive from the Downloads SAP Installations amp Upgrades areaof SAP Service Marketplace
5 Extract the files from the archive Go to the BPC Setup folder and run the StartUpexe file
6 From the Server Install screen select Install the Planning and Consolidation server
7 From the Welcome screen choose Next
8 From the License Agreement page choose I accept the terms of the license agreement then choose Next
9 From the Installation Method page accept the default Single machine enter a system ID for the systemlandscape directory (SLD) and choose Next
NoteEntering a system ID of the SLD is only required if you have a SAP Solution Manager license If you do nothave a SAP Solution Manager license you can leave this field empty
10 From the Authentication Method page choose the desired authentication method and choose Next
11 If you have chosen SAP BusinessObjects User Management System in the previous screen on the CMSAuthentication page enter the information required to log on to CMS as an administrator
The following information is required
24
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
Table 8
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 Thisgroup name is filtered as the default when adding a user in Planning andConsolidation Administration Use a comma ( ) to separate multiple names
12 After entering the CMS administrator authentication details choose Next
13 From the Service type accounts page enter service-level account user IDs and passwords See Service-LevelAccounts [page 15]
14 After defining the IDs and passwords choose Next
15 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 chooseNext
16 Specify the location and name of AntiXssLibrarydll See Installing the Anti-Cross Site ScriptingLibrary [page 23]
Choose Next
17 Select destination folders for Programs and Data The Data files include Webfolders and FileDB (publishedreports) and should be installed on a separate drive in a production environment This recommendation reducesthe hard disk IO time and helps to speed up SQL commands
Accept the defaults or make your selections then choose Next
18 Select the default values for the Web client The values are used to determine the default language and regionfor the Web client when you connect to it You can change the values in the Planning and Consolidation ServerManager
19 The installation process takes a few moments When it is complete choose Exit
20 A prompt is displayed to restart your computer Select OK to restart
21 Perform the steps in After Installing Planning and Consolidation Servers [page 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 avariety of ways and configure the servers as a Network Load Balancing (NLB) environment
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 25
The recommended Planning and Consolidation practice is to assign resources using a round robin approach for loadbalancing
You can install the SQL OLAP and FileShare types remotely from the application server You need to performadditional server installations if you have multiple application servers
Installing each Planning and Consolidation application server in a multiserver (NLB) configuration is identical to theprocedure 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 Balancingenvironment With this option there is an additional choice to Include sample environment (required on only oneof the application servers) This is because when you install the application server it connects to the databaseserver and creates the sample environment (EnvironmentShell) Installing the sample environment is requiredon 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
26
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
3 After Installing Planning and ConsolidationServers
31 Post-Installation Steps
Procedure
Perform these steps after installing the Planning and Consolidation servers for new installations of Planning andConsolidation
1 Connect your Planning and Consolidation system to Solution Manager Diagnostics (SMD) to allow support staffto identify analyze and resolve problems with your application See Connecting to Solution ManagerDiagnostics [page 28]
2 Configure the Planning and Consolidation NET and application server to ensure that it and its related servicesfunction properly and reliably For more information see Configuring the Planning and Consolidation NETApplication Server [page 29]
3 Optional configuration steps [page 29]
1 To ensure proper functioning of the Management Console create an SQL user and modify the System DSNand 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 loggingfor ODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default WebSite [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory canaccess the Management Console with whatever rights they have been granted on the server Forinformation about removing default access and creating a group that can access the console see RemovingDefault Access to the Console [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommendthat you only grant Management Console access to system administrators Planning and Consolidationusers should not have any access For more information see Management Console AccessControl [page 33]
6 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
4 Take the following steps to set up security
If you are defining security and application structure continue with step 5
If you want to designate someone other than the system administrator to manage security and applicationstructure log on to EnvironmentShell designate a user as a Primary Administrator
This user must have Administration ndash Environment and Security ‒ Define User task rights so that he or shecan 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 SeeInstalling the Administration Client [page 37]
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 27
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 taskprofiles 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 mustcomplete this step since there is no access to dimensions or members)
NoteTo allow users to request and query large amounts of data you can edit the metabasexml file located at CWindowssystem32inetsrv Set the following parameters to the stated values
ASPBUFFERINGLIMIT = 10485760
MAXREQUESTENTITYALLOWED = 10485760
32 Connecting to Solution Manager Diagnostics
NoteYou only need to perform the steps in this section if you have a SAP Solution Manager licence
The diagnostics functions in SAP Solution Manager allow identification analysis and resolution of problems Thisprocedure 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 areinstalled
NoteInstallation files for Diagnostics Agent are available on Service Marketplace by navigating to SupportPackages and Patches mdash Entry by Application Group SAP Technology Components SAP SOLUTIONMANAGER SAP SOLUTION MANAGER 70 EHP 1 Entry by Component Agents for managed systemsDIAGNOSTICS AGENT 711
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 whereMicrosoft 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
28
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
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 ServiceMarketplace at servicesapcom~sapidb011000358700000074392009E and follow the chapters that applyto Planning and Consolidation
33 Configuring the Planning and Consolidation NETApplication Servers
Procedure
Modifying machineconfig Files
To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock occurrences that wouldcause the application server to ldquosleeprdquo and not process anymore you can modify the machineconfig file whichresides in the WINDOWSMicrosoftNETFramework64v4030319Config directory
1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to specifywhether to automatically configure settings to achieve optimal performance based on the machineconfiguration You can set this attribute to True or False
For more information see msdnmicrosoftcomen-uslibrary7w2sway1aspx
2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the Planning andConsolidation application) or Machineconfig (for all applications including Planning and Consolidation) toensure the validationKey and decryptionKey keys have the same value on all application servers Thisway when the authentication cookie is checked the authentication ticket used on one server can still be validon another server
For more information and sample Visual Basic code for generating random key values seemsdnmicrosoftcomen-uslibraryms998288aspxpaght000007_webfarmdeploymentconsiderationsand msdnmicrosoftcomen-uslibraryms998310aspx
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 DSNand 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 forODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory can accessthe Management Console with whatever rights they have been granted on the server For information about
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 29
removing default access and creating a group that can access the console see Removing Default Access to theConsole [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommend thatyou only grant Management Console access to system administrators Planning and Consolidation users shouldnot have any access For more information see Management Console Access Control [page 33]
6 Configure the use of SSL in Planning and Consolidation See Configuring Planning and Consolidation to useSSL [page 34]
7 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
8 Configure Microsoft SQL Server Reporting Services to use SSL See Configuring MS SQL Server ReportingServices to use SSL [page 36]
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 databaserole 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 optionto use ODBC Logging Enter the following values
DSN is BPC_ManagementDSN Table is BPCLog The Microsoft SQL Server Username and Password
5 Restart IIS
NoteWithout these updates the Management Console does work but some functionality (specifically User Activityand Service Status) does not work as expected
Should you need to uninstall Planning and Consolidation we recommend that you reset the Active Log Formatfield in IIS to W3C Extended Log File Format
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
30
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
Prerequisites
ODBC logging has been configured according to the Microsoft Knowledge Base article 245243 How to configureODBC 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 inApplicationHostconfig as shown here
ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0logFormat=Custom gtUse 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-00AA006111E0appcmd 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 articlespecified in the Prerequisites section Configure these settings in the ltodbcLogginggt node underltsystemwebServergt
Exampleltlocation path=Default Web SitegtltsystemwebServergtltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog userName=Usernamepassword=mypassword gtltsystemwebServergtltlocationgt
Use the following AppCmds to configure these attributes for the default Web site
appcmd set config Default Web Site sectionodbcLogging dataSourceBPC_ManagementDSN commitappHostappcmd set config Default Web Site sectionodbcLogging tableNameBPCLog commitappHostappcmd set config Default Web Site sectionodbcLogging userNameUsername commitappHostappcmd set config Default Web Site sectionodbcLogging passwordmypassword commitappHost
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 31
NoteYou cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must use the SQL ServerODBC driver For more information see the Microsoft Knowledge Base article 931202 The requirements for usingthe ODBC logging feature in IIS
343 Setting Up an ODBC Data Source in Windows Server2008 2008 R2 2012 or 2012 R2
Procedure
This procedure describes how to set up an ODBC data source for the Management Console in Windows Server 20082008 R2 2012 or 2012 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
NoteIf you have chosen SAP BusinessObjects User Management System in the installation screen you do not needto remove or configure access because the Management Console service always runs with the System Admin IDaccount which is a member of the Administrators group
Procedure
To remove default access to the Management Console and create a group that does have access to the console usethe procedure described below
32
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
NoteCreate your Management Console administrative group either on the server that hosts the Management Consoleor 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
NoteAlternatively you can perform analogous steps in Active Directory
3 In the Groups context menu choose New Group
4 Enter data as required Click Create
5 In the Computer Management dialog box choose Services and Applications Internet InformationServices 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 objectand all child objects Include these with entries explicitly defined here checkbox
NoteThis step is a necessary precursor to the completion of this procedure
10 In the Security dialog box click Copy to ensure that the System group retains its privileges
11 Remove access to the Management Console from all groups that should not have it
12 Choose Authentication in the center pane then disable Windows authentication
Result
Users who have not been granted access to the Management Console can still open the Management Console Webpage but it contains no data or menu options This does not affect the access that a user would otherwise have toPlanning and Consolidation
345 Management Console Access Control
After establishing the Management Console group you can add users or groups to it For more information aboutcreating this group see Removing Default Access to the Console [page 32] Their rights in Active Directory determinewhat they can access in the Console
By default any member of the Administrators Active Directory group on the application server or domain has fullaccess to all of the features of the Console except the Planning and Consolidation logging area Access to Planningand Consolidation logging is controlled within the Planning and Consolidation Administration Client task securityThe user must be granted View system logs task privileges For more information see the SAP Library Planning and
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 33
Consolidation Administrators Guide in servicesapcominstguidesepm-bpc 100 version for the Microsoftplatform
Your IT policy determines whether you grant access by group or user You may wish to create several levels of Consoleusers (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 describedin this table
Table 9
Privilege Rights Management Area
Task Manager and Kill Process Administrators group on application server or domain
Performance Monitor Counters Administrators group on application server or domain
Power Users group on application server or domain
Performance Monitor Users group on application server
Microsoft Analysis Services performance monitoring Administrators group on application server or domain
Microsoft SQL Server Monitoring (performance counters andstatistics)
Administrators group on application server or domain
346 Configuring Planning and Consolidation to use SSL
Procedure
Creating a Certificate for the Server
During the handshake phase of the SSL communication the server must send its certificate to the client The clientthen uses the certificate to encrypt information and send it back to the server
The procedure below describes how to create a self-signed certificate for the server
RecommendationWe recommend that you limit the use of self-signed certificates to testing only For a productive system you shouldobtain a certificate signed by a well-known certification authority (CA)
1 Start the Internet Information Services (IIS) Manager To do that go to Start All Programs AdministrativeTools Internet Information Services (IIS) Manager
2 In the Connections panel on the left-hand side select the server node and then choose Server Certificates
3 In the Actions panel on the right hand side choose the Create Self-Signed Certificate action
4 Enter the name that you want the certificate to be identified by for example MyTestSSLCertificate
IIS generates a new SSL certificate for you that has one yearrsquos expiry lease The certificate is issued to the local servername
Binding the Certificate to the Web Site
The procedure below describes how to bind the certificate to the web site for which SSL connections must be used
1 In the Connections panel select the web site node
2 In the Actions panel choose Bindings
34
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
3 In the Site Bindings dialog that appears choose the Add button to create a new binding
4 Configure the parameters as follows
Type = https IP Address = [1] - this is a shorthand expression for the local server name
Port = 443 - this is the default SSL port
SSL Certificate = enter your newly created certificate name
5 Choose OK to create the new binding and then close the Site Bindings dialog
6 Restart the IIS processes To do this choose Restart from the Actions panel
7 In the middle panel under the IIS section choose SSL Settings
8 In the SSL Settings screen select the Require SSL checkbox
9 In the Actions panel choose to Apply these settings
To test the SSL connection in the Actions panel choose the Browse [1] 443 (https) link
347 Using Client Certificates
To enable the use of client certificates in Planning and Consolidation you must follow several manual steps
NotePlanning and Consolidation supports client certificate authentication in Windows Authentication Mode butdoes 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 technetmicrosoftcomen-uslibrarycc753810aspx
For more information about configuring the client certificate mapping authentication see technetmicrosoftcomen-uslibrarycc732996(WS10)aspx
When you create the client certificates you can set the type of certificate in the SSL Settings screen in InternetInformation Services (IIS) Manager
Procedure
1 Set the options for client certificates
1 In the IIS Manager select the web site where you installed Planning and Consolidation
2 Choose SSL Settings
3 In the Client certificates section select the Accept client certificates option
This option allows you to use a client certificate or username and password (Basic authentication) toconnect 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 theManagementConsole home page
3 Double-click Authentication and enable Anonymous Authentication
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 35
4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way asin step 3
5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the sameway 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
348 Configuring MS SQL Server Reporting Services to useSSL
Procedure
The procedure below describes how to configure the use of SSL in Microsoft SQL Server Reporting Services
NoteReporting Services does not provide functionalities for generating requesting or installing a certificate Theserver certificates that you want to use for configuring SSL must have already been installed on your computer
1 Open the Reporting Services Configuration Manager program To do this open the Windows Start menu andnavigate to All Programs Microsoft SQL Server ltversiongt Configuration Tools Reporting ServicesConfiguration Manager
2 In the Connect panel on the left-hand side select the Web Service URL option to open all the Report Server webservice parameters
3 Configure the parameters as follows
SSL Certificate = the name of the certificate that you want to use
SSL Port = 4434 Choose Apply to confirm the changes
5 In the Connect panel choose Report Manager URL to open the list of parameters that link Reporting Servicesto IIS
6 Choose Advanced to add your new SSL web URL
7 In the section Multiple SSL Identities for Report Manager choose Add Configure the parameters as follows
IP Address = (All IPv4) SSL Port = 443 Certificate = the name of your SSL certificate
8 To test the configuration click the URL that appears under the Report manager Site Identification section
36
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
4 Installing Planning and ConsolidationAdministration Client and the SAPBusinessObjects EPM solutions Add-in forMicrosoft Office
The installation of the Planning and Consolidation Administration Client allows administrators to build and maintainPlanning and Consolidation environments and models and administer security
All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions add-in forMicrosoft 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 valueof the Planning and Consolidation client to prompt for user name and password Otherwise the Planning andConsolidation Start Page does not display
41 Installing the Administration Client
Prerequisites
NoteFor a definitive list of system requirements see the Product Availability Matrix on SAP Service Marketplace atservicesapcompam Search on Planning and Consolidation
The following list describes the minimum software requirements
Microsoft Internet Explorer 70 80 90 or 10
Microsoft Office 2003 2007 2010 or 2012
NET Framework 20 or higher (install any required NET Framework Hotfixes by referring tosupportmicrosoftcomkb)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 37
NoteWe recommend that you install all of the latest Microsoft Windows hotfixes prior to installing the Administrationclient For information about which hotfixes to install see updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us
Procedure
The 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 ltPC_serverportgtsapbpcweb
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 mustdownload the most recent version of the full setup (EPM Add-inexe) from the Service Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPCInstallation folder
Individual users can install the EPM add-in on their own machines by going to the Planning and Consolidation Homepage 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 upthe 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
38
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
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 toperform the upgrade If Client Auto Update is not enabled and a newer version is detected clients must be installedmanually 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 andpassword in the Admin ID and Admin password fields respectively The Admin ID should be a member of thelocal administrators group on all the computers running the auto update This setting is not needed if all usershave 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 Thisoption is stored in the user preferences and may also be turned on or off using the User Optionshellip menu itemIf 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 toinstall 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 installit 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 servicesapcom
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 versionand policy information For a support package these files are
EPM Addin Support Package ltSP versiongtmsp EPM Addin Support Package ltSP versiongtxmlFor a patch these files are
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 (WebsrvrWebBPCInstallation)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 39
You can set a different update policy for each package listed
ExampleThe following table illustrates some possible situations assuming that you have installed the first full version(V1)
Table 10
Available maintenancepackages
V2-user update
V3-force update
V4-force update
V5-user update
V5-user update V5-user update
V6-auto update
V7-force update
Minimum RequiredVersion
V4 V4 V7
Notification A prompt tells the user toinstall maintenancepackage V4 using theForced Update behavior
If User Update is enabledthe prompt informs theuser that maintenancepackage V5 is available
A prompt tells the user toinstall maintenancepackage V7 using theForced Update behavior
New Version V4 V4 or V5 V7
If you change the update policy for any package click Update to complete the change
40
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
5 Connection Issues
You may experience connection problems with ports the proxy server or programs and settings that interact withthese components If you have any issues related to connection review the following recommendations andtroubleshooting tips
51 Checking for Open Ports
You must ensure that all required ports are open for inboundoutbound traffic By default Planning andConsolidation requires that Ports 80 (used by http) and 1433 and 2383 (used by SQL Server 2008) are open Totest whether the required ports are open go to a command prompt and enter the Telnet serveripaddress and portFor example Telnet 431181836 80 If the system returns a blank command window the port is open If it returnsa message stating that it is unable to connect the port is not open
NoteYou can use the following site to scan for the normal ports It allows you to manually enter a port number to test
wwwmyserverorgportsniffasp
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 Planningand Consolidation server as an exception You can do this at the client level ( Internet Explorer ToolsInternet 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 fullyqualified 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 Consolidationauthentication Do not use authentication on the proxy server The system synchronizes the user name andpassword on the remote server with the local user name and password
SAP Business Planning and Consolidation 100Connection Issues
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 41
NoteFor more information about setting up an ISA proxy server contact SAP Support to request a copy of Setting upISA Proxy Server White Paper For more information about Business Planning and Consolidation firewall portssee SAP Note 1505250
Internet Explorer Settings Issues
Internet Explorer settings must be set correctly to prevent errors and problems when you attempt to access thePlanning 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 insertthe IP address or fully qualified server name of the Planning and Consolidation server as an exception bychoosing 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
42
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Connection Issues
6 Installing Planning and Consolidation withTwo Active Directory Domains
To set up a Planning and Consolidation 10 application server in a hosted environment and use your own domainusers follow this procedure In general you install Planning and Consolidation on the host domain use the hostdomain account and assign it to the Planning and Consolidation users SysAdmin Admin and Users Then you acceptone 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 andpassword 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 topromote 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 privilegefor the Planning and Consolidation server
5 Install Planning and Consolidation and assign your domain account either to the three Planning andConsolidation administrative users SysAdmin Admin and Users or to only one of the three Planning andConsolidation administrative users and to three of your users Be sure you use your own user account ratherthan host domain users
Planning and Consolidation impersonation can then access your domain from the host environment becauseit has the privilege of your domain account
SAP Business Planning and Consolidation 100Installing Planning and Consolidation with Two Active Directory Domains
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 43
7 Installing Planning and Consolidation in aTerminal Services or Citrix ServerDeployment
This section describes best practices and instructions for installing Planning and Consolidation in a Terminal Servicesor Citrix Server deployment
71 Terminal Services Home Directories
We recommend using Terminal Server home directories rather than using the userrsquos profile directory The profiledirectory downloads a minimal amount of information about the dimensions of the environment you are logging onto and may be as large as 2 MB per user The profile directory is on the system drive and has limited space Byspecifying 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 individualserver 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 clientserver (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
44
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
Procedure
The following steps outline how to install the Planning and Consolidation clients in a Terminal Services (TS) or CitrixServer deployment
1 Make sure the Terminal Services or Citrix Server machine has the system requirements installed
2 Log on to the Terminal Services or Citrix Server machine with a user ID that has the rights to install on thatserver
3 At a command prompt enter Change userinstall
4 Open a browser and connect to the URL ltPC_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_MSBPCAdminMainexe
74 Creating a Shortcut to the Launch Page
Procedure
If you use published desktops instead of published applications the Planning and Consolidation desktop file (whichis installed on the current userrsquos desktop) must be moved to the All UsersDesktop folder
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 45
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 SQLServer 2012 support the remote modification of SSIS packages Planning and Consolidation also supports theremote 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 whichyou want to modify SSIS packages
These custom tasks reference dlls that connect to the database server and perform certain validation when usersset up the parameters of each task All the custom task reference components must also be installed in the machineon which you want to modify SSIS packages
We provide a program that registers all the reference components of the custom tasks This section explains theinstallation 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 ndash This folder contains all the dlls that should be installed on the machine There are Planning andConsolidation platform components and all of the Data Manager custom task files
Config folder ndash This folder contains only one file named Filelistxml and lists all of the files that should be installedIf you need to add or remove certain components from the installation you can modify this xml file
OSoftSetupexe ndash This is the main executable file to run the installation package
NoteIf you are not installing SSIS Custom Tasks on your client machine ndash specifically a machine other than the Planningand Consolidation application server ndash you must first install OSoftSSIS2008_Client or OSoftSSIS2012_Client onthe client machine followed by the SQL Server version If you want to use SQL 2008 Tasks under the SQL 2012environment you must install OSoftSSIS2008_Client on the application server For detailed information see SAPNote 1707410 You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package byextracting OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPCInstallation folder on the Planning and Consolidation server To modify SSIS packages on the Planning andConsolidation application server you need to install OSoftSSIS2008_Client or OSoftSSIS2012_Client for creatinga COM+ application For more information see Before You Modify the SSIS Packages [page 49] and Setup ofa COM+ Application on the Application Server [page 50]
Bin folder
This folder contains the following components
46
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Table 11
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012respectively
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
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 47
Name Remark
BPCWriteBackdll
InteropDTSdll
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 addmore components to the installation package you can copy the new components into the Bin folder and add theproper xml tags in FileListxml You need to enter information for the following tags
RegistType ndash This is the registration information of the component You can enter the following values
RegAsm ndash For NET component
48
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Regsvr32 ndash For VB6 component
Gacutil ndash For NET Framework component that should be registered into Global Assembly Cache
FileName ndash Component file name
OSoftSetupexe
This is the executable file to run the SSIS installation package Double-click the file to start the installation You needto enter information for the following fields
Set SQL server
Specify the SQL server name If your SQL Server has an instance specify the instance name
NoteIf you installed the OSoftSSIS2008_Client or OSoftSSIS2012_Client on the application server the SQL servername is automatically disabled
Set server credential
This is the credential name of the COM+ package component Enter the user ID and password that can accessyour SQL Server This should be either the System Admin ID or Admin ID that was registered as a COM+ userwhen 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 ifyou 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 packagesremotely This is also true for the application server that has SSIS installed The Planning and ConsolidationData Manager has the following custom tasks
Table 12
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008and 2012 respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and2012 respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012respectively
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 49
Name Remark
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and2012 respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008and 2012 respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL2008 and 2012 respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and2012 respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012respectively
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
ltdrivegtWebsrvrbin2 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 FilesMicrosoft SQLServer paste all files into the CProgram Files (x86)Microsoft SQL Server100DTSTasksfolder
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
50
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Typographic Conventions
Table 13
Example Description
lt gt Angle brackets indicate that you replace these words or characters with appropriate entries tomake entries in the system for example Enter your ltUser Namegt
File Save Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
Example Textual cross-references to an internet address for example wwwsapcom
example Quicklinks added to the internet address of a homepage to enable quick access to specificcontent 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 titlespushbutton 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 namesof installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transactioncodes database table names and key concepts of a programming language when they aresurrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
SAP Business Planning and Consolidation 100Typographic Conventions
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 51
52
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
wwwsapcom
Material Number
- SAP Business 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 2008 R2 2012 or 2012 R2
- 344 Removing Default Access to the Console
- 345 Management Console Access Control
- 346 Configuring Planning and Consolidation to use SSL
- 347 Using Client Certificates
- 348 Configuring MS SQL Server Reporting Services to use SSL
-
- 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
-
8
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
1 Introduction
The SAP BusinessObjects Planning and Consolidation Installation Guide is intended for System Administrators whoperform Planning and Consolidation server and Administration client installations It contains everything you needto 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 releasewe provide detailed instructions on how to migrate your existing environments For more information see theUpgrade Guide which is available on SAP Service Marketplace at servicesapcominstguidesEPM-BPC Planningand Consolidation 100 version for the Microsoft platform
For more information about the Planning and Consolidation Office client software see the SAP BusinessObjects EPMsolutions 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 FileOLAP 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 2008or Windows Server 2008 R2 for remote desktop access
Planning and Consolidation no longer requires a separate Web server only an application server You can installthe application server on a single machine or on multiple machines with network load balancing (NLB) If youuse 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 informationon the installation as well as corrections to the installation documentation Make sure that you have the up-to-dateversion of each SAP Note which you can find in the SAP Service Marketplace at the Internet addressservicesapcomnotes
Table 2
SAP Note Number Title Comments
1584890 Documentation Addendum Contains information that does not yet appear in theapplication help of Business Planning and Consolidation100 version for the Microsoft platform Application helpis available at helpsapcombopacms100
2000499 Business Planning amp Consolidation 10 forMicrosoft SP14 Central Note
This note contains important information about theinstallation of support package 14
SAP Business Planning and Consolidation 100Introduction
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 9
SAP Note Number Title Comments
1961655 Business Planning amp Consolidation 10 forMicrosoft SP13 Central Note
This note contains important information about theinstallation of support package 13
1897745 Business Planning amp Consolidation 10 forMicrosoft SP12 Central Note
This note contains important information about theinstallation of support package 12
1846917 Business Planning amp Consolidation 10 forMicrosoft SP11 Central Note
This note contains important information about theinstallation of support package 11
1804918 Business Planning amp Consolidation 10 forMicrosoft SP10 Central Note
This note contains important information about theinstallation of support package 10
1755355 Business Planning amp Consolidation 10 forMicrosoft SP09 Central Note
This note contains important information about theinstallation of support package 9
1733053 Business Planning amp Consolidation 10 forMicrosoft SP08 Central Note
This note contains important information about theinstallation of support package 8
1689792 Business Planning amp Consolidation 10 forMicrosoft SP07 Central Note
This note contains important information about theinstallation of support package 7
1665656 Business Planning amp Consolidation 10 forMicrosoft SP06 Central Note
This note contains important information about theinstallation of support package 6
1643037 Business Planning amp Consolidation 10 forMicrosoft SP05 Central Note
This note contains important information about theinstallation of support package 5
1620464 Business Planning amp Consolidation 10 forMicrosoft SP04 Central Note
This note contains important information about theinstallation of support package 4
1601213 Business Planning amp Consolidation 10 forMicrosoft SP03 Central Note
This note contains important information about theinstallation of support package 3
1591848 Business Planning amp Consolidation 10 forMicrosoft SP02 Central Note
This note contains important information about theinstallation of support package 2
1573539 Business Planning amp Consolidation 10 forMicrosoft SP01 Central Note
This note contains important information about theinstallation of support package 1
12 Naming Conventions
In this document the following naming conventions apply
Table 3
Variable Description
ltPC_serverportgt Server name or IP address and port number of SAP Planningand Consolidation application location
ltdrivegt The drive where SAP Planning and Consolidation is installed
The default for this is CPC_MS
10
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Introduction
2 Installing Planning and ConsolidationServers
This section includes the basic steps for installing a Planning and Consolidation server the prerequisites and whatto 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 atservicesapcominstguidesepm-bpc 100 version for the Microsoft platform
2 Perform the tasks in the Before Starting the Planning and Consolidation Server Installation [page 13] sectionincluding installing all prerequisites
3 From the application server install the Planning and Consolidation server See Installing Planning andConsolidation on a Single Server [page 24]
NoteYou must install both Planning and Consolidation 100 as well as the most recent Planning and Consolidation100 Support Package available from the SAP Service Marketplace at servicesapcomswdc SoftwareDownloads Support Packages and Patches A - Z Index B SAP BPC FOR MICROSOFT SBOP PC 100FOR MICROSOFT Comprised Software Component Versions SAP CPM BPC 100 M Windows Server onx64 64bit
4 If you have multiple machines see Installing the Server in a Multiserver Configuration [page 25]
5 Perform the steps in the section After Installing Planning and Consolidation Servers [page 27]
22 Prerequisites
The following table describes the software you need to install before installing the Planning and Consolidation serverand the minimum versions required
NoteA list of the supported operating systems and database systems is also available in the Product Availability Matrixon SAP Service Marketplace at servicesapcompam Search on Planning and Consolidation
Table 4
Component Minimum Requirement
Operating System The requirements outlined below are for the following operating systems
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 11
Component Minimum Requirement
Windows Server 2008 (64-bit) Standard Enterprise or Data Center with or withoutHyper-V
Windows Server 2008 R2 (64-bit) Foundation Standard Enterprise or DataCenter with or without Hyper-V
Windows Server 2012 (64-bit) Standard Data Center
Windows Server 2012 R2 (64-bit) Standard Data Center
NoteThe operating system must be configured with NTFS
Relational Database Microsoft SQL Server 2008 Enterprise Edition
Microsoft SQL Server 2008 R2 (Gemini) Enterprise Edition
Microsoft SQL Server 2012 Enterprise Edition
OLAP Database Microsoft SQL Server 2008 Enterprise Edition ndash Analysis Server
Microsoft SQL Server 2008 R2 Enterprise Edition ndash Analysis Server
Microsoft SQL Server 2012 Enterprise Edition ndash Analysis Server
Data Integration Microsoft SQL Server 2008 Enterprise Edition ndash SQL Service Integration Services
Microsoft SQL Server 2008 R2 Enterprise Edition ndash SQL Service IntegrationServices
Microsoft SQL Server 2012 Enterprise Edition ndash 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
NET 35 and NET 45 are required for Windows 2012 and 2012 R2
NET 40 is required for all other operating systems
IIS
IIS 75 or IIS 70
(Included in your Operating System IIS 75 is required for Windows 2008 R2editions)
IIS 80 or IIS 85
(Included in your Operating System IIS 85 is required for Windows 2012 R2editions)
Anti-Cross Site Scripting Library 42
This component must be downloaded before installing the server The serverinstallation program asks for the path of each file and copies the files into theappropriate Planning and Consolidation path
Microsoft Visual C++ 2010 SP1 Redistributable Package (x64)
Microsoft Access Database Engine 2010 64bit
12
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
Component Minimum Requirement
VMWare ESX 3x or ESX 40
(Required only if a landscape deployment strategy using virtualizationtechnologies is planned)
NoteMSXML 40 SP2 ADOMDNET 100 and Microsoft Visual C++ 2010 SP1Redistributable Package (x64) are included with the installation program but notinstalled 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 values being returned withcalculated accounts For more information see SAP Note number 1429246 which also contains downloadinformation
We recommend SQL Server 2008 (or R2) Enterprise Edition or SQL Server 2012 Enterprise Edition for theOLAP database to support proactive cache and cube partitioning It is technically possible to use SQL Server2008 (or R2) Standard Edition or SQL Server 2012 Standard Edition for data integration servers but we donot recommend this
23 Before Starting the Planning and Consolidation ServerInstallation
You must perform the following tasks before starting your Planning and Consolidation server installation
Install all the prerequisite software including all of the latest Microsoft hotfixes For more information seeInstalling the Prerequisites [page 17]
If you access your application through a firewall verify with your network administrator which TCP ports tochoose during the installation By default port 80 is the setting for standard http access and port 443 is thesetting for https access If you require a service to listen on a different port you can specify it during theinstallation 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 onwhich 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 Consolidationand automatically overwrites the previous version If you have made any modifications to EnvironmentShellthat 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 ScriptBlocking
If a version of Planning and Consolidation on a NetWeaver platform exists uninstall it before you install Planningand Consolidation 100 version for the Microsoft platform
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 13
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 enterconvert c fsntfsV
All servers in a multiserver environment must be members of the same domain
In a multiserver environment the installing ID must be a domain user ID We recommend that you do not logon to the servers using a local server user ID even if the user ID is a member of the Administrator group on theserver This way you have the proper authority to install software and to modify the Component Services SeeLogging On to Servers [page 14]
You must determine the IP addresses or server names for all servers before installing Planning andConsolidation 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 portaccess reasons (DMZ WORKGROUP or nontrusted domain authentication failures) do the following
1 Copy the EnvironmentShell database file ServerEnvironmentShelldb10 from the Planning andConsolidation 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 theEnvironmentShell database file in the Server Information Advanced Options Local path forEnvironmentShell DB field (for example cEnvironmentShelldb10)
Install the Anti-Cross Site Scripting Library which provides protection to Web-based applications againstCross-Site Scripting (XSS) attacks See Installing the Anti-Cross Site Scripting Library [page 23]
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 theAdministrator group of a domain to which the server belongs or a member of the Administrator group on the localserver
Errors may display during the installation program and in the diagnostic program if the installing user is not assignedto the Administrator group directly but is assigned to a group with Administrator rights You can ignore thesemessages
NoteIf you change the password used to install Planning and Consolidation you must change the password for theapplicable Planning and Consolidation service To do this go to Server Manager on the application server andselect Server Reset Logon Credentials For more information see the SAP Planning and ConsolidationOperations Guide in servicesapcominstguidesepm-bpc 100 for the Microsoft Platform SBOP Plan amp Consol100 MS Administrators Guide
14
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
25 Service-level Accounts
Service accounts are Windows domain IDs with access to all Planning and Consolidation servers with varying levelsof privileges They allow the software to use the minimum amount of privilege required for each job making it moresecure
You must define these user IDs on the Windows machine For security purposes they should not be used to definePlanning and Consolidation users
Prerequisites
Planning and Consolidation 100 has the following Windows services
BPC SendGovernor which manages Microsoft Analysis Service locks to ensure consistent performance andavoid deadlocks
BPC ServiceManager which manages the System Landscape Directory (SLD) service logging service andglobal caches
BPC CTS ServiceManager which listens and handles CTS import requests from the CTS+ transportmanagement system
Since these services should be able to access to the FileShare server an Admin account is assigned automaticallyto the service during the installation of the Planning and Consolidation server program Even though an Adminaccount 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 serviceon the local machine This logon right strictly applies only to the local computer and must be granted in the LocalSecurity Policy
To edit the Local Security Policy of the computer you want to define the logon as a service permission performthe 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 supportmicrosoftcomkb259733
Features
During the installation enter user IDs and passwords for the following user types
System Admin ID
This ID is read-only and is the same as the installation user ID that is the system displays the ID on theinstallation screen but you cannot modify it This ID allows access to code that provides system administrator-level functionality For example this ID can write to the Windows registry has full access to the FileShare server
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 15
and can create remove backup and restore OLAP and SQL databases The system administrator should be amember 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 createsubdirectory access on the FileShare server readwrite metadata and application set database data in OLAPand can create and remove tables in SQL The Administrator should be a member of the domain users groupand 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 theservers has write access to FileShare data and can read metadata and data in OLAP and SQL The User IDmust 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 isinstalled you can change these settings using the Server Manager
NoteWhen defining server names the name refers to the NetBIOS name IP address and fully qualified domain names(FQDN)
Standard Settings
Standard settings are typically used for a single-server environment The following table describes each setting
Table 5
Server Option Value Description
SQL Database server name The name of the SQL DB server
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 computername
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
Table 6
Server Option Value Description
SQL Server Name The name of the SQL DB server Defaults to the local server
Instance name The SQL instance name If left blank the default instance is used
16
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
Server Option Value Description
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 computername
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 forhttp and 443 is the default for https
Authentication type Note If you have chosen SAP BusinessObjects User Management System in theinstallation screen Authentication type does not appear in Advanced settings (asthat IIS authentication type is Anonymous in CMS mode)
Windows or Kerberos The default is Windows If you change this value fromWindows to Kerberos you must make some additional changes
See the Kerberos authentication settings section in the SAP Library ServerManager Guide on servicesapcominstguidesEPM-BPC 100 for theMicrosoft Platform
Scheduler Server Name The name of the server used for scheduling usually the application server forexample GMPV50072862B If you have multiple application servers select theappropriate one
NoteIf the primary server stops working you must manually configure yourapplication 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 theoperating system IIS SQL server analysis services ADOMDNET and MSXML This section provides guidance on
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 17
installing each component For specific versions required see Prerequisites [page 11] and the Product AvailabilityMatrix on the SAP Service Marketplace at servicesapcompam Search on Planning and Consolidation
NoteTo ensure a successful installation you must install the software in the order listed in this procedure
Check all third-party infrastructure services to ensure that they are functioning and that their authenticationmodels 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 itsown 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 applicationserver before you start the installation You can find the UMC installation package (UMCexe) on the Planningand Consolidation CD in a folder called UMC_100_INSTALLER When you run the installation package the wizardguides 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 andConsolidation)
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 multiserverconfiguration See Installing the Operating System [page 19]
3 Install the latest service pack for your operating system To install this service pack go towwwmicrosoftcom
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 SQLServer [page 19]
6 From your SQL Server media install Analysis Services Enterprise Edition and its required service packs and hotfixes See Installing Analysis Services [page 23]
7 On your application server install ADOMDNET The Planning and Consolidation zip file contains theADOMDNET 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 followinglocation BPC SetupServermsxmlmsi
18
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
9 On your application server install Microsoft Visual C++ 2010 SP1 Redistributable Package (x64)
The Microsoft Visual C++ 2010 SP1 Redistributable Package (x64) installation package is contained in thePlanning and Consolidation zip file at the following location BPC SetupServervcredist_x64exe
NoteThe version of vcredist_x64exe in BPC SetupServer has been updated to 10040219 If you have aprevious 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 wwwmicrosoftcomdownloadsendetailsaspxFamilyID=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 Marketplaceat servicesapcompam Search on Planning and Consolidation
Business Planning and Consolidation can support all servers with an operating system in any language
NoteCurrently Business Planning and Consolidation does not support an operating system in bi-directionallanguages such as Hebrew
Procedure
If you are installing IIS 70 75 80 or 85 you must enable the following features
Enable Basic Authentication and Windows Authentication these are not installed by default
Install IIS 6 Metabase Compatibility role
Business Planning and Consolidation uses the ADSI provider to handle IIS administration such as virtualdirectory and security but IIS 7 does not install the ADSI provider by default
273 Installing the SQL Server
Prerequisites
During the installation procedure you have the opportunity to specify the location of the EnvironmentShell databasefile Check that it is possible to access EnvironmentShell from the location where you intend to install the SQL serverIf it is not possible for port access reasons (DMZ WORKGROUP or nontrusted domain authentication failures) copyEnvironmentShell to a location on the SQL server (for example CEnvironmentShelldb10) You specify thislocation on the Server Information page by choosing Server Information Advanced Options Local Path forEnvironmentShell DB
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 19
Procedure
This section describes the general steps for installing the SQL Server component options and considerations wheninstalling 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
NoteIf you encounter a 500 HTTP Error when trying to connect to the Planning and Consolidation Web Client referto Microsoft Support articles 2520479 and 2468871 for assistance
To reinforce security we recommend that you install the SQL server and SSAS components to a nondefaultinstance 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 Optionssection below then choose Next
4 Review disc space requirements then choose Next
5 In Server Configuration Perform the following actions
1 In the Service Accounts tab enter a Planning and Consolidation sysadmin account for the SQL ServerDatabase Engine and the SQL Server Analysis services This is required so that the Planning andConsolidation sysadmin can create and process the Planning and Consolidation database because theMicrosoft SQL server tries to back up or restore database with the privileged account This account is alsorequired 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 differentdomain 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 theapplication server and the account requires the folder access privilege for the application server
To ensure that you have the complete access privileges we recommend the Planning and Consolidationsysadmin 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 touse a restrictive SQL ID that works with the drill-through feature If you must restrict SQL authentication forsecurity 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 installationprogram
20
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
8 Choose Install to begin the installation with the options you have set
SQL Server Component Options
For Single-Machine Installations
Install the following components from the Feature Selection screen
Database Engine Services
Analysis Services
Integration Service which is listed as one of the Shared Features
For Multiple Machine Installations
For multiple machine installations install the following components on each server
Table 7
Server Component What to Install
SQL Server Database Engine Services
SSAS Server Analysis Services
Application Server The following Shared Features
Client Tools Connectivity
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 Server2008 R2 and SQL Server 2012
Process Dimension
It is now possible to process a dimension with multiple selections At processing time the process dimension modulemakes changed or added information for each dimension and process for all selected dimensions and cubes inparallel
Optimize Model
If there are custom partitions for a FACT partition in the OLAP database an optimization module can process custompartitions in parallel when Full or Incremental Optimize is performed However if a full optimize is performed withthe 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 parallelbecause 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 applicationserver and application set databases
NoteSetting the SQL isolation level to be Read Committed Snapshot mode for a database can only be done once andcannot be reversed
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 21
Real Time MOLAP
You can set the OLAP storage model of the write-back partition to be MOLAP (Multidimensional OLAP) This settingremains 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 asfollows
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 Servertrade20052008 which you can download from wwwmicrosoftcom (search on ldquoTable Partitioningrdquo to find all relevantarticles)
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 Thebrowser 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 localhostand external network interface machine
3 If you want to use IP1 which indicates Server IP set Enabled to Yes and specify the TCP Port as desired
4 Delete 0 from TCP Dynamic Ports Set IPAll - TCP Ports as desired (for example 1533)
RecommendationWe do not recommend using dynamic ports
In an SQL server the default instance has a listener which listens on a fixed port (TCP port 1433)However for the named instance the port on which the SQL server listens is random and dynamicallyselected when the named instance of the SQL server starts This recommendation prevents any conflictproblems
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 Setthe 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 thatthe user identified as the Log on as user has the sysadmin SQL Server role defined under Server Roles in theSQL Server Management Studio This is required so Analysis Services can process the SQL Server
From SQL Server Management Studio do the following tasks
22
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
1 If you want to use a port with a named instance select the server type Analysis Services select the servername (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 ServerProperties window displays which shows all configurable properties
3 For enhanced security change the default value to your port number (for example 2724) This means thatyou use a fixed port as for the SQL Server option Then choose OK
NoteWe do not support a nondefault port with the default instance in this release If you want to use the defaultinstance do not change the port number
Restart SQL and OLAP
Confirm that the installation has completed successfully by checking that there are no installation relatedproblems on the event viewer You can now install Planning and Consolidation
274 Installing Analysis Services
Procedure
After you install SQL Server and its required service packs and hotfixes you must install SQL Server Analysis Servicesand its required service packs and hotfixes
NoteIf you have migrated your Analysis Services repository to the SQL Server back up the database that contains therepository before installing this release
To install Analysis Services for SQL Server 2008 SQL Server 2008 R2 or SQL Server 2012 follow the steps andguidelines in technetmicrosoftcomen-uslibraryms143219aspx
To avoid slow performance when a user has more than six OLAP databases follow the steps and guidelines in thePerformance Guide for SQL 2008 at wwwmicrosoftcomdownloadsdetailsaspxFamilyID=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 tohave it available for the Planning and Consolidation installation program
1 Download the Anti-Cross Site Scripting Library file AntiXSSLibraryDLL from the Microsoft Web site atwwwmicrosoftcomdownloadendetailsaspxid=28589
2 Save the extracted file locally
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 23
When you install Planning and Consolidation Server a step in the process requires you to identify the path toAntiXssLibrarydll
28 Installing on a Single Server
When you install all Planning and Consolidation server components on a single server you should consider thefollowing 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 theuncompressed 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 Log on to the server with a local server user ID or domain user ID For more information see Logging on toservers [page 14]
3 Make sure all prerequisite software is installed on the server For more information see Installing thePrerequisites [page 17]
4 Obtain SAP Planning and Consolidation archive from the Downloads SAP Installations amp Upgrades areaof SAP Service Marketplace
5 Extract the files from the archive Go to the BPC Setup folder and run the StartUpexe file
6 From the Server Install screen select Install the Planning and Consolidation server
7 From the Welcome screen choose Next
8 From the License Agreement page choose I accept the terms of the license agreement then choose Next
9 From the Installation Method page accept the default Single machine enter a system ID for the systemlandscape directory (SLD) and choose Next
NoteEntering a system ID of the SLD is only required if you have a SAP Solution Manager license If you do nothave a SAP Solution Manager license you can leave this field empty
10 From the Authentication Method page choose the desired authentication method and choose Next
11 If you have chosen SAP BusinessObjects User Management System in the previous screen on the CMSAuthentication page enter the information required to log on to CMS as an administrator
The following information is required
24
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
Table 8
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 Thisgroup name is filtered as the default when adding a user in Planning andConsolidation Administration Use a comma ( ) to separate multiple names
12 After entering the CMS administrator authentication details choose Next
13 From the Service type accounts page enter service-level account user IDs and passwords See Service-LevelAccounts [page 15]
14 After defining the IDs and passwords choose Next
15 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 chooseNext
16 Specify the location and name of AntiXssLibrarydll See Installing the Anti-Cross Site ScriptingLibrary [page 23]
Choose Next
17 Select destination folders for Programs and Data The Data files include Webfolders and FileDB (publishedreports) and should be installed on a separate drive in a production environment This recommendation reducesthe hard disk IO time and helps to speed up SQL commands
Accept the defaults or make your selections then choose Next
18 Select the default values for the Web client The values are used to determine the default language and regionfor the Web client when you connect to it You can change the values in the Planning and Consolidation ServerManager
19 The installation process takes a few moments When it is complete choose Exit
20 A prompt is displayed to restart your computer Select OK to restart
21 Perform the steps in After Installing Planning and Consolidation Servers [page 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 avariety of ways and configure the servers as a Network Load Balancing (NLB) environment
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 25
The recommended Planning and Consolidation practice is to assign resources using a round robin approach for loadbalancing
You can install the SQL OLAP and FileShare types remotely from the application server You need to performadditional server installations if you have multiple application servers
Installing each Planning and Consolidation application server in a multiserver (NLB) configuration is identical to theprocedure 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 Balancingenvironment With this option there is an additional choice to Include sample environment (required on only oneof the application servers) This is because when you install the application server it connects to the databaseserver and creates the sample environment (EnvironmentShell) Installing the sample environment is requiredon 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
26
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
3 After Installing Planning and ConsolidationServers
31 Post-Installation Steps
Procedure
Perform these steps after installing the Planning and Consolidation servers for new installations of Planning andConsolidation
1 Connect your Planning and Consolidation system to Solution Manager Diagnostics (SMD) to allow support staffto identify analyze and resolve problems with your application See Connecting to Solution ManagerDiagnostics [page 28]
2 Configure the Planning and Consolidation NET and application server to ensure that it and its related servicesfunction properly and reliably For more information see Configuring the Planning and Consolidation NETApplication Server [page 29]
3 Optional configuration steps [page 29]
1 To ensure proper functioning of the Management Console create an SQL user and modify the System DSNand 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 loggingfor ODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default WebSite [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory canaccess the Management Console with whatever rights they have been granted on the server Forinformation about removing default access and creating a group that can access the console see RemovingDefault Access to the Console [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommendthat you only grant Management Console access to system administrators Planning and Consolidationusers should not have any access For more information see Management Console AccessControl [page 33]
6 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
4 Take the following steps to set up security
If you are defining security and application structure continue with step 5
If you want to designate someone other than the system administrator to manage security and applicationstructure log on to EnvironmentShell designate a user as a Primary Administrator
This user must have Administration ndash Environment and Security ‒ Define User task rights so that he or shecan 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 SeeInstalling the Administration Client [page 37]
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 27
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 taskprofiles 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 mustcomplete this step since there is no access to dimensions or members)
NoteTo allow users to request and query large amounts of data you can edit the metabasexml file located at CWindowssystem32inetsrv Set the following parameters to the stated values
ASPBUFFERINGLIMIT = 10485760
MAXREQUESTENTITYALLOWED = 10485760
32 Connecting to Solution Manager Diagnostics
NoteYou only need to perform the steps in this section if you have a SAP Solution Manager licence
The diagnostics functions in SAP Solution Manager allow identification analysis and resolution of problems Thisprocedure 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 areinstalled
NoteInstallation files for Diagnostics Agent are available on Service Marketplace by navigating to SupportPackages and Patches mdash Entry by Application Group SAP Technology Components SAP SOLUTIONMANAGER SAP SOLUTION MANAGER 70 EHP 1 Entry by Component Agents for managed systemsDIAGNOSTICS AGENT 711
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 whereMicrosoft 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
28
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
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 ServiceMarketplace at servicesapcom~sapidb011000358700000074392009E and follow the chapters that applyto Planning and Consolidation
33 Configuring the Planning and Consolidation NETApplication Servers
Procedure
Modifying machineconfig Files
To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock occurrences that wouldcause the application server to ldquosleeprdquo and not process anymore you can modify the machineconfig file whichresides in the WINDOWSMicrosoftNETFramework64v4030319Config directory
1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to specifywhether to automatically configure settings to achieve optimal performance based on the machineconfiguration You can set this attribute to True or False
For more information see msdnmicrosoftcomen-uslibrary7w2sway1aspx
2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the Planning andConsolidation application) or Machineconfig (for all applications including Planning and Consolidation) toensure the validationKey and decryptionKey keys have the same value on all application servers Thisway when the authentication cookie is checked the authentication ticket used on one server can still be validon another server
For more information and sample Visual Basic code for generating random key values seemsdnmicrosoftcomen-uslibraryms998288aspxpaght000007_webfarmdeploymentconsiderationsand msdnmicrosoftcomen-uslibraryms998310aspx
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 DSNand 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 forODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory can accessthe Management Console with whatever rights they have been granted on the server For information about
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 29
removing default access and creating a group that can access the console see Removing Default Access to theConsole [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommend thatyou only grant Management Console access to system administrators Planning and Consolidation users shouldnot have any access For more information see Management Console Access Control [page 33]
6 Configure the use of SSL in Planning and Consolidation See Configuring Planning and Consolidation to useSSL [page 34]
7 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
8 Configure Microsoft SQL Server Reporting Services to use SSL See Configuring MS SQL Server ReportingServices to use SSL [page 36]
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 databaserole 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 optionto use ODBC Logging Enter the following values
DSN is BPC_ManagementDSN Table is BPCLog The Microsoft SQL Server Username and Password
5 Restart IIS
NoteWithout these updates the Management Console does work but some functionality (specifically User Activityand Service Status) does not work as expected
Should you need to uninstall Planning and Consolidation we recommend that you reset the Active Log Formatfield in IIS to W3C Extended Log File Format
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
30
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
Prerequisites
ODBC logging has been configured according to the Microsoft Knowledge Base article 245243 How to configureODBC 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 inApplicationHostconfig as shown here
ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0logFormat=Custom gtUse 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-00AA006111E0appcmd 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 articlespecified in the Prerequisites section Configure these settings in the ltodbcLogginggt node underltsystemwebServergt
Exampleltlocation path=Default Web SitegtltsystemwebServergtltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog userName=Usernamepassword=mypassword gtltsystemwebServergtltlocationgt
Use the following AppCmds to configure these attributes for the default Web site
appcmd set config Default Web Site sectionodbcLogging dataSourceBPC_ManagementDSN commitappHostappcmd set config Default Web Site sectionodbcLogging tableNameBPCLog commitappHostappcmd set config Default Web Site sectionodbcLogging userNameUsername commitappHostappcmd set config Default Web Site sectionodbcLogging passwordmypassword commitappHost
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 31
NoteYou cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must use the SQL ServerODBC driver For more information see the Microsoft Knowledge Base article 931202 The requirements for usingthe ODBC logging feature in IIS
343 Setting Up an ODBC Data Source in Windows Server2008 2008 R2 2012 or 2012 R2
Procedure
This procedure describes how to set up an ODBC data source for the Management Console in Windows Server 20082008 R2 2012 or 2012 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
NoteIf you have chosen SAP BusinessObjects User Management System in the installation screen you do not needto remove or configure access because the Management Console service always runs with the System Admin IDaccount which is a member of the Administrators group
Procedure
To remove default access to the Management Console and create a group that does have access to the console usethe procedure described below
32
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
NoteCreate your Management Console administrative group either on the server that hosts the Management Consoleor 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
NoteAlternatively you can perform analogous steps in Active Directory
3 In the Groups context menu choose New Group
4 Enter data as required Click Create
5 In the Computer Management dialog box choose Services and Applications Internet InformationServices 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 objectand all child objects Include these with entries explicitly defined here checkbox
NoteThis step is a necessary precursor to the completion of this procedure
10 In the Security dialog box click Copy to ensure that the System group retains its privileges
11 Remove access to the Management Console from all groups that should not have it
12 Choose Authentication in the center pane then disable Windows authentication
Result
Users who have not been granted access to the Management Console can still open the Management Console Webpage but it contains no data or menu options This does not affect the access that a user would otherwise have toPlanning and Consolidation
345 Management Console Access Control
After establishing the Management Console group you can add users or groups to it For more information aboutcreating this group see Removing Default Access to the Console [page 32] Their rights in Active Directory determinewhat they can access in the Console
By default any member of the Administrators Active Directory group on the application server or domain has fullaccess to all of the features of the Console except the Planning and Consolidation logging area Access to Planningand Consolidation logging is controlled within the Planning and Consolidation Administration Client task securityThe user must be granted View system logs task privileges For more information see the SAP Library Planning and
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 33
Consolidation Administrators Guide in servicesapcominstguidesepm-bpc 100 version for the Microsoftplatform
Your IT policy determines whether you grant access by group or user You may wish to create several levels of Consoleusers (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 describedin this table
Table 9
Privilege Rights Management Area
Task Manager and Kill Process Administrators group on application server or domain
Performance Monitor Counters Administrators group on application server or domain
Power Users group on application server or domain
Performance Monitor Users group on application server
Microsoft Analysis Services performance monitoring Administrators group on application server or domain
Microsoft SQL Server Monitoring (performance counters andstatistics)
Administrators group on application server or domain
346 Configuring Planning and Consolidation to use SSL
Procedure
Creating a Certificate for the Server
During the handshake phase of the SSL communication the server must send its certificate to the client The clientthen uses the certificate to encrypt information and send it back to the server
The procedure below describes how to create a self-signed certificate for the server
RecommendationWe recommend that you limit the use of self-signed certificates to testing only For a productive system you shouldobtain a certificate signed by a well-known certification authority (CA)
1 Start the Internet Information Services (IIS) Manager To do that go to Start All Programs AdministrativeTools Internet Information Services (IIS) Manager
2 In the Connections panel on the left-hand side select the server node and then choose Server Certificates
3 In the Actions panel on the right hand side choose the Create Self-Signed Certificate action
4 Enter the name that you want the certificate to be identified by for example MyTestSSLCertificate
IIS generates a new SSL certificate for you that has one yearrsquos expiry lease The certificate is issued to the local servername
Binding the Certificate to the Web Site
The procedure below describes how to bind the certificate to the web site for which SSL connections must be used
1 In the Connections panel select the web site node
2 In the Actions panel choose Bindings
34
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
3 In the Site Bindings dialog that appears choose the Add button to create a new binding
4 Configure the parameters as follows
Type = https IP Address = [1] - this is a shorthand expression for the local server name
Port = 443 - this is the default SSL port
SSL Certificate = enter your newly created certificate name
5 Choose OK to create the new binding and then close the Site Bindings dialog
6 Restart the IIS processes To do this choose Restart from the Actions panel
7 In the middle panel under the IIS section choose SSL Settings
8 In the SSL Settings screen select the Require SSL checkbox
9 In the Actions panel choose to Apply these settings
To test the SSL connection in the Actions panel choose the Browse [1] 443 (https) link
347 Using Client Certificates
To enable the use of client certificates in Planning and Consolidation you must follow several manual steps
NotePlanning and Consolidation supports client certificate authentication in Windows Authentication Mode butdoes 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 technetmicrosoftcomen-uslibrarycc753810aspx
For more information about configuring the client certificate mapping authentication see technetmicrosoftcomen-uslibrarycc732996(WS10)aspx
When you create the client certificates you can set the type of certificate in the SSL Settings screen in InternetInformation Services (IIS) Manager
Procedure
1 Set the options for client certificates
1 In the IIS Manager select the web site where you installed Planning and Consolidation
2 Choose SSL Settings
3 In the Client certificates section select the Accept client certificates option
This option allows you to use a client certificate or username and password (Basic authentication) toconnect 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 theManagementConsole home page
3 Double-click Authentication and enable Anonymous Authentication
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 35
4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way asin step 3
5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the sameway 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
348 Configuring MS SQL Server Reporting Services to useSSL
Procedure
The procedure below describes how to configure the use of SSL in Microsoft SQL Server Reporting Services
NoteReporting Services does not provide functionalities for generating requesting or installing a certificate Theserver certificates that you want to use for configuring SSL must have already been installed on your computer
1 Open the Reporting Services Configuration Manager program To do this open the Windows Start menu andnavigate to All Programs Microsoft SQL Server ltversiongt Configuration Tools Reporting ServicesConfiguration Manager
2 In the Connect panel on the left-hand side select the Web Service URL option to open all the Report Server webservice parameters
3 Configure the parameters as follows
SSL Certificate = the name of the certificate that you want to use
SSL Port = 4434 Choose Apply to confirm the changes
5 In the Connect panel choose Report Manager URL to open the list of parameters that link Reporting Servicesto IIS
6 Choose Advanced to add your new SSL web URL
7 In the section Multiple SSL Identities for Report Manager choose Add Configure the parameters as follows
IP Address = (All IPv4) SSL Port = 443 Certificate = the name of your SSL certificate
8 To test the configuration click the URL that appears under the Report manager Site Identification section
36
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
4 Installing Planning and ConsolidationAdministration Client and the SAPBusinessObjects EPM solutions Add-in forMicrosoft Office
The installation of the Planning and Consolidation Administration Client allows administrators to build and maintainPlanning and Consolidation environments and models and administer security
All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions add-in forMicrosoft 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 valueof the Planning and Consolidation client to prompt for user name and password Otherwise the Planning andConsolidation Start Page does not display
41 Installing the Administration Client
Prerequisites
NoteFor a definitive list of system requirements see the Product Availability Matrix on SAP Service Marketplace atservicesapcompam Search on Planning and Consolidation
The following list describes the minimum software requirements
Microsoft Internet Explorer 70 80 90 or 10
Microsoft Office 2003 2007 2010 or 2012
NET Framework 20 or higher (install any required NET Framework Hotfixes by referring tosupportmicrosoftcomkb)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 37
NoteWe recommend that you install all of the latest Microsoft Windows hotfixes prior to installing the Administrationclient For information about which hotfixes to install see updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us
Procedure
The 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 ltPC_serverportgtsapbpcweb
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 mustdownload the most recent version of the full setup (EPM Add-inexe) from the Service Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPCInstallation folder
Individual users can install the EPM add-in on their own machines by going to the Planning and Consolidation Homepage 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 upthe 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
38
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
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 toperform the upgrade If Client Auto Update is not enabled and a newer version is detected clients must be installedmanually 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 andpassword in the Admin ID and Admin password fields respectively The Admin ID should be a member of thelocal administrators group on all the computers running the auto update This setting is not needed if all usershave 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 Thisoption is stored in the user preferences and may also be turned on or off using the User Optionshellip menu itemIf 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 toinstall 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 installit 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 servicesapcom
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 versionand policy information For a support package these files are
EPM Addin Support Package ltSP versiongtmsp EPM Addin Support Package ltSP versiongtxmlFor a patch these files are
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 (WebsrvrWebBPCInstallation)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 39
You can set a different update policy for each package listed
ExampleThe following table illustrates some possible situations assuming that you have installed the first full version(V1)
Table 10
Available maintenancepackages
V2-user update
V3-force update
V4-force update
V5-user update
V5-user update V5-user update
V6-auto update
V7-force update
Minimum RequiredVersion
V4 V4 V7
Notification A prompt tells the user toinstall maintenancepackage V4 using theForced Update behavior
If User Update is enabledthe prompt informs theuser that maintenancepackage V5 is available
A prompt tells the user toinstall maintenancepackage V7 using theForced Update behavior
New Version V4 V4 or V5 V7
If you change the update policy for any package click Update to complete the change
40
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
5 Connection Issues
You may experience connection problems with ports the proxy server or programs and settings that interact withthese components If you have any issues related to connection review the following recommendations andtroubleshooting tips
51 Checking for Open Ports
You must ensure that all required ports are open for inboundoutbound traffic By default Planning andConsolidation requires that Ports 80 (used by http) and 1433 and 2383 (used by SQL Server 2008) are open Totest whether the required ports are open go to a command prompt and enter the Telnet serveripaddress and portFor example Telnet 431181836 80 If the system returns a blank command window the port is open If it returnsa message stating that it is unable to connect the port is not open
NoteYou can use the following site to scan for the normal ports It allows you to manually enter a port number to test
wwwmyserverorgportsniffasp
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 Planningand Consolidation server as an exception You can do this at the client level ( Internet Explorer ToolsInternet 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 fullyqualified 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 Consolidationauthentication Do not use authentication on the proxy server The system synchronizes the user name andpassword on the remote server with the local user name and password
SAP Business Planning and Consolidation 100Connection Issues
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 41
NoteFor more information about setting up an ISA proxy server contact SAP Support to request a copy of Setting upISA Proxy Server White Paper For more information about Business Planning and Consolidation firewall portssee SAP Note 1505250
Internet Explorer Settings Issues
Internet Explorer settings must be set correctly to prevent errors and problems when you attempt to access thePlanning 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 insertthe IP address or fully qualified server name of the Planning and Consolidation server as an exception bychoosing 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
42
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Connection Issues
6 Installing Planning and Consolidation withTwo Active Directory Domains
To set up a Planning and Consolidation 10 application server in a hosted environment and use your own domainusers follow this procedure In general you install Planning and Consolidation on the host domain use the hostdomain account and assign it to the Planning and Consolidation users SysAdmin Admin and Users Then you acceptone 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 andpassword 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 topromote 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 privilegefor the Planning and Consolidation server
5 Install Planning and Consolidation and assign your domain account either to the three Planning andConsolidation administrative users SysAdmin Admin and Users or to only one of the three Planning andConsolidation administrative users and to three of your users Be sure you use your own user account ratherthan host domain users
Planning and Consolidation impersonation can then access your domain from the host environment becauseit has the privilege of your domain account
SAP Business Planning and Consolidation 100Installing Planning and Consolidation with Two Active Directory Domains
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 43
7 Installing Planning and Consolidation in aTerminal Services or Citrix ServerDeployment
This section describes best practices and instructions for installing Planning and Consolidation in a Terminal Servicesor Citrix Server deployment
71 Terminal Services Home Directories
We recommend using Terminal Server home directories rather than using the userrsquos profile directory The profiledirectory downloads a minimal amount of information about the dimensions of the environment you are logging onto and may be as large as 2 MB per user The profile directory is on the system drive and has limited space Byspecifying 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 individualserver 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 clientserver (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
44
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
Procedure
The following steps outline how to install the Planning and Consolidation clients in a Terminal Services (TS) or CitrixServer deployment
1 Make sure the Terminal Services or Citrix Server machine has the system requirements installed
2 Log on to the Terminal Services or Citrix Server machine with a user ID that has the rights to install on thatserver
3 At a command prompt enter Change userinstall
4 Open a browser and connect to the URL ltPC_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_MSBPCAdminMainexe
74 Creating a Shortcut to the Launch Page
Procedure
If you use published desktops instead of published applications the Planning and Consolidation desktop file (whichis installed on the current userrsquos desktop) must be moved to the All UsersDesktop folder
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 45
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 SQLServer 2012 support the remote modification of SSIS packages Planning and Consolidation also supports theremote 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 whichyou want to modify SSIS packages
These custom tasks reference dlls that connect to the database server and perform certain validation when usersset up the parameters of each task All the custom task reference components must also be installed in the machineon which you want to modify SSIS packages
We provide a program that registers all the reference components of the custom tasks This section explains theinstallation 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 ndash This folder contains all the dlls that should be installed on the machine There are Planning andConsolidation platform components and all of the Data Manager custom task files
Config folder ndash This folder contains only one file named Filelistxml and lists all of the files that should be installedIf you need to add or remove certain components from the installation you can modify this xml file
OSoftSetupexe ndash This is the main executable file to run the installation package
NoteIf you are not installing SSIS Custom Tasks on your client machine ndash specifically a machine other than the Planningand Consolidation application server ndash you must first install OSoftSSIS2008_Client or OSoftSSIS2012_Client onthe client machine followed by the SQL Server version If you want to use SQL 2008 Tasks under the SQL 2012environment you must install OSoftSSIS2008_Client on the application server For detailed information see SAPNote 1707410 You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package byextracting OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPCInstallation folder on the Planning and Consolidation server To modify SSIS packages on the Planning andConsolidation application server you need to install OSoftSSIS2008_Client or OSoftSSIS2012_Client for creatinga COM+ application For more information see Before You Modify the SSIS Packages [page 49] and Setup ofa COM+ Application on the Application Server [page 50]
Bin folder
This folder contains the following components
46
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Table 11
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012respectively
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
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 47
Name Remark
BPCWriteBackdll
InteropDTSdll
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 addmore components to the installation package you can copy the new components into the Bin folder and add theproper xml tags in FileListxml You need to enter information for the following tags
RegistType ndash This is the registration information of the component You can enter the following values
RegAsm ndash For NET component
48
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Regsvr32 ndash For VB6 component
Gacutil ndash For NET Framework component that should be registered into Global Assembly Cache
FileName ndash Component file name
OSoftSetupexe
This is the executable file to run the SSIS installation package Double-click the file to start the installation You needto enter information for the following fields
Set SQL server
Specify the SQL server name If your SQL Server has an instance specify the instance name
NoteIf you installed the OSoftSSIS2008_Client or OSoftSSIS2012_Client on the application server the SQL servername is automatically disabled
Set server credential
This is the credential name of the COM+ package component Enter the user ID and password that can accessyour SQL Server This should be either the System Admin ID or Admin ID that was registered as a COM+ userwhen 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 ifyou 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 packagesremotely This is also true for the application server that has SSIS installed The Planning and ConsolidationData Manager has the following custom tasks
Table 12
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008and 2012 respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and2012 respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012respectively
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 49
Name Remark
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and2012 respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008and 2012 respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL2008 and 2012 respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and2012 respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012respectively
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
ltdrivegtWebsrvrbin2 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 FilesMicrosoft SQLServer paste all files into the CProgram Files (x86)Microsoft SQL Server100DTSTasksfolder
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
50
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Typographic Conventions
Table 13
Example Description
lt gt Angle brackets indicate that you replace these words or characters with appropriate entries tomake entries in the system for example Enter your ltUser Namegt
File Save Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
Example Textual cross-references to an internet address for example wwwsapcom
example Quicklinks added to the internet address of a homepage to enable quick access to specificcontent 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 titlespushbutton 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 namesof installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transactioncodes database table names and key concepts of a programming language when they aresurrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
SAP Business Planning and Consolidation 100Typographic Conventions
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 51
52
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
wwwsapcom
Material Number
- SAP Business 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 2008 R2 2012 or 2012 R2
- 344 Removing Default Access to the Console
- 345 Management Console Access Control
- 346 Configuring Planning and Consolidation to use SSL
- 347 Using Client Certificates
- 348 Configuring MS SQL Server Reporting Services to use SSL
-
- 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
-
1 Introduction
The SAP BusinessObjects Planning and Consolidation Installation Guide is intended for System Administrators whoperform Planning and Consolidation server and Administration client installations It contains everything you needto 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 releasewe provide detailed instructions on how to migrate your existing environments For more information see theUpgrade Guide which is available on SAP Service Marketplace at servicesapcominstguidesEPM-BPC Planningand Consolidation 100 version for the Microsoft platform
For more information about the Planning and Consolidation Office client software see the SAP BusinessObjects EPMsolutions 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 FileOLAP 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 2008or Windows Server 2008 R2 for remote desktop access
Planning and Consolidation no longer requires a separate Web server only an application server You can installthe application server on a single machine or on multiple machines with network load balancing (NLB) If youuse 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 informationon the installation as well as corrections to the installation documentation Make sure that you have the up-to-dateversion of each SAP Note which you can find in the SAP Service Marketplace at the Internet addressservicesapcomnotes
Table 2
SAP Note Number Title Comments
1584890 Documentation Addendum Contains information that does not yet appear in theapplication help of Business Planning and Consolidation100 version for the Microsoft platform Application helpis available at helpsapcombopacms100
2000499 Business Planning amp Consolidation 10 forMicrosoft SP14 Central Note
This note contains important information about theinstallation of support package 14
SAP Business Planning and Consolidation 100Introduction
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 9
SAP Note Number Title Comments
1961655 Business Planning amp Consolidation 10 forMicrosoft SP13 Central Note
This note contains important information about theinstallation of support package 13
1897745 Business Planning amp Consolidation 10 forMicrosoft SP12 Central Note
This note contains important information about theinstallation of support package 12
1846917 Business Planning amp Consolidation 10 forMicrosoft SP11 Central Note
This note contains important information about theinstallation of support package 11
1804918 Business Planning amp Consolidation 10 forMicrosoft SP10 Central Note
This note contains important information about theinstallation of support package 10
1755355 Business Planning amp Consolidation 10 forMicrosoft SP09 Central Note
This note contains important information about theinstallation of support package 9
1733053 Business Planning amp Consolidation 10 forMicrosoft SP08 Central Note
This note contains important information about theinstallation of support package 8
1689792 Business Planning amp Consolidation 10 forMicrosoft SP07 Central Note
This note contains important information about theinstallation of support package 7
1665656 Business Planning amp Consolidation 10 forMicrosoft SP06 Central Note
This note contains important information about theinstallation of support package 6
1643037 Business Planning amp Consolidation 10 forMicrosoft SP05 Central Note
This note contains important information about theinstallation of support package 5
1620464 Business Planning amp Consolidation 10 forMicrosoft SP04 Central Note
This note contains important information about theinstallation of support package 4
1601213 Business Planning amp Consolidation 10 forMicrosoft SP03 Central Note
This note contains important information about theinstallation of support package 3
1591848 Business Planning amp Consolidation 10 forMicrosoft SP02 Central Note
This note contains important information about theinstallation of support package 2
1573539 Business Planning amp Consolidation 10 forMicrosoft SP01 Central Note
This note contains important information about theinstallation of support package 1
12 Naming Conventions
In this document the following naming conventions apply
Table 3
Variable Description
ltPC_serverportgt Server name or IP address and port number of SAP Planningand Consolidation application location
ltdrivegt The drive where SAP Planning and Consolidation is installed
The default for this is CPC_MS
10
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Introduction
2 Installing Planning and ConsolidationServers
This section includes the basic steps for installing a Planning and Consolidation server the prerequisites and whatto 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 atservicesapcominstguidesepm-bpc 100 version for the Microsoft platform
2 Perform the tasks in the Before Starting the Planning and Consolidation Server Installation [page 13] sectionincluding installing all prerequisites
3 From the application server install the Planning and Consolidation server See Installing Planning andConsolidation on a Single Server [page 24]
NoteYou must install both Planning and Consolidation 100 as well as the most recent Planning and Consolidation100 Support Package available from the SAP Service Marketplace at servicesapcomswdc SoftwareDownloads Support Packages and Patches A - Z Index B SAP BPC FOR MICROSOFT SBOP PC 100FOR MICROSOFT Comprised Software Component Versions SAP CPM BPC 100 M Windows Server onx64 64bit
4 If you have multiple machines see Installing the Server in a Multiserver Configuration [page 25]
5 Perform the steps in the section After Installing Planning and Consolidation Servers [page 27]
22 Prerequisites
The following table describes the software you need to install before installing the Planning and Consolidation serverand the minimum versions required
NoteA list of the supported operating systems and database systems is also available in the Product Availability Matrixon SAP Service Marketplace at servicesapcompam Search on Planning and Consolidation
Table 4
Component Minimum Requirement
Operating System The requirements outlined below are for the following operating systems
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 11
Component Minimum Requirement
Windows Server 2008 (64-bit) Standard Enterprise or Data Center with or withoutHyper-V
Windows Server 2008 R2 (64-bit) Foundation Standard Enterprise or DataCenter with or without Hyper-V
Windows Server 2012 (64-bit) Standard Data Center
Windows Server 2012 R2 (64-bit) Standard Data Center
NoteThe operating system must be configured with NTFS
Relational Database Microsoft SQL Server 2008 Enterprise Edition
Microsoft SQL Server 2008 R2 (Gemini) Enterprise Edition
Microsoft SQL Server 2012 Enterprise Edition
OLAP Database Microsoft SQL Server 2008 Enterprise Edition ndash Analysis Server
Microsoft SQL Server 2008 R2 Enterprise Edition ndash Analysis Server
Microsoft SQL Server 2012 Enterprise Edition ndash Analysis Server
Data Integration Microsoft SQL Server 2008 Enterprise Edition ndash SQL Service Integration Services
Microsoft SQL Server 2008 R2 Enterprise Edition ndash SQL Service IntegrationServices
Microsoft SQL Server 2012 Enterprise Edition ndash 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
NET 35 and NET 45 are required for Windows 2012 and 2012 R2
NET 40 is required for all other operating systems
IIS
IIS 75 or IIS 70
(Included in your Operating System IIS 75 is required for Windows 2008 R2editions)
IIS 80 or IIS 85
(Included in your Operating System IIS 85 is required for Windows 2012 R2editions)
Anti-Cross Site Scripting Library 42
This component must be downloaded before installing the server The serverinstallation program asks for the path of each file and copies the files into theappropriate Planning and Consolidation path
Microsoft Visual C++ 2010 SP1 Redistributable Package (x64)
Microsoft Access Database Engine 2010 64bit
12
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
Component Minimum Requirement
VMWare ESX 3x or ESX 40
(Required only if a landscape deployment strategy using virtualizationtechnologies is planned)
NoteMSXML 40 SP2 ADOMDNET 100 and Microsoft Visual C++ 2010 SP1Redistributable Package (x64) are included with the installation program but notinstalled 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 values being returned withcalculated accounts For more information see SAP Note number 1429246 which also contains downloadinformation
We recommend SQL Server 2008 (or R2) Enterprise Edition or SQL Server 2012 Enterprise Edition for theOLAP database to support proactive cache and cube partitioning It is technically possible to use SQL Server2008 (or R2) Standard Edition or SQL Server 2012 Standard Edition for data integration servers but we donot recommend this
23 Before Starting the Planning and Consolidation ServerInstallation
You must perform the following tasks before starting your Planning and Consolidation server installation
Install all the prerequisite software including all of the latest Microsoft hotfixes For more information seeInstalling the Prerequisites [page 17]
If you access your application through a firewall verify with your network administrator which TCP ports tochoose during the installation By default port 80 is the setting for standard http access and port 443 is thesetting for https access If you require a service to listen on a different port you can specify it during theinstallation 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 onwhich 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 Consolidationand automatically overwrites the previous version If you have made any modifications to EnvironmentShellthat 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 ScriptBlocking
If a version of Planning and Consolidation on a NetWeaver platform exists uninstall it before you install Planningand Consolidation 100 version for the Microsoft platform
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 13
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 enterconvert c fsntfsV
All servers in a multiserver environment must be members of the same domain
In a multiserver environment the installing ID must be a domain user ID We recommend that you do not logon to the servers using a local server user ID even if the user ID is a member of the Administrator group on theserver This way you have the proper authority to install software and to modify the Component Services SeeLogging On to Servers [page 14]
You must determine the IP addresses or server names for all servers before installing Planning andConsolidation 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 portaccess reasons (DMZ WORKGROUP or nontrusted domain authentication failures) do the following
1 Copy the EnvironmentShell database file ServerEnvironmentShelldb10 from the Planning andConsolidation 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 theEnvironmentShell database file in the Server Information Advanced Options Local path forEnvironmentShell DB field (for example cEnvironmentShelldb10)
Install the Anti-Cross Site Scripting Library which provides protection to Web-based applications againstCross-Site Scripting (XSS) attacks See Installing the Anti-Cross Site Scripting Library [page 23]
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 theAdministrator group of a domain to which the server belongs or a member of the Administrator group on the localserver
Errors may display during the installation program and in the diagnostic program if the installing user is not assignedto the Administrator group directly but is assigned to a group with Administrator rights You can ignore thesemessages
NoteIf you change the password used to install Planning and Consolidation you must change the password for theapplicable Planning and Consolidation service To do this go to Server Manager on the application server andselect Server Reset Logon Credentials For more information see the SAP Planning and ConsolidationOperations Guide in servicesapcominstguidesepm-bpc 100 for the Microsoft Platform SBOP Plan amp Consol100 MS Administrators Guide
14
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
25 Service-level Accounts
Service accounts are Windows domain IDs with access to all Planning and Consolidation servers with varying levelsof privileges They allow the software to use the minimum amount of privilege required for each job making it moresecure
You must define these user IDs on the Windows machine For security purposes they should not be used to definePlanning and Consolidation users
Prerequisites
Planning and Consolidation 100 has the following Windows services
BPC SendGovernor which manages Microsoft Analysis Service locks to ensure consistent performance andavoid deadlocks
BPC ServiceManager which manages the System Landscape Directory (SLD) service logging service andglobal caches
BPC CTS ServiceManager which listens and handles CTS import requests from the CTS+ transportmanagement system
Since these services should be able to access to the FileShare server an Admin account is assigned automaticallyto the service during the installation of the Planning and Consolidation server program Even though an Adminaccount 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 serviceon the local machine This logon right strictly applies only to the local computer and must be granted in the LocalSecurity Policy
To edit the Local Security Policy of the computer you want to define the logon as a service permission performthe 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 supportmicrosoftcomkb259733
Features
During the installation enter user IDs and passwords for the following user types
System Admin ID
This ID is read-only and is the same as the installation user ID that is the system displays the ID on theinstallation screen but you cannot modify it This ID allows access to code that provides system administrator-level functionality For example this ID can write to the Windows registry has full access to the FileShare server
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 15
and can create remove backup and restore OLAP and SQL databases The system administrator should be amember 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 createsubdirectory access on the FileShare server readwrite metadata and application set database data in OLAPand can create and remove tables in SQL The Administrator should be a member of the domain users groupand 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 theservers has write access to FileShare data and can read metadata and data in OLAP and SQL The User IDmust 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 isinstalled you can change these settings using the Server Manager
NoteWhen defining server names the name refers to the NetBIOS name IP address and fully qualified domain names(FQDN)
Standard Settings
Standard settings are typically used for a single-server environment The following table describes each setting
Table 5
Server Option Value Description
SQL Database server name The name of the SQL DB server
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 computername
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
Table 6
Server Option Value Description
SQL Server Name The name of the SQL DB server Defaults to the local server
Instance name The SQL instance name If left blank the default instance is used
16
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
Server Option Value Description
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 computername
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 forhttp and 443 is the default for https
Authentication type Note If you have chosen SAP BusinessObjects User Management System in theinstallation screen Authentication type does not appear in Advanced settings (asthat IIS authentication type is Anonymous in CMS mode)
Windows or Kerberos The default is Windows If you change this value fromWindows to Kerberos you must make some additional changes
See the Kerberos authentication settings section in the SAP Library ServerManager Guide on servicesapcominstguidesEPM-BPC 100 for theMicrosoft Platform
Scheduler Server Name The name of the server used for scheduling usually the application server forexample GMPV50072862B If you have multiple application servers select theappropriate one
NoteIf the primary server stops working you must manually configure yourapplication 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 theoperating system IIS SQL server analysis services ADOMDNET and MSXML This section provides guidance on
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 17
installing each component For specific versions required see Prerequisites [page 11] and the Product AvailabilityMatrix on the SAP Service Marketplace at servicesapcompam Search on Planning and Consolidation
NoteTo ensure a successful installation you must install the software in the order listed in this procedure
Check all third-party infrastructure services to ensure that they are functioning and that their authenticationmodels 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 itsown 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 applicationserver before you start the installation You can find the UMC installation package (UMCexe) on the Planningand Consolidation CD in a folder called UMC_100_INSTALLER When you run the installation package the wizardguides 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 andConsolidation)
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 multiserverconfiguration See Installing the Operating System [page 19]
3 Install the latest service pack for your operating system To install this service pack go towwwmicrosoftcom
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 SQLServer [page 19]
6 From your SQL Server media install Analysis Services Enterprise Edition and its required service packs and hotfixes See Installing Analysis Services [page 23]
7 On your application server install ADOMDNET The Planning and Consolidation zip file contains theADOMDNET 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 followinglocation BPC SetupServermsxmlmsi
18
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
9 On your application server install Microsoft Visual C++ 2010 SP1 Redistributable Package (x64)
The Microsoft Visual C++ 2010 SP1 Redistributable Package (x64) installation package is contained in thePlanning and Consolidation zip file at the following location BPC SetupServervcredist_x64exe
NoteThe version of vcredist_x64exe in BPC SetupServer has been updated to 10040219 If you have aprevious 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 wwwmicrosoftcomdownloadsendetailsaspxFamilyID=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 Marketplaceat servicesapcompam Search on Planning and Consolidation
Business Planning and Consolidation can support all servers with an operating system in any language
NoteCurrently Business Planning and Consolidation does not support an operating system in bi-directionallanguages such as Hebrew
Procedure
If you are installing IIS 70 75 80 or 85 you must enable the following features
Enable Basic Authentication and Windows Authentication these are not installed by default
Install IIS 6 Metabase Compatibility role
Business Planning and Consolidation uses the ADSI provider to handle IIS administration such as virtualdirectory and security but IIS 7 does not install the ADSI provider by default
273 Installing the SQL Server
Prerequisites
During the installation procedure you have the opportunity to specify the location of the EnvironmentShell databasefile Check that it is possible to access EnvironmentShell from the location where you intend to install the SQL serverIf it is not possible for port access reasons (DMZ WORKGROUP or nontrusted domain authentication failures) copyEnvironmentShell to a location on the SQL server (for example CEnvironmentShelldb10) You specify thislocation on the Server Information page by choosing Server Information Advanced Options Local Path forEnvironmentShell DB
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 19
Procedure
This section describes the general steps for installing the SQL Server component options and considerations wheninstalling 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
NoteIf you encounter a 500 HTTP Error when trying to connect to the Planning and Consolidation Web Client referto Microsoft Support articles 2520479 and 2468871 for assistance
To reinforce security we recommend that you install the SQL server and SSAS components to a nondefaultinstance 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 Optionssection below then choose Next
4 Review disc space requirements then choose Next
5 In Server Configuration Perform the following actions
1 In the Service Accounts tab enter a Planning and Consolidation sysadmin account for the SQL ServerDatabase Engine and the SQL Server Analysis services This is required so that the Planning andConsolidation sysadmin can create and process the Planning and Consolidation database because theMicrosoft SQL server tries to back up or restore database with the privileged account This account is alsorequired 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 differentdomain 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 theapplication server and the account requires the folder access privilege for the application server
To ensure that you have the complete access privileges we recommend the Planning and Consolidationsysadmin 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 touse a restrictive SQL ID that works with the drill-through feature If you must restrict SQL authentication forsecurity 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 installationprogram
20
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
8 Choose Install to begin the installation with the options you have set
SQL Server Component Options
For Single-Machine Installations
Install the following components from the Feature Selection screen
Database Engine Services
Analysis Services
Integration Service which is listed as one of the Shared Features
For Multiple Machine Installations
For multiple machine installations install the following components on each server
Table 7
Server Component What to Install
SQL Server Database Engine Services
SSAS Server Analysis Services
Application Server The following Shared Features
Client Tools Connectivity
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 Server2008 R2 and SQL Server 2012
Process Dimension
It is now possible to process a dimension with multiple selections At processing time the process dimension modulemakes changed or added information for each dimension and process for all selected dimensions and cubes inparallel
Optimize Model
If there are custom partitions for a FACT partition in the OLAP database an optimization module can process custompartitions in parallel when Full or Incremental Optimize is performed However if a full optimize is performed withthe 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 parallelbecause 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 applicationserver and application set databases
NoteSetting the SQL isolation level to be Read Committed Snapshot mode for a database can only be done once andcannot be reversed
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 21
Real Time MOLAP
You can set the OLAP storage model of the write-back partition to be MOLAP (Multidimensional OLAP) This settingremains 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 asfollows
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 Servertrade20052008 which you can download from wwwmicrosoftcom (search on ldquoTable Partitioningrdquo to find all relevantarticles)
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 Thebrowser 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 localhostand external network interface machine
3 If you want to use IP1 which indicates Server IP set Enabled to Yes and specify the TCP Port as desired
4 Delete 0 from TCP Dynamic Ports Set IPAll - TCP Ports as desired (for example 1533)
RecommendationWe do not recommend using dynamic ports
In an SQL server the default instance has a listener which listens on a fixed port (TCP port 1433)However for the named instance the port on which the SQL server listens is random and dynamicallyselected when the named instance of the SQL server starts This recommendation prevents any conflictproblems
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 Setthe 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 thatthe user identified as the Log on as user has the sysadmin SQL Server role defined under Server Roles in theSQL Server Management Studio This is required so Analysis Services can process the SQL Server
From SQL Server Management Studio do the following tasks
22
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
1 If you want to use a port with a named instance select the server type Analysis Services select the servername (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 ServerProperties window displays which shows all configurable properties
3 For enhanced security change the default value to your port number (for example 2724) This means thatyou use a fixed port as for the SQL Server option Then choose OK
NoteWe do not support a nondefault port with the default instance in this release If you want to use the defaultinstance do not change the port number
Restart SQL and OLAP
Confirm that the installation has completed successfully by checking that there are no installation relatedproblems on the event viewer You can now install Planning and Consolidation
274 Installing Analysis Services
Procedure
After you install SQL Server and its required service packs and hotfixes you must install SQL Server Analysis Servicesand its required service packs and hotfixes
NoteIf you have migrated your Analysis Services repository to the SQL Server back up the database that contains therepository before installing this release
To install Analysis Services for SQL Server 2008 SQL Server 2008 R2 or SQL Server 2012 follow the steps andguidelines in technetmicrosoftcomen-uslibraryms143219aspx
To avoid slow performance when a user has more than six OLAP databases follow the steps and guidelines in thePerformance Guide for SQL 2008 at wwwmicrosoftcomdownloadsdetailsaspxFamilyID=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 tohave it available for the Planning and Consolidation installation program
1 Download the Anti-Cross Site Scripting Library file AntiXSSLibraryDLL from the Microsoft Web site atwwwmicrosoftcomdownloadendetailsaspxid=28589
2 Save the extracted file locally
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 23
When you install Planning and Consolidation Server a step in the process requires you to identify the path toAntiXssLibrarydll
28 Installing on a Single Server
When you install all Planning and Consolidation server components on a single server you should consider thefollowing 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 theuncompressed 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 Log on to the server with a local server user ID or domain user ID For more information see Logging on toservers [page 14]
3 Make sure all prerequisite software is installed on the server For more information see Installing thePrerequisites [page 17]
4 Obtain SAP Planning and Consolidation archive from the Downloads SAP Installations amp Upgrades areaof SAP Service Marketplace
5 Extract the files from the archive Go to the BPC Setup folder and run the StartUpexe file
6 From the Server Install screen select Install the Planning and Consolidation server
7 From the Welcome screen choose Next
8 From the License Agreement page choose I accept the terms of the license agreement then choose Next
9 From the Installation Method page accept the default Single machine enter a system ID for the systemlandscape directory (SLD) and choose Next
NoteEntering a system ID of the SLD is only required if you have a SAP Solution Manager license If you do nothave a SAP Solution Manager license you can leave this field empty
10 From the Authentication Method page choose the desired authentication method and choose Next
11 If you have chosen SAP BusinessObjects User Management System in the previous screen on the CMSAuthentication page enter the information required to log on to CMS as an administrator
The following information is required
24
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
Table 8
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 Thisgroup name is filtered as the default when adding a user in Planning andConsolidation Administration Use a comma ( ) to separate multiple names
12 After entering the CMS administrator authentication details choose Next
13 From the Service type accounts page enter service-level account user IDs and passwords See Service-LevelAccounts [page 15]
14 After defining the IDs and passwords choose Next
15 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 chooseNext
16 Specify the location and name of AntiXssLibrarydll See Installing the Anti-Cross Site ScriptingLibrary [page 23]
Choose Next
17 Select destination folders for Programs and Data The Data files include Webfolders and FileDB (publishedreports) and should be installed on a separate drive in a production environment This recommendation reducesthe hard disk IO time and helps to speed up SQL commands
Accept the defaults or make your selections then choose Next
18 Select the default values for the Web client The values are used to determine the default language and regionfor the Web client when you connect to it You can change the values in the Planning and Consolidation ServerManager
19 The installation process takes a few moments When it is complete choose Exit
20 A prompt is displayed to restart your computer Select OK to restart
21 Perform the steps in After Installing Planning and Consolidation Servers [page 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 avariety of ways and configure the servers as a Network Load Balancing (NLB) environment
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 25
The recommended Planning and Consolidation practice is to assign resources using a round robin approach for loadbalancing
You can install the SQL OLAP and FileShare types remotely from the application server You need to performadditional server installations if you have multiple application servers
Installing each Planning and Consolidation application server in a multiserver (NLB) configuration is identical to theprocedure 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 Balancingenvironment With this option there is an additional choice to Include sample environment (required on only oneof the application servers) This is because when you install the application server it connects to the databaseserver and creates the sample environment (EnvironmentShell) Installing the sample environment is requiredon 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
26
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
3 After Installing Planning and ConsolidationServers
31 Post-Installation Steps
Procedure
Perform these steps after installing the Planning and Consolidation servers for new installations of Planning andConsolidation
1 Connect your Planning and Consolidation system to Solution Manager Diagnostics (SMD) to allow support staffto identify analyze and resolve problems with your application See Connecting to Solution ManagerDiagnostics [page 28]
2 Configure the Planning and Consolidation NET and application server to ensure that it and its related servicesfunction properly and reliably For more information see Configuring the Planning and Consolidation NETApplication Server [page 29]
3 Optional configuration steps [page 29]
1 To ensure proper functioning of the Management Console create an SQL user and modify the System DSNand 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 loggingfor ODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default WebSite [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory canaccess the Management Console with whatever rights they have been granted on the server Forinformation about removing default access and creating a group that can access the console see RemovingDefault Access to the Console [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommendthat you only grant Management Console access to system administrators Planning and Consolidationusers should not have any access For more information see Management Console AccessControl [page 33]
6 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
4 Take the following steps to set up security
If you are defining security and application structure continue with step 5
If you want to designate someone other than the system administrator to manage security and applicationstructure log on to EnvironmentShell designate a user as a Primary Administrator
This user must have Administration ndash Environment and Security ‒ Define User task rights so that he or shecan 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 SeeInstalling the Administration Client [page 37]
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 27
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 taskprofiles 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 mustcomplete this step since there is no access to dimensions or members)
NoteTo allow users to request and query large amounts of data you can edit the metabasexml file located at CWindowssystem32inetsrv Set the following parameters to the stated values
ASPBUFFERINGLIMIT = 10485760
MAXREQUESTENTITYALLOWED = 10485760
32 Connecting to Solution Manager Diagnostics
NoteYou only need to perform the steps in this section if you have a SAP Solution Manager licence
The diagnostics functions in SAP Solution Manager allow identification analysis and resolution of problems Thisprocedure 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 areinstalled
NoteInstallation files for Diagnostics Agent are available on Service Marketplace by navigating to SupportPackages and Patches mdash Entry by Application Group SAP Technology Components SAP SOLUTIONMANAGER SAP SOLUTION MANAGER 70 EHP 1 Entry by Component Agents for managed systemsDIAGNOSTICS AGENT 711
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 whereMicrosoft 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
28
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
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 ServiceMarketplace at servicesapcom~sapidb011000358700000074392009E and follow the chapters that applyto Planning and Consolidation
33 Configuring the Planning and Consolidation NETApplication Servers
Procedure
Modifying machineconfig Files
To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock occurrences that wouldcause the application server to ldquosleeprdquo and not process anymore you can modify the machineconfig file whichresides in the WINDOWSMicrosoftNETFramework64v4030319Config directory
1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to specifywhether to automatically configure settings to achieve optimal performance based on the machineconfiguration You can set this attribute to True or False
For more information see msdnmicrosoftcomen-uslibrary7w2sway1aspx
2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the Planning andConsolidation application) or Machineconfig (for all applications including Planning and Consolidation) toensure the validationKey and decryptionKey keys have the same value on all application servers Thisway when the authentication cookie is checked the authentication ticket used on one server can still be validon another server
For more information and sample Visual Basic code for generating random key values seemsdnmicrosoftcomen-uslibraryms998288aspxpaght000007_webfarmdeploymentconsiderationsand msdnmicrosoftcomen-uslibraryms998310aspx
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 DSNand 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 forODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory can accessthe Management Console with whatever rights they have been granted on the server For information about
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 29
removing default access and creating a group that can access the console see Removing Default Access to theConsole [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommend thatyou only grant Management Console access to system administrators Planning and Consolidation users shouldnot have any access For more information see Management Console Access Control [page 33]
6 Configure the use of SSL in Planning and Consolidation See Configuring Planning and Consolidation to useSSL [page 34]
7 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
8 Configure Microsoft SQL Server Reporting Services to use SSL See Configuring MS SQL Server ReportingServices to use SSL [page 36]
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 databaserole 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 optionto use ODBC Logging Enter the following values
DSN is BPC_ManagementDSN Table is BPCLog The Microsoft SQL Server Username and Password
5 Restart IIS
NoteWithout these updates the Management Console does work but some functionality (specifically User Activityand Service Status) does not work as expected
Should you need to uninstall Planning and Consolidation we recommend that you reset the Active Log Formatfield in IIS to W3C Extended Log File Format
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
30
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
Prerequisites
ODBC logging has been configured according to the Microsoft Knowledge Base article 245243 How to configureODBC 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 inApplicationHostconfig as shown here
ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0logFormat=Custom gtUse 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-00AA006111E0appcmd 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 articlespecified in the Prerequisites section Configure these settings in the ltodbcLogginggt node underltsystemwebServergt
Exampleltlocation path=Default Web SitegtltsystemwebServergtltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog userName=Usernamepassword=mypassword gtltsystemwebServergtltlocationgt
Use the following AppCmds to configure these attributes for the default Web site
appcmd set config Default Web Site sectionodbcLogging dataSourceBPC_ManagementDSN commitappHostappcmd set config Default Web Site sectionodbcLogging tableNameBPCLog commitappHostappcmd set config Default Web Site sectionodbcLogging userNameUsername commitappHostappcmd set config Default Web Site sectionodbcLogging passwordmypassword commitappHost
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 31
NoteYou cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must use the SQL ServerODBC driver For more information see the Microsoft Knowledge Base article 931202 The requirements for usingthe ODBC logging feature in IIS
343 Setting Up an ODBC Data Source in Windows Server2008 2008 R2 2012 or 2012 R2
Procedure
This procedure describes how to set up an ODBC data source for the Management Console in Windows Server 20082008 R2 2012 or 2012 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
NoteIf you have chosen SAP BusinessObjects User Management System in the installation screen you do not needto remove or configure access because the Management Console service always runs with the System Admin IDaccount which is a member of the Administrators group
Procedure
To remove default access to the Management Console and create a group that does have access to the console usethe procedure described below
32
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
NoteCreate your Management Console administrative group either on the server that hosts the Management Consoleor 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
NoteAlternatively you can perform analogous steps in Active Directory
3 In the Groups context menu choose New Group
4 Enter data as required Click Create
5 In the Computer Management dialog box choose Services and Applications Internet InformationServices 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 objectand all child objects Include these with entries explicitly defined here checkbox
NoteThis step is a necessary precursor to the completion of this procedure
10 In the Security dialog box click Copy to ensure that the System group retains its privileges
11 Remove access to the Management Console from all groups that should not have it
12 Choose Authentication in the center pane then disable Windows authentication
Result
Users who have not been granted access to the Management Console can still open the Management Console Webpage but it contains no data or menu options This does not affect the access that a user would otherwise have toPlanning and Consolidation
345 Management Console Access Control
After establishing the Management Console group you can add users or groups to it For more information aboutcreating this group see Removing Default Access to the Console [page 32] Their rights in Active Directory determinewhat they can access in the Console
By default any member of the Administrators Active Directory group on the application server or domain has fullaccess to all of the features of the Console except the Planning and Consolidation logging area Access to Planningand Consolidation logging is controlled within the Planning and Consolidation Administration Client task securityThe user must be granted View system logs task privileges For more information see the SAP Library Planning and
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 33
Consolidation Administrators Guide in servicesapcominstguidesepm-bpc 100 version for the Microsoftplatform
Your IT policy determines whether you grant access by group or user You may wish to create several levels of Consoleusers (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 describedin this table
Table 9
Privilege Rights Management Area
Task Manager and Kill Process Administrators group on application server or domain
Performance Monitor Counters Administrators group on application server or domain
Power Users group on application server or domain
Performance Monitor Users group on application server
Microsoft Analysis Services performance monitoring Administrators group on application server or domain
Microsoft SQL Server Monitoring (performance counters andstatistics)
Administrators group on application server or domain
346 Configuring Planning and Consolidation to use SSL
Procedure
Creating a Certificate for the Server
During the handshake phase of the SSL communication the server must send its certificate to the client The clientthen uses the certificate to encrypt information and send it back to the server
The procedure below describes how to create a self-signed certificate for the server
RecommendationWe recommend that you limit the use of self-signed certificates to testing only For a productive system you shouldobtain a certificate signed by a well-known certification authority (CA)
1 Start the Internet Information Services (IIS) Manager To do that go to Start All Programs AdministrativeTools Internet Information Services (IIS) Manager
2 In the Connections panel on the left-hand side select the server node and then choose Server Certificates
3 In the Actions panel on the right hand side choose the Create Self-Signed Certificate action
4 Enter the name that you want the certificate to be identified by for example MyTestSSLCertificate
IIS generates a new SSL certificate for you that has one yearrsquos expiry lease The certificate is issued to the local servername
Binding the Certificate to the Web Site
The procedure below describes how to bind the certificate to the web site for which SSL connections must be used
1 In the Connections panel select the web site node
2 In the Actions panel choose Bindings
34
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
3 In the Site Bindings dialog that appears choose the Add button to create a new binding
4 Configure the parameters as follows
Type = https IP Address = [1] - this is a shorthand expression for the local server name
Port = 443 - this is the default SSL port
SSL Certificate = enter your newly created certificate name
5 Choose OK to create the new binding and then close the Site Bindings dialog
6 Restart the IIS processes To do this choose Restart from the Actions panel
7 In the middle panel under the IIS section choose SSL Settings
8 In the SSL Settings screen select the Require SSL checkbox
9 In the Actions panel choose to Apply these settings
To test the SSL connection in the Actions panel choose the Browse [1] 443 (https) link
347 Using Client Certificates
To enable the use of client certificates in Planning and Consolidation you must follow several manual steps
NotePlanning and Consolidation supports client certificate authentication in Windows Authentication Mode butdoes 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 technetmicrosoftcomen-uslibrarycc753810aspx
For more information about configuring the client certificate mapping authentication see technetmicrosoftcomen-uslibrarycc732996(WS10)aspx
When you create the client certificates you can set the type of certificate in the SSL Settings screen in InternetInformation Services (IIS) Manager
Procedure
1 Set the options for client certificates
1 In the IIS Manager select the web site where you installed Planning and Consolidation
2 Choose SSL Settings
3 In the Client certificates section select the Accept client certificates option
This option allows you to use a client certificate or username and password (Basic authentication) toconnect 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 theManagementConsole home page
3 Double-click Authentication and enable Anonymous Authentication
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 35
4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way asin step 3
5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the sameway 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
348 Configuring MS SQL Server Reporting Services to useSSL
Procedure
The procedure below describes how to configure the use of SSL in Microsoft SQL Server Reporting Services
NoteReporting Services does not provide functionalities for generating requesting or installing a certificate Theserver certificates that you want to use for configuring SSL must have already been installed on your computer
1 Open the Reporting Services Configuration Manager program To do this open the Windows Start menu andnavigate to All Programs Microsoft SQL Server ltversiongt Configuration Tools Reporting ServicesConfiguration Manager
2 In the Connect panel on the left-hand side select the Web Service URL option to open all the Report Server webservice parameters
3 Configure the parameters as follows
SSL Certificate = the name of the certificate that you want to use
SSL Port = 4434 Choose Apply to confirm the changes
5 In the Connect panel choose Report Manager URL to open the list of parameters that link Reporting Servicesto IIS
6 Choose Advanced to add your new SSL web URL
7 In the section Multiple SSL Identities for Report Manager choose Add Configure the parameters as follows
IP Address = (All IPv4) SSL Port = 443 Certificate = the name of your SSL certificate
8 To test the configuration click the URL that appears under the Report manager Site Identification section
36
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
4 Installing Planning and ConsolidationAdministration Client and the SAPBusinessObjects EPM solutions Add-in forMicrosoft Office
The installation of the Planning and Consolidation Administration Client allows administrators to build and maintainPlanning and Consolidation environments and models and administer security
All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions add-in forMicrosoft 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 valueof the Planning and Consolidation client to prompt for user name and password Otherwise the Planning andConsolidation Start Page does not display
41 Installing the Administration Client
Prerequisites
NoteFor a definitive list of system requirements see the Product Availability Matrix on SAP Service Marketplace atservicesapcompam Search on Planning and Consolidation
The following list describes the minimum software requirements
Microsoft Internet Explorer 70 80 90 or 10
Microsoft Office 2003 2007 2010 or 2012
NET Framework 20 or higher (install any required NET Framework Hotfixes by referring tosupportmicrosoftcomkb)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 37
NoteWe recommend that you install all of the latest Microsoft Windows hotfixes prior to installing the Administrationclient For information about which hotfixes to install see updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us
Procedure
The 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 ltPC_serverportgtsapbpcweb
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 mustdownload the most recent version of the full setup (EPM Add-inexe) from the Service Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPCInstallation folder
Individual users can install the EPM add-in on their own machines by going to the Planning and Consolidation Homepage 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 upthe 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
38
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
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 toperform the upgrade If Client Auto Update is not enabled and a newer version is detected clients must be installedmanually 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 andpassword in the Admin ID and Admin password fields respectively The Admin ID should be a member of thelocal administrators group on all the computers running the auto update This setting is not needed if all usershave 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 Thisoption is stored in the user preferences and may also be turned on or off using the User Optionshellip menu itemIf 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 toinstall 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 installit 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 servicesapcom
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 versionand policy information For a support package these files are
EPM Addin Support Package ltSP versiongtmsp EPM Addin Support Package ltSP versiongtxmlFor a patch these files are
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 (WebsrvrWebBPCInstallation)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 39
You can set a different update policy for each package listed
ExampleThe following table illustrates some possible situations assuming that you have installed the first full version(V1)
Table 10
Available maintenancepackages
V2-user update
V3-force update
V4-force update
V5-user update
V5-user update V5-user update
V6-auto update
V7-force update
Minimum RequiredVersion
V4 V4 V7
Notification A prompt tells the user toinstall maintenancepackage V4 using theForced Update behavior
If User Update is enabledthe prompt informs theuser that maintenancepackage V5 is available
A prompt tells the user toinstall maintenancepackage V7 using theForced Update behavior
New Version V4 V4 or V5 V7
If you change the update policy for any package click Update to complete the change
40
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
5 Connection Issues
You may experience connection problems with ports the proxy server or programs and settings that interact withthese components If you have any issues related to connection review the following recommendations andtroubleshooting tips
51 Checking for Open Ports
You must ensure that all required ports are open for inboundoutbound traffic By default Planning andConsolidation requires that Ports 80 (used by http) and 1433 and 2383 (used by SQL Server 2008) are open Totest whether the required ports are open go to a command prompt and enter the Telnet serveripaddress and portFor example Telnet 431181836 80 If the system returns a blank command window the port is open If it returnsa message stating that it is unable to connect the port is not open
NoteYou can use the following site to scan for the normal ports It allows you to manually enter a port number to test
wwwmyserverorgportsniffasp
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 Planningand Consolidation server as an exception You can do this at the client level ( Internet Explorer ToolsInternet 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 fullyqualified 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 Consolidationauthentication Do not use authentication on the proxy server The system synchronizes the user name andpassword on the remote server with the local user name and password
SAP Business Planning and Consolidation 100Connection Issues
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 41
NoteFor more information about setting up an ISA proxy server contact SAP Support to request a copy of Setting upISA Proxy Server White Paper For more information about Business Planning and Consolidation firewall portssee SAP Note 1505250
Internet Explorer Settings Issues
Internet Explorer settings must be set correctly to prevent errors and problems when you attempt to access thePlanning 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 insertthe IP address or fully qualified server name of the Planning and Consolidation server as an exception bychoosing 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
42
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Connection Issues
6 Installing Planning and Consolidation withTwo Active Directory Domains
To set up a Planning and Consolidation 10 application server in a hosted environment and use your own domainusers follow this procedure In general you install Planning and Consolidation on the host domain use the hostdomain account and assign it to the Planning and Consolidation users SysAdmin Admin and Users Then you acceptone 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 andpassword 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 topromote 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 privilegefor the Planning and Consolidation server
5 Install Planning and Consolidation and assign your domain account either to the three Planning andConsolidation administrative users SysAdmin Admin and Users or to only one of the three Planning andConsolidation administrative users and to three of your users Be sure you use your own user account ratherthan host domain users
Planning and Consolidation impersonation can then access your domain from the host environment becauseit has the privilege of your domain account
SAP Business Planning and Consolidation 100Installing Planning and Consolidation with Two Active Directory Domains
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 43
7 Installing Planning and Consolidation in aTerminal Services or Citrix ServerDeployment
This section describes best practices and instructions for installing Planning and Consolidation in a Terminal Servicesor Citrix Server deployment
71 Terminal Services Home Directories
We recommend using Terminal Server home directories rather than using the userrsquos profile directory The profiledirectory downloads a minimal amount of information about the dimensions of the environment you are logging onto and may be as large as 2 MB per user The profile directory is on the system drive and has limited space Byspecifying 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 individualserver 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 clientserver (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
44
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
Procedure
The following steps outline how to install the Planning and Consolidation clients in a Terminal Services (TS) or CitrixServer deployment
1 Make sure the Terminal Services or Citrix Server machine has the system requirements installed
2 Log on to the Terminal Services or Citrix Server machine with a user ID that has the rights to install on thatserver
3 At a command prompt enter Change userinstall
4 Open a browser and connect to the URL ltPC_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_MSBPCAdminMainexe
74 Creating a Shortcut to the Launch Page
Procedure
If you use published desktops instead of published applications the Planning and Consolidation desktop file (whichis installed on the current userrsquos desktop) must be moved to the All UsersDesktop folder
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 45
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 SQLServer 2012 support the remote modification of SSIS packages Planning and Consolidation also supports theremote 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 whichyou want to modify SSIS packages
These custom tasks reference dlls that connect to the database server and perform certain validation when usersset up the parameters of each task All the custom task reference components must also be installed in the machineon which you want to modify SSIS packages
We provide a program that registers all the reference components of the custom tasks This section explains theinstallation 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 ndash This folder contains all the dlls that should be installed on the machine There are Planning andConsolidation platform components and all of the Data Manager custom task files
Config folder ndash This folder contains only one file named Filelistxml and lists all of the files that should be installedIf you need to add or remove certain components from the installation you can modify this xml file
OSoftSetupexe ndash This is the main executable file to run the installation package
NoteIf you are not installing SSIS Custom Tasks on your client machine ndash specifically a machine other than the Planningand Consolidation application server ndash you must first install OSoftSSIS2008_Client or OSoftSSIS2012_Client onthe client machine followed by the SQL Server version If you want to use SQL 2008 Tasks under the SQL 2012environment you must install OSoftSSIS2008_Client on the application server For detailed information see SAPNote 1707410 You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package byextracting OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPCInstallation folder on the Planning and Consolidation server To modify SSIS packages on the Planning andConsolidation application server you need to install OSoftSSIS2008_Client or OSoftSSIS2012_Client for creatinga COM+ application For more information see Before You Modify the SSIS Packages [page 49] and Setup ofa COM+ Application on the Application Server [page 50]
Bin folder
This folder contains the following components
46
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Table 11
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012respectively
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
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 47
Name Remark
BPCWriteBackdll
InteropDTSdll
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 addmore components to the installation package you can copy the new components into the Bin folder and add theproper xml tags in FileListxml You need to enter information for the following tags
RegistType ndash This is the registration information of the component You can enter the following values
RegAsm ndash For NET component
48
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Regsvr32 ndash For VB6 component
Gacutil ndash For NET Framework component that should be registered into Global Assembly Cache
FileName ndash Component file name
OSoftSetupexe
This is the executable file to run the SSIS installation package Double-click the file to start the installation You needto enter information for the following fields
Set SQL server
Specify the SQL server name If your SQL Server has an instance specify the instance name
NoteIf you installed the OSoftSSIS2008_Client or OSoftSSIS2012_Client on the application server the SQL servername is automatically disabled
Set server credential
This is the credential name of the COM+ package component Enter the user ID and password that can accessyour SQL Server This should be either the System Admin ID or Admin ID that was registered as a COM+ userwhen 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 ifyou 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 packagesremotely This is also true for the application server that has SSIS installed The Planning and ConsolidationData Manager has the following custom tasks
Table 12
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008and 2012 respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and2012 respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012respectively
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 49
Name Remark
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and2012 respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008and 2012 respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL2008 and 2012 respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and2012 respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012respectively
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
ltdrivegtWebsrvrbin2 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 FilesMicrosoft SQLServer paste all files into the CProgram Files (x86)Microsoft SQL Server100DTSTasksfolder
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
50
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Typographic Conventions
Table 13
Example Description
lt gt Angle brackets indicate that you replace these words or characters with appropriate entries tomake entries in the system for example Enter your ltUser Namegt
File Save Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
Example Textual cross-references to an internet address for example wwwsapcom
example Quicklinks added to the internet address of a homepage to enable quick access to specificcontent 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 titlespushbutton 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 namesof installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transactioncodes database table names and key concepts of a programming language when they aresurrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
SAP Business Planning and Consolidation 100Typographic Conventions
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 51
52
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
wwwsapcom
Material Number
- SAP Business 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 2008 R2 2012 or 2012 R2
- 344 Removing Default Access to the Console
- 345 Management Console Access Control
- 346 Configuring Planning and Consolidation to use SSL
- 347 Using Client Certificates
- 348 Configuring MS SQL Server Reporting Services to use SSL
-
- 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
-
SAP Note Number Title Comments
1961655 Business Planning amp Consolidation 10 forMicrosoft SP13 Central Note
This note contains important information about theinstallation of support package 13
1897745 Business Planning amp Consolidation 10 forMicrosoft SP12 Central Note
This note contains important information about theinstallation of support package 12
1846917 Business Planning amp Consolidation 10 forMicrosoft SP11 Central Note
This note contains important information about theinstallation of support package 11
1804918 Business Planning amp Consolidation 10 forMicrosoft SP10 Central Note
This note contains important information about theinstallation of support package 10
1755355 Business Planning amp Consolidation 10 forMicrosoft SP09 Central Note
This note contains important information about theinstallation of support package 9
1733053 Business Planning amp Consolidation 10 forMicrosoft SP08 Central Note
This note contains important information about theinstallation of support package 8
1689792 Business Planning amp Consolidation 10 forMicrosoft SP07 Central Note
This note contains important information about theinstallation of support package 7
1665656 Business Planning amp Consolidation 10 forMicrosoft SP06 Central Note
This note contains important information about theinstallation of support package 6
1643037 Business Planning amp Consolidation 10 forMicrosoft SP05 Central Note
This note contains important information about theinstallation of support package 5
1620464 Business Planning amp Consolidation 10 forMicrosoft SP04 Central Note
This note contains important information about theinstallation of support package 4
1601213 Business Planning amp Consolidation 10 forMicrosoft SP03 Central Note
This note contains important information about theinstallation of support package 3
1591848 Business Planning amp Consolidation 10 forMicrosoft SP02 Central Note
This note contains important information about theinstallation of support package 2
1573539 Business Planning amp Consolidation 10 forMicrosoft SP01 Central Note
This note contains important information about theinstallation of support package 1
12 Naming Conventions
In this document the following naming conventions apply
Table 3
Variable Description
ltPC_serverportgt Server name or IP address and port number of SAP Planningand Consolidation application location
ltdrivegt The drive where SAP Planning and Consolidation is installed
The default for this is CPC_MS
10
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Introduction
2 Installing Planning and ConsolidationServers
This section includes the basic steps for installing a Planning and Consolidation server the prerequisites and whatto 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 atservicesapcominstguidesepm-bpc 100 version for the Microsoft platform
2 Perform the tasks in the Before Starting the Planning and Consolidation Server Installation [page 13] sectionincluding installing all prerequisites
3 From the application server install the Planning and Consolidation server See Installing Planning andConsolidation on a Single Server [page 24]
NoteYou must install both Planning and Consolidation 100 as well as the most recent Planning and Consolidation100 Support Package available from the SAP Service Marketplace at servicesapcomswdc SoftwareDownloads Support Packages and Patches A - Z Index B SAP BPC FOR MICROSOFT SBOP PC 100FOR MICROSOFT Comprised Software Component Versions SAP CPM BPC 100 M Windows Server onx64 64bit
4 If you have multiple machines see Installing the Server in a Multiserver Configuration [page 25]
5 Perform the steps in the section After Installing Planning and Consolidation Servers [page 27]
22 Prerequisites
The following table describes the software you need to install before installing the Planning and Consolidation serverand the minimum versions required
NoteA list of the supported operating systems and database systems is also available in the Product Availability Matrixon SAP Service Marketplace at servicesapcompam Search on Planning and Consolidation
Table 4
Component Minimum Requirement
Operating System The requirements outlined below are for the following operating systems
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 11
Component Minimum Requirement
Windows Server 2008 (64-bit) Standard Enterprise or Data Center with or withoutHyper-V
Windows Server 2008 R2 (64-bit) Foundation Standard Enterprise or DataCenter with or without Hyper-V
Windows Server 2012 (64-bit) Standard Data Center
Windows Server 2012 R2 (64-bit) Standard Data Center
NoteThe operating system must be configured with NTFS
Relational Database Microsoft SQL Server 2008 Enterprise Edition
Microsoft SQL Server 2008 R2 (Gemini) Enterprise Edition
Microsoft SQL Server 2012 Enterprise Edition
OLAP Database Microsoft SQL Server 2008 Enterprise Edition ndash Analysis Server
Microsoft SQL Server 2008 R2 Enterprise Edition ndash Analysis Server
Microsoft SQL Server 2012 Enterprise Edition ndash Analysis Server
Data Integration Microsoft SQL Server 2008 Enterprise Edition ndash SQL Service Integration Services
Microsoft SQL Server 2008 R2 Enterprise Edition ndash SQL Service IntegrationServices
Microsoft SQL Server 2012 Enterprise Edition ndash 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
NET 35 and NET 45 are required for Windows 2012 and 2012 R2
NET 40 is required for all other operating systems
IIS
IIS 75 or IIS 70
(Included in your Operating System IIS 75 is required for Windows 2008 R2editions)
IIS 80 or IIS 85
(Included in your Operating System IIS 85 is required for Windows 2012 R2editions)
Anti-Cross Site Scripting Library 42
This component must be downloaded before installing the server The serverinstallation program asks for the path of each file and copies the files into theappropriate Planning and Consolidation path
Microsoft Visual C++ 2010 SP1 Redistributable Package (x64)
Microsoft Access Database Engine 2010 64bit
12
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
Component Minimum Requirement
VMWare ESX 3x or ESX 40
(Required only if a landscape deployment strategy using virtualizationtechnologies is planned)
NoteMSXML 40 SP2 ADOMDNET 100 and Microsoft Visual C++ 2010 SP1Redistributable Package (x64) are included with the installation program but notinstalled 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 values being returned withcalculated accounts For more information see SAP Note number 1429246 which also contains downloadinformation
We recommend SQL Server 2008 (or R2) Enterprise Edition or SQL Server 2012 Enterprise Edition for theOLAP database to support proactive cache and cube partitioning It is technically possible to use SQL Server2008 (or R2) Standard Edition or SQL Server 2012 Standard Edition for data integration servers but we donot recommend this
23 Before Starting the Planning and Consolidation ServerInstallation
You must perform the following tasks before starting your Planning and Consolidation server installation
Install all the prerequisite software including all of the latest Microsoft hotfixes For more information seeInstalling the Prerequisites [page 17]
If you access your application through a firewall verify with your network administrator which TCP ports tochoose during the installation By default port 80 is the setting for standard http access and port 443 is thesetting for https access If you require a service to listen on a different port you can specify it during theinstallation 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 onwhich 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 Consolidationand automatically overwrites the previous version If you have made any modifications to EnvironmentShellthat 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 ScriptBlocking
If a version of Planning and Consolidation on a NetWeaver platform exists uninstall it before you install Planningand Consolidation 100 version for the Microsoft platform
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 13
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 enterconvert c fsntfsV
All servers in a multiserver environment must be members of the same domain
In a multiserver environment the installing ID must be a domain user ID We recommend that you do not logon to the servers using a local server user ID even if the user ID is a member of the Administrator group on theserver This way you have the proper authority to install software and to modify the Component Services SeeLogging On to Servers [page 14]
You must determine the IP addresses or server names for all servers before installing Planning andConsolidation 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 portaccess reasons (DMZ WORKGROUP or nontrusted domain authentication failures) do the following
1 Copy the EnvironmentShell database file ServerEnvironmentShelldb10 from the Planning andConsolidation 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 theEnvironmentShell database file in the Server Information Advanced Options Local path forEnvironmentShell DB field (for example cEnvironmentShelldb10)
Install the Anti-Cross Site Scripting Library which provides protection to Web-based applications againstCross-Site Scripting (XSS) attacks See Installing the Anti-Cross Site Scripting Library [page 23]
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 theAdministrator group of a domain to which the server belongs or a member of the Administrator group on the localserver
Errors may display during the installation program and in the diagnostic program if the installing user is not assignedto the Administrator group directly but is assigned to a group with Administrator rights You can ignore thesemessages
NoteIf you change the password used to install Planning and Consolidation you must change the password for theapplicable Planning and Consolidation service To do this go to Server Manager on the application server andselect Server Reset Logon Credentials For more information see the SAP Planning and ConsolidationOperations Guide in servicesapcominstguidesepm-bpc 100 for the Microsoft Platform SBOP Plan amp Consol100 MS Administrators Guide
14
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
25 Service-level Accounts
Service accounts are Windows domain IDs with access to all Planning and Consolidation servers with varying levelsof privileges They allow the software to use the minimum amount of privilege required for each job making it moresecure
You must define these user IDs on the Windows machine For security purposes they should not be used to definePlanning and Consolidation users
Prerequisites
Planning and Consolidation 100 has the following Windows services
BPC SendGovernor which manages Microsoft Analysis Service locks to ensure consistent performance andavoid deadlocks
BPC ServiceManager which manages the System Landscape Directory (SLD) service logging service andglobal caches
BPC CTS ServiceManager which listens and handles CTS import requests from the CTS+ transportmanagement system
Since these services should be able to access to the FileShare server an Admin account is assigned automaticallyto the service during the installation of the Planning and Consolidation server program Even though an Adminaccount 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 serviceon the local machine This logon right strictly applies only to the local computer and must be granted in the LocalSecurity Policy
To edit the Local Security Policy of the computer you want to define the logon as a service permission performthe 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 supportmicrosoftcomkb259733
Features
During the installation enter user IDs and passwords for the following user types
System Admin ID
This ID is read-only and is the same as the installation user ID that is the system displays the ID on theinstallation screen but you cannot modify it This ID allows access to code that provides system administrator-level functionality For example this ID can write to the Windows registry has full access to the FileShare server
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 15
and can create remove backup and restore OLAP and SQL databases The system administrator should be amember 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 createsubdirectory access on the FileShare server readwrite metadata and application set database data in OLAPand can create and remove tables in SQL The Administrator should be a member of the domain users groupand 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 theservers has write access to FileShare data and can read metadata and data in OLAP and SQL The User IDmust 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 isinstalled you can change these settings using the Server Manager
NoteWhen defining server names the name refers to the NetBIOS name IP address and fully qualified domain names(FQDN)
Standard Settings
Standard settings are typically used for a single-server environment The following table describes each setting
Table 5
Server Option Value Description
SQL Database server name The name of the SQL DB server
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 computername
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
Table 6
Server Option Value Description
SQL Server Name The name of the SQL DB server Defaults to the local server
Instance name The SQL instance name If left blank the default instance is used
16
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
Server Option Value Description
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 computername
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 forhttp and 443 is the default for https
Authentication type Note If you have chosen SAP BusinessObjects User Management System in theinstallation screen Authentication type does not appear in Advanced settings (asthat IIS authentication type is Anonymous in CMS mode)
Windows or Kerberos The default is Windows If you change this value fromWindows to Kerberos you must make some additional changes
See the Kerberos authentication settings section in the SAP Library ServerManager Guide on servicesapcominstguidesEPM-BPC 100 for theMicrosoft Platform
Scheduler Server Name The name of the server used for scheduling usually the application server forexample GMPV50072862B If you have multiple application servers select theappropriate one
NoteIf the primary server stops working you must manually configure yourapplication 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 theoperating system IIS SQL server analysis services ADOMDNET and MSXML This section provides guidance on
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 17
installing each component For specific versions required see Prerequisites [page 11] and the Product AvailabilityMatrix on the SAP Service Marketplace at servicesapcompam Search on Planning and Consolidation
NoteTo ensure a successful installation you must install the software in the order listed in this procedure
Check all third-party infrastructure services to ensure that they are functioning and that their authenticationmodels 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 itsown 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 applicationserver before you start the installation You can find the UMC installation package (UMCexe) on the Planningand Consolidation CD in a folder called UMC_100_INSTALLER When you run the installation package the wizardguides 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 andConsolidation)
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 multiserverconfiguration See Installing the Operating System [page 19]
3 Install the latest service pack for your operating system To install this service pack go towwwmicrosoftcom
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 SQLServer [page 19]
6 From your SQL Server media install Analysis Services Enterprise Edition and its required service packs and hotfixes See Installing Analysis Services [page 23]
7 On your application server install ADOMDNET The Planning and Consolidation zip file contains theADOMDNET 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 followinglocation BPC SetupServermsxmlmsi
18
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
9 On your application server install Microsoft Visual C++ 2010 SP1 Redistributable Package (x64)
The Microsoft Visual C++ 2010 SP1 Redistributable Package (x64) installation package is contained in thePlanning and Consolidation zip file at the following location BPC SetupServervcredist_x64exe
NoteThe version of vcredist_x64exe in BPC SetupServer has been updated to 10040219 If you have aprevious 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 wwwmicrosoftcomdownloadsendetailsaspxFamilyID=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 Marketplaceat servicesapcompam Search on Planning and Consolidation
Business Planning and Consolidation can support all servers with an operating system in any language
NoteCurrently Business Planning and Consolidation does not support an operating system in bi-directionallanguages such as Hebrew
Procedure
If you are installing IIS 70 75 80 or 85 you must enable the following features
Enable Basic Authentication and Windows Authentication these are not installed by default
Install IIS 6 Metabase Compatibility role
Business Planning and Consolidation uses the ADSI provider to handle IIS administration such as virtualdirectory and security but IIS 7 does not install the ADSI provider by default
273 Installing the SQL Server
Prerequisites
During the installation procedure you have the opportunity to specify the location of the EnvironmentShell databasefile Check that it is possible to access EnvironmentShell from the location where you intend to install the SQL serverIf it is not possible for port access reasons (DMZ WORKGROUP or nontrusted domain authentication failures) copyEnvironmentShell to a location on the SQL server (for example CEnvironmentShelldb10) You specify thislocation on the Server Information page by choosing Server Information Advanced Options Local Path forEnvironmentShell DB
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 19
Procedure
This section describes the general steps for installing the SQL Server component options and considerations wheninstalling 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
NoteIf you encounter a 500 HTTP Error when trying to connect to the Planning and Consolidation Web Client referto Microsoft Support articles 2520479 and 2468871 for assistance
To reinforce security we recommend that you install the SQL server and SSAS components to a nondefaultinstance 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 Optionssection below then choose Next
4 Review disc space requirements then choose Next
5 In Server Configuration Perform the following actions
1 In the Service Accounts tab enter a Planning and Consolidation sysadmin account for the SQL ServerDatabase Engine and the SQL Server Analysis services This is required so that the Planning andConsolidation sysadmin can create and process the Planning and Consolidation database because theMicrosoft SQL server tries to back up or restore database with the privileged account This account is alsorequired 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 differentdomain 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 theapplication server and the account requires the folder access privilege for the application server
To ensure that you have the complete access privileges we recommend the Planning and Consolidationsysadmin 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 touse a restrictive SQL ID that works with the drill-through feature If you must restrict SQL authentication forsecurity 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 installationprogram
20
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
8 Choose Install to begin the installation with the options you have set
SQL Server Component Options
For Single-Machine Installations
Install the following components from the Feature Selection screen
Database Engine Services
Analysis Services
Integration Service which is listed as one of the Shared Features
For Multiple Machine Installations
For multiple machine installations install the following components on each server
Table 7
Server Component What to Install
SQL Server Database Engine Services
SSAS Server Analysis Services
Application Server The following Shared Features
Client Tools Connectivity
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 Server2008 R2 and SQL Server 2012
Process Dimension
It is now possible to process a dimension with multiple selections At processing time the process dimension modulemakes changed or added information for each dimension and process for all selected dimensions and cubes inparallel
Optimize Model
If there are custom partitions for a FACT partition in the OLAP database an optimization module can process custompartitions in parallel when Full or Incremental Optimize is performed However if a full optimize is performed withthe 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 parallelbecause 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 applicationserver and application set databases
NoteSetting the SQL isolation level to be Read Committed Snapshot mode for a database can only be done once andcannot be reversed
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 21
Real Time MOLAP
You can set the OLAP storage model of the write-back partition to be MOLAP (Multidimensional OLAP) This settingremains 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 asfollows
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 Servertrade20052008 which you can download from wwwmicrosoftcom (search on ldquoTable Partitioningrdquo to find all relevantarticles)
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 Thebrowser 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 localhostand external network interface machine
3 If you want to use IP1 which indicates Server IP set Enabled to Yes and specify the TCP Port as desired
4 Delete 0 from TCP Dynamic Ports Set IPAll - TCP Ports as desired (for example 1533)
RecommendationWe do not recommend using dynamic ports
In an SQL server the default instance has a listener which listens on a fixed port (TCP port 1433)However for the named instance the port on which the SQL server listens is random and dynamicallyselected when the named instance of the SQL server starts This recommendation prevents any conflictproblems
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 Setthe 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 thatthe user identified as the Log on as user has the sysadmin SQL Server role defined under Server Roles in theSQL Server Management Studio This is required so Analysis Services can process the SQL Server
From SQL Server Management Studio do the following tasks
22
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
1 If you want to use a port with a named instance select the server type Analysis Services select the servername (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 ServerProperties window displays which shows all configurable properties
3 For enhanced security change the default value to your port number (for example 2724) This means thatyou use a fixed port as for the SQL Server option Then choose OK
NoteWe do not support a nondefault port with the default instance in this release If you want to use the defaultinstance do not change the port number
Restart SQL and OLAP
Confirm that the installation has completed successfully by checking that there are no installation relatedproblems on the event viewer You can now install Planning and Consolidation
274 Installing Analysis Services
Procedure
After you install SQL Server and its required service packs and hotfixes you must install SQL Server Analysis Servicesand its required service packs and hotfixes
NoteIf you have migrated your Analysis Services repository to the SQL Server back up the database that contains therepository before installing this release
To install Analysis Services for SQL Server 2008 SQL Server 2008 R2 or SQL Server 2012 follow the steps andguidelines in technetmicrosoftcomen-uslibraryms143219aspx
To avoid slow performance when a user has more than six OLAP databases follow the steps and guidelines in thePerformance Guide for SQL 2008 at wwwmicrosoftcomdownloadsdetailsaspxFamilyID=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 tohave it available for the Planning and Consolidation installation program
1 Download the Anti-Cross Site Scripting Library file AntiXSSLibraryDLL from the Microsoft Web site atwwwmicrosoftcomdownloadendetailsaspxid=28589
2 Save the extracted file locally
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 23
When you install Planning and Consolidation Server a step in the process requires you to identify the path toAntiXssLibrarydll
28 Installing on a Single Server
When you install all Planning and Consolidation server components on a single server you should consider thefollowing 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 theuncompressed 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 Log on to the server with a local server user ID or domain user ID For more information see Logging on toservers [page 14]
3 Make sure all prerequisite software is installed on the server For more information see Installing thePrerequisites [page 17]
4 Obtain SAP Planning and Consolidation archive from the Downloads SAP Installations amp Upgrades areaof SAP Service Marketplace
5 Extract the files from the archive Go to the BPC Setup folder and run the StartUpexe file
6 From the Server Install screen select Install the Planning and Consolidation server
7 From the Welcome screen choose Next
8 From the License Agreement page choose I accept the terms of the license agreement then choose Next
9 From the Installation Method page accept the default Single machine enter a system ID for the systemlandscape directory (SLD) and choose Next
NoteEntering a system ID of the SLD is only required if you have a SAP Solution Manager license If you do nothave a SAP Solution Manager license you can leave this field empty
10 From the Authentication Method page choose the desired authentication method and choose Next
11 If you have chosen SAP BusinessObjects User Management System in the previous screen on the CMSAuthentication page enter the information required to log on to CMS as an administrator
The following information is required
24
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
Table 8
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 Thisgroup name is filtered as the default when adding a user in Planning andConsolidation Administration Use a comma ( ) to separate multiple names
12 After entering the CMS administrator authentication details choose Next
13 From the Service type accounts page enter service-level account user IDs and passwords See Service-LevelAccounts [page 15]
14 After defining the IDs and passwords choose Next
15 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 chooseNext
16 Specify the location and name of AntiXssLibrarydll See Installing the Anti-Cross Site ScriptingLibrary [page 23]
Choose Next
17 Select destination folders for Programs and Data The Data files include Webfolders and FileDB (publishedreports) and should be installed on a separate drive in a production environment This recommendation reducesthe hard disk IO time and helps to speed up SQL commands
Accept the defaults or make your selections then choose Next
18 Select the default values for the Web client The values are used to determine the default language and regionfor the Web client when you connect to it You can change the values in the Planning and Consolidation ServerManager
19 The installation process takes a few moments When it is complete choose Exit
20 A prompt is displayed to restart your computer Select OK to restart
21 Perform the steps in After Installing Planning and Consolidation Servers [page 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 avariety of ways and configure the servers as a Network Load Balancing (NLB) environment
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 25
The recommended Planning and Consolidation practice is to assign resources using a round robin approach for loadbalancing
You can install the SQL OLAP and FileShare types remotely from the application server You need to performadditional server installations if you have multiple application servers
Installing each Planning and Consolidation application server in a multiserver (NLB) configuration is identical to theprocedure 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 Balancingenvironment With this option there is an additional choice to Include sample environment (required on only oneof the application servers) This is because when you install the application server it connects to the databaseserver and creates the sample environment (EnvironmentShell) Installing the sample environment is requiredon 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
26
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
3 After Installing Planning and ConsolidationServers
31 Post-Installation Steps
Procedure
Perform these steps after installing the Planning and Consolidation servers for new installations of Planning andConsolidation
1 Connect your Planning and Consolidation system to Solution Manager Diagnostics (SMD) to allow support staffto identify analyze and resolve problems with your application See Connecting to Solution ManagerDiagnostics [page 28]
2 Configure the Planning and Consolidation NET and application server to ensure that it and its related servicesfunction properly and reliably For more information see Configuring the Planning and Consolidation NETApplication Server [page 29]
3 Optional configuration steps [page 29]
1 To ensure proper functioning of the Management Console create an SQL user and modify the System DSNand 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 loggingfor ODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default WebSite [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory canaccess the Management Console with whatever rights they have been granted on the server Forinformation about removing default access and creating a group that can access the console see RemovingDefault Access to the Console [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommendthat you only grant Management Console access to system administrators Planning and Consolidationusers should not have any access For more information see Management Console AccessControl [page 33]
6 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
4 Take the following steps to set up security
If you are defining security and application structure continue with step 5
If you want to designate someone other than the system administrator to manage security and applicationstructure log on to EnvironmentShell designate a user as a Primary Administrator
This user must have Administration ndash Environment and Security ‒ Define User task rights so that he or shecan 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 SeeInstalling the Administration Client [page 37]
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 27
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 taskprofiles 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 mustcomplete this step since there is no access to dimensions or members)
NoteTo allow users to request and query large amounts of data you can edit the metabasexml file located at CWindowssystem32inetsrv Set the following parameters to the stated values
ASPBUFFERINGLIMIT = 10485760
MAXREQUESTENTITYALLOWED = 10485760
32 Connecting to Solution Manager Diagnostics
NoteYou only need to perform the steps in this section if you have a SAP Solution Manager licence
The diagnostics functions in SAP Solution Manager allow identification analysis and resolution of problems Thisprocedure 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 areinstalled
NoteInstallation files for Diagnostics Agent are available on Service Marketplace by navigating to SupportPackages and Patches mdash Entry by Application Group SAP Technology Components SAP SOLUTIONMANAGER SAP SOLUTION MANAGER 70 EHP 1 Entry by Component Agents for managed systemsDIAGNOSTICS AGENT 711
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 whereMicrosoft 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
28
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
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 ServiceMarketplace at servicesapcom~sapidb011000358700000074392009E and follow the chapters that applyto Planning and Consolidation
33 Configuring the Planning and Consolidation NETApplication Servers
Procedure
Modifying machineconfig Files
To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock occurrences that wouldcause the application server to ldquosleeprdquo and not process anymore you can modify the machineconfig file whichresides in the WINDOWSMicrosoftNETFramework64v4030319Config directory
1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to specifywhether to automatically configure settings to achieve optimal performance based on the machineconfiguration You can set this attribute to True or False
For more information see msdnmicrosoftcomen-uslibrary7w2sway1aspx
2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the Planning andConsolidation application) or Machineconfig (for all applications including Planning and Consolidation) toensure the validationKey and decryptionKey keys have the same value on all application servers Thisway when the authentication cookie is checked the authentication ticket used on one server can still be validon another server
For more information and sample Visual Basic code for generating random key values seemsdnmicrosoftcomen-uslibraryms998288aspxpaght000007_webfarmdeploymentconsiderationsand msdnmicrosoftcomen-uslibraryms998310aspx
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 DSNand 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 forODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory can accessthe Management Console with whatever rights they have been granted on the server For information about
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 29
removing default access and creating a group that can access the console see Removing Default Access to theConsole [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommend thatyou only grant Management Console access to system administrators Planning and Consolidation users shouldnot have any access For more information see Management Console Access Control [page 33]
6 Configure the use of SSL in Planning and Consolidation See Configuring Planning and Consolidation to useSSL [page 34]
7 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
8 Configure Microsoft SQL Server Reporting Services to use SSL See Configuring MS SQL Server ReportingServices to use SSL [page 36]
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 databaserole 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 optionto use ODBC Logging Enter the following values
DSN is BPC_ManagementDSN Table is BPCLog The Microsoft SQL Server Username and Password
5 Restart IIS
NoteWithout these updates the Management Console does work but some functionality (specifically User Activityand Service Status) does not work as expected
Should you need to uninstall Planning and Consolidation we recommend that you reset the Active Log Formatfield in IIS to W3C Extended Log File Format
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
30
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
Prerequisites
ODBC logging has been configured according to the Microsoft Knowledge Base article 245243 How to configureODBC 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 inApplicationHostconfig as shown here
ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0logFormat=Custom gtUse 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-00AA006111E0appcmd 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 articlespecified in the Prerequisites section Configure these settings in the ltodbcLogginggt node underltsystemwebServergt
Exampleltlocation path=Default Web SitegtltsystemwebServergtltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog userName=Usernamepassword=mypassword gtltsystemwebServergtltlocationgt
Use the following AppCmds to configure these attributes for the default Web site
appcmd set config Default Web Site sectionodbcLogging dataSourceBPC_ManagementDSN commitappHostappcmd set config Default Web Site sectionodbcLogging tableNameBPCLog commitappHostappcmd set config Default Web Site sectionodbcLogging userNameUsername commitappHostappcmd set config Default Web Site sectionodbcLogging passwordmypassword commitappHost
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 31
NoteYou cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must use the SQL ServerODBC driver For more information see the Microsoft Knowledge Base article 931202 The requirements for usingthe ODBC logging feature in IIS
343 Setting Up an ODBC Data Source in Windows Server2008 2008 R2 2012 or 2012 R2
Procedure
This procedure describes how to set up an ODBC data source for the Management Console in Windows Server 20082008 R2 2012 or 2012 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
NoteIf you have chosen SAP BusinessObjects User Management System in the installation screen you do not needto remove or configure access because the Management Console service always runs with the System Admin IDaccount which is a member of the Administrators group
Procedure
To remove default access to the Management Console and create a group that does have access to the console usethe procedure described below
32
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
NoteCreate your Management Console administrative group either on the server that hosts the Management Consoleor 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
NoteAlternatively you can perform analogous steps in Active Directory
3 In the Groups context menu choose New Group
4 Enter data as required Click Create
5 In the Computer Management dialog box choose Services and Applications Internet InformationServices 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 objectand all child objects Include these with entries explicitly defined here checkbox
NoteThis step is a necessary precursor to the completion of this procedure
10 In the Security dialog box click Copy to ensure that the System group retains its privileges
11 Remove access to the Management Console from all groups that should not have it
12 Choose Authentication in the center pane then disable Windows authentication
Result
Users who have not been granted access to the Management Console can still open the Management Console Webpage but it contains no data or menu options This does not affect the access that a user would otherwise have toPlanning and Consolidation
345 Management Console Access Control
After establishing the Management Console group you can add users or groups to it For more information aboutcreating this group see Removing Default Access to the Console [page 32] Their rights in Active Directory determinewhat they can access in the Console
By default any member of the Administrators Active Directory group on the application server or domain has fullaccess to all of the features of the Console except the Planning and Consolidation logging area Access to Planningand Consolidation logging is controlled within the Planning and Consolidation Administration Client task securityThe user must be granted View system logs task privileges For more information see the SAP Library Planning and
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 33
Consolidation Administrators Guide in servicesapcominstguidesepm-bpc 100 version for the Microsoftplatform
Your IT policy determines whether you grant access by group or user You may wish to create several levels of Consoleusers (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 describedin this table
Table 9
Privilege Rights Management Area
Task Manager and Kill Process Administrators group on application server or domain
Performance Monitor Counters Administrators group on application server or domain
Power Users group on application server or domain
Performance Monitor Users group on application server
Microsoft Analysis Services performance monitoring Administrators group on application server or domain
Microsoft SQL Server Monitoring (performance counters andstatistics)
Administrators group on application server or domain
346 Configuring Planning and Consolidation to use SSL
Procedure
Creating a Certificate for the Server
During the handshake phase of the SSL communication the server must send its certificate to the client The clientthen uses the certificate to encrypt information and send it back to the server
The procedure below describes how to create a self-signed certificate for the server
RecommendationWe recommend that you limit the use of self-signed certificates to testing only For a productive system you shouldobtain a certificate signed by a well-known certification authority (CA)
1 Start the Internet Information Services (IIS) Manager To do that go to Start All Programs AdministrativeTools Internet Information Services (IIS) Manager
2 In the Connections panel on the left-hand side select the server node and then choose Server Certificates
3 In the Actions panel on the right hand side choose the Create Self-Signed Certificate action
4 Enter the name that you want the certificate to be identified by for example MyTestSSLCertificate
IIS generates a new SSL certificate for you that has one yearrsquos expiry lease The certificate is issued to the local servername
Binding the Certificate to the Web Site
The procedure below describes how to bind the certificate to the web site for which SSL connections must be used
1 In the Connections panel select the web site node
2 In the Actions panel choose Bindings
34
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
3 In the Site Bindings dialog that appears choose the Add button to create a new binding
4 Configure the parameters as follows
Type = https IP Address = [1] - this is a shorthand expression for the local server name
Port = 443 - this is the default SSL port
SSL Certificate = enter your newly created certificate name
5 Choose OK to create the new binding and then close the Site Bindings dialog
6 Restart the IIS processes To do this choose Restart from the Actions panel
7 In the middle panel under the IIS section choose SSL Settings
8 In the SSL Settings screen select the Require SSL checkbox
9 In the Actions panel choose to Apply these settings
To test the SSL connection in the Actions panel choose the Browse [1] 443 (https) link
347 Using Client Certificates
To enable the use of client certificates in Planning and Consolidation you must follow several manual steps
NotePlanning and Consolidation supports client certificate authentication in Windows Authentication Mode butdoes 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 technetmicrosoftcomen-uslibrarycc753810aspx
For more information about configuring the client certificate mapping authentication see technetmicrosoftcomen-uslibrarycc732996(WS10)aspx
When you create the client certificates you can set the type of certificate in the SSL Settings screen in InternetInformation Services (IIS) Manager
Procedure
1 Set the options for client certificates
1 In the IIS Manager select the web site where you installed Planning and Consolidation
2 Choose SSL Settings
3 In the Client certificates section select the Accept client certificates option
This option allows you to use a client certificate or username and password (Basic authentication) toconnect 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 theManagementConsole home page
3 Double-click Authentication and enable Anonymous Authentication
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 35
4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way asin step 3
5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the sameway 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
348 Configuring MS SQL Server Reporting Services to useSSL
Procedure
The procedure below describes how to configure the use of SSL in Microsoft SQL Server Reporting Services
NoteReporting Services does not provide functionalities for generating requesting or installing a certificate Theserver certificates that you want to use for configuring SSL must have already been installed on your computer
1 Open the Reporting Services Configuration Manager program To do this open the Windows Start menu andnavigate to All Programs Microsoft SQL Server ltversiongt Configuration Tools Reporting ServicesConfiguration Manager
2 In the Connect panel on the left-hand side select the Web Service URL option to open all the Report Server webservice parameters
3 Configure the parameters as follows
SSL Certificate = the name of the certificate that you want to use
SSL Port = 4434 Choose Apply to confirm the changes
5 In the Connect panel choose Report Manager URL to open the list of parameters that link Reporting Servicesto IIS
6 Choose Advanced to add your new SSL web URL
7 In the section Multiple SSL Identities for Report Manager choose Add Configure the parameters as follows
IP Address = (All IPv4) SSL Port = 443 Certificate = the name of your SSL certificate
8 To test the configuration click the URL that appears under the Report manager Site Identification section
36
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
4 Installing Planning and ConsolidationAdministration Client and the SAPBusinessObjects EPM solutions Add-in forMicrosoft Office
The installation of the Planning and Consolidation Administration Client allows administrators to build and maintainPlanning and Consolidation environments and models and administer security
All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions add-in forMicrosoft 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 valueof the Planning and Consolidation client to prompt for user name and password Otherwise the Planning andConsolidation Start Page does not display
41 Installing the Administration Client
Prerequisites
NoteFor a definitive list of system requirements see the Product Availability Matrix on SAP Service Marketplace atservicesapcompam Search on Planning and Consolidation
The following list describes the minimum software requirements
Microsoft Internet Explorer 70 80 90 or 10
Microsoft Office 2003 2007 2010 or 2012
NET Framework 20 or higher (install any required NET Framework Hotfixes by referring tosupportmicrosoftcomkb)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 37
NoteWe recommend that you install all of the latest Microsoft Windows hotfixes prior to installing the Administrationclient For information about which hotfixes to install see updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us
Procedure
The 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 ltPC_serverportgtsapbpcweb
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 mustdownload the most recent version of the full setup (EPM Add-inexe) from the Service Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPCInstallation folder
Individual users can install the EPM add-in on their own machines by going to the Planning and Consolidation Homepage 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 upthe 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
38
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
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 toperform the upgrade If Client Auto Update is not enabled and a newer version is detected clients must be installedmanually 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 andpassword in the Admin ID and Admin password fields respectively The Admin ID should be a member of thelocal administrators group on all the computers running the auto update This setting is not needed if all usershave 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 Thisoption is stored in the user preferences and may also be turned on or off using the User Optionshellip menu itemIf 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 toinstall 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 installit 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 servicesapcom
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 versionand policy information For a support package these files are
EPM Addin Support Package ltSP versiongtmsp EPM Addin Support Package ltSP versiongtxmlFor a patch these files are
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 (WebsrvrWebBPCInstallation)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 39
You can set a different update policy for each package listed
ExampleThe following table illustrates some possible situations assuming that you have installed the first full version(V1)
Table 10
Available maintenancepackages
V2-user update
V3-force update
V4-force update
V5-user update
V5-user update V5-user update
V6-auto update
V7-force update
Minimum RequiredVersion
V4 V4 V7
Notification A prompt tells the user toinstall maintenancepackage V4 using theForced Update behavior
If User Update is enabledthe prompt informs theuser that maintenancepackage V5 is available
A prompt tells the user toinstall maintenancepackage V7 using theForced Update behavior
New Version V4 V4 or V5 V7
If you change the update policy for any package click Update to complete the change
40
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
5 Connection Issues
You may experience connection problems with ports the proxy server or programs and settings that interact withthese components If you have any issues related to connection review the following recommendations andtroubleshooting tips
51 Checking for Open Ports
You must ensure that all required ports are open for inboundoutbound traffic By default Planning andConsolidation requires that Ports 80 (used by http) and 1433 and 2383 (used by SQL Server 2008) are open Totest whether the required ports are open go to a command prompt and enter the Telnet serveripaddress and portFor example Telnet 431181836 80 If the system returns a blank command window the port is open If it returnsa message stating that it is unable to connect the port is not open
NoteYou can use the following site to scan for the normal ports It allows you to manually enter a port number to test
wwwmyserverorgportsniffasp
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 Planningand Consolidation server as an exception You can do this at the client level ( Internet Explorer ToolsInternet 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 fullyqualified 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 Consolidationauthentication Do not use authentication on the proxy server The system synchronizes the user name andpassword on the remote server with the local user name and password
SAP Business Planning and Consolidation 100Connection Issues
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 41
NoteFor more information about setting up an ISA proxy server contact SAP Support to request a copy of Setting upISA Proxy Server White Paper For more information about Business Planning and Consolidation firewall portssee SAP Note 1505250
Internet Explorer Settings Issues
Internet Explorer settings must be set correctly to prevent errors and problems when you attempt to access thePlanning 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 insertthe IP address or fully qualified server name of the Planning and Consolidation server as an exception bychoosing 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
42
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Connection Issues
6 Installing Planning and Consolidation withTwo Active Directory Domains
To set up a Planning and Consolidation 10 application server in a hosted environment and use your own domainusers follow this procedure In general you install Planning and Consolidation on the host domain use the hostdomain account and assign it to the Planning and Consolidation users SysAdmin Admin and Users Then you acceptone 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 andpassword 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 topromote 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 privilegefor the Planning and Consolidation server
5 Install Planning and Consolidation and assign your domain account either to the three Planning andConsolidation administrative users SysAdmin Admin and Users or to only one of the three Planning andConsolidation administrative users and to three of your users Be sure you use your own user account ratherthan host domain users
Planning and Consolidation impersonation can then access your domain from the host environment becauseit has the privilege of your domain account
SAP Business Planning and Consolidation 100Installing Planning and Consolidation with Two Active Directory Domains
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 43
7 Installing Planning and Consolidation in aTerminal Services or Citrix ServerDeployment
This section describes best practices and instructions for installing Planning and Consolidation in a Terminal Servicesor Citrix Server deployment
71 Terminal Services Home Directories
We recommend using Terminal Server home directories rather than using the userrsquos profile directory The profiledirectory downloads a minimal amount of information about the dimensions of the environment you are logging onto and may be as large as 2 MB per user The profile directory is on the system drive and has limited space Byspecifying 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 individualserver 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 clientserver (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
44
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
Procedure
The following steps outline how to install the Planning and Consolidation clients in a Terminal Services (TS) or CitrixServer deployment
1 Make sure the Terminal Services or Citrix Server machine has the system requirements installed
2 Log on to the Terminal Services or Citrix Server machine with a user ID that has the rights to install on thatserver
3 At a command prompt enter Change userinstall
4 Open a browser and connect to the URL ltPC_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_MSBPCAdminMainexe
74 Creating a Shortcut to the Launch Page
Procedure
If you use published desktops instead of published applications the Planning and Consolidation desktop file (whichis installed on the current userrsquos desktop) must be moved to the All UsersDesktop folder
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 45
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 SQLServer 2012 support the remote modification of SSIS packages Planning and Consolidation also supports theremote 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 whichyou want to modify SSIS packages
These custom tasks reference dlls that connect to the database server and perform certain validation when usersset up the parameters of each task All the custom task reference components must also be installed in the machineon which you want to modify SSIS packages
We provide a program that registers all the reference components of the custom tasks This section explains theinstallation 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 ndash This folder contains all the dlls that should be installed on the machine There are Planning andConsolidation platform components and all of the Data Manager custom task files
Config folder ndash This folder contains only one file named Filelistxml and lists all of the files that should be installedIf you need to add or remove certain components from the installation you can modify this xml file
OSoftSetupexe ndash This is the main executable file to run the installation package
NoteIf you are not installing SSIS Custom Tasks on your client machine ndash specifically a machine other than the Planningand Consolidation application server ndash you must first install OSoftSSIS2008_Client or OSoftSSIS2012_Client onthe client machine followed by the SQL Server version If you want to use SQL 2008 Tasks under the SQL 2012environment you must install OSoftSSIS2008_Client on the application server For detailed information see SAPNote 1707410 You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package byextracting OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPCInstallation folder on the Planning and Consolidation server To modify SSIS packages on the Planning andConsolidation application server you need to install OSoftSSIS2008_Client or OSoftSSIS2012_Client for creatinga COM+ application For more information see Before You Modify the SSIS Packages [page 49] and Setup ofa COM+ Application on the Application Server [page 50]
Bin folder
This folder contains the following components
46
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Table 11
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012respectively
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
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 47
Name Remark
BPCWriteBackdll
InteropDTSdll
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 addmore components to the installation package you can copy the new components into the Bin folder and add theproper xml tags in FileListxml You need to enter information for the following tags
RegistType ndash This is the registration information of the component You can enter the following values
RegAsm ndash For NET component
48
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Regsvr32 ndash For VB6 component
Gacutil ndash For NET Framework component that should be registered into Global Assembly Cache
FileName ndash Component file name
OSoftSetupexe
This is the executable file to run the SSIS installation package Double-click the file to start the installation You needto enter information for the following fields
Set SQL server
Specify the SQL server name If your SQL Server has an instance specify the instance name
NoteIf you installed the OSoftSSIS2008_Client or OSoftSSIS2012_Client on the application server the SQL servername is automatically disabled
Set server credential
This is the credential name of the COM+ package component Enter the user ID and password that can accessyour SQL Server This should be either the System Admin ID or Admin ID that was registered as a COM+ userwhen 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 ifyou 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 packagesremotely This is also true for the application server that has SSIS installed The Planning and ConsolidationData Manager has the following custom tasks
Table 12
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008and 2012 respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and2012 respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012respectively
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 49
Name Remark
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and2012 respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008and 2012 respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL2008 and 2012 respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and2012 respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012respectively
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
ltdrivegtWebsrvrbin2 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 FilesMicrosoft SQLServer paste all files into the CProgram Files (x86)Microsoft SQL Server100DTSTasksfolder
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
50
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Typographic Conventions
Table 13
Example Description
lt gt Angle brackets indicate that you replace these words or characters with appropriate entries tomake entries in the system for example Enter your ltUser Namegt
File Save Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
Example Textual cross-references to an internet address for example wwwsapcom
example Quicklinks added to the internet address of a homepage to enable quick access to specificcontent 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 titlespushbutton 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 namesof installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transactioncodes database table names and key concepts of a programming language when they aresurrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
SAP Business Planning and Consolidation 100Typographic Conventions
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 51
52
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
wwwsapcom
Material Number
- SAP Business 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 2008 R2 2012 or 2012 R2
- 344 Removing Default Access to the Console
- 345 Management Console Access Control
- 346 Configuring Planning and Consolidation to use SSL
- 347 Using Client Certificates
- 348 Configuring MS SQL Server Reporting Services to use SSL
-
- 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
-
2 Installing Planning and ConsolidationServers
This section includes the basic steps for installing a Planning and Consolidation server the prerequisites and whatto 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 atservicesapcominstguidesepm-bpc 100 version for the Microsoft platform
2 Perform the tasks in the Before Starting the Planning and Consolidation Server Installation [page 13] sectionincluding installing all prerequisites
3 From the application server install the Planning and Consolidation server See Installing Planning andConsolidation on a Single Server [page 24]
NoteYou must install both Planning and Consolidation 100 as well as the most recent Planning and Consolidation100 Support Package available from the SAP Service Marketplace at servicesapcomswdc SoftwareDownloads Support Packages and Patches A - Z Index B SAP BPC FOR MICROSOFT SBOP PC 100FOR MICROSOFT Comprised Software Component Versions SAP CPM BPC 100 M Windows Server onx64 64bit
4 If you have multiple machines see Installing the Server in a Multiserver Configuration [page 25]
5 Perform the steps in the section After Installing Planning and Consolidation Servers [page 27]
22 Prerequisites
The following table describes the software you need to install before installing the Planning and Consolidation serverand the minimum versions required
NoteA list of the supported operating systems and database systems is also available in the Product Availability Matrixon SAP Service Marketplace at servicesapcompam Search on Planning and Consolidation
Table 4
Component Minimum Requirement
Operating System The requirements outlined below are for the following operating systems
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 11
Component Minimum Requirement
Windows Server 2008 (64-bit) Standard Enterprise or Data Center with or withoutHyper-V
Windows Server 2008 R2 (64-bit) Foundation Standard Enterprise or DataCenter with or without Hyper-V
Windows Server 2012 (64-bit) Standard Data Center
Windows Server 2012 R2 (64-bit) Standard Data Center
NoteThe operating system must be configured with NTFS
Relational Database Microsoft SQL Server 2008 Enterprise Edition
Microsoft SQL Server 2008 R2 (Gemini) Enterprise Edition
Microsoft SQL Server 2012 Enterprise Edition
OLAP Database Microsoft SQL Server 2008 Enterprise Edition ndash Analysis Server
Microsoft SQL Server 2008 R2 Enterprise Edition ndash Analysis Server
Microsoft SQL Server 2012 Enterprise Edition ndash Analysis Server
Data Integration Microsoft SQL Server 2008 Enterprise Edition ndash SQL Service Integration Services
Microsoft SQL Server 2008 R2 Enterprise Edition ndash SQL Service IntegrationServices
Microsoft SQL Server 2012 Enterprise Edition ndash 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
NET 35 and NET 45 are required for Windows 2012 and 2012 R2
NET 40 is required for all other operating systems
IIS
IIS 75 or IIS 70
(Included in your Operating System IIS 75 is required for Windows 2008 R2editions)
IIS 80 or IIS 85
(Included in your Operating System IIS 85 is required for Windows 2012 R2editions)
Anti-Cross Site Scripting Library 42
This component must be downloaded before installing the server The serverinstallation program asks for the path of each file and copies the files into theappropriate Planning and Consolidation path
Microsoft Visual C++ 2010 SP1 Redistributable Package (x64)
Microsoft Access Database Engine 2010 64bit
12
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
Component Minimum Requirement
VMWare ESX 3x or ESX 40
(Required only if a landscape deployment strategy using virtualizationtechnologies is planned)
NoteMSXML 40 SP2 ADOMDNET 100 and Microsoft Visual C++ 2010 SP1Redistributable Package (x64) are included with the installation program but notinstalled 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 values being returned withcalculated accounts For more information see SAP Note number 1429246 which also contains downloadinformation
We recommend SQL Server 2008 (or R2) Enterprise Edition or SQL Server 2012 Enterprise Edition for theOLAP database to support proactive cache and cube partitioning It is technically possible to use SQL Server2008 (or R2) Standard Edition or SQL Server 2012 Standard Edition for data integration servers but we donot recommend this
23 Before Starting the Planning and Consolidation ServerInstallation
You must perform the following tasks before starting your Planning and Consolidation server installation
Install all the prerequisite software including all of the latest Microsoft hotfixes For more information seeInstalling the Prerequisites [page 17]
If you access your application through a firewall verify with your network administrator which TCP ports tochoose during the installation By default port 80 is the setting for standard http access and port 443 is thesetting for https access If you require a service to listen on a different port you can specify it during theinstallation 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 onwhich 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 Consolidationand automatically overwrites the previous version If you have made any modifications to EnvironmentShellthat 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 ScriptBlocking
If a version of Planning and Consolidation on a NetWeaver platform exists uninstall it before you install Planningand Consolidation 100 version for the Microsoft platform
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 13
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 enterconvert c fsntfsV
All servers in a multiserver environment must be members of the same domain
In a multiserver environment the installing ID must be a domain user ID We recommend that you do not logon to the servers using a local server user ID even if the user ID is a member of the Administrator group on theserver This way you have the proper authority to install software and to modify the Component Services SeeLogging On to Servers [page 14]
You must determine the IP addresses or server names for all servers before installing Planning andConsolidation 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 portaccess reasons (DMZ WORKGROUP or nontrusted domain authentication failures) do the following
1 Copy the EnvironmentShell database file ServerEnvironmentShelldb10 from the Planning andConsolidation 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 theEnvironmentShell database file in the Server Information Advanced Options Local path forEnvironmentShell DB field (for example cEnvironmentShelldb10)
Install the Anti-Cross Site Scripting Library which provides protection to Web-based applications againstCross-Site Scripting (XSS) attacks See Installing the Anti-Cross Site Scripting Library [page 23]
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 theAdministrator group of a domain to which the server belongs or a member of the Administrator group on the localserver
Errors may display during the installation program and in the diagnostic program if the installing user is not assignedto the Administrator group directly but is assigned to a group with Administrator rights You can ignore thesemessages
NoteIf you change the password used to install Planning and Consolidation you must change the password for theapplicable Planning and Consolidation service To do this go to Server Manager on the application server andselect Server Reset Logon Credentials For more information see the SAP Planning and ConsolidationOperations Guide in servicesapcominstguidesepm-bpc 100 for the Microsoft Platform SBOP Plan amp Consol100 MS Administrators Guide
14
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
25 Service-level Accounts
Service accounts are Windows domain IDs with access to all Planning and Consolidation servers with varying levelsof privileges They allow the software to use the minimum amount of privilege required for each job making it moresecure
You must define these user IDs on the Windows machine For security purposes they should not be used to definePlanning and Consolidation users
Prerequisites
Planning and Consolidation 100 has the following Windows services
BPC SendGovernor which manages Microsoft Analysis Service locks to ensure consistent performance andavoid deadlocks
BPC ServiceManager which manages the System Landscape Directory (SLD) service logging service andglobal caches
BPC CTS ServiceManager which listens and handles CTS import requests from the CTS+ transportmanagement system
Since these services should be able to access to the FileShare server an Admin account is assigned automaticallyto the service during the installation of the Planning and Consolidation server program Even though an Adminaccount 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 serviceon the local machine This logon right strictly applies only to the local computer and must be granted in the LocalSecurity Policy
To edit the Local Security Policy of the computer you want to define the logon as a service permission performthe 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 supportmicrosoftcomkb259733
Features
During the installation enter user IDs and passwords for the following user types
System Admin ID
This ID is read-only and is the same as the installation user ID that is the system displays the ID on theinstallation screen but you cannot modify it This ID allows access to code that provides system administrator-level functionality For example this ID can write to the Windows registry has full access to the FileShare server
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 15
and can create remove backup and restore OLAP and SQL databases The system administrator should be amember 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 createsubdirectory access on the FileShare server readwrite metadata and application set database data in OLAPand can create and remove tables in SQL The Administrator should be a member of the domain users groupand 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 theservers has write access to FileShare data and can read metadata and data in OLAP and SQL The User IDmust 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 isinstalled you can change these settings using the Server Manager
NoteWhen defining server names the name refers to the NetBIOS name IP address and fully qualified domain names(FQDN)
Standard Settings
Standard settings are typically used for a single-server environment The following table describes each setting
Table 5
Server Option Value Description
SQL Database server name The name of the SQL DB server
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 computername
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
Table 6
Server Option Value Description
SQL Server Name The name of the SQL DB server Defaults to the local server
Instance name The SQL instance name If left blank the default instance is used
16
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
Server Option Value Description
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 computername
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 forhttp and 443 is the default for https
Authentication type Note If you have chosen SAP BusinessObjects User Management System in theinstallation screen Authentication type does not appear in Advanced settings (asthat IIS authentication type is Anonymous in CMS mode)
Windows or Kerberos The default is Windows If you change this value fromWindows to Kerberos you must make some additional changes
See the Kerberos authentication settings section in the SAP Library ServerManager Guide on servicesapcominstguidesEPM-BPC 100 for theMicrosoft Platform
Scheduler Server Name The name of the server used for scheduling usually the application server forexample GMPV50072862B If you have multiple application servers select theappropriate one
NoteIf the primary server stops working you must manually configure yourapplication 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 theoperating system IIS SQL server analysis services ADOMDNET and MSXML This section provides guidance on
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 17
installing each component For specific versions required see Prerequisites [page 11] and the Product AvailabilityMatrix on the SAP Service Marketplace at servicesapcompam Search on Planning and Consolidation
NoteTo ensure a successful installation you must install the software in the order listed in this procedure
Check all third-party infrastructure services to ensure that they are functioning and that their authenticationmodels 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 itsown 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 applicationserver before you start the installation You can find the UMC installation package (UMCexe) on the Planningand Consolidation CD in a folder called UMC_100_INSTALLER When you run the installation package the wizardguides 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 andConsolidation)
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 multiserverconfiguration See Installing the Operating System [page 19]
3 Install the latest service pack for your operating system To install this service pack go towwwmicrosoftcom
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 SQLServer [page 19]
6 From your SQL Server media install Analysis Services Enterprise Edition and its required service packs and hotfixes See Installing Analysis Services [page 23]
7 On your application server install ADOMDNET The Planning and Consolidation zip file contains theADOMDNET 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 followinglocation BPC SetupServermsxmlmsi
18
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
9 On your application server install Microsoft Visual C++ 2010 SP1 Redistributable Package (x64)
The Microsoft Visual C++ 2010 SP1 Redistributable Package (x64) installation package is contained in thePlanning and Consolidation zip file at the following location BPC SetupServervcredist_x64exe
NoteThe version of vcredist_x64exe in BPC SetupServer has been updated to 10040219 If you have aprevious 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 wwwmicrosoftcomdownloadsendetailsaspxFamilyID=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 Marketplaceat servicesapcompam Search on Planning and Consolidation
Business Planning and Consolidation can support all servers with an operating system in any language
NoteCurrently Business Planning and Consolidation does not support an operating system in bi-directionallanguages such as Hebrew
Procedure
If you are installing IIS 70 75 80 or 85 you must enable the following features
Enable Basic Authentication and Windows Authentication these are not installed by default
Install IIS 6 Metabase Compatibility role
Business Planning and Consolidation uses the ADSI provider to handle IIS administration such as virtualdirectory and security but IIS 7 does not install the ADSI provider by default
273 Installing the SQL Server
Prerequisites
During the installation procedure you have the opportunity to specify the location of the EnvironmentShell databasefile Check that it is possible to access EnvironmentShell from the location where you intend to install the SQL serverIf it is not possible for port access reasons (DMZ WORKGROUP or nontrusted domain authentication failures) copyEnvironmentShell to a location on the SQL server (for example CEnvironmentShelldb10) You specify thislocation on the Server Information page by choosing Server Information Advanced Options Local Path forEnvironmentShell DB
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 19
Procedure
This section describes the general steps for installing the SQL Server component options and considerations wheninstalling 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
NoteIf you encounter a 500 HTTP Error when trying to connect to the Planning and Consolidation Web Client referto Microsoft Support articles 2520479 and 2468871 for assistance
To reinforce security we recommend that you install the SQL server and SSAS components to a nondefaultinstance 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 Optionssection below then choose Next
4 Review disc space requirements then choose Next
5 In Server Configuration Perform the following actions
1 In the Service Accounts tab enter a Planning and Consolidation sysadmin account for the SQL ServerDatabase Engine and the SQL Server Analysis services This is required so that the Planning andConsolidation sysadmin can create and process the Planning and Consolidation database because theMicrosoft SQL server tries to back up or restore database with the privileged account This account is alsorequired 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 differentdomain 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 theapplication server and the account requires the folder access privilege for the application server
To ensure that you have the complete access privileges we recommend the Planning and Consolidationsysadmin 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 touse a restrictive SQL ID that works with the drill-through feature If you must restrict SQL authentication forsecurity 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 installationprogram
20
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
8 Choose Install to begin the installation with the options you have set
SQL Server Component Options
For Single-Machine Installations
Install the following components from the Feature Selection screen
Database Engine Services
Analysis Services
Integration Service which is listed as one of the Shared Features
For Multiple Machine Installations
For multiple machine installations install the following components on each server
Table 7
Server Component What to Install
SQL Server Database Engine Services
SSAS Server Analysis Services
Application Server The following Shared Features
Client Tools Connectivity
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 Server2008 R2 and SQL Server 2012
Process Dimension
It is now possible to process a dimension with multiple selections At processing time the process dimension modulemakes changed or added information for each dimension and process for all selected dimensions and cubes inparallel
Optimize Model
If there are custom partitions for a FACT partition in the OLAP database an optimization module can process custompartitions in parallel when Full or Incremental Optimize is performed However if a full optimize is performed withthe 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 parallelbecause 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 applicationserver and application set databases
NoteSetting the SQL isolation level to be Read Committed Snapshot mode for a database can only be done once andcannot be reversed
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 21
Real Time MOLAP
You can set the OLAP storage model of the write-back partition to be MOLAP (Multidimensional OLAP) This settingremains 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 asfollows
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 Servertrade20052008 which you can download from wwwmicrosoftcom (search on ldquoTable Partitioningrdquo to find all relevantarticles)
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 Thebrowser 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 localhostand external network interface machine
3 If you want to use IP1 which indicates Server IP set Enabled to Yes and specify the TCP Port as desired
4 Delete 0 from TCP Dynamic Ports Set IPAll - TCP Ports as desired (for example 1533)
RecommendationWe do not recommend using dynamic ports
In an SQL server the default instance has a listener which listens on a fixed port (TCP port 1433)However for the named instance the port on which the SQL server listens is random and dynamicallyselected when the named instance of the SQL server starts This recommendation prevents any conflictproblems
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 Setthe 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 thatthe user identified as the Log on as user has the sysadmin SQL Server role defined under Server Roles in theSQL Server Management Studio This is required so Analysis Services can process the SQL Server
From SQL Server Management Studio do the following tasks
22
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
1 If you want to use a port with a named instance select the server type Analysis Services select the servername (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 ServerProperties window displays which shows all configurable properties
3 For enhanced security change the default value to your port number (for example 2724) This means thatyou use a fixed port as for the SQL Server option Then choose OK
NoteWe do not support a nondefault port with the default instance in this release If you want to use the defaultinstance do not change the port number
Restart SQL and OLAP
Confirm that the installation has completed successfully by checking that there are no installation relatedproblems on the event viewer You can now install Planning and Consolidation
274 Installing Analysis Services
Procedure
After you install SQL Server and its required service packs and hotfixes you must install SQL Server Analysis Servicesand its required service packs and hotfixes
NoteIf you have migrated your Analysis Services repository to the SQL Server back up the database that contains therepository before installing this release
To install Analysis Services for SQL Server 2008 SQL Server 2008 R2 or SQL Server 2012 follow the steps andguidelines in technetmicrosoftcomen-uslibraryms143219aspx
To avoid slow performance when a user has more than six OLAP databases follow the steps and guidelines in thePerformance Guide for SQL 2008 at wwwmicrosoftcomdownloadsdetailsaspxFamilyID=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 tohave it available for the Planning and Consolidation installation program
1 Download the Anti-Cross Site Scripting Library file AntiXSSLibraryDLL from the Microsoft Web site atwwwmicrosoftcomdownloadendetailsaspxid=28589
2 Save the extracted file locally
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 23
When you install Planning and Consolidation Server a step in the process requires you to identify the path toAntiXssLibrarydll
28 Installing on a Single Server
When you install all Planning and Consolidation server components on a single server you should consider thefollowing 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 theuncompressed 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 Log on to the server with a local server user ID or domain user ID For more information see Logging on toservers [page 14]
3 Make sure all prerequisite software is installed on the server For more information see Installing thePrerequisites [page 17]
4 Obtain SAP Planning and Consolidation archive from the Downloads SAP Installations amp Upgrades areaof SAP Service Marketplace
5 Extract the files from the archive Go to the BPC Setup folder and run the StartUpexe file
6 From the Server Install screen select Install the Planning and Consolidation server
7 From the Welcome screen choose Next
8 From the License Agreement page choose I accept the terms of the license agreement then choose Next
9 From the Installation Method page accept the default Single machine enter a system ID for the systemlandscape directory (SLD) and choose Next
NoteEntering a system ID of the SLD is only required if you have a SAP Solution Manager license If you do nothave a SAP Solution Manager license you can leave this field empty
10 From the Authentication Method page choose the desired authentication method and choose Next
11 If you have chosen SAP BusinessObjects User Management System in the previous screen on the CMSAuthentication page enter the information required to log on to CMS as an administrator
The following information is required
24
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
Table 8
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 Thisgroup name is filtered as the default when adding a user in Planning andConsolidation Administration Use a comma ( ) to separate multiple names
12 After entering the CMS administrator authentication details choose Next
13 From the Service type accounts page enter service-level account user IDs and passwords See Service-LevelAccounts [page 15]
14 After defining the IDs and passwords choose Next
15 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 chooseNext
16 Specify the location and name of AntiXssLibrarydll See Installing the Anti-Cross Site ScriptingLibrary [page 23]
Choose Next
17 Select destination folders for Programs and Data The Data files include Webfolders and FileDB (publishedreports) and should be installed on a separate drive in a production environment This recommendation reducesthe hard disk IO time and helps to speed up SQL commands
Accept the defaults or make your selections then choose Next
18 Select the default values for the Web client The values are used to determine the default language and regionfor the Web client when you connect to it You can change the values in the Planning and Consolidation ServerManager
19 The installation process takes a few moments When it is complete choose Exit
20 A prompt is displayed to restart your computer Select OK to restart
21 Perform the steps in After Installing Planning and Consolidation Servers [page 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 avariety of ways and configure the servers as a Network Load Balancing (NLB) environment
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 25
The recommended Planning and Consolidation practice is to assign resources using a round robin approach for loadbalancing
You can install the SQL OLAP and FileShare types remotely from the application server You need to performadditional server installations if you have multiple application servers
Installing each Planning and Consolidation application server in a multiserver (NLB) configuration is identical to theprocedure 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 Balancingenvironment With this option there is an additional choice to Include sample environment (required on only oneof the application servers) This is because when you install the application server it connects to the databaseserver and creates the sample environment (EnvironmentShell) Installing the sample environment is requiredon 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
26
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
3 After Installing Planning and ConsolidationServers
31 Post-Installation Steps
Procedure
Perform these steps after installing the Planning and Consolidation servers for new installations of Planning andConsolidation
1 Connect your Planning and Consolidation system to Solution Manager Diagnostics (SMD) to allow support staffto identify analyze and resolve problems with your application See Connecting to Solution ManagerDiagnostics [page 28]
2 Configure the Planning and Consolidation NET and application server to ensure that it and its related servicesfunction properly and reliably For more information see Configuring the Planning and Consolidation NETApplication Server [page 29]
3 Optional configuration steps [page 29]
1 To ensure proper functioning of the Management Console create an SQL user and modify the System DSNand 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 loggingfor ODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default WebSite [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory canaccess the Management Console with whatever rights they have been granted on the server Forinformation about removing default access and creating a group that can access the console see RemovingDefault Access to the Console [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommendthat you only grant Management Console access to system administrators Planning and Consolidationusers should not have any access For more information see Management Console AccessControl [page 33]
6 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
4 Take the following steps to set up security
If you are defining security and application structure continue with step 5
If you want to designate someone other than the system administrator to manage security and applicationstructure log on to EnvironmentShell designate a user as a Primary Administrator
This user must have Administration ndash Environment and Security ‒ Define User task rights so that he or shecan 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 SeeInstalling the Administration Client [page 37]
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 27
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 taskprofiles 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 mustcomplete this step since there is no access to dimensions or members)
NoteTo allow users to request and query large amounts of data you can edit the metabasexml file located at CWindowssystem32inetsrv Set the following parameters to the stated values
ASPBUFFERINGLIMIT = 10485760
MAXREQUESTENTITYALLOWED = 10485760
32 Connecting to Solution Manager Diagnostics
NoteYou only need to perform the steps in this section if you have a SAP Solution Manager licence
The diagnostics functions in SAP Solution Manager allow identification analysis and resolution of problems Thisprocedure 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 areinstalled
NoteInstallation files for Diagnostics Agent are available on Service Marketplace by navigating to SupportPackages and Patches mdash Entry by Application Group SAP Technology Components SAP SOLUTIONMANAGER SAP SOLUTION MANAGER 70 EHP 1 Entry by Component Agents for managed systemsDIAGNOSTICS AGENT 711
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 whereMicrosoft 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
28
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
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 ServiceMarketplace at servicesapcom~sapidb011000358700000074392009E and follow the chapters that applyto Planning and Consolidation
33 Configuring the Planning and Consolidation NETApplication Servers
Procedure
Modifying machineconfig Files
To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock occurrences that wouldcause the application server to ldquosleeprdquo and not process anymore you can modify the machineconfig file whichresides in the WINDOWSMicrosoftNETFramework64v4030319Config directory
1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to specifywhether to automatically configure settings to achieve optimal performance based on the machineconfiguration You can set this attribute to True or False
For more information see msdnmicrosoftcomen-uslibrary7w2sway1aspx
2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the Planning andConsolidation application) or Machineconfig (for all applications including Planning and Consolidation) toensure the validationKey and decryptionKey keys have the same value on all application servers Thisway when the authentication cookie is checked the authentication ticket used on one server can still be validon another server
For more information and sample Visual Basic code for generating random key values seemsdnmicrosoftcomen-uslibraryms998288aspxpaght000007_webfarmdeploymentconsiderationsand msdnmicrosoftcomen-uslibraryms998310aspx
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 DSNand 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 forODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory can accessthe Management Console with whatever rights they have been granted on the server For information about
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 29
removing default access and creating a group that can access the console see Removing Default Access to theConsole [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommend thatyou only grant Management Console access to system administrators Planning and Consolidation users shouldnot have any access For more information see Management Console Access Control [page 33]
6 Configure the use of SSL in Planning and Consolidation See Configuring Planning and Consolidation to useSSL [page 34]
7 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
8 Configure Microsoft SQL Server Reporting Services to use SSL See Configuring MS SQL Server ReportingServices to use SSL [page 36]
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 databaserole 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 optionto use ODBC Logging Enter the following values
DSN is BPC_ManagementDSN Table is BPCLog The Microsoft SQL Server Username and Password
5 Restart IIS
NoteWithout these updates the Management Console does work but some functionality (specifically User Activityand Service Status) does not work as expected
Should you need to uninstall Planning and Consolidation we recommend that you reset the Active Log Formatfield in IIS to W3C Extended Log File Format
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
30
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
Prerequisites
ODBC logging has been configured according to the Microsoft Knowledge Base article 245243 How to configureODBC 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 inApplicationHostconfig as shown here
ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0logFormat=Custom gtUse 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-00AA006111E0appcmd 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 articlespecified in the Prerequisites section Configure these settings in the ltodbcLogginggt node underltsystemwebServergt
Exampleltlocation path=Default Web SitegtltsystemwebServergtltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog userName=Usernamepassword=mypassword gtltsystemwebServergtltlocationgt
Use the following AppCmds to configure these attributes for the default Web site
appcmd set config Default Web Site sectionodbcLogging dataSourceBPC_ManagementDSN commitappHostappcmd set config Default Web Site sectionodbcLogging tableNameBPCLog commitappHostappcmd set config Default Web Site sectionodbcLogging userNameUsername commitappHostappcmd set config Default Web Site sectionodbcLogging passwordmypassword commitappHost
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 31
NoteYou cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must use the SQL ServerODBC driver For more information see the Microsoft Knowledge Base article 931202 The requirements for usingthe ODBC logging feature in IIS
343 Setting Up an ODBC Data Source in Windows Server2008 2008 R2 2012 or 2012 R2
Procedure
This procedure describes how to set up an ODBC data source for the Management Console in Windows Server 20082008 R2 2012 or 2012 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
NoteIf you have chosen SAP BusinessObjects User Management System in the installation screen you do not needto remove or configure access because the Management Console service always runs with the System Admin IDaccount which is a member of the Administrators group
Procedure
To remove default access to the Management Console and create a group that does have access to the console usethe procedure described below
32
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
NoteCreate your Management Console administrative group either on the server that hosts the Management Consoleor 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
NoteAlternatively you can perform analogous steps in Active Directory
3 In the Groups context menu choose New Group
4 Enter data as required Click Create
5 In the Computer Management dialog box choose Services and Applications Internet InformationServices 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 objectand all child objects Include these with entries explicitly defined here checkbox
NoteThis step is a necessary precursor to the completion of this procedure
10 In the Security dialog box click Copy to ensure that the System group retains its privileges
11 Remove access to the Management Console from all groups that should not have it
12 Choose Authentication in the center pane then disable Windows authentication
Result
Users who have not been granted access to the Management Console can still open the Management Console Webpage but it contains no data or menu options This does not affect the access that a user would otherwise have toPlanning and Consolidation
345 Management Console Access Control
After establishing the Management Console group you can add users or groups to it For more information aboutcreating this group see Removing Default Access to the Console [page 32] Their rights in Active Directory determinewhat they can access in the Console
By default any member of the Administrators Active Directory group on the application server or domain has fullaccess to all of the features of the Console except the Planning and Consolidation logging area Access to Planningand Consolidation logging is controlled within the Planning and Consolidation Administration Client task securityThe user must be granted View system logs task privileges For more information see the SAP Library Planning and
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 33
Consolidation Administrators Guide in servicesapcominstguidesepm-bpc 100 version for the Microsoftplatform
Your IT policy determines whether you grant access by group or user You may wish to create several levels of Consoleusers (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 describedin this table
Table 9
Privilege Rights Management Area
Task Manager and Kill Process Administrators group on application server or domain
Performance Monitor Counters Administrators group on application server or domain
Power Users group on application server or domain
Performance Monitor Users group on application server
Microsoft Analysis Services performance monitoring Administrators group on application server or domain
Microsoft SQL Server Monitoring (performance counters andstatistics)
Administrators group on application server or domain
346 Configuring Planning and Consolidation to use SSL
Procedure
Creating a Certificate for the Server
During the handshake phase of the SSL communication the server must send its certificate to the client The clientthen uses the certificate to encrypt information and send it back to the server
The procedure below describes how to create a self-signed certificate for the server
RecommendationWe recommend that you limit the use of self-signed certificates to testing only For a productive system you shouldobtain a certificate signed by a well-known certification authority (CA)
1 Start the Internet Information Services (IIS) Manager To do that go to Start All Programs AdministrativeTools Internet Information Services (IIS) Manager
2 In the Connections panel on the left-hand side select the server node and then choose Server Certificates
3 In the Actions panel on the right hand side choose the Create Self-Signed Certificate action
4 Enter the name that you want the certificate to be identified by for example MyTestSSLCertificate
IIS generates a new SSL certificate for you that has one yearrsquos expiry lease The certificate is issued to the local servername
Binding the Certificate to the Web Site
The procedure below describes how to bind the certificate to the web site for which SSL connections must be used
1 In the Connections panel select the web site node
2 In the Actions panel choose Bindings
34
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
3 In the Site Bindings dialog that appears choose the Add button to create a new binding
4 Configure the parameters as follows
Type = https IP Address = [1] - this is a shorthand expression for the local server name
Port = 443 - this is the default SSL port
SSL Certificate = enter your newly created certificate name
5 Choose OK to create the new binding and then close the Site Bindings dialog
6 Restart the IIS processes To do this choose Restart from the Actions panel
7 In the middle panel under the IIS section choose SSL Settings
8 In the SSL Settings screen select the Require SSL checkbox
9 In the Actions panel choose to Apply these settings
To test the SSL connection in the Actions panel choose the Browse [1] 443 (https) link
347 Using Client Certificates
To enable the use of client certificates in Planning and Consolidation you must follow several manual steps
NotePlanning and Consolidation supports client certificate authentication in Windows Authentication Mode butdoes 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 technetmicrosoftcomen-uslibrarycc753810aspx
For more information about configuring the client certificate mapping authentication see technetmicrosoftcomen-uslibrarycc732996(WS10)aspx
When you create the client certificates you can set the type of certificate in the SSL Settings screen in InternetInformation Services (IIS) Manager
Procedure
1 Set the options for client certificates
1 In the IIS Manager select the web site where you installed Planning and Consolidation
2 Choose SSL Settings
3 In the Client certificates section select the Accept client certificates option
This option allows you to use a client certificate or username and password (Basic authentication) toconnect 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 theManagementConsole home page
3 Double-click Authentication and enable Anonymous Authentication
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 35
4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way asin step 3
5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the sameway 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
348 Configuring MS SQL Server Reporting Services to useSSL
Procedure
The procedure below describes how to configure the use of SSL in Microsoft SQL Server Reporting Services
NoteReporting Services does not provide functionalities for generating requesting or installing a certificate Theserver certificates that you want to use for configuring SSL must have already been installed on your computer
1 Open the Reporting Services Configuration Manager program To do this open the Windows Start menu andnavigate to All Programs Microsoft SQL Server ltversiongt Configuration Tools Reporting ServicesConfiguration Manager
2 In the Connect panel on the left-hand side select the Web Service URL option to open all the Report Server webservice parameters
3 Configure the parameters as follows
SSL Certificate = the name of the certificate that you want to use
SSL Port = 4434 Choose Apply to confirm the changes
5 In the Connect panel choose Report Manager URL to open the list of parameters that link Reporting Servicesto IIS
6 Choose Advanced to add your new SSL web URL
7 In the section Multiple SSL Identities for Report Manager choose Add Configure the parameters as follows
IP Address = (All IPv4) SSL Port = 443 Certificate = the name of your SSL certificate
8 To test the configuration click the URL that appears under the Report manager Site Identification section
36
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
4 Installing Planning and ConsolidationAdministration Client and the SAPBusinessObjects EPM solutions Add-in forMicrosoft Office
The installation of the Planning and Consolidation Administration Client allows administrators to build and maintainPlanning and Consolidation environments and models and administer security
All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions add-in forMicrosoft 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 valueof the Planning and Consolidation client to prompt for user name and password Otherwise the Planning andConsolidation Start Page does not display
41 Installing the Administration Client
Prerequisites
NoteFor a definitive list of system requirements see the Product Availability Matrix on SAP Service Marketplace atservicesapcompam Search on Planning and Consolidation
The following list describes the minimum software requirements
Microsoft Internet Explorer 70 80 90 or 10
Microsoft Office 2003 2007 2010 or 2012
NET Framework 20 or higher (install any required NET Framework Hotfixes by referring tosupportmicrosoftcomkb)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 37
NoteWe recommend that you install all of the latest Microsoft Windows hotfixes prior to installing the Administrationclient For information about which hotfixes to install see updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us
Procedure
The 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 ltPC_serverportgtsapbpcweb
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 mustdownload the most recent version of the full setup (EPM Add-inexe) from the Service Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPCInstallation folder
Individual users can install the EPM add-in on their own machines by going to the Planning and Consolidation Homepage 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 upthe 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
38
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
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 toperform the upgrade If Client Auto Update is not enabled and a newer version is detected clients must be installedmanually 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 andpassword in the Admin ID and Admin password fields respectively The Admin ID should be a member of thelocal administrators group on all the computers running the auto update This setting is not needed if all usershave 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 Thisoption is stored in the user preferences and may also be turned on or off using the User Optionshellip menu itemIf 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 toinstall 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 installit 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 servicesapcom
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 versionand policy information For a support package these files are
EPM Addin Support Package ltSP versiongtmsp EPM Addin Support Package ltSP versiongtxmlFor a patch these files are
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 (WebsrvrWebBPCInstallation)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 39
You can set a different update policy for each package listed
ExampleThe following table illustrates some possible situations assuming that you have installed the first full version(V1)
Table 10
Available maintenancepackages
V2-user update
V3-force update
V4-force update
V5-user update
V5-user update V5-user update
V6-auto update
V7-force update
Minimum RequiredVersion
V4 V4 V7
Notification A prompt tells the user toinstall maintenancepackage V4 using theForced Update behavior
If User Update is enabledthe prompt informs theuser that maintenancepackage V5 is available
A prompt tells the user toinstall maintenancepackage V7 using theForced Update behavior
New Version V4 V4 or V5 V7
If you change the update policy for any package click Update to complete the change
40
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
5 Connection Issues
You may experience connection problems with ports the proxy server or programs and settings that interact withthese components If you have any issues related to connection review the following recommendations andtroubleshooting tips
51 Checking for Open Ports
You must ensure that all required ports are open for inboundoutbound traffic By default Planning andConsolidation requires that Ports 80 (used by http) and 1433 and 2383 (used by SQL Server 2008) are open Totest whether the required ports are open go to a command prompt and enter the Telnet serveripaddress and portFor example Telnet 431181836 80 If the system returns a blank command window the port is open If it returnsa message stating that it is unable to connect the port is not open
NoteYou can use the following site to scan for the normal ports It allows you to manually enter a port number to test
wwwmyserverorgportsniffasp
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 Planningand Consolidation server as an exception You can do this at the client level ( Internet Explorer ToolsInternet 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 fullyqualified 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 Consolidationauthentication Do not use authentication on the proxy server The system synchronizes the user name andpassword on the remote server with the local user name and password
SAP Business Planning and Consolidation 100Connection Issues
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 41
NoteFor more information about setting up an ISA proxy server contact SAP Support to request a copy of Setting upISA Proxy Server White Paper For more information about Business Planning and Consolidation firewall portssee SAP Note 1505250
Internet Explorer Settings Issues
Internet Explorer settings must be set correctly to prevent errors and problems when you attempt to access thePlanning 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 insertthe IP address or fully qualified server name of the Planning and Consolidation server as an exception bychoosing 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
42
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Connection Issues
6 Installing Planning and Consolidation withTwo Active Directory Domains
To set up a Planning and Consolidation 10 application server in a hosted environment and use your own domainusers follow this procedure In general you install Planning and Consolidation on the host domain use the hostdomain account and assign it to the Planning and Consolidation users SysAdmin Admin and Users Then you acceptone 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 andpassword 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 topromote 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 privilegefor the Planning and Consolidation server
5 Install Planning and Consolidation and assign your domain account either to the three Planning andConsolidation administrative users SysAdmin Admin and Users or to only one of the three Planning andConsolidation administrative users and to three of your users Be sure you use your own user account ratherthan host domain users
Planning and Consolidation impersonation can then access your domain from the host environment becauseit has the privilege of your domain account
SAP Business Planning and Consolidation 100Installing Planning and Consolidation with Two Active Directory Domains
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 43
7 Installing Planning and Consolidation in aTerminal Services or Citrix ServerDeployment
This section describes best practices and instructions for installing Planning and Consolidation in a Terminal Servicesor Citrix Server deployment
71 Terminal Services Home Directories
We recommend using Terminal Server home directories rather than using the userrsquos profile directory The profiledirectory downloads a minimal amount of information about the dimensions of the environment you are logging onto and may be as large as 2 MB per user The profile directory is on the system drive and has limited space Byspecifying 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 individualserver 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 clientserver (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
44
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
Procedure
The following steps outline how to install the Planning and Consolidation clients in a Terminal Services (TS) or CitrixServer deployment
1 Make sure the Terminal Services or Citrix Server machine has the system requirements installed
2 Log on to the Terminal Services or Citrix Server machine with a user ID that has the rights to install on thatserver
3 At a command prompt enter Change userinstall
4 Open a browser and connect to the URL ltPC_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_MSBPCAdminMainexe
74 Creating a Shortcut to the Launch Page
Procedure
If you use published desktops instead of published applications the Planning and Consolidation desktop file (whichis installed on the current userrsquos desktop) must be moved to the All UsersDesktop folder
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 45
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 SQLServer 2012 support the remote modification of SSIS packages Planning and Consolidation also supports theremote 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 whichyou want to modify SSIS packages
These custom tasks reference dlls that connect to the database server and perform certain validation when usersset up the parameters of each task All the custom task reference components must also be installed in the machineon which you want to modify SSIS packages
We provide a program that registers all the reference components of the custom tasks This section explains theinstallation 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 ndash This folder contains all the dlls that should be installed on the machine There are Planning andConsolidation platform components and all of the Data Manager custom task files
Config folder ndash This folder contains only one file named Filelistxml and lists all of the files that should be installedIf you need to add or remove certain components from the installation you can modify this xml file
OSoftSetupexe ndash This is the main executable file to run the installation package
NoteIf you are not installing SSIS Custom Tasks on your client machine ndash specifically a machine other than the Planningand Consolidation application server ndash you must first install OSoftSSIS2008_Client or OSoftSSIS2012_Client onthe client machine followed by the SQL Server version If you want to use SQL 2008 Tasks under the SQL 2012environment you must install OSoftSSIS2008_Client on the application server For detailed information see SAPNote 1707410 You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package byextracting OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPCInstallation folder on the Planning and Consolidation server To modify SSIS packages on the Planning andConsolidation application server you need to install OSoftSSIS2008_Client or OSoftSSIS2012_Client for creatinga COM+ application For more information see Before You Modify the SSIS Packages [page 49] and Setup ofa COM+ Application on the Application Server [page 50]
Bin folder
This folder contains the following components
46
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Table 11
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012respectively
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
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 47
Name Remark
BPCWriteBackdll
InteropDTSdll
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 addmore components to the installation package you can copy the new components into the Bin folder and add theproper xml tags in FileListxml You need to enter information for the following tags
RegistType ndash This is the registration information of the component You can enter the following values
RegAsm ndash For NET component
48
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Regsvr32 ndash For VB6 component
Gacutil ndash For NET Framework component that should be registered into Global Assembly Cache
FileName ndash Component file name
OSoftSetupexe
This is the executable file to run the SSIS installation package Double-click the file to start the installation You needto enter information for the following fields
Set SQL server
Specify the SQL server name If your SQL Server has an instance specify the instance name
NoteIf you installed the OSoftSSIS2008_Client or OSoftSSIS2012_Client on the application server the SQL servername is automatically disabled
Set server credential
This is the credential name of the COM+ package component Enter the user ID and password that can accessyour SQL Server This should be either the System Admin ID or Admin ID that was registered as a COM+ userwhen 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 ifyou 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 packagesremotely This is also true for the application server that has SSIS installed The Planning and ConsolidationData Manager has the following custom tasks
Table 12
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008and 2012 respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and2012 respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012respectively
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 49
Name Remark
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and2012 respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008and 2012 respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL2008 and 2012 respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and2012 respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012respectively
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
ltdrivegtWebsrvrbin2 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 FilesMicrosoft SQLServer paste all files into the CProgram Files (x86)Microsoft SQL Server100DTSTasksfolder
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
50
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Typographic Conventions
Table 13
Example Description
lt gt Angle brackets indicate that you replace these words or characters with appropriate entries tomake entries in the system for example Enter your ltUser Namegt
File Save Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
Example Textual cross-references to an internet address for example wwwsapcom
example Quicklinks added to the internet address of a homepage to enable quick access to specificcontent 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 titlespushbutton 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 namesof installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transactioncodes database table names and key concepts of a programming language when they aresurrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
SAP Business Planning and Consolidation 100Typographic Conventions
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 51
52
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
wwwsapcom
Material Number
- SAP Business 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 2008 R2 2012 or 2012 R2
- 344 Removing Default Access to the Console
- 345 Management Console Access Control
- 346 Configuring Planning and Consolidation to use SSL
- 347 Using Client Certificates
- 348 Configuring MS SQL Server Reporting Services to use SSL
-
- 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
-
Component Minimum Requirement
Windows Server 2008 (64-bit) Standard Enterprise or Data Center with or withoutHyper-V
Windows Server 2008 R2 (64-bit) Foundation Standard Enterprise or DataCenter with or without Hyper-V
Windows Server 2012 (64-bit) Standard Data Center
Windows Server 2012 R2 (64-bit) Standard Data Center
NoteThe operating system must be configured with NTFS
Relational Database Microsoft SQL Server 2008 Enterprise Edition
Microsoft SQL Server 2008 R2 (Gemini) Enterprise Edition
Microsoft SQL Server 2012 Enterprise Edition
OLAP Database Microsoft SQL Server 2008 Enterprise Edition ndash Analysis Server
Microsoft SQL Server 2008 R2 Enterprise Edition ndash Analysis Server
Microsoft SQL Server 2012 Enterprise Edition ndash Analysis Server
Data Integration Microsoft SQL Server 2008 Enterprise Edition ndash SQL Service Integration Services
Microsoft SQL Server 2008 R2 Enterprise Edition ndash SQL Service IntegrationServices
Microsoft SQL Server 2012 Enterprise Edition ndash 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
NET 35 and NET 45 are required for Windows 2012 and 2012 R2
NET 40 is required for all other operating systems
IIS
IIS 75 or IIS 70
(Included in your Operating System IIS 75 is required for Windows 2008 R2editions)
IIS 80 or IIS 85
(Included in your Operating System IIS 85 is required for Windows 2012 R2editions)
Anti-Cross Site Scripting Library 42
This component must be downloaded before installing the server The serverinstallation program asks for the path of each file and copies the files into theappropriate Planning and Consolidation path
Microsoft Visual C++ 2010 SP1 Redistributable Package (x64)
Microsoft Access Database Engine 2010 64bit
12
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
Component Minimum Requirement
VMWare ESX 3x or ESX 40
(Required only if a landscape deployment strategy using virtualizationtechnologies is planned)
NoteMSXML 40 SP2 ADOMDNET 100 and Microsoft Visual C++ 2010 SP1Redistributable Package (x64) are included with the installation program but notinstalled 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 values being returned withcalculated accounts For more information see SAP Note number 1429246 which also contains downloadinformation
We recommend SQL Server 2008 (or R2) Enterprise Edition or SQL Server 2012 Enterprise Edition for theOLAP database to support proactive cache and cube partitioning It is technically possible to use SQL Server2008 (or R2) Standard Edition or SQL Server 2012 Standard Edition for data integration servers but we donot recommend this
23 Before Starting the Planning and Consolidation ServerInstallation
You must perform the following tasks before starting your Planning and Consolidation server installation
Install all the prerequisite software including all of the latest Microsoft hotfixes For more information seeInstalling the Prerequisites [page 17]
If you access your application through a firewall verify with your network administrator which TCP ports tochoose during the installation By default port 80 is the setting for standard http access and port 443 is thesetting for https access If you require a service to listen on a different port you can specify it during theinstallation 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 onwhich 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 Consolidationand automatically overwrites the previous version If you have made any modifications to EnvironmentShellthat 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 ScriptBlocking
If a version of Planning and Consolidation on a NetWeaver platform exists uninstall it before you install Planningand Consolidation 100 version for the Microsoft platform
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 13
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 enterconvert c fsntfsV
All servers in a multiserver environment must be members of the same domain
In a multiserver environment the installing ID must be a domain user ID We recommend that you do not logon to the servers using a local server user ID even if the user ID is a member of the Administrator group on theserver This way you have the proper authority to install software and to modify the Component Services SeeLogging On to Servers [page 14]
You must determine the IP addresses or server names for all servers before installing Planning andConsolidation 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 portaccess reasons (DMZ WORKGROUP or nontrusted domain authentication failures) do the following
1 Copy the EnvironmentShell database file ServerEnvironmentShelldb10 from the Planning andConsolidation 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 theEnvironmentShell database file in the Server Information Advanced Options Local path forEnvironmentShell DB field (for example cEnvironmentShelldb10)
Install the Anti-Cross Site Scripting Library which provides protection to Web-based applications againstCross-Site Scripting (XSS) attacks See Installing the Anti-Cross Site Scripting Library [page 23]
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 theAdministrator group of a domain to which the server belongs or a member of the Administrator group on the localserver
Errors may display during the installation program and in the diagnostic program if the installing user is not assignedto the Administrator group directly but is assigned to a group with Administrator rights You can ignore thesemessages
NoteIf you change the password used to install Planning and Consolidation you must change the password for theapplicable Planning and Consolidation service To do this go to Server Manager on the application server andselect Server Reset Logon Credentials For more information see the SAP Planning and ConsolidationOperations Guide in servicesapcominstguidesepm-bpc 100 for the Microsoft Platform SBOP Plan amp Consol100 MS Administrators Guide
14
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
25 Service-level Accounts
Service accounts are Windows domain IDs with access to all Planning and Consolidation servers with varying levelsof privileges They allow the software to use the minimum amount of privilege required for each job making it moresecure
You must define these user IDs on the Windows machine For security purposes they should not be used to definePlanning and Consolidation users
Prerequisites
Planning and Consolidation 100 has the following Windows services
BPC SendGovernor which manages Microsoft Analysis Service locks to ensure consistent performance andavoid deadlocks
BPC ServiceManager which manages the System Landscape Directory (SLD) service logging service andglobal caches
BPC CTS ServiceManager which listens and handles CTS import requests from the CTS+ transportmanagement system
Since these services should be able to access to the FileShare server an Admin account is assigned automaticallyto the service during the installation of the Planning and Consolidation server program Even though an Adminaccount 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 serviceon the local machine This logon right strictly applies only to the local computer and must be granted in the LocalSecurity Policy
To edit the Local Security Policy of the computer you want to define the logon as a service permission performthe 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 supportmicrosoftcomkb259733
Features
During the installation enter user IDs and passwords for the following user types
System Admin ID
This ID is read-only and is the same as the installation user ID that is the system displays the ID on theinstallation screen but you cannot modify it This ID allows access to code that provides system administrator-level functionality For example this ID can write to the Windows registry has full access to the FileShare server
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 15
and can create remove backup and restore OLAP and SQL databases The system administrator should be amember 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 createsubdirectory access on the FileShare server readwrite metadata and application set database data in OLAPand can create and remove tables in SQL The Administrator should be a member of the domain users groupand 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 theservers has write access to FileShare data and can read metadata and data in OLAP and SQL The User IDmust 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 isinstalled you can change these settings using the Server Manager
NoteWhen defining server names the name refers to the NetBIOS name IP address and fully qualified domain names(FQDN)
Standard Settings
Standard settings are typically used for a single-server environment The following table describes each setting
Table 5
Server Option Value Description
SQL Database server name The name of the SQL DB server
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 computername
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
Table 6
Server Option Value Description
SQL Server Name The name of the SQL DB server Defaults to the local server
Instance name The SQL instance name If left blank the default instance is used
16
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
Server Option Value Description
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 computername
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 forhttp and 443 is the default for https
Authentication type Note If you have chosen SAP BusinessObjects User Management System in theinstallation screen Authentication type does not appear in Advanced settings (asthat IIS authentication type is Anonymous in CMS mode)
Windows or Kerberos The default is Windows If you change this value fromWindows to Kerberos you must make some additional changes
See the Kerberos authentication settings section in the SAP Library ServerManager Guide on servicesapcominstguidesEPM-BPC 100 for theMicrosoft Platform
Scheduler Server Name The name of the server used for scheduling usually the application server forexample GMPV50072862B If you have multiple application servers select theappropriate one
NoteIf the primary server stops working you must manually configure yourapplication 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 theoperating system IIS SQL server analysis services ADOMDNET and MSXML This section provides guidance on
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 17
installing each component For specific versions required see Prerequisites [page 11] and the Product AvailabilityMatrix on the SAP Service Marketplace at servicesapcompam Search on Planning and Consolidation
NoteTo ensure a successful installation you must install the software in the order listed in this procedure
Check all third-party infrastructure services to ensure that they are functioning and that their authenticationmodels 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 itsown 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 applicationserver before you start the installation You can find the UMC installation package (UMCexe) on the Planningand Consolidation CD in a folder called UMC_100_INSTALLER When you run the installation package the wizardguides 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 andConsolidation)
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 multiserverconfiguration See Installing the Operating System [page 19]
3 Install the latest service pack for your operating system To install this service pack go towwwmicrosoftcom
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 SQLServer [page 19]
6 From your SQL Server media install Analysis Services Enterprise Edition and its required service packs and hotfixes See Installing Analysis Services [page 23]
7 On your application server install ADOMDNET The Planning and Consolidation zip file contains theADOMDNET 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 followinglocation BPC SetupServermsxmlmsi
18
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
9 On your application server install Microsoft Visual C++ 2010 SP1 Redistributable Package (x64)
The Microsoft Visual C++ 2010 SP1 Redistributable Package (x64) installation package is contained in thePlanning and Consolidation zip file at the following location BPC SetupServervcredist_x64exe
NoteThe version of vcredist_x64exe in BPC SetupServer has been updated to 10040219 If you have aprevious 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 wwwmicrosoftcomdownloadsendetailsaspxFamilyID=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 Marketplaceat servicesapcompam Search on Planning and Consolidation
Business Planning and Consolidation can support all servers with an operating system in any language
NoteCurrently Business Planning and Consolidation does not support an operating system in bi-directionallanguages such as Hebrew
Procedure
If you are installing IIS 70 75 80 or 85 you must enable the following features
Enable Basic Authentication and Windows Authentication these are not installed by default
Install IIS 6 Metabase Compatibility role
Business Planning and Consolidation uses the ADSI provider to handle IIS administration such as virtualdirectory and security but IIS 7 does not install the ADSI provider by default
273 Installing the SQL Server
Prerequisites
During the installation procedure you have the opportunity to specify the location of the EnvironmentShell databasefile Check that it is possible to access EnvironmentShell from the location where you intend to install the SQL serverIf it is not possible for port access reasons (DMZ WORKGROUP or nontrusted domain authentication failures) copyEnvironmentShell to a location on the SQL server (for example CEnvironmentShelldb10) You specify thislocation on the Server Information page by choosing Server Information Advanced Options Local Path forEnvironmentShell DB
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 19
Procedure
This section describes the general steps for installing the SQL Server component options and considerations wheninstalling 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
NoteIf you encounter a 500 HTTP Error when trying to connect to the Planning and Consolidation Web Client referto Microsoft Support articles 2520479 and 2468871 for assistance
To reinforce security we recommend that you install the SQL server and SSAS components to a nondefaultinstance 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 Optionssection below then choose Next
4 Review disc space requirements then choose Next
5 In Server Configuration Perform the following actions
1 In the Service Accounts tab enter a Planning and Consolidation sysadmin account for the SQL ServerDatabase Engine and the SQL Server Analysis services This is required so that the Planning andConsolidation sysadmin can create and process the Planning and Consolidation database because theMicrosoft SQL server tries to back up or restore database with the privileged account This account is alsorequired 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 differentdomain 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 theapplication server and the account requires the folder access privilege for the application server
To ensure that you have the complete access privileges we recommend the Planning and Consolidationsysadmin 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 touse a restrictive SQL ID that works with the drill-through feature If you must restrict SQL authentication forsecurity 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 installationprogram
20
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
8 Choose Install to begin the installation with the options you have set
SQL Server Component Options
For Single-Machine Installations
Install the following components from the Feature Selection screen
Database Engine Services
Analysis Services
Integration Service which is listed as one of the Shared Features
For Multiple Machine Installations
For multiple machine installations install the following components on each server
Table 7
Server Component What to Install
SQL Server Database Engine Services
SSAS Server Analysis Services
Application Server The following Shared Features
Client Tools Connectivity
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 Server2008 R2 and SQL Server 2012
Process Dimension
It is now possible to process a dimension with multiple selections At processing time the process dimension modulemakes changed or added information for each dimension and process for all selected dimensions and cubes inparallel
Optimize Model
If there are custom partitions for a FACT partition in the OLAP database an optimization module can process custompartitions in parallel when Full or Incremental Optimize is performed However if a full optimize is performed withthe 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 parallelbecause 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 applicationserver and application set databases
NoteSetting the SQL isolation level to be Read Committed Snapshot mode for a database can only be done once andcannot be reversed
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 21
Real Time MOLAP
You can set the OLAP storage model of the write-back partition to be MOLAP (Multidimensional OLAP) This settingremains 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 asfollows
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 Servertrade20052008 which you can download from wwwmicrosoftcom (search on ldquoTable Partitioningrdquo to find all relevantarticles)
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 Thebrowser 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 localhostand external network interface machine
3 If you want to use IP1 which indicates Server IP set Enabled to Yes and specify the TCP Port as desired
4 Delete 0 from TCP Dynamic Ports Set IPAll - TCP Ports as desired (for example 1533)
RecommendationWe do not recommend using dynamic ports
In an SQL server the default instance has a listener which listens on a fixed port (TCP port 1433)However for the named instance the port on which the SQL server listens is random and dynamicallyselected when the named instance of the SQL server starts This recommendation prevents any conflictproblems
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 Setthe 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 thatthe user identified as the Log on as user has the sysadmin SQL Server role defined under Server Roles in theSQL Server Management Studio This is required so Analysis Services can process the SQL Server
From SQL Server Management Studio do the following tasks
22
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
1 If you want to use a port with a named instance select the server type Analysis Services select the servername (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 ServerProperties window displays which shows all configurable properties
3 For enhanced security change the default value to your port number (for example 2724) This means thatyou use a fixed port as for the SQL Server option Then choose OK
NoteWe do not support a nondefault port with the default instance in this release If you want to use the defaultinstance do not change the port number
Restart SQL and OLAP
Confirm that the installation has completed successfully by checking that there are no installation relatedproblems on the event viewer You can now install Planning and Consolidation
274 Installing Analysis Services
Procedure
After you install SQL Server and its required service packs and hotfixes you must install SQL Server Analysis Servicesand its required service packs and hotfixes
NoteIf you have migrated your Analysis Services repository to the SQL Server back up the database that contains therepository before installing this release
To install Analysis Services for SQL Server 2008 SQL Server 2008 R2 or SQL Server 2012 follow the steps andguidelines in technetmicrosoftcomen-uslibraryms143219aspx
To avoid slow performance when a user has more than six OLAP databases follow the steps and guidelines in thePerformance Guide for SQL 2008 at wwwmicrosoftcomdownloadsdetailsaspxFamilyID=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 tohave it available for the Planning and Consolidation installation program
1 Download the Anti-Cross Site Scripting Library file AntiXSSLibraryDLL from the Microsoft Web site atwwwmicrosoftcomdownloadendetailsaspxid=28589
2 Save the extracted file locally
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 23
When you install Planning and Consolidation Server a step in the process requires you to identify the path toAntiXssLibrarydll
28 Installing on a Single Server
When you install all Planning and Consolidation server components on a single server you should consider thefollowing 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 theuncompressed 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 Log on to the server with a local server user ID or domain user ID For more information see Logging on toservers [page 14]
3 Make sure all prerequisite software is installed on the server For more information see Installing thePrerequisites [page 17]
4 Obtain SAP Planning and Consolidation archive from the Downloads SAP Installations amp Upgrades areaof SAP Service Marketplace
5 Extract the files from the archive Go to the BPC Setup folder and run the StartUpexe file
6 From the Server Install screen select Install the Planning and Consolidation server
7 From the Welcome screen choose Next
8 From the License Agreement page choose I accept the terms of the license agreement then choose Next
9 From the Installation Method page accept the default Single machine enter a system ID for the systemlandscape directory (SLD) and choose Next
NoteEntering a system ID of the SLD is only required if you have a SAP Solution Manager license If you do nothave a SAP Solution Manager license you can leave this field empty
10 From the Authentication Method page choose the desired authentication method and choose Next
11 If you have chosen SAP BusinessObjects User Management System in the previous screen on the CMSAuthentication page enter the information required to log on to CMS as an administrator
The following information is required
24
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
Table 8
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 Thisgroup name is filtered as the default when adding a user in Planning andConsolidation Administration Use a comma ( ) to separate multiple names
12 After entering the CMS administrator authentication details choose Next
13 From the Service type accounts page enter service-level account user IDs and passwords See Service-LevelAccounts [page 15]
14 After defining the IDs and passwords choose Next
15 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 chooseNext
16 Specify the location and name of AntiXssLibrarydll See Installing the Anti-Cross Site ScriptingLibrary [page 23]
Choose Next
17 Select destination folders for Programs and Data The Data files include Webfolders and FileDB (publishedreports) and should be installed on a separate drive in a production environment This recommendation reducesthe hard disk IO time and helps to speed up SQL commands
Accept the defaults or make your selections then choose Next
18 Select the default values for the Web client The values are used to determine the default language and regionfor the Web client when you connect to it You can change the values in the Planning and Consolidation ServerManager
19 The installation process takes a few moments When it is complete choose Exit
20 A prompt is displayed to restart your computer Select OK to restart
21 Perform the steps in After Installing Planning and Consolidation Servers [page 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 avariety of ways and configure the servers as a Network Load Balancing (NLB) environment
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 25
The recommended Planning and Consolidation practice is to assign resources using a round robin approach for loadbalancing
You can install the SQL OLAP and FileShare types remotely from the application server You need to performadditional server installations if you have multiple application servers
Installing each Planning and Consolidation application server in a multiserver (NLB) configuration is identical to theprocedure 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 Balancingenvironment With this option there is an additional choice to Include sample environment (required on only oneof the application servers) This is because when you install the application server it connects to the databaseserver and creates the sample environment (EnvironmentShell) Installing the sample environment is requiredon 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
26
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
3 After Installing Planning and ConsolidationServers
31 Post-Installation Steps
Procedure
Perform these steps after installing the Planning and Consolidation servers for new installations of Planning andConsolidation
1 Connect your Planning and Consolidation system to Solution Manager Diagnostics (SMD) to allow support staffto identify analyze and resolve problems with your application See Connecting to Solution ManagerDiagnostics [page 28]
2 Configure the Planning and Consolidation NET and application server to ensure that it and its related servicesfunction properly and reliably For more information see Configuring the Planning and Consolidation NETApplication Server [page 29]
3 Optional configuration steps [page 29]
1 To ensure proper functioning of the Management Console create an SQL user and modify the System DSNand 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 loggingfor ODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default WebSite [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory canaccess the Management Console with whatever rights they have been granted on the server Forinformation about removing default access and creating a group that can access the console see RemovingDefault Access to the Console [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommendthat you only grant Management Console access to system administrators Planning and Consolidationusers should not have any access For more information see Management Console AccessControl [page 33]
6 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
4 Take the following steps to set up security
If you are defining security and application structure continue with step 5
If you want to designate someone other than the system administrator to manage security and applicationstructure log on to EnvironmentShell designate a user as a Primary Administrator
This user must have Administration ndash Environment and Security ‒ Define User task rights so that he or shecan 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 SeeInstalling the Administration Client [page 37]
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 27
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 taskprofiles 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 mustcomplete this step since there is no access to dimensions or members)
NoteTo allow users to request and query large amounts of data you can edit the metabasexml file located at CWindowssystem32inetsrv Set the following parameters to the stated values
ASPBUFFERINGLIMIT = 10485760
MAXREQUESTENTITYALLOWED = 10485760
32 Connecting to Solution Manager Diagnostics
NoteYou only need to perform the steps in this section if you have a SAP Solution Manager licence
The diagnostics functions in SAP Solution Manager allow identification analysis and resolution of problems Thisprocedure 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 areinstalled
NoteInstallation files for Diagnostics Agent are available on Service Marketplace by navigating to SupportPackages and Patches mdash Entry by Application Group SAP Technology Components SAP SOLUTIONMANAGER SAP SOLUTION MANAGER 70 EHP 1 Entry by Component Agents for managed systemsDIAGNOSTICS AGENT 711
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 whereMicrosoft 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
28
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
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 ServiceMarketplace at servicesapcom~sapidb011000358700000074392009E and follow the chapters that applyto Planning and Consolidation
33 Configuring the Planning and Consolidation NETApplication Servers
Procedure
Modifying machineconfig Files
To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock occurrences that wouldcause the application server to ldquosleeprdquo and not process anymore you can modify the machineconfig file whichresides in the WINDOWSMicrosoftNETFramework64v4030319Config directory
1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to specifywhether to automatically configure settings to achieve optimal performance based on the machineconfiguration You can set this attribute to True or False
For more information see msdnmicrosoftcomen-uslibrary7w2sway1aspx
2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the Planning andConsolidation application) or Machineconfig (for all applications including Planning and Consolidation) toensure the validationKey and decryptionKey keys have the same value on all application servers Thisway when the authentication cookie is checked the authentication ticket used on one server can still be validon another server
For more information and sample Visual Basic code for generating random key values seemsdnmicrosoftcomen-uslibraryms998288aspxpaght000007_webfarmdeploymentconsiderationsand msdnmicrosoftcomen-uslibraryms998310aspx
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 DSNand 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 forODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory can accessthe Management Console with whatever rights they have been granted on the server For information about
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 29
removing default access and creating a group that can access the console see Removing Default Access to theConsole [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommend thatyou only grant Management Console access to system administrators Planning and Consolidation users shouldnot have any access For more information see Management Console Access Control [page 33]
6 Configure the use of SSL in Planning and Consolidation See Configuring Planning and Consolidation to useSSL [page 34]
7 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
8 Configure Microsoft SQL Server Reporting Services to use SSL See Configuring MS SQL Server ReportingServices to use SSL [page 36]
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 databaserole 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 optionto use ODBC Logging Enter the following values
DSN is BPC_ManagementDSN Table is BPCLog The Microsoft SQL Server Username and Password
5 Restart IIS
NoteWithout these updates the Management Console does work but some functionality (specifically User Activityand Service Status) does not work as expected
Should you need to uninstall Planning and Consolidation we recommend that you reset the Active Log Formatfield in IIS to W3C Extended Log File Format
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
30
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
Prerequisites
ODBC logging has been configured according to the Microsoft Knowledge Base article 245243 How to configureODBC 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 inApplicationHostconfig as shown here
ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0logFormat=Custom gtUse 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-00AA006111E0appcmd 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 articlespecified in the Prerequisites section Configure these settings in the ltodbcLogginggt node underltsystemwebServergt
Exampleltlocation path=Default Web SitegtltsystemwebServergtltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog userName=Usernamepassword=mypassword gtltsystemwebServergtltlocationgt
Use the following AppCmds to configure these attributes for the default Web site
appcmd set config Default Web Site sectionodbcLogging dataSourceBPC_ManagementDSN commitappHostappcmd set config Default Web Site sectionodbcLogging tableNameBPCLog commitappHostappcmd set config Default Web Site sectionodbcLogging userNameUsername commitappHostappcmd set config Default Web Site sectionodbcLogging passwordmypassword commitappHost
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 31
NoteYou cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must use the SQL ServerODBC driver For more information see the Microsoft Knowledge Base article 931202 The requirements for usingthe ODBC logging feature in IIS
343 Setting Up an ODBC Data Source in Windows Server2008 2008 R2 2012 or 2012 R2
Procedure
This procedure describes how to set up an ODBC data source for the Management Console in Windows Server 20082008 R2 2012 or 2012 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
NoteIf you have chosen SAP BusinessObjects User Management System in the installation screen you do not needto remove or configure access because the Management Console service always runs with the System Admin IDaccount which is a member of the Administrators group
Procedure
To remove default access to the Management Console and create a group that does have access to the console usethe procedure described below
32
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
NoteCreate your Management Console administrative group either on the server that hosts the Management Consoleor 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
NoteAlternatively you can perform analogous steps in Active Directory
3 In the Groups context menu choose New Group
4 Enter data as required Click Create
5 In the Computer Management dialog box choose Services and Applications Internet InformationServices 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 objectand all child objects Include these with entries explicitly defined here checkbox
NoteThis step is a necessary precursor to the completion of this procedure
10 In the Security dialog box click Copy to ensure that the System group retains its privileges
11 Remove access to the Management Console from all groups that should not have it
12 Choose Authentication in the center pane then disable Windows authentication
Result
Users who have not been granted access to the Management Console can still open the Management Console Webpage but it contains no data or menu options This does not affect the access that a user would otherwise have toPlanning and Consolidation
345 Management Console Access Control
After establishing the Management Console group you can add users or groups to it For more information aboutcreating this group see Removing Default Access to the Console [page 32] Their rights in Active Directory determinewhat they can access in the Console
By default any member of the Administrators Active Directory group on the application server or domain has fullaccess to all of the features of the Console except the Planning and Consolidation logging area Access to Planningand Consolidation logging is controlled within the Planning and Consolidation Administration Client task securityThe user must be granted View system logs task privileges For more information see the SAP Library Planning and
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 33
Consolidation Administrators Guide in servicesapcominstguidesepm-bpc 100 version for the Microsoftplatform
Your IT policy determines whether you grant access by group or user You may wish to create several levels of Consoleusers (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 describedin this table
Table 9
Privilege Rights Management Area
Task Manager and Kill Process Administrators group on application server or domain
Performance Monitor Counters Administrators group on application server or domain
Power Users group on application server or domain
Performance Monitor Users group on application server
Microsoft Analysis Services performance monitoring Administrators group on application server or domain
Microsoft SQL Server Monitoring (performance counters andstatistics)
Administrators group on application server or domain
346 Configuring Planning and Consolidation to use SSL
Procedure
Creating a Certificate for the Server
During the handshake phase of the SSL communication the server must send its certificate to the client The clientthen uses the certificate to encrypt information and send it back to the server
The procedure below describes how to create a self-signed certificate for the server
RecommendationWe recommend that you limit the use of self-signed certificates to testing only For a productive system you shouldobtain a certificate signed by a well-known certification authority (CA)
1 Start the Internet Information Services (IIS) Manager To do that go to Start All Programs AdministrativeTools Internet Information Services (IIS) Manager
2 In the Connections panel on the left-hand side select the server node and then choose Server Certificates
3 In the Actions panel on the right hand side choose the Create Self-Signed Certificate action
4 Enter the name that you want the certificate to be identified by for example MyTestSSLCertificate
IIS generates a new SSL certificate for you that has one yearrsquos expiry lease The certificate is issued to the local servername
Binding the Certificate to the Web Site
The procedure below describes how to bind the certificate to the web site for which SSL connections must be used
1 In the Connections panel select the web site node
2 In the Actions panel choose Bindings
34
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
3 In the Site Bindings dialog that appears choose the Add button to create a new binding
4 Configure the parameters as follows
Type = https IP Address = [1] - this is a shorthand expression for the local server name
Port = 443 - this is the default SSL port
SSL Certificate = enter your newly created certificate name
5 Choose OK to create the new binding and then close the Site Bindings dialog
6 Restart the IIS processes To do this choose Restart from the Actions panel
7 In the middle panel under the IIS section choose SSL Settings
8 In the SSL Settings screen select the Require SSL checkbox
9 In the Actions panel choose to Apply these settings
To test the SSL connection in the Actions panel choose the Browse [1] 443 (https) link
347 Using Client Certificates
To enable the use of client certificates in Planning and Consolidation you must follow several manual steps
NotePlanning and Consolidation supports client certificate authentication in Windows Authentication Mode butdoes 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 technetmicrosoftcomen-uslibrarycc753810aspx
For more information about configuring the client certificate mapping authentication see technetmicrosoftcomen-uslibrarycc732996(WS10)aspx
When you create the client certificates you can set the type of certificate in the SSL Settings screen in InternetInformation Services (IIS) Manager
Procedure
1 Set the options for client certificates
1 In the IIS Manager select the web site where you installed Planning and Consolidation
2 Choose SSL Settings
3 In the Client certificates section select the Accept client certificates option
This option allows you to use a client certificate or username and password (Basic authentication) toconnect 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 theManagementConsole home page
3 Double-click Authentication and enable Anonymous Authentication
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 35
4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way asin step 3
5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the sameway 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
348 Configuring MS SQL Server Reporting Services to useSSL
Procedure
The procedure below describes how to configure the use of SSL in Microsoft SQL Server Reporting Services
NoteReporting Services does not provide functionalities for generating requesting or installing a certificate Theserver certificates that you want to use for configuring SSL must have already been installed on your computer
1 Open the Reporting Services Configuration Manager program To do this open the Windows Start menu andnavigate to All Programs Microsoft SQL Server ltversiongt Configuration Tools Reporting ServicesConfiguration Manager
2 In the Connect panel on the left-hand side select the Web Service URL option to open all the Report Server webservice parameters
3 Configure the parameters as follows
SSL Certificate = the name of the certificate that you want to use
SSL Port = 4434 Choose Apply to confirm the changes
5 In the Connect panel choose Report Manager URL to open the list of parameters that link Reporting Servicesto IIS
6 Choose Advanced to add your new SSL web URL
7 In the section Multiple SSL Identities for Report Manager choose Add Configure the parameters as follows
IP Address = (All IPv4) SSL Port = 443 Certificate = the name of your SSL certificate
8 To test the configuration click the URL that appears under the Report manager Site Identification section
36
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
4 Installing Planning and ConsolidationAdministration Client and the SAPBusinessObjects EPM solutions Add-in forMicrosoft Office
The installation of the Planning and Consolidation Administration Client allows administrators to build and maintainPlanning and Consolidation environments and models and administer security
All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions add-in forMicrosoft 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 valueof the Planning and Consolidation client to prompt for user name and password Otherwise the Planning andConsolidation Start Page does not display
41 Installing the Administration Client
Prerequisites
NoteFor a definitive list of system requirements see the Product Availability Matrix on SAP Service Marketplace atservicesapcompam Search on Planning and Consolidation
The following list describes the minimum software requirements
Microsoft Internet Explorer 70 80 90 or 10
Microsoft Office 2003 2007 2010 or 2012
NET Framework 20 or higher (install any required NET Framework Hotfixes by referring tosupportmicrosoftcomkb)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 37
NoteWe recommend that you install all of the latest Microsoft Windows hotfixes prior to installing the Administrationclient For information about which hotfixes to install see updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us
Procedure
The 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 ltPC_serverportgtsapbpcweb
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 mustdownload the most recent version of the full setup (EPM Add-inexe) from the Service Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPCInstallation folder
Individual users can install the EPM add-in on their own machines by going to the Planning and Consolidation Homepage 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 upthe 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
38
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
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 toperform the upgrade If Client Auto Update is not enabled and a newer version is detected clients must be installedmanually 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 andpassword in the Admin ID and Admin password fields respectively The Admin ID should be a member of thelocal administrators group on all the computers running the auto update This setting is not needed if all usershave 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 Thisoption is stored in the user preferences and may also be turned on or off using the User Optionshellip menu itemIf 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 toinstall 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 installit 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 servicesapcom
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 versionand policy information For a support package these files are
EPM Addin Support Package ltSP versiongtmsp EPM Addin Support Package ltSP versiongtxmlFor a patch these files are
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 (WebsrvrWebBPCInstallation)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 39
You can set a different update policy for each package listed
ExampleThe following table illustrates some possible situations assuming that you have installed the first full version(V1)
Table 10
Available maintenancepackages
V2-user update
V3-force update
V4-force update
V5-user update
V5-user update V5-user update
V6-auto update
V7-force update
Minimum RequiredVersion
V4 V4 V7
Notification A prompt tells the user toinstall maintenancepackage V4 using theForced Update behavior
If User Update is enabledthe prompt informs theuser that maintenancepackage V5 is available
A prompt tells the user toinstall maintenancepackage V7 using theForced Update behavior
New Version V4 V4 or V5 V7
If you change the update policy for any package click Update to complete the change
40
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
5 Connection Issues
You may experience connection problems with ports the proxy server or programs and settings that interact withthese components If you have any issues related to connection review the following recommendations andtroubleshooting tips
51 Checking for Open Ports
You must ensure that all required ports are open for inboundoutbound traffic By default Planning andConsolidation requires that Ports 80 (used by http) and 1433 and 2383 (used by SQL Server 2008) are open Totest whether the required ports are open go to a command prompt and enter the Telnet serveripaddress and portFor example Telnet 431181836 80 If the system returns a blank command window the port is open If it returnsa message stating that it is unable to connect the port is not open
NoteYou can use the following site to scan for the normal ports It allows you to manually enter a port number to test
wwwmyserverorgportsniffasp
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 Planningand Consolidation server as an exception You can do this at the client level ( Internet Explorer ToolsInternet 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 fullyqualified 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 Consolidationauthentication Do not use authentication on the proxy server The system synchronizes the user name andpassword on the remote server with the local user name and password
SAP Business Planning and Consolidation 100Connection Issues
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 41
NoteFor more information about setting up an ISA proxy server contact SAP Support to request a copy of Setting upISA Proxy Server White Paper For more information about Business Planning and Consolidation firewall portssee SAP Note 1505250
Internet Explorer Settings Issues
Internet Explorer settings must be set correctly to prevent errors and problems when you attempt to access thePlanning 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 insertthe IP address or fully qualified server name of the Planning and Consolidation server as an exception bychoosing 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
42
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Connection Issues
6 Installing Planning and Consolidation withTwo Active Directory Domains
To set up a Planning and Consolidation 10 application server in a hosted environment and use your own domainusers follow this procedure In general you install Planning and Consolidation on the host domain use the hostdomain account and assign it to the Planning and Consolidation users SysAdmin Admin and Users Then you acceptone 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 andpassword 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 topromote 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 privilegefor the Planning and Consolidation server
5 Install Planning and Consolidation and assign your domain account either to the three Planning andConsolidation administrative users SysAdmin Admin and Users or to only one of the three Planning andConsolidation administrative users and to three of your users Be sure you use your own user account ratherthan host domain users
Planning and Consolidation impersonation can then access your domain from the host environment becauseit has the privilege of your domain account
SAP Business Planning and Consolidation 100Installing Planning and Consolidation with Two Active Directory Domains
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 43
7 Installing Planning and Consolidation in aTerminal Services or Citrix ServerDeployment
This section describes best practices and instructions for installing Planning and Consolidation in a Terminal Servicesor Citrix Server deployment
71 Terminal Services Home Directories
We recommend using Terminal Server home directories rather than using the userrsquos profile directory The profiledirectory downloads a minimal amount of information about the dimensions of the environment you are logging onto and may be as large as 2 MB per user The profile directory is on the system drive and has limited space Byspecifying 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 individualserver 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 clientserver (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
44
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
Procedure
The following steps outline how to install the Planning and Consolidation clients in a Terminal Services (TS) or CitrixServer deployment
1 Make sure the Terminal Services or Citrix Server machine has the system requirements installed
2 Log on to the Terminal Services or Citrix Server machine with a user ID that has the rights to install on thatserver
3 At a command prompt enter Change userinstall
4 Open a browser and connect to the URL ltPC_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_MSBPCAdminMainexe
74 Creating a Shortcut to the Launch Page
Procedure
If you use published desktops instead of published applications the Planning and Consolidation desktop file (whichis installed on the current userrsquos desktop) must be moved to the All UsersDesktop folder
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 45
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 SQLServer 2012 support the remote modification of SSIS packages Planning and Consolidation also supports theremote 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 whichyou want to modify SSIS packages
These custom tasks reference dlls that connect to the database server and perform certain validation when usersset up the parameters of each task All the custom task reference components must also be installed in the machineon which you want to modify SSIS packages
We provide a program that registers all the reference components of the custom tasks This section explains theinstallation 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 ndash This folder contains all the dlls that should be installed on the machine There are Planning andConsolidation platform components and all of the Data Manager custom task files
Config folder ndash This folder contains only one file named Filelistxml and lists all of the files that should be installedIf you need to add or remove certain components from the installation you can modify this xml file
OSoftSetupexe ndash This is the main executable file to run the installation package
NoteIf you are not installing SSIS Custom Tasks on your client machine ndash specifically a machine other than the Planningand Consolidation application server ndash you must first install OSoftSSIS2008_Client or OSoftSSIS2012_Client onthe client machine followed by the SQL Server version If you want to use SQL 2008 Tasks under the SQL 2012environment you must install OSoftSSIS2008_Client on the application server For detailed information see SAPNote 1707410 You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package byextracting OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPCInstallation folder on the Planning and Consolidation server To modify SSIS packages on the Planning andConsolidation application server you need to install OSoftSSIS2008_Client or OSoftSSIS2012_Client for creatinga COM+ application For more information see Before You Modify the SSIS Packages [page 49] and Setup ofa COM+ Application on the Application Server [page 50]
Bin folder
This folder contains the following components
46
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Table 11
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012respectively
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
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 47
Name Remark
BPCWriteBackdll
InteropDTSdll
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 addmore components to the installation package you can copy the new components into the Bin folder and add theproper xml tags in FileListxml You need to enter information for the following tags
RegistType ndash This is the registration information of the component You can enter the following values
RegAsm ndash For NET component
48
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Regsvr32 ndash For VB6 component
Gacutil ndash For NET Framework component that should be registered into Global Assembly Cache
FileName ndash Component file name
OSoftSetupexe
This is the executable file to run the SSIS installation package Double-click the file to start the installation You needto enter information for the following fields
Set SQL server
Specify the SQL server name If your SQL Server has an instance specify the instance name
NoteIf you installed the OSoftSSIS2008_Client or OSoftSSIS2012_Client on the application server the SQL servername is automatically disabled
Set server credential
This is the credential name of the COM+ package component Enter the user ID and password that can accessyour SQL Server This should be either the System Admin ID or Admin ID that was registered as a COM+ userwhen 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 ifyou 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 packagesremotely This is also true for the application server that has SSIS installed The Planning and ConsolidationData Manager has the following custom tasks
Table 12
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008and 2012 respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and2012 respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012respectively
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 49
Name Remark
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and2012 respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008and 2012 respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL2008 and 2012 respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and2012 respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012respectively
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
ltdrivegtWebsrvrbin2 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 FilesMicrosoft SQLServer paste all files into the CProgram Files (x86)Microsoft SQL Server100DTSTasksfolder
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
50
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Typographic Conventions
Table 13
Example Description
lt gt Angle brackets indicate that you replace these words or characters with appropriate entries tomake entries in the system for example Enter your ltUser Namegt
File Save Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
Example Textual cross-references to an internet address for example wwwsapcom
example Quicklinks added to the internet address of a homepage to enable quick access to specificcontent 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 titlespushbutton 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 namesof installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transactioncodes database table names and key concepts of a programming language when they aresurrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
SAP Business Planning and Consolidation 100Typographic Conventions
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 51
52
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
wwwsapcom
Material Number
- SAP Business 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 2008 R2 2012 or 2012 R2
- 344 Removing Default Access to the Console
- 345 Management Console Access Control
- 346 Configuring Planning and Consolidation to use SSL
- 347 Using Client Certificates
- 348 Configuring MS SQL Server Reporting Services to use SSL
-
- 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
-
Component Minimum Requirement
VMWare ESX 3x or ESX 40
(Required only if a landscape deployment strategy using virtualizationtechnologies is planned)
NoteMSXML 40 SP2 ADOMDNET 100 and Microsoft Visual C++ 2010 SP1Redistributable Package (x64) are included with the installation program but notinstalled 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 values being returned withcalculated accounts For more information see SAP Note number 1429246 which also contains downloadinformation
We recommend SQL Server 2008 (or R2) Enterprise Edition or SQL Server 2012 Enterprise Edition for theOLAP database to support proactive cache and cube partitioning It is technically possible to use SQL Server2008 (or R2) Standard Edition or SQL Server 2012 Standard Edition for data integration servers but we donot recommend this
23 Before Starting the Planning and Consolidation ServerInstallation
You must perform the following tasks before starting your Planning and Consolidation server installation
Install all the prerequisite software including all of the latest Microsoft hotfixes For more information seeInstalling the Prerequisites [page 17]
If you access your application through a firewall verify with your network administrator which TCP ports tochoose during the installation By default port 80 is the setting for standard http access and port 443 is thesetting for https access If you require a service to listen on a different port you can specify it during theinstallation 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 onwhich 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 Consolidationand automatically overwrites the previous version If you have made any modifications to EnvironmentShellthat 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 ScriptBlocking
If a version of Planning and Consolidation on a NetWeaver platform exists uninstall it before you install Planningand Consolidation 100 version for the Microsoft platform
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 13
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 enterconvert c fsntfsV
All servers in a multiserver environment must be members of the same domain
In a multiserver environment the installing ID must be a domain user ID We recommend that you do not logon to the servers using a local server user ID even if the user ID is a member of the Administrator group on theserver This way you have the proper authority to install software and to modify the Component Services SeeLogging On to Servers [page 14]
You must determine the IP addresses or server names for all servers before installing Planning andConsolidation 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 portaccess reasons (DMZ WORKGROUP or nontrusted domain authentication failures) do the following
1 Copy the EnvironmentShell database file ServerEnvironmentShelldb10 from the Planning andConsolidation 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 theEnvironmentShell database file in the Server Information Advanced Options Local path forEnvironmentShell DB field (for example cEnvironmentShelldb10)
Install the Anti-Cross Site Scripting Library which provides protection to Web-based applications againstCross-Site Scripting (XSS) attacks See Installing the Anti-Cross Site Scripting Library [page 23]
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 theAdministrator group of a domain to which the server belongs or a member of the Administrator group on the localserver
Errors may display during the installation program and in the diagnostic program if the installing user is not assignedto the Administrator group directly but is assigned to a group with Administrator rights You can ignore thesemessages
NoteIf you change the password used to install Planning and Consolidation you must change the password for theapplicable Planning and Consolidation service To do this go to Server Manager on the application server andselect Server Reset Logon Credentials For more information see the SAP Planning and ConsolidationOperations Guide in servicesapcominstguidesepm-bpc 100 for the Microsoft Platform SBOP Plan amp Consol100 MS Administrators Guide
14
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
25 Service-level Accounts
Service accounts are Windows domain IDs with access to all Planning and Consolidation servers with varying levelsof privileges They allow the software to use the minimum amount of privilege required for each job making it moresecure
You must define these user IDs on the Windows machine For security purposes they should not be used to definePlanning and Consolidation users
Prerequisites
Planning and Consolidation 100 has the following Windows services
BPC SendGovernor which manages Microsoft Analysis Service locks to ensure consistent performance andavoid deadlocks
BPC ServiceManager which manages the System Landscape Directory (SLD) service logging service andglobal caches
BPC CTS ServiceManager which listens and handles CTS import requests from the CTS+ transportmanagement system
Since these services should be able to access to the FileShare server an Admin account is assigned automaticallyto the service during the installation of the Planning and Consolidation server program Even though an Adminaccount 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 serviceon the local machine This logon right strictly applies only to the local computer and must be granted in the LocalSecurity Policy
To edit the Local Security Policy of the computer you want to define the logon as a service permission performthe 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 supportmicrosoftcomkb259733
Features
During the installation enter user IDs and passwords for the following user types
System Admin ID
This ID is read-only and is the same as the installation user ID that is the system displays the ID on theinstallation screen but you cannot modify it This ID allows access to code that provides system administrator-level functionality For example this ID can write to the Windows registry has full access to the FileShare server
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 15
and can create remove backup and restore OLAP and SQL databases The system administrator should be amember 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 createsubdirectory access on the FileShare server readwrite metadata and application set database data in OLAPand can create and remove tables in SQL The Administrator should be a member of the domain users groupand 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 theservers has write access to FileShare data and can read metadata and data in OLAP and SQL The User IDmust 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 isinstalled you can change these settings using the Server Manager
NoteWhen defining server names the name refers to the NetBIOS name IP address and fully qualified domain names(FQDN)
Standard Settings
Standard settings are typically used for a single-server environment The following table describes each setting
Table 5
Server Option Value Description
SQL Database server name The name of the SQL DB server
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 computername
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
Table 6
Server Option Value Description
SQL Server Name The name of the SQL DB server Defaults to the local server
Instance name The SQL instance name If left blank the default instance is used
16
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
Server Option Value Description
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 computername
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 forhttp and 443 is the default for https
Authentication type Note If you have chosen SAP BusinessObjects User Management System in theinstallation screen Authentication type does not appear in Advanced settings (asthat IIS authentication type is Anonymous in CMS mode)
Windows or Kerberos The default is Windows If you change this value fromWindows to Kerberos you must make some additional changes
See the Kerberos authentication settings section in the SAP Library ServerManager Guide on servicesapcominstguidesEPM-BPC 100 for theMicrosoft Platform
Scheduler Server Name The name of the server used for scheduling usually the application server forexample GMPV50072862B If you have multiple application servers select theappropriate one
NoteIf the primary server stops working you must manually configure yourapplication 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 theoperating system IIS SQL server analysis services ADOMDNET and MSXML This section provides guidance on
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 17
installing each component For specific versions required see Prerequisites [page 11] and the Product AvailabilityMatrix on the SAP Service Marketplace at servicesapcompam Search on Planning and Consolidation
NoteTo ensure a successful installation you must install the software in the order listed in this procedure
Check all third-party infrastructure services to ensure that they are functioning and that their authenticationmodels 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 itsown 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 applicationserver before you start the installation You can find the UMC installation package (UMCexe) on the Planningand Consolidation CD in a folder called UMC_100_INSTALLER When you run the installation package the wizardguides 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 andConsolidation)
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 multiserverconfiguration See Installing the Operating System [page 19]
3 Install the latest service pack for your operating system To install this service pack go towwwmicrosoftcom
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 SQLServer [page 19]
6 From your SQL Server media install Analysis Services Enterprise Edition and its required service packs and hotfixes See Installing Analysis Services [page 23]
7 On your application server install ADOMDNET The Planning and Consolidation zip file contains theADOMDNET 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 followinglocation BPC SetupServermsxmlmsi
18
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
9 On your application server install Microsoft Visual C++ 2010 SP1 Redistributable Package (x64)
The Microsoft Visual C++ 2010 SP1 Redistributable Package (x64) installation package is contained in thePlanning and Consolidation zip file at the following location BPC SetupServervcredist_x64exe
NoteThe version of vcredist_x64exe in BPC SetupServer has been updated to 10040219 If you have aprevious 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 wwwmicrosoftcomdownloadsendetailsaspxFamilyID=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 Marketplaceat servicesapcompam Search on Planning and Consolidation
Business Planning and Consolidation can support all servers with an operating system in any language
NoteCurrently Business Planning and Consolidation does not support an operating system in bi-directionallanguages such as Hebrew
Procedure
If you are installing IIS 70 75 80 or 85 you must enable the following features
Enable Basic Authentication and Windows Authentication these are not installed by default
Install IIS 6 Metabase Compatibility role
Business Planning and Consolidation uses the ADSI provider to handle IIS administration such as virtualdirectory and security but IIS 7 does not install the ADSI provider by default
273 Installing the SQL Server
Prerequisites
During the installation procedure you have the opportunity to specify the location of the EnvironmentShell databasefile Check that it is possible to access EnvironmentShell from the location where you intend to install the SQL serverIf it is not possible for port access reasons (DMZ WORKGROUP or nontrusted domain authentication failures) copyEnvironmentShell to a location on the SQL server (for example CEnvironmentShelldb10) You specify thislocation on the Server Information page by choosing Server Information Advanced Options Local Path forEnvironmentShell DB
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 19
Procedure
This section describes the general steps for installing the SQL Server component options and considerations wheninstalling 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
NoteIf you encounter a 500 HTTP Error when trying to connect to the Planning and Consolidation Web Client referto Microsoft Support articles 2520479 and 2468871 for assistance
To reinforce security we recommend that you install the SQL server and SSAS components to a nondefaultinstance 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 Optionssection below then choose Next
4 Review disc space requirements then choose Next
5 In Server Configuration Perform the following actions
1 In the Service Accounts tab enter a Planning and Consolidation sysadmin account for the SQL ServerDatabase Engine and the SQL Server Analysis services This is required so that the Planning andConsolidation sysadmin can create and process the Planning and Consolidation database because theMicrosoft SQL server tries to back up or restore database with the privileged account This account is alsorequired 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 differentdomain 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 theapplication server and the account requires the folder access privilege for the application server
To ensure that you have the complete access privileges we recommend the Planning and Consolidationsysadmin 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 touse a restrictive SQL ID that works with the drill-through feature If you must restrict SQL authentication forsecurity 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 installationprogram
20
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
8 Choose Install to begin the installation with the options you have set
SQL Server Component Options
For Single-Machine Installations
Install the following components from the Feature Selection screen
Database Engine Services
Analysis Services
Integration Service which is listed as one of the Shared Features
For Multiple Machine Installations
For multiple machine installations install the following components on each server
Table 7
Server Component What to Install
SQL Server Database Engine Services
SSAS Server Analysis Services
Application Server The following Shared Features
Client Tools Connectivity
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 Server2008 R2 and SQL Server 2012
Process Dimension
It is now possible to process a dimension with multiple selections At processing time the process dimension modulemakes changed or added information for each dimension and process for all selected dimensions and cubes inparallel
Optimize Model
If there are custom partitions for a FACT partition in the OLAP database an optimization module can process custompartitions in parallel when Full or Incremental Optimize is performed However if a full optimize is performed withthe 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 parallelbecause 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 applicationserver and application set databases
NoteSetting the SQL isolation level to be Read Committed Snapshot mode for a database can only be done once andcannot be reversed
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 21
Real Time MOLAP
You can set the OLAP storage model of the write-back partition to be MOLAP (Multidimensional OLAP) This settingremains 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 asfollows
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 Servertrade20052008 which you can download from wwwmicrosoftcom (search on ldquoTable Partitioningrdquo to find all relevantarticles)
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 Thebrowser 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 localhostand external network interface machine
3 If you want to use IP1 which indicates Server IP set Enabled to Yes and specify the TCP Port as desired
4 Delete 0 from TCP Dynamic Ports Set IPAll - TCP Ports as desired (for example 1533)
RecommendationWe do not recommend using dynamic ports
In an SQL server the default instance has a listener which listens on a fixed port (TCP port 1433)However for the named instance the port on which the SQL server listens is random and dynamicallyselected when the named instance of the SQL server starts This recommendation prevents any conflictproblems
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 Setthe 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 thatthe user identified as the Log on as user has the sysadmin SQL Server role defined under Server Roles in theSQL Server Management Studio This is required so Analysis Services can process the SQL Server
From SQL Server Management Studio do the following tasks
22
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
1 If you want to use a port with a named instance select the server type Analysis Services select the servername (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 ServerProperties window displays which shows all configurable properties
3 For enhanced security change the default value to your port number (for example 2724) This means thatyou use a fixed port as for the SQL Server option Then choose OK
NoteWe do not support a nondefault port with the default instance in this release If you want to use the defaultinstance do not change the port number
Restart SQL and OLAP
Confirm that the installation has completed successfully by checking that there are no installation relatedproblems on the event viewer You can now install Planning and Consolidation
274 Installing Analysis Services
Procedure
After you install SQL Server and its required service packs and hotfixes you must install SQL Server Analysis Servicesand its required service packs and hotfixes
NoteIf you have migrated your Analysis Services repository to the SQL Server back up the database that contains therepository before installing this release
To install Analysis Services for SQL Server 2008 SQL Server 2008 R2 or SQL Server 2012 follow the steps andguidelines in technetmicrosoftcomen-uslibraryms143219aspx
To avoid slow performance when a user has more than six OLAP databases follow the steps and guidelines in thePerformance Guide for SQL 2008 at wwwmicrosoftcomdownloadsdetailsaspxFamilyID=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 tohave it available for the Planning and Consolidation installation program
1 Download the Anti-Cross Site Scripting Library file AntiXSSLibraryDLL from the Microsoft Web site atwwwmicrosoftcomdownloadendetailsaspxid=28589
2 Save the extracted file locally
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 23
When you install Planning and Consolidation Server a step in the process requires you to identify the path toAntiXssLibrarydll
28 Installing on a Single Server
When you install all Planning and Consolidation server components on a single server you should consider thefollowing 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 theuncompressed 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 Log on to the server with a local server user ID or domain user ID For more information see Logging on toservers [page 14]
3 Make sure all prerequisite software is installed on the server For more information see Installing thePrerequisites [page 17]
4 Obtain SAP Planning and Consolidation archive from the Downloads SAP Installations amp Upgrades areaof SAP Service Marketplace
5 Extract the files from the archive Go to the BPC Setup folder and run the StartUpexe file
6 From the Server Install screen select Install the Planning and Consolidation server
7 From the Welcome screen choose Next
8 From the License Agreement page choose I accept the terms of the license agreement then choose Next
9 From the Installation Method page accept the default Single machine enter a system ID for the systemlandscape directory (SLD) and choose Next
NoteEntering a system ID of the SLD is only required if you have a SAP Solution Manager license If you do nothave a SAP Solution Manager license you can leave this field empty
10 From the Authentication Method page choose the desired authentication method and choose Next
11 If you have chosen SAP BusinessObjects User Management System in the previous screen on the CMSAuthentication page enter the information required to log on to CMS as an administrator
The following information is required
24
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
Table 8
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 Thisgroup name is filtered as the default when adding a user in Planning andConsolidation Administration Use a comma ( ) to separate multiple names
12 After entering the CMS administrator authentication details choose Next
13 From the Service type accounts page enter service-level account user IDs and passwords See Service-LevelAccounts [page 15]
14 After defining the IDs and passwords choose Next
15 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 chooseNext
16 Specify the location and name of AntiXssLibrarydll See Installing the Anti-Cross Site ScriptingLibrary [page 23]
Choose Next
17 Select destination folders for Programs and Data The Data files include Webfolders and FileDB (publishedreports) and should be installed on a separate drive in a production environment This recommendation reducesthe hard disk IO time and helps to speed up SQL commands
Accept the defaults or make your selections then choose Next
18 Select the default values for the Web client The values are used to determine the default language and regionfor the Web client when you connect to it You can change the values in the Planning and Consolidation ServerManager
19 The installation process takes a few moments When it is complete choose Exit
20 A prompt is displayed to restart your computer Select OK to restart
21 Perform the steps in After Installing Planning and Consolidation Servers [page 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 avariety of ways and configure the servers as a Network Load Balancing (NLB) environment
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 25
The recommended Planning and Consolidation practice is to assign resources using a round robin approach for loadbalancing
You can install the SQL OLAP and FileShare types remotely from the application server You need to performadditional server installations if you have multiple application servers
Installing each Planning and Consolidation application server in a multiserver (NLB) configuration is identical to theprocedure 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 Balancingenvironment With this option there is an additional choice to Include sample environment (required on only oneof the application servers) This is because when you install the application server it connects to the databaseserver and creates the sample environment (EnvironmentShell) Installing the sample environment is requiredon 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
26
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
3 After Installing Planning and ConsolidationServers
31 Post-Installation Steps
Procedure
Perform these steps after installing the Planning and Consolidation servers for new installations of Planning andConsolidation
1 Connect your Planning and Consolidation system to Solution Manager Diagnostics (SMD) to allow support staffto identify analyze and resolve problems with your application See Connecting to Solution ManagerDiagnostics [page 28]
2 Configure the Planning and Consolidation NET and application server to ensure that it and its related servicesfunction properly and reliably For more information see Configuring the Planning and Consolidation NETApplication Server [page 29]
3 Optional configuration steps [page 29]
1 To ensure proper functioning of the Management Console create an SQL user and modify the System DSNand 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 loggingfor ODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default WebSite [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory canaccess the Management Console with whatever rights they have been granted on the server Forinformation about removing default access and creating a group that can access the console see RemovingDefault Access to the Console [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommendthat you only grant Management Console access to system administrators Planning and Consolidationusers should not have any access For more information see Management Console AccessControl [page 33]
6 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
4 Take the following steps to set up security
If you are defining security and application structure continue with step 5
If you want to designate someone other than the system administrator to manage security and applicationstructure log on to EnvironmentShell designate a user as a Primary Administrator
This user must have Administration ndash Environment and Security ‒ Define User task rights so that he or shecan 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 SeeInstalling the Administration Client [page 37]
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 27
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 taskprofiles 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 mustcomplete this step since there is no access to dimensions or members)
NoteTo allow users to request and query large amounts of data you can edit the metabasexml file located at CWindowssystem32inetsrv Set the following parameters to the stated values
ASPBUFFERINGLIMIT = 10485760
MAXREQUESTENTITYALLOWED = 10485760
32 Connecting to Solution Manager Diagnostics
NoteYou only need to perform the steps in this section if you have a SAP Solution Manager licence
The diagnostics functions in SAP Solution Manager allow identification analysis and resolution of problems Thisprocedure 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 areinstalled
NoteInstallation files for Diagnostics Agent are available on Service Marketplace by navigating to SupportPackages and Patches mdash Entry by Application Group SAP Technology Components SAP SOLUTIONMANAGER SAP SOLUTION MANAGER 70 EHP 1 Entry by Component Agents for managed systemsDIAGNOSTICS AGENT 711
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 whereMicrosoft 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
28
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
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 ServiceMarketplace at servicesapcom~sapidb011000358700000074392009E and follow the chapters that applyto Planning and Consolidation
33 Configuring the Planning and Consolidation NETApplication Servers
Procedure
Modifying machineconfig Files
To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock occurrences that wouldcause the application server to ldquosleeprdquo and not process anymore you can modify the machineconfig file whichresides in the WINDOWSMicrosoftNETFramework64v4030319Config directory
1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to specifywhether to automatically configure settings to achieve optimal performance based on the machineconfiguration You can set this attribute to True or False
For more information see msdnmicrosoftcomen-uslibrary7w2sway1aspx
2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the Planning andConsolidation application) or Machineconfig (for all applications including Planning and Consolidation) toensure the validationKey and decryptionKey keys have the same value on all application servers Thisway when the authentication cookie is checked the authentication ticket used on one server can still be validon another server
For more information and sample Visual Basic code for generating random key values seemsdnmicrosoftcomen-uslibraryms998288aspxpaght000007_webfarmdeploymentconsiderationsand msdnmicrosoftcomen-uslibraryms998310aspx
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 DSNand 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 forODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory can accessthe Management Console with whatever rights they have been granted on the server For information about
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 29
removing default access and creating a group that can access the console see Removing Default Access to theConsole [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommend thatyou only grant Management Console access to system administrators Planning and Consolidation users shouldnot have any access For more information see Management Console Access Control [page 33]
6 Configure the use of SSL in Planning and Consolidation See Configuring Planning and Consolidation to useSSL [page 34]
7 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
8 Configure Microsoft SQL Server Reporting Services to use SSL See Configuring MS SQL Server ReportingServices to use SSL [page 36]
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 databaserole 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 optionto use ODBC Logging Enter the following values
DSN is BPC_ManagementDSN Table is BPCLog The Microsoft SQL Server Username and Password
5 Restart IIS
NoteWithout these updates the Management Console does work but some functionality (specifically User Activityand Service Status) does not work as expected
Should you need to uninstall Planning and Consolidation we recommend that you reset the Active Log Formatfield in IIS to W3C Extended Log File Format
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
30
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
Prerequisites
ODBC logging has been configured according to the Microsoft Knowledge Base article 245243 How to configureODBC 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 inApplicationHostconfig as shown here
ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0logFormat=Custom gtUse 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-00AA006111E0appcmd 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 articlespecified in the Prerequisites section Configure these settings in the ltodbcLogginggt node underltsystemwebServergt
Exampleltlocation path=Default Web SitegtltsystemwebServergtltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog userName=Usernamepassword=mypassword gtltsystemwebServergtltlocationgt
Use the following AppCmds to configure these attributes for the default Web site
appcmd set config Default Web Site sectionodbcLogging dataSourceBPC_ManagementDSN commitappHostappcmd set config Default Web Site sectionodbcLogging tableNameBPCLog commitappHostappcmd set config Default Web Site sectionodbcLogging userNameUsername commitappHostappcmd set config Default Web Site sectionodbcLogging passwordmypassword commitappHost
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 31
NoteYou cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must use the SQL ServerODBC driver For more information see the Microsoft Knowledge Base article 931202 The requirements for usingthe ODBC logging feature in IIS
343 Setting Up an ODBC Data Source in Windows Server2008 2008 R2 2012 or 2012 R2
Procedure
This procedure describes how to set up an ODBC data source for the Management Console in Windows Server 20082008 R2 2012 or 2012 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
NoteIf you have chosen SAP BusinessObjects User Management System in the installation screen you do not needto remove or configure access because the Management Console service always runs with the System Admin IDaccount which is a member of the Administrators group
Procedure
To remove default access to the Management Console and create a group that does have access to the console usethe procedure described below
32
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
NoteCreate your Management Console administrative group either on the server that hosts the Management Consoleor 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
NoteAlternatively you can perform analogous steps in Active Directory
3 In the Groups context menu choose New Group
4 Enter data as required Click Create
5 In the Computer Management dialog box choose Services and Applications Internet InformationServices 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 objectand all child objects Include these with entries explicitly defined here checkbox
NoteThis step is a necessary precursor to the completion of this procedure
10 In the Security dialog box click Copy to ensure that the System group retains its privileges
11 Remove access to the Management Console from all groups that should not have it
12 Choose Authentication in the center pane then disable Windows authentication
Result
Users who have not been granted access to the Management Console can still open the Management Console Webpage but it contains no data or menu options This does not affect the access that a user would otherwise have toPlanning and Consolidation
345 Management Console Access Control
After establishing the Management Console group you can add users or groups to it For more information aboutcreating this group see Removing Default Access to the Console [page 32] Their rights in Active Directory determinewhat they can access in the Console
By default any member of the Administrators Active Directory group on the application server or domain has fullaccess to all of the features of the Console except the Planning and Consolidation logging area Access to Planningand Consolidation logging is controlled within the Planning and Consolidation Administration Client task securityThe user must be granted View system logs task privileges For more information see the SAP Library Planning and
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 33
Consolidation Administrators Guide in servicesapcominstguidesepm-bpc 100 version for the Microsoftplatform
Your IT policy determines whether you grant access by group or user You may wish to create several levels of Consoleusers (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 describedin this table
Table 9
Privilege Rights Management Area
Task Manager and Kill Process Administrators group on application server or domain
Performance Monitor Counters Administrators group on application server or domain
Power Users group on application server or domain
Performance Monitor Users group on application server
Microsoft Analysis Services performance monitoring Administrators group on application server or domain
Microsoft SQL Server Monitoring (performance counters andstatistics)
Administrators group on application server or domain
346 Configuring Planning and Consolidation to use SSL
Procedure
Creating a Certificate for the Server
During the handshake phase of the SSL communication the server must send its certificate to the client The clientthen uses the certificate to encrypt information and send it back to the server
The procedure below describes how to create a self-signed certificate for the server
RecommendationWe recommend that you limit the use of self-signed certificates to testing only For a productive system you shouldobtain a certificate signed by a well-known certification authority (CA)
1 Start the Internet Information Services (IIS) Manager To do that go to Start All Programs AdministrativeTools Internet Information Services (IIS) Manager
2 In the Connections panel on the left-hand side select the server node and then choose Server Certificates
3 In the Actions panel on the right hand side choose the Create Self-Signed Certificate action
4 Enter the name that you want the certificate to be identified by for example MyTestSSLCertificate
IIS generates a new SSL certificate for you that has one yearrsquos expiry lease The certificate is issued to the local servername
Binding the Certificate to the Web Site
The procedure below describes how to bind the certificate to the web site for which SSL connections must be used
1 In the Connections panel select the web site node
2 In the Actions panel choose Bindings
34
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
3 In the Site Bindings dialog that appears choose the Add button to create a new binding
4 Configure the parameters as follows
Type = https IP Address = [1] - this is a shorthand expression for the local server name
Port = 443 - this is the default SSL port
SSL Certificate = enter your newly created certificate name
5 Choose OK to create the new binding and then close the Site Bindings dialog
6 Restart the IIS processes To do this choose Restart from the Actions panel
7 In the middle panel under the IIS section choose SSL Settings
8 In the SSL Settings screen select the Require SSL checkbox
9 In the Actions panel choose to Apply these settings
To test the SSL connection in the Actions panel choose the Browse [1] 443 (https) link
347 Using Client Certificates
To enable the use of client certificates in Planning and Consolidation you must follow several manual steps
NotePlanning and Consolidation supports client certificate authentication in Windows Authentication Mode butdoes 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 technetmicrosoftcomen-uslibrarycc753810aspx
For more information about configuring the client certificate mapping authentication see technetmicrosoftcomen-uslibrarycc732996(WS10)aspx
When you create the client certificates you can set the type of certificate in the SSL Settings screen in InternetInformation Services (IIS) Manager
Procedure
1 Set the options for client certificates
1 In the IIS Manager select the web site where you installed Planning and Consolidation
2 Choose SSL Settings
3 In the Client certificates section select the Accept client certificates option
This option allows you to use a client certificate or username and password (Basic authentication) toconnect 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 theManagementConsole home page
3 Double-click Authentication and enable Anonymous Authentication
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 35
4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way asin step 3
5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the sameway 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
348 Configuring MS SQL Server Reporting Services to useSSL
Procedure
The procedure below describes how to configure the use of SSL in Microsoft SQL Server Reporting Services
NoteReporting Services does not provide functionalities for generating requesting or installing a certificate Theserver certificates that you want to use for configuring SSL must have already been installed on your computer
1 Open the Reporting Services Configuration Manager program To do this open the Windows Start menu andnavigate to All Programs Microsoft SQL Server ltversiongt Configuration Tools Reporting ServicesConfiguration Manager
2 In the Connect panel on the left-hand side select the Web Service URL option to open all the Report Server webservice parameters
3 Configure the parameters as follows
SSL Certificate = the name of the certificate that you want to use
SSL Port = 4434 Choose Apply to confirm the changes
5 In the Connect panel choose Report Manager URL to open the list of parameters that link Reporting Servicesto IIS
6 Choose Advanced to add your new SSL web URL
7 In the section Multiple SSL Identities for Report Manager choose Add Configure the parameters as follows
IP Address = (All IPv4) SSL Port = 443 Certificate = the name of your SSL certificate
8 To test the configuration click the URL that appears under the Report manager Site Identification section
36
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
4 Installing Planning and ConsolidationAdministration Client and the SAPBusinessObjects EPM solutions Add-in forMicrosoft Office
The installation of the Planning and Consolidation Administration Client allows administrators to build and maintainPlanning and Consolidation environments and models and administer security
All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions add-in forMicrosoft 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 valueof the Planning and Consolidation client to prompt for user name and password Otherwise the Planning andConsolidation Start Page does not display
41 Installing the Administration Client
Prerequisites
NoteFor a definitive list of system requirements see the Product Availability Matrix on SAP Service Marketplace atservicesapcompam Search on Planning and Consolidation
The following list describes the minimum software requirements
Microsoft Internet Explorer 70 80 90 or 10
Microsoft Office 2003 2007 2010 or 2012
NET Framework 20 or higher (install any required NET Framework Hotfixes by referring tosupportmicrosoftcomkb)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 37
NoteWe recommend that you install all of the latest Microsoft Windows hotfixes prior to installing the Administrationclient For information about which hotfixes to install see updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us
Procedure
The 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 ltPC_serverportgtsapbpcweb
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 mustdownload the most recent version of the full setup (EPM Add-inexe) from the Service Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPCInstallation folder
Individual users can install the EPM add-in on their own machines by going to the Planning and Consolidation Homepage 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 upthe 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
38
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
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 toperform the upgrade If Client Auto Update is not enabled and a newer version is detected clients must be installedmanually 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 andpassword in the Admin ID and Admin password fields respectively The Admin ID should be a member of thelocal administrators group on all the computers running the auto update This setting is not needed if all usershave 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 Thisoption is stored in the user preferences and may also be turned on or off using the User Optionshellip menu itemIf 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 toinstall 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 installit 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 servicesapcom
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 versionand policy information For a support package these files are
EPM Addin Support Package ltSP versiongtmsp EPM Addin Support Package ltSP versiongtxmlFor a patch these files are
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 (WebsrvrWebBPCInstallation)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 39
You can set a different update policy for each package listed
ExampleThe following table illustrates some possible situations assuming that you have installed the first full version(V1)
Table 10
Available maintenancepackages
V2-user update
V3-force update
V4-force update
V5-user update
V5-user update V5-user update
V6-auto update
V7-force update
Minimum RequiredVersion
V4 V4 V7
Notification A prompt tells the user toinstall maintenancepackage V4 using theForced Update behavior
If User Update is enabledthe prompt informs theuser that maintenancepackage V5 is available
A prompt tells the user toinstall maintenancepackage V7 using theForced Update behavior
New Version V4 V4 or V5 V7
If you change the update policy for any package click Update to complete the change
40
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
5 Connection Issues
You may experience connection problems with ports the proxy server or programs and settings that interact withthese components If you have any issues related to connection review the following recommendations andtroubleshooting tips
51 Checking for Open Ports
You must ensure that all required ports are open for inboundoutbound traffic By default Planning andConsolidation requires that Ports 80 (used by http) and 1433 and 2383 (used by SQL Server 2008) are open Totest whether the required ports are open go to a command prompt and enter the Telnet serveripaddress and portFor example Telnet 431181836 80 If the system returns a blank command window the port is open If it returnsa message stating that it is unable to connect the port is not open
NoteYou can use the following site to scan for the normal ports It allows you to manually enter a port number to test
wwwmyserverorgportsniffasp
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 Planningand Consolidation server as an exception You can do this at the client level ( Internet Explorer ToolsInternet 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 fullyqualified 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 Consolidationauthentication Do not use authentication on the proxy server The system synchronizes the user name andpassword on the remote server with the local user name and password
SAP Business Planning and Consolidation 100Connection Issues
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 41
NoteFor more information about setting up an ISA proxy server contact SAP Support to request a copy of Setting upISA Proxy Server White Paper For more information about Business Planning and Consolidation firewall portssee SAP Note 1505250
Internet Explorer Settings Issues
Internet Explorer settings must be set correctly to prevent errors and problems when you attempt to access thePlanning 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 insertthe IP address or fully qualified server name of the Planning and Consolidation server as an exception bychoosing 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
42
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Connection Issues
6 Installing Planning and Consolidation withTwo Active Directory Domains
To set up a Planning and Consolidation 10 application server in a hosted environment and use your own domainusers follow this procedure In general you install Planning and Consolidation on the host domain use the hostdomain account and assign it to the Planning and Consolidation users SysAdmin Admin and Users Then you acceptone 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 andpassword 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 topromote 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 privilegefor the Planning and Consolidation server
5 Install Planning and Consolidation and assign your domain account either to the three Planning andConsolidation administrative users SysAdmin Admin and Users or to only one of the three Planning andConsolidation administrative users and to three of your users Be sure you use your own user account ratherthan host domain users
Planning and Consolidation impersonation can then access your domain from the host environment becauseit has the privilege of your domain account
SAP Business Planning and Consolidation 100Installing Planning and Consolidation with Two Active Directory Domains
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 43
7 Installing Planning and Consolidation in aTerminal Services or Citrix ServerDeployment
This section describes best practices and instructions for installing Planning and Consolidation in a Terminal Servicesor Citrix Server deployment
71 Terminal Services Home Directories
We recommend using Terminal Server home directories rather than using the userrsquos profile directory The profiledirectory downloads a minimal amount of information about the dimensions of the environment you are logging onto and may be as large as 2 MB per user The profile directory is on the system drive and has limited space Byspecifying 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 individualserver 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 clientserver (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
44
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
Procedure
The following steps outline how to install the Planning and Consolidation clients in a Terminal Services (TS) or CitrixServer deployment
1 Make sure the Terminal Services or Citrix Server machine has the system requirements installed
2 Log on to the Terminal Services or Citrix Server machine with a user ID that has the rights to install on thatserver
3 At a command prompt enter Change userinstall
4 Open a browser and connect to the URL ltPC_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_MSBPCAdminMainexe
74 Creating a Shortcut to the Launch Page
Procedure
If you use published desktops instead of published applications the Planning and Consolidation desktop file (whichis installed on the current userrsquos desktop) must be moved to the All UsersDesktop folder
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 45
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 SQLServer 2012 support the remote modification of SSIS packages Planning and Consolidation also supports theremote 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 whichyou want to modify SSIS packages
These custom tasks reference dlls that connect to the database server and perform certain validation when usersset up the parameters of each task All the custom task reference components must also be installed in the machineon which you want to modify SSIS packages
We provide a program that registers all the reference components of the custom tasks This section explains theinstallation 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 ndash This folder contains all the dlls that should be installed on the machine There are Planning andConsolidation platform components and all of the Data Manager custom task files
Config folder ndash This folder contains only one file named Filelistxml and lists all of the files that should be installedIf you need to add or remove certain components from the installation you can modify this xml file
OSoftSetupexe ndash This is the main executable file to run the installation package
NoteIf you are not installing SSIS Custom Tasks on your client machine ndash specifically a machine other than the Planningand Consolidation application server ndash you must first install OSoftSSIS2008_Client or OSoftSSIS2012_Client onthe client machine followed by the SQL Server version If you want to use SQL 2008 Tasks under the SQL 2012environment you must install OSoftSSIS2008_Client on the application server For detailed information see SAPNote 1707410 You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package byextracting OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPCInstallation folder on the Planning and Consolidation server To modify SSIS packages on the Planning andConsolidation application server you need to install OSoftSSIS2008_Client or OSoftSSIS2012_Client for creatinga COM+ application For more information see Before You Modify the SSIS Packages [page 49] and Setup ofa COM+ Application on the Application Server [page 50]
Bin folder
This folder contains the following components
46
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Table 11
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012respectively
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
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 47
Name Remark
BPCWriteBackdll
InteropDTSdll
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 addmore components to the installation package you can copy the new components into the Bin folder and add theproper xml tags in FileListxml You need to enter information for the following tags
RegistType ndash This is the registration information of the component You can enter the following values
RegAsm ndash For NET component
48
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Regsvr32 ndash For VB6 component
Gacutil ndash For NET Framework component that should be registered into Global Assembly Cache
FileName ndash Component file name
OSoftSetupexe
This is the executable file to run the SSIS installation package Double-click the file to start the installation You needto enter information for the following fields
Set SQL server
Specify the SQL server name If your SQL Server has an instance specify the instance name
NoteIf you installed the OSoftSSIS2008_Client or OSoftSSIS2012_Client on the application server the SQL servername is automatically disabled
Set server credential
This is the credential name of the COM+ package component Enter the user ID and password that can accessyour SQL Server This should be either the System Admin ID or Admin ID that was registered as a COM+ userwhen 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 ifyou 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 packagesremotely This is also true for the application server that has SSIS installed The Planning and ConsolidationData Manager has the following custom tasks
Table 12
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008and 2012 respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and2012 respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012respectively
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 49
Name Remark
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and2012 respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008and 2012 respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL2008 and 2012 respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and2012 respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012respectively
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
ltdrivegtWebsrvrbin2 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 FilesMicrosoft SQLServer paste all files into the CProgram Files (x86)Microsoft SQL Server100DTSTasksfolder
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
50
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Typographic Conventions
Table 13
Example Description
lt gt Angle brackets indicate that you replace these words or characters with appropriate entries tomake entries in the system for example Enter your ltUser Namegt
File Save Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
Example Textual cross-references to an internet address for example wwwsapcom
example Quicklinks added to the internet address of a homepage to enable quick access to specificcontent 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 titlespushbutton 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 namesof installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transactioncodes database table names and key concepts of a programming language when they aresurrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
SAP Business Planning and Consolidation 100Typographic Conventions
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 51
52
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
wwwsapcom
Material Number
- SAP Business 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 2008 R2 2012 or 2012 R2
- 344 Removing Default Access to the Console
- 345 Management Console Access Control
- 346 Configuring Planning and Consolidation to use SSL
- 347 Using Client Certificates
- 348 Configuring MS SQL Server Reporting Services to use SSL
-
- 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
-
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 enterconvert c fsntfsV
All servers in a multiserver environment must be members of the same domain
In a multiserver environment the installing ID must be a domain user ID We recommend that you do not logon to the servers using a local server user ID even if the user ID is a member of the Administrator group on theserver This way you have the proper authority to install software and to modify the Component Services SeeLogging On to Servers [page 14]
You must determine the IP addresses or server names for all servers before installing Planning andConsolidation 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 portaccess reasons (DMZ WORKGROUP or nontrusted domain authentication failures) do the following
1 Copy the EnvironmentShell database file ServerEnvironmentShelldb10 from the Planning andConsolidation 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 theEnvironmentShell database file in the Server Information Advanced Options Local path forEnvironmentShell DB field (for example cEnvironmentShelldb10)
Install the Anti-Cross Site Scripting Library which provides protection to Web-based applications againstCross-Site Scripting (XSS) attacks See Installing the Anti-Cross Site Scripting Library [page 23]
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 theAdministrator group of a domain to which the server belongs or a member of the Administrator group on the localserver
Errors may display during the installation program and in the diagnostic program if the installing user is not assignedto the Administrator group directly but is assigned to a group with Administrator rights You can ignore thesemessages
NoteIf you change the password used to install Planning and Consolidation you must change the password for theapplicable Planning and Consolidation service To do this go to Server Manager on the application server andselect Server Reset Logon Credentials For more information see the SAP Planning and ConsolidationOperations Guide in servicesapcominstguidesepm-bpc 100 for the Microsoft Platform SBOP Plan amp Consol100 MS Administrators Guide
14
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
25 Service-level Accounts
Service accounts are Windows domain IDs with access to all Planning and Consolidation servers with varying levelsof privileges They allow the software to use the minimum amount of privilege required for each job making it moresecure
You must define these user IDs on the Windows machine For security purposes they should not be used to definePlanning and Consolidation users
Prerequisites
Planning and Consolidation 100 has the following Windows services
BPC SendGovernor which manages Microsoft Analysis Service locks to ensure consistent performance andavoid deadlocks
BPC ServiceManager which manages the System Landscape Directory (SLD) service logging service andglobal caches
BPC CTS ServiceManager which listens and handles CTS import requests from the CTS+ transportmanagement system
Since these services should be able to access to the FileShare server an Admin account is assigned automaticallyto the service during the installation of the Planning and Consolidation server program Even though an Adminaccount 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 serviceon the local machine This logon right strictly applies only to the local computer and must be granted in the LocalSecurity Policy
To edit the Local Security Policy of the computer you want to define the logon as a service permission performthe 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 supportmicrosoftcomkb259733
Features
During the installation enter user IDs and passwords for the following user types
System Admin ID
This ID is read-only and is the same as the installation user ID that is the system displays the ID on theinstallation screen but you cannot modify it This ID allows access to code that provides system administrator-level functionality For example this ID can write to the Windows registry has full access to the FileShare server
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 15
and can create remove backup and restore OLAP and SQL databases The system administrator should be amember 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 createsubdirectory access on the FileShare server readwrite metadata and application set database data in OLAPand can create and remove tables in SQL The Administrator should be a member of the domain users groupand 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 theservers has write access to FileShare data and can read metadata and data in OLAP and SQL The User IDmust 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 isinstalled you can change these settings using the Server Manager
NoteWhen defining server names the name refers to the NetBIOS name IP address and fully qualified domain names(FQDN)
Standard Settings
Standard settings are typically used for a single-server environment The following table describes each setting
Table 5
Server Option Value Description
SQL Database server name The name of the SQL DB server
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 computername
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
Table 6
Server Option Value Description
SQL Server Name The name of the SQL DB server Defaults to the local server
Instance name The SQL instance name If left blank the default instance is used
16
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
Server Option Value Description
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 computername
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 forhttp and 443 is the default for https
Authentication type Note If you have chosen SAP BusinessObjects User Management System in theinstallation screen Authentication type does not appear in Advanced settings (asthat IIS authentication type is Anonymous in CMS mode)
Windows or Kerberos The default is Windows If you change this value fromWindows to Kerberos you must make some additional changes
See the Kerberos authentication settings section in the SAP Library ServerManager Guide on servicesapcominstguidesEPM-BPC 100 for theMicrosoft Platform
Scheduler Server Name The name of the server used for scheduling usually the application server forexample GMPV50072862B If you have multiple application servers select theappropriate one
NoteIf the primary server stops working you must manually configure yourapplication 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 theoperating system IIS SQL server analysis services ADOMDNET and MSXML This section provides guidance on
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 17
installing each component For specific versions required see Prerequisites [page 11] and the Product AvailabilityMatrix on the SAP Service Marketplace at servicesapcompam Search on Planning and Consolidation
NoteTo ensure a successful installation you must install the software in the order listed in this procedure
Check all third-party infrastructure services to ensure that they are functioning and that their authenticationmodels 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 itsown 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 applicationserver before you start the installation You can find the UMC installation package (UMCexe) on the Planningand Consolidation CD in a folder called UMC_100_INSTALLER When you run the installation package the wizardguides 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 andConsolidation)
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 multiserverconfiguration See Installing the Operating System [page 19]
3 Install the latest service pack for your operating system To install this service pack go towwwmicrosoftcom
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 SQLServer [page 19]
6 From your SQL Server media install Analysis Services Enterprise Edition and its required service packs and hotfixes See Installing Analysis Services [page 23]
7 On your application server install ADOMDNET The Planning and Consolidation zip file contains theADOMDNET 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 followinglocation BPC SetupServermsxmlmsi
18
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
9 On your application server install Microsoft Visual C++ 2010 SP1 Redistributable Package (x64)
The Microsoft Visual C++ 2010 SP1 Redistributable Package (x64) installation package is contained in thePlanning and Consolidation zip file at the following location BPC SetupServervcredist_x64exe
NoteThe version of vcredist_x64exe in BPC SetupServer has been updated to 10040219 If you have aprevious 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 wwwmicrosoftcomdownloadsendetailsaspxFamilyID=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 Marketplaceat servicesapcompam Search on Planning and Consolidation
Business Planning and Consolidation can support all servers with an operating system in any language
NoteCurrently Business Planning and Consolidation does not support an operating system in bi-directionallanguages such as Hebrew
Procedure
If you are installing IIS 70 75 80 or 85 you must enable the following features
Enable Basic Authentication and Windows Authentication these are not installed by default
Install IIS 6 Metabase Compatibility role
Business Planning and Consolidation uses the ADSI provider to handle IIS administration such as virtualdirectory and security but IIS 7 does not install the ADSI provider by default
273 Installing the SQL Server
Prerequisites
During the installation procedure you have the opportunity to specify the location of the EnvironmentShell databasefile Check that it is possible to access EnvironmentShell from the location where you intend to install the SQL serverIf it is not possible for port access reasons (DMZ WORKGROUP or nontrusted domain authentication failures) copyEnvironmentShell to a location on the SQL server (for example CEnvironmentShelldb10) You specify thislocation on the Server Information page by choosing Server Information Advanced Options Local Path forEnvironmentShell DB
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 19
Procedure
This section describes the general steps for installing the SQL Server component options and considerations wheninstalling 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
NoteIf you encounter a 500 HTTP Error when trying to connect to the Planning and Consolidation Web Client referto Microsoft Support articles 2520479 and 2468871 for assistance
To reinforce security we recommend that you install the SQL server and SSAS components to a nondefaultinstance 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 Optionssection below then choose Next
4 Review disc space requirements then choose Next
5 In Server Configuration Perform the following actions
1 In the Service Accounts tab enter a Planning and Consolidation sysadmin account for the SQL ServerDatabase Engine and the SQL Server Analysis services This is required so that the Planning andConsolidation sysadmin can create and process the Planning and Consolidation database because theMicrosoft SQL server tries to back up or restore database with the privileged account This account is alsorequired 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 differentdomain 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 theapplication server and the account requires the folder access privilege for the application server
To ensure that you have the complete access privileges we recommend the Planning and Consolidationsysadmin 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 touse a restrictive SQL ID that works with the drill-through feature If you must restrict SQL authentication forsecurity 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 installationprogram
20
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
8 Choose Install to begin the installation with the options you have set
SQL Server Component Options
For Single-Machine Installations
Install the following components from the Feature Selection screen
Database Engine Services
Analysis Services
Integration Service which is listed as one of the Shared Features
For Multiple Machine Installations
For multiple machine installations install the following components on each server
Table 7
Server Component What to Install
SQL Server Database Engine Services
SSAS Server Analysis Services
Application Server The following Shared Features
Client Tools Connectivity
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 Server2008 R2 and SQL Server 2012
Process Dimension
It is now possible to process a dimension with multiple selections At processing time the process dimension modulemakes changed or added information for each dimension and process for all selected dimensions and cubes inparallel
Optimize Model
If there are custom partitions for a FACT partition in the OLAP database an optimization module can process custompartitions in parallel when Full or Incremental Optimize is performed However if a full optimize is performed withthe 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 parallelbecause 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 applicationserver and application set databases
NoteSetting the SQL isolation level to be Read Committed Snapshot mode for a database can only be done once andcannot be reversed
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 21
Real Time MOLAP
You can set the OLAP storage model of the write-back partition to be MOLAP (Multidimensional OLAP) This settingremains 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 asfollows
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 Servertrade20052008 which you can download from wwwmicrosoftcom (search on ldquoTable Partitioningrdquo to find all relevantarticles)
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 Thebrowser 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 localhostand external network interface machine
3 If you want to use IP1 which indicates Server IP set Enabled to Yes and specify the TCP Port as desired
4 Delete 0 from TCP Dynamic Ports Set IPAll - TCP Ports as desired (for example 1533)
RecommendationWe do not recommend using dynamic ports
In an SQL server the default instance has a listener which listens on a fixed port (TCP port 1433)However for the named instance the port on which the SQL server listens is random and dynamicallyselected when the named instance of the SQL server starts This recommendation prevents any conflictproblems
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 Setthe 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 thatthe user identified as the Log on as user has the sysadmin SQL Server role defined under Server Roles in theSQL Server Management Studio This is required so Analysis Services can process the SQL Server
From SQL Server Management Studio do the following tasks
22
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
1 If you want to use a port with a named instance select the server type Analysis Services select the servername (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 ServerProperties window displays which shows all configurable properties
3 For enhanced security change the default value to your port number (for example 2724) This means thatyou use a fixed port as for the SQL Server option Then choose OK
NoteWe do not support a nondefault port with the default instance in this release If you want to use the defaultinstance do not change the port number
Restart SQL and OLAP
Confirm that the installation has completed successfully by checking that there are no installation relatedproblems on the event viewer You can now install Planning and Consolidation
274 Installing Analysis Services
Procedure
After you install SQL Server and its required service packs and hotfixes you must install SQL Server Analysis Servicesand its required service packs and hotfixes
NoteIf you have migrated your Analysis Services repository to the SQL Server back up the database that contains therepository before installing this release
To install Analysis Services for SQL Server 2008 SQL Server 2008 R2 or SQL Server 2012 follow the steps andguidelines in technetmicrosoftcomen-uslibraryms143219aspx
To avoid slow performance when a user has more than six OLAP databases follow the steps and guidelines in thePerformance Guide for SQL 2008 at wwwmicrosoftcomdownloadsdetailsaspxFamilyID=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 tohave it available for the Planning and Consolidation installation program
1 Download the Anti-Cross Site Scripting Library file AntiXSSLibraryDLL from the Microsoft Web site atwwwmicrosoftcomdownloadendetailsaspxid=28589
2 Save the extracted file locally
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 23
When you install Planning and Consolidation Server a step in the process requires you to identify the path toAntiXssLibrarydll
28 Installing on a Single Server
When you install all Planning and Consolidation server components on a single server you should consider thefollowing 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 theuncompressed 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 Log on to the server with a local server user ID or domain user ID For more information see Logging on toservers [page 14]
3 Make sure all prerequisite software is installed on the server For more information see Installing thePrerequisites [page 17]
4 Obtain SAP Planning and Consolidation archive from the Downloads SAP Installations amp Upgrades areaof SAP Service Marketplace
5 Extract the files from the archive Go to the BPC Setup folder and run the StartUpexe file
6 From the Server Install screen select Install the Planning and Consolidation server
7 From the Welcome screen choose Next
8 From the License Agreement page choose I accept the terms of the license agreement then choose Next
9 From the Installation Method page accept the default Single machine enter a system ID for the systemlandscape directory (SLD) and choose Next
NoteEntering a system ID of the SLD is only required if you have a SAP Solution Manager license If you do nothave a SAP Solution Manager license you can leave this field empty
10 From the Authentication Method page choose the desired authentication method and choose Next
11 If you have chosen SAP BusinessObjects User Management System in the previous screen on the CMSAuthentication page enter the information required to log on to CMS as an administrator
The following information is required
24
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
Table 8
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 Thisgroup name is filtered as the default when adding a user in Planning andConsolidation Administration Use a comma ( ) to separate multiple names
12 After entering the CMS administrator authentication details choose Next
13 From the Service type accounts page enter service-level account user IDs and passwords See Service-LevelAccounts [page 15]
14 After defining the IDs and passwords choose Next
15 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 chooseNext
16 Specify the location and name of AntiXssLibrarydll See Installing the Anti-Cross Site ScriptingLibrary [page 23]
Choose Next
17 Select destination folders for Programs and Data The Data files include Webfolders and FileDB (publishedreports) and should be installed on a separate drive in a production environment This recommendation reducesthe hard disk IO time and helps to speed up SQL commands
Accept the defaults or make your selections then choose Next
18 Select the default values for the Web client The values are used to determine the default language and regionfor the Web client when you connect to it You can change the values in the Planning and Consolidation ServerManager
19 The installation process takes a few moments When it is complete choose Exit
20 A prompt is displayed to restart your computer Select OK to restart
21 Perform the steps in After Installing Planning and Consolidation Servers [page 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 avariety of ways and configure the servers as a Network Load Balancing (NLB) environment
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 25
The recommended Planning and Consolidation practice is to assign resources using a round robin approach for loadbalancing
You can install the SQL OLAP and FileShare types remotely from the application server You need to performadditional server installations if you have multiple application servers
Installing each Planning and Consolidation application server in a multiserver (NLB) configuration is identical to theprocedure 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 Balancingenvironment With this option there is an additional choice to Include sample environment (required on only oneof the application servers) This is because when you install the application server it connects to the databaseserver and creates the sample environment (EnvironmentShell) Installing the sample environment is requiredon 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
26
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
3 After Installing Planning and ConsolidationServers
31 Post-Installation Steps
Procedure
Perform these steps after installing the Planning and Consolidation servers for new installations of Planning andConsolidation
1 Connect your Planning and Consolidation system to Solution Manager Diagnostics (SMD) to allow support staffto identify analyze and resolve problems with your application See Connecting to Solution ManagerDiagnostics [page 28]
2 Configure the Planning and Consolidation NET and application server to ensure that it and its related servicesfunction properly and reliably For more information see Configuring the Planning and Consolidation NETApplication Server [page 29]
3 Optional configuration steps [page 29]
1 To ensure proper functioning of the Management Console create an SQL user and modify the System DSNand 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 loggingfor ODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default WebSite [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory canaccess the Management Console with whatever rights they have been granted on the server Forinformation about removing default access and creating a group that can access the console see RemovingDefault Access to the Console [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommendthat you only grant Management Console access to system administrators Planning and Consolidationusers should not have any access For more information see Management Console AccessControl [page 33]
6 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
4 Take the following steps to set up security
If you are defining security and application structure continue with step 5
If you want to designate someone other than the system administrator to manage security and applicationstructure log on to EnvironmentShell designate a user as a Primary Administrator
This user must have Administration ndash Environment and Security ‒ Define User task rights so that he or shecan 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 SeeInstalling the Administration Client [page 37]
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 27
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 taskprofiles 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 mustcomplete this step since there is no access to dimensions or members)
NoteTo allow users to request and query large amounts of data you can edit the metabasexml file located at CWindowssystem32inetsrv Set the following parameters to the stated values
ASPBUFFERINGLIMIT = 10485760
MAXREQUESTENTITYALLOWED = 10485760
32 Connecting to Solution Manager Diagnostics
NoteYou only need to perform the steps in this section if you have a SAP Solution Manager licence
The diagnostics functions in SAP Solution Manager allow identification analysis and resolution of problems Thisprocedure 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 areinstalled
NoteInstallation files for Diagnostics Agent are available on Service Marketplace by navigating to SupportPackages and Patches mdash Entry by Application Group SAP Technology Components SAP SOLUTIONMANAGER SAP SOLUTION MANAGER 70 EHP 1 Entry by Component Agents for managed systemsDIAGNOSTICS AGENT 711
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 whereMicrosoft 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
28
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
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 ServiceMarketplace at servicesapcom~sapidb011000358700000074392009E and follow the chapters that applyto Planning and Consolidation
33 Configuring the Planning and Consolidation NETApplication Servers
Procedure
Modifying machineconfig Files
To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock occurrences that wouldcause the application server to ldquosleeprdquo and not process anymore you can modify the machineconfig file whichresides in the WINDOWSMicrosoftNETFramework64v4030319Config directory
1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to specifywhether to automatically configure settings to achieve optimal performance based on the machineconfiguration You can set this attribute to True or False
For more information see msdnmicrosoftcomen-uslibrary7w2sway1aspx
2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the Planning andConsolidation application) or Machineconfig (for all applications including Planning and Consolidation) toensure the validationKey and decryptionKey keys have the same value on all application servers Thisway when the authentication cookie is checked the authentication ticket used on one server can still be validon another server
For more information and sample Visual Basic code for generating random key values seemsdnmicrosoftcomen-uslibraryms998288aspxpaght000007_webfarmdeploymentconsiderationsand msdnmicrosoftcomen-uslibraryms998310aspx
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 DSNand 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 forODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory can accessthe Management Console with whatever rights they have been granted on the server For information about
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 29
removing default access and creating a group that can access the console see Removing Default Access to theConsole [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommend thatyou only grant Management Console access to system administrators Planning and Consolidation users shouldnot have any access For more information see Management Console Access Control [page 33]
6 Configure the use of SSL in Planning and Consolidation See Configuring Planning and Consolidation to useSSL [page 34]
7 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
8 Configure Microsoft SQL Server Reporting Services to use SSL See Configuring MS SQL Server ReportingServices to use SSL [page 36]
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 databaserole 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 optionto use ODBC Logging Enter the following values
DSN is BPC_ManagementDSN Table is BPCLog The Microsoft SQL Server Username and Password
5 Restart IIS
NoteWithout these updates the Management Console does work but some functionality (specifically User Activityand Service Status) does not work as expected
Should you need to uninstall Planning and Consolidation we recommend that you reset the Active Log Formatfield in IIS to W3C Extended Log File Format
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
30
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
Prerequisites
ODBC logging has been configured according to the Microsoft Knowledge Base article 245243 How to configureODBC 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 inApplicationHostconfig as shown here
ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0logFormat=Custom gtUse 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-00AA006111E0appcmd 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 articlespecified in the Prerequisites section Configure these settings in the ltodbcLogginggt node underltsystemwebServergt
Exampleltlocation path=Default Web SitegtltsystemwebServergtltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog userName=Usernamepassword=mypassword gtltsystemwebServergtltlocationgt
Use the following AppCmds to configure these attributes for the default Web site
appcmd set config Default Web Site sectionodbcLogging dataSourceBPC_ManagementDSN commitappHostappcmd set config Default Web Site sectionodbcLogging tableNameBPCLog commitappHostappcmd set config Default Web Site sectionodbcLogging userNameUsername commitappHostappcmd set config Default Web Site sectionodbcLogging passwordmypassword commitappHost
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 31
NoteYou cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must use the SQL ServerODBC driver For more information see the Microsoft Knowledge Base article 931202 The requirements for usingthe ODBC logging feature in IIS
343 Setting Up an ODBC Data Source in Windows Server2008 2008 R2 2012 or 2012 R2
Procedure
This procedure describes how to set up an ODBC data source for the Management Console in Windows Server 20082008 R2 2012 or 2012 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
NoteIf you have chosen SAP BusinessObjects User Management System in the installation screen you do not needto remove or configure access because the Management Console service always runs with the System Admin IDaccount which is a member of the Administrators group
Procedure
To remove default access to the Management Console and create a group that does have access to the console usethe procedure described below
32
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
NoteCreate your Management Console administrative group either on the server that hosts the Management Consoleor 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
NoteAlternatively you can perform analogous steps in Active Directory
3 In the Groups context menu choose New Group
4 Enter data as required Click Create
5 In the Computer Management dialog box choose Services and Applications Internet InformationServices 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 objectand all child objects Include these with entries explicitly defined here checkbox
NoteThis step is a necessary precursor to the completion of this procedure
10 In the Security dialog box click Copy to ensure that the System group retains its privileges
11 Remove access to the Management Console from all groups that should not have it
12 Choose Authentication in the center pane then disable Windows authentication
Result
Users who have not been granted access to the Management Console can still open the Management Console Webpage but it contains no data or menu options This does not affect the access that a user would otherwise have toPlanning and Consolidation
345 Management Console Access Control
After establishing the Management Console group you can add users or groups to it For more information aboutcreating this group see Removing Default Access to the Console [page 32] Their rights in Active Directory determinewhat they can access in the Console
By default any member of the Administrators Active Directory group on the application server or domain has fullaccess to all of the features of the Console except the Planning and Consolidation logging area Access to Planningand Consolidation logging is controlled within the Planning and Consolidation Administration Client task securityThe user must be granted View system logs task privileges For more information see the SAP Library Planning and
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 33
Consolidation Administrators Guide in servicesapcominstguidesepm-bpc 100 version for the Microsoftplatform
Your IT policy determines whether you grant access by group or user You may wish to create several levels of Consoleusers (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 describedin this table
Table 9
Privilege Rights Management Area
Task Manager and Kill Process Administrators group on application server or domain
Performance Monitor Counters Administrators group on application server or domain
Power Users group on application server or domain
Performance Monitor Users group on application server
Microsoft Analysis Services performance monitoring Administrators group on application server or domain
Microsoft SQL Server Monitoring (performance counters andstatistics)
Administrators group on application server or domain
346 Configuring Planning and Consolidation to use SSL
Procedure
Creating a Certificate for the Server
During the handshake phase of the SSL communication the server must send its certificate to the client The clientthen uses the certificate to encrypt information and send it back to the server
The procedure below describes how to create a self-signed certificate for the server
RecommendationWe recommend that you limit the use of self-signed certificates to testing only For a productive system you shouldobtain a certificate signed by a well-known certification authority (CA)
1 Start the Internet Information Services (IIS) Manager To do that go to Start All Programs AdministrativeTools Internet Information Services (IIS) Manager
2 In the Connections panel on the left-hand side select the server node and then choose Server Certificates
3 In the Actions panel on the right hand side choose the Create Self-Signed Certificate action
4 Enter the name that you want the certificate to be identified by for example MyTestSSLCertificate
IIS generates a new SSL certificate for you that has one yearrsquos expiry lease The certificate is issued to the local servername
Binding the Certificate to the Web Site
The procedure below describes how to bind the certificate to the web site for which SSL connections must be used
1 In the Connections panel select the web site node
2 In the Actions panel choose Bindings
34
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
3 In the Site Bindings dialog that appears choose the Add button to create a new binding
4 Configure the parameters as follows
Type = https IP Address = [1] - this is a shorthand expression for the local server name
Port = 443 - this is the default SSL port
SSL Certificate = enter your newly created certificate name
5 Choose OK to create the new binding and then close the Site Bindings dialog
6 Restart the IIS processes To do this choose Restart from the Actions panel
7 In the middle panel under the IIS section choose SSL Settings
8 In the SSL Settings screen select the Require SSL checkbox
9 In the Actions panel choose to Apply these settings
To test the SSL connection in the Actions panel choose the Browse [1] 443 (https) link
347 Using Client Certificates
To enable the use of client certificates in Planning and Consolidation you must follow several manual steps
NotePlanning and Consolidation supports client certificate authentication in Windows Authentication Mode butdoes 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 technetmicrosoftcomen-uslibrarycc753810aspx
For more information about configuring the client certificate mapping authentication see technetmicrosoftcomen-uslibrarycc732996(WS10)aspx
When you create the client certificates you can set the type of certificate in the SSL Settings screen in InternetInformation Services (IIS) Manager
Procedure
1 Set the options for client certificates
1 In the IIS Manager select the web site where you installed Planning and Consolidation
2 Choose SSL Settings
3 In the Client certificates section select the Accept client certificates option
This option allows you to use a client certificate or username and password (Basic authentication) toconnect 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 theManagementConsole home page
3 Double-click Authentication and enable Anonymous Authentication
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 35
4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way asin step 3
5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the sameway 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
348 Configuring MS SQL Server Reporting Services to useSSL
Procedure
The procedure below describes how to configure the use of SSL in Microsoft SQL Server Reporting Services
NoteReporting Services does not provide functionalities for generating requesting or installing a certificate Theserver certificates that you want to use for configuring SSL must have already been installed on your computer
1 Open the Reporting Services Configuration Manager program To do this open the Windows Start menu andnavigate to All Programs Microsoft SQL Server ltversiongt Configuration Tools Reporting ServicesConfiguration Manager
2 In the Connect panel on the left-hand side select the Web Service URL option to open all the Report Server webservice parameters
3 Configure the parameters as follows
SSL Certificate = the name of the certificate that you want to use
SSL Port = 4434 Choose Apply to confirm the changes
5 In the Connect panel choose Report Manager URL to open the list of parameters that link Reporting Servicesto IIS
6 Choose Advanced to add your new SSL web URL
7 In the section Multiple SSL Identities for Report Manager choose Add Configure the parameters as follows
IP Address = (All IPv4) SSL Port = 443 Certificate = the name of your SSL certificate
8 To test the configuration click the URL that appears under the Report manager Site Identification section
36
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
4 Installing Planning and ConsolidationAdministration Client and the SAPBusinessObjects EPM solutions Add-in forMicrosoft Office
The installation of the Planning and Consolidation Administration Client allows administrators to build and maintainPlanning and Consolidation environments and models and administer security
All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions add-in forMicrosoft 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 valueof the Planning and Consolidation client to prompt for user name and password Otherwise the Planning andConsolidation Start Page does not display
41 Installing the Administration Client
Prerequisites
NoteFor a definitive list of system requirements see the Product Availability Matrix on SAP Service Marketplace atservicesapcompam Search on Planning and Consolidation
The following list describes the minimum software requirements
Microsoft Internet Explorer 70 80 90 or 10
Microsoft Office 2003 2007 2010 or 2012
NET Framework 20 or higher (install any required NET Framework Hotfixes by referring tosupportmicrosoftcomkb)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 37
NoteWe recommend that you install all of the latest Microsoft Windows hotfixes prior to installing the Administrationclient For information about which hotfixes to install see updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us
Procedure
The 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 ltPC_serverportgtsapbpcweb
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 mustdownload the most recent version of the full setup (EPM Add-inexe) from the Service Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPCInstallation folder
Individual users can install the EPM add-in on their own machines by going to the Planning and Consolidation Homepage 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 upthe 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
38
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
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 toperform the upgrade If Client Auto Update is not enabled and a newer version is detected clients must be installedmanually 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 andpassword in the Admin ID and Admin password fields respectively The Admin ID should be a member of thelocal administrators group on all the computers running the auto update This setting is not needed if all usershave 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 Thisoption is stored in the user preferences and may also be turned on or off using the User Optionshellip menu itemIf 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 toinstall 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 installit 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 servicesapcom
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 versionand policy information For a support package these files are
EPM Addin Support Package ltSP versiongtmsp EPM Addin Support Package ltSP versiongtxmlFor a patch these files are
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 (WebsrvrWebBPCInstallation)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 39
You can set a different update policy for each package listed
ExampleThe following table illustrates some possible situations assuming that you have installed the first full version(V1)
Table 10
Available maintenancepackages
V2-user update
V3-force update
V4-force update
V5-user update
V5-user update V5-user update
V6-auto update
V7-force update
Minimum RequiredVersion
V4 V4 V7
Notification A prompt tells the user toinstall maintenancepackage V4 using theForced Update behavior
If User Update is enabledthe prompt informs theuser that maintenancepackage V5 is available
A prompt tells the user toinstall maintenancepackage V7 using theForced Update behavior
New Version V4 V4 or V5 V7
If you change the update policy for any package click Update to complete the change
40
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
5 Connection Issues
You may experience connection problems with ports the proxy server or programs and settings that interact withthese components If you have any issues related to connection review the following recommendations andtroubleshooting tips
51 Checking for Open Ports
You must ensure that all required ports are open for inboundoutbound traffic By default Planning andConsolidation requires that Ports 80 (used by http) and 1433 and 2383 (used by SQL Server 2008) are open Totest whether the required ports are open go to a command prompt and enter the Telnet serveripaddress and portFor example Telnet 431181836 80 If the system returns a blank command window the port is open If it returnsa message stating that it is unable to connect the port is not open
NoteYou can use the following site to scan for the normal ports It allows you to manually enter a port number to test
wwwmyserverorgportsniffasp
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 Planningand Consolidation server as an exception You can do this at the client level ( Internet Explorer ToolsInternet 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 fullyqualified 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 Consolidationauthentication Do not use authentication on the proxy server The system synchronizes the user name andpassword on the remote server with the local user name and password
SAP Business Planning and Consolidation 100Connection Issues
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 41
NoteFor more information about setting up an ISA proxy server contact SAP Support to request a copy of Setting upISA Proxy Server White Paper For more information about Business Planning and Consolidation firewall portssee SAP Note 1505250
Internet Explorer Settings Issues
Internet Explorer settings must be set correctly to prevent errors and problems when you attempt to access thePlanning 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 insertthe IP address or fully qualified server name of the Planning and Consolidation server as an exception bychoosing 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
42
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Connection Issues
6 Installing Planning and Consolidation withTwo Active Directory Domains
To set up a Planning and Consolidation 10 application server in a hosted environment and use your own domainusers follow this procedure In general you install Planning and Consolidation on the host domain use the hostdomain account and assign it to the Planning and Consolidation users SysAdmin Admin and Users Then you acceptone 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 andpassword 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 topromote 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 privilegefor the Planning and Consolidation server
5 Install Planning and Consolidation and assign your domain account either to the three Planning andConsolidation administrative users SysAdmin Admin and Users or to only one of the three Planning andConsolidation administrative users and to three of your users Be sure you use your own user account ratherthan host domain users
Planning and Consolidation impersonation can then access your domain from the host environment becauseit has the privilege of your domain account
SAP Business Planning and Consolidation 100Installing Planning and Consolidation with Two Active Directory Domains
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 43
7 Installing Planning and Consolidation in aTerminal Services or Citrix ServerDeployment
This section describes best practices and instructions for installing Planning and Consolidation in a Terminal Servicesor Citrix Server deployment
71 Terminal Services Home Directories
We recommend using Terminal Server home directories rather than using the userrsquos profile directory The profiledirectory downloads a minimal amount of information about the dimensions of the environment you are logging onto and may be as large as 2 MB per user The profile directory is on the system drive and has limited space Byspecifying 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 individualserver 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 clientserver (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
44
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
Procedure
The following steps outline how to install the Planning and Consolidation clients in a Terminal Services (TS) or CitrixServer deployment
1 Make sure the Terminal Services or Citrix Server machine has the system requirements installed
2 Log on to the Terminal Services or Citrix Server machine with a user ID that has the rights to install on thatserver
3 At a command prompt enter Change userinstall
4 Open a browser and connect to the URL ltPC_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_MSBPCAdminMainexe
74 Creating a Shortcut to the Launch Page
Procedure
If you use published desktops instead of published applications the Planning and Consolidation desktop file (whichis installed on the current userrsquos desktop) must be moved to the All UsersDesktop folder
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 45
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 SQLServer 2012 support the remote modification of SSIS packages Planning and Consolidation also supports theremote 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 whichyou want to modify SSIS packages
These custom tasks reference dlls that connect to the database server and perform certain validation when usersset up the parameters of each task All the custom task reference components must also be installed in the machineon which you want to modify SSIS packages
We provide a program that registers all the reference components of the custom tasks This section explains theinstallation 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 ndash This folder contains all the dlls that should be installed on the machine There are Planning andConsolidation platform components and all of the Data Manager custom task files
Config folder ndash This folder contains only one file named Filelistxml and lists all of the files that should be installedIf you need to add or remove certain components from the installation you can modify this xml file
OSoftSetupexe ndash This is the main executable file to run the installation package
NoteIf you are not installing SSIS Custom Tasks on your client machine ndash specifically a machine other than the Planningand Consolidation application server ndash you must first install OSoftSSIS2008_Client or OSoftSSIS2012_Client onthe client machine followed by the SQL Server version If you want to use SQL 2008 Tasks under the SQL 2012environment you must install OSoftSSIS2008_Client on the application server For detailed information see SAPNote 1707410 You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package byextracting OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPCInstallation folder on the Planning and Consolidation server To modify SSIS packages on the Planning andConsolidation application server you need to install OSoftSSIS2008_Client or OSoftSSIS2012_Client for creatinga COM+ application For more information see Before You Modify the SSIS Packages [page 49] and Setup ofa COM+ Application on the Application Server [page 50]
Bin folder
This folder contains the following components
46
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Table 11
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012respectively
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
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 47
Name Remark
BPCWriteBackdll
InteropDTSdll
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 addmore components to the installation package you can copy the new components into the Bin folder and add theproper xml tags in FileListxml You need to enter information for the following tags
RegistType ndash This is the registration information of the component You can enter the following values
RegAsm ndash For NET component
48
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Regsvr32 ndash For VB6 component
Gacutil ndash For NET Framework component that should be registered into Global Assembly Cache
FileName ndash Component file name
OSoftSetupexe
This is the executable file to run the SSIS installation package Double-click the file to start the installation You needto enter information for the following fields
Set SQL server
Specify the SQL server name If your SQL Server has an instance specify the instance name
NoteIf you installed the OSoftSSIS2008_Client or OSoftSSIS2012_Client on the application server the SQL servername is automatically disabled
Set server credential
This is the credential name of the COM+ package component Enter the user ID and password that can accessyour SQL Server This should be either the System Admin ID or Admin ID that was registered as a COM+ userwhen 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 ifyou 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 packagesremotely This is also true for the application server that has SSIS installed The Planning and ConsolidationData Manager has the following custom tasks
Table 12
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008and 2012 respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and2012 respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012respectively
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 49
Name Remark
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and2012 respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008and 2012 respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL2008 and 2012 respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and2012 respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012respectively
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
ltdrivegtWebsrvrbin2 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 FilesMicrosoft SQLServer paste all files into the CProgram Files (x86)Microsoft SQL Server100DTSTasksfolder
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
50
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Typographic Conventions
Table 13
Example Description
lt gt Angle brackets indicate that you replace these words or characters with appropriate entries tomake entries in the system for example Enter your ltUser Namegt
File Save Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
Example Textual cross-references to an internet address for example wwwsapcom
example Quicklinks added to the internet address of a homepage to enable quick access to specificcontent 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 titlespushbutton 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 namesof installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transactioncodes database table names and key concepts of a programming language when they aresurrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
SAP Business Planning and Consolidation 100Typographic Conventions
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 51
52
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
wwwsapcom
Material Number
- SAP Business 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 2008 R2 2012 or 2012 R2
- 344 Removing Default Access to the Console
- 345 Management Console Access Control
- 346 Configuring Planning and Consolidation to use SSL
- 347 Using Client Certificates
- 348 Configuring MS SQL Server Reporting Services to use SSL
-
- 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
-
25 Service-level Accounts
Service accounts are Windows domain IDs with access to all Planning and Consolidation servers with varying levelsof privileges They allow the software to use the minimum amount of privilege required for each job making it moresecure
You must define these user IDs on the Windows machine For security purposes they should not be used to definePlanning and Consolidation users
Prerequisites
Planning and Consolidation 100 has the following Windows services
BPC SendGovernor which manages Microsoft Analysis Service locks to ensure consistent performance andavoid deadlocks
BPC ServiceManager which manages the System Landscape Directory (SLD) service logging service andglobal caches
BPC CTS ServiceManager which listens and handles CTS import requests from the CTS+ transportmanagement system
Since these services should be able to access to the FileShare server an Admin account is assigned automaticallyto the service during the installation of the Planning and Consolidation server program Even though an Adminaccount 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 serviceon the local machine This logon right strictly applies only to the local computer and must be granted in the LocalSecurity Policy
To edit the Local Security Policy of the computer you want to define the logon as a service permission performthe 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 supportmicrosoftcomkb259733
Features
During the installation enter user IDs and passwords for the following user types
System Admin ID
This ID is read-only and is the same as the installation user ID that is the system displays the ID on theinstallation screen but you cannot modify it This ID allows access to code that provides system administrator-level functionality For example this ID can write to the Windows registry has full access to the FileShare server
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 15
and can create remove backup and restore OLAP and SQL databases The system administrator should be amember 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 createsubdirectory access on the FileShare server readwrite metadata and application set database data in OLAPand can create and remove tables in SQL The Administrator should be a member of the domain users groupand 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 theservers has write access to FileShare data and can read metadata and data in OLAP and SQL The User IDmust 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 isinstalled you can change these settings using the Server Manager
NoteWhen defining server names the name refers to the NetBIOS name IP address and fully qualified domain names(FQDN)
Standard Settings
Standard settings are typically used for a single-server environment The following table describes each setting
Table 5
Server Option Value Description
SQL Database server name The name of the SQL DB server
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 computername
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
Table 6
Server Option Value Description
SQL Server Name The name of the SQL DB server Defaults to the local server
Instance name The SQL instance name If left blank the default instance is used
16
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
Server Option Value Description
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 computername
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 forhttp and 443 is the default for https
Authentication type Note If you have chosen SAP BusinessObjects User Management System in theinstallation screen Authentication type does not appear in Advanced settings (asthat IIS authentication type is Anonymous in CMS mode)
Windows or Kerberos The default is Windows If you change this value fromWindows to Kerberos you must make some additional changes
See the Kerberos authentication settings section in the SAP Library ServerManager Guide on servicesapcominstguidesEPM-BPC 100 for theMicrosoft Platform
Scheduler Server Name The name of the server used for scheduling usually the application server forexample GMPV50072862B If you have multiple application servers select theappropriate one
NoteIf the primary server stops working you must manually configure yourapplication 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 theoperating system IIS SQL server analysis services ADOMDNET and MSXML This section provides guidance on
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 17
installing each component For specific versions required see Prerequisites [page 11] and the Product AvailabilityMatrix on the SAP Service Marketplace at servicesapcompam Search on Planning and Consolidation
NoteTo ensure a successful installation you must install the software in the order listed in this procedure
Check all third-party infrastructure services to ensure that they are functioning and that their authenticationmodels 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 itsown 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 applicationserver before you start the installation You can find the UMC installation package (UMCexe) on the Planningand Consolidation CD in a folder called UMC_100_INSTALLER When you run the installation package the wizardguides 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 andConsolidation)
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 multiserverconfiguration See Installing the Operating System [page 19]
3 Install the latest service pack for your operating system To install this service pack go towwwmicrosoftcom
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 SQLServer [page 19]
6 From your SQL Server media install Analysis Services Enterprise Edition and its required service packs and hotfixes See Installing Analysis Services [page 23]
7 On your application server install ADOMDNET The Planning and Consolidation zip file contains theADOMDNET 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 followinglocation BPC SetupServermsxmlmsi
18
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
9 On your application server install Microsoft Visual C++ 2010 SP1 Redistributable Package (x64)
The Microsoft Visual C++ 2010 SP1 Redistributable Package (x64) installation package is contained in thePlanning and Consolidation zip file at the following location BPC SetupServervcredist_x64exe
NoteThe version of vcredist_x64exe in BPC SetupServer has been updated to 10040219 If you have aprevious 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 wwwmicrosoftcomdownloadsendetailsaspxFamilyID=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 Marketplaceat servicesapcompam Search on Planning and Consolidation
Business Planning and Consolidation can support all servers with an operating system in any language
NoteCurrently Business Planning and Consolidation does not support an operating system in bi-directionallanguages such as Hebrew
Procedure
If you are installing IIS 70 75 80 or 85 you must enable the following features
Enable Basic Authentication and Windows Authentication these are not installed by default
Install IIS 6 Metabase Compatibility role
Business Planning and Consolidation uses the ADSI provider to handle IIS administration such as virtualdirectory and security but IIS 7 does not install the ADSI provider by default
273 Installing the SQL Server
Prerequisites
During the installation procedure you have the opportunity to specify the location of the EnvironmentShell databasefile Check that it is possible to access EnvironmentShell from the location where you intend to install the SQL serverIf it is not possible for port access reasons (DMZ WORKGROUP or nontrusted domain authentication failures) copyEnvironmentShell to a location on the SQL server (for example CEnvironmentShelldb10) You specify thislocation on the Server Information page by choosing Server Information Advanced Options Local Path forEnvironmentShell DB
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 19
Procedure
This section describes the general steps for installing the SQL Server component options and considerations wheninstalling 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
NoteIf you encounter a 500 HTTP Error when trying to connect to the Planning and Consolidation Web Client referto Microsoft Support articles 2520479 and 2468871 for assistance
To reinforce security we recommend that you install the SQL server and SSAS components to a nondefaultinstance 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 Optionssection below then choose Next
4 Review disc space requirements then choose Next
5 In Server Configuration Perform the following actions
1 In the Service Accounts tab enter a Planning and Consolidation sysadmin account for the SQL ServerDatabase Engine and the SQL Server Analysis services This is required so that the Planning andConsolidation sysadmin can create and process the Planning and Consolidation database because theMicrosoft SQL server tries to back up or restore database with the privileged account This account is alsorequired 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 differentdomain 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 theapplication server and the account requires the folder access privilege for the application server
To ensure that you have the complete access privileges we recommend the Planning and Consolidationsysadmin 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 touse a restrictive SQL ID that works with the drill-through feature If you must restrict SQL authentication forsecurity 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 installationprogram
20
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
8 Choose Install to begin the installation with the options you have set
SQL Server Component Options
For Single-Machine Installations
Install the following components from the Feature Selection screen
Database Engine Services
Analysis Services
Integration Service which is listed as one of the Shared Features
For Multiple Machine Installations
For multiple machine installations install the following components on each server
Table 7
Server Component What to Install
SQL Server Database Engine Services
SSAS Server Analysis Services
Application Server The following Shared Features
Client Tools Connectivity
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 Server2008 R2 and SQL Server 2012
Process Dimension
It is now possible to process a dimension with multiple selections At processing time the process dimension modulemakes changed or added information for each dimension and process for all selected dimensions and cubes inparallel
Optimize Model
If there are custom partitions for a FACT partition in the OLAP database an optimization module can process custompartitions in parallel when Full or Incremental Optimize is performed However if a full optimize is performed withthe 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 parallelbecause 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 applicationserver and application set databases
NoteSetting the SQL isolation level to be Read Committed Snapshot mode for a database can only be done once andcannot be reversed
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 21
Real Time MOLAP
You can set the OLAP storage model of the write-back partition to be MOLAP (Multidimensional OLAP) This settingremains 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 asfollows
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 Servertrade20052008 which you can download from wwwmicrosoftcom (search on ldquoTable Partitioningrdquo to find all relevantarticles)
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 Thebrowser 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 localhostand external network interface machine
3 If you want to use IP1 which indicates Server IP set Enabled to Yes and specify the TCP Port as desired
4 Delete 0 from TCP Dynamic Ports Set IPAll - TCP Ports as desired (for example 1533)
RecommendationWe do not recommend using dynamic ports
In an SQL server the default instance has a listener which listens on a fixed port (TCP port 1433)However for the named instance the port on which the SQL server listens is random and dynamicallyselected when the named instance of the SQL server starts This recommendation prevents any conflictproblems
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 Setthe 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 thatthe user identified as the Log on as user has the sysadmin SQL Server role defined under Server Roles in theSQL Server Management Studio This is required so Analysis Services can process the SQL Server
From SQL Server Management Studio do the following tasks
22
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
1 If you want to use a port with a named instance select the server type Analysis Services select the servername (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 ServerProperties window displays which shows all configurable properties
3 For enhanced security change the default value to your port number (for example 2724) This means thatyou use a fixed port as for the SQL Server option Then choose OK
NoteWe do not support a nondefault port with the default instance in this release If you want to use the defaultinstance do not change the port number
Restart SQL and OLAP
Confirm that the installation has completed successfully by checking that there are no installation relatedproblems on the event viewer You can now install Planning and Consolidation
274 Installing Analysis Services
Procedure
After you install SQL Server and its required service packs and hotfixes you must install SQL Server Analysis Servicesand its required service packs and hotfixes
NoteIf you have migrated your Analysis Services repository to the SQL Server back up the database that contains therepository before installing this release
To install Analysis Services for SQL Server 2008 SQL Server 2008 R2 or SQL Server 2012 follow the steps andguidelines in technetmicrosoftcomen-uslibraryms143219aspx
To avoid slow performance when a user has more than six OLAP databases follow the steps and guidelines in thePerformance Guide for SQL 2008 at wwwmicrosoftcomdownloadsdetailsaspxFamilyID=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 tohave it available for the Planning and Consolidation installation program
1 Download the Anti-Cross Site Scripting Library file AntiXSSLibraryDLL from the Microsoft Web site atwwwmicrosoftcomdownloadendetailsaspxid=28589
2 Save the extracted file locally
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 23
When you install Planning and Consolidation Server a step in the process requires you to identify the path toAntiXssLibrarydll
28 Installing on a Single Server
When you install all Planning and Consolidation server components on a single server you should consider thefollowing 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 theuncompressed 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 Log on to the server with a local server user ID or domain user ID For more information see Logging on toservers [page 14]
3 Make sure all prerequisite software is installed on the server For more information see Installing thePrerequisites [page 17]
4 Obtain SAP Planning and Consolidation archive from the Downloads SAP Installations amp Upgrades areaof SAP Service Marketplace
5 Extract the files from the archive Go to the BPC Setup folder and run the StartUpexe file
6 From the Server Install screen select Install the Planning and Consolidation server
7 From the Welcome screen choose Next
8 From the License Agreement page choose I accept the terms of the license agreement then choose Next
9 From the Installation Method page accept the default Single machine enter a system ID for the systemlandscape directory (SLD) and choose Next
NoteEntering a system ID of the SLD is only required if you have a SAP Solution Manager license If you do nothave a SAP Solution Manager license you can leave this field empty
10 From the Authentication Method page choose the desired authentication method and choose Next
11 If you have chosen SAP BusinessObjects User Management System in the previous screen on the CMSAuthentication page enter the information required to log on to CMS as an administrator
The following information is required
24
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
Table 8
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 Thisgroup name is filtered as the default when adding a user in Planning andConsolidation Administration Use a comma ( ) to separate multiple names
12 After entering the CMS administrator authentication details choose Next
13 From the Service type accounts page enter service-level account user IDs and passwords See Service-LevelAccounts [page 15]
14 After defining the IDs and passwords choose Next
15 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 chooseNext
16 Specify the location and name of AntiXssLibrarydll See Installing the Anti-Cross Site ScriptingLibrary [page 23]
Choose Next
17 Select destination folders for Programs and Data The Data files include Webfolders and FileDB (publishedreports) and should be installed on a separate drive in a production environment This recommendation reducesthe hard disk IO time and helps to speed up SQL commands
Accept the defaults or make your selections then choose Next
18 Select the default values for the Web client The values are used to determine the default language and regionfor the Web client when you connect to it You can change the values in the Planning and Consolidation ServerManager
19 The installation process takes a few moments When it is complete choose Exit
20 A prompt is displayed to restart your computer Select OK to restart
21 Perform the steps in After Installing Planning and Consolidation Servers [page 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 avariety of ways and configure the servers as a Network Load Balancing (NLB) environment
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 25
The recommended Planning and Consolidation practice is to assign resources using a round robin approach for loadbalancing
You can install the SQL OLAP and FileShare types remotely from the application server You need to performadditional server installations if you have multiple application servers
Installing each Planning and Consolidation application server in a multiserver (NLB) configuration is identical to theprocedure 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 Balancingenvironment With this option there is an additional choice to Include sample environment (required on only oneof the application servers) This is because when you install the application server it connects to the databaseserver and creates the sample environment (EnvironmentShell) Installing the sample environment is requiredon 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
26
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
3 After Installing Planning and ConsolidationServers
31 Post-Installation Steps
Procedure
Perform these steps after installing the Planning and Consolidation servers for new installations of Planning andConsolidation
1 Connect your Planning and Consolidation system to Solution Manager Diagnostics (SMD) to allow support staffto identify analyze and resolve problems with your application See Connecting to Solution ManagerDiagnostics [page 28]
2 Configure the Planning and Consolidation NET and application server to ensure that it and its related servicesfunction properly and reliably For more information see Configuring the Planning and Consolidation NETApplication Server [page 29]
3 Optional configuration steps [page 29]
1 To ensure proper functioning of the Management Console create an SQL user and modify the System DSNand 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 loggingfor ODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default WebSite [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory canaccess the Management Console with whatever rights they have been granted on the server Forinformation about removing default access and creating a group that can access the console see RemovingDefault Access to the Console [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommendthat you only grant Management Console access to system administrators Planning and Consolidationusers should not have any access For more information see Management Console AccessControl [page 33]
6 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
4 Take the following steps to set up security
If you are defining security and application structure continue with step 5
If you want to designate someone other than the system administrator to manage security and applicationstructure log on to EnvironmentShell designate a user as a Primary Administrator
This user must have Administration ndash Environment and Security ‒ Define User task rights so that he or shecan 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 SeeInstalling the Administration Client [page 37]
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 27
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 taskprofiles 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 mustcomplete this step since there is no access to dimensions or members)
NoteTo allow users to request and query large amounts of data you can edit the metabasexml file located at CWindowssystem32inetsrv Set the following parameters to the stated values
ASPBUFFERINGLIMIT = 10485760
MAXREQUESTENTITYALLOWED = 10485760
32 Connecting to Solution Manager Diagnostics
NoteYou only need to perform the steps in this section if you have a SAP Solution Manager licence
The diagnostics functions in SAP Solution Manager allow identification analysis and resolution of problems Thisprocedure 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 areinstalled
NoteInstallation files for Diagnostics Agent are available on Service Marketplace by navigating to SupportPackages and Patches mdash Entry by Application Group SAP Technology Components SAP SOLUTIONMANAGER SAP SOLUTION MANAGER 70 EHP 1 Entry by Component Agents for managed systemsDIAGNOSTICS AGENT 711
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 whereMicrosoft 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
28
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
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 ServiceMarketplace at servicesapcom~sapidb011000358700000074392009E and follow the chapters that applyto Planning and Consolidation
33 Configuring the Planning and Consolidation NETApplication Servers
Procedure
Modifying machineconfig Files
To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock occurrences that wouldcause the application server to ldquosleeprdquo and not process anymore you can modify the machineconfig file whichresides in the WINDOWSMicrosoftNETFramework64v4030319Config directory
1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to specifywhether to automatically configure settings to achieve optimal performance based on the machineconfiguration You can set this attribute to True or False
For more information see msdnmicrosoftcomen-uslibrary7w2sway1aspx
2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the Planning andConsolidation application) or Machineconfig (for all applications including Planning and Consolidation) toensure the validationKey and decryptionKey keys have the same value on all application servers Thisway when the authentication cookie is checked the authentication ticket used on one server can still be validon another server
For more information and sample Visual Basic code for generating random key values seemsdnmicrosoftcomen-uslibraryms998288aspxpaght000007_webfarmdeploymentconsiderationsand msdnmicrosoftcomen-uslibraryms998310aspx
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 DSNand 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 forODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory can accessthe Management Console with whatever rights they have been granted on the server For information about
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 29
removing default access and creating a group that can access the console see Removing Default Access to theConsole [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommend thatyou only grant Management Console access to system administrators Planning and Consolidation users shouldnot have any access For more information see Management Console Access Control [page 33]
6 Configure the use of SSL in Planning and Consolidation See Configuring Planning and Consolidation to useSSL [page 34]
7 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
8 Configure Microsoft SQL Server Reporting Services to use SSL See Configuring MS SQL Server ReportingServices to use SSL [page 36]
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 databaserole 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 optionto use ODBC Logging Enter the following values
DSN is BPC_ManagementDSN Table is BPCLog The Microsoft SQL Server Username and Password
5 Restart IIS
NoteWithout these updates the Management Console does work but some functionality (specifically User Activityand Service Status) does not work as expected
Should you need to uninstall Planning and Consolidation we recommend that you reset the Active Log Formatfield in IIS to W3C Extended Log File Format
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
30
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
Prerequisites
ODBC logging has been configured according to the Microsoft Knowledge Base article 245243 How to configureODBC 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 inApplicationHostconfig as shown here
ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0logFormat=Custom gtUse 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-00AA006111E0appcmd 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 articlespecified in the Prerequisites section Configure these settings in the ltodbcLogginggt node underltsystemwebServergt
Exampleltlocation path=Default Web SitegtltsystemwebServergtltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog userName=Usernamepassword=mypassword gtltsystemwebServergtltlocationgt
Use the following AppCmds to configure these attributes for the default Web site
appcmd set config Default Web Site sectionodbcLogging dataSourceBPC_ManagementDSN commitappHostappcmd set config Default Web Site sectionodbcLogging tableNameBPCLog commitappHostappcmd set config Default Web Site sectionodbcLogging userNameUsername commitappHostappcmd set config Default Web Site sectionodbcLogging passwordmypassword commitappHost
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 31
NoteYou cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must use the SQL ServerODBC driver For more information see the Microsoft Knowledge Base article 931202 The requirements for usingthe ODBC logging feature in IIS
343 Setting Up an ODBC Data Source in Windows Server2008 2008 R2 2012 or 2012 R2
Procedure
This procedure describes how to set up an ODBC data source for the Management Console in Windows Server 20082008 R2 2012 or 2012 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
NoteIf you have chosen SAP BusinessObjects User Management System in the installation screen you do not needto remove or configure access because the Management Console service always runs with the System Admin IDaccount which is a member of the Administrators group
Procedure
To remove default access to the Management Console and create a group that does have access to the console usethe procedure described below
32
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
NoteCreate your Management Console administrative group either on the server that hosts the Management Consoleor 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
NoteAlternatively you can perform analogous steps in Active Directory
3 In the Groups context menu choose New Group
4 Enter data as required Click Create
5 In the Computer Management dialog box choose Services and Applications Internet InformationServices 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 objectand all child objects Include these with entries explicitly defined here checkbox
NoteThis step is a necessary precursor to the completion of this procedure
10 In the Security dialog box click Copy to ensure that the System group retains its privileges
11 Remove access to the Management Console from all groups that should not have it
12 Choose Authentication in the center pane then disable Windows authentication
Result
Users who have not been granted access to the Management Console can still open the Management Console Webpage but it contains no data or menu options This does not affect the access that a user would otherwise have toPlanning and Consolidation
345 Management Console Access Control
After establishing the Management Console group you can add users or groups to it For more information aboutcreating this group see Removing Default Access to the Console [page 32] Their rights in Active Directory determinewhat they can access in the Console
By default any member of the Administrators Active Directory group on the application server or domain has fullaccess to all of the features of the Console except the Planning and Consolidation logging area Access to Planningand Consolidation logging is controlled within the Planning and Consolidation Administration Client task securityThe user must be granted View system logs task privileges For more information see the SAP Library Planning and
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 33
Consolidation Administrators Guide in servicesapcominstguidesepm-bpc 100 version for the Microsoftplatform
Your IT policy determines whether you grant access by group or user You may wish to create several levels of Consoleusers (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 describedin this table
Table 9
Privilege Rights Management Area
Task Manager and Kill Process Administrators group on application server or domain
Performance Monitor Counters Administrators group on application server or domain
Power Users group on application server or domain
Performance Monitor Users group on application server
Microsoft Analysis Services performance monitoring Administrators group on application server or domain
Microsoft SQL Server Monitoring (performance counters andstatistics)
Administrators group on application server or domain
346 Configuring Planning and Consolidation to use SSL
Procedure
Creating a Certificate for the Server
During the handshake phase of the SSL communication the server must send its certificate to the client The clientthen uses the certificate to encrypt information and send it back to the server
The procedure below describes how to create a self-signed certificate for the server
RecommendationWe recommend that you limit the use of self-signed certificates to testing only For a productive system you shouldobtain a certificate signed by a well-known certification authority (CA)
1 Start the Internet Information Services (IIS) Manager To do that go to Start All Programs AdministrativeTools Internet Information Services (IIS) Manager
2 In the Connections panel on the left-hand side select the server node and then choose Server Certificates
3 In the Actions panel on the right hand side choose the Create Self-Signed Certificate action
4 Enter the name that you want the certificate to be identified by for example MyTestSSLCertificate
IIS generates a new SSL certificate for you that has one yearrsquos expiry lease The certificate is issued to the local servername
Binding the Certificate to the Web Site
The procedure below describes how to bind the certificate to the web site for which SSL connections must be used
1 In the Connections panel select the web site node
2 In the Actions panel choose Bindings
34
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
3 In the Site Bindings dialog that appears choose the Add button to create a new binding
4 Configure the parameters as follows
Type = https IP Address = [1] - this is a shorthand expression for the local server name
Port = 443 - this is the default SSL port
SSL Certificate = enter your newly created certificate name
5 Choose OK to create the new binding and then close the Site Bindings dialog
6 Restart the IIS processes To do this choose Restart from the Actions panel
7 In the middle panel under the IIS section choose SSL Settings
8 In the SSL Settings screen select the Require SSL checkbox
9 In the Actions panel choose to Apply these settings
To test the SSL connection in the Actions panel choose the Browse [1] 443 (https) link
347 Using Client Certificates
To enable the use of client certificates in Planning and Consolidation you must follow several manual steps
NotePlanning and Consolidation supports client certificate authentication in Windows Authentication Mode butdoes 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 technetmicrosoftcomen-uslibrarycc753810aspx
For more information about configuring the client certificate mapping authentication see technetmicrosoftcomen-uslibrarycc732996(WS10)aspx
When you create the client certificates you can set the type of certificate in the SSL Settings screen in InternetInformation Services (IIS) Manager
Procedure
1 Set the options for client certificates
1 In the IIS Manager select the web site where you installed Planning and Consolidation
2 Choose SSL Settings
3 In the Client certificates section select the Accept client certificates option
This option allows you to use a client certificate or username and password (Basic authentication) toconnect 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 theManagementConsole home page
3 Double-click Authentication and enable Anonymous Authentication
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 35
4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way asin step 3
5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the sameway 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
348 Configuring MS SQL Server Reporting Services to useSSL
Procedure
The procedure below describes how to configure the use of SSL in Microsoft SQL Server Reporting Services
NoteReporting Services does not provide functionalities for generating requesting or installing a certificate Theserver certificates that you want to use for configuring SSL must have already been installed on your computer
1 Open the Reporting Services Configuration Manager program To do this open the Windows Start menu andnavigate to All Programs Microsoft SQL Server ltversiongt Configuration Tools Reporting ServicesConfiguration Manager
2 In the Connect panel on the left-hand side select the Web Service URL option to open all the Report Server webservice parameters
3 Configure the parameters as follows
SSL Certificate = the name of the certificate that you want to use
SSL Port = 4434 Choose Apply to confirm the changes
5 In the Connect panel choose Report Manager URL to open the list of parameters that link Reporting Servicesto IIS
6 Choose Advanced to add your new SSL web URL
7 In the section Multiple SSL Identities for Report Manager choose Add Configure the parameters as follows
IP Address = (All IPv4) SSL Port = 443 Certificate = the name of your SSL certificate
8 To test the configuration click the URL that appears under the Report manager Site Identification section
36
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
4 Installing Planning and ConsolidationAdministration Client and the SAPBusinessObjects EPM solutions Add-in forMicrosoft Office
The installation of the Planning and Consolidation Administration Client allows administrators to build and maintainPlanning and Consolidation environments and models and administer security
All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions add-in forMicrosoft 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 valueof the Planning and Consolidation client to prompt for user name and password Otherwise the Planning andConsolidation Start Page does not display
41 Installing the Administration Client
Prerequisites
NoteFor a definitive list of system requirements see the Product Availability Matrix on SAP Service Marketplace atservicesapcompam Search on Planning and Consolidation
The following list describes the minimum software requirements
Microsoft Internet Explorer 70 80 90 or 10
Microsoft Office 2003 2007 2010 or 2012
NET Framework 20 or higher (install any required NET Framework Hotfixes by referring tosupportmicrosoftcomkb)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 37
NoteWe recommend that you install all of the latest Microsoft Windows hotfixes prior to installing the Administrationclient For information about which hotfixes to install see updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us
Procedure
The 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 ltPC_serverportgtsapbpcweb
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 mustdownload the most recent version of the full setup (EPM Add-inexe) from the Service Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPCInstallation folder
Individual users can install the EPM add-in on their own machines by going to the Planning and Consolidation Homepage 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 upthe 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
38
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
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 toperform the upgrade If Client Auto Update is not enabled and a newer version is detected clients must be installedmanually 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 andpassword in the Admin ID and Admin password fields respectively The Admin ID should be a member of thelocal administrators group on all the computers running the auto update This setting is not needed if all usershave 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 Thisoption is stored in the user preferences and may also be turned on or off using the User Optionshellip menu itemIf 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 toinstall 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 installit 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 servicesapcom
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 versionand policy information For a support package these files are
EPM Addin Support Package ltSP versiongtmsp EPM Addin Support Package ltSP versiongtxmlFor a patch these files are
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 (WebsrvrWebBPCInstallation)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 39
You can set a different update policy for each package listed
ExampleThe following table illustrates some possible situations assuming that you have installed the first full version(V1)
Table 10
Available maintenancepackages
V2-user update
V3-force update
V4-force update
V5-user update
V5-user update V5-user update
V6-auto update
V7-force update
Minimum RequiredVersion
V4 V4 V7
Notification A prompt tells the user toinstall maintenancepackage V4 using theForced Update behavior
If User Update is enabledthe prompt informs theuser that maintenancepackage V5 is available
A prompt tells the user toinstall maintenancepackage V7 using theForced Update behavior
New Version V4 V4 or V5 V7
If you change the update policy for any package click Update to complete the change
40
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
5 Connection Issues
You may experience connection problems with ports the proxy server or programs and settings that interact withthese components If you have any issues related to connection review the following recommendations andtroubleshooting tips
51 Checking for Open Ports
You must ensure that all required ports are open for inboundoutbound traffic By default Planning andConsolidation requires that Ports 80 (used by http) and 1433 and 2383 (used by SQL Server 2008) are open Totest whether the required ports are open go to a command prompt and enter the Telnet serveripaddress and portFor example Telnet 431181836 80 If the system returns a blank command window the port is open If it returnsa message stating that it is unable to connect the port is not open
NoteYou can use the following site to scan for the normal ports It allows you to manually enter a port number to test
wwwmyserverorgportsniffasp
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 Planningand Consolidation server as an exception You can do this at the client level ( Internet Explorer ToolsInternet 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 fullyqualified 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 Consolidationauthentication Do not use authentication on the proxy server The system synchronizes the user name andpassword on the remote server with the local user name and password
SAP Business Planning and Consolidation 100Connection Issues
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 41
NoteFor more information about setting up an ISA proxy server contact SAP Support to request a copy of Setting upISA Proxy Server White Paper For more information about Business Planning and Consolidation firewall portssee SAP Note 1505250
Internet Explorer Settings Issues
Internet Explorer settings must be set correctly to prevent errors and problems when you attempt to access thePlanning 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 insertthe IP address or fully qualified server name of the Planning and Consolidation server as an exception bychoosing 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
42
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Connection Issues
6 Installing Planning and Consolidation withTwo Active Directory Domains
To set up a Planning and Consolidation 10 application server in a hosted environment and use your own domainusers follow this procedure In general you install Planning and Consolidation on the host domain use the hostdomain account and assign it to the Planning and Consolidation users SysAdmin Admin and Users Then you acceptone 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 andpassword 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 topromote 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 privilegefor the Planning and Consolidation server
5 Install Planning and Consolidation and assign your domain account either to the three Planning andConsolidation administrative users SysAdmin Admin and Users or to only one of the three Planning andConsolidation administrative users and to three of your users Be sure you use your own user account ratherthan host domain users
Planning and Consolidation impersonation can then access your domain from the host environment becauseit has the privilege of your domain account
SAP Business Planning and Consolidation 100Installing Planning and Consolidation with Two Active Directory Domains
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 43
7 Installing Planning and Consolidation in aTerminal Services or Citrix ServerDeployment
This section describes best practices and instructions for installing Planning and Consolidation in a Terminal Servicesor Citrix Server deployment
71 Terminal Services Home Directories
We recommend using Terminal Server home directories rather than using the userrsquos profile directory The profiledirectory downloads a minimal amount of information about the dimensions of the environment you are logging onto and may be as large as 2 MB per user The profile directory is on the system drive and has limited space Byspecifying 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 individualserver 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 clientserver (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
44
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
Procedure
The following steps outline how to install the Planning and Consolidation clients in a Terminal Services (TS) or CitrixServer deployment
1 Make sure the Terminal Services or Citrix Server machine has the system requirements installed
2 Log on to the Terminal Services or Citrix Server machine with a user ID that has the rights to install on thatserver
3 At a command prompt enter Change userinstall
4 Open a browser and connect to the URL ltPC_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_MSBPCAdminMainexe
74 Creating a Shortcut to the Launch Page
Procedure
If you use published desktops instead of published applications the Planning and Consolidation desktop file (whichis installed on the current userrsquos desktop) must be moved to the All UsersDesktop folder
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 45
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 SQLServer 2012 support the remote modification of SSIS packages Planning and Consolidation also supports theremote 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 whichyou want to modify SSIS packages
These custom tasks reference dlls that connect to the database server and perform certain validation when usersset up the parameters of each task All the custom task reference components must also be installed in the machineon which you want to modify SSIS packages
We provide a program that registers all the reference components of the custom tasks This section explains theinstallation 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 ndash This folder contains all the dlls that should be installed on the machine There are Planning andConsolidation platform components and all of the Data Manager custom task files
Config folder ndash This folder contains only one file named Filelistxml and lists all of the files that should be installedIf you need to add or remove certain components from the installation you can modify this xml file
OSoftSetupexe ndash This is the main executable file to run the installation package
NoteIf you are not installing SSIS Custom Tasks on your client machine ndash specifically a machine other than the Planningand Consolidation application server ndash you must first install OSoftSSIS2008_Client or OSoftSSIS2012_Client onthe client machine followed by the SQL Server version If you want to use SQL 2008 Tasks under the SQL 2012environment you must install OSoftSSIS2008_Client on the application server For detailed information see SAPNote 1707410 You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package byextracting OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPCInstallation folder on the Planning and Consolidation server To modify SSIS packages on the Planning andConsolidation application server you need to install OSoftSSIS2008_Client or OSoftSSIS2012_Client for creatinga COM+ application For more information see Before You Modify the SSIS Packages [page 49] and Setup ofa COM+ Application on the Application Server [page 50]
Bin folder
This folder contains the following components
46
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Table 11
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012respectively
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
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 47
Name Remark
BPCWriteBackdll
InteropDTSdll
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 addmore components to the installation package you can copy the new components into the Bin folder and add theproper xml tags in FileListxml You need to enter information for the following tags
RegistType ndash This is the registration information of the component You can enter the following values
RegAsm ndash For NET component
48
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Regsvr32 ndash For VB6 component
Gacutil ndash For NET Framework component that should be registered into Global Assembly Cache
FileName ndash Component file name
OSoftSetupexe
This is the executable file to run the SSIS installation package Double-click the file to start the installation You needto enter information for the following fields
Set SQL server
Specify the SQL server name If your SQL Server has an instance specify the instance name
NoteIf you installed the OSoftSSIS2008_Client or OSoftSSIS2012_Client on the application server the SQL servername is automatically disabled
Set server credential
This is the credential name of the COM+ package component Enter the user ID and password that can accessyour SQL Server This should be either the System Admin ID or Admin ID that was registered as a COM+ userwhen 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 ifyou 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 packagesremotely This is also true for the application server that has SSIS installed The Planning and ConsolidationData Manager has the following custom tasks
Table 12
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008and 2012 respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and2012 respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012respectively
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 49
Name Remark
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and2012 respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008and 2012 respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL2008 and 2012 respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and2012 respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012respectively
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
ltdrivegtWebsrvrbin2 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 FilesMicrosoft SQLServer paste all files into the CProgram Files (x86)Microsoft SQL Server100DTSTasksfolder
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
50
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Typographic Conventions
Table 13
Example Description
lt gt Angle brackets indicate that you replace these words or characters with appropriate entries tomake entries in the system for example Enter your ltUser Namegt
File Save Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
Example Textual cross-references to an internet address for example wwwsapcom
example Quicklinks added to the internet address of a homepage to enable quick access to specificcontent 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 titlespushbutton 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 namesof installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transactioncodes database table names and key concepts of a programming language when they aresurrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
SAP Business Planning and Consolidation 100Typographic Conventions
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 51
52
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
wwwsapcom
Material Number
- SAP Business 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 2008 R2 2012 or 2012 R2
- 344 Removing Default Access to the Console
- 345 Management Console Access Control
- 346 Configuring Planning and Consolidation to use SSL
- 347 Using Client Certificates
- 348 Configuring MS SQL Server Reporting Services to use SSL
-
- 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
-
and can create remove backup and restore OLAP and SQL databases The system administrator should be amember 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 createsubdirectory access on the FileShare server readwrite metadata and application set database data in OLAPand can create and remove tables in SQL The Administrator should be a member of the domain users groupand 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 theservers has write access to FileShare data and can read metadata and data in OLAP and SQL The User IDmust 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 isinstalled you can change these settings using the Server Manager
NoteWhen defining server names the name refers to the NetBIOS name IP address and fully qualified domain names(FQDN)
Standard Settings
Standard settings are typically used for a single-server environment The following table describes each setting
Table 5
Server Option Value Description
SQL Database server name The name of the SQL DB server
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 computername
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
Table 6
Server Option Value Description
SQL Server Name The name of the SQL DB server Defaults to the local server
Instance name The SQL instance name If left blank the default instance is used
16
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
Server Option Value Description
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 computername
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 forhttp and 443 is the default for https
Authentication type Note If you have chosen SAP BusinessObjects User Management System in theinstallation screen Authentication type does not appear in Advanced settings (asthat IIS authentication type is Anonymous in CMS mode)
Windows or Kerberos The default is Windows If you change this value fromWindows to Kerberos you must make some additional changes
See the Kerberos authentication settings section in the SAP Library ServerManager Guide on servicesapcominstguidesEPM-BPC 100 for theMicrosoft Platform
Scheduler Server Name The name of the server used for scheduling usually the application server forexample GMPV50072862B If you have multiple application servers select theappropriate one
NoteIf the primary server stops working you must manually configure yourapplication 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 theoperating system IIS SQL server analysis services ADOMDNET and MSXML This section provides guidance on
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 17
installing each component For specific versions required see Prerequisites [page 11] and the Product AvailabilityMatrix on the SAP Service Marketplace at servicesapcompam Search on Planning and Consolidation
NoteTo ensure a successful installation you must install the software in the order listed in this procedure
Check all third-party infrastructure services to ensure that they are functioning and that their authenticationmodels 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 itsown 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 applicationserver before you start the installation You can find the UMC installation package (UMCexe) on the Planningand Consolidation CD in a folder called UMC_100_INSTALLER When you run the installation package the wizardguides 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 andConsolidation)
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 multiserverconfiguration See Installing the Operating System [page 19]
3 Install the latest service pack for your operating system To install this service pack go towwwmicrosoftcom
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 SQLServer [page 19]
6 From your SQL Server media install Analysis Services Enterprise Edition and its required service packs and hotfixes See Installing Analysis Services [page 23]
7 On your application server install ADOMDNET The Planning and Consolidation zip file contains theADOMDNET 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 followinglocation BPC SetupServermsxmlmsi
18
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
9 On your application server install Microsoft Visual C++ 2010 SP1 Redistributable Package (x64)
The Microsoft Visual C++ 2010 SP1 Redistributable Package (x64) installation package is contained in thePlanning and Consolidation zip file at the following location BPC SetupServervcredist_x64exe
NoteThe version of vcredist_x64exe in BPC SetupServer has been updated to 10040219 If you have aprevious 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 wwwmicrosoftcomdownloadsendetailsaspxFamilyID=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 Marketplaceat servicesapcompam Search on Planning and Consolidation
Business Planning and Consolidation can support all servers with an operating system in any language
NoteCurrently Business Planning and Consolidation does not support an operating system in bi-directionallanguages such as Hebrew
Procedure
If you are installing IIS 70 75 80 or 85 you must enable the following features
Enable Basic Authentication and Windows Authentication these are not installed by default
Install IIS 6 Metabase Compatibility role
Business Planning and Consolidation uses the ADSI provider to handle IIS administration such as virtualdirectory and security but IIS 7 does not install the ADSI provider by default
273 Installing the SQL Server
Prerequisites
During the installation procedure you have the opportunity to specify the location of the EnvironmentShell databasefile Check that it is possible to access EnvironmentShell from the location where you intend to install the SQL serverIf it is not possible for port access reasons (DMZ WORKGROUP or nontrusted domain authentication failures) copyEnvironmentShell to a location on the SQL server (for example CEnvironmentShelldb10) You specify thislocation on the Server Information page by choosing Server Information Advanced Options Local Path forEnvironmentShell DB
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 19
Procedure
This section describes the general steps for installing the SQL Server component options and considerations wheninstalling 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
NoteIf you encounter a 500 HTTP Error when trying to connect to the Planning and Consolidation Web Client referto Microsoft Support articles 2520479 and 2468871 for assistance
To reinforce security we recommend that you install the SQL server and SSAS components to a nondefaultinstance 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 Optionssection below then choose Next
4 Review disc space requirements then choose Next
5 In Server Configuration Perform the following actions
1 In the Service Accounts tab enter a Planning and Consolidation sysadmin account for the SQL ServerDatabase Engine and the SQL Server Analysis services This is required so that the Planning andConsolidation sysadmin can create and process the Planning and Consolidation database because theMicrosoft SQL server tries to back up or restore database with the privileged account This account is alsorequired 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 differentdomain 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 theapplication server and the account requires the folder access privilege for the application server
To ensure that you have the complete access privileges we recommend the Planning and Consolidationsysadmin 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 touse a restrictive SQL ID that works with the drill-through feature If you must restrict SQL authentication forsecurity 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 installationprogram
20
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
8 Choose Install to begin the installation with the options you have set
SQL Server Component Options
For Single-Machine Installations
Install the following components from the Feature Selection screen
Database Engine Services
Analysis Services
Integration Service which is listed as one of the Shared Features
For Multiple Machine Installations
For multiple machine installations install the following components on each server
Table 7
Server Component What to Install
SQL Server Database Engine Services
SSAS Server Analysis Services
Application Server The following Shared Features
Client Tools Connectivity
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 Server2008 R2 and SQL Server 2012
Process Dimension
It is now possible to process a dimension with multiple selections At processing time the process dimension modulemakes changed or added information for each dimension and process for all selected dimensions and cubes inparallel
Optimize Model
If there are custom partitions for a FACT partition in the OLAP database an optimization module can process custompartitions in parallel when Full or Incremental Optimize is performed However if a full optimize is performed withthe 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 parallelbecause 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 applicationserver and application set databases
NoteSetting the SQL isolation level to be Read Committed Snapshot mode for a database can only be done once andcannot be reversed
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 21
Real Time MOLAP
You can set the OLAP storage model of the write-back partition to be MOLAP (Multidimensional OLAP) This settingremains 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 asfollows
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 Servertrade20052008 which you can download from wwwmicrosoftcom (search on ldquoTable Partitioningrdquo to find all relevantarticles)
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 Thebrowser 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 localhostand external network interface machine
3 If you want to use IP1 which indicates Server IP set Enabled to Yes and specify the TCP Port as desired
4 Delete 0 from TCP Dynamic Ports Set IPAll - TCP Ports as desired (for example 1533)
RecommendationWe do not recommend using dynamic ports
In an SQL server the default instance has a listener which listens on a fixed port (TCP port 1433)However for the named instance the port on which the SQL server listens is random and dynamicallyselected when the named instance of the SQL server starts This recommendation prevents any conflictproblems
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 Setthe 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 thatthe user identified as the Log on as user has the sysadmin SQL Server role defined under Server Roles in theSQL Server Management Studio This is required so Analysis Services can process the SQL Server
From SQL Server Management Studio do the following tasks
22
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
1 If you want to use a port with a named instance select the server type Analysis Services select the servername (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 ServerProperties window displays which shows all configurable properties
3 For enhanced security change the default value to your port number (for example 2724) This means thatyou use a fixed port as for the SQL Server option Then choose OK
NoteWe do not support a nondefault port with the default instance in this release If you want to use the defaultinstance do not change the port number
Restart SQL and OLAP
Confirm that the installation has completed successfully by checking that there are no installation relatedproblems on the event viewer You can now install Planning and Consolidation
274 Installing Analysis Services
Procedure
After you install SQL Server and its required service packs and hotfixes you must install SQL Server Analysis Servicesand its required service packs and hotfixes
NoteIf you have migrated your Analysis Services repository to the SQL Server back up the database that contains therepository before installing this release
To install Analysis Services for SQL Server 2008 SQL Server 2008 R2 or SQL Server 2012 follow the steps andguidelines in technetmicrosoftcomen-uslibraryms143219aspx
To avoid slow performance when a user has more than six OLAP databases follow the steps and guidelines in thePerformance Guide for SQL 2008 at wwwmicrosoftcomdownloadsdetailsaspxFamilyID=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 tohave it available for the Planning and Consolidation installation program
1 Download the Anti-Cross Site Scripting Library file AntiXSSLibraryDLL from the Microsoft Web site atwwwmicrosoftcomdownloadendetailsaspxid=28589
2 Save the extracted file locally
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 23
When you install Planning and Consolidation Server a step in the process requires you to identify the path toAntiXssLibrarydll
28 Installing on a Single Server
When you install all Planning and Consolidation server components on a single server you should consider thefollowing 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 theuncompressed 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 Log on to the server with a local server user ID or domain user ID For more information see Logging on toservers [page 14]
3 Make sure all prerequisite software is installed on the server For more information see Installing thePrerequisites [page 17]
4 Obtain SAP Planning and Consolidation archive from the Downloads SAP Installations amp Upgrades areaof SAP Service Marketplace
5 Extract the files from the archive Go to the BPC Setup folder and run the StartUpexe file
6 From the Server Install screen select Install the Planning and Consolidation server
7 From the Welcome screen choose Next
8 From the License Agreement page choose I accept the terms of the license agreement then choose Next
9 From the Installation Method page accept the default Single machine enter a system ID for the systemlandscape directory (SLD) and choose Next
NoteEntering a system ID of the SLD is only required if you have a SAP Solution Manager license If you do nothave a SAP Solution Manager license you can leave this field empty
10 From the Authentication Method page choose the desired authentication method and choose Next
11 If you have chosen SAP BusinessObjects User Management System in the previous screen on the CMSAuthentication page enter the information required to log on to CMS as an administrator
The following information is required
24
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
Table 8
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 Thisgroup name is filtered as the default when adding a user in Planning andConsolidation Administration Use a comma ( ) to separate multiple names
12 After entering the CMS administrator authentication details choose Next
13 From the Service type accounts page enter service-level account user IDs and passwords See Service-LevelAccounts [page 15]
14 After defining the IDs and passwords choose Next
15 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 chooseNext
16 Specify the location and name of AntiXssLibrarydll See Installing the Anti-Cross Site ScriptingLibrary [page 23]
Choose Next
17 Select destination folders for Programs and Data The Data files include Webfolders and FileDB (publishedreports) and should be installed on a separate drive in a production environment This recommendation reducesthe hard disk IO time and helps to speed up SQL commands
Accept the defaults or make your selections then choose Next
18 Select the default values for the Web client The values are used to determine the default language and regionfor the Web client when you connect to it You can change the values in the Planning and Consolidation ServerManager
19 The installation process takes a few moments When it is complete choose Exit
20 A prompt is displayed to restart your computer Select OK to restart
21 Perform the steps in After Installing Planning and Consolidation Servers [page 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 avariety of ways and configure the servers as a Network Load Balancing (NLB) environment
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 25
The recommended Planning and Consolidation practice is to assign resources using a round robin approach for loadbalancing
You can install the SQL OLAP and FileShare types remotely from the application server You need to performadditional server installations if you have multiple application servers
Installing each Planning and Consolidation application server in a multiserver (NLB) configuration is identical to theprocedure 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 Balancingenvironment With this option there is an additional choice to Include sample environment (required on only oneof the application servers) This is because when you install the application server it connects to the databaseserver and creates the sample environment (EnvironmentShell) Installing the sample environment is requiredon 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
26
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
3 After Installing Planning and ConsolidationServers
31 Post-Installation Steps
Procedure
Perform these steps after installing the Planning and Consolidation servers for new installations of Planning andConsolidation
1 Connect your Planning and Consolidation system to Solution Manager Diagnostics (SMD) to allow support staffto identify analyze and resolve problems with your application See Connecting to Solution ManagerDiagnostics [page 28]
2 Configure the Planning and Consolidation NET and application server to ensure that it and its related servicesfunction properly and reliably For more information see Configuring the Planning and Consolidation NETApplication Server [page 29]
3 Optional configuration steps [page 29]
1 To ensure proper functioning of the Management Console create an SQL user and modify the System DSNand 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 loggingfor ODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default WebSite [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory canaccess the Management Console with whatever rights they have been granted on the server Forinformation about removing default access and creating a group that can access the console see RemovingDefault Access to the Console [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommendthat you only grant Management Console access to system administrators Planning and Consolidationusers should not have any access For more information see Management Console AccessControl [page 33]
6 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
4 Take the following steps to set up security
If you are defining security and application structure continue with step 5
If you want to designate someone other than the system administrator to manage security and applicationstructure log on to EnvironmentShell designate a user as a Primary Administrator
This user must have Administration ndash Environment and Security ‒ Define User task rights so that he or shecan 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 SeeInstalling the Administration Client [page 37]
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 27
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 taskprofiles 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 mustcomplete this step since there is no access to dimensions or members)
NoteTo allow users to request and query large amounts of data you can edit the metabasexml file located at CWindowssystem32inetsrv Set the following parameters to the stated values
ASPBUFFERINGLIMIT = 10485760
MAXREQUESTENTITYALLOWED = 10485760
32 Connecting to Solution Manager Diagnostics
NoteYou only need to perform the steps in this section if you have a SAP Solution Manager licence
The diagnostics functions in SAP Solution Manager allow identification analysis and resolution of problems Thisprocedure 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 areinstalled
NoteInstallation files for Diagnostics Agent are available on Service Marketplace by navigating to SupportPackages and Patches mdash Entry by Application Group SAP Technology Components SAP SOLUTIONMANAGER SAP SOLUTION MANAGER 70 EHP 1 Entry by Component Agents for managed systemsDIAGNOSTICS AGENT 711
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 whereMicrosoft 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
28
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
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 ServiceMarketplace at servicesapcom~sapidb011000358700000074392009E and follow the chapters that applyto Planning and Consolidation
33 Configuring the Planning and Consolidation NETApplication Servers
Procedure
Modifying machineconfig Files
To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock occurrences that wouldcause the application server to ldquosleeprdquo and not process anymore you can modify the machineconfig file whichresides in the WINDOWSMicrosoftNETFramework64v4030319Config directory
1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to specifywhether to automatically configure settings to achieve optimal performance based on the machineconfiguration You can set this attribute to True or False
For more information see msdnmicrosoftcomen-uslibrary7w2sway1aspx
2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the Planning andConsolidation application) or Machineconfig (for all applications including Planning and Consolidation) toensure the validationKey and decryptionKey keys have the same value on all application servers Thisway when the authentication cookie is checked the authentication ticket used on one server can still be validon another server
For more information and sample Visual Basic code for generating random key values seemsdnmicrosoftcomen-uslibraryms998288aspxpaght000007_webfarmdeploymentconsiderationsand msdnmicrosoftcomen-uslibraryms998310aspx
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 DSNand 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 forODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory can accessthe Management Console with whatever rights they have been granted on the server For information about
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 29
removing default access and creating a group that can access the console see Removing Default Access to theConsole [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommend thatyou only grant Management Console access to system administrators Planning and Consolidation users shouldnot have any access For more information see Management Console Access Control [page 33]
6 Configure the use of SSL in Planning and Consolidation See Configuring Planning and Consolidation to useSSL [page 34]
7 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
8 Configure Microsoft SQL Server Reporting Services to use SSL See Configuring MS SQL Server ReportingServices to use SSL [page 36]
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 databaserole 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 optionto use ODBC Logging Enter the following values
DSN is BPC_ManagementDSN Table is BPCLog The Microsoft SQL Server Username and Password
5 Restart IIS
NoteWithout these updates the Management Console does work but some functionality (specifically User Activityand Service Status) does not work as expected
Should you need to uninstall Planning and Consolidation we recommend that you reset the Active Log Formatfield in IIS to W3C Extended Log File Format
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
30
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
Prerequisites
ODBC logging has been configured according to the Microsoft Knowledge Base article 245243 How to configureODBC 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 inApplicationHostconfig as shown here
ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0logFormat=Custom gtUse 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-00AA006111E0appcmd 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 articlespecified in the Prerequisites section Configure these settings in the ltodbcLogginggt node underltsystemwebServergt
Exampleltlocation path=Default Web SitegtltsystemwebServergtltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog userName=Usernamepassword=mypassword gtltsystemwebServergtltlocationgt
Use the following AppCmds to configure these attributes for the default Web site
appcmd set config Default Web Site sectionodbcLogging dataSourceBPC_ManagementDSN commitappHostappcmd set config Default Web Site sectionodbcLogging tableNameBPCLog commitappHostappcmd set config Default Web Site sectionodbcLogging userNameUsername commitappHostappcmd set config Default Web Site sectionodbcLogging passwordmypassword commitappHost
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 31
NoteYou cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must use the SQL ServerODBC driver For more information see the Microsoft Knowledge Base article 931202 The requirements for usingthe ODBC logging feature in IIS
343 Setting Up an ODBC Data Source in Windows Server2008 2008 R2 2012 or 2012 R2
Procedure
This procedure describes how to set up an ODBC data source for the Management Console in Windows Server 20082008 R2 2012 or 2012 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
NoteIf you have chosen SAP BusinessObjects User Management System in the installation screen you do not needto remove or configure access because the Management Console service always runs with the System Admin IDaccount which is a member of the Administrators group
Procedure
To remove default access to the Management Console and create a group that does have access to the console usethe procedure described below
32
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
NoteCreate your Management Console administrative group either on the server that hosts the Management Consoleor 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
NoteAlternatively you can perform analogous steps in Active Directory
3 In the Groups context menu choose New Group
4 Enter data as required Click Create
5 In the Computer Management dialog box choose Services and Applications Internet InformationServices 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 objectand all child objects Include these with entries explicitly defined here checkbox
NoteThis step is a necessary precursor to the completion of this procedure
10 In the Security dialog box click Copy to ensure that the System group retains its privileges
11 Remove access to the Management Console from all groups that should not have it
12 Choose Authentication in the center pane then disable Windows authentication
Result
Users who have not been granted access to the Management Console can still open the Management Console Webpage but it contains no data or menu options This does not affect the access that a user would otherwise have toPlanning and Consolidation
345 Management Console Access Control
After establishing the Management Console group you can add users or groups to it For more information aboutcreating this group see Removing Default Access to the Console [page 32] Their rights in Active Directory determinewhat they can access in the Console
By default any member of the Administrators Active Directory group on the application server or domain has fullaccess to all of the features of the Console except the Planning and Consolidation logging area Access to Planningand Consolidation logging is controlled within the Planning and Consolidation Administration Client task securityThe user must be granted View system logs task privileges For more information see the SAP Library Planning and
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 33
Consolidation Administrators Guide in servicesapcominstguidesepm-bpc 100 version for the Microsoftplatform
Your IT policy determines whether you grant access by group or user You may wish to create several levels of Consoleusers (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 describedin this table
Table 9
Privilege Rights Management Area
Task Manager and Kill Process Administrators group on application server or domain
Performance Monitor Counters Administrators group on application server or domain
Power Users group on application server or domain
Performance Monitor Users group on application server
Microsoft Analysis Services performance monitoring Administrators group on application server or domain
Microsoft SQL Server Monitoring (performance counters andstatistics)
Administrators group on application server or domain
346 Configuring Planning and Consolidation to use SSL
Procedure
Creating a Certificate for the Server
During the handshake phase of the SSL communication the server must send its certificate to the client The clientthen uses the certificate to encrypt information and send it back to the server
The procedure below describes how to create a self-signed certificate for the server
RecommendationWe recommend that you limit the use of self-signed certificates to testing only For a productive system you shouldobtain a certificate signed by a well-known certification authority (CA)
1 Start the Internet Information Services (IIS) Manager To do that go to Start All Programs AdministrativeTools Internet Information Services (IIS) Manager
2 In the Connections panel on the left-hand side select the server node and then choose Server Certificates
3 In the Actions panel on the right hand side choose the Create Self-Signed Certificate action
4 Enter the name that you want the certificate to be identified by for example MyTestSSLCertificate
IIS generates a new SSL certificate for you that has one yearrsquos expiry lease The certificate is issued to the local servername
Binding the Certificate to the Web Site
The procedure below describes how to bind the certificate to the web site for which SSL connections must be used
1 In the Connections panel select the web site node
2 In the Actions panel choose Bindings
34
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
3 In the Site Bindings dialog that appears choose the Add button to create a new binding
4 Configure the parameters as follows
Type = https IP Address = [1] - this is a shorthand expression for the local server name
Port = 443 - this is the default SSL port
SSL Certificate = enter your newly created certificate name
5 Choose OK to create the new binding and then close the Site Bindings dialog
6 Restart the IIS processes To do this choose Restart from the Actions panel
7 In the middle panel under the IIS section choose SSL Settings
8 In the SSL Settings screen select the Require SSL checkbox
9 In the Actions panel choose to Apply these settings
To test the SSL connection in the Actions panel choose the Browse [1] 443 (https) link
347 Using Client Certificates
To enable the use of client certificates in Planning and Consolidation you must follow several manual steps
NotePlanning and Consolidation supports client certificate authentication in Windows Authentication Mode butdoes 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 technetmicrosoftcomen-uslibrarycc753810aspx
For more information about configuring the client certificate mapping authentication see technetmicrosoftcomen-uslibrarycc732996(WS10)aspx
When you create the client certificates you can set the type of certificate in the SSL Settings screen in InternetInformation Services (IIS) Manager
Procedure
1 Set the options for client certificates
1 In the IIS Manager select the web site where you installed Planning and Consolidation
2 Choose SSL Settings
3 In the Client certificates section select the Accept client certificates option
This option allows you to use a client certificate or username and password (Basic authentication) toconnect 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 theManagementConsole home page
3 Double-click Authentication and enable Anonymous Authentication
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 35
4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way asin step 3
5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the sameway 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
348 Configuring MS SQL Server Reporting Services to useSSL
Procedure
The procedure below describes how to configure the use of SSL in Microsoft SQL Server Reporting Services
NoteReporting Services does not provide functionalities for generating requesting or installing a certificate Theserver certificates that you want to use for configuring SSL must have already been installed on your computer
1 Open the Reporting Services Configuration Manager program To do this open the Windows Start menu andnavigate to All Programs Microsoft SQL Server ltversiongt Configuration Tools Reporting ServicesConfiguration Manager
2 In the Connect panel on the left-hand side select the Web Service URL option to open all the Report Server webservice parameters
3 Configure the parameters as follows
SSL Certificate = the name of the certificate that you want to use
SSL Port = 4434 Choose Apply to confirm the changes
5 In the Connect panel choose Report Manager URL to open the list of parameters that link Reporting Servicesto IIS
6 Choose Advanced to add your new SSL web URL
7 In the section Multiple SSL Identities for Report Manager choose Add Configure the parameters as follows
IP Address = (All IPv4) SSL Port = 443 Certificate = the name of your SSL certificate
8 To test the configuration click the URL that appears under the Report manager Site Identification section
36
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
4 Installing Planning and ConsolidationAdministration Client and the SAPBusinessObjects EPM solutions Add-in forMicrosoft Office
The installation of the Planning and Consolidation Administration Client allows administrators to build and maintainPlanning and Consolidation environments and models and administer security
All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions add-in forMicrosoft 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 valueof the Planning and Consolidation client to prompt for user name and password Otherwise the Planning andConsolidation Start Page does not display
41 Installing the Administration Client
Prerequisites
NoteFor a definitive list of system requirements see the Product Availability Matrix on SAP Service Marketplace atservicesapcompam Search on Planning and Consolidation
The following list describes the minimum software requirements
Microsoft Internet Explorer 70 80 90 or 10
Microsoft Office 2003 2007 2010 or 2012
NET Framework 20 or higher (install any required NET Framework Hotfixes by referring tosupportmicrosoftcomkb)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 37
NoteWe recommend that you install all of the latest Microsoft Windows hotfixes prior to installing the Administrationclient For information about which hotfixes to install see updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us
Procedure
The 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 ltPC_serverportgtsapbpcweb
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 mustdownload the most recent version of the full setup (EPM Add-inexe) from the Service Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPCInstallation folder
Individual users can install the EPM add-in on their own machines by going to the Planning and Consolidation Homepage 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 upthe 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
38
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
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 toperform the upgrade If Client Auto Update is not enabled and a newer version is detected clients must be installedmanually 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 andpassword in the Admin ID and Admin password fields respectively The Admin ID should be a member of thelocal administrators group on all the computers running the auto update This setting is not needed if all usershave 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 Thisoption is stored in the user preferences and may also be turned on or off using the User Optionshellip menu itemIf 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 toinstall 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 installit 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 servicesapcom
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 versionand policy information For a support package these files are
EPM Addin Support Package ltSP versiongtmsp EPM Addin Support Package ltSP versiongtxmlFor a patch these files are
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 (WebsrvrWebBPCInstallation)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 39
You can set a different update policy for each package listed
ExampleThe following table illustrates some possible situations assuming that you have installed the first full version(V1)
Table 10
Available maintenancepackages
V2-user update
V3-force update
V4-force update
V5-user update
V5-user update V5-user update
V6-auto update
V7-force update
Minimum RequiredVersion
V4 V4 V7
Notification A prompt tells the user toinstall maintenancepackage V4 using theForced Update behavior
If User Update is enabledthe prompt informs theuser that maintenancepackage V5 is available
A prompt tells the user toinstall maintenancepackage V7 using theForced Update behavior
New Version V4 V4 or V5 V7
If you change the update policy for any package click Update to complete the change
40
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
5 Connection Issues
You may experience connection problems with ports the proxy server or programs and settings that interact withthese components If you have any issues related to connection review the following recommendations andtroubleshooting tips
51 Checking for Open Ports
You must ensure that all required ports are open for inboundoutbound traffic By default Planning andConsolidation requires that Ports 80 (used by http) and 1433 and 2383 (used by SQL Server 2008) are open Totest whether the required ports are open go to a command prompt and enter the Telnet serveripaddress and portFor example Telnet 431181836 80 If the system returns a blank command window the port is open If it returnsa message stating that it is unable to connect the port is not open
NoteYou can use the following site to scan for the normal ports It allows you to manually enter a port number to test
wwwmyserverorgportsniffasp
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 Planningand Consolidation server as an exception You can do this at the client level ( Internet Explorer ToolsInternet 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 fullyqualified 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 Consolidationauthentication Do not use authentication on the proxy server The system synchronizes the user name andpassword on the remote server with the local user name and password
SAP Business Planning and Consolidation 100Connection Issues
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 41
NoteFor more information about setting up an ISA proxy server contact SAP Support to request a copy of Setting upISA Proxy Server White Paper For more information about Business Planning and Consolidation firewall portssee SAP Note 1505250
Internet Explorer Settings Issues
Internet Explorer settings must be set correctly to prevent errors and problems when you attempt to access thePlanning 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 insertthe IP address or fully qualified server name of the Planning and Consolidation server as an exception bychoosing 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
42
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Connection Issues
6 Installing Planning and Consolidation withTwo Active Directory Domains
To set up a Planning and Consolidation 10 application server in a hosted environment and use your own domainusers follow this procedure In general you install Planning and Consolidation on the host domain use the hostdomain account and assign it to the Planning and Consolidation users SysAdmin Admin and Users Then you acceptone 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 andpassword 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 topromote 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 privilegefor the Planning and Consolidation server
5 Install Planning and Consolidation and assign your domain account either to the three Planning andConsolidation administrative users SysAdmin Admin and Users or to only one of the three Planning andConsolidation administrative users and to three of your users Be sure you use your own user account ratherthan host domain users
Planning and Consolidation impersonation can then access your domain from the host environment becauseit has the privilege of your domain account
SAP Business Planning and Consolidation 100Installing Planning and Consolidation with Two Active Directory Domains
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 43
7 Installing Planning and Consolidation in aTerminal Services or Citrix ServerDeployment
This section describes best practices and instructions for installing Planning and Consolidation in a Terminal Servicesor Citrix Server deployment
71 Terminal Services Home Directories
We recommend using Terminal Server home directories rather than using the userrsquos profile directory The profiledirectory downloads a minimal amount of information about the dimensions of the environment you are logging onto and may be as large as 2 MB per user The profile directory is on the system drive and has limited space Byspecifying 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 individualserver 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 clientserver (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
44
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
Procedure
The following steps outline how to install the Planning and Consolidation clients in a Terminal Services (TS) or CitrixServer deployment
1 Make sure the Terminal Services or Citrix Server machine has the system requirements installed
2 Log on to the Terminal Services or Citrix Server machine with a user ID that has the rights to install on thatserver
3 At a command prompt enter Change userinstall
4 Open a browser and connect to the URL ltPC_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_MSBPCAdminMainexe
74 Creating a Shortcut to the Launch Page
Procedure
If you use published desktops instead of published applications the Planning and Consolidation desktop file (whichis installed on the current userrsquos desktop) must be moved to the All UsersDesktop folder
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 45
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 SQLServer 2012 support the remote modification of SSIS packages Planning and Consolidation also supports theremote 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 whichyou want to modify SSIS packages
These custom tasks reference dlls that connect to the database server and perform certain validation when usersset up the parameters of each task All the custom task reference components must also be installed in the machineon which you want to modify SSIS packages
We provide a program that registers all the reference components of the custom tasks This section explains theinstallation 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 ndash This folder contains all the dlls that should be installed on the machine There are Planning andConsolidation platform components and all of the Data Manager custom task files
Config folder ndash This folder contains only one file named Filelistxml and lists all of the files that should be installedIf you need to add or remove certain components from the installation you can modify this xml file
OSoftSetupexe ndash This is the main executable file to run the installation package
NoteIf you are not installing SSIS Custom Tasks on your client machine ndash specifically a machine other than the Planningand Consolidation application server ndash you must first install OSoftSSIS2008_Client or OSoftSSIS2012_Client onthe client machine followed by the SQL Server version If you want to use SQL 2008 Tasks under the SQL 2012environment you must install OSoftSSIS2008_Client on the application server For detailed information see SAPNote 1707410 You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package byextracting OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPCInstallation folder on the Planning and Consolidation server To modify SSIS packages on the Planning andConsolidation application server you need to install OSoftSSIS2008_Client or OSoftSSIS2012_Client for creatinga COM+ application For more information see Before You Modify the SSIS Packages [page 49] and Setup ofa COM+ Application on the Application Server [page 50]
Bin folder
This folder contains the following components
46
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Table 11
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012respectively
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
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 47
Name Remark
BPCWriteBackdll
InteropDTSdll
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 addmore components to the installation package you can copy the new components into the Bin folder and add theproper xml tags in FileListxml You need to enter information for the following tags
RegistType ndash This is the registration information of the component You can enter the following values
RegAsm ndash For NET component
48
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Regsvr32 ndash For VB6 component
Gacutil ndash For NET Framework component that should be registered into Global Assembly Cache
FileName ndash Component file name
OSoftSetupexe
This is the executable file to run the SSIS installation package Double-click the file to start the installation You needto enter information for the following fields
Set SQL server
Specify the SQL server name If your SQL Server has an instance specify the instance name
NoteIf you installed the OSoftSSIS2008_Client or OSoftSSIS2012_Client on the application server the SQL servername is automatically disabled
Set server credential
This is the credential name of the COM+ package component Enter the user ID and password that can accessyour SQL Server This should be either the System Admin ID or Admin ID that was registered as a COM+ userwhen 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 ifyou 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 packagesremotely This is also true for the application server that has SSIS installed The Planning and ConsolidationData Manager has the following custom tasks
Table 12
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008and 2012 respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and2012 respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012respectively
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 49
Name Remark
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and2012 respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008and 2012 respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL2008 and 2012 respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and2012 respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012respectively
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
ltdrivegtWebsrvrbin2 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 FilesMicrosoft SQLServer paste all files into the CProgram Files (x86)Microsoft SQL Server100DTSTasksfolder
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
50
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Typographic Conventions
Table 13
Example Description
lt gt Angle brackets indicate that you replace these words or characters with appropriate entries tomake entries in the system for example Enter your ltUser Namegt
File Save Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
Example Textual cross-references to an internet address for example wwwsapcom
example Quicklinks added to the internet address of a homepage to enable quick access to specificcontent 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 titlespushbutton 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 namesof installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transactioncodes database table names and key concepts of a programming language when they aresurrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
SAP Business Planning and Consolidation 100Typographic Conventions
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 51
52
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
wwwsapcom
Material Number
- SAP Business 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 2008 R2 2012 or 2012 R2
- 344 Removing Default Access to the Console
- 345 Management Console Access Control
- 346 Configuring Planning and Consolidation to use SSL
- 347 Using Client Certificates
- 348 Configuring MS SQL Server Reporting Services to use SSL
-
- 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
-
Server Option Value Description
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 computername
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 forhttp and 443 is the default for https
Authentication type Note If you have chosen SAP BusinessObjects User Management System in theinstallation screen Authentication type does not appear in Advanced settings (asthat IIS authentication type is Anonymous in CMS mode)
Windows or Kerberos The default is Windows If you change this value fromWindows to Kerberos you must make some additional changes
See the Kerberos authentication settings section in the SAP Library ServerManager Guide on servicesapcominstguidesEPM-BPC 100 for theMicrosoft Platform
Scheduler Server Name The name of the server used for scheduling usually the application server forexample GMPV50072862B If you have multiple application servers select theappropriate one
NoteIf the primary server stops working you must manually configure yourapplication 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 theoperating system IIS SQL server analysis services ADOMDNET and MSXML This section provides guidance on
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 17
installing each component For specific versions required see Prerequisites [page 11] and the Product AvailabilityMatrix on the SAP Service Marketplace at servicesapcompam Search on Planning and Consolidation
NoteTo ensure a successful installation you must install the software in the order listed in this procedure
Check all third-party infrastructure services to ensure that they are functioning and that their authenticationmodels 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 itsown 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 applicationserver before you start the installation You can find the UMC installation package (UMCexe) on the Planningand Consolidation CD in a folder called UMC_100_INSTALLER When you run the installation package the wizardguides 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 andConsolidation)
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 multiserverconfiguration See Installing the Operating System [page 19]
3 Install the latest service pack for your operating system To install this service pack go towwwmicrosoftcom
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 SQLServer [page 19]
6 From your SQL Server media install Analysis Services Enterprise Edition and its required service packs and hotfixes See Installing Analysis Services [page 23]
7 On your application server install ADOMDNET The Planning and Consolidation zip file contains theADOMDNET 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 followinglocation BPC SetupServermsxmlmsi
18
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
9 On your application server install Microsoft Visual C++ 2010 SP1 Redistributable Package (x64)
The Microsoft Visual C++ 2010 SP1 Redistributable Package (x64) installation package is contained in thePlanning and Consolidation zip file at the following location BPC SetupServervcredist_x64exe
NoteThe version of vcredist_x64exe in BPC SetupServer has been updated to 10040219 If you have aprevious 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 wwwmicrosoftcomdownloadsendetailsaspxFamilyID=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 Marketplaceat servicesapcompam Search on Planning and Consolidation
Business Planning and Consolidation can support all servers with an operating system in any language
NoteCurrently Business Planning and Consolidation does not support an operating system in bi-directionallanguages such as Hebrew
Procedure
If you are installing IIS 70 75 80 or 85 you must enable the following features
Enable Basic Authentication and Windows Authentication these are not installed by default
Install IIS 6 Metabase Compatibility role
Business Planning and Consolidation uses the ADSI provider to handle IIS administration such as virtualdirectory and security but IIS 7 does not install the ADSI provider by default
273 Installing the SQL Server
Prerequisites
During the installation procedure you have the opportunity to specify the location of the EnvironmentShell databasefile Check that it is possible to access EnvironmentShell from the location where you intend to install the SQL serverIf it is not possible for port access reasons (DMZ WORKGROUP or nontrusted domain authentication failures) copyEnvironmentShell to a location on the SQL server (for example CEnvironmentShelldb10) You specify thislocation on the Server Information page by choosing Server Information Advanced Options Local Path forEnvironmentShell DB
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 19
Procedure
This section describes the general steps for installing the SQL Server component options and considerations wheninstalling 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
NoteIf you encounter a 500 HTTP Error when trying to connect to the Planning and Consolidation Web Client referto Microsoft Support articles 2520479 and 2468871 for assistance
To reinforce security we recommend that you install the SQL server and SSAS components to a nondefaultinstance 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 Optionssection below then choose Next
4 Review disc space requirements then choose Next
5 In Server Configuration Perform the following actions
1 In the Service Accounts tab enter a Planning and Consolidation sysadmin account for the SQL ServerDatabase Engine and the SQL Server Analysis services This is required so that the Planning andConsolidation sysadmin can create and process the Planning and Consolidation database because theMicrosoft SQL server tries to back up or restore database with the privileged account This account is alsorequired 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 differentdomain 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 theapplication server and the account requires the folder access privilege for the application server
To ensure that you have the complete access privileges we recommend the Planning and Consolidationsysadmin 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 touse a restrictive SQL ID that works with the drill-through feature If you must restrict SQL authentication forsecurity 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 installationprogram
20
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
8 Choose Install to begin the installation with the options you have set
SQL Server Component Options
For Single-Machine Installations
Install the following components from the Feature Selection screen
Database Engine Services
Analysis Services
Integration Service which is listed as one of the Shared Features
For Multiple Machine Installations
For multiple machine installations install the following components on each server
Table 7
Server Component What to Install
SQL Server Database Engine Services
SSAS Server Analysis Services
Application Server The following Shared Features
Client Tools Connectivity
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 Server2008 R2 and SQL Server 2012
Process Dimension
It is now possible to process a dimension with multiple selections At processing time the process dimension modulemakes changed or added information for each dimension and process for all selected dimensions and cubes inparallel
Optimize Model
If there are custom partitions for a FACT partition in the OLAP database an optimization module can process custompartitions in parallel when Full or Incremental Optimize is performed However if a full optimize is performed withthe 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 parallelbecause 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 applicationserver and application set databases
NoteSetting the SQL isolation level to be Read Committed Snapshot mode for a database can only be done once andcannot be reversed
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 21
Real Time MOLAP
You can set the OLAP storage model of the write-back partition to be MOLAP (Multidimensional OLAP) This settingremains 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 asfollows
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 Servertrade20052008 which you can download from wwwmicrosoftcom (search on ldquoTable Partitioningrdquo to find all relevantarticles)
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 Thebrowser 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 localhostand external network interface machine
3 If you want to use IP1 which indicates Server IP set Enabled to Yes and specify the TCP Port as desired
4 Delete 0 from TCP Dynamic Ports Set IPAll - TCP Ports as desired (for example 1533)
RecommendationWe do not recommend using dynamic ports
In an SQL server the default instance has a listener which listens on a fixed port (TCP port 1433)However for the named instance the port on which the SQL server listens is random and dynamicallyselected when the named instance of the SQL server starts This recommendation prevents any conflictproblems
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 Setthe 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 thatthe user identified as the Log on as user has the sysadmin SQL Server role defined under Server Roles in theSQL Server Management Studio This is required so Analysis Services can process the SQL Server
From SQL Server Management Studio do the following tasks
22
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
1 If you want to use a port with a named instance select the server type Analysis Services select the servername (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 ServerProperties window displays which shows all configurable properties
3 For enhanced security change the default value to your port number (for example 2724) This means thatyou use a fixed port as for the SQL Server option Then choose OK
NoteWe do not support a nondefault port with the default instance in this release If you want to use the defaultinstance do not change the port number
Restart SQL and OLAP
Confirm that the installation has completed successfully by checking that there are no installation relatedproblems on the event viewer You can now install Planning and Consolidation
274 Installing Analysis Services
Procedure
After you install SQL Server and its required service packs and hotfixes you must install SQL Server Analysis Servicesand its required service packs and hotfixes
NoteIf you have migrated your Analysis Services repository to the SQL Server back up the database that contains therepository before installing this release
To install Analysis Services for SQL Server 2008 SQL Server 2008 R2 or SQL Server 2012 follow the steps andguidelines in technetmicrosoftcomen-uslibraryms143219aspx
To avoid slow performance when a user has more than six OLAP databases follow the steps and guidelines in thePerformance Guide for SQL 2008 at wwwmicrosoftcomdownloadsdetailsaspxFamilyID=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 tohave it available for the Planning and Consolidation installation program
1 Download the Anti-Cross Site Scripting Library file AntiXSSLibraryDLL from the Microsoft Web site atwwwmicrosoftcomdownloadendetailsaspxid=28589
2 Save the extracted file locally
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 23
When you install Planning and Consolidation Server a step in the process requires you to identify the path toAntiXssLibrarydll
28 Installing on a Single Server
When you install all Planning and Consolidation server components on a single server you should consider thefollowing 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 theuncompressed 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 Log on to the server with a local server user ID or domain user ID For more information see Logging on toservers [page 14]
3 Make sure all prerequisite software is installed on the server For more information see Installing thePrerequisites [page 17]
4 Obtain SAP Planning and Consolidation archive from the Downloads SAP Installations amp Upgrades areaof SAP Service Marketplace
5 Extract the files from the archive Go to the BPC Setup folder and run the StartUpexe file
6 From the Server Install screen select Install the Planning and Consolidation server
7 From the Welcome screen choose Next
8 From the License Agreement page choose I accept the terms of the license agreement then choose Next
9 From the Installation Method page accept the default Single machine enter a system ID for the systemlandscape directory (SLD) and choose Next
NoteEntering a system ID of the SLD is only required if you have a SAP Solution Manager license If you do nothave a SAP Solution Manager license you can leave this field empty
10 From the Authentication Method page choose the desired authentication method and choose Next
11 If you have chosen SAP BusinessObjects User Management System in the previous screen on the CMSAuthentication page enter the information required to log on to CMS as an administrator
The following information is required
24
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
Table 8
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 Thisgroup name is filtered as the default when adding a user in Planning andConsolidation Administration Use a comma ( ) to separate multiple names
12 After entering the CMS administrator authentication details choose Next
13 From the Service type accounts page enter service-level account user IDs and passwords See Service-LevelAccounts [page 15]
14 After defining the IDs and passwords choose Next
15 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 chooseNext
16 Specify the location and name of AntiXssLibrarydll See Installing the Anti-Cross Site ScriptingLibrary [page 23]
Choose Next
17 Select destination folders for Programs and Data The Data files include Webfolders and FileDB (publishedreports) and should be installed on a separate drive in a production environment This recommendation reducesthe hard disk IO time and helps to speed up SQL commands
Accept the defaults or make your selections then choose Next
18 Select the default values for the Web client The values are used to determine the default language and regionfor the Web client when you connect to it You can change the values in the Planning and Consolidation ServerManager
19 The installation process takes a few moments When it is complete choose Exit
20 A prompt is displayed to restart your computer Select OK to restart
21 Perform the steps in After Installing Planning and Consolidation Servers [page 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 avariety of ways and configure the servers as a Network Load Balancing (NLB) environment
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 25
The recommended Planning and Consolidation practice is to assign resources using a round robin approach for loadbalancing
You can install the SQL OLAP and FileShare types remotely from the application server You need to performadditional server installations if you have multiple application servers
Installing each Planning and Consolidation application server in a multiserver (NLB) configuration is identical to theprocedure 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 Balancingenvironment With this option there is an additional choice to Include sample environment (required on only oneof the application servers) This is because when you install the application server it connects to the databaseserver and creates the sample environment (EnvironmentShell) Installing the sample environment is requiredon 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
26
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
3 After Installing Planning and ConsolidationServers
31 Post-Installation Steps
Procedure
Perform these steps after installing the Planning and Consolidation servers for new installations of Planning andConsolidation
1 Connect your Planning and Consolidation system to Solution Manager Diagnostics (SMD) to allow support staffto identify analyze and resolve problems with your application See Connecting to Solution ManagerDiagnostics [page 28]
2 Configure the Planning and Consolidation NET and application server to ensure that it and its related servicesfunction properly and reliably For more information see Configuring the Planning and Consolidation NETApplication Server [page 29]
3 Optional configuration steps [page 29]
1 To ensure proper functioning of the Management Console create an SQL user and modify the System DSNand 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 loggingfor ODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default WebSite [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory canaccess the Management Console with whatever rights they have been granted on the server Forinformation about removing default access and creating a group that can access the console see RemovingDefault Access to the Console [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommendthat you only grant Management Console access to system administrators Planning and Consolidationusers should not have any access For more information see Management Console AccessControl [page 33]
6 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
4 Take the following steps to set up security
If you are defining security and application structure continue with step 5
If you want to designate someone other than the system administrator to manage security and applicationstructure log on to EnvironmentShell designate a user as a Primary Administrator
This user must have Administration ndash Environment and Security ‒ Define User task rights so that he or shecan 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 SeeInstalling the Administration Client [page 37]
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 27
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 taskprofiles 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 mustcomplete this step since there is no access to dimensions or members)
NoteTo allow users to request and query large amounts of data you can edit the metabasexml file located at CWindowssystem32inetsrv Set the following parameters to the stated values
ASPBUFFERINGLIMIT = 10485760
MAXREQUESTENTITYALLOWED = 10485760
32 Connecting to Solution Manager Diagnostics
NoteYou only need to perform the steps in this section if you have a SAP Solution Manager licence
The diagnostics functions in SAP Solution Manager allow identification analysis and resolution of problems Thisprocedure 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 areinstalled
NoteInstallation files for Diagnostics Agent are available on Service Marketplace by navigating to SupportPackages and Patches mdash Entry by Application Group SAP Technology Components SAP SOLUTIONMANAGER SAP SOLUTION MANAGER 70 EHP 1 Entry by Component Agents for managed systemsDIAGNOSTICS AGENT 711
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 whereMicrosoft 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
28
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
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 ServiceMarketplace at servicesapcom~sapidb011000358700000074392009E and follow the chapters that applyto Planning and Consolidation
33 Configuring the Planning and Consolidation NETApplication Servers
Procedure
Modifying machineconfig Files
To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock occurrences that wouldcause the application server to ldquosleeprdquo and not process anymore you can modify the machineconfig file whichresides in the WINDOWSMicrosoftNETFramework64v4030319Config directory
1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to specifywhether to automatically configure settings to achieve optimal performance based on the machineconfiguration You can set this attribute to True or False
For more information see msdnmicrosoftcomen-uslibrary7w2sway1aspx
2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the Planning andConsolidation application) or Machineconfig (for all applications including Planning and Consolidation) toensure the validationKey and decryptionKey keys have the same value on all application servers Thisway when the authentication cookie is checked the authentication ticket used on one server can still be validon another server
For more information and sample Visual Basic code for generating random key values seemsdnmicrosoftcomen-uslibraryms998288aspxpaght000007_webfarmdeploymentconsiderationsand msdnmicrosoftcomen-uslibraryms998310aspx
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 DSNand 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 forODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory can accessthe Management Console with whatever rights they have been granted on the server For information about
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 29
removing default access and creating a group that can access the console see Removing Default Access to theConsole [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommend thatyou only grant Management Console access to system administrators Planning and Consolidation users shouldnot have any access For more information see Management Console Access Control [page 33]
6 Configure the use of SSL in Planning and Consolidation See Configuring Planning and Consolidation to useSSL [page 34]
7 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
8 Configure Microsoft SQL Server Reporting Services to use SSL See Configuring MS SQL Server ReportingServices to use SSL [page 36]
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 databaserole 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 optionto use ODBC Logging Enter the following values
DSN is BPC_ManagementDSN Table is BPCLog The Microsoft SQL Server Username and Password
5 Restart IIS
NoteWithout these updates the Management Console does work but some functionality (specifically User Activityand Service Status) does not work as expected
Should you need to uninstall Planning and Consolidation we recommend that you reset the Active Log Formatfield in IIS to W3C Extended Log File Format
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
30
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
Prerequisites
ODBC logging has been configured according to the Microsoft Knowledge Base article 245243 How to configureODBC 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 inApplicationHostconfig as shown here
ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0logFormat=Custom gtUse 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-00AA006111E0appcmd 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 articlespecified in the Prerequisites section Configure these settings in the ltodbcLogginggt node underltsystemwebServergt
Exampleltlocation path=Default Web SitegtltsystemwebServergtltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog userName=Usernamepassword=mypassword gtltsystemwebServergtltlocationgt
Use the following AppCmds to configure these attributes for the default Web site
appcmd set config Default Web Site sectionodbcLogging dataSourceBPC_ManagementDSN commitappHostappcmd set config Default Web Site sectionodbcLogging tableNameBPCLog commitappHostappcmd set config Default Web Site sectionodbcLogging userNameUsername commitappHostappcmd set config Default Web Site sectionodbcLogging passwordmypassword commitappHost
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 31
NoteYou cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must use the SQL ServerODBC driver For more information see the Microsoft Knowledge Base article 931202 The requirements for usingthe ODBC logging feature in IIS
343 Setting Up an ODBC Data Source in Windows Server2008 2008 R2 2012 or 2012 R2
Procedure
This procedure describes how to set up an ODBC data source for the Management Console in Windows Server 20082008 R2 2012 or 2012 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
NoteIf you have chosen SAP BusinessObjects User Management System in the installation screen you do not needto remove or configure access because the Management Console service always runs with the System Admin IDaccount which is a member of the Administrators group
Procedure
To remove default access to the Management Console and create a group that does have access to the console usethe procedure described below
32
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
NoteCreate your Management Console administrative group either on the server that hosts the Management Consoleor 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
NoteAlternatively you can perform analogous steps in Active Directory
3 In the Groups context menu choose New Group
4 Enter data as required Click Create
5 In the Computer Management dialog box choose Services and Applications Internet InformationServices 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 objectand all child objects Include these with entries explicitly defined here checkbox
NoteThis step is a necessary precursor to the completion of this procedure
10 In the Security dialog box click Copy to ensure that the System group retains its privileges
11 Remove access to the Management Console from all groups that should not have it
12 Choose Authentication in the center pane then disable Windows authentication
Result
Users who have not been granted access to the Management Console can still open the Management Console Webpage but it contains no data or menu options This does not affect the access that a user would otherwise have toPlanning and Consolidation
345 Management Console Access Control
After establishing the Management Console group you can add users or groups to it For more information aboutcreating this group see Removing Default Access to the Console [page 32] Their rights in Active Directory determinewhat they can access in the Console
By default any member of the Administrators Active Directory group on the application server or domain has fullaccess to all of the features of the Console except the Planning and Consolidation logging area Access to Planningand Consolidation logging is controlled within the Planning and Consolidation Administration Client task securityThe user must be granted View system logs task privileges For more information see the SAP Library Planning and
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 33
Consolidation Administrators Guide in servicesapcominstguidesepm-bpc 100 version for the Microsoftplatform
Your IT policy determines whether you grant access by group or user You may wish to create several levels of Consoleusers (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 describedin this table
Table 9
Privilege Rights Management Area
Task Manager and Kill Process Administrators group on application server or domain
Performance Monitor Counters Administrators group on application server or domain
Power Users group on application server or domain
Performance Monitor Users group on application server
Microsoft Analysis Services performance monitoring Administrators group on application server or domain
Microsoft SQL Server Monitoring (performance counters andstatistics)
Administrators group on application server or domain
346 Configuring Planning and Consolidation to use SSL
Procedure
Creating a Certificate for the Server
During the handshake phase of the SSL communication the server must send its certificate to the client The clientthen uses the certificate to encrypt information and send it back to the server
The procedure below describes how to create a self-signed certificate for the server
RecommendationWe recommend that you limit the use of self-signed certificates to testing only For a productive system you shouldobtain a certificate signed by a well-known certification authority (CA)
1 Start the Internet Information Services (IIS) Manager To do that go to Start All Programs AdministrativeTools Internet Information Services (IIS) Manager
2 In the Connections panel on the left-hand side select the server node and then choose Server Certificates
3 In the Actions panel on the right hand side choose the Create Self-Signed Certificate action
4 Enter the name that you want the certificate to be identified by for example MyTestSSLCertificate
IIS generates a new SSL certificate for you that has one yearrsquos expiry lease The certificate is issued to the local servername
Binding the Certificate to the Web Site
The procedure below describes how to bind the certificate to the web site for which SSL connections must be used
1 In the Connections panel select the web site node
2 In the Actions panel choose Bindings
34
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
3 In the Site Bindings dialog that appears choose the Add button to create a new binding
4 Configure the parameters as follows
Type = https IP Address = [1] - this is a shorthand expression for the local server name
Port = 443 - this is the default SSL port
SSL Certificate = enter your newly created certificate name
5 Choose OK to create the new binding and then close the Site Bindings dialog
6 Restart the IIS processes To do this choose Restart from the Actions panel
7 In the middle panel under the IIS section choose SSL Settings
8 In the SSL Settings screen select the Require SSL checkbox
9 In the Actions panel choose to Apply these settings
To test the SSL connection in the Actions panel choose the Browse [1] 443 (https) link
347 Using Client Certificates
To enable the use of client certificates in Planning and Consolidation you must follow several manual steps
NotePlanning and Consolidation supports client certificate authentication in Windows Authentication Mode butdoes 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 technetmicrosoftcomen-uslibrarycc753810aspx
For more information about configuring the client certificate mapping authentication see technetmicrosoftcomen-uslibrarycc732996(WS10)aspx
When you create the client certificates you can set the type of certificate in the SSL Settings screen in InternetInformation Services (IIS) Manager
Procedure
1 Set the options for client certificates
1 In the IIS Manager select the web site where you installed Planning and Consolidation
2 Choose SSL Settings
3 In the Client certificates section select the Accept client certificates option
This option allows you to use a client certificate or username and password (Basic authentication) toconnect 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 theManagementConsole home page
3 Double-click Authentication and enable Anonymous Authentication
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 35
4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way asin step 3
5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the sameway 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
348 Configuring MS SQL Server Reporting Services to useSSL
Procedure
The procedure below describes how to configure the use of SSL in Microsoft SQL Server Reporting Services
NoteReporting Services does not provide functionalities for generating requesting or installing a certificate Theserver certificates that you want to use for configuring SSL must have already been installed on your computer
1 Open the Reporting Services Configuration Manager program To do this open the Windows Start menu andnavigate to All Programs Microsoft SQL Server ltversiongt Configuration Tools Reporting ServicesConfiguration Manager
2 In the Connect panel on the left-hand side select the Web Service URL option to open all the Report Server webservice parameters
3 Configure the parameters as follows
SSL Certificate = the name of the certificate that you want to use
SSL Port = 4434 Choose Apply to confirm the changes
5 In the Connect panel choose Report Manager URL to open the list of parameters that link Reporting Servicesto IIS
6 Choose Advanced to add your new SSL web URL
7 In the section Multiple SSL Identities for Report Manager choose Add Configure the parameters as follows
IP Address = (All IPv4) SSL Port = 443 Certificate = the name of your SSL certificate
8 To test the configuration click the URL that appears under the Report manager Site Identification section
36
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
4 Installing Planning and ConsolidationAdministration Client and the SAPBusinessObjects EPM solutions Add-in forMicrosoft Office
The installation of the Planning and Consolidation Administration Client allows administrators to build and maintainPlanning and Consolidation environments and models and administer security
All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions add-in forMicrosoft 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 valueof the Planning and Consolidation client to prompt for user name and password Otherwise the Planning andConsolidation Start Page does not display
41 Installing the Administration Client
Prerequisites
NoteFor a definitive list of system requirements see the Product Availability Matrix on SAP Service Marketplace atservicesapcompam Search on Planning and Consolidation
The following list describes the minimum software requirements
Microsoft Internet Explorer 70 80 90 or 10
Microsoft Office 2003 2007 2010 or 2012
NET Framework 20 or higher (install any required NET Framework Hotfixes by referring tosupportmicrosoftcomkb)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 37
NoteWe recommend that you install all of the latest Microsoft Windows hotfixes prior to installing the Administrationclient For information about which hotfixes to install see updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us
Procedure
The 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 ltPC_serverportgtsapbpcweb
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 mustdownload the most recent version of the full setup (EPM Add-inexe) from the Service Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPCInstallation folder
Individual users can install the EPM add-in on their own machines by going to the Planning and Consolidation Homepage 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 upthe 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
38
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
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 toperform the upgrade If Client Auto Update is not enabled and a newer version is detected clients must be installedmanually 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 andpassword in the Admin ID and Admin password fields respectively The Admin ID should be a member of thelocal administrators group on all the computers running the auto update This setting is not needed if all usershave 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 Thisoption is stored in the user preferences and may also be turned on or off using the User Optionshellip menu itemIf 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 toinstall 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 installit 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 servicesapcom
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 versionand policy information For a support package these files are
EPM Addin Support Package ltSP versiongtmsp EPM Addin Support Package ltSP versiongtxmlFor a patch these files are
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 (WebsrvrWebBPCInstallation)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 39
You can set a different update policy for each package listed
ExampleThe following table illustrates some possible situations assuming that you have installed the first full version(V1)
Table 10
Available maintenancepackages
V2-user update
V3-force update
V4-force update
V5-user update
V5-user update V5-user update
V6-auto update
V7-force update
Minimum RequiredVersion
V4 V4 V7
Notification A prompt tells the user toinstall maintenancepackage V4 using theForced Update behavior
If User Update is enabledthe prompt informs theuser that maintenancepackage V5 is available
A prompt tells the user toinstall maintenancepackage V7 using theForced Update behavior
New Version V4 V4 or V5 V7
If you change the update policy for any package click Update to complete the change
40
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
5 Connection Issues
You may experience connection problems with ports the proxy server or programs and settings that interact withthese components If you have any issues related to connection review the following recommendations andtroubleshooting tips
51 Checking for Open Ports
You must ensure that all required ports are open for inboundoutbound traffic By default Planning andConsolidation requires that Ports 80 (used by http) and 1433 and 2383 (used by SQL Server 2008) are open Totest whether the required ports are open go to a command prompt and enter the Telnet serveripaddress and portFor example Telnet 431181836 80 If the system returns a blank command window the port is open If it returnsa message stating that it is unable to connect the port is not open
NoteYou can use the following site to scan for the normal ports It allows you to manually enter a port number to test
wwwmyserverorgportsniffasp
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 Planningand Consolidation server as an exception You can do this at the client level ( Internet Explorer ToolsInternet 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 fullyqualified 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 Consolidationauthentication Do not use authentication on the proxy server The system synchronizes the user name andpassword on the remote server with the local user name and password
SAP Business Planning and Consolidation 100Connection Issues
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 41
NoteFor more information about setting up an ISA proxy server contact SAP Support to request a copy of Setting upISA Proxy Server White Paper For more information about Business Planning and Consolidation firewall portssee SAP Note 1505250
Internet Explorer Settings Issues
Internet Explorer settings must be set correctly to prevent errors and problems when you attempt to access thePlanning 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 insertthe IP address or fully qualified server name of the Planning and Consolidation server as an exception bychoosing 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
42
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Connection Issues
6 Installing Planning and Consolidation withTwo Active Directory Domains
To set up a Planning and Consolidation 10 application server in a hosted environment and use your own domainusers follow this procedure In general you install Planning and Consolidation on the host domain use the hostdomain account and assign it to the Planning and Consolidation users SysAdmin Admin and Users Then you acceptone 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 andpassword 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 topromote 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 privilegefor the Planning and Consolidation server
5 Install Planning and Consolidation and assign your domain account either to the three Planning andConsolidation administrative users SysAdmin Admin and Users or to only one of the three Planning andConsolidation administrative users and to three of your users Be sure you use your own user account ratherthan host domain users
Planning and Consolidation impersonation can then access your domain from the host environment becauseit has the privilege of your domain account
SAP Business Planning and Consolidation 100Installing Planning and Consolidation with Two Active Directory Domains
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 43
7 Installing Planning and Consolidation in aTerminal Services or Citrix ServerDeployment
This section describes best practices and instructions for installing Planning and Consolidation in a Terminal Servicesor Citrix Server deployment
71 Terminal Services Home Directories
We recommend using Terminal Server home directories rather than using the userrsquos profile directory The profiledirectory downloads a minimal amount of information about the dimensions of the environment you are logging onto and may be as large as 2 MB per user The profile directory is on the system drive and has limited space Byspecifying 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 individualserver 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 clientserver (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
44
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
Procedure
The following steps outline how to install the Planning and Consolidation clients in a Terminal Services (TS) or CitrixServer deployment
1 Make sure the Terminal Services or Citrix Server machine has the system requirements installed
2 Log on to the Terminal Services or Citrix Server machine with a user ID that has the rights to install on thatserver
3 At a command prompt enter Change userinstall
4 Open a browser and connect to the URL ltPC_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_MSBPCAdminMainexe
74 Creating a Shortcut to the Launch Page
Procedure
If you use published desktops instead of published applications the Planning and Consolidation desktop file (whichis installed on the current userrsquos desktop) must be moved to the All UsersDesktop folder
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 45
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 SQLServer 2012 support the remote modification of SSIS packages Planning and Consolidation also supports theremote 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 whichyou want to modify SSIS packages
These custom tasks reference dlls that connect to the database server and perform certain validation when usersset up the parameters of each task All the custom task reference components must also be installed in the machineon which you want to modify SSIS packages
We provide a program that registers all the reference components of the custom tasks This section explains theinstallation 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 ndash This folder contains all the dlls that should be installed on the machine There are Planning andConsolidation platform components and all of the Data Manager custom task files
Config folder ndash This folder contains only one file named Filelistxml and lists all of the files that should be installedIf you need to add or remove certain components from the installation you can modify this xml file
OSoftSetupexe ndash This is the main executable file to run the installation package
NoteIf you are not installing SSIS Custom Tasks on your client machine ndash specifically a machine other than the Planningand Consolidation application server ndash you must first install OSoftSSIS2008_Client or OSoftSSIS2012_Client onthe client machine followed by the SQL Server version If you want to use SQL 2008 Tasks under the SQL 2012environment you must install OSoftSSIS2008_Client on the application server For detailed information see SAPNote 1707410 You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package byextracting OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPCInstallation folder on the Planning and Consolidation server To modify SSIS packages on the Planning andConsolidation application server you need to install OSoftSSIS2008_Client or OSoftSSIS2012_Client for creatinga COM+ application For more information see Before You Modify the SSIS Packages [page 49] and Setup ofa COM+ Application on the Application Server [page 50]
Bin folder
This folder contains the following components
46
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Table 11
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012respectively
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
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 47
Name Remark
BPCWriteBackdll
InteropDTSdll
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 addmore components to the installation package you can copy the new components into the Bin folder and add theproper xml tags in FileListxml You need to enter information for the following tags
RegistType ndash This is the registration information of the component You can enter the following values
RegAsm ndash For NET component
48
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Regsvr32 ndash For VB6 component
Gacutil ndash For NET Framework component that should be registered into Global Assembly Cache
FileName ndash Component file name
OSoftSetupexe
This is the executable file to run the SSIS installation package Double-click the file to start the installation You needto enter information for the following fields
Set SQL server
Specify the SQL server name If your SQL Server has an instance specify the instance name
NoteIf you installed the OSoftSSIS2008_Client or OSoftSSIS2012_Client on the application server the SQL servername is automatically disabled
Set server credential
This is the credential name of the COM+ package component Enter the user ID and password that can accessyour SQL Server This should be either the System Admin ID or Admin ID that was registered as a COM+ userwhen 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 ifyou 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 packagesremotely This is also true for the application server that has SSIS installed The Planning and ConsolidationData Manager has the following custom tasks
Table 12
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008and 2012 respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and2012 respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012respectively
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 49
Name Remark
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and2012 respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008and 2012 respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL2008 and 2012 respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and2012 respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012respectively
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
ltdrivegtWebsrvrbin2 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 FilesMicrosoft SQLServer paste all files into the CProgram Files (x86)Microsoft SQL Server100DTSTasksfolder
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
50
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Typographic Conventions
Table 13
Example Description
lt gt Angle brackets indicate that you replace these words or characters with appropriate entries tomake entries in the system for example Enter your ltUser Namegt
File Save Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
Example Textual cross-references to an internet address for example wwwsapcom
example Quicklinks added to the internet address of a homepage to enable quick access to specificcontent 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 titlespushbutton 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 namesof installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transactioncodes database table names and key concepts of a programming language when they aresurrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
SAP Business Planning and Consolidation 100Typographic Conventions
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 51
52
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
wwwsapcom
Material Number
- SAP Business 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 2008 R2 2012 or 2012 R2
- 344 Removing Default Access to the Console
- 345 Management Console Access Control
- 346 Configuring Planning and Consolidation to use SSL
- 347 Using Client Certificates
- 348 Configuring MS SQL Server Reporting Services to use SSL
-
- 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
-
installing each component For specific versions required see Prerequisites [page 11] and the Product AvailabilityMatrix on the SAP Service Marketplace at servicesapcompam Search on Planning and Consolidation
NoteTo ensure a successful installation you must install the software in the order listed in this procedure
Check all third-party infrastructure services to ensure that they are functioning and that their authenticationmodels 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 itsown 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 applicationserver before you start the installation You can find the UMC installation package (UMCexe) on the Planningand Consolidation CD in a folder called UMC_100_INSTALLER When you run the installation package the wizardguides 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 andConsolidation)
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 multiserverconfiguration See Installing the Operating System [page 19]
3 Install the latest service pack for your operating system To install this service pack go towwwmicrosoftcom
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 SQLServer [page 19]
6 From your SQL Server media install Analysis Services Enterprise Edition and its required service packs and hotfixes See Installing Analysis Services [page 23]
7 On your application server install ADOMDNET The Planning and Consolidation zip file contains theADOMDNET 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 followinglocation BPC SetupServermsxmlmsi
18
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
9 On your application server install Microsoft Visual C++ 2010 SP1 Redistributable Package (x64)
The Microsoft Visual C++ 2010 SP1 Redistributable Package (x64) installation package is contained in thePlanning and Consolidation zip file at the following location BPC SetupServervcredist_x64exe
NoteThe version of vcredist_x64exe in BPC SetupServer has been updated to 10040219 If you have aprevious 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 wwwmicrosoftcomdownloadsendetailsaspxFamilyID=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 Marketplaceat servicesapcompam Search on Planning and Consolidation
Business Planning and Consolidation can support all servers with an operating system in any language
NoteCurrently Business Planning and Consolidation does not support an operating system in bi-directionallanguages such as Hebrew
Procedure
If you are installing IIS 70 75 80 or 85 you must enable the following features
Enable Basic Authentication and Windows Authentication these are not installed by default
Install IIS 6 Metabase Compatibility role
Business Planning and Consolidation uses the ADSI provider to handle IIS administration such as virtualdirectory and security but IIS 7 does not install the ADSI provider by default
273 Installing the SQL Server
Prerequisites
During the installation procedure you have the opportunity to specify the location of the EnvironmentShell databasefile Check that it is possible to access EnvironmentShell from the location where you intend to install the SQL serverIf it is not possible for port access reasons (DMZ WORKGROUP or nontrusted domain authentication failures) copyEnvironmentShell to a location on the SQL server (for example CEnvironmentShelldb10) You specify thislocation on the Server Information page by choosing Server Information Advanced Options Local Path forEnvironmentShell DB
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 19
Procedure
This section describes the general steps for installing the SQL Server component options and considerations wheninstalling 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
NoteIf you encounter a 500 HTTP Error when trying to connect to the Planning and Consolidation Web Client referto Microsoft Support articles 2520479 and 2468871 for assistance
To reinforce security we recommend that you install the SQL server and SSAS components to a nondefaultinstance 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 Optionssection below then choose Next
4 Review disc space requirements then choose Next
5 In Server Configuration Perform the following actions
1 In the Service Accounts tab enter a Planning and Consolidation sysadmin account for the SQL ServerDatabase Engine and the SQL Server Analysis services This is required so that the Planning andConsolidation sysadmin can create and process the Planning and Consolidation database because theMicrosoft SQL server tries to back up or restore database with the privileged account This account is alsorequired 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 differentdomain 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 theapplication server and the account requires the folder access privilege for the application server
To ensure that you have the complete access privileges we recommend the Planning and Consolidationsysadmin 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 touse a restrictive SQL ID that works with the drill-through feature If you must restrict SQL authentication forsecurity 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 installationprogram
20
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
8 Choose Install to begin the installation with the options you have set
SQL Server Component Options
For Single-Machine Installations
Install the following components from the Feature Selection screen
Database Engine Services
Analysis Services
Integration Service which is listed as one of the Shared Features
For Multiple Machine Installations
For multiple machine installations install the following components on each server
Table 7
Server Component What to Install
SQL Server Database Engine Services
SSAS Server Analysis Services
Application Server The following Shared Features
Client Tools Connectivity
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 Server2008 R2 and SQL Server 2012
Process Dimension
It is now possible to process a dimension with multiple selections At processing time the process dimension modulemakes changed or added information for each dimension and process for all selected dimensions and cubes inparallel
Optimize Model
If there are custom partitions for a FACT partition in the OLAP database an optimization module can process custompartitions in parallel when Full or Incremental Optimize is performed However if a full optimize is performed withthe 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 parallelbecause 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 applicationserver and application set databases
NoteSetting the SQL isolation level to be Read Committed Snapshot mode for a database can only be done once andcannot be reversed
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 21
Real Time MOLAP
You can set the OLAP storage model of the write-back partition to be MOLAP (Multidimensional OLAP) This settingremains 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 asfollows
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 Servertrade20052008 which you can download from wwwmicrosoftcom (search on ldquoTable Partitioningrdquo to find all relevantarticles)
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 Thebrowser 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 localhostand external network interface machine
3 If you want to use IP1 which indicates Server IP set Enabled to Yes and specify the TCP Port as desired
4 Delete 0 from TCP Dynamic Ports Set IPAll - TCP Ports as desired (for example 1533)
RecommendationWe do not recommend using dynamic ports
In an SQL server the default instance has a listener which listens on a fixed port (TCP port 1433)However for the named instance the port on which the SQL server listens is random and dynamicallyselected when the named instance of the SQL server starts This recommendation prevents any conflictproblems
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 Setthe 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 thatthe user identified as the Log on as user has the sysadmin SQL Server role defined under Server Roles in theSQL Server Management Studio This is required so Analysis Services can process the SQL Server
From SQL Server Management Studio do the following tasks
22
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
1 If you want to use a port with a named instance select the server type Analysis Services select the servername (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 ServerProperties window displays which shows all configurable properties
3 For enhanced security change the default value to your port number (for example 2724) This means thatyou use a fixed port as for the SQL Server option Then choose OK
NoteWe do not support a nondefault port with the default instance in this release If you want to use the defaultinstance do not change the port number
Restart SQL and OLAP
Confirm that the installation has completed successfully by checking that there are no installation relatedproblems on the event viewer You can now install Planning and Consolidation
274 Installing Analysis Services
Procedure
After you install SQL Server and its required service packs and hotfixes you must install SQL Server Analysis Servicesand its required service packs and hotfixes
NoteIf you have migrated your Analysis Services repository to the SQL Server back up the database that contains therepository before installing this release
To install Analysis Services for SQL Server 2008 SQL Server 2008 R2 or SQL Server 2012 follow the steps andguidelines in technetmicrosoftcomen-uslibraryms143219aspx
To avoid slow performance when a user has more than six OLAP databases follow the steps and guidelines in thePerformance Guide for SQL 2008 at wwwmicrosoftcomdownloadsdetailsaspxFamilyID=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 tohave it available for the Planning and Consolidation installation program
1 Download the Anti-Cross Site Scripting Library file AntiXSSLibraryDLL from the Microsoft Web site atwwwmicrosoftcomdownloadendetailsaspxid=28589
2 Save the extracted file locally
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 23
When you install Planning and Consolidation Server a step in the process requires you to identify the path toAntiXssLibrarydll
28 Installing on a Single Server
When you install all Planning and Consolidation server components on a single server you should consider thefollowing 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 theuncompressed 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 Log on to the server with a local server user ID or domain user ID For more information see Logging on toservers [page 14]
3 Make sure all prerequisite software is installed on the server For more information see Installing thePrerequisites [page 17]
4 Obtain SAP Planning and Consolidation archive from the Downloads SAP Installations amp Upgrades areaof SAP Service Marketplace
5 Extract the files from the archive Go to the BPC Setup folder and run the StartUpexe file
6 From the Server Install screen select Install the Planning and Consolidation server
7 From the Welcome screen choose Next
8 From the License Agreement page choose I accept the terms of the license agreement then choose Next
9 From the Installation Method page accept the default Single machine enter a system ID for the systemlandscape directory (SLD) and choose Next
NoteEntering a system ID of the SLD is only required if you have a SAP Solution Manager license If you do nothave a SAP Solution Manager license you can leave this field empty
10 From the Authentication Method page choose the desired authentication method and choose Next
11 If you have chosen SAP BusinessObjects User Management System in the previous screen on the CMSAuthentication page enter the information required to log on to CMS as an administrator
The following information is required
24
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
Table 8
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 Thisgroup name is filtered as the default when adding a user in Planning andConsolidation Administration Use a comma ( ) to separate multiple names
12 After entering the CMS administrator authentication details choose Next
13 From the Service type accounts page enter service-level account user IDs and passwords See Service-LevelAccounts [page 15]
14 After defining the IDs and passwords choose Next
15 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 chooseNext
16 Specify the location and name of AntiXssLibrarydll See Installing the Anti-Cross Site ScriptingLibrary [page 23]
Choose Next
17 Select destination folders for Programs and Data The Data files include Webfolders and FileDB (publishedreports) and should be installed on a separate drive in a production environment This recommendation reducesthe hard disk IO time and helps to speed up SQL commands
Accept the defaults or make your selections then choose Next
18 Select the default values for the Web client The values are used to determine the default language and regionfor the Web client when you connect to it You can change the values in the Planning and Consolidation ServerManager
19 The installation process takes a few moments When it is complete choose Exit
20 A prompt is displayed to restart your computer Select OK to restart
21 Perform the steps in After Installing Planning and Consolidation Servers [page 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 avariety of ways and configure the servers as a Network Load Balancing (NLB) environment
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 25
The recommended Planning and Consolidation practice is to assign resources using a round robin approach for loadbalancing
You can install the SQL OLAP and FileShare types remotely from the application server You need to performadditional server installations if you have multiple application servers
Installing each Planning and Consolidation application server in a multiserver (NLB) configuration is identical to theprocedure 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 Balancingenvironment With this option there is an additional choice to Include sample environment (required on only oneof the application servers) This is because when you install the application server it connects to the databaseserver and creates the sample environment (EnvironmentShell) Installing the sample environment is requiredon 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
26
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
3 After Installing Planning and ConsolidationServers
31 Post-Installation Steps
Procedure
Perform these steps after installing the Planning and Consolidation servers for new installations of Planning andConsolidation
1 Connect your Planning and Consolidation system to Solution Manager Diagnostics (SMD) to allow support staffto identify analyze and resolve problems with your application See Connecting to Solution ManagerDiagnostics [page 28]
2 Configure the Planning and Consolidation NET and application server to ensure that it and its related servicesfunction properly and reliably For more information see Configuring the Planning and Consolidation NETApplication Server [page 29]
3 Optional configuration steps [page 29]
1 To ensure proper functioning of the Management Console create an SQL user and modify the System DSNand 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 loggingfor ODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default WebSite [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory canaccess the Management Console with whatever rights they have been granted on the server Forinformation about removing default access and creating a group that can access the console see RemovingDefault Access to the Console [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommendthat you only grant Management Console access to system administrators Planning and Consolidationusers should not have any access For more information see Management Console AccessControl [page 33]
6 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
4 Take the following steps to set up security
If you are defining security and application structure continue with step 5
If you want to designate someone other than the system administrator to manage security and applicationstructure log on to EnvironmentShell designate a user as a Primary Administrator
This user must have Administration ndash Environment and Security ‒ Define User task rights so that he or shecan 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 SeeInstalling the Administration Client [page 37]
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 27
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 taskprofiles 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 mustcomplete this step since there is no access to dimensions or members)
NoteTo allow users to request and query large amounts of data you can edit the metabasexml file located at CWindowssystem32inetsrv Set the following parameters to the stated values
ASPBUFFERINGLIMIT = 10485760
MAXREQUESTENTITYALLOWED = 10485760
32 Connecting to Solution Manager Diagnostics
NoteYou only need to perform the steps in this section if you have a SAP Solution Manager licence
The diagnostics functions in SAP Solution Manager allow identification analysis and resolution of problems Thisprocedure 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 areinstalled
NoteInstallation files for Diagnostics Agent are available on Service Marketplace by navigating to SupportPackages and Patches mdash Entry by Application Group SAP Technology Components SAP SOLUTIONMANAGER SAP SOLUTION MANAGER 70 EHP 1 Entry by Component Agents for managed systemsDIAGNOSTICS AGENT 711
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 whereMicrosoft 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
28
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
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 ServiceMarketplace at servicesapcom~sapidb011000358700000074392009E and follow the chapters that applyto Planning and Consolidation
33 Configuring the Planning and Consolidation NETApplication Servers
Procedure
Modifying machineconfig Files
To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock occurrences that wouldcause the application server to ldquosleeprdquo and not process anymore you can modify the machineconfig file whichresides in the WINDOWSMicrosoftNETFramework64v4030319Config directory
1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to specifywhether to automatically configure settings to achieve optimal performance based on the machineconfiguration You can set this attribute to True or False
For more information see msdnmicrosoftcomen-uslibrary7w2sway1aspx
2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the Planning andConsolidation application) or Machineconfig (for all applications including Planning and Consolidation) toensure the validationKey and decryptionKey keys have the same value on all application servers Thisway when the authentication cookie is checked the authentication ticket used on one server can still be validon another server
For more information and sample Visual Basic code for generating random key values seemsdnmicrosoftcomen-uslibraryms998288aspxpaght000007_webfarmdeploymentconsiderationsand msdnmicrosoftcomen-uslibraryms998310aspx
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 DSNand 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 forODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory can accessthe Management Console with whatever rights they have been granted on the server For information about
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 29
removing default access and creating a group that can access the console see Removing Default Access to theConsole [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommend thatyou only grant Management Console access to system administrators Planning and Consolidation users shouldnot have any access For more information see Management Console Access Control [page 33]
6 Configure the use of SSL in Planning and Consolidation See Configuring Planning and Consolidation to useSSL [page 34]
7 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
8 Configure Microsoft SQL Server Reporting Services to use SSL See Configuring MS SQL Server ReportingServices to use SSL [page 36]
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 databaserole 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 optionto use ODBC Logging Enter the following values
DSN is BPC_ManagementDSN Table is BPCLog The Microsoft SQL Server Username and Password
5 Restart IIS
NoteWithout these updates the Management Console does work but some functionality (specifically User Activityand Service Status) does not work as expected
Should you need to uninstall Planning and Consolidation we recommend that you reset the Active Log Formatfield in IIS to W3C Extended Log File Format
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
30
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
Prerequisites
ODBC logging has been configured according to the Microsoft Knowledge Base article 245243 How to configureODBC 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 inApplicationHostconfig as shown here
ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0logFormat=Custom gtUse 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-00AA006111E0appcmd 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 articlespecified in the Prerequisites section Configure these settings in the ltodbcLogginggt node underltsystemwebServergt
Exampleltlocation path=Default Web SitegtltsystemwebServergtltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog userName=Usernamepassword=mypassword gtltsystemwebServergtltlocationgt
Use the following AppCmds to configure these attributes for the default Web site
appcmd set config Default Web Site sectionodbcLogging dataSourceBPC_ManagementDSN commitappHostappcmd set config Default Web Site sectionodbcLogging tableNameBPCLog commitappHostappcmd set config Default Web Site sectionodbcLogging userNameUsername commitappHostappcmd set config Default Web Site sectionodbcLogging passwordmypassword commitappHost
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 31
NoteYou cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must use the SQL ServerODBC driver For more information see the Microsoft Knowledge Base article 931202 The requirements for usingthe ODBC logging feature in IIS
343 Setting Up an ODBC Data Source in Windows Server2008 2008 R2 2012 or 2012 R2
Procedure
This procedure describes how to set up an ODBC data source for the Management Console in Windows Server 20082008 R2 2012 or 2012 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
NoteIf you have chosen SAP BusinessObjects User Management System in the installation screen you do not needto remove or configure access because the Management Console service always runs with the System Admin IDaccount which is a member of the Administrators group
Procedure
To remove default access to the Management Console and create a group that does have access to the console usethe procedure described below
32
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
NoteCreate your Management Console administrative group either on the server that hosts the Management Consoleor 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
NoteAlternatively you can perform analogous steps in Active Directory
3 In the Groups context menu choose New Group
4 Enter data as required Click Create
5 In the Computer Management dialog box choose Services and Applications Internet InformationServices 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 objectand all child objects Include these with entries explicitly defined here checkbox
NoteThis step is a necessary precursor to the completion of this procedure
10 In the Security dialog box click Copy to ensure that the System group retains its privileges
11 Remove access to the Management Console from all groups that should not have it
12 Choose Authentication in the center pane then disable Windows authentication
Result
Users who have not been granted access to the Management Console can still open the Management Console Webpage but it contains no data or menu options This does not affect the access that a user would otherwise have toPlanning and Consolidation
345 Management Console Access Control
After establishing the Management Console group you can add users or groups to it For more information aboutcreating this group see Removing Default Access to the Console [page 32] Their rights in Active Directory determinewhat they can access in the Console
By default any member of the Administrators Active Directory group on the application server or domain has fullaccess to all of the features of the Console except the Planning and Consolidation logging area Access to Planningand Consolidation logging is controlled within the Planning and Consolidation Administration Client task securityThe user must be granted View system logs task privileges For more information see the SAP Library Planning and
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 33
Consolidation Administrators Guide in servicesapcominstguidesepm-bpc 100 version for the Microsoftplatform
Your IT policy determines whether you grant access by group or user You may wish to create several levels of Consoleusers (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 describedin this table
Table 9
Privilege Rights Management Area
Task Manager and Kill Process Administrators group on application server or domain
Performance Monitor Counters Administrators group on application server or domain
Power Users group on application server or domain
Performance Monitor Users group on application server
Microsoft Analysis Services performance monitoring Administrators group on application server or domain
Microsoft SQL Server Monitoring (performance counters andstatistics)
Administrators group on application server or domain
346 Configuring Planning and Consolidation to use SSL
Procedure
Creating a Certificate for the Server
During the handshake phase of the SSL communication the server must send its certificate to the client The clientthen uses the certificate to encrypt information and send it back to the server
The procedure below describes how to create a self-signed certificate for the server
RecommendationWe recommend that you limit the use of self-signed certificates to testing only For a productive system you shouldobtain a certificate signed by a well-known certification authority (CA)
1 Start the Internet Information Services (IIS) Manager To do that go to Start All Programs AdministrativeTools Internet Information Services (IIS) Manager
2 In the Connections panel on the left-hand side select the server node and then choose Server Certificates
3 In the Actions panel on the right hand side choose the Create Self-Signed Certificate action
4 Enter the name that you want the certificate to be identified by for example MyTestSSLCertificate
IIS generates a new SSL certificate for you that has one yearrsquos expiry lease The certificate is issued to the local servername
Binding the Certificate to the Web Site
The procedure below describes how to bind the certificate to the web site for which SSL connections must be used
1 In the Connections panel select the web site node
2 In the Actions panel choose Bindings
34
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
3 In the Site Bindings dialog that appears choose the Add button to create a new binding
4 Configure the parameters as follows
Type = https IP Address = [1] - this is a shorthand expression for the local server name
Port = 443 - this is the default SSL port
SSL Certificate = enter your newly created certificate name
5 Choose OK to create the new binding and then close the Site Bindings dialog
6 Restart the IIS processes To do this choose Restart from the Actions panel
7 In the middle panel under the IIS section choose SSL Settings
8 In the SSL Settings screen select the Require SSL checkbox
9 In the Actions panel choose to Apply these settings
To test the SSL connection in the Actions panel choose the Browse [1] 443 (https) link
347 Using Client Certificates
To enable the use of client certificates in Planning and Consolidation you must follow several manual steps
NotePlanning and Consolidation supports client certificate authentication in Windows Authentication Mode butdoes 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 technetmicrosoftcomen-uslibrarycc753810aspx
For more information about configuring the client certificate mapping authentication see technetmicrosoftcomen-uslibrarycc732996(WS10)aspx
When you create the client certificates you can set the type of certificate in the SSL Settings screen in InternetInformation Services (IIS) Manager
Procedure
1 Set the options for client certificates
1 In the IIS Manager select the web site where you installed Planning and Consolidation
2 Choose SSL Settings
3 In the Client certificates section select the Accept client certificates option
This option allows you to use a client certificate or username and password (Basic authentication) toconnect 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 theManagementConsole home page
3 Double-click Authentication and enable Anonymous Authentication
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 35
4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way asin step 3
5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the sameway 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
348 Configuring MS SQL Server Reporting Services to useSSL
Procedure
The procedure below describes how to configure the use of SSL in Microsoft SQL Server Reporting Services
NoteReporting Services does not provide functionalities for generating requesting or installing a certificate Theserver certificates that you want to use for configuring SSL must have already been installed on your computer
1 Open the Reporting Services Configuration Manager program To do this open the Windows Start menu andnavigate to All Programs Microsoft SQL Server ltversiongt Configuration Tools Reporting ServicesConfiguration Manager
2 In the Connect panel on the left-hand side select the Web Service URL option to open all the Report Server webservice parameters
3 Configure the parameters as follows
SSL Certificate = the name of the certificate that you want to use
SSL Port = 4434 Choose Apply to confirm the changes
5 In the Connect panel choose Report Manager URL to open the list of parameters that link Reporting Servicesto IIS
6 Choose Advanced to add your new SSL web URL
7 In the section Multiple SSL Identities for Report Manager choose Add Configure the parameters as follows
IP Address = (All IPv4) SSL Port = 443 Certificate = the name of your SSL certificate
8 To test the configuration click the URL that appears under the Report manager Site Identification section
36
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
4 Installing Planning and ConsolidationAdministration Client and the SAPBusinessObjects EPM solutions Add-in forMicrosoft Office
The installation of the Planning and Consolidation Administration Client allows administrators to build and maintainPlanning and Consolidation environments and models and administer security
All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions add-in forMicrosoft 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 valueof the Planning and Consolidation client to prompt for user name and password Otherwise the Planning andConsolidation Start Page does not display
41 Installing the Administration Client
Prerequisites
NoteFor a definitive list of system requirements see the Product Availability Matrix on SAP Service Marketplace atservicesapcompam Search on Planning and Consolidation
The following list describes the minimum software requirements
Microsoft Internet Explorer 70 80 90 or 10
Microsoft Office 2003 2007 2010 or 2012
NET Framework 20 or higher (install any required NET Framework Hotfixes by referring tosupportmicrosoftcomkb)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 37
NoteWe recommend that you install all of the latest Microsoft Windows hotfixes prior to installing the Administrationclient For information about which hotfixes to install see updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us
Procedure
The 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 ltPC_serverportgtsapbpcweb
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 mustdownload the most recent version of the full setup (EPM Add-inexe) from the Service Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPCInstallation folder
Individual users can install the EPM add-in on their own machines by going to the Planning and Consolidation Homepage 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 upthe 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
38
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
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 toperform the upgrade If Client Auto Update is not enabled and a newer version is detected clients must be installedmanually 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 andpassword in the Admin ID and Admin password fields respectively The Admin ID should be a member of thelocal administrators group on all the computers running the auto update This setting is not needed if all usershave 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 Thisoption is stored in the user preferences and may also be turned on or off using the User Optionshellip menu itemIf 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 toinstall 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 installit 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 servicesapcom
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 versionand policy information For a support package these files are
EPM Addin Support Package ltSP versiongtmsp EPM Addin Support Package ltSP versiongtxmlFor a patch these files are
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 (WebsrvrWebBPCInstallation)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 39
You can set a different update policy for each package listed
ExampleThe following table illustrates some possible situations assuming that you have installed the first full version(V1)
Table 10
Available maintenancepackages
V2-user update
V3-force update
V4-force update
V5-user update
V5-user update V5-user update
V6-auto update
V7-force update
Minimum RequiredVersion
V4 V4 V7
Notification A prompt tells the user toinstall maintenancepackage V4 using theForced Update behavior
If User Update is enabledthe prompt informs theuser that maintenancepackage V5 is available
A prompt tells the user toinstall maintenancepackage V7 using theForced Update behavior
New Version V4 V4 or V5 V7
If you change the update policy for any package click Update to complete the change
40
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
5 Connection Issues
You may experience connection problems with ports the proxy server or programs and settings that interact withthese components If you have any issues related to connection review the following recommendations andtroubleshooting tips
51 Checking for Open Ports
You must ensure that all required ports are open for inboundoutbound traffic By default Planning andConsolidation requires that Ports 80 (used by http) and 1433 and 2383 (used by SQL Server 2008) are open Totest whether the required ports are open go to a command prompt and enter the Telnet serveripaddress and portFor example Telnet 431181836 80 If the system returns a blank command window the port is open If it returnsa message stating that it is unable to connect the port is not open
NoteYou can use the following site to scan for the normal ports It allows you to manually enter a port number to test
wwwmyserverorgportsniffasp
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 Planningand Consolidation server as an exception You can do this at the client level ( Internet Explorer ToolsInternet 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 fullyqualified 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 Consolidationauthentication Do not use authentication on the proxy server The system synchronizes the user name andpassword on the remote server with the local user name and password
SAP Business Planning and Consolidation 100Connection Issues
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 41
NoteFor more information about setting up an ISA proxy server contact SAP Support to request a copy of Setting upISA Proxy Server White Paper For more information about Business Planning and Consolidation firewall portssee SAP Note 1505250
Internet Explorer Settings Issues
Internet Explorer settings must be set correctly to prevent errors and problems when you attempt to access thePlanning 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 insertthe IP address or fully qualified server name of the Planning and Consolidation server as an exception bychoosing 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
42
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Connection Issues
6 Installing Planning and Consolidation withTwo Active Directory Domains
To set up a Planning and Consolidation 10 application server in a hosted environment and use your own domainusers follow this procedure In general you install Planning and Consolidation on the host domain use the hostdomain account and assign it to the Planning and Consolidation users SysAdmin Admin and Users Then you acceptone 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 andpassword 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 topromote 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 privilegefor the Planning and Consolidation server
5 Install Planning and Consolidation and assign your domain account either to the three Planning andConsolidation administrative users SysAdmin Admin and Users or to only one of the three Planning andConsolidation administrative users and to three of your users Be sure you use your own user account ratherthan host domain users
Planning and Consolidation impersonation can then access your domain from the host environment becauseit has the privilege of your domain account
SAP Business Planning and Consolidation 100Installing Planning and Consolidation with Two Active Directory Domains
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 43
7 Installing Planning and Consolidation in aTerminal Services or Citrix ServerDeployment
This section describes best practices and instructions for installing Planning and Consolidation in a Terminal Servicesor Citrix Server deployment
71 Terminal Services Home Directories
We recommend using Terminal Server home directories rather than using the userrsquos profile directory The profiledirectory downloads a minimal amount of information about the dimensions of the environment you are logging onto and may be as large as 2 MB per user The profile directory is on the system drive and has limited space Byspecifying 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 individualserver 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 clientserver (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
44
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
Procedure
The following steps outline how to install the Planning and Consolidation clients in a Terminal Services (TS) or CitrixServer deployment
1 Make sure the Terminal Services or Citrix Server machine has the system requirements installed
2 Log on to the Terminal Services or Citrix Server machine with a user ID that has the rights to install on thatserver
3 At a command prompt enter Change userinstall
4 Open a browser and connect to the URL ltPC_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_MSBPCAdminMainexe
74 Creating a Shortcut to the Launch Page
Procedure
If you use published desktops instead of published applications the Planning and Consolidation desktop file (whichis installed on the current userrsquos desktop) must be moved to the All UsersDesktop folder
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 45
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 SQLServer 2012 support the remote modification of SSIS packages Planning and Consolidation also supports theremote 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 whichyou want to modify SSIS packages
These custom tasks reference dlls that connect to the database server and perform certain validation when usersset up the parameters of each task All the custom task reference components must also be installed in the machineon which you want to modify SSIS packages
We provide a program that registers all the reference components of the custom tasks This section explains theinstallation 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 ndash This folder contains all the dlls that should be installed on the machine There are Planning andConsolidation platform components and all of the Data Manager custom task files
Config folder ndash This folder contains only one file named Filelistxml and lists all of the files that should be installedIf you need to add or remove certain components from the installation you can modify this xml file
OSoftSetupexe ndash This is the main executable file to run the installation package
NoteIf you are not installing SSIS Custom Tasks on your client machine ndash specifically a machine other than the Planningand Consolidation application server ndash you must first install OSoftSSIS2008_Client or OSoftSSIS2012_Client onthe client machine followed by the SQL Server version If you want to use SQL 2008 Tasks under the SQL 2012environment you must install OSoftSSIS2008_Client on the application server For detailed information see SAPNote 1707410 You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package byextracting OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPCInstallation folder on the Planning and Consolidation server To modify SSIS packages on the Planning andConsolidation application server you need to install OSoftSSIS2008_Client or OSoftSSIS2012_Client for creatinga COM+ application For more information see Before You Modify the SSIS Packages [page 49] and Setup ofa COM+ Application on the Application Server [page 50]
Bin folder
This folder contains the following components
46
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Table 11
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012respectively
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
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 47
Name Remark
BPCWriteBackdll
InteropDTSdll
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 addmore components to the installation package you can copy the new components into the Bin folder and add theproper xml tags in FileListxml You need to enter information for the following tags
RegistType ndash This is the registration information of the component You can enter the following values
RegAsm ndash For NET component
48
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Regsvr32 ndash For VB6 component
Gacutil ndash For NET Framework component that should be registered into Global Assembly Cache
FileName ndash Component file name
OSoftSetupexe
This is the executable file to run the SSIS installation package Double-click the file to start the installation You needto enter information for the following fields
Set SQL server
Specify the SQL server name If your SQL Server has an instance specify the instance name
NoteIf you installed the OSoftSSIS2008_Client or OSoftSSIS2012_Client on the application server the SQL servername is automatically disabled
Set server credential
This is the credential name of the COM+ package component Enter the user ID and password that can accessyour SQL Server This should be either the System Admin ID or Admin ID that was registered as a COM+ userwhen 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 ifyou 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 packagesremotely This is also true for the application server that has SSIS installed The Planning and ConsolidationData Manager has the following custom tasks
Table 12
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008and 2012 respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and2012 respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012respectively
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 49
Name Remark
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and2012 respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008and 2012 respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL2008 and 2012 respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and2012 respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012respectively
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
ltdrivegtWebsrvrbin2 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 FilesMicrosoft SQLServer paste all files into the CProgram Files (x86)Microsoft SQL Server100DTSTasksfolder
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
50
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Typographic Conventions
Table 13
Example Description
lt gt Angle brackets indicate that you replace these words or characters with appropriate entries tomake entries in the system for example Enter your ltUser Namegt
File Save Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
Example Textual cross-references to an internet address for example wwwsapcom
example Quicklinks added to the internet address of a homepage to enable quick access to specificcontent 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 titlespushbutton 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 namesof installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transactioncodes database table names and key concepts of a programming language when they aresurrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
SAP Business Planning and Consolidation 100Typographic Conventions
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 51
52
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
wwwsapcom
Material Number
- SAP Business 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 2008 R2 2012 or 2012 R2
- 344 Removing Default Access to the Console
- 345 Management Console Access Control
- 346 Configuring Planning and Consolidation to use SSL
- 347 Using Client Certificates
- 348 Configuring MS SQL Server Reporting Services to use SSL
-
- 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
-
9 On your application server install Microsoft Visual C++ 2010 SP1 Redistributable Package (x64)
The Microsoft Visual C++ 2010 SP1 Redistributable Package (x64) installation package is contained in thePlanning and Consolidation zip file at the following location BPC SetupServervcredist_x64exe
NoteThe version of vcredist_x64exe in BPC SetupServer has been updated to 10040219 If you have aprevious 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 wwwmicrosoftcomdownloadsendetailsaspxFamilyID=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 Marketplaceat servicesapcompam Search on Planning and Consolidation
Business Planning and Consolidation can support all servers with an operating system in any language
NoteCurrently Business Planning and Consolidation does not support an operating system in bi-directionallanguages such as Hebrew
Procedure
If you are installing IIS 70 75 80 or 85 you must enable the following features
Enable Basic Authentication and Windows Authentication these are not installed by default
Install IIS 6 Metabase Compatibility role
Business Planning and Consolidation uses the ADSI provider to handle IIS administration such as virtualdirectory and security but IIS 7 does not install the ADSI provider by default
273 Installing the SQL Server
Prerequisites
During the installation procedure you have the opportunity to specify the location of the EnvironmentShell databasefile Check that it is possible to access EnvironmentShell from the location where you intend to install the SQL serverIf it is not possible for port access reasons (DMZ WORKGROUP or nontrusted domain authentication failures) copyEnvironmentShell to a location on the SQL server (for example CEnvironmentShelldb10) You specify thislocation on the Server Information page by choosing Server Information Advanced Options Local Path forEnvironmentShell DB
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 19
Procedure
This section describes the general steps for installing the SQL Server component options and considerations wheninstalling 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
NoteIf you encounter a 500 HTTP Error when trying to connect to the Planning and Consolidation Web Client referto Microsoft Support articles 2520479 and 2468871 for assistance
To reinforce security we recommend that you install the SQL server and SSAS components to a nondefaultinstance 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 Optionssection below then choose Next
4 Review disc space requirements then choose Next
5 In Server Configuration Perform the following actions
1 In the Service Accounts tab enter a Planning and Consolidation sysadmin account for the SQL ServerDatabase Engine and the SQL Server Analysis services This is required so that the Planning andConsolidation sysadmin can create and process the Planning and Consolidation database because theMicrosoft SQL server tries to back up or restore database with the privileged account This account is alsorequired 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 differentdomain 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 theapplication server and the account requires the folder access privilege for the application server
To ensure that you have the complete access privileges we recommend the Planning and Consolidationsysadmin 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 touse a restrictive SQL ID that works with the drill-through feature If you must restrict SQL authentication forsecurity 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 installationprogram
20
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
8 Choose Install to begin the installation with the options you have set
SQL Server Component Options
For Single-Machine Installations
Install the following components from the Feature Selection screen
Database Engine Services
Analysis Services
Integration Service which is listed as one of the Shared Features
For Multiple Machine Installations
For multiple machine installations install the following components on each server
Table 7
Server Component What to Install
SQL Server Database Engine Services
SSAS Server Analysis Services
Application Server The following Shared Features
Client Tools Connectivity
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 Server2008 R2 and SQL Server 2012
Process Dimension
It is now possible to process a dimension with multiple selections At processing time the process dimension modulemakes changed or added information for each dimension and process for all selected dimensions and cubes inparallel
Optimize Model
If there are custom partitions for a FACT partition in the OLAP database an optimization module can process custompartitions in parallel when Full or Incremental Optimize is performed However if a full optimize is performed withthe 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 parallelbecause 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 applicationserver and application set databases
NoteSetting the SQL isolation level to be Read Committed Snapshot mode for a database can only be done once andcannot be reversed
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 21
Real Time MOLAP
You can set the OLAP storage model of the write-back partition to be MOLAP (Multidimensional OLAP) This settingremains 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 asfollows
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 Servertrade20052008 which you can download from wwwmicrosoftcom (search on ldquoTable Partitioningrdquo to find all relevantarticles)
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 Thebrowser 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 localhostand external network interface machine
3 If you want to use IP1 which indicates Server IP set Enabled to Yes and specify the TCP Port as desired
4 Delete 0 from TCP Dynamic Ports Set IPAll - TCP Ports as desired (for example 1533)
RecommendationWe do not recommend using dynamic ports
In an SQL server the default instance has a listener which listens on a fixed port (TCP port 1433)However for the named instance the port on which the SQL server listens is random and dynamicallyselected when the named instance of the SQL server starts This recommendation prevents any conflictproblems
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 Setthe 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 thatthe user identified as the Log on as user has the sysadmin SQL Server role defined under Server Roles in theSQL Server Management Studio This is required so Analysis Services can process the SQL Server
From SQL Server Management Studio do the following tasks
22
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
1 If you want to use a port with a named instance select the server type Analysis Services select the servername (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 ServerProperties window displays which shows all configurable properties
3 For enhanced security change the default value to your port number (for example 2724) This means thatyou use a fixed port as for the SQL Server option Then choose OK
NoteWe do not support a nondefault port with the default instance in this release If you want to use the defaultinstance do not change the port number
Restart SQL and OLAP
Confirm that the installation has completed successfully by checking that there are no installation relatedproblems on the event viewer You can now install Planning and Consolidation
274 Installing Analysis Services
Procedure
After you install SQL Server and its required service packs and hotfixes you must install SQL Server Analysis Servicesand its required service packs and hotfixes
NoteIf you have migrated your Analysis Services repository to the SQL Server back up the database that contains therepository before installing this release
To install Analysis Services for SQL Server 2008 SQL Server 2008 R2 or SQL Server 2012 follow the steps andguidelines in technetmicrosoftcomen-uslibraryms143219aspx
To avoid slow performance when a user has more than six OLAP databases follow the steps and guidelines in thePerformance Guide for SQL 2008 at wwwmicrosoftcomdownloadsdetailsaspxFamilyID=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 tohave it available for the Planning and Consolidation installation program
1 Download the Anti-Cross Site Scripting Library file AntiXSSLibraryDLL from the Microsoft Web site atwwwmicrosoftcomdownloadendetailsaspxid=28589
2 Save the extracted file locally
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 23
When you install Planning and Consolidation Server a step in the process requires you to identify the path toAntiXssLibrarydll
28 Installing on a Single Server
When you install all Planning and Consolidation server components on a single server you should consider thefollowing 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 theuncompressed 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 Log on to the server with a local server user ID or domain user ID For more information see Logging on toservers [page 14]
3 Make sure all prerequisite software is installed on the server For more information see Installing thePrerequisites [page 17]
4 Obtain SAP Planning and Consolidation archive from the Downloads SAP Installations amp Upgrades areaof SAP Service Marketplace
5 Extract the files from the archive Go to the BPC Setup folder and run the StartUpexe file
6 From the Server Install screen select Install the Planning and Consolidation server
7 From the Welcome screen choose Next
8 From the License Agreement page choose I accept the terms of the license agreement then choose Next
9 From the Installation Method page accept the default Single machine enter a system ID for the systemlandscape directory (SLD) and choose Next
NoteEntering a system ID of the SLD is only required if you have a SAP Solution Manager license If you do nothave a SAP Solution Manager license you can leave this field empty
10 From the Authentication Method page choose the desired authentication method and choose Next
11 If you have chosen SAP BusinessObjects User Management System in the previous screen on the CMSAuthentication page enter the information required to log on to CMS as an administrator
The following information is required
24
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
Table 8
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 Thisgroup name is filtered as the default when adding a user in Planning andConsolidation Administration Use a comma ( ) to separate multiple names
12 After entering the CMS administrator authentication details choose Next
13 From the Service type accounts page enter service-level account user IDs and passwords See Service-LevelAccounts [page 15]
14 After defining the IDs and passwords choose Next
15 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 chooseNext
16 Specify the location and name of AntiXssLibrarydll See Installing the Anti-Cross Site ScriptingLibrary [page 23]
Choose Next
17 Select destination folders for Programs and Data The Data files include Webfolders and FileDB (publishedreports) and should be installed on a separate drive in a production environment This recommendation reducesthe hard disk IO time and helps to speed up SQL commands
Accept the defaults or make your selections then choose Next
18 Select the default values for the Web client The values are used to determine the default language and regionfor the Web client when you connect to it You can change the values in the Planning and Consolidation ServerManager
19 The installation process takes a few moments When it is complete choose Exit
20 A prompt is displayed to restart your computer Select OK to restart
21 Perform the steps in After Installing Planning and Consolidation Servers [page 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 avariety of ways and configure the servers as a Network Load Balancing (NLB) environment
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 25
The recommended Planning and Consolidation practice is to assign resources using a round robin approach for loadbalancing
You can install the SQL OLAP and FileShare types remotely from the application server You need to performadditional server installations if you have multiple application servers
Installing each Planning and Consolidation application server in a multiserver (NLB) configuration is identical to theprocedure 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 Balancingenvironment With this option there is an additional choice to Include sample environment (required on only oneof the application servers) This is because when you install the application server it connects to the databaseserver and creates the sample environment (EnvironmentShell) Installing the sample environment is requiredon 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
26
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
3 After Installing Planning and ConsolidationServers
31 Post-Installation Steps
Procedure
Perform these steps after installing the Planning and Consolidation servers for new installations of Planning andConsolidation
1 Connect your Planning and Consolidation system to Solution Manager Diagnostics (SMD) to allow support staffto identify analyze and resolve problems with your application See Connecting to Solution ManagerDiagnostics [page 28]
2 Configure the Planning and Consolidation NET and application server to ensure that it and its related servicesfunction properly and reliably For more information see Configuring the Planning and Consolidation NETApplication Server [page 29]
3 Optional configuration steps [page 29]
1 To ensure proper functioning of the Management Console create an SQL user and modify the System DSNand 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 loggingfor ODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default WebSite [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory canaccess the Management Console with whatever rights they have been granted on the server Forinformation about removing default access and creating a group that can access the console see RemovingDefault Access to the Console [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommendthat you only grant Management Console access to system administrators Planning and Consolidationusers should not have any access For more information see Management Console AccessControl [page 33]
6 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
4 Take the following steps to set up security
If you are defining security and application structure continue with step 5
If you want to designate someone other than the system administrator to manage security and applicationstructure log on to EnvironmentShell designate a user as a Primary Administrator
This user must have Administration ndash Environment and Security ‒ Define User task rights so that he or shecan 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 SeeInstalling the Administration Client [page 37]
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 27
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 taskprofiles 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 mustcomplete this step since there is no access to dimensions or members)
NoteTo allow users to request and query large amounts of data you can edit the metabasexml file located at CWindowssystem32inetsrv Set the following parameters to the stated values
ASPBUFFERINGLIMIT = 10485760
MAXREQUESTENTITYALLOWED = 10485760
32 Connecting to Solution Manager Diagnostics
NoteYou only need to perform the steps in this section if you have a SAP Solution Manager licence
The diagnostics functions in SAP Solution Manager allow identification analysis and resolution of problems Thisprocedure 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 areinstalled
NoteInstallation files for Diagnostics Agent are available on Service Marketplace by navigating to SupportPackages and Patches mdash Entry by Application Group SAP Technology Components SAP SOLUTIONMANAGER SAP SOLUTION MANAGER 70 EHP 1 Entry by Component Agents for managed systemsDIAGNOSTICS AGENT 711
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 whereMicrosoft 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
28
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
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 ServiceMarketplace at servicesapcom~sapidb011000358700000074392009E and follow the chapters that applyto Planning and Consolidation
33 Configuring the Planning and Consolidation NETApplication Servers
Procedure
Modifying machineconfig Files
To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock occurrences that wouldcause the application server to ldquosleeprdquo and not process anymore you can modify the machineconfig file whichresides in the WINDOWSMicrosoftNETFramework64v4030319Config directory
1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to specifywhether to automatically configure settings to achieve optimal performance based on the machineconfiguration You can set this attribute to True or False
For more information see msdnmicrosoftcomen-uslibrary7w2sway1aspx
2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the Planning andConsolidation application) or Machineconfig (for all applications including Planning and Consolidation) toensure the validationKey and decryptionKey keys have the same value on all application servers Thisway when the authentication cookie is checked the authentication ticket used on one server can still be validon another server
For more information and sample Visual Basic code for generating random key values seemsdnmicrosoftcomen-uslibraryms998288aspxpaght000007_webfarmdeploymentconsiderationsand msdnmicrosoftcomen-uslibraryms998310aspx
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 DSNand 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 forODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory can accessthe Management Console with whatever rights they have been granted on the server For information about
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 29
removing default access and creating a group that can access the console see Removing Default Access to theConsole [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommend thatyou only grant Management Console access to system administrators Planning and Consolidation users shouldnot have any access For more information see Management Console Access Control [page 33]
6 Configure the use of SSL in Planning and Consolidation See Configuring Planning and Consolidation to useSSL [page 34]
7 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
8 Configure Microsoft SQL Server Reporting Services to use SSL See Configuring MS SQL Server ReportingServices to use SSL [page 36]
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 databaserole 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 optionto use ODBC Logging Enter the following values
DSN is BPC_ManagementDSN Table is BPCLog The Microsoft SQL Server Username and Password
5 Restart IIS
NoteWithout these updates the Management Console does work but some functionality (specifically User Activityand Service Status) does not work as expected
Should you need to uninstall Planning and Consolidation we recommend that you reset the Active Log Formatfield in IIS to W3C Extended Log File Format
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
30
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
Prerequisites
ODBC logging has been configured according to the Microsoft Knowledge Base article 245243 How to configureODBC 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 inApplicationHostconfig as shown here
ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0logFormat=Custom gtUse 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-00AA006111E0appcmd 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 articlespecified in the Prerequisites section Configure these settings in the ltodbcLogginggt node underltsystemwebServergt
Exampleltlocation path=Default Web SitegtltsystemwebServergtltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog userName=Usernamepassword=mypassword gtltsystemwebServergtltlocationgt
Use the following AppCmds to configure these attributes for the default Web site
appcmd set config Default Web Site sectionodbcLogging dataSourceBPC_ManagementDSN commitappHostappcmd set config Default Web Site sectionodbcLogging tableNameBPCLog commitappHostappcmd set config Default Web Site sectionodbcLogging userNameUsername commitappHostappcmd set config Default Web Site sectionodbcLogging passwordmypassword commitappHost
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 31
NoteYou cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must use the SQL ServerODBC driver For more information see the Microsoft Knowledge Base article 931202 The requirements for usingthe ODBC logging feature in IIS
343 Setting Up an ODBC Data Source in Windows Server2008 2008 R2 2012 or 2012 R2
Procedure
This procedure describes how to set up an ODBC data source for the Management Console in Windows Server 20082008 R2 2012 or 2012 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
NoteIf you have chosen SAP BusinessObjects User Management System in the installation screen you do not needto remove or configure access because the Management Console service always runs with the System Admin IDaccount which is a member of the Administrators group
Procedure
To remove default access to the Management Console and create a group that does have access to the console usethe procedure described below
32
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
NoteCreate your Management Console administrative group either on the server that hosts the Management Consoleor 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
NoteAlternatively you can perform analogous steps in Active Directory
3 In the Groups context menu choose New Group
4 Enter data as required Click Create
5 In the Computer Management dialog box choose Services and Applications Internet InformationServices 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 objectand all child objects Include these with entries explicitly defined here checkbox
NoteThis step is a necessary precursor to the completion of this procedure
10 In the Security dialog box click Copy to ensure that the System group retains its privileges
11 Remove access to the Management Console from all groups that should not have it
12 Choose Authentication in the center pane then disable Windows authentication
Result
Users who have not been granted access to the Management Console can still open the Management Console Webpage but it contains no data or menu options This does not affect the access that a user would otherwise have toPlanning and Consolidation
345 Management Console Access Control
After establishing the Management Console group you can add users or groups to it For more information aboutcreating this group see Removing Default Access to the Console [page 32] Their rights in Active Directory determinewhat they can access in the Console
By default any member of the Administrators Active Directory group on the application server or domain has fullaccess to all of the features of the Console except the Planning and Consolidation logging area Access to Planningand Consolidation logging is controlled within the Planning and Consolidation Administration Client task securityThe user must be granted View system logs task privileges For more information see the SAP Library Planning and
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 33
Consolidation Administrators Guide in servicesapcominstguidesepm-bpc 100 version for the Microsoftplatform
Your IT policy determines whether you grant access by group or user You may wish to create several levels of Consoleusers (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 describedin this table
Table 9
Privilege Rights Management Area
Task Manager and Kill Process Administrators group on application server or domain
Performance Monitor Counters Administrators group on application server or domain
Power Users group on application server or domain
Performance Monitor Users group on application server
Microsoft Analysis Services performance monitoring Administrators group on application server or domain
Microsoft SQL Server Monitoring (performance counters andstatistics)
Administrators group on application server or domain
346 Configuring Planning and Consolidation to use SSL
Procedure
Creating a Certificate for the Server
During the handshake phase of the SSL communication the server must send its certificate to the client The clientthen uses the certificate to encrypt information and send it back to the server
The procedure below describes how to create a self-signed certificate for the server
RecommendationWe recommend that you limit the use of self-signed certificates to testing only For a productive system you shouldobtain a certificate signed by a well-known certification authority (CA)
1 Start the Internet Information Services (IIS) Manager To do that go to Start All Programs AdministrativeTools Internet Information Services (IIS) Manager
2 In the Connections panel on the left-hand side select the server node and then choose Server Certificates
3 In the Actions panel on the right hand side choose the Create Self-Signed Certificate action
4 Enter the name that you want the certificate to be identified by for example MyTestSSLCertificate
IIS generates a new SSL certificate for you that has one yearrsquos expiry lease The certificate is issued to the local servername
Binding the Certificate to the Web Site
The procedure below describes how to bind the certificate to the web site for which SSL connections must be used
1 In the Connections panel select the web site node
2 In the Actions panel choose Bindings
34
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
3 In the Site Bindings dialog that appears choose the Add button to create a new binding
4 Configure the parameters as follows
Type = https IP Address = [1] - this is a shorthand expression for the local server name
Port = 443 - this is the default SSL port
SSL Certificate = enter your newly created certificate name
5 Choose OK to create the new binding and then close the Site Bindings dialog
6 Restart the IIS processes To do this choose Restart from the Actions panel
7 In the middle panel under the IIS section choose SSL Settings
8 In the SSL Settings screen select the Require SSL checkbox
9 In the Actions panel choose to Apply these settings
To test the SSL connection in the Actions panel choose the Browse [1] 443 (https) link
347 Using Client Certificates
To enable the use of client certificates in Planning and Consolidation you must follow several manual steps
NotePlanning and Consolidation supports client certificate authentication in Windows Authentication Mode butdoes 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 technetmicrosoftcomen-uslibrarycc753810aspx
For more information about configuring the client certificate mapping authentication see technetmicrosoftcomen-uslibrarycc732996(WS10)aspx
When you create the client certificates you can set the type of certificate in the SSL Settings screen in InternetInformation Services (IIS) Manager
Procedure
1 Set the options for client certificates
1 In the IIS Manager select the web site where you installed Planning and Consolidation
2 Choose SSL Settings
3 In the Client certificates section select the Accept client certificates option
This option allows you to use a client certificate or username and password (Basic authentication) toconnect 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 theManagementConsole home page
3 Double-click Authentication and enable Anonymous Authentication
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 35
4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way asin step 3
5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the sameway 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
348 Configuring MS SQL Server Reporting Services to useSSL
Procedure
The procedure below describes how to configure the use of SSL in Microsoft SQL Server Reporting Services
NoteReporting Services does not provide functionalities for generating requesting or installing a certificate Theserver certificates that you want to use for configuring SSL must have already been installed on your computer
1 Open the Reporting Services Configuration Manager program To do this open the Windows Start menu andnavigate to All Programs Microsoft SQL Server ltversiongt Configuration Tools Reporting ServicesConfiguration Manager
2 In the Connect panel on the left-hand side select the Web Service URL option to open all the Report Server webservice parameters
3 Configure the parameters as follows
SSL Certificate = the name of the certificate that you want to use
SSL Port = 4434 Choose Apply to confirm the changes
5 In the Connect panel choose Report Manager URL to open the list of parameters that link Reporting Servicesto IIS
6 Choose Advanced to add your new SSL web URL
7 In the section Multiple SSL Identities for Report Manager choose Add Configure the parameters as follows
IP Address = (All IPv4) SSL Port = 443 Certificate = the name of your SSL certificate
8 To test the configuration click the URL that appears under the Report manager Site Identification section
36
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
4 Installing Planning and ConsolidationAdministration Client and the SAPBusinessObjects EPM solutions Add-in forMicrosoft Office
The installation of the Planning and Consolidation Administration Client allows administrators to build and maintainPlanning and Consolidation environments and models and administer security
All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions add-in forMicrosoft 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 valueof the Planning and Consolidation client to prompt for user name and password Otherwise the Planning andConsolidation Start Page does not display
41 Installing the Administration Client
Prerequisites
NoteFor a definitive list of system requirements see the Product Availability Matrix on SAP Service Marketplace atservicesapcompam Search on Planning and Consolidation
The following list describes the minimum software requirements
Microsoft Internet Explorer 70 80 90 or 10
Microsoft Office 2003 2007 2010 or 2012
NET Framework 20 or higher (install any required NET Framework Hotfixes by referring tosupportmicrosoftcomkb)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 37
NoteWe recommend that you install all of the latest Microsoft Windows hotfixes prior to installing the Administrationclient For information about which hotfixes to install see updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us
Procedure
The 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 ltPC_serverportgtsapbpcweb
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 mustdownload the most recent version of the full setup (EPM Add-inexe) from the Service Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPCInstallation folder
Individual users can install the EPM add-in on their own machines by going to the Planning and Consolidation Homepage 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 upthe 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
38
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
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 toperform the upgrade If Client Auto Update is not enabled and a newer version is detected clients must be installedmanually 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 andpassword in the Admin ID and Admin password fields respectively The Admin ID should be a member of thelocal administrators group on all the computers running the auto update This setting is not needed if all usershave 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 Thisoption is stored in the user preferences and may also be turned on or off using the User Optionshellip menu itemIf 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 toinstall 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 installit 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 servicesapcom
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 versionand policy information For a support package these files are
EPM Addin Support Package ltSP versiongtmsp EPM Addin Support Package ltSP versiongtxmlFor a patch these files are
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 (WebsrvrWebBPCInstallation)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 39
You can set a different update policy for each package listed
ExampleThe following table illustrates some possible situations assuming that you have installed the first full version(V1)
Table 10
Available maintenancepackages
V2-user update
V3-force update
V4-force update
V5-user update
V5-user update V5-user update
V6-auto update
V7-force update
Minimum RequiredVersion
V4 V4 V7
Notification A prompt tells the user toinstall maintenancepackage V4 using theForced Update behavior
If User Update is enabledthe prompt informs theuser that maintenancepackage V5 is available
A prompt tells the user toinstall maintenancepackage V7 using theForced Update behavior
New Version V4 V4 or V5 V7
If you change the update policy for any package click Update to complete the change
40
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
5 Connection Issues
You may experience connection problems with ports the proxy server or programs and settings that interact withthese components If you have any issues related to connection review the following recommendations andtroubleshooting tips
51 Checking for Open Ports
You must ensure that all required ports are open for inboundoutbound traffic By default Planning andConsolidation requires that Ports 80 (used by http) and 1433 and 2383 (used by SQL Server 2008) are open Totest whether the required ports are open go to a command prompt and enter the Telnet serveripaddress and portFor example Telnet 431181836 80 If the system returns a blank command window the port is open If it returnsa message stating that it is unable to connect the port is not open
NoteYou can use the following site to scan for the normal ports It allows you to manually enter a port number to test
wwwmyserverorgportsniffasp
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 Planningand Consolidation server as an exception You can do this at the client level ( Internet Explorer ToolsInternet 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 fullyqualified 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 Consolidationauthentication Do not use authentication on the proxy server The system synchronizes the user name andpassword on the remote server with the local user name and password
SAP Business Planning and Consolidation 100Connection Issues
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 41
NoteFor more information about setting up an ISA proxy server contact SAP Support to request a copy of Setting upISA Proxy Server White Paper For more information about Business Planning and Consolidation firewall portssee SAP Note 1505250
Internet Explorer Settings Issues
Internet Explorer settings must be set correctly to prevent errors and problems when you attempt to access thePlanning 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 insertthe IP address or fully qualified server name of the Planning and Consolidation server as an exception bychoosing 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
42
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Connection Issues
6 Installing Planning and Consolidation withTwo Active Directory Domains
To set up a Planning and Consolidation 10 application server in a hosted environment and use your own domainusers follow this procedure In general you install Planning and Consolidation on the host domain use the hostdomain account and assign it to the Planning and Consolidation users SysAdmin Admin and Users Then you acceptone 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 andpassword 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 topromote 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 privilegefor the Planning and Consolidation server
5 Install Planning and Consolidation and assign your domain account either to the three Planning andConsolidation administrative users SysAdmin Admin and Users or to only one of the three Planning andConsolidation administrative users and to three of your users Be sure you use your own user account ratherthan host domain users
Planning and Consolidation impersonation can then access your domain from the host environment becauseit has the privilege of your domain account
SAP Business Planning and Consolidation 100Installing Planning and Consolidation with Two Active Directory Domains
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 43
7 Installing Planning and Consolidation in aTerminal Services or Citrix ServerDeployment
This section describes best practices and instructions for installing Planning and Consolidation in a Terminal Servicesor Citrix Server deployment
71 Terminal Services Home Directories
We recommend using Terminal Server home directories rather than using the userrsquos profile directory The profiledirectory downloads a minimal amount of information about the dimensions of the environment you are logging onto and may be as large as 2 MB per user The profile directory is on the system drive and has limited space Byspecifying 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 individualserver 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 clientserver (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
44
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
Procedure
The following steps outline how to install the Planning and Consolidation clients in a Terminal Services (TS) or CitrixServer deployment
1 Make sure the Terminal Services or Citrix Server machine has the system requirements installed
2 Log on to the Terminal Services or Citrix Server machine with a user ID that has the rights to install on thatserver
3 At a command prompt enter Change userinstall
4 Open a browser and connect to the URL ltPC_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_MSBPCAdminMainexe
74 Creating a Shortcut to the Launch Page
Procedure
If you use published desktops instead of published applications the Planning and Consolidation desktop file (whichis installed on the current userrsquos desktop) must be moved to the All UsersDesktop folder
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 45
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 SQLServer 2012 support the remote modification of SSIS packages Planning and Consolidation also supports theremote 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 whichyou want to modify SSIS packages
These custom tasks reference dlls that connect to the database server and perform certain validation when usersset up the parameters of each task All the custom task reference components must also be installed in the machineon which you want to modify SSIS packages
We provide a program that registers all the reference components of the custom tasks This section explains theinstallation 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 ndash This folder contains all the dlls that should be installed on the machine There are Planning andConsolidation platform components and all of the Data Manager custom task files
Config folder ndash This folder contains only one file named Filelistxml and lists all of the files that should be installedIf you need to add or remove certain components from the installation you can modify this xml file
OSoftSetupexe ndash This is the main executable file to run the installation package
NoteIf you are not installing SSIS Custom Tasks on your client machine ndash specifically a machine other than the Planningand Consolidation application server ndash you must first install OSoftSSIS2008_Client or OSoftSSIS2012_Client onthe client machine followed by the SQL Server version If you want to use SQL 2008 Tasks under the SQL 2012environment you must install OSoftSSIS2008_Client on the application server For detailed information see SAPNote 1707410 You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package byextracting OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPCInstallation folder on the Planning and Consolidation server To modify SSIS packages on the Planning andConsolidation application server you need to install OSoftSSIS2008_Client or OSoftSSIS2012_Client for creatinga COM+ application For more information see Before You Modify the SSIS Packages [page 49] and Setup ofa COM+ Application on the Application Server [page 50]
Bin folder
This folder contains the following components
46
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Table 11
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012respectively
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
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 47
Name Remark
BPCWriteBackdll
InteropDTSdll
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 addmore components to the installation package you can copy the new components into the Bin folder and add theproper xml tags in FileListxml You need to enter information for the following tags
RegistType ndash This is the registration information of the component You can enter the following values
RegAsm ndash For NET component
48
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Regsvr32 ndash For VB6 component
Gacutil ndash For NET Framework component that should be registered into Global Assembly Cache
FileName ndash Component file name
OSoftSetupexe
This is the executable file to run the SSIS installation package Double-click the file to start the installation You needto enter information for the following fields
Set SQL server
Specify the SQL server name If your SQL Server has an instance specify the instance name
NoteIf you installed the OSoftSSIS2008_Client or OSoftSSIS2012_Client on the application server the SQL servername is automatically disabled
Set server credential
This is the credential name of the COM+ package component Enter the user ID and password that can accessyour SQL Server This should be either the System Admin ID or Admin ID that was registered as a COM+ userwhen 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 ifyou 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 packagesremotely This is also true for the application server that has SSIS installed The Planning and ConsolidationData Manager has the following custom tasks
Table 12
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008and 2012 respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and2012 respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012respectively
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 49
Name Remark
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and2012 respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008and 2012 respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL2008 and 2012 respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and2012 respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012respectively
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
ltdrivegtWebsrvrbin2 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 FilesMicrosoft SQLServer paste all files into the CProgram Files (x86)Microsoft SQL Server100DTSTasksfolder
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
50
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Typographic Conventions
Table 13
Example Description
lt gt Angle brackets indicate that you replace these words or characters with appropriate entries tomake entries in the system for example Enter your ltUser Namegt
File Save Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
Example Textual cross-references to an internet address for example wwwsapcom
example Quicklinks added to the internet address of a homepage to enable quick access to specificcontent 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 titlespushbutton 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 namesof installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transactioncodes database table names and key concepts of a programming language when they aresurrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
SAP Business Planning and Consolidation 100Typographic Conventions
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 51
52
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
wwwsapcom
Material Number
- SAP Business 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 2008 R2 2012 or 2012 R2
- 344 Removing Default Access to the Console
- 345 Management Console Access Control
- 346 Configuring Planning and Consolidation to use SSL
- 347 Using Client Certificates
- 348 Configuring MS SQL Server Reporting Services to use SSL
-
- 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
-
Procedure
This section describes the general steps for installing the SQL Server component options and considerations wheninstalling 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
NoteIf you encounter a 500 HTTP Error when trying to connect to the Planning and Consolidation Web Client referto Microsoft Support articles 2520479 and 2468871 for assistance
To reinforce security we recommend that you install the SQL server and SSAS components to a nondefaultinstance 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 Optionssection below then choose Next
4 Review disc space requirements then choose Next
5 In Server Configuration Perform the following actions
1 In the Service Accounts tab enter a Planning and Consolidation sysadmin account for the SQL ServerDatabase Engine and the SQL Server Analysis services This is required so that the Planning andConsolidation sysadmin can create and process the Planning and Consolidation database because theMicrosoft SQL server tries to back up or restore database with the privileged account This account is alsorequired 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 differentdomain 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 theapplication server and the account requires the folder access privilege for the application server
To ensure that you have the complete access privileges we recommend the Planning and Consolidationsysadmin 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 touse a restrictive SQL ID that works with the drill-through feature If you must restrict SQL authentication forsecurity 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 installationprogram
20
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
8 Choose Install to begin the installation with the options you have set
SQL Server Component Options
For Single-Machine Installations
Install the following components from the Feature Selection screen
Database Engine Services
Analysis Services
Integration Service which is listed as one of the Shared Features
For Multiple Machine Installations
For multiple machine installations install the following components on each server
Table 7
Server Component What to Install
SQL Server Database Engine Services
SSAS Server Analysis Services
Application Server The following Shared Features
Client Tools Connectivity
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 Server2008 R2 and SQL Server 2012
Process Dimension
It is now possible to process a dimension with multiple selections At processing time the process dimension modulemakes changed or added information for each dimension and process for all selected dimensions and cubes inparallel
Optimize Model
If there are custom partitions for a FACT partition in the OLAP database an optimization module can process custompartitions in parallel when Full or Incremental Optimize is performed However if a full optimize is performed withthe 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 parallelbecause 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 applicationserver and application set databases
NoteSetting the SQL isolation level to be Read Committed Snapshot mode for a database can only be done once andcannot be reversed
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 21
Real Time MOLAP
You can set the OLAP storage model of the write-back partition to be MOLAP (Multidimensional OLAP) This settingremains 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 asfollows
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 Servertrade20052008 which you can download from wwwmicrosoftcom (search on ldquoTable Partitioningrdquo to find all relevantarticles)
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 Thebrowser 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 localhostand external network interface machine
3 If you want to use IP1 which indicates Server IP set Enabled to Yes and specify the TCP Port as desired
4 Delete 0 from TCP Dynamic Ports Set IPAll - TCP Ports as desired (for example 1533)
RecommendationWe do not recommend using dynamic ports
In an SQL server the default instance has a listener which listens on a fixed port (TCP port 1433)However for the named instance the port on which the SQL server listens is random and dynamicallyselected when the named instance of the SQL server starts This recommendation prevents any conflictproblems
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 Setthe 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 thatthe user identified as the Log on as user has the sysadmin SQL Server role defined under Server Roles in theSQL Server Management Studio This is required so Analysis Services can process the SQL Server
From SQL Server Management Studio do the following tasks
22
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
1 If you want to use a port with a named instance select the server type Analysis Services select the servername (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 ServerProperties window displays which shows all configurable properties
3 For enhanced security change the default value to your port number (for example 2724) This means thatyou use a fixed port as for the SQL Server option Then choose OK
NoteWe do not support a nondefault port with the default instance in this release If you want to use the defaultinstance do not change the port number
Restart SQL and OLAP
Confirm that the installation has completed successfully by checking that there are no installation relatedproblems on the event viewer You can now install Planning and Consolidation
274 Installing Analysis Services
Procedure
After you install SQL Server and its required service packs and hotfixes you must install SQL Server Analysis Servicesand its required service packs and hotfixes
NoteIf you have migrated your Analysis Services repository to the SQL Server back up the database that contains therepository before installing this release
To install Analysis Services for SQL Server 2008 SQL Server 2008 R2 or SQL Server 2012 follow the steps andguidelines in technetmicrosoftcomen-uslibraryms143219aspx
To avoid slow performance when a user has more than six OLAP databases follow the steps and guidelines in thePerformance Guide for SQL 2008 at wwwmicrosoftcomdownloadsdetailsaspxFamilyID=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 tohave it available for the Planning and Consolidation installation program
1 Download the Anti-Cross Site Scripting Library file AntiXSSLibraryDLL from the Microsoft Web site atwwwmicrosoftcomdownloadendetailsaspxid=28589
2 Save the extracted file locally
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 23
When you install Planning and Consolidation Server a step in the process requires you to identify the path toAntiXssLibrarydll
28 Installing on a Single Server
When you install all Planning and Consolidation server components on a single server you should consider thefollowing 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 theuncompressed 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 Log on to the server with a local server user ID or domain user ID For more information see Logging on toservers [page 14]
3 Make sure all prerequisite software is installed on the server For more information see Installing thePrerequisites [page 17]
4 Obtain SAP Planning and Consolidation archive from the Downloads SAP Installations amp Upgrades areaof SAP Service Marketplace
5 Extract the files from the archive Go to the BPC Setup folder and run the StartUpexe file
6 From the Server Install screen select Install the Planning and Consolidation server
7 From the Welcome screen choose Next
8 From the License Agreement page choose I accept the terms of the license agreement then choose Next
9 From the Installation Method page accept the default Single machine enter a system ID for the systemlandscape directory (SLD) and choose Next
NoteEntering a system ID of the SLD is only required if you have a SAP Solution Manager license If you do nothave a SAP Solution Manager license you can leave this field empty
10 From the Authentication Method page choose the desired authentication method and choose Next
11 If you have chosen SAP BusinessObjects User Management System in the previous screen on the CMSAuthentication page enter the information required to log on to CMS as an administrator
The following information is required
24
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
Table 8
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 Thisgroup name is filtered as the default when adding a user in Planning andConsolidation Administration Use a comma ( ) to separate multiple names
12 After entering the CMS administrator authentication details choose Next
13 From the Service type accounts page enter service-level account user IDs and passwords See Service-LevelAccounts [page 15]
14 After defining the IDs and passwords choose Next
15 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 chooseNext
16 Specify the location and name of AntiXssLibrarydll See Installing the Anti-Cross Site ScriptingLibrary [page 23]
Choose Next
17 Select destination folders for Programs and Data The Data files include Webfolders and FileDB (publishedreports) and should be installed on a separate drive in a production environment This recommendation reducesthe hard disk IO time and helps to speed up SQL commands
Accept the defaults or make your selections then choose Next
18 Select the default values for the Web client The values are used to determine the default language and regionfor the Web client when you connect to it You can change the values in the Planning and Consolidation ServerManager
19 The installation process takes a few moments When it is complete choose Exit
20 A prompt is displayed to restart your computer Select OK to restart
21 Perform the steps in After Installing Planning and Consolidation Servers [page 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 avariety of ways and configure the servers as a Network Load Balancing (NLB) environment
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 25
The recommended Planning and Consolidation practice is to assign resources using a round robin approach for loadbalancing
You can install the SQL OLAP and FileShare types remotely from the application server You need to performadditional server installations if you have multiple application servers
Installing each Planning and Consolidation application server in a multiserver (NLB) configuration is identical to theprocedure 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 Balancingenvironment With this option there is an additional choice to Include sample environment (required on only oneof the application servers) This is because when you install the application server it connects to the databaseserver and creates the sample environment (EnvironmentShell) Installing the sample environment is requiredon 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
26
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
3 After Installing Planning and ConsolidationServers
31 Post-Installation Steps
Procedure
Perform these steps after installing the Planning and Consolidation servers for new installations of Planning andConsolidation
1 Connect your Planning and Consolidation system to Solution Manager Diagnostics (SMD) to allow support staffto identify analyze and resolve problems with your application See Connecting to Solution ManagerDiagnostics [page 28]
2 Configure the Planning and Consolidation NET and application server to ensure that it and its related servicesfunction properly and reliably For more information see Configuring the Planning and Consolidation NETApplication Server [page 29]
3 Optional configuration steps [page 29]
1 To ensure proper functioning of the Management Console create an SQL user and modify the System DSNand 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 loggingfor ODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default WebSite [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory canaccess the Management Console with whatever rights they have been granted on the server Forinformation about removing default access and creating a group that can access the console see RemovingDefault Access to the Console [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommendthat you only grant Management Console access to system administrators Planning and Consolidationusers should not have any access For more information see Management Console AccessControl [page 33]
6 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
4 Take the following steps to set up security
If you are defining security and application structure continue with step 5
If you want to designate someone other than the system administrator to manage security and applicationstructure log on to EnvironmentShell designate a user as a Primary Administrator
This user must have Administration ndash Environment and Security ‒ Define User task rights so that he or shecan 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 SeeInstalling the Administration Client [page 37]
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 27
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 taskprofiles 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 mustcomplete this step since there is no access to dimensions or members)
NoteTo allow users to request and query large amounts of data you can edit the metabasexml file located at CWindowssystem32inetsrv Set the following parameters to the stated values
ASPBUFFERINGLIMIT = 10485760
MAXREQUESTENTITYALLOWED = 10485760
32 Connecting to Solution Manager Diagnostics
NoteYou only need to perform the steps in this section if you have a SAP Solution Manager licence
The diagnostics functions in SAP Solution Manager allow identification analysis and resolution of problems Thisprocedure 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 areinstalled
NoteInstallation files for Diagnostics Agent are available on Service Marketplace by navigating to SupportPackages and Patches mdash Entry by Application Group SAP Technology Components SAP SOLUTIONMANAGER SAP SOLUTION MANAGER 70 EHP 1 Entry by Component Agents for managed systemsDIAGNOSTICS AGENT 711
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 whereMicrosoft 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
28
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
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 ServiceMarketplace at servicesapcom~sapidb011000358700000074392009E and follow the chapters that applyto Planning and Consolidation
33 Configuring the Planning and Consolidation NETApplication Servers
Procedure
Modifying machineconfig Files
To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock occurrences that wouldcause the application server to ldquosleeprdquo and not process anymore you can modify the machineconfig file whichresides in the WINDOWSMicrosoftNETFramework64v4030319Config directory
1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to specifywhether to automatically configure settings to achieve optimal performance based on the machineconfiguration You can set this attribute to True or False
For more information see msdnmicrosoftcomen-uslibrary7w2sway1aspx
2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the Planning andConsolidation application) or Machineconfig (for all applications including Planning and Consolidation) toensure the validationKey and decryptionKey keys have the same value on all application servers Thisway when the authentication cookie is checked the authentication ticket used on one server can still be validon another server
For more information and sample Visual Basic code for generating random key values seemsdnmicrosoftcomen-uslibraryms998288aspxpaght000007_webfarmdeploymentconsiderationsand msdnmicrosoftcomen-uslibraryms998310aspx
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 DSNand 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 forODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory can accessthe Management Console with whatever rights they have been granted on the server For information about
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 29
removing default access and creating a group that can access the console see Removing Default Access to theConsole [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommend thatyou only grant Management Console access to system administrators Planning and Consolidation users shouldnot have any access For more information see Management Console Access Control [page 33]
6 Configure the use of SSL in Planning and Consolidation See Configuring Planning and Consolidation to useSSL [page 34]
7 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
8 Configure Microsoft SQL Server Reporting Services to use SSL See Configuring MS SQL Server ReportingServices to use SSL [page 36]
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 databaserole 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 optionto use ODBC Logging Enter the following values
DSN is BPC_ManagementDSN Table is BPCLog The Microsoft SQL Server Username and Password
5 Restart IIS
NoteWithout these updates the Management Console does work but some functionality (specifically User Activityand Service Status) does not work as expected
Should you need to uninstall Planning and Consolidation we recommend that you reset the Active Log Formatfield in IIS to W3C Extended Log File Format
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
30
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
Prerequisites
ODBC logging has been configured according to the Microsoft Knowledge Base article 245243 How to configureODBC 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 inApplicationHostconfig as shown here
ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0logFormat=Custom gtUse 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-00AA006111E0appcmd 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 articlespecified in the Prerequisites section Configure these settings in the ltodbcLogginggt node underltsystemwebServergt
Exampleltlocation path=Default Web SitegtltsystemwebServergtltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog userName=Usernamepassword=mypassword gtltsystemwebServergtltlocationgt
Use the following AppCmds to configure these attributes for the default Web site
appcmd set config Default Web Site sectionodbcLogging dataSourceBPC_ManagementDSN commitappHostappcmd set config Default Web Site sectionodbcLogging tableNameBPCLog commitappHostappcmd set config Default Web Site sectionodbcLogging userNameUsername commitappHostappcmd set config Default Web Site sectionodbcLogging passwordmypassword commitappHost
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 31
NoteYou cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must use the SQL ServerODBC driver For more information see the Microsoft Knowledge Base article 931202 The requirements for usingthe ODBC logging feature in IIS
343 Setting Up an ODBC Data Source in Windows Server2008 2008 R2 2012 or 2012 R2
Procedure
This procedure describes how to set up an ODBC data source for the Management Console in Windows Server 20082008 R2 2012 or 2012 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
NoteIf you have chosen SAP BusinessObjects User Management System in the installation screen you do not needto remove or configure access because the Management Console service always runs with the System Admin IDaccount which is a member of the Administrators group
Procedure
To remove default access to the Management Console and create a group that does have access to the console usethe procedure described below
32
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
NoteCreate your Management Console administrative group either on the server that hosts the Management Consoleor 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
NoteAlternatively you can perform analogous steps in Active Directory
3 In the Groups context menu choose New Group
4 Enter data as required Click Create
5 In the Computer Management dialog box choose Services and Applications Internet InformationServices 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 objectand all child objects Include these with entries explicitly defined here checkbox
NoteThis step is a necessary precursor to the completion of this procedure
10 In the Security dialog box click Copy to ensure that the System group retains its privileges
11 Remove access to the Management Console from all groups that should not have it
12 Choose Authentication in the center pane then disable Windows authentication
Result
Users who have not been granted access to the Management Console can still open the Management Console Webpage but it contains no data or menu options This does not affect the access that a user would otherwise have toPlanning and Consolidation
345 Management Console Access Control
After establishing the Management Console group you can add users or groups to it For more information aboutcreating this group see Removing Default Access to the Console [page 32] Their rights in Active Directory determinewhat they can access in the Console
By default any member of the Administrators Active Directory group on the application server or domain has fullaccess to all of the features of the Console except the Planning and Consolidation logging area Access to Planningand Consolidation logging is controlled within the Planning and Consolidation Administration Client task securityThe user must be granted View system logs task privileges For more information see the SAP Library Planning and
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 33
Consolidation Administrators Guide in servicesapcominstguidesepm-bpc 100 version for the Microsoftplatform
Your IT policy determines whether you grant access by group or user You may wish to create several levels of Consoleusers (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 describedin this table
Table 9
Privilege Rights Management Area
Task Manager and Kill Process Administrators group on application server or domain
Performance Monitor Counters Administrators group on application server or domain
Power Users group on application server or domain
Performance Monitor Users group on application server
Microsoft Analysis Services performance monitoring Administrators group on application server or domain
Microsoft SQL Server Monitoring (performance counters andstatistics)
Administrators group on application server or domain
346 Configuring Planning and Consolidation to use SSL
Procedure
Creating a Certificate for the Server
During the handshake phase of the SSL communication the server must send its certificate to the client The clientthen uses the certificate to encrypt information and send it back to the server
The procedure below describes how to create a self-signed certificate for the server
RecommendationWe recommend that you limit the use of self-signed certificates to testing only For a productive system you shouldobtain a certificate signed by a well-known certification authority (CA)
1 Start the Internet Information Services (IIS) Manager To do that go to Start All Programs AdministrativeTools Internet Information Services (IIS) Manager
2 In the Connections panel on the left-hand side select the server node and then choose Server Certificates
3 In the Actions panel on the right hand side choose the Create Self-Signed Certificate action
4 Enter the name that you want the certificate to be identified by for example MyTestSSLCertificate
IIS generates a new SSL certificate for you that has one yearrsquos expiry lease The certificate is issued to the local servername
Binding the Certificate to the Web Site
The procedure below describes how to bind the certificate to the web site for which SSL connections must be used
1 In the Connections panel select the web site node
2 In the Actions panel choose Bindings
34
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
3 In the Site Bindings dialog that appears choose the Add button to create a new binding
4 Configure the parameters as follows
Type = https IP Address = [1] - this is a shorthand expression for the local server name
Port = 443 - this is the default SSL port
SSL Certificate = enter your newly created certificate name
5 Choose OK to create the new binding and then close the Site Bindings dialog
6 Restart the IIS processes To do this choose Restart from the Actions panel
7 In the middle panel under the IIS section choose SSL Settings
8 In the SSL Settings screen select the Require SSL checkbox
9 In the Actions panel choose to Apply these settings
To test the SSL connection in the Actions panel choose the Browse [1] 443 (https) link
347 Using Client Certificates
To enable the use of client certificates in Planning and Consolidation you must follow several manual steps
NotePlanning and Consolidation supports client certificate authentication in Windows Authentication Mode butdoes 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 technetmicrosoftcomen-uslibrarycc753810aspx
For more information about configuring the client certificate mapping authentication see technetmicrosoftcomen-uslibrarycc732996(WS10)aspx
When you create the client certificates you can set the type of certificate in the SSL Settings screen in InternetInformation Services (IIS) Manager
Procedure
1 Set the options for client certificates
1 In the IIS Manager select the web site where you installed Planning and Consolidation
2 Choose SSL Settings
3 In the Client certificates section select the Accept client certificates option
This option allows you to use a client certificate or username and password (Basic authentication) toconnect 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 theManagementConsole home page
3 Double-click Authentication and enable Anonymous Authentication
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 35
4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way asin step 3
5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the sameway 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
348 Configuring MS SQL Server Reporting Services to useSSL
Procedure
The procedure below describes how to configure the use of SSL in Microsoft SQL Server Reporting Services
NoteReporting Services does not provide functionalities for generating requesting or installing a certificate Theserver certificates that you want to use for configuring SSL must have already been installed on your computer
1 Open the Reporting Services Configuration Manager program To do this open the Windows Start menu andnavigate to All Programs Microsoft SQL Server ltversiongt Configuration Tools Reporting ServicesConfiguration Manager
2 In the Connect panel on the left-hand side select the Web Service URL option to open all the Report Server webservice parameters
3 Configure the parameters as follows
SSL Certificate = the name of the certificate that you want to use
SSL Port = 4434 Choose Apply to confirm the changes
5 In the Connect panel choose Report Manager URL to open the list of parameters that link Reporting Servicesto IIS
6 Choose Advanced to add your new SSL web URL
7 In the section Multiple SSL Identities for Report Manager choose Add Configure the parameters as follows
IP Address = (All IPv4) SSL Port = 443 Certificate = the name of your SSL certificate
8 To test the configuration click the URL that appears under the Report manager Site Identification section
36
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
4 Installing Planning and ConsolidationAdministration Client and the SAPBusinessObjects EPM solutions Add-in forMicrosoft Office
The installation of the Planning and Consolidation Administration Client allows administrators to build and maintainPlanning and Consolidation environments and models and administer security
All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions add-in forMicrosoft 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 valueof the Planning and Consolidation client to prompt for user name and password Otherwise the Planning andConsolidation Start Page does not display
41 Installing the Administration Client
Prerequisites
NoteFor a definitive list of system requirements see the Product Availability Matrix on SAP Service Marketplace atservicesapcompam Search on Planning and Consolidation
The following list describes the minimum software requirements
Microsoft Internet Explorer 70 80 90 or 10
Microsoft Office 2003 2007 2010 or 2012
NET Framework 20 or higher (install any required NET Framework Hotfixes by referring tosupportmicrosoftcomkb)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 37
NoteWe recommend that you install all of the latest Microsoft Windows hotfixes prior to installing the Administrationclient For information about which hotfixes to install see updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us
Procedure
The 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 ltPC_serverportgtsapbpcweb
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 mustdownload the most recent version of the full setup (EPM Add-inexe) from the Service Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPCInstallation folder
Individual users can install the EPM add-in on their own machines by going to the Planning and Consolidation Homepage 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 upthe 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
38
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
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 toperform the upgrade If Client Auto Update is not enabled and a newer version is detected clients must be installedmanually 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 andpassword in the Admin ID and Admin password fields respectively The Admin ID should be a member of thelocal administrators group on all the computers running the auto update This setting is not needed if all usershave 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 Thisoption is stored in the user preferences and may also be turned on or off using the User Optionshellip menu itemIf 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 toinstall 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 installit 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 servicesapcom
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 versionand policy information For a support package these files are
EPM Addin Support Package ltSP versiongtmsp EPM Addin Support Package ltSP versiongtxmlFor a patch these files are
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 (WebsrvrWebBPCInstallation)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 39
You can set a different update policy for each package listed
ExampleThe following table illustrates some possible situations assuming that you have installed the first full version(V1)
Table 10
Available maintenancepackages
V2-user update
V3-force update
V4-force update
V5-user update
V5-user update V5-user update
V6-auto update
V7-force update
Minimum RequiredVersion
V4 V4 V7
Notification A prompt tells the user toinstall maintenancepackage V4 using theForced Update behavior
If User Update is enabledthe prompt informs theuser that maintenancepackage V5 is available
A prompt tells the user toinstall maintenancepackage V7 using theForced Update behavior
New Version V4 V4 or V5 V7
If you change the update policy for any package click Update to complete the change
40
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
5 Connection Issues
You may experience connection problems with ports the proxy server or programs and settings that interact withthese components If you have any issues related to connection review the following recommendations andtroubleshooting tips
51 Checking for Open Ports
You must ensure that all required ports are open for inboundoutbound traffic By default Planning andConsolidation requires that Ports 80 (used by http) and 1433 and 2383 (used by SQL Server 2008) are open Totest whether the required ports are open go to a command prompt and enter the Telnet serveripaddress and portFor example Telnet 431181836 80 If the system returns a blank command window the port is open If it returnsa message stating that it is unable to connect the port is not open
NoteYou can use the following site to scan for the normal ports It allows you to manually enter a port number to test
wwwmyserverorgportsniffasp
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 Planningand Consolidation server as an exception You can do this at the client level ( Internet Explorer ToolsInternet 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 fullyqualified 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 Consolidationauthentication Do not use authentication on the proxy server The system synchronizes the user name andpassword on the remote server with the local user name and password
SAP Business Planning and Consolidation 100Connection Issues
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 41
NoteFor more information about setting up an ISA proxy server contact SAP Support to request a copy of Setting upISA Proxy Server White Paper For more information about Business Planning and Consolidation firewall portssee SAP Note 1505250
Internet Explorer Settings Issues
Internet Explorer settings must be set correctly to prevent errors and problems when you attempt to access thePlanning 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 insertthe IP address or fully qualified server name of the Planning and Consolidation server as an exception bychoosing 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
42
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Connection Issues
6 Installing Planning and Consolidation withTwo Active Directory Domains
To set up a Planning and Consolidation 10 application server in a hosted environment and use your own domainusers follow this procedure In general you install Planning and Consolidation on the host domain use the hostdomain account and assign it to the Planning and Consolidation users SysAdmin Admin and Users Then you acceptone 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 andpassword 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 topromote 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 privilegefor the Planning and Consolidation server
5 Install Planning and Consolidation and assign your domain account either to the three Planning andConsolidation administrative users SysAdmin Admin and Users or to only one of the three Planning andConsolidation administrative users and to three of your users Be sure you use your own user account ratherthan host domain users
Planning and Consolidation impersonation can then access your domain from the host environment becauseit has the privilege of your domain account
SAP Business Planning and Consolidation 100Installing Planning and Consolidation with Two Active Directory Domains
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 43
7 Installing Planning and Consolidation in aTerminal Services or Citrix ServerDeployment
This section describes best practices and instructions for installing Planning and Consolidation in a Terminal Servicesor Citrix Server deployment
71 Terminal Services Home Directories
We recommend using Terminal Server home directories rather than using the userrsquos profile directory The profiledirectory downloads a minimal amount of information about the dimensions of the environment you are logging onto and may be as large as 2 MB per user The profile directory is on the system drive and has limited space Byspecifying 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 individualserver 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 clientserver (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
44
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
Procedure
The following steps outline how to install the Planning and Consolidation clients in a Terminal Services (TS) or CitrixServer deployment
1 Make sure the Terminal Services or Citrix Server machine has the system requirements installed
2 Log on to the Terminal Services or Citrix Server machine with a user ID that has the rights to install on thatserver
3 At a command prompt enter Change userinstall
4 Open a browser and connect to the URL ltPC_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_MSBPCAdminMainexe
74 Creating a Shortcut to the Launch Page
Procedure
If you use published desktops instead of published applications the Planning and Consolidation desktop file (whichis installed on the current userrsquos desktop) must be moved to the All UsersDesktop folder
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 45
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 SQLServer 2012 support the remote modification of SSIS packages Planning and Consolidation also supports theremote 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 whichyou want to modify SSIS packages
These custom tasks reference dlls that connect to the database server and perform certain validation when usersset up the parameters of each task All the custom task reference components must also be installed in the machineon which you want to modify SSIS packages
We provide a program that registers all the reference components of the custom tasks This section explains theinstallation 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 ndash This folder contains all the dlls that should be installed on the machine There are Planning andConsolidation platform components and all of the Data Manager custom task files
Config folder ndash This folder contains only one file named Filelistxml and lists all of the files that should be installedIf you need to add or remove certain components from the installation you can modify this xml file
OSoftSetupexe ndash This is the main executable file to run the installation package
NoteIf you are not installing SSIS Custom Tasks on your client machine ndash specifically a machine other than the Planningand Consolidation application server ndash you must first install OSoftSSIS2008_Client or OSoftSSIS2012_Client onthe client machine followed by the SQL Server version If you want to use SQL 2008 Tasks under the SQL 2012environment you must install OSoftSSIS2008_Client on the application server For detailed information see SAPNote 1707410 You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package byextracting OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPCInstallation folder on the Planning and Consolidation server To modify SSIS packages on the Planning andConsolidation application server you need to install OSoftSSIS2008_Client or OSoftSSIS2012_Client for creatinga COM+ application For more information see Before You Modify the SSIS Packages [page 49] and Setup ofa COM+ Application on the Application Server [page 50]
Bin folder
This folder contains the following components
46
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Table 11
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012respectively
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
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 47
Name Remark
BPCWriteBackdll
InteropDTSdll
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 addmore components to the installation package you can copy the new components into the Bin folder and add theproper xml tags in FileListxml You need to enter information for the following tags
RegistType ndash This is the registration information of the component You can enter the following values
RegAsm ndash For NET component
48
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Regsvr32 ndash For VB6 component
Gacutil ndash For NET Framework component that should be registered into Global Assembly Cache
FileName ndash Component file name
OSoftSetupexe
This is the executable file to run the SSIS installation package Double-click the file to start the installation You needto enter information for the following fields
Set SQL server
Specify the SQL server name If your SQL Server has an instance specify the instance name
NoteIf you installed the OSoftSSIS2008_Client or OSoftSSIS2012_Client on the application server the SQL servername is automatically disabled
Set server credential
This is the credential name of the COM+ package component Enter the user ID and password that can accessyour SQL Server This should be either the System Admin ID or Admin ID that was registered as a COM+ userwhen 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 ifyou 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 packagesremotely This is also true for the application server that has SSIS installed The Planning and ConsolidationData Manager has the following custom tasks
Table 12
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008and 2012 respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and2012 respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012respectively
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 49
Name Remark
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and2012 respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008and 2012 respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL2008 and 2012 respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and2012 respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012respectively
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
ltdrivegtWebsrvrbin2 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 FilesMicrosoft SQLServer paste all files into the CProgram Files (x86)Microsoft SQL Server100DTSTasksfolder
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
50
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Typographic Conventions
Table 13
Example Description
lt gt Angle brackets indicate that you replace these words or characters with appropriate entries tomake entries in the system for example Enter your ltUser Namegt
File Save Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
Example Textual cross-references to an internet address for example wwwsapcom
example Quicklinks added to the internet address of a homepage to enable quick access to specificcontent 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 titlespushbutton 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 namesof installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transactioncodes database table names and key concepts of a programming language when they aresurrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
SAP Business Planning and Consolidation 100Typographic Conventions
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 51
52
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
wwwsapcom
Material Number
- SAP Business 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 2008 R2 2012 or 2012 R2
- 344 Removing Default Access to the Console
- 345 Management Console Access Control
- 346 Configuring Planning and Consolidation to use SSL
- 347 Using Client Certificates
- 348 Configuring MS SQL Server Reporting Services to use SSL
-
- 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
-
8 Choose Install to begin the installation with the options you have set
SQL Server Component Options
For Single-Machine Installations
Install the following components from the Feature Selection screen
Database Engine Services
Analysis Services
Integration Service which is listed as one of the Shared Features
For Multiple Machine Installations
For multiple machine installations install the following components on each server
Table 7
Server Component What to Install
SQL Server Database Engine Services
SSAS Server Analysis Services
Application Server The following Shared Features
Client Tools Connectivity
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 Server2008 R2 and SQL Server 2012
Process Dimension
It is now possible to process a dimension with multiple selections At processing time the process dimension modulemakes changed or added information for each dimension and process for all selected dimensions and cubes inparallel
Optimize Model
If there are custom partitions for a FACT partition in the OLAP database an optimization module can process custompartitions in parallel when Full or Incremental Optimize is performed However if a full optimize is performed withthe 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 parallelbecause 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 applicationserver and application set databases
NoteSetting the SQL isolation level to be Read Committed Snapshot mode for a database can only be done once andcannot be reversed
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 21
Real Time MOLAP
You can set the OLAP storage model of the write-back partition to be MOLAP (Multidimensional OLAP) This settingremains 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 asfollows
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 Servertrade20052008 which you can download from wwwmicrosoftcom (search on ldquoTable Partitioningrdquo to find all relevantarticles)
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 Thebrowser 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 localhostand external network interface machine
3 If you want to use IP1 which indicates Server IP set Enabled to Yes and specify the TCP Port as desired
4 Delete 0 from TCP Dynamic Ports Set IPAll - TCP Ports as desired (for example 1533)
RecommendationWe do not recommend using dynamic ports
In an SQL server the default instance has a listener which listens on a fixed port (TCP port 1433)However for the named instance the port on which the SQL server listens is random and dynamicallyselected when the named instance of the SQL server starts This recommendation prevents any conflictproblems
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 Setthe 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 thatthe user identified as the Log on as user has the sysadmin SQL Server role defined under Server Roles in theSQL Server Management Studio This is required so Analysis Services can process the SQL Server
From SQL Server Management Studio do the following tasks
22
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
1 If you want to use a port with a named instance select the server type Analysis Services select the servername (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 ServerProperties window displays which shows all configurable properties
3 For enhanced security change the default value to your port number (for example 2724) This means thatyou use a fixed port as for the SQL Server option Then choose OK
NoteWe do not support a nondefault port with the default instance in this release If you want to use the defaultinstance do not change the port number
Restart SQL and OLAP
Confirm that the installation has completed successfully by checking that there are no installation relatedproblems on the event viewer You can now install Planning and Consolidation
274 Installing Analysis Services
Procedure
After you install SQL Server and its required service packs and hotfixes you must install SQL Server Analysis Servicesand its required service packs and hotfixes
NoteIf you have migrated your Analysis Services repository to the SQL Server back up the database that contains therepository before installing this release
To install Analysis Services for SQL Server 2008 SQL Server 2008 R2 or SQL Server 2012 follow the steps andguidelines in technetmicrosoftcomen-uslibraryms143219aspx
To avoid slow performance when a user has more than six OLAP databases follow the steps and guidelines in thePerformance Guide for SQL 2008 at wwwmicrosoftcomdownloadsdetailsaspxFamilyID=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 tohave it available for the Planning and Consolidation installation program
1 Download the Anti-Cross Site Scripting Library file AntiXSSLibraryDLL from the Microsoft Web site atwwwmicrosoftcomdownloadendetailsaspxid=28589
2 Save the extracted file locally
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 23
When you install Planning and Consolidation Server a step in the process requires you to identify the path toAntiXssLibrarydll
28 Installing on a Single Server
When you install all Planning and Consolidation server components on a single server you should consider thefollowing 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 theuncompressed 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 Log on to the server with a local server user ID or domain user ID For more information see Logging on toservers [page 14]
3 Make sure all prerequisite software is installed on the server For more information see Installing thePrerequisites [page 17]
4 Obtain SAP Planning and Consolidation archive from the Downloads SAP Installations amp Upgrades areaof SAP Service Marketplace
5 Extract the files from the archive Go to the BPC Setup folder and run the StartUpexe file
6 From the Server Install screen select Install the Planning and Consolidation server
7 From the Welcome screen choose Next
8 From the License Agreement page choose I accept the terms of the license agreement then choose Next
9 From the Installation Method page accept the default Single machine enter a system ID for the systemlandscape directory (SLD) and choose Next
NoteEntering a system ID of the SLD is only required if you have a SAP Solution Manager license If you do nothave a SAP Solution Manager license you can leave this field empty
10 From the Authentication Method page choose the desired authentication method and choose Next
11 If you have chosen SAP BusinessObjects User Management System in the previous screen on the CMSAuthentication page enter the information required to log on to CMS as an administrator
The following information is required
24
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
Table 8
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 Thisgroup name is filtered as the default when adding a user in Planning andConsolidation Administration Use a comma ( ) to separate multiple names
12 After entering the CMS administrator authentication details choose Next
13 From the Service type accounts page enter service-level account user IDs and passwords See Service-LevelAccounts [page 15]
14 After defining the IDs and passwords choose Next
15 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 chooseNext
16 Specify the location and name of AntiXssLibrarydll See Installing the Anti-Cross Site ScriptingLibrary [page 23]
Choose Next
17 Select destination folders for Programs and Data The Data files include Webfolders and FileDB (publishedreports) and should be installed on a separate drive in a production environment This recommendation reducesthe hard disk IO time and helps to speed up SQL commands
Accept the defaults or make your selections then choose Next
18 Select the default values for the Web client The values are used to determine the default language and regionfor the Web client when you connect to it You can change the values in the Planning and Consolidation ServerManager
19 The installation process takes a few moments When it is complete choose Exit
20 A prompt is displayed to restart your computer Select OK to restart
21 Perform the steps in After Installing Planning and Consolidation Servers [page 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 avariety of ways and configure the servers as a Network Load Balancing (NLB) environment
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 25
The recommended Planning and Consolidation practice is to assign resources using a round robin approach for loadbalancing
You can install the SQL OLAP and FileShare types remotely from the application server You need to performadditional server installations if you have multiple application servers
Installing each Planning and Consolidation application server in a multiserver (NLB) configuration is identical to theprocedure 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 Balancingenvironment With this option there is an additional choice to Include sample environment (required on only oneof the application servers) This is because when you install the application server it connects to the databaseserver and creates the sample environment (EnvironmentShell) Installing the sample environment is requiredon 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
26
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
3 After Installing Planning and ConsolidationServers
31 Post-Installation Steps
Procedure
Perform these steps after installing the Planning and Consolidation servers for new installations of Planning andConsolidation
1 Connect your Planning and Consolidation system to Solution Manager Diagnostics (SMD) to allow support staffto identify analyze and resolve problems with your application See Connecting to Solution ManagerDiagnostics [page 28]
2 Configure the Planning and Consolidation NET and application server to ensure that it and its related servicesfunction properly and reliably For more information see Configuring the Planning and Consolidation NETApplication Server [page 29]
3 Optional configuration steps [page 29]
1 To ensure proper functioning of the Management Console create an SQL user and modify the System DSNand 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 loggingfor ODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default WebSite [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory canaccess the Management Console with whatever rights they have been granted on the server Forinformation about removing default access and creating a group that can access the console see RemovingDefault Access to the Console [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommendthat you only grant Management Console access to system administrators Planning and Consolidationusers should not have any access For more information see Management Console AccessControl [page 33]
6 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
4 Take the following steps to set up security
If you are defining security and application structure continue with step 5
If you want to designate someone other than the system administrator to manage security and applicationstructure log on to EnvironmentShell designate a user as a Primary Administrator
This user must have Administration ndash Environment and Security ‒ Define User task rights so that he or shecan 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 SeeInstalling the Administration Client [page 37]
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 27
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 taskprofiles 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 mustcomplete this step since there is no access to dimensions or members)
NoteTo allow users to request and query large amounts of data you can edit the metabasexml file located at CWindowssystem32inetsrv Set the following parameters to the stated values
ASPBUFFERINGLIMIT = 10485760
MAXREQUESTENTITYALLOWED = 10485760
32 Connecting to Solution Manager Diagnostics
NoteYou only need to perform the steps in this section if you have a SAP Solution Manager licence
The diagnostics functions in SAP Solution Manager allow identification analysis and resolution of problems Thisprocedure 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 areinstalled
NoteInstallation files for Diagnostics Agent are available on Service Marketplace by navigating to SupportPackages and Patches mdash Entry by Application Group SAP Technology Components SAP SOLUTIONMANAGER SAP SOLUTION MANAGER 70 EHP 1 Entry by Component Agents for managed systemsDIAGNOSTICS AGENT 711
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 whereMicrosoft 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
28
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
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 ServiceMarketplace at servicesapcom~sapidb011000358700000074392009E and follow the chapters that applyto Planning and Consolidation
33 Configuring the Planning and Consolidation NETApplication Servers
Procedure
Modifying machineconfig Files
To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock occurrences that wouldcause the application server to ldquosleeprdquo and not process anymore you can modify the machineconfig file whichresides in the WINDOWSMicrosoftNETFramework64v4030319Config directory
1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to specifywhether to automatically configure settings to achieve optimal performance based on the machineconfiguration You can set this attribute to True or False
For more information see msdnmicrosoftcomen-uslibrary7w2sway1aspx
2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the Planning andConsolidation application) or Machineconfig (for all applications including Planning and Consolidation) toensure the validationKey and decryptionKey keys have the same value on all application servers Thisway when the authentication cookie is checked the authentication ticket used on one server can still be validon another server
For more information and sample Visual Basic code for generating random key values seemsdnmicrosoftcomen-uslibraryms998288aspxpaght000007_webfarmdeploymentconsiderationsand msdnmicrosoftcomen-uslibraryms998310aspx
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 DSNand 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 forODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory can accessthe Management Console with whatever rights they have been granted on the server For information about
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 29
removing default access and creating a group that can access the console see Removing Default Access to theConsole [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommend thatyou only grant Management Console access to system administrators Planning and Consolidation users shouldnot have any access For more information see Management Console Access Control [page 33]
6 Configure the use of SSL in Planning and Consolidation See Configuring Planning and Consolidation to useSSL [page 34]
7 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
8 Configure Microsoft SQL Server Reporting Services to use SSL See Configuring MS SQL Server ReportingServices to use SSL [page 36]
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 databaserole 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 optionto use ODBC Logging Enter the following values
DSN is BPC_ManagementDSN Table is BPCLog The Microsoft SQL Server Username and Password
5 Restart IIS
NoteWithout these updates the Management Console does work but some functionality (specifically User Activityand Service Status) does not work as expected
Should you need to uninstall Planning and Consolidation we recommend that you reset the Active Log Formatfield in IIS to W3C Extended Log File Format
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
30
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
Prerequisites
ODBC logging has been configured according to the Microsoft Knowledge Base article 245243 How to configureODBC 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 inApplicationHostconfig as shown here
ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0logFormat=Custom gtUse 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-00AA006111E0appcmd 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 articlespecified in the Prerequisites section Configure these settings in the ltodbcLogginggt node underltsystemwebServergt
Exampleltlocation path=Default Web SitegtltsystemwebServergtltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog userName=Usernamepassword=mypassword gtltsystemwebServergtltlocationgt
Use the following AppCmds to configure these attributes for the default Web site
appcmd set config Default Web Site sectionodbcLogging dataSourceBPC_ManagementDSN commitappHostappcmd set config Default Web Site sectionodbcLogging tableNameBPCLog commitappHostappcmd set config Default Web Site sectionodbcLogging userNameUsername commitappHostappcmd set config Default Web Site sectionodbcLogging passwordmypassword commitappHost
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 31
NoteYou cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must use the SQL ServerODBC driver For more information see the Microsoft Knowledge Base article 931202 The requirements for usingthe ODBC logging feature in IIS
343 Setting Up an ODBC Data Source in Windows Server2008 2008 R2 2012 or 2012 R2
Procedure
This procedure describes how to set up an ODBC data source for the Management Console in Windows Server 20082008 R2 2012 or 2012 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
NoteIf you have chosen SAP BusinessObjects User Management System in the installation screen you do not needto remove or configure access because the Management Console service always runs with the System Admin IDaccount which is a member of the Administrators group
Procedure
To remove default access to the Management Console and create a group that does have access to the console usethe procedure described below
32
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
NoteCreate your Management Console administrative group either on the server that hosts the Management Consoleor 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
NoteAlternatively you can perform analogous steps in Active Directory
3 In the Groups context menu choose New Group
4 Enter data as required Click Create
5 In the Computer Management dialog box choose Services and Applications Internet InformationServices 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 objectand all child objects Include these with entries explicitly defined here checkbox
NoteThis step is a necessary precursor to the completion of this procedure
10 In the Security dialog box click Copy to ensure that the System group retains its privileges
11 Remove access to the Management Console from all groups that should not have it
12 Choose Authentication in the center pane then disable Windows authentication
Result
Users who have not been granted access to the Management Console can still open the Management Console Webpage but it contains no data or menu options This does not affect the access that a user would otherwise have toPlanning and Consolidation
345 Management Console Access Control
After establishing the Management Console group you can add users or groups to it For more information aboutcreating this group see Removing Default Access to the Console [page 32] Their rights in Active Directory determinewhat they can access in the Console
By default any member of the Administrators Active Directory group on the application server or domain has fullaccess to all of the features of the Console except the Planning and Consolidation logging area Access to Planningand Consolidation logging is controlled within the Planning and Consolidation Administration Client task securityThe user must be granted View system logs task privileges For more information see the SAP Library Planning and
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 33
Consolidation Administrators Guide in servicesapcominstguidesepm-bpc 100 version for the Microsoftplatform
Your IT policy determines whether you grant access by group or user You may wish to create several levels of Consoleusers (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 describedin this table
Table 9
Privilege Rights Management Area
Task Manager and Kill Process Administrators group on application server or domain
Performance Monitor Counters Administrators group on application server or domain
Power Users group on application server or domain
Performance Monitor Users group on application server
Microsoft Analysis Services performance monitoring Administrators group on application server or domain
Microsoft SQL Server Monitoring (performance counters andstatistics)
Administrators group on application server or domain
346 Configuring Planning and Consolidation to use SSL
Procedure
Creating a Certificate for the Server
During the handshake phase of the SSL communication the server must send its certificate to the client The clientthen uses the certificate to encrypt information and send it back to the server
The procedure below describes how to create a self-signed certificate for the server
RecommendationWe recommend that you limit the use of self-signed certificates to testing only For a productive system you shouldobtain a certificate signed by a well-known certification authority (CA)
1 Start the Internet Information Services (IIS) Manager To do that go to Start All Programs AdministrativeTools Internet Information Services (IIS) Manager
2 In the Connections panel on the left-hand side select the server node and then choose Server Certificates
3 In the Actions panel on the right hand side choose the Create Self-Signed Certificate action
4 Enter the name that you want the certificate to be identified by for example MyTestSSLCertificate
IIS generates a new SSL certificate for you that has one yearrsquos expiry lease The certificate is issued to the local servername
Binding the Certificate to the Web Site
The procedure below describes how to bind the certificate to the web site for which SSL connections must be used
1 In the Connections panel select the web site node
2 In the Actions panel choose Bindings
34
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
3 In the Site Bindings dialog that appears choose the Add button to create a new binding
4 Configure the parameters as follows
Type = https IP Address = [1] - this is a shorthand expression for the local server name
Port = 443 - this is the default SSL port
SSL Certificate = enter your newly created certificate name
5 Choose OK to create the new binding and then close the Site Bindings dialog
6 Restart the IIS processes To do this choose Restart from the Actions panel
7 In the middle panel under the IIS section choose SSL Settings
8 In the SSL Settings screen select the Require SSL checkbox
9 In the Actions panel choose to Apply these settings
To test the SSL connection in the Actions panel choose the Browse [1] 443 (https) link
347 Using Client Certificates
To enable the use of client certificates in Planning and Consolidation you must follow several manual steps
NotePlanning and Consolidation supports client certificate authentication in Windows Authentication Mode butdoes 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 technetmicrosoftcomen-uslibrarycc753810aspx
For more information about configuring the client certificate mapping authentication see technetmicrosoftcomen-uslibrarycc732996(WS10)aspx
When you create the client certificates you can set the type of certificate in the SSL Settings screen in InternetInformation Services (IIS) Manager
Procedure
1 Set the options for client certificates
1 In the IIS Manager select the web site where you installed Planning and Consolidation
2 Choose SSL Settings
3 In the Client certificates section select the Accept client certificates option
This option allows you to use a client certificate or username and password (Basic authentication) toconnect 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 theManagementConsole home page
3 Double-click Authentication and enable Anonymous Authentication
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 35
4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way asin step 3
5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the sameway 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
348 Configuring MS SQL Server Reporting Services to useSSL
Procedure
The procedure below describes how to configure the use of SSL in Microsoft SQL Server Reporting Services
NoteReporting Services does not provide functionalities for generating requesting or installing a certificate Theserver certificates that you want to use for configuring SSL must have already been installed on your computer
1 Open the Reporting Services Configuration Manager program To do this open the Windows Start menu andnavigate to All Programs Microsoft SQL Server ltversiongt Configuration Tools Reporting ServicesConfiguration Manager
2 In the Connect panel on the left-hand side select the Web Service URL option to open all the Report Server webservice parameters
3 Configure the parameters as follows
SSL Certificate = the name of the certificate that you want to use
SSL Port = 4434 Choose Apply to confirm the changes
5 In the Connect panel choose Report Manager URL to open the list of parameters that link Reporting Servicesto IIS
6 Choose Advanced to add your new SSL web URL
7 In the section Multiple SSL Identities for Report Manager choose Add Configure the parameters as follows
IP Address = (All IPv4) SSL Port = 443 Certificate = the name of your SSL certificate
8 To test the configuration click the URL that appears under the Report manager Site Identification section
36
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
4 Installing Planning and ConsolidationAdministration Client and the SAPBusinessObjects EPM solutions Add-in forMicrosoft Office
The installation of the Planning and Consolidation Administration Client allows administrators to build and maintainPlanning and Consolidation environments and models and administer security
All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions add-in forMicrosoft 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 valueof the Planning and Consolidation client to prompt for user name and password Otherwise the Planning andConsolidation Start Page does not display
41 Installing the Administration Client
Prerequisites
NoteFor a definitive list of system requirements see the Product Availability Matrix on SAP Service Marketplace atservicesapcompam Search on Planning and Consolidation
The following list describes the minimum software requirements
Microsoft Internet Explorer 70 80 90 or 10
Microsoft Office 2003 2007 2010 or 2012
NET Framework 20 or higher (install any required NET Framework Hotfixes by referring tosupportmicrosoftcomkb)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 37
NoteWe recommend that you install all of the latest Microsoft Windows hotfixes prior to installing the Administrationclient For information about which hotfixes to install see updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us
Procedure
The 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 ltPC_serverportgtsapbpcweb
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 mustdownload the most recent version of the full setup (EPM Add-inexe) from the Service Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPCInstallation folder
Individual users can install the EPM add-in on their own machines by going to the Planning and Consolidation Homepage 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 upthe 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
38
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
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 toperform the upgrade If Client Auto Update is not enabled and a newer version is detected clients must be installedmanually 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 andpassword in the Admin ID and Admin password fields respectively The Admin ID should be a member of thelocal administrators group on all the computers running the auto update This setting is not needed if all usershave 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 Thisoption is stored in the user preferences and may also be turned on or off using the User Optionshellip menu itemIf 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 toinstall 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 installit 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 servicesapcom
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 versionand policy information For a support package these files are
EPM Addin Support Package ltSP versiongtmsp EPM Addin Support Package ltSP versiongtxmlFor a patch these files are
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 (WebsrvrWebBPCInstallation)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 39
You can set a different update policy for each package listed
ExampleThe following table illustrates some possible situations assuming that you have installed the first full version(V1)
Table 10
Available maintenancepackages
V2-user update
V3-force update
V4-force update
V5-user update
V5-user update V5-user update
V6-auto update
V7-force update
Minimum RequiredVersion
V4 V4 V7
Notification A prompt tells the user toinstall maintenancepackage V4 using theForced Update behavior
If User Update is enabledthe prompt informs theuser that maintenancepackage V5 is available
A prompt tells the user toinstall maintenancepackage V7 using theForced Update behavior
New Version V4 V4 or V5 V7
If you change the update policy for any package click Update to complete the change
40
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
5 Connection Issues
You may experience connection problems with ports the proxy server or programs and settings that interact withthese components If you have any issues related to connection review the following recommendations andtroubleshooting tips
51 Checking for Open Ports
You must ensure that all required ports are open for inboundoutbound traffic By default Planning andConsolidation requires that Ports 80 (used by http) and 1433 and 2383 (used by SQL Server 2008) are open Totest whether the required ports are open go to a command prompt and enter the Telnet serveripaddress and portFor example Telnet 431181836 80 If the system returns a blank command window the port is open If it returnsa message stating that it is unable to connect the port is not open
NoteYou can use the following site to scan for the normal ports It allows you to manually enter a port number to test
wwwmyserverorgportsniffasp
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 Planningand Consolidation server as an exception You can do this at the client level ( Internet Explorer ToolsInternet 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 fullyqualified 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 Consolidationauthentication Do not use authentication on the proxy server The system synchronizes the user name andpassword on the remote server with the local user name and password
SAP Business Planning and Consolidation 100Connection Issues
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 41
NoteFor more information about setting up an ISA proxy server contact SAP Support to request a copy of Setting upISA Proxy Server White Paper For more information about Business Planning and Consolidation firewall portssee SAP Note 1505250
Internet Explorer Settings Issues
Internet Explorer settings must be set correctly to prevent errors and problems when you attempt to access thePlanning 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 insertthe IP address or fully qualified server name of the Planning and Consolidation server as an exception bychoosing 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
42
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Connection Issues
6 Installing Planning and Consolidation withTwo Active Directory Domains
To set up a Planning and Consolidation 10 application server in a hosted environment and use your own domainusers follow this procedure In general you install Planning and Consolidation on the host domain use the hostdomain account and assign it to the Planning and Consolidation users SysAdmin Admin and Users Then you acceptone 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 andpassword 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 topromote 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 privilegefor the Planning and Consolidation server
5 Install Planning and Consolidation and assign your domain account either to the three Planning andConsolidation administrative users SysAdmin Admin and Users or to only one of the three Planning andConsolidation administrative users and to three of your users Be sure you use your own user account ratherthan host domain users
Planning and Consolidation impersonation can then access your domain from the host environment becauseit has the privilege of your domain account
SAP Business Planning and Consolidation 100Installing Planning and Consolidation with Two Active Directory Domains
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 43
7 Installing Planning and Consolidation in aTerminal Services or Citrix ServerDeployment
This section describes best practices and instructions for installing Planning and Consolidation in a Terminal Servicesor Citrix Server deployment
71 Terminal Services Home Directories
We recommend using Terminal Server home directories rather than using the userrsquos profile directory The profiledirectory downloads a minimal amount of information about the dimensions of the environment you are logging onto and may be as large as 2 MB per user The profile directory is on the system drive and has limited space Byspecifying 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 individualserver 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 clientserver (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
44
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
Procedure
The following steps outline how to install the Planning and Consolidation clients in a Terminal Services (TS) or CitrixServer deployment
1 Make sure the Terminal Services or Citrix Server machine has the system requirements installed
2 Log on to the Terminal Services or Citrix Server machine with a user ID that has the rights to install on thatserver
3 At a command prompt enter Change userinstall
4 Open a browser and connect to the URL ltPC_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_MSBPCAdminMainexe
74 Creating a Shortcut to the Launch Page
Procedure
If you use published desktops instead of published applications the Planning and Consolidation desktop file (whichis installed on the current userrsquos desktop) must be moved to the All UsersDesktop folder
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 45
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 SQLServer 2012 support the remote modification of SSIS packages Planning and Consolidation also supports theremote 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 whichyou want to modify SSIS packages
These custom tasks reference dlls that connect to the database server and perform certain validation when usersset up the parameters of each task All the custom task reference components must also be installed in the machineon which you want to modify SSIS packages
We provide a program that registers all the reference components of the custom tasks This section explains theinstallation 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 ndash This folder contains all the dlls that should be installed on the machine There are Planning andConsolidation platform components and all of the Data Manager custom task files
Config folder ndash This folder contains only one file named Filelistxml and lists all of the files that should be installedIf you need to add or remove certain components from the installation you can modify this xml file
OSoftSetupexe ndash This is the main executable file to run the installation package
NoteIf you are not installing SSIS Custom Tasks on your client machine ndash specifically a machine other than the Planningand Consolidation application server ndash you must first install OSoftSSIS2008_Client or OSoftSSIS2012_Client onthe client machine followed by the SQL Server version If you want to use SQL 2008 Tasks under the SQL 2012environment you must install OSoftSSIS2008_Client on the application server For detailed information see SAPNote 1707410 You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package byextracting OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPCInstallation folder on the Planning and Consolidation server To modify SSIS packages on the Planning andConsolidation application server you need to install OSoftSSIS2008_Client or OSoftSSIS2012_Client for creatinga COM+ application For more information see Before You Modify the SSIS Packages [page 49] and Setup ofa COM+ Application on the Application Server [page 50]
Bin folder
This folder contains the following components
46
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Table 11
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012respectively
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
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 47
Name Remark
BPCWriteBackdll
InteropDTSdll
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 addmore components to the installation package you can copy the new components into the Bin folder and add theproper xml tags in FileListxml You need to enter information for the following tags
RegistType ndash This is the registration information of the component You can enter the following values
RegAsm ndash For NET component
48
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Regsvr32 ndash For VB6 component
Gacutil ndash For NET Framework component that should be registered into Global Assembly Cache
FileName ndash Component file name
OSoftSetupexe
This is the executable file to run the SSIS installation package Double-click the file to start the installation You needto enter information for the following fields
Set SQL server
Specify the SQL server name If your SQL Server has an instance specify the instance name
NoteIf you installed the OSoftSSIS2008_Client or OSoftSSIS2012_Client on the application server the SQL servername is automatically disabled
Set server credential
This is the credential name of the COM+ package component Enter the user ID and password that can accessyour SQL Server This should be either the System Admin ID or Admin ID that was registered as a COM+ userwhen 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 ifyou 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 packagesremotely This is also true for the application server that has SSIS installed The Planning and ConsolidationData Manager has the following custom tasks
Table 12
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008and 2012 respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and2012 respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012respectively
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 49
Name Remark
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and2012 respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008and 2012 respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL2008 and 2012 respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and2012 respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012respectively
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
ltdrivegtWebsrvrbin2 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 FilesMicrosoft SQLServer paste all files into the CProgram Files (x86)Microsoft SQL Server100DTSTasksfolder
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
50
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Typographic Conventions
Table 13
Example Description
lt gt Angle brackets indicate that you replace these words or characters with appropriate entries tomake entries in the system for example Enter your ltUser Namegt
File Save Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
Example Textual cross-references to an internet address for example wwwsapcom
example Quicklinks added to the internet address of a homepage to enable quick access to specificcontent 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 titlespushbutton 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 namesof installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transactioncodes database table names and key concepts of a programming language when they aresurrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
SAP Business Planning and Consolidation 100Typographic Conventions
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 51
52
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
wwwsapcom
Material Number
- SAP Business 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 2008 R2 2012 or 2012 R2
- 344 Removing Default Access to the Console
- 345 Management Console Access Control
- 346 Configuring Planning and Consolidation to use SSL
- 347 Using Client Certificates
- 348 Configuring MS SQL Server Reporting Services to use SSL
-
- 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
-
Real Time MOLAP
You can set the OLAP storage model of the write-back partition to be MOLAP (Multidimensional OLAP) This settingremains 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 asfollows
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 Servertrade20052008 which you can download from wwwmicrosoftcom (search on ldquoTable Partitioningrdquo to find all relevantarticles)
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 Thebrowser 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 localhostand external network interface machine
3 If you want to use IP1 which indicates Server IP set Enabled to Yes and specify the TCP Port as desired
4 Delete 0 from TCP Dynamic Ports Set IPAll - TCP Ports as desired (for example 1533)
RecommendationWe do not recommend using dynamic ports
In an SQL server the default instance has a listener which listens on a fixed port (TCP port 1433)However for the named instance the port on which the SQL server listens is random and dynamicallyselected when the named instance of the SQL server starts This recommendation prevents any conflictproblems
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 Setthe 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 thatthe user identified as the Log on as user has the sysadmin SQL Server role defined under Server Roles in theSQL Server Management Studio This is required so Analysis Services can process the SQL Server
From SQL Server Management Studio do the following tasks
22
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
1 If you want to use a port with a named instance select the server type Analysis Services select the servername (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 ServerProperties window displays which shows all configurable properties
3 For enhanced security change the default value to your port number (for example 2724) This means thatyou use a fixed port as for the SQL Server option Then choose OK
NoteWe do not support a nondefault port with the default instance in this release If you want to use the defaultinstance do not change the port number
Restart SQL and OLAP
Confirm that the installation has completed successfully by checking that there are no installation relatedproblems on the event viewer You can now install Planning and Consolidation
274 Installing Analysis Services
Procedure
After you install SQL Server and its required service packs and hotfixes you must install SQL Server Analysis Servicesand its required service packs and hotfixes
NoteIf you have migrated your Analysis Services repository to the SQL Server back up the database that contains therepository before installing this release
To install Analysis Services for SQL Server 2008 SQL Server 2008 R2 or SQL Server 2012 follow the steps andguidelines in technetmicrosoftcomen-uslibraryms143219aspx
To avoid slow performance when a user has more than six OLAP databases follow the steps and guidelines in thePerformance Guide for SQL 2008 at wwwmicrosoftcomdownloadsdetailsaspxFamilyID=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 tohave it available for the Planning and Consolidation installation program
1 Download the Anti-Cross Site Scripting Library file AntiXSSLibraryDLL from the Microsoft Web site atwwwmicrosoftcomdownloadendetailsaspxid=28589
2 Save the extracted file locally
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 23
When you install Planning and Consolidation Server a step in the process requires you to identify the path toAntiXssLibrarydll
28 Installing on a Single Server
When you install all Planning and Consolidation server components on a single server you should consider thefollowing 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 theuncompressed 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 Log on to the server with a local server user ID or domain user ID For more information see Logging on toservers [page 14]
3 Make sure all prerequisite software is installed on the server For more information see Installing thePrerequisites [page 17]
4 Obtain SAP Planning and Consolidation archive from the Downloads SAP Installations amp Upgrades areaof SAP Service Marketplace
5 Extract the files from the archive Go to the BPC Setup folder and run the StartUpexe file
6 From the Server Install screen select Install the Planning and Consolidation server
7 From the Welcome screen choose Next
8 From the License Agreement page choose I accept the terms of the license agreement then choose Next
9 From the Installation Method page accept the default Single machine enter a system ID for the systemlandscape directory (SLD) and choose Next
NoteEntering a system ID of the SLD is only required if you have a SAP Solution Manager license If you do nothave a SAP Solution Manager license you can leave this field empty
10 From the Authentication Method page choose the desired authentication method and choose Next
11 If you have chosen SAP BusinessObjects User Management System in the previous screen on the CMSAuthentication page enter the information required to log on to CMS as an administrator
The following information is required
24
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
Table 8
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 Thisgroup name is filtered as the default when adding a user in Planning andConsolidation Administration Use a comma ( ) to separate multiple names
12 After entering the CMS administrator authentication details choose Next
13 From the Service type accounts page enter service-level account user IDs and passwords See Service-LevelAccounts [page 15]
14 After defining the IDs and passwords choose Next
15 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 chooseNext
16 Specify the location and name of AntiXssLibrarydll See Installing the Anti-Cross Site ScriptingLibrary [page 23]
Choose Next
17 Select destination folders for Programs and Data The Data files include Webfolders and FileDB (publishedreports) and should be installed on a separate drive in a production environment This recommendation reducesthe hard disk IO time and helps to speed up SQL commands
Accept the defaults or make your selections then choose Next
18 Select the default values for the Web client The values are used to determine the default language and regionfor the Web client when you connect to it You can change the values in the Planning and Consolidation ServerManager
19 The installation process takes a few moments When it is complete choose Exit
20 A prompt is displayed to restart your computer Select OK to restart
21 Perform the steps in After Installing Planning and Consolidation Servers [page 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 avariety of ways and configure the servers as a Network Load Balancing (NLB) environment
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 25
The recommended Planning and Consolidation practice is to assign resources using a round robin approach for loadbalancing
You can install the SQL OLAP and FileShare types remotely from the application server You need to performadditional server installations if you have multiple application servers
Installing each Planning and Consolidation application server in a multiserver (NLB) configuration is identical to theprocedure 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 Balancingenvironment With this option there is an additional choice to Include sample environment (required on only oneof the application servers) This is because when you install the application server it connects to the databaseserver and creates the sample environment (EnvironmentShell) Installing the sample environment is requiredon 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
26
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
3 After Installing Planning and ConsolidationServers
31 Post-Installation Steps
Procedure
Perform these steps after installing the Planning and Consolidation servers for new installations of Planning andConsolidation
1 Connect your Planning and Consolidation system to Solution Manager Diagnostics (SMD) to allow support staffto identify analyze and resolve problems with your application See Connecting to Solution ManagerDiagnostics [page 28]
2 Configure the Planning and Consolidation NET and application server to ensure that it and its related servicesfunction properly and reliably For more information see Configuring the Planning and Consolidation NETApplication Server [page 29]
3 Optional configuration steps [page 29]
1 To ensure proper functioning of the Management Console create an SQL user and modify the System DSNand 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 loggingfor ODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default WebSite [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory canaccess the Management Console with whatever rights they have been granted on the server Forinformation about removing default access and creating a group that can access the console see RemovingDefault Access to the Console [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommendthat you only grant Management Console access to system administrators Planning and Consolidationusers should not have any access For more information see Management Console AccessControl [page 33]
6 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
4 Take the following steps to set up security
If you are defining security and application structure continue with step 5
If you want to designate someone other than the system administrator to manage security and applicationstructure log on to EnvironmentShell designate a user as a Primary Administrator
This user must have Administration ndash Environment and Security ‒ Define User task rights so that he or shecan 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 SeeInstalling the Administration Client [page 37]
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 27
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 taskprofiles 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 mustcomplete this step since there is no access to dimensions or members)
NoteTo allow users to request and query large amounts of data you can edit the metabasexml file located at CWindowssystem32inetsrv Set the following parameters to the stated values
ASPBUFFERINGLIMIT = 10485760
MAXREQUESTENTITYALLOWED = 10485760
32 Connecting to Solution Manager Diagnostics
NoteYou only need to perform the steps in this section if you have a SAP Solution Manager licence
The diagnostics functions in SAP Solution Manager allow identification analysis and resolution of problems Thisprocedure 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 areinstalled
NoteInstallation files for Diagnostics Agent are available on Service Marketplace by navigating to SupportPackages and Patches mdash Entry by Application Group SAP Technology Components SAP SOLUTIONMANAGER SAP SOLUTION MANAGER 70 EHP 1 Entry by Component Agents for managed systemsDIAGNOSTICS AGENT 711
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 whereMicrosoft 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
28
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
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 ServiceMarketplace at servicesapcom~sapidb011000358700000074392009E and follow the chapters that applyto Planning and Consolidation
33 Configuring the Planning and Consolidation NETApplication Servers
Procedure
Modifying machineconfig Files
To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock occurrences that wouldcause the application server to ldquosleeprdquo and not process anymore you can modify the machineconfig file whichresides in the WINDOWSMicrosoftNETFramework64v4030319Config directory
1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to specifywhether to automatically configure settings to achieve optimal performance based on the machineconfiguration You can set this attribute to True or False
For more information see msdnmicrosoftcomen-uslibrary7w2sway1aspx
2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the Planning andConsolidation application) or Machineconfig (for all applications including Planning and Consolidation) toensure the validationKey and decryptionKey keys have the same value on all application servers Thisway when the authentication cookie is checked the authentication ticket used on one server can still be validon another server
For more information and sample Visual Basic code for generating random key values seemsdnmicrosoftcomen-uslibraryms998288aspxpaght000007_webfarmdeploymentconsiderationsand msdnmicrosoftcomen-uslibraryms998310aspx
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 DSNand 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 forODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory can accessthe Management Console with whatever rights they have been granted on the server For information about
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 29
removing default access and creating a group that can access the console see Removing Default Access to theConsole [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommend thatyou only grant Management Console access to system administrators Planning and Consolidation users shouldnot have any access For more information see Management Console Access Control [page 33]
6 Configure the use of SSL in Planning and Consolidation See Configuring Planning and Consolidation to useSSL [page 34]
7 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
8 Configure Microsoft SQL Server Reporting Services to use SSL See Configuring MS SQL Server ReportingServices to use SSL [page 36]
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 databaserole 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 optionto use ODBC Logging Enter the following values
DSN is BPC_ManagementDSN Table is BPCLog The Microsoft SQL Server Username and Password
5 Restart IIS
NoteWithout these updates the Management Console does work but some functionality (specifically User Activityand Service Status) does not work as expected
Should you need to uninstall Planning and Consolidation we recommend that you reset the Active Log Formatfield in IIS to W3C Extended Log File Format
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
30
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
Prerequisites
ODBC logging has been configured according to the Microsoft Knowledge Base article 245243 How to configureODBC 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 inApplicationHostconfig as shown here
ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0logFormat=Custom gtUse 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-00AA006111E0appcmd 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 articlespecified in the Prerequisites section Configure these settings in the ltodbcLogginggt node underltsystemwebServergt
Exampleltlocation path=Default Web SitegtltsystemwebServergtltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog userName=Usernamepassword=mypassword gtltsystemwebServergtltlocationgt
Use the following AppCmds to configure these attributes for the default Web site
appcmd set config Default Web Site sectionodbcLogging dataSourceBPC_ManagementDSN commitappHostappcmd set config Default Web Site sectionodbcLogging tableNameBPCLog commitappHostappcmd set config Default Web Site sectionodbcLogging userNameUsername commitappHostappcmd set config Default Web Site sectionodbcLogging passwordmypassword commitappHost
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 31
NoteYou cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must use the SQL ServerODBC driver For more information see the Microsoft Knowledge Base article 931202 The requirements for usingthe ODBC logging feature in IIS
343 Setting Up an ODBC Data Source in Windows Server2008 2008 R2 2012 or 2012 R2
Procedure
This procedure describes how to set up an ODBC data source for the Management Console in Windows Server 20082008 R2 2012 or 2012 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
NoteIf you have chosen SAP BusinessObjects User Management System in the installation screen you do not needto remove or configure access because the Management Console service always runs with the System Admin IDaccount which is a member of the Administrators group
Procedure
To remove default access to the Management Console and create a group that does have access to the console usethe procedure described below
32
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
NoteCreate your Management Console administrative group either on the server that hosts the Management Consoleor 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
NoteAlternatively you can perform analogous steps in Active Directory
3 In the Groups context menu choose New Group
4 Enter data as required Click Create
5 In the Computer Management dialog box choose Services and Applications Internet InformationServices 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 objectand all child objects Include these with entries explicitly defined here checkbox
NoteThis step is a necessary precursor to the completion of this procedure
10 In the Security dialog box click Copy to ensure that the System group retains its privileges
11 Remove access to the Management Console from all groups that should not have it
12 Choose Authentication in the center pane then disable Windows authentication
Result
Users who have not been granted access to the Management Console can still open the Management Console Webpage but it contains no data or menu options This does not affect the access that a user would otherwise have toPlanning and Consolidation
345 Management Console Access Control
After establishing the Management Console group you can add users or groups to it For more information aboutcreating this group see Removing Default Access to the Console [page 32] Their rights in Active Directory determinewhat they can access in the Console
By default any member of the Administrators Active Directory group on the application server or domain has fullaccess to all of the features of the Console except the Planning and Consolidation logging area Access to Planningand Consolidation logging is controlled within the Planning and Consolidation Administration Client task securityThe user must be granted View system logs task privileges For more information see the SAP Library Planning and
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 33
Consolidation Administrators Guide in servicesapcominstguidesepm-bpc 100 version for the Microsoftplatform
Your IT policy determines whether you grant access by group or user You may wish to create several levels of Consoleusers (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 describedin this table
Table 9
Privilege Rights Management Area
Task Manager and Kill Process Administrators group on application server or domain
Performance Monitor Counters Administrators group on application server or domain
Power Users group on application server or domain
Performance Monitor Users group on application server
Microsoft Analysis Services performance monitoring Administrators group on application server or domain
Microsoft SQL Server Monitoring (performance counters andstatistics)
Administrators group on application server or domain
346 Configuring Planning and Consolidation to use SSL
Procedure
Creating a Certificate for the Server
During the handshake phase of the SSL communication the server must send its certificate to the client The clientthen uses the certificate to encrypt information and send it back to the server
The procedure below describes how to create a self-signed certificate for the server
RecommendationWe recommend that you limit the use of self-signed certificates to testing only For a productive system you shouldobtain a certificate signed by a well-known certification authority (CA)
1 Start the Internet Information Services (IIS) Manager To do that go to Start All Programs AdministrativeTools Internet Information Services (IIS) Manager
2 In the Connections panel on the left-hand side select the server node and then choose Server Certificates
3 In the Actions panel on the right hand side choose the Create Self-Signed Certificate action
4 Enter the name that you want the certificate to be identified by for example MyTestSSLCertificate
IIS generates a new SSL certificate for you that has one yearrsquos expiry lease The certificate is issued to the local servername
Binding the Certificate to the Web Site
The procedure below describes how to bind the certificate to the web site for which SSL connections must be used
1 In the Connections panel select the web site node
2 In the Actions panel choose Bindings
34
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
3 In the Site Bindings dialog that appears choose the Add button to create a new binding
4 Configure the parameters as follows
Type = https IP Address = [1] - this is a shorthand expression for the local server name
Port = 443 - this is the default SSL port
SSL Certificate = enter your newly created certificate name
5 Choose OK to create the new binding and then close the Site Bindings dialog
6 Restart the IIS processes To do this choose Restart from the Actions panel
7 In the middle panel under the IIS section choose SSL Settings
8 In the SSL Settings screen select the Require SSL checkbox
9 In the Actions panel choose to Apply these settings
To test the SSL connection in the Actions panel choose the Browse [1] 443 (https) link
347 Using Client Certificates
To enable the use of client certificates in Planning and Consolidation you must follow several manual steps
NotePlanning and Consolidation supports client certificate authentication in Windows Authentication Mode butdoes 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 technetmicrosoftcomen-uslibrarycc753810aspx
For more information about configuring the client certificate mapping authentication see technetmicrosoftcomen-uslibrarycc732996(WS10)aspx
When you create the client certificates you can set the type of certificate in the SSL Settings screen in InternetInformation Services (IIS) Manager
Procedure
1 Set the options for client certificates
1 In the IIS Manager select the web site where you installed Planning and Consolidation
2 Choose SSL Settings
3 In the Client certificates section select the Accept client certificates option
This option allows you to use a client certificate or username and password (Basic authentication) toconnect 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 theManagementConsole home page
3 Double-click Authentication and enable Anonymous Authentication
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 35
4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way asin step 3
5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the sameway 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
348 Configuring MS SQL Server Reporting Services to useSSL
Procedure
The procedure below describes how to configure the use of SSL in Microsoft SQL Server Reporting Services
NoteReporting Services does not provide functionalities for generating requesting or installing a certificate Theserver certificates that you want to use for configuring SSL must have already been installed on your computer
1 Open the Reporting Services Configuration Manager program To do this open the Windows Start menu andnavigate to All Programs Microsoft SQL Server ltversiongt Configuration Tools Reporting ServicesConfiguration Manager
2 In the Connect panel on the left-hand side select the Web Service URL option to open all the Report Server webservice parameters
3 Configure the parameters as follows
SSL Certificate = the name of the certificate that you want to use
SSL Port = 4434 Choose Apply to confirm the changes
5 In the Connect panel choose Report Manager URL to open the list of parameters that link Reporting Servicesto IIS
6 Choose Advanced to add your new SSL web URL
7 In the section Multiple SSL Identities for Report Manager choose Add Configure the parameters as follows
IP Address = (All IPv4) SSL Port = 443 Certificate = the name of your SSL certificate
8 To test the configuration click the URL that appears under the Report manager Site Identification section
36
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
4 Installing Planning and ConsolidationAdministration Client and the SAPBusinessObjects EPM solutions Add-in forMicrosoft Office
The installation of the Planning and Consolidation Administration Client allows administrators to build and maintainPlanning and Consolidation environments and models and administer security
All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions add-in forMicrosoft 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 valueof the Planning and Consolidation client to prompt for user name and password Otherwise the Planning andConsolidation Start Page does not display
41 Installing the Administration Client
Prerequisites
NoteFor a definitive list of system requirements see the Product Availability Matrix on SAP Service Marketplace atservicesapcompam Search on Planning and Consolidation
The following list describes the minimum software requirements
Microsoft Internet Explorer 70 80 90 or 10
Microsoft Office 2003 2007 2010 or 2012
NET Framework 20 or higher (install any required NET Framework Hotfixes by referring tosupportmicrosoftcomkb)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 37
NoteWe recommend that you install all of the latest Microsoft Windows hotfixes prior to installing the Administrationclient For information about which hotfixes to install see updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us
Procedure
The 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 ltPC_serverportgtsapbpcweb
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 mustdownload the most recent version of the full setup (EPM Add-inexe) from the Service Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPCInstallation folder
Individual users can install the EPM add-in on their own machines by going to the Planning and Consolidation Homepage 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 upthe 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
38
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
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 toperform the upgrade If Client Auto Update is not enabled and a newer version is detected clients must be installedmanually 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 andpassword in the Admin ID and Admin password fields respectively The Admin ID should be a member of thelocal administrators group on all the computers running the auto update This setting is not needed if all usershave 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 Thisoption is stored in the user preferences and may also be turned on or off using the User Optionshellip menu itemIf 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 toinstall 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 installit 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 servicesapcom
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 versionand policy information For a support package these files are
EPM Addin Support Package ltSP versiongtmsp EPM Addin Support Package ltSP versiongtxmlFor a patch these files are
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 (WebsrvrWebBPCInstallation)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 39
You can set a different update policy for each package listed
ExampleThe following table illustrates some possible situations assuming that you have installed the first full version(V1)
Table 10
Available maintenancepackages
V2-user update
V3-force update
V4-force update
V5-user update
V5-user update V5-user update
V6-auto update
V7-force update
Minimum RequiredVersion
V4 V4 V7
Notification A prompt tells the user toinstall maintenancepackage V4 using theForced Update behavior
If User Update is enabledthe prompt informs theuser that maintenancepackage V5 is available
A prompt tells the user toinstall maintenancepackage V7 using theForced Update behavior
New Version V4 V4 or V5 V7
If you change the update policy for any package click Update to complete the change
40
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
5 Connection Issues
You may experience connection problems with ports the proxy server or programs and settings that interact withthese components If you have any issues related to connection review the following recommendations andtroubleshooting tips
51 Checking for Open Ports
You must ensure that all required ports are open for inboundoutbound traffic By default Planning andConsolidation requires that Ports 80 (used by http) and 1433 and 2383 (used by SQL Server 2008) are open Totest whether the required ports are open go to a command prompt and enter the Telnet serveripaddress and portFor example Telnet 431181836 80 If the system returns a blank command window the port is open If it returnsa message stating that it is unable to connect the port is not open
NoteYou can use the following site to scan for the normal ports It allows you to manually enter a port number to test
wwwmyserverorgportsniffasp
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 Planningand Consolidation server as an exception You can do this at the client level ( Internet Explorer ToolsInternet 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 fullyqualified 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 Consolidationauthentication Do not use authentication on the proxy server The system synchronizes the user name andpassword on the remote server with the local user name and password
SAP Business Planning and Consolidation 100Connection Issues
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 41
NoteFor more information about setting up an ISA proxy server contact SAP Support to request a copy of Setting upISA Proxy Server White Paper For more information about Business Planning and Consolidation firewall portssee SAP Note 1505250
Internet Explorer Settings Issues
Internet Explorer settings must be set correctly to prevent errors and problems when you attempt to access thePlanning 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 insertthe IP address or fully qualified server name of the Planning and Consolidation server as an exception bychoosing 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
42
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Connection Issues
6 Installing Planning and Consolidation withTwo Active Directory Domains
To set up a Planning and Consolidation 10 application server in a hosted environment and use your own domainusers follow this procedure In general you install Planning and Consolidation on the host domain use the hostdomain account and assign it to the Planning and Consolidation users SysAdmin Admin and Users Then you acceptone 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 andpassword 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 topromote 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 privilegefor the Planning and Consolidation server
5 Install Planning and Consolidation and assign your domain account either to the three Planning andConsolidation administrative users SysAdmin Admin and Users or to only one of the three Planning andConsolidation administrative users and to three of your users Be sure you use your own user account ratherthan host domain users
Planning and Consolidation impersonation can then access your domain from the host environment becauseit has the privilege of your domain account
SAP Business Planning and Consolidation 100Installing Planning and Consolidation with Two Active Directory Domains
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 43
7 Installing Planning and Consolidation in aTerminal Services or Citrix ServerDeployment
This section describes best practices and instructions for installing Planning and Consolidation in a Terminal Servicesor Citrix Server deployment
71 Terminal Services Home Directories
We recommend using Terminal Server home directories rather than using the userrsquos profile directory The profiledirectory downloads a minimal amount of information about the dimensions of the environment you are logging onto and may be as large as 2 MB per user The profile directory is on the system drive and has limited space Byspecifying 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 individualserver 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 clientserver (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
44
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
Procedure
The following steps outline how to install the Planning and Consolidation clients in a Terminal Services (TS) or CitrixServer deployment
1 Make sure the Terminal Services or Citrix Server machine has the system requirements installed
2 Log on to the Terminal Services or Citrix Server machine with a user ID that has the rights to install on thatserver
3 At a command prompt enter Change userinstall
4 Open a browser and connect to the URL ltPC_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_MSBPCAdminMainexe
74 Creating a Shortcut to the Launch Page
Procedure
If you use published desktops instead of published applications the Planning and Consolidation desktop file (whichis installed on the current userrsquos desktop) must be moved to the All UsersDesktop folder
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 45
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 SQLServer 2012 support the remote modification of SSIS packages Planning and Consolidation also supports theremote 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 whichyou want to modify SSIS packages
These custom tasks reference dlls that connect to the database server and perform certain validation when usersset up the parameters of each task All the custom task reference components must also be installed in the machineon which you want to modify SSIS packages
We provide a program that registers all the reference components of the custom tasks This section explains theinstallation 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 ndash This folder contains all the dlls that should be installed on the machine There are Planning andConsolidation platform components and all of the Data Manager custom task files
Config folder ndash This folder contains only one file named Filelistxml and lists all of the files that should be installedIf you need to add or remove certain components from the installation you can modify this xml file
OSoftSetupexe ndash This is the main executable file to run the installation package
NoteIf you are not installing SSIS Custom Tasks on your client machine ndash specifically a machine other than the Planningand Consolidation application server ndash you must first install OSoftSSIS2008_Client or OSoftSSIS2012_Client onthe client machine followed by the SQL Server version If you want to use SQL 2008 Tasks under the SQL 2012environment you must install OSoftSSIS2008_Client on the application server For detailed information see SAPNote 1707410 You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package byextracting OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPCInstallation folder on the Planning and Consolidation server To modify SSIS packages on the Planning andConsolidation application server you need to install OSoftSSIS2008_Client or OSoftSSIS2012_Client for creatinga COM+ application For more information see Before You Modify the SSIS Packages [page 49] and Setup ofa COM+ Application on the Application Server [page 50]
Bin folder
This folder contains the following components
46
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Table 11
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012respectively
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
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 47
Name Remark
BPCWriteBackdll
InteropDTSdll
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 addmore components to the installation package you can copy the new components into the Bin folder and add theproper xml tags in FileListxml You need to enter information for the following tags
RegistType ndash This is the registration information of the component You can enter the following values
RegAsm ndash For NET component
48
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Regsvr32 ndash For VB6 component
Gacutil ndash For NET Framework component that should be registered into Global Assembly Cache
FileName ndash Component file name
OSoftSetupexe
This is the executable file to run the SSIS installation package Double-click the file to start the installation You needto enter information for the following fields
Set SQL server
Specify the SQL server name If your SQL Server has an instance specify the instance name
NoteIf you installed the OSoftSSIS2008_Client or OSoftSSIS2012_Client on the application server the SQL servername is automatically disabled
Set server credential
This is the credential name of the COM+ package component Enter the user ID and password that can accessyour SQL Server This should be either the System Admin ID or Admin ID that was registered as a COM+ userwhen 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 ifyou 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 packagesremotely This is also true for the application server that has SSIS installed The Planning and ConsolidationData Manager has the following custom tasks
Table 12
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008and 2012 respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and2012 respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012respectively
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 49
Name Remark
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and2012 respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008and 2012 respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL2008 and 2012 respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and2012 respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012respectively
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
ltdrivegtWebsrvrbin2 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 FilesMicrosoft SQLServer paste all files into the CProgram Files (x86)Microsoft SQL Server100DTSTasksfolder
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
50
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Typographic Conventions
Table 13
Example Description
lt gt Angle brackets indicate that you replace these words or characters with appropriate entries tomake entries in the system for example Enter your ltUser Namegt
File Save Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
Example Textual cross-references to an internet address for example wwwsapcom
example Quicklinks added to the internet address of a homepage to enable quick access to specificcontent 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 titlespushbutton 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 namesof installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transactioncodes database table names and key concepts of a programming language when they aresurrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
SAP Business Planning and Consolidation 100Typographic Conventions
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 51
52
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
wwwsapcom
Material Number
- SAP Business 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 2008 R2 2012 or 2012 R2
- 344 Removing Default Access to the Console
- 345 Management Console Access Control
- 346 Configuring Planning and Consolidation to use SSL
- 347 Using Client Certificates
- 348 Configuring MS SQL Server Reporting Services to use SSL
-
- 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
-
1 If you want to use a port with a named instance select the server type Analysis Services select the servername (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 ServerProperties window displays which shows all configurable properties
3 For enhanced security change the default value to your port number (for example 2724) This means thatyou use a fixed port as for the SQL Server option Then choose OK
NoteWe do not support a nondefault port with the default instance in this release If you want to use the defaultinstance do not change the port number
Restart SQL and OLAP
Confirm that the installation has completed successfully by checking that there are no installation relatedproblems on the event viewer You can now install Planning and Consolidation
274 Installing Analysis Services
Procedure
After you install SQL Server and its required service packs and hotfixes you must install SQL Server Analysis Servicesand its required service packs and hotfixes
NoteIf you have migrated your Analysis Services repository to the SQL Server back up the database that contains therepository before installing this release
To install Analysis Services for SQL Server 2008 SQL Server 2008 R2 or SQL Server 2012 follow the steps andguidelines in technetmicrosoftcomen-uslibraryms143219aspx
To avoid slow performance when a user has more than six OLAP databases follow the steps and guidelines in thePerformance Guide for SQL 2008 at wwwmicrosoftcomdownloadsdetailsaspxFamilyID=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 tohave it available for the Planning and Consolidation installation program
1 Download the Anti-Cross Site Scripting Library file AntiXSSLibraryDLL from the Microsoft Web site atwwwmicrosoftcomdownloadendetailsaspxid=28589
2 Save the extracted file locally
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 23
When you install Planning and Consolidation Server a step in the process requires you to identify the path toAntiXssLibrarydll
28 Installing on a Single Server
When you install all Planning and Consolidation server components on a single server you should consider thefollowing 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 theuncompressed 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 Log on to the server with a local server user ID or domain user ID For more information see Logging on toservers [page 14]
3 Make sure all prerequisite software is installed on the server For more information see Installing thePrerequisites [page 17]
4 Obtain SAP Planning and Consolidation archive from the Downloads SAP Installations amp Upgrades areaof SAP Service Marketplace
5 Extract the files from the archive Go to the BPC Setup folder and run the StartUpexe file
6 From the Server Install screen select Install the Planning and Consolidation server
7 From the Welcome screen choose Next
8 From the License Agreement page choose I accept the terms of the license agreement then choose Next
9 From the Installation Method page accept the default Single machine enter a system ID for the systemlandscape directory (SLD) and choose Next
NoteEntering a system ID of the SLD is only required if you have a SAP Solution Manager license If you do nothave a SAP Solution Manager license you can leave this field empty
10 From the Authentication Method page choose the desired authentication method and choose Next
11 If you have chosen SAP BusinessObjects User Management System in the previous screen on the CMSAuthentication page enter the information required to log on to CMS as an administrator
The following information is required
24
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
Table 8
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 Thisgroup name is filtered as the default when adding a user in Planning andConsolidation Administration Use a comma ( ) to separate multiple names
12 After entering the CMS administrator authentication details choose Next
13 From the Service type accounts page enter service-level account user IDs and passwords See Service-LevelAccounts [page 15]
14 After defining the IDs and passwords choose Next
15 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 chooseNext
16 Specify the location and name of AntiXssLibrarydll See Installing the Anti-Cross Site ScriptingLibrary [page 23]
Choose Next
17 Select destination folders for Programs and Data The Data files include Webfolders and FileDB (publishedreports) and should be installed on a separate drive in a production environment This recommendation reducesthe hard disk IO time and helps to speed up SQL commands
Accept the defaults or make your selections then choose Next
18 Select the default values for the Web client The values are used to determine the default language and regionfor the Web client when you connect to it You can change the values in the Planning and Consolidation ServerManager
19 The installation process takes a few moments When it is complete choose Exit
20 A prompt is displayed to restart your computer Select OK to restart
21 Perform the steps in After Installing Planning and Consolidation Servers [page 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 avariety of ways and configure the servers as a Network Load Balancing (NLB) environment
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 25
The recommended Planning and Consolidation practice is to assign resources using a round robin approach for loadbalancing
You can install the SQL OLAP and FileShare types remotely from the application server You need to performadditional server installations if you have multiple application servers
Installing each Planning and Consolidation application server in a multiserver (NLB) configuration is identical to theprocedure 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 Balancingenvironment With this option there is an additional choice to Include sample environment (required on only oneof the application servers) This is because when you install the application server it connects to the databaseserver and creates the sample environment (EnvironmentShell) Installing the sample environment is requiredon 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
26
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
3 After Installing Planning and ConsolidationServers
31 Post-Installation Steps
Procedure
Perform these steps after installing the Planning and Consolidation servers for new installations of Planning andConsolidation
1 Connect your Planning and Consolidation system to Solution Manager Diagnostics (SMD) to allow support staffto identify analyze and resolve problems with your application See Connecting to Solution ManagerDiagnostics [page 28]
2 Configure the Planning and Consolidation NET and application server to ensure that it and its related servicesfunction properly and reliably For more information see Configuring the Planning and Consolidation NETApplication Server [page 29]
3 Optional configuration steps [page 29]
1 To ensure proper functioning of the Management Console create an SQL user and modify the System DSNand 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 loggingfor ODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default WebSite [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory canaccess the Management Console with whatever rights they have been granted on the server Forinformation about removing default access and creating a group that can access the console see RemovingDefault Access to the Console [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommendthat you only grant Management Console access to system administrators Planning and Consolidationusers should not have any access For more information see Management Console AccessControl [page 33]
6 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
4 Take the following steps to set up security
If you are defining security and application structure continue with step 5
If you want to designate someone other than the system administrator to manage security and applicationstructure log on to EnvironmentShell designate a user as a Primary Administrator
This user must have Administration ndash Environment and Security ‒ Define User task rights so that he or shecan 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 SeeInstalling the Administration Client [page 37]
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 27
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 taskprofiles 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 mustcomplete this step since there is no access to dimensions or members)
NoteTo allow users to request and query large amounts of data you can edit the metabasexml file located at CWindowssystem32inetsrv Set the following parameters to the stated values
ASPBUFFERINGLIMIT = 10485760
MAXREQUESTENTITYALLOWED = 10485760
32 Connecting to Solution Manager Diagnostics
NoteYou only need to perform the steps in this section if you have a SAP Solution Manager licence
The diagnostics functions in SAP Solution Manager allow identification analysis and resolution of problems Thisprocedure 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 areinstalled
NoteInstallation files for Diagnostics Agent are available on Service Marketplace by navigating to SupportPackages and Patches mdash Entry by Application Group SAP Technology Components SAP SOLUTIONMANAGER SAP SOLUTION MANAGER 70 EHP 1 Entry by Component Agents for managed systemsDIAGNOSTICS AGENT 711
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 whereMicrosoft 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
28
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
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 ServiceMarketplace at servicesapcom~sapidb011000358700000074392009E and follow the chapters that applyto Planning and Consolidation
33 Configuring the Planning and Consolidation NETApplication Servers
Procedure
Modifying machineconfig Files
To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock occurrences that wouldcause the application server to ldquosleeprdquo and not process anymore you can modify the machineconfig file whichresides in the WINDOWSMicrosoftNETFramework64v4030319Config directory
1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to specifywhether to automatically configure settings to achieve optimal performance based on the machineconfiguration You can set this attribute to True or False
For more information see msdnmicrosoftcomen-uslibrary7w2sway1aspx
2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the Planning andConsolidation application) or Machineconfig (for all applications including Planning and Consolidation) toensure the validationKey and decryptionKey keys have the same value on all application servers Thisway when the authentication cookie is checked the authentication ticket used on one server can still be validon another server
For more information and sample Visual Basic code for generating random key values seemsdnmicrosoftcomen-uslibraryms998288aspxpaght000007_webfarmdeploymentconsiderationsand msdnmicrosoftcomen-uslibraryms998310aspx
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 DSNand 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 forODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory can accessthe Management Console with whatever rights they have been granted on the server For information about
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 29
removing default access and creating a group that can access the console see Removing Default Access to theConsole [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommend thatyou only grant Management Console access to system administrators Planning and Consolidation users shouldnot have any access For more information see Management Console Access Control [page 33]
6 Configure the use of SSL in Planning and Consolidation See Configuring Planning and Consolidation to useSSL [page 34]
7 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
8 Configure Microsoft SQL Server Reporting Services to use SSL See Configuring MS SQL Server ReportingServices to use SSL [page 36]
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 databaserole 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 optionto use ODBC Logging Enter the following values
DSN is BPC_ManagementDSN Table is BPCLog The Microsoft SQL Server Username and Password
5 Restart IIS
NoteWithout these updates the Management Console does work but some functionality (specifically User Activityand Service Status) does not work as expected
Should you need to uninstall Planning and Consolidation we recommend that you reset the Active Log Formatfield in IIS to W3C Extended Log File Format
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
30
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
Prerequisites
ODBC logging has been configured according to the Microsoft Knowledge Base article 245243 How to configureODBC 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 inApplicationHostconfig as shown here
ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0logFormat=Custom gtUse 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-00AA006111E0appcmd 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 articlespecified in the Prerequisites section Configure these settings in the ltodbcLogginggt node underltsystemwebServergt
Exampleltlocation path=Default Web SitegtltsystemwebServergtltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog userName=Usernamepassword=mypassword gtltsystemwebServergtltlocationgt
Use the following AppCmds to configure these attributes for the default Web site
appcmd set config Default Web Site sectionodbcLogging dataSourceBPC_ManagementDSN commitappHostappcmd set config Default Web Site sectionodbcLogging tableNameBPCLog commitappHostappcmd set config Default Web Site sectionodbcLogging userNameUsername commitappHostappcmd set config Default Web Site sectionodbcLogging passwordmypassword commitappHost
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 31
NoteYou cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must use the SQL ServerODBC driver For more information see the Microsoft Knowledge Base article 931202 The requirements for usingthe ODBC logging feature in IIS
343 Setting Up an ODBC Data Source in Windows Server2008 2008 R2 2012 or 2012 R2
Procedure
This procedure describes how to set up an ODBC data source for the Management Console in Windows Server 20082008 R2 2012 or 2012 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
NoteIf you have chosen SAP BusinessObjects User Management System in the installation screen you do not needto remove or configure access because the Management Console service always runs with the System Admin IDaccount which is a member of the Administrators group
Procedure
To remove default access to the Management Console and create a group that does have access to the console usethe procedure described below
32
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
NoteCreate your Management Console administrative group either on the server that hosts the Management Consoleor 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
NoteAlternatively you can perform analogous steps in Active Directory
3 In the Groups context menu choose New Group
4 Enter data as required Click Create
5 In the Computer Management dialog box choose Services and Applications Internet InformationServices 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 objectand all child objects Include these with entries explicitly defined here checkbox
NoteThis step is a necessary precursor to the completion of this procedure
10 In the Security dialog box click Copy to ensure that the System group retains its privileges
11 Remove access to the Management Console from all groups that should not have it
12 Choose Authentication in the center pane then disable Windows authentication
Result
Users who have not been granted access to the Management Console can still open the Management Console Webpage but it contains no data or menu options This does not affect the access that a user would otherwise have toPlanning and Consolidation
345 Management Console Access Control
After establishing the Management Console group you can add users or groups to it For more information aboutcreating this group see Removing Default Access to the Console [page 32] Their rights in Active Directory determinewhat they can access in the Console
By default any member of the Administrators Active Directory group on the application server or domain has fullaccess to all of the features of the Console except the Planning and Consolidation logging area Access to Planningand Consolidation logging is controlled within the Planning and Consolidation Administration Client task securityThe user must be granted View system logs task privileges For more information see the SAP Library Planning and
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 33
Consolidation Administrators Guide in servicesapcominstguidesepm-bpc 100 version for the Microsoftplatform
Your IT policy determines whether you grant access by group or user You may wish to create several levels of Consoleusers (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 describedin this table
Table 9
Privilege Rights Management Area
Task Manager and Kill Process Administrators group on application server or domain
Performance Monitor Counters Administrators group on application server or domain
Power Users group on application server or domain
Performance Monitor Users group on application server
Microsoft Analysis Services performance monitoring Administrators group on application server or domain
Microsoft SQL Server Monitoring (performance counters andstatistics)
Administrators group on application server or domain
346 Configuring Planning and Consolidation to use SSL
Procedure
Creating a Certificate for the Server
During the handshake phase of the SSL communication the server must send its certificate to the client The clientthen uses the certificate to encrypt information and send it back to the server
The procedure below describes how to create a self-signed certificate for the server
RecommendationWe recommend that you limit the use of self-signed certificates to testing only For a productive system you shouldobtain a certificate signed by a well-known certification authority (CA)
1 Start the Internet Information Services (IIS) Manager To do that go to Start All Programs AdministrativeTools Internet Information Services (IIS) Manager
2 In the Connections panel on the left-hand side select the server node and then choose Server Certificates
3 In the Actions panel on the right hand side choose the Create Self-Signed Certificate action
4 Enter the name that you want the certificate to be identified by for example MyTestSSLCertificate
IIS generates a new SSL certificate for you that has one yearrsquos expiry lease The certificate is issued to the local servername
Binding the Certificate to the Web Site
The procedure below describes how to bind the certificate to the web site for which SSL connections must be used
1 In the Connections panel select the web site node
2 In the Actions panel choose Bindings
34
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
3 In the Site Bindings dialog that appears choose the Add button to create a new binding
4 Configure the parameters as follows
Type = https IP Address = [1] - this is a shorthand expression for the local server name
Port = 443 - this is the default SSL port
SSL Certificate = enter your newly created certificate name
5 Choose OK to create the new binding and then close the Site Bindings dialog
6 Restart the IIS processes To do this choose Restart from the Actions panel
7 In the middle panel under the IIS section choose SSL Settings
8 In the SSL Settings screen select the Require SSL checkbox
9 In the Actions panel choose to Apply these settings
To test the SSL connection in the Actions panel choose the Browse [1] 443 (https) link
347 Using Client Certificates
To enable the use of client certificates in Planning and Consolidation you must follow several manual steps
NotePlanning and Consolidation supports client certificate authentication in Windows Authentication Mode butdoes 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 technetmicrosoftcomen-uslibrarycc753810aspx
For more information about configuring the client certificate mapping authentication see technetmicrosoftcomen-uslibrarycc732996(WS10)aspx
When you create the client certificates you can set the type of certificate in the SSL Settings screen in InternetInformation Services (IIS) Manager
Procedure
1 Set the options for client certificates
1 In the IIS Manager select the web site where you installed Planning and Consolidation
2 Choose SSL Settings
3 In the Client certificates section select the Accept client certificates option
This option allows you to use a client certificate or username and password (Basic authentication) toconnect 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 theManagementConsole home page
3 Double-click Authentication and enable Anonymous Authentication
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 35
4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way asin step 3
5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the sameway 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
348 Configuring MS SQL Server Reporting Services to useSSL
Procedure
The procedure below describes how to configure the use of SSL in Microsoft SQL Server Reporting Services
NoteReporting Services does not provide functionalities for generating requesting or installing a certificate Theserver certificates that you want to use for configuring SSL must have already been installed on your computer
1 Open the Reporting Services Configuration Manager program To do this open the Windows Start menu andnavigate to All Programs Microsoft SQL Server ltversiongt Configuration Tools Reporting ServicesConfiguration Manager
2 In the Connect panel on the left-hand side select the Web Service URL option to open all the Report Server webservice parameters
3 Configure the parameters as follows
SSL Certificate = the name of the certificate that you want to use
SSL Port = 4434 Choose Apply to confirm the changes
5 In the Connect panel choose Report Manager URL to open the list of parameters that link Reporting Servicesto IIS
6 Choose Advanced to add your new SSL web URL
7 In the section Multiple SSL Identities for Report Manager choose Add Configure the parameters as follows
IP Address = (All IPv4) SSL Port = 443 Certificate = the name of your SSL certificate
8 To test the configuration click the URL that appears under the Report manager Site Identification section
36
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
4 Installing Planning and ConsolidationAdministration Client and the SAPBusinessObjects EPM solutions Add-in forMicrosoft Office
The installation of the Planning and Consolidation Administration Client allows administrators to build and maintainPlanning and Consolidation environments and models and administer security
All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions add-in forMicrosoft 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 valueof the Planning and Consolidation client to prompt for user name and password Otherwise the Planning andConsolidation Start Page does not display
41 Installing the Administration Client
Prerequisites
NoteFor a definitive list of system requirements see the Product Availability Matrix on SAP Service Marketplace atservicesapcompam Search on Planning and Consolidation
The following list describes the minimum software requirements
Microsoft Internet Explorer 70 80 90 or 10
Microsoft Office 2003 2007 2010 or 2012
NET Framework 20 or higher (install any required NET Framework Hotfixes by referring tosupportmicrosoftcomkb)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 37
NoteWe recommend that you install all of the latest Microsoft Windows hotfixes prior to installing the Administrationclient For information about which hotfixes to install see updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us
Procedure
The 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 ltPC_serverportgtsapbpcweb
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 mustdownload the most recent version of the full setup (EPM Add-inexe) from the Service Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPCInstallation folder
Individual users can install the EPM add-in on their own machines by going to the Planning and Consolidation Homepage 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 upthe 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
38
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
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 toperform the upgrade If Client Auto Update is not enabled and a newer version is detected clients must be installedmanually 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 andpassword in the Admin ID and Admin password fields respectively The Admin ID should be a member of thelocal administrators group on all the computers running the auto update This setting is not needed if all usershave 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 Thisoption is stored in the user preferences and may also be turned on or off using the User Optionshellip menu itemIf 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 toinstall 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 installit 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 servicesapcom
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 versionand policy information For a support package these files are
EPM Addin Support Package ltSP versiongtmsp EPM Addin Support Package ltSP versiongtxmlFor a patch these files are
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 (WebsrvrWebBPCInstallation)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 39
You can set a different update policy for each package listed
ExampleThe following table illustrates some possible situations assuming that you have installed the first full version(V1)
Table 10
Available maintenancepackages
V2-user update
V3-force update
V4-force update
V5-user update
V5-user update V5-user update
V6-auto update
V7-force update
Minimum RequiredVersion
V4 V4 V7
Notification A prompt tells the user toinstall maintenancepackage V4 using theForced Update behavior
If User Update is enabledthe prompt informs theuser that maintenancepackage V5 is available
A prompt tells the user toinstall maintenancepackage V7 using theForced Update behavior
New Version V4 V4 or V5 V7
If you change the update policy for any package click Update to complete the change
40
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
5 Connection Issues
You may experience connection problems with ports the proxy server or programs and settings that interact withthese components If you have any issues related to connection review the following recommendations andtroubleshooting tips
51 Checking for Open Ports
You must ensure that all required ports are open for inboundoutbound traffic By default Planning andConsolidation requires that Ports 80 (used by http) and 1433 and 2383 (used by SQL Server 2008) are open Totest whether the required ports are open go to a command prompt and enter the Telnet serveripaddress and portFor example Telnet 431181836 80 If the system returns a blank command window the port is open If it returnsa message stating that it is unable to connect the port is not open
NoteYou can use the following site to scan for the normal ports It allows you to manually enter a port number to test
wwwmyserverorgportsniffasp
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 Planningand Consolidation server as an exception You can do this at the client level ( Internet Explorer ToolsInternet 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 fullyqualified 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 Consolidationauthentication Do not use authentication on the proxy server The system synchronizes the user name andpassword on the remote server with the local user name and password
SAP Business Planning and Consolidation 100Connection Issues
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 41
NoteFor more information about setting up an ISA proxy server contact SAP Support to request a copy of Setting upISA Proxy Server White Paper For more information about Business Planning and Consolidation firewall portssee SAP Note 1505250
Internet Explorer Settings Issues
Internet Explorer settings must be set correctly to prevent errors and problems when you attempt to access thePlanning 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 insertthe IP address or fully qualified server name of the Planning and Consolidation server as an exception bychoosing 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
42
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Connection Issues
6 Installing Planning and Consolidation withTwo Active Directory Domains
To set up a Planning and Consolidation 10 application server in a hosted environment and use your own domainusers follow this procedure In general you install Planning and Consolidation on the host domain use the hostdomain account and assign it to the Planning and Consolidation users SysAdmin Admin and Users Then you acceptone 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 andpassword 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 topromote 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 privilegefor the Planning and Consolidation server
5 Install Planning and Consolidation and assign your domain account either to the three Planning andConsolidation administrative users SysAdmin Admin and Users or to only one of the three Planning andConsolidation administrative users and to three of your users Be sure you use your own user account ratherthan host domain users
Planning and Consolidation impersonation can then access your domain from the host environment becauseit has the privilege of your domain account
SAP Business Planning and Consolidation 100Installing Planning and Consolidation with Two Active Directory Domains
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 43
7 Installing Planning and Consolidation in aTerminal Services or Citrix ServerDeployment
This section describes best practices and instructions for installing Planning and Consolidation in a Terminal Servicesor Citrix Server deployment
71 Terminal Services Home Directories
We recommend using Terminal Server home directories rather than using the userrsquos profile directory The profiledirectory downloads a minimal amount of information about the dimensions of the environment you are logging onto and may be as large as 2 MB per user The profile directory is on the system drive and has limited space Byspecifying 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 individualserver 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 clientserver (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
44
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
Procedure
The following steps outline how to install the Planning and Consolidation clients in a Terminal Services (TS) or CitrixServer deployment
1 Make sure the Terminal Services or Citrix Server machine has the system requirements installed
2 Log on to the Terminal Services or Citrix Server machine with a user ID that has the rights to install on thatserver
3 At a command prompt enter Change userinstall
4 Open a browser and connect to the URL ltPC_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_MSBPCAdminMainexe
74 Creating a Shortcut to the Launch Page
Procedure
If you use published desktops instead of published applications the Planning and Consolidation desktop file (whichis installed on the current userrsquos desktop) must be moved to the All UsersDesktop folder
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 45
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 SQLServer 2012 support the remote modification of SSIS packages Planning and Consolidation also supports theremote 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 whichyou want to modify SSIS packages
These custom tasks reference dlls that connect to the database server and perform certain validation when usersset up the parameters of each task All the custom task reference components must also be installed in the machineon which you want to modify SSIS packages
We provide a program that registers all the reference components of the custom tasks This section explains theinstallation 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 ndash This folder contains all the dlls that should be installed on the machine There are Planning andConsolidation platform components and all of the Data Manager custom task files
Config folder ndash This folder contains only one file named Filelistxml and lists all of the files that should be installedIf you need to add or remove certain components from the installation you can modify this xml file
OSoftSetupexe ndash This is the main executable file to run the installation package
NoteIf you are not installing SSIS Custom Tasks on your client machine ndash specifically a machine other than the Planningand Consolidation application server ndash you must first install OSoftSSIS2008_Client or OSoftSSIS2012_Client onthe client machine followed by the SQL Server version If you want to use SQL 2008 Tasks under the SQL 2012environment you must install OSoftSSIS2008_Client on the application server For detailed information see SAPNote 1707410 You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package byextracting OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPCInstallation folder on the Planning and Consolidation server To modify SSIS packages on the Planning andConsolidation application server you need to install OSoftSSIS2008_Client or OSoftSSIS2012_Client for creatinga COM+ application For more information see Before You Modify the SSIS Packages [page 49] and Setup ofa COM+ Application on the Application Server [page 50]
Bin folder
This folder contains the following components
46
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Table 11
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012respectively
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
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 47
Name Remark
BPCWriteBackdll
InteropDTSdll
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 addmore components to the installation package you can copy the new components into the Bin folder and add theproper xml tags in FileListxml You need to enter information for the following tags
RegistType ndash This is the registration information of the component You can enter the following values
RegAsm ndash For NET component
48
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Regsvr32 ndash For VB6 component
Gacutil ndash For NET Framework component that should be registered into Global Assembly Cache
FileName ndash Component file name
OSoftSetupexe
This is the executable file to run the SSIS installation package Double-click the file to start the installation You needto enter information for the following fields
Set SQL server
Specify the SQL server name If your SQL Server has an instance specify the instance name
NoteIf you installed the OSoftSSIS2008_Client or OSoftSSIS2012_Client on the application server the SQL servername is automatically disabled
Set server credential
This is the credential name of the COM+ package component Enter the user ID and password that can accessyour SQL Server This should be either the System Admin ID or Admin ID that was registered as a COM+ userwhen 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 ifyou 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 packagesremotely This is also true for the application server that has SSIS installed The Planning and ConsolidationData Manager has the following custom tasks
Table 12
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008and 2012 respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and2012 respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012respectively
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 49
Name Remark
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and2012 respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008and 2012 respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL2008 and 2012 respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and2012 respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012respectively
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
ltdrivegtWebsrvrbin2 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 FilesMicrosoft SQLServer paste all files into the CProgram Files (x86)Microsoft SQL Server100DTSTasksfolder
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
50
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Typographic Conventions
Table 13
Example Description
lt gt Angle brackets indicate that you replace these words or characters with appropriate entries tomake entries in the system for example Enter your ltUser Namegt
File Save Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
Example Textual cross-references to an internet address for example wwwsapcom
example Quicklinks added to the internet address of a homepage to enable quick access to specificcontent 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 titlespushbutton 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 namesof installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transactioncodes database table names and key concepts of a programming language when they aresurrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
SAP Business Planning and Consolidation 100Typographic Conventions
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 51
52
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
wwwsapcom
Material Number
- SAP Business 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 2008 R2 2012 or 2012 R2
- 344 Removing Default Access to the Console
- 345 Management Console Access Control
- 346 Configuring Planning and Consolidation to use SSL
- 347 Using Client Certificates
- 348 Configuring MS SQL Server Reporting Services to use SSL
-
- 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
-
When you install Planning and Consolidation Server a step in the process requires you to identify the path toAntiXssLibrarydll
28 Installing on a Single Server
When you install all Planning and Consolidation server components on a single server you should consider thefollowing 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 theuncompressed 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 Log on to the server with a local server user ID or domain user ID For more information see Logging on toservers [page 14]
3 Make sure all prerequisite software is installed on the server For more information see Installing thePrerequisites [page 17]
4 Obtain SAP Planning and Consolidation archive from the Downloads SAP Installations amp Upgrades areaof SAP Service Marketplace
5 Extract the files from the archive Go to the BPC Setup folder and run the StartUpexe file
6 From the Server Install screen select Install the Planning and Consolidation server
7 From the Welcome screen choose Next
8 From the License Agreement page choose I accept the terms of the license agreement then choose Next
9 From the Installation Method page accept the default Single machine enter a system ID for the systemlandscape directory (SLD) and choose Next
NoteEntering a system ID of the SLD is only required if you have a SAP Solution Manager license If you do nothave a SAP Solution Manager license you can leave this field empty
10 From the Authentication Method page choose the desired authentication method and choose Next
11 If you have chosen SAP BusinessObjects User Management System in the previous screen on the CMSAuthentication page enter the information required to log on to CMS as an administrator
The following information is required
24
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
Table 8
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 Thisgroup name is filtered as the default when adding a user in Planning andConsolidation Administration Use a comma ( ) to separate multiple names
12 After entering the CMS administrator authentication details choose Next
13 From the Service type accounts page enter service-level account user IDs and passwords See Service-LevelAccounts [page 15]
14 After defining the IDs and passwords choose Next
15 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 chooseNext
16 Specify the location and name of AntiXssLibrarydll See Installing the Anti-Cross Site ScriptingLibrary [page 23]
Choose Next
17 Select destination folders for Programs and Data The Data files include Webfolders and FileDB (publishedreports) and should be installed on a separate drive in a production environment This recommendation reducesthe hard disk IO time and helps to speed up SQL commands
Accept the defaults or make your selections then choose Next
18 Select the default values for the Web client The values are used to determine the default language and regionfor the Web client when you connect to it You can change the values in the Planning and Consolidation ServerManager
19 The installation process takes a few moments When it is complete choose Exit
20 A prompt is displayed to restart your computer Select OK to restart
21 Perform the steps in After Installing Planning and Consolidation Servers [page 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 avariety of ways and configure the servers as a Network Load Balancing (NLB) environment
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 25
The recommended Planning and Consolidation practice is to assign resources using a round robin approach for loadbalancing
You can install the SQL OLAP and FileShare types remotely from the application server You need to performadditional server installations if you have multiple application servers
Installing each Planning and Consolidation application server in a multiserver (NLB) configuration is identical to theprocedure 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 Balancingenvironment With this option there is an additional choice to Include sample environment (required on only oneof the application servers) This is because when you install the application server it connects to the databaseserver and creates the sample environment (EnvironmentShell) Installing the sample environment is requiredon 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
26
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
3 After Installing Planning and ConsolidationServers
31 Post-Installation Steps
Procedure
Perform these steps after installing the Planning and Consolidation servers for new installations of Planning andConsolidation
1 Connect your Planning and Consolidation system to Solution Manager Diagnostics (SMD) to allow support staffto identify analyze and resolve problems with your application See Connecting to Solution ManagerDiagnostics [page 28]
2 Configure the Planning and Consolidation NET and application server to ensure that it and its related servicesfunction properly and reliably For more information see Configuring the Planning and Consolidation NETApplication Server [page 29]
3 Optional configuration steps [page 29]
1 To ensure proper functioning of the Management Console create an SQL user and modify the System DSNand 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 loggingfor ODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default WebSite [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory canaccess the Management Console with whatever rights they have been granted on the server Forinformation about removing default access and creating a group that can access the console see RemovingDefault Access to the Console [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommendthat you only grant Management Console access to system administrators Planning and Consolidationusers should not have any access For more information see Management Console AccessControl [page 33]
6 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
4 Take the following steps to set up security
If you are defining security and application structure continue with step 5
If you want to designate someone other than the system administrator to manage security and applicationstructure log on to EnvironmentShell designate a user as a Primary Administrator
This user must have Administration ndash Environment and Security ‒ Define User task rights so that he or shecan 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 SeeInstalling the Administration Client [page 37]
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 27
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 taskprofiles 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 mustcomplete this step since there is no access to dimensions or members)
NoteTo allow users to request and query large amounts of data you can edit the metabasexml file located at CWindowssystem32inetsrv Set the following parameters to the stated values
ASPBUFFERINGLIMIT = 10485760
MAXREQUESTENTITYALLOWED = 10485760
32 Connecting to Solution Manager Diagnostics
NoteYou only need to perform the steps in this section if you have a SAP Solution Manager licence
The diagnostics functions in SAP Solution Manager allow identification analysis and resolution of problems Thisprocedure 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 areinstalled
NoteInstallation files for Diagnostics Agent are available on Service Marketplace by navigating to SupportPackages and Patches mdash Entry by Application Group SAP Technology Components SAP SOLUTIONMANAGER SAP SOLUTION MANAGER 70 EHP 1 Entry by Component Agents for managed systemsDIAGNOSTICS AGENT 711
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 whereMicrosoft 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
28
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
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 ServiceMarketplace at servicesapcom~sapidb011000358700000074392009E and follow the chapters that applyto Planning and Consolidation
33 Configuring the Planning and Consolidation NETApplication Servers
Procedure
Modifying machineconfig Files
To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock occurrences that wouldcause the application server to ldquosleeprdquo and not process anymore you can modify the machineconfig file whichresides in the WINDOWSMicrosoftNETFramework64v4030319Config directory
1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to specifywhether to automatically configure settings to achieve optimal performance based on the machineconfiguration You can set this attribute to True or False
For more information see msdnmicrosoftcomen-uslibrary7w2sway1aspx
2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the Planning andConsolidation application) or Machineconfig (for all applications including Planning and Consolidation) toensure the validationKey and decryptionKey keys have the same value on all application servers Thisway when the authentication cookie is checked the authentication ticket used on one server can still be validon another server
For more information and sample Visual Basic code for generating random key values seemsdnmicrosoftcomen-uslibraryms998288aspxpaght000007_webfarmdeploymentconsiderationsand msdnmicrosoftcomen-uslibraryms998310aspx
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 DSNand 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 forODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory can accessthe Management Console with whatever rights they have been granted on the server For information about
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 29
removing default access and creating a group that can access the console see Removing Default Access to theConsole [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommend thatyou only grant Management Console access to system administrators Planning and Consolidation users shouldnot have any access For more information see Management Console Access Control [page 33]
6 Configure the use of SSL in Planning and Consolidation See Configuring Planning and Consolidation to useSSL [page 34]
7 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
8 Configure Microsoft SQL Server Reporting Services to use SSL See Configuring MS SQL Server ReportingServices to use SSL [page 36]
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 databaserole 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 optionto use ODBC Logging Enter the following values
DSN is BPC_ManagementDSN Table is BPCLog The Microsoft SQL Server Username and Password
5 Restart IIS
NoteWithout these updates the Management Console does work but some functionality (specifically User Activityand Service Status) does not work as expected
Should you need to uninstall Planning and Consolidation we recommend that you reset the Active Log Formatfield in IIS to W3C Extended Log File Format
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
30
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
Prerequisites
ODBC logging has been configured according to the Microsoft Knowledge Base article 245243 How to configureODBC 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 inApplicationHostconfig as shown here
ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0logFormat=Custom gtUse 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-00AA006111E0appcmd 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 articlespecified in the Prerequisites section Configure these settings in the ltodbcLogginggt node underltsystemwebServergt
Exampleltlocation path=Default Web SitegtltsystemwebServergtltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog userName=Usernamepassword=mypassword gtltsystemwebServergtltlocationgt
Use the following AppCmds to configure these attributes for the default Web site
appcmd set config Default Web Site sectionodbcLogging dataSourceBPC_ManagementDSN commitappHostappcmd set config Default Web Site sectionodbcLogging tableNameBPCLog commitappHostappcmd set config Default Web Site sectionodbcLogging userNameUsername commitappHostappcmd set config Default Web Site sectionodbcLogging passwordmypassword commitappHost
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 31
NoteYou cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must use the SQL ServerODBC driver For more information see the Microsoft Knowledge Base article 931202 The requirements for usingthe ODBC logging feature in IIS
343 Setting Up an ODBC Data Source in Windows Server2008 2008 R2 2012 or 2012 R2
Procedure
This procedure describes how to set up an ODBC data source for the Management Console in Windows Server 20082008 R2 2012 or 2012 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
NoteIf you have chosen SAP BusinessObjects User Management System in the installation screen you do not needto remove or configure access because the Management Console service always runs with the System Admin IDaccount which is a member of the Administrators group
Procedure
To remove default access to the Management Console and create a group that does have access to the console usethe procedure described below
32
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
NoteCreate your Management Console administrative group either on the server that hosts the Management Consoleor 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
NoteAlternatively you can perform analogous steps in Active Directory
3 In the Groups context menu choose New Group
4 Enter data as required Click Create
5 In the Computer Management dialog box choose Services and Applications Internet InformationServices 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 objectand all child objects Include these with entries explicitly defined here checkbox
NoteThis step is a necessary precursor to the completion of this procedure
10 In the Security dialog box click Copy to ensure that the System group retains its privileges
11 Remove access to the Management Console from all groups that should not have it
12 Choose Authentication in the center pane then disable Windows authentication
Result
Users who have not been granted access to the Management Console can still open the Management Console Webpage but it contains no data or menu options This does not affect the access that a user would otherwise have toPlanning and Consolidation
345 Management Console Access Control
After establishing the Management Console group you can add users or groups to it For more information aboutcreating this group see Removing Default Access to the Console [page 32] Their rights in Active Directory determinewhat they can access in the Console
By default any member of the Administrators Active Directory group on the application server or domain has fullaccess to all of the features of the Console except the Planning and Consolidation logging area Access to Planningand Consolidation logging is controlled within the Planning and Consolidation Administration Client task securityThe user must be granted View system logs task privileges For more information see the SAP Library Planning and
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 33
Consolidation Administrators Guide in servicesapcominstguidesepm-bpc 100 version for the Microsoftplatform
Your IT policy determines whether you grant access by group or user You may wish to create several levels of Consoleusers (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 describedin this table
Table 9
Privilege Rights Management Area
Task Manager and Kill Process Administrators group on application server or domain
Performance Monitor Counters Administrators group on application server or domain
Power Users group on application server or domain
Performance Monitor Users group on application server
Microsoft Analysis Services performance monitoring Administrators group on application server or domain
Microsoft SQL Server Monitoring (performance counters andstatistics)
Administrators group on application server or domain
346 Configuring Planning and Consolidation to use SSL
Procedure
Creating a Certificate for the Server
During the handshake phase of the SSL communication the server must send its certificate to the client The clientthen uses the certificate to encrypt information and send it back to the server
The procedure below describes how to create a self-signed certificate for the server
RecommendationWe recommend that you limit the use of self-signed certificates to testing only For a productive system you shouldobtain a certificate signed by a well-known certification authority (CA)
1 Start the Internet Information Services (IIS) Manager To do that go to Start All Programs AdministrativeTools Internet Information Services (IIS) Manager
2 In the Connections panel on the left-hand side select the server node and then choose Server Certificates
3 In the Actions panel on the right hand side choose the Create Self-Signed Certificate action
4 Enter the name that you want the certificate to be identified by for example MyTestSSLCertificate
IIS generates a new SSL certificate for you that has one yearrsquos expiry lease The certificate is issued to the local servername
Binding the Certificate to the Web Site
The procedure below describes how to bind the certificate to the web site for which SSL connections must be used
1 In the Connections panel select the web site node
2 In the Actions panel choose Bindings
34
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
3 In the Site Bindings dialog that appears choose the Add button to create a new binding
4 Configure the parameters as follows
Type = https IP Address = [1] - this is a shorthand expression for the local server name
Port = 443 - this is the default SSL port
SSL Certificate = enter your newly created certificate name
5 Choose OK to create the new binding and then close the Site Bindings dialog
6 Restart the IIS processes To do this choose Restart from the Actions panel
7 In the middle panel under the IIS section choose SSL Settings
8 In the SSL Settings screen select the Require SSL checkbox
9 In the Actions panel choose to Apply these settings
To test the SSL connection in the Actions panel choose the Browse [1] 443 (https) link
347 Using Client Certificates
To enable the use of client certificates in Planning and Consolidation you must follow several manual steps
NotePlanning and Consolidation supports client certificate authentication in Windows Authentication Mode butdoes 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 technetmicrosoftcomen-uslibrarycc753810aspx
For more information about configuring the client certificate mapping authentication see technetmicrosoftcomen-uslibrarycc732996(WS10)aspx
When you create the client certificates you can set the type of certificate in the SSL Settings screen in InternetInformation Services (IIS) Manager
Procedure
1 Set the options for client certificates
1 In the IIS Manager select the web site where you installed Planning and Consolidation
2 Choose SSL Settings
3 In the Client certificates section select the Accept client certificates option
This option allows you to use a client certificate or username and password (Basic authentication) toconnect 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 theManagementConsole home page
3 Double-click Authentication and enable Anonymous Authentication
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 35
4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way asin step 3
5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the sameway 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
348 Configuring MS SQL Server Reporting Services to useSSL
Procedure
The procedure below describes how to configure the use of SSL in Microsoft SQL Server Reporting Services
NoteReporting Services does not provide functionalities for generating requesting or installing a certificate Theserver certificates that you want to use for configuring SSL must have already been installed on your computer
1 Open the Reporting Services Configuration Manager program To do this open the Windows Start menu andnavigate to All Programs Microsoft SQL Server ltversiongt Configuration Tools Reporting ServicesConfiguration Manager
2 In the Connect panel on the left-hand side select the Web Service URL option to open all the Report Server webservice parameters
3 Configure the parameters as follows
SSL Certificate = the name of the certificate that you want to use
SSL Port = 4434 Choose Apply to confirm the changes
5 In the Connect panel choose Report Manager URL to open the list of parameters that link Reporting Servicesto IIS
6 Choose Advanced to add your new SSL web URL
7 In the section Multiple SSL Identities for Report Manager choose Add Configure the parameters as follows
IP Address = (All IPv4) SSL Port = 443 Certificate = the name of your SSL certificate
8 To test the configuration click the URL that appears under the Report manager Site Identification section
36
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
4 Installing Planning and ConsolidationAdministration Client and the SAPBusinessObjects EPM solutions Add-in forMicrosoft Office
The installation of the Planning and Consolidation Administration Client allows administrators to build and maintainPlanning and Consolidation environments and models and administer security
All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions add-in forMicrosoft 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 valueof the Planning and Consolidation client to prompt for user name and password Otherwise the Planning andConsolidation Start Page does not display
41 Installing the Administration Client
Prerequisites
NoteFor a definitive list of system requirements see the Product Availability Matrix on SAP Service Marketplace atservicesapcompam Search on Planning and Consolidation
The following list describes the minimum software requirements
Microsoft Internet Explorer 70 80 90 or 10
Microsoft Office 2003 2007 2010 or 2012
NET Framework 20 or higher (install any required NET Framework Hotfixes by referring tosupportmicrosoftcomkb)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 37
NoteWe recommend that you install all of the latest Microsoft Windows hotfixes prior to installing the Administrationclient For information about which hotfixes to install see updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us
Procedure
The 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 ltPC_serverportgtsapbpcweb
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 mustdownload the most recent version of the full setup (EPM Add-inexe) from the Service Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPCInstallation folder
Individual users can install the EPM add-in on their own machines by going to the Planning and Consolidation Homepage 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 upthe 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
38
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
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 toperform the upgrade If Client Auto Update is not enabled and a newer version is detected clients must be installedmanually 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 andpassword in the Admin ID and Admin password fields respectively The Admin ID should be a member of thelocal administrators group on all the computers running the auto update This setting is not needed if all usershave 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 Thisoption is stored in the user preferences and may also be turned on or off using the User Optionshellip menu itemIf 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 toinstall 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 installit 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 servicesapcom
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 versionand policy information For a support package these files are
EPM Addin Support Package ltSP versiongtmsp EPM Addin Support Package ltSP versiongtxmlFor a patch these files are
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 (WebsrvrWebBPCInstallation)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 39
You can set a different update policy for each package listed
ExampleThe following table illustrates some possible situations assuming that you have installed the first full version(V1)
Table 10
Available maintenancepackages
V2-user update
V3-force update
V4-force update
V5-user update
V5-user update V5-user update
V6-auto update
V7-force update
Minimum RequiredVersion
V4 V4 V7
Notification A prompt tells the user toinstall maintenancepackage V4 using theForced Update behavior
If User Update is enabledthe prompt informs theuser that maintenancepackage V5 is available
A prompt tells the user toinstall maintenancepackage V7 using theForced Update behavior
New Version V4 V4 or V5 V7
If you change the update policy for any package click Update to complete the change
40
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
5 Connection Issues
You may experience connection problems with ports the proxy server or programs and settings that interact withthese components If you have any issues related to connection review the following recommendations andtroubleshooting tips
51 Checking for Open Ports
You must ensure that all required ports are open for inboundoutbound traffic By default Planning andConsolidation requires that Ports 80 (used by http) and 1433 and 2383 (used by SQL Server 2008) are open Totest whether the required ports are open go to a command prompt and enter the Telnet serveripaddress and portFor example Telnet 431181836 80 If the system returns a blank command window the port is open If it returnsa message stating that it is unable to connect the port is not open
NoteYou can use the following site to scan for the normal ports It allows you to manually enter a port number to test
wwwmyserverorgportsniffasp
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 Planningand Consolidation server as an exception You can do this at the client level ( Internet Explorer ToolsInternet 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 fullyqualified 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 Consolidationauthentication Do not use authentication on the proxy server The system synchronizes the user name andpassword on the remote server with the local user name and password
SAP Business Planning and Consolidation 100Connection Issues
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 41
NoteFor more information about setting up an ISA proxy server contact SAP Support to request a copy of Setting upISA Proxy Server White Paper For more information about Business Planning and Consolidation firewall portssee SAP Note 1505250
Internet Explorer Settings Issues
Internet Explorer settings must be set correctly to prevent errors and problems when you attempt to access thePlanning 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 insertthe IP address or fully qualified server name of the Planning and Consolidation server as an exception bychoosing 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
42
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Connection Issues
6 Installing Planning and Consolidation withTwo Active Directory Domains
To set up a Planning and Consolidation 10 application server in a hosted environment and use your own domainusers follow this procedure In general you install Planning and Consolidation on the host domain use the hostdomain account and assign it to the Planning and Consolidation users SysAdmin Admin and Users Then you acceptone 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 andpassword 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 topromote 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 privilegefor the Planning and Consolidation server
5 Install Planning and Consolidation and assign your domain account either to the three Planning andConsolidation administrative users SysAdmin Admin and Users or to only one of the three Planning andConsolidation administrative users and to three of your users Be sure you use your own user account ratherthan host domain users
Planning and Consolidation impersonation can then access your domain from the host environment becauseit has the privilege of your domain account
SAP Business Planning and Consolidation 100Installing Planning and Consolidation with Two Active Directory Domains
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 43
7 Installing Planning and Consolidation in aTerminal Services or Citrix ServerDeployment
This section describes best practices and instructions for installing Planning and Consolidation in a Terminal Servicesor Citrix Server deployment
71 Terminal Services Home Directories
We recommend using Terminal Server home directories rather than using the userrsquos profile directory The profiledirectory downloads a minimal amount of information about the dimensions of the environment you are logging onto and may be as large as 2 MB per user The profile directory is on the system drive and has limited space Byspecifying 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 individualserver 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 clientserver (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
44
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
Procedure
The following steps outline how to install the Planning and Consolidation clients in a Terminal Services (TS) or CitrixServer deployment
1 Make sure the Terminal Services or Citrix Server machine has the system requirements installed
2 Log on to the Terminal Services or Citrix Server machine with a user ID that has the rights to install on thatserver
3 At a command prompt enter Change userinstall
4 Open a browser and connect to the URL ltPC_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_MSBPCAdminMainexe
74 Creating a Shortcut to the Launch Page
Procedure
If you use published desktops instead of published applications the Planning and Consolidation desktop file (whichis installed on the current userrsquos desktop) must be moved to the All UsersDesktop folder
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 45
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 SQLServer 2012 support the remote modification of SSIS packages Planning and Consolidation also supports theremote 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 whichyou want to modify SSIS packages
These custom tasks reference dlls that connect to the database server and perform certain validation when usersset up the parameters of each task All the custom task reference components must also be installed in the machineon which you want to modify SSIS packages
We provide a program that registers all the reference components of the custom tasks This section explains theinstallation 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 ndash This folder contains all the dlls that should be installed on the machine There are Planning andConsolidation platform components and all of the Data Manager custom task files
Config folder ndash This folder contains only one file named Filelistxml and lists all of the files that should be installedIf you need to add or remove certain components from the installation you can modify this xml file
OSoftSetupexe ndash This is the main executable file to run the installation package
NoteIf you are not installing SSIS Custom Tasks on your client machine ndash specifically a machine other than the Planningand Consolidation application server ndash you must first install OSoftSSIS2008_Client or OSoftSSIS2012_Client onthe client machine followed by the SQL Server version If you want to use SQL 2008 Tasks under the SQL 2012environment you must install OSoftSSIS2008_Client on the application server For detailed information see SAPNote 1707410 You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package byextracting OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPCInstallation folder on the Planning and Consolidation server To modify SSIS packages on the Planning andConsolidation application server you need to install OSoftSSIS2008_Client or OSoftSSIS2012_Client for creatinga COM+ application For more information see Before You Modify the SSIS Packages [page 49] and Setup ofa COM+ Application on the Application Server [page 50]
Bin folder
This folder contains the following components
46
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Table 11
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012respectively
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
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 47
Name Remark
BPCWriteBackdll
InteropDTSdll
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 addmore components to the installation package you can copy the new components into the Bin folder and add theproper xml tags in FileListxml You need to enter information for the following tags
RegistType ndash This is the registration information of the component You can enter the following values
RegAsm ndash For NET component
48
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Regsvr32 ndash For VB6 component
Gacutil ndash For NET Framework component that should be registered into Global Assembly Cache
FileName ndash Component file name
OSoftSetupexe
This is the executable file to run the SSIS installation package Double-click the file to start the installation You needto enter information for the following fields
Set SQL server
Specify the SQL server name If your SQL Server has an instance specify the instance name
NoteIf you installed the OSoftSSIS2008_Client or OSoftSSIS2012_Client on the application server the SQL servername is automatically disabled
Set server credential
This is the credential name of the COM+ package component Enter the user ID and password that can accessyour SQL Server This should be either the System Admin ID or Admin ID that was registered as a COM+ userwhen 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 ifyou 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 packagesremotely This is also true for the application server that has SSIS installed The Planning and ConsolidationData Manager has the following custom tasks
Table 12
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008and 2012 respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and2012 respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012respectively
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 49
Name Remark
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and2012 respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008and 2012 respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL2008 and 2012 respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and2012 respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012respectively
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
ltdrivegtWebsrvrbin2 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 FilesMicrosoft SQLServer paste all files into the CProgram Files (x86)Microsoft SQL Server100DTSTasksfolder
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
50
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Typographic Conventions
Table 13
Example Description
lt gt Angle brackets indicate that you replace these words or characters with appropriate entries tomake entries in the system for example Enter your ltUser Namegt
File Save Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
Example Textual cross-references to an internet address for example wwwsapcom
example Quicklinks added to the internet address of a homepage to enable quick access to specificcontent 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 titlespushbutton 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 namesof installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transactioncodes database table names and key concepts of a programming language when they aresurrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
SAP Business Planning and Consolidation 100Typographic Conventions
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 51
52
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
wwwsapcom
Material Number
- SAP Business 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 2008 R2 2012 or 2012 R2
- 344 Removing Default Access to the Console
- 345 Management Console Access Control
- 346 Configuring Planning and Consolidation to use SSL
- 347 Using Client Certificates
- 348 Configuring MS SQL Server Reporting Services to use SSL
-
- 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
-
Table 8
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 Thisgroup name is filtered as the default when adding a user in Planning andConsolidation Administration Use a comma ( ) to separate multiple names
12 After entering the CMS administrator authentication details choose Next
13 From the Service type accounts page enter service-level account user IDs and passwords See Service-LevelAccounts [page 15]
14 After defining the IDs and passwords choose Next
15 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 chooseNext
16 Specify the location and name of AntiXssLibrarydll See Installing the Anti-Cross Site ScriptingLibrary [page 23]
Choose Next
17 Select destination folders for Programs and Data The Data files include Webfolders and FileDB (publishedreports) and should be installed on a separate drive in a production environment This recommendation reducesthe hard disk IO time and helps to speed up SQL commands
Accept the defaults or make your selections then choose Next
18 Select the default values for the Web client The values are used to determine the default language and regionfor the Web client when you connect to it You can change the values in the Planning and Consolidation ServerManager
19 The installation process takes a few moments When it is complete choose Exit
20 A prompt is displayed to restart your computer Select OK to restart
21 Perform the steps in After Installing Planning and Consolidation Servers [page 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 avariety of ways and configure the servers as a Network Load Balancing (NLB) environment
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 25
The recommended Planning and Consolidation practice is to assign resources using a round robin approach for loadbalancing
You can install the SQL OLAP and FileShare types remotely from the application server You need to performadditional server installations if you have multiple application servers
Installing each Planning and Consolidation application server in a multiserver (NLB) configuration is identical to theprocedure 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 Balancingenvironment With this option there is an additional choice to Include sample environment (required on only oneof the application servers) This is because when you install the application server it connects to the databaseserver and creates the sample environment (EnvironmentShell) Installing the sample environment is requiredon 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
26
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
3 After Installing Planning and ConsolidationServers
31 Post-Installation Steps
Procedure
Perform these steps after installing the Planning and Consolidation servers for new installations of Planning andConsolidation
1 Connect your Planning and Consolidation system to Solution Manager Diagnostics (SMD) to allow support staffto identify analyze and resolve problems with your application See Connecting to Solution ManagerDiagnostics [page 28]
2 Configure the Planning and Consolidation NET and application server to ensure that it and its related servicesfunction properly and reliably For more information see Configuring the Planning and Consolidation NETApplication Server [page 29]
3 Optional configuration steps [page 29]
1 To ensure proper functioning of the Management Console create an SQL user and modify the System DSNand 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 loggingfor ODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default WebSite [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory canaccess the Management Console with whatever rights they have been granted on the server Forinformation about removing default access and creating a group that can access the console see RemovingDefault Access to the Console [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommendthat you only grant Management Console access to system administrators Planning and Consolidationusers should not have any access For more information see Management Console AccessControl [page 33]
6 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
4 Take the following steps to set up security
If you are defining security and application structure continue with step 5
If you want to designate someone other than the system administrator to manage security and applicationstructure log on to EnvironmentShell designate a user as a Primary Administrator
This user must have Administration ndash Environment and Security ‒ Define User task rights so that he or shecan 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 SeeInstalling the Administration Client [page 37]
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 27
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 taskprofiles 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 mustcomplete this step since there is no access to dimensions or members)
NoteTo allow users to request and query large amounts of data you can edit the metabasexml file located at CWindowssystem32inetsrv Set the following parameters to the stated values
ASPBUFFERINGLIMIT = 10485760
MAXREQUESTENTITYALLOWED = 10485760
32 Connecting to Solution Manager Diagnostics
NoteYou only need to perform the steps in this section if you have a SAP Solution Manager licence
The diagnostics functions in SAP Solution Manager allow identification analysis and resolution of problems Thisprocedure 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 areinstalled
NoteInstallation files for Diagnostics Agent are available on Service Marketplace by navigating to SupportPackages and Patches mdash Entry by Application Group SAP Technology Components SAP SOLUTIONMANAGER SAP SOLUTION MANAGER 70 EHP 1 Entry by Component Agents for managed systemsDIAGNOSTICS AGENT 711
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 whereMicrosoft 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
28
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
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 ServiceMarketplace at servicesapcom~sapidb011000358700000074392009E and follow the chapters that applyto Planning and Consolidation
33 Configuring the Planning and Consolidation NETApplication Servers
Procedure
Modifying machineconfig Files
To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock occurrences that wouldcause the application server to ldquosleeprdquo and not process anymore you can modify the machineconfig file whichresides in the WINDOWSMicrosoftNETFramework64v4030319Config directory
1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to specifywhether to automatically configure settings to achieve optimal performance based on the machineconfiguration You can set this attribute to True or False
For more information see msdnmicrosoftcomen-uslibrary7w2sway1aspx
2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the Planning andConsolidation application) or Machineconfig (for all applications including Planning and Consolidation) toensure the validationKey and decryptionKey keys have the same value on all application servers Thisway when the authentication cookie is checked the authentication ticket used on one server can still be validon another server
For more information and sample Visual Basic code for generating random key values seemsdnmicrosoftcomen-uslibraryms998288aspxpaght000007_webfarmdeploymentconsiderationsand msdnmicrosoftcomen-uslibraryms998310aspx
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 DSNand 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 forODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory can accessthe Management Console with whatever rights they have been granted on the server For information about
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 29
removing default access and creating a group that can access the console see Removing Default Access to theConsole [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommend thatyou only grant Management Console access to system administrators Planning and Consolidation users shouldnot have any access For more information see Management Console Access Control [page 33]
6 Configure the use of SSL in Planning and Consolidation See Configuring Planning and Consolidation to useSSL [page 34]
7 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
8 Configure Microsoft SQL Server Reporting Services to use SSL See Configuring MS SQL Server ReportingServices to use SSL [page 36]
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 databaserole 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 optionto use ODBC Logging Enter the following values
DSN is BPC_ManagementDSN Table is BPCLog The Microsoft SQL Server Username and Password
5 Restart IIS
NoteWithout these updates the Management Console does work but some functionality (specifically User Activityand Service Status) does not work as expected
Should you need to uninstall Planning and Consolidation we recommend that you reset the Active Log Formatfield in IIS to W3C Extended Log File Format
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
30
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
Prerequisites
ODBC logging has been configured according to the Microsoft Knowledge Base article 245243 How to configureODBC 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 inApplicationHostconfig as shown here
ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0logFormat=Custom gtUse 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-00AA006111E0appcmd 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 articlespecified in the Prerequisites section Configure these settings in the ltodbcLogginggt node underltsystemwebServergt
Exampleltlocation path=Default Web SitegtltsystemwebServergtltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog userName=Usernamepassword=mypassword gtltsystemwebServergtltlocationgt
Use the following AppCmds to configure these attributes for the default Web site
appcmd set config Default Web Site sectionodbcLogging dataSourceBPC_ManagementDSN commitappHostappcmd set config Default Web Site sectionodbcLogging tableNameBPCLog commitappHostappcmd set config Default Web Site sectionodbcLogging userNameUsername commitappHostappcmd set config Default Web Site sectionodbcLogging passwordmypassword commitappHost
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 31
NoteYou cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must use the SQL ServerODBC driver For more information see the Microsoft Knowledge Base article 931202 The requirements for usingthe ODBC logging feature in IIS
343 Setting Up an ODBC Data Source in Windows Server2008 2008 R2 2012 or 2012 R2
Procedure
This procedure describes how to set up an ODBC data source for the Management Console in Windows Server 20082008 R2 2012 or 2012 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
NoteIf you have chosen SAP BusinessObjects User Management System in the installation screen you do not needto remove or configure access because the Management Console service always runs with the System Admin IDaccount which is a member of the Administrators group
Procedure
To remove default access to the Management Console and create a group that does have access to the console usethe procedure described below
32
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
NoteCreate your Management Console administrative group either on the server that hosts the Management Consoleor 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
NoteAlternatively you can perform analogous steps in Active Directory
3 In the Groups context menu choose New Group
4 Enter data as required Click Create
5 In the Computer Management dialog box choose Services and Applications Internet InformationServices 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 objectand all child objects Include these with entries explicitly defined here checkbox
NoteThis step is a necessary precursor to the completion of this procedure
10 In the Security dialog box click Copy to ensure that the System group retains its privileges
11 Remove access to the Management Console from all groups that should not have it
12 Choose Authentication in the center pane then disable Windows authentication
Result
Users who have not been granted access to the Management Console can still open the Management Console Webpage but it contains no data or menu options This does not affect the access that a user would otherwise have toPlanning and Consolidation
345 Management Console Access Control
After establishing the Management Console group you can add users or groups to it For more information aboutcreating this group see Removing Default Access to the Console [page 32] Their rights in Active Directory determinewhat they can access in the Console
By default any member of the Administrators Active Directory group on the application server or domain has fullaccess to all of the features of the Console except the Planning and Consolidation logging area Access to Planningand Consolidation logging is controlled within the Planning and Consolidation Administration Client task securityThe user must be granted View system logs task privileges For more information see the SAP Library Planning and
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 33
Consolidation Administrators Guide in servicesapcominstguidesepm-bpc 100 version for the Microsoftplatform
Your IT policy determines whether you grant access by group or user You may wish to create several levels of Consoleusers (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 describedin this table
Table 9
Privilege Rights Management Area
Task Manager and Kill Process Administrators group on application server or domain
Performance Monitor Counters Administrators group on application server or domain
Power Users group on application server or domain
Performance Monitor Users group on application server
Microsoft Analysis Services performance monitoring Administrators group on application server or domain
Microsoft SQL Server Monitoring (performance counters andstatistics)
Administrators group on application server or domain
346 Configuring Planning and Consolidation to use SSL
Procedure
Creating a Certificate for the Server
During the handshake phase of the SSL communication the server must send its certificate to the client The clientthen uses the certificate to encrypt information and send it back to the server
The procedure below describes how to create a self-signed certificate for the server
RecommendationWe recommend that you limit the use of self-signed certificates to testing only For a productive system you shouldobtain a certificate signed by a well-known certification authority (CA)
1 Start the Internet Information Services (IIS) Manager To do that go to Start All Programs AdministrativeTools Internet Information Services (IIS) Manager
2 In the Connections panel on the left-hand side select the server node and then choose Server Certificates
3 In the Actions panel on the right hand side choose the Create Self-Signed Certificate action
4 Enter the name that you want the certificate to be identified by for example MyTestSSLCertificate
IIS generates a new SSL certificate for you that has one yearrsquos expiry lease The certificate is issued to the local servername
Binding the Certificate to the Web Site
The procedure below describes how to bind the certificate to the web site for which SSL connections must be used
1 In the Connections panel select the web site node
2 In the Actions panel choose Bindings
34
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
3 In the Site Bindings dialog that appears choose the Add button to create a new binding
4 Configure the parameters as follows
Type = https IP Address = [1] - this is a shorthand expression for the local server name
Port = 443 - this is the default SSL port
SSL Certificate = enter your newly created certificate name
5 Choose OK to create the new binding and then close the Site Bindings dialog
6 Restart the IIS processes To do this choose Restart from the Actions panel
7 In the middle panel under the IIS section choose SSL Settings
8 In the SSL Settings screen select the Require SSL checkbox
9 In the Actions panel choose to Apply these settings
To test the SSL connection in the Actions panel choose the Browse [1] 443 (https) link
347 Using Client Certificates
To enable the use of client certificates in Planning and Consolidation you must follow several manual steps
NotePlanning and Consolidation supports client certificate authentication in Windows Authentication Mode butdoes 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 technetmicrosoftcomen-uslibrarycc753810aspx
For more information about configuring the client certificate mapping authentication see technetmicrosoftcomen-uslibrarycc732996(WS10)aspx
When you create the client certificates you can set the type of certificate in the SSL Settings screen in InternetInformation Services (IIS) Manager
Procedure
1 Set the options for client certificates
1 In the IIS Manager select the web site where you installed Planning and Consolidation
2 Choose SSL Settings
3 In the Client certificates section select the Accept client certificates option
This option allows you to use a client certificate or username and password (Basic authentication) toconnect 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 theManagementConsole home page
3 Double-click Authentication and enable Anonymous Authentication
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 35
4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way asin step 3
5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the sameway 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
348 Configuring MS SQL Server Reporting Services to useSSL
Procedure
The procedure below describes how to configure the use of SSL in Microsoft SQL Server Reporting Services
NoteReporting Services does not provide functionalities for generating requesting or installing a certificate Theserver certificates that you want to use for configuring SSL must have already been installed on your computer
1 Open the Reporting Services Configuration Manager program To do this open the Windows Start menu andnavigate to All Programs Microsoft SQL Server ltversiongt Configuration Tools Reporting ServicesConfiguration Manager
2 In the Connect panel on the left-hand side select the Web Service URL option to open all the Report Server webservice parameters
3 Configure the parameters as follows
SSL Certificate = the name of the certificate that you want to use
SSL Port = 4434 Choose Apply to confirm the changes
5 In the Connect panel choose Report Manager URL to open the list of parameters that link Reporting Servicesto IIS
6 Choose Advanced to add your new SSL web URL
7 In the section Multiple SSL Identities for Report Manager choose Add Configure the parameters as follows
IP Address = (All IPv4) SSL Port = 443 Certificate = the name of your SSL certificate
8 To test the configuration click the URL that appears under the Report manager Site Identification section
36
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
4 Installing Planning and ConsolidationAdministration Client and the SAPBusinessObjects EPM solutions Add-in forMicrosoft Office
The installation of the Planning and Consolidation Administration Client allows administrators to build and maintainPlanning and Consolidation environments and models and administer security
All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions add-in forMicrosoft 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 valueof the Planning and Consolidation client to prompt for user name and password Otherwise the Planning andConsolidation Start Page does not display
41 Installing the Administration Client
Prerequisites
NoteFor a definitive list of system requirements see the Product Availability Matrix on SAP Service Marketplace atservicesapcompam Search on Planning and Consolidation
The following list describes the minimum software requirements
Microsoft Internet Explorer 70 80 90 or 10
Microsoft Office 2003 2007 2010 or 2012
NET Framework 20 or higher (install any required NET Framework Hotfixes by referring tosupportmicrosoftcomkb)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 37
NoteWe recommend that you install all of the latest Microsoft Windows hotfixes prior to installing the Administrationclient For information about which hotfixes to install see updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us
Procedure
The 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 ltPC_serverportgtsapbpcweb
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 mustdownload the most recent version of the full setup (EPM Add-inexe) from the Service Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPCInstallation folder
Individual users can install the EPM add-in on their own machines by going to the Planning and Consolidation Homepage 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 upthe 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
38
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
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 toperform the upgrade If Client Auto Update is not enabled and a newer version is detected clients must be installedmanually 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 andpassword in the Admin ID and Admin password fields respectively The Admin ID should be a member of thelocal administrators group on all the computers running the auto update This setting is not needed if all usershave 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 Thisoption is stored in the user preferences and may also be turned on or off using the User Optionshellip menu itemIf 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 toinstall 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 installit 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 servicesapcom
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 versionand policy information For a support package these files are
EPM Addin Support Package ltSP versiongtmsp EPM Addin Support Package ltSP versiongtxmlFor a patch these files are
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 (WebsrvrWebBPCInstallation)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 39
You can set a different update policy for each package listed
ExampleThe following table illustrates some possible situations assuming that you have installed the first full version(V1)
Table 10
Available maintenancepackages
V2-user update
V3-force update
V4-force update
V5-user update
V5-user update V5-user update
V6-auto update
V7-force update
Minimum RequiredVersion
V4 V4 V7
Notification A prompt tells the user toinstall maintenancepackage V4 using theForced Update behavior
If User Update is enabledthe prompt informs theuser that maintenancepackage V5 is available
A prompt tells the user toinstall maintenancepackage V7 using theForced Update behavior
New Version V4 V4 or V5 V7
If you change the update policy for any package click Update to complete the change
40
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
5 Connection Issues
You may experience connection problems with ports the proxy server or programs and settings that interact withthese components If you have any issues related to connection review the following recommendations andtroubleshooting tips
51 Checking for Open Ports
You must ensure that all required ports are open for inboundoutbound traffic By default Planning andConsolidation requires that Ports 80 (used by http) and 1433 and 2383 (used by SQL Server 2008) are open Totest whether the required ports are open go to a command prompt and enter the Telnet serveripaddress and portFor example Telnet 431181836 80 If the system returns a blank command window the port is open If it returnsa message stating that it is unable to connect the port is not open
NoteYou can use the following site to scan for the normal ports It allows you to manually enter a port number to test
wwwmyserverorgportsniffasp
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 Planningand Consolidation server as an exception You can do this at the client level ( Internet Explorer ToolsInternet 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 fullyqualified 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 Consolidationauthentication Do not use authentication on the proxy server The system synchronizes the user name andpassword on the remote server with the local user name and password
SAP Business Planning and Consolidation 100Connection Issues
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 41
NoteFor more information about setting up an ISA proxy server contact SAP Support to request a copy of Setting upISA Proxy Server White Paper For more information about Business Planning and Consolidation firewall portssee SAP Note 1505250
Internet Explorer Settings Issues
Internet Explorer settings must be set correctly to prevent errors and problems when you attempt to access thePlanning 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 insertthe IP address or fully qualified server name of the Planning and Consolidation server as an exception bychoosing 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
42
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Connection Issues
6 Installing Planning and Consolidation withTwo Active Directory Domains
To set up a Planning and Consolidation 10 application server in a hosted environment and use your own domainusers follow this procedure In general you install Planning and Consolidation on the host domain use the hostdomain account and assign it to the Planning and Consolidation users SysAdmin Admin and Users Then you acceptone 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 andpassword 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 topromote 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 privilegefor the Planning and Consolidation server
5 Install Planning and Consolidation and assign your domain account either to the three Planning andConsolidation administrative users SysAdmin Admin and Users or to only one of the three Planning andConsolidation administrative users and to three of your users Be sure you use your own user account ratherthan host domain users
Planning and Consolidation impersonation can then access your domain from the host environment becauseit has the privilege of your domain account
SAP Business Planning and Consolidation 100Installing Planning and Consolidation with Two Active Directory Domains
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 43
7 Installing Planning and Consolidation in aTerminal Services or Citrix ServerDeployment
This section describes best practices and instructions for installing Planning and Consolidation in a Terminal Servicesor Citrix Server deployment
71 Terminal Services Home Directories
We recommend using Terminal Server home directories rather than using the userrsquos profile directory The profiledirectory downloads a minimal amount of information about the dimensions of the environment you are logging onto and may be as large as 2 MB per user The profile directory is on the system drive and has limited space Byspecifying 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 individualserver 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 clientserver (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
44
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
Procedure
The following steps outline how to install the Planning and Consolidation clients in a Terminal Services (TS) or CitrixServer deployment
1 Make sure the Terminal Services or Citrix Server machine has the system requirements installed
2 Log on to the Terminal Services or Citrix Server machine with a user ID that has the rights to install on thatserver
3 At a command prompt enter Change userinstall
4 Open a browser and connect to the URL ltPC_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_MSBPCAdminMainexe
74 Creating a Shortcut to the Launch Page
Procedure
If you use published desktops instead of published applications the Planning and Consolidation desktop file (whichis installed on the current userrsquos desktop) must be moved to the All UsersDesktop folder
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 45
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 SQLServer 2012 support the remote modification of SSIS packages Planning and Consolidation also supports theremote 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 whichyou want to modify SSIS packages
These custom tasks reference dlls that connect to the database server and perform certain validation when usersset up the parameters of each task All the custom task reference components must also be installed in the machineon which you want to modify SSIS packages
We provide a program that registers all the reference components of the custom tasks This section explains theinstallation 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 ndash This folder contains all the dlls that should be installed on the machine There are Planning andConsolidation platform components and all of the Data Manager custom task files
Config folder ndash This folder contains only one file named Filelistxml and lists all of the files that should be installedIf you need to add or remove certain components from the installation you can modify this xml file
OSoftSetupexe ndash This is the main executable file to run the installation package
NoteIf you are not installing SSIS Custom Tasks on your client machine ndash specifically a machine other than the Planningand Consolidation application server ndash you must first install OSoftSSIS2008_Client or OSoftSSIS2012_Client onthe client machine followed by the SQL Server version If you want to use SQL 2008 Tasks under the SQL 2012environment you must install OSoftSSIS2008_Client on the application server For detailed information see SAPNote 1707410 You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package byextracting OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPCInstallation folder on the Planning and Consolidation server To modify SSIS packages on the Planning andConsolidation application server you need to install OSoftSSIS2008_Client or OSoftSSIS2012_Client for creatinga COM+ application For more information see Before You Modify the SSIS Packages [page 49] and Setup ofa COM+ Application on the Application Server [page 50]
Bin folder
This folder contains the following components
46
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Table 11
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012respectively
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
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 47
Name Remark
BPCWriteBackdll
InteropDTSdll
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 addmore components to the installation package you can copy the new components into the Bin folder and add theproper xml tags in FileListxml You need to enter information for the following tags
RegistType ndash This is the registration information of the component You can enter the following values
RegAsm ndash For NET component
48
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Regsvr32 ndash For VB6 component
Gacutil ndash For NET Framework component that should be registered into Global Assembly Cache
FileName ndash Component file name
OSoftSetupexe
This is the executable file to run the SSIS installation package Double-click the file to start the installation You needto enter information for the following fields
Set SQL server
Specify the SQL server name If your SQL Server has an instance specify the instance name
NoteIf you installed the OSoftSSIS2008_Client or OSoftSSIS2012_Client on the application server the SQL servername is automatically disabled
Set server credential
This is the credential name of the COM+ package component Enter the user ID and password that can accessyour SQL Server This should be either the System Admin ID or Admin ID that was registered as a COM+ userwhen 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 ifyou 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 packagesremotely This is also true for the application server that has SSIS installed The Planning and ConsolidationData Manager has the following custom tasks
Table 12
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008and 2012 respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and2012 respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012respectively
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 49
Name Remark
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and2012 respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008and 2012 respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL2008 and 2012 respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and2012 respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012respectively
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
ltdrivegtWebsrvrbin2 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 FilesMicrosoft SQLServer paste all files into the CProgram Files (x86)Microsoft SQL Server100DTSTasksfolder
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
50
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Typographic Conventions
Table 13
Example Description
lt gt Angle brackets indicate that you replace these words or characters with appropriate entries tomake entries in the system for example Enter your ltUser Namegt
File Save Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
Example Textual cross-references to an internet address for example wwwsapcom
example Quicklinks added to the internet address of a homepage to enable quick access to specificcontent 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 titlespushbutton 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 namesof installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transactioncodes database table names and key concepts of a programming language when they aresurrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
SAP Business Planning and Consolidation 100Typographic Conventions
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 51
52
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
wwwsapcom
Material Number
- SAP Business 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 2008 R2 2012 or 2012 R2
- 344 Removing Default Access to the Console
- 345 Management Console Access Control
- 346 Configuring Planning and Consolidation to use SSL
- 347 Using Client Certificates
- 348 Configuring MS SQL Server Reporting Services to use SSL
-
- 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
-
The recommended Planning and Consolidation practice is to assign resources using a round robin approach for loadbalancing
You can install the SQL OLAP and FileShare types remotely from the application server You need to performadditional server installations if you have multiple application servers
Installing each Planning and Consolidation application server in a multiserver (NLB) configuration is identical to theprocedure 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 Balancingenvironment With this option there is an additional choice to Include sample environment (required on only oneof the application servers) This is because when you install the application server it connects to the databaseserver and creates the sample environment (EnvironmentShell) Installing the sample environment is requiredon 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
26
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Servers
3 After Installing Planning and ConsolidationServers
31 Post-Installation Steps
Procedure
Perform these steps after installing the Planning and Consolidation servers for new installations of Planning andConsolidation
1 Connect your Planning and Consolidation system to Solution Manager Diagnostics (SMD) to allow support staffto identify analyze and resolve problems with your application See Connecting to Solution ManagerDiagnostics [page 28]
2 Configure the Planning and Consolidation NET and application server to ensure that it and its related servicesfunction properly and reliably For more information see Configuring the Planning and Consolidation NETApplication Server [page 29]
3 Optional configuration steps [page 29]
1 To ensure proper functioning of the Management Console create an SQL user and modify the System DSNand 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 loggingfor ODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default WebSite [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory canaccess the Management Console with whatever rights they have been granted on the server Forinformation about removing default access and creating a group that can access the console see RemovingDefault Access to the Console [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommendthat you only grant Management Console access to system administrators Planning and Consolidationusers should not have any access For more information see Management Console AccessControl [page 33]
6 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
4 Take the following steps to set up security
If you are defining security and application structure continue with step 5
If you want to designate someone other than the system administrator to manage security and applicationstructure log on to EnvironmentShell designate a user as a Primary Administrator
This user must have Administration ndash Environment and Security ‒ Define User task rights so that he or shecan 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 SeeInstalling the Administration Client [page 37]
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 27
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 taskprofiles 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 mustcomplete this step since there is no access to dimensions or members)
NoteTo allow users to request and query large amounts of data you can edit the metabasexml file located at CWindowssystem32inetsrv Set the following parameters to the stated values
ASPBUFFERINGLIMIT = 10485760
MAXREQUESTENTITYALLOWED = 10485760
32 Connecting to Solution Manager Diagnostics
NoteYou only need to perform the steps in this section if you have a SAP Solution Manager licence
The diagnostics functions in SAP Solution Manager allow identification analysis and resolution of problems Thisprocedure 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 areinstalled
NoteInstallation files for Diagnostics Agent are available on Service Marketplace by navigating to SupportPackages and Patches mdash Entry by Application Group SAP Technology Components SAP SOLUTIONMANAGER SAP SOLUTION MANAGER 70 EHP 1 Entry by Component Agents for managed systemsDIAGNOSTICS AGENT 711
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 whereMicrosoft 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
28
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
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 ServiceMarketplace at servicesapcom~sapidb011000358700000074392009E and follow the chapters that applyto Planning and Consolidation
33 Configuring the Planning and Consolidation NETApplication Servers
Procedure
Modifying machineconfig Files
To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock occurrences that wouldcause the application server to ldquosleeprdquo and not process anymore you can modify the machineconfig file whichresides in the WINDOWSMicrosoftNETFramework64v4030319Config directory
1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to specifywhether to automatically configure settings to achieve optimal performance based on the machineconfiguration You can set this attribute to True or False
For more information see msdnmicrosoftcomen-uslibrary7w2sway1aspx
2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the Planning andConsolidation application) or Machineconfig (for all applications including Planning and Consolidation) toensure the validationKey and decryptionKey keys have the same value on all application servers Thisway when the authentication cookie is checked the authentication ticket used on one server can still be validon another server
For more information and sample Visual Basic code for generating random key values seemsdnmicrosoftcomen-uslibraryms998288aspxpaght000007_webfarmdeploymentconsiderationsand msdnmicrosoftcomen-uslibraryms998310aspx
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 DSNand 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 forODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory can accessthe Management Console with whatever rights they have been granted on the server For information about
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 29
removing default access and creating a group that can access the console see Removing Default Access to theConsole [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommend thatyou only grant Management Console access to system administrators Planning and Consolidation users shouldnot have any access For more information see Management Console Access Control [page 33]
6 Configure the use of SSL in Planning and Consolidation See Configuring Planning and Consolidation to useSSL [page 34]
7 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
8 Configure Microsoft SQL Server Reporting Services to use SSL See Configuring MS SQL Server ReportingServices to use SSL [page 36]
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 databaserole 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 optionto use ODBC Logging Enter the following values
DSN is BPC_ManagementDSN Table is BPCLog The Microsoft SQL Server Username and Password
5 Restart IIS
NoteWithout these updates the Management Console does work but some functionality (specifically User Activityand Service Status) does not work as expected
Should you need to uninstall Planning and Consolidation we recommend that you reset the Active Log Formatfield in IIS to W3C Extended Log File Format
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
30
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
Prerequisites
ODBC logging has been configured according to the Microsoft Knowledge Base article 245243 How to configureODBC 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 inApplicationHostconfig as shown here
ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0logFormat=Custom gtUse 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-00AA006111E0appcmd 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 articlespecified in the Prerequisites section Configure these settings in the ltodbcLogginggt node underltsystemwebServergt
Exampleltlocation path=Default Web SitegtltsystemwebServergtltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog userName=Usernamepassword=mypassword gtltsystemwebServergtltlocationgt
Use the following AppCmds to configure these attributes for the default Web site
appcmd set config Default Web Site sectionodbcLogging dataSourceBPC_ManagementDSN commitappHostappcmd set config Default Web Site sectionodbcLogging tableNameBPCLog commitappHostappcmd set config Default Web Site sectionodbcLogging userNameUsername commitappHostappcmd set config Default Web Site sectionodbcLogging passwordmypassword commitappHost
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 31
NoteYou cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must use the SQL ServerODBC driver For more information see the Microsoft Knowledge Base article 931202 The requirements for usingthe ODBC logging feature in IIS
343 Setting Up an ODBC Data Source in Windows Server2008 2008 R2 2012 or 2012 R2
Procedure
This procedure describes how to set up an ODBC data source for the Management Console in Windows Server 20082008 R2 2012 or 2012 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
NoteIf you have chosen SAP BusinessObjects User Management System in the installation screen you do not needto remove or configure access because the Management Console service always runs with the System Admin IDaccount which is a member of the Administrators group
Procedure
To remove default access to the Management Console and create a group that does have access to the console usethe procedure described below
32
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
NoteCreate your Management Console administrative group either on the server that hosts the Management Consoleor 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
NoteAlternatively you can perform analogous steps in Active Directory
3 In the Groups context menu choose New Group
4 Enter data as required Click Create
5 In the Computer Management dialog box choose Services and Applications Internet InformationServices 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 objectand all child objects Include these with entries explicitly defined here checkbox
NoteThis step is a necessary precursor to the completion of this procedure
10 In the Security dialog box click Copy to ensure that the System group retains its privileges
11 Remove access to the Management Console from all groups that should not have it
12 Choose Authentication in the center pane then disable Windows authentication
Result
Users who have not been granted access to the Management Console can still open the Management Console Webpage but it contains no data or menu options This does not affect the access that a user would otherwise have toPlanning and Consolidation
345 Management Console Access Control
After establishing the Management Console group you can add users or groups to it For more information aboutcreating this group see Removing Default Access to the Console [page 32] Their rights in Active Directory determinewhat they can access in the Console
By default any member of the Administrators Active Directory group on the application server or domain has fullaccess to all of the features of the Console except the Planning and Consolidation logging area Access to Planningand Consolidation logging is controlled within the Planning and Consolidation Administration Client task securityThe user must be granted View system logs task privileges For more information see the SAP Library Planning and
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 33
Consolidation Administrators Guide in servicesapcominstguidesepm-bpc 100 version for the Microsoftplatform
Your IT policy determines whether you grant access by group or user You may wish to create several levels of Consoleusers (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 describedin this table
Table 9
Privilege Rights Management Area
Task Manager and Kill Process Administrators group on application server or domain
Performance Monitor Counters Administrators group on application server or domain
Power Users group on application server or domain
Performance Monitor Users group on application server
Microsoft Analysis Services performance monitoring Administrators group on application server or domain
Microsoft SQL Server Monitoring (performance counters andstatistics)
Administrators group on application server or domain
346 Configuring Planning and Consolidation to use SSL
Procedure
Creating a Certificate for the Server
During the handshake phase of the SSL communication the server must send its certificate to the client The clientthen uses the certificate to encrypt information and send it back to the server
The procedure below describes how to create a self-signed certificate for the server
RecommendationWe recommend that you limit the use of self-signed certificates to testing only For a productive system you shouldobtain a certificate signed by a well-known certification authority (CA)
1 Start the Internet Information Services (IIS) Manager To do that go to Start All Programs AdministrativeTools Internet Information Services (IIS) Manager
2 In the Connections panel on the left-hand side select the server node and then choose Server Certificates
3 In the Actions panel on the right hand side choose the Create Self-Signed Certificate action
4 Enter the name that you want the certificate to be identified by for example MyTestSSLCertificate
IIS generates a new SSL certificate for you that has one yearrsquos expiry lease The certificate is issued to the local servername
Binding the Certificate to the Web Site
The procedure below describes how to bind the certificate to the web site for which SSL connections must be used
1 In the Connections panel select the web site node
2 In the Actions panel choose Bindings
34
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
3 In the Site Bindings dialog that appears choose the Add button to create a new binding
4 Configure the parameters as follows
Type = https IP Address = [1] - this is a shorthand expression for the local server name
Port = 443 - this is the default SSL port
SSL Certificate = enter your newly created certificate name
5 Choose OK to create the new binding and then close the Site Bindings dialog
6 Restart the IIS processes To do this choose Restart from the Actions panel
7 In the middle panel under the IIS section choose SSL Settings
8 In the SSL Settings screen select the Require SSL checkbox
9 In the Actions panel choose to Apply these settings
To test the SSL connection in the Actions panel choose the Browse [1] 443 (https) link
347 Using Client Certificates
To enable the use of client certificates in Planning and Consolidation you must follow several manual steps
NotePlanning and Consolidation supports client certificate authentication in Windows Authentication Mode butdoes 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 technetmicrosoftcomen-uslibrarycc753810aspx
For more information about configuring the client certificate mapping authentication see technetmicrosoftcomen-uslibrarycc732996(WS10)aspx
When you create the client certificates you can set the type of certificate in the SSL Settings screen in InternetInformation Services (IIS) Manager
Procedure
1 Set the options for client certificates
1 In the IIS Manager select the web site where you installed Planning and Consolidation
2 Choose SSL Settings
3 In the Client certificates section select the Accept client certificates option
This option allows you to use a client certificate or username and password (Basic authentication) toconnect 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 theManagementConsole home page
3 Double-click Authentication and enable Anonymous Authentication
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 35
4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way asin step 3
5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the sameway 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
348 Configuring MS SQL Server Reporting Services to useSSL
Procedure
The procedure below describes how to configure the use of SSL in Microsoft SQL Server Reporting Services
NoteReporting Services does not provide functionalities for generating requesting or installing a certificate Theserver certificates that you want to use for configuring SSL must have already been installed on your computer
1 Open the Reporting Services Configuration Manager program To do this open the Windows Start menu andnavigate to All Programs Microsoft SQL Server ltversiongt Configuration Tools Reporting ServicesConfiguration Manager
2 In the Connect panel on the left-hand side select the Web Service URL option to open all the Report Server webservice parameters
3 Configure the parameters as follows
SSL Certificate = the name of the certificate that you want to use
SSL Port = 4434 Choose Apply to confirm the changes
5 In the Connect panel choose Report Manager URL to open the list of parameters that link Reporting Servicesto IIS
6 Choose Advanced to add your new SSL web URL
7 In the section Multiple SSL Identities for Report Manager choose Add Configure the parameters as follows
IP Address = (All IPv4) SSL Port = 443 Certificate = the name of your SSL certificate
8 To test the configuration click the URL that appears under the Report manager Site Identification section
36
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
4 Installing Planning and ConsolidationAdministration Client and the SAPBusinessObjects EPM solutions Add-in forMicrosoft Office
The installation of the Planning and Consolidation Administration Client allows administrators to build and maintainPlanning and Consolidation environments and models and administer security
All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions add-in forMicrosoft 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 valueof the Planning and Consolidation client to prompt for user name and password Otherwise the Planning andConsolidation Start Page does not display
41 Installing the Administration Client
Prerequisites
NoteFor a definitive list of system requirements see the Product Availability Matrix on SAP Service Marketplace atservicesapcompam Search on Planning and Consolidation
The following list describes the minimum software requirements
Microsoft Internet Explorer 70 80 90 or 10
Microsoft Office 2003 2007 2010 or 2012
NET Framework 20 or higher (install any required NET Framework Hotfixes by referring tosupportmicrosoftcomkb)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 37
NoteWe recommend that you install all of the latest Microsoft Windows hotfixes prior to installing the Administrationclient For information about which hotfixes to install see updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us
Procedure
The 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 ltPC_serverportgtsapbpcweb
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 mustdownload the most recent version of the full setup (EPM Add-inexe) from the Service Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPCInstallation folder
Individual users can install the EPM add-in on their own machines by going to the Planning and Consolidation Homepage 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 upthe 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
38
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
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 toperform the upgrade If Client Auto Update is not enabled and a newer version is detected clients must be installedmanually 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 andpassword in the Admin ID and Admin password fields respectively The Admin ID should be a member of thelocal administrators group on all the computers running the auto update This setting is not needed if all usershave 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 Thisoption is stored in the user preferences and may also be turned on or off using the User Optionshellip menu itemIf 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 toinstall 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 installit 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 servicesapcom
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 versionand policy information For a support package these files are
EPM Addin Support Package ltSP versiongtmsp EPM Addin Support Package ltSP versiongtxmlFor a patch these files are
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 (WebsrvrWebBPCInstallation)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 39
You can set a different update policy for each package listed
ExampleThe following table illustrates some possible situations assuming that you have installed the first full version(V1)
Table 10
Available maintenancepackages
V2-user update
V3-force update
V4-force update
V5-user update
V5-user update V5-user update
V6-auto update
V7-force update
Minimum RequiredVersion
V4 V4 V7
Notification A prompt tells the user toinstall maintenancepackage V4 using theForced Update behavior
If User Update is enabledthe prompt informs theuser that maintenancepackage V5 is available
A prompt tells the user toinstall maintenancepackage V7 using theForced Update behavior
New Version V4 V4 or V5 V7
If you change the update policy for any package click Update to complete the change
40
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
5 Connection Issues
You may experience connection problems with ports the proxy server or programs and settings that interact withthese components If you have any issues related to connection review the following recommendations andtroubleshooting tips
51 Checking for Open Ports
You must ensure that all required ports are open for inboundoutbound traffic By default Planning andConsolidation requires that Ports 80 (used by http) and 1433 and 2383 (used by SQL Server 2008) are open Totest whether the required ports are open go to a command prompt and enter the Telnet serveripaddress and portFor example Telnet 431181836 80 If the system returns a blank command window the port is open If it returnsa message stating that it is unable to connect the port is not open
NoteYou can use the following site to scan for the normal ports It allows you to manually enter a port number to test
wwwmyserverorgportsniffasp
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 Planningand Consolidation server as an exception You can do this at the client level ( Internet Explorer ToolsInternet 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 fullyqualified 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 Consolidationauthentication Do not use authentication on the proxy server The system synchronizes the user name andpassword on the remote server with the local user name and password
SAP Business Planning and Consolidation 100Connection Issues
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 41
NoteFor more information about setting up an ISA proxy server contact SAP Support to request a copy of Setting upISA Proxy Server White Paper For more information about Business Planning and Consolidation firewall portssee SAP Note 1505250
Internet Explorer Settings Issues
Internet Explorer settings must be set correctly to prevent errors and problems when you attempt to access thePlanning 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 insertthe IP address or fully qualified server name of the Planning and Consolidation server as an exception bychoosing 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
42
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Connection Issues
6 Installing Planning and Consolidation withTwo Active Directory Domains
To set up a Planning and Consolidation 10 application server in a hosted environment and use your own domainusers follow this procedure In general you install Planning and Consolidation on the host domain use the hostdomain account and assign it to the Planning and Consolidation users SysAdmin Admin and Users Then you acceptone 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 andpassword 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 topromote 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 privilegefor the Planning and Consolidation server
5 Install Planning and Consolidation and assign your domain account either to the three Planning andConsolidation administrative users SysAdmin Admin and Users or to only one of the three Planning andConsolidation administrative users and to three of your users Be sure you use your own user account ratherthan host domain users
Planning and Consolidation impersonation can then access your domain from the host environment becauseit has the privilege of your domain account
SAP Business Planning and Consolidation 100Installing Planning and Consolidation with Two Active Directory Domains
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 43
7 Installing Planning and Consolidation in aTerminal Services or Citrix ServerDeployment
This section describes best practices and instructions for installing Planning and Consolidation in a Terminal Servicesor Citrix Server deployment
71 Terminal Services Home Directories
We recommend using Terminal Server home directories rather than using the userrsquos profile directory The profiledirectory downloads a minimal amount of information about the dimensions of the environment you are logging onto and may be as large as 2 MB per user The profile directory is on the system drive and has limited space Byspecifying 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 individualserver 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 clientserver (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
44
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
Procedure
The following steps outline how to install the Planning and Consolidation clients in a Terminal Services (TS) or CitrixServer deployment
1 Make sure the Terminal Services or Citrix Server machine has the system requirements installed
2 Log on to the Terminal Services or Citrix Server machine with a user ID that has the rights to install on thatserver
3 At a command prompt enter Change userinstall
4 Open a browser and connect to the URL ltPC_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_MSBPCAdminMainexe
74 Creating a Shortcut to the Launch Page
Procedure
If you use published desktops instead of published applications the Planning and Consolidation desktop file (whichis installed on the current userrsquos desktop) must be moved to the All UsersDesktop folder
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 45
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 SQLServer 2012 support the remote modification of SSIS packages Planning and Consolidation also supports theremote 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 whichyou want to modify SSIS packages
These custom tasks reference dlls that connect to the database server and perform certain validation when usersset up the parameters of each task All the custom task reference components must also be installed in the machineon which you want to modify SSIS packages
We provide a program that registers all the reference components of the custom tasks This section explains theinstallation 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 ndash This folder contains all the dlls that should be installed on the machine There are Planning andConsolidation platform components and all of the Data Manager custom task files
Config folder ndash This folder contains only one file named Filelistxml and lists all of the files that should be installedIf you need to add or remove certain components from the installation you can modify this xml file
OSoftSetupexe ndash This is the main executable file to run the installation package
NoteIf you are not installing SSIS Custom Tasks on your client machine ndash specifically a machine other than the Planningand Consolidation application server ndash you must first install OSoftSSIS2008_Client or OSoftSSIS2012_Client onthe client machine followed by the SQL Server version If you want to use SQL 2008 Tasks under the SQL 2012environment you must install OSoftSSIS2008_Client on the application server For detailed information see SAPNote 1707410 You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package byextracting OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPCInstallation folder on the Planning and Consolidation server To modify SSIS packages on the Planning andConsolidation application server you need to install OSoftSSIS2008_Client or OSoftSSIS2012_Client for creatinga COM+ application For more information see Before You Modify the SSIS Packages [page 49] and Setup ofa COM+ Application on the Application Server [page 50]
Bin folder
This folder contains the following components
46
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Table 11
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012respectively
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
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 47
Name Remark
BPCWriteBackdll
InteropDTSdll
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 addmore components to the installation package you can copy the new components into the Bin folder and add theproper xml tags in FileListxml You need to enter information for the following tags
RegistType ndash This is the registration information of the component You can enter the following values
RegAsm ndash For NET component
48
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Regsvr32 ndash For VB6 component
Gacutil ndash For NET Framework component that should be registered into Global Assembly Cache
FileName ndash Component file name
OSoftSetupexe
This is the executable file to run the SSIS installation package Double-click the file to start the installation You needto enter information for the following fields
Set SQL server
Specify the SQL server name If your SQL Server has an instance specify the instance name
NoteIf you installed the OSoftSSIS2008_Client or OSoftSSIS2012_Client on the application server the SQL servername is automatically disabled
Set server credential
This is the credential name of the COM+ package component Enter the user ID and password that can accessyour SQL Server This should be either the System Admin ID or Admin ID that was registered as a COM+ userwhen 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 ifyou 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 packagesremotely This is also true for the application server that has SSIS installed The Planning and ConsolidationData Manager has the following custom tasks
Table 12
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008and 2012 respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and2012 respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012respectively
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 49
Name Remark
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and2012 respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008and 2012 respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL2008 and 2012 respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and2012 respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012respectively
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
ltdrivegtWebsrvrbin2 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 FilesMicrosoft SQLServer paste all files into the CProgram Files (x86)Microsoft SQL Server100DTSTasksfolder
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
50
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Typographic Conventions
Table 13
Example Description
lt gt Angle brackets indicate that you replace these words or characters with appropriate entries tomake entries in the system for example Enter your ltUser Namegt
File Save Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
Example Textual cross-references to an internet address for example wwwsapcom
example Quicklinks added to the internet address of a homepage to enable quick access to specificcontent 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 titlespushbutton 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 namesof installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transactioncodes database table names and key concepts of a programming language when they aresurrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
SAP Business Planning and Consolidation 100Typographic Conventions
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 51
52
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
wwwsapcom
Material Number
- SAP Business 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 2008 R2 2012 or 2012 R2
- 344 Removing Default Access to the Console
- 345 Management Console Access Control
- 346 Configuring Planning and Consolidation to use SSL
- 347 Using Client Certificates
- 348 Configuring MS SQL Server Reporting Services to use SSL
-
- 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
-
3 After Installing Planning and ConsolidationServers
31 Post-Installation Steps
Procedure
Perform these steps after installing the Planning and Consolidation servers for new installations of Planning andConsolidation
1 Connect your Planning and Consolidation system to Solution Manager Diagnostics (SMD) to allow support staffto identify analyze and resolve problems with your application See Connecting to Solution ManagerDiagnostics [page 28]
2 Configure the Planning and Consolidation NET and application server to ensure that it and its related servicesfunction properly and reliably For more information see Configuring the Planning and Consolidation NETApplication Server [page 29]
3 Optional configuration steps [page 29]
1 To ensure proper functioning of the Management Console create an SQL user and modify the System DSNand 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 loggingfor ODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default WebSite [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory canaccess the Management Console with whatever rights they have been granted on the server Forinformation about removing default access and creating a group that can access the console see RemovingDefault Access to the Console [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommendthat you only grant Management Console access to system administrators Planning and Consolidationusers should not have any access For more information see Management Console AccessControl [page 33]
6 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
4 Take the following steps to set up security
If you are defining security and application structure continue with step 5
If you want to designate someone other than the system administrator to manage security and applicationstructure log on to EnvironmentShell designate a user as a Primary Administrator
This user must have Administration ndash Environment and Security ‒ Define User task rights so that he or shecan 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 SeeInstalling the Administration Client [page 37]
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 27
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 taskprofiles 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 mustcomplete this step since there is no access to dimensions or members)
NoteTo allow users to request and query large amounts of data you can edit the metabasexml file located at CWindowssystem32inetsrv Set the following parameters to the stated values
ASPBUFFERINGLIMIT = 10485760
MAXREQUESTENTITYALLOWED = 10485760
32 Connecting to Solution Manager Diagnostics
NoteYou only need to perform the steps in this section if you have a SAP Solution Manager licence
The diagnostics functions in SAP Solution Manager allow identification analysis and resolution of problems Thisprocedure 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 areinstalled
NoteInstallation files for Diagnostics Agent are available on Service Marketplace by navigating to SupportPackages and Patches mdash Entry by Application Group SAP Technology Components SAP SOLUTIONMANAGER SAP SOLUTION MANAGER 70 EHP 1 Entry by Component Agents for managed systemsDIAGNOSTICS AGENT 711
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 whereMicrosoft 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
28
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
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 ServiceMarketplace at servicesapcom~sapidb011000358700000074392009E and follow the chapters that applyto Planning and Consolidation
33 Configuring the Planning and Consolidation NETApplication Servers
Procedure
Modifying machineconfig Files
To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock occurrences that wouldcause the application server to ldquosleeprdquo and not process anymore you can modify the machineconfig file whichresides in the WINDOWSMicrosoftNETFramework64v4030319Config directory
1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to specifywhether to automatically configure settings to achieve optimal performance based on the machineconfiguration You can set this attribute to True or False
For more information see msdnmicrosoftcomen-uslibrary7w2sway1aspx
2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the Planning andConsolidation application) or Machineconfig (for all applications including Planning and Consolidation) toensure the validationKey and decryptionKey keys have the same value on all application servers Thisway when the authentication cookie is checked the authentication ticket used on one server can still be validon another server
For more information and sample Visual Basic code for generating random key values seemsdnmicrosoftcomen-uslibraryms998288aspxpaght000007_webfarmdeploymentconsiderationsand msdnmicrosoftcomen-uslibraryms998310aspx
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 DSNand 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 forODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory can accessthe Management Console with whatever rights they have been granted on the server For information about
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 29
removing default access and creating a group that can access the console see Removing Default Access to theConsole [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommend thatyou only grant Management Console access to system administrators Planning and Consolidation users shouldnot have any access For more information see Management Console Access Control [page 33]
6 Configure the use of SSL in Planning and Consolidation See Configuring Planning and Consolidation to useSSL [page 34]
7 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
8 Configure Microsoft SQL Server Reporting Services to use SSL See Configuring MS SQL Server ReportingServices to use SSL [page 36]
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 databaserole 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 optionto use ODBC Logging Enter the following values
DSN is BPC_ManagementDSN Table is BPCLog The Microsoft SQL Server Username and Password
5 Restart IIS
NoteWithout these updates the Management Console does work but some functionality (specifically User Activityand Service Status) does not work as expected
Should you need to uninstall Planning and Consolidation we recommend that you reset the Active Log Formatfield in IIS to W3C Extended Log File Format
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
30
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
Prerequisites
ODBC logging has been configured according to the Microsoft Knowledge Base article 245243 How to configureODBC 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 inApplicationHostconfig as shown here
ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0logFormat=Custom gtUse 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-00AA006111E0appcmd 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 articlespecified in the Prerequisites section Configure these settings in the ltodbcLogginggt node underltsystemwebServergt
Exampleltlocation path=Default Web SitegtltsystemwebServergtltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog userName=Usernamepassword=mypassword gtltsystemwebServergtltlocationgt
Use the following AppCmds to configure these attributes for the default Web site
appcmd set config Default Web Site sectionodbcLogging dataSourceBPC_ManagementDSN commitappHostappcmd set config Default Web Site sectionodbcLogging tableNameBPCLog commitappHostappcmd set config Default Web Site sectionodbcLogging userNameUsername commitappHostappcmd set config Default Web Site sectionodbcLogging passwordmypassword commitappHost
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 31
NoteYou cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must use the SQL ServerODBC driver For more information see the Microsoft Knowledge Base article 931202 The requirements for usingthe ODBC logging feature in IIS
343 Setting Up an ODBC Data Source in Windows Server2008 2008 R2 2012 or 2012 R2
Procedure
This procedure describes how to set up an ODBC data source for the Management Console in Windows Server 20082008 R2 2012 or 2012 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
NoteIf you have chosen SAP BusinessObjects User Management System in the installation screen you do not needto remove or configure access because the Management Console service always runs with the System Admin IDaccount which is a member of the Administrators group
Procedure
To remove default access to the Management Console and create a group that does have access to the console usethe procedure described below
32
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
NoteCreate your Management Console administrative group either on the server that hosts the Management Consoleor 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
NoteAlternatively you can perform analogous steps in Active Directory
3 In the Groups context menu choose New Group
4 Enter data as required Click Create
5 In the Computer Management dialog box choose Services and Applications Internet InformationServices 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 objectand all child objects Include these with entries explicitly defined here checkbox
NoteThis step is a necessary precursor to the completion of this procedure
10 In the Security dialog box click Copy to ensure that the System group retains its privileges
11 Remove access to the Management Console from all groups that should not have it
12 Choose Authentication in the center pane then disable Windows authentication
Result
Users who have not been granted access to the Management Console can still open the Management Console Webpage but it contains no data or menu options This does not affect the access that a user would otherwise have toPlanning and Consolidation
345 Management Console Access Control
After establishing the Management Console group you can add users or groups to it For more information aboutcreating this group see Removing Default Access to the Console [page 32] Their rights in Active Directory determinewhat they can access in the Console
By default any member of the Administrators Active Directory group on the application server or domain has fullaccess to all of the features of the Console except the Planning and Consolidation logging area Access to Planningand Consolidation logging is controlled within the Planning and Consolidation Administration Client task securityThe user must be granted View system logs task privileges For more information see the SAP Library Planning and
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 33
Consolidation Administrators Guide in servicesapcominstguidesepm-bpc 100 version for the Microsoftplatform
Your IT policy determines whether you grant access by group or user You may wish to create several levels of Consoleusers (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 describedin this table
Table 9
Privilege Rights Management Area
Task Manager and Kill Process Administrators group on application server or domain
Performance Monitor Counters Administrators group on application server or domain
Power Users group on application server or domain
Performance Monitor Users group on application server
Microsoft Analysis Services performance monitoring Administrators group on application server or domain
Microsoft SQL Server Monitoring (performance counters andstatistics)
Administrators group on application server or domain
346 Configuring Planning and Consolidation to use SSL
Procedure
Creating a Certificate for the Server
During the handshake phase of the SSL communication the server must send its certificate to the client The clientthen uses the certificate to encrypt information and send it back to the server
The procedure below describes how to create a self-signed certificate for the server
RecommendationWe recommend that you limit the use of self-signed certificates to testing only For a productive system you shouldobtain a certificate signed by a well-known certification authority (CA)
1 Start the Internet Information Services (IIS) Manager To do that go to Start All Programs AdministrativeTools Internet Information Services (IIS) Manager
2 In the Connections panel on the left-hand side select the server node and then choose Server Certificates
3 In the Actions panel on the right hand side choose the Create Self-Signed Certificate action
4 Enter the name that you want the certificate to be identified by for example MyTestSSLCertificate
IIS generates a new SSL certificate for you that has one yearrsquos expiry lease The certificate is issued to the local servername
Binding the Certificate to the Web Site
The procedure below describes how to bind the certificate to the web site for which SSL connections must be used
1 In the Connections panel select the web site node
2 In the Actions panel choose Bindings
34
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
3 In the Site Bindings dialog that appears choose the Add button to create a new binding
4 Configure the parameters as follows
Type = https IP Address = [1] - this is a shorthand expression for the local server name
Port = 443 - this is the default SSL port
SSL Certificate = enter your newly created certificate name
5 Choose OK to create the new binding and then close the Site Bindings dialog
6 Restart the IIS processes To do this choose Restart from the Actions panel
7 In the middle panel under the IIS section choose SSL Settings
8 In the SSL Settings screen select the Require SSL checkbox
9 In the Actions panel choose to Apply these settings
To test the SSL connection in the Actions panel choose the Browse [1] 443 (https) link
347 Using Client Certificates
To enable the use of client certificates in Planning and Consolidation you must follow several manual steps
NotePlanning and Consolidation supports client certificate authentication in Windows Authentication Mode butdoes 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 technetmicrosoftcomen-uslibrarycc753810aspx
For more information about configuring the client certificate mapping authentication see technetmicrosoftcomen-uslibrarycc732996(WS10)aspx
When you create the client certificates you can set the type of certificate in the SSL Settings screen in InternetInformation Services (IIS) Manager
Procedure
1 Set the options for client certificates
1 In the IIS Manager select the web site where you installed Planning and Consolidation
2 Choose SSL Settings
3 In the Client certificates section select the Accept client certificates option
This option allows you to use a client certificate or username and password (Basic authentication) toconnect 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 theManagementConsole home page
3 Double-click Authentication and enable Anonymous Authentication
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 35
4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way asin step 3
5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the sameway 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
348 Configuring MS SQL Server Reporting Services to useSSL
Procedure
The procedure below describes how to configure the use of SSL in Microsoft SQL Server Reporting Services
NoteReporting Services does not provide functionalities for generating requesting or installing a certificate Theserver certificates that you want to use for configuring SSL must have already been installed on your computer
1 Open the Reporting Services Configuration Manager program To do this open the Windows Start menu andnavigate to All Programs Microsoft SQL Server ltversiongt Configuration Tools Reporting ServicesConfiguration Manager
2 In the Connect panel on the left-hand side select the Web Service URL option to open all the Report Server webservice parameters
3 Configure the parameters as follows
SSL Certificate = the name of the certificate that you want to use
SSL Port = 4434 Choose Apply to confirm the changes
5 In the Connect panel choose Report Manager URL to open the list of parameters that link Reporting Servicesto IIS
6 Choose Advanced to add your new SSL web URL
7 In the section Multiple SSL Identities for Report Manager choose Add Configure the parameters as follows
IP Address = (All IPv4) SSL Port = 443 Certificate = the name of your SSL certificate
8 To test the configuration click the URL that appears under the Report manager Site Identification section
36
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
4 Installing Planning and ConsolidationAdministration Client and the SAPBusinessObjects EPM solutions Add-in forMicrosoft Office
The installation of the Planning and Consolidation Administration Client allows administrators to build and maintainPlanning and Consolidation environments and models and administer security
All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions add-in forMicrosoft 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 valueof the Planning and Consolidation client to prompt for user name and password Otherwise the Planning andConsolidation Start Page does not display
41 Installing the Administration Client
Prerequisites
NoteFor a definitive list of system requirements see the Product Availability Matrix on SAP Service Marketplace atservicesapcompam Search on Planning and Consolidation
The following list describes the minimum software requirements
Microsoft Internet Explorer 70 80 90 or 10
Microsoft Office 2003 2007 2010 or 2012
NET Framework 20 or higher (install any required NET Framework Hotfixes by referring tosupportmicrosoftcomkb)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 37
NoteWe recommend that you install all of the latest Microsoft Windows hotfixes prior to installing the Administrationclient For information about which hotfixes to install see updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us
Procedure
The 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 ltPC_serverportgtsapbpcweb
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 mustdownload the most recent version of the full setup (EPM Add-inexe) from the Service Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPCInstallation folder
Individual users can install the EPM add-in on their own machines by going to the Planning and Consolidation Homepage 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 upthe 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
38
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
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 toperform the upgrade If Client Auto Update is not enabled and a newer version is detected clients must be installedmanually 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 andpassword in the Admin ID and Admin password fields respectively The Admin ID should be a member of thelocal administrators group on all the computers running the auto update This setting is not needed if all usershave 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 Thisoption is stored in the user preferences and may also be turned on or off using the User Optionshellip menu itemIf 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 toinstall 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 installit 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 servicesapcom
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 versionand policy information For a support package these files are
EPM Addin Support Package ltSP versiongtmsp EPM Addin Support Package ltSP versiongtxmlFor a patch these files are
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 (WebsrvrWebBPCInstallation)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 39
You can set a different update policy for each package listed
ExampleThe following table illustrates some possible situations assuming that you have installed the first full version(V1)
Table 10
Available maintenancepackages
V2-user update
V3-force update
V4-force update
V5-user update
V5-user update V5-user update
V6-auto update
V7-force update
Minimum RequiredVersion
V4 V4 V7
Notification A prompt tells the user toinstall maintenancepackage V4 using theForced Update behavior
If User Update is enabledthe prompt informs theuser that maintenancepackage V5 is available
A prompt tells the user toinstall maintenancepackage V7 using theForced Update behavior
New Version V4 V4 or V5 V7
If you change the update policy for any package click Update to complete the change
40
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
5 Connection Issues
You may experience connection problems with ports the proxy server or programs and settings that interact withthese components If you have any issues related to connection review the following recommendations andtroubleshooting tips
51 Checking for Open Ports
You must ensure that all required ports are open for inboundoutbound traffic By default Planning andConsolidation requires that Ports 80 (used by http) and 1433 and 2383 (used by SQL Server 2008) are open Totest whether the required ports are open go to a command prompt and enter the Telnet serveripaddress and portFor example Telnet 431181836 80 If the system returns a blank command window the port is open If it returnsa message stating that it is unable to connect the port is not open
NoteYou can use the following site to scan for the normal ports It allows you to manually enter a port number to test
wwwmyserverorgportsniffasp
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 Planningand Consolidation server as an exception You can do this at the client level ( Internet Explorer ToolsInternet 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 fullyqualified 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 Consolidationauthentication Do not use authentication on the proxy server The system synchronizes the user name andpassword on the remote server with the local user name and password
SAP Business Planning and Consolidation 100Connection Issues
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 41
NoteFor more information about setting up an ISA proxy server contact SAP Support to request a copy of Setting upISA Proxy Server White Paper For more information about Business Planning and Consolidation firewall portssee SAP Note 1505250
Internet Explorer Settings Issues
Internet Explorer settings must be set correctly to prevent errors and problems when you attempt to access thePlanning 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 insertthe IP address or fully qualified server name of the Planning and Consolidation server as an exception bychoosing 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
42
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Connection Issues
6 Installing Planning and Consolidation withTwo Active Directory Domains
To set up a Planning and Consolidation 10 application server in a hosted environment and use your own domainusers follow this procedure In general you install Planning and Consolidation on the host domain use the hostdomain account and assign it to the Planning and Consolidation users SysAdmin Admin and Users Then you acceptone 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 andpassword 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 topromote 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 privilegefor the Planning and Consolidation server
5 Install Planning and Consolidation and assign your domain account either to the three Planning andConsolidation administrative users SysAdmin Admin and Users or to only one of the three Planning andConsolidation administrative users and to three of your users Be sure you use your own user account ratherthan host domain users
Planning and Consolidation impersonation can then access your domain from the host environment becauseit has the privilege of your domain account
SAP Business Planning and Consolidation 100Installing Planning and Consolidation with Two Active Directory Domains
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 43
7 Installing Planning and Consolidation in aTerminal Services or Citrix ServerDeployment
This section describes best practices and instructions for installing Planning and Consolidation in a Terminal Servicesor Citrix Server deployment
71 Terminal Services Home Directories
We recommend using Terminal Server home directories rather than using the userrsquos profile directory The profiledirectory downloads a minimal amount of information about the dimensions of the environment you are logging onto and may be as large as 2 MB per user The profile directory is on the system drive and has limited space Byspecifying 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 individualserver 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 clientserver (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
44
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
Procedure
The following steps outline how to install the Planning and Consolidation clients in a Terminal Services (TS) or CitrixServer deployment
1 Make sure the Terminal Services or Citrix Server machine has the system requirements installed
2 Log on to the Terminal Services or Citrix Server machine with a user ID that has the rights to install on thatserver
3 At a command prompt enter Change userinstall
4 Open a browser and connect to the URL ltPC_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_MSBPCAdminMainexe
74 Creating a Shortcut to the Launch Page
Procedure
If you use published desktops instead of published applications the Planning and Consolidation desktop file (whichis installed on the current userrsquos desktop) must be moved to the All UsersDesktop folder
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 45
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 SQLServer 2012 support the remote modification of SSIS packages Planning and Consolidation also supports theremote 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 whichyou want to modify SSIS packages
These custom tasks reference dlls that connect to the database server and perform certain validation when usersset up the parameters of each task All the custom task reference components must also be installed in the machineon which you want to modify SSIS packages
We provide a program that registers all the reference components of the custom tasks This section explains theinstallation 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 ndash This folder contains all the dlls that should be installed on the machine There are Planning andConsolidation platform components and all of the Data Manager custom task files
Config folder ndash This folder contains only one file named Filelistxml and lists all of the files that should be installedIf you need to add or remove certain components from the installation you can modify this xml file
OSoftSetupexe ndash This is the main executable file to run the installation package
NoteIf you are not installing SSIS Custom Tasks on your client machine ndash specifically a machine other than the Planningand Consolidation application server ndash you must first install OSoftSSIS2008_Client or OSoftSSIS2012_Client onthe client machine followed by the SQL Server version If you want to use SQL 2008 Tasks under the SQL 2012environment you must install OSoftSSIS2008_Client on the application server For detailed information see SAPNote 1707410 You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package byextracting OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPCInstallation folder on the Planning and Consolidation server To modify SSIS packages on the Planning andConsolidation application server you need to install OSoftSSIS2008_Client or OSoftSSIS2012_Client for creatinga COM+ application For more information see Before You Modify the SSIS Packages [page 49] and Setup ofa COM+ Application on the Application Server [page 50]
Bin folder
This folder contains the following components
46
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Table 11
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012respectively
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
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 47
Name Remark
BPCWriteBackdll
InteropDTSdll
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 addmore components to the installation package you can copy the new components into the Bin folder and add theproper xml tags in FileListxml You need to enter information for the following tags
RegistType ndash This is the registration information of the component You can enter the following values
RegAsm ndash For NET component
48
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Regsvr32 ndash For VB6 component
Gacutil ndash For NET Framework component that should be registered into Global Assembly Cache
FileName ndash Component file name
OSoftSetupexe
This is the executable file to run the SSIS installation package Double-click the file to start the installation You needto enter information for the following fields
Set SQL server
Specify the SQL server name If your SQL Server has an instance specify the instance name
NoteIf you installed the OSoftSSIS2008_Client or OSoftSSIS2012_Client on the application server the SQL servername is automatically disabled
Set server credential
This is the credential name of the COM+ package component Enter the user ID and password that can accessyour SQL Server This should be either the System Admin ID or Admin ID that was registered as a COM+ userwhen 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 ifyou 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 packagesremotely This is also true for the application server that has SSIS installed The Planning and ConsolidationData Manager has the following custom tasks
Table 12
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008and 2012 respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and2012 respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012respectively
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 49
Name Remark
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and2012 respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008and 2012 respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL2008 and 2012 respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and2012 respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012respectively
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
ltdrivegtWebsrvrbin2 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 FilesMicrosoft SQLServer paste all files into the CProgram Files (x86)Microsoft SQL Server100DTSTasksfolder
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
50
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Typographic Conventions
Table 13
Example Description
lt gt Angle brackets indicate that you replace these words or characters with appropriate entries tomake entries in the system for example Enter your ltUser Namegt
File Save Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
Example Textual cross-references to an internet address for example wwwsapcom
example Quicklinks added to the internet address of a homepage to enable quick access to specificcontent 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 titlespushbutton 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 namesof installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transactioncodes database table names and key concepts of a programming language when they aresurrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
SAP Business Planning and Consolidation 100Typographic Conventions
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 51
52
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
wwwsapcom
Material Number
- SAP Business 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 2008 R2 2012 or 2012 R2
- 344 Removing Default Access to the Console
- 345 Management Console Access Control
- 346 Configuring Planning and Consolidation to use SSL
- 347 Using Client Certificates
- 348 Configuring MS SQL Server Reporting Services to use SSL
-
- 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
-
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 taskprofiles 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 mustcomplete this step since there is no access to dimensions or members)
NoteTo allow users to request and query large amounts of data you can edit the metabasexml file located at CWindowssystem32inetsrv Set the following parameters to the stated values
ASPBUFFERINGLIMIT = 10485760
MAXREQUESTENTITYALLOWED = 10485760
32 Connecting to Solution Manager Diagnostics
NoteYou only need to perform the steps in this section if you have a SAP Solution Manager licence
The diagnostics functions in SAP Solution Manager allow identification analysis and resolution of problems Thisprocedure 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 areinstalled
NoteInstallation files for Diagnostics Agent are available on Service Marketplace by navigating to SupportPackages and Patches mdash Entry by Application Group SAP Technology Components SAP SOLUTIONMANAGER SAP SOLUTION MANAGER 70 EHP 1 Entry by Component Agents for managed systemsDIAGNOSTICS AGENT 711
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 whereMicrosoft 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
28
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
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 ServiceMarketplace at servicesapcom~sapidb011000358700000074392009E and follow the chapters that applyto Planning and Consolidation
33 Configuring the Planning and Consolidation NETApplication Servers
Procedure
Modifying machineconfig Files
To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock occurrences that wouldcause the application server to ldquosleeprdquo and not process anymore you can modify the machineconfig file whichresides in the WINDOWSMicrosoftNETFramework64v4030319Config directory
1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to specifywhether to automatically configure settings to achieve optimal performance based on the machineconfiguration You can set this attribute to True or False
For more information see msdnmicrosoftcomen-uslibrary7w2sway1aspx
2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the Planning andConsolidation application) or Machineconfig (for all applications including Planning and Consolidation) toensure the validationKey and decryptionKey keys have the same value on all application servers Thisway when the authentication cookie is checked the authentication ticket used on one server can still be validon another server
For more information and sample Visual Basic code for generating random key values seemsdnmicrosoftcomen-uslibraryms998288aspxpaght000007_webfarmdeploymentconsiderationsand msdnmicrosoftcomen-uslibraryms998310aspx
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 DSNand 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 forODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory can accessthe Management Console with whatever rights they have been granted on the server For information about
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 29
removing default access and creating a group that can access the console see Removing Default Access to theConsole [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommend thatyou only grant Management Console access to system administrators Planning and Consolidation users shouldnot have any access For more information see Management Console Access Control [page 33]
6 Configure the use of SSL in Planning and Consolidation See Configuring Planning and Consolidation to useSSL [page 34]
7 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
8 Configure Microsoft SQL Server Reporting Services to use SSL See Configuring MS SQL Server ReportingServices to use SSL [page 36]
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 databaserole 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 optionto use ODBC Logging Enter the following values
DSN is BPC_ManagementDSN Table is BPCLog The Microsoft SQL Server Username and Password
5 Restart IIS
NoteWithout these updates the Management Console does work but some functionality (specifically User Activityand Service Status) does not work as expected
Should you need to uninstall Planning and Consolidation we recommend that you reset the Active Log Formatfield in IIS to W3C Extended Log File Format
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
30
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
Prerequisites
ODBC logging has been configured according to the Microsoft Knowledge Base article 245243 How to configureODBC 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 inApplicationHostconfig as shown here
ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0logFormat=Custom gtUse 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-00AA006111E0appcmd 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 articlespecified in the Prerequisites section Configure these settings in the ltodbcLogginggt node underltsystemwebServergt
Exampleltlocation path=Default Web SitegtltsystemwebServergtltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog userName=Usernamepassword=mypassword gtltsystemwebServergtltlocationgt
Use the following AppCmds to configure these attributes for the default Web site
appcmd set config Default Web Site sectionodbcLogging dataSourceBPC_ManagementDSN commitappHostappcmd set config Default Web Site sectionodbcLogging tableNameBPCLog commitappHostappcmd set config Default Web Site sectionodbcLogging userNameUsername commitappHostappcmd set config Default Web Site sectionodbcLogging passwordmypassword commitappHost
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 31
NoteYou cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must use the SQL ServerODBC driver For more information see the Microsoft Knowledge Base article 931202 The requirements for usingthe ODBC logging feature in IIS
343 Setting Up an ODBC Data Source in Windows Server2008 2008 R2 2012 or 2012 R2
Procedure
This procedure describes how to set up an ODBC data source for the Management Console in Windows Server 20082008 R2 2012 or 2012 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
NoteIf you have chosen SAP BusinessObjects User Management System in the installation screen you do not needto remove or configure access because the Management Console service always runs with the System Admin IDaccount which is a member of the Administrators group
Procedure
To remove default access to the Management Console and create a group that does have access to the console usethe procedure described below
32
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
NoteCreate your Management Console administrative group either on the server that hosts the Management Consoleor 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
NoteAlternatively you can perform analogous steps in Active Directory
3 In the Groups context menu choose New Group
4 Enter data as required Click Create
5 In the Computer Management dialog box choose Services and Applications Internet InformationServices 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 objectand all child objects Include these with entries explicitly defined here checkbox
NoteThis step is a necessary precursor to the completion of this procedure
10 In the Security dialog box click Copy to ensure that the System group retains its privileges
11 Remove access to the Management Console from all groups that should not have it
12 Choose Authentication in the center pane then disable Windows authentication
Result
Users who have not been granted access to the Management Console can still open the Management Console Webpage but it contains no data or menu options This does not affect the access that a user would otherwise have toPlanning and Consolidation
345 Management Console Access Control
After establishing the Management Console group you can add users or groups to it For more information aboutcreating this group see Removing Default Access to the Console [page 32] Their rights in Active Directory determinewhat they can access in the Console
By default any member of the Administrators Active Directory group on the application server or domain has fullaccess to all of the features of the Console except the Planning and Consolidation logging area Access to Planningand Consolidation logging is controlled within the Planning and Consolidation Administration Client task securityThe user must be granted View system logs task privileges For more information see the SAP Library Planning and
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 33
Consolidation Administrators Guide in servicesapcominstguidesepm-bpc 100 version for the Microsoftplatform
Your IT policy determines whether you grant access by group or user You may wish to create several levels of Consoleusers (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 describedin this table
Table 9
Privilege Rights Management Area
Task Manager and Kill Process Administrators group on application server or domain
Performance Monitor Counters Administrators group on application server or domain
Power Users group on application server or domain
Performance Monitor Users group on application server
Microsoft Analysis Services performance monitoring Administrators group on application server or domain
Microsoft SQL Server Monitoring (performance counters andstatistics)
Administrators group on application server or domain
346 Configuring Planning and Consolidation to use SSL
Procedure
Creating a Certificate for the Server
During the handshake phase of the SSL communication the server must send its certificate to the client The clientthen uses the certificate to encrypt information and send it back to the server
The procedure below describes how to create a self-signed certificate for the server
RecommendationWe recommend that you limit the use of self-signed certificates to testing only For a productive system you shouldobtain a certificate signed by a well-known certification authority (CA)
1 Start the Internet Information Services (IIS) Manager To do that go to Start All Programs AdministrativeTools Internet Information Services (IIS) Manager
2 In the Connections panel on the left-hand side select the server node and then choose Server Certificates
3 In the Actions panel on the right hand side choose the Create Self-Signed Certificate action
4 Enter the name that you want the certificate to be identified by for example MyTestSSLCertificate
IIS generates a new SSL certificate for you that has one yearrsquos expiry lease The certificate is issued to the local servername
Binding the Certificate to the Web Site
The procedure below describes how to bind the certificate to the web site for which SSL connections must be used
1 In the Connections panel select the web site node
2 In the Actions panel choose Bindings
34
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
3 In the Site Bindings dialog that appears choose the Add button to create a new binding
4 Configure the parameters as follows
Type = https IP Address = [1] - this is a shorthand expression for the local server name
Port = 443 - this is the default SSL port
SSL Certificate = enter your newly created certificate name
5 Choose OK to create the new binding and then close the Site Bindings dialog
6 Restart the IIS processes To do this choose Restart from the Actions panel
7 In the middle panel under the IIS section choose SSL Settings
8 In the SSL Settings screen select the Require SSL checkbox
9 In the Actions panel choose to Apply these settings
To test the SSL connection in the Actions panel choose the Browse [1] 443 (https) link
347 Using Client Certificates
To enable the use of client certificates in Planning and Consolidation you must follow several manual steps
NotePlanning and Consolidation supports client certificate authentication in Windows Authentication Mode butdoes 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 technetmicrosoftcomen-uslibrarycc753810aspx
For more information about configuring the client certificate mapping authentication see technetmicrosoftcomen-uslibrarycc732996(WS10)aspx
When you create the client certificates you can set the type of certificate in the SSL Settings screen in InternetInformation Services (IIS) Manager
Procedure
1 Set the options for client certificates
1 In the IIS Manager select the web site where you installed Planning and Consolidation
2 Choose SSL Settings
3 In the Client certificates section select the Accept client certificates option
This option allows you to use a client certificate or username and password (Basic authentication) toconnect 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 theManagementConsole home page
3 Double-click Authentication and enable Anonymous Authentication
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 35
4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way asin step 3
5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the sameway 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
348 Configuring MS SQL Server Reporting Services to useSSL
Procedure
The procedure below describes how to configure the use of SSL in Microsoft SQL Server Reporting Services
NoteReporting Services does not provide functionalities for generating requesting or installing a certificate Theserver certificates that you want to use for configuring SSL must have already been installed on your computer
1 Open the Reporting Services Configuration Manager program To do this open the Windows Start menu andnavigate to All Programs Microsoft SQL Server ltversiongt Configuration Tools Reporting ServicesConfiguration Manager
2 In the Connect panel on the left-hand side select the Web Service URL option to open all the Report Server webservice parameters
3 Configure the parameters as follows
SSL Certificate = the name of the certificate that you want to use
SSL Port = 4434 Choose Apply to confirm the changes
5 In the Connect panel choose Report Manager URL to open the list of parameters that link Reporting Servicesto IIS
6 Choose Advanced to add your new SSL web URL
7 In the section Multiple SSL Identities for Report Manager choose Add Configure the parameters as follows
IP Address = (All IPv4) SSL Port = 443 Certificate = the name of your SSL certificate
8 To test the configuration click the URL that appears under the Report manager Site Identification section
36
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
4 Installing Planning and ConsolidationAdministration Client and the SAPBusinessObjects EPM solutions Add-in forMicrosoft Office
The installation of the Planning and Consolidation Administration Client allows administrators to build and maintainPlanning and Consolidation environments and models and administer security
All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions add-in forMicrosoft 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 valueof the Planning and Consolidation client to prompt for user name and password Otherwise the Planning andConsolidation Start Page does not display
41 Installing the Administration Client
Prerequisites
NoteFor a definitive list of system requirements see the Product Availability Matrix on SAP Service Marketplace atservicesapcompam Search on Planning and Consolidation
The following list describes the minimum software requirements
Microsoft Internet Explorer 70 80 90 or 10
Microsoft Office 2003 2007 2010 or 2012
NET Framework 20 or higher (install any required NET Framework Hotfixes by referring tosupportmicrosoftcomkb)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 37
NoteWe recommend that you install all of the latest Microsoft Windows hotfixes prior to installing the Administrationclient For information about which hotfixes to install see updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us
Procedure
The 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 ltPC_serverportgtsapbpcweb
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 mustdownload the most recent version of the full setup (EPM Add-inexe) from the Service Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPCInstallation folder
Individual users can install the EPM add-in on their own machines by going to the Planning and Consolidation Homepage 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 upthe 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
38
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
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 toperform the upgrade If Client Auto Update is not enabled and a newer version is detected clients must be installedmanually 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 andpassword in the Admin ID and Admin password fields respectively The Admin ID should be a member of thelocal administrators group on all the computers running the auto update This setting is not needed if all usershave 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 Thisoption is stored in the user preferences and may also be turned on or off using the User Optionshellip menu itemIf 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 toinstall 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 installit 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 servicesapcom
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 versionand policy information For a support package these files are
EPM Addin Support Package ltSP versiongtmsp EPM Addin Support Package ltSP versiongtxmlFor a patch these files are
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 (WebsrvrWebBPCInstallation)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 39
You can set a different update policy for each package listed
ExampleThe following table illustrates some possible situations assuming that you have installed the first full version(V1)
Table 10
Available maintenancepackages
V2-user update
V3-force update
V4-force update
V5-user update
V5-user update V5-user update
V6-auto update
V7-force update
Minimum RequiredVersion
V4 V4 V7
Notification A prompt tells the user toinstall maintenancepackage V4 using theForced Update behavior
If User Update is enabledthe prompt informs theuser that maintenancepackage V5 is available
A prompt tells the user toinstall maintenancepackage V7 using theForced Update behavior
New Version V4 V4 or V5 V7
If you change the update policy for any package click Update to complete the change
40
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
5 Connection Issues
You may experience connection problems with ports the proxy server or programs and settings that interact withthese components If you have any issues related to connection review the following recommendations andtroubleshooting tips
51 Checking for Open Ports
You must ensure that all required ports are open for inboundoutbound traffic By default Planning andConsolidation requires that Ports 80 (used by http) and 1433 and 2383 (used by SQL Server 2008) are open Totest whether the required ports are open go to a command prompt and enter the Telnet serveripaddress and portFor example Telnet 431181836 80 If the system returns a blank command window the port is open If it returnsa message stating that it is unable to connect the port is not open
NoteYou can use the following site to scan for the normal ports It allows you to manually enter a port number to test
wwwmyserverorgportsniffasp
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 Planningand Consolidation server as an exception You can do this at the client level ( Internet Explorer ToolsInternet 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 fullyqualified 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 Consolidationauthentication Do not use authentication on the proxy server The system synchronizes the user name andpassword on the remote server with the local user name and password
SAP Business Planning and Consolidation 100Connection Issues
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 41
NoteFor more information about setting up an ISA proxy server contact SAP Support to request a copy of Setting upISA Proxy Server White Paper For more information about Business Planning and Consolidation firewall portssee SAP Note 1505250
Internet Explorer Settings Issues
Internet Explorer settings must be set correctly to prevent errors and problems when you attempt to access thePlanning 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 insertthe IP address or fully qualified server name of the Planning and Consolidation server as an exception bychoosing 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
42
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Connection Issues
6 Installing Planning and Consolidation withTwo Active Directory Domains
To set up a Planning and Consolidation 10 application server in a hosted environment and use your own domainusers follow this procedure In general you install Planning and Consolidation on the host domain use the hostdomain account and assign it to the Planning and Consolidation users SysAdmin Admin and Users Then you acceptone 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 andpassword 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 topromote 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 privilegefor the Planning and Consolidation server
5 Install Planning and Consolidation and assign your domain account either to the three Planning andConsolidation administrative users SysAdmin Admin and Users or to only one of the three Planning andConsolidation administrative users and to three of your users Be sure you use your own user account ratherthan host domain users
Planning and Consolidation impersonation can then access your domain from the host environment becauseit has the privilege of your domain account
SAP Business Planning and Consolidation 100Installing Planning and Consolidation with Two Active Directory Domains
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 43
7 Installing Planning and Consolidation in aTerminal Services or Citrix ServerDeployment
This section describes best practices and instructions for installing Planning and Consolidation in a Terminal Servicesor Citrix Server deployment
71 Terminal Services Home Directories
We recommend using Terminal Server home directories rather than using the userrsquos profile directory The profiledirectory downloads a minimal amount of information about the dimensions of the environment you are logging onto and may be as large as 2 MB per user The profile directory is on the system drive and has limited space Byspecifying 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 individualserver 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 clientserver (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
44
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
Procedure
The following steps outline how to install the Planning and Consolidation clients in a Terminal Services (TS) or CitrixServer deployment
1 Make sure the Terminal Services or Citrix Server machine has the system requirements installed
2 Log on to the Terminal Services or Citrix Server machine with a user ID that has the rights to install on thatserver
3 At a command prompt enter Change userinstall
4 Open a browser and connect to the URL ltPC_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_MSBPCAdminMainexe
74 Creating a Shortcut to the Launch Page
Procedure
If you use published desktops instead of published applications the Planning and Consolidation desktop file (whichis installed on the current userrsquos desktop) must be moved to the All UsersDesktop folder
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 45
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 SQLServer 2012 support the remote modification of SSIS packages Planning and Consolidation also supports theremote 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 whichyou want to modify SSIS packages
These custom tasks reference dlls that connect to the database server and perform certain validation when usersset up the parameters of each task All the custom task reference components must also be installed in the machineon which you want to modify SSIS packages
We provide a program that registers all the reference components of the custom tasks This section explains theinstallation 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 ndash This folder contains all the dlls that should be installed on the machine There are Planning andConsolidation platform components and all of the Data Manager custom task files
Config folder ndash This folder contains only one file named Filelistxml and lists all of the files that should be installedIf you need to add or remove certain components from the installation you can modify this xml file
OSoftSetupexe ndash This is the main executable file to run the installation package
NoteIf you are not installing SSIS Custom Tasks on your client machine ndash specifically a machine other than the Planningand Consolidation application server ndash you must first install OSoftSSIS2008_Client or OSoftSSIS2012_Client onthe client machine followed by the SQL Server version If you want to use SQL 2008 Tasks under the SQL 2012environment you must install OSoftSSIS2008_Client on the application server For detailed information see SAPNote 1707410 You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package byextracting OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPCInstallation folder on the Planning and Consolidation server To modify SSIS packages on the Planning andConsolidation application server you need to install OSoftSSIS2008_Client or OSoftSSIS2012_Client for creatinga COM+ application For more information see Before You Modify the SSIS Packages [page 49] and Setup ofa COM+ Application on the Application Server [page 50]
Bin folder
This folder contains the following components
46
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Table 11
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012respectively
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
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 47
Name Remark
BPCWriteBackdll
InteropDTSdll
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 addmore components to the installation package you can copy the new components into the Bin folder and add theproper xml tags in FileListxml You need to enter information for the following tags
RegistType ndash This is the registration information of the component You can enter the following values
RegAsm ndash For NET component
48
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Regsvr32 ndash For VB6 component
Gacutil ndash For NET Framework component that should be registered into Global Assembly Cache
FileName ndash Component file name
OSoftSetupexe
This is the executable file to run the SSIS installation package Double-click the file to start the installation You needto enter information for the following fields
Set SQL server
Specify the SQL server name If your SQL Server has an instance specify the instance name
NoteIf you installed the OSoftSSIS2008_Client or OSoftSSIS2012_Client on the application server the SQL servername is automatically disabled
Set server credential
This is the credential name of the COM+ package component Enter the user ID and password that can accessyour SQL Server This should be either the System Admin ID or Admin ID that was registered as a COM+ userwhen 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 ifyou 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 packagesremotely This is also true for the application server that has SSIS installed The Planning and ConsolidationData Manager has the following custom tasks
Table 12
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008and 2012 respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and2012 respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012respectively
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 49
Name Remark
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and2012 respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008and 2012 respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL2008 and 2012 respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and2012 respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012respectively
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
ltdrivegtWebsrvrbin2 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 FilesMicrosoft SQLServer paste all files into the CProgram Files (x86)Microsoft SQL Server100DTSTasksfolder
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
50
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Typographic Conventions
Table 13
Example Description
lt gt Angle brackets indicate that you replace these words or characters with appropriate entries tomake entries in the system for example Enter your ltUser Namegt
File Save Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
Example Textual cross-references to an internet address for example wwwsapcom
example Quicklinks added to the internet address of a homepage to enable quick access to specificcontent 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 titlespushbutton 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 namesof installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transactioncodes database table names and key concepts of a programming language when they aresurrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
SAP Business Planning and Consolidation 100Typographic Conventions
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 51
52
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
wwwsapcom
Material Number
- SAP Business 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 2008 R2 2012 or 2012 R2
- 344 Removing Default Access to the Console
- 345 Management Console Access Control
- 346 Configuring Planning and Consolidation to use SSL
- 347 Using Client Certificates
- 348 Configuring MS SQL Server Reporting Services to use SSL
-
- 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
-
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 ServiceMarketplace at servicesapcom~sapidb011000358700000074392009E and follow the chapters that applyto Planning and Consolidation
33 Configuring the Planning and Consolidation NETApplication Servers
Procedure
Modifying machineconfig Files
To ensure the right balance between the number of threads ldquoworkingrdquo requests and deadlock occurrences that wouldcause the application server to ldquosleeprdquo and not process anymore you can modify the machineconfig file whichresides in the WINDOWSMicrosoftNETFramework64v4030319Config directory
1 In NET 40 the processModel element in machineconfig supports the attribute autoConfig to specifywhether to automatically configure settings to achieve optimal performance based on the machineconfiguration You can set this attribute to True or False
For more information see msdnmicrosoftcomen-uslibrary7w2sway1aspx
2 If you are using a Web farm you must change the ltmachineKeygt tag in Webconfig (for just the Planning andConsolidation application) or Machineconfig (for all applications including Planning and Consolidation) toensure the validationKey and decryptionKey keys have the same value on all application servers Thisway when the authentication cookie is checked the authentication ticket used on one server can still be validon another server
For more information and sample Visual Basic code for generating random key values seemsdnmicrosoftcomen-uslibraryms998288aspxpaght000007_webfarmdeploymentconsiderationsand msdnmicrosoftcomen-uslibraryms998310aspx
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 DSNand 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 forODBC in IIS 70 75 80 or 85 see Setting Up ODBC Logging in IIS 70 for the Default Web Site [page 30]
3 Manually set up an ODBC data source for the Management Console See Setting Up an ODBC DataSource [page 32]
4 Modify the default access rights to the Management Console By default users in Active Directory can accessthe Management Console with whatever rights they have been granted on the server For information about
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 29
removing default access and creating a group that can access the console see Removing Default Access to theConsole [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommend thatyou only grant Management Console access to system administrators Planning and Consolidation users shouldnot have any access For more information see Management Console Access Control [page 33]
6 Configure the use of SSL in Planning and Consolidation See Configuring Planning and Consolidation to useSSL [page 34]
7 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
8 Configure Microsoft SQL Server Reporting Services to use SSL See Configuring MS SQL Server ReportingServices to use SSL [page 36]
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 databaserole 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 optionto use ODBC Logging Enter the following values
DSN is BPC_ManagementDSN Table is BPCLog The Microsoft SQL Server Username and Password
5 Restart IIS
NoteWithout these updates the Management Console does work but some functionality (specifically User Activityand Service Status) does not work as expected
Should you need to uninstall Planning and Consolidation we recommend that you reset the Active Log Formatfield in IIS to W3C Extended Log File Format
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
30
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
Prerequisites
ODBC logging has been configured according to the Microsoft Knowledge Base article 245243 How to configureODBC 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 inApplicationHostconfig as shown here
ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0logFormat=Custom gtUse 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-00AA006111E0appcmd 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 articlespecified in the Prerequisites section Configure these settings in the ltodbcLogginggt node underltsystemwebServergt
Exampleltlocation path=Default Web SitegtltsystemwebServergtltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog userName=Usernamepassword=mypassword gtltsystemwebServergtltlocationgt
Use the following AppCmds to configure these attributes for the default Web site
appcmd set config Default Web Site sectionodbcLogging dataSourceBPC_ManagementDSN commitappHostappcmd set config Default Web Site sectionodbcLogging tableNameBPCLog commitappHostappcmd set config Default Web Site sectionodbcLogging userNameUsername commitappHostappcmd set config Default Web Site sectionodbcLogging passwordmypassword commitappHost
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 31
NoteYou cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must use the SQL ServerODBC driver For more information see the Microsoft Knowledge Base article 931202 The requirements for usingthe ODBC logging feature in IIS
343 Setting Up an ODBC Data Source in Windows Server2008 2008 R2 2012 or 2012 R2
Procedure
This procedure describes how to set up an ODBC data source for the Management Console in Windows Server 20082008 R2 2012 or 2012 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
NoteIf you have chosen SAP BusinessObjects User Management System in the installation screen you do not needto remove or configure access because the Management Console service always runs with the System Admin IDaccount which is a member of the Administrators group
Procedure
To remove default access to the Management Console and create a group that does have access to the console usethe procedure described below
32
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
NoteCreate your Management Console administrative group either on the server that hosts the Management Consoleor 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
NoteAlternatively you can perform analogous steps in Active Directory
3 In the Groups context menu choose New Group
4 Enter data as required Click Create
5 In the Computer Management dialog box choose Services and Applications Internet InformationServices 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 objectand all child objects Include these with entries explicitly defined here checkbox
NoteThis step is a necessary precursor to the completion of this procedure
10 In the Security dialog box click Copy to ensure that the System group retains its privileges
11 Remove access to the Management Console from all groups that should not have it
12 Choose Authentication in the center pane then disable Windows authentication
Result
Users who have not been granted access to the Management Console can still open the Management Console Webpage but it contains no data or menu options This does not affect the access that a user would otherwise have toPlanning and Consolidation
345 Management Console Access Control
After establishing the Management Console group you can add users or groups to it For more information aboutcreating this group see Removing Default Access to the Console [page 32] Their rights in Active Directory determinewhat they can access in the Console
By default any member of the Administrators Active Directory group on the application server or domain has fullaccess to all of the features of the Console except the Planning and Consolidation logging area Access to Planningand Consolidation logging is controlled within the Planning and Consolidation Administration Client task securityThe user must be granted View system logs task privileges For more information see the SAP Library Planning and
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 33
Consolidation Administrators Guide in servicesapcominstguidesepm-bpc 100 version for the Microsoftplatform
Your IT policy determines whether you grant access by group or user You may wish to create several levels of Consoleusers (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 describedin this table
Table 9
Privilege Rights Management Area
Task Manager and Kill Process Administrators group on application server or domain
Performance Monitor Counters Administrators group on application server or domain
Power Users group on application server or domain
Performance Monitor Users group on application server
Microsoft Analysis Services performance monitoring Administrators group on application server or domain
Microsoft SQL Server Monitoring (performance counters andstatistics)
Administrators group on application server or domain
346 Configuring Planning and Consolidation to use SSL
Procedure
Creating a Certificate for the Server
During the handshake phase of the SSL communication the server must send its certificate to the client The clientthen uses the certificate to encrypt information and send it back to the server
The procedure below describes how to create a self-signed certificate for the server
RecommendationWe recommend that you limit the use of self-signed certificates to testing only For a productive system you shouldobtain a certificate signed by a well-known certification authority (CA)
1 Start the Internet Information Services (IIS) Manager To do that go to Start All Programs AdministrativeTools Internet Information Services (IIS) Manager
2 In the Connections panel on the left-hand side select the server node and then choose Server Certificates
3 In the Actions panel on the right hand side choose the Create Self-Signed Certificate action
4 Enter the name that you want the certificate to be identified by for example MyTestSSLCertificate
IIS generates a new SSL certificate for you that has one yearrsquos expiry lease The certificate is issued to the local servername
Binding the Certificate to the Web Site
The procedure below describes how to bind the certificate to the web site for which SSL connections must be used
1 In the Connections panel select the web site node
2 In the Actions panel choose Bindings
34
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
3 In the Site Bindings dialog that appears choose the Add button to create a new binding
4 Configure the parameters as follows
Type = https IP Address = [1] - this is a shorthand expression for the local server name
Port = 443 - this is the default SSL port
SSL Certificate = enter your newly created certificate name
5 Choose OK to create the new binding and then close the Site Bindings dialog
6 Restart the IIS processes To do this choose Restart from the Actions panel
7 In the middle panel under the IIS section choose SSL Settings
8 In the SSL Settings screen select the Require SSL checkbox
9 In the Actions panel choose to Apply these settings
To test the SSL connection in the Actions panel choose the Browse [1] 443 (https) link
347 Using Client Certificates
To enable the use of client certificates in Planning and Consolidation you must follow several manual steps
NotePlanning and Consolidation supports client certificate authentication in Windows Authentication Mode butdoes 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 technetmicrosoftcomen-uslibrarycc753810aspx
For more information about configuring the client certificate mapping authentication see technetmicrosoftcomen-uslibrarycc732996(WS10)aspx
When you create the client certificates you can set the type of certificate in the SSL Settings screen in InternetInformation Services (IIS) Manager
Procedure
1 Set the options for client certificates
1 In the IIS Manager select the web site where you installed Planning and Consolidation
2 Choose SSL Settings
3 In the Client certificates section select the Accept client certificates option
This option allows you to use a client certificate or username and password (Basic authentication) toconnect 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 theManagementConsole home page
3 Double-click Authentication and enable Anonymous Authentication
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 35
4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way asin step 3
5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the sameway 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
348 Configuring MS SQL Server Reporting Services to useSSL
Procedure
The procedure below describes how to configure the use of SSL in Microsoft SQL Server Reporting Services
NoteReporting Services does not provide functionalities for generating requesting or installing a certificate Theserver certificates that you want to use for configuring SSL must have already been installed on your computer
1 Open the Reporting Services Configuration Manager program To do this open the Windows Start menu andnavigate to All Programs Microsoft SQL Server ltversiongt Configuration Tools Reporting ServicesConfiguration Manager
2 In the Connect panel on the left-hand side select the Web Service URL option to open all the Report Server webservice parameters
3 Configure the parameters as follows
SSL Certificate = the name of the certificate that you want to use
SSL Port = 4434 Choose Apply to confirm the changes
5 In the Connect panel choose Report Manager URL to open the list of parameters that link Reporting Servicesto IIS
6 Choose Advanced to add your new SSL web URL
7 In the section Multiple SSL Identities for Report Manager choose Add Configure the parameters as follows
IP Address = (All IPv4) SSL Port = 443 Certificate = the name of your SSL certificate
8 To test the configuration click the URL that appears under the Report manager Site Identification section
36
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
4 Installing Planning and ConsolidationAdministration Client and the SAPBusinessObjects EPM solutions Add-in forMicrosoft Office
The installation of the Planning and Consolidation Administration Client allows administrators to build and maintainPlanning and Consolidation environments and models and administer security
All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions add-in forMicrosoft 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 valueof the Planning and Consolidation client to prompt for user name and password Otherwise the Planning andConsolidation Start Page does not display
41 Installing the Administration Client
Prerequisites
NoteFor a definitive list of system requirements see the Product Availability Matrix on SAP Service Marketplace atservicesapcompam Search on Planning and Consolidation
The following list describes the minimum software requirements
Microsoft Internet Explorer 70 80 90 or 10
Microsoft Office 2003 2007 2010 or 2012
NET Framework 20 or higher (install any required NET Framework Hotfixes by referring tosupportmicrosoftcomkb)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 37
NoteWe recommend that you install all of the latest Microsoft Windows hotfixes prior to installing the Administrationclient For information about which hotfixes to install see updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us
Procedure
The 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 ltPC_serverportgtsapbpcweb
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 mustdownload the most recent version of the full setup (EPM Add-inexe) from the Service Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPCInstallation folder
Individual users can install the EPM add-in on their own machines by going to the Planning and Consolidation Homepage 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 upthe 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
38
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
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 toperform the upgrade If Client Auto Update is not enabled and a newer version is detected clients must be installedmanually 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 andpassword in the Admin ID and Admin password fields respectively The Admin ID should be a member of thelocal administrators group on all the computers running the auto update This setting is not needed if all usershave 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 Thisoption is stored in the user preferences and may also be turned on or off using the User Optionshellip menu itemIf 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 toinstall 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 installit 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 servicesapcom
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 versionand policy information For a support package these files are
EPM Addin Support Package ltSP versiongtmsp EPM Addin Support Package ltSP versiongtxmlFor a patch these files are
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 (WebsrvrWebBPCInstallation)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 39
You can set a different update policy for each package listed
ExampleThe following table illustrates some possible situations assuming that you have installed the first full version(V1)
Table 10
Available maintenancepackages
V2-user update
V3-force update
V4-force update
V5-user update
V5-user update V5-user update
V6-auto update
V7-force update
Minimum RequiredVersion
V4 V4 V7
Notification A prompt tells the user toinstall maintenancepackage V4 using theForced Update behavior
If User Update is enabledthe prompt informs theuser that maintenancepackage V5 is available
A prompt tells the user toinstall maintenancepackage V7 using theForced Update behavior
New Version V4 V4 or V5 V7
If you change the update policy for any package click Update to complete the change
40
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
5 Connection Issues
You may experience connection problems with ports the proxy server or programs and settings that interact withthese components If you have any issues related to connection review the following recommendations andtroubleshooting tips
51 Checking for Open Ports
You must ensure that all required ports are open for inboundoutbound traffic By default Planning andConsolidation requires that Ports 80 (used by http) and 1433 and 2383 (used by SQL Server 2008) are open Totest whether the required ports are open go to a command prompt and enter the Telnet serveripaddress and portFor example Telnet 431181836 80 If the system returns a blank command window the port is open If it returnsa message stating that it is unable to connect the port is not open
NoteYou can use the following site to scan for the normal ports It allows you to manually enter a port number to test
wwwmyserverorgportsniffasp
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 Planningand Consolidation server as an exception You can do this at the client level ( Internet Explorer ToolsInternet 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 fullyqualified 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 Consolidationauthentication Do not use authentication on the proxy server The system synchronizes the user name andpassword on the remote server with the local user name and password
SAP Business Planning and Consolidation 100Connection Issues
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 41
NoteFor more information about setting up an ISA proxy server contact SAP Support to request a copy of Setting upISA Proxy Server White Paper For more information about Business Planning and Consolidation firewall portssee SAP Note 1505250
Internet Explorer Settings Issues
Internet Explorer settings must be set correctly to prevent errors and problems when you attempt to access thePlanning 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 insertthe IP address or fully qualified server name of the Planning and Consolidation server as an exception bychoosing 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
42
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Connection Issues
6 Installing Planning and Consolidation withTwo Active Directory Domains
To set up a Planning and Consolidation 10 application server in a hosted environment and use your own domainusers follow this procedure In general you install Planning and Consolidation on the host domain use the hostdomain account and assign it to the Planning and Consolidation users SysAdmin Admin and Users Then you acceptone 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 andpassword 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 topromote 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 privilegefor the Planning and Consolidation server
5 Install Planning and Consolidation and assign your domain account either to the three Planning andConsolidation administrative users SysAdmin Admin and Users or to only one of the three Planning andConsolidation administrative users and to three of your users Be sure you use your own user account ratherthan host domain users
Planning and Consolidation impersonation can then access your domain from the host environment becauseit has the privilege of your domain account
SAP Business Planning and Consolidation 100Installing Planning and Consolidation with Two Active Directory Domains
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 43
7 Installing Planning and Consolidation in aTerminal Services or Citrix ServerDeployment
This section describes best practices and instructions for installing Planning and Consolidation in a Terminal Servicesor Citrix Server deployment
71 Terminal Services Home Directories
We recommend using Terminal Server home directories rather than using the userrsquos profile directory The profiledirectory downloads a minimal amount of information about the dimensions of the environment you are logging onto and may be as large as 2 MB per user The profile directory is on the system drive and has limited space Byspecifying 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 individualserver 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 clientserver (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
44
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
Procedure
The following steps outline how to install the Planning and Consolidation clients in a Terminal Services (TS) or CitrixServer deployment
1 Make sure the Terminal Services or Citrix Server machine has the system requirements installed
2 Log on to the Terminal Services or Citrix Server machine with a user ID that has the rights to install on thatserver
3 At a command prompt enter Change userinstall
4 Open a browser and connect to the URL ltPC_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_MSBPCAdminMainexe
74 Creating a Shortcut to the Launch Page
Procedure
If you use published desktops instead of published applications the Planning and Consolidation desktop file (whichis installed on the current userrsquos desktop) must be moved to the All UsersDesktop folder
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 45
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 SQLServer 2012 support the remote modification of SSIS packages Planning and Consolidation also supports theremote 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 whichyou want to modify SSIS packages
These custom tasks reference dlls that connect to the database server and perform certain validation when usersset up the parameters of each task All the custom task reference components must also be installed in the machineon which you want to modify SSIS packages
We provide a program that registers all the reference components of the custom tasks This section explains theinstallation 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 ndash This folder contains all the dlls that should be installed on the machine There are Planning andConsolidation platform components and all of the Data Manager custom task files
Config folder ndash This folder contains only one file named Filelistxml and lists all of the files that should be installedIf you need to add or remove certain components from the installation you can modify this xml file
OSoftSetupexe ndash This is the main executable file to run the installation package
NoteIf you are not installing SSIS Custom Tasks on your client machine ndash specifically a machine other than the Planningand Consolidation application server ndash you must first install OSoftSSIS2008_Client or OSoftSSIS2012_Client onthe client machine followed by the SQL Server version If you want to use SQL 2008 Tasks under the SQL 2012environment you must install OSoftSSIS2008_Client on the application server For detailed information see SAPNote 1707410 You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package byextracting OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPCInstallation folder on the Planning and Consolidation server To modify SSIS packages on the Planning andConsolidation application server you need to install OSoftSSIS2008_Client or OSoftSSIS2012_Client for creatinga COM+ application For more information see Before You Modify the SSIS Packages [page 49] and Setup ofa COM+ Application on the Application Server [page 50]
Bin folder
This folder contains the following components
46
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Table 11
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012respectively
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
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 47
Name Remark
BPCWriteBackdll
InteropDTSdll
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 addmore components to the installation package you can copy the new components into the Bin folder and add theproper xml tags in FileListxml You need to enter information for the following tags
RegistType ndash This is the registration information of the component You can enter the following values
RegAsm ndash For NET component
48
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Regsvr32 ndash For VB6 component
Gacutil ndash For NET Framework component that should be registered into Global Assembly Cache
FileName ndash Component file name
OSoftSetupexe
This is the executable file to run the SSIS installation package Double-click the file to start the installation You needto enter information for the following fields
Set SQL server
Specify the SQL server name If your SQL Server has an instance specify the instance name
NoteIf you installed the OSoftSSIS2008_Client or OSoftSSIS2012_Client on the application server the SQL servername is automatically disabled
Set server credential
This is the credential name of the COM+ package component Enter the user ID and password that can accessyour SQL Server This should be either the System Admin ID or Admin ID that was registered as a COM+ userwhen 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 ifyou 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 packagesremotely This is also true for the application server that has SSIS installed The Planning and ConsolidationData Manager has the following custom tasks
Table 12
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008and 2012 respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and2012 respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012respectively
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 49
Name Remark
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and2012 respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008and 2012 respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL2008 and 2012 respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and2012 respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012respectively
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
ltdrivegtWebsrvrbin2 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 FilesMicrosoft SQLServer paste all files into the CProgram Files (x86)Microsoft SQL Server100DTSTasksfolder
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
50
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Typographic Conventions
Table 13
Example Description
lt gt Angle brackets indicate that you replace these words or characters with appropriate entries tomake entries in the system for example Enter your ltUser Namegt
File Save Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
Example Textual cross-references to an internet address for example wwwsapcom
example Quicklinks added to the internet address of a homepage to enable quick access to specificcontent 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 titlespushbutton 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 namesof installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transactioncodes database table names and key concepts of a programming language when they aresurrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
SAP Business Planning and Consolidation 100Typographic Conventions
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 51
52
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
wwwsapcom
Material Number
- SAP Business 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 2008 R2 2012 or 2012 R2
- 344 Removing Default Access to the Console
- 345 Management Console Access Control
- 346 Configuring Planning and Consolidation to use SSL
- 347 Using Client Certificates
- 348 Configuring MS SQL Server Reporting Services to use SSL
-
- 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
-
removing default access and creating a group that can access the console see Removing Default Access to theConsole [page 32]
5 Add authorized users or groups to the group that can access the Management Console We recommend thatyou only grant Management Console access to system administrators Planning and Consolidation users shouldnot have any access For more information see Management Console Access Control [page 33]
6 Configure the use of SSL in Planning and Consolidation See Configuring Planning and Consolidation to useSSL [page 34]
7 Configure the use of client certificates for authentication See Using Client Certificates [page 35]
8 Configure Microsoft SQL Server Reporting Services to use SSL See Configuring MS SQL Server ReportingServices to use SSL [page 36]
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 databaserole 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 optionto use ODBC Logging Enter the following values
DSN is BPC_ManagementDSN Table is BPCLog The Microsoft SQL Server Username and Password
5 Restart IIS
NoteWithout these updates the Management Console does work but some functionality (specifically User Activityand Service Status) does not work as expected
Should you need to uninstall Planning and Consolidation we recommend that you reset the Active Log Formatfield in IIS to W3C Extended Log File Format
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
30
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
Prerequisites
ODBC logging has been configured according to the Microsoft Knowledge Base article 245243 How to configureODBC 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 inApplicationHostconfig as shown here
ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0logFormat=Custom gtUse 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-00AA006111E0appcmd 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 articlespecified in the Prerequisites section Configure these settings in the ltodbcLogginggt node underltsystemwebServergt
Exampleltlocation path=Default Web SitegtltsystemwebServergtltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog userName=Usernamepassword=mypassword gtltsystemwebServergtltlocationgt
Use the following AppCmds to configure these attributes for the default Web site
appcmd set config Default Web Site sectionodbcLogging dataSourceBPC_ManagementDSN commitappHostappcmd set config Default Web Site sectionodbcLogging tableNameBPCLog commitappHostappcmd set config Default Web Site sectionodbcLogging userNameUsername commitappHostappcmd set config Default Web Site sectionodbcLogging passwordmypassword commitappHost
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 31
NoteYou cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must use the SQL ServerODBC driver For more information see the Microsoft Knowledge Base article 931202 The requirements for usingthe ODBC logging feature in IIS
343 Setting Up an ODBC Data Source in Windows Server2008 2008 R2 2012 or 2012 R2
Procedure
This procedure describes how to set up an ODBC data source for the Management Console in Windows Server 20082008 R2 2012 or 2012 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
NoteIf you have chosen SAP BusinessObjects User Management System in the installation screen you do not needto remove or configure access because the Management Console service always runs with the System Admin IDaccount which is a member of the Administrators group
Procedure
To remove default access to the Management Console and create a group that does have access to the console usethe procedure described below
32
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
NoteCreate your Management Console administrative group either on the server that hosts the Management Consoleor 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
NoteAlternatively you can perform analogous steps in Active Directory
3 In the Groups context menu choose New Group
4 Enter data as required Click Create
5 In the Computer Management dialog box choose Services and Applications Internet InformationServices 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 objectand all child objects Include these with entries explicitly defined here checkbox
NoteThis step is a necessary precursor to the completion of this procedure
10 In the Security dialog box click Copy to ensure that the System group retains its privileges
11 Remove access to the Management Console from all groups that should not have it
12 Choose Authentication in the center pane then disable Windows authentication
Result
Users who have not been granted access to the Management Console can still open the Management Console Webpage but it contains no data or menu options This does not affect the access that a user would otherwise have toPlanning and Consolidation
345 Management Console Access Control
After establishing the Management Console group you can add users or groups to it For more information aboutcreating this group see Removing Default Access to the Console [page 32] Their rights in Active Directory determinewhat they can access in the Console
By default any member of the Administrators Active Directory group on the application server or domain has fullaccess to all of the features of the Console except the Planning and Consolidation logging area Access to Planningand Consolidation logging is controlled within the Planning and Consolidation Administration Client task securityThe user must be granted View system logs task privileges For more information see the SAP Library Planning and
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 33
Consolidation Administrators Guide in servicesapcominstguidesepm-bpc 100 version for the Microsoftplatform
Your IT policy determines whether you grant access by group or user You may wish to create several levels of Consoleusers (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 describedin this table
Table 9
Privilege Rights Management Area
Task Manager and Kill Process Administrators group on application server or domain
Performance Monitor Counters Administrators group on application server or domain
Power Users group on application server or domain
Performance Monitor Users group on application server
Microsoft Analysis Services performance monitoring Administrators group on application server or domain
Microsoft SQL Server Monitoring (performance counters andstatistics)
Administrators group on application server or domain
346 Configuring Planning and Consolidation to use SSL
Procedure
Creating a Certificate for the Server
During the handshake phase of the SSL communication the server must send its certificate to the client The clientthen uses the certificate to encrypt information and send it back to the server
The procedure below describes how to create a self-signed certificate for the server
RecommendationWe recommend that you limit the use of self-signed certificates to testing only For a productive system you shouldobtain a certificate signed by a well-known certification authority (CA)
1 Start the Internet Information Services (IIS) Manager To do that go to Start All Programs AdministrativeTools Internet Information Services (IIS) Manager
2 In the Connections panel on the left-hand side select the server node and then choose Server Certificates
3 In the Actions panel on the right hand side choose the Create Self-Signed Certificate action
4 Enter the name that you want the certificate to be identified by for example MyTestSSLCertificate
IIS generates a new SSL certificate for you that has one yearrsquos expiry lease The certificate is issued to the local servername
Binding the Certificate to the Web Site
The procedure below describes how to bind the certificate to the web site for which SSL connections must be used
1 In the Connections panel select the web site node
2 In the Actions panel choose Bindings
34
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
3 In the Site Bindings dialog that appears choose the Add button to create a new binding
4 Configure the parameters as follows
Type = https IP Address = [1] - this is a shorthand expression for the local server name
Port = 443 - this is the default SSL port
SSL Certificate = enter your newly created certificate name
5 Choose OK to create the new binding and then close the Site Bindings dialog
6 Restart the IIS processes To do this choose Restart from the Actions panel
7 In the middle panel under the IIS section choose SSL Settings
8 In the SSL Settings screen select the Require SSL checkbox
9 In the Actions panel choose to Apply these settings
To test the SSL connection in the Actions panel choose the Browse [1] 443 (https) link
347 Using Client Certificates
To enable the use of client certificates in Planning and Consolidation you must follow several manual steps
NotePlanning and Consolidation supports client certificate authentication in Windows Authentication Mode butdoes 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 technetmicrosoftcomen-uslibrarycc753810aspx
For more information about configuring the client certificate mapping authentication see technetmicrosoftcomen-uslibrarycc732996(WS10)aspx
When you create the client certificates you can set the type of certificate in the SSL Settings screen in InternetInformation Services (IIS) Manager
Procedure
1 Set the options for client certificates
1 In the IIS Manager select the web site where you installed Planning and Consolidation
2 Choose SSL Settings
3 In the Client certificates section select the Accept client certificates option
This option allows you to use a client certificate or username and password (Basic authentication) toconnect 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 theManagementConsole home page
3 Double-click Authentication and enable Anonymous Authentication
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 35
4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way asin step 3
5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the sameway 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
348 Configuring MS SQL Server Reporting Services to useSSL
Procedure
The procedure below describes how to configure the use of SSL in Microsoft SQL Server Reporting Services
NoteReporting Services does not provide functionalities for generating requesting or installing a certificate Theserver certificates that you want to use for configuring SSL must have already been installed on your computer
1 Open the Reporting Services Configuration Manager program To do this open the Windows Start menu andnavigate to All Programs Microsoft SQL Server ltversiongt Configuration Tools Reporting ServicesConfiguration Manager
2 In the Connect panel on the left-hand side select the Web Service URL option to open all the Report Server webservice parameters
3 Configure the parameters as follows
SSL Certificate = the name of the certificate that you want to use
SSL Port = 4434 Choose Apply to confirm the changes
5 In the Connect panel choose Report Manager URL to open the list of parameters that link Reporting Servicesto IIS
6 Choose Advanced to add your new SSL web URL
7 In the section Multiple SSL Identities for Report Manager choose Add Configure the parameters as follows
IP Address = (All IPv4) SSL Port = 443 Certificate = the name of your SSL certificate
8 To test the configuration click the URL that appears under the Report manager Site Identification section
36
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
4 Installing Planning and ConsolidationAdministration Client and the SAPBusinessObjects EPM solutions Add-in forMicrosoft Office
The installation of the Planning and Consolidation Administration Client allows administrators to build and maintainPlanning and Consolidation environments and models and administer security
All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions add-in forMicrosoft 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 valueof the Planning and Consolidation client to prompt for user name and password Otherwise the Planning andConsolidation Start Page does not display
41 Installing the Administration Client
Prerequisites
NoteFor a definitive list of system requirements see the Product Availability Matrix on SAP Service Marketplace atservicesapcompam Search on Planning and Consolidation
The following list describes the minimum software requirements
Microsoft Internet Explorer 70 80 90 or 10
Microsoft Office 2003 2007 2010 or 2012
NET Framework 20 or higher (install any required NET Framework Hotfixes by referring tosupportmicrosoftcomkb)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 37
NoteWe recommend that you install all of the latest Microsoft Windows hotfixes prior to installing the Administrationclient For information about which hotfixes to install see updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us
Procedure
The 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 ltPC_serverportgtsapbpcweb
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 mustdownload the most recent version of the full setup (EPM Add-inexe) from the Service Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPCInstallation folder
Individual users can install the EPM add-in on their own machines by going to the Planning and Consolidation Homepage 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 upthe 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
38
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
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 toperform the upgrade If Client Auto Update is not enabled and a newer version is detected clients must be installedmanually 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 andpassword in the Admin ID and Admin password fields respectively The Admin ID should be a member of thelocal administrators group on all the computers running the auto update This setting is not needed if all usershave 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 Thisoption is stored in the user preferences and may also be turned on or off using the User Optionshellip menu itemIf 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 toinstall 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 installit 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 servicesapcom
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 versionand policy information For a support package these files are
EPM Addin Support Package ltSP versiongtmsp EPM Addin Support Package ltSP versiongtxmlFor a patch these files are
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 (WebsrvrWebBPCInstallation)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 39
You can set a different update policy for each package listed
ExampleThe following table illustrates some possible situations assuming that you have installed the first full version(V1)
Table 10
Available maintenancepackages
V2-user update
V3-force update
V4-force update
V5-user update
V5-user update V5-user update
V6-auto update
V7-force update
Minimum RequiredVersion
V4 V4 V7
Notification A prompt tells the user toinstall maintenancepackage V4 using theForced Update behavior
If User Update is enabledthe prompt informs theuser that maintenancepackage V5 is available
A prompt tells the user toinstall maintenancepackage V7 using theForced Update behavior
New Version V4 V4 or V5 V7
If you change the update policy for any package click Update to complete the change
40
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
5 Connection Issues
You may experience connection problems with ports the proxy server or programs and settings that interact withthese components If you have any issues related to connection review the following recommendations andtroubleshooting tips
51 Checking for Open Ports
You must ensure that all required ports are open for inboundoutbound traffic By default Planning andConsolidation requires that Ports 80 (used by http) and 1433 and 2383 (used by SQL Server 2008) are open Totest whether the required ports are open go to a command prompt and enter the Telnet serveripaddress and portFor example Telnet 431181836 80 If the system returns a blank command window the port is open If it returnsa message stating that it is unable to connect the port is not open
NoteYou can use the following site to scan for the normal ports It allows you to manually enter a port number to test
wwwmyserverorgportsniffasp
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 Planningand Consolidation server as an exception You can do this at the client level ( Internet Explorer ToolsInternet 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 fullyqualified 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 Consolidationauthentication Do not use authentication on the proxy server The system synchronizes the user name andpassword on the remote server with the local user name and password
SAP Business Planning and Consolidation 100Connection Issues
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 41
NoteFor more information about setting up an ISA proxy server contact SAP Support to request a copy of Setting upISA Proxy Server White Paper For more information about Business Planning and Consolidation firewall portssee SAP Note 1505250
Internet Explorer Settings Issues
Internet Explorer settings must be set correctly to prevent errors and problems when you attempt to access thePlanning 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 insertthe IP address or fully qualified server name of the Planning and Consolidation server as an exception bychoosing 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
42
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Connection Issues
6 Installing Planning and Consolidation withTwo Active Directory Domains
To set up a Planning and Consolidation 10 application server in a hosted environment and use your own domainusers follow this procedure In general you install Planning and Consolidation on the host domain use the hostdomain account and assign it to the Planning and Consolidation users SysAdmin Admin and Users Then you acceptone 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 andpassword 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 topromote 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 privilegefor the Planning and Consolidation server
5 Install Planning and Consolidation and assign your domain account either to the three Planning andConsolidation administrative users SysAdmin Admin and Users or to only one of the three Planning andConsolidation administrative users and to three of your users Be sure you use your own user account ratherthan host domain users
Planning and Consolidation impersonation can then access your domain from the host environment becauseit has the privilege of your domain account
SAP Business Planning and Consolidation 100Installing Planning and Consolidation with Two Active Directory Domains
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 43
7 Installing Planning and Consolidation in aTerminal Services or Citrix ServerDeployment
This section describes best practices and instructions for installing Planning and Consolidation in a Terminal Servicesor Citrix Server deployment
71 Terminal Services Home Directories
We recommend using Terminal Server home directories rather than using the userrsquos profile directory The profiledirectory downloads a minimal amount of information about the dimensions of the environment you are logging onto and may be as large as 2 MB per user The profile directory is on the system drive and has limited space Byspecifying 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 individualserver 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 clientserver (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
44
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
Procedure
The following steps outline how to install the Planning and Consolidation clients in a Terminal Services (TS) or CitrixServer deployment
1 Make sure the Terminal Services or Citrix Server machine has the system requirements installed
2 Log on to the Terminal Services or Citrix Server machine with a user ID that has the rights to install on thatserver
3 At a command prompt enter Change userinstall
4 Open a browser and connect to the URL ltPC_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_MSBPCAdminMainexe
74 Creating a Shortcut to the Launch Page
Procedure
If you use published desktops instead of published applications the Planning and Consolidation desktop file (whichis installed on the current userrsquos desktop) must be moved to the All UsersDesktop folder
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 45
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 SQLServer 2012 support the remote modification of SSIS packages Planning and Consolidation also supports theremote 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 whichyou want to modify SSIS packages
These custom tasks reference dlls that connect to the database server and perform certain validation when usersset up the parameters of each task All the custom task reference components must also be installed in the machineon which you want to modify SSIS packages
We provide a program that registers all the reference components of the custom tasks This section explains theinstallation 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 ndash This folder contains all the dlls that should be installed on the machine There are Planning andConsolidation platform components and all of the Data Manager custom task files
Config folder ndash This folder contains only one file named Filelistxml and lists all of the files that should be installedIf you need to add or remove certain components from the installation you can modify this xml file
OSoftSetupexe ndash This is the main executable file to run the installation package
NoteIf you are not installing SSIS Custom Tasks on your client machine ndash specifically a machine other than the Planningand Consolidation application server ndash you must first install OSoftSSIS2008_Client or OSoftSSIS2012_Client onthe client machine followed by the SQL Server version If you want to use SQL 2008 Tasks under the SQL 2012environment you must install OSoftSSIS2008_Client on the application server For detailed information see SAPNote 1707410 You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package byextracting OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPCInstallation folder on the Planning and Consolidation server To modify SSIS packages on the Planning andConsolidation application server you need to install OSoftSSIS2008_Client or OSoftSSIS2012_Client for creatinga COM+ application For more information see Before You Modify the SSIS Packages [page 49] and Setup ofa COM+ Application on the Application Server [page 50]
Bin folder
This folder contains the following components
46
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Table 11
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012respectively
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
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 47
Name Remark
BPCWriteBackdll
InteropDTSdll
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 addmore components to the installation package you can copy the new components into the Bin folder and add theproper xml tags in FileListxml You need to enter information for the following tags
RegistType ndash This is the registration information of the component You can enter the following values
RegAsm ndash For NET component
48
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Regsvr32 ndash For VB6 component
Gacutil ndash For NET Framework component that should be registered into Global Assembly Cache
FileName ndash Component file name
OSoftSetupexe
This is the executable file to run the SSIS installation package Double-click the file to start the installation You needto enter information for the following fields
Set SQL server
Specify the SQL server name If your SQL Server has an instance specify the instance name
NoteIf you installed the OSoftSSIS2008_Client or OSoftSSIS2012_Client on the application server the SQL servername is automatically disabled
Set server credential
This is the credential name of the COM+ package component Enter the user ID and password that can accessyour SQL Server This should be either the System Admin ID or Admin ID that was registered as a COM+ userwhen 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 ifyou 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 packagesremotely This is also true for the application server that has SSIS installed The Planning and ConsolidationData Manager has the following custom tasks
Table 12
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008and 2012 respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and2012 respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012respectively
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 49
Name Remark
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and2012 respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008and 2012 respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL2008 and 2012 respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and2012 respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012respectively
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
ltdrivegtWebsrvrbin2 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 FilesMicrosoft SQLServer paste all files into the CProgram Files (x86)Microsoft SQL Server100DTSTasksfolder
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
50
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Typographic Conventions
Table 13
Example Description
lt gt Angle brackets indicate that you replace these words or characters with appropriate entries tomake entries in the system for example Enter your ltUser Namegt
File Save Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
Example Textual cross-references to an internet address for example wwwsapcom
example Quicklinks added to the internet address of a homepage to enable quick access to specificcontent 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 titlespushbutton 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 namesof installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transactioncodes database table names and key concepts of a programming language when they aresurrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
SAP Business Planning and Consolidation 100Typographic Conventions
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 51
52
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
wwwsapcom
Material Number
- SAP Business 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 2008 R2 2012 or 2012 R2
- 344 Removing Default Access to the Console
- 345 Management Console Access Control
- 346 Configuring Planning and Consolidation to use SSL
- 347 Using Client Certificates
- 348 Configuring MS SQL Server Reporting Services to use SSL
-
- 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
-
Prerequisites
ODBC logging has been configured according to the Microsoft Knowledge Base article 245243 How to configureODBC 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 inApplicationHostconfig as shown here
ltlogFile customLogPluginClsid=FF16065B-DE82-11CF-BC0A-00AA006111E0logFormat=Custom gtUse 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-00AA006111E0appcmd 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 articlespecified in the Prerequisites section Configure these settings in the ltodbcLogginggt node underltsystemwebServergt
Exampleltlocation path=Default Web SitegtltsystemwebServergtltodbcLogging dataSource=BPC_ManagementDSN tableName=BPCLog userName=Usernamepassword=mypassword gtltsystemwebServergtltlocationgt
Use the following AppCmds to configure these attributes for the default Web site
appcmd set config Default Web Site sectionodbcLogging dataSourceBPC_ManagementDSN commitappHostappcmd set config Default Web Site sectionodbcLogging tableNameBPCLog commitappHostappcmd set config Default Web Site sectionodbcLogging userNameUsername commitappHostappcmd set config Default Web Site sectionodbcLogging passwordmypassword commitappHost
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 31
NoteYou cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must use the SQL ServerODBC driver For more information see the Microsoft Knowledge Base article 931202 The requirements for usingthe ODBC logging feature in IIS
343 Setting Up an ODBC Data Source in Windows Server2008 2008 R2 2012 or 2012 R2
Procedure
This procedure describes how to set up an ODBC data source for the Management Console in Windows Server 20082008 R2 2012 or 2012 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
NoteIf you have chosen SAP BusinessObjects User Management System in the installation screen you do not needto remove or configure access because the Management Console service always runs with the System Admin IDaccount which is a member of the Administrators group
Procedure
To remove default access to the Management Console and create a group that does have access to the console usethe procedure described below
32
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
NoteCreate your Management Console administrative group either on the server that hosts the Management Consoleor 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
NoteAlternatively you can perform analogous steps in Active Directory
3 In the Groups context menu choose New Group
4 Enter data as required Click Create
5 In the Computer Management dialog box choose Services and Applications Internet InformationServices 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 objectand all child objects Include these with entries explicitly defined here checkbox
NoteThis step is a necessary precursor to the completion of this procedure
10 In the Security dialog box click Copy to ensure that the System group retains its privileges
11 Remove access to the Management Console from all groups that should not have it
12 Choose Authentication in the center pane then disable Windows authentication
Result
Users who have not been granted access to the Management Console can still open the Management Console Webpage but it contains no data or menu options This does not affect the access that a user would otherwise have toPlanning and Consolidation
345 Management Console Access Control
After establishing the Management Console group you can add users or groups to it For more information aboutcreating this group see Removing Default Access to the Console [page 32] Their rights in Active Directory determinewhat they can access in the Console
By default any member of the Administrators Active Directory group on the application server or domain has fullaccess to all of the features of the Console except the Planning and Consolidation logging area Access to Planningand Consolidation logging is controlled within the Planning and Consolidation Administration Client task securityThe user must be granted View system logs task privileges For more information see the SAP Library Planning and
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 33
Consolidation Administrators Guide in servicesapcominstguidesepm-bpc 100 version for the Microsoftplatform
Your IT policy determines whether you grant access by group or user You may wish to create several levels of Consoleusers (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 describedin this table
Table 9
Privilege Rights Management Area
Task Manager and Kill Process Administrators group on application server or domain
Performance Monitor Counters Administrators group on application server or domain
Power Users group on application server or domain
Performance Monitor Users group on application server
Microsoft Analysis Services performance monitoring Administrators group on application server or domain
Microsoft SQL Server Monitoring (performance counters andstatistics)
Administrators group on application server or domain
346 Configuring Planning and Consolidation to use SSL
Procedure
Creating a Certificate for the Server
During the handshake phase of the SSL communication the server must send its certificate to the client The clientthen uses the certificate to encrypt information and send it back to the server
The procedure below describes how to create a self-signed certificate for the server
RecommendationWe recommend that you limit the use of self-signed certificates to testing only For a productive system you shouldobtain a certificate signed by a well-known certification authority (CA)
1 Start the Internet Information Services (IIS) Manager To do that go to Start All Programs AdministrativeTools Internet Information Services (IIS) Manager
2 In the Connections panel on the left-hand side select the server node and then choose Server Certificates
3 In the Actions panel on the right hand side choose the Create Self-Signed Certificate action
4 Enter the name that you want the certificate to be identified by for example MyTestSSLCertificate
IIS generates a new SSL certificate for you that has one yearrsquos expiry lease The certificate is issued to the local servername
Binding the Certificate to the Web Site
The procedure below describes how to bind the certificate to the web site for which SSL connections must be used
1 In the Connections panel select the web site node
2 In the Actions panel choose Bindings
34
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
3 In the Site Bindings dialog that appears choose the Add button to create a new binding
4 Configure the parameters as follows
Type = https IP Address = [1] - this is a shorthand expression for the local server name
Port = 443 - this is the default SSL port
SSL Certificate = enter your newly created certificate name
5 Choose OK to create the new binding and then close the Site Bindings dialog
6 Restart the IIS processes To do this choose Restart from the Actions panel
7 In the middle panel under the IIS section choose SSL Settings
8 In the SSL Settings screen select the Require SSL checkbox
9 In the Actions panel choose to Apply these settings
To test the SSL connection in the Actions panel choose the Browse [1] 443 (https) link
347 Using Client Certificates
To enable the use of client certificates in Planning and Consolidation you must follow several manual steps
NotePlanning and Consolidation supports client certificate authentication in Windows Authentication Mode butdoes 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 technetmicrosoftcomen-uslibrarycc753810aspx
For more information about configuring the client certificate mapping authentication see technetmicrosoftcomen-uslibrarycc732996(WS10)aspx
When you create the client certificates you can set the type of certificate in the SSL Settings screen in InternetInformation Services (IIS) Manager
Procedure
1 Set the options for client certificates
1 In the IIS Manager select the web site where you installed Planning and Consolidation
2 Choose SSL Settings
3 In the Client certificates section select the Accept client certificates option
This option allows you to use a client certificate or username and password (Basic authentication) toconnect 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 theManagementConsole home page
3 Double-click Authentication and enable Anonymous Authentication
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 35
4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way asin step 3
5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the sameway 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
348 Configuring MS SQL Server Reporting Services to useSSL
Procedure
The procedure below describes how to configure the use of SSL in Microsoft SQL Server Reporting Services
NoteReporting Services does not provide functionalities for generating requesting or installing a certificate Theserver certificates that you want to use for configuring SSL must have already been installed on your computer
1 Open the Reporting Services Configuration Manager program To do this open the Windows Start menu andnavigate to All Programs Microsoft SQL Server ltversiongt Configuration Tools Reporting ServicesConfiguration Manager
2 In the Connect panel on the left-hand side select the Web Service URL option to open all the Report Server webservice parameters
3 Configure the parameters as follows
SSL Certificate = the name of the certificate that you want to use
SSL Port = 4434 Choose Apply to confirm the changes
5 In the Connect panel choose Report Manager URL to open the list of parameters that link Reporting Servicesto IIS
6 Choose Advanced to add your new SSL web URL
7 In the section Multiple SSL Identities for Report Manager choose Add Configure the parameters as follows
IP Address = (All IPv4) SSL Port = 443 Certificate = the name of your SSL certificate
8 To test the configuration click the URL that appears under the Report manager Site Identification section
36
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
4 Installing Planning and ConsolidationAdministration Client and the SAPBusinessObjects EPM solutions Add-in forMicrosoft Office
The installation of the Planning and Consolidation Administration Client allows administrators to build and maintainPlanning and Consolidation environments and models and administer security
All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions add-in forMicrosoft 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 valueof the Planning and Consolidation client to prompt for user name and password Otherwise the Planning andConsolidation Start Page does not display
41 Installing the Administration Client
Prerequisites
NoteFor a definitive list of system requirements see the Product Availability Matrix on SAP Service Marketplace atservicesapcompam Search on Planning and Consolidation
The following list describes the minimum software requirements
Microsoft Internet Explorer 70 80 90 or 10
Microsoft Office 2003 2007 2010 or 2012
NET Framework 20 or higher (install any required NET Framework Hotfixes by referring tosupportmicrosoftcomkb)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 37
NoteWe recommend that you install all of the latest Microsoft Windows hotfixes prior to installing the Administrationclient For information about which hotfixes to install see updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us
Procedure
The 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 ltPC_serverportgtsapbpcweb
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 mustdownload the most recent version of the full setup (EPM Add-inexe) from the Service Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPCInstallation folder
Individual users can install the EPM add-in on their own machines by going to the Planning and Consolidation Homepage 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 upthe 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
38
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
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 toperform the upgrade If Client Auto Update is not enabled and a newer version is detected clients must be installedmanually 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 andpassword in the Admin ID and Admin password fields respectively The Admin ID should be a member of thelocal administrators group on all the computers running the auto update This setting is not needed if all usershave 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 Thisoption is stored in the user preferences and may also be turned on or off using the User Optionshellip menu itemIf 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 toinstall 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 installit 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 servicesapcom
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 versionand policy information For a support package these files are
EPM Addin Support Package ltSP versiongtmsp EPM Addin Support Package ltSP versiongtxmlFor a patch these files are
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 (WebsrvrWebBPCInstallation)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 39
You can set a different update policy for each package listed
ExampleThe following table illustrates some possible situations assuming that you have installed the first full version(V1)
Table 10
Available maintenancepackages
V2-user update
V3-force update
V4-force update
V5-user update
V5-user update V5-user update
V6-auto update
V7-force update
Minimum RequiredVersion
V4 V4 V7
Notification A prompt tells the user toinstall maintenancepackage V4 using theForced Update behavior
If User Update is enabledthe prompt informs theuser that maintenancepackage V5 is available
A prompt tells the user toinstall maintenancepackage V7 using theForced Update behavior
New Version V4 V4 or V5 V7
If you change the update policy for any package click Update to complete the change
40
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
5 Connection Issues
You may experience connection problems with ports the proxy server or programs and settings that interact withthese components If you have any issues related to connection review the following recommendations andtroubleshooting tips
51 Checking for Open Ports
You must ensure that all required ports are open for inboundoutbound traffic By default Planning andConsolidation requires that Ports 80 (used by http) and 1433 and 2383 (used by SQL Server 2008) are open Totest whether the required ports are open go to a command prompt and enter the Telnet serveripaddress and portFor example Telnet 431181836 80 If the system returns a blank command window the port is open If it returnsa message stating that it is unable to connect the port is not open
NoteYou can use the following site to scan for the normal ports It allows you to manually enter a port number to test
wwwmyserverorgportsniffasp
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 Planningand Consolidation server as an exception You can do this at the client level ( Internet Explorer ToolsInternet 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 fullyqualified 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 Consolidationauthentication Do not use authentication on the proxy server The system synchronizes the user name andpassword on the remote server with the local user name and password
SAP Business Planning and Consolidation 100Connection Issues
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 41
NoteFor more information about setting up an ISA proxy server contact SAP Support to request a copy of Setting upISA Proxy Server White Paper For more information about Business Planning and Consolidation firewall portssee SAP Note 1505250
Internet Explorer Settings Issues
Internet Explorer settings must be set correctly to prevent errors and problems when you attempt to access thePlanning 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 insertthe IP address or fully qualified server name of the Planning and Consolidation server as an exception bychoosing 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
42
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Connection Issues
6 Installing Planning and Consolidation withTwo Active Directory Domains
To set up a Planning and Consolidation 10 application server in a hosted environment and use your own domainusers follow this procedure In general you install Planning and Consolidation on the host domain use the hostdomain account and assign it to the Planning and Consolidation users SysAdmin Admin and Users Then you acceptone 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 andpassword 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 topromote 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 privilegefor the Planning and Consolidation server
5 Install Planning and Consolidation and assign your domain account either to the three Planning andConsolidation administrative users SysAdmin Admin and Users or to only one of the three Planning andConsolidation administrative users and to three of your users Be sure you use your own user account ratherthan host domain users
Planning and Consolidation impersonation can then access your domain from the host environment becauseit has the privilege of your domain account
SAP Business Planning and Consolidation 100Installing Planning and Consolidation with Two Active Directory Domains
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 43
7 Installing Planning and Consolidation in aTerminal Services or Citrix ServerDeployment
This section describes best practices and instructions for installing Planning and Consolidation in a Terminal Servicesor Citrix Server deployment
71 Terminal Services Home Directories
We recommend using Terminal Server home directories rather than using the userrsquos profile directory The profiledirectory downloads a minimal amount of information about the dimensions of the environment you are logging onto and may be as large as 2 MB per user The profile directory is on the system drive and has limited space Byspecifying 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 individualserver 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 clientserver (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
44
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
Procedure
The following steps outline how to install the Planning and Consolidation clients in a Terminal Services (TS) or CitrixServer deployment
1 Make sure the Terminal Services or Citrix Server machine has the system requirements installed
2 Log on to the Terminal Services or Citrix Server machine with a user ID that has the rights to install on thatserver
3 At a command prompt enter Change userinstall
4 Open a browser and connect to the URL ltPC_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_MSBPCAdminMainexe
74 Creating a Shortcut to the Launch Page
Procedure
If you use published desktops instead of published applications the Planning and Consolidation desktop file (whichis installed on the current userrsquos desktop) must be moved to the All UsersDesktop folder
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 45
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 SQLServer 2012 support the remote modification of SSIS packages Planning and Consolidation also supports theremote 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 whichyou want to modify SSIS packages
These custom tasks reference dlls that connect to the database server and perform certain validation when usersset up the parameters of each task All the custom task reference components must also be installed in the machineon which you want to modify SSIS packages
We provide a program that registers all the reference components of the custom tasks This section explains theinstallation 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 ndash This folder contains all the dlls that should be installed on the machine There are Planning andConsolidation platform components and all of the Data Manager custom task files
Config folder ndash This folder contains only one file named Filelistxml and lists all of the files that should be installedIf you need to add or remove certain components from the installation you can modify this xml file
OSoftSetupexe ndash This is the main executable file to run the installation package
NoteIf you are not installing SSIS Custom Tasks on your client machine ndash specifically a machine other than the Planningand Consolidation application server ndash you must first install OSoftSSIS2008_Client or OSoftSSIS2012_Client onthe client machine followed by the SQL Server version If you want to use SQL 2008 Tasks under the SQL 2012environment you must install OSoftSSIS2008_Client on the application server For detailed information see SAPNote 1707410 You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package byextracting OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPCInstallation folder on the Planning and Consolidation server To modify SSIS packages on the Planning andConsolidation application server you need to install OSoftSSIS2008_Client or OSoftSSIS2012_Client for creatinga COM+ application For more information see Before You Modify the SSIS Packages [page 49] and Setup ofa COM+ Application on the Application Server [page 50]
Bin folder
This folder contains the following components
46
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Table 11
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012respectively
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
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 47
Name Remark
BPCWriteBackdll
InteropDTSdll
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 addmore components to the installation package you can copy the new components into the Bin folder and add theproper xml tags in FileListxml You need to enter information for the following tags
RegistType ndash This is the registration information of the component You can enter the following values
RegAsm ndash For NET component
48
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Regsvr32 ndash For VB6 component
Gacutil ndash For NET Framework component that should be registered into Global Assembly Cache
FileName ndash Component file name
OSoftSetupexe
This is the executable file to run the SSIS installation package Double-click the file to start the installation You needto enter information for the following fields
Set SQL server
Specify the SQL server name If your SQL Server has an instance specify the instance name
NoteIf you installed the OSoftSSIS2008_Client or OSoftSSIS2012_Client on the application server the SQL servername is automatically disabled
Set server credential
This is the credential name of the COM+ package component Enter the user ID and password that can accessyour SQL Server This should be either the System Admin ID or Admin ID that was registered as a COM+ userwhen 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 ifyou 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 packagesremotely This is also true for the application server that has SSIS installed The Planning and ConsolidationData Manager has the following custom tasks
Table 12
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008and 2012 respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and2012 respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012respectively
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 49
Name Remark
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and2012 respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008and 2012 respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL2008 and 2012 respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and2012 respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012respectively
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
ltdrivegtWebsrvrbin2 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 FilesMicrosoft SQLServer paste all files into the CProgram Files (x86)Microsoft SQL Server100DTSTasksfolder
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
50
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Typographic Conventions
Table 13
Example Description
lt gt Angle brackets indicate that you replace these words or characters with appropriate entries tomake entries in the system for example Enter your ltUser Namegt
File Save Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
Example Textual cross-references to an internet address for example wwwsapcom
example Quicklinks added to the internet address of a homepage to enable quick access to specificcontent 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 titlespushbutton 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 namesof installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transactioncodes database table names and key concepts of a programming language when they aresurrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
SAP Business Planning and Consolidation 100Typographic Conventions
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 51
52
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
wwwsapcom
Material Number
- SAP Business 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 2008 R2 2012 or 2012 R2
- 344 Removing Default Access to the Console
- 345 Management Console Access Control
- 346 Configuring Planning and Consolidation to use SSL
- 347 Using Client Certificates
- 348 Configuring MS SQL Server Reporting Services to use SSL
-
- 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
-
NoteYou cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver You must use the SQL ServerODBC driver For more information see the Microsoft Knowledge Base article 931202 The requirements for usingthe ODBC logging feature in IIS
343 Setting Up an ODBC Data Source in Windows Server2008 2008 R2 2012 or 2012 R2
Procedure
This procedure describes how to set up an ODBC data source for the Management Console in Windows Server 20082008 R2 2012 or 2012 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
NoteIf you have chosen SAP BusinessObjects User Management System in the installation screen you do not needto remove or configure access because the Management Console service always runs with the System Admin IDaccount which is a member of the Administrators group
Procedure
To remove default access to the Management Console and create a group that does have access to the console usethe procedure described below
32
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
NoteCreate your Management Console administrative group either on the server that hosts the Management Consoleor 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
NoteAlternatively you can perform analogous steps in Active Directory
3 In the Groups context menu choose New Group
4 Enter data as required Click Create
5 In the Computer Management dialog box choose Services and Applications Internet InformationServices 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 objectand all child objects Include these with entries explicitly defined here checkbox
NoteThis step is a necessary precursor to the completion of this procedure
10 In the Security dialog box click Copy to ensure that the System group retains its privileges
11 Remove access to the Management Console from all groups that should not have it
12 Choose Authentication in the center pane then disable Windows authentication
Result
Users who have not been granted access to the Management Console can still open the Management Console Webpage but it contains no data or menu options This does not affect the access that a user would otherwise have toPlanning and Consolidation
345 Management Console Access Control
After establishing the Management Console group you can add users or groups to it For more information aboutcreating this group see Removing Default Access to the Console [page 32] Their rights in Active Directory determinewhat they can access in the Console
By default any member of the Administrators Active Directory group on the application server or domain has fullaccess to all of the features of the Console except the Planning and Consolidation logging area Access to Planningand Consolidation logging is controlled within the Planning and Consolidation Administration Client task securityThe user must be granted View system logs task privileges For more information see the SAP Library Planning and
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 33
Consolidation Administrators Guide in servicesapcominstguidesepm-bpc 100 version for the Microsoftplatform
Your IT policy determines whether you grant access by group or user You may wish to create several levels of Consoleusers (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 describedin this table
Table 9
Privilege Rights Management Area
Task Manager and Kill Process Administrators group on application server or domain
Performance Monitor Counters Administrators group on application server or domain
Power Users group on application server or domain
Performance Monitor Users group on application server
Microsoft Analysis Services performance monitoring Administrators group on application server or domain
Microsoft SQL Server Monitoring (performance counters andstatistics)
Administrators group on application server or domain
346 Configuring Planning and Consolidation to use SSL
Procedure
Creating a Certificate for the Server
During the handshake phase of the SSL communication the server must send its certificate to the client The clientthen uses the certificate to encrypt information and send it back to the server
The procedure below describes how to create a self-signed certificate for the server
RecommendationWe recommend that you limit the use of self-signed certificates to testing only For a productive system you shouldobtain a certificate signed by a well-known certification authority (CA)
1 Start the Internet Information Services (IIS) Manager To do that go to Start All Programs AdministrativeTools Internet Information Services (IIS) Manager
2 In the Connections panel on the left-hand side select the server node and then choose Server Certificates
3 In the Actions panel on the right hand side choose the Create Self-Signed Certificate action
4 Enter the name that you want the certificate to be identified by for example MyTestSSLCertificate
IIS generates a new SSL certificate for you that has one yearrsquos expiry lease The certificate is issued to the local servername
Binding the Certificate to the Web Site
The procedure below describes how to bind the certificate to the web site for which SSL connections must be used
1 In the Connections panel select the web site node
2 In the Actions panel choose Bindings
34
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
3 In the Site Bindings dialog that appears choose the Add button to create a new binding
4 Configure the parameters as follows
Type = https IP Address = [1] - this is a shorthand expression for the local server name
Port = 443 - this is the default SSL port
SSL Certificate = enter your newly created certificate name
5 Choose OK to create the new binding and then close the Site Bindings dialog
6 Restart the IIS processes To do this choose Restart from the Actions panel
7 In the middle panel under the IIS section choose SSL Settings
8 In the SSL Settings screen select the Require SSL checkbox
9 In the Actions panel choose to Apply these settings
To test the SSL connection in the Actions panel choose the Browse [1] 443 (https) link
347 Using Client Certificates
To enable the use of client certificates in Planning and Consolidation you must follow several manual steps
NotePlanning and Consolidation supports client certificate authentication in Windows Authentication Mode butdoes 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 technetmicrosoftcomen-uslibrarycc753810aspx
For more information about configuring the client certificate mapping authentication see technetmicrosoftcomen-uslibrarycc732996(WS10)aspx
When you create the client certificates you can set the type of certificate in the SSL Settings screen in InternetInformation Services (IIS) Manager
Procedure
1 Set the options for client certificates
1 In the IIS Manager select the web site where you installed Planning and Consolidation
2 Choose SSL Settings
3 In the Client certificates section select the Accept client certificates option
This option allows you to use a client certificate or username and password (Basic authentication) toconnect 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 theManagementConsole home page
3 Double-click Authentication and enable Anonymous Authentication
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 35
4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way asin step 3
5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the sameway 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
348 Configuring MS SQL Server Reporting Services to useSSL
Procedure
The procedure below describes how to configure the use of SSL in Microsoft SQL Server Reporting Services
NoteReporting Services does not provide functionalities for generating requesting or installing a certificate Theserver certificates that you want to use for configuring SSL must have already been installed on your computer
1 Open the Reporting Services Configuration Manager program To do this open the Windows Start menu andnavigate to All Programs Microsoft SQL Server ltversiongt Configuration Tools Reporting ServicesConfiguration Manager
2 In the Connect panel on the left-hand side select the Web Service URL option to open all the Report Server webservice parameters
3 Configure the parameters as follows
SSL Certificate = the name of the certificate that you want to use
SSL Port = 4434 Choose Apply to confirm the changes
5 In the Connect panel choose Report Manager URL to open the list of parameters that link Reporting Servicesto IIS
6 Choose Advanced to add your new SSL web URL
7 In the section Multiple SSL Identities for Report Manager choose Add Configure the parameters as follows
IP Address = (All IPv4) SSL Port = 443 Certificate = the name of your SSL certificate
8 To test the configuration click the URL that appears under the Report manager Site Identification section
36
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
4 Installing Planning and ConsolidationAdministration Client and the SAPBusinessObjects EPM solutions Add-in forMicrosoft Office
The installation of the Planning and Consolidation Administration Client allows administrators to build and maintainPlanning and Consolidation environments and models and administer security
All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions add-in forMicrosoft 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 valueof the Planning and Consolidation client to prompt for user name and password Otherwise the Planning andConsolidation Start Page does not display
41 Installing the Administration Client
Prerequisites
NoteFor a definitive list of system requirements see the Product Availability Matrix on SAP Service Marketplace atservicesapcompam Search on Planning and Consolidation
The following list describes the minimum software requirements
Microsoft Internet Explorer 70 80 90 or 10
Microsoft Office 2003 2007 2010 or 2012
NET Framework 20 or higher (install any required NET Framework Hotfixes by referring tosupportmicrosoftcomkb)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 37
NoteWe recommend that you install all of the latest Microsoft Windows hotfixes prior to installing the Administrationclient For information about which hotfixes to install see updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us
Procedure
The 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 ltPC_serverportgtsapbpcweb
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 mustdownload the most recent version of the full setup (EPM Add-inexe) from the Service Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPCInstallation folder
Individual users can install the EPM add-in on their own machines by going to the Planning and Consolidation Homepage 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 upthe 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
38
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
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 toperform the upgrade If Client Auto Update is not enabled and a newer version is detected clients must be installedmanually 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 andpassword in the Admin ID and Admin password fields respectively The Admin ID should be a member of thelocal administrators group on all the computers running the auto update This setting is not needed if all usershave 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 Thisoption is stored in the user preferences and may also be turned on or off using the User Optionshellip menu itemIf 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 toinstall 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 installit 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 servicesapcom
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 versionand policy information For a support package these files are
EPM Addin Support Package ltSP versiongtmsp EPM Addin Support Package ltSP versiongtxmlFor a patch these files are
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 (WebsrvrWebBPCInstallation)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 39
You can set a different update policy for each package listed
ExampleThe following table illustrates some possible situations assuming that you have installed the first full version(V1)
Table 10
Available maintenancepackages
V2-user update
V3-force update
V4-force update
V5-user update
V5-user update V5-user update
V6-auto update
V7-force update
Minimum RequiredVersion
V4 V4 V7
Notification A prompt tells the user toinstall maintenancepackage V4 using theForced Update behavior
If User Update is enabledthe prompt informs theuser that maintenancepackage V5 is available
A prompt tells the user toinstall maintenancepackage V7 using theForced Update behavior
New Version V4 V4 or V5 V7
If you change the update policy for any package click Update to complete the change
40
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
5 Connection Issues
You may experience connection problems with ports the proxy server or programs and settings that interact withthese components If you have any issues related to connection review the following recommendations andtroubleshooting tips
51 Checking for Open Ports
You must ensure that all required ports are open for inboundoutbound traffic By default Planning andConsolidation requires that Ports 80 (used by http) and 1433 and 2383 (used by SQL Server 2008) are open Totest whether the required ports are open go to a command prompt and enter the Telnet serveripaddress and portFor example Telnet 431181836 80 If the system returns a blank command window the port is open If it returnsa message stating that it is unable to connect the port is not open
NoteYou can use the following site to scan for the normal ports It allows you to manually enter a port number to test
wwwmyserverorgportsniffasp
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 Planningand Consolidation server as an exception You can do this at the client level ( Internet Explorer ToolsInternet 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 fullyqualified 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 Consolidationauthentication Do not use authentication on the proxy server The system synchronizes the user name andpassword on the remote server with the local user name and password
SAP Business Planning and Consolidation 100Connection Issues
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 41
NoteFor more information about setting up an ISA proxy server contact SAP Support to request a copy of Setting upISA Proxy Server White Paper For more information about Business Planning and Consolidation firewall portssee SAP Note 1505250
Internet Explorer Settings Issues
Internet Explorer settings must be set correctly to prevent errors and problems when you attempt to access thePlanning 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 insertthe IP address or fully qualified server name of the Planning and Consolidation server as an exception bychoosing 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
42
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Connection Issues
6 Installing Planning and Consolidation withTwo Active Directory Domains
To set up a Planning and Consolidation 10 application server in a hosted environment and use your own domainusers follow this procedure In general you install Planning and Consolidation on the host domain use the hostdomain account and assign it to the Planning and Consolidation users SysAdmin Admin and Users Then you acceptone 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 andpassword 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 topromote 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 privilegefor the Planning and Consolidation server
5 Install Planning and Consolidation and assign your domain account either to the three Planning andConsolidation administrative users SysAdmin Admin and Users or to only one of the three Planning andConsolidation administrative users and to three of your users Be sure you use your own user account ratherthan host domain users
Planning and Consolidation impersonation can then access your domain from the host environment becauseit has the privilege of your domain account
SAP Business Planning and Consolidation 100Installing Planning and Consolidation with Two Active Directory Domains
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 43
7 Installing Planning and Consolidation in aTerminal Services or Citrix ServerDeployment
This section describes best practices and instructions for installing Planning and Consolidation in a Terminal Servicesor Citrix Server deployment
71 Terminal Services Home Directories
We recommend using Terminal Server home directories rather than using the userrsquos profile directory The profiledirectory downloads a minimal amount of information about the dimensions of the environment you are logging onto and may be as large as 2 MB per user The profile directory is on the system drive and has limited space Byspecifying 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 individualserver 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 clientserver (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
44
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
Procedure
The following steps outline how to install the Planning and Consolidation clients in a Terminal Services (TS) or CitrixServer deployment
1 Make sure the Terminal Services or Citrix Server machine has the system requirements installed
2 Log on to the Terminal Services or Citrix Server machine with a user ID that has the rights to install on thatserver
3 At a command prompt enter Change userinstall
4 Open a browser and connect to the URL ltPC_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_MSBPCAdminMainexe
74 Creating a Shortcut to the Launch Page
Procedure
If you use published desktops instead of published applications the Planning and Consolidation desktop file (whichis installed on the current userrsquos desktop) must be moved to the All UsersDesktop folder
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 45
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 SQLServer 2012 support the remote modification of SSIS packages Planning and Consolidation also supports theremote 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 whichyou want to modify SSIS packages
These custom tasks reference dlls that connect to the database server and perform certain validation when usersset up the parameters of each task All the custom task reference components must also be installed in the machineon which you want to modify SSIS packages
We provide a program that registers all the reference components of the custom tasks This section explains theinstallation 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 ndash This folder contains all the dlls that should be installed on the machine There are Planning andConsolidation platform components and all of the Data Manager custom task files
Config folder ndash This folder contains only one file named Filelistxml and lists all of the files that should be installedIf you need to add or remove certain components from the installation you can modify this xml file
OSoftSetupexe ndash This is the main executable file to run the installation package
NoteIf you are not installing SSIS Custom Tasks on your client machine ndash specifically a machine other than the Planningand Consolidation application server ndash you must first install OSoftSSIS2008_Client or OSoftSSIS2012_Client onthe client machine followed by the SQL Server version If you want to use SQL 2008 Tasks under the SQL 2012environment you must install OSoftSSIS2008_Client on the application server For detailed information see SAPNote 1707410 You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package byextracting OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPCInstallation folder on the Planning and Consolidation server To modify SSIS packages on the Planning andConsolidation application server you need to install OSoftSSIS2008_Client or OSoftSSIS2012_Client for creatinga COM+ application For more information see Before You Modify the SSIS Packages [page 49] and Setup ofa COM+ Application on the Application Server [page 50]
Bin folder
This folder contains the following components
46
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Table 11
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012respectively
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
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 47
Name Remark
BPCWriteBackdll
InteropDTSdll
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 addmore components to the installation package you can copy the new components into the Bin folder and add theproper xml tags in FileListxml You need to enter information for the following tags
RegistType ndash This is the registration information of the component You can enter the following values
RegAsm ndash For NET component
48
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Regsvr32 ndash For VB6 component
Gacutil ndash For NET Framework component that should be registered into Global Assembly Cache
FileName ndash Component file name
OSoftSetupexe
This is the executable file to run the SSIS installation package Double-click the file to start the installation You needto enter information for the following fields
Set SQL server
Specify the SQL server name If your SQL Server has an instance specify the instance name
NoteIf you installed the OSoftSSIS2008_Client or OSoftSSIS2012_Client on the application server the SQL servername is automatically disabled
Set server credential
This is the credential name of the COM+ package component Enter the user ID and password that can accessyour SQL Server This should be either the System Admin ID or Admin ID that was registered as a COM+ userwhen 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 ifyou 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 packagesremotely This is also true for the application server that has SSIS installed The Planning and ConsolidationData Manager has the following custom tasks
Table 12
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008and 2012 respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and2012 respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012respectively
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 49
Name Remark
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and2012 respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008and 2012 respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL2008 and 2012 respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and2012 respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012respectively
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
ltdrivegtWebsrvrbin2 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 FilesMicrosoft SQLServer paste all files into the CProgram Files (x86)Microsoft SQL Server100DTSTasksfolder
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
50
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Typographic Conventions
Table 13
Example Description
lt gt Angle brackets indicate that you replace these words or characters with appropriate entries tomake entries in the system for example Enter your ltUser Namegt
File Save Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
Example Textual cross-references to an internet address for example wwwsapcom
example Quicklinks added to the internet address of a homepage to enable quick access to specificcontent 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 titlespushbutton 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 namesof installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transactioncodes database table names and key concepts of a programming language when they aresurrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
SAP Business Planning and Consolidation 100Typographic Conventions
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 51
52
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
wwwsapcom
Material Number
- SAP Business 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 2008 R2 2012 or 2012 R2
- 344 Removing Default Access to the Console
- 345 Management Console Access Control
- 346 Configuring Planning and Consolidation to use SSL
- 347 Using Client Certificates
- 348 Configuring MS SQL Server Reporting Services to use SSL
-
- 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
-
NoteCreate your Management Console administrative group either on the server that hosts the Management Consoleor 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
NoteAlternatively you can perform analogous steps in Active Directory
3 In the Groups context menu choose New Group
4 Enter data as required Click Create
5 In the Computer Management dialog box choose Services and Applications Internet InformationServices 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 objectand all child objects Include these with entries explicitly defined here checkbox
NoteThis step is a necessary precursor to the completion of this procedure
10 In the Security dialog box click Copy to ensure that the System group retains its privileges
11 Remove access to the Management Console from all groups that should not have it
12 Choose Authentication in the center pane then disable Windows authentication
Result
Users who have not been granted access to the Management Console can still open the Management Console Webpage but it contains no data or menu options This does not affect the access that a user would otherwise have toPlanning and Consolidation
345 Management Console Access Control
After establishing the Management Console group you can add users or groups to it For more information aboutcreating this group see Removing Default Access to the Console [page 32] Their rights in Active Directory determinewhat they can access in the Console
By default any member of the Administrators Active Directory group on the application server or domain has fullaccess to all of the features of the Console except the Planning and Consolidation logging area Access to Planningand Consolidation logging is controlled within the Planning and Consolidation Administration Client task securityThe user must be granted View system logs task privileges For more information see the SAP Library Planning and
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 33
Consolidation Administrators Guide in servicesapcominstguidesepm-bpc 100 version for the Microsoftplatform
Your IT policy determines whether you grant access by group or user You may wish to create several levels of Consoleusers (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 describedin this table
Table 9
Privilege Rights Management Area
Task Manager and Kill Process Administrators group on application server or domain
Performance Monitor Counters Administrators group on application server or domain
Power Users group on application server or domain
Performance Monitor Users group on application server
Microsoft Analysis Services performance monitoring Administrators group on application server or domain
Microsoft SQL Server Monitoring (performance counters andstatistics)
Administrators group on application server or domain
346 Configuring Planning and Consolidation to use SSL
Procedure
Creating a Certificate for the Server
During the handshake phase of the SSL communication the server must send its certificate to the client The clientthen uses the certificate to encrypt information and send it back to the server
The procedure below describes how to create a self-signed certificate for the server
RecommendationWe recommend that you limit the use of self-signed certificates to testing only For a productive system you shouldobtain a certificate signed by a well-known certification authority (CA)
1 Start the Internet Information Services (IIS) Manager To do that go to Start All Programs AdministrativeTools Internet Information Services (IIS) Manager
2 In the Connections panel on the left-hand side select the server node and then choose Server Certificates
3 In the Actions panel on the right hand side choose the Create Self-Signed Certificate action
4 Enter the name that you want the certificate to be identified by for example MyTestSSLCertificate
IIS generates a new SSL certificate for you that has one yearrsquos expiry lease The certificate is issued to the local servername
Binding the Certificate to the Web Site
The procedure below describes how to bind the certificate to the web site for which SSL connections must be used
1 In the Connections panel select the web site node
2 In the Actions panel choose Bindings
34
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
3 In the Site Bindings dialog that appears choose the Add button to create a new binding
4 Configure the parameters as follows
Type = https IP Address = [1] - this is a shorthand expression for the local server name
Port = 443 - this is the default SSL port
SSL Certificate = enter your newly created certificate name
5 Choose OK to create the new binding and then close the Site Bindings dialog
6 Restart the IIS processes To do this choose Restart from the Actions panel
7 In the middle panel under the IIS section choose SSL Settings
8 In the SSL Settings screen select the Require SSL checkbox
9 In the Actions panel choose to Apply these settings
To test the SSL connection in the Actions panel choose the Browse [1] 443 (https) link
347 Using Client Certificates
To enable the use of client certificates in Planning and Consolidation you must follow several manual steps
NotePlanning and Consolidation supports client certificate authentication in Windows Authentication Mode butdoes 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 technetmicrosoftcomen-uslibrarycc753810aspx
For more information about configuring the client certificate mapping authentication see technetmicrosoftcomen-uslibrarycc732996(WS10)aspx
When you create the client certificates you can set the type of certificate in the SSL Settings screen in InternetInformation Services (IIS) Manager
Procedure
1 Set the options for client certificates
1 In the IIS Manager select the web site where you installed Planning and Consolidation
2 Choose SSL Settings
3 In the Client certificates section select the Accept client certificates option
This option allows you to use a client certificate or username and password (Basic authentication) toconnect 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 theManagementConsole home page
3 Double-click Authentication and enable Anonymous Authentication
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 35
4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way asin step 3
5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the sameway 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
348 Configuring MS SQL Server Reporting Services to useSSL
Procedure
The procedure below describes how to configure the use of SSL in Microsoft SQL Server Reporting Services
NoteReporting Services does not provide functionalities for generating requesting or installing a certificate Theserver certificates that you want to use for configuring SSL must have already been installed on your computer
1 Open the Reporting Services Configuration Manager program To do this open the Windows Start menu andnavigate to All Programs Microsoft SQL Server ltversiongt Configuration Tools Reporting ServicesConfiguration Manager
2 In the Connect panel on the left-hand side select the Web Service URL option to open all the Report Server webservice parameters
3 Configure the parameters as follows
SSL Certificate = the name of the certificate that you want to use
SSL Port = 4434 Choose Apply to confirm the changes
5 In the Connect panel choose Report Manager URL to open the list of parameters that link Reporting Servicesto IIS
6 Choose Advanced to add your new SSL web URL
7 In the section Multiple SSL Identities for Report Manager choose Add Configure the parameters as follows
IP Address = (All IPv4) SSL Port = 443 Certificate = the name of your SSL certificate
8 To test the configuration click the URL that appears under the Report manager Site Identification section
36
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
4 Installing Planning and ConsolidationAdministration Client and the SAPBusinessObjects EPM solutions Add-in forMicrosoft Office
The installation of the Planning and Consolidation Administration Client allows administrators to build and maintainPlanning and Consolidation environments and models and administer security
All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions add-in forMicrosoft 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 valueof the Planning and Consolidation client to prompt for user name and password Otherwise the Planning andConsolidation Start Page does not display
41 Installing the Administration Client
Prerequisites
NoteFor a definitive list of system requirements see the Product Availability Matrix on SAP Service Marketplace atservicesapcompam Search on Planning and Consolidation
The following list describes the minimum software requirements
Microsoft Internet Explorer 70 80 90 or 10
Microsoft Office 2003 2007 2010 or 2012
NET Framework 20 or higher (install any required NET Framework Hotfixes by referring tosupportmicrosoftcomkb)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 37
NoteWe recommend that you install all of the latest Microsoft Windows hotfixes prior to installing the Administrationclient For information about which hotfixes to install see updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us
Procedure
The 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 ltPC_serverportgtsapbpcweb
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 mustdownload the most recent version of the full setup (EPM Add-inexe) from the Service Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPCInstallation folder
Individual users can install the EPM add-in on their own machines by going to the Planning and Consolidation Homepage 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 upthe 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
38
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
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 toperform the upgrade If Client Auto Update is not enabled and a newer version is detected clients must be installedmanually 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 andpassword in the Admin ID and Admin password fields respectively The Admin ID should be a member of thelocal administrators group on all the computers running the auto update This setting is not needed if all usershave 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 Thisoption is stored in the user preferences and may also be turned on or off using the User Optionshellip menu itemIf 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 toinstall 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 installit 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 servicesapcom
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 versionand policy information For a support package these files are
EPM Addin Support Package ltSP versiongtmsp EPM Addin Support Package ltSP versiongtxmlFor a patch these files are
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 (WebsrvrWebBPCInstallation)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 39
You can set a different update policy for each package listed
ExampleThe following table illustrates some possible situations assuming that you have installed the first full version(V1)
Table 10
Available maintenancepackages
V2-user update
V3-force update
V4-force update
V5-user update
V5-user update V5-user update
V6-auto update
V7-force update
Minimum RequiredVersion
V4 V4 V7
Notification A prompt tells the user toinstall maintenancepackage V4 using theForced Update behavior
If User Update is enabledthe prompt informs theuser that maintenancepackage V5 is available
A prompt tells the user toinstall maintenancepackage V7 using theForced Update behavior
New Version V4 V4 or V5 V7
If you change the update policy for any package click Update to complete the change
40
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
5 Connection Issues
You may experience connection problems with ports the proxy server or programs and settings that interact withthese components If you have any issues related to connection review the following recommendations andtroubleshooting tips
51 Checking for Open Ports
You must ensure that all required ports are open for inboundoutbound traffic By default Planning andConsolidation requires that Ports 80 (used by http) and 1433 and 2383 (used by SQL Server 2008) are open Totest whether the required ports are open go to a command prompt and enter the Telnet serveripaddress and portFor example Telnet 431181836 80 If the system returns a blank command window the port is open If it returnsa message stating that it is unable to connect the port is not open
NoteYou can use the following site to scan for the normal ports It allows you to manually enter a port number to test
wwwmyserverorgportsniffasp
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 Planningand Consolidation server as an exception You can do this at the client level ( Internet Explorer ToolsInternet 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 fullyqualified 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 Consolidationauthentication Do not use authentication on the proxy server The system synchronizes the user name andpassword on the remote server with the local user name and password
SAP Business Planning and Consolidation 100Connection Issues
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 41
NoteFor more information about setting up an ISA proxy server contact SAP Support to request a copy of Setting upISA Proxy Server White Paper For more information about Business Planning and Consolidation firewall portssee SAP Note 1505250
Internet Explorer Settings Issues
Internet Explorer settings must be set correctly to prevent errors and problems when you attempt to access thePlanning 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 insertthe IP address or fully qualified server name of the Planning and Consolidation server as an exception bychoosing 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
42
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Connection Issues
6 Installing Planning and Consolidation withTwo Active Directory Domains
To set up a Planning and Consolidation 10 application server in a hosted environment and use your own domainusers follow this procedure In general you install Planning and Consolidation on the host domain use the hostdomain account and assign it to the Planning and Consolidation users SysAdmin Admin and Users Then you acceptone 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 andpassword 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 topromote 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 privilegefor the Planning and Consolidation server
5 Install Planning and Consolidation and assign your domain account either to the three Planning andConsolidation administrative users SysAdmin Admin and Users or to only one of the three Planning andConsolidation administrative users and to three of your users Be sure you use your own user account ratherthan host domain users
Planning and Consolidation impersonation can then access your domain from the host environment becauseit has the privilege of your domain account
SAP Business Planning and Consolidation 100Installing Planning and Consolidation with Two Active Directory Domains
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 43
7 Installing Planning and Consolidation in aTerminal Services or Citrix ServerDeployment
This section describes best practices and instructions for installing Planning and Consolidation in a Terminal Servicesor Citrix Server deployment
71 Terminal Services Home Directories
We recommend using Terminal Server home directories rather than using the userrsquos profile directory The profiledirectory downloads a minimal amount of information about the dimensions of the environment you are logging onto and may be as large as 2 MB per user The profile directory is on the system drive and has limited space Byspecifying 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 individualserver 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 clientserver (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
44
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
Procedure
The following steps outline how to install the Planning and Consolidation clients in a Terminal Services (TS) or CitrixServer deployment
1 Make sure the Terminal Services or Citrix Server machine has the system requirements installed
2 Log on to the Terminal Services or Citrix Server machine with a user ID that has the rights to install on thatserver
3 At a command prompt enter Change userinstall
4 Open a browser and connect to the URL ltPC_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_MSBPCAdminMainexe
74 Creating a Shortcut to the Launch Page
Procedure
If you use published desktops instead of published applications the Planning and Consolidation desktop file (whichis installed on the current userrsquos desktop) must be moved to the All UsersDesktop folder
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 45
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 SQLServer 2012 support the remote modification of SSIS packages Planning and Consolidation also supports theremote 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 whichyou want to modify SSIS packages
These custom tasks reference dlls that connect to the database server and perform certain validation when usersset up the parameters of each task All the custom task reference components must also be installed in the machineon which you want to modify SSIS packages
We provide a program that registers all the reference components of the custom tasks This section explains theinstallation 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 ndash This folder contains all the dlls that should be installed on the machine There are Planning andConsolidation platform components and all of the Data Manager custom task files
Config folder ndash This folder contains only one file named Filelistxml and lists all of the files that should be installedIf you need to add or remove certain components from the installation you can modify this xml file
OSoftSetupexe ndash This is the main executable file to run the installation package
NoteIf you are not installing SSIS Custom Tasks on your client machine ndash specifically a machine other than the Planningand Consolidation application server ndash you must first install OSoftSSIS2008_Client or OSoftSSIS2012_Client onthe client machine followed by the SQL Server version If you want to use SQL 2008 Tasks under the SQL 2012environment you must install OSoftSSIS2008_Client on the application server For detailed information see SAPNote 1707410 You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package byextracting OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPCInstallation folder on the Planning and Consolidation server To modify SSIS packages on the Planning andConsolidation application server you need to install OSoftSSIS2008_Client or OSoftSSIS2012_Client for creatinga COM+ application For more information see Before You Modify the SSIS Packages [page 49] and Setup ofa COM+ Application on the Application Server [page 50]
Bin folder
This folder contains the following components
46
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Table 11
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012respectively
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
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 47
Name Remark
BPCWriteBackdll
InteropDTSdll
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 addmore components to the installation package you can copy the new components into the Bin folder and add theproper xml tags in FileListxml You need to enter information for the following tags
RegistType ndash This is the registration information of the component You can enter the following values
RegAsm ndash For NET component
48
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Regsvr32 ndash For VB6 component
Gacutil ndash For NET Framework component that should be registered into Global Assembly Cache
FileName ndash Component file name
OSoftSetupexe
This is the executable file to run the SSIS installation package Double-click the file to start the installation You needto enter information for the following fields
Set SQL server
Specify the SQL server name If your SQL Server has an instance specify the instance name
NoteIf you installed the OSoftSSIS2008_Client or OSoftSSIS2012_Client on the application server the SQL servername is automatically disabled
Set server credential
This is the credential name of the COM+ package component Enter the user ID and password that can accessyour SQL Server This should be either the System Admin ID or Admin ID that was registered as a COM+ userwhen 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 ifyou 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 packagesremotely This is also true for the application server that has SSIS installed The Planning and ConsolidationData Manager has the following custom tasks
Table 12
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008and 2012 respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and2012 respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012respectively
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 49
Name Remark
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and2012 respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008and 2012 respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL2008 and 2012 respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and2012 respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012respectively
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
ltdrivegtWebsrvrbin2 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 FilesMicrosoft SQLServer paste all files into the CProgram Files (x86)Microsoft SQL Server100DTSTasksfolder
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
50
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Typographic Conventions
Table 13
Example Description
lt gt Angle brackets indicate that you replace these words or characters with appropriate entries tomake entries in the system for example Enter your ltUser Namegt
File Save Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
Example Textual cross-references to an internet address for example wwwsapcom
example Quicklinks added to the internet address of a homepage to enable quick access to specificcontent 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 titlespushbutton 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 namesof installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transactioncodes database table names and key concepts of a programming language when they aresurrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
SAP Business Planning and Consolidation 100Typographic Conventions
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 51
52
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
wwwsapcom
Material Number
- SAP Business 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 2008 R2 2012 or 2012 R2
- 344 Removing Default Access to the Console
- 345 Management Console Access Control
- 346 Configuring Planning and Consolidation to use SSL
- 347 Using Client Certificates
- 348 Configuring MS SQL Server Reporting Services to use SSL
-
- 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
-
Consolidation Administrators Guide in servicesapcominstguidesepm-bpc 100 version for the Microsoftplatform
Your IT policy determines whether you grant access by group or user You may wish to create several levels of Consoleusers (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 describedin this table
Table 9
Privilege Rights Management Area
Task Manager and Kill Process Administrators group on application server or domain
Performance Monitor Counters Administrators group on application server or domain
Power Users group on application server or domain
Performance Monitor Users group on application server
Microsoft Analysis Services performance monitoring Administrators group on application server or domain
Microsoft SQL Server Monitoring (performance counters andstatistics)
Administrators group on application server or domain
346 Configuring Planning and Consolidation to use SSL
Procedure
Creating a Certificate for the Server
During the handshake phase of the SSL communication the server must send its certificate to the client The clientthen uses the certificate to encrypt information and send it back to the server
The procedure below describes how to create a self-signed certificate for the server
RecommendationWe recommend that you limit the use of self-signed certificates to testing only For a productive system you shouldobtain a certificate signed by a well-known certification authority (CA)
1 Start the Internet Information Services (IIS) Manager To do that go to Start All Programs AdministrativeTools Internet Information Services (IIS) Manager
2 In the Connections panel on the left-hand side select the server node and then choose Server Certificates
3 In the Actions panel on the right hand side choose the Create Self-Signed Certificate action
4 Enter the name that you want the certificate to be identified by for example MyTestSSLCertificate
IIS generates a new SSL certificate for you that has one yearrsquos expiry lease The certificate is issued to the local servername
Binding the Certificate to the Web Site
The procedure below describes how to bind the certificate to the web site for which SSL connections must be used
1 In the Connections panel select the web site node
2 In the Actions panel choose Bindings
34
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
3 In the Site Bindings dialog that appears choose the Add button to create a new binding
4 Configure the parameters as follows
Type = https IP Address = [1] - this is a shorthand expression for the local server name
Port = 443 - this is the default SSL port
SSL Certificate = enter your newly created certificate name
5 Choose OK to create the new binding and then close the Site Bindings dialog
6 Restart the IIS processes To do this choose Restart from the Actions panel
7 In the middle panel under the IIS section choose SSL Settings
8 In the SSL Settings screen select the Require SSL checkbox
9 In the Actions panel choose to Apply these settings
To test the SSL connection in the Actions panel choose the Browse [1] 443 (https) link
347 Using Client Certificates
To enable the use of client certificates in Planning and Consolidation you must follow several manual steps
NotePlanning and Consolidation supports client certificate authentication in Windows Authentication Mode butdoes 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 technetmicrosoftcomen-uslibrarycc753810aspx
For more information about configuring the client certificate mapping authentication see technetmicrosoftcomen-uslibrarycc732996(WS10)aspx
When you create the client certificates you can set the type of certificate in the SSL Settings screen in InternetInformation Services (IIS) Manager
Procedure
1 Set the options for client certificates
1 In the IIS Manager select the web site where you installed Planning and Consolidation
2 Choose SSL Settings
3 In the Client certificates section select the Accept client certificates option
This option allows you to use a client certificate or username and password (Basic authentication) toconnect 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 theManagementConsole home page
3 Double-click Authentication and enable Anonymous Authentication
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 35
4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way asin step 3
5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the sameway 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
348 Configuring MS SQL Server Reporting Services to useSSL
Procedure
The procedure below describes how to configure the use of SSL in Microsoft SQL Server Reporting Services
NoteReporting Services does not provide functionalities for generating requesting or installing a certificate Theserver certificates that you want to use for configuring SSL must have already been installed on your computer
1 Open the Reporting Services Configuration Manager program To do this open the Windows Start menu andnavigate to All Programs Microsoft SQL Server ltversiongt Configuration Tools Reporting ServicesConfiguration Manager
2 In the Connect panel on the left-hand side select the Web Service URL option to open all the Report Server webservice parameters
3 Configure the parameters as follows
SSL Certificate = the name of the certificate that you want to use
SSL Port = 4434 Choose Apply to confirm the changes
5 In the Connect panel choose Report Manager URL to open the list of parameters that link Reporting Servicesto IIS
6 Choose Advanced to add your new SSL web URL
7 In the section Multiple SSL Identities for Report Manager choose Add Configure the parameters as follows
IP Address = (All IPv4) SSL Port = 443 Certificate = the name of your SSL certificate
8 To test the configuration click the URL that appears under the Report manager Site Identification section
36
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
4 Installing Planning and ConsolidationAdministration Client and the SAPBusinessObjects EPM solutions Add-in forMicrosoft Office
The installation of the Planning and Consolidation Administration Client allows administrators to build and maintainPlanning and Consolidation environments and models and administer security
All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions add-in forMicrosoft 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 valueof the Planning and Consolidation client to prompt for user name and password Otherwise the Planning andConsolidation Start Page does not display
41 Installing the Administration Client
Prerequisites
NoteFor a definitive list of system requirements see the Product Availability Matrix on SAP Service Marketplace atservicesapcompam Search on Planning and Consolidation
The following list describes the minimum software requirements
Microsoft Internet Explorer 70 80 90 or 10
Microsoft Office 2003 2007 2010 or 2012
NET Framework 20 or higher (install any required NET Framework Hotfixes by referring tosupportmicrosoftcomkb)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 37
NoteWe recommend that you install all of the latest Microsoft Windows hotfixes prior to installing the Administrationclient For information about which hotfixes to install see updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us
Procedure
The 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 ltPC_serverportgtsapbpcweb
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 mustdownload the most recent version of the full setup (EPM Add-inexe) from the Service Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPCInstallation folder
Individual users can install the EPM add-in on their own machines by going to the Planning and Consolidation Homepage 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 upthe 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
38
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
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 toperform the upgrade If Client Auto Update is not enabled and a newer version is detected clients must be installedmanually 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 andpassword in the Admin ID and Admin password fields respectively The Admin ID should be a member of thelocal administrators group on all the computers running the auto update This setting is not needed if all usershave 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 Thisoption is stored in the user preferences and may also be turned on or off using the User Optionshellip menu itemIf 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 toinstall 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 installit 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 servicesapcom
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 versionand policy information For a support package these files are
EPM Addin Support Package ltSP versiongtmsp EPM Addin Support Package ltSP versiongtxmlFor a patch these files are
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 (WebsrvrWebBPCInstallation)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 39
You can set a different update policy for each package listed
ExampleThe following table illustrates some possible situations assuming that you have installed the first full version(V1)
Table 10
Available maintenancepackages
V2-user update
V3-force update
V4-force update
V5-user update
V5-user update V5-user update
V6-auto update
V7-force update
Minimum RequiredVersion
V4 V4 V7
Notification A prompt tells the user toinstall maintenancepackage V4 using theForced Update behavior
If User Update is enabledthe prompt informs theuser that maintenancepackage V5 is available
A prompt tells the user toinstall maintenancepackage V7 using theForced Update behavior
New Version V4 V4 or V5 V7
If you change the update policy for any package click Update to complete the change
40
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
5 Connection Issues
You may experience connection problems with ports the proxy server or programs and settings that interact withthese components If you have any issues related to connection review the following recommendations andtroubleshooting tips
51 Checking for Open Ports
You must ensure that all required ports are open for inboundoutbound traffic By default Planning andConsolidation requires that Ports 80 (used by http) and 1433 and 2383 (used by SQL Server 2008) are open Totest whether the required ports are open go to a command prompt and enter the Telnet serveripaddress and portFor example Telnet 431181836 80 If the system returns a blank command window the port is open If it returnsa message stating that it is unable to connect the port is not open
NoteYou can use the following site to scan for the normal ports It allows you to manually enter a port number to test
wwwmyserverorgportsniffasp
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 Planningand Consolidation server as an exception You can do this at the client level ( Internet Explorer ToolsInternet 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 fullyqualified 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 Consolidationauthentication Do not use authentication on the proxy server The system synchronizes the user name andpassword on the remote server with the local user name and password
SAP Business Planning and Consolidation 100Connection Issues
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 41
NoteFor more information about setting up an ISA proxy server contact SAP Support to request a copy of Setting upISA Proxy Server White Paper For more information about Business Planning and Consolidation firewall portssee SAP Note 1505250
Internet Explorer Settings Issues
Internet Explorer settings must be set correctly to prevent errors and problems when you attempt to access thePlanning 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 insertthe IP address or fully qualified server name of the Planning and Consolidation server as an exception bychoosing 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
42
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Connection Issues
6 Installing Planning and Consolidation withTwo Active Directory Domains
To set up a Planning and Consolidation 10 application server in a hosted environment and use your own domainusers follow this procedure In general you install Planning and Consolidation on the host domain use the hostdomain account and assign it to the Planning and Consolidation users SysAdmin Admin and Users Then you acceptone 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 andpassword 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 topromote 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 privilegefor the Planning and Consolidation server
5 Install Planning and Consolidation and assign your domain account either to the three Planning andConsolidation administrative users SysAdmin Admin and Users or to only one of the three Planning andConsolidation administrative users and to three of your users Be sure you use your own user account ratherthan host domain users
Planning and Consolidation impersonation can then access your domain from the host environment becauseit has the privilege of your domain account
SAP Business Planning and Consolidation 100Installing Planning and Consolidation with Two Active Directory Domains
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 43
7 Installing Planning and Consolidation in aTerminal Services or Citrix ServerDeployment
This section describes best practices and instructions for installing Planning and Consolidation in a Terminal Servicesor Citrix Server deployment
71 Terminal Services Home Directories
We recommend using Terminal Server home directories rather than using the userrsquos profile directory The profiledirectory downloads a minimal amount of information about the dimensions of the environment you are logging onto and may be as large as 2 MB per user The profile directory is on the system drive and has limited space Byspecifying 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 individualserver 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 clientserver (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
44
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
Procedure
The following steps outline how to install the Planning and Consolidation clients in a Terminal Services (TS) or CitrixServer deployment
1 Make sure the Terminal Services or Citrix Server machine has the system requirements installed
2 Log on to the Terminal Services or Citrix Server machine with a user ID that has the rights to install on thatserver
3 At a command prompt enter Change userinstall
4 Open a browser and connect to the URL ltPC_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_MSBPCAdminMainexe
74 Creating a Shortcut to the Launch Page
Procedure
If you use published desktops instead of published applications the Planning and Consolidation desktop file (whichis installed on the current userrsquos desktop) must be moved to the All UsersDesktop folder
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 45
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 SQLServer 2012 support the remote modification of SSIS packages Planning and Consolidation also supports theremote 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 whichyou want to modify SSIS packages
These custom tasks reference dlls that connect to the database server and perform certain validation when usersset up the parameters of each task All the custom task reference components must also be installed in the machineon which you want to modify SSIS packages
We provide a program that registers all the reference components of the custom tasks This section explains theinstallation 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 ndash This folder contains all the dlls that should be installed on the machine There are Planning andConsolidation platform components and all of the Data Manager custom task files
Config folder ndash This folder contains only one file named Filelistxml and lists all of the files that should be installedIf you need to add or remove certain components from the installation you can modify this xml file
OSoftSetupexe ndash This is the main executable file to run the installation package
NoteIf you are not installing SSIS Custom Tasks on your client machine ndash specifically a machine other than the Planningand Consolidation application server ndash you must first install OSoftSSIS2008_Client or OSoftSSIS2012_Client onthe client machine followed by the SQL Server version If you want to use SQL 2008 Tasks under the SQL 2012environment you must install OSoftSSIS2008_Client on the application server For detailed information see SAPNote 1707410 You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package byextracting OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPCInstallation folder on the Planning and Consolidation server To modify SSIS packages on the Planning andConsolidation application server you need to install OSoftSSIS2008_Client or OSoftSSIS2012_Client for creatinga COM+ application For more information see Before You Modify the SSIS Packages [page 49] and Setup ofa COM+ Application on the Application Server [page 50]
Bin folder
This folder contains the following components
46
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Table 11
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012respectively
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
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 47
Name Remark
BPCWriteBackdll
InteropDTSdll
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 addmore components to the installation package you can copy the new components into the Bin folder and add theproper xml tags in FileListxml You need to enter information for the following tags
RegistType ndash This is the registration information of the component You can enter the following values
RegAsm ndash For NET component
48
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Regsvr32 ndash For VB6 component
Gacutil ndash For NET Framework component that should be registered into Global Assembly Cache
FileName ndash Component file name
OSoftSetupexe
This is the executable file to run the SSIS installation package Double-click the file to start the installation You needto enter information for the following fields
Set SQL server
Specify the SQL server name If your SQL Server has an instance specify the instance name
NoteIf you installed the OSoftSSIS2008_Client or OSoftSSIS2012_Client on the application server the SQL servername is automatically disabled
Set server credential
This is the credential name of the COM+ package component Enter the user ID and password that can accessyour SQL Server This should be either the System Admin ID or Admin ID that was registered as a COM+ userwhen 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 ifyou 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 packagesremotely This is also true for the application server that has SSIS installed The Planning and ConsolidationData Manager has the following custom tasks
Table 12
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008and 2012 respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and2012 respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012respectively
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 49
Name Remark
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and2012 respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008and 2012 respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL2008 and 2012 respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and2012 respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012respectively
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
ltdrivegtWebsrvrbin2 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 FilesMicrosoft SQLServer paste all files into the CProgram Files (x86)Microsoft SQL Server100DTSTasksfolder
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
50
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Typographic Conventions
Table 13
Example Description
lt gt Angle brackets indicate that you replace these words or characters with appropriate entries tomake entries in the system for example Enter your ltUser Namegt
File Save Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
Example Textual cross-references to an internet address for example wwwsapcom
example Quicklinks added to the internet address of a homepage to enable quick access to specificcontent 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 titlespushbutton 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 namesof installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transactioncodes database table names and key concepts of a programming language when they aresurrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
SAP Business Planning and Consolidation 100Typographic Conventions
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 51
52
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
wwwsapcom
Material Number
- SAP Business 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 2008 R2 2012 or 2012 R2
- 344 Removing Default Access to the Console
- 345 Management Console Access Control
- 346 Configuring Planning and Consolidation to use SSL
- 347 Using Client Certificates
- 348 Configuring MS SQL Server Reporting Services to use SSL
-
- 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
-
3 In the Site Bindings dialog that appears choose the Add button to create a new binding
4 Configure the parameters as follows
Type = https IP Address = [1] - this is a shorthand expression for the local server name
Port = 443 - this is the default SSL port
SSL Certificate = enter your newly created certificate name
5 Choose OK to create the new binding and then close the Site Bindings dialog
6 Restart the IIS processes To do this choose Restart from the Actions panel
7 In the middle panel under the IIS section choose SSL Settings
8 In the SSL Settings screen select the Require SSL checkbox
9 In the Actions panel choose to Apply these settings
To test the SSL connection in the Actions panel choose the Browse [1] 443 (https) link
347 Using Client Certificates
To enable the use of client certificates in Planning and Consolidation you must follow several manual steps
NotePlanning and Consolidation supports client certificate authentication in Windows Authentication Mode butdoes 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 technetmicrosoftcomen-uslibrarycc753810aspx
For more information about configuring the client certificate mapping authentication see technetmicrosoftcomen-uslibrarycc732996(WS10)aspx
When you create the client certificates you can set the type of certificate in the SSL Settings screen in InternetInformation Services (IIS) Manager
Procedure
1 Set the options for client certificates
1 In the IIS Manager select the web site where you installed Planning and Consolidation
2 Choose SSL Settings
3 In the Client certificates section select the Accept client certificates option
This option allows you to use a client certificate or username and password (Basic authentication) toconnect 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 theManagementConsole home page
3 Double-click Authentication and enable Anonymous Authentication
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 35
4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way asin step 3
5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the sameway 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
348 Configuring MS SQL Server Reporting Services to useSSL
Procedure
The procedure below describes how to configure the use of SSL in Microsoft SQL Server Reporting Services
NoteReporting Services does not provide functionalities for generating requesting or installing a certificate Theserver certificates that you want to use for configuring SSL must have already been installed on your computer
1 Open the Reporting Services Configuration Manager program To do this open the Windows Start menu andnavigate to All Programs Microsoft SQL Server ltversiongt Configuration Tools Reporting ServicesConfiguration Manager
2 In the Connect panel on the left-hand side select the Web Service URL option to open all the Report Server webservice parameters
3 Configure the parameters as follows
SSL Certificate = the name of the certificate that you want to use
SSL Port = 4434 Choose Apply to confirm the changes
5 In the Connect panel choose Report Manager URL to open the list of parameters that link Reporting Servicesto IIS
6 Choose Advanced to add your new SSL web URL
7 In the section Multiple SSL Identities for Report Manager choose Add Configure the parameters as follows
IP Address = (All IPv4) SSL Port = 443 Certificate = the name of your SSL certificate
8 To test the configuration click the URL that appears under the Report manager Site Identification section
36
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
4 Installing Planning and ConsolidationAdministration Client and the SAPBusinessObjects EPM solutions Add-in forMicrosoft Office
The installation of the Planning and Consolidation Administration Client allows administrators to build and maintainPlanning and Consolidation environments and models and administer security
All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions add-in forMicrosoft 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 valueof the Planning and Consolidation client to prompt for user name and password Otherwise the Planning andConsolidation Start Page does not display
41 Installing the Administration Client
Prerequisites
NoteFor a definitive list of system requirements see the Product Availability Matrix on SAP Service Marketplace atservicesapcompam Search on Planning and Consolidation
The following list describes the minimum software requirements
Microsoft Internet Explorer 70 80 90 or 10
Microsoft Office 2003 2007 2010 or 2012
NET Framework 20 or higher (install any required NET Framework Hotfixes by referring tosupportmicrosoftcomkb)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 37
NoteWe recommend that you install all of the latest Microsoft Windows hotfixes prior to installing the Administrationclient For information about which hotfixes to install see updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us
Procedure
The 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 ltPC_serverportgtsapbpcweb
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 mustdownload the most recent version of the full setup (EPM Add-inexe) from the Service Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPCInstallation folder
Individual users can install the EPM add-in on their own machines by going to the Planning and Consolidation Homepage 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 upthe 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
38
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
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 toperform the upgrade If Client Auto Update is not enabled and a newer version is detected clients must be installedmanually 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 andpassword in the Admin ID and Admin password fields respectively The Admin ID should be a member of thelocal administrators group on all the computers running the auto update This setting is not needed if all usershave 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 Thisoption is stored in the user preferences and may also be turned on or off using the User Optionshellip menu itemIf 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 toinstall 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 installit 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 servicesapcom
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 versionand policy information For a support package these files are
EPM Addin Support Package ltSP versiongtmsp EPM Addin Support Package ltSP versiongtxmlFor a patch these files are
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 (WebsrvrWebBPCInstallation)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 39
You can set a different update policy for each package listed
ExampleThe following table illustrates some possible situations assuming that you have installed the first full version(V1)
Table 10
Available maintenancepackages
V2-user update
V3-force update
V4-force update
V5-user update
V5-user update V5-user update
V6-auto update
V7-force update
Minimum RequiredVersion
V4 V4 V7
Notification A prompt tells the user toinstall maintenancepackage V4 using theForced Update behavior
If User Update is enabledthe prompt informs theuser that maintenancepackage V5 is available
A prompt tells the user toinstall maintenancepackage V7 using theForced Update behavior
New Version V4 V4 or V5 V7
If you change the update policy for any package click Update to complete the change
40
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
5 Connection Issues
You may experience connection problems with ports the proxy server or programs and settings that interact withthese components If you have any issues related to connection review the following recommendations andtroubleshooting tips
51 Checking for Open Ports
You must ensure that all required ports are open for inboundoutbound traffic By default Planning andConsolidation requires that Ports 80 (used by http) and 1433 and 2383 (used by SQL Server 2008) are open Totest whether the required ports are open go to a command prompt and enter the Telnet serveripaddress and portFor example Telnet 431181836 80 If the system returns a blank command window the port is open If it returnsa message stating that it is unable to connect the port is not open
NoteYou can use the following site to scan for the normal ports It allows you to manually enter a port number to test
wwwmyserverorgportsniffasp
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 Planningand Consolidation server as an exception You can do this at the client level ( Internet Explorer ToolsInternet 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 fullyqualified 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 Consolidationauthentication Do not use authentication on the proxy server The system synchronizes the user name andpassword on the remote server with the local user name and password
SAP Business Planning and Consolidation 100Connection Issues
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 41
NoteFor more information about setting up an ISA proxy server contact SAP Support to request a copy of Setting upISA Proxy Server White Paper For more information about Business Planning and Consolidation firewall portssee SAP Note 1505250
Internet Explorer Settings Issues
Internet Explorer settings must be set correctly to prevent errors and problems when you attempt to access thePlanning 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 insertthe IP address or fully qualified server name of the Planning and Consolidation server as an exception bychoosing 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
42
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Connection Issues
6 Installing Planning and Consolidation withTwo Active Directory Domains
To set up a Planning and Consolidation 10 application server in a hosted environment and use your own domainusers follow this procedure In general you install Planning and Consolidation on the host domain use the hostdomain account and assign it to the Planning and Consolidation users SysAdmin Admin and Users Then you acceptone 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 andpassword 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 topromote 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 privilegefor the Planning and Consolidation server
5 Install Planning and Consolidation and assign your domain account either to the three Planning andConsolidation administrative users SysAdmin Admin and Users or to only one of the three Planning andConsolidation administrative users and to three of your users Be sure you use your own user account ratherthan host domain users
Planning and Consolidation impersonation can then access your domain from the host environment becauseit has the privilege of your domain account
SAP Business Planning and Consolidation 100Installing Planning and Consolidation with Two Active Directory Domains
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 43
7 Installing Planning and Consolidation in aTerminal Services or Citrix ServerDeployment
This section describes best practices and instructions for installing Planning and Consolidation in a Terminal Servicesor Citrix Server deployment
71 Terminal Services Home Directories
We recommend using Terminal Server home directories rather than using the userrsquos profile directory The profiledirectory downloads a minimal amount of information about the dimensions of the environment you are logging onto and may be as large as 2 MB per user The profile directory is on the system drive and has limited space Byspecifying 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 individualserver 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 clientserver (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
44
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
Procedure
The following steps outline how to install the Planning and Consolidation clients in a Terminal Services (TS) or CitrixServer deployment
1 Make sure the Terminal Services or Citrix Server machine has the system requirements installed
2 Log on to the Terminal Services or Citrix Server machine with a user ID that has the rights to install on thatserver
3 At a command prompt enter Change userinstall
4 Open a browser and connect to the URL ltPC_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_MSBPCAdminMainexe
74 Creating a Shortcut to the Launch Page
Procedure
If you use published desktops instead of published applications the Planning and Consolidation desktop file (whichis installed on the current userrsquos desktop) must be moved to the All UsersDesktop folder
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 45
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 SQLServer 2012 support the remote modification of SSIS packages Planning and Consolidation also supports theremote 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 whichyou want to modify SSIS packages
These custom tasks reference dlls that connect to the database server and perform certain validation when usersset up the parameters of each task All the custom task reference components must also be installed in the machineon which you want to modify SSIS packages
We provide a program that registers all the reference components of the custom tasks This section explains theinstallation 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 ndash This folder contains all the dlls that should be installed on the machine There are Planning andConsolidation platform components and all of the Data Manager custom task files
Config folder ndash This folder contains only one file named Filelistxml and lists all of the files that should be installedIf you need to add or remove certain components from the installation you can modify this xml file
OSoftSetupexe ndash This is the main executable file to run the installation package
NoteIf you are not installing SSIS Custom Tasks on your client machine ndash specifically a machine other than the Planningand Consolidation application server ndash you must first install OSoftSSIS2008_Client or OSoftSSIS2012_Client onthe client machine followed by the SQL Server version If you want to use SQL 2008 Tasks under the SQL 2012environment you must install OSoftSSIS2008_Client on the application server For detailed information see SAPNote 1707410 You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package byextracting OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPCInstallation folder on the Planning and Consolidation server To modify SSIS packages on the Planning andConsolidation application server you need to install OSoftSSIS2008_Client or OSoftSSIS2012_Client for creatinga COM+ application For more information see Before You Modify the SSIS Packages [page 49] and Setup ofa COM+ Application on the Application Server [page 50]
Bin folder
This folder contains the following components
46
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Table 11
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012respectively
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
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 47
Name Remark
BPCWriteBackdll
InteropDTSdll
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 addmore components to the installation package you can copy the new components into the Bin folder and add theproper xml tags in FileListxml You need to enter information for the following tags
RegistType ndash This is the registration information of the component You can enter the following values
RegAsm ndash For NET component
48
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Regsvr32 ndash For VB6 component
Gacutil ndash For NET Framework component that should be registered into Global Assembly Cache
FileName ndash Component file name
OSoftSetupexe
This is the executable file to run the SSIS installation package Double-click the file to start the installation You needto enter information for the following fields
Set SQL server
Specify the SQL server name If your SQL Server has an instance specify the instance name
NoteIf you installed the OSoftSSIS2008_Client or OSoftSSIS2012_Client on the application server the SQL servername is automatically disabled
Set server credential
This is the credential name of the COM+ package component Enter the user ID and password that can accessyour SQL Server This should be either the System Admin ID or Admin ID that was registered as a COM+ userwhen 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 ifyou 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 packagesremotely This is also true for the application server that has SSIS installed The Planning and ConsolidationData Manager has the following custom tasks
Table 12
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008and 2012 respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and2012 respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012respectively
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 49
Name Remark
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and2012 respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008and 2012 respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL2008 and 2012 respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and2012 respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012respectively
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
ltdrivegtWebsrvrbin2 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 FilesMicrosoft SQLServer paste all files into the CProgram Files (x86)Microsoft SQL Server100DTSTasksfolder
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
50
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Typographic Conventions
Table 13
Example Description
lt gt Angle brackets indicate that you replace these words or characters with appropriate entries tomake entries in the system for example Enter your ltUser Namegt
File Save Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
Example Textual cross-references to an internet address for example wwwsapcom
example Quicklinks added to the internet address of a homepage to enable quick access to specificcontent 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 titlespushbutton 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 namesof installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transactioncodes database table names and key concepts of a programming language when they aresurrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
SAP Business Planning and Consolidation 100Typographic Conventions
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 51
52
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
wwwsapcom
Material Number
- SAP Business 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 2008 R2 2012 or 2012 R2
- 344 Removing Default Access to the Console
- 345 Management Console Access Control
- 346 Configuring Planning and Consolidation to use SSL
- 347 Using Client Certificates
- 348 Configuring MS SQL Server Reporting Services to use SSL
-
- 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
-
4 Select the BPC directory (ltWebsitegtSAPBPC) and enable Anonymous Authentication the same way asin step 3
5 Select the SBC directory (ltWebsitegtSAPPOASBC) and enable Anonymous Authentication the sameway 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
348 Configuring MS SQL Server Reporting Services to useSSL
Procedure
The procedure below describes how to configure the use of SSL in Microsoft SQL Server Reporting Services
NoteReporting Services does not provide functionalities for generating requesting or installing a certificate Theserver certificates that you want to use for configuring SSL must have already been installed on your computer
1 Open the Reporting Services Configuration Manager program To do this open the Windows Start menu andnavigate to All Programs Microsoft SQL Server ltversiongt Configuration Tools Reporting ServicesConfiguration Manager
2 In the Connect panel on the left-hand side select the Web Service URL option to open all the Report Server webservice parameters
3 Configure the parameters as follows
SSL Certificate = the name of the certificate that you want to use
SSL Port = 4434 Choose Apply to confirm the changes
5 In the Connect panel choose Report Manager URL to open the list of parameters that link Reporting Servicesto IIS
6 Choose Advanced to add your new SSL web URL
7 In the section Multiple SSL Identities for Report Manager choose Add Configure the parameters as follows
IP Address = (All IPv4) SSL Port = 443 Certificate = the name of your SSL certificate
8 To test the configuration click the URL that appears under the Report manager Site Identification section
36
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100After Installing Planning and Consolidation Servers
4 Installing Planning and ConsolidationAdministration Client and the SAPBusinessObjects EPM solutions Add-in forMicrosoft Office
The installation of the Planning and Consolidation Administration Client allows administrators to build and maintainPlanning and Consolidation environments and models and administer security
All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions add-in forMicrosoft 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 valueof the Planning and Consolidation client to prompt for user name and password Otherwise the Planning andConsolidation Start Page does not display
41 Installing the Administration Client
Prerequisites
NoteFor a definitive list of system requirements see the Product Availability Matrix on SAP Service Marketplace atservicesapcompam Search on Planning and Consolidation
The following list describes the minimum software requirements
Microsoft Internet Explorer 70 80 90 or 10
Microsoft Office 2003 2007 2010 or 2012
NET Framework 20 or higher (install any required NET Framework Hotfixes by referring tosupportmicrosoftcomkb)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 37
NoteWe recommend that you install all of the latest Microsoft Windows hotfixes prior to installing the Administrationclient For information about which hotfixes to install see updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us
Procedure
The 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 ltPC_serverportgtsapbpcweb
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 mustdownload the most recent version of the full setup (EPM Add-inexe) from the Service Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPCInstallation folder
Individual users can install the EPM add-in on their own machines by going to the Planning and Consolidation Homepage 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 upthe 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
38
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
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 toperform the upgrade If Client Auto Update is not enabled and a newer version is detected clients must be installedmanually 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 andpassword in the Admin ID and Admin password fields respectively The Admin ID should be a member of thelocal administrators group on all the computers running the auto update This setting is not needed if all usershave 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 Thisoption is stored in the user preferences and may also be turned on or off using the User Optionshellip menu itemIf 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 toinstall 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 installit 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 servicesapcom
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 versionand policy information For a support package these files are
EPM Addin Support Package ltSP versiongtmsp EPM Addin Support Package ltSP versiongtxmlFor a patch these files are
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 (WebsrvrWebBPCInstallation)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 39
You can set a different update policy for each package listed
ExampleThe following table illustrates some possible situations assuming that you have installed the first full version(V1)
Table 10
Available maintenancepackages
V2-user update
V3-force update
V4-force update
V5-user update
V5-user update V5-user update
V6-auto update
V7-force update
Minimum RequiredVersion
V4 V4 V7
Notification A prompt tells the user toinstall maintenancepackage V4 using theForced Update behavior
If User Update is enabledthe prompt informs theuser that maintenancepackage V5 is available
A prompt tells the user toinstall maintenancepackage V7 using theForced Update behavior
New Version V4 V4 or V5 V7
If you change the update policy for any package click Update to complete the change
40
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
5 Connection Issues
You may experience connection problems with ports the proxy server or programs and settings that interact withthese components If you have any issues related to connection review the following recommendations andtroubleshooting tips
51 Checking for Open Ports
You must ensure that all required ports are open for inboundoutbound traffic By default Planning andConsolidation requires that Ports 80 (used by http) and 1433 and 2383 (used by SQL Server 2008) are open Totest whether the required ports are open go to a command prompt and enter the Telnet serveripaddress and portFor example Telnet 431181836 80 If the system returns a blank command window the port is open If it returnsa message stating that it is unable to connect the port is not open
NoteYou can use the following site to scan for the normal ports It allows you to manually enter a port number to test
wwwmyserverorgportsniffasp
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 Planningand Consolidation server as an exception You can do this at the client level ( Internet Explorer ToolsInternet 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 fullyqualified 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 Consolidationauthentication Do not use authentication on the proxy server The system synchronizes the user name andpassword on the remote server with the local user name and password
SAP Business Planning and Consolidation 100Connection Issues
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 41
NoteFor more information about setting up an ISA proxy server contact SAP Support to request a copy of Setting upISA Proxy Server White Paper For more information about Business Planning and Consolidation firewall portssee SAP Note 1505250
Internet Explorer Settings Issues
Internet Explorer settings must be set correctly to prevent errors and problems when you attempt to access thePlanning 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 insertthe IP address or fully qualified server name of the Planning and Consolidation server as an exception bychoosing 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
42
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Connection Issues
6 Installing Planning and Consolidation withTwo Active Directory Domains
To set up a Planning and Consolidation 10 application server in a hosted environment and use your own domainusers follow this procedure In general you install Planning and Consolidation on the host domain use the hostdomain account and assign it to the Planning and Consolidation users SysAdmin Admin and Users Then you acceptone 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 andpassword 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 topromote 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 privilegefor the Planning and Consolidation server
5 Install Planning and Consolidation and assign your domain account either to the three Planning andConsolidation administrative users SysAdmin Admin and Users or to only one of the three Planning andConsolidation administrative users and to three of your users Be sure you use your own user account ratherthan host domain users
Planning and Consolidation impersonation can then access your domain from the host environment becauseit has the privilege of your domain account
SAP Business Planning and Consolidation 100Installing Planning and Consolidation with Two Active Directory Domains
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 43
7 Installing Planning and Consolidation in aTerminal Services or Citrix ServerDeployment
This section describes best practices and instructions for installing Planning and Consolidation in a Terminal Servicesor Citrix Server deployment
71 Terminal Services Home Directories
We recommend using Terminal Server home directories rather than using the userrsquos profile directory The profiledirectory downloads a minimal amount of information about the dimensions of the environment you are logging onto and may be as large as 2 MB per user The profile directory is on the system drive and has limited space Byspecifying 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 individualserver 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 clientserver (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
44
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
Procedure
The following steps outline how to install the Planning and Consolidation clients in a Terminal Services (TS) or CitrixServer deployment
1 Make sure the Terminal Services or Citrix Server machine has the system requirements installed
2 Log on to the Terminal Services or Citrix Server machine with a user ID that has the rights to install on thatserver
3 At a command prompt enter Change userinstall
4 Open a browser and connect to the URL ltPC_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_MSBPCAdminMainexe
74 Creating a Shortcut to the Launch Page
Procedure
If you use published desktops instead of published applications the Planning and Consolidation desktop file (whichis installed on the current userrsquos desktop) must be moved to the All UsersDesktop folder
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 45
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 SQLServer 2012 support the remote modification of SSIS packages Planning and Consolidation also supports theremote 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 whichyou want to modify SSIS packages
These custom tasks reference dlls that connect to the database server and perform certain validation when usersset up the parameters of each task All the custom task reference components must also be installed in the machineon which you want to modify SSIS packages
We provide a program that registers all the reference components of the custom tasks This section explains theinstallation 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 ndash This folder contains all the dlls that should be installed on the machine There are Planning andConsolidation platform components and all of the Data Manager custom task files
Config folder ndash This folder contains only one file named Filelistxml and lists all of the files that should be installedIf you need to add or remove certain components from the installation you can modify this xml file
OSoftSetupexe ndash This is the main executable file to run the installation package
NoteIf you are not installing SSIS Custom Tasks on your client machine ndash specifically a machine other than the Planningand Consolidation application server ndash you must first install OSoftSSIS2008_Client or OSoftSSIS2012_Client onthe client machine followed by the SQL Server version If you want to use SQL 2008 Tasks under the SQL 2012environment you must install OSoftSSIS2008_Client on the application server For detailed information see SAPNote 1707410 You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package byextracting OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPCInstallation folder on the Planning and Consolidation server To modify SSIS packages on the Planning andConsolidation application server you need to install OSoftSSIS2008_Client or OSoftSSIS2012_Client for creatinga COM+ application For more information see Before You Modify the SSIS Packages [page 49] and Setup ofa COM+ Application on the Application Server [page 50]
Bin folder
This folder contains the following components
46
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Table 11
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012respectively
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
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 47
Name Remark
BPCWriteBackdll
InteropDTSdll
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 addmore components to the installation package you can copy the new components into the Bin folder and add theproper xml tags in FileListxml You need to enter information for the following tags
RegistType ndash This is the registration information of the component You can enter the following values
RegAsm ndash For NET component
48
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Regsvr32 ndash For VB6 component
Gacutil ndash For NET Framework component that should be registered into Global Assembly Cache
FileName ndash Component file name
OSoftSetupexe
This is the executable file to run the SSIS installation package Double-click the file to start the installation You needto enter information for the following fields
Set SQL server
Specify the SQL server name If your SQL Server has an instance specify the instance name
NoteIf you installed the OSoftSSIS2008_Client or OSoftSSIS2012_Client on the application server the SQL servername is automatically disabled
Set server credential
This is the credential name of the COM+ package component Enter the user ID and password that can accessyour SQL Server This should be either the System Admin ID or Admin ID that was registered as a COM+ userwhen 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 ifyou 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 packagesremotely This is also true for the application server that has SSIS installed The Planning and ConsolidationData Manager has the following custom tasks
Table 12
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008and 2012 respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and2012 respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012respectively
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 49
Name Remark
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and2012 respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008and 2012 respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL2008 and 2012 respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and2012 respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012respectively
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
ltdrivegtWebsrvrbin2 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 FilesMicrosoft SQLServer paste all files into the CProgram Files (x86)Microsoft SQL Server100DTSTasksfolder
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
50
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Typographic Conventions
Table 13
Example Description
lt gt Angle brackets indicate that you replace these words or characters with appropriate entries tomake entries in the system for example Enter your ltUser Namegt
File Save Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
Example Textual cross-references to an internet address for example wwwsapcom
example Quicklinks added to the internet address of a homepage to enable quick access to specificcontent 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 titlespushbutton 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 namesof installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transactioncodes database table names and key concepts of a programming language when they aresurrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
SAP Business Planning and Consolidation 100Typographic Conventions
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 51
52
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
wwwsapcom
Material Number
- SAP Business 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 2008 R2 2012 or 2012 R2
- 344 Removing Default Access to the Console
- 345 Management Console Access Control
- 346 Configuring Planning and Consolidation to use SSL
- 347 Using Client Certificates
- 348 Configuring MS SQL Server Reporting Services to use SSL
-
- 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
-
4 Installing Planning and ConsolidationAdministration Client and the SAPBusinessObjects EPM solutions Add-in forMicrosoft Office
The installation of the Planning and Consolidation Administration Client allows administrators to build and maintainPlanning and Consolidation environments and models and administer security
All reporting budgeting publishing and other user tasks use the SAP BusinessObjects EPM solutions add-in forMicrosoft 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 valueof the Planning and Consolidation client to prompt for user name and password Otherwise the Planning andConsolidation Start Page does not display
41 Installing the Administration Client
Prerequisites
NoteFor a definitive list of system requirements see the Product Availability Matrix on SAP Service Marketplace atservicesapcompam Search on Planning and Consolidation
The following list describes the minimum software requirements
Microsoft Internet Explorer 70 80 90 or 10
Microsoft Office 2003 2007 2010 or 2012
NET Framework 20 or higher (install any required NET Framework Hotfixes by referring tosupportmicrosoftcomkb)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 37
NoteWe recommend that you install all of the latest Microsoft Windows hotfixes prior to installing the Administrationclient For information about which hotfixes to install see updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us
Procedure
The 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 ltPC_serverportgtsapbpcweb
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 mustdownload the most recent version of the full setup (EPM Add-inexe) from the Service Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPCInstallation folder
Individual users can install the EPM add-in on their own machines by going to the Planning and Consolidation Homepage 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 upthe 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
38
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
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 toperform the upgrade If Client Auto Update is not enabled and a newer version is detected clients must be installedmanually 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 andpassword in the Admin ID and Admin password fields respectively The Admin ID should be a member of thelocal administrators group on all the computers running the auto update This setting is not needed if all usershave 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 Thisoption is stored in the user preferences and may also be turned on or off using the User Optionshellip menu itemIf 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 toinstall 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 installit 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 servicesapcom
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 versionand policy information For a support package these files are
EPM Addin Support Package ltSP versiongtmsp EPM Addin Support Package ltSP versiongtxmlFor a patch these files are
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 (WebsrvrWebBPCInstallation)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 39
You can set a different update policy for each package listed
ExampleThe following table illustrates some possible situations assuming that you have installed the first full version(V1)
Table 10
Available maintenancepackages
V2-user update
V3-force update
V4-force update
V5-user update
V5-user update V5-user update
V6-auto update
V7-force update
Minimum RequiredVersion
V4 V4 V7
Notification A prompt tells the user toinstall maintenancepackage V4 using theForced Update behavior
If User Update is enabledthe prompt informs theuser that maintenancepackage V5 is available
A prompt tells the user toinstall maintenancepackage V7 using theForced Update behavior
New Version V4 V4 or V5 V7
If you change the update policy for any package click Update to complete the change
40
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
5 Connection Issues
You may experience connection problems with ports the proxy server or programs and settings that interact withthese components If you have any issues related to connection review the following recommendations andtroubleshooting tips
51 Checking for Open Ports
You must ensure that all required ports are open for inboundoutbound traffic By default Planning andConsolidation requires that Ports 80 (used by http) and 1433 and 2383 (used by SQL Server 2008) are open Totest whether the required ports are open go to a command prompt and enter the Telnet serveripaddress and portFor example Telnet 431181836 80 If the system returns a blank command window the port is open If it returnsa message stating that it is unable to connect the port is not open
NoteYou can use the following site to scan for the normal ports It allows you to manually enter a port number to test
wwwmyserverorgportsniffasp
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 Planningand Consolidation server as an exception You can do this at the client level ( Internet Explorer ToolsInternet 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 fullyqualified 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 Consolidationauthentication Do not use authentication on the proxy server The system synchronizes the user name andpassword on the remote server with the local user name and password
SAP Business Planning and Consolidation 100Connection Issues
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 41
NoteFor more information about setting up an ISA proxy server contact SAP Support to request a copy of Setting upISA Proxy Server White Paper For more information about Business Planning and Consolidation firewall portssee SAP Note 1505250
Internet Explorer Settings Issues
Internet Explorer settings must be set correctly to prevent errors and problems when you attempt to access thePlanning 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 insertthe IP address or fully qualified server name of the Planning and Consolidation server as an exception bychoosing 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
42
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Connection Issues
6 Installing Planning and Consolidation withTwo Active Directory Domains
To set up a Planning and Consolidation 10 application server in a hosted environment and use your own domainusers follow this procedure In general you install Planning and Consolidation on the host domain use the hostdomain account and assign it to the Planning and Consolidation users SysAdmin Admin and Users Then you acceptone 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 andpassword 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 topromote 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 privilegefor the Planning and Consolidation server
5 Install Planning and Consolidation and assign your domain account either to the three Planning andConsolidation administrative users SysAdmin Admin and Users or to only one of the three Planning andConsolidation administrative users and to three of your users Be sure you use your own user account ratherthan host domain users
Planning and Consolidation impersonation can then access your domain from the host environment becauseit has the privilege of your domain account
SAP Business Planning and Consolidation 100Installing Planning and Consolidation with Two Active Directory Domains
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 43
7 Installing Planning and Consolidation in aTerminal Services or Citrix ServerDeployment
This section describes best practices and instructions for installing Planning and Consolidation in a Terminal Servicesor Citrix Server deployment
71 Terminal Services Home Directories
We recommend using Terminal Server home directories rather than using the userrsquos profile directory The profiledirectory downloads a minimal amount of information about the dimensions of the environment you are logging onto and may be as large as 2 MB per user The profile directory is on the system drive and has limited space Byspecifying 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 individualserver 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 clientserver (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
44
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
Procedure
The following steps outline how to install the Planning and Consolidation clients in a Terminal Services (TS) or CitrixServer deployment
1 Make sure the Terminal Services or Citrix Server machine has the system requirements installed
2 Log on to the Terminal Services or Citrix Server machine with a user ID that has the rights to install on thatserver
3 At a command prompt enter Change userinstall
4 Open a browser and connect to the URL ltPC_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_MSBPCAdminMainexe
74 Creating a Shortcut to the Launch Page
Procedure
If you use published desktops instead of published applications the Planning and Consolidation desktop file (whichis installed on the current userrsquos desktop) must be moved to the All UsersDesktop folder
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 45
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 SQLServer 2012 support the remote modification of SSIS packages Planning and Consolidation also supports theremote 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 whichyou want to modify SSIS packages
These custom tasks reference dlls that connect to the database server and perform certain validation when usersset up the parameters of each task All the custom task reference components must also be installed in the machineon which you want to modify SSIS packages
We provide a program that registers all the reference components of the custom tasks This section explains theinstallation 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 ndash This folder contains all the dlls that should be installed on the machine There are Planning andConsolidation platform components and all of the Data Manager custom task files
Config folder ndash This folder contains only one file named Filelistxml and lists all of the files that should be installedIf you need to add or remove certain components from the installation you can modify this xml file
OSoftSetupexe ndash This is the main executable file to run the installation package
NoteIf you are not installing SSIS Custom Tasks on your client machine ndash specifically a machine other than the Planningand Consolidation application server ndash you must first install OSoftSSIS2008_Client or OSoftSSIS2012_Client onthe client machine followed by the SQL Server version If you want to use SQL 2008 Tasks under the SQL 2012environment you must install OSoftSSIS2008_Client on the application server For detailed information see SAPNote 1707410 You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package byextracting OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPCInstallation folder on the Planning and Consolidation server To modify SSIS packages on the Planning andConsolidation application server you need to install OSoftSSIS2008_Client or OSoftSSIS2012_Client for creatinga COM+ application For more information see Before You Modify the SSIS Packages [page 49] and Setup ofa COM+ Application on the Application Server [page 50]
Bin folder
This folder contains the following components
46
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Table 11
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012respectively
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
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 47
Name Remark
BPCWriteBackdll
InteropDTSdll
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 addmore components to the installation package you can copy the new components into the Bin folder and add theproper xml tags in FileListxml You need to enter information for the following tags
RegistType ndash This is the registration information of the component You can enter the following values
RegAsm ndash For NET component
48
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Regsvr32 ndash For VB6 component
Gacutil ndash For NET Framework component that should be registered into Global Assembly Cache
FileName ndash Component file name
OSoftSetupexe
This is the executable file to run the SSIS installation package Double-click the file to start the installation You needto enter information for the following fields
Set SQL server
Specify the SQL server name If your SQL Server has an instance specify the instance name
NoteIf you installed the OSoftSSIS2008_Client or OSoftSSIS2012_Client on the application server the SQL servername is automatically disabled
Set server credential
This is the credential name of the COM+ package component Enter the user ID and password that can accessyour SQL Server This should be either the System Admin ID or Admin ID that was registered as a COM+ userwhen 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 ifyou 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 packagesremotely This is also true for the application server that has SSIS installed The Planning and ConsolidationData Manager has the following custom tasks
Table 12
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008and 2012 respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and2012 respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012respectively
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 49
Name Remark
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and2012 respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008and 2012 respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL2008 and 2012 respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and2012 respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012respectively
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
ltdrivegtWebsrvrbin2 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 FilesMicrosoft SQLServer paste all files into the CProgram Files (x86)Microsoft SQL Server100DTSTasksfolder
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
50
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Typographic Conventions
Table 13
Example Description
lt gt Angle brackets indicate that you replace these words or characters with appropriate entries tomake entries in the system for example Enter your ltUser Namegt
File Save Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
Example Textual cross-references to an internet address for example wwwsapcom
example Quicklinks added to the internet address of a homepage to enable quick access to specificcontent 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 titlespushbutton 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 namesof installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transactioncodes database table names and key concepts of a programming language when they aresurrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
SAP Business Planning and Consolidation 100Typographic Conventions
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 51
52
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
wwwsapcom
Material Number
- SAP Business 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 2008 R2 2012 or 2012 R2
- 344 Removing Default Access to the Console
- 345 Management Console Access Control
- 346 Configuring Planning and Consolidation to use SSL
- 347 Using Client Certificates
- 348 Configuring MS SQL Server Reporting Services to use SSL
-
- 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
-
NoteWe recommend that you install all of the latest Microsoft Windows hotfixes prior to installing the Administrationclient For information about which hotfixes to install see updatemicrosoftcomwindowsupdatev6defaultaspxln=en-us
Procedure
The 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 ltPC_serverportgtsapbpcweb
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 mustdownload the most recent version of the full setup (EPM Add-inexe) from the Service Marketplace (htpservicesapcom)) Copy this file to the servers WebsrvrWebBPCInstallation folder
Individual users can install the EPM add-in on their own machines by going to the Planning and Consolidation Homepage 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 upthe 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
38
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
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 toperform the upgrade If Client Auto Update is not enabled and a newer version is detected clients must be installedmanually 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 andpassword in the Admin ID and Admin password fields respectively The Admin ID should be a member of thelocal administrators group on all the computers running the auto update This setting is not needed if all usershave 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 Thisoption is stored in the user preferences and may also be turned on or off using the User Optionshellip menu itemIf 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 toinstall 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 installit 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 servicesapcom
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 versionand policy information For a support package these files are
EPM Addin Support Package ltSP versiongtmsp EPM Addin Support Package ltSP versiongtxmlFor a patch these files are
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 (WebsrvrWebBPCInstallation)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 39
You can set a different update policy for each package listed
ExampleThe following table illustrates some possible situations assuming that you have installed the first full version(V1)
Table 10
Available maintenancepackages
V2-user update
V3-force update
V4-force update
V5-user update
V5-user update V5-user update
V6-auto update
V7-force update
Minimum RequiredVersion
V4 V4 V7
Notification A prompt tells the user toinstall maintenancepackage V4 using theForced Update behavior
If User Update is enabledthe prompt informs theuser that maintenancepackage V5 is available
A prompt tells the user toinstall maintenancepackage V7 using theForced Update behavior
New Version V4 V4 or V5 V7
If you change the update policy for any package click Update to complete the change
40
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
5 Connection Issues
You may experience connection problems with ports the proxy server or programs and settings that interact withthese components If you have any issues related to connection review the following recommendations andtroubleshooting tips
51 Checking for Open Ports
You must ensure that all required ports are open for inboundoutbound traffic By default Planning andConsolidation requires that Ports 80 (used by http) and 1433 and 2383 (used by SQL Server 2008) are open Totest whether the required ports are open go to a command prompt and enter the Telnet serveripaddress and portFor example Telnet 431181836 80 If the system returns a blank command window the port is open If it returnsa message stating that it is unable to connect the port is not open
NoteYou can use the following site to scan for the normal ports It allows you to manually enter a port number to test
wwwmyserverorgportsniffasp
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 Planningand Consolidation server as an exception You can do this at the client level ( Internet Explorer ToolsInternet 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 fullyqualified 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 Consolidationauthentication Do not use authentication on the proxy server The system synchronizes the user name andpassword on the remote server with the local user name and password
SAP Business Planning and Consolidation 100Connection Issues
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 41
NoteFor more information about setting up an ISA proxy server contact SAP Support to request a copy of Setting upISA Proxy Server White Paper For more information about Business Planning and Consolidation firewall portssee SAP Note 1505250
Internet Explorer Settings Issues
Internet Explorer settings must be set correctly to prevent errors and problems when you attempt to access thePlanning 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 insertthe IP address or fully qualified server name of the Planning and Consolidation server as an exception bychoosing 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
42
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Connection Issues
6 Installing Planning and Consolidation withTwo Active Directory Domains
To set up a Planning and Consolidation 10 application server in a hosted environment and use your own domainusers follow this procedure In general you install Planning and Consolidation on the host domain use the hostdomain account and assign it to the Planning and Consolidation users SysAdmin Admin and Users Then you acceptone 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 andpassword 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 topromote 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 privilegefor the Planning and Consolidation server
5 Install Planning and Consolidation and assign your domain account either to the three Planning andConsolidation administrative users SysAdmin Admin and Users or to only one of the three Planning andConsolidation administrative users and to three of your users Be sure you use your own user account ratherthan host domain users
Planning and Consolidation impersonation can then access your domain from the host environment becauseit has the privilege of your domain account
SAP Business Planning and Consolidation 100Installing Planning and Consolidation with Two Active Directory Domains
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 43
7 Installing Planning and Consolidation in aTerminal Services or Citrix ServerDeployment
This section describes best practices and instructions for installing Planning and Consolidation in a Terminal Servicesor Citrix Server deployment
71 Terminal Services Home Directories
We recommend using Terminal Server home directories rather than using the userrsquos profile directory The profiledirectory downloads a minimal amount of information about the dimensions of the environment you are logging onto and may be as large as 2 MB per user The profile directory is on the system drive and has limited space Byspecifying 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 individualserver 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 clientserver (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
44
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
Procedure
The following steps outline how to install the Planning and Consolidation clients in a Terminal Services (TS) or CitrixServer deployment
1 Make sure the Terminal Services or Citrix Server machine has the system requirements installed
2 Log on to the Terminal Services or Citrix Server machine with a user ID that has the rights to install on thatserver
3 At a command prompt enter Change userinstall
4 Open a browser and connect to the URL ltPC_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_MSBPCAdminMainexe
74 Creating a Shortcut to the Launch Page
Procedure
If you use published desktops instead of published applications the Planning and Consolidation desktop file (whichis installed on the current userrsquos desktop) must be moved to the All UsersDesktop folder
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 45
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 SQLServer 2012 support the remote modification of SSIS packages Planning and Consolidation also supports theremote 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 whichyou want to modify SSIS packages
These custom tasks reference dlls that connect to the database server and perform certain validation when usersset up the parameters of each task All the custom task reference components must also be installed in the machineon which you want to modify SSIS packages
We provide a program that registers all the reference components of the custom tasks This section explains theinstallation 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 ndash This folder contains all the dlls that should be installed on the machine There are Planning andConsolidation platform components and all of the Data Manager custom task files
Config folder ndash This folder contains only one file named Filelistxml and lists all of the files that should be installedIf you need to add or remove certain components from the installation you can modify this xml file
OSoftSetupexe ndash This is the main executable file to run the installation package
NoteIf you are not installing SSIS Custom Tasks on your client machine ndash specifically a machine other than the Planningand Consolidation application server ndash you must first install OSoftSSIS2008_Client or OSoftSSIS2012_Client onthe client machine followed by the SQL Server version If you want to use SQL 2008 Tasks under the SQL 2012environment you must install OSoftSSIS2008_Client on the application server For detailed information see SAPNote 1707410 You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package byextracting OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPCInstallation folder on the Planning and Consolidation server To modify SSIS packages on the Planning andConsolidation application server you need to install OSoftSSIS2008_Client or OSoftSSIS2012_Client for creatinga COM+ application For more information see Before You Modify the SSIS Packages [page 49] and Setup ofa COM+ Application on the Application Server [page 50]
Bin folder
This folder contains the following components
46
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Table 11
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012respectively
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
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 47
Name Remark
BPCWriteBackdll
InteropDTSdll
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 addmore components to the installation package you can copy the new components into the Bin folder and add theproper xml tags in FileListxml You need to enter information for the following tags
RegistType ndash This is the registration information of the component You can enter the following values
RegAsm ndash For NET component
48
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Regsvr32 ndash For VB6 component
Gacutil ndash For NET Framework component that should be registered into Global Assembly Cache
FileName ndash Component file name
OSoftSetupexe
This is the executable file to run the SSIS installation package Double-click the file to start the installation You needto enter information for the following fields
Set SQL server
Specify the SQL server name If your SQL Server has an instance specify the instance name
NoteIf you installed the OSoftSSIS2008_Client or OSoftSSIS2012_Client on the application server the SQL servername is automatically disabled
Set server credential
This is the credential name of the COM+ package component Enter the user ID and password that can accessyour SQL Server This should be either the System Admin ID or Admin ID that was registered as a COM+ userwhen 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 ifyou 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 packagesremotely This is also true for the application server that has SSIS installed The Planning and ConsolidationData Manager has the following custom tasks
Table 12
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008and 2012 respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and2012 respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012respectively
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 49
Name Remark
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and2012 respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008and 2012 respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL2008 and 2012 respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and2012 respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012respectively
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
ltdrivegtWebsrvrbin2 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 FilesMicrosoft SQLServer paste all files into the CProgram Files (x86)Microsoft SQL Server100DTSTasksfolder
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
50
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Typographic Conventions
Table 13
Example Description
lt gt Angle brackets indicate that you replace these words or characters with appropriate entries tomake entries in the system for example Enter your ltUser Namegt
File Save Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
Example Textual cross-references to an internet address for example wwwsapcom
example Quicklinks added to the internet address of a homepage to enable quick access to specificcontent 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 titlespushbutton 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 namesof installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transactioncodes database table names and key concepts of a programming language when they aresurrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
SAP Business Planning and Consolidation 100Typographic Conventions
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 51
52
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
wwwsapcom
Material Number
- SAP Business 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 2008 R2 2012 or 2012 R2
- 344 Removing Default Access to the Console
- 345 Management Console Access Control
- 346 Configuring Planning and Consolidation to use SSL
- 347 Using Client Certificates
- 348 Configuring MS SQL Server Reporting Services to use SSL
-
- 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
-
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 toperform the upgrade If Client Auto Update is not enabled and a newer version is detected clients must be installedmanually 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 andpassword in the Admin ID and Admin password fields respectively The Admin ID should be a member of thelocal administrators group on all the computers running the auto update This setting is not needed if all usershave 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 Thisoption is stored in the user preferences and may also be turned on or off using the User Optionshellip menu itemIf 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 toinstall 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 installit 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 servicesapcom
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 versionand policy information For a support package these files are
EPM Addin Support Package ltSP versiongtmsp EPM Addin Support Package ltSP versiongtxmlFor a patch these files are
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 (WebsrvrWebBPCInstallation)
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
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAPBusinessObjects EPM solutions Add-in for Microsoft Office
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 39
You can set a different update policy for each package listed
ExampleThe following table illustrates some possible situations assuming that you have installed the first full version(V1)
Table 10
Available maintenancepackages
V2-user update
V3-force update
V4-force update
V5-user update
V5-user update V5-user update
V6-auto update
V7-force update
Minimum RequiredVersion
V4 V4 V7
Notification A prompt tells the user toinstall maintenancepackage V4 using theForced Update behavior
If User Update is enabledthe prompt informs theuser that maintenancepackage V5 is available
A prompt tells the user toinstall maintenancepackage V7 using theForced Update behavior
New Version V4 V4 or V5 V7
If you change the update policy for any package click Update to complete the change
40
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
5 Connection Issues
You may experience connection problems with ports the proxy server or programs and settings that interact withthese components If you have any issues related to connection review the following recommendations andtroubleshooting tips
51 Checking for Open Ports
You must ensure that all required ports are open for inboundoutbound traffic By default Planning andConsolidation requires that Ports 80 (used by http) and 1433 and 2383 (used by SQL Server 2008) are open Totest whether the required ports are open go to a command prompt and enter the Telnet serveripaddress and portFor example Telnet 431181836 80 If the system returns a blank command window the port is open If it returnsa message stating that it is unable to connect the port is not open
NoteYou can use the following site to scan for the normal ports It allows you to manually enter a port number to test
wwwmyserverorgportsniffasp
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 Planningand Consolidation server as an exception You can do this at the client level ( Internet Explorer ToolsInternet 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 fullyqualified 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 Consolidationauthentication Do not use authentication on the proxy server The system synchronizes the user name andpassword on the remote server with the local user name and password
SAP Business Planning and Consolidation 100Connection Issues
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 41
NoteFor more information about setting up an ISA proxy server contact SAP Support to request a copy of Setting upISA Proxy Server White Paper For more information about Business Planning and Consolidation firewall portssee SAP Note 1505250
Internet Explorer Settings Issues
Internet Explorer settings must be set correctly to prevent errors and problems when you attempt to access thePlanning 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 insertthe IP address or fully qualified server name of the Planning and Consolidation server as an exception bychoosing 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
42
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Connection Issues
6 Installing Planning and Consolidation withTwo Active Directory Domains
To set up a Planning and Consolidation 10 application server in a hosted environment and use your own domainusers follow this procedure In general you install Planning and Consolidation on the host domain use the hostdomain account and assign it to the Planning and Consolidation users SysAdmin Admin and Users Then you acceptone 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 andpassword 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 topromote 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 privilegefor the Planning and Consolidation server
5 Install Planning and Consolidation and assign your domain account either to the three Planning andConsolidation administrative users SysAdmin Admin and Users or to only one of the three Planning andConsolidation administrative users and to three of your users Be sure you use your own user account ratherthan host domain users
Planning and Consolidation impersonation can then access your domain from the host environment becauseit has the privilege of your domain account
SAP Business Planning and Consolidation 100Installing Planning and Consolidation with Two Active Directory Domains
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 43
7 Installing Planning and Consolidation in aTerminal Services or Citrix ServerDeployment
This section describes best practices and instructions for installing Planning and Consolidation in a Terminal Servicesor Citrix Server deployment
71 Terminal Services Home Directories
We recommend using Terminal Server home directories rather than using the userrsquos profile directory The profiledirectory downloads a minimal amount of information about the dimensions of the environment you are logging onto and may be as large as 2 MB per user The profile directory is on the system drive and has limited space Byspecifying 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 individualserver 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 clientserver (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
44
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
Procedure
The following steps outline how to install the Planning and Consolidation clients in a Terminal Services (TS) or CitrixServer deployment
1 Make sure the Terminal Services or Citrix Server machine has the system requirements installed
2 Log on to the Terminal Services or Citrix Server machine with a user ID that has the rights to install on thatserver
3 At a command prompt enter Change userinstall
4 Open a browser and connect to the URL ltPC_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_MSBPCAdminMainexe
74 Creating a Shortcut to the Launch Page
Procedure
If you use published desktops instead of published applications the Planning and Consolidation desktop file (whichis installed on the current userrsquos desktop) must be moved to the All UsersDesktop folder
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 45
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 SQLServer 2012 support the remote modification of SSIS packages Planning and Consolidation also supports theremote 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 whichyou want to modify SSIS packages
These custom tasks reference dlls that connect to the database server and perform certain validation when usersset up the parameters of each task All the custom task reference components must also be installed in the machineon which you want to modify SSIS packages
We provide a program that registers all the reference components of the custom tasks This section explains theinstallation 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 ndash This folder contains all the dlls that should be installed on the machine There are Planning andConsolidation platform components and all of the Data Manager custom task files
Config folder ndash This folder contains only one file named Filelistxml and lists all of the files that should be installedIf you need to add or remove certain components from the installation you can modify this xml file
OSoftSetupexe ndash This is the main executable file to run the installation package
NoteIf you are not installing SSIS Custom Tasks on your client machine ndash specifically a machine other than the Planningand Consolidation application server ndash you must first install OSoftSSIS2008_Client or OSoftSSIS2012_Client onthe client machine followed by the SQL Server version If you want to use SQL 2008 Tasks under the SQL 2012environment you must install OSoftSSIS2008_Client on the application server For detailed information see SAPNote 1707410 You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package byextracting OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPCInstallation folder on the Planning and Consolidation server To modify SSIS packages on the Planning andConsolidation application server you need to install OSoftSSIS2008_Client or OSoftSSIS2012_Client for creatinga COM+ application For more information see Before You Modify the SSIS Packages [page 49] and Setup ofa COM+ Application on the Application Server [page 50]
Bin folder
This folder contains the following components
46
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Table 11
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012respectively
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
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 47
Name Remark
BPCWriteBackdll
InteropDTSdll
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 addmore components to the installation package you can copy the new components into the Bin folder and add theproper xml tags in FileListxml You need to enter information for the following tags
RegistType ndash This is the registration information of the component You can enter the following values
RegAsm ndash For NET component
48
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Regsvr32 ndash For VB6 component
Gacutil ndash For NET Framework component that should be registered into Global Assembly Cache
FileName ndash Component file name
OSoftSetupexe
This is the executable file to run the SSIS installation package Double-click the file to start the installation You needto enter information for the following fields
Set SQL server
Specify the SQL server name If your SQL Server has an instance specify the instance name
NoteIf you installed the OSoftSSIS2008_Client or OSoftSSIS2012_Client on the application server the SQL servername is automatically disabled
Set server credential
This is the credential name of the COM+ package component Enter the user ID and password that can accessyour SQL Server This should be either the System Admin ID or Admin ID that was registered as a COM+ userwhen 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 ifyou 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 packagesremotely This is also true for the application server that has SSIS installed The Planning and ConsolidationData Manager has the following custom tasks
Table 12
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008and 2012 respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and2012 respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012respectively
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 49
Name Remark
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and2012 respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008and 2012 respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL2008 and 2012 respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and2012 respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012respectively
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
ltdrivegtWebsrvrbin2 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 FilesMicrosoft SQLServer paste all files into the CProgram Files (x86)Microsoft SQL Server100DTSTasksfolder
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
50
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Typographic Conventions
Table 13
Example Description
lt gt Angle brackets indicate that you replace these words or characters with appropriate entries tomake entries in the system for example Enter your ltUser Namegt
File Save Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
Example Textual cross-references to an internet address for example wwwsapcom
example Quicklinks added to the internet address of a homepage to enable quick access to specificcontent 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 titlespushbutton 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 namesof installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transactioncodes database table names and key concepts of a programming language when they aresurrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
SAP Business Planning and Consolidation 100Typographic Conventions
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 51
52
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
wwwsapcom
Material Number
- SAP Business 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 2008 R2 2012 or 2012 R2
- 344 Removing Default Access to the Console
- 345 Management Console Access Control
- 346 Configuring Planning and Consolidation to use SSL
- 347 Using Client Certificates
- 348 Configuring MS SQL Server Reporting Services to use SSL
-
- 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
-
You can set a different update policy for each package listed
ExampleThe following table illustrates some possible situations assuming that you have installed the first full version(V1)
Table 10
Available maintenancepackages
V2-user update
V3-force update
V4-force update
V5-user update
V5-user update V5-user update
V6-auto update
V7-force update
Minimum RequiredVersion
V4 V4 V7
Notification A prompt tells the user toinstall maintenancepackage V4 using theForced Update behavior
If User Update is enabledthe prompt informs theuser that maintenancepackage V5 is available
A prompt tells the user toinstall maintenancepackage V7 using theForced Update behavior
New Version V4 V4 or V5 V7
If you change the update policy for any package click Update to complete the change
40
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation Administration Client and the SAP
BusinessObjects EPM solutions Add-in for Microsoft Office
5 Connection Issues
You may experience connection problems with ports the proxy server or programs and settings that interact withthese components If you have any issues related to connection review the following recommendations andtroubleshooting tips
51 Checking for Open Ports
You must ensure that all required ports are open for inboundoutbound traffic By default Planning andConsolidation requires that Ports 80 (used by http) and 1433 and 2383 (used by SQL Server 2008) are open Totest whether the required ports are open go to a command prompt and enter the Telnet serveripaddress and portFor example Telnet 431181836 80 If the system returns a blank command window the port is open If it returnsa message stating that it is unable to connect the port is not open
NoteYou can use the following site to scan for the normal ports It allows you to manually enter a port number to test
wwwmyserverorgportsniffasp
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 Planningand Consolidation server as an exception You can do this at the client level ( Internet Explorer ToolsInternet 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 fullyqualified 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 Consolidationauthentication Do not use authentication on the proxy server The system synchronizes the user name andpassword on the remote server with the local user name and password
SAP Business Planning and Consolidation 100Connection Issues
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 41
NoteFor more information about setting up an ISA proxy server contact SAP Support to request a copy of Setting upISA Proxy Server White Paper For more information about Business Planning and Consolidation firewall portssee SAP Note 1505250
Internet Explorer Settings Issues
Internet Explorer settings must be set correctly to prevent errors and problems when you attempt to access thePlanning 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 insertthe IP address or fully qualified server name of the Planning and Consolidation server as an exception bychoosing 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
42
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Connection Issues
6 Installing Planning and Consolidation withTwo Active Directory Domains
To set up a Planning and Consolidation 10 application server in a hosted environment and use your own domainusers follow this procedure In general you install Planning and Consolidation on the host domain use the hostdomain account and assign it to the Planning and Consolidation users SysAdmin Admin and Users Then you acceptone 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 andpassword 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 topromote 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 privilegefor the Planning and Consolidation server
5 Install Planning and Consolidation and assign your domain account either to the three Planning andConsolidation administrative users SysAdmin Admin and Users or to only one of the three Planning andConsolidation administrative users and to three of your users Be sure you use your own user account ratherthan host domain users
Planning and Consolidation impersonation can then access your domain from the host environment becauseit has the privilege of your domain account
SAP Business Planning and Consolidation 100Installing Planning and Consolidation with Two Active Directory Domains
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 43
7 Installing Planning and Consolidation in aTerminal Services or Citrix ServerDeployment
This section describes best practices and instructions for installing Planning and Consolidation in a Terminal Servicesor Citrix Server deployment
71 Terminal Services Home Directories
We recommend using Terminal Server home directories rather than using the userrsquos profile directory The profiledirectory downloads a minimal amount of information about the dimensions of the environment you are logging onto and may be as large as 2 MB per user The profile directory is on the system drive and has limited space Byspecifying 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 individualserver 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 clientserver (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
44
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
Procedure
The following steps outline how to install the Planning and Consolidation clients in a Terminal Services (TS) or CitrixServer deployment
1 Make sure the Terminal Services or Citrix Server machine has the system requirements installed
2 Log on to the Terminal Services or Citrix Server machine with a user ID that has the rights to install on thatserver
3 At a command prompt enter Change userinstall
4 Open a browser and connect to the URL ltPC_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_MSBPCAdminMainexe
74 Creating a Shortcut to the Launch Page
Procedure
If you use published desktops instead of published applications the Planning and Consolidation desktop file (whichis installed on the current userrsquos desktop) must be moved to the All UsersDesktop folder
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 45
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 SQLServer 2012 support the remote modification of SSIS packages Planning and Consolidation also supports theremote 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 whichyou want to modify SSIS packages
These custom tasks reference dlls that connect to the database server and perform certain validation when usersset up the parameters of each task All the custom task reference components must also be installed in the machineon which you want to modify SSIS packages
We provide a program that registers all the reference components of the custom tasks This section explains theinstallation 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 ndash This folder contains all the dlls that should be installed on the machine There are Planning andConsolidation platform components and all of the Data Manager custom task files
Config folder ndash This folder contains only one file named Filelistxml and lists all of the files that should be installedIf you need to add or remove certain components from the installation you can modify this xml file
OSoftSetupexe ndash This is the main executable file to run the installation package
NoteIf you are not installing SSIS Custom Tasks on your client machine ndash specifically a machine other than the Planningand Consolidation application server ndash you must first install OSoftSSIS2008_Client or OSoftSSIS2012_Client onthe client machine followed by the SQL Server version If you want to use SQL 2008 Tasks under the SQL 2012environment you must install OSoftSSIS2008_Client on the application server For detailed information see SAPNote 1707410 You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package byextracting OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPCInstallation folder on the Planning and Consolidation server To modify SSIS packages on the Planning andConsolidation application server you need to install OSoftSSIS2008_Client or OSoftSSIS2012_Client for creatinga COM+ application For more information see Before You Modify the SSIS Packages [page 49] and Setup ofa COM+ Application on the Application Server [page 50]
Bin folder
This folder contains the following components
46
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Table 11
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012respectively
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
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 47
Name Remark
BPCWriteBackdll
InteropDTSdll
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 addmore components to the installation package you can copy the new components into the Bin folder and add theproper xml tags in FileListxml You need to enter information for the following tags
RegistType ndash This is the registration information of the component You can enter the following values
RegAsm ndash For NET component
48
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Regsvr32 ndash For VB6 component
Gacutil ndash For NET Framework component that should be registered into Global Assembly Cache
FileName ndash Component file name
OSoftSetupexe
This is the executable file to run the SSIS installation package Double-click the file to start the installation You needto enter information for the following fields
Set SQL server
Specify the SQL server name If your SQL Server has an instance specify the instance name
NoteIf you installed the OSoftSSIS2008_Client or OSoftSSIS2012_Client on the application server the SQL servername is automatically disabled
Set server credential
This is the credential name of the COM+ package component Enter the user ID and password that can accessyour SQL Server This should be either the System Admin ID or Admin ID that was registered as a COM+ userwhen 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 ifyou 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 packagesremotely This is also true for the application server that has SSIS installed The Planning and ConsolidationData Manager has the following custom tasks
Table 12
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008and 2012 respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and2012 respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012respectively
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 49
Name Remark
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and2012 respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008and 2012 respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL2008 and 2012 respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and2012 respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012respectively
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
ltdrivegtWebsrvrbin2 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 FilesMicrosoft SQLServer paste all files into the CProgram Files (x86)Microsoft SQL Server100DTSTasksfolder
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
50
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Typographic Conventions
Table 13
Example Description
lt gt Angle brackets indicate that you replace these words or characters with appropriate entries tomake entries in the system for example Enter your ltUser Namegt
File Save Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
Example Textual cross-references to an internet address for example wwwsapcom
example Quicklinks added to the internet address of a homepage to enable quick access to specificcontent 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 titlespushbutton 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 namesof installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transactioncodes database table names and key concepts of a programming language when they aresurrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
SAP Business Planning and Consolidation 100Typographic Conventions
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 51
52
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
wwwsapcom
Material Number
- SAP Business 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 2008 R2 2012 or 2012 R2
- 344 Removing Default Access to the Console
- 345 Management Console Access Control
- 346 Configuring Planning and Consolidation to use SSL
- 347 Using Client Certificates
- 348 Configuring MS SQL Server Reporting Services to use SSL
-
- 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
-
5 Connection Issues
You may experience connection problems with ports the proxy server or programs and settings that interact withthese components If you have any issues related to connection review the following recommendations andtroubleshooting tips
51 Checking for Open Ports
You must ensure that all required ports are open for inboundoutbound traffic By default Planning andConsolidation requires that Ports 80 (used by http) and 1433 and 2383 (used by SQL Server 2008) are open Totest whether the required ports are open go to a command prompt and enter the Telnet serveripaddress and portFor example Telnet 431181836 80 If the system returns a blank command window the port is open If it returnsa message stating that it is unable to connect the port is not open
NoteYou can use the following site to scan for the normal ports It allows you to manually enter a port number to test
wwwmyserverorgportsniffasp
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 Planningand Consolidation server as an exception You can do this at the client level ( Internet Explorer ToolsInternet 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 fullyqualified 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 Consolidationauthentication Do not use authentication on the proxy server The system synchronizes the user name andpassword on the remote server with the local user name and password
SAP Business Planning and Consolidation 100Connection Issues
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 41
NoteFor more information about setting up an ISA proxy server contact SAP Support to request a copy of Setting upISA Proxy Server White Paper For more information about Business Planning and Consolidation firewall portssee SAP Note 1505250
Internet Explorer Settings Issues
Internet Explorer settings must be set correctly to prevent errors and problems when you attempt to access thePlanning 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 insertthe IP address or fully qualified server name of the Planning and Consolidation server as an exception bychoosing 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
42
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Connection Issues
6 Installing Planning and Consolidation withTwo Active Directory Domains
To set up a Planning and Consolidation 10 application server in a hosted environment and use your own domainusers follow this procedure In general you install Planning and Consolidation on the host domain use the hostdomain account and assign it to the Planning and Consolidation users SysAdmin Admin and Users Then you acceptone 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 andpassword 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 topromote 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 privilegefor the Planning and Consolidation server
5 Install Planning and Consolidation and assign your domain account either to the three Planning andConsolidation administrative users SysAdmin Admin and Users or to only one of the three Planning andConsolidation administrative users and to three of your users Be sure you use your own user account ratherthan host domain users
Planning and Consolidation impersonation can then access your domain from the host environment becauseit has the privilege of your domain account
SAP Business Planning and Consolidation 100Installing Planning and Consolidation with Two Active Directory Domains
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 43
7 Installing Planning and Consolidation in aTerminal Services or Citrix ServerDeployment
This section describes best practices and instructions for installing Planning and Consolidation in a Terminal Servicesor Citrix Server deployment
71 Terminal Services Home Directories
We recommend using Terminal Server home directories rather than using the userrsquos profile directory The profiledirectory downloads a minimal amount of information about the dimensions of the environment you are logging onto and may be as large as 2 MB per user The profile directory is on the system drive and has limited space Byspecifying 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 individualserver 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 clientserver (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
44
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
Procedure
The following steps outline how to install the Planning and Consolidation clients in a Terminal Services (TS) or CitrixServer deployment
1 Make sure the Terminal Services or Citrix Server machine has the system requirements installed
2 Log on to the Terminal Services or Citrix Server machine with a user ID that has the rights to install on thatserver
3 At a command prompt enter Change userinstall
4 Open a browser and connect to the URL ltPC_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_MSBPCAdminMainexe
74 Creating a Shortcut to the Launch Page
Procedure
If you use published desktops instead of published applications the Planning and Consolidation desktop file (whichis installed on the current userrsquos desktop) must be moved to the All UsersDesktop folder
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 45
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 SQLServer 2012 support the remote modification of SSIS packages Planning and Consolidation also supports theremote 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 whichyou want to modify SSIS packages
These custom tasks reference dlls that connect to the database server and perform certain validation when usersset up the parameters of each task All the custom task reference components must also be installed in the machineon which you want to modify SSIS packages
We provide a program that registers all the reference components of the custom tasks This section explains theinstallation 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 ndash This folder contains all the dlls that should be installed on the machine There are Planning andConsolidation platform components and all of the Data Manager custom task files
Config folder ndash This folder contains only one file named Filelistxml and lists all of the files that should be installedIf you need to add or remove certain components from the installation you can modify this xml file
OSoftSetupexe ndash This is the main executable file to run the installation package
NoteIf you are not installing SSIS Custom Tasks on your client machine ndash specifically a machine other than the Planningand Consolidation application server ndash you must first install OSoftSSIS2008_Client or OSoftSSIS2012_Client onthe client machine followed by the SQL Server version If you want to use SQL 2008 Tasks under the SQL 2012environment you must install OSoftSSIS2008_Client on the application server For detailed information see SAPNote 1707410 You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package byextracting OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPCInstallation folder on the Planning and Consolidation server To modify SSIS packages on the Planning andConsolidation application server you need to install OSoftSSIS2008_Client or OSoftSSIS2012_Client for creatinga COM+ application For more information see Before You Modify the SSIS Packages [page 49] and Setup ofa COM+ Application on the Application Server [page 50]
Bin folder
This folder contains the following components
46
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Table 11
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012respectively
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
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 47
Name Remark
BPCWriteBackdll
InteropDTSdll
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 addmore components to the installation package you can copy the new components into the Bin folder and add theproper xml tags in FileListxml You need to enter information for the following tags
RegistType ndash This is the registration information of the component You can enter the following values
RegAsm ndash For NET component
48
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Regsvr32 ndash For VB6 component
Gacutil ndash For NET Framework component that should be registered into Global Assembly Cache
FileName ndash Component file name
OSoftSetupexe
This is the executable file to run the SSIS installation package Double-click the file to start the installation You needto enter information for the following fields
Set SQL server
Specify the SQL server name If your SQL Server has an instance specify the instance name
NoteIf you installed the OSoftSSIS2008_Client or OSoftSSIS2012_Client on the application server the SQL servername is automatically disabled
Set server credential
This is the credential name of the COM+ package component Enter the user ID and password that can accessyour SQL Server This should be either the System Admin ID or Admin ID that was registered as a COM+ userwhen 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 ifyou 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 packagesremotely This is also true for the application server that has SSIS installed The Planning and ConsolidationData Manager has the following custom tasks
Table 12
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008and 2012 respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and2012 respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012respectively
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 49
Name Remark
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and2012 respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008and 2012 respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL2008 and 2012 respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and2012 respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012respectively
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
ltdrivegtWebsrvrbin2 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 FilesMicrosoft SQLServer paste all files into the CProgram Files (x86)Microsoft SQL Server100DTSTasksfolder
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
50
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Typographic Conventions
Table 13
Example Description
lt gt Angle brackets indicate that you replace these words or characters with appropriate entries tomake entries in the system for example Enter your ltUser Namegt
File Save Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
Example Textual cross-references to an internet address for example wwwsapcom
example Quicklinks added to the internet address of a homepage to enable quick access to specificcontent 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 titlespushbutton 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 namesof installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transactioncodes database table names and key concepts of a programming language when they aresurrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
SAP Business Planning and Consolidation 100Typographic Conventions
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 51
52
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
wwwsapcom
Material Number
- SAP Business 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 2008 R2 2012 or 2012 R2
- 344 Removing Default Access to the Console
- 345 Management Console Access Control
- 346 Configuring Planning and Consolidation to use SSL
- 347 Using Client Certificates
- 348 Configuring MS SQL Server Reporting Services to use SSL
-
- 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
-
NoteFor more information about setting up an ISA proxy server contact SAP Support to request a copy of Setting upISA Proxy Server White Paper For more information about Business Planning and Consolidation firewall portssee SAP Note 1505250
Internet Explorer Settings Issues
Internet Explorer settings must be set correctly to prevent errors and problems when you attempt to access thePlanning 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 insertthe IP address or fully qualified server name of the Planning and Consolidation server as an exception bychoosing 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
42
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Connection Issues
6 Installing Planning and Consolidation withTwo Active Directory Domains
To set up a Planning and Consolidation 10 application server in a hosted environment and use your own domainusers follow this procedure In general you install Planning and Consolidation on the host domain use the hostdomain account and assign it to the Planning and Consolidation users SysAdmin Admin and Users Then you acceptone 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 andpassword 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 topromote 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 privilegefor the Planning and Consolidation server
5 Install Planning and Consolidation and assign your domain account either to the three Planning andConsolidation administrative users SysAdmin Admin and Users or to only one of the three Planning andConsolidation administrative users and to three of your users Be sure you use your own user account ratherthan host domain users
Planning and Consolidation impersonation can then access your domain from the host environment becauseit has the privilege of your domain account
SAP Business Planning and Consolidation 100Installing Planning and Consolidation with Two Active Directory Domains
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 43
7 Installing Planning and Consolidation in aTerminal Services or Citrix ServerDeployment
This section describes best practices and instructions for installing Planning and Consolidation in a Terminal Servicesor Citrix Server deployment
71 Terminal Services Home Directories
We recommend using Terminal Server home directories rather than using the userrsquos profile directory The profiledirectory downloads a minimal amount of information about the dimensions of the environment you are logging onto and may be as large as 2 MB per user The profile directory is on the system drive and has limited space Byspecifying 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 individualserver 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 clientserver (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
44
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
Procedure
The following steps outline how to install the Planning and Consolidation clients in a Terminal Services (TS) or CitrixServer deployment
1 Make sure the Terminal Services or Citrix Server machine has the system requirements installed
2 Log on to the Terminal Services or Citrix Server machine with a user ID that has the rights to install on thatserver
3 At a command prompt enter Change userinstall
4 Open a browser and connect to the URL ltPC_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_MSBPCAdminMainexe
74 Creating a Shortcut to the Launch Page
Procedure
If you use published desktops instead of published applications the Planning and Consolidation desktop file (whichis installed on the current userrsquos desktop) must be moved to the All UsersDesktop folder
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 45
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 SQLServer 2012 support the remote modification of SSIS packages Planning and Consolidation also supports theremote 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 whichyou want to modify SSIS packages
These custom tasks reference dlls that connect to the database server and perform certain validation when usersset up the parameters of each task All the custom task reference components must also be installed in the machineon which you want to modify SSIS packages
We provide a program that registers all the reference components of the custom tasks This section explains theinstallation 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 ndash This folder contains all the dlls that should be installed on the machine There are Planning andConsolidation platform components and all of the Data Manager custom task files
Config folder ndash This folder contains only one file named Filelistxml and lists all of the files that should be installedIf you need to add or remove certain components from the installation you can modify this xml file
OSoftSetupexe ndash This is the main executable file to run the installation package
NoteIf you are not installing SSIS Custom Tasks on your client machine ndash specifically a machine other than the Planningand Consolidation application server ndash you must first install OSoftSSIS2008_Client or OSoftSSIS2012_Client onthe client machine followed by the SQL Server version If you want to use SQL 2008 Tasks under the SQL 2012environment you must install OSoftSSIS2008_Client on the application server For detailed information see SAPNote 1707410 You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package byextracting OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPCInstallation folder on the Planning and Consolidation server To modify SSIS packages on the Planning andConsolidation application server you need to install OSoftSSIS2008_Client or OSoftSSIS2012_Client for creatinga COM+ application For more information see Before You Modify the SSIS Packages [page 49] and Setup ofa COM+ Application on the Application Server [page 50]
Bin folder
This folder contains the following components
46
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Table 11
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012respectively
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
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 47
Name Remark
BPCWriteBackdll
InteropDTSdll
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 addmore components to the installation package you can copy the new components into the Bin folder and add theproper xml tags in FileListxml You need to enter information for the following tags
RegistType ndash This is the registration information of the component You can enter the following values
RegAsm ndash For NET component
48
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Regsvr32 ndash For VB6 component
Gacutil ndash For NET Framework component that should be registered into Global Assembly Cache
FileName ndash Component file name
OSoftSetupexe
This is the executable file to run the SSIS installation package Double-click the file to start the installation You needto enter information for the following fields
Set SQL server
Specify the SQL server name If your SQL Server has an instance specify the instance name
NoteIf you installed the OSoftSSIS2008_Client or OSoftSSIS2012_Client on the application server the SQL servername is automatically disabled
Set server credential
This is the credential name of the COM+ package component Enter the user ID and password that can accessyour SQL Server This should be either the System Admin ID or Admin ID that was registered as a COM+ userwhen 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 ifyou 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 packagesremotely This is also true for the application server that has SSIS installed The Planning and ConsolidationData Manager has the following custom tasks
Table 12
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008and 2012 respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and2012 respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012respectively
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 49
Name Remark
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and2012 respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008and 2012 respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL2008 and 2012 respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and2012 respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012respectively
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
ltdrivegtWebsrvrbin2 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 FilesMicrosoft SQLServer paste all files into the CProgram Files (x86)Microsoft SQL Server100DTSTasksfolder
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
50
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Typographic Conventions
Table 13
Example Description
lt gt Angle brackets indicate that you replace these words or characters with appropriate entries tomake entries in the system for example Enter your ltUser Namegt
File Save Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
Example Textual cross-references to an internet address for example wwwsapcom
example Quicklinks added to the internet address of a homepage to enable quick access to specificcontent 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 titlespushbutton 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 namesof installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transactioncodes database table names and key concepts of a programming language when they aresurrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
SAP Business Planning and Consolidation 100Typographic Conventions
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 51
52
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
wwwsapcom
Material Number
- SAP Business 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 2008 R2 2012 or 2012 R2
- 344 Removing Default Access to the Console
- 345 Management Console Access Control
- 346 Configuring Planning and Consolidation to use SSL
- 347 Using Client Certificates
- 348 Configuring MS SQL Server Reporting Services to use SSL
-
- 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
-
6 Installing Planning and Consolidation withTwo Active Directory Domains
To set up a Planning and Consolidation 10 application server in a hosted environment and use your own domainusers follow this procedure In general you install Planning and Consolidation on the host domain use the hostdomain account and assign it to the Planning and Consolidation users SysAdmin Admin and Users Then you acceptone 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 andpassword 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 topromote 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 privilegefor the Planning and Consolidation server
5 Install Planning and Consolidation and assign your domain account either to the three Planning andConsolidation administrative users SysAdmin Admin and Users or to only one of the three Planning andConsolidation administrative users and to three of your users Be sure you use your own user account ratherthan host domain users
Planning and Consolidation impersonation can then access your domain from the host environment becauseit has the privilege of your domain account
SAP Business Planning and Consolidation 100Installing Planning and Consolidation with Two Active Directory Domains
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 43
7 Installing Planning and Consolidation in aTerminal Services or Citrix ServerDeployment
This section describes best practices and instructions for installing Planning and Consolidation in a Terminal Servicesor Citrix Server deployment
71 Terminal Services Home Directories
We recommend using Terminal Server home directories rather than using the userrsquos profile directory The profiledirectory downloads a minimal amount of information about the dimensions of the environment you are logging onto and may be as large as 2 MB per user The profile directory is on the system drive and has limited space Byspecifying 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 individualserver 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 clientserver (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
44
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
Procedure
The following steps outline how to install the Planning and Consolidation clients in a Terminal Services (TS) or CitrixServer deployment
1 Make sure the Terminal Services or Citrix Server machine has the system requirements installed
2 Log on to the Terminal Services or Citrix Server machine with a user ID that has the rights to install on thatserver
3 At a command prompt enter Change userinstall
4 Open a browser and connect to the URL ltPC_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_MSBPCAdminMainexe
74 Creating a Shortcut to the Launch Page
Procedure
If you use published desktops instead of published applications the Planning and Consolidation desktop file (whichis installed on the current userrsquos desktop) must be moved to the All UsersDesktop folder
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 45
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 SQLServer 2012 support the remote modification of SSIS packages Planning and Consolidation also supports theremote 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 whichyou want to modify SSIS packages
These custom tasks reference dlls that connect to the database server and perform certain validation when usersset up the parameters of each task All the custom task reference components must also be installed in the machineon which you want to modify SSIS packages
We provide a program that registers all the reference components of the custom tasks This section explains theinstallation 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 ndash This folder contains all the dlls that should be installed on the machine There are Planning andConsolidation platform components and all of the Data Manager custom task files
Config folder ndash This folder contains only one file named Filelistxml and lists all of the files that should be installedIf you need to add or remove certain components from the installation you can modify this xml file
OSoftSetupexe ndash This is the main executable file to run the installation package
NoteIf you are not installing SSIS Custom Tasks on your client machine ndash specifically a machine other than the Planningand Consolidation application server ndash you must first install OSoftSSIS2008_Client or OSoftSSIS2012_Client onthe client machine followed by the SQL Server version If you want to use SQL 2008 Tasks under the SQL 2012environment you must install OSoftSSIS2008_Client on the application server For detailed information see SAPNote 1707410 You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package byextracting OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPCInstallation folder on the Planning and Consolidation server To modify SSIS packages on the Planning andConsolidation application server you need to install OSoftSSIS2008_Client or OSoftSSIS2012_Client for creatinga COM+ application For more information see Before You Modify the SSIS Packages [page 49] and Setup ofa COM+ Application on the Application Server [page 50]
Bin folder
This folder contains the following components
46
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Table 11
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012respectively
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
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 47
Name Remark
BPCWriteBackdll
InteropDTSdll
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 addmore components to the installation package you can copy the new components into the Bin folder and add theproper xml tags in FileListxml You need to enter information for the following tags
RegistType ndash This is the registration information of the component You can enter the following values
RegAsm ndash For NET component
48
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Regsvr32 ndash For VB6 component
Gacutil ndash For NET Framework component that should be registered into Global Assembly Cache
FileName ndash Component file name
OSoftSetupexe
This is the executable file to run the SSIS installation package Double-click the file to start the installation You needto enter information for the following fields
Set SQL server
Specify the SQL server name If your SQL Server has an instance specify the instance name
NoteIf you installed the OSoftSSIS2008_Client or OSoftSSIS2012_Client on the application server the SQL servername is automatically disabled
Set server credential
This is the credential name of the COM+ package component Enter the user ID and password that can accessyour SQL Server This should be either the System Admin ID or Admin ID that was registered as a COM+ userwhen 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 ifyou 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 packagesremotely This is also true for the application server that has SSIS installed The Planning and ConsolidationData Manager has the following custom tasks
Table 12
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008and 2012 respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and2012 respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012respectively
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 49
Name Remark
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and2012 respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008and 2012 respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL2008 and 2012 respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and2012 respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012respectively
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
ltdrivegtWebsrvrbin2 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 FilesMicrosoft SQLServer paste all files into the CProgram Files (x86)Microsoft SQL Server100DTSTasksfolder
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
50
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Typographic Conventions
Table 13
Example Description
lt gt Angle brackets indicate that you replace these words or characters with appropriate entries tomake entries in the system for example Enter your ltUser Namegt
File Save Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
Example Textual cross-references to an internet address for example wwwsapcom
example Quicklinks added to the internet address of a homepage to enable quick access to specificcontent 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 titlespushbutton 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 namesof installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transactioncodes database table names and key concepts of a programming language when they aresurrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
SAP Business Planning and Consolidation 100Typographic Conventions
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 51
52
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
wwwsapcom
Material Number
- SAP Business 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 2008 R2 2012 or 2012 R2
- 344 Removing Default Access to the Console
- 345 Management Console Access Control
- 346 Configuring Planning and Consolidation to use SSL
- 347 Using Client Certificates
- 348 Configuring MS SQL Server Reporting Services to use SSL
-
- 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
-
7 Installing Planning and Consolidation in aTerminal Services or Citrix ServerDeployment
This section describes best practices and instructions for installing Planning and Consolidation in a Terminal Servicesor Citrix Server deployment
71 Terminal Services Home Directories
We recommend using Terminal Server home directories rather than using the userrsquos profile directory The profiledirectory downloads a minimal amount of information about the dimensions of the environment you are logging onto and may be as large as 2 MB per user The profile directory is on the system drive and has limited space Byspecifying 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 individualserver 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 clientserver (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
44
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
Procedure
The following steps outline how to install the Planning and Consolidation clients in a Terminal Services (TS) or CitrixServer deployment
1 Make sure the Terminal Services or Citrix Server machine has the system requirements installed
2 Log on to the Terminal Services or Citrix Server machine with a user ID that has the rights to install on thatserver
3 At a command prompt enter Change userinstall
4 Open a browser and connect to the URL ltPC_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_MSBPCAdminMainexe
74 Creating a Shortcut to the Launch Page
Procedure
If you use published desktops instead of published applications the Planning and Consolidation desktop file (whichis installed on the current userrsquos desktop) must be moved to the All UsersDesktop folder
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 45
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 SQLServer 2012 support the remote modification of SSIS packages Planning and Consolidation also supports theremote 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 whichyou want to modify SSIS packages
These custom tasks reference dlls that connect to the database server and perform certain validation when usersset up the parameters of each task All the custom task reference components must also be installed in the machineon which you want to modify SSIS packages
We provide a program that registers all the reference components of the custom tasks This section explains theinstallation 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 ndash This folder contains all the dlls that should be installed on the machine There are Planning andConsolidation platform components and all of the Data Manager custom task files
Config folder ndash This folder contains only one file named Filelistxml and lists all of the files that should be installedIf you need to add or remove certain components from the installation you can modify this xml file
OSoftSetupexe ndash This is the main executable file to run the installation package
NoteIf you are not installing SSIS Custom Tasks on your client machine ndash specifically a machine other than the Planningand Consolidation application server ndash you must first install OSoftSSIS2008_Client or OSoftSSIS2012_Client onthe client machine followed by the SQL Server version If you want to use SQL 2008 Tasks under the SQL 2012environment you must install OSoftSSIS2008_Client on the application server For detailed information see SAPNote 1707410 You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package byextracting OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPCInstallation folder on the Planning and Consolidation server To modify SSIS packages on the Planning andConsolidation application server you need to install OSoftSSIS2008_Client or OSoftSSIS2012_Client for creatinga COM+ application For more information see Before You Modify the SSIS Packages [page 49] and Setup ofa COM+ Application on the Application Server [page 50]
Bin folder
This folder contains the following components
46
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Table 11
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012respectively
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
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 47
Name Remark
BPCWriteBackdll
InteropDTSdll
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 addmore components to the installation package you can copy the new components into the Bin folder and add theproper xml tags in FileListxml You need to enter information for the following tags
RegistType ndash This is the registration information of the component You can enter the following values
RegAsm ndash For NET component
48
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Regsvr32 ndash For VB6 component
Gacutil ndash For NET Framework component that should be registered into Global Assembly Cache
FileName ndash Component file name
OSoftSetupexe
This is the executable file to run the SSIS installation package Double-click the file to start the installation You needto enter information for the following fields
Set SQL server
Specify the SQL server name If your SQL Server has an instance specify the instance name
NoteIf you installed the OSoftSSIS2008_Client or OSoftSSIS2012_Client on the application server the SQL servername is automatically disabled
Set server credential
This is the credential name of the COM+ package component Enter the user ID and password that can accessyour SQL Server This should be either the System Admin ID or Admin ID that was registered as a COM+ userwhen 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 ifyou 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 packagesremotely This is also true for the application server that has SSIS installed The Planning and ConsolidationData Manager has the following custom tasks
Table 12
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008and 2012 respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and2012 respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012respectively
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 49
Name Remark
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and2012 respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008and 2012 respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL2008 and 2012 respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and2012 respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012respectively
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
ltdrivegtWebsrvrbin2 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 FilesMicrosoft SQLServer paste all files into the CProgram Files (x86)Microsoft SQL Server100DTSTasksfolder
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
50
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Typographic Conventions
Table 13
Example Description
lt gt Angle brackets indicate that you replace these words or characters with appropriate entries tomake entries in the system for example Enter your ltUser Namegt
File Save Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
Example Textual cross-references to an internet address for example wwwsapcom
example Quicklinks added to the internet address of a homepage to enable quick access to specificcontent 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 titlespushbutton 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 namesof installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transactioncodes database table names and key concepts of a programming language when they aresurrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
SAP Business Planning and Consolidation 100Typographic Conventions
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 51
52
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
wwwsapcom
Material Number
- SAP Business 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 2008 R2 2012 or 2012 R2
- 344 Removing Default Access to the Console
- 345 Management Console Access Control
- 346 Configuring Planning and Consolidation to use SSL
- 347 Using Client Certificates
- 348 Configuring MS SQL Server Reporting Services to use SSL
-
- 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
-
Procedure
The following steps outline how to install the Planning and Consolidation clients in a Terminal Services (TS) or CitrixServer deployment
1 Make sure the Terminal Services or Citrix Server machine has the system requirements installed
2 Log on to the Terminal Services or Citrix Server machine with a user ID that has the rights to install on thatserver
3 At a command prompt enter Change userinstall
4 Open a browser and connect to the URL ltPC_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_MSBPCAdminMainexe
74 Creating a Shortcut to the Launch Page
Procedure
If you use published desktops instead of published applications the Planning and Consolidation desktop file (whichis installed on the current userrsquos desktop) must be moved to the All UsersDesktop folder
SAP Business Planning and Consolidation 100Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 45
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 SQLServer 2012 support the remote modification of SSIS packages Planning and Consolidation also supports theremote 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 whichyou want to modify SSIS packages
These custom tasks reference dlls that connect to the database server and perform certain validation when usersset up the parameters of each task All the custom task reference components must also be installed in the machineon which you want to modify SSIS packages
We provide a program that registers all the reference components of the custom tasks This section explains theinstallation 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 ndash This folder contains all the dlls that should be installed on the machine There are Planning andConsolidation platform components and all of the Data Manager custom task files
Config folder ndash This folder contains only one file named Filelistxml and lists all of the files that should be installedIf you need to add or remove certain components from the installation you can modify this xml file
OSoftSetupexe ndash This is the main executable file to run the installation package
NoteIf you are not installing SSIS Custom Tasks on your client machine ndash specifically a machine other than the Planningand Consolidation application server ndash you must first install OSoftSSIS2008_Client or OSoftSSIS2012_Client onthe client machine followed by the SQL Server version If you want to use SQL 2008 Tasks under the SQL 2012environment you must install OSoftSSIS2008_Client on the application server For detailed information see SAPNote 1707410 You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package byextracting OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPCInstallation folder on the Planning and Consolidation server To modify SSIS packages on the Planning andConsolidation application server you need to install OSoftSSIS2008_Client or OSoftSSIS2012_Client for creatinga COM+ application For more information see Before You Modify the SSIS Packages [page 49] and Setup ofa COM+ Application on the Application Server [page 50]
Bin folder
This folder contains the following components
46
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Table 11
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012respectively
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
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 47
Name Remark
BPCWriteBackdll
InteropDTSdll
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 addmore components to the installation package you can copy the new components into the Bin folder and add theproper xml tags in FileListxml You need to enter information for the following tags
RegistType ndash This is the registration information of the component You can enter the following values
RegAsm ndash For NET component
48
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Regsvr32 ndash For VB6 component
Gacutil ndash For NET Framework component that should be registered into Global Assembly Cache
FileName ndash Component file name
OSoftSetupexe
This is the executable file to run the SSIS installation package Double-click the file to start the installation You needto enter information for the following fields
Set SQL server
Specify the SQL server name If your SQL Server has an instance specify the instance name
NoteIf you installed the OSoftSSIS2008_Client or OSoftSSIS2012_Client on the application server the SQL servername is automatically disabled
Set server credential
This is the credential name of the COM+ package component Enter the user ID and password that can accessyour SQL Server This should be either the System Admin ID or Admin ID that was registered as a COM+ userwhen 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 ifyou 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 packagesremotely This is also true for the application server that has SSIS installed The Planning and ConsolidationData Manager has the following custom tasks
Table 12
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008and 2012 respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and2012 respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012respectively
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 49
Name Remark
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and2012 respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008and 2012 respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL2008 and 2012 respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and2012 respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012respectively
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
ltdrivegtWebsrvrbin2 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 FilesMicrosoft SQLServer paste all files into the CProgram Files (x86)Microsoft SQL Server100DTSTasksfolder
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
50
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Typographic Conventions
Table 13
Example Description
lt gt Angle brackets indicate that you replace these words or characters with appropriate entries tomake entries in the system for example Enter your ltUser Namegt
File Save Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
Example Textual cross-references to an internet address for example wwwsapcom
example Quicklinks added to the internet address of a homepage to enable quick access to specificcontent 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 titlespushbutton 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 namesof installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transactioncodes database table names and key concepts of a programming language when they aresurrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
SAP Business Planning and Consolidation 100Typographic Conventions
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 51
52
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
wwwsapcom
Material Number
- SAP Business 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 2008 R2 2012 or 2012 R2
- 344 Removing Default Access to the Console
- 345 Management Console Access Control
- 346 Configuring Planning and Consolidation to use SSL
- 347 Using Client Certificates
- 348 Configuring MS SQL Server Reporting Services to use SSL
-
- 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
-
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 SQLServer 2012 support the remote modification of SSIS packages Planning and Consolidation also supports theremote 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 whichyou want to modify SSIS packages
These custom tasks reference dlls that connect to the database server and perform certain validation when usersset up the parameters of each task All the custom task reference components must also be installed in the machineon which you want to modify SSIS packages
We provide a program that registers all the reference components of the custom tasks This section explains theinstallation 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 ndash This folder contains all the dlls that should be installed on the machine There are Planning andConsolidation platform components and all of the Data Manager custom task files
Config folder ndash This folder contains only one file named Filelistxml and lists all of the files that should be installedIf you need to add or remove certain components from the installation you can modify this xml file
OSoftSetupexe ndash This is the main executable file to run the installation package
NoteIf you are not installing SSIS Custom Tasks on your client machine ndash specifically a machine other than the Planningand Consolidation application server ndash you must first install OSoftSSIS2008_Client or OSoftSSIS2012_Client onthe client machine followed by the SQL Server version If you want to use SQL 2008 Tasks under the SQL 2012environment you must install OSoftSSIS2008_Client on the application server For detailed information see SAPNote 1707410 You can find the OSoftSSIS2008_Client or OSoftSSIS2012_Client installation package byextracting OSoftSSIS2008_Clientzip or OSoftSSIS2012_Clientzip from the ltdrivegtWebsrvrWebBPCInstallation folder on the Planning and Consolidation server To modify SSIS packages on the Planning andConsolidation application server you need to install OSoftSSIS2008_Client or OSoftSSIS2012_Client for creatinga COM+ application For more information see Before You Modify the SSIS Packages [page 49] and Setup ofa COM+ Application on the Application Server [page 50]
Bin folder
This folder contains the following components
46
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Table 11
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012respectively
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
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 47
Name Remark
BPCWriteBackdll
InteropDTSdll
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 addmore components to the installation package you can copy the new components into the Bin folder and add theproper xml tags in FileListxml You need to enter information for the following tags
RegistType ndash This is the registration information of the component You can enter the following values
RegAsm ndash For NET component
48
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Regsvr32 ndash For VB6 component
Gacutil ndash For NET Framework component that should be registered into Global Assembly Cache
FileName ndash Component file name
OSoftSetupexe
This is the executable file to run the SSIS installation package Double-click the file to start the installation You needto enter information for the following fields
Set SQL server
Specify the SQL server name If your SQL Server has an instance specify the instance name
NoteIf you installed the OSoftSSIS2008_Client or OSoftSSIS2012_Client on the application server the SQL servername is automatically disabled
Set server credential
This is the credential name of the COM+ package component Enter the user ID and password that can accessyour SQL Server This should be either the System Admin ID or Admin ID that was registered as a COM+ userwhen 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 ifyou 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 packagesremotely This is also true for the application server that has SSIS installed The Planning and ConsolidationData Manager has the following custom tasks
Table 12
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008and 2012 respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and2012 respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012respectively
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 49
Name Remark
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and2012 respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008and 2012 respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL2008 and 2012 respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and2012 respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012respectively
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
ltdrivegtWebsrvrbin2 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 FilesMicrosoft SQLServer paste all files into the CProgram Files (x86)Microsoft SQL Server100DTSTasksfolder
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
50
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Typographic Conventions
Table 13
Example Description
lt gt Angle brackets indicate that you replace these words or characters with appropriate entries tomake entries in the system for example Enter your ltUser Namegt
File Save Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
Example Textual cross-references to an internet address for example wwwsapcom
example Quicklinks added to the internet address of a homepage to enable quick access to specificcontent 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 titlespushbutton 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 namesof installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transactioncodes database table names and key concepts of a programming language when they aresurrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
SAP Business Planning and Consolidation 100Typographic Conventions
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 51
52
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
wwwsapcom
Material Number
- SAP Business 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 2008 R2 2012 or 2012 R2
- 344 Removing Default Access to the Console
- 345 Management Console Access Control
- 346 Configuring Planning and Consolidation to use SSL
- 347 Using Client Certificates
- 348 Configuring MS SQL Server Reporting Services to use SSL
-
- 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
-
Table 11
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager custom task for SQL 2008 and 2012respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager custom task for SQL 2008 and 2012respectively
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
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 47
Name Remark
BPCWriteBackdll
InteropDTSdll
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 addmore components to the installation package you can copy the new components into the Bin folder and add theproper xml tags in FileListxml You need to enter information for the following tags
RegistType ndash This is the registration information of the component You can enter the following values
RegAsm ndash For NET component
48
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Regsvr32 ndash For VB6 component
Gacutil ndash For NET Framework component that should be registered into Global Assembly Cache
FileName ndash Component file name
OSoftSetupexe
This is the executable file to run the SSIS installation package Double-click the file to start the installation You needto enter information for the following fields
Set SQL server
Specify the SQL server name If your SQL Server has an instance specify the instance name
NoteIf you installed the OSoftSSIS2008_Client or OSoftSSIS2012_Client on the application server the SQL servername is automatically disabled
Set server credential
This is the credential name of the COM+ package component Enter the user ID and password that can accessyour SQL Server This should be either the System Admin ID or Admin ID that was registered as a COM+ userwhen 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 ifyou 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 packagesremotely This is also true for the application server that has SSIS installed The Planning and ConsolidationData Manager has the following custom tasks
Table 12
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008and 2012 respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and2012 respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012respectively
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 49
Name Remark
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and2012 respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008and 2012 respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL2008 and 2012 respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and2012 respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012respectively
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
ltdrivegtWebsrvrbin2 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 FilesMicrosoft SQLServer paste all files into the CProgram Files (x86)Microsoft SQL Server100DTSTasksfolder
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
50
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Typographic Conventions
Table 13
Example Description
lt gt Angle brackets indicate that you replace these words or characters with appropriate entries tomake entries in the system for example Enter your ltUser Namegt
File Save Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
Example Textual cross-references to an internet address for example wwwsapcom
example Quicklinks added to the internet address of a homepage to enable quick access to specificcontent 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 titlespushbutton 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 namesof installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transactioncodes database table names and key concepts of a programming language when they aresurrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
SAP Business Planning and Consolidation 100Typographic Conventions
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 51
52
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
wwwsapcom
Material Number
- SAP Business 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 2008 R2 2012 or 2012 R2
- 344 Removing Default Access to the Console
- 345 Management Console Access Control
- 346 Configuring Planning and Consolidation to use SSL
- 347 Using Client Certificates
- 348 Configuring MS SQL Server Reporting Services to use SSL
-
- 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
-
Name Remark
BPCWriteBackdll
InteropDTSdll
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 addmore components to the installation package you can copy the new components into the Bin folder and add theproper xml tags in FileListxml You need to enter information for the following tags
RegistType ndash This is the registration information of the component You can enter the following values
RegAsm ndash For NET component
48
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Regsvr32 ndash For VB6 component
Gacutil ndash For NET Framework component that should be registered into Global Assembly Cache
FileName ndash Component file name
OSoftSetupexe
This is the executable file to run the SSIS installation package Double-click the file to start the installation You needto enter information for the following fields
Set SQL server
Specify the SQL server name If your SQL Server has an instance specify the instance name
NoteIf you installed the OSoftSSIS2008_Client or OSoftSSIS2012_Client on the application server the SQL servername is automatically disabled
Set server credential
This is the credential name of the COM+ package component Enter the user ID and password that can accessyour SQL Server This should be either the System Admin ID or Admin ID that was registered as a COM+ userwhen 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 ifyou 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 packagesremotely This is also true for the application server that has SSIS installed The Planning and ConsolidationData Manager has the following custom tasks
Table 12
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008and 2012 respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and2012 respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012respectively
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 49
Name Remark
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and2012 respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008and 2012 respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL2008 and 2012 respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and2012 respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012respectively
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
ltdrivegtWebsrvrbin2 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 FilesMicrosoft SQLServer paste all files into the CProgram Files (x86)Microsoft SQL Server100DTSTasksfolder
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
50
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Typographic Conventions
Table 13
Example Description
lt gt Angle brackets indicate that you replace these words or characters with appropriate entries tomake entries in the system for example Enter your ltUser Namegt
File Save Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
Example Textual cross-references to an internet address for example wwwsapcom
example Quicklinks added to the internet address of a homepage to enable quick access to specificcontent 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 titlespushbutton 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 namesof installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transactioncodes database table names and key concepts of a programming language when they aresurrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
SAP Business Planning and Consolidation 100Typographic Conventions
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 51
52
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
wwwsapcom
Material Number
- SAP Business 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 2008 R2 2012 or 2012 R2
- 344 Removing Default Access to the Console
- 345 Management Console Access Control
- 346 Configuring Planning and Consolidation to use SSL
- 347 Using Client Certificates
- 348 Configuring MS SQL Server Reporting Services to use SSL
-
- 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
-
Regsvr32 ndash For VB6 component
Gacutil ndash For NET Framework component that should be registered into Global Assembly Cache
FileName ndash Component file name
OSoftSetupexe
This is the executable file to run the SSIS installation package Double-click the file to start the installation You needto enter information for the following fields
Set SQL server
Specify the SQL server name If your SQL Server has an instance specify the instance name
NoteIf you installed the OSoftSSIS2008_Client or OSoftSSIS2012_Client on the application server the SQL servername is automatically disabled
Set server credential
This is the credential name of the COM+ package component Enter the user ID and password that can accessyour SQL Server This should be either the System Admin ID or Admin ID that was registered as a COM+ userwhen 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 ifyou 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 packagesremotely This is also true for the application server that has SSIS installed The Planning and ConsolidationData Manager has the following custom tasks
Table 12
Name Remark
BPCTaskAdmindll or BPCTaskAdmin2012dll Data Manager Admin custom task for SQL 2008 and 2012respectively
BPCTaskAuditdll or BPCTaskAudit2012dll Data Manager Audit custom task for SQL 2008 and 2012respectively
BPCTaskAvailabledll or BPCTaskAvailable2012dll Data Manager System Available custom task for SQL 2008and 2012 respectively
BPCTaskCommentdll or BPCTaskComment2012dll Data Manager Comment custom task for SQL 2008 and2012 respectively
BPCTaskConvertdll or BPCTaskConvert2012dll Data Manager Convert custom task for SQL 2008 and 2012respectively
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 49
Name Remark
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and2012 respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008and 2012 respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL2008 and 2012 respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and2012 respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012respectively
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
ltdrivegtWebsrvrbin2 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 FilesMicrosoft SQLServer paste all files into the CProgram Files (x86)Microsoft SQL Server100DTSTasksfolder
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
50
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Typographic Conventions
Table 13
Example Description
lt gt Angle brackets indicate that you replace these words or characters with appropriate entries tomake entries in the system for example Enter your ltUser Namegt
File Save Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
Example Textual cross-references to an internet address for example wwwsapcom
example Quicklinks added to the internet address of a homepage to enable quick access to specificcontent 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 titlespushbutton 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 namesof installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transactioncodes database table names and key concepts of a programming language when they aresurrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
SAP Business Planning and Consolidation 100Typographic Conventions
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 51
52
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
wwwsapcom
Material Number
- SAP Business 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 2008 R2 2012 or 2012 R2
- 344 Removing Default Access to the Console
- 345 Management Console Access Control
- 346 Configuring Planning and Consolidation to use SSL
- 347 Using Client Certificates
- 348 Configuring MS SQL Server Reporting Services to use SSL
-
- 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
-
Name Remark
BPCTaskDumpLoaddll or BPCTaskDumpLoad2012dll Data Manager DumpLoad custom task for SQL 2008 and2012 respectively
BPCTaskLogicdll or BPCTaskLogic2012dll Data Manager Logic custom task for SQL 2008 and 2012respectively
BPCTaskMakeDimdll or BPCTaskMakeDim2012dll Data Manager Make Dimension custom task for SQL 2008and 2012 respectively
BPCTaskOwnershipdll or BPCTaskOwnership2012dll Data Manager Ownership Calculation custom task for SQL2008 and 2012 respectively
BPCTaskSendMaildll or BPCTaskSendMail2012dll Data Manager Send Mail custom task for SQL 2008 and2012 respectively
BPCTaskTriggerdll or BPCTaskTrigger2012dll Data Manager Trigger custom task for SQL 2008 and 2012respectively
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
ltdrivegtWebsrvrbin2 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 FilesMicrosoft SQLServer paste all files into the CProgram Files (x86)Microsoft SQL Server100DTSTasksfolder
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
50
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved
SAP Business Planning and Consolidation 100Installing SSIS Custom Tasks
Typographic Conventions
Table 13
Example Description
lt gt Angle brackets indicate that you replace these words or characters with appropriate entries tomake entries in the system for example Enter your ltUser Namegt
File Save Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
Example Textual cross-references to an internet address for example wwwsapcom
example Quicklinks added to the internet address of a homepage to enable quick access to specificcontent 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 titlespushbutton 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 namesof installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transactioncodes database table names and key concepts of a programming language when they aresurrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
SAP Business Planning and Consolidation 100Typographic Conventions
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 51
52
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
wwwsapcom
Material Number
- SAP Business 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 2008 R2 2012 or 2012 R2
- 344 Removing Default Access to the Console
- 345 Management Console Access Control
- 346 Configuring Planning and Consolidation to use SSL
- 347 Using Client Certificates
- 348 Configuring MS SQL Server Reporting Services to use SSL
-
- 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
-
Typographic Conventions
Table 13
Example Description
lt gt Angle brackets indicate that you replace these words or characters with appropriate entries tomake entries in the system for example Enter your ltUser Namegt
File Save Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
Example Textual cross-references to an internet address for example wwwsapcom
example Quicklinks added to the internet address of a homepage to enable quick access to specificcontent 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 titlespushbutton 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 namesof installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transactioncodes database table names and key concepts of a programming language when they aresurrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
SAP Business Planning and Consolidation 100Typographic Conventions
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate company
All rights reserved 51
52
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
wwwsapcom
Material Number
- SAP Business 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 2008 R2 2012 or 2012 R2
- 344 Removing Default Access to the Console
- 345 Management Console Access Control
- 346 Configuring Planning and Consolidation to use SSL
- 347 Using Client Certificates
- 348 Configuring MS SQL Server Reporting Services to use SSL
-
- 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
-
52
CUSTOMERcopy Copyright 2014 SAP AG or an SAP affiliate companyAll rights reserved SAP Business Planning and Consolidation 100
wwwsapcom
Material Number
- SAP Business 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 2008 R2 2012 or 2012 R2
- 344 Removing Default Access to the Console
- 345 Management Console Access Control
- 346 Configuring Planning and Consolidation to use SSL
- 347 Using Client Certificates
- 348 Configuring MS SQL Server Reporting Services to use SSL
-
- 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
-
wwwsapcom
Material Number
- SAP Business 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 2008 R2 2012 or 2012 R2
- 344 Removing Default Access to the Console
- 345 Management Console Access Control
- 346 Configuring Planning and Consolidation to use SSL
- 347 Using Client Certificates
- 348 Configuring MS SQL Server Reporting Services to use SSL
-
- 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
-