Perform a Multi-Server Installation of SAP BPC (MS SQL 2005) Version 1.00 January 2008

Transcription

1 How-to Guide SAP CPM How To Perform a Multi-Server Installation of SAP BPC (MS SQL 2005) Version 1.00 January 2008 Applicable Releases: SAP BPC 5.1

2 Copyright 2007 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 PowerPointare 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, z/os, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation 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, 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. These materials are provided as is without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP shall not be liable for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. SAP does not warrant the accuracy or completeness of the information, text, graphics, links or other items contained within these materials. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third party web pages nor provide any warranty whatsoever relating to third party web pages. SAP CPM How-to Guides are intended to simplify the product implementation. While specific product features and procedures typically are explained in a practical business context, it is not implied that those features and procedures are the only approach in solving a specific business problem using SAP. Should you wish to receive additional information, clarification or support, please refer to SAP Consulting. Any software coding and/or code lines / strings ( Code ) included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, except if such damages were caused by SAP intentionally or grossly negligent.

3 1 Introduction SAP Business Planning and Consolidation has a very versatile platform that allows for many deployment scenarios. The more scalable the design is, the more complex the installation tends to be. This guide attempts to diminish the complexity of the installation process by outlining a standard multi-server installation of SAP BPC on two servers. This is certainly not the only, or best, deployment scenario for all situations, but should be general enough to be useful in any multi server installation. User ID(s) for Multi Server Environment A domain account is required while performing a multi server installation. The user account should be in the same domain as the servers themselves. For example, if you have two trusted domains, one with user accounts (USERDOMAIN) and one with resource accounts such as servers (RESOURCEDOMAIN) the installation account should be created in the domain RESOUREDOMAIN. This will ensure successful authentication between SAP BPC and its required components (Microsoft SQL, etc). The installation user account(s) should not expire. If there is a policy requiring accounts to expire every x number of days, care should be taken maintaining the service account(s) as the BPC installation will cease to work once the account is expired. The installation user should be a member of the local Administrators group on each server involved in the installation. Please note, important steps will have the following font color. 1

4 The Step By Step Solution This how to guide provides guidance on the installation of SAP Business Planning and Consolidation in a multi server environment on the Microsoft SQL 2005 platform. It will review the installation and configuration for a two server installation. The first server will have the following components installed/configured: Microsoft SQL Server 2005 Enterprise Edition (64 bit) Microsoft Analysis Services 2005 Enterprise Edition (64 bit) The second server will have the following components installed/configured: IIS Microsoft Reporting Services 2005 Enterprise Edition (32 bit) Microsoft SQL Server 2005 components (32 bit) o Integration Services o Workstation Components, Books online, and development tools o Client Components SAP BPC 5.1 and prerequisites SAP BPC file share After the install is complete, we will review the process on installing the SAP BPC 5.1 SP and outline some basic steps for testing the installation. *** Verify that ALL SQL, OLAP, File, Web and Application servers were installed with the English - (United States) system locale / default locale before installing any SQL, OLAP or BPC specific components. *** 1.1 Install Microsoft SQL and Analysis Server Log into the DB/OLAP server with your install user account. D_WDF_R3\OsoftUser is the install user in this how to guide. 2. Launch the SQL 2005 installation. I am using SQL bit media on the DB/OLAP tier but the process would be similar with 32 bit media. As with most software installations, the first step is to accept the license agreement. 2

5 3. Click the install button to install the prerequisites. 4. Click Next when the Prerequisite installation completes. 5. Next, the installer will verify the systems configuration. 3

6 6. Once the configuration check completes the SQL Server installation continues with a Welcome screen. Click Next. 7. The SQL installation performs a more in depth configuration check. Upon successful completion click Next. 8. Note - You can disregard errors related to IIS as long as Reporting Services will not be installed on this server. 9. Enter the license information and click Next. 4

7 10. SQL Server Database Services and Analysis Services are required for this configuration. Workstation components are not required, unless you wish to have access to all of the SQL tools on the server. You should change the location of the Data Files for both Database Services and Analysis Services. This is done by clicking Advanced. 11. Change the path of the Data Files for Database and Analysis services to a location other than the C drive. Change other installation paths if required. Click Next. 12. The next dialog prompts you for your SQL Instance name. I will use the default instance in this guide. If you use a named instance make sure to record it as it will be required later when installing SAP BPC. 5

8 13. Add the domain user service account information for the SQL service accounts. Set all services to start at the end of setup. Click Next. 14. SAP BPC can work with Windows or Mixed authentication mode. Select the appropriate mode for your environment. This can be changed after the installation if necessary. 15. SAP BPC requires that the collation be set to SQL_Latin1_General_CP1_CI_AS. Make sure that you select this collation. Click Next. 6

9 16. The Error and Usage Report selections do not have an impact on the SAP BPC installation. Select the appropriate options and click Next. 17. The SQL Installer provides you with an overview of the components to be installed. Click Install to continue. 18. During this step the installation occurs and displays its progress. Once complete the final status of the installation is displayed. Each step should complete with a green checkmark. If any errors occur they need to be addressed before continuing. Click Next. 7

10 19. Lastly, you are presented with additional details on the installation and a link to the Summary Log. The installation is now complete. Continue to SQL and Analysis Services 2005 Network Configuration. 8

11 1.2 SQL and Analysis Services 2005 Network Configuration This section reviews the process of enabling TCP/IP for both the Microsoft SQL Server and Analysis Server engines. It also outlines the process for ensuring that both services are configured to use static TCP ports. 20. Launch SQL Server Configuration Manager. 21. Verify that TCP/IP is enabled for SQL Server. Expand SQL Server 2005 Network Configuration and select Protocols for MSSQLSERVER (or Instance name if set during install). Verify the TCP/IP is enabled. If it is not, right click on TCP/IP and select Enable. 22. Verify the TCP Port used by SQL Server. Right Click TCP/IP and select Properties. Select the IP Addresses tab. Verify that the TCP Dynamic Ports value is not set. Also verify that the TCP Port is set for all network adapters. Note, the default Microsoft SQL TCP port is Make sure to apply any changes. 23. Close SQL Server Configuration Manager. 9

12 24. Launch the Microsoft SQL Server Surface Area Configuration tool. Select Surface Area Configuration for Services and Connections. 25. Verify that TCP/IP is enabled. Navigate to Analysis Services -> Remote Connections. Verify that Local and remote connections is selected. Select OK. Close the Surface Area Configuration tool. 26. If you installed Analysis Services under the default instance you do not need to modify the TCP port. It will default to TCP Port If you installed Analysis Services using the default instance name please continue to the next section, Applying SQL Service Packs. 27. If you installed Analysis Services in a named instance you should configure a static port for Analysis Services. To do this, launch Microsoft SQL Server Management Studio. 28. Connect to the Analysis Services Server. Note, to connect to a named instance of Analysis Server with SQL Management Studio use a server name in the following format. ServerName \ InstanceName. 10

13 29. Verify the Analysis Services TCP Port. Right Click on the database server name in SQL Server Management Studio and select Properties. Select the General Page and enable Show Advanced (All) Properties. Scroll down to the Port setting. If it is set to 0 then dynamic ports are enabled. Set this to an unused TCP port. Click OK. 30. SQL and Analysis Server Network configuration is now complete. Restart the SQL/OLAP server and continue to Applying SQL Service Packs. 1.3 Applying SQL Service Packs This section reviews the process of installing a Microsoft SQL 2005 service pack. Microsoft SQL 2005 service packs can be obtained from Microsoft s web site ( There are 32 and 64 bit versions. Make sure to download the appropriate version for your installation. Service Pack 2 for SQL 2005 is required for BPC 5.1. Review the current installation guide for the current requirements. 31. Launch the SQL 2005 Service Pack 2 executable. Click Next on the welcome screen. 11

14 32. Review and accept the license terms. Click Next. 33. The appropriate features will be selected. Click Next. 34. Select Windows Authentication. Click Next. 12

15 35. Review the error and usage reporting options. Click Next. 36. The installer checks for locked files that would require a reboot. Click Next. 37. Click Install. 13

16 38. You will be notified that the system should be rebooted to complete the installation. Click OK. 39. Click Next. 40. Review the summary information. Click Next. 14

17 41. Deselect Launch the User Provisioning Tool and click Finish. 42. Restart the server. 1.4 Verify DNS Configuration SAP BPC uses Active Directory for authentication in a multi server environment. Active Directory requires DNS to be configured correctly in order to function properly, thus proper DNS configuration is a requirement for SAP BPC in a multi-server environment. This section will review how to verify your DNS configuration. Contact your network administrator if you encounter issues with your DNS configuration. 43. To verify DNS settings open a command prompt on each server and issue the following commands for each server in the environment. 44. Issue the command nslookup servername.domain.name and verify that it returns the correct IP address for the server. This checks the A or host DNS record. 45. Issue the command nslookup ip.address and verify that it returns the correct fully qualified hostname (servername.domain.name). This checks the PTR or reverse lookup DNS record. 46. If any of these are incorrect work contact your network administrator. 15

18 1.5 Install Microsoft Reporting Services 2005 Prerequisites This section will show you how to verify that IIS is installed and configured properly for both Microsoft Reporting Services and SAP BPC. This process will take place on the Web/Application server. If you have to modify your IIS installation then you must also reapply any Windows Server 2003 service packs to ensure that your IIS installation is up to date. This must be done before you actually install Microsoft Reporting Services Log onto the application server. Open Add/Remove Programs, Windows Components and verify that the required IIS Components are installed. 48. Application Server details 49. Internet Information Services (IIS) details 16

19 50. World Wide Web Service details 51. If any changes were made, click OK on each of the details dialog boxes. Once you get to the Windows Components Wizard dialog box select Next 52. When the installation is complete, click Finish. 53. *** Note, you may be prompted for installation media during the install. 54. *** Note, if you had to add components for IIS then you will need to reapply any Windows 2003 services packs at this point. 17

20 55. Configure IIS. Open the Internet Information Services (IIS) Manager administrator tool. 56. Allow the ASP.NET v and ASP.NET v Web Service Extensions. 57. Create a new application pool for ASP.NET v2. Right Click on Application Pools and select New - > Application Pool. 18

21 58. Enter an Application pool ID. Leave Use default settings for new application pool selected. Click OK. 59. Right Click on Default Web Site and select Properties. Select the ASP.NET tab and verify that the ASP.NET version is Close Internet Information Services (IIS) Manager. 1.6 Install Microsoft Reporting Services 2005 This section will review the installation of Microsoft Reporting Services Please note, the SAP BPC application server requires a 32 bit version of Windows Server 2003 as of release 5.1. Because of this we will install the 32 bit version of Microsoft Reporting Services 2005 in this configuration. 19

22 61. Log into the APP/Web server with your install user account. 62. Launch the SQL 2005 installation. We will be using the 32 bit version of SQL here, as this will also host the SAP BPC application install which requires a 32 bit OS. Again, the first step is to accept the license agreement. 63. Click Install to install the prerequisites. 64. Click Next once the prerequisites installation finishes. 20

23 65. Click Next on the Welcome screen. 66. If any errors occur in the System Configuration Check correct them before continuing. Click Next after a successful System Configuration Check. 67. Enter your registration / license information. Click Next. 21

24 68. Select Reporting Services, Integration Services and Workstation components. Click Advanced to change installation paths or Next to continue without altering installation paths. 69. If you decide to change installation paths, make sure you check the location of all components. Click Next to continue. 70. Select your instance name for Reporting Services. Click Next 22

25 71. Enter the install users information for the service account. Verify that Reporting Services is selected to start after installation. Click Next. 72. Click Next to continue. Note, the Report Server Installation Options will be grayed out because Microsoft SQL Server is not installed on this server. 73. Select your Error reporting options. These choices do not effect the installation. Click Next. 23

26 74. Click Install. 75. Verify that all components were installed successfully. Click Next. 76. Click Finish. 1.7 Configure Microsoft Reporting Services 2005 This section will review the post installation configuration of Microsoft Reporting Services

27 77. Launch the Reporting Services Configuration tool. 78. Enter the connection information for the newly installed instance. If you installed the default instance, then the instance name is MSSQLSERVER. Click Connect. 79. Select Report Server Virtual Directory in the left hand pane. You will see the settings in the right hand pane. Click the New button. Leave the defaults. Click OK. The Report Server virtual directory will be created. 80. Select Report Manager Virtual Directory in the left pane. Click New. Leave the defaults. Click OK. The Report Manager virtual directory will be created. 25

28 81. Select Web Service Identity in the left pane. Set the Application Pool for Report Server and Report Manager to the Application Pool created in the Reporting Services 2005 Prerequisites section. Click Apply. 82. Select Database Setup in the left pane. Enter the database server name in the Server Name field and click New. Leave the defaults on the Connection Dialog and click OK. The Reporting Services database will be created. 83. While still in Database Setup, select Windows Credentials for credentials type and enter the install users credentials for Account Name and Password. Click Apply. 26

29 84. Select OK in the SQL Server Connection Dialog. The Database Setup task will be completed. 85. At this point the Initialization item in the left pane should have a green check mark next to it. Configuration is complete. Close the Reporting Services Configuration Manager tool. 1.8 Apply Service Pack 2 for Microsoft Reporting Services 2005 In this section we will review the installation of Service Pack 2 for Microsoft Reporting Services This process is effectively the same as installing the service pack for Microsoft SQL Server If fact, it is the same service pack. Make sure you have the correct service pack version (32 bit). 27

30 86. Launch the SQL 2005 Service Pack 2 executable. Click Next on the welcome screen. 87. Review the license terms. Click Next. 88. The appropriate features will be selected for upgrade. Click Next. 28

31 89. Leave the default authentication information. Click Next. 90. Click Next. 91. Click Next 29

32 92. Click Install. 93. Once the install is complete you will receive a notification that the server will need to be restarted. Click OK. 94. Click Next. 30

33 95. Click Next. 96. Deselect Launch the User Provisioning Tool for Windows Vista after SP2 installation completes. Click Finish 97. Restart the application server. 1.9 Install SAP BPC 5.1 Prerequisites In this section we will review the installation of the BPC 5.1 prerequisites. We will create the file share and install ADOMD and MSXML. The ADOMD and MSXML installers can be found with the BPC 5.1 setup files. We will also copy the ApShell.db9 database from the SAP BPC Setup folder on the Application Server to a temporary location on the Database Server. 31

34 98. Create a directory on the application server for the file share. The path will be d:\bpc\share for this example. Right click on the folder and select properties. 99. Select the Sharing Tab. Select Share this folder. Enter Osoft as the share name then, click Permissions. Remove Everyone and add the install users account. Grant the install user Full Control. Click OK in the Permissions dialog box. 32

35 100. Select the Security tab. Add the install user and grant the account Full Control. Click OK Navigate to the \BPC Setup\Server directory. Double click on ADOMD.NET.msi. Click Next Select I agree. Click Next. 33

36 103. Click Next The install will be very quick. Click Close Navigate to the \BPC Setup\Server directory. Double click on msxml.msi. Click Next Select I accept. Click Next. 34

37 107. Enter your customer information. Click Next Click Install Now Click Finish Navigate to the \BPC Setup\Server directory. Copy ApShell.db9 to some location on the database server. I will use d:\tmp. Record this location. It will be used during the SAP BPC Installation Install SAP BPC 5.1 In this section we will review the installation of SAP BPC

38 111. Navigate to the \BPC Setup directory. Double click on Startup.exe. Select Install BPC on SQL Click Next Enter your Company Name and the path to your Product key then click Next. 36

39 114. Review and accept the license agreement. Click Next Select Custom multi-server. Ensure that Application Server, Sample Application and Web Server are all select. Click Next Enter the install user id and password for System Admin ID, Admin ID and User ID. Different accounts can be used if required. Check the install guide for more details. The Password is only checked for the System Admin ID. It is vitally important that you type the correct password for the Admin ID and User ID as well. Click Next. 37

40 117. Select Advanced Settings. Enter the fully qualified domain name of the database server for SQL Server name, OLAP Server name and Insight OLAP Server name. Enter the path to the ApShell DB. This should match the destination directory of ApShell.db9 from the SAP BPC Prerequisites section. The Instance Name should only be entered if you chose a non-default instance. The Port Number should also only be entered if it is not the default port (1433 for SQL, 2383 for Analysis Services). Entering a Port Number or an Instance Name when the defaults were used will cause issues. Leave them blank if the default Port and/or the default Instance Name were used Enter the fully qualified domain name for the Application Server under File Share Server name. Enter the Local data path to match the location of the file share we created in the SAP BPC Prerequisites section Enter the fully qualified domain name for the Web/Application Server under Reporting Services Server Name. Only enter an Instance Name if a named instance was created during the Microsoft Reporting Services 2005 install Enter the fully qualified domain name for the Web/Application Server under Application Server Name Enter the fully qualified domain name for the Web/Application Server under Scheduler Server Name and Web Server Name. 38

41 122. Click Next Set the destination installation directory under Program Path. Click Next. The installation will begin Click Finish. 39

42 1.11 SAP BPC Post Install Task 1 Server Diagnostics In this section we will launch the Server Diagnostics component of the SAP BPC Server Manager Launch Server Manager Select the Server menu item, and click Diagnostic Verify that no errors are detected SAP BPC Post Install Task 2 COM+ Object Review In this section we will view the COM+ Objects in the Component Services MMC on the Web/Application server to verify that they have all been created. 40

43 128. Launch the Component Services MMC Expand Component Services -> Computers -> My Computer -> COM+ Applications. Verify COM+ Services were created and are associated with the install user ID. SAP BPC COM+ components begin with the prefixes EV, K2, and OSoft. Close the Component Services Snap-In SAP BPC Post Install Task 3 Verify Database Creation In this section we will verify that all required databases (SQL and OLAP) were created Launch SQL Server Management Studio (on either the DB or Web/App server) and connect to your Analysis and SQL server instances. 41

44 131. Verify that the ApShell OLAP database was created. Also verify that the AppServer, ApShell, ReportServer and ReportServerTempDB SQL databases were created. You may also see the ApShellExtra database if you have already logged into BPC Administration. Close SQL Server Management Studio SAP BPC Post Install Task 4 Install BPC SP1 In this section we will install SAP BPC SP1. It will be performed on the Application Server Double Click on Setup.exe from the SP1 setup files. Click Next. 42

45 133. Review and accept the license. Click Next Enter the install users credentials for System Admin, Admin and User. Be very careful when entering the passwords. Click Next Click Finish. 43

46 136. Restart the Application server SAP BPC Post Install Task 5 Test Basic SAP BPC Administration In this section we will install the SAP BPC Administration client and test some basic SAP BPC Administration functionality. Perform these steps from a system that has Microsoft Office (Excel, Word, PowerPoint) installed, and you should be logged in as the SAP BPC install user Open Internet Explorer and go to Click on Client Software Center Select BPC Administration Installation. 44

47 139. Click Next Click Next Review and accept the license terms. Click Next Restart your computer if prompted. 45

48 143. Go back to Click on BPC Administration Select Manage Security from the Action Pane Enter the server name in the BPC server name: text box. Click Next. 46

49 146. Enter the install users credentials in the Logon Information section. Click Next Click Next Click Finish. 47

50 149. Click OK Expand Security -> Users -> Domain and select your install user. Click Modify User in the Action Pane Click Next Select Admin Team from the team drop down. Select your install user under Available Users. Press the > button and enable the check box next to your install users name. Click the Assign to Task profiles tab. 48

51 153. Select PrimaryAdmin from the Task Profile drop down menu. Select your install user under Available Users and click the > button. Click the Assign to Member Access profiles tab Select AdminMbrAccPrf from the Member access profile drop down. Select your install users account under Available Users. Click the > button. Click Next Click Apply. 49

52 156. Click OK Expand ApShell -> Dimension Library and select Account. Click Process Dimension in the Action Pane Click OK Verify that the dimension was processed successfully. Click OK. 50

53 160. Expand ApShell -> Application and select Finance. Click Modify Application in the Action Pane Select Process Application in the Action Pane. Click Modify Application Verify that the application was processed successfully. Click OK. Exit SAP BPC Administration. 51

54 52