Installation Guide SAP BusinessObjects Planning and Consolidation 7.5 version for SAP NetWeaver
Target Audience ÃH System Administrators ÃH Technical Consultants
CUSTOMER ÃH, ç; !Æ º6+È£$ã$¾ÚpÓ/;r#ý\W\
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 2013 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.
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/56 CUSTOMER 2013-09-17
Typographic Conventions
Example Description < > Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system, for example, “Enter your
2013-09-17 CUSTOMER 3/56
Document History
The following table provides an overview of the most important document changes:
Version Date Description 1.0 2009-12-15 First version 1.1 2009-12-28 Added information on IIS 7.0 and system.WebServer in Web.config to the “Troubleshooting” section. 1.2 2010-01-06 In “Server Prerequisites”, clarified the requirement of SAP NetWeaver BW 7.0 EhP 1. In section 3.2 Configuring the ABAP Server Component, clarified the ABAP service users and assigned roles, added the authorization SAP_BW_CONTENT_ADMIN to activate business content, and made other minor modifications. 1.3 2010-02-23 In “Server Prerequisites”, added recommendation for English international version of Windows. 1.4 2010-02-26 In “Verifying and Installing Client Prerequisites”, added reference to version number of Visual C++ for the client machine. The required version number is 6.0. In ”Installing the Prerequisite Software on the ABAP Application Server”, added note to implement the correction instruction (indicated in SAP Note 1410973) to ensure correct cube maintenance with BAPI. Added a section within "Security Considerations and Connection Issues” to highlight an Adobe Flash player limitation on ports that cannot be used for the Planning and Consolidation Web server. Added a reference to the Product Availability Matrix in the client and server prerequisites. 1.5 2010-03-23 Added a reference to the Product Availability Matrix in the client and server prerequisites. 1.6 2010-04-02 Added solution to “Troubleshooting” to describe how to specify the generation of detailed error messages for IIS 7.0 with Windows 2008 on a 64–bit server and .NET Framework 1.1. 1.7 2010-06-10 Added the option for using CMS user domains for ABAP configuration. 2.0 2010-06-15 This is the update for SP03. For detailed information, refer to the appropriate SAP central note. 2.1 2010-07-13 Added a item to the “Verifying and Installing Client Prerequisites” for Adobe Flash 10. 2.2 2010-07-20 In the section “Configuring the ABAP Server Component” modified the settings for namespaces and software components in production. 2.3 2010-08-11 In the section “2.4.2 Installing the Prerequisite Software on the .NET Servers”, changed the reference to the operating system to install so that the product availability matrix (PAM) can be used as a reference. 2.4 2010-10-20 In the “Introduction”, added information about virtualization.
4/56 CUSTOMER 2013-09-17
Version Date Description 2.5 2010-11-19 This is the update for SP05. For detailed information, refer to the appropriate SAP central note. 2.6 2010-12-09 Changed the ASP.NET version to 2.0. Changed .NET Framework requirement to 1.1 and 2.0 for SP00 to SP04. 2.7 2011-01-25 In the sections “2.3 Server Prerequisites” and “2.4.2 Installing the Prerequisite Software on the .NET Servers”, changed the MSXML version to 3.0 SP5 or later, or 4.0 SP2 or later for Windows 2003; changed the MSXML version to 4.0 SP3 or later for Windows 2008. In the section “4.1 Modifying machine.config Files”, changed the information for modifying Machine.config for .NET Framework 1.1 and .NET Framework 2.0. 2.8 2011-01-26 Added client hardware requirements to section “5.1 Verifying and Installing Client Prerequisites”. 2.9 2011-02-28 Updated required version of XceedZip.dll in “2.4.2 Installing the Prerequisite Software on the .NET Servers” and “5.1 Verifying and Installing Client Prerequisites”. 3.0 2011-04-08 Updated the step for downloading the XceedZip Compression Library in the topic “Installing the Prerequisite Software on the .NET Servers” to state that setting up Secure Socket Layer (SSL) encryption should be done for Internet-facing servers only. 3.1 2011-04-19 Updated the version of MSXML in the topic “Verifying and Installing Client Prerequisites” to state that MSXML 4.0 SP3 is required for Windows 7. 3.2 2011-04-21 Added a note to the topic “Connecting to Solution Manager Diagnostics” to explain the behavior of the PlanningAndConsolidationJobService service. 3.3 2011-06-01 In section “Server Prerequisites”, revised details of the SAP NetWeaver version. 3.4 2011-10-12 Updated the guide for support of SAP NetWeaver 7.3. 3.5 2011-10-18 Updated the topic “Installing the ABAP Server Component” with information about Planning and Consolidation 7.53 and applicable SAP Notes. 3.55 2011-10-20 In “Configuring the ABAP Server Component”, changed references to UJA_ACTIVATE_CONTENT to UJS_ACTIVATE_CONTENT. In the section “New Installation Program Features in 7.5” of the Introduction, added the support of SAP NetWeaver 7.30. In “Installing the Prerequisite Software on the .NET Servers”, replaced references to SAP GUI 7.10 with SAP GUI 7.10 or above. 3.6 2012-03-02 In “Installing the Prerequisite Software on the .NET Servers”, updated step 4 “Download and Install the Anti-Cross Site Scripting Library” and step 6 “Download the XceedZip Compression Library”. 3.65 2012-03-28 In “Installing the Prerequisite Software on the .NET Servers”, updated the subfolders mentioned in step 4 “Download and Install the Anti-Cross Site Scripting Library”. 3.70 2012-05-24 Added SP2 to .NET Framework 2.0 and added SP1 to .NET Framework 3.5 in the topics “Server Prerequisites” and “Installing the Prerequisite Software on the .NET Servers”. 3.75 2013-02-01 SP15: Updated the prerequisites for the .NET Application Server and Web Server in the topic “Server Prerequisites”. 3.76 2013-09-17 In the topic “Configuring the ABAP Server Component”, corrected the SAP note number mentioned in the step in which you use transaction RSTPRFC to set up transports to 1329651.
2013-09-17 CUSTOMER 5/56
Table of Contents
Chapter 1 Introduction ...... 9 1.1 SAP Notes for the Installation ...... 9 1.2 Naming Conventions ...... 10
Chapter 2 Planning the Server Installation ...... 11 2.1 Installation Scenarios ...... 11 2.2 Hardware Requirements ...... 11 2.3 Server Prerequisites ...... 12 2.4 Installing the Server Prerequisites ...... 13 2.4.1 Installing the Prerequisite Software on the ABAP Application Server ...... 13 2.4.2 Installing the Prerequisite Software on the .NET Servers ...... 13 2.5 Acquiring the ABAP and .NET Server Components ...... 18
Chapter 3 Installing Planning and Consolidation Servers ...... 21 3.1 Installing and Configuring SAP NetWeaver ...... 21 3.2 Installing the ABAP Server Component ...... 21 3.3 Configuring the ABAP Server Component ...... 22 3.4 Installing the .NET Server Component ...... 25 3.5 Configuring the .NET Server Component ...... 27
Chapter 4 Post-Installation of the Server Components ...... 29 4.1 Modifying Machine.config Files ...... 29 4.2 Configuring COM+ Application Pooling Values ...... 31 4.3 Verification of Windows Authentication Providers ...... 31 4.4 Adding a Firewall Exception to the Website Port ...... 32 4.5 Setting Up for Large Requests ...... 32
Chapter 5 Installing Planning and Consolidation Clients ...... 33 5.1 Verifying and Installing Client Prerequisites ...... 33 5.2 Uninstalling Previous Client Components ...... 34 5.3 Installing the Admin and Office Client Components ...... 34
6/56 CUSTOMER 2013-09-17
5.4 Running the Silent Installation ...... 35
Chapter 6 Basic Steps for Setting up an Initial Application Set ...... 37
Chapter 7 Tips ...... 39 7.1 Creating Start and Stop Batch Files ...... 39 7.2 SMS for Planning and Consolidation Package Delivery ...... 39
Chapter 8 Troubleshooting ...... 43
Chapter 9 Connecting to Solution Manager Diagnostics ...... 47
Chapter 10 Security Considerations and Connection Issues ...... 49 10.1 Setting up SSL Encryption ...... 49 10.2 Checking for Open Ports ...... 50 10.3 Adobe Flash Player Issues ...... 51 10.4 Proxy Server and Firewall Issues ...... 51
Chapter 11 Terminal Services or Citrix Server ...... 53 11.1 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment ...... 53 11.1.1 Terminal Services Home Directories ...... 53 11.1.2 System Requirements ...... 53 11.1.3 Installing Planning and Consolidation ...... 53 11.1.4 Creating a Shortcut to the Launch Page ...... 54 11.1.5 Terminal Services Considerations for Installing Microsoft Excel ...... 54
2013-09-17 CUSTOMER 7/56 This page is left blank for documents that are printed on both sides. 1 Introduction 1.1 SAP Notes for the Installation 1 Introduction
The SAP BusinessObjects Planning and Consolidation Installation Guide is intended for system administrators and technical consultants. It contains everything you need to know about installing the Planning and Consolidation components.
New Installation Program Features in 7.5 These features are new to the Planning and Consolidation 7.5 installation program: F Planning and Consolidation supports Central Management System (CMS) in addition to Active Directory (AD). Users can also migrate their security from AD to CMS. For more information, see Migrating Users to the Central Management System in the Upgrade Guide. F You can run your production version of Planning and Consolidation in a virtualized environment. For more information, see SAP Note 1098847. F Planning and Consolidation supports Load Runner for performance testing. F Planning and Consolidation supports SAP Netweaver 7.30 in addition to versions 7.01, 7.02, and 7.03.
1.1 SAP Notes for the Installation Read the following SAP Notes before you start the installation. These SAP Notes contain the most recent information on the installation, as well as additions to the installation documentation. Make sure that you have the up-to-date version of each SAP Note, which you can find on SAP Service Marketplace at the Internet address http://service.sap.com/notes.
Important SAP Notes SAP Note Number Title Comments 1410517 SAP Planning and Consolidation 7.5 This is the Central Note for Planning and SP00, version for SAP NetWeaver Consolidation 7.5. 1409989 SAP Planning and Consolidation 7.5 This is the Central Note for Planning and SP01, version for SAP NetWeaver Consolidation 7.5, Service Pack 01. 1433411 SAP Planning and Consolidation 7.5 This is the Central Note for Planning and SP02, version for SAP NetWeaver Consolidation 7.5, Service Pack 02. 1453797 SAP Planning and Consolidation 7.5 This is the Central Note for Planning and SP03, version for SAP NetWeaver Consolidation 7.5, Service Pack 03. 1471662 SAP Planning and Consolidation 7.5 This is the Central Note for Planning and SP04, version for SAP NetWeaver Consolidation 7.5, Service Pack 04.
2013-09-17 CUSTOMER 9/56 1 Introduction 1.2 Naming Conventions
SAP Note Number Title Comments 1497632 SAP Planning and Consolidation 7.5 This is the Central Note for Planning and SP05, version for SAP NetWeaver Consolidation 7.5, Service Pack 05. 1527325 SAP Planning and Consolidation 7.5 This is the Central Note for Planning and SP06, version for SAP NetWeaver Consolidation 7.5, Service Pack 06.
1.2 Naming Conventions In this document, the following naming conventions apply:
Variable Description
10/56 CUSTOMER 2013-09-17 2 Planning the Server Installation 2.1 Installation Scenarios 2 Planning the Server Installation
Before installing Planning and Consolidation, complete the following planning activities. 1. Make sure your hardware is appropriate for the server tiers. See Hardware Requirements [page 11]. 2. Verify that you have the required prerequisites installed on the server. If not, install them. See Server Prerequisites [page 12] and Installing the Server Prerequisites [page 13]. 3. Download the Planning and Consolidation server components from SAP Service Marketplace. See Acquiring the ABAP and .NET Server Components [page 18].
2.1 Installation Scenarios The Planning and Consolidation installation program consists of a standalone .NET server component, an ABAP server component, and a client installation. You can install the ABAP server component in one of two configurations: 0+ On an existing NetWeaver 7.30 system (that meets minimum prerequisites) 0+ On a completely new NetWeaver 7.30 system Planning and Consolidation supports Central Management System (CMS) in addition to Active Directory (AD). If you want to use CMS for Planning and Consolidation authorization, you must download and install it on its own server. For more information, see Downloading Central Management System in the Master Guide.
2.2 Hardware Requirements Procedure Before starting the Planning and Consolidation installation, make sure you follow these hardware requirements for the server tiers:
Tier Hardware required ABAP Application Server The NetWeaver application server can run on any supported NetWeaver platform. For information about the requirements for this tier, see the NetWeaver Master Guide and Installation Guide at https://service.sap.com/installnw73. .NET Application/Web Server The .NET server can run on a 32 bit or 64 bit platform. However, .NET natively runs 32 bit.
2013-09-17 CUSTOMER 11/56 2 Planning the Server Installation 2.3 Server Prerequisites
2.3 Server Prerequisites You must install the following requirements on the ABAP application server and .NET application and Web servers before installing the Planning and Consolidation server components:
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.sap.com/pam. Search on Planning and Consolidation.
Server Requirements ABAP Application Server SAP NetWeaver 7.30, 7.01, 7.02, or 7.03 An operating system supported by SAP NetWeaver A database supported by SAP NetWeaver
NOTE For information on installing the prerequisite software, see Installing the Prerequisite Software on the ABAP Application Server [page 13]. .NET Application Server and Web Server A list of supported operating systems is available in the Product Availability Matrix on SAP Service Marketplace at http:// service.sap.com/pam. Search on Planning and Consolidation. Microsoft Windows Script 5.6 (for Windows Server 2003) or 5.7 (for Windows Server 2008) SP00 to SP04: Microsoft .NET Framework 1.1 and 2.0 SP05 or later: Microsoft .NET Framework 2.0 SP2, 3.0 or 3.5 SP1 Microsoft Message Queue (MSMQ) SP00 to SP04: Microsoft IIS 6.0 or 7.0 SP05 or later: Microsoft IIS 6.0, 7.0 or 7.5 Microsoft Visual Basic 6 Run-Time SP5 or later** For Windows 2003: MSXML 3.0 SP5 or later** MSXML 4.0 SP2 or later** For Windows 2008: MSXML 4.0 SP3 or later** For Planning and Consolidation 7.5 SP00 to SP14: SAP GUI 7.10 or above (or only LIBRFC32.DLL (and its dependent DLLs) manually); For Planning and Consolidation 7.5 SP15 or higher: SAP GUI and LIBRFC32.DLL are not required. Dundas Chart* Farpoint* Microsoft Anti-Cross Site Scripting Library**. For more information, see SAP note 1679046. Xceed Zip Compression Library 6.5.9417.0 or later**
12/56 CUSTOMER 2013-09-17 2 Planning the Server Installation 2.4 Installing the Server Prerequisites
Server Requirements RECOMMENDATION Install the Planning and Consolidation servers on the English international version of Windows rather than on localized versions. For details, see SAP Note 362379.
NOTE The requirements with an asterisk (*) are third party components installed during the server installation. The requirements with two asterisks (**) must be downloaded prior to the server installation program. For information on installing the prerequisite software, see Installing the Prerequisite Software on the .NET Servers [page 13].
2.4 Installing the Server Prerequisites 2.4.1 Installing the Prerequisite Software on the ABAP Application Server For information about installing SAP NetWeaver, the required software, and the supported databases for the ABAP application server, see https://service.sap.com/instguidesNW70. See SAP Notes 1248905 and 1175848 for support package information.
NOTE It is important that you also refer to SAP Note 1410973 and apply the indicated correction. This ensures that maintaining a cube with BAPI (BAPI_CUBE_CREATE or BAPI_CUBE_CHANGE) functions correctly.
2.4.2 Installing the Prerequisite Software on the .NET Servers This section contains information on installing the prerequisite software for the .NET servers. It contains the following subsections: 1. Installing the Operating System and its related components 2. Installing MSMQ 3. Installing Microsoft Visual Basic 6 Run-Time 4. Installing the Anti-Cross Site Scripting Library 5. Installing SAP GUI 7.10 or above 6. Downloading XCeedZip.dll
2013-09-17 CUSTOMER 13/56 2 Planning the Server Installation 2.4 Installing the Server Prerequisites
1. Installing the Operating System and its related components Install the desired operating system on each application and Web server. To verify the operating system version, you can check the Windows system properties. If necessary, download the required operating system software from the Microsoft download site. Do the following for Windows 2003: öÚ Install Windows Script 5.6 on each application and Web server. You can obtain the software from the Microsoft download site. Windows Script is installed if the scrrun.dll file is located in the SYSTEM32 directory. öÚ Make sure you have MSXML 3.0 SP5 or MSXML 4.0 SP2 installed. To verify that MSXML 3.0 SP5 has been installed, check that the correct version of msxml3.dll, and msxml3r.dll exists in the system folder (typically C:\Windows\system32 for a 32bit system or C:\Windows\SysWOW64 for a 64bit system). To verify that MSXML 4.0 SP2 has been installed, check that the correct version of msxml4.dll and msxml4r.dll exists in the system folder (typically C:\Windows\system32 for a 32bit system or C: \Windows\SysWOW64 for a 64bit system). You can find details of the correct versions of the DLLs by going to http:// support.microsoft.com/kb/269238. You can check the availability of MSXML 3.0 SP5 and MSXML 4.0 SP2 in the Add or Remove Programs area of Windows Control Panel. öÚ Install Microsoft IIS 6.0 on each application server and Web server: 1. Go to Control Panel Add or Remove Programs Add/Remove Windows Components . 2. Double-click Application Server. 3. Double-click Internet Information Services (IIS). 4. Check that IIS, World Wide Web Services are selected, and choose OK. öÚ Planning and Consolidation 7.5 SP00 – SP04: Install .NET Framework version 1.1 and 2.0 (if not installed with your operating system) on each application and Web server. Install the required .NET Framework 1.1 hotfix by going to http://support.microsoft.com/kb/899511. Planning and Consolidation 7.5 SP05 or later: Install .NET Framework version 2.0 SP2, 3.0 or 3.5 SP1 (if not installed with your operating system) on each application and Web server. You can check the version in the Add or Remove Programs area of Windows Control Panel. You can obtain the .NET Framework software from the Microsoft download site. For Windows Server 2003, install both 237428_ENU_i386_zip.exe and 237718_ENU_i386_zip.exe. öÚ If you are running Windows 2003 on a 64–bit server, you must enable IIS to run 32–bit applications. Do the following: 1. Open a command prompt and navigate to the
14/56 CUSTOMER 2013-09-17 2 Planning the Server Installation 2.4 Installing the Server Prerequisites
For more information, see http://support.microsoft.com/kb/894435. Do the following for Windows 2008: ºü Install Windows Script 5.7 on each application and Web server. You can obtain the software from the Microsoft download site. You can check whether Windows Script is installed if the scrrun.dll file is in the SYSTEM32 directory. If it exists there, Windows Script is installed. ºü Make sure you have MSXML 4.0 SP3 installed. To verify that MSXML 4.0 SP3 has been installed, check that the correct version of msxml4.dll exists in the system folder (typically C:\Windows\system32 for a 32–bit system or C:\Windows \SysWOW64 for a 64bit system). You can find details of the correct version of the DLL by going to http://support.microsoft.com/ kb/269238. You can check the availability of MSXML 4.0 SP3 in the Add or Remove Programs area of Windows Control Panel. ºü Planning and Consolidation 7.5 SP00 – SP04: Install Microsoft IIS 6.0 or 7.0 on each application server and Web server Planning and Consolidation 7.5 SP05 or later: Install Microsoft IIS 6.0, 7.0 or 7.5 on each application server and Web server. ºü Install IIS according to the following procedure: http://learn.iis.net/page.aspx/29/ installing-iis-7-on-windows-server-2008-or-windows-server-2008-r2/ ºü When installing Microsoft IIS 7.0, make sure all Role Services are installed. ºü Planning and Consolidation 7.5 SP00 – SP04: Install .NET Framework version 1.1 and 2.0 (if not installed with your operating system) on each application and Web server. Install the required .NET Framework 1.1 hot fix by going to http://support.microsoft.com/kb/899511. Planning and Consolidation 7.5 SP05 or later: Install .NET Framework version 2.0 SP2, 3.0 or 3.5 SP1 (if not installed with your operating system) on each application and Web server. You can check the version in the Add or Remove Programs area of Windows Control Panel. You can obtain the software from the Microsoft download site. ºü If you are running Windows 2008 on a 64–bit server, you must enable IIS to run 32–bit applications. Do the following: 1. Go to Start Control Panel Administrative Tools . 2. Open Internet Information Services (IIS) Manager. 3. Select ASP.NET 2.0 in application pools of local web site, then click Advanced Settings in the actions panel. 4. Verify that the value of Enable 32-Bit Applications is set to true. Similarly, you must configure the XMLA application pool to run 32-bit applications. The XMLA site uses ASP.NET 2.0 so in this case, you should select ASP.NET 2.0 and verify that the value of Enable 32-Bit Applications is set to true. For more information, see http://support.microsoft.com/kb/894435.
2013-09-17 CUSTOMER 15/56 2 Planning the Server Installation 2.4 Installing the Server Prerequisites
2. Installing and Setting Up Microsoft Message Queue You must install and set up Microsoft Message Queue (MSMQ) on each application and Web server. The system uses the queue to store process states for administrative tasks. You must create at least one message queue. We recommend that this is a Private queue, as the system uses the path specified during the installation, and does not use Active Directory to look up the message queue. A message queue can be accessed locally or remotely and can be shared by one or more Planning and Consolidation application servers. When referencing a message queue that has been created on the same server as the application server, use the following syntax to connect to a message queue named bpcmessagequeue: .\Private$\bpcmessagequeue. When referencing a message queue that is located on a different server, use the following syntax to access the message queue remotely:
16/56 CUSTOMER 2013-09-17 2 Planning the Server Installation 2.4 Installing the Server Prerequisites
1. Go to Message Queuing (as described above for your operating system), then right-click Private Queues and select New Private Queue . 2. Enter the queue name, such as BPCStatusMessageQueue, select Nontransactional, then click OK. NOTE Make sure the message queue path in the ServerConfiguration.config file resembles
3. Download and install Microsoft Visual Basic 6 Run-Time Download and install Microsoft Visual Basic 6 Run-Time SP5 or later from the Microsoft Download Center. No special installation or configuration settings are necessary. You can verify that it is installed correctly by locating msvbvm60.dll in the Windows system folder, which is typically C:\WINDOWS \system32\ for Windows Server 2003 and C:\WINDOWS\SysWOW64 for Windows Server 2008.
4. Download and install the Anti-Cross Site Scripting Library 1. Download the Anti-Cross Site Scripting Library 4.2 setup program from the Microsoft Download Center. Locate it by searching with the keywords Anti-Cross Site Scripting. 2. Run the setup program. 3. Verify that the setup program created the subfolder \NET20 under the destination folder and that the file AntiXssLibrary.dll is there. For example, if you installed the library to the default destination folder, verify that AntiXssLibrary.dll exists in
2013-09-17 CUSTOMER 17/56 2 Planning the Server Installation 2.5 Acquiring the ABAP and .NET Server Components
5. Install SAP GUI 7.10 or above NOTE As of Planning and Consolidation 7.5 support package 15 the SAP GUI is not required. For lower support packages (SP00 to SP14) you still need to obtain and install the SAP GUI.
Install SAP GUI 7.10 or above (or only LIBRFC32.DLL and its dependent DLLs manually). You can obtain information on how to download it from the SAP Library at http://help.sap.com/saphelp_nw70/
helpdata/EN/45/0896abec042d6ae10000000a11466f/frameset.htm . When enabling the Logon Group (which is done during the .NET component installation described later in this document) on Windows Server 2003 or 2008, the application tries to connect to two ports of the ABAP server. We recommend that you first confirm that the following two items are defined in
6. Download the XceedZip Compression Library Download XCeedZip.dll (version 6.5.9417.0 or later) from http://service.sap.com/swdc/ Installation and Upgrades Browse our Download Catalog SAP Cryptographic Software . You are prompted for this file location during the server install.
NOTE Make sure that the server is configured on the domain or a trusted domain by going to My Computer Properties Computer Name Change . Make sure the correct domain is specified. We recommend that you set up Secure Socket Layer (SSL) encryption on a single server or on each application and Web server that is part of a multiserver configuration. This applies to Internet- facing servers only, as performance may be affected.
2.5 Acquiring the ABAP and .NET Server Components Procedure
Downloading the ABAP and .NET Server Components 1. Go to http://service.sap.com/swdc/. 2. Go to SAP Support Packages and Patches Entry by Application Group SAP Application Components SAP Planning and Consolidation for SAP NetWeaver 7.5 (NW). and select the latest support package file. 3. Download the ABAP and .NET server components to your Download Basket, then download the components from the basket using SAP Download Manager.
18/56 CUSTOMER 2013-09-17 2 Planning the Server Installation 2.5 Acquiring the ABAP and .NET Server Components
NOTE For information about installing of using the SAP Download Manager, go to https:// service.sap.com/support and choose my Download Basket from the my Personalized Information pane.
2013-09-17 CUSTOMER 19/56 This page is left blank for documents that are printed on both sides. 3 Installing Planning and Consolidation Servers 3.1 Installing and Configuring SAP NetWeaver 3 Installing Planning and Consolidation Servers
The main steps for installing Planning and Consolidation servers are the following: 1. Install and configure SAP NetWeaver — see Installing and Configuring SAP NetWeaver [page 21] 2. Install and configure the Planning and Consolidation ABAP addon — see Installing the ABAP Server Component [page 21] 3. Configure the Planning and Consolidation ABAP addon — see Configuring the ABAP Server Component [page 22] 4. Install Planning and Consolidation .NET server — see Installing the .NET Server Component [page 25] 5. Configure the Planning and Consolidation .NET server — see Configuring the .NET Server Component [page 27]
3.1 Installing and Configuring SAP NetWeaver Based on your configuration, you can install Planning and Consolidation on an existing SAP NetWeaver 7.30 technology platform, or you can install it on a new SAP NetWeaver 7.30 platform. The Business Intelligence usage type is required.
Procedure If you are installing on a new SAP NetWeaver technology platform, follow the steps outlined in the SAP NetWeaver documentation – see https://service.sap.com/instguidesNW73. After you install SAP NetWeaver, configure it based on the guidelines in the SAP NetWeaver documentation.
3.2 Installing the ABAP Server Component Prerequisites You have downloaded the ABAP server component from SAP Service Marketplace. See Acquiring the ABAP and .NET Server Components [page 18]. If you have a Planning and Consolidation 7.0, version for SAP NetWeaver installation, and you are upgrading to SAP NetWeaver 7.30, you must first upgrade to Planning and Consolidation 7.53 by downloading and installing CPMBPC 7.53. If you do not plan to use SAP NetWeaver 7.30, download and install CPMBPC 7.5.
2013-09-17 CUSTOMER 21/56 3 Installing Planning and Consolidation Servers 3.3 Configuring the ABAP Server Component
Planning and Consolidation 7.53 requires SAP NetWeaver 7.30 SP02 or above. In addition, you must apply SAP Note 1484591 if you are running SAP_BASIS 730 SP04 or lower. You must apply SAP Notes 1545834 and 1561043 if you are running SAP_BW 730 SP02.
Procedure To install the ABAP server component, use the transaction SAINT. For information about using SAINT, see http://help.sap.com/saphelp_nw70/helpdata/EN/ 26/5a8c38e3494231e10000009b38f8cf/frameset.htm.
3.3 Configuring the ABAP Server Component You must configure the ABAP server component after installing it. Included in this procedure is information about running the UJS_ACTIVATE_CONTENT program, which is how the default application set, ApShell, is created. It installs the ApShell application set by leveraging parts of the Planning and Consolidation transport framework. This program also supports the installation of many other table entries that are required in order for the system to work correctly such as, default users, formulas, client options, language settings, BW Business Content, and data manager instructions.
NOTE The UJS_ACTIVATE_CONTENT program cannot be used to activate a pre-existing application set migrated from 7.0 to 7.5.
The program also supports data loading into the ApShell application set. This option triggers data manager packages to run and creates the default transactional and master data for ApShell. The delete option is useful when the installation of ApShell fails, and leaves orphaned objects and table entries in the system. The deletion function cleans up all BW objects as well as clear all Planning and Consolidation UJ* metadata tables. If you are upgrading your ABAP server component from Planning and Consolidation 7.0 and have already configured it, these steps are not necessary.
Prerequisites The ABAP server component has been installed.
RECOMMENDATION We recommend that you set the ABAP buffer size to at least 2 GB to minimize the risk of errors during the UJS_ACTIVATE_CONTENT step (step 10 below). You can set the buffer size using the parameter abap/buffersize in the instance profile with transaction RZ10. After completing the step, you can change it back. After changing the parameter, you must restart the ABAP instance, for example, with the SAP Management Console.
22/56 CUSTOMER 2013-09-17 3 Installing Planning and Consolidation Servers 3.3 Configuring the ABAP Server Component
For more information about changing the buffer size, see SAP Note 1273283.
Procedure These steps are required for proper functioning of the Planning and Consolidation software: 1. For maximum flexibility, you can make the following namespaces and software components changeable: Ýþ Namespaces: Ýþ /CPMB/ Ýþ /1CPMB/ Ýþ /B28/ Ýþ Customer Name Range Ýþ General SAP Name Range Ýþ Software Components: Ýþ CPMBPC Ýþ HOME Ýþ LOCAL However, in a production environment, you may want to minimize the number of components that can be modified. If this is the case, you can set the following namespaces and software components to unchangeable: Ýþ Namespaces: Ýþ /1CPMB/ Ýþ Customer Name Range Ýþ General SAP Name Range Ýþ /CPMB/ after you have applied notes 1448525 ,1312139, and 1437880 to the system Ýþ /B28/ after you have applied notes 1448525 ,1312139, and 1437880 to the system Ýþ Software Components: Ýþ CPMBPC Use the following procedure to set the components to Modifiable or Unmodifiable: 1. Go to transaction SE06 and choose System Change Option. 2. Make sure that the Planning and Consolidation Addon is set to Restricted Modifiability. 3. Set the namespaces and software components to Modifiable. 2. Using transaction SU01, create the following ABAP service users with a user type of Communications Data, then assign each of them to the appropriate role:
ABAP service user Role BPC_ADMIN SAP_BPC_ADMIN BPC_SYSADMIN SAP_BPC_SYSADMIN BPC_USER SAP_BPC_USER
Use transaction PFCG to check that the correct user profiles are created in the system.
2013-09-17 CUSTOMER 23/56 3 Installing Planning and Consolidation Servers 3.3 Configuring the ABAP Server Component
If these roles have not been created, generate them manually. For more information about creating and maintaining profiles, see SAP NetWeaver Library on SAP Help Portal at http:// help.sap.com. 3. Ensure ALEREMOTE is created with appropriate authorization as outlined in the NetWeaver documentation, which is available at http://help.sap.com/saphelp_nw70/helpdata/EN/ab/ 4c69f832429f419fa6f216c83dccb0/content.htm. 4. Using transaction RSTPRFC, set up transports by creating the RFC destination for the After Import method. Save the password, then assign the BW client. For more information, see http:// help.sap.com/saphelp_nw70/helpdata/en/45/b517e0ed2f52f5e10000000a1553f7/ content.htm. If the transport fails, see SAP Note 1329651 for information. 5. Using transaction SM59, run a connection test on the RFC destination MDX PARSER. NOTE If this fails, apply SAP Note 1032461. After applying this note, you must restart the ABAP server. 6. Assign the authorization SAP_BW_CONTENT_ADMIN to the user installing ApShell as the Planning and Consolidation system administration user to activate business content (such as default BW objects). 7. Assign profile S_RS_ALL to the Planning and Consolidation system administration user. We recommend that you also assign the SAP_ALL profile during the installation process of ApShell. You can remove the SAP_ALL profile after the installation. 8. If they do not already exist, create entries in the BPC Transports table by doing the following: 1. Go to transaction SM30. 2. Enter the table name UJT_TRANS_CHG, then click Maintain. 3. Choose New Entries. 4. From the TLogo Object column, select one of the available entries from the listbox, then select Development in the adjacent column. 5. Repeat step 8d for each available item in the listbox in the TLogo Object column. 6. After all entries have been added, click Save. 9. Install ApShell by doing the following: 1. Run the program UJS_ACTIVATE_CONTENT. 2. In the Content Activation window, set the AppSet ID toApShell and the Content Version to 1. 3. Choose the following options: 1½ Update Default Users 1½ Update Default Formula Table 1½ Update Client Options 1½ Update Language 1½ Activate SAP NetWeaver BW content objects for Planning and Consolidation
24/56 CUSTOMER 2013-09-17 3 Installing Planning and Consolidation Servers 3.4 Installing the .NET Server Component
bÌ Update Default DM (Data Manager) Instructions bÌ Activate ApShell 4. Run UJS_ACTIVATE_CONTENT again, this time choosing only the Load Data Into AppSet option. 5. Select Program Execute in background . 6. Check the logs by selecting System Own Jobs . 7. Select the job and display the spool. 10. Define the .NET service user that is needed to log on to ApShell and run Server Manager by doing the following: 1. Stop the IIS and SAP Planning and Consolidation instances using the stoposoft.bat file. For more information, see Tips [page 39]. 2. Go to transaction SE38 and run program UJA3_WRITE_SYS_USERS. This updates the settings in table UJA_SVR_DEFAULT with the Planning and Consolidation users defined earlier (step 2). 3. Assign a single domain user to each user type:
Planning and Consolidation System Enter
3.4 Installing the .NET Server Component Prerequisites bÌ You have installed all prerequisites. See Installing the Prerequisite Software on the .NET Servers [page 13]. bÌ You have downloaded the .NET server component. See Acquiring the ABAP and .NET Server Components [page 18]. bÌ You have uninstalled any previous version of the Planning and Consolidation server and restarted the server. NOTE To uninstall Planning and Consolidation 7.0 SP00 (with or without patches 1 or 2), run the installer of Planning and Consolidation patch 2 to make sure all the dlls are unregistered. bÌ You are logged on to the .NET server with the domain user with sufficient rights. See Configuring the ABAP Server Component [page 22].
Procedure Do the following on each .NET application and Web server: 1. Start the installation program for the .NET server component. You can download the installation file from the service marketplace.
2013-09-17 CUSTOMER 25/56 3 Installing Planning and Consolidation Servers 3.4 Installing the .NET Server Component
2. Select Next from the Welcome screen. 3. From the license agreement screen, select Agree to continue with the installation or Disagree to stop the installation. 4. Choose the location of the Xceedzip.dll and AntiXSSlibrary.dll files, then select Next. 5. Specify your user name and company name, then select Next. 6. Enter the System Administrator ID and password for the Windows Server that you are logged on to, then select Next. NOTE You should have specifically added the System Administrator ID that you use into the local administrator group. 7. Choose your target installation location (the default, and preferred, location is C:\PC_NW) then select Next. 8. Select the authentication method. You can choose Windows or CMS (Central Management System). If you select CMS as an authentication method, you are required to enter some additional identification information, including: - CMS identification information - CMS Cluster: CMS server address or IP - Cache out time: by default 300 min - Authentication Type: authentication type used by CMS server side Select Next. 9. Choose the appropriate logon group: Enabling logon groups allows the Planning and Consolidation .NET server to connect to ABAP logon groups to use the logon groups for load balancing in the ABAP tier. Select Next. 10. Enter the following information, then select Next:
Site Port Set the IIS port. If the port you set for the Planning and Consolidation site is also used by other sites, go to Internet Information Services and do one of the following: - Stop the other sites that have the same port as the Planning and Consolidation site, and start the Planning and Consolidation site manually. - Change the port of the other sites that have the same port as the Planning and Consolidation site, and start the Planning and Consolidation site manually. Message Queue The path, including the server name, where MSMQ is installed. For example,
26/56 CUSTOMER 2013-09-17 3 Installing Planning and Consolidation Servers 3.5 Configuring the .NET Server Component
NOTE If the operating system is Microsoft Windows 2008, you must run Server Manager as an administrator (right-click the icon and select Run as Administrator). For more information, see Installing and Setting Up Microsoft Message Queue (MSMQ). [external document] Message Server The name of the application server where you installed the ABAP server component. Check the System Entry properties of the ABAP application server, and enter one of the following: * If Connection Type is Group/Server Selection, enter the address of the Message Server. * If Connection Type is Customer Application Server, enter the address of the Application Server. If you want to change this location, you can change it in the Server Manager. From Server Manager, select Server Maintain ABAP System Server Host. If you are using Logon Groups to connect to multiple ABAP application servers, use the Server Manager to modify the parameters. From Server Manager, select Server Maintain ABAP System Logon Group. NOTE If the operating system is Microsoft Windows 2008, you must run Server Manager as an administrator (right-click the icon and select Run as Administrator). System ID The System ID the ABAP server component configuration. For more information, see Configuring the ABAP Server Component [page 22]. Client The client number of the NetWeaver BW client (application server). Since the NetWeaver BW client only supports one client instance, you can only install one instance of Planning and Consolidation on a single BW client. Language The language of the NetWeaver BW client (application server). System Number The system number of the NetWeaver instance (application server). Typically, this is 00, unless you have several instances with different numbers. It is the same number as indicated in the logon properties of SAP GUI, if you want to connect to the ABAP back end, for example, to execute transactions. 11. Enter the System Administrator, Administrator, and User user IDs, together with their passwords, for the ABAP service users that were created during the ABAP server component configuration. For more information, see Configuring the ABAP Server Component [page 22]. 12. Click Install, and then Finish.
3.5 Configuring the .NET Server Component You must configure the .NET server component after installing it. If you are upgrading from a previous version of Planning and Consolidation, and have already configured it, these steps are not necessary.
Prerequisites The .NET server component is installed on the .NET tier.
2013-09-17 CUSTOMER 27/56 3 Installing Planning and Consolidation Servers 3.5 Configuring the .NET Server Component
Procedure 1. Update your IIS properties as follows: 1. Go to Control Panel Administrative Tools Internet Information Services (IIS) Manager . 2. Update your IIS properties (Web Service Extensions). Uó Allow ASP .NET 2.0 by finding the Web Service Extensions property (the path to it differs for different operating system versions), and update it to allow ASP .NET 2.0. NOTE If using Windows 2008, navigate to Start Control Panel Administrative Tools Internet Information Services (IIS) Manager . Choose the appropriate computer, then open ISAPI and CGI Restrictions. Make sure that ASP.NET v2.0.50727 is allowed. If not, choose Edit to enable them. 2. Add the group Users to the Windows temp folder, and give them the following permissions: Uó Read&Execute Uó List folder contents Uó Read 3. Restart IIS. 4. If you want to use Logon Groups to connect to multiple ABAP application servers, go to Server Server Options and enter the required information. 5. Specify the domain to be used by the .NET server. Do the following: 1. Start Server Manager, and select Options Define System Users Group . 2. Enter a system user group name, Active Directory as the domain type, and the domain name. NOTE For more information, see the Managing your Planning and Consolidation Servers section of the Operations Guide.
28/56 CUSTOMER 2013-09-17 4 Post-Installation of the Server Components 4.1 Modifying Machine.config Files 4 Post-Installation of the Server Components
After you have installed and configured the server components, do the following: 1. Modify the machine.config file. See Modifying machine.config Files [page 29]. 2. Set the application pooling values for the COM+ components. See Configuring COM+ Application Pooling Values [page 31]. 3. If you are running Windows Server 2008, do the following: Hw Make sure that the related Windows authentication providers are configured properly. See Verification of Windows Authentication Providers. [page 31] Hw Add a firewall exception for the Planning and Consolidation Web site port. See Adding a Firewall Exception to the Website Port [page 32] 4. Set up the SLD Data Supplier, which is the central directory of all of your system landscape information. For more information, see Configuring the SLD Data Supplier in the Operations Guide.
NOTE If your queries contain large amounts of data, you can optionally update the metabase.xml file to improve performance. See Setting up for Large Requests [page 32].
4.1 Modifying Machine.config Files
The machine configuration file, Machine.config, contains settings that apply to an entire computer. This file is located in the runtime
Prerequisites If using Windows Server 2008, the user making modifications to this file must have special permissions to change the file.
2013-09-17 CUSTOMER 29/56 4 Post-Installation of the Server Components 4.1 Modifying Machine.config Files
Procedure If using .NET Framework 2.0 or later, do not change the ProcessModel property AutoConfig. Leave it set to its default value of TRUE. The properties described in the following procedure will be set automatically for optimal performance. If using .NET Framework 1.1, make the following changes to Machine.Config: 1. Set both the
30/56 CUSTOMER 2013-09-17 4 Post-Installation of the Server Components 4.2 Configuring COM+ Application Pooling Values
Machine.config file. If you are not using a Web farm, you do not need to change the
4.2 Configuring COM+ Application Pooling Values For load balancing purposes, set the application pooling values for the COM+ components OsoftLogging, OsoftUserManage, and OsoftWebFileManage.
Procedure 1. Choose Start Administrative Tools Component Services COM+ applications . 2. Right-click the application. 3. Choose Properties, then on the Pooling & Recycling tab, change the application pooling pool size to 4.
4.3 Verification of Windows Authentication Providers If using Microsoft Windows Server 2008, use this procedure to ensure that the related Windows authentication providers are configured properly.
Procedure 1. Open
2013-09-17 CUSTOMER 31/56 4 Post-Installation of the Server Components 4.4 Adding a Firewall Exception to the Website Port
4.4 Adding a Firewall Exception to the Website Port This procedure ensures that the client can connect to the .NET server, by adding a firewall exception to the Planning and Consolidation Web site port. To add a firewall exception: 1. Go to Control Panel Windows Firewall Allow a Program through Windows Firewall Add Port . 2. Name the exception. For example, Plan_Consol. 3. Add the port number for the Plan_Consol Web site. (This was specified during the .NET installation procedure.) 4. For the protocol, choose TCP. 5. Click OK.
4.5 Setting Up for Large Requests Procedure To allow users to request/query large amounts of data, you can edit the metabase.xml file located at C:\Windows\system32\inetsrv\. Set the following parameters to the stated values: ö, ASPBUFFERINGLIMIT = 10485760 ö, MAXREQUESTENTITYALLOWED = 10485760 If your system has more than 4 GB of memory and your operating system is Windows 2003, you must install a hotfix. You can install it from: http://support.microsoft.com/default.aspx?scid=kb;en- us;834628.
32/56 CUSTOMER 2013-09-17 5 Installing Planning and Consolidation Clients 5.1 Verifying and Installing Client Prerequisites 5 Installing Planning and Consolidation Clients
The basic steps for installing Planning and Consolidation clients include: 1. Verify and install client prerequisites. See Verifying and Installing Prerequisites [external document]. 2. Uninstall any previously installed Planning and Consolidation clients. See Uninstalling Previous Client Components [page 34]. 3. Install the Administration and Office clients. See Installing the Admin and Office Client Components [page 34]. 4. Run the silent installation. See Running the Silent Installation [page 35].
5.1 Verifying and Installing Client Prerequisites Planning and Consolidation requires the following software before installing the client components: /â A list of supported operating systems available in the Product Availability Matrix on SAP Service Marketplace at http://service.sap.com/pam. Search on Planning and Consolidation. /â XceedZip.dll (version 6.5.9417.0 or later) NOTE You must use same version of XceedZip.dll for the client as for the .NET server. You can download this component from the SAP Software Download Center (see Installing the Prerequisite Software on the .NET Servers [page 13]). /â Microsoft Internet Explorer 6.0, 7.0, 8.0 or later /â SP00 to SP04: Microsoft Office 2003 or Microsoft Office 2007 SP05 or later: Microsoft Office 2003, Microsoft Office 2007 or Microsoft Office 2010 /â Microsoft Visual Basic 6.0 runtime and Visual C++ 6.0 runtime These third party components must be installed prior to the client installation. /â All supported operating systems, except Windows 7: MSXML 4.0 SP2 Windows 7: MSXML 4.0 SP3 /â SP00 to SP04: .NET Framework 1.1 and 2.0 SP05 or later: .NET Framework 2.0, 3.0 or 3.5 NOTE /â For Windows Vista or Windows 7, it is not necessary to install .NET Framework 2.0 as a later version (.NET framework 3.0 or 3.5) is provided with the operating system.
2013-09-17 CUSTOMER 33/56 5 Installing Planning and Consolidation Clients 5.2 Uninstalling Previous Client Components
i For Windows XP, you must install Service Pack 1 and Service Pack 2 for .NET Framework 2.0. i Microsoft Windows Script (version based on the operating system) EXAMPLE If the operating system in the client machine is Microsoft Windows XP, the Microsoft Windows Script for the Microsoft Windows XP should be installed before the client installation. i Adobe Flash, 10.0 or later This is required to support business process flows. Hardware Requirements These are the minimum requirements for the client components: i Pentium IV (1 GHZ CPU) i 512 MB RAM i 100 MB of free hard disk space in the My Documents folder i 30 MB of free hard disk space for the installed Client files
5.2 Uninstalling Previous Client Components Procedure To uninstall versions of the Administration and Office client components from a previous release or support package, go to Control Panel Add/Remove Programs . If the client is installed silently, it must be uninstalled silently, as well, through run BPCClient7.5.exe /s /x /z”Uninstall” in a command prompt. You cannot use Add/remove Programs to remove the installer.
5.3 Installing the Admin and Office Client Components Typical installations include either the Admin client or the Office client on a single client machine, although you can install both if necessary.
Prerequisites i Make sure all prerequisites are installed as described in Verifying and Installing Client Prerequisites [page 33]. i Close Microsoft Office and Microsoft Internet Explorer. i Check the registry of the client machine to verify that no entry contains the value OSoftDMClientTools.DMTools. If it does exist, remove it. For more information, see the Client Installation Issues in Troubleshooting [page 43]. i Ensure that all users have write access to the registry table. i Uninstall the previous clients and restart the client machine.
34/56 CUSTOMER 2013-09-17 5 Installing Planning and Consolidation Clients 5.4 Running the Silent Installation
Procedure To install the Administration client, the Office client, or both, perform the following steps: 1. Start the client component installation on the client machine in one of the following ways: ë Go to http://
CAUTION For Office client installations, 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 to create the registry key for XCeedZip.
5.4 Running the Silent Installation Procedure 1. Download the Planning and Consolidation Install program file BPCClient7.5.exe from the SAP Service Marketplace Software Distribution Center to a local drive on your computer. 2. Uninstall the previous version of the software, if applicable, using this format:
2013-09-17 CUSTOMER 35/56 5 Installing Planning and Consolidation Clients 5.4 Running the Silent Installation
Language Selections Description EN English (United States) ZH Chinese (Simplified) FR French (France) DE German IT Italian JA Japanese KO Korean PT Portuguese (Brazil) RU Russian ES Spanish NL Dutch DA Danish NO Norwegian SV Swedish FI Finnish PL Polish SK Slovakian CS Czech ALL Selects all languages The feature selections are shown below:
Feature Selection Description Admin Specifies that you only want to install the Admin client Office Specifies that you only want to install the Office client ALL Specifies that you want to install both clients
36/56 CUSTOMER 2013-09-17 6 Basic Steps for Setting up an Initial Application Set
6 Basic Steps for Setting up an Initial Application Set
This section describes how to create an initial application set, and then how to start setting up security.
Procedure
Creating an Initial Application Set These are the basic steps for setting up an initial application set. You create this application set by copying the application set, ApShell, that is provided with Planning and Consolidation.
NOTE Do not make any changes to ApShell directly.
Prerequisites _ The server components and Administration client are installed. _ The user who creates the initial application set must be the domain user specified in the sysadmin field of the UJA3_WRITE_SYS_USERS program. To create an initial application set: 1. Log on to the Administration client. In the Connection Wizard screen, specify the Planning and Consolidation server name or IP address. Click Next. 2. Specify the user credentials for logging onto Planning and Consolidation. The first time you log on, enter the sysadmin domain user. Click Next. 3. Select APSHELL. Click Next. A summary of the connection details appears. 4. Click Finish. The Logon dialog box appears. 5. Select APSHELL, then click OK. The Administration Console loads the application set and then displays it. 6. From the Action pane, click Add a New Application Set. 7. Enter a name and description for the new application set, and click Go to Next Step 2 of 2. 8. Select all records to copy, and click Add a New Application Set to start the copy process. The new application set is created; this might take several minutes. NOTE Before you can view and edit the newly created application set after copying the ApShell application set, you must close the Administration client and then open it again. You can then make changes to it in the Administration Console.
2013-09-17 CUSTOMER 37/56 6 Basic Steps for Setting up an Initial Application Set
Setting up Initial Security To set up security for Planning and Consolidation, do the following: 1. Set up a domain 2. Add a new Admin user 3. Assign task and member access Setting up a Domain To assign users in Planning and Consolidation, you must set up a domain. Log on to Server Manager and create a domain in Options Define System User Groups. See the Operations Guide for more information. Adding a New Admin User In the new, copied application set, add an Admin user. To add an Admin user: 1. In the Logon dialog box, select the new application set, then click Connection Wizard. 2. In the Connection Wizard screen, specify your user credentials for logging onto Planning and Consolidation, then click Finish. 3. In the Logon dialog box, click OK. The Administration Console displays the application set. 4. In the hierarchical list, expand the application set. 5. Select Security Users . 6. From the action pane, choose Add new user. 7. In the User Setup screen, select a domain, and then select the user to which you want to grant Admin access. Click Next. 8. From the Assignments screen, click Next. 9. From the Finish screen, click Apply. Assigning Task and Member Access Do the following to add the Admin user to the ADMIN team, then assign full member access and task access to this team. 1. In the Administration Console, in the hierarchical list, select Security Teams ADMIN . 2. From the action pane, choose Modify Team. 3. From the Modify Team screen, click Next. 4. From the Users screen, select the new user. Click Next. 5. From the Access screen, in Task Profile, select FULL_TSK. From Member Access Profiles, select the Enable check box for AdminMbrAccPrf. Click Next. 6. From the Finish screen, review the summary and click Apply.
NOTE For more information, see the Administration section in the application help.
38/56 CUSTOMER 2013-09-17 7 Tips 7.1 Creating Start and Stop Batch Files 7 Tips
7.1 Creating Start and Stop Batch Files Follow these steps to create start and stop batch files for the server components.
Procedure 1. Create a batch file called StartOsoft.bat and ensure the contents of the batch file are as specified below. Place this batch file on the desktop. sù NET START World Wide Web Publishing sù NET START HTTP SSL sù NET START IIS Admin sù NET START IIS Admin Service sù NET START Simple Mail Transfer Protocol (SMTP) sù iisreset /start 2. Create a batch file called StopOsoft.bat and ensure the contents of the batch file are as specified below. Place this batch file on the desktop. sù iisreset /stop sù NET STOP World Wide Web Publishing sù NET STOP HTTP SSL sù NET STOP Simple Mail Transfer Protocol (SMTP) sù NET STOP IIS Admin sù NET STOP IIS Admin Service
7.2 SMS for Planning and Consolidation Package Delivery Use these instructions for SMS usage in the Planning and Consolidation installer and for patch publication.
Prerequisites Client and SMS server are installed and configured.
Procedure 1. Log on to the server on which SMS is installed. 2. Create a folder for placing published packages.
2013-09-17 CUSTOMER 39/56 7 Tips 7.2 SMS for Planning and Consolidation Package Delivery
3. Create the folders SMSPACK and AP001 on D:\, where SMSPACK is the parent folder for publishing packages with subfolders such as AP001, 002, and so on, for each package. 4. Place the Planning and Consolidation setup files in D:\SMSPACK\AP001\. 5. To publish the Planning and Consolidation setup files or to advertise them to the clients, create a package for the setup file as follows: 1. Open the SMS Admin console from Programs Systems Management Server SMS Administrator console . 2. Right-click on the packages folder, then select New Package . 3. Enter the required data. 4. On the General tab, click the data source and choose This package contains source files. 5. Set the directory of the source files to the local drive D:\, then choose Apply/OK. 6. To run this package, create a program as follows: 1. Expand the packages folder in the Admin console, right-click the programs, and select New Program . 2. Enter the Program Properties as required. NOTE If you have command line options for the setup, you can browse to choose the package and add the command line parameters next to it. If not, you can simply choose the setup file. You can use the After Running dropdown to configure the action once the package is installed. On the Environment tab, you can choose how the package should run and whether the user must be logged in or not and with what rights. If the user does not have administrator rights, select Run with administrative rights and Allow users to interact with this program. 3. Choose Apply to save the settings, then choose OK. 7. To notify client machines that a package is available, create an advertisement as follows: 1. Right-click on the Advertisements folder and choose New Advertisement . 2. Provide a name and appropriate details, and choose the package and the program. 3. Choose the systems to which the package is available. 4. Indicate whether to advertise the package at a specific time or set a mandatory assignment by choosing the yellow star button. The checkbox allows users to run the package installation independently, whenever convenient, from Control Panel or Add/Remove Programs. 5. On the Advanced tab, set the location from which you want to run the program, then choose Apply and OK. 8. Create a distribution point for this program as follows: 1. Expand the packages folder in the Admin Console, expand the package you created, and right- click the distribution point folder.
40/56 CUSTOMER 2013-09-17 7 Tips 7.2 SMS for Planning and Consolidation Package Delivery
2. Choose New Distribution point , and set the distribution point. 3. Update this with the package you created by right-clicking on the distribution points folder, selecting all tasks, and updating the distribution points. 4. Choose Yes at the confirmation message. 9. Verify that the package is available on the client side.
2013-09-17 CUSTOMER 41/56 This page is left blank for documents that are printed on both sides. 8 Troubleshooting
8 Troubleshooting
Server Installation Issues By default, the installation program runs a diagnostic program. Here are some potential error messages that display during the server installation: H “Windows Script is not installed” Download the Windows script for your operating system and then run it. H “IIS x.x is not installed” Install the relevant version of IIS with FrontPage Extensions using Add/Remove Programs in the Control Panel. H “.NET Framework x.x is not installed” Install the relevant version of .NET Framework before continuing.
NOTE For more information about installing these prerequisites, see Installing the Server Prerequisites [page 13]
Issues with IIS 7.0 H IIS 7.0 combines with ASP.NET to provide an integrated request pipeline. Using IIS 7.0 may require minor changes to your Web.config file. However, these changes may not be compatible with .NET Framework 2.0 and lead to Error 500 server access problems. For a solution to this problem, see http://msdn.microsoft.com/en-us/library/ bb515251.aspx. H IIS 7.0 adds the section system.webServer to the file Web.config. As a result, when using IIS 7.0 in Classic mode with LDAP authentication, logging on to Planning and Consolidation generates an internal server error. To solve this issue, you must manually remove the section system.webServer from Web.config, then run iisreset. H For IIS 7.0 with Windows 2008 on a 64–bit server and .NET Framework 2.0: When a Planning and Consolidation web service throws an exception, IIS 7.0 generates 500 — Internal Server Error messages. You can change the IIS settings to generate error messages that are more detailed, as follows: 1. Log on to Internet Information Services (IIS) Manager. 2. Under OSoft, double-click Error Pages. 3. In the Actions pane, choose Edit Feature Settings. 4. In the Edit Error Pages Settings window, under Error Responses, choose Detailed errors.
2013-09-17 CUSTOMER 43/56 8 Troubleshooting
Client Installation Issues By default, the installation program runs a diagnostic program. Here are some potential error messages that display during the client installation: í “Visual Basic 6.0 SP5: Run-Time Redistribution Pack not installed” Download vbrun60sp5.exe, then run it. í “Visual C++ 6.0 Run-Time not installed” Download vc6redistsetup_enu.exe, then run it. í “OSoftDMClientTools.DMTools found in registry. Please refer to system administrator before installation” Open the registry table, find the key OSoftDMClientTools.DMTool under HKEY_LOCAL_MACHINE\ \SOFTWARE\\Classes and delete this key. í “.NET Framework x.x is not installed” Install the relevant version of .NET Framework before continuing.
Server Manager Issues Always run Server Manager as the administrator. To do this, right-click the Server Manager icon and select Run as administrator. If modifying the C:\PC_NW\Websrvr\web\ServerConfiguration.config file, you must also choose Run as administrator from the right-click menu.
Service-Level Accounts Planning and Consolidation 7.5 has a new Windows service named OutlookSoft ServiceManager Service, which manages the System Landscape Directory (SLD) service, logging service and shard query engine caches. Since the service should be able to access to the FileShare server, a system administrator account is assigned automatically to the service during the installation of tehPlanning and Consolidation server program. Even though system administrator account has been assigned to the server correctly, the service may not start with the error message, The service did not start due to a logon failure. The reason for this is that the system administrator account is not registered as a service. When installing a service to run under a domain user account, the account must have the right to logon as a service on the local machine. This logon right strictly applies only to the local computer and must be granted in the Local Security Policy. To edit the Local Security Policy of the computer you want to define the logon as a service permission, perform the following actions: 1. Start the Local Security Settings Microsoft Management Console (MMC) snap-in. 2. Expand Local Policies, and then click User Rights Assignment. 3. In the right-hand pane, right-click Log on as a service, and then click Security. 4. Add the user to the policy, and click OK. 5. Close the Local Security Settings MMC snap-in.
44/56 CUSTOMER 2013-09-17 8 Troubleshooting
For more details, see How to Troubleshoot Service Startup Permissions: http:// support.microsoft.com/kb/259733.
Other Potential Issues The ABAP service users can be locked as a result of the install. Check and unlock any locked ABAP service users after performing the install. To do so, perform transaction SU01, enter each service user ID (PC_SYSADMIN, PC_ADMIN, and PC_USER), then press Ctrl+F5. You can run the Diagnostic program in Server Manager at any time. Review the steps below to determine the source of the issue. See the procedure below for more information.
Procedure 1. Run the Server Manager Diagnostic program. 2. Check that the COM+ Components exist. 3. Check the interfaces for COM+ Components. 4. Check that the librfc32.dll is set up appropriately. 5. Check the IIS Port. 6. Check the ServerConfiguration.Config file for the correct username and system information. 7. Check the Registry Entries on 32 bit and 64 bit locations. 8. Check the C:\WINDOWS\system32\drivers\etc\hosts file to ensure that a fully qualified domain and an IP resolution exists.
2013-09-17 CUSTOMER 45/56 This page is left blank for documents that are printed on both sides. 9 Connecting to Solution Manager Diagnostics
9 Connecting to Solution Manager Diagnostics
The diagnostics functions in SAP Solution Manager allow identification, analysis, and resolution of problems. This procedure provides the steps required to connect Planning and Consolidation to Solution Manager Diagnostics.
Procedure 1. Install the Diagnostics Agent according to SAP Note 1234387 on all servers where Interface for the Web and Application Servers are installed. 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.0 EHP 1 Entry by Component Agents for managed systems DIAGNOSTICS AGENT 7.11 . Download an installation file based on one of the following system landscapes: °L Windows Server on IA32 °L 32bit Windows Server on IA64 °L 64bit Windows Server on x64 64bit 2. Set up your system for Diagnostics. Refer to End-to-End Root Cause Analysis System Landscape Setup Guide, which is available on Service Marketplace at https://service.sap.com/~sapidb/011000358700000074392009E, and follow the chapters that apply to Planning and Consolidation.
NOTE After installing or upgrading to service package (SP) 6, the service PlanningAndConsolidationJobService fails to start and generates an error message. This service is not required by Planning and Consolidation and has no effect on its operation. To avoid receiving error messages, you can safely disable this service. The service PlanningAndConsolidationJobService is designed to be part of the Solution Manager analysis and log collection function in a future release.
2013-09-17 CUSTOMER 47/56 This page is left blank for documents that are printed on both sides. 10 Security Considerations and Connection Issues 10.1 Setting up SSL Encryption 10 Security Considerations and Connection Issues
Your client/server configuration is unique as it relates to security, so you may experience connection problems with SSL, proxy servers, or programs and settings that interact with these components. If you are having any issues related to connection, review the following recommendations and troubleshooting tips.
10.1 Setting up SSL Encryption We recommend that you set up Secure Socket Layer (SSL) encryption on a single Planning and Consolidation server, or on each Application and Web server that is part of a multiserver configuration.
Prerequisites You have an SSL certificate for your Planning and Consolidation IIS Server.
Procedure 1. Assign the SSL certificate: 1. From IIS, open the Web site properties, and select the Directory Security tab. 2. Choose Server Certificate, click Next, then select Assign an existing certificate. . 3. Choose your SSL certificate, and click Next. 4. Check the summary and click Finish to complete the process. 2. Set the SSL port: 1. Select the Web Site tab. 2. Change the port number to the SSL port, for example, 443. CAUTION If you change the port number in IIS, you must also change the port number the Web and Server Manager configuration files. Otherwise, the Interface for the Web and Server Manager programs do not work correctly. To change the port number for the Web configuration file, open the Web.config file:
2013-09-17 CUSTOMER 49/56 10 Security Considerations and Connection Issues 10.2 Checking for Open Ports
To change the port number for the Server Manager configuration file, open the
Result After setting up SSL security, users must enter the server name and the SSL port in the Connection Wizard when logging on to the Planning and Consolidation client applications.
EXAMPLE BPCSERVER:443
When logging on to Interface for the Web, users must use.https://
NOTE The specified server name must be the same as the server name setting in the Web.config file.
10.2 Checking for Open Ports You must ensure that all required ports are open for inbound/outbound traffic. By default, Planning and Consolidation requires that Port 80 (used by http) is open. To test whether the required port is open, go to a command prompt and enter Telnet serveripaddress. For example, Telnet 43.118.18.36 80. If the system returns a blank command window, the port is open. If it returns a message stating that it cannot connect, the port is not open.
50/56 CUSTOMER 2013-09-17 10 Security Considerations and Connection Issues 10.3 Adobe Flash Player Issues
NOTE You can use http://www.myserver.org/portsniff.asp to scan for the normal ports. It allows you to manually enter a port number to test. You can change the name of a port.
10.3 Adobe Flash Player Issues The Planning and Consolidation Flex Client uses the Adobe Flash player to generate the user interface. A limitation in the Adobe Flash player prevents the installation of the Planning and Consolidation Web server on some ports as the Flex Client cannot perform http calls on these ports.
Features From Adobe Flash player 9.0.112.0, a security control blocks commonly reserved ports to prevent malicious activity. If a port number is specified at the end of a URL, such as http://www.adobe.com: 80, the system checks the port against a list of commonly reserved ports. If the port is on this list, the network request is rejected and a security error event is generated. The Adobe Web site (http://www.adobe.com) has a Knowledge Base page, entitled URL requests to certain ports throw security errors in Adobe Flash Player 9.0.115.0 and higher, that lists the ports that Adobe Flash player considers to be reserved. You should not use the ports listed in this Knowledge Base page.
10.4 Proxy Server and Firewall Issues For questions about specific proxy servers, contact SAP Support.
General Considerations Î If you connect to the Internet through a firewall or proxy server, you need to add the IP address of the Planning and Consolidation server as an exception. You can do this at the client level ( Internet Explorer Tools Internet Options Connections LAN Settings ) or at the server level. Î Enabling content filtering on the proxy server or firewall may cause connection problems. Î If external users are having trouble connecting to the server, make sure the proxy server connects using a fully qualified domain name. Fully qualified domain names typically resolve both internal and external IP addresses. Î Each secure Planning and Consolidation server name must be identified on the proxy server. For example, if the Web server and OLAP server components both connect to a proxy server, make sure both names are identified on the proxy server. Î Proxy servers may or may not require authentication, which could conflict with Planning and Consolidation authentication. Do not use authentication on the proxy server. The system synchronizes the user name and password on the remote server with the local user name and password.
2013-09-17 CUSTOMER 51/56 10 Security Considerations and Connection Issues 10.4 Proxy Server and Firewall Issues
NOTE For more information about setting up an ISA proxy server, contact SAP Support to request a copy of the Setting up ISA Proxy Server white paper.
Internet Explorer Settings Issues Internet Explorer settings must be set correctly to prevent errors and problems when you attempt to access the Planning and Consolidation server using the Connection Wizard. Change the settings by taking the following steps: 1. From Internet Explorer, select Tools Internet Options . 2. From the General tab, delete all temporary Internet files, cookies, and history. 3. From the Security tab, set security to Default level for Internet and local intranet. 4. From the Connections tab, choose the LAN settings button. If you select Use a proxy server for your LAN, then insert the IP address or fully qualified server name of the Planning and Consolidation server as an exception by choosing the Advanced button. 5. From the Advanced tab, choose the Restore Defaults button, Apply, then OK.
Microsoft Office Issues There should only be one instance of Excel installed on the client machine. You can check this by using Add/Remove Programs. Multiple instances of Office may cause errors when you perform administrative functions in Planning and Consolidation.
Microsoft Windows Issues If you have Windows XP SP2, disable the Windows firewall.
Norton AntiVirus Issues Having Script Blocking enabled in Norton AntiVirus can cause the following issues: ¶B You cannot view the contents of the installation page in Interface for the Web. ¶B Errors downloading dimension files when logging into the Office client.
52/56 CUSTOMER 2013-09-17 11 Terminal Services or Citrix Server 11.1 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment 11 Terminal Services or Citrix Server
11.1 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.
11.1.1 Terminal Services Home Directories We recommend using Terminal Server home directories rather than using the user’s profile directory. The profile directory downloads a minimal amount of information about the dimensions of the application set you are logging on to and may be as large as 2 MB per user. The profile directory is on the system drive and has limited space. By specifying a home directory, you can manage the disk space required. If you have a farm of servers, put the profile information in a common home directory rather than on each individual server, so that all users consistently use the current download of dimensions.
11.1.2 System Requirements The following programs are required on the Terminal Services or Citrix Server computer: b Planning and Consolidation 7.5 SP00 – SP04: Microsoft Office 2003 or 2007 Planning and Consolidation 7.5 SP05 or later: Microsoft Office 2003, 2007 or 2010 b Microsoft XML 4 b VB Runtime 6.0 SP5 b VC++ Runtime 6.0 b Planning and Consolidation 7.5 SP00 – SP04: Microsoft .NET Framework 1.1 Planning and Consolidation 7.5 SP05 or later: Microsoft .NET Framework 2.0, 3.0 or 3.5
11.1.3 Installing Planning and Consolidation Prerequisites The server installation files have been downloaded from SAP Service Marketplace and installed.
2013-09-17 CUSTOMER 53/56 11 Terminal Services or Citrix Server 11.1 Installing Planning and Consolidation in a Terminal Services or Citrix Server Deployment
Procedure The following steps outline how to install the Planning and Consolidation clients in a Terminal Services (TS) or Citrix Server deployment: 1. Make sure the Terminal Services or Citrix Server machine has the system requirements installed. 2. Log on to the Terminal Services or Citrix Server machine with a user ID that has the rights to install on that server. 3. At a command prompt, enter Change user/install. 4. Open a browser and connect to the URL http://
11.1.4 Creating a Shortcut to the Launch Page Procedure If you use published desktops instead of published applications, the Planning and Consolidation desktop file (which is installed on the current user’s desktop) must be moved to the All Users/Desktop folder.
11.1.5 Terminal Services Considerations for Installing Microsoft Excel The Windows Installer, used to set up and configure programs and components of Office, uses a transform file to allow a network administrator to designate the options and features to install. Since the Terminal Server environment is different from the usual network environment, Microsoft has supplied a transform file handle the Terminal Server installation. If you attempt to use a customized transform not designated for use with Terminal Server, the system does not install Office. The transform file is named Termsrv.mst and is available with the ORK (office resource kit). Although Termsrvr.mst can be customized to include options and features that you wish to make available to Terminal Server client users, modification of the TermSrvr.mst is not supported by Microsoft.
54/56 CUSTOMER 2013-09-17 Documentation in the SAP Service Marketplace You can find this document at the following address: http://service.sap.com/instguides
2013-09-17 CUSTOMER 55/56 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 2013 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.