You are on page 1of 66

n

n




































“ ”








™ ’









“ ”

“ ” “



“ ”

“ ”

“ ”

“ ”

“ ”











“ ”

“ ”

“ ”


“ ”
“ ” “ ”

“ ” “ ”



“ ”
“ ”

“ ”
“ ”

“ ”


“ ” “
































































¸ ¸ ¸


n


n



n


n





























































¸ ¸ ¸
¸






¸
¸


¸

¸













n


n


n

n


n

















n


n











n


n



n


n

n

n

n

n

n


n






n










n

n














n

n

n

n

n

n

n

l

l



n

n

n

n



l

l

l


l

n

n

n

n

n

n








n


n





n

¸
n


n




n


n


n


n

n


n

n


n




n





n



n

n



¸

¸
¸ ¸

n















¸
¸ ¸










n





n




n




¸




























































































¸ ¸ ¸
























¸ ¸ ¸








































¸


¸










n



n

n


n



¸










n




n


n































n


n





“ ”
























n


n












n






n




n


n










¸

¸





¸




n

¸ ¸
¸













n

n

n

n

n



n

n

n

n





n

n

n



n

n


n

n



n

n





n












n

n


n


n
















n

n

n

n




n



¸
™ “ ”


n


n

¸







n


¸



n



n














n
¸ ¸
¸ ¸


n
¸




¸
¸ ¸














l




l







¸
¸ ¸










n

n







n



n


n





¸


n








n




n




n







¸


























¸






n

n




n

n

n

n

n

n














¸

























¸
n

n



n


n


n











¸















n


n






n










n

n
























¸
n

n



n


n





n








¸













¸ ¸





¸





¸


n

n


‒ ‒

n



















¸
¸ ¸ ¸
¸


¸



n

















n

n











¸


n

n

n
‒ ‒




¸






















n

n

n













¸











































¸ ¸










n

n

n




¸






















¸
¸



¸
¸










¸









¸ ¸ ¸






n


n


n


n


n




n


n


n


n












“ ”
“ ”



















” ” ” ”






































¸






















n



n



n



n



n

















¸











¸





















n

n






n


n

n

n

n

n

n

n

n

n




n


n



n



n
















¸


¸















n


n

n

n

n

n

n

n

n

n

n

n


n






n



n



n

















¸
¸ ¸ ¸

¸






¸ ¸

















¸ ¸



n



n














¸

















n

n

n








































¸ ¸ ¸ ¸
¸
























n



n

n






n



n













¸
¸


¸








n
¸ ¸
n


















n

n

n

n
















¸



n

¸
n
¸

n
¸ ¸ ¸ ¸ ¸























































¸


¸
¸

¸






n




n



n


























































n


l

l

l


n




n


n

















n


n

n

n

n
















SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +49/18 05/34 34 20 www.sap.com

© Copyright 2011 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies (“SAP Group”) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. This document was created using stylesheet 2007-12-10 (V7.2) / XSL-FO: V5.1 Gamma and XSLT processor SAXON 6.5.2 from Michael Kay (http://saxon.sf.net/), XSLT version 1.
Disclaimer

Some components of this product are based on Java™. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressively prohibited, as is any decompilation of these components. Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified or altered in any way.

2/66

PUBLIC

03/11/2011

Documentation in the SAP Service Marketplace

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

03/11/2011

PUBLIC

3/66

5 2.0 for the Default Web Site”: amended the AppCmds. In “Installing SQL Server”. setting the Osoft application pool to 64-bit. In “Prerequisites” added recommendation to install SQL 2008 SP1 cumulative update package 6. Added the recommendation of Windows Server 2008 64 bit over Windows Server 2003 64 bit in the server prerequisites.Document History The following table provides an overview of the most important document changes. In “Prerequisites” added recommendation for English international version of Windows.7 2. For detailed information. Added a clarification in “Prerequisites” of the requirement for SQL 2008 Enterprise Edition. Update to split note into two parts in “SQL Server 2005” section of “After Installing SQL Server 2005 or 2008”.NET Web and Application Servers” section to tune CMS for multiple requests.1 12/7/2009 12/11/2009 12/11/2009 First version Update to “Using Client Auto Update Program” for SP01.2 2.0 2. corrected the value for the default collation settings. and setting the XMLA application pool to 32-bit. refer to the appropriate SAP central note.1 6/15/2010 7/14/2010 3.4 2. This is the update for SP03. Version Date Description 1. Added a reference to the Product Availability Matrix in the client and server prerequisites.config Files” for Web farm and <machineKey> information in item 2.2 8/10/2010 4/66 PUBLIC 03/11/2011 . Addition to the “Configuring the Planning and Consolidation . “Setting Up ODBC Logging in IIS 7.8 12/18/2009 1/28/2009 2/12/2010 2/23/2010 3/23/2010 4/1/2010 4/23/2010 3. Update to “Modifying machine. “Installing the Operating System”: added instruction about not changing the regional setting.0 2. and removed reference to the standard edition.3 2.0 3. 2. Modified the Windows 2008 Considerations section of “Installing the Operating System” to describe separating XMLA and Osoft into two application pools.6 2. Update to prerequisites for the Administration and Office clients to include Windows 7 for SP01 and later. Modified the “Installing the Operating System” section to allow enabling 32-bit applications on 64-bit servers.

5 1/14/2011 3/11/2011 03/11/2011 PUBLIC 5/66 . In the “Introduction”. added information about IIS 7. For detailed information. Updated the “Prerequisites” section with IIS 7. reworded the collation settings information for clarity.2 4. In the “Installing the SQL Server” section. refer to the appropriate SAP central note (1512045).3 9/10/2010 In “Installing SQL Server”. 3. added information about SQL 2008 performance tuning. In “Installing the Administration Client” and “Installing the Office Client”.0 provider on the Application server to the topics “Installing the Office Client” and “Installing the Administration Client”.5.3 9/17/2010 10/8/2010 10/20/2010 11/5/2010 12/3/2010 4.12.5 information. added information about table partitioning.4 4.NET framework. Updated the “Prerequisites” and “Installing the Operating System” sections to allow for operating in 32-bit mode. updated the version information for the .1 4. Added a note about installing the Microsoft. In the “Installing the SQL Server” section.Version Date Description 3.0 4. In the “Setting Up ODBC Logging in IIS for the Default Web Site” section. This is the update for SP04.ACE. added information about virtualization.4 4.OLEDB.

. .2 2. . . . . . . . . . . .2 Chapter 2 2. . . . . . . . . . . . . . .2 3. . . . . Prerequisites . . . . . . . . . . . . . . . . . . . .8. . . Connecting to Solution Manager Diagnostics . . . . . . . . . . . . . . . SAP Notes for the Installation . . .4 3. . .6 2.3 Introduction . . . . . . . . Management Console Access Control . . . Naming Conventions . . . . . . . . . . .4 2. . . . . . . . . . . . . . . . . . . . Installing the SQL Server . . . Basic Steps .Table of Contents Chapter 1 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the Client Auto Update Program . . . .8. . . . . .8 Chapter 4 4. . . . . . . . . . . .1 2. . . .3 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the Planning and Consolidation . Removing Default Access to the Console . . . . . . . . .2 4. . . . Installing the Prerequisites ‒ Basic Steps . . . . . . . . . . . .1 3. . . . . . . . .1 4. Installing the Server in a Multiserver Configuration . . . . . . . Required Post-Installation Steps . . . . . . . . . . .8.6 3. . . . .2 2. . . Multiserver Prerequisites . . . . . . . .9 2. . . . . Setting Up ODBC Logging in IIS for the Default Web Site .1 2. . .8. . . . . . Standard and Advanced Settings . . . . . . . . . . Installing the Prerequisites . . . . . .4 2. . . . . . . Setting Up an ODBC Data Source in Windows Server 2008 . Installing on a Single Server . . . Installing Planning and Consolidation Servers . Installing the Operating System . . . . . Installing the Office Client . Service-Level Accounts . 6/66 PUBLIC 03/11/2011 .5 2. . . . . . . . . . . .8. . . . . . . . . . . . . . . . Installing Analysis Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling Management Console . . . . .NET Web and Application Servers Installing Planning and Consolidation Clients Installing the Administration Client . . . . .5 3. . .3 2. . . . . .8 2. . . . . . . . .1 1.7 2. . 9 9 10 11 11 11 14 15 16 16 18 20 20 22 24 31 32 32 34 37 37 39 40 40 42 42 43 45 49 49 51 52 After Installing Planning and Consolidation Servers . . . . . . .3 3. . . . . . . . .10 Chapter 3 3. . . . Before Starting the Planning and Consolidation Server Installation Logging on to Servers . . . . . . . . . . . . . . . . . . . . . . . . . . .5 2. Installing the Anti-Cross Site Scripting Library . .7 3. . . . . . . . .

. .4 4. . . . . . . . Terminal Services Home Directories . . . . . . . . . . . . . . . . . . . .1 7. . . . . . . . . . . . . . Customizing Client Software . . . . .2 Installing the Office Client in Unattended Mode Using SMS . . . . . . Using the Client Diagnostic Program . . . . . . .2 Chapter 6 6. . . . . . . Terminal Services Considerations for Installing Microsoft Excel . . . . System Requirements . . . . . . Installing SSIS Custom Tasks . .5 4. . Installing Planning and Consolidation . . . . . Before You Run the SSIS Custom Task Installation . . . . . . . .1 5. . . . . . . . . .4 6. . . . . . . . . . . . . . . . . . . . . . 53 54 55 57 57 57 59 59 59 59 60 60 61 61 62 03/11/2011 PUBLIC 7/66 . . . . . . . .1 6. . . . . . . . . . . . . . . . . . . . . . .2 6. . . . . . Proxy Server and Firewall Issues .6 Chapter 5 5. . . . . . . . . . . Connection Issues . The Composition of SSIS Custom Task Installation . . . . . . . Creating a Shortcut to the Launch Page . . . . . . . . . . . .4. . . . . . . . . . . . . . . . . . . . . . . .3 6. . . Checking for Open Ports . .5 Chapter 7 7. . . . . . . . . Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment . . . .

8/66 PUBLIC 03/11/2011 .

These SAP Notes contain the most recent information on the installation. n You can run your production version of Planning and Consolidation in a virtualized environment.com/instguidesEPM-BPC 7.sap. OLAP.5.1 Introduction 1 Introduction The SAP BusinessObjects Planning and Consolidation Installation Guide is intended for System Administrators who perform Planning and Consolidation server and client installations. Make sure that you have the up-to-date version of each SAP Note. see SAP Note 1098847. For more information. n Planning and Consolidation supports Load Runner for performance testing.com/notes. File. and SQL): Japanese. and French. Web. Users can also migrate their security from AD to CMS.sap. 1. which you can find in the SAP Service Marketplace at the Internet address http://service. Note If upgrading to Planning and Consolidation from an earlier version. which is available on SAP Service Marketplace at http://service. as well as corrections to the installation documentation.5 The following items are new to the installation program for Planning and Consolidation: n Planning and Consolidation supports Non-English operating systems for all servers (Application. 03/11/2011 PUBLIC 9/66 . It contains everything you need to know about installing the prerequisite components and the server and client software. The installation package contains a full installation program. n Planning and Consolidation supports Central Management System (CMS) in addition to Active Directory (AD). version for the Microsoft Platform . see the Upgrade Guide. For more information. German. see Migrating Users to the Central Management System in the Operations Guide.1 SAP Notes for the Installation Read the following SAP Notes before you start the installation. New Installation Program Features in 7.

the following naming conventions apply. Croatian.5. Turkish. <drive> 10/66 PUBLIC 03/11/2011 .5. 1.1 1. The default for this is C:/PC_MS. Variable <PC_server:port> Description Server name or IP address and port number of SAP Planning and Consolidation application location. version for the Microsoft platform SAP Planning and Consolidation 7.2 Naming Conventions In this document.5 SP04. This is the Central Note for Planning and Consolidation 7.2 Introduction Naming Conventions Important SAP Notes SAP Note Number Title Comments 1336043 SAP Planning and Consolidation 7.5.5 SP03.5 SP01.5 SP02. Service Pack 04 1401702 1426263 1475726 1512045 Additional SAP Notes SAP Note Number Title Comments 1459545 Support for Language Packs (Traditional Chinese. The drive where SAP Planning and Consolidation is installed. Service Pack 03 This is the Central Note for Planning and Consolidation 7. version for the Microsoft platform SAP Planning and Consolidation 7.5. version for the Microsoft platform This is the Central Note for Planning and Consolidation 7. Serbian) This note describes the limitations for using Turkish and Traditional Chinese.5 SP00.5. version for the Microsoft platform SAP Planning and Consolidation 7. Service Pack 02 This is the Central Note for Planning and Consolidation 7. version for the Microsoft platform SAP Planning and Consolidation 7. Service Pack 01 This is the Central Note for Planning and Consolidation 7.

2.5 Support Package available from the SAP Service Marketplace at http://service. 03/11/2011 PUBLIC 11/66 . 2. If you have a separate machine for the Web server.5. See Installing Planning and Consolidation on a Single Server [page 32]. version for the Microsoft Platform . Perform the tasks in the Before Starting the Planning and Consolidation Server Installation [page 15] section.5 M WIN32 .sap. For guidelines. including installing all prerequisites. follow the steps outlined below: 1. install the Planning and Consolidation server. see Multiserver Prerequisites [page 14] for a description of where each software component is required. Determine your server configuration. the prerequisites.5 as well as the most recent Planning and Consolidation 7. what to do before the server installation. 5.2 Prerequisites The following table describes the software you need to install before installing the Planning and Consolidation server. Note You must install both Planning and Consolidation 7. and steps for performing a server installation. Perform the steps in the section After Installing Planning and Consolidation Servers [page 37].com/instguidesepm-bpc 7.Z Index B SAP BPC FOR MICROSOFT SBOP PC 7.com/swdc Software Downloads Support Packages and Patches A . and the minimum versions required. See Installing the Server in a Multiserver Configuration [page 34]. see the SAP Planning and Consolidation Master Guide at http://service. 3.sap. 4.1 Basic Steps To install a Planning and Consolidation server. From the application server.5 FOR MICROSOFT Comprised Software Component Versions SAP CPM BPC 7. If you are installing in a multiserver environment. 2.2 Installing Planning and Consolidation Servers 2 Installing Planning and Consolidation Servers This section includes the basic steps for installing a Planning and Consolidation server. install the Web server component of the Planning and Consolidation server on that machine.

com/pam.2 2.sap. Search on Planning and Consolidation. Relational Database Microsoft SQL Server 2005 Enterprise Edition with the latest service pack and hotfix. For more information see Installing the Operating System [page 22]. Otherwise. For details. Component Minimum Requirement Operating System n SP04 or later: Windows Server 2008 R2 Standard or Enterprise Edition with or without Hyper-V n Windows Server 2008 Standard or Enterprise Edition with or without Hyper-V. see SAP Note 362379. or Windows Server 2008 Data Center with or without Hyper-V n Windows Server 2003 Standard or Enterprise Edition SP2 n Windows Server 2003 Standard configured on the SQL database or OLAP server components only n Windows Server 2003 R2 Standard or Enterprise Edition SP2 Recommendation Install the Planning and Consolidation servers on the English international version of Windows rather than on localized versions.2 Installing Planning and Consolidation Servers Prerequisites Note A list of the supported operating systems and database systems is also available in the Product Availability Matrix on SAP Service Marketplace at http://service. or Microsoft SQL Server 2008 Enterprise Edition (SP04 or later: Microsoft SQL Server 2008 R2 Enterprise Edition) with: n Microsoft SQL Server 2008 Feature Pack (Microsoft SQL Server 2005 Backward Compatibility Components) n Microsoft SQL Server 2008 SP1 cumulative update package 6 Recommendation We highly recommend SQL Server 2008 Enterprise Edition to take advantage of improved performance associated with MDX formulas. Recommendation Since all Planning and Consolidation 7. 12/66 PUBLIC 03/11/2011 . supportability is limited. SAP recommends that you enable 32-bit applications for the application pool running the Osoft application. Note The operating system must be configured with NTFS. SAP recommends using Windows Server 2008 64 bit over Windows Server 2003 64 bit.5 components require 32-bit processing.

Third-Party Tools The following software components are third-party tools that are installed: n FarPoint 4. and you do not need to download them.2 Installing Planning and Consolidation Servers Prerequisites Component Minimum Requirement OLAP Database Microsoft SQL Server Analysis Services 2005 Enterprise Edition with the latest service pack and hotfix. and Xceed Zip component must be downloaded prior to installing the server. n Dundas Chart V7.NET 2. see SAP Note number 1429246.0 and Microsoft Report Viewer 2008 SP1 are included with the installation program.0 (included in your Operating System) (SP04 or later) IIS 7. which also contains download information. Anti-Cross Site Scripting Library 3.0 SP2. or Microsoft SQL Server 2008 Enterprise Edition with n Microsoft SQL Server 2008 Feature Pack (Microsoft SQL Server 2005 Backward Compatibility Components) n Microsoft SQL Server 2008 SP1 cumulative update package 6 Microsoft SQL Server 2005 Reporting Services with the latest service pack and hotfix. For more information. but not installed automatically.0 or IIS 6.0 for ASP.0.NET 9.0 SP2 or later ADOMD.NET 3. or Microsoft SQL Server 2008 Enterprise Edition with n Microsoft SQL Server 2008 Feature Pack (Microsoft SQL Server 2005 Backward Compatibility Components) n Microsoft SQL Server 2008 SP1 cumulative update package 6 MSXML 4.NET. The server installation program asks for the path of each file and copies the files into the appropriate Planning and Consolidation path. Recommendation We recommend the installation of Microsoft SQL Server SP1 cumulative update package 6 to solve a problem with incorrect periodic values being returned with calculated accounts.0 and .5 SP1 IIS 7.0 SQL Server software components (see Multiserver Prerequisites [page 14]) . SP04 or later: AmyUni PDF Creator and Xceed Zip are included in the installation package.5 (included with Microsoft Windows 2008 R2) n AmyUni PDF Creator.2 2. n Microsoft Report Viewer 2008 SP1 n n n n n Note Reporting Services Other Requirements MSXML 4. 03/11/2011 PUBLIC 13/66 . is installed on the Web server.0. which is required for Planning and Consolidation Web. which is required for Planning and Consolidation Web.NET 9. is installed on the Web server. ADOMD.

.0 n IIS n If the application server is on a separate machine than the SQL or OLAP servers. and an OLAP DB server. The different server types can be installed on up to seven different machines. a SQL DB server. l If SQL Server 2008 is installed. We recommend a four-server environment. it must have the following configuration: For SQL Server 2005: l Integration Services l Workstation components.3 Installing Planning and Consolidation Servers Multiserver Prerequisites 2.3 Multiserver Prerequisites When the required server components are located on different servers.2 2.NET Framework 3. the following components are required on each physical machine where the server type is located: Server Type Prerequisite SQL Server OLAP server Insight OLAP server Application server n Operating system n Relational database n Operating system n OLAP database n Operating system n OLAP database n Operating system l If SQL Server 2005 is installed.5 SP1 is required. application server (application/fileshare/reporting services).NET 9. If you are installing in a multiserver environment. with a Web server.0 SP2 or later n ADOMD. and development tools l Client Component For SQL Server 2008: l Shared Features n Operating system n Operating system n IIS n Microsoft Report Viewer 2008 SP1 n Operating system n Reporting Services FileShare server Web server Reporting Services server 14/66 PUBLIC 03/11/2011 . this is considered a multiserver configuration. Books Online. Microsoft SQL Server 2008 Feature Pack (Microsoft SQL Server 2005 Backward Compatibility Components) is required. n MSXML 4.

see Installing the Prerequisites [page 20]. and that there is communication between the physical servers on which you are going to install the server types. n If you have the URLScan and IIS Lockdown tools installed on your Application server. has been updated in this version of Planning and Consolidation. By default. n Set up the required service accounts that you need to install the Planning and Consolidation server. After the installation. Web. make a copy of it before continuing with the installation. n In a multiserver environment. n The sample application set. n Make sure all required server ports are open. 03/11/2011 PUBLIC 15/66 .4 Installing Planning and Consolidation Servers Before Starting the Planning and Consolidation Server Installation 2. To convert to NTFS (from FAT). which is required. n You must determine the IP addresses or server names for all servers before installing Planning and Consolidation. verify with your network administrator which TCP ports to choose during the installation. the installing ID must be a domain user ID. n Do not install the FileShare server type on a domain controller.2 2. n If a version of Planning and Consolidation on a NetWeaver platform exists. This way you have the proper authority to install software and to modify the Component Services.4 Before Starting the Planning and Consolidation Server Installation You must perform the following tasks before starting your Planning and Consolidation server installation: n Install all the prerequisite software. See Service-Level Accounts [page 16]. and automatically overwrites the previous version of ApShell. including all of the latest Microsoft hotfixes. version for the Microsoft platform. n All users in a multiserver environment that require access to Planning and Consolidation must be domain users. you must reinstall them using the Planning and Consolidation configuration templates. We recommend that you do not log on to the servers using a local server user ID. See Checking for Open Ports [page 57].5. n Disable your anti-virus software program. See Standard and Advanced Settings [page 18]. port 80 is the setting for standard http access. For more information. ApShell. when you enable the program. n All servers in a multiserver environment must be members of the same domain. uninstall it before you install Planning and Consolidation 7. n If you access your application. and port 443 is the setting for https access. even if the user ID is a member of the Administrator group on the server. See Logging On to Servers [page 16]. you can specify it during the installation program in Advanced Settings. n Configure your server for NTFS. If you have made any modifications to ApShell that you want to keep. at a command prompt enter: convert c: fs:ntfs/V. or reporting services server components through a firewall. turn off Script Blocking. If you require a service to listen on a different port. We recommend that you use static IP addresses.

Errors may display during the installation program and in the diagnostic program if the installing user is not assigned to the Administrator group directly.com/instguidesepm-bpc 7. Install the Anti-Cross Site Scripting Library. Server\ApShell.db9). and reporting services servers. or a member of the Administrator group on the local server. If the shared folder name is not Osoft the installation fails. you must use a domain user ID to log on to all components. application. specify the location of the ApShell database file in the Server Information Advanced Options Local path for ApShell DB field (for example.2 2.5 Installing Planning and Consolidation Servers Logging on to Servers n If you are installing the FileShare server component on a separate server than the application server component. 2. from the Planning and Consolidation installation program to any folder on the SQL server (for example.6 Service-Level Accounts Service accounts are Windows domain IDs with access to all Planning and Consolidation servers with varying levels of privileges. A local server user ID is a member of the Administrator group on the server. See Installing the Anti-Cross Site Scripting Library [page 32]. which provides protection to Web-based applications n against Cross-Site Scripting (XSS) attacks. go to Server Manager on the application server. They allow the software to use the least-privileged method required for each job. but is assigned to a group with Administrator rights. n IIS must be enabled on the Web. These messages can be ignored. c:\ApShell. making it more secure.db9 (for SQL 2005 and 2008). 2. and select Server Reset Logon Credentials . c:\ApShell.5 Logging on to Servers When installing in a multiserver environment. you must reset the SQL. do the following: 1. and Web server passwords as well. application server. To do this. WORKGROUP. 2. you must change the shared folder name on the FileShare server to Osoft before the installation.5. For more information.sap. n If the application server is not able to copy files to the database server during the installation because of port access reasons (DMZ. 16/66 PUBLIC 03/11/2011 . for the Microsoft Platform . Copy the ApShell database file. During the installation procedure (on the Server Information page). or nontrusted domain authentication failures). Note If you change the password used to install Planning and Consolidation. A domain user ID is a member of the Administrator group of a domain to which the server belongs.db9). see the SAP Planning and Consolidation Operations Guide in http://service.

Close the Local Security Settings MMC snap-in. 5. displaying the error message. see How to Troubleshoot Service Startup Permissions: http://support. this ID can write to the Windows registry. and can create and remove tables in SQL. The User ID must be a member of the domain users group. and click OK. The Admin should be a member of the domain users group and the local administrators group. remove. For security purposes. When installing a service to run under a domain user account. enter user IDs and passwords for the following user types: n System Admin ID ‒ This ID is read-only and is the same as the installation user ID. they should not be used to define Planning and Consolidation users. and restore OLAP and SQL databases. Even though the system administrator account has been assigned to the server correctly.6 Installing Planning and Consolidation Servers Service-Level Accounts You must define these user IDs on the Windows machine. and can create. Add the user to the policy. the system administrator account is assigned automatically to the service during the installation of the Planning and Consolidation server program. For example.2 2. which manages the System Landscape Directory (SLD) service. right-click Log on as a service. this ID can create subdirectory access on the FileShare server. To edit the Local Security Policy of the computer for which you want to define the logon as a service permission. In the right-hand pane. read/write metadata and application set database data in OLAP. For more details. local administrators group. the service may not start. The service did not start due to a logon failure. this ID can read and write temporary files on the servers. backup. n User ID ‒ This ID allows access to code at the user level. logging service and shared query engine caches. the account must have the right to logon as a service on the local machine. Troubleshooting Planning and Consolidation 7. 4. and SQL administrators group. Start the Local Security Settings Microsoft Management Console (MMC) snap-in.5 has a new Windows service named OutlookSoft ServiceManager Service. and then click User Rights Assignment. For example. and can read metadata and data in OLAP and SQL. has write access to FileShare data. 03/11/2011 PUBLIC 17/66 . This logon right strictly applies only to the local computer and must be granted in the Local Security Policy.microsoft. has full access to the FileShare server. For example. and then click Security. Since the service should be able to access the FileShare server. perform the following actions: 1. 3. The reason for this is that the system administrator account is not registered as a service.com/kb/259733. n Admin ID ‒ This ID allows access to code that provides more limited Admin-level functionality. 2. During the installation. This ID allows access to code that provides broad system administrator-level functionality. The system administrator should be a member of the domain users group. Expand Local Policies.

Port number Insight OLAP Server Name The name of the SQL DB server. IP address. The name of the OLAP server. and fully qualified domain names (FQDN). the name refers to the NetBIOS name. The name of the reporting services server. The name of the Web server. If left blank. Standard Settings Standard settings are typically used for a single-server environment. The following table describes each setting: Server Option Value Description SQL Database server name OLAP server name Insight OLAP server name File Share server name Local data path Reporting Services server name Application server name Web server name The name of the SQL DB server. C: PC_MS Data .7 Standard and Advanced Settings The following tables describe the standard and advanced settings for the installation program. Defaults to the local server.Provider OLAP Server Name . you can change these settings using Server Manager. The default port number for the SQL Server is 1433. The default value is the name of the File Share server that should be the computer name (NetBIOS name). Advanced Settings Advanced settings are typically used in a multiserver environment. The default value is 2383.Instance name . The OLAP instance name. The following table describes each setting: Server Option Value Description SQL Server Name .2 2.Port number . Note When defining server names. the default instance is used. The instance name can be changed.7 Installing Planning and Consolidation Servers Standard and Advanced Settings 2. Where the data files are saved on the File Share server. The name of the OLAP server. 18/66 PUBLIC 03/11/2011 . The only available value is SQL. By default. The name of the application server.Instance name . Default is the local server. After the server is installed. The name of the Insight OLAP server. The name of the Insight OLAP server. The SQL instance name.

The port number to which the reporting services server connects.Instance name . Where the data files are saved on File Share server. The instance name can be changed.Port number .Local data path Reporting Services Server Name . By default. The server name for load balancing if it is installed. The default value is 2383. Note: If you have chosen SAP BusinessObjects User Management System in the installation screen. 80 is the default for http. The available values are http or https. The port number to which the application server connects.) The available values are http or https.Virtual server name . If you have multiple application servers. If you change this value from Windows to Kerberos. The name of the application server. The name of the server used for scheduling.sap.Instance name . The default value is Integrated. Windows or Kerberos. (Yes provides better performance in some situations.2 2.Website . usually the application server. The IIS Web site name.Protocol . See the Kerberos authentication settings section in the SAP Library Server Manager Guide on http://service.7 Installing Planning and Consolidation Servers Standard and Advanced Settings Server Option Value Description . 80 is the default for http and 443 is the default for https. for the Microsoft Platform . The default value is No. The default value is the name of the local server.Port number File Share Server Name . TCP/IP address for accessing the server from outside a firewall.Protocol .Port number . The default value is http. select the appropriate one. The protocol on the reporting services server. The default value is the name of the File Share server that should be the computer name (NetBIOS name). if it differs from the default Web site. The reporting services instance name. PC_MS Data .com/instguidesEPM-BPC 7. The instance name can be changed.Authentication type The Insight OLAP instance name.HTTP compression . C: The name of the reporting services server. you must make some additional changes.External server name .Authentication type Application Server Name . The default is Windows. Authentication type does not appear in Advanced settings (as that IIS authentication type is Anonymous in CMS mode).External server name . Basic. TCP/IP address for accessing the server from outside a firewall. The default value is http.5. The authentication type on the reporting services server. Scheduler Server Name Web Server Name 03/11/2011 PUBLIC 19/66 . The name of the Web server. and 443 is the default for https.

SQL services. and that their authentication models are documented (stated).) The available values are http or https.8 Installing Planning and Consolidation Servers Installing the Prerequisites Server Option Value Description .HTTP compression . 2.com/instguidesCPM-BPC 7. you must install the software in the order listed in this procedure.Authentication type TCP/IP address for accessing the server from outside a firewall. if it differs from the default Web site. The IIS Web site name. if it is installed. If you change this value from Windows to Kerberos.Virtual server name .Port number . 20/66 PUBLIC 03/11/2011 . since you need to reference this information during the installation. The server name for load balancing. Check all third-party infrastructure services to ensure that they are functioning.5. Note To ensure a successful installation. you must install the prerequisite Microsoft software: the operating system.2 2. and Active Directory (AD). Windows or Kerberos. The default is Windows.Website . you must make some additional changes.8 Installing the Prerequisites 2.80 is the default for http and 443 is the default for https Note: If you have chosen SAP BusinessObjects User Management System in the installation screen. for the Microsoft Platform .External server name . These third-party services include IIS. The default value is No. The default value is http.1 Installing the Prerequisites ‒ Basic Steps Before installing your Planning and Consolidation server. SQL server.NET. see Prerequisites [page 11]. (Yes provides better performance in some situations. analysis services. For specific versions required. IIS. The port number to which the Reporting Services Server connects.sap.Protocol . reporting services. This section provides guidance on installing each component. Authentication type does not appear in Advanced settings (as that IIS authentication type is Anonymous in CMS mode). See the Kerberos authentication settings section in the SAP Library Server Manager Guide on http://service. and MSXML. ADOMD. reporting services. OLAP service.8.

8.0 Service Pack 2 or later. see the SAP BusinessObjects Planning and Consolidation Master Guide. On your application server. install MSXML 4. 4.5 of XceedZip. 3. SP04 or later: AmyUni PDF Creator is included to the installation package.dll. you can uninstall it from your OLAP server. go to www.dll file from the SAP Cryptographic Software link on the Downloads SAP Software Distribution Center page.0 installation package is contained in the Planning and Consolidation zip file at the following location: \BPC Setup\Server\SQLServer2005_ADOMD. After the installation is complete.msi. Install the required operating system on the single-server computer or on each physical server for a multiserver configuration. and you do not need to download it. Note Planning and Consolidation Version 7. 10. From your operating system’s media. The ADOMD. See Installing Analysis Services [page 31].NET 9. install SQL Server and its required service packs and hotfixes.2 2. 6. which is required on your Web.0 SP2 installation package is contained in the Planning and Consolidation zip file at the following location: \BPC Setup\Server\msxml. You can download this file from the SAP Cryptographic Software link on the Downloads SAP Software Distribution Center page. 5. and reporting services servers. You can download the XceedZip.NET 9. If you want to use CMS for Planning and Consolidation authorization. See Installing SQL Server [page 24]. install Analysis Services Enterprise Edition and its required service packs and hotfixes.microsoft.5 for the Microsoft platform requires version 6.com. you must download and install it on its own server.) 9. SP04 or later: XceedZip is included to the installation package. 2. For more information.msi. (MSXML 4.8 Installing Planning and Consolidation Servers Installing the Prerequisites Procedure 1. install IIS. From your SQL Server media. install ADOMD. Download the AmyuniPDF. and you do not need to download it.dll file to the application and Web servers. On your application server. application. 03/11/2011 PUBLIC 21/66 . Download the XceedZip.exe file to the application server. To install this service pack.0. See Installing the Operating System [page 22].0 Service Pack 2 is part of Windows 2003 Service Pack 2. The MSXML 4. Note You can also install it on your OLAP server if you want to support alternate connections to Analysis Services. Install the latest service pack for your operating system. From your SQL Server media. 7.

or Japanese operating system.5 components require 32-bit processing.0 or 7. Turkish. As of Service Pack 03. n If your company has a policy to assign disk space to a certain drive. SAP recommends you enable 32-bit applications for the application pool running the OSoft application. but IIS 7. Croatian. Note For information about enabling Hungarian and special considerations for using Hungarian. Chinese. n Install the IIS 6 Metabase Compatibility role Planning and Consolidation uses the ADSI provider to handle IIS administration such as virtual directory and security. n Planning and Consolidation can support all servers with an English. do not change the regional setting from English (US). n Before installing the operating system.2 Installing the Operating System About Installing the Operating System n During the Windows installation. see SAP Note 1459545. If you change the setting to another language. Since Planning and Consolidation 7. Slovak. you must enable the following features: n Enable Basic Authentication and Windows Authentication. Search on Planning and Consolidation. French. Czech. these are not installed by default.5 do not install the ADSI provider by default.com/pam. see SAP Note 1329631. You can check the installation on the Web Server (IIS) pane of Windows Server Manager. and Serbian.8 Installing Planning and Consolidation Servers Installing the Prerequisites 2.8. If not. Windows 2008 Considerations If you are installing IIS 7. if you are running Windows 2008 on a 64-bit server. then follow it. make sure that you configure your server for NTFS. Planning and Consolidation also supports Traditional Chinese.5.0 and 7. we recommend you use C: for system files. Proceed as follows: 22/66 PUBLIC 03/11/2011 . Polish. and D: for data storage. or Russian version of Business Planning and Consolidation. such as C:. German. Note If you are using Window XP or Windows Server 2003. n A list of all supported language and operating system combinations is available in the Product Availability Matrix on SAP Service Marketplace at http://service.2 2.sap. Select the appropriate language in the Language for Non-Unicode Programs dropdown list within Regional and Language Options on Application servers and Web servers if you use a Japanese. unexpected errors may occur when you try to log on to some interfaces. there are limitations with the support for Traditional Chinese and Turkish. Korean.

For more information. Go to Start Control Panel Administrative Tools . and then click Add Application pool. Verify that the value of Enable 32-Bit Applications is set to True. 2. see http://support.com/kb/894435.2 2. you must install a hotfix from Microsoft. see http://support. also require a 32-bit environment.. After you have installed ASP.exe adsutil. 7. “true”. 4. then click Advanced Settings in the actions panel.NET on Windows 2003 For a single-server configuration. XML for Analysis (XMLA) services. Select the application pool that runs the OSoft application. Go to Start Control Panel Administrative Tools . Select the application pool that you created. If you need to run XMLA services in Windows Server 2008 64-bit but in a different application pool.8 Installing Planning and Consolidation Servers Installing the Prerequisites 1.NET. then click Advanced Settings in the actions panel. Windows 2003 Considerations n If a 32-bit Windows 2003 operating system has more than 4 GB of memory. n You must install ASP. Verify that the value of Enable 32-Bit Applications is set to True. 8.microsoft.microsoft. which are used for data access. Web server. 4. select . If you are running Windows 2003 on a 64-bit server. 5. Open Internet Information Services (IIS) Manager. and click OK.. For more information. See Installing ASP. Restart IIS.0. Do the following: 1. 4. 2.NET during 03/11/2011 PUBLIC 23/66 . 3. This is to allow applications that require a 32-bit environment. to run successfully.microsoft.. Start application pool immediately. 9.com/kb/834628/en. Select the Sites node and navigate to /BPC /XMLA .NET on Windows 2003 below. Enter a suitable name for the XMLA application pool. See Article 834628 at http://support. you must install ASP. Installing ASP.vbs set W3SVC/AppPools/Enable32BitAppOnWin64 Press Enter . Open Internet Information Services (IIS) Manager.com/kb/894435. reporting server (only SQL 2005) and application server on which you are installing Windows 2003 as your operating system. Change the name of the Application Pool to the name of the application pool that you created and click OK. Enter cscript. integrated pipeline mode. such as XMLA. 2. Open a command prompt and navigate to the AdminScripts directory. you must configure the XMLA application pool to run 32-bit applications. Restart IIS.NET Framework Version 2. 6. 3. then click Advanced Settings in the actions panel. Select the Application Pools node. you must enable 32-bit applications. enable 32-bit applications by doing the following: 1.NET. 3.

2 2.8

Installing Planning and Consolidation Servers Installing the Prerequisites

the server installation. If the server configuration is a Web server, ASP.NET 2.0 is not required. To install ASP.NET, perform the following steps: 1. During the Windows 2003 server installation, select Add or remove a role on the Manage Your Server dialog box. 2. Under Server Role, choose Application server (IIS,ASP.NET), then choose Next. 3. Select Enable ASP.NET, then choose Next. 4. Run Internet Information Service (IIS) Manager and go to Web Service Extensions. Check the status of ASP.NET v2.0.50727. If .NET Framework 2.0 has been installed on the application server, the status of ASP.NET v2.0 Web Service Extension is automatically set to Allowed during the Planning and Consolidation server installation (see SAP note 1306497).
Note

If ASP.NET v2.0.50727 does not exist in the list of Web service extensions, check this again after executing the SQL Server installation since SQL Server installs ASP.NET. If ASP.NET v2.0 Web Service Extension is set to Not Allowed, do the following on the application server: n Run Internet Information Service (IIS) Manager on your Application server, then allow the ASP.NET v2.0.50727 from Web Service Extensions. n Execute the following commands at a command prompt on your application server: a) Enter "cd %WINDIR%\Microsoft.NET\Framework\v2.0.50727". b) Enter aspnet_regiis.exe -ir -enable.
Note

The double quotation marks in the step above should be straight double quotes. Make sure that you run the aspnet_regiis.exe file located in .NET Framework 2.0, not 1.1. If .NET Framework 2.0 is not installed, you should install it manually or install SQL Server component first.

2.8.3 Installing the SQL Server
This section describes the general steps for installing SQL Server, component options, and considerations when installing and configuring SQL Server 2005 and 2008.
SQL Server 2005 and 2008 Considerations

n We recommend installing all required components in sequence. For example, install the Operating System (Windows Server), then enable IIS and ASP.NET and install any Windows Server service packs.

24/66

PUBLIC

03/11/2011

2 2.8

Installing Planning and Consolidation Servers Installing the Prerequisites

n We recommend that you have IIS on your application server, and .NET Framework 3.5 SP1 installed. If you install SQL 2005 without IIS, Reporting Services (RS) is not installed. If you install IIS on your Windows 2003 server, you also need to re-install all service packs related to the operating system. n To reinforce security, we recommend that you install the DB, OLAP, and Reporting Services components to a nondefault instance of SQL Server. n When you upgrade from SQL2005 to SQL2008 and you want to run Data Manager packages in your application set that were created in SQL2005, you must install both SQL Server Integrated Services for SQL2005 and SQL2008 on the Application server.
General Installation Steps

1. Launch the SQL Server Setup program, entering a product key if necessary and accepting the license terms. 2. Choose Install to install the SQL support files. 3. In Feature Selections, select instance and shared features as indicated in the SQL Server Component Options section below, then choose Next. 4. Review disc space requirements, then choose Next. 5. In Server Configuration, set Service Accounts and ensure that Collation is set to SQL_Latin1_General_CP1_CI_AS. Choose Next. 6. Set Database Engine Configuration options, then choose Next. We recommend you choose Mixed mode (Windows authentication and SQL authentication). This allows you to use a restrictive SQL ID that works with the drill-through feature. If you must restrict SQL authentication for security reasons, you can define a specific parameter in your drill-through queries. If you do not need drill-through support, or use it without leveraging SQL authentication, you can install SQL Server in Windows-only mode. 7. Accept the Analysis Services Configuration default options and the remaining default options of the installation program. 8. Choose Install to begin the installation with the options you have set.
SQL Server Component Options
For Both Single and Multiserver Installations

n You must set up Reporting Services appropriately when installing SQL Server. During the Reporting Services installation, select the Install the default configuration option to associate the default Reporting Services instance to Planning and Consolidation. If you select the Install but do not configure the server option and configure Reporting Services later, the Reporting Services instance is not associated with Planning and Consolidation.

03/11/2011

PUBLIC

25/66

2 2.8

Installing Planning and Consolidation Servers Installing the Prerequisites

Note

If you do not use the default Reporting Services instance, you cannot use the default configuration. In this case, you can use the Microsoft SQL Server Configuration Manager to create virtual directories, a database, and an application pool before installing Planning and Consolidation.
For Single-Server Installations

For single-server installations running SQL Server 2005, install the following components from the Components to Install screen: n n n n n SQL Server Data Services Analysis Services Reporting Services (see note in table below) Integration Services Workstation components, Books Online, and development tools

For single-server installations running SQL Server 2008, install the following components from the Feature Selection screen: n n n n Database Engine Services Analysis Services Reporting Services Shared Features

For Multiserver Installations

For multiserver installations, install the following components on each machine:
Server Component What to Install

SQL Server

For SQL Server 2005: n SQL Server Data Services n Integration Service n Workstation components, Books Online, and development tools For SQL Server 2008: n Database Engine Services n Shared Features For SQL Server 2005: n Analysis Services n Workstation components, Books Online, and development tools For SQL Server 2008: n Analysis Services n Shared Features

OLAP Server

26/66

PUBLIC

03/11/2011

2 2. Read Committed Snapshot You can set the SQL isolation level to be Read Committed Snapshot mode for each SQL database and for application server and application set databases. we recommend that you install Reporting Services on the application server. Books Online. Real-time MOLAP You can set the OLAP storage model of the write-back partition to be MOLAP (Multidimensional OLAP).5. You specify the SQL Server you want to use for the Reporting Services DB during installation of the application server. If you want to install and operate Reporting Services on a different machine that has SQL Server. Planning and Consolidation supports the following new features for SQL Server 2005 and SQL Server 2008. Reporting Services for SQL Server 2008 does not need to run IIS. Note Setting the SQL isolation level to be Read Committed Snapshot mode for a database can only be done once and cannot be reversed.8 Installing Planning and Consolidation Servers Installing the Prerequisites Server Component What to Install Reporting Services Server n Reporting Services Note For SQL Server 2005. The process to set the OLAP storage modes is as follows: n n n n Enable proactive caching Update the cache when data changes to 0 Reduce outdated cache latency to 0 Bring the system online immediately PUBLIC 27/66 03/11/2011 . You should set the OLAP storage model of the write-back partition after installing Planning and Consolidation (without an application set) and after restoring an application set. Application Server For SQL Server 2005: n Integration Service n Workstation components. This setting remains even during modifying and copying an application. then you must also run IIS on the server. and development tools n Client Component For SQL Server 2008: n Shared Features Custom Settings for SQL Server As of version 7.

1533). From SQL Server Management Studio. then select Connect.TCP Ports as desired (for example. then select OK. and select Properties. When prompted for the TCP/IP Properties. 1533). If you want to use a port with a named instance. The Analysis Server Properties window displays. 2724). Then choose OK. specify the client protocol options for the application server: 1. n From SQL Server Management Studio. which shows all configurable properties. 3. 2. select the server name (it should be automatically selected unless you have several instances). 2. Right-click Analysis server object (top object named instance). n From SQL Server Configuration Manager. The browser service is required for Planning and Consolidation. confirm that the SQL Server Browser service is running. set Enabled to Yes and specify the TCP Port. Delete 0 from TCP Dynamic Ports. For enhanced security. 2. see the Microsoft white paper Table Partitioning in SAP BI on Microsoft® SQL Server™ 2005/2008. 3. like for the SQL Server option. Set IPAll . For more information. Set the default port to the same port as you set for the above step (for example.microsoft. change the default value to your port number (for example. which indicates Server IP. You see two IPs that indicate the localhost and external network interface machine. then double-click TCP/IP from the right side of the window. select the server type Analysis Services. double-click TCP/IP. n From the SQL Server Configuration Manager. which you can download from www. Select Protocols for InstanceName.2 2. Select Client Protocols from the SQL Native Client Configuration folder. as desired. 28/66 PUBLIC 03/11/2011 .com (search on “Table Partitioning” to find all relevant articles). The TCP/IP Properties window is displayed.8 Installing Planning and Consolidation Servers Installing the Prerequisites n Enable notification with the SQL server after setting the tblFactWB<app> table Table Partitioning You can create a partition function and scheme but only for the fact table. If you want to use IP1. 4. Note We do not recommend using dynamic ports. After Installing SQL Server 2005 or 2008 n From SQL Server Configuration Manager. This is required so Analysis Services can process the SQL Server. This means that you use a fixed port. From the right side of the window. select IP Addresses. do the following: 1. do the following tasks: 1. open SQL Server Analysis Services Log On tab and confirm n that the user identified as the Log on as user has the sysadmin SQL Server role defined under Server Roles.

do not change the port number. choose Install the default configuration for SQL 2005 or Install the native mode default configuration for SQL 2008. 3. it creates two virtual directories and it has a non-default application pool. l Two different ASP. Select the application pool for Report Server and Report Manager. the Planning and Consolidation application is in DefaultAppPool. Connect the Report Server you installed.NET versions (1. but do not configure server. select the database. Choose OK. 4. Choose OK.8 Installing Planning and Consolidation Servers Installing the Prerequisites Note We do not support a non-default port with the default instance in this release.50727. That is. then choose Connect. Choose OK and Apply to proceed. You can select the existing application pool or create new application pool. Navigate to Database Setup. choose New and enter a database name to create. 5. Open Reporting Services Configuration Manager by choosing All Programs Microsoft SQL Server 2005 Configuration Tools Reporting Services Configuration Manager . you should configure the setting for Reporting Service Server manually through Reporting Service Configuration Manager after installing Reporting Service Server.2 2. then choose Apply. 2. You must distinguish between them after the Planning and Consolidation server installation. Choose Website and enter the Virtual Directory name. If you install Reporting Service as the default. n If you install Reporting Service Server with SQL Server. Therefore. 8. If you want to create a new database. Choose Website and enter the Virtual Directory name. enter the server name. If you want to create new application. You can skip the following instructions if Reporting Service configuration is already set: SQL Server 2005 1. Navigate to Report Manager Virtual Directory and choose New. If you want to use an existing database. 6. In this case. 7. n If you install Reporting Service Server with Install. enter the application pool name. SQL Server 2008 03/11/2011 PUBLIC 29/66 .4322 and 2. then choose OK.0.0) cannot exist on the same application pool. Navigate to Report Server Virtual Directory and choose New. you must make a new application pool in which to place the Planning and Consolidation application pool. choose New.1. Navigate to Web Service Identity. If you want to use the default instance. Note l Make sure that the application pool for Planning and Consolidation is different from the application pool of Reporting Services. users do not need to make an entry if using the default setting for Reporting Service Server.

choose Test Connection. n You must check that the ASP. Connect the Report Server you installed. n Planning and Consolidation requires Reporting Services to use the Windows account when connecting to back end databases. You can change the configuration.NET tab. you do not need to carry out this procedure. If you want to set various identities for Report Manager. 1. Set the default value of this property to twice the number of CPU cores plus the number of 30/66 PUBLIC 03/11/2011 . This white paper describes how application developers can apply query and processing performance-tuning techniques to their SQL Server 2008 Analysis Services OLAP solutions. choose Advanced. 5. 7. Navigate to Database and choose Change Database. From IIS Manager. You can change the configuration. Enter the database name and choose Next.0. Choose Apply to proceed. SQL 2008 Performance Tuning Because Microsoft SQL Server Analysis Services query and processing performance tuning is a fairly broad subject.2 2. 3. Choose an authentication type and choose Next.NET Version is set to 2. You can then install Planning and Consolidation. OLAP. If you want to set various identities. Note If you are running SQL Server 2008 without virtual directories. 2. and Reporting Services for the latest settings. 2. Microsoft has produced a white paper SQL Server 2008 White Paper: Analysis Services Performance Guide. and select Properties.8 Installing Planning and Consolidation Servers Installing the Prerequisites 1. select the Reports and ReportServer virtual directories. ensure that ASP. The key points raised in this white paper are as follows: n Threadpool\Query\MaxThreads This determines the maximum number of worker threads maintained in the querying thread pool. Open Reporting Services Configuration Manager by choosing All Programs Microsoft SQL Server 2008 Configuration Tools Reporting Services Configuration Manager . n Restart SQL. Note n The only limitation for the application pool controlling Reporting Services (2005) is to run . Choose Apply to proceed.NET Framework 2. Navigate to Report Manager URL. then choose Next. 6. Choose Create a new report server database and choose Next. 8.0. 4. Enter the server name. Navigate to Web Service URL.0. choose Advanced.NET version for the Reports and ReportServer virtual directories is set to 2. n Confirm that the installation has completed successfully by checking that there are no installation related problems on the event viewer. 9. On the ASP.

ini. back up the database that contains the repository before installing this release. you must install SQL Server Analysis Services and its required service packs and hotfixes.4 Installing Analysis Services After you install SQL Server and its required service packs and hotfixes.aspx. can be used to reserve physical memory for Analysis Services. n Long-Running Queries In multiple-user scenarios.8. follow the steps and guidelines in: http://technet. Note If you have migrated your Analysis Services repository to SQL Server. setting PreAllocate can provide a more stable memory configuration. n PreAllocate The PreAllocate setting.aspx. you should set this property to 21.com/downloads/details.8 Installing Planning and Consolidation Servers Installing the Prerequisites analysis server databases. This increase in throughput can cause a small but measurable cost to single-user queries.microsoft.) n Memory Heap Type Multiple-user throughput can be improved by using the Windows heap instead of the Analysis Services heap. To avoid slow performance when a user has more than six OLAP databases. follow the steps and guidelines in http://technet. long-running queries can starve other queries ‒ even shorter-running queries ‒ by consuming all available threads. follow the steps and guidelines in the Performance Guide for SQL 2008 at http://www. found in msmdsrv.com/en-us/library/ms143219. 03/11/2011 PUBLIC 31/66 . see SQL Server 2008 White Paper: Analysis Services Performance Guide.com.2 2.microsoft.mspx. To avoid slow performance when a user has more than six OLAP databases.aspx?FamilyID=3be0488d-e7aa-4078-a050ae39912d2e43&displaylang=en.microsoft.microsoft. With the introduction of Windows Server 2008. 2. (For example. For installations where Analysis Services coexist with other services on the same machine.90). PreAllocate has the largest impact on the Windows Server® 2003 operating system. which you can download from http://www. You can reduce the aggressiveness of how each coordinator job consumes queries by changing how each segment job is queued up. follow the steps and guidelines in the Performance Guide for SQL 2005 at http://www. To install Analysis Services for SQL 2008. To install Analysis Services for SQL2005.com/technet/prodtechnol/sql/2005/ssas2005perfguide. For more information about implementing these tuning options.microsoft. if you have four dual core CPUs and five analysis databases. memory management is much improved and setting PreAllocate has little effect.com/en-us/library/ms143219(SQL.

2.exe. Download the Anti-Cross Site Scripting Library file AntiXSSLibrary. you must download the Anti-Cross Site Scripting Library.8. 32/66 PUBLIC 03/11/2011 . take the following steps: 1. which is a minimum of two times the uncompressed size of the application set files. Log on to the server with a local server user ID or domain user ID.5 Installing the Anti-Cross Site Scripting Library Before installing Planning and Consolidation servers. which provides protection to Web-based applications against Cross-Site Scripting (XSS) attacks to have it available for the Planning and Consolidation installation program. 2.dll. then extract the files and run StartUp. For more information. 3. as appropriate. the system adds the following server components: n n n n n n SQL DB Server OLAP Server Insight OLAP Server Application Server FileShare server Web server To install Planning and Consolidation on a single server.9 Installing Planning and Consolidation Servers Installing on a Single Server 2. Save the extracted file locally. select Install on SQL 2005 or Install on SQL Server 2008. 2.com/swdc Download SAP Cryptographic Software . When you install Planning and Consolidation Server. Obtain SAP Planning and Consolidation from the Downloads SAP Installations & Upgrades area of SAP Service Marketplace.9 Installing on a Single Server When you install all Planning and Consolidation server components on a single server. 6. choose Next. 5. Exit all Windows programs. n Additional application set installations require more free disk space.sap. a step in the process requires you to identify the path to AntiXssLibrary. When you install Planning and Consolidation on a single-server. be aware of the following issues: n Make sure the server has a minimum of 800 MB of hard disk space.2 2. 4. From the Server Install screen. For more information. see Installing the Prerequisites [page 20]. Make sure all prerequisite software is installed on the server. 1. see Logging on to servers [page 16]. From the Welcome screen.DLL from the SAP Cryptographic Software download area at https://service.

exe is included to the installation package. amend this protocol accordingly. 13. choose the Advanced Settings button. from the CMS Authentication page. Specify the location and name of the following files: n AntiXssLibrary. Enter the desired information and choose Next. enter a system ID for the system landscape directory (SLD). accept the default. choose I accept the terms of the license agreement. Use a comma (. The following information is required: Field Description System name Trusted CMS name Authentication type Administrator ID Administrator password Group name CMS system name (server name:port number). From the License Agreement page. 03/11/2011 PUBLIC 33/66 . Choose Next. This group name is filtered as the default when adding a user in Planning and Consolidation Administration. If a CMS cluster name exists.9 Installing Planning and Consolidation Servers Installing on a Single Server 7. and choose Next. for example.dll (application and Web server).dll (application and Web server). After entering the CMS administrator authentication details. From the Service type accounts page. choose Next. and you do not need to install it. n To set advanced settings. 15. See Service-Level Accounts [page 16]. See Installing the Anti-Cross Site Scripting Library. Web service URL 11.dll is included to the installation package. Single server.) to separate multiple names. SP04 or later: AmyuniPDF. From the Installation Method page. SP04 or later: XceedZip.) to separate multiple names. Select the appropriate value from the list The user identifier of the dedicated administrator account Password for the administrator account Group of BusinessObjects Enterprise users who have access to the system. then choose Next. From the Server Information page (see Standard and Advanced Settings [page 18]). CMSServer:6400 CMS system name. 8. 9. and you do not need to install it. [page 32] n XceedZip. enter service-level account user IDs and passwords.exe (application server). Use a comma (. choose the desired authentication method and choose Next. use the cluster name. The default is http://<CMS name>:8080/dewbobje/ If your system is configures with an SSL protocol and a specific port. choose Next. enter the information required to log on to CMS as an administrator. If you have chosen SAP BusinessObjects User Management System in the previous screen. After defining the IDs and passwords. and choose Next. do one of the following: n Review the standard settings. n AmyuniPDF. 12. 10.2 2. 14. From the Authentication Method page.

10 Installing the Server in a Multiserver Configuration 16. It allows you to install the required server types in a variety of ways. then click the URL link on the Web Service URL page. such as http://SERVERNAME:PORT/ReportServer$INSTANCE. but you cannot install the Web server remotely. Confirm that Reporting Services is running. see Logging on to servers [page 16]. open the URL for Reporting Services. Select OK to restart. For more information. Accept the defaults or make your selections. When it is complete. 19. From the Server Install screen. 3.2 Installing Planning and Consolidation Servers 2. choose Exit. 34/66 PUBLIC 03/11/2011 . You can install the SQL.exe. You perform additional server installations if you have multiple Web or application servers. and do the following: n Select Web Server if you are installing the Web server or select Application Server if you are installing the application server. Do one of the following: n If you have SQL Server 2008. open the configuration tool for Reporting Services. select Install server on SQL Server 2005 or Install server on SQL Server 2008. This means that you might have to run the installation program at least twice: once on the application server and once on the Web server. OLAP. follow these steps: 1. The Application Server option allows you to install the other components. A prompt is displayed to restart your computer. as appropriate. To install Planning and Consolidation in a multiserver configuration. choose Next. then extract the files and run StartUp.10 Installing the Server in a Multiserver Configuration A multiserver installation is the most flexible installation option. The Data files include Webfolders and FileDB (published reports) and should be installed on a separate drive in a production environment. Note Do not run StartUp. 18. 4. The installation process takes a few moments. You can also choose to install the Sample Application set. n If you have SQL Server 2005. Obtain SAP Planning and Consolidation from the Downloads Support Packages and Patches area of SAP Service Marketplace. as well (SQL DB.exe directly under the Server or Upgrade folder. 2. 6. then choose Next. select Custom multiserver. From the Welcome screen. Select destination folders for Programs and Data. 2. 17. OLAP. Log on with a domain user ID to the server where you are installing the application server. 5. Perform the steps in After Installing Planning and Consolidation Servers [page 37]. and FileShare types remotely from the application server. File). From the Installation Method page.

Enter the desired information and choose Next (see Standard and Advanced settings [page 18]).10 Installing the Server in a Multiserver Configuration Note Install the sample application set on only one application server if installing multiple application servers. This group name is filtered as the default when adding a user in Planning and Consolidation Administration. The default is http://<CMS name>:8080/dewbobje/ If your system is configures with an SSL protocol and a specific port. n Choose the Advanced Settings button. enter service-level account user IDs and passwords (see Service-Level Accounts [page 16]). Specify the location and name of the following file: n AntiXssLibrary. 7. Select the appropriate value from the list The user identifier of the dedicated administrator account Password for the administrator account Group of BusinessObjects Enterprise users who have access to the system. 12. which includes default security settings and templates. You need the sample application set. to create new application sets.dll is included to the installation package. After defining the IDs and passwords. From the Server Information page. and you do not need to install it. and choose Next. Use a comma (. If a CMS cluster name exists.2 Installing Planning and Consolidation Servers 2. enter the information required to log on to CMS as an administrator. From the Service type accounts page. choose the desired authentication method and choose Next. 03/11/2011 PUBLIC 35/66 . use the cluster name. SP04 or later: Xceedzip. do one of the following: n Review the standard settings.dll (application and Web server). From the Authentication Method page.) to separate multiple names. amend this protocol accordingly. See Installing the Anti-Cross Site Scripting Library. The following information is required: Field Description System name Trusted CMS name Authentication type Administrator ID Administrator password Group name CMS system name (server name:port number). from the CMS Authentication page. 13. choose Next. 11. choose Next. Use a comma (. If you chose SAP BusinessObjects User Management System in the previous screen. n Enter a system ID for the system landscape directory (SLD).) to separate multiple names. After entering the CMS administrator authentication details. CMSServer:6400 CMS system name. Web service URL 9. 8. for example.dll (application and Web server). n Choose Next. 10. [page 32] n Xceedzip.

Install Web servers on their physical machines. 36/66 PUBLIC 03/11/2011 .exe is included to the installation package.10 Installing the Server in a Multiserver Configuration n AmyuniPDF. install them on a separate drive in a production environment. The installation process takes a few moments. 17. 16. Perform the steps in After Installing Planning and Consolidation Servers [page 37]. When complete. The Data files include Webfolders and FileDB (published reports). 14. then choose Next. Choose Next. choose Exit.2 Installing Planning and Consolidation Servers 2. Accept the defaults or make your selections. Select destination folders for the Programs and Data.exe (application server). and you do not need to install it. SP04 or later: AmyuniPDF. 15.

7. Configure custom ODBC logging for the default Web site. n The Primary Administrator can continue with the next step (9). 03/11/2011 PUBLIC 37/66 . Configure the Planning and Consolidation .5. 8.NET Web and application server to ensure that it and its related services function properly and reliably. see Setting Up ODBC Logging in IISfor the Default Web Site [page 40]. 5. See Setting Up an ODBC Data Source [page 42]. continue with step 9.3 After Installing Planning and Consolidation Servers 3 After Installing Planning and Consolidation Servers 3. For more information. see Removing Default Access to the Console [page 42]. n If you want to designate someone other than the system administrator to define security and application structure. See Connecting to Solution Manager Diagnostics [page 39]. 3. By default. create an SQL user. log on to ApShell. 2. This user must have Administration ‒ Appset and Security ‒ Define User task rights. For details of how to configure custom logging for ODBC in IIS 7. 6. manually set up an ODBC data source for the Management Console.0 or 7. users in Active Directory can access the Management Console with whatever rights they have been granted on the server. Take the following steps to set up security: n If you are defining security and application structure. see Configuring the Planning and Consolidation . so they can add and delete application sets and define user security. We recommend that you only grant Management Console access to system administrators. Connect your Planning and Consolidation system to Solution Manager Diagnostics (SMD) to allow our support staff to identify. and resolve problems with your application. For more information. see Management Console Access Control [page 43]. then designate a user as a Primary Administrator. 4. For information about removing default access and creating a group that can access the console. For Windows Server 2008 only. Planning and Consolidation users should not have any access. analyze.1 Required Post-Installation Steps You must follow these steps after installing the Planning and Consolidation servers for new installations as well as when upgrading from earlier versions of Planning and Consolidation: 1.NET Web and Application Servers [page 45]. Add authorized users or groups to the group that can access the Management Console. See Enabling Management Console [page 40]. Modify the default access rights to the Management Console. and modify the System DSN and IIS to reflect those user credentials. To ensure proper functioning of the Management Console.

Log on to Planning and Consolidation for Excel client as an Administrator. 11. d) Exit Planning and Consolidation for Excel client. the Send Governor service fails to start until the COM+ service has been started. 38/66 PUBLIC 03/11/2011 . This occurs because Send Governor has a service-level dependency that is not set during the installation. You can install the Office clients on individual users’ machines. the OutlookSoft Insight Service must be set to Automatic. In addition. you may notice that during the reboot of the system. Verify this and make the change.microsoft. click OK. 13.) 16. (You must complete this step. 10. and add users (or teams) to one or more member access profiles.3 3. If you want to use Insight after installing Planning and Consolidation for the first time or if no application sets have Insight enabled. When the Update Complete message displays. and do the following: a) From the launch page. and select Manage Application Sets from the action pane. Select Connection Wizard. and log on to ApShell. since there is no access to dimensions or members.com/?Kbid=193888. Start Planning and Consolidation Administration from the launch page. create a dependency by adding a multistring value registry setting named DependOnService with the value COMsysApp at the following location: HKLM\System\CurrentControlSet\Services\OSoftSendGovernor. Follow the prompts to install the client software. Create a new application set using ApShell as the source.1 After Installing Planning and Consolidation Servers Required Post-Installation Steps 9. or users can install them (if they have Administrator rights on their machines). For more information about how to delay Windows services. Log on to the newly-created application. open the Client Software Center page. log on to Planning and Consolidation for Excel client with the Planning and Consolidation Administrator ID. (You must set up task profiles since there is no access to Planning and Consolidation tasks. 17. After you update security. 15. c) After you complete the installation. 12. see http://support.) 14. See Installing the Administration Client [page 49]. you must create the dimension files on the server. Set up your member access profiles. and set up users. within Administrative Tools Services on the Application server. teams. and task profiles. From the machine on which you administer Planning and Consolidation. To resolve this manually. b) Select Planning and Consolidation for Office client. and before users access the system. note the following: n After you install the Planning and Consolidation server. 18. Create a financial-type application with at least one secured dimension (this is typically the Entity dimension). install the Administration client. if necessary.

Note Installation files for Diagnostics Agent are available on Service Marketplace by navigating to Support Packages and Patches — Entry by Application Group SAP Technology Components SAP SOLUTION MANAGER SAP SOLUTION MANAGER 7. then choose Properties. Set up your system for Diagnostics.xml file located at C:\Windows\system32\inetsrv\. b) Create a new user. then select Databases Security Logins . h) Select Server roles. Procedure 1. g) Select New Login and enter the user you created previously. you can edit the metabase. select Add.2 After Installing Planning and Consolidation Servers Connecting to Solution Manager Diagnostics Note To allow users to request and query large amounts of data.2 Connecting to Solution Manager Diagnostics The diagnostics functions in SAP Solution Manager allow identification. analysis. you must create a user account with sufficient rights on all Windows Servers where Microsoft SQL Server is installed. c) Right-click on the user.0 EHP 1 Entry by Component Agents for managed systems DIAGNOSTICS AGENT 7. 3. 03/11/2011 PUBLIC 39/66 . This procedure provides the steps required to connect Planning and Consolidation to Solution Manager Diagnostics. e) Log on to Microsoft SQL Server Management Studio. select sysadmin. On the Member Of tab.3 3. f) Right-click on the user. then select Action New User .11 . To access the DBA Cockpit. and resolution of problems. ensuring that Windows Authentication is set. Install the Diagnostics Agent according to SAP Note 1234387 on all servers where Interface for the Web and application servers are installed. Do the following: a) Start Computer Management. Download an installation file based on one of the following system landscapes: n Windows Server on IA32 n 32‒bit Windows Server on IA64 n 64‒bit Windows Server on x64 64‒bit 2. Set the following parameters to the stated values: n ASPBUFFERINGLIMIT = 10485760 n MAXREQUESTENTITYALLOWED = 10485760 3. then choose OK. d) Add the group SQLServer<Release>SQLAgentUser$<Domain or hostname>$MSSQLSERVER.

After you reinstall Planning and Consolidation. 3.5 for the default Web site. 3. Give the db_Owner database role to the user for AppServer database. Restart IIS. modify the Active Log Format option to use ODBC Logging.3 Enabling Management Console To ensure proper functioning of the Management Console. Create a Microsoft SQL Server user to access AppServer as the default database. and follow the chapters that apply to Planning and Consolidation. How to configure ODBC logging in IIS. 40/66 PUBLIC 03/11/2011 .0 or 7. set the field back to ODBC Logging and reset the DSN entries as outlined above. 5. 3.3 After Installing Planning and Consolidation Servers Enabling Management Console Refer to End-to-End Root Cause Analysis System Landscape Setup Guide.sap. which is available on Service Marketplace at https://service. Setting the Log File Format and customLogPluginClsid You must set the log file format and log plug-in ID for ODBC logging. Enter the Microsoft SQL Server user information in the BPC_ManagementDSN system DSN in DataSource (OBDC). Change the Microsoft SQL Server authentication mode to SQL Server and Windows Authentication mode 2. 4. we recommend that you reset the Active Log Format field in IIS to W3C Extended Log File Format. After you uninstall Planning and Consolidation.3 3. In the IIS web site of the Planning and Consolidation application server.4 Setting Up ODBC Logging in IIS for the Default Web Site This procedure describes how to configure custom logging for ODBC in IIS 7. Enter the following values: n DSN is BPC_ManagementDSN n Table is BPCLog n The Microsoft SQL Server Username and Password. Note Without these updates. the Management Console does work. but some functionality (specifically User Activity and Service Status) does not work as expected.com/~sapidb/011000358700000074392009E. Prerequisites ODBC logging has been configured according to the Microsoft Knowledge Base article 245243. you must do the following: 1.

in the property customLogPluginClsid.webServer> </location> Use the following AppCmds to configure these attributes for the default Web site: appcmd set config "Default Web Site" /section:odbcLogging /dataSource:"ODBCLogging" /commit:appHost appcmd set config "Default Web Site" /section:odbcLogging /tableName:"ODBCLogTable" /commit:appHost appcmd set config "Default Web Site" /section:odbcLogging /userName:"Username" /commit:appHost appcmd set config "Default Web Site" /section:odbcLogging /password:"mypassword" /commit:appHost 03/11/2011 PUBLIC 41/66 .config to contain the database table information.4 After Installing Planning and Consolidation Servers Setting Up ODBC Logging in IIS for the Default Web Site Note In IIS 6.config You must configure ApplicationHost.0.0.0 or 7.3 3. the log plug-in ID property was LogModuleId.customLogPluginClsid:"{FF16065B-DE82-11CF-BC0A-00AA006111E0}" appcmd set site /site.webServer>. you must use the same value as for IIS 6.webServer> <odbcLogging dataSource="ODBCLogging" tableName="HTTPLog" userName="Username" password="mypassword" /> </system. for IIS 7.XML might already contain this property. with the value {FF16065B-DE82-11CF-BC0A-00AA006111E0}. as shown here: <logFile customLogPluginClsid="{FF16065B-DE82-11CF-BC0A-00AA006111E0}" logFormat="Custom" /> You use the following AppCmds to configure IIS to use ODBC logging for the default Web site: appcmd set site /site.config. You configure these settings in the <odbcLogging> node under <system. You can find this in the <logFile> node in ApplicationHost.name:"Default Web Site" /logFile. The file Metabase.name:"Default Web Site" /logFile. In this procedure.5. You must set the logFormat to Custom. as set up in the Microsoft Support article specified in the Prerequisites section.logFormat:"Custom" Configuring ODBC Logging Parameters in ApplicationHost. Example <location path="Default Web Site"> <system. but set it in the file ApplicationHost.config.

Choose the Next button. Proceed as follows: 1. 42/66 PUBLIC 03/11/2011 . 5. 3. see the Microsoft Knowledge Base article 931202. Leave default settings. You must use the SQL Server ODBC driver. 3. Choose the OK button. Leave the default settings. n Choose the Finish button. 6. enter the name of your SQL Server. which is a member of the Administrator group. and choose the Next button. In the Server field. Note In Windows Server 2003. and choose the Next button. Choose the Change the default database to field and enter AppServer. The requirements for using the ODBC logging feature in IIS.3 3. 4. add a new DSN: n Choose the Add button.6 Removing Default Access to the Console Note If you have chosen SAP BusinessObjects User Management System in the installation screen.5 After Installing Planning and Consolidation Servers Setting Up an ODBC Data Source in Windows Server 2008 Note You cannot configure ODBC logging in IIS using the SQL Native Client ODBC driver. 7. you do not need to remove or configure access because the Management Console service always runs with the System Admin ID account. Choose the Next button. In the Name and Description fields. n Choose SQL Server as the driver. In Windows Server 2008. On the System DSN tab page. you must manually create the ODBC data source for the Management Console. For more information. 2. 3.5 Setting Up an ODBC Data Source in Windows Server 2008 This procedure describes how to set up an ODBC data source for the Management Console in Windows Server 2008. the ODBC data source setup is created in the Planning and Consolidation installation process. Open ODBC Connection Manager. enter BPC_ManagementDSN. 8.

1. Click Create. choose Services and Applications Internet Information Services Web Sites Default Web Sites Management Console . Note Create your Management Console administrative group either on the server that hosts the Management Console or in the Active Directory. choose Permissions. Note This step is a necessary precursor to the completion of this procedure. Remove access to the Management Console from all groups that should not have it. 3. 9. you can perform analogous steps in Active Directory. In the Security dialog box. 3. Click Advanced. 4. 10. 11. For information about creating this group. In the Management Console context menu. choose Manage. use the procedure described below. and add the group you created earlier in this procedure. 8. On the Permissions tab. 5. 2. In the Computer Management dialog box. Alternately. In the Computer Management dialog box.7 After Installing Planning and Consolidation Servers Management Console Access Control Procedure To remove default access to the Management Console and create a group that does have access to the console. Click Add. you can add users or groups to it. see Removing Default Access to the Console [page 42]. 7. but it contains no data or menu options (this does not affect the access that a user would otherwise have to Planning and Consolidation).7 Management Console Access Control After establishing the Management Console group. Their rights in Active Directory determine what they can access in the Console. click Copy (to ensure that the System group retains its privileges). 6. choose New Group. In the context menu of the server’s My Computer icon.3 3. deselect the Allow inheritable permissions from the parent to propagate to this object and all child objects. Result Users who have not been granted access to the Management Console can still open the Management Console Web page. Enter data as required. 03/11/2011 PUBLIC 43/66 . choose Local Users and Groups Note Groups . In the Groups context menu. Include these with entries explicitly defined here checkbox.

see the SAP Library Planning and Consolidation Administration Guide in http://service.3 3. any member of the Administrators Active Directory group on the application server or domain will have full access to all of the features of the Console except the Planning and Consolidation logging area. 44/66 PUBLIC 03/11/2011 .sap. you can add or remove the following privileges from the areas described in this table: Privilege Task Manager and Kill Process Performance Monitor Counters Rights Management Area Administrators group on application server or domain n Administrators group on application server or domain n Power Users group on application server or domain n Performance Monitor Users group on application server n Administrators group on application server or domain n SQLServer2005MSOLAPUser* group on database server n Administrators group on application server or domain n SQLServer2005MSSQLUser* group on database server n Administrators group on application server or domain n SQLServer2005MSSQLUser* group on database server Note Microsoft Analysis Services performance monitoring Microsoft SQL Server Monitoring (performance counters and statistics) Web Server section Web server statistics are pulled from the database. The user must be granted WebAdmin task privileges. You may wish to create several levels of Console users (read-only users. version for the Microsoft platform .com/instguidesepm-bpc 7. for example) in your environment.5. the user must have permission to SQL in order to access the data from the IIS log table. Your IT policy determines whether you grant access by group or user. As such. For more information. To grant or limit access to users or groups.7 After Installing Planning and Consolidation Servers Management Console Access Control By default. Access to Planning and Consolidation logging is controlled within the Planning and Consolidation Administration Console task security.

microsoft. which is located in the \Program Objects\Tomcat55\conf directory 2.0.com/en-us/library/ms998310. this attribute has the default value of 200.com/en-us/library/7w2sway1. You can set this attribute to True or False. Open the server. see http://msdn.config (for all Web applications. If you are using a Web farm.config file of each Web server as follows: <connectionManagement> <add address=”app server ip” maxConnection=”48”/> <add address="*" maxconnection="2"/> </connectionManagement> Optimization Tasks When Using CMS Authentication If you use CMS for Planning and Consolidation authorization.aspx. Tomcat maxThreads represents the maximum number of request processing threads that can be created by the HTTPConnector.config file.microsoft. For more information. you can optimize the CMS configuration to run large requests or large numbers of concurrent users. see http://msdn.config (for just the Planning and Consolidation application) or Machine. including Planning and Consolidation) to ensure the validationKey and decryptionKey keys have the same value on all Web.com/en-us/library/ms998288. adjust HTTP TCP/IP connections settings in the machine. when the authentication cookie is checked.NET Web and Application Servers 3. This way.NET 2.config supports the attribute autoConfig to specify whether to automatically configure settings to achieve optimal performance based on the machine configuration.xml file as follows: 1. In .xml file. If not specified. You optimize the CMS configuration by modifying the server. Locate the statement: 03/11/2011 PUBLIC Files\Business 45/66 . 1.aspx #paght000007_webfarmdeploymentconsiderations and http://msdn.0. For more information.3 3.NET\Framework\v2. For a deployment where the Web servers do not reside on the same servers as the Application servers.config Files To ensure that the right balance is struck between the number of threads “working” requests and deadlock occurrences that would cause the application server to “sleep” and not process anymore.50727\Config\ directory. the processModel element in machine.8 After Installing Planning and Consolidation Servers Configuring the Planning and Consolidation . the authentication ticket used on one Web server can still be valid on another server.8 Configuring the Planning and Consolidation . This determines the maximum number of simultaneous requests that can be handled. 2. or application. you can modify the machine. and sample Visual Basic code for how to generate random key values. you must change the <machineKey> tag in Web.aspx. which resides in the \WINDOWS\Microsoft.NET Web and Application Servers Modifying machine. servers.microsoft. 3.

5-doc/config/http. and expand Application pools. you configure Internet Information Services (IIS) to restart a worker process in an application pool so that it is recycled after using a set amount of memory. enter 1800 (the maximum amount). maxSpareThreads 4 For more information. then on the Pooling & Recycling tab. 4. Right-click the application. 1. Setting Memory Recycling in the IIS Application Pool To run large requests. From the Recycling tab.html. Setting COM+ Object Application Pooling Pool Size For load balancing purposes. To configure a worker process to be recycled.NET Web and Application Servers <Connector URIEncoding="UTF-8" acceptCount="100" connectionTimeout="20000" disableUploadTimeout="true" enableLookups="false" maxHttpHeaderSize="8192" maxSpareThreads="75" maxThreads="150" minSpareThreads="25" port="8080" redirectPort="8443"/> 3. change the application pool size to 5. The connector also ensures that there are this number of idle threads available. Right-click the application pool that contains the Osoft virtual directory. and then select OK. 46/66 PUBLIC 03/11/2011 . The number of request processing threads that are created when the connector is first started. 2.apache.3 3. K2Processing. 2. and OsoftDataService. Start Internet Information Services (IIS) Manager on the Application server. take the following steps: 1. 3. maxSpareThreads should be smaller than maxThreads. Choose Properties. set the application pooling pool size for the COM+ components Everest Update.org/tomcat-5. choose Maximum used memory (in megabytes). This determines the maximum number of simultaneous requests that can be handled. OSoftSystemConfig. Modify the values of maxThreads and maxSpareThreads according to your requirements and the following definitions Parameter maxThreads Default Definition 200 The maximum number of request processing threads that can be created by this connector. Expand the local computer. 3. see http://tomcat.8 After Installing Planning and Consolidation Servers Configuring the Planning and Consolidation . then select Properties. Choose Start Administrative Tools Component Services COM+ applications .

.50727/CONFIG/"> <ConfigStore Name="machine.config" Type="xml" Alias="OSoft Config" /> </ConfigStores> n <ConfigStores Path="Websrvr/Web/"> <ConfigStore Name="Web.NET/Framework/v2.3 3.NET/Framework/v2. the system can handle between 2.com/technet/prodtechnol/WindowsServer2003/Library/IIS /1eee28e2-b319-4b4e-8267-a8c0aa0dcf36./WINDOWS/system32/inetsrv/"> <ConfigStore Name="MetaBase. By changing this setting.mspx?mfr=true Stored Configuration Values The installation process modifies the following values: Application Server Registry Entries n <ConfigStores Path=".0.config" Type="xml" Alias="Web Config" /> </ConfigStores> Web Server Registry Entries <Path Name="C:/WINDOWS/system32/inetsrv/" /> <ConfigStore Name="MetaBase.xml" Type="xml" Alias="OSoft Install" /> </ConfigStores> n <ConfigStores Path="Websrvr/bin/"> <ConfigStore Name="OutlookSoft. 03/11/2011 PUBLIC 47/66 . destination.dll" Type="jardll" Alias="BPC DLLs" /> <Path Name="Websrvr/Web/" /> <ConfigStore Name="Web.microsoft. and post) used in your logic calculations.config" Type="xml" Alias="Web Config" /> <Path Name="Websrvr/bin/" /> <ConfigStore Name="bin/*dll" Type="jardll" Alias="BPC DLLs" /> <ConfigStore Name="OutlookSoft.config" Type="xml" Alias="BPC Config" /> Setting 3GB Support for Memory on the COM+ Object You can change a COM+ setting so the system can handle large data regions (source.5 million and 3.config" Type="xml" Alias="Machine Config" /> </ConfigStores> n <ConfigStores Path="Server Management/"> <ConfigStore Name="OSoftInstall.xml" Type="xml" Alias="IIS Metabase" /> <Path Name="C:/WINDOWS/Microsoft.5 million records for each data region in the memory of the application server./WINDOWS/Microsoft..xml" Type="xml" Alias="BPC Install" /> <Path Name="Websrvr/bin/" /> <ConfigStore Name="*.xml" Type="xml" Alias="IIS MetaBase" /> </ConfigStores> n <ConfigStores Path=".NET Web and Application Servers See http://www.0.config" Type="xml" Alias="Machine Config" /> <Path Name="Server Management/" /> <ConfigStore Name="OSoftInstall.8 After Installing Planning and Consolidation Servers Configuring the Planning and Consolidation .50727/CONFIG/" /> <ConfigStore Name="machine.

Do the following: 1. 48/66 PUBLIC 03/11/2011 .3 3. Open the Advanced tab. 3. Note Changing this setting is a potential solution if you receive an Out of memory exception error while running logic. Select the Enable 3GB support option. 5. then click OK.NET Web and Application Servers The actual number that your system can handle is based on number of dimensions and member ID lengths in the application set from which you are performing logic calculations. 2. Open Component Services on the application server. the number of records that can be supported decreases. Choose the Everest Update component in COM+ Applications tree. For example. 4. as the number of dimensions increases in an application set.8 After Installing Planning and Consolidation Servers Configuring the Planning and Consolidation . Open the Properties menu using the right-click menu.

0 SP1 n XML 4. budgeting. which is used to move data between external systems and Planning and Consolidation. publishing.0. Planning and Consolidation Administration and Planning and Consolidation for Office.0 SP2 (included with the Internet Explorer software) n Pentium IV (1 GHz CPU) n 512 MB RAM n 100 MB of free hard disk space in the My Documents folder n 20 MB of free hard disk space for the installed Administration files 03/11/2011 PUBLIC 49/66 .NET Framework 2.4 Installing Planning and Consolidation Clients 4 Installing Planning and Consolidation Clients The client components. and administer security. 8. including maintenance of your business logic and business process flows. can be installed separately or together. The Office component includes Data Manager. It also has many other functions. Search on Planning and Consolidation.1 Installing the Administration Client Prerequisites The following list describes the minimum software requirements: n A list of all supported operating systems is available in the Product Availability Matrix on SAP Service Marketplace at http://service. Note n You must update the Administration and Office components to the same version as the server. the Planning and Consolidation Launch page does not display.0. and other user tasks. you must set the Internet Explorer Security Zone value of the Planning and Consolidation client to prompt for user name and password. n Microsoft Internet Explorer 7. Otherwise. n If your PC is on a different domain than your server. The installation of the Planning and Consolidation Administration component allows administrators to build and maintain Planning and Consolidation application sets and applications.sap.com/pam. The Planning and Consolidation for Office client component is used for all reporting. or later n Microsoft Office 2003 or 2007 n SP04 or later: Microsoft Office 2010 (32‒bit only) n . 4.

To install the Administration client: 1. Select the language in which you want to see the user interface. Wait while the installation wizard verifies your prerequisites. 8.1 Installing Planning and Consolidation Clients Installing the Administration Client n XceedZip.5). you can use Client Auto Update and uninstallation is not necessary. Select Administration Client Installation. Point your browser to Planning and Consolidation Web at http://<PC_server:port>/osoft. 2. Procedure The following procedure describes how to install the Administration client onto an administrator’s machine from Planning and Consolidation Web. n For the software to function correctly in Excel 2007. The components must be installed on the Application server. which you can download from the Microsoft web site.OLEDB.dll (version 6. select Next. you must install the Microsoft Office 2007 system driver Data Connectivity Components. From the installation wizard. Log on to the machine as a member of the local Administrators group.com/windowsupdate/v6/default. Uninstall any previous versions of the Planning and Consolidation Administration client. then select I accept the terms of the license agreement and click Next.microsoft.4 4. n We recommend that you install all of the latest Microsoft Windows hotfixes prior to installing the Administration client. (Use Add/Remove Programs in the Windows Control Panel. 5.0 onwards. For information about which hotfixes to install. 7. Note n In order for the software to function correctly in Excel 2007. from Planning and Consolidation version 7. Select Next to install the program to the default location. then select Next. 6. 10. Choose Finish.0 or later is installed. you must install the Microsoft.) However.aspx?ln=en-us.0 provider. 3. Note If Planning and Consolidation 7. which you can get from the Microsoft Web site. See Using the Client Auto Update Program [page 52]. 9. You must install the provider on the Application server.12. 50/66 PUBLIC 03/11/2011 . Select the Client Software Center link or icon from the Planning and Consolidation Launch page. see http://update. SP04 or later: This file is included as part of the installation package. 4. then select Next.ACE. you can also use Client Auto Update to install the client.

5 unless you download and install the shared add-in support update for the Microsoft . For information about which hotfixes to install.0 (KB907417). SP04 or later: This file is included as part of the installation package.4 4. You must install the provider on the Application server. You can download this update and find more information about its installation from http://support.0.5).12. n In order for the software to function correctly in Excel 2007. all client modules have been migrated to . Prerequisites n A list of all supported operating systems is available in the Product Availability Matrix on SAP Service Marketplace at http://service.NET 2.0 Framework.2 Installing Planning and Consolidation Clients Installing the Office Client 4. n We recommend that you install all of the latest Microsoft Windows hotfixes prior to installing the Office client.0 SP1 n XML 4. or later n Microsoft Office 2003 or 2007 n SP04 or later: Microsoft Office 2010 (32‒bit only) n . in Planning and Consolidation 7. you cannot log on to Planning and Consolidation 7.2 Installing the Office Client This topic describes the minimum prerequisites required and how to install the Planning and Consolidation for Office client. This creates the registry key for Xceed Zip. you must install the Microsoft. 8. You must install the components on the Application server. you must install the Microsoft Office 2007 system driver Data Connectivity Components. n Microsoft Internet Explorer 7.OLEDB. Note For Office client installations.NET Framework 2.NET 2. Search on Planning and Consolidation.com/pam. you must log on to the Office client as an administrator before the business user of the local machine logs on for the first time. which you can download from the Microsoft Web site.0.0 provider. This is an update for Visual Studio 2005 that distributes the required fixes to Office 2003 and the . which you can get from the Microsoft Web site. Note n If you are using Office 2003.sap.5.com/kb/907417/en-us.0. n For the software to function correctly in Excel 2007.0 SP2 (included with the Internet Explorer software) n Pentium IV (1 GHz CPU) n 512 MB RAM n 100 MB of free hard disk space in the My Documents folder n 30 MB of free hard disk space for the installed Client files n Adobe Reader (free from Adobe) n Xceedzip.dll (version 6.microsoft.ACE. see 03/11/2011 PUBLIC 51/66 . The update is required because.NET Framework 2.

then select Next. Wait while the installation wizard verifies your prerequisites. When the installation is complete. where <PC_server:port> is the name or IP address and port of the server where you installed Planning and Consolidation. Log on to a machine on which the user is part of the Administrators group 2. 9. Installing the Office client in Unattended mode using SMS You can perform an unattended install of the Office client and Administration programs on client machines.0 to Planning and Consolidation 7. Point your browser to Planning and Consolidation Web (http://<PC_server:port>/osoft). Note If Planning and Consolidation 7.4 4. Select Next to install the program to the default location. 8. then select I accept the terms of the license agreement and click Next. For more information. See SAP note 1471194. 5.5 SP03. See Using the Client Auto Update Program [page 52]. choose the Client Software Center link or icon. 4. select Next. (Use Add/Remove Programs in the Windows Control Panel. Uninstall any previous versions of the Planning and Consolidation for Office clients.aspx?ln=en-us The following procedure describes how to install the Planning and Consolidation for Office client. 6. choose Finish.0 or later is installed.com/windowsupdate/v6/default. Select the language in which you want to see the user interface.0 or later is installed. When you choose Yes in the Auto Update dialog. Select Client for Office Installation.3 Using the Client Auto Update Program If Planning and Consolidation 7. From the installation wizard. 10. 52/66 PUBLIC 03/11/2011 . then select Next. From the Business Planning and Consolidation Launch page.microsoft. 4. you can use the Client Auto Update program to install the client. you can also use Client Auto Update to install the client. 7.3 Installing Planning and Consolidation Clients Using the Client Auto Update Program http://update. the message Update Complete appears immediately but nothing is updated.) 3. To install the Office client: 1. Note The Client Auto Update program cannot update from Planning and Consolidation 7. see Installing the Office Client in Unattended Mode Using SMS [page 53].

as described here: n When a user logs onto the Planning and Consolidation Office client. 4. To use the Client Auto Update program: 1. see Installing the Administration Client [page 49] and Installing the Office Client [page 51]. This setting is not needed if all users have administrator rights on their machines. Note Contact Product Support to request a copy of this installation program. then Auto Update runs for both. it prompts the user to perform the upgrade. 3. you can use the Client Auto Update program to set up the server so that it determines if an upgrade for a connecting Administration or Office client is necessary. if an upgrade is required for either one. SMS can use the setup program in the Client for SMS\Client folder or the Admin folder to install Planning and Consolidation. clients must be installed manually. n When a user logs onto the Planning and Consolidation Administration client.4 Installing Planning and Consolidation Clients Installing the Office Client in Unattended Mode Using SMS Procedure If Planning and Consolidation version 7. If users without administrator rights on their machines use the auto update. followed by the Office client installation. you modify or create the following files: 03/11/2011 PUBLIC 53/66 . Select Update.0 or later is installed. if an upgrade to the client is necessary. or Admin Update (Administration component). For details of manual installation. select Options Client Options .4 4. 4. Select the ON radio button for the Client Update (Office component). If Client Auto Update is enabled and the system finds a previous version. enter an admin ID and password in the Admin ID and Admin password fields. From Server Manager. followed by the Administration client installation. Auto Update runs the Administration client installation. 2. where the installation messages are suppressed. if an upgrade to the client is necessary. Auto Update runs the Office client installation. SMS install also supports Silent mode. If Client Auto Update is not enabled and a previous version has been installed. For unattended installation.4 Installing the Office Client in Unattended Mode Using SMS You can perform an unattended install of the Office client and Administration programs on client machines. The Admin ID should be a member of the local administrators group on all the computers running the auto update. If you want to run an unattended install. respectively. If both the Planning and Consolidation Office Client and Administration client are installed on the same machine.

you want your clients to support an earlier version of a prerequisite). the response must be recorded in an Installation Setup Initialization file (. and where the XML file to download is located. n Modify the messages displayed during the Administration client installation. Option Description Client Option The latest version number of XML installed on the server. Enter the desired XML version.iss file — This file is used to specify the unattended setup and can be modified by a system 1. administrator who is familiar with SMS. To create this file. Modifying the Client System Requirements When users log on to their Planning and Consolidation clients. 2. open the CustomMsgAdminEnglish. run the Setup. 1. the Planning and Consolidation server checks for certain prerequisite software versions to make sure the minimum required versions are installed. you can change that setting. n Modify the messages displayed during the Office client installation. The way the system determines which versions are acceptable is by looking at certain settings on the server. the settings are automatically configured. 54/66 PUBLIC 03/11/2011 . Record a response file — When you run an unattended installation. InstallShield records the installation choices in the Setup. The table below describes the options you can modify.5 Installing Planning and Consolidation Clients Customizing Client Software Setup. or does not have the software. then select Options 2. If you want to change the software version (for example. and the prerequisite software is installed when a user opts to update the software.ISS).5 Customizing Client Software There are several ways you can modify software located on the clients that connect to a particular server.exe ‒r command on a clean machine. although in most cases no changes are required. and places the file in the Windows or WinNT folder.4 4. 4. When set this way. Open it using a text editor like Notepad.txt file (located in <drive>\Websrvr\Web\Installation. Open Server Manager. From the server. Modifying Administration Installation Messages You can modify the messages that are displayed on the dialog boxes during the Administration component installation. You can make the following modifications: n Modify the client system requirements. Client Options . the server determines when a client machine has an earlier version than the specified version. To modify client system requirements. When you receive a new build of the server software. follow these steps: 1.iss file.

Save the file under another name to back it up.4 4. CustomMsgEnglish. as it provides useful information on the status of your client. Choose More info to see system information. take the following steps: 1. 3. Select Planning and Consolidation for Office or Planning and Consolidation for Administration.txt 4.6 Using the Client Diagnostic Program This program can help you to troubleshoot your Office client or Administration software. 2. Modify the file. then save and close it. 3. 1. then save and close it. open the file (located in <drive>\Websrvr\Web\Installation. Select the Client Diagnostic link.6 Installing Planning and Consolidation Clients Using the Client Diagnostic Program 2. Modifying the Office Client Installation Messages You can modify the messages that are displayed on the dialog boxes during the Office client installation. From the server. Save the file under another name to back it up. 2. To use the Client Diagnostic program. Run this program before contacting SAP Support. Open it in a text editor like Notepad. 03/11/2011 PUBLIC 55/66 . Choose Close to close the dialog box. Point your browser to Planning and Consolidation Web. then choose Next. Modify the file. 3. 4. 5.

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

If it returns a message stating that it cannot connect. n Enabling content filtering on the proxy server or firewall may cause connection problems.5 Connection Issues 5 Connection Issues You may experience connection problems with ports. the port is open.asp You can change the name of a port. If you have any issues related to connection. To test whether the required ports are open. For example. Note You can use the following site to scan for the normal ports. Fully qualified domain names typically resolve both internal and external IP addresses. the port is not open.2 Proxy Server and Firewall Issues For questions about specific proxy servers.18.36 80. go to a command prompt and enter the Telnet server IP address and port. Planning and Consolidation requires that Ports 80 (used by http) and 1433 and 2383 (used by SQL Server/Analysis Services 2005 and SQL Server 2008) are open. Telnet 43. General Considerations n If you connect to the Internet through a firewall or proxy server. By default.1 Checking for Open Ports You must ensure that all required ports are open for inbound/outbound traffic. You can do this at the client level ( Internet Explorer Tools Internet Options Connections LAN Settings ) or at the server level. or programs and settings that interact with these components. the proxy server. make sure the proxy server connects using a fully qualified domain name. you need to add the IP address of the Planning and Consolidation server as an exception. http://www.118.myserver. If the system returns a blank command window. review the following recommendations and troubleshooting tips. 5. n If external users are having trouble connecting to the server. It allows you to manually enter a port number to test. contact SAP Support.org/portsniff. 5. 03/11/2011 PUBLIC 57/66 .

5. Microsoft Office Issues There should only be one instance of Excel installed on the client machine. 58/66 PUBLIC 03/11/2011 . then insert the IP address or fully qualified server name of the Planning and Consolidation server as an exception by choosing the Advanced button. From Internet Explorer. if the Web server and OLAP server components both connect to a proxy server. then OK. contact SAP Support to request a copy of the Setting up ISA Proxy Server white paper. Apply. cookies. The system synchronizes the user name and password on the remote server with the local user name and password. Change the settings by taking the following steps: 1. choose the Restore Defaults button. Norton AntiVirus Issues Having Script Blocking enabled in Norton AntiVirus can cause the following issues: n You cannot view the contents of the installation page in Interface for the Web.2 Connection Issues Proxy Server and Firewall Issues n Each secure Planning and Consolidation server name must be identified on the proxy server. delete all temporary Internet files. From the Security tab. choose the LAN settings button. 3. From the Connections tab. disable the Windows firewall. n Errors downloading dimension files when logging into the Office client. make sure both names are identified on the proxy server. From the Advanced tab.5 5. You can check this by using Add/Remove Programs. set security to Default level for Internet and local intranet. select Tools Internet Options . 2. which could conflict with Planning and Consolidation authentication. Internet Explorer Settings Issues Internet Explorer settings must be set correctly to prevent errors and problems when you attempt to access the Planning and Consolidation server using the Connection Wizard. 4. and history. Microsoft Windows Issues If you have Windows XP SP2. From the General tab. Multiple instances of Office may cause errors when you perform administrative functions in Planning and Consolidation. n Proxy servers may or may not require authentication. For example. If you select Use a proxy server for your LAN. Do not use authentication on the proxy server. Note For more information about setting up an ISA proxy server.

The profile directory is on the system drive and has limited space. 03/11/2011 PUBLIC 59/66 .6 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment 6 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment This section describes best practices and instructions for installing Planning and Consolidation in a Terminal Services or Citrix Server deployment. so that all users consistently use the current download of dimensions. If you have a farm of servers. By specifying a home directory. you can manage the disk space required. 6.3 Installing Planning and Consolidation Prerequisites The server installation files have been downloaded from SAP Service Marketplace and installed. The profile directory downloads a minimal amount of information about the dimensions of the application set you are logging on to and may be as large as 2 MB per user.0 Adobe Reader 6.NET Framework 2.1 Terminal Services Home Directories We recommend using Terminal Server home directories rather than using the user’s profile directory. put the profile information in a common home directory rather than on each individual server.2 System Requirements The following programs are required on the Terminal Services or Citrix Server computer: n n n n Microsoft Office 2007 or 2003 Microsoft XML 4 SP2 Microsoft . 6.

8. 5. Log on to the web site with the service account. 3. the system does not install Office.exe http(s)://<ServerName>NetBIOS or FQDN/osoft n To publish Planning and Consolidation Administration: C:\Program Files\PC_MS\OsoftAdminMain. Microsoft has supplied a transform file to handle the Terminal Server installation. and domain.4 Creating a Shortcut to the Launch Page If you use published desktops instead of published applications. Go back to the command prompt and enter Change user/execute or Restart the server. Although Termsrvr. used to set up and configure programs and components of Office. 2. The transform file is named Termsrvr. Log on to the Terminal Services or Citrix Server machine with a user ID that has the rights to install on that server. 6.exe <drive>\ev4excel.4 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment Creating a Shortcut to the Launch Page Procedure The following steps outline how to install the Planning and Consolidation clients in a Terminal Services (TS) or Citrix Server deployment: 1.mst and is available with the ORK (office resource kit). enter Change user/install. Go to the Software Center and install the Planning and Consolidation Administration and Planning and Consolidation for Office clients. 7. Since the Terminal Server environment is different from the usual network environment. you must publish each client application.exe n To publish Planning and Consolidation for Office: C:\Program Files\Microsoft Office\Office\Excel. At a command prompt. 6. Open a browser and connect to the URL http://<PC_server:port>/osoft. modification of the TermSrvr. password.mst can be customized to include options and features that you wish to make available to Terminal Server client users. uses a transform file to allow a network administrator to designate the options and features to install.6 6. For the Citrix Server. If you attempt to use a customized transform not designated for use with Terminal Server. 60/66 PUBLIC 03/11/2011 .5 Terminal Services Considerations for Installing Microsoft Excel The Windows Installer.mst is not supported by Microsoft. the Planning and Consolidation desktop file (which is installed on the current user’s desktop) must be moved to the All Users/Desktop folder. Take the following steps: n To publish the Planning and Consolidation Launch page: Iexplore. Make sure the Terminal Services or Citrix Server machine has the system requirements installed.xla 6. 4.

dll OSoftTaskMakeDim. 1.dll OSoftTaskFtp.dll OSoftTaskLogic.7 Installing SSIS Custom Tasks 7 Installing SSIS Custom Tasks This section describes background information and instructions for installing SQL Server 2005 and 2008 Integration Services (SSIS). Planning and Consolidation Data Manager has the following custom tasks: Name Remark OSoftTaskAdmin. Planning and Consolidation also supports the remote modification of SSIS packages with system and custom tasks. complete the tasks outlined below.dll OSoftTaskConvert. These custom tasks reference dlls that connect to the DB server and perform certain validation when users set up the parameters of each task. To successfully modify an SSIS package that contains Data Manager custom tasks. 7. These steps are required if you remotely modify SSIS packages with Data Manager custom tasks. Copy all Data Manager custom task components to your SQL server.1 Before You Run the SSIS Custom Task Installation Before you run the SSIS custom task installation on the client machine.dll OSoftTaskAvailable. All the custom task reference components must also be installed in the machine on which you want to run and modify SSIS packages. We provide a program that registers all the reference components of the custom tasks.dll Data Manager Admin custom task Data Manager System Available custom task Data Manager Comment custom task Data Manager Convert custom task Data Manager DumpLoad custom task Data Manager FTP custom task Data Manager Logic custom task Data Manager Make Dimension custom task 03/11/2011 PUBLIC 61/66 . Do not modify the SSIS package on a machine other than the application server or DB server. Since SQL Server 2005 and 2008 support the modification of SSIS packages remotely. This section explains the installation package and how to use it. do so on the Planning and Consolidation application server or DB server.dll OSoftTaskComment. The Planning and Consolidation Data Manager component supports and uses SSIS.dll OSoftTaskDumpLoad.

2 Installing SSIS Custom Tasks The Composition of SSIS Custom Task Installation Name Remark OSoftTaskSendMail. Bin folder This folder contains the following components. if you install your SQL 2008 server on C:\Program Files\Microsoft SQL Server. n OSoftSetup. Some components are registered into the registry and some components are registered into a COM+ service on the machine.7 7. Paste these files into the SQL Server 2005 folder \90\DTS\Tasks.dll OSoftTaskTrigger. you can modify this xml file. or the SQL Server 2008 folder \100\DTS\Tasks. paste all files into the C:\Program Files\Microsoft SQL Server\100\DTS\Tasks folder.exe ‒ This is the main executable file to run the installation package. You can find these files in the <drive>\Websrvr\bin folder. paste the files into D:\Program Files (x86)\Microsoft SQL Server\100\DTS\Tasks. The program installs the following files: Name Remark BPCGacutil_20. The path of your client should be the %SQL 2005 client install%\90\DTS\Tasks folder or the %SQL 2008 client install%\100\DTS\Tasks folder. set the property Run64BitRunTime to False.dll OSoftTaskOwnership. In Integration Services. If you need to add or remove certain components from the installation. Copy all Data Manager custom task components to your client machine.exe OSoftResSvrDMM. see SAP Note 1406471. For more information.2 The Composition of SSIS Custom Task Installation You use the following elements when you install SSIS Custom tasks: n Bin folder ‒ This folder contains all the dlls that should be installed on the machine. If the server is running on a 64‒bit operating system. n Config folder ‒ This folder contains only one file named Filelist. There are Planning and Consolidation platform components and all of the Data Manager custom task files. such as OSoftTaskAdmin2008. 2.dll Note Data Manager Send Mail custom task Data Manager Trigger custom task Data Manager Ownership Calculation custom task The file names shown above contain 2008 in their name when you run SQL Server 2008. Paste the Data Manager task files (above) into the specific path on your client machine.dll System File 62/66 PUBLIC 03/11/2011 . For example.dll. 7.xml and lists all of the files that should be installed.

dll OSoftDatabaseADMIN.dll OSoftLogging.dll OSoftCustomXMLSvr. such as OSoftTaskAdmin2008.dll OSoftSQE.dll OSoftAudit.dll OSoftTaskAvailable.dll OSoftDMTaskMain.dll OSoftSvrZip. OSoftTaskAdmin.dll OSoftDMTaskForm.DTS.7 7.dll OSoftAdminServer.2 Installing SSIS Custom Tasks The Composition of SSIS Custom Task Installation Name Remark OSoftResSvrshr.dll OSoftTaskConvert.dll OSoftSystemConfig.dll OSoftSvrZip.dll K2Logic.dll OSoftMetaData.dll DataManager custom task DataManager custom task DataManager custom task DataManager custom task DataManager custom task DataManager custom task 03/11/2011 PUBLIC 63/66 .dll K2Processing.dll OSoftConfiguration.dll OSoftTaskDumpLoad.dll OSoftCommonResQry.dll OSoftDMTools.dll OSoftTaskFtp.dll OSoftDatabaseUSER.dll OSoftTaskComment.dll OSoftDatabaseSYSADMIN.dll OSoftComLibServer.dll Note Com+ component Com+ component Com+ component Com+ component Com+ component Com+ component Com+ component Com+ component Com+ component Com+ component Com+ component The file names shown below contain 2008 in their name when you run SQL Server 2008.dll OSoftLogWriter.dll OSoftZFPSvrRes_English.dll.dll Interop.

If you need to add more components to the installation package.NET Framework component that should be registered into Global Assembly Cache n FileName ‒ Component file name OSoftSetup.dll OSoftTaskMakeDim. If your SQL Server has an instance.2 Installing SSIS Custom Tasks The Composition of SSIS Custom Task Installation Name Remark OSoftTaskLogic.dll OSoftTaskSendMail. n Set server credential: This is the credential name of the COM+ package component. you can copy the new components into the Bin folder and add the proper xml tags in FileList.dll OSoftTaskOwnership. which contains the registration method of each component. specify the instance name. Double-click the file to start the installation. You can write down the following values: l RegAsm ‒ For . You need to give information for the following fields: n Set SQL server: Specify the SQL server name.xml.xml file.NET component l Regsvr32 ‒ For VB6 component l Gacutil ‒ For .exe This is the executable file to run the SSIS installation package. This account should be one of the user IDs registered as a COM+ user when the Planning and Consolidation application server was installed. Enter the user ID and password that can access your SQL Server.dll OutlookSoft.7 7. 64/66 PUBLIC 03/11/2011 . You need to give information for the following tags: n RegistType ‒ This is the registration information of the component.dll OSoftTaskTrigger.config Config folder DataManager custom task DataManager custom task DataManager custom task DataManager custom task DataManager custom task Configuration file to connect DB server This folder has FileList.

These include field labels. program names. for example. and key concepts of a programming language when they are surrounded by body text. transaction codes. Enter your <User Name>. for example. names of variables and parameters. for example.com Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web Hyperlink to an SAP Note. upgrade. for example. pushbutton labels. and names of installation. screen titles.sap. These include report names. messages n Source code or syntax quoted directly from a program n File and directory names and their paths. and menu options.Typographic Conventions Example < > Description Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system. and database tools Technical names of system objects. for example. database table names. menu options Emphasized words or expressions Words or characters that you enter in the system exactly as they appear in the documentation Textual cross-references to an internet address. for example. Arrows separating the parts of a navigation path. menu names. SAP Note 123456 n Words or characters quoted from the screen. n Cross-references to other documentation or published works n Output on the screen following a user action. http://www. SELECT and INCLUDE Keys on the keyboard Example Example Example /example 123456 Example Example EXAMPLE EXAMPLE 03/11/2011 PUBLIC 65/66 .

com © Copyright 2011 SAP AG. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden. Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind. All rights reserved.SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +49/18 05/34 34 20 www. zu welchem Zweck und in welcher Form auch immer.sap. ohne die ausdrückliche schriftliche Genehmigung durch SAP AG nicht gestattet. .