hfm install

110
ORACLE® HYPERION FINANCIAL MANAGEMENT – SYSTEM 9 RELEASE 9.2.1 INSTALLATION GUIDE P/N: DF90092100

Upload: raghuram-pavuluri

Post on 15-Nov-2014

278 views

Category:

Education


3 download

DESCRIPTION

HFM Install

TRANSCRIPT

Page 1: Hfm install

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

P / N : D F 9 0 0 9 2 1 0 0

Page 2: Hfm install

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

Page 3: Hfm install

Contents iii

Contents

CHAPTER 1 Installation Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Financial Management Installation Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Additional Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Financial Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Data Integration Management Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Hyperion Application Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Smart View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Financial Management Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

CHAPTER 2 Financial Management Installation Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Financial Management Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

CHAPTER 3 Planning the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Client Tier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Middle Tier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Client Tier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Middle Tier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Database Tier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Supported Authentication Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Required Hyperion Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Required Installation Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Port Numbers Used by Hyperion Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Default Port Numbers for Remote Method Invocation (RMI) Servers . . . . . . . . . . . . . . . 24

CHAPTER 4 Installing and Creating a Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

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

Page 4: Hfm install

iv Contents

Configuring the Data Link for Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Configuring the Data Link for Microsoft SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Configuring the Data Link for IBM DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Encrypting UDL Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Database Connection Pooling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

CHAPTER 5 Installing Financial Management Server Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Installing Microsoft Internet Information Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Verifying the IIS Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

About Hyperion Home . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Hyperion Home Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Changing the Hyperion Home Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Installation Files and Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

What Happens During Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Directories and Files Installed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Installing Financial Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Installing Only Web Server Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Installing Only the Analytic Data Model (ADM) Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Installing the HFM Software Development ToolKit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Performing Silent Installations of Financial Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Creating the Response File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Running the Silent Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

CHAPTER 6 Installing the Client Tier Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Installing Financial Management on the Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Installing Smart View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Verifying Communications Between the Application Server and Client . . . . . . . . . . . . . . . . . 46

CHAPTER 7 Configuring and Setting Up Financial Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Hyperion Configuration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Task Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Configuring Product Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Launching the Configuration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Registering Products with Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Deregistering Products with Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Reconfiguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Configuration Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Completing Financial Management Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Using the Financial Management Configuration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Configuring Application Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Page 5: Hfm install

Contents v

Configuring DCOM Security Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Specifying the Application Creator and Administrator Groups . . . . . . . . . . . . . . . . . . . . . 55

Setting Server Working Folder and Database Information . . . . . . . . . . . . . . . . . . . . . . . . . 55

Enabling Multiple Server Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Specifying a Data Source for Extended Analytics (Optional) . . . . . . . . . . . . . . . . . . . . . . . 57

Configuring Application Server Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Enabling Remote Activation (DCOM Limits for 2003 and XP) . . . . . . . . . . . . . . . . . . . . . 59

Configuring Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Registering Application Server Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Enabling DCOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Configuring Web Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Specifying Web Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Specifying the File Transfer Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Setting ASP Properties (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Enabling SiteMinder Web Security Agent Support (Optional) . . . . . . . . . . . . . . . . . . . . . . 62

Specifying Support for Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Specifying URLs for Other Hyperion Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Setting Web Server DCOM User Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Configuring Related Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Configuring Smart View for Office Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Setting Up the Web Server for Web Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Setting Up Proxy Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Running IIS 5.0 Isolation Mode in IIS 6.0 on Windows 2003 . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Verifying Startup Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Starting Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Verifying Successful Startup of Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Testing Installed Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Creating a Shared Services Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Using Sample Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Creating Test Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Opening Test Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Loading Sample Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Viewing Sample Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

CHAPTER 8 Uninstalling Financial Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Uninstalling Prior Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Uninstalling Shared Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Uninstalling Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

CHAPTER 9 Upgrading to Financial Management 9.2.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Upgrading Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Backing Up Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Page 6: Hfm install

vi Contents

Backing Up Database Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Verifying MDAC Version on the Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Uninstalling Prior Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Uninstalling Shared Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Uninstalling Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Installing Financial Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Installing Financial Management Server Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Installing Financial Management on the Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Upgrading Applications from Prior Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Using the Schema Upgrade Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

CHAPTER 10 Installing Additional Hyperion Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Installing Financial Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Accessing Financial Reporting Web Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Installing the Hyperion Application Link Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Updating Financial Management Adapter 3.0.80 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Updating Financial Management Adapter 9.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Installing Data Integration Management Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Installing Adapters in Silent Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Installing Adapters in Console Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Configuring Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Uninstalling Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

APPENDIX A Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Troubleshooting Application Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Establishing the SQL Server Connection Using TCP/IP . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Verifying Data Link Connection Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Verifying Microsoft SQL Server Authentication Settings . . . . . . . . . . . . . . . . . . . . . . . . . 106

Troubleshooting Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Troubleshooting Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Page 7: Hfm install

Installation Overview 9

C h a p t e r

1Installation 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 IntroductionFinancial 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.

Page 8: Hfm install

10 Installation Overview

Additional ProductsBeginning 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 ServicesFeatures 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 ReportingOracle’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 AdaptersOracle’s Hyperion Data Integration Management adapters enable you to retrieve and write data for Financial Management and transfer application data to an external target.

Page 9: Hfm install

Financial Management Configurations 11

Hyperion Application LinkOracle’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 ViewOracle’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 ConfigurationsFinancial 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.

Page 10: Hfm install

12 Installation Overview

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.

Page 11: Hfm install

Financial Management Installation Sequence 13

C h a p t e r

2Financial 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.

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

Page 12: Hfm install

14 Financial Management Installation Sequence

Financial Management Installation ChecklistThis 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.

Page 13: Hfm install

Financial Management Installation Checklist 15

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.

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:

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.

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

Page 14: Hfm install

16 Financial Management Installation Sequence

Page 15: Hfm install

Planning the Installation 17

C h a p t e r

3Planning the Installation

This chapter lists Financial Management hardware and software requirements.

In This Chapter Hardware Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Required Hyperion Products. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Port Numbers Used by Hyperion Products. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Page 16: Hfm install

18 Planning the Installation

Hardware RequirementsThe 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:

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.

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 TierThe client tier consists of a Windows Desktop client and Rules Editor and a Web client.

Table 1 Client Tier Hardware Requirements

Middle TierThe 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.

Page 17: Hfm install

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 RequirementsThe 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

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

Hyperion Product/Component Hardware Required

Financial Management Application Server

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

Financial Management Application Server1

Shared Services

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

Financial Management Application Server1

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

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

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

Page 18: Hfm install

20 Planning the Installation

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:

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

Web Browsers One of these Web browsers:

Microsoft Internet Explorer 6.0 or 7.0

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:

Microsoft Excel 9 (Office 2000)

Microsoft Excel 10 (Office XP)

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.

Page 19: Hfm install

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:

Apache Jakarta Tomcat 5.0.28 (included)

BEA WebLogic Express and Premium 8.1.4 and 9.2

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:

GNU Ghostscript 7.0.6

AFPL Ghostscript 8.14

Adobe Acrobat 6.0 and higher

Component Requirement

Microsoft Internet Information Services (IIS)

5.0 on Windows 2000

6.0 on Windows 2003

5.0 in Isolation mode on Windows 2003

Page 20: Hfm install

22 Planning the Installation

Database TierFinancial 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 - 9.2.05/ 10g - 10.1.0.5, 10g R2 10.2.0.2, 11g

Microsoft SQL Server 2000 with SP3a/ 2005 SP1

IBM DB2 8.1 with FP7a and later, or DB2 9.1

Supported Authentication SourcesFinancial 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 2.3.37

Required Hyperion ProductsFinancial 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)

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.

Component Requirement

Page 21: Hfm install

Port Numbers Used by Hyperion Products 23

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

Hyperion Shared Services Installation Guide

Hyperion System 9 Shared Services User Management Guide

Hyperion Reporting and Analysis Installation Guide or Hyperion Reports Installation Guide

Port Numbers Used by Hyperion ProductsDuring 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 PortShutdown 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

Page 22: Hfm install

24 Planning the Installation

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 PortShutdown Port for Apache Tomcat

Page 23: Hfm install

Installing and Creating a Database 25

C h a p t e r

4Installing 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

Page 24: Hfm install

26 Installing and Creating a Database

Creating a Financial Management Database in OracleThe 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:

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.

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

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.

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

Page 25: Hfm install

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:

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

The TCP port on which SQL Server is listening (if not the default port 1433)

The name of the database created for Financial Management

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

Creating a Financial Management Database in IBM DB2For 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:

Register this Database as ODBC

As a System Data Source

Note these guidelines:

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

Page 26: Hfm install

28 Installing and Creating a Database

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.

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

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

Connect database

Create tables

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

4 When asked to confirm changing the file extension, click Yes.

Page 27: Hfm install

Creating Data Link (UDL) Files 29

For information on configuring data links, see these topics:

“Configuring the Data Link for Oracle” on page 29

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

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

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

Page 28: Hfm install

30 Installing and Creating a Database

Configuring the Data Link for Microsoft SQL Server 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.

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.

4 On the Connection tab:

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

To configure the data link for IBM DB2:

1 From Windows Explorer, double-click the UDL file that you created.

Page 29: Hfm install

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.

4 On the Connection tab:

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

Select Start > Programs > Accessories > Command Prompt.

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.

Page 30: Hfm install

32 Installing and Creating a Database

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:

Select Start > Programs > Accessories > Command Prompt.

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

A pool of nine connections per application is reserved for system activity.

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

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

Page 31: Hfm install

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)

Application A is logged on - 8 connections (plus system)

Application B is logged on - 8 connections (plus system)

Application C is logged on - 8 connections (plus system)

System connections: 59 (8 plus 17 per application)

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

Application B is logged off (no users)

Total connections: 83

All users log off all applications

Total connections: 0

Example 2

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

Application A is logged on (server 1) - 8 connections (plus system)

Application A is logged on (server 2) - 8 connections (plus system)

System connections: 50 (8 plus 17 per application per application server)

Total connections: 66

Application A (server 2) is logged off (no users)

Total connections: 33

Page 32: Hfm install

34 Installing and Creating a Database

All users log off all applications

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.

Page 33: Hfm install

Installing Financial Management Server Components 35

C h a p t e r

5Installing Financial Management

Server Components

Before installing Financial Management, you must complete these steps:

Install and configure Shared Services.

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

Page 34: Hfm install

36 Installing Financial Management Server Components

Installing Microsoft Internet Information ServicesTo 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.

For Windows 2000 Server, IIS 5.0 is provided.

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.

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 InstallationThis 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 HomeWhen 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 LocationThe 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

Page 35: Hfm install

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 LocationAfter 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 InstallationBy default, the Financial Management installation program performs these operations:

Creates installation directories

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

Copies common components to the HYPERION_HOME directory

Installs the Java Runtime Environment (JRE) version to \HYPERION_HOME\common\JRE.

Page 36: Hfm install

38 Installing Financial Management Server Components

Directories and Files InstalledThe setup program installs files in two locations:

Financial Management software files are installed in the directory specified during installation (for example, <drive>:\Hyperion\FinancialManagement).

Additional internal components and third-party products are installed in Drive:\HYPERION_HOME\common.

Installing Financial ManagementUse 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.

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

Page 37: Hfm install

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.

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

OR

Select to install these components:

Client Install all components for a full client installation.

Application Server Install all files required for the application server.

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.

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.

14 Run the configuration utility. See Chapter 7, “Configuring and Setting Up Financial Management”.

Page 38: Hfm install

40 Installing Financial Management Server Components

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

Installing Only Web Server ComponentsIf 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) DriverIf 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.

Page 39: Hfm install

Performing Silent Installations of Financial Management 41

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

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

3 Select a destination folder for the files, 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 ManagementIf 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 FileThe 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:

setup.exe -options-record <responsefilename>

Page 40: Hfm install

42 Installing Financial Management Server Components

The Financial Management installation program is launched.

5 As you step through the installation, enter the values to use as the defaults in the response file.

The values are recorded in the response file. You can modify the response file if you want to change the options.

6 After the installation, open the response file in a text editor. Confirm that the bean ID keys and values are correct, or modify as required. Save the file.

Running the Silent InstallationYou can silently install Financial Management by running the response file.

To run the silent installation:

1 Copy the response file and the Financial Management installation files to the location of the computer on which you are installing.

2 Open the command prompt and enter:

setup.exe -options <responsefilename> -silent

The installation runs in the background, and Financial Management is installed with the settings of the original installation.

Page 41: Hfm install

Installing the Client Tier Components 43

C h a p t e r

6Installing the Client Tier

Components

The client is offered through Web servers or through a Win32 client installed on the local computer. Requirements at the client level are minimal, as no processing or business rules are performed on the client. For client requirements, see “Client Tier” on page 20.

Before installing Financial Management, you must complete these steps:

Install and configure Shared Services.

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.

In This Chapter Installing Financial Management on the Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Installing Smart View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Verifying Communications Between the Application Server and Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Verifying Communications Between the Application Server and Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Page 42: Hfm install

44 Installing the Client Tier Components

Installing Financial Management on the ClientThe Financial Management installation program installs files needed to run Financial Management and common components used by multiple Hyperion products.

The Typical installation for client installations does not install server components. If you need to install server components, see Chapter 5, “Installing Financial Management Server Components”.

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.

To install Financial Management on the client tier:

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.

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.

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.

8 From Setup Type, select Typical, and click Next.

9 From Component Selection, select the components to install, and clear components that you do not want to install.

10 For a Typical installation, you can install these components:

Win32 Client Install all components for the Windows 32 client desktop.

Hyperion Application Link (HAL) Adapter

Page 43: Hfm install

Installing Smart View 45

ADM Client Install Analytic Data Model (ADM) if you use Financial Management with Financial Reporting, Web Analysis, or Application Builder. ADM is the connectivity component between Hyperion data sources. You can also install ADM later on another machine.

Sample Applications Select this option to install sample applications.

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

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

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

14 Run the configuration utility.

See Chapter 7, “Configuring and Setting Up Financial Management”.

Installing Smart ViewSmart View 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, and work with Financial Management functions.

The Financial Management Setup program places the installer for Smart View for Office in this location:

C:\Hyperion\FinancialManagement\Web\HFMOfficeProvider.

The installer for Smart View is named SmartView.exe. You can distribute the installer to your users using several methods, for example, by e-mail or by a URL. You can also create a public workspace with a SmartView link to the installer and specify a security group for add-in users. Users in the specified security group can then click the link and run the installation. For information on creating a workspace, see the Financial Management User’s Guide.

After Smart View is installed, users must create a connection to Financial Management using the SmartView Connection Manager.

For instructions on using Smart View, see the Smart View for Office User Guide or Online Help installed with Smart View.

To install Smart View on the client tier:

1 Navigate to the Smart View installation file location specified by your administrator.

2 Double-click the SmartView.exe file to run the installation and click Next.

3 Install Smart View to the default path, C:\Hyperion\SmartView, or click Change to install to another directory, and click Next.

4 Click Install.

5 Click Finish to exit the installation wizard.

Page 44: Hfm install

46 Installing the Client Tier Components

The next time that you open Microsoft Excel, Word, or PowerPoint, a Hyperion menu is added to the menu bar.

Note: Before you uninstall Smart View, you must exit all Microsoft Office applications. When you uninstall Smart View, several registry items remain on your computer to preserve your Smart View login and user preference information. These files are in the HKEY_CURRENT_USER\Software\Hyperion Solutions folder and are called Hyperion SmartViewConnections, Login, and Preferences.

Verifying Communications Between the Application Server and Client

After setting up the application server and the client workstation, you must make sure that communications between the server and client are working properly.

Verify these items:

Make sure that the user logged on the application server has administrative rights to the Windows server.

Check the Distributed Component Object Model (DCOM) configuration on the application server and the client workstation. DCOM configuration must be enabled on the application server. The Default Authentication level must be set to None on the client workstation to enable Financial Management components to communicate with other Hyperion products.

To confirm communications between the application server and the client, you must register the application server at the client workstation.

Page 45: Hfm install

Configuring and Setting Up Financial Management 47

C h a p t e r

7Configuring and Setting Up

Financial Management

You run the Hyperion Configuration Utility to configure Hyperion products. After running the Hyperion Configuration Utility, you must run the Financial Management Configuration Utility, which enables you to perform these tasks:

Configure application servers

Set up application server clusters

Register and unregister application server clusters

Configure Web servers

Set up links to Related Content

Configure Smart View

Whenever you install or reinstall Financial Management, you must run the Financial Management configuration utility.

After running the configuration utilities, you can test the Financial Management installation.

In This Chapter Hyperion Configuration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Task Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Configuring Product Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Launching the Configuration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Registering Products with Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Deregistering Products with Shared Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Reconfiguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Configuration Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Completing Financial Management Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Using the Financial Management Configuration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Configuring Application Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Configuring Application Server Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Registering Application Server Clusters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Configuring Web Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Configuring Related Content. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Configuring Smart View for Office Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Page 46: Hfm install

48 Configuring and Setting Up Financial Management

Setting Up the Web Server for Web Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Setting Up Proxy Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Running IIS 5.0 Isolation Mode in IIS 6.0 on Windows 2003 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Verifying Startup Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Starting Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Testing Installed Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Using Sample Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Creating Test Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Page 47: Hfm install

Prerequisites 49

Hyperion Configuration UtilityHyperion Configuration Utility is a common tool used to configure installed Hyperion products. This utility is installed with the first product installed on a machine, and you can use it to configure all products that are installed on that machine. You must run the Configuration Utility on each machine to which a product is installed.

Configuration involves these tasks:

Product option activation - To comply with your license agreement, select the product features that you are authorized to use.

Shared Services Registration- To use Shared Services to provision and share users among Hyperion product applications

Relational database configuration - To store and retrieve application data in a database repository.

Application server deployment - To deploy the application automatically, or partially, to an application server.

Shared Services deregistration - To deregister products form Shared Services before upgrading or installing these products.

You can use the Configuration Utility to perform configuration tasks sequentially for multiple products in one session. The sequence of Configuration Utility pages depends on your product and task selections. As a troubleshooting measure, perform configuration tasks individually for one product at a time.

You can reconfigure products after the initial configuration, following the same procedures.

PrerequisitesComplete these tasks before using the Configuration Utility:

Task Documentation

Install, configure, and start the Shared Services server. Shared Services Installation Guide

“Starting Shared Services” on page 67

Install the application server that you plan to use. Application server documentation

Prepare a database to use for relational storage.

The database user that you specify during configuration should have the following user rights for the database: inserting seeded data and creating, deleting, and updating tables.

Database documentation

Install Hyperion products.

Note: Do not start the product that you are configuring.

Product installation guide

Page 48: Hfm install

50 Configuring and Setting Up Financial Management

Task SequenceWhen performing multiple configuration tasks in one session, the Configuration Utility orders the tasks for you. If you use the Configuration Utility to perform tasks individually, follow this order:

Shared Services registration

Database configuration

Application server deployment

Some products may require a different configuration order.

Configuring Product UpgradesUse the Configuration Utility to configure products that are upgraded from a previous System 9 release. The Configuration Utility determines whether the products installed on the machine are new or upgraded. The product selection page indicates which products were specified as upgrades during the product installation process.

All configuration tasks are available for upgraded products; however, if an upgraded product is configured for a relational database, the database configuration page is read-only except for the password. You can configure only one upgraded product at a time because each product may be configured for a different database. Similarly, you cannot configure new products and upgraded products simultaneously.

If you are upgrading Shared Services and products, upgrade Shared Services first. You must activate upgraded products and reregister them with Shared Services.

Note: The Configuration Utility is backward compatible with previous System 9 releases and can be used to configure products for that release.

Launching the Configuration UtilityYou must run the Configuration Utility on each machine to which a product is installed. The utility can be launched from a product installer or independently.

To launch the Configuration Utility:

1 Choose a method:

On the last page of a product installer, select the option to launch the Configuration Utility.

On Windows, choose a method:

From Start, select Programs > Hyperion > Foundation Services > Configuration Utility.

Double-click the configtool.bat file from:

\%HYPERION_HOME%\common\config

Page 49: Hfm install

Registering Products with Shared Services 51

From a Windows console, change to this directory:

\%HYPERION_HOME%\common\config

Then type:

startconfigtool.bat -console

Note: If you are running the Configuration Utility in console mode, follow the command-line prompts.

2 On the welcome page, click Next.

3 From the list of installed products, select those to configure and click Next.

A list of configuration tasks is displayed.

4 Follow the instructions for configuration tasks, as appropriate for the selected products. For Financial Management, these tasks are available:

“Registering Products with Shared Services” on page 51

“Using the Financial Management Configuration Utility” on page 53

“Deregistering Products with Shared Services” on page 52

Registering Products with Shared ServicesShared Services functionality is programmed into Hyperion products to enable user provisioning, single-sign on, and metadata management.

Products that implement Shared Services functionality require access to the Shared Services server and to a database dedicated to Shared Services. Registering with Shared Services enables a product to implement the required information in the Shared Services server by creating a registration file under its corresponding product directory in Shared Services.

To register products with Shared Services:

1 Launch the Configuration Utility.

See “Launching the Configuration Utility” on page 50.

2 From the list of installed products, select those to configure and click Next.

3 On the task selection page, select Shared Services Registration and click Next.

4 Specify Shared Services server information:

Table 7 Shared Services Server Fields

Server Enter the computer name (host name) where Shared Services server is installed. Do not specify an IP address for the server, especially in DHCP environments.

Port Enter the Shared Services server port number, or accept the default (58080).

User Enter the username of the Shared Services Administrator.

Page 50: Hfm install

52 Configuring and Setting Up Financial Management

5 Click Next to go to the next configuration task or to finish.

Deregistering Products with Shared ServicesIf you need to uninstall a Hyperion product after installation and configuration, and if the product is registered with Shared Services, first deregister the product before uninstalling it.

To deregister products with Shared Services:

1 Launch the Configuration Utility.

See “Launching the Configuration Utility” on page 50.

2 From the list of installed products, select those to configure and click Next.

3 On the task selection page, select Shared Services Deregistration and click Next.

On the Shared Services location page, the Server, Port, and User fields display the information that was specified when the product was registered with Shared Services.

4 In the Password text box, enter the password for the specified Shared Services user.

5 Click Next to go to the next configuration task or to finish.

ReconfigurationThe Configuration Utility enables you to reconfigure Hyperion products multiple times. Reconfiguration procedures are identical to the initial configuration procedures. Launch the Configuration Utility, select the products to reconfigure, and repeat the procedures. Select the options that you want to change and follow the prompts to enter the required information.

Product activation is not required when you reconfigure.

Configuration TroubleshootingBecause the Configuration Utility separates configuration from product installation, the task of tracking and correcting configuration errors is simplified. The Configuration Utility logs configuration errors and warning messages to a log file, configtool.log, in a central location:

Windows:%HYPERION_HOME%\logs\config

Password Enter the password for the Shared Services Administrator.

SSL Select this checkbox if you are using Secure Sockets Layer (SSL).

Table 7 Shared Services Server Fields

Page 51: Hfm install

Configuring Application Servers 53

Note: If you experience problems with configuration, as a troubleshooting measure, perform configuration tasks individually for one product at a time.

Completing Financial Management ConfigurationAfter running the Hyperion Configuration Utility, you must run the Financial Management Configuration Utility to complete the Financial Management configuration. The configuration utility is a wizard that enables you to enter server security information and create database links when you run it on the application server, register servers and create virtual Web directories when you run it on the Web server, set up links to related content, and configure Smart View.

Using the Financial Management Configuration Utility The tabs that display in the configuration utility depend on the components that you are configuring. For example, the Application Server and Application Server Cluster tabs pertain to an Application Server installation. The Server/Cluster Registration tab pertains to the Client installation. The Web Server, Related Content, and Smart View tabs pertain to a Web Server installation.

To start the configuration utility:

1 Select Start > Programs > Hyperion System 9 Applications+ > Financial Management > Server and Web Configuration, or select the Financial Management Configuration task from the Hyperion Configuration Utility.

2 Enter information on each tab and click Apply to save your changes before moving to the next tab.

Note: If you click Cancel and move to another tab before applying changes, the system prompts you with a message that changes have not been applied. You can click Yes to save the changes, or No to exit the utility without saving changes.

3 When you finish entering information for each tab, click OK to save your changes and close the utility.

Configuring Application ServersYou use the Financial Management configuration utility to configure application servers.

Configuring DCOM Security InformationThe configuration utility enables you to configure Distributed Component Object Model (DCOM) security. For instructions on setting up security classes and roles, see the Financial Management Administrator’s Guide.

Page 52: Hfm install

54 Configuring and Setting Up Financial Management

Note: You must run the configuration utility as a Domain or Local Administrator to configure the DCOM user.

The Financial Management application server is built using DCOM technology. DCOM enables network-based component interaction and enables process sharing across a network. All Financial Management application server processes are run under an administrator identity (the specified Windows admin user), so no other administrator is required to log on the application server to start the application server processes.

You must specify the Windows administrator under whose identity the application server processes are launched.

After you enter the Windows administrator information, the system performs these steps:

Creates the Windows admin user (DCOM user) if the user does not exist. The user must be part of the server domain to access Financial Management tasks and application elements.

Adds the user to the local Administrators group

Note: The Financial Management administrator user or group must be a member of the local Administrators group on each application server.

Assigns to the admin user these local security policies: “Act as part of the operating system” and “Log on as a batch job” . These local security rights must be enabled for users on each Financial Management application server.

Sets the “DCOM Run as” identity for all Financial Management application processes

Sets DCOM Launch permissions for users

To specify the DCOM user information:

1 From the Financial Management Configuration Utility, select Application Server.

2 For DCOM User Info, enter the domain and username.

If a username is not specified, security settings are retained from the previous configuration (if applicable).

Note these limitations for the domain and username:

A username cannot duplicate any other user or group name of the computer being administered. A username can contain up to 20 uppercase and lowercase letters. A username cannot consist solely of periods ( . ) and spaces and cannot contain these special characters: " ‘ / \ [ ] : ; | = , + * ? < > &

Do not use a single quotation mark ( ‘ ) in a username. A user with a single quotation mark in the username cannot log on Financial Management.

You cannot use an IP address as a domain name when you configure the user account.

3 Enter the user password.

Note: The password can contain up to 14 characters.

Page 53: Hfm install

Configuring Application Servers 55

4 Re-enter the password.

The Password and Confirm Password boxes are case-sensitive.

Note: If the entries that you make require changing the local security policy on the system, you must log off and log on again to commit the changes.

Specifying the Application Creator and Administrator GroupsYou must specify the Financial Management Application Creator group and Administrator Group. The Creator Group and Administrator Group can be the local Windows security group or a domain group. Only the users in the Creator group can create Financial Management applications. Only the users in the Administrator group can access administrative tasks.

To specify the Application Creator Group and Administrator Group:

1 From the Financial Management Configuration Utility, select Application Server.

2 In the Application Security section, enter the Creator Group name, or leave the default setting of Everyone.

3 In the Administrator Group box, enter the Administrator Group name.

Setting Server Working Folder and Database InformationYou must specify the Financial Management Application Server Working folder, the database link file, and the number of pooled database connections. You can, if you choose, specify the database tablespaces in which data tables and indexes are created.

To specify the folder and database link information:

1 From the Financial Management Configuration Utility, select Application Server.

2 In the Working Folder and Database Link section, enter or browse to the path for the Server Working Folder.

The Server Working folder stores system-generated files, such as reports. The default location for the Server Working Folder is: C:\Hyperion\FinancialManagement\Server Working Folder.

Note: When you use multiple application servers, each server should have its own working folder. Application servers should not share working folders as temporary files might be overwritten.

3 Enter or browse to the database link (UDL) file name that you created when you set up the database.

Page 54: Hfm install

56 Configuring and Setting Up Financial Management

If you do not have a database link, you must create one. A database link (UDL) provides a connection between an application server and a database server. You must create a database link for each application server to access applications. The database 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.

Note: For instructions on creating a database link, see “Creating Data Link (UDL) Files” on page 28.

4 Optional: To specify the database tablespaces in which the Financial Management data tables and indexes

are created, click next to Data Tablespace or Index Tablespace; select the location for the data tables, the indexes, or both, and click OK.

If you do not specify a tablespace, the default tablespace is used.

Note: For IBM DB2 Database Managed Space (DMS), or for Oracle and SQL databases, you can specify a tablespace for the data table and a tablespace for the index. For IBM DB2 System Managed Space (SMS), you can specify only a data tablespace, which is used for both the data table and the index. You cannot specify a separate tablespace for the index.

5 Enter the number of maximum pooled relational database connections for the application, or use the default setting of 40.

Note: Financial Management requires approximately 25 relational database connections per application in addition to the number that you specify in the Relational Database Support dialog box.

Enabling Multiple Server Support

Note: If you want to use application server clusters, you must enable multiple server support. If you do not want to enable multiple server support, you can skip this topic. Click Apply before closing the utility or moving to the next tab.

You must enable multiple-server support to access an application from multiple application servers. You can control the amount of time between when users make changes to data or to an application and when the changes are visible to users who are accessing the data or application from another application server.

If you use multiple application servers connected to one database server, you must make sure that the system clocks on the application servers are synchronized to the second. If the clocks are not synchronized, the data being viewed might not be current.

Note: The synchronization between Financial Management application servers is based on system time. Changing the clock can affect this. For the time change to and from Daylight Savings Time, Hyperion recommends that you stop the servers before the time change, and then restart them afterwards.

Page 55: Hfm install

Configuring Application Servers 57

To enable access to an application from multiple application servers, all application servers must have this setup:

Multi-server support enabled

Access to the same data link (UDL file)

Access to the same data link (UDL file) for Extended Analytics

To enable multiple server support:

1 From the Financial Management Configuration Utility, select Application Server.

2 In the Multi Server Support section, select Enable Multi Server Support.

3 In the Maximum Application Server Delay (Seconds) box, enter the time interval between when a change is made to an application and when the change is visible to users accessing the application through another application server.

4 In the Maximum Data Synchronization Delay (Seconds) box, enter the time interval between when a change is made to data and when the change is visible to users accessing the data through another application server.

Tip: If these text boxes are grayed out, deselect them and then reselect them to adjust the settings.

Specifying a Data Source for Extended Analytics (Optional)

Note: If you do not want to specify Data Source Name (DSN) information for Extended Analytics, you can skip this topic. Click Apply before moving to the next tab or closing the utility.

A data source name (DSN) is used to specify the relational database destination for Extended Analytics. You must specify the data source name and path. You can add, remove, or modify data source names as needed.

You should not use the relational database and UDL file for Extended Analytics that you use for your Financial Management applications. You should create a database for the exported star schema and data and a UDL file that points to the database.

Note: When you use multiple servers with the Extended Analytics feature, you must enable multiple server support on each application server, and you must set up each application server so that these elements are the same on all servers: Clock setting, Data source, and UDL file.

To add a data source name:

1 From the Financial Management Configuration Utility, select Application Server.

2 In the DSN Info section, click Add DSN.

3 In the DSN Name box, enter the data source name.

4 In the DSN Path box, enter or browse for the data source path.

Page 56: Hfm install

58 Configuring and Setting Up Financial Management

5 Optional: To specify the database tablespaces in which the Financial Management data tables and indexes are created, follow these steps:

a. Click (next to the Data Tablespace field), and select the data table location.

b. Click OK.

c. Click (next to the Index Tablespace field), and select the index location.

Note: For Oracle and IBM DB2 SMS, you can specify only a data tablespace; index tablespaces are not used.

d. Click OK.

6 Click OK.

To modify a data source name:

1 Select Application Server.

2 In the DSN Info section, select the DSN.

3 Click Modify DSN and change the name.

To remove a data source name:

1 Select Application Server.

2 In the DSN Info section, select the DSN.

3 Click Remove DSN.

Configuring Application Server ClustersAn application server cluster is a set of application servers running the same application. Clustered application servers provide load balancing and failover capacity, and enable the servers to be transparently maintained while applications remain available for users.

Note: To use application server clusters, you must enable multiple server support.

To set up application server clusters:

1 From the Financial Management Configuration Utility, select Application Server Clusters.

2 For Cluster Name, enter an application server cluster name.

To add a cluster or server, click Add Cluster, enter the name, and click OK.

To remove a cluster or server, select the name, and click Remove Cluster.

3 Specify the names of the application servers that participate in the cluster:

To add servers to a cluster, click Add Server, enter the server name, and click OK.

Page 57: Hfm install

Registering Application Server Clusters 59

To remove servers from a cluster, select the server name, and click Remove Server.

Enabling Remote Activation (DCOM Limits for 2003 and XP)If you use Windows 2003 Service Pack 1 or Windows XP Service Pack 2, you might experience problems starting Financial Management remotely as an Anonymous User. If you are using these, the Configure Limits button will be active if DCOM settings are not configured for Financial Management.

Note: If you use Windows 2000, this button is not displayed.

Hyperion recommends that if the button is active for your computer, you should click it to enable the Financial Management Server to be started remotely.

To enable remote activation for Windows 2003 SP1 or Windows XP SP2:

1 From the Financial Management Configuration Utility, select Application Server Clusters.

2 From Enable Remote Activation, click Enable Limits.

3 Click Apply to apply the changes.

Configuring SecurityFinancial Management stores user security class access information in the database. This information is partly keyed by a unique user identity. MSAD and LDAP provide different formats to represent the unique user identity (DN, ObjectGUID). This action updates the format of the user identity to conform to the one specified in the User Management Console for each respective provider. The action has no effect unless the user identity format has been changed in the console.

If you do not need to migrate users, you can skip this topic.

To migrate users:

1 From the Financial Management Configuration Utility, select the Security tab.

2 Click Migrate Users.

Registering Application Server Clusters You must register an application server cluster before you can create or open an application on the server cluster. Registering a server cluster with one server of the cluster registers the cluster with all servers of the cluster.

Page 58: Hfm install

60 Configuring and Setting Up Financial Management

For example, you create an application server cluster named Marketing_Servers and add application servers Mkt1, Mkt2, Mkt3, and Mkt4. To register the cluster, you enter Mkt2 in the register server field.

If you run the configuration utility from an admin account, the configuration utility creates the HKeyLocalMachine/Software/Hyperion Solutions registry key so that you can register server clusters. If you are not running the configuration utility from an admin account, you might encounter problems when registering servers. In this case, in the registry, you should manually assign Read/Write access rights to HKeyLocalMachine/Software for the user who is registering the servers.

When you specify an individual server name from the servers in the cluster, the entire cluster is registered. If there is only one application server in the server cluster, you must enter the server name.

To register an application server cluster:

1 From the Financial Management Configuration Utility, select Server and Cluster Registration.

2 Enter the application server name that you are registering.

The application server name is used to obtain application server cluster information.

3 Select one of these options:

Use Automatic Load Balancing - to register the server cluster that was created in the Application Server Clusters tab.

Use One Server Only - to specify that only one server be used instead of a cluster

4 Click Add Cluster.

Tip: If you need to unregister a cluster, select it from the list and click Remove Cluster.

Enabling DCOMFrom the Financial Management configuration utility, you can enable DCOM for the entire computer. Enabling DCOM makes possible the launching of servers and connecting to objects by remote clients for the machine. It also sets the DCOM Default Authentication level to None for the computer. The Enable DCOM step is required for Financial Management client components to communicate with Financial Management application server components when the application server is on a different computer. It also makes it possible for the Financial Management client and application server computers to be on different domains.

To enable DCOM:

1 From the Financial Management Configuration Utility, select Server and Cluster Registration.

2 Click Enable DCOM.

Note: This button is grayed out if previously configured.

Page 59: Hfm install

Configuring Web Servers 61

3 Click Apply.

Configuring Web ServersYou use the Financial Management Configuration Utility to configure Web servers.

You must register an application server on the Web server machine for users to be able to connect to the application server through the Web. See “Registering Application Server Clusters” on page 59.

Specifying Web DirectoriesYou must create a virtual directory on the Financial Management Web server for the Financial Management Web components to be accessible to Web users. You specify the Web installation directory and the directory URL.

To create Web directories:

1 From the Financial Management Configuration Utility, select Web Server.

2 In the Web Server Installation Directory box, enter or browse to the path for the Financial Management Web installation directory.

Note: The default location is the directory in which the Web components were installed, for example, C:\ Hyperion\FinancialManagement\Web\HFM.

3 In the Virtual Directory Name box, enter the virtual directory name, for example, HFM.

Specifying the File Transfer DirectoryYou must create a file transfer directory for load and extract log files and temporary files. When you set up the file transfer directory, the system performs these steps:

Creates the file transfer directory, if it does not exist

Assigns the IIS users Windows permissions of Read, Write, and Execute

Page 60: Hfm install

62 Configuring and Setting Up Financial Management

To specify the File Transfer directory, browse to the for the folder for the load, extract, and log files, or use the default location, for example: C:\Hyperion\FinancialManagement\Web\HFM\FileTransfer

Setting ASP Properties (Optional)If you use IIS 6.0, you can use the Financial Management Configuration Utility to set the file size properties for loading and extracting files on the Web. Hyperion recommends that you use the default file size properties unless you experience problems during loading and extracting. However, if you load or extract huge files and send large amounts of data to the browser and experience errors, you can change the file size settings.

For example, if you load large files you might receive a 403 error message if the maximum upload file size is set too low. In this case, you must increase the maximum file size. You enter the file size in bytes, so if you expect to load files of 200 megabytes, you change the setting for maximum upload file size to 200,000,000 bytes.

To set ASP properties:

1 From Web Server, in the Max Upload File Size box, enter a maximum size for loading Web files.

2 In the Response Buffer Size box, enter a maximum size for extracting Web files.

Enabling SiteMinder Web Security Agent Support (Optional)When you set up Financial Management security, you can use Netegrity SiteMinder as a Web security agent, which is a Web access management solutions provider used to protect Web resources. When you use SiteMinder, the system bypasses the Financial Management Web logon screen and the user’s credentials are sent from SiteMinder. The system verifies the credentials sent by SiteMinder against the external authentication provider and uses the credentials to log the user on to Financial Management.

In addition to selecting the security agent support check box, the administrator must configure external authentication to enable SiteMinder. See the Hyperion Shared Services Installation Guide.

To enable SiteMinder Web Security Agent Support:

1 Configure external authentication to enable SiteMinder.

2 From the Financial Management Configuration Utility, select Web Server, and select Enable Web Security Agent Support.

Page 61: Hfm install

Configuring Web Servers 63

Specifying Support for AlertsYou can use e-mail alerts for intercompany transactions, intercompany matching reports, and during the process control review process to highlight key events or data changes in the system. E-mail alerts are sent using standard Simple Mail Transfer Protocol (SMTP) protocol. To enable e-mail alerts, you must specify the SMTP server name. For information on using alerts, see the Financial Management User’s Guide.

To specify support for alerts:

1 From the Financial Management Configuration Utility, select Web Server.

2 In the Alert SMTP Server box, enter the SMTP server name.

Specifying URLs for Other Hyperion Applications

Note: If you do not want to access other Hyperion applications, you can skip this topic. Before moving to the next tab or closing the utility, click Apply.

You can launch other Hyperion products from the Financial Management Home page and access other Hyperion applications without having to supply login information. You must specify the URL for each application that you want to access.

To specify URLs for other Hyperion applications:

1 From the Financial Management Configuration Utility, select Web Server.

2 In the Application Links section, enter the URL for the Hyperion application that you want to access.

The URL is case-sensitive.

Note: The Shared Services URL is the URL for the Web Server link (not your application server).

Setting Web Server DCOM User InformationIf you are installing only the Web Server components, you must specify the DCOM user information on the Web Server tab.

To set DCOM user information:

1 From the Financial Management Configuration Utility, select Web Server.

2 For the DCOM user information, enter the Domain, username, and user password, and confirm the password.

Note: The Password and Confirm Password boxes are case-sensitive.

Page 62: Hfm install

64 Configuring and Setting Up Financial Management

3 Click Apply.

Configuring Related ContentYou can link from Financial Management to related content in other applications, such as Financial Reporting and Web Analysis. The Related Content feature enables you to include reports, views, and folders from other applications directly within Financial Management on the Web.

To link to related content in another application:

1 From the Financial Management Configuration Utility, select Related Content.

2 Enter the URL to the related content resource server. To obtain the URL, see the documentation for that product.

3 Click Add to add the URL to your URL list or Remove to remove a URL.

Note: After adding or removing a URL, you must close and reopen the Resource Server dialog box to see your changes.

4 Click Apply.

Configuring Smart View for Office ServicesThe Smart View for Office Services component enables you to use Smart View and is supplied as part of the Financial Management installation. If you did not select this component when you ran the installation, you can rerun the installation process and install it.

To configure Smart View:

1 From the Financial Management Configuration Utility, select Smart View for Office Services.

2 In the Web Session Timeout box, enter the Web session timeout value in minutes.

Note: The default session timeout is 20 minutes. You should set the timeout option to a length of time appropriate for your Smart View sessions.

3 In the Installation Folder box, enter the location in which the SmartView component was installed or use the default location.

Note: The default location is: C:\Hyperion\FinancialManagement\Web\HFMOfficeProvider.

4 In the Virtual Directory Name text box, enter the virtual directory name for Smart View for Office, or use the default virtual directory.

The default directory name is HFMOfficeProvider.

Page 63: Hfm install

Setting Up Proxy Authentication 65

5 Optional: From the Deployment section, select an option:

Always force client to upgrade to upgrade to the latest add-in version to ensure that the client and server versions are compatible

Always warn when client version is newer to warn of a newer add-in version

6 Optional: If you use a proxy server between the Web server and client, select Enable connection keep alive, and set a time interval in seconds for the connection.

Setting Up the Web Server for Web AuthenticationWhen you set up the Web server, you can use the default setting of anonymous authentication. However, if you have high security requirements, you can set up the server to use Web authentication.

Note: If you use proxy authentication, see “Setting Up Proxy Authentication” on page 65.

To set up the Web server to use Web authentication:

1 Do one of these tasks to start IIS:

For Windows 2000 Server, select Start > Programs > Administrative Tools > Internet Services Manager or Start > Settings > Control Panel > Administrative Tools > Internet Service Manager.

For Windows 2003 Server, select Start > Settings > Control Panel > Administrative Tools > Internet Information Services (IIS) Manager.

2 Expand the Internet Information Server folder, and expand the Default Web Site folder.

3 Right-click the folder to use for Web authentication, for example, the HFM folder for the Web, and select Properties.

4 Select Directory Security.

5 In the Anonymous Access and Authentication Control section, click Edit.

6 Clear Anonymous Access, and in the Authenticated Access section, select Basic Authentication or Integrated Windows Authentication.

7 Click OK.

Setting Up Proxy AuthenticationThis topic describes the procedures for setting up proxy authentication for Internet Explorer.

Note: You cannot enable both Web authentication and proxy authentication; dual authentication functionality is not supported. Before you use proxy authentication, you must disable Web authentication if it is enabled, and set proxy authentication.

Page 64: Hfm install

66 Configuring and Setting Up Financial Management

To enable proxy authentication for Internet Explorer:

1 From Internet Explorer menu, select Tools > Internet Options > Properties.

2 Select Connections, and click LAN Settings.

3 From the LAN Settings box, in the Proxy Server section, select Use a Proxy Server.

Note: You cannot specify the proxy server and port in the LAN Settings dialog box. You must specify the proxy server and port in the Proxy Settings dialog box.

4 In the Proxy Server section, click Advanced.

5 From the Proxy Settings box, specify the proxy server; for example, specify a proxy server for HTTP protocol and a port number.

Note: Make sure that the Use Same Proxy Server for All Protocols option is not selected.

6 To bypass the proxy server for local addresses:

In the Exceptions box in the Proxy Settings dialog box, specify the local addresses.

From the Proxy Server section of the LAN Settings dialog box, select Bypass proxy server for local addresses.

7 Click OK.

Running IIS 5.0 Isolation Mode in IIS 6.0 on Windows 2003If you run IIS 5.0 Isolation mode in IIS 6.0 on Windows 2003, after you run the configuration utility and create your Web directories, you must manually set two additional IIS properties for the application protection and authentication level.

To set the IIS 5.0 properties:

1 Select Start > Programs > Administrative Tools > Internet Services Manager.

2 Expand Internet Information Services and its subdirectories, and right-click the virtual directory for Financial Management, for example, HFM.

3 On the Virtual Directory tab, from the list for Application protection, change the setting to High (Isolated).

4 Close Internet Services Manager.

5 Select Start > Programs > Administrative Tools > Component Services.

6 Expand the folders, and select COM+ Applications.

7 Select the Financial Management Web site, for example, IIS (Default Web Site//Root/HFM).

8 Right-click the Web site, and select Properties.

9 On the Security tab, from the list in the Authentication Level for Calls, change the setting to None.

Page 65: Hfm install

Starting Shared Services 67

Verifying Startup DependenciesBefore starting, you must verify that the dependent software components are running:

Starting Shared ServicesThis section describes how to start Shared Services if you did not deploy the Shared Services application server as a Windows service. If you deployed the Shared Services application server as a Windows service, start the service manually from Windows control panel.

To start Shared Services server:

1 Choose a method:

On Windows, select Start > Programs > Hyperion System 9 Foundation > Start Shared Services.

The menu item indicates which application server the Shared Services server is deployed to.

Execute the startup script:

Component How to Verify Successful Startup How to Start

Hyperion Shared Services™ server

On the Shared Services server computer, look for confirmation messages in the server console window or launch User Management Console. See “Verifying Successful Startup of Shared Services” on page 68.

See “Starting Shared Services” on page 67.

Application Server Path to Script

IBM WebSphere Windows:

<HSS_HOME>\AppServer\InstalledApps\<AppServName>\<version>\SharedServices9\bin\startSharedServices9.bat

UNIX:

<HSS_HOME>/AppServer/InstalledApps/<AppServName>/<version>/SharedServices9/bin/startSharedServices9.sh

BEA WebLogic Windows:

<HSS_HOME>\AppServer\InstalledApps\<AppServName>\<version>\SharedServices9\startSharedServices.bat

UNIX:

<HSS_HOME>/AppServer/InstalledApps/<AppServName>/<version>/SharedServices9/startSharedServices.sh

Oracle Windows:

<OracleInstallDir>\bin\emctl start iasconsole<OracleInstallDir>\opmn\bin\opmnctl startall

UNIX:

<OracleInstallDir>/bin/emctl start iasconsole<OracleInstallDir>/opmn/bin/opmnctl startall

Page 66: Hfm install

68 Configuring and Setting Up Financial Management

Verifying Successful Startup of Shared Services

To verify successful startup and configuration of Shared Services:

1 Look for the following confirmation messages in the Shared Services console window during startup:

Database Configuration Test Passed

Security System Initialized Successfully

Shared Services Initialized Successfully

On UNIX and Windows, when Shared Services is deployed to WebSphere, these confirmation messages are logged to the following file:

Windows:

<WebSphereInstallDir>\AppServer\logs\SharedServices9\SystemOut.log

UNIX:

<WebSphereInstallDir>/AppServer/logs/SharedServices9/SystemOut.log

On UNIX and Windows, when Shared Services is deployed to WebLogic, these confirmation messages are also logged to the following file, unless the log level is set to WARN:

Windows:

<HSS_HOME>\AppServer\InstalledApps\WebLogic\8.1\SharedServices9\ logs\SharedServices_Metadata.log

2 On the Shared Services server computer, launch the User Management Console login page using one of these methods:

a. Open a browser and enter this URL:

http://SharedServicesServerName:port#/interop

where SharedServicesServerName is the name of the computer where the Shared Services Server is installed and port# is the Shared Services Server port number. The default port number is 58080; if Shared Services Server is installed to a non-default port, specify that value. For example, using the default port:

http://jdoe:58080/interop/

Note: As a best practice when accessing User Management Console on the machine where the Shared Services Server is running, the URL to access the console should always use an IP address or a fully qualified machine name that includes the domain name. If the IP address is dynamic, use the fully qualified machine name.

Apache Tomcat Windows:

<HSS_HOME>\AppServer\InstalledApps\<AppServName>\<version>\SharedServices9\bin\startSharedServices9.bat

UNIX:

<HSS_HOME>/AppServer/InstalledApps/<AppServName>/<version>/SharedServices9/bin/startSharedServices9.sh

Note: <HSS_HOME> is the directory where Shared Services is installed; for example, c:\hyperion\SharedServices\9.0.

Application Server Path to Script

Page 67: Hfm install

Testing Installed Components 69

b. On Windows, select Start > Programs > Hyperion System 9 Foundation > User Management Console.

If the User Management Console login page is displayed, Shared Services server is started successfully.

Testing Installed ComponentsYou can test the Financial Management installation by verifying that you can log on and open an application. You can use an existing application or use sample files to quickly populate a small test application. See “Using Sample Files” on page 70.

Note: Before you can create or open an application in Financial Management, you must create a project in Shared Services. See “Creating a Shared Services Project” on page 70.

After configuring the Web Server, you should test to make sure that you can start Financial Management in a Web browser. When you start Financial Management in a Web browser, you must specify the machine name on which you installed Financial Management and the virtual directory name that you created.

Hyperion recommends that you add Financial Management to the exceptions for your Web pop-up blocker. When you perform some Financial Management tasks, such as loading data on the Web, a status window pops up showing the task status. If you have a pop-up blocker enabled on your computer, the status window is not displayed.

To test that Financial Management starts in a Web browser:

1 Make sure that the Shared Services server is running and that you create a project to use with Financial Management.

If you do not have a project in Shared Services, see “Creating a Shared Services Project” on page 70.

2 Open the Web browser.

3 Enter this text in the Address text box: http://server_URL/aliasdir where server_URL identifies the machine name on which Financial Management and its components are installed and aliasdir is the alias directory name that you created for Financial Management on the Web.

4 On the Logon page, enter a domain, username, and password.

Note: The next time that you log on, the system displays the domain and username from the previous logon.

5 From the Language list, select the language to use for Financial Management.

6 Click Logon.

Page 68: Hfm install

70 Configuring and Setting Up Financial Management

7 Select File > Create Application to create an application, or if you previously created an application, select File > Open Application to open it from the Web browser.

For instructions on creating an application, see “Creating Test Applications” on page 71.

Creating a Shared Services ProjectBefore you can create or open a Financial Management application, you must set up a project in Shared Services.

To create a Shared Services project:

1 Make sure that the Shared Services server is running.

2 Start the User Management Console (http://<servername>:58080/interop) and log on.

3 Select and right-click Projects > New > Project, and type a project name (for example, HFM).

4 Click Finish to save the project and close the User Management Console.

Using Sample FilesFinancial Management provides sample application files that you can use to populate a test application. If you selected to install the Sample Applications component from the Typical or Custom installation process, the files are in the directory in which you installed Financial Management.

Note: By default, the sample applications are installed in C:\Hyperion\FinancialManagement\Sample Apps.

If you did not install the sample files, you can obtain them by reinstalling Financial Management and selecting the Sample Applications component. See “Installing Financial Management” on page 38.

When you create a test application, you can load files from the Sample Apps directory. The directory includes sample security, metadata, data, rules, and journal files; report definitions, data grids; and Web Data Entry form scripts. Instructions for loading the sample files are included in the Documentation folder of each application. See “Loading Sample Files” on page 73.

Table 8 describes application file types:

Table 8 Application File Types

Sample File Contents

Application profile

(.per)

Calendar, language, and frequency definitions for the application

Security (.sec) Application security information

Page 69: Hfm install

Creating Test Applications 71

Creating Test ApplicationsThe following procedure lists the steps for creating a test application.

For instructions on creating applications for a production environment, see the Financial Management Administrator’s Guide.

To create a test application:

1 Make sure that the Shared Services server is running.

2 Open the Web browser and log on to Financial Management.

See “Testing Installed Components” on page 69.

3 Select File > Create Application.

4 From the Server list, select the application server cluster on which to run the application.

If the server cluster is not listed, you may need to register it. See “Registering Application Server Clusters” on page 59.

5 For Application Name, enter an application name, for example, TestApp.

Note: The application label can have a maximum of 10 alphanumeric characters but cannot start with a number or contain spaces or special characters. HFM, HSV, and HSX are reserved names and cannot be used for application names or application descriptions.

6 For Application Description, enter an application description, for example, TestApplication.

Note: The application description can contain a maximum of 40 characters. HFM, HSV, and HSX are reserved names and cannot be used for application descriptions.

Member List (.lst) Dimension member lists

Metadata (.xml) Metadata

Data (.dat) Applicable scenarios and years with data

Rules (.rle) Rules used to run logic on the data in the application

Journals (.jlf) Sample journal and template file formats

Data Explorer (.hde) Explore Data grids

System Report (.rpt) System reports for Explore Data, Journals, or Intercompany Reports

Web Data Grid files (*.xml) Web data grids

Web Data Entry Forms (.wdf) Web Data Entry Form scripts

Table 8 Application File Types (Continued)

Sample File Contents

Page 70: Hfm install

72 Configuring and Setting Up Financial Management

7 Click Browse next to the Application Profile box, navigate to the application profile (.per) file in the Financial Management Sample Apps folder, and click Open.

Example: C:\Hyperion\FinancialManagement\SampleApps\Comma\Profile\CommaCalendar.per

Note: An application profile contains calendar, language, and frequency definitions for the application. The procedures in this topic use files from the Sample Application for the Comma Communications company.

8 From the User Management Project list, select the Shared Services project to which to add the application.

The projects list is populated from the projects that you set up in Shared Services. Each application must belong to a User Management project.

9 In the Financial Management Web Server URL for Security Administration box, enter the protocol, Web server, port, and virtual folder for the application; for example,

http://Server1:80/hfm

The default port for Financial Management is 80. The virtual folder is the Financial Management virtual directory that you created when you ran the configuration utility.

10 Click Create.

11 When the system displays the message “The application was created successfully,” click OK.

Note: If you receive an error message, “There was an error creating the application,” verify the domain, username, and password that you used to log on. If you have additional problems, see “Troubleshooting Applications” on page 106.

Opening Test Applications After you create an application, you can open it and load sample files.

To open the test application:

1 Select File > Open Application.

2 From the Select Cluster list, select the application server on which the application is running.

A list of your applications is displayed.

3 Select the application to open.

Note: When you open an application, the system authenticates your username and password.

4 Verify that the application is open by checking that the application name is displayed in the Financial Management masthead.

Page 71: Hfm install

Creating Test Applications 73

Loading Sample Files After you create and open a test application, you can load sample files to populate the test application. You can use these procedures or the instructions that are included in the Documentation folder of each application.

For instructions on loading files into a production application, see the Financial Management Administrator’s Guide.

You use these procedures to load sample files:

“Loading Security” on page 73

“Loading Metadata” on page 73

“Loading Member Lists” on page 74

“Loading Data” on page 74

“Loading Rules” on page 74

Loading Security Security elements include users, user groups, security classes, and roles. The users that you load must exist in an external authentication file.

To load security:

1 From the Browser View in the left view pane, expand Tasks and select Load Tasks.

2 Select Load Security.

3 In the Security File box, click Browse to locate and open the sample security (.sec) file; for example:

C:\Hyperion\FinancialManagement\Sample Apps\Comma\Security\Comma.sec.

4 Leave the default load selections and click Load.

Loading Metadata Metadata is a set of data that defines and describes the data properties and attributes stored in a database or used by an application. Examples of metadata include dimension names, member names, properties, and time periods.

To load metadata:

1 From the Browser View in the left view pane, expand Tasks and select Load Tasks.

2 Select Load Metadata.

3 In the Metadata Filename box, click Browse to locate and open the sample metadata (.xml) file; for example:

C:\Hyperion\FinancialManagement\Sample Apps\Comma\Metadata\Comma.xml.

4 Leave the default load selections and click Load.

Page 72: Hfm install

74 Configuring and Setting Up Financial Management

Loading Member Lists A member list is a system or user-defined group that references members or functions within a dimension.

To load a member list:

1 From the Browser View in the left view pane, expand Tasks and select Load Tasks.

2 Select Load Member Lists.

3 In the Member Lists File box, click Browse to locate and open the sample member list (.lst) file; for example,

C:\Hyperion\FinancialManagement\Sample Apps\Comma\Lists\Comma.lst.

4 Click Load.

Loading Data You can load base-level input data into an application in an ASCII format.

To load data:

1 From the Browser View in the left view pane, expand Tasks and select Load Tasks.

2 Select Load Data.

3 In the File box, click Browse to locate and open the sample data (.dat) file; for example,

C:\Hyperion\FinancialManagement\Sample Apps\Comma\Data\AllData.dat.

4 Click Load.

Loading Rules Rules automate the calculations for processes such as currency translations, consolidations, and allocations.

To load rules:

1 From the Browser View in the left view pane, expand Tasks and select Load Tasks.

2 Select Load Rules.

3 In the Rules File box, click Browse to locate and open the sample rules (.rle) file; for example,

C:\Hyperion\FinancialManagement\Sample Apps\Comma\Rules\Comma.rle.

4 Click Load.

Page 73: Hfm install

Creating Test Applications 75

Viewing Sample Data After you load sample application files, you can test to see whether you can open a data grid. The Sample Apps directory contains sample grids with predefined rows and columns of sample data.

To view data in a data grid:

1 Select Administration > Manage Documents, or click the Manage Documents button, , and select the Data Grid tab.

2 Click Load.

3 Click Browse to locate and open a sample grid file, for example,

C:\Hyperion\FinancialManagement\Sample Apps\Comma\WebGrids

4 Select a grid name, click OK, and click Finished.

5 Select a grid to open.

The following figure shows a sample data grid. The grid content varies depending on the sample grid that you open.

This test confirms that your installation was successful and that you can connect to a Financial Management application.

Page 74: Hfm install

76 Configuring and Setting Up Financial Management

Page 75: Hfm install

Uninstalling Financial Management 77

C h a p t e r

8Uninstalling Financial

Management

This section describes uninstallation procedures for Financial Management and shared components.

In This Chapter Uninstalling Prior Releases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Uninstalling Shared Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Page 76: Hfm install

78 Uninstalling Financial Management

Uninstalling Prior ReleasesBefore you uninstall Financial Management, stop all activities and processes connected to the Financial Management servers.

The uninstall process does not remove IIS virtual directories, so after uninstalling Financial Management, you must open IIS and manually remove the directories. The uninstall process also may not remove all common components in the <Hyperion_Home>\Common directory because other Hyperion products may be using them. You can manually remove components that you are not using for other products.

If Financial Management is registered with Shared Services, deregister it before uninstalling.

After uninstalling Financial Management or shared components, restart your computer.

To uninstall Financial Management:

1 Deregister Financial Management from Shared Services:

a. Select Start > Programs > Hyperion > Foundation Services > Configuration Utility.

b. Select Financial Management and click Next.

c. Select Shared Services Deregistration and click Next.

d. Enter the password and click Next.

2 Use one of these methods to uninstall:

Navigate to the Uninstall directory in the Financial Management directory, and click UninstallFinancialManagement.exe.

Select Start > Settings > Control Panel > Add/Remove Programs, select Hyperion Financial Management, and click Remove.

3 After the uninstall process is complete, restart your computer.

4 Remove files remaining in the installation directory.

5 Manually remove IIS virtual directories that you created that point to physical directories removed by the uninstall.

6 Make sure that all references to Hyperion Financial Management in the registry are removed.

Uninstalling Shared ComponentsUse these procedures to uninstall shared components for Financial Management. After uninstalling shared components, restart your computer.

Page 77: Hfm install

Uninstalling Shared Components 79

Uninstalling Shared ServicesBefore you uninstall Shared Services, stop all activities and processes tied to Shared Services, including the application server, the database, and any server related to Shared Services. An exception is if you use IBM WebSphere as the Web application server. In this case, leave WebSphere running because it removes files during the uninstall.

When you uninstall Shared Services, you must also manually remove the common components that reside in the Common directory and delete your Shared Services database.

Page 78: Hfm install

80 Uninstalling Financial Management

Page 79: Hfm install

Upgrading to Financial Management 9.2.1 81

C h a p t e r

9Upgrading to Financial

Management 9.2.1

This chapter describes the procedures for upgrading from prior releases.

In This Chapter Upgrading Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Uninstalling Prior Releases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Uninstalling Shared Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Installing Financial Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Upgrading Applications from Prior Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Using the Schema Upgrade Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Page 80: Hfm install

82 Upgrading to Financial Management 9.2.1

Upgrading Overview Use these steps to upgrade from a prior Financial Management release. Detailed procedures are provided in the following sections.

Backing Up Applications You can use Financial Management applications by running an upgrade utility to update them. If you plan to keep applications, you should make backup copies before you uninstall Financial Management.

UPGRADE TASKS REFERENCE

1. Install Shared Services and configure the Shared Services Application Server and RDBMS.

Note: Ensure that the database that you are using for Shared Services is installed and operational before installing Shared Services.

Hyperion Shared Services Installation Guide

2. Save your application data to the relational database and back up your relational database.

RDBMS guide

3. Back up applications. “Backing Up Applications” on page 82

4. Uninstall prior Financial Management releases if needed. “Uninstalling Prior Releases” on page 78

5. Install Financial Management. “Installing Financial Management” on page 86

6. Run the configuration utility and upgrade applications using the HFM Schema Upgrade utility.

Chapter 7, “Configuring and Setting Up Financial Management” and “Using the Schema Upgrade Utility” on page 90.

7. Back up Financial Reporting files, and if necessary, upgrade the version. Hyperion System 9 BI+ Installation Guide

8. If you use Hyperion Application Link, update the Financial Management Adapter extension.

“Installing the Hyperion Application Link Adapter” on page 95

9. If you use Smart View for Office, install it on the client tier. “Installing Smart View” on page 45

10. Activate and configure Hyperion products and register them with Shared Services. You can configure multiple products simultaneously, provided that they are installed on the same computer.

“Registering Products with Shared Services” on page 51 and “Registering Products with Shared Services” on page 51

11. Set up projects, create applications, and provision (assign) users to projects. Hyperion System 9 Shared Services User Management Guide

Page 81: Hfm install

Upgrading Overview 83

To make backup copies of applications, extract and save application files. For instructions on extracting files, see the Financial Management Administrator’s Guide.

Extract and save these application file types to the Temp directory on the application server:

Security files (*.sec)

Metadata files (*.xml or *.app)

Member Lists files (*.lst)

Rules files (*.rle)

Data files (*.dat) - all applicable scenarios and years with data

Journals files (*.jlf) - all applicable scenarios and years with journal data

Calendar files (*.per)

Back up all of these files:

Data Explorer grid files (*.hde)

Web data grid files (*.xml)

Web Data Entry Form files (*.wdf or *.grd)

System Report files (*.rpt, *.xml, or *.html)

Backing Up Database Information In general, all application and user data is stored in the relational database. To preserve application integrity, perform standard backup and restoration procedures as dictated by the RDBMS vendor. Some configuration files and registry settings reside on other servers, however the files and settings are easily re-created in case of loss and do not hamper application integrity.

The following table shows the Financial Management components and recommended backup procedures.

Table 9 Recommended Backup Procedures

Component Data Stored Backup Restore Restore Order

Supported RDBMS All application data Periodic complete database backup using the RDBMS tools available, and regular backups of the transaction log

Restore from last dump and roll in transaction logs

First

Financial Management Primary Server

Registry settings, .UDL file, Report style sheets for system reports (.xsl)

Standard incremental file backups

Standard full restore Second

Financial Management secondary servers

Registry settings, .UDL file, report style sheet for system reports (.xsl)

Standard incremental file backups

Standard full restore Third

Page 82: Hfm install

84 Upgrading to Financial Management 9.2.1

When you perform a periodic complete backup using the database procedures recommended by the vendor, to insure database integrity, you must place the RDBMS in single-user mode. Use of single-user mode temporarily disconnects the application servers from the relational database.

Before you restore a database, stop these services:

Application servers (Financial Management and Financial Reporting servers)

Financial Management server processes:

HsxServer.exe

HsvDataSource.exe (Stop all instances of this process.)

Financial Reporting server processes

When you end processes, all user connections are dropped. After completing the restore procedure, restart the stopped services. Users can then re-connect.

Verifying MDAC Version on the Application Server Before you uninstall Financial Management, you must verify that the Microsoft Data Access Component (MDAC) version running on the application server is MDAC 2.7.1 or higher. The file name for MDAC is msado15.dll.

Note: This file should be in the Program Files\Common Files\System\ado directory. If your system does not have MDAC 2.7.1 installed, Financial Management installs it during the installation process.

To verify the MDAC version:

1 Select Start > Search > For Files or Folders, type msado15.dll, and click Search Now.

2 Right-click the file and click Properties.

3 Select the Version tab.

4 Click Product Version, and ensure that it is 2.7.1 or higher.

5 Click OK.

Uninstalling Prior ReleasesIf you are using a pre-System 9 version of Financial Management, Hyperion recommends that you uninstall it before installing this release.

Financial Management Web server

Registry settings Standard incremental file backups

Standard full restore Fourth

Win32 Client workstations

Win32 grid definitions if HFM Windows client installed

Standard incremental file backups

Standard full restore Last

Page 83: Hfm install

Uninstalling Shared Components 85

If you are using Financial Management 9.2.x, you can install Release 9.2.1over your existing installation.

Before you uninstall Financial Management, stop all activities and processes connected to the Financial Management servers.

The uninstall process does not automatically remove virtual directories from IIS, so after you uninstall Financial Management, you must open IIS and manually remove the directories. The uninstall process also may not remove all common components in the <Hyperion_Home>\Common directory because other Hyperion products may be using them. You can manually remove components that you are not using for other products.

If Financial Management is registered with Shared Services, deregister it before uninstalling.

After you uninstall Financial Management or shared components, restart your computer.

To uninstall Financial Management:

1 Deregister Financial Management from Shared Services:

a. Select Start > Programs > Hyperion System 9 Foundation > Configuration Utility.

b. Select Financial Management and click Next.

c. Select Shared Services Deregistration and click Next.

d. Enter the password and click Next.

2 Use one of these methods to uninstall:

Navigate to the Uninstall directory in the Financial Management directory, and click UninstallFinancialManagement.exe.

Select Start > Settings > Control Panel > Add/Remove Programs, select Hyperion Financial Management, and click Remove.

3 After the uninstall process is complete, restart your computer.

4 Remove files remaining in the installation directory.

5 Manually remove virtual directories that you created that point to physical directories removed by the uninstall.

6 Make sure that all references to Hyperion Financial Management in the registry are removed.

Uninstalling Shared ComponentsUse these procedures to uninstall shared components for Financial Management. After uninstalling shared components, restart your computer.

Page 84: Hfm install

86 Upgrading to Financial Management 9.2.1

Uninstalling Shared ServicesBefore you uninstall Shared Services, stop all activities and processes tied to Shared Services, including the application server, the database, and any server related to Shared Services. An exception is if you use IBM WebSphere as the Web application server. In this case, leave WebSphere running because it removes files during the uninstall.

When you uninstall Shared Services, you must also manually remove the common components that reside in the Common directory and delete your Shared Services database.

To uninstall Shared Services, from the Control Panel, select Add/Remove Programs, and select the file.

The location and file name depends on the version that you installed.

Installing Financial ManagementIf 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.

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

1 Install and configure Shared Services, and 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.

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

3 Select the installation process language, and click OK.

4 Review the Welcome dialog box and click Next.

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

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

7 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:\).

Page 85: Hfm install

Installing Financial Management 87

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

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

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

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

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

OR

Select to install these components:

Client Install all components for a full client installation.

Application Server Install all files required for the application server.

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

Consultant Utilities Install additional utilities for Financial Management.

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

Page 86: Hfm install

88 Upgrading to Financial Management 9.2.1

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.

13 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 files that were updated, check the install log, installLog.txt, at the root of the directory in which you installed Financial Management.

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

15 Select whether to restart your computer, and click Finish.

Run the configuration utility. See Chapter 7, “Configuring and Setting Up Financial Management”.

Installing Financial Management on the ClientThe Financial Management installation program installs files needed to run Financial Management and common components that are used by multiple Hyperion products.

The Typical installation does not install server components. If you need to install server components, see Chapter 5, “Installing Financial Management Server Components”.

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.

To install Financial Management on the client tier:

1 Install and configure Shared Services, and configure external authentication through Shared Services.

See the Hyperion Shared Services Installation Guide.

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

3 Select the installation process language, and click OK.

4 Review the Welcome dialog box and click Next.

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

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

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

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:\).

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

Page 87: Hfm install

Upgrading Applications from Prior Releases 89

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.

9 From Setup Type, select Typical, and click Next.

10 From Component Selection, select the components to install, and clear components that you do not want to install.

11 For a Typical installation, you can install these components:

Win32 Client Install all components for the Windows 32 client desktop.

ADM Client Install Analytic Data Model (ADM) if you use Financial Management with Financial Reporting, Web Analysis, or Application Builder. ADM is the connectivity component between Hyperion data sources. You can also install ADM later on another machine.

Sample Applications Install sample applications.

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

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

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

15 Run the configuration utility.

See Chapter 7, “Configuring and Setting Up Financial Management”.

Upgrading Applications from Prior Releases All products in release 9.2.1 (Data Integration Management excepted) support upgrades from 4.0.5.2, 9.0.1x and 9.2. In addition, Financial Management supports upgrades for all releases from 3.5.1.

If you are upgrading from Financial Management 9.2.x:

You can install Financial Management 9.2.1 over the existing installation. You must re-run the Hyperion Configuration Utility. The system performs a silent re-registration of products, and might prompt you for a username and password. The silent re-registration updates product information such as roles and version.

For applications that you saved from a previous release, when the first user opens an application, the system performs a silent re-registration that updates the registered application.

Page 88: Hfm install

90 Upgrading to Financial Management 9.2.1

If you want to use applications from prior releases, you must use the Schema Upgrade utility to upgrade the applications. The utility is installed in the Server directory when you install Financial Management, and it runs on the application server.

You must first run the Financial Management Configuration Utility, and then launch the Schema Upgrade utility.

The Schema Upgrade utility requires that Financial Management is configured with Shared Services. The utility converts any database table that does not meet the current release specifications. This accounts for changes in metadata, data types, and other changes that optimize or enhance Financial Management. It also migrates security users from prior releases to Shared Services. This is handled by the migration utility that is executed by the Schema Upgrade utility, which analyzes the current security settings and extracts a security load file used to relocate Financial Management security to Shared Services.

When you run the utility, based on your settings, the Schema Upgrade utility sequentially upgrades one application at a time. If it is determined that security needs to be migrated, the migration utility is launched on the first instance and used for subsequent applications. The migration utility prompts you for your Shared Services URL, the Financial Management project to which you want to migrate, the Web URL used for security administration, and an administrator name and password. It converts the tables and migrates the users from your Financial Management application to Shared Services for all applications.

Using the Schema Upgrade UtilityBefore you use the upgrade utility and connect to the database with the utility, you must complete these tasks:

Shared Services must be installed, configured and running, and you must create a project. Financial Management must be registered in Shared Services, which configures external authentication.

You must configure Financial Management and you must have an available Financial Management Web server. Use the Financial Management Configuration utility to complete the configuration tasks. See “Configuring Application Servers” on page 53 and “Configuring Web Servers” on page 61.

Note that if the all the applications to be upgraded are pre-system 9, then you must complete the Schema Upgrade before you can create or register HFM Clusters using the Financial Management Configuration Utility “Configuring Application Server Clusters” page 58 and “Registering Application Server Clusters” page 59.

Additionally, when using the HFM copy utility to copy a single application from an environment with an older release of Financial Management into the environment running 9.2.1, the schema upgrade utility must be run after the copy is complete to upgrade the newly copied application. When running the schema upgrade utility again, any existing 9.2.1 applications will be rescanned, but no updates will be made.

Page 89: Hfm install

Using the Schema Upgrade Utility 91

Note: The upgrade utility assumes that the decimal character is a period (.). If you use another character, such as a comma (,), you must change the decimal character setting in the RDBMS to a period, and after running the utility, change it back. Web data grids that you created in prior releases with Java applets are supported after you upgrade, however, data grids that you created using HTML in prior releases are not supported or viewable after you run the upgrade utility.

When you use the Schema Upgrade utility, all applications for the current database are upgraded simultaneously, and the upgrading options apply to all applications. You cannot upgrade only one application.

You can choose how to handle errors that occur during the upgrading process. For example, you can set the process to halt when an error occurs so that you can view it immediately, or to ignore errors and continue upgrading, and view the errors later.

You can create an error log to check results after the upgrade. If an error log exists, you can choose to truncate the log on startup to clear the contents, or back up the log.

During the upgrading process, the system stores security load files used in the user migration in your system Temp directory, so you can also review that directory for results. The security filenames are HFMSecurityFile_<application name>_<month-date-year>.sec. It is recommended after completing the upgrading process that you manually extract the security files from each application to save for backup and future reference.

Users are validated during the upgrading process, so users who no longer exist in external security do not load. After upgrading, you can view results in the log file in the system Temp directory. The log file is named HFMSecurityFile_<application name>_<month-date-year>.log.

Note: The utility recognizes the security files based on the application name and month, date, and year. If for any reason the upgrading process fails and you restart it on a different day, you must manually adjust and reload the files.

To upgrade applications:

1 Navigate to the Financial Management installation directory, and locate the Server directory, for example:

C:\Hyperion\FinancialManagement\Server.

2 From the Server directory, double-click the Upgrade utility file, HFM Schema Upgrade.exe.

3 From the SchemaUpgrade window, click Connect.

All applications with the defined database are displayed in the Available Applications section.

4 For Error Handling , select an option:

Halt on Any Error

Ignore Errors and Continue

5 For Log File Name, enter a name for the upgrade error log.

Note: You can save the log file in any directory that you choose.

Page 90: Hfm install

92 Upgrading to Financial Management 9.2.1

6 For Logging Options, select an option:

To clear the log contents, select Truncate Existing Log on Startup.

To save the log, select Backup Existing Log.

7 Click Upgrade.

The system prompts you with a reminder to back up your database and the option to postpone the upgrade so that you can do the backup.

8 From the system warning that all applications will be converted, click Yes to continue.

When the application tables are upgraded, the security tables are extracted as load files and reloaded. This process may take several minutes based on the size of the security files and the number of users, groups, and roles. When the utility reaches the security tables for the first application, if it detects that users need to be migrated, the User Migration dialog box is displayed.

9 From the User Migration box, enter the information to provision the application:

a. In the User Management URL text box, enter the URL that you use for Shared Services, for example, http://<Shared Services server>:58080/interop.

b. In the User Management Project text box, enter the name of the project that you created in Shared Services.

c. In the Financial Management Web Server URL for Security Administration text box, enter the name of your Financial Management Web server.

d. In the Administrator Logon section, enter the domain, username, and password. The user must be an administrator in Shared Services.

Note: After you specify this information the first time, the system uses it to upgrade subsequent applications.

10 When you receive the Processing Complete message, click OK.

11 Optional: To view the error log after upgrading, click View Log.

12 Click Close.

Page 91: Hfm install

Installing Additional Hyperion Products 93

C h a p t e r

10Installing Additional Hyperion

Products

After installing Financial Management and verifying that you can create and connect to applications, you can install Financial Reporting, and the Hyperion Application Link adapter or Data Integration Management adapter.

In This Chapter Installing Financial Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Accessing Financial Reporting Web Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Installing the Hyperion Application Link Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Installing Data Integration Management Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Page 92: Hfm install

94 Installing Additional Hyperion Products

Installing Financial ReportingFinancial Reporting enables you to create highly formatted reports that combine text, grids of data, 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.

If you use Financial Management with Financial Reporting, you must install the Analytic Data Model (ADM) Driver component to enable connectivity between Financial Management and Financial Reporting. You can install ADM during the Custom installation process, or install it later. See “Installing Financial Management” on page 38.

If you use Financial Management and Financial Reporting on different domains, you must set the DCOM authentication on the Financial Management client computer to None to ensure communication between them.

After installing Financial Management, you can install Financial Reporting on the application server.

Note: Financial Reporting can use Apache Web server for the Web server; however, Apache and Microsoft IIS use the same port. If you run Financial Management and Financial Reporting on the same computer, you must use IIS as the Web server.

Accessing Financial Reporting Web ApplicationsYou can launch Financial Reporting from Financial Management and access a Financial Reporting Web application without supplying login information. However, you must first do these tasks:

Ensure that the Financial Management user IDs and passwords match the Financial Reporting user IDs and passwords. For example, if you log on Financial Management using a <Domain>\<UserID> convention such as Hyperion\JSmith, you must create an instance of Hyperion\JSmith ID in Financial Reporting that uses the Financial Management password.

Set the registry key to specify the Financial Reporting Web application server and port. You can specify this information using the Web server setup procedure in the Financial Management Configuration Utility.

If you do not use the Financial Management Configuration Utility to set up the Web server, you must manually specify the Financial Reporting Web application information.

To manually specify the Financial Reporting Web application:

1 Select Start > Run.

2 In the Open box, type regedt32, and click OK.

3 Select HKEY_LOCAL MACHINE.

Page 93: Hfm install

Installing the Hyperion Application Link Adapter 95

4 Double-click SOFTWARE to expand the list.

5 Navigate to Hyperion Solutions > Hyperion Financial Management > Web > HyperionReportsServer.

6 Double-click HyperionReportsServer.

7 Set HyperionReportsServer to the value of the computer name or IP address and the port where the Financial Reporting Web application is running.

Example: Value name: HyperionReportsServerValue data: ReportsRack1:8200

8 Click OK.

Installing the Hyperion Application Link AdapterHyperion Application Link is an application integration product with a graphical user interface that makes it easy to create seamless integration from your source system into Financial Management. You can use Hyperion Application Link to load data values, accounts, entities, and custom dimensions from a flat file or ODBC-compliant database into Financial Management. Hyperion Application Link includes the Hyperion Translation Manager wizard, to map your source data to Financial Management equivalents.

For Hyperion Application Link 9.2, use the 9.2 adapter. For Hyperion Application Link 3.0, use the 3.0.80 adapter.

Updating Financial Management Adapter 3.0.80You install the adapter in the Update Suites or Extensions process. To use the adapter, see the Financial Management Adapter User’s Guide.

If you have an earlier release of the Financial Management Adapter installed, uninstall it before installing this release. After uninstalling, ensure that the HsvHALClasses.jar file is deleted.

To update the Financial Management Adapter 3.0.80:

1 Download the adapter.

2 Select Start > Programs > Vignette Business Integration Studio V6 > Update Adapter Libraries.

3 Select Install or Upgrade Business Integration Studio Adapter Libraries, and click Next.

4 Select Scan for New or Updated Adapter Libraries, click Browse and navigate to the directory in which you stored the adapter file, and click OK.

5 Click Next.

6 Select Financial Management, enter the adapter serial number, and click Next.

7 Click Next, and follow the installation prompts.

Page 94: Hfm install

96 Installing Additional Hyperion Products

Updating Financial Management Adapter 9.2To use the adapter, see the Financial Management Adapter User’s Guide.

If you uninstall a previous version of the adapter before installing this release, ensure that the HsvHALClasses.jar file is deleted.

To update Financial Management Adapter 9.2:

1 Locate and double-click the setup executable file from the adapter zip file: setup_vbis_win32.exe.

Note: This utility may take several minutes to load.

2 From Welcome to Vignette V7 Business Integration Studio, click Next.

3 From Adapter Library Selection, select Hyperion Financial Management Adapter library and do one of these steps:

If the status is displayed as Compatible or Upgrade, click Next.

If the status is displayed as Incompatible, cancel the installation and review the installation log in your <vbis install dir>\vbis\logs directory.

The log file name is vbis_install_<date – timestamp>.log.

4 From Install Preview, verify that the Financial Management adapter library is displayed in the list, and click Next.

5 When Installation Summary is displayed, click Finish.

Installing Data Integration Management AdaptersTo use the Data Integration Management adapter for Financial Management, you must first install and configure Financial Management.

A Hyperion product and the Data Integration Management adapter for that product can be on different computers. For example, you can install Financial Management on one computer and the Data Integration Management adapter for Financial Management on another.

You must have administrative privileges on any computer where you install a Data Integration Management adapter. A Data Integration Management adapter installer provides two options:

Typical - Install all adapter components

Custom - Install the component that you select:

Client Plug-in - Enables you to configure source and target definitions for the Hyperion application in Designer. Client Plug-in should be installed on the same computer as PowerCenter Client.

Repository Server Plug-in - Enables you to register the adapter in a repository.

Server Plug-in - Enables you to execute workflows.

The installer sets environment and system variables:

Page 95: Hfm install

Installing Data Integration Management Adapters 97

HFMCONNECTORPATH is set to Installation Folder\HFM Connector.

PATH is updated with the Installation Folder\HFMConnector\lib folder.

Note: When you install the client and server components of any Data Integration Management adapter on one computer, you must install both components in the same location.

To install a Data Integration Management adapter:

1 From the directory where you downloaded the adapter installer, click setupwin32Platform.exe.

2 On the adapter installer Welcome screen, click Next.

3 Select a country for the installation, and click Next.

4 On the license agreement screen, select I AGREE, and click Next.

Note: You must select I AGREE to continue with the installation.

5 Click Next to accept the Hyperion Home directory.

6 Select a setup type, and click Next.

7 If you selected the Custom setup option in the preceding step, select components to install, and click Next.

8 Verify the installation summary, and click Next.

Tip: You can click Back to change installation choices.

Installing Adapters in Silent ModeWhen you install a Data Integration Management adapter in silent mode, the installer retrieves the installation properties that are saved in a response file instead of displaying screens where you enter these properties. Silent mode is often used for performing installations remotely. You can create the response file from a template before you perform an installation, or you can create the file during an installation for use in subsequent silent-mode installations.

To install an adapter in silent mode, run this command:

InstallerFile -silent -options Response File

where InstallerFile is a platform-specific installation program (such as setupwin32.exe for an installation on a Windows platform) and ResponseFile is the property file containing the parameters required for the installation.

Installing Adapters in Console ModeWhen you run the installer for an adapter in console mode, you select input from a series of menus that are displayed.

To install an adapter in console mode, run this command:

Page 96: Hfm install

98 Installing Additional Hyperion Products

InstallerFile -console

where InstallerFile is a platform-specific installation program (such as setupSolaris.bin for a Solaris platform).

Configuring AdaptersAfter installing Data Integration Management adapters, you must configure them on the computers hosting the PowerCenter Server, Client and Repository Server components of Data Integration Management.

Adapter configuration tasks are described in these topics:

“Registering Adapters with a Repository” on page 98

“Configuring Hyperion Application Connections” on page 99

“Configuring JVM Options” on page 100

You can perform these tasks on Windows computers where PowerCenter Client is installed.

Note: Adapter configuration is not done with the Hyperion Configuration Utility.

Registering Adapters with a RepositoryIf you install the Repository Server Plug-in or Server Plug-in component of a Data Integration Management adapter, you must register the adapter with the repository. This registration is not required if you install only the Client Plug-in.

To register a Data Integration Management adapter with a repository:

1 Ensure that Data Integration Management Repository Server is running:

a. From the Windows Control Panel, select Administrative Tools.

b. Select Services.

c. In the Services window, check the status of Hyperion S9 Data Integration Management Repository Server.

d. Unless the status is “Started”, click Start (in the upper left of the window).

Note: Keep the Services window open for the next step.

2 Stop Data Integration Management Server, if it is running:

a. In the Services window, check the status of Hyperion S9 Data Integration Management Server.

b. If the status is “Started”, click Stop (in the upper left of the window).

3 Connect to the Repository Server host computer:

Page 97: Hfm install

Installing Data Integration Management Adapters 99

a. Select Start > Programs > Hyperion System 9 > Data Integration Management > Informatica PowerCenter 7.1.4 - Client > Repository Server Administration Console.

b. In Repository Server Administration Console, right-click the name of the Repository Server host computer, and select Connect.

c. Enter your password for the host computer, and click OK.

4 Under the Repository Server host computer name, click Available packages.

5 Right-click HFM.xml and select Register.

6 Enter the repository administrator user name and password, and click OK.

Note: By default, both the user name and the password are Administrator if you are using Informatica native authentication. If you are using Shared Services authentication, the default user name and password are admin and password, respectively.

7 When a message that the registration succeeded is displayed, click OK.

8 Repeat steps 5 through 7 for each adapter to be registered.

Note: For more information, see “Registering and Unregistering Repository Plug-ins” in the Informatica PowerCenter Repository Guide.

Configuring Hyperion Application ConnectionsAfter you configure an adapter, you must configure an application connection in Workflow Manager before you can extract data from sources or write data into targets. When configuring application connections, you specify attributes that Data Integration Management Server uses to connect to a database during a Data Integration Management session. The application connections that you define in Workflow Manager are saved in Data Integration Management Repository.

To configure application connections:

1 Ensure that Data Integration Management Repository Server is running:

a. From the Control Panel, select Administrative Tools.

b. Select Servers.

c. In the Services window, check the status of Hyperion S9 Data Integration Management Repository Server.

d. Unless the status is “Started”, click Start (in the upper left of the window).

2 Start the repository:

a. Select Start > Programs > Hyperion System 9 > Data Integration Management > Informatica PowerCenter 7.1.4 - Client > Repository Server Administration Console.

b. In Repository Server Administration Console, right-click the name of the Repository Server host computer and select Connect.

Page 98: Hfm install

100 Installing Additional Hyperion Products

c. Enter your password for the host computer, and click OK.

d. In the Repositories directory, double-click the repository name.

e. Click Start (on the left).

3 Select Start > Programs > Hyperion System 9 > Data Integration Management > Informatica PowerCenter 7.1.4 - Client > Workflow Manager.

4 In Workflow Manager, connect to the repository:

a. In the Repository Navigator panel, double-click the repository name.

b. Enter the repository administrator’s user name and password, and click Connect.

5 Select Connections > Application.

6 Click New.

7 Select the connection for the adapter that you are configuring (Hyperion Financial Management Connection), and click OK.

8 Enter the requested information, and click OK:

The information requested depends on the Hyperion application. It can include these items:

Name - A name for the connection

User Name - Your user name for the Hyperion application; for example, your user name for Financial Management.

Password - Your password for the repository, for example, your password for Financial Management.

URL - The Hyperion product application URL that you want to use

Host or ServerHost - The name of the Hyperion product server host computer, for example, the name of the Financial Management server host computer.

Port - The port number used by the application

Cluster - The name of the registered cluster where the application runs

Application Connection Browser lists the new application connection.

Tip: You can edit or delete an application connection by selecting it in the list in Application Connection Browser and clicking Edit or Delete.

Configuring JVM Options

To configure JVM options:

1 Start Informatica Server Setup by selecting Start > Programs > Hyperion System 9 > Data Integration Management > Informatica PowerCenter 7.1.4 - Server > Informatica Server Setup.

2 With Configure Informatica Service selected, click Continue.

3 Select the JVM Options tab.

Page 99: Hfm install

Installing Data Integration Management Adapters 101

4 In VM Location, enter the fully qualified path to the jvm.dll file in your JAVA_HOME directory, and click OK.

Uninstalling Adapters

To uninstall a Data Integration Management adapter:

1 Start the adapter uninstaller (uninstall.exe).

2 On the uninstaller Welcome screen, click Next.

3 Ensure that all PowerCenter Client applications are selected, and click Next.

4 On the uninstallation summary screen, click Next.

5 When the summary screen says that the uninstallation has succeeded, click Finish.

6 Optional: Remove the adapter from a repository:

a. Open Data Integration Management Repository Server Administration Console by selecting Start > Programs > Hyperion System 9 > Data Integration Management > Informatica PowerCenter 7.1.4 - Client > Repository Server Administration Console.

b. Select the repository in which the adapter is registered.

c. Stop the repository if it is running.

d. Click Repository > Registered packages and select HFM.xml.

e. Click Unregister.

f. In Remove Repository plug-in, enter the repository user name and password, and click OK.

The Output window displays the status of the plug-in uninstallation.

Note: Repeat step 6 to remove the adapter from additional repositories.

Uninstalling Adapters in Silent ModeWhen you uninstall a Data Integration Management adapter in silent mode, the installer retrieves the uninstallation options that are saved in a response file instead of displaying screens where you enter these properties. Silent mode is often used for performing uninstallations remotely. You can create the response file from a template before you perform an uninstallation, or you can create the file during an uninstallation for use in subsequent silent-mode uninstallations.

To uninstall an adapter in silent mode, run this command:

UninstallerFile -silent -options Response File

The uninstaller file is in the Uninstall subdirectory of the adapter installation directory.

Page 100: Hfm install

102 Installing Additional Hyperion Products

Uninstalling Adapters in Console ModeWhen you run the uninstaller for an adapter in console mode, you select input from a series of menus that are displayed.

To uninstall and adapter in console mode, run this command:

UninstallerFile -console

The uninstaller file is in the Uninstall subdirectory of the adapter installation directory.

Page 101: Hfm install

Troubleshooting 103

A P P E N D I X

ATroubleshooting

This appendix describes troubleshooting procedures for the application server and for Financial Management applications.

In addition, the installation log provides information about errors that occurred during installation. The log is named installLog.txt and is installed at the root of the directory in which you installed Financial Management.

In This Chapter Troubleshooting Application Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Troubleshooting Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Troubleshooting Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Page 102: Hfm install

104 Troubleshooting

Troubleshooting Application Server Configuration Table 10 provides solutions to problems that you may experience when configuring the application server for Financial Management.

Table 10 Installation Troubleshooting

Error Message or Problem Solution

You cannot log on Financial Management. Do not use a single quotation mark ( ’ ) in the username, because Financial Management cannot authenticate it.

You cannot connect to the SQL Server. The file is not a valid compound file.

Configure the UDL file. See “Configuring the Data Link for Microsoft SQL Server” on page 30.

Windows 2000: When you create a data link (UDL) file, the Microsoft Data Link option is not displayed when you right-click and select New from the menu.

Create a text document, rename it with a .UDL extension, and create the data link. See “Creating Data Link (UDL) Files” on page 28.

For Microsoft SQL Server: Test connection failed because of an error in initializing provider. Client unable to establish connection.

A problem exists with the Microsoft SQL Server connection and the UDL file. See “Verifying Data Link Connection Settings” on page 106.

You cannot connect to the SQL Server. 1) The system may be using the Microsoft SQL Server default setting to connect to the database using named pipes instead of TCP/IP. See “Establishing the SQL Server Connection Using TCP/IP” on page 105.

2) Windows authentication may have been used instead of Microsoft SQL Server authentication. Hyperion recommends using SQL Server authentication. See “Verifying Microsoft SQL Server Authentication Settings” on page 106.

You are unable to open the selected application when you click Open, Create, or Delete.

This problem is specific to application servers with the French locale and can occur with a Win32 client connected to an application server residing on a separate computer, or a Web client connected to a Web server residing on a machine other than the application server.

1. Create this registry key on the Financial Management server where the problem occurs:

HKEY_LOCAL_MACHINE\Software\Microsoft\Cryptography\defaults\CheckInfo.

2. Create a REG_DWORD value named Mask and assign it a value of 0xFF.

When the computer is restarted, Financial Management fails installation.

This problem may be the Remote Procedure Call service in Windows.

1. Select Start > Programs > Administrative Tools > Services. or for Windows 2003, select Start > Settings > Control Panel > Administrative Tools > Services.

2. Check the Remote Procedure Call (RPC) Locator, which is set to Manual by default. Select the service, click Start, and restart the computer.

Page 103: Hfm install

Troubleshooting Application Server Configuration 105

The following troubleshooting procedures describe how to use TCIP/IP to establish the connection and how to troubleshoot connection issues.

Establishing the SQL Server Connection Using TCP/IP

To establish the SQL Server connection using TCP/IP:

1 Select Start > Settings > Control Panel.

2 Select Administrative Tools, and double-click Data Sources (ODBC).

3 Click Add.

4 In the list of drivers, highlight SQL Server, and click Finish.

5 Enter a data source name, description, the data server name for the SQL Server to which to connect, and click Next.

6 Select this authentication option: With SQL Server authentication using a login ID and password entered by the user.

7 Click Client Configuration, select TCP/IP (if not selected), and click OK.

Connection fails for Financial Management. If the DCOM launching user is set to a local machine account, domain users cannot log on to some modules. For example, if a user logs on to a workstation with a user ID on Domain A, and logs on to Financial Management with a user ID on Domain B (or any domain that Domain B can access), when the user attempts to connect to a Financial Management server on Domain B, the connection might fail. To resolve the problem, do one of these procedures:

Set up a one-way trust relationship from Domain B (Financial Management Server) to Domain A (Financial Management Client). This method is recommended as the best workaround.

Set the DCOM Default Authentication Level to None on the client. However, note that by turning off the DCOM authentication on the client, DCOM authentication is turned off for all the DCOM applications on the client.

You are unable to register a server cluster. This problem might be due to registry access requirements. If you run the configuration utility from an admin account, the configuration utility creates the HKeyLocalMachine/Software/Hyperion Solutions registry key so that you can register server clusters. If you do not run the configuration utility from an admin account, you might encounter problems when trying to register servers. In this case, in the registry, you should manually assign Read/Write access rights to HKeyLocalMachine/Software for the user who is registering the servers.

Table 10 Installation Troubleshooting (Continued)

Error Message or Problem Solution

Page 104: Hfm install

106 Troubleshooting

8 For Connect to SQL Server , enter the login ID and password, and click Next.

9 Change the default database to the Financial Management database.

10 Click Next, and click Finish.

11 Click Test Data Source.

12 When you receive the success message, click OK, and click OK to close the dialog box.

13 Click OK to close the ODBC Administrator dialog box.

14 Create and set the data link (.udl).

See “Creating Data Link (UDL) Files” on page 28.

Verifying Data Link Connection Settings

To verify data link connection settings:

1 In Data Link Properties, select the Connection tab.

2 Ensure that Use a specific user name and password is selected.

Verifying Microsoft SQL Server Authentication Settings

To verify the Microsoft SQL Server authentication setting:

1 Select Start > Programs > Microsoft SQL Server > Enterprise Manager.

2 Expand the list of Microsoft SQL Servers.

3 Right-click the database server name, and select Properties.

4 Select the Security tab.

5 Ensure that this Authentication option is selected: SQL Server and Windows.

6 Click OK.

Troubleshooting ApplicationsTable 11 provides solutions to problems that you may experience when creating or opening applications.

Page 105: Hfm install

Troubleshooting Shared Services 107

Troubleshooting Shared ServicesIf you experience problems installing or running Shared Services, see the Hyperion Shared Services Installation Guide, which contains information about Shared Services applicable to all Hyperion products.

Table 11 Application Troubleshooting

Error Message or Problem Solution

Unable to create application Ensure that the user is assigned to an administrator group.

Ensure that the user has these security rights: Act as Part of Operating System, Log on as Batch Job, Bypass Traverse Checking.

See “Configuring Application Servers” on page 53.

Ensure that Shared Services is properly configured. See the Shared Services Installation Guide and “Verifying Startup Dependencies” on page 67.

Error creating the application Check these items:

DCOM permissions are set.

A .UDL file exists.

See “Configuring Application Servers” on page 53.

Ensure that Shared Services is properly configured.See the Shared Services Installation Guide and “Verifying Startup Dependencies” on page 67.

Unable to open application Re-enter your user name and password.

Unable to connect to server Unregister and re-register the server.

Page 106: Hfm install

108 Troubleshooting

Page 107: Hfm install

Index A 109

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Index

AAdministrators group

in configuration utility, 55

Analytic Data Model (ADM) driver installation, 40

Application Creator group, 55

application server

configuring, 53

installing Financial Management, 37

multiple server support, 56

system requirements, 20

verifying communication to, 46

applications

making backup copies, 82

opening, 72

sample files for, 70

authentication

proxy, 65

Web server, 65

Bbacking up applications, 82

backup procedures, 83

Cclient

installing Financial Management, 44, 88

system requirements, 20

verifying communication to, 46

component selection, 37

Configuration Utility

database user rights, 49

prerequisites, 49

configuration utility

for application server, 53

for Web servers, 61

connection pooling, 32

conversion utility for applications, 89

Ddata backup procedures, 83

data link

creating, 28

encrypting, 31

setting up for IBM DB2, 30

setting up for Oracle, 29

setting up for SQL Server, 30

data source for Extended Analytics, 57

data tablespace information, 55

database connection pooling, 32

database requirements, 22

EExtended Analytics data source, 57

FFile Transfer folder in configuration utility, 61

Financial Management

installing on application server, 37

installing on client, 44, 88

installing Web Server components only, 44, 88

Ggroups

in configuration utility, 55

Page 108: Hfm install

110 Index H

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

HHFM Software Development ToolKit, 41

Hyperion Application Link

overview, 11

Hyperion Configuration Utility

log file, 52

reconfiguration, 52

Shared Services deregistration, 52

Shared Services registration, 51

troubleshooting, 52

upgrades and, 50

Hyperion Home directory, 36

Iindex tablespace information, 55

install log, 103

Internet Information Services (IIS), 36

Lloading

sample data, 74

sample member lists, 74

sample metadata, 73

sample rules, 74

sample security, 73

MMicrosoft Data Access Component

installation, 39, 88

verifying version, 84

Microsoft Internet Information Services (IIS)

installing, 36

verifying installation, 36

multiple server support, 56

Pproxy authentication, 65

Rregistering server clusters, 59

registry keys

for servers in French locale, 104

Related Content tab in configuration utility, 64

Remote Procedure Call service, 104

Ssample files

loading into applications, 73

viewing sample data, 75

Schema Upgrade utility, 90

server clusters

registering, 59

unregistering, 59

Server Working folder, 55

Shared Services

overview, 10

starting, 67

verifying startup, 68

silent install, 41

Smart View for Office

overview, 11

Software Development ToolKit (SDK), 41

specifying database tablespaces, 56

startup dependencies, 67

system requirements

application server, 20

client, 20

Web server, 20

Ttroubleshooting, 104

UUDL file

creating, 28

encrypting, 31

setting up for IBM DB2, 30

setting up for Oracle, 29

setting up for SQL Server, 30

upgrading applications, 90

upgrading from prior releases, 82

WWeb authentication, 65

Web Security Agent support, 62

Page 109: Hfm install

Index W 111

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Web server

installing components, 40

system requirements, 20

Page 110: Hfm install

112 Index W