ORACLE HYPERION INSTALLATION GUIDE FINANCIAL MANAGEMENT SYSTEM 9 RELEASE P/N: DF

Transcription

1 ORACLE HYPERION FINANCIAL MANAGEMENT SYSTEM 9 RELEASE INSTALLATION GUIDE P/N: DF

2 Financial Management, Release 9.2.1, Installation Guide Copyright 2000, 2009, Oracle and/or its affiliates. All rights reserved. Authors: EPM Information Development Team This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS: Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR , Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA This software is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications. This software and documentation may provide access to or information on content, products and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third party content, products and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third party content, products or services.

3 Contents CHAPTER 1 Installation Overview Financial Management Installation Introduction Additional Products Shared Services Financial Reporting Data Integration Management Adapters Hyperion Application Link Smart View Financial Management Configurations CHAPTER 2 Financial Management Installation Sequence Financial Management Installation Checklist CHAPTER 3 Planning the Installation Hardware Requirements Client Tier Middle Tier Software Requirements Client Tier Middle Tier Database Tier Supported Authentication Sources Required Hyperion Products Required Installation Documentation Port Numbers Used by Hyperion Products Default Port Numbers for Remote Method Invocation (RMI) Servers CHAPTER 4 Installing and Creating a Database Creating a Financial Management Database in Oracle Creating a Financial Management Database in Microsoft SQL Server Creating a Financial Management Database in IBM DB Creating a Shared Services Database Creating Data Link (UDL) Files Contents iii

4 Configuring the Data Link for Oracle Configuring the Data Link for Microsoft SQL Server Configuring the Data Link for IBM DB Encrypting UDL Files Database Connection Pooling CHAPTER 5 Installing Financial Management Server Components Installing Microsoft Internet Information Services Verifying the IIS Installation About Hyperion Home Hyperion Home Location Changing the Hyperion Home Location Installation Files and Directories What Happens During Installation Directories and Files Installed Installing Financial Management Installing Only Web Server Components Installing Only the Analytic Data Model (ADM) Driver Installing the HFM Software Development ToolKit Performing Silent Installations of Financial Management Creating the Response File Running the Silent Installation CHAPTER 6 Installing the Client Tier Components Installing Financial Management on the Client Installing Smart View Verifying Communications Between the Application Server and Client CHAPTER 7 Configuring and Setting Up Financial Management Hyperion Configuration Utility Prerequisites Task Sequence Configuring Product Upgrades Launching the Configuration Utility Registering Products with Shared Services Deregistering Products with Shared Services Reconfiguration Configuration Troubleshooting Completing Financial Management Configuration Using the Financial Management Configuration Utility Configuring Application Servers iv Contents

5 Configuring DCOM Security Information Specifying the Application Creator and Administrator Groups Setting Server Working Folder and Database Information Enabling Multiple Server Support Specifying a Data Source for Extended Analytics (Optional) Configuring Application Server Clusters Enabling Remote Activation (DCOM Limits for 2003 and XP) Configuring Security Registering Application Server Clusters Enabling DCOM Configuring Web Servers Specifying Web Directories Specifying the File Transfer Directory Setting ASP Properties (Optional) Enabling SiteMinder Web Security Agent Support (Optional) Specifying Support for Alerts Specifying URLs for Other Hyperion Applications Setting Web Server DCOM User Information Configuring Related Content Configuring Smart View for Office Services Setting Up the Web Server for Web Authentication Setting Up Proxy Authentication Running IIS 5.0 Isolation Mode in IIS 6.0 on Windows Verifying Startup Dependencies Starting Shared Services Verifying Successful Startup of Shared Services Testing Installed Components Creating a Shared Services Project Using Sample Files Creating Test Applications Opening Test Applications Loading Sample Files Viewing Sample Data CHAPTER 8 Uninstalling Financial Management Uninstalling Prior Releases Uninstalling Shared Components Uninstalling Shared Services CHAPTER 9 Upgrading to Financial Management Upgrading Overview Backing Up Applications Contents v

6 Backing Up Database Information Verifying MDAC Version on the Application Server Uninstalling Prior Releases Uninstalling Shared Components Uninstalling Shared Services Installing Financial Management Installing Financial Management Server Components Installing Financial Management on the Client Upgrading Applications from Prior Releases Using the Schema Upgrade Utility CHAPTER 10 Installing Additional Hyperion Products Installing Financial Reporting Accessing Financial Reporting Web Applications Installing the Hyperion Application Link Adapter Updating Financial Management Adapter Updating Financial Management Adapter Installing Data Integration Management Adapters Installing Adapters in Silent Mode Installing Adapters in Console Mode Configuring Adapters Uninstalling Adapters APPENDIX A Troubleshooting Troubleshooting Application Server Configuration Establishing the SQL Server Connection Using TCP/IP Verifying Data Link Connection Settings Verifying Microsoft SQL Server Authentication Settings Troubleshooting Applications Troubleshooting Shared Services Index vi Contents

7 Chapter 1 Installation Overview This chapter describes Financial Management components and provides a high level view of the installation process. In This Chapter Financial Management Installation Introduction Additional Products Financial Management Configurations Financial Management Installation Introduction Financial Management is a comprehensive, Web-based application that delivers global collection, financial consolidation, reporting, and analysis in one highly scalable solution. Financial Management is designed to operate as a multitier system. A Financial Management configuration contains three logical tiers: a database tier, application/web server tier (also referred to as the middle tier), and client tier. The database tier contains the relational database and all Financial Management data and metadata. Supported databases include Oracle, Microsoft SQL Server, and IBM DB2. The application/web server tier, or middle tier, contains the domain intelligence and connections to the relational database, application server, and Web server. You can access the Financial Management Web-enabled portions in this tier. The client tier provides the user interface and the ability to communicate with the application tier. You can display data and metadata, enter data, and maintain metadata in this tier. Financial Management has a thin Web-client architecture so that basic users require only a supported browser on a client computer. No processing or business rules occur on the client. The client is offered through Web servers or through a Windows client installed on the local computer. Installation Overview 9

8 Additional Products Beginning with this release, Hyperion License Server and standalone license files are not used for license management. Instead, administrators need to audit product use. To ensure compliance with your license agreement, you need to edit a properties file to activate or deactivate features in accordance with what you have purchased. For more information about license compliance, see the Hyperion License Compliance Readme (hyp_license_compliance_readme_921.pdf), which you can find on the Oracle E- Delivery site or the product DVD. Shared Services Features enabled by Shared Services: User provisioning External authentication definition Metadata synchronization Data synchronization Task flow management The Hyperion System 9 Shared Services User Management Guide describes user-provisioning functionality. The Hyperion Shared Services Installation Guide describes external authentication definition. All other Shared Services functionality is described in the administrator s and user s guides for the products that implement Shared Services. Financial Reporting Oracle s Hyperion Financial Reporting System 9 enables you to create highly formatted reports that combine text, data grids, charts, graphs, and images. In addition to providing complete control over layouts, formatting, fonts, and colors, Financial Reporting provides powerful business analytics, such as conditional suppression and automatic calculations, that can be used to focus and filter reports. A repository of reusable report components simplifies the process of building and maintaining complex reports. Data Integration Management Adapters Oracle s Hyperion Data Integration Management adapters enable you to retrieve and write data for Financial Management and transfer application data to an external target. 10 Installation Overview

9 Hyperion Application Link Oracle s Hyperion Application Link is a suite of application integration services that integrates external source data with Hyperion s business analysis software. You can use it to load data values, accounts, entities, and custom dimensions from flat files or ODBC-compliant databases into Financial Management. Smart View Oracle s Hyperion Smart View for Office provides a common Microsoft Office interface for Hyperion products. Using menu-driven options in Microsoft Office, you can import data and images from Hyperion products into Microsoft Office components such as Excel, Word, and PowerPoint. In addition, you can work with Financial Management functions and data forms in Smart View. Financial Management Configurations Financial Management uses N-Tier architecture to deploy mission critical consolidations and reporting applications to hundreds and even thousands of users. Load balancing is used to support large numbers of concurrent users. In general, load balancing is a way of dividing concurrent usage as equally as possible across a cluster of machines. To end users, the machines in a cluster seem to be one machine but, behind the scenes, the system assigns users to various servers to help distribute the load. There are two types of automatic load balancing: session level and request level. With session level load balancing, the user performs all operations from logon to logoff on one application server, but may perform the operations of another session on another machine. Usually, this type of load balancing is used for applications that must maintain state throughout a user s session. Financial Management falls into this classification. Load balancing can be achieved through the Financial Management Clustering feature. The administrator configures a cluster to include all Financial Management application servers. During logon, the user selects the cluster name. Using a random approach, Financial Management logs users on the application servers defined in the cluster, thereby spreading the users across the available servers. Financial Management generates a random number by using time (milliseconds) as a parameter and logs each user on the appropriate server. Using milliseconds helps guarantee random assignments if users log on at the same time. If any server fails, the cluster is automatically notified and the failed server is removed from the list of available servers. Any users logged on to the failed server must log on again, using the cluster. Users are automatically assigned to available servers. It is possible to have a server that is not part of the cluster but is synchronized with the other application servers in the cluster. Thus a dedicated reports or consolidation server can be used with servers that are part of the cluster. Clustering applies only to the Financial Management application server and does not apply to the Web server or Database server tiers. Financial Management Configurations 11

10 End-user load balancing is a way of distributing concurrent usage as evenly as possible across multiple servers. If you use multiple application servers, you can specify a cluster of application servers through which to distribute the user load. For example, you can create an application server cluster named Marketing_Servers and add application servers Mkt1, Mkt2, Mkt3, and Mkt4 to the cluster. You can add or remove servers from an application server cluster as needed. In random load balancing, requests are randomly routed to servers. Random load balancing is commonly used for homogeneous cluster deployments such as Financial Management. In random load balancing, users are distributed evenly, thus all servers in a cluster should have similar configurations to prevent unpredictable performance. If one machine in a cluster has significantly less processing power than other machines in the cluster, random load balancing gives the less powerful machine as many requests as it gives more powerful machines. The client computer stores a list of the available servers in the local registry. Upon logon, the computer randomly selects a server and attempts to log on. If the selected server has a problem, it is removed from the local list, and the client computer randomly picks another server. After the client computer connects to a server, it asks the server to which it is connected for an updated list of servers. The client computer updates its local registry with the new list in preparation for the next log on request. Web-based operations occur similarly, except that the registry is maintained on the Web server and updated after each user logon. By using the registry to store available server information, the Web server avoids relying on a central server to process all logons. 12 Installation Overview

11 Chapter 2 Financial Management Installation Sequence This chapter provides the following information about installing, and configuring Financial Management: High-level task flow that identifies basic steps Installation checklist to guide you through each step in the installation and configuration process STEP INSTRUCTION PRODUCT COMPONENT DOCUMENTATION 1 Install Shared Services and configure the Shared Services application server and RDBMS. 2 Configure Shared Services to authenticate user names that are stored externally in LDAP, Active Directory, or Windows NT LAN Manager, enabling single sign-on. Shared Services installer Configuration Utility Shared Services External Authentication Configuration Console Shared Services Installation Guide Shared Services Installation Guide 3 Install Hyperion products. Hyperion product installers Product installation guides 4 Activate and configure Hyperion products and register them with Shared Services. You can configure multiple products at one time, if they are installed on the same computer. 5 Create projects, add applications to projects, and provision users for applications. Configuration Utility Shared Services User Management Console Product installation guides Hyperion System 9 Shared Services User Management Guide Financial Management Installation Sequence 13

12 Financial Management Installation Checklist This checklist contains steps required for a successful Financial Management installation. Page numbers refer to the Financial Management Installation Guide unless otherwise noted. If you are upgrading, see Chapter 9, Upgrading to Financial Management Before you begin the installation process, ensure that you meet the hardware and software system requirements outlined in Chapter 3, Planning the Installation. INSTALL SHARED SERVICES AND CONFIGURE THE SHARED SERVICES APPLICATION SERVER AND RDBMS 1. Ensure that the database you are using for Shared Services is installed and operational before installing Shared Services. 2. Download Shared Services software and documentation. 3. Install Shared Services and configure the Shared Services Application server and RDBMS. REFERENCE Hyperion Shared Services Installation Guide CONFIGURE THE SHARED SERVICES EXTERNAL AUTHENTICATION PROVIDER REFERENCE 1. Ensure that your Shared Services server is running. 2. Using Shared Services, configure one of the following External Authentication Providers: Windows NT LAN Manager (NTLM) Lightweight Directory Access Protocol (LDAP) Microsoft Active Directory (MSAD) Shared Services writes your configuration information to a central XML-based security configuration file that is generated by Shared Services. Financial Management references the security configuration file for single sign-on of external and remote users. 3. Set up the environment and user rights for NT LAN Manager support. 4. Optionally, set up the environment for Netegrity Single Sign-on, configure Shared Services to use Single Socket Layers, and install the Hyperion Remote Authentication Module. Hyperion Shared Services Installation Guide DATA TIER INSTALLATION TASKS REFERENCE Install and configure a database for Financial Management. See Chapter 4, Installing and Creating a Database. MIDDLE TIER INSTALLATION TASKS REFERENCE Install Financial Management. See Installing Financial Management on page 38. CLIENT TIER INSTALLATION TASKS REFERENCE Install Financial Management. See Installing Financial Management on the Client on page Financial Management Installation Sequence

13 CONFIGURATION TASKS REFERENCE Activate and configure Financial Management and register with Shared Services using the Hyperion Configuration Utility. Activate Financial Management. Specify the Shared Services Server location. Configure relational databases and repositories. Auto-deploy products to application servers (recommended). If preferred, select the Manual Deployment option to manually configure the deployment. The Shared Services server must be running to perform this step. Launching the Configuration Utility on page 50 Using the Financial Management Configuration Utility on page 53 POST-CONFIGURATION TASKS REFERENCE Test the installation. ASSIGN ROLES FOR SHARED SERVICES USER MANAGEMENT AND PROVISION USERS A Shared Services administrator must perform these tasks: Assign the Project Manager role to users who are responsible for creating projects and assigning applications to projects. For each application, assign the Provisioning Manger role to users who are responsible for assigning roles and access control permissions to application users. Assign the Directory Manager role to users who are responsible for managing the native Shared Services directory. Project Managers can now create projects and add applications to projects. Provisioning Managers for each application can now provision users and groups (assign roles and access control permissions) for their applications. INSTALL ADDITIONAL PRODUCTS (OPTIONAL) Install Smart View on the client tier (requires Microsoft Office 2003, 2002 XP or 2000 SP1). Install the Data Integration Management adapter or Hyperion Application Link adapter. Install Financial Reporting. Testing Installed Components on page 69 REFERENCE Hyperion System 9 Shared Services User Management Guide REFERENCE Installing Smart View on page 45 Chapter 10, Installing Additional Hyperion Products Hyperion Reporting and Analysis Installation Guide Financial Management Installation Checklist 15

14 16 Financial Management Installation Sequence

15 Chapter 3 Planning the Installation This chapter lists Financial Management hardware and software requirements. In This Chapter Hardware Requirements Software Requirements Required Hyperion Products Port Numbers Used by Hyperion Products Planning the Installation 17

16 Hardware Requirements The following tables list requirements for a representative Financial Management deployment (up to 150 total users, concurrent users, one Financial Management application) and do not contain sizing guidelines. For sizing guidelines, see the Hyperion Business Performance Management Deployment Guidelines. For larger deployments, we highly recommend that you contact Consulting Services to determine the number of servers for your environment. Keep these considerations in mind: User counts are approximations. Concurrent usage could be much higher or lower, based on the hardware recommended above, depending on user actions. Use case scenarios, think times between queries, and volume of report generation could adversely affect these general guidelines. Adequate load and performance testing should be integrated into your implementation testing phase to validate your production environment hardware sizing and assess the overall technical readiness before go-live. For single-user testing, all three tiers can be on the same computer. However, this arrangement does not accurately represent production environment performance. Client Tier The client tier consists of a Windows Desktop client and Rules Editor and a Web client. Table 1 Client Tier Hardware Requirements Requirements Basic User View User Administrator Minimum: Intel Pentium III, 800 MHz, 256 MB available RAM Recommended: Intel Pentium 4, 1 GHz or higher, 256 MB available RAM Disk space: 50 MB DCOM must be enabled on the client when running the Win32 client, or when running the Financial Reporting client against a Financial Management application. Minimum: Intel Pentium III, 800 MHz, 256 MB available RAM Recommended: Intel Pentium 4, 1.6 GHz or higher, 512 MB available RAM Disk space: 50 MB DCOM must be enabled on the client when running the Win32 client, or when running the Financial Reporting client against a Financial Management application. Middle Tier The following tables list the middle tier hardware requirements for two scenarios: installing Financial Management with Oracle s Hyperion Financial Reporting System 9 or with Hyperion Reports. 18 Planning the Installation

17 Table 2 Scenario A - Installing Financial Management with Reporting and Analysis Hyperion Product/Component Financial Management Web Server Shared Services Hardware Required Dual Pentium 4, 2 GHz and higher, 4 GB RAM, 32 GB Disk (After OS installation, 10 GB available) Dual Pentium 4, 2 GHz and higher, 4 GB RAM, 32 GB Disk (After OS installation, 10 GB available) (2) Financial Management Servers 1 Dual Pentium 4, 2 GHz and higher, 4 GB RAM, 32 GB Disk (After OS installation, 10 GB available) Financial Reporting Server (includes Financial Reporting Service, Financial Reporting Web Application, Financial Reporting Print Service) Reporting and Analysis Services Workspace Dual Pentium 4, 2 GHz and higher, 4 GB RAM, 32 GB Disk (After OS installation, 10 GB available) Dual Pentium 4, 2 GHz and higher, 4 GB RAM, 32 GB Disk (After OS installation, 10 GB available) 1 One of the application servers may be dedicated to an administration server for high data load and consolidation volume. Application servers may start as dual processors but should be quad capable. Table 3 Scenario B - Installing Financial Management with Hyperion Reports Hyperion Product/Component Financial Management Application Server Financial Management Application Server 1 Shared Services Financial Management Application Server 1 Reports Server (includes Reports Service, Reports Web Application, Reports Service) Hardware Required Dual Pentium 4, 2 GHz and higher, 4 GB RAM, 32 GB Disk (After OS installation, 10 GB available) Dual Pentium 4, 2 GHz and higher, 4 GB RAM, 32 GB Disk (After OS installation, 10 GB available) Dual Pentium 4, 2 GHz and higher, 4 GB RAM, 32 GB Disk (After OS installation, 10 GB available) Dual Pentium 4, 2 GHz and higher, 4 GB RAM, 32 GB Disk (After OS installation, 10 GB available) 1 One of the application servers may be dedicated to an administration server for high data load and consolidation volume. Software Requirements The following tables list the software requirements for Financial Management. Software Requirements 19

18 Subsequent maintenance releases and service packs for third-party platform software may be used where the vendor asserts backward compatibility. Please be aware, however, that although these assertions are made in good faith, certain incompatibilities may exist. In the event that an incompatibility is identified, Hyperion may experience a delay in reproducing and fixing resultant issues for the affected versions. Client Tier Requirements at the client level for a standard user are minimal. There are no other client requirements beyond what is required to run Microsoft Office. Table 4 Client Tier Software Requirements Component Operating system Web Browsers Requirements Any of these operating systems: Windows 2000 Professional, SP4 and later Windows 2000 Server, SP4 and later Windows 2003 Standard Edition SP1 Windows XP Pro SP1a and later Windows Vista One of these Web browsers: Microsoft Internet Explorer 6.0 or 7.0 Mozilla Firefox Pop-up windows must be allowed for your browser. Microsoft Excel Bandwidth To use Financial Management with Hyperion System 9 Smart View for Office, installation of one of these versions: Microsoft Excel 9 (Office 2000) Microsoft Excel 10 (Office XP) Microsoft Excel 11 (Office 2003) Dial-up access to Financial Management server of at least 56KB bandwidth. For certain operations, specifically spreadsheet functionality, a wider bandwidth may be necessary. Middle Tier The following table lists the application and Web server software requirements. For high performance, a very high speed LAN connection is required between the application/ Web server and the database server. In addition, good network availability between the application/web server and the database server is expected. The application server should be a trusted resource and should be behind the firewall and close to the database server. This arrangement improves performance and avoids additional network packet hops. The Web server can be the same computer as the application server or Reports server. 20 Planning the Installation

19 Table 5 Application Server Software Requirements Component Microsoft Data Access Component (MDAC) RDBMS driver Operating system Distributed Component Object Model (DCOM) Java application server for Shared Services Requirement or higher (2.8 required for Windows 2003) Same version as the RDBMS Server Windows 2000 Server SP4 and later Windows 2003 SP1 Must be enabled One of these application servers: Apache Jakarta Tomcat (included) BEA WebLogic Express and Premium and 9.2 IBM WebSphere and 6.1 Hyperion provides Apache Tomcat on the installation media for convenience if you want to use it for your deployment. Hyperion does not own or maintain the Apache Tomcat application server and is not responsible for problems that you may encounter with its functionality. Hyperion, however, fully supports the use of Apache Tomcat in its products. In deployments where customers require high availability or failover, Hyperion recommends that you deploy a commercially supported application server that supports these capabilities. On UNIX platforms, if you use the IBM WebSphere application server, ensure that you use the same account to install, deploy, and execute Hyperion products that you use to install WebSphere. Using the same account ensures that the Configuration Utility can successfully deploy Hyperion products to WebSphere. Portable document format (PDF) generator (for Reports - optional) One of these PDF generators: GNU Ghostscript AFPL Ghostscript 8.14 Adobe Acrobat 6.0 and higher Hyperthreading is not recommended for application servers running on Windows 2000 Server; however, Advanced Windows 2000 Server and Windows 2003 Enterprise Edition are supported. Table 6 Web Server Software Requirements Component Microsoft Internet Information Services (IIS) Requirement 5.0 on Windows on Windows in Isolation mode on Windows 2003 Software Requirements 21

20 Component Operating system Requirement Windows 2000 Server SP4 and later Windows 2003 SP1 Microsoft.NET Framework Version 2.0 Required to use Smart View for Office. Available through Windows Update or from Microsoft Web site at Database Tier Financial Management is used with a relational database management system (RDBMS) such as Oracle, Microsoft SQL Server, or IBM DB2. Licenses must be purchased from the RDBMS vendor. Financial Management supports these databases: Oracle 9i / 10g , 10g R , 11g Microsoft SQL Server 2000 with SP3a/ 2005 SP1 IBM DB2 8.1 with FP7a and later, or DB2 9.1 Supported Authentication Sources Financial Management supports these external authentication sources: LDAP: Sun One 5.2 Patch 4; Novell edirectory 8.8; IBM Directory Server 5.1; Domino 6.0 Microsoft NTLM Microsoft Active Directory 2000, 2003 IBM Tivoli Directory Server V5.2 Domino LDAP 6.0 Netegrity SiteMinder 5.5 SP2 Open LDAP Required Hyperion Products Financial Management requires these Hyperion products: Shared Services One of these Reporting solutions: Hyperion Reports (supported only on Windows 2000 and 2003) Reporting and Analysis (supported only on Windows 2000 and 2003) 22 Planning the Installation