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

(1)

O R A C L E ® H Y P E R I O N

FINANCIAL MANAGEMENT – SYSTEM 9

R E L E A S E 9 . 2 . 1

I N S T A L L A T I O N G U I D E

(2)

Financial Management, Release 9.2.1, Installation Guide

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 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

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 iii

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 . . . 9 Additional Products . . . 10 Financial Management Configurations . . . 11

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.

z The database tier contains the relational database and all Financial Management data and metadata. Supported databases include Oracle, Microsoft SQL Server, and IBM DB2. z 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.

z 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.

(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: z User provisioning

z External authentication definition z Metadata synchronization

z Data synchronization z 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.

(9)

Financial Management Configurations 11

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.

(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.

(11)

Financial Management Installation Sequence 13

C h a p t e r

2

Financial Management

Installation Sequence

This chapter provides the following information about installing, and configuring Financial Management:

z High-level task flow that identifies basic steps

z 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.

Shared Services installer Configuration Utility

Shared Services Installation Guide

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 External Authentication Configuration Console

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.

Configuration Utility Product installation guides

5 Create projects, add applications to projects, and provision users for applications.

Shared Services User Management Console

Hyperion System 9 Shared Services User Management Guide

(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 9.2.1”.

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 REFERENCE

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.

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 44.

(13)

Financial Management Installation Checklist 15

CONFIGURATION TASKS REFERENCE

Activate and configure Financial Management and register with Shared Services using the Hyperion Configuration Utility.

z Activate Financial Management.

z Specify the Shared Services Server location.

z Configure relational databases and repositories.

z Auto-deploy products to application servers (recommended). If preferred, select the Manual Deployment option to manually configure the deployment.

Note: 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. “Testing Installed Components” on page 69

ASSIGN ROLES FOR SHARED SERVICES USER MANAGEMENT AND PROVISION

USERS REFERENCE

A Shared Services administrator must perform these tasks:

z Assign the Project Manager role to users who are responsible for creating projects and assigning applications to projects.

z For each application, assign the Provisioning Manger role to users who are responsible for assigning roles and access control permissions to application users.

z 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.

Hyperion System 9 Shared Services User Management Guide

INSTALL ADDITIONAL PRODUCTS (OPTIONAL) REFERENCE

Install Smart View on the client tier (requires Microsoft Office 2003, 2002 XP or 2000 SP1).

“Installing Smart View” on page 45

Install the Data Integration Management adapter or Hyperion Application Link adapter.

Chapter 10, “Installing Additional Hyperion Products”

Install Financial Reporting. Hyperion Reporting and Analysis Installation Guide

(14)

(15)

Planning the Installation 17

C h a p t e r

3

Planning the Installation

This chapter lists Financial Management hardware and software requirements. In This Chapter Hardware Requirements. . . 18

Software Requirements . . . 19

Required Hyperion Products. . . 22

(16)

Hardware Requirements

The following tables list requirements for a representative Financial Management deployment (up to 150 total users, 30-40 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:

z User counts are approximations. Concurrent usage could be much higher or lower, based on the hardware recommended above, depending on user actions.

z Use case scenarios, think times between queries, and volume of report generation could adversely affect these general guidelines.

z 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.

Note: 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

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™_.

Requirements

Basic User View User

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.

Administrator 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.

(17)

Software Requirements 19 Table 2 Scenario A - Installing Financial Management with Reporting and Analysis

Note: 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

Note: 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. Hyperion Product/Component Hardware Required

Financial Management Web Server Dual Pentium 4, 2 GHz and higher, 4 GB RAM, 32 GB Disk (After OS installation, 10 GB available)

Shared Services Dual Pentium 4, 2 GHz and higher, 4 GB RAM, 32 GB Disk (After OS installation, 10 GB available)

(2) Financial Management Servers1 _{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)

Dual Pentium 4, 2 GHz and higher, 4 GB RAM, 32 GB Disk (After OS installation, 10 GB available)

Reporting and Analysis Services Workspace

Hyperion Product/Component Hardware Required

Financial Management Application Server

Financial Management Application Server1

Shared Services

Financial Management Application Server1

Reports Server (includes Reports Service, Reports Web Application, Reports Service)

(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

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.

Note: The Web server can be the same computer as the application server or Reports server.

Component Requirements

Operating system Any of these operating systems:

z Windows 2000 Professional, SP4 and later

z Windows 2000 Server, SP4 and later

z Windows 2003 Standard Edition SP1

z Windows XP Pro SP1a and later

z Windows Vista Web Browsers One of these Web browsers:

z Microsoft Internet Explorer 6.0 or 7.0

z Mozilla Firefox 2.0.0.3

Note: Pop-up windows must be allowed for your browser.

Microsoft Excel To use Financial Management with Hyperion System 9 Smart View for Office, installation of one of these versions:

z Microsoft Excel 9 (Office 2000)

z Microsoft Excel 10 (Office XP)

z Microsoft Excel 11 (Office 2003)

Bandwidth Dial-up access to Financial Management server of at least 56KB bandwidth. For certain operations, specifically spreadsheet functionality, a wider bandwidth may be necessary.

(19)

Software Requirements 21 Table 5 Application Server Software Requirements

Note: 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 Requirement

Microsoft Data Access Component (MDAC)

2.7.1 or higher

(2.8 required for Windows 2003) RDBMS driver Same version as the RDBMS Server Operating system Windows 2000 Server SP4 and later

Windows 2003 SP1 Distributed Component Object

Model (DCOM)

Must be enabled

Java application server for Shared Services

One of these application servers:

z Apache Jakarta Tomcat 5.0.28 (included)

z BEA WebLogic Express and Premium 8.1.4 and 9.2

z IBM WebSphere 5.1.1.7 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:

z GNU Ghostscript 7.0.6

z AFPL Ghostscript 8.14

z Adobe Acrobat 6.0 and higher

Component Requirement

Microsoft Internet Information Services (IIS)

5.0 on Windows 2000 6.0 on Windows 2003

(20)

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:

z Oracle 9i - 9.2.05/ 10g - 10.1.0.5, 10g R2 10.2.0.2, 11g z Microsoft SQL Server 2000 with SP3a/ 2005 SP1 z IBM DB2 8.1 with FP7a and later, or DB2 9.1

Supported Authentication Sources

Financial Management supports these external authentication sources:

z LDAP: Sun One 5.2 Patch 4; Novell eDirectory 8.8; IBM Directory Server 5.1; Domino 6.0 z Microsoft NTLM

z Microsoft Active Directory 2000, 2003 z IBM Tivoli Directory Server V5.2 z Domino LDAP 6.0

z Netegrity SiteMinder 5.5 SP2 z Open LDAP 2.3.37

Required Hyperion Products

Financial Management requires these Hyperion products: z Shared Services

One of these Reporting solutions:

z Hyperion Reports (supported only on Windows 2000 and 2003) z Reporting and Analysis (supported only on Windows 2000 and 2003)

Operating system 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

http://www.microsoft.com/net.

(21)

Port Numbers Used by Hyperion Products 23

Required Installation Documentation

The following documentation is required for installation and is available from the Oracle e-Delivery site.

z Hyperion Shared Services Installation Guide

z Hyperion System 9 Shared Services User Management Guide

z Hyperion Reporting and Analysis Installation Guide or Hyperion Reports Installation Guide

Port Numbers Used by Hyperion Products

During Hyperion product installation, the default port number for application servers is automatically populated and can be changed during the configuration process. For

instructions to modify default ports after installation, see Chapter 7, “Configuring and Setting Up Financial Management”.

Each application port number must be unique. After modifying the default port number, if your application does not launch, or if an error message is displayed similar to “port already in use” or “bind error,” there may be a port number conflict.

If you do not change the default port number, the software is configured with these values:

Hyperion Product Listen Port SSL Listen Port

Shutdown Port for Apache Tomcat

Shared Services 58080 58090 58005 Application Builder J2EE 21080 21090 21005 Application Builder.NET 22080 22082 22081 Essbase Administration Services 10080 10090 10005 Analytic High Availability Services 11080 11090 11005 Planning 8300 8300 8301 Hyperion Translation Manager 14080 14090 14005 Financial Reporting 8200 8201 Web Analysis 16000 16001 Hyperion Business Modeling 17080 17090 17005 Performance Scorecard 18080 18090 18005 Performance Scorecard Alerting 18081 18091 18006

(22)

Default Port Numbers for Remote Method Invocation (RMI)

Servers

Enterprise Metrics 8180 8280 8205

8105

Analytic Services Smart View Provider

13080 13090 13005

Workspace 19000 45001

Hyperion Component RMI Port

Hyperion Remote Authentication Module 58000

Financial Reporting 1099

Planning 11333

Strategic Finance 1493 and 1495

Hyperion Performance Suite Legacy 1494 - 1498

Hyperion Performance Suite GSM 1800

Hyperion Performance Suite Services 1801-1803

OpenLDAP 58081

Hyperion Product Listen Port SSL Listen Port

Shutdown Port for Apache Tomcat

(23)

Installing and Creating a Database 25

C h a p t e r

4

Installing and Creating a

Database

Financial Management uses the relational database as a storage container for all its data. Before you can create Financial Management applications, you must install, create, and configure a relational database to work with Financial Management, and create a database to work with Shared Services.

For database requirements, see “Database Tier” on page 22.

When you configure Financial Management, you specify the maximum number of relational database connections used by each application. See “Database Connection Pooling” on page 32.

When you create the database, record usernames and passwords that you assign so that you can refer to them when running the configuration utility.

In This Chapter Creating a Financial Management Database in Oracle. . . 26 Creating a Financial Management Database in Microsoft SQL Server . . . 27 Creating a Financial Management Database in IBM DB2. . . 27 Creating a Shared Services Database. . . 28 Creating Data Link (UDL) Files . . . 28 Encrypting UDL Files . . . 31 Database Connection Pooling . . . 32

(24)

Creating a Financial Management Database in Oracle

The Oracle Universal Installer program guides you through the installation and configuration of your Oracle database server. For additional information, see the Oracle Administrator’s Guide. To use Financial Management with Oracle Server, you must purchase licenses from Oracle.

Before you can use Financial Management with Oracle, the database administrator must create a tablespace for Financial Management and set up users. Note these guidelines:

z Your database administrator should create a tablespace and an Oracle user. The user administers the Financial Management repository. Ensure that the user is granted the privileges to create, update, and delete tables.

Note: Using a pre-existing user and tablespace is not recommended.

z The minimum tablespace requirement is one gigabyte (recommended). The tablespace requirement depends on the amount of data and the application size.

z Minimum Oracle user rights required for the tablespace to which Financial Management creates tables are as follows:

ROLES: CONNECT and RESOURCE

SYSTEM PRIVILEGES: CREATE SESSION and CREATE PROCEDURE (generally part of the RESOURCE role)

SYSTEM PRIVILEGES: CREATE TABLE and CREATE SEQUENCE QUOTA - Unlimited quota for temporary tablespace

Note: You can grant UNLIMITED TABLESPACE for SYSTEM PRIVILEGES instead of using the QUOTA tab.

z The Oracle client must be installed on the Financial Management application server. When you configure the server, you need this information:

The name or IP address of the computer on which Oracle is installed The TCP port on which Oracle is listening (if not the default port 1521) The Oracle service name or SID where the tablespace resides

The name of the Oracle user with rights to connect to and create tables in the Oracle instance

The password of the Oracle user with rights to connect to and create tables in the Oracle instance

(25)

Creating a Financial Management Database in IBM DB2 27

Creating a Financial Management Database in Microsoft SQL

Server

Before you can use Financial Management with Microsoft SQL Server, the database

administrator must create a database and user for Financial Management. Ensure that the user is granted the privileges to create, update, and delete tables.

For instructions on installing Microsoft SQL Server, see Microsoft’s SQL Server installation instructions. To use Financial Management with Microsoft SQL Server, you must purchase licenses from Microsoft.

For information on creating the database, see the Microsoft SQL Server Creating and Maintaining Databases Guide.

Note: When you set the Security properties for the database, make sure that you select this Authentication option: “SQL Server and Windows”.

When you configure the application server, you need this database information: z The name or IP address of the computer on which SQL Server is installed z The TCP port on which SQL Server is listening (if not the default port 1433) z The name of the database created for Financial Management

z The name and password of the SQL Server user with db_owner rights to the database

Creating a Financial Management Database in IBM DB2

For information on installing and configuring the database, see the IBM DB2 Administration Guide: Planning and IBM DB2 Administration Guide: Implementation.

Note: When you install DB2, clear the OLAP Starter Kit option, because Hyperion Essbase – System 9 is not part of DB2 installation and should be installed separately.

Before you can use Financial Management with IBM DB2, the database administrator must create a database that contains the Financial Management tables and set up users. Use the IBM DB2 Client Configuration Assistant to set up a database alias that enables Financial

Management to connect to the database. Select these options:

z Register this Database as ODBC z As a System Data Source

Note these guidelines:

z The Financial Management database must be created using UTF-8 (Unicode Transformation Format)

(26)

z Your database administrator should create a database and a DB2 user for administering the Financial Management repository. Ensure that the user is granted the privileges to create, update, and delete tables.

z The minimum database requirement is one gigabyte (recommended). The tablespace requirement depends on the amount of data and the application size.

z Minimum DB2 user rights required for the database in which Financial Management creates tables are as follows:

Connect database Create tables

z You must install the IBM DB2 client on the Financial Management application server. When you configure your application server, you need this information:

The name or IP address of the computer on which DB2 is installed

The TCP port on which the DB2 JDBC Applet Server is listening (if not the default port of 6789)

The name of the database on which the Financial Management DB2 user resides The name and password of the DB2 user with rights to connect to and create tables in

the Financial Management database instance on DB2

Creating a Shared Services Database

In addition to the Financial Management database, you must create a database to use with Shared Services. See the procedures in this chapter for creating a database in Oracle, SQL Server, or DB2.

Creating Data Link (UDL) Files

A universal data link (.udl) file provides a connection between a database server and an application server.

Ê

To create a data link (.udl) file:

1 From Windows Explorer, select the folder in which to store the file.

Note: You should store the file in a directory other than the Financial Management installation directory, so that you can retain the file if you uninstall Financial Management.

2 Select File > New > Text Document.

A file named New Text Document.txt is displayed.

3 Rename the file, removing all spaces, and changing its file extension to .udl, for example, hfm.udl.

(27)

Creating Data Link (UDL) Files 29 For information on configuring data links, see these topics:

z “Configuring the Data Link for Oracle” on page 29

z “Configuring the Data Link for Microsoft SQL Server” on page 30 z “Configuring the Data Link for IBM DB2” on page 30

Configuring the Data Link for Oracle

The data link specifies the database server name and other database-related information, such as the username and password of a user with full access rights to the database server.

Financial Management requires the Oracle OLE DB Provider. If you use Oracle 8.1.7, the Oracle Provider version is 8.1.7.3.0. You can download and obtain information about the Oracle DB Provider from the Oracle Web site.

Ê

To download Oracle OLE DB Provider:

1 Using a Web browser, go to www.oracle.com.

2 Click the Downloads link.

3 From the Technologies, Utilities, and Drivers section, select Oracle Provider for OLE DB.

4 Select the file to download, and follow the screen prompts.

Ê

To configure the data link for Oracle:

1 From Windows Explorer, double-click the UDL file that you created. The Data Link Properties dialog box is displayed.

2 On the Provider tab, from the OLE DB Providers list, select Oracle Provider for OLE DB.

3 Click Next.

4 On the Connection tab:

a. Enter the server name <Oracle Global Database Name>. b. Enter a username and password.

Note: Ensure that the user is granted privileges to create, update, and delete tables. See “Creating a Financial Management Database in Oracle” on page 26.

5 Select Allow saving password.

6 Select the database to which you want to connect.

7 Click Test Connection.

8 On the Test Connection Succeeded box, click OK.

(28)

Configuring the Data Link for Microsoft SQL Server

Ê

To configure the data link for Microsoft SQL Server:

1 From Windows Explorer, double-click the UDL file that you created. The Data Link Properties dialog box is displayed.

2 On the Provider tab, from the OLE DB Providers list, select Microsoft OLE DB Provider for SQL Server.

3 Click Next.

a. Enter the server name, which is the computer hosting the relational database. b. Select Use a Specific User Name and Password.

c. Enter a username and password for a user with full access rights to the database.

Note: You can use the default username sa. If you use the default name, leave the password text box blank, and select Blank Password.

If you do not want to use the default username, you must enter the name of a user other than the default user who has full access rights. Ensure that this user is granted privileges to create, update, and delete tables. See

“Creating a Financial Management Database in Microsoft SQL Server” on page 27.

d. Select Allow Saving Password.

5 Select the database to which you want to connect.

6 Click Test Connection.

7 On the Test Connection Succeeded box, click OK.

8 Click OK to save the connection, and close the dialog box.

9 Right-click the UDL file, and select Open to set the selected UDL file as the system data link file.

Note: If you use Microsoft SQL Server as your database server on Windows and have problems connecting to or creating applications or if you fail the connection test after creating a data link (UDL), see “Troubleshooting Applications” on page 106.

Configuring the Data Link for IBM DB2

Ê

To configure the data link for IBM DB2:

(29)

Encrypting UDL Files 31 The Data Link Properties dialog box is displayed.

2 On the Provider tab, from the OLE DB Providers list, select IBM OLE DB Provider for DB2 Servers.

3 Click Next.

a. Select Use data source name option.

This option selects the data source name that you established during the IBM DB2 installation. Note: If the data source name is not displayed in the drop-down list, go to the Client Configuration Assistant, Database

Properties dialog box, and select As a system data source.

b. Enter a username and password.

Note: Ensure that the user is granted privileges to create, update, and delete tables. See “Creating a Financial Management Database in IBM DB2” on page 27.

5 Select Allow saving password.

6 Click Test Connection.

7 On the Test Connection Succeeded box, click OK.

8 Click OK to save the connection and close the dialog box.

9 Right-click the UDL file and select Open to set the UDL file as the system data link file.

Encrypting UDL Files

Financial Management provides a utility to encrypt the UDL file used by the application server to communicate with the database. Based on the UDL file extension, Financial Management detects whether the file is encrypted. If the file extension is.udl, the system assumes that the file is not encrypted. If the file extension is .hfmudl, the system assumes that the file is encrypted.

To encrypt the UDL file, you use the EncryptHFMUDL utility located in the FinancialManagement/Server directory.

Ê

To encrypt the UDL file:

1 Do one of these tasks to access the MSDOS command prompt:

z Select Start > Programs > Accessories > Command Prompt. z Select Start > Run, and type cmd.

2 Enter encrypthfmudl hfm.udl hfm.hfmudl

where hfm.udl is the location of your original UDL file, and hfm.hfmudl is the location of the encrypted UDL file.

(30)

Note: The encrypted UDL file extension must be .hfmudl. After encrypting the file, you can delete the original unencrypted file.

Ê

To decrypt the UDL file:

1 Do one of these tasks to access the MSDOS command prompt:

z Select Start > Programs > Accessories > Command Prompt. z Select Start > Run, and type cmd.

2 Enter encrypthfmudl hfm.hfmudl hfm.udl /u

where hfm.hfmudl is the location of the encrypted UDL file and hfm.udl is the location of the decrypted file.

Database Connection Pooling

Financial Management utilizes connection pooling in communicating with the database. Connection pooling enables more efficient database utilization and does not require each user to be set up in the relational repository.

The number of connections that you specify in the configuration utility is the maximum number of pooled connections consumed by an application. The pool starts with eight connections. If after a certain number of attempts, the pool is unable to service a request for an additional connection, it adds eight more connections. The system continues adding blocks of eight connections until it reaches the maximum number of connections defined in the utility. If the system needs an additional connection beyond this limit, a temporary connection is created to service the request, which is closed after the task is complete.

The system also creates additional connection pools that are reserved for system use and are not used for user activity. The system-use pools are divided into these connection types: z A pool of nine connections per application is reserved for system activity.

z A pool of eight connections per application is reserved for error handling.

z A pool of eight connections per application server is created for user logon activities. The user logon pool can grow by four to the system-defined maximum value of 16 connections. Connections required above the maximum are temporary.

In general, there are 25 connections dedicated to system-level activities: eight connections reserved for each application server, and 17 connections reserved for each application. Connection use is dependent on the activity type. Users with Read access, which are the majority of users in an application, generally use one or no connections. Users with Write access can consume more connections, as they write to the database. The number of

connections consumed by a user with Write access, for example, a consolidator, depends on the application server hardware and quantity of data being written. In general, users with Write access may use five to ten connections.

Financial Management opens the defined number of connections when an application is first opened. The connections are then available for subsequent users of the system. If a user process requests a connection and all connections are in use, the system polls the connection pool for a

(31)

Database Connection Pooling 33 short time, waiting for a connection to become available. If no connection is available, the system creates eight connections and adds them to the pool. The connection pool is limited to the total that you define in the configuration utility.

Connections are application specific. The default pool is created only after an application is opened. However, connections are not released on an application basis. They are released on an application server basis; thus all connections are not released until the application server has no Financial Management users accessing any application.

Financial Management also supports Extended Analytics, which enables extracting data to a relational database for use with other systems, such as Essbase. The extract process has a dedicated connection pool that is created when a star schema is created. The default pool is 16 temporary connections that are destroyed when the processing is complete.

Example 1

Three applications on one application server, default maximum connection pooling is used (40 connections)

z Application A is logged on - 8 connections (plus system) z Application B is logged on - 8 connections (plus system) z Application C is logged on - 8 connections (plus system) z System connections: 59 (8 plus 17 per application) z Total connections: 83

Note: Total connections could grow by 96 if all application connection pools expand to the system maximum as defined in the configuration utility (default is 40).

z Application B is logged off (no users) z Total connections: 83

z All users log off all applications z Total connections: 0

Example 2

One application on two application servers, default maximum connection pooling is used (40 connections)

z Application A is logged on (server 1) - 8 connections (plus system) z Application A is logged on (server 2) - 8 connections (plus system) z System connections: 50 (8 plus 17 per application per application server) z Total connections: 66

z Application A (server 2) is logged off (no users) z Total connections: 33

(32)

z All users log off all applications z Total connections: 0

At times, connectivity between the application server and the database server might be lost due to network issues, for example. If the system detects that a connection is no longer valid, it attempts to recreate the connection.

Deleting applications also consumes the default number of pooled connections. Before deleting an application, Financial Management opens the application to verify security access, consuming the default number of connections. After security is validated, the system deletes the application.

(33)

Installing Financial Management Server Components 35

C h a p t e r

5

Installing Financial Management

Server Components

Before installing Financial Management, you must complete these steps: z Install and configure Shared Services.

z Configure external authentication through Shared Services.

For instructions, see the Hyperion Shared Services Installation Guide. To verify startup of these components, see “Verifying Startup Dependencies” on page 67.

If you use a separate application server and client workstation, you must install Financial Management on each computer.

If you install Financial Management on one computer, you can install the Server and Client components simultaneously with the Custom installation option.

For server requirements, see “Middle Tier” on page 20.

In This Chapter Installing Microsoft Internet Information Services . . . 36 About Hyperion Home . . . 36 Installation Files and Directories . . . 37 Installing Financial Management . . . 38 Installing Only the Analytic Data Model (ADM) Driver . . . 40 Installing the HFM Software Development ToolKit . . . 41 Performing Silent Installations of Financial Management . . . 41

(34)

Installing Microsoft Internet Information Services

To use Financial Management on the Web, you must install Microsoft Internet Information Services (IIS) on the Web Server. If you use a separate, dedicated computer to run the Financial Management Web server components, you must install the IIS Web server on that computer. z For Windows 2000 Server, IIS 5.0 is provided.

z For Windows 2003, IIS 6.0 is provided.

Note: For Windows 2003 and IIS 6.0, make sure that you enable the Active Server Pages (ASP) and ASP.NET components, which are not enabled by default.

z If you run IIS 5.0 Isolation Mode in IIS 6.0, you must set additional properties in Internet Services Manager. You set the properties manually after installing Financial Management and running the configuration utility to create the Web directories. See “Running IIS 5.0 Isolation Mode in IIS 6.0 on Windows 2003” on page 66.

Verifying the IIS Installation

This procedure describes how to verify the IIS installation.

Ê

To verify the IIS installation:

1 Select Start > Programs > Administrative Tools > Component Services, and double-click Services, or from Windows 2003, select Start > Settings > Control Panel > Administrative Tools > Services.

2 Check to see that the IIS services are running:

a. Select IIS Admin Service and if it is not started, click Start.

b. Select World Wide Web Publishing Service, and if it is not started, click Start.

c. If you did not see the services for IIS, verify that IIS is installed, and if it is not, install it.

About Hyperion Home

When multiple Hyperion products are installed on one computer, common internal and third-party product components are installed to a central location called Hyperion Home. On Windows platforms, the Hyperion Home location is defined in the system environment variable called HYPERION_HOME. On UNIX, the Hyperion Home value is stored in .hyperion.<hostname> in the /home directory.

Hyperion Home Location

The Financial Management installer prompts you to define the Hyperion Home location. The default location is C:\Hyperion for Windows and $HOME/Hyperion for UNIX. If the location is defined for another Hyperion product, the installation uses that location and it

(35)

Installation Files and Directories 37 cannot be changed through the installer. If this is the first Hyperion installation on the

computer, and you have not specified the Hyperion Home location, you can specify it during installation.

Note: Ensure that the Hyperion Home directory name does not contain spaces. You can enter only English alphanumeric characters and these special characters: dash (-), underscore ( _ ), plus sign (+), backslash (\), forward slash (/), dot (.), colon (:). The colon character (:) is supported only for Windows platforms to specify the drive (for example, c:\).

Changing the Hyperion Home Location

After Hyperion Home is defined through a product installation, if you want to change its location, you must run a migration utility. The migration utility is provided with the Financial Management installation and moves the files installed in Hyperion Home to the location that you specify.

Ê

To change the Hyperion Home location:

1 Select Start > Programs > Hyperion System 9 Shared Services > Hyperion Home Migration Utility.

2 Step through the utility screens and enter the new Hyperion Home location or click Browse to navigate to the new location.

The migration utility copies the Hyperion Home directory to the new location and replaces the value of the current HYPERION_HOME environment variable.

Installation Files and Directories

The Financial Management installation program installs files needed to run Financial Management and common components used by multiple Hyperion products.

Note: The installation program contains these three files: media.inf, setup.exe, and suite.jar, which must be in the same directory for the installation program to run.

What Happens During Installation

By default, the Financial Management installation program performs these operations: z Creates installation directories

z Copies Financial Management software files to the directory specified during the installation

z Copies common components to the HYPERION_HOME directory

(36)

Directories and Files Installed

The setup program installs files in two locations:

z Financial Management software files are installed in the directory specified during installation (for example, <drive>:\Hyperion\FinancialManagement). z Additional internal components and third-party products are installed in

Drive:\HYPERION_HOME\common.

Installing Financial Management

Use this procedure to install Financial Management Application and Web Server components.

Ê

To install Financial Management on the application server:

1 Navigate to the directory where you downloaded the installation program, select File > Run or Start > Run and enter Drive:\folder\Setup.exe, where Drive and folder are the installation program location.

2 Select the installation process language, and click OK.

3 Review the Welcome box and click Next.

4 From the list of countries, select the location from which you are installing, and click Next.

5 Read the license agreement, select I AGREE and click Next.

6 Click Next to accept the default installation directory or click Browse to select another directory, and click Next.

The default directory is C:\Hyperion\FinancialManagement.

Ensure that the directory name does not contain spaces. You can enter only English

alphanumeric characters and these special characters: dash (-), underscore ( _ ), plus sign (+), backslash (\), forward slash (/), dot (.), colon (:). The colon character (:) is supported only for Windows platforms to specify the drive (for example, c:\).

7 Click Next to accept the default installation path for HYPERION_HOME, or click Browse and navigate to another directory, and click Next.

The default directory is C:\Hyperion.

Ensure that the directory name does not contain spaces. You can enter only English

alphanumeric characters and these special characters: dash (-), underscore ( _ ), plus sign (+), backslash (\), forward slash (/), dot (.), colon (:). The colon character (:) is supported only for Windows platforms to specify the drive (for example, c:\).

Note: If the installation program detects a HYPERION_HOME directory, Directory Name and Browse are not selectable.

If a Java Virtual Machine (JVM) version is detected in the Hyperion Home location, a warning message is displayed. Shut down products using JVM and click OK to continue.

(37)

Installing Financial Management 39

9 Select the components to install, and clear components that you do not want to install. All components are selected by default.

z To install all Client, Application Server, and Web components, select Hyperion System 9 Financial Management.

OR

Select to install these components: z Client

Install all components for a full client installation. z Application Server

Install all files required for the application server.

z Web

Install all components to access Financial Management through the Internet. Web Server

Install Web Server components on this computer. You can, if you want, install the Web Server components later on another computer.

Smart View for Office Services

Install the Smart View for Office provider on the Web server. For information on installing Smart View on the client tier, see “Installing Smart View” on page 45. For information on using Smart View, see the Smart View for Office User Guide or Online Help installed with Smart View.

Note: If you use Smart View for Office, you must have Microsoft .NET Framework installed. You can obtain .NET Framework from the Microsoft Web site at http://www.microsoft.com/net.

z Consultant Utilities

Install additional utilities for Financial Management.

10 Review the component summary information, and click Next to continue the installation, or Back to change settings.

Note: If you do not have Microsoft Data Access Component (MDAC) installed on the application server, the system installs it automatically at this point. The MDAC installation process can be time-consuming, and requires that you reboot your computer.

11 If system files were detected that needed to be updated during installation, a status message is displayed. Click Next to continue.

For a list of updated files, check the install log, installLog.txt, at the root of the directory in

which you installed Financial Management. If Windows File Protection is enabled, download the Windows update to obtain the latest version of the files.

12 When you receive the message that the installation is complete, click Next.

13 If prompted, select whether to restart your computer at this time, and click Finish.

(38)

It is recommended that you reboot your computer before starting configuration.

Installing Only Web Server Components

If you run Web server components on the application server, you can install the components during a Custom installation.

If you need to install the Financial Management Web server components on an additional application server or on the server that is running Microsoft Internet Information Server (IIS), during the installation process, you can install only the Web Server components.

Ê

To install only the Financial Management Web server components:

1 Start the Financial Management installation.

See “Installing Financial Management” on page 38.

2 From Setup Type, select Custom, and click Next.

3 From Component Selection, select Web Server.

Note: Clear components that you do not want to install. If you clear a component that is already installed on the computer, the component is removed from the computer.

4 Select a destination folder for the files, and click Next.

5 Review the current settings, and click Next to continue the installation, or Back to change settings.

6 If prompted, select whether to restart your computer at this time, and click Finish.

Installing Only the Analytic Data Model (ADM) Driver

If you use Financial Management with Financial Reporting, Web Analysis, or Application Builder J2EE, you must install the Analytic Data Model (ADM) driver components. You can install only the ADM components using the following procedure. This process installs the files needed for ADM integration with Financial Management. By default, the ADM driver, HsvADMDriver.dll, is installed in Drive:\Hyperion\FinancialManagement\Client.

Ê

To install only the ADM components:

1 Start the Financial Management installation.

See “Installing Financial Management” on page 38.

2 From Setup Type, select Custom, and click Next.

3 From Component Selection, select ADM Client.

Note: Clear components that you do not want to install. If you clear a component that is already installed on the computer, the component is removed from the computer.

(39)

Performing Silent Installations of Financial Management 41

5 Review the component settings, and click Next to continue the installation or Back to change settings.

6 If prompted, select whether to restart your computer at this time, and click Finish.

Installing the HFM Software Development ToolKit

The HFM Software Development ToolKit is a guide for programmers who are responsible for using the Financial Management Web object model to customize Financial Management.

Ê

To install the HFM Software Development ToolKit:

1 From the Additional Documentation folder, or the directory in which you downloaded the ToolKit, double-click HFM_SDK.exe

2 Review the Welcome box and click Next.

4 Click Finish.

5 After you install the Toolkit, navigate to the installation directory, and open Readme.html.

Performing Silent Installations of Financial Management

If you want to install Financial Management on multiple computers and use the same options for each installation, you can use a silent mode installation process. Silent installations automate the installation process so that you can install Financial Management without manually specifying settings during each installation.

To run a silent installation, you record your installation settings in a response file for the first computer and then run the response file to apply the settings for other computers.

Creating the Response File

The response file is a recording of the Financial Management installation program and contains the system-specific information that you are prompted to enter during installation, including the bean ID keys and their values.

Ê

To create the response file:

1 Ensure that JDK version 1.3.1 or later is installed on your computer.

2 Create a blank text file to use as the response file.

3 Navigate to the directory that contains the product installer (setup.exe).

4 Open the command prompt and enter: