Hsys9 Install Start Here

Hyperion

Installation Start Here

RELEASE 9.3.1

Updated: November 2010

Hyperion Installation Start Here, 9.3.1

Copyright © 2007, 2010, 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 anddisclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement orallowed 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 decompilationof this software, unless required by law for interoperability, is prohibited. The information contained herein is subject tochange 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 customersare "commercial computer software" or "commercial technical data" pursuant to the applicable Federal AcquisitionRegulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, andadaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, tothe extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, CommercialComputer 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 orintended for use in any inherently dangerous applications, including applications which may create a risk of personalinjury. 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 affiliatesdisclaim any liability for any damages caused by use of this software in dangerous applications.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of theirrespective owners.

This software and documentation may provide access to or information on content, products, and services from thirdparties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind withrespect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for anyloss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Contents

Chapter 1. Hyperion Product Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter 2. Upgrading Hyperion Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 3. System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

About System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Foundation Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Shared Services Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Shared Services Server Disk Space and RAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

User Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Client Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Client OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Required Hyperion Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Assistive Technologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Screen Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Runtime Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Disk Space and RAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Product-Specific Client Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Web Browser Client Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Other Required Third-Party Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Essbase - System 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Server Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Data Source Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Reporting and Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26



Financial Performance Management Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33


Data Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38



Contents iii

Chapter 4. Release Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

How to Read the Tables in This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Shared Services Release Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Essbase - System 9 Release Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Reporting and Analysis Release Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Financial Performance Management Applications Release Compatibility . . . . . . . . . . . . . 49

Data Management Release Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Chapter 5. Hyperion License Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Ensuring License Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Activating and Deactivating Product Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

About registry.properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Auditing Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Retrieving License Keys for Data Integration Management . . . . . . . . . . . . . . . . . . . . . . . 65

Chapter 6. Planning Hyperion Product Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Planning Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Preparing Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

General Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

IBM DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Preparing Java Application Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

General Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Apache Tomcat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

BEA WebLogic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

IBM WebSphere . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Oracle 10g . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Chapter 7. Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

About Default Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Shared Services Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Changing the OpenLDAP Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Essbase - System 9 Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Essbase Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Administration Services Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Provider Services Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Smart Search Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Reporting and Analysis Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Foundation Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Financial Reporting Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

iv Contents

Interactive Reporting Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Web Analysis Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Workspace Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Application Builder J2EE Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Application Builder.NET Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Financial Performance Management Applications Ports . . . . . . . . . . . . . . . . . . . . . . . . . 84

Financial Management Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Performance Scorecard Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Planning Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Strategic Finance Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Performance Management Architect Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Data Management Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Data Integration Management Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Translation Manager Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

FDM Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Data Relationship Management Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Chapter 8. Changing Repository Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

About Repository Password Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Changing the Shared Services Repository Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Changing the Administration Services Repository Password . . . . . . . . . . . . . . . . . . . . . . 94

Changing Reporting and Analysis Repository Passwords . . . . . . . . . . . . . . . . . . . . . . . . . 94

Changing the Workspace Repository Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Changing the Financial Reporting Repository Password . . . . . . . . . . . . . . . . . . . . . . 95

Changing the Web Analysis Repository Password . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Changing Financial Performance Management Applications Repository Passwords . . . . . . 96

Changing the Planning Repository Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Changing the Financial Management Repository Password . . . . . . . . . . . . . . . . . . . . 97

Changing the Performance Management Architect Repository Password . . . . . . . . . . 98

Changing the Performance Scorecard Repository Password . . . . . . . . . . . . . . . . . . . . 99

Changing Data Management Repository Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Changing the FDM Repository Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Changing the Data Relationship Management Repository Password . . . . . . . . . . . . . 100

Changing the Translation Manager Repository Password . . . . . . . . . . . . . . . . . . . . . 101

Chapter 9. Configuration Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

About Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Product Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Shared Services Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Contents v

Relational Database Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Application Server Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Essbase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Reporting and Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Financial Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Interactive Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

SQR Production Reporting Engine for Interactive Reporting (Optional) . . . . . . . . . . 108

Performance Scorecard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Performance Scorecard Alerter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Strategic Finance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Financial Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Performance Management Architect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Chapter 10. Installation Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

About Installation Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

General Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Shared Services Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Essbase - System 9 Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Planning Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Financial Management Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Reporting and Analysis Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Performance Scorecard Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Strategic Finance Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Data Relationship Management Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

FDM Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Data Integration Management Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

User Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Appendix A. Startup Dependencies and Default URLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Summary List of Services and Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Services and Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

1. Shared Services OpenLDAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

2. Shared Services Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

3. Reporting and Analysis Core Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

4. Performance Management Architect Services . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

5. Essbase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

6. Administration Services Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

7. Integration Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

vi Contents

8. Provider Services Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

9. Reporting and Analysis Services/Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

10. Application Server Services/Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

11. Remaining Product Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Default URLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Appendix B. Deploying Hyperion 9.3.1 Products with Components from Previous Releases . . . . . . . . . . . . . . 139

Upgrading to a Single-Release Hyperion Product Environment . . . . . . . . . . . . . . . . . . . 139

Upgrading to a Mixed-Release Hyperion Product Environment . . . . . . . . . . . . . . . . . . . 140

Configuring Products in a Mixed-Release Environment . . . . . . . . . . . . . . . . . . . . . 142

Navigating in Workspace in a Mixed-Release Environment . . . . . . . . . . . . . . . . . . . 143

Sample HTML Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Contents vii

viii Contents

1Hyperion Product Components

Check on Oracle® Technology Network to see if an updated version of this guide is available.

Use this document to help plan your Hyperion product installation and configuration. Afterreading this document, use it in conjunction with the product installation guides to install,configure, and manually deploy products. For large, complex deployments, also see the HyperionSystem 9 BI+ Performance whitepaper, available on the Oracle® Technology Network.

Primary components of Hyperion products:

l Oracle's Hyperion® Foundation Services

l Oracle's Hyperion® Essbase - System 9

l Oracle's Hyperion® Reporting and Analysis – System 9

l Oracle's Hyperion® Financial Performance Management Applications

l Data Management

Table 1 Hyperion Product Components

Hyperion Product Component Products Associated with Component

Foundation Services Oracle's Hyperion® Shared Services

Oracle's Hyperion® Smart View for Office

Essbase - System 9 Oracle's Hyperion® Essbase® – System 9

Oracle's Essbase® Administration Services

Oracle's Essbase® Integration Services

Oracle's Hyperion® Provider Services

Oracle's Hyperion® Smart Search

Reporting and Analysis Oracle's Hyperion® Interactive Reporting – System 9

Oracle's Hyperion® Financial Reporting – System 9

Oracle's Hyperion® SQR® Production Reporting – System 9

Oracle's Hyperion® Web Analysis – System 9

9

Hyperion Product Component Products Associated with Component

Financial Performance Management Applications Oracle's Hyperion® Planning – System 9

Oracle's Hyperion® Financial Management – System 9

Oracle's Hyperion® Performance Scorecard – System 9

Oracle's Hyperion® Strategic Finance

Data Management Oracle's Hyperion® Data Integration Management

Oracle's Hyperion® Translation Manager

Oracle's Hyperion® Financial Data Quality Management

Oracle's Hyperion® Data Relationship Management and Oracle's Hyperion® DataRelationship Management Web Publishing

Note: Oracle's Hyperion® Workspace is the Web client for Reporting and Analysis, Planning,and Financial Management and is part of the Reporting and Analysis installation. Oracle'sEnterprise Performance Management Architect is part of the Financial Management andPlanning installations.

10 Hyperion Product Components

2Upgrading Hyperion Products

If you are upgrading from a previous release of Hyperion products, note the following supportedupgrade paths:

l 9.2.0.3 to 9.3.1

Note: Upgrading from 9.2 releases prior to 9.2.0.3 will be supported in an upcoming servicepack.

l 9.3.0.x to 9.3.1

If you are using a release prior to 9.2.0.3, you must first upgrade to one of the versions notedabove, and then upgrade to 9.3.1.

Check the product readmes to find out if additional upgrade paths are supported for a particularproduct.

See the product installation guides for the products you are using for upgrade procedures.

11

12 Upgrading Hyperion Products

3System Requirements

In This Chapter

About System Requirements... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Foundation Services ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

Client Requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

Essbase - System 9... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

Reporting and Analysis .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26

Financial Performance Management Applications ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33

Data Management .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38

About System RequirementsThis chapter describes Shared Services, Client, and product-specific system requirements forHyperion products.

The Hyperion product-specific system requirements are grouped into five categories:

l Foundation Services:

m Shared Services

m User Directories

l Essbase - System 9:

m Essbase

m Administration Services

m Integration Services

m Provider Services

l Reporting and Analysis:

m Financial Reporting

m Interactive Reporting

m SQR Production Reporting

m Web Analysis

m Workspace

l Financial Performance Management Applications:

About System Requirements 13

m Performance Management Architect

m Financial Management

m Performance Scorecard

m Planning

m Strategic Finance

l Data Management:

m Data Integration Management

m FDM

m Data Relationship Management

m Translation Manager

For each product section, additional requirements are described in the Server Requirementssections; for example: OS/Processor, disk space and RAM, and third-party softwarerequirements.

Disk space and RAM requirements are approximate and do not include additional possiblerequirements on the machine, such as extra space needed for a VMware image. The installationprogram calculates the required disk space, based on your installation choices. Disk spaceestimates include documentation files (if applicable) and Hyperion common components.Documentation is installed automatically with some products.

The requirements described in this chapter are for a representative deployment of up to 150total users (30 to 40 concurrent users) for one installation of a Hyperion product. For larger andmore complex deployments—a larger number of users, multiple installations of one product,and installations of multiple products—Hyperion highly recommends that you contactHyperion Consulting Services to determine the appropriate number of servers for yourenvironment.

For information on prerequisites, see Chapter 6, “Planning Hyperion Product Installations.”

For information on current and backward compatibility with other Hyperion products, seeChapter 4, “Release Compatibility.”

Before installing Hyperion products, verify that all system requirements and prerequisites aremet.

Note: Hyperion acknowledges and supports the backward compatibility assertions made bythird-party vendors. Therefore, where vendors assert backward compatibility, subsequentmaintenance releases and service packs may be used. If an incompatibility is identified,Hyperion will specify a patch release on which the product should be deployed (andremove the incompatible version from the supported matrix) or provide a maintenancerelease or service fix to the Hyperion product code.

14 System Requirements

Foundation Servicesl “Shared Services Requirements” on page 15

l “Shared Services Server Disk Space and RAM” on page 15

l “User Directories” on page 15

Shared Services RequirementsShared Services is considered a component of other Hyperion products. In general, SharedServices supports the same platform as the products it is used with; therefore, the systemrequirements for the Shared Services server are not called out specifically. Shared Services isincluded in “Client Requirements” on page 16. You can assume that Shared Services supportsthe same software that is listed in each product-specific section of this chapter, unless otherwisenoted. Disk space and RAM for Shared Services server is listed below.

Shared Services Server Disk Space and RAM

Item Requirement

Disk Space 400 MB1

RAM 1.5 GB

1This number is for the base Shared Services installation. More disk space is required based on OpenLDAP (Native Directory) usage forprovisioning, depending on how often you back up OpenLDAP.

User DirectoriesA user directory is required for external authentication through Shared Services for all productsexcept Data Relationship Management (optional feature for that product).

User Directories Notes

l IBM Tivoli Directory Server 5.2

l Lightweight Directory Access Protocol (LDAP)

m Sun ONE 5.2 SP4

m Novell eDirectory 8.8

m IBM Directory Server 5.1

m Domino LDAP 6.0

l Microsoft Active Directory 2008



l Microsoft NTLM1

l OpenLDAP 2.3.37

Foundation Services 15

User Directories Notes

l Netegrity SiteMinder 6 Not supported by FDM

Oracle Identity Management (OIM) 10.1.4.0.1, including these components:

l Oracle Internet Directory 10.1.4.0.1

l Oracle Virtual Directory 10.1.4.0.1

SAP Directory

l SAP R/3 Enterprise 5.0

Database providers:

l IBM DB2 9.1

l IBM DB2 8.2

l Microsoft SQL Server 2005 SP1

l Microsoft SQL Server 2000 SP3a

l Oracle 11g2

l Oracle 10g Release 2 (10.2.0.2)

l Oracle 10g (10.1.0.5)

l Oracle 9i (9.2.0.5)

1Shared Services running on UNIX requires Oracle's Hyperion® Remote Authentication Module™ for UNIX authentication.2Oracle 11g requires Oracle Hyperion Configuration Utility Service Fix 9.3.1.0.01.

Client RequirementsHyperion client products have the following system requirements:

l General Requirements

m “Client OS” on page 17

m “Processor” on page 17

m “Required Hyperion Software” on page 17

m “Assistive Technologies” on page 18

m “Screen Resolution” on page 18

m “Runtime Clients” on page 18

m “Disk Space and RAM” on page 19

m “Product-Specific Client Requirements” on page 20

l Web Browser Client Requirements

m “Web Browsers” on page 20

m “Web Browser Plug-in” on page 21

m “Java Runtime Environment” on page 21

l Other Third Party Requirements


m “Other Required Third-Party Software” on page 21

Client OS

Operating System Notes

l Windows Vista

l Windows XP Professional SP2

l Windows 2003 SP1

l Windows 2000 Professional SP4*

l Windows 2000 Server SP4*

*Windows 2000 Server is supported for SQR Production Reporting only.All other Reporting and Analysis modules support Windows 2000Professional.

l Oracle Enterprise Linux 412

Red Hat Linux3:

l Red Hat Linux AS 4 Update 2 with glibc-2.3.4-2.13 or later

l Red Hat Linux EL 4

1For supporting browser-based clients only. For Interactive Reporting, only the HTML client is supported; the plug-in client is not supported.2Reporting and Analysis supports only the x86 processor.3For supporting browser-based clients only. For Interactive Reporting, only the HTML client is supported; the plug-in client is not supported.

Processor

Processor (Windows) Notes

Pentium 4, 1.6 GHz The minimum required for allproducts except for the productslisted below.

One of the following:

l 2 GHz (light use-Defined as fewer than 50 users connecting to the server to check entities in andout or to run server-based consolidation for structures that contain fewer than 15 entities.)

l 3.2 GHz (heavy use-Defined as 50 or more users connecting to the server to check entities in andout or to run server-based consolidation for structures that contain more than 15 entities.)

Applies only to StrategicFinance

Pentium 4.8 GHz minimum Applies only to TranslationManager

2 GHz minimum Applies only to DataRelationship Management

Required Hyperion SoftwareIf you are using Smart View to access Essbase as a data source, Provider Services is required.

Client Requirements 17

Assistive TechnologiesAssistive Technologies apply only to Windows operating systems and Microsoft InternetExplorer.

Not supported for:

l Reporting and Analysis

l Oracle's Hyperion® Shared Services User Management Console

l Strategic Finance

Assistive Technologies Supported Versions

Screen readerl JAWS 7

l JAWS 6.2

l Window Eyes 5.5

Screen magnifierl MAGic 9.3

l MAGic 9.0

Screen ResolutionHyperion products are optimized for a minimum screen resolution of 1024 x 768.

Runtime ClientsSome Hyperion clients require the runtime clients of other Hyperion or third-party products.Hyperion runtime client and server versions must match.

For information on Hyperion product compatibility, see Chapter 4, “Release Compatibility.”

Clients Runtime Client

l Financial Reporting

l Interactive Reporting

l SQR ProductionReporting

l Web Analysis

l Essbase—The Essbase runtime client is installed automatically.

l Microsoft SQL Server 2000 SP3a Analysis Services

l Microsoft SQL Server 2005 SP1 Analysis Services


l Web Analysis

l Financial Management—The version of the Financial Management ADM driver and the version of FinancialManagement that is used for Financial Reporting and Web Analysis must match.

l Planning—The Planning runtime client must be installed on the Financial Reporting machine and is acomponent named Planning ADM Driver in the Planning installer.


Clients Runtime Client

Web Analysisl Java Plug-in: 1.5.0_09 and 1.4.2_12

JRE is downloaded to the client computer when a user logs on to Oracle's Hyperion® Web Analysis Studio.The WebAnalysis.properties file contains settings for the correct version of JRE. See the HyperionReporting and Analysis – System 9 Installation Guide.

Planning Essbase—The Essbase runtime client is installed automatically.

Disk Space and RAMThis section does not apply to Web browser clients.

RAM requirements are 512 MB minimum, 1 GB recommended.

Product Grouping Component Disk Space Notes

Oracle's Hyperion® FoundationServices

Smart View 45 MB, 50 MB for Smart View with Oracle'sHyperion® Essbase® Visual Explorer

Essbase - System 9 Essbase Runtime Client 150 MB

UNIX Essbase Runtime Client 150 MB

Essbase Administration ServicesConsole

150 MB

Essbase Integration Services Console 46 MB

Reporting and Analysis Financial Reporting 200 MB

Interactive Reporting 500 MB

SQR Production Reporting 200 MB

Web Analysis 2 GB

Financial Performance ManagementApplications

Performance Management Architect 50 MB

Financial Management 50 MB

Performance Scorecard 250 MB

Strategic Finance 210 MB

Data Integration Management:

Data Management: PowerCenter Client 200 MB

FDM:

Workbench Client 200 MB

Data Relationship Management1 20 MB


Product Grouping Component Disk Space Notes

Translation Manager 100 MB

1If users pre-load applications or if multiple applications open simultaneously, more RAM is recommended.

Product-Specific Client Requirements

Financial Reporting and Web AnalysisTo perform chart generation in UNIX, Financial Reporting and Web Analysis UI services requireaccess to a graphics display device, either real or virtual. Hyperion recommends that an X virtualframe buffer (Xvfb) be used instead of a hardware graphics display device (because Xvfbperforms all operations in memory and does not require that a screen or input device be attachedto the computer). See the Hyperion Reporting and Analysis – System 9 Installation Guide forUNIX.

Web Browser Client Requirements

Web BrowsersWeb browsers are required for:

l Shared Services

l Workspace

l Administration Services

l Reporting and Analysis

l Financial Management

l Performance Scorecard

l Planning

l FDM

l

Supported Web Browsers Notes

l Microsoft Internet Explorer 7.0

l Microsoft Internet Explorer 6.0

l Firefox 2.0.0.3

l Firefox 1.5.0.3

FDM does not support Firefox.

Set your browser to enable JavaScript and cookies. Storing cookies on your computer isrecommended; at a minimum, allow per-session (not stored) cookies. If a Web site is a trustedsite, enable SSL (HTTPS).


Web Browser Plug-inPlanning does not require a Web browser plug-in.

Platform Supported Versions

32-bit JRE 1.5.0 Update 11

64-bit JRE 1.4.2 Update 13

Java Runtime EnvironmentA JRE is required for all products except Strategic Finance and is automatically installed.

Platform Supported Windows Versions Supported UNIX Versions Notes

32-bit JRE 1.5.0 Update 11l AIX:

5.0.0.75 1.5.0 SR4 pap32dev-20070201

l Linux and Solaris: JRE 1.5.0 Update 11

l HP-UX: 1.5.0_06

64-bit12 JRE 1.4.2 Update 13l AIX:

5.0.0.75 pap64dev-20070201

l HP-UX: 1.5.0_06

l Solaris: JRE 1.5.0 Update 11

1To run 64-bit Essbase on 64-bit operating systems, 64-bit JVM is required. JVM is required for triggers, data mining, and custom-definedfunctions that are used in calculation scripts.2Planning supports 64–bit JRE for HP-UX and Windows 2003 64–bit only.

Other Required Third-Party Software

Supported Software Notes

Adobe Acrobat Reader 6.0 or later

DCOM enabled on the client computer Required only for Financial Management when running theFinancial Management Win32 client, or when running theFinancial Reporting client against a Financial Managementapplication.

l One of the following:

m Microsoft Office 2007


m Microsoft Office XP (2002)


l A version of Microsoft Excel is required to use Smart Viewwith:

m Reporting and Analysis

m Financial Management

m Planning


Supported Software Notes

Microsoft SQL Server (2005 SP1 or 2000 SP3a) Analysis Services client Required only for:


l Financial Reporting1

l Web Analysis

l SAP GUI 6.20 OLE DB for OLAP Provider

l SAP GUI 6.4 OLE DB for OLAP Provider

Required only for Interactive Reporting

SAP Java Connector (JCO) 2.1.7–Optional—used to connect to SAP BW.2 Required only for:


l SQR Production Reporting3

l Web Analysis

1Microsoft SQL Server Analysis Services is supported only by Financial Reporting on Windows. The SSAS client and SSAS server versions mustmatch.2Configure the SAP data source access and authentication after installation, when Reporting and Analysis create the correct SAP directories.Download it as a registered user at https://service.sap.com/connectors.3If you are installing SQR Production Reporting DDO, SAP Java Connector (JCO) drivers are required. Configure the SAP data source access andauthentication after installation, when Reporting and Analysis creates the correct SAP directories. Download it as a registered user at https://service.sap.com/connectors.

Essbase - System 9This section lists the requirements for:

l Essbase


l Integration Services

l Provider Services

l Shared Services

Server RequirementsEssbase - System 9 server requirements:

l “Server OS/Processor” on page 23

l “Disk Space and RAM” on page 24

l “Hyperion Software” on page 24

l “Repository Databases” on page 24

l “Java Application Server” on page 25

l “Data Source Requirements” on page 26


Server OS/Processor

Operating System Platform Processor Notes

Windows:

l Windows 2003 SP1

l Windows 2000 Server SP4

32-bit x86

l Windows 2003 SP1 (Server Enterprise Edition) 64-bit Itanium 2 Administration Services and Provider Services onlysupport Windows 2003 64–bit if Tomcat is used asthe application server.

l Windows 2003 SP1 (Server Enterprise Edition) 64-bit x64l For example, AMD Opteron or Intel Xeon.

l Supported with 32–bit or 64–bit installersexcept for Administration Services andIntegration Services which are supported onlywith 32–bit installers.

HP-UX:

l HP-UX 11.11

32–bit Risc Release 9.3.1 is the last release to support HP-UX11.11 Risc.

HP-UX:

l HP-UX 11.11

64–bit Risc Release 9.3.1 is the last release to support HP-UX11.11 Risc.

Note: All products are only supported on thisprocessor with 32–bit installer.

l HP-UX 11.31

l HP-UX 11.23

64-bit Itanium 2 Administration Services and Provider Services onlysupport HP-UX 64-bit if Tomcat is used as theapplication server.

IBM AIX:

l AIX 5.3 ML3

l AIX 5.2 ML7

32-bit PowerPC For AIX 5.2, Shared Services requires ML8.

l AIX 5.3 ML3

l AIX 5.2 ML7

64-bit PowerPC Supported with 32–bit or 64–bit installers exceptfor Administration Services which is supported onlywith 32–bit installer.

Oracle Enterprise Linux 4 32–bit x86

Red Hat Linux:

l Red Hat Linux AS 4 Update 2 with glibc-2.3.4-2.13 orlater


32-bit x86

Solaris:

l Solaris 10

l Solaris 9

32-bit SPARC V9

l Solaris 10

l Solaris 9

64-bit SPARC V9 Supported with 32–bit or 64–bit installers exceptfor Administration Services which is supported onlywith 32–bit installer.

Essbase - System 9 23

Disk Space and RAMDisk space and RAM requirements are for Hyperion products and sample applications.

Component Disk Space RAM Notes

Essbase Server1 1 GB 1 GB

Application ProgrammingInterface

20 MB 256 MB minimum

Analytic AdministrationServer

500 MB2 32 MB times the number of concurrent Administration Server users

For example, 32 MB * 10 users = 320 MB. For detailed RAM requirements, see theEssbase Administration Services Installation Guide.

Essbase Integration Server 170 MB 256 MB

Provider Services 340 MB 128 MB

132–bit Administration Server supports both 32–bit and 64–bit Essbase Server. 64–bit Administration Server supports only 64–bit EssbaseServer.2Allow extra disk space for data files and outline files that are copied to Administration Server during data loading and outline editing, respectively.

Hyperion Software

Required Hyperion Software Required For Notes

Shared Services (unless using Essbase in native securitymode)

l Essbase


l Provider Services

See “Shared Services Requirements” on page15.

Essbasel Administration Services


l Provider Services

Administration Services Provider Services

Smart View Provider Services

Note: For information about which releases of these required products are compatible with thisrelease of Essbase - System 9, see Chapter 4, “Release Compatibility.”

Repository DatabasesA repository is required for:

l Administration Services—only when using Log Analyzer


l Shared Services


Supported Relational Data Repositories Notes

l IBM DB2 9.1

l IBM DB2 8.2



Oracle:2

l Oracle 11g3


l Oracle 10g (10.1.0.5)

l Oracle 9i (9.2.0.5)

1By default, SQL Server 2005 disables TCP/IP connections to the database. Ensure that the TCP/IP connections are enabled.2For all supported versions of Oracle: 1) Includes support for RAC - Real Application Cluster and ASM. Includes support for SE, SE1, EE. TheOracle OLE provider and Oracle database server must be the same version.3Oracle 11g requires Oracle Hyperion Configuration Utility Service Fix 9.3.1.0.01.

Java Application ServerIf an application contains more than 500 users and 10,000 measures, deploy to a Java applicationserver cluster for increased scalability.

Java Application Servers are required for:


l Provider Services

l Shared Services

Note: Only 32-bit application servers are supported.

Supported Java Application Servers Notes

Apache Tomcat 5.0.281

l BEA WebLogic 9.22

l BEA WebLogic 9.1

l BEA WebLogic 8.1.63

Also includes support for WebLogic Express.

l IBM WebSphere 6.1.0.54


l Oracle 10g Release 3 (10.1.3.1.0)


1Apache Tomcat is automatically installed on all platforms. For deployments that require high availability or failover, Hyperion recommendsusing a commercially supported Java application server that supports high availability and failover.

Essbase - System 9 25

2When manually deploying Shared Services to WebLogic 9.2, you must set the <enfore-valid-basic-auth-credentials> tag to false in the <DOMAIN_LOCATION>/<DOMAIN_NAME>/config/config.xml file.3Hyperion release 9.3.1 is the last release to support BEA WebLogic 8.1.6.4WebSphere Express, ND, and XD Editions are supported for each supported version of WebSphere; ND and XD are supported only via manualdeployment.

Data Source Requirements

Database ConnectivityDatabase Connectivity applies only to Essbase SQL Interface and Integration Services.

For more information, see the Hyperion Essbase - System 9 Installation Guide and the EssbaseIntegration Services Installation Guide.

Protocols Drivers Supported Notes

ODBC DataDirect 5.2 SP1

JDBC DataDirect 3.6 build 24

Reporting and AnalysisThis section lists the requirements for:



l SQR Production Reporting

l Web Analysis

l Workspace

l Shared Services

Server RequirementsReporting and Analysis server requirements:



l “Required Hyperion Software” on page 28

l “Required Third-Party Software” on page 28


l “Java Application Servers and Web Servers” on page 29


Server OS/Processor

Operation System Platform Processor Notes

Windows:

l Windows 2003 SP1


32-bit x86

HP-UX:

l HP-UX 11.31

l HP-UX 11.23

64–bit Itanium 2 Interactive Reporting services run only in 32–bit mode.

Connectivity to Interactive Reporting datasources in a 64–bit operating system requiresa 32–bit database client.

l HP-UX 11.111 32-bit RISC

IBM AIX:

l AIX 5.3 ML3

l AIX 5.2 ML7

32-bit2 PowerPC For AIX 5.2, Shared Services requires ML8.

Red Hat Linux:



32-bit x86

Solaris:

l Solaris 10

l Solaris 9

32-bit SPARC

1Release 9.3.1 is the last release to support HP-UX 11.11 RISC.2If running Reporting and Analysis on a UNIX platform, do not use Financial Management as a data source.


Component Disk Space RAM

Workspace 1 GB

For services: 200 MB

For importing files: 1 GB minimum

1 GB

For services: 1 GB minimum

Financial Reporting 200 MB 1 GB

Interactive Reporting 500 MB 1 GB

SQR Production Reporting 200 MB 256 MB

Web Analysis 2 GB 1 GB

Reporting and Analysis 27

Required Hyperion SoftwareReporting and Analysis requires Shared Services. See also “Shared Services Requirements” onpage 15.

Required Third-Party Software

Software Required For Notes

l One of the following Distillers:

m Adobe Acrobat Distiller Server 6.01

m AFPL Ghostscript 8.5.1, or GNU Ghostscript 7.0.6

Required only for FinancialReporting2


l Microsoft SQL Server (2005 SP1 or 2000 SP3a) Analysis Services client—Windows only

l SAP GUI 6.20 OLE DB for OLAP Provider—Windows only

l SAP GUI 6.4 OLE DB for OLAP Provider—Windows only

Interactive Reporting


l NetWeaver BI and SAP BW 7.0 connectivity require the use of SAP JCO 2.1.7

l For Microsoft SQL Server, you need Microsoft SQL Server (2005 SP1 or 2000 SP3a) AnalysisServices. The SSAS client and SSAS server versions must match.


l SQR ProductionReporting

l Web Analysis

SQL Grid connectivity (Supports SQL Grid with Oracle, IBM DB2, and Microsoft SQL Server)—Merantdrivers


l Web Analysis

1To obtain a copy of Acrobat Distiller Server 6.0, see your account manager.2For Financial Reporting, you must use Ghostscript and not Distiller to import content into Microsoft Word and PowerPoint. When you run Oracle'sHyperion® Configuration Utility™, you must choose AFPL Ghostscript 8.5.1 or GNU Ghostscript 7.0.6.

Repository DatabasesOne of the following must be used as the repository database:

Database Notes

IBM DB2:

l IBM DB2 9.1

l IBM DB2 8.2

Microsoft SQL Server:




Database Notes

Oracle2:

l Oracle 11g3


l Oracle 10g (10.1.0.5)

l Oracle 9i (9.2.0.5)

1By default, SQL Server 2005 disables TCP/IP connections to the database. Ensure that the TCP/IP connections are enabled.2For all supported versions of Oracle: 1) Includes support for Real Application Cluster (RAC) and ASM. Includes support for SE, SE1, and EE.The Oracle OLE provider and Oracle database server must be the same version.3Oracle 11g requires Oracle Hyperion Configuration Utility Service Fix 9.3.1.0.01.

Java Application Servers and Web ServersIf an application contains more than 500 users and 10,000 measures, deploy to a Java applicationserver cluster for increased scalability.

A Java Application Server is required for:


l Web Analysis

l Workspace (includes Interactive Reporting and SQR Production Reporting)

l Shared Services


Supported Java Application Servers Notes

l Apache Tomcat 5.0.281

l BEA WebLogic 9.22

l BEA WebLogic 9.1





l Sun Java Enterprise System 8.1 05Q45 Does not apply to Shared Services



Includes support for Oracle Application Server Single Sign-On, for Workspace only.

1Apache Tomcat is automatically installed on all platforms. For deployments that require high availability or failover, Hyperion recommendsusing a commercially supported Java application server that supports high availability and failover.2When manually deploying Shared Services to WebLogic 9.2, you must set the <enfore-valid-basic-auth-credentials> tag to false in the <DOMAIN_LOCATION>/<DOMAIN_NAME>/config/config.xml file.3Hyperion release 9.3.1 is the last release to support BEA WebLogic 8.1.6.4WebSphere Express, ND, and XD Editions are supported for each supported version of WebSphere; ND and XD are supported only via manualdeployment.


5Supported on Solaris platforms only, via manual deployment; auto-deployment using Hyperion Configuration Utility is not supported for SunJava Enterprise System.

A Web Server is required for:


l Web Analysis

l Workspace (includes Interactive Reporting and SQR Production Reporting)

Web Server Notes

Supported Windows Versions:

l Apache Server 2.0.52

l IBM HTTP Server 6.1


l Microsoft IIS 6.0 (on Windows 2003 SP1)

l Microsoft IIS 5.0 (on Windows Server 2000 SP4)

l Oracle HTTP Server

Supported UNIX Version:




l Oracle HTTP Server


Databases as Data Sources

Supported Data Source Databases Reporting and Analysis Modules andConnectivity

Notes

Hyperion data sources: one or more of the following:1

l Essbase

l Interactive Reporting—C API / MDX

l Financial Reporting—ADM

l Web Analysis—ADM

l SQR Production Reporting—DDO

l Financial Managementl Financial Reporting—ADM


The version of FinancialManagement ADM must matchthe version of FinancialManagement Server



Notes

l Planning l Financial Reporting—ADM


l Planning data sources onlyapply to FinancialReporting.

l Web Analysis supportsPlanning only for access toEssbase cubes.

l The version of PlanningADM must match therelease of Planning Server.

l One of the following:

m Microsoft Access 2007


m Microsoft Access XP (2002)


SQR Production Reporting—ODBC Supported only by SQRProduction Reporting —Windows only

l IBM DB2 9.1 l Interactive Reporting—ODBC

l SQR Production Reporting—ODBC, JDBC,DB2 Connect

l Web Analysis—JDBC

l IBM DB2 8.2 l Interactive Reporting—ODBC



l IBM DB2 v7x for z/OS l Interactive Reporting—ODBC


Supported only by:



l Web Analysis

l IBM DB2:

m IBM DB2 OLAP Server 8.2

m IBM DB2 OLAP Server 8.1.7a

Not supported by:

l Oracle's Hyperion®Interactive ReportingStudio

l Oracle's Hyperion®Financial Reporting Studio

l Web Analysis

l Informix 9.4 and later SQR Production Reporting—ODBC, JDBC,SDK 2.81

Supported only by SQRProduction Reporting

l Informix 9.2 and later Interactive Reporting—ODBC Supported only by InteractiveReporting



Notes

l Microsoft SQL Server:

m Microsoft SQL Server 2005 SP12

m Microsoft SQL Server 2000 SP3a

l Interactive Reporting—ODBC

l SQR Production Reporting—ODBC, JDBC


l Microsoft SQL Server:3

m Microsoft SQL Server 2005 SP1 AnalysisServices

m Microsoft SQL Server 2000 SP3a AnalysisServices

l Interactive Reporting—ODBO

l Financial Reporting—ADM

l SQR Production Reporting—DDO


l OpenEdge 10.1B SQR Production Reporting—ODBC Supported only by SQRProduction Reporting

l Oracle4:

m Oracle 11g5

m Oracle 10g Release 2 (10.2.0.2)

m Oracle 10g (10.1.0.5)

m Oracle 9i (9.2.0.5)

l Interactive Reporting—OCI, ODBC

l SQR Production Reporting—OCI, ODBC,JDBC


l Progress 9.1E04 SQR Production Reporting—ODBC Supported only by SQRProduction Reporting

l Red Brick 6.3 or higher l Interactive Reporting—ODBC

l SQR Production Reporting—ODBC

Supported only by:

l Interactive Reporting—Windows only

l SQR Production Reporting—Windows only

SAP:

l SAP BW 3.1 or 3.5

l NetWeaver BI (SAP BW) 7.0

l Financial Reporting—BAPI

l Interactive Reporting—ODBO

l SQR Production Reporting—BAPI

l Web Analysis—BAPI

SAP R/3

l SAP R/3 Enterprise (mySAP ERP 2005 ) 4.6C / 6.x

l SQR Production Reporting—BAPI Supported only by SQRProduction Reporting

l Sybase 15 l Interactive Reporting—ODBC

l SQR Production Reporting—ODBC, JDBC,CTLIB

Supported only by:



l Sybase ASE 12.5.1 and 12.5.2 and later l Interactive Reporting—ODBC

l SQR Production Reporting—ODBC, JDBC,CTLIB


Supported only by:





Notes

l Sybase IQ 12.6 and later l Interactive Reporting—ODBC

l SQR Production Reporting—ODBC

Supported only by:

l Interactive Reporting—Windows only

l SQR Production Reporting—Windows only

Teradata:6

l Teradata V12.x (Teradata ODBC driver version 12.0)

l Teradata V2R6.0.x (Teradata ODBC driver version 3.06)



l SQR Production Reporting—ODBC,PP2(Solaris, PA-RISC HP-UX)


Supported only by:



l Web Analysis

Teradata (ODBC):7

l Teradata V12.x (Teradata ODBC driver version 12.0)




l SQR Production Reporting—ODBC, PP2(Solaris, PA-RISC HP-UX)


Not supported by FinancialReporting

Teradata (JDBC):8

l Teradata V12.x (Teradata JDBC driver version 12.00.00.01)

l Teradata V2R6.0.x (Teradata JDBC driver version 03.01.00.102 or 03.02.00.03)

l Teradata V2R5.1.x (Teradata JDBC driver version 03.01.00.10, 03.03.00.06, or 03.04.00.03)

l Web Analysis—JDBC Not supported by FinancialReporting

1 data sources should be consistent with compatibility matrix. See Chapter 4, “Release Compatibility”2By default, SQL Server 2005 disables TCP/IP connections to the database. Ensure that the TCP/IP connections are enabled.3Microsoft SQL Server Analysis Services, supported only by Windows-based Reporting and Analysis servers4For all supported versions of Oracle: 1) Includes support for Real Application Cluster (RAC) and ASM. Includes support for SE, SE1, and EE.The Oracle OLE provider and Oracle database server must be the same version.5Oracle 11g requires Oracle Hyperion Configuration Utility Service Fix 9.3.1.0.01.6Teradata ODBC drivers must be obtained separately from Teradata.7Obtain the driver separately from the Teradata web site.8Obtain the driver separately from the Teradata web site.

Financial Performance Management ApplicationsThis section lists the requirements for:

l Performance Management Architect



l Planning

Financial Performance Management Applications 33

http://www.teradata.com/DownloadCenter/

http://www.teradata.com/DownloadCenter/

l Strategic Finance

l Shared Services

Server Requirements

Financial Performance Management Applications server requirements:




l “Required Third-Party Software” on page 36



Server OS/Processor


l Windows 2003 SP11


32-bit Dual Pentium4, 2 GHzminimum

Supported only by:

l Financial Management Server

l Database Server for Financial Management

l Planning


l Windows 2003 SP1


32-bit Dual Pentium2, 8 GHzminimum

Supported only by: Strategic Finance Server2

l Windows 2003 SP13


64-bit Itanium 2 Not supported by:



Planning supports Windows 2003 64-bit only for PlanningWeb using Tomcat.

l HP-UX 11.23 64-bit Itanium 2 Not supported by:



Planning supports HP-UX 11.23 64-bit only for PlanningWeb using Tomcat.

HP-UX:

l HP-UX 11.114

32–bit PA-RISC Supported only by Performance Scorecard



IBM AIX:

l AIX 5.3 ML3

l AIX 5.2 ML7

32-bit PowerPC Supported only by:


l Planning

For AIX 5.2, Shared Services requires ML8.

Oracle Enterprise Linux 4 32-bit Not supported by:


l Planning

Red Hat Linux:



32-bit x86 Supported only by Performance Scorecard

Solaris:

l Solaris 10

l Solaris 9

32-bit SPARC Supported only by:


l Planning

1For Financial Management, also install the following DCOM hot fix from Microsoft: http://support.microsoft.com/kb/8991482Strategic Finance Server —Requires a Dual or Quad Pentium for 50 or more users connecting to the server to check entities in and out or torun server-based consolidation for structures that contain more than 15 entities.3For Financial Management, also install the following DCOM hot fix from Microsoft: http://support.microsoft.com/kb/899148 .4Release 9.3.1 is the last release to support HP-UX 11.11 PA-RISC.



Financial Management Server 32 GB (10 GB available) 4 GB

Database Server for Financial Management 12 GB minimum 4 GB minimum

Planning 32 GB (10 GB available) 4 GB

Performance Scorecard 2 GB recommended (1 GB minimum) 1 GB1

Strategic Finance Server 250 MB2 2 GB minimum

11 GB includes Performance Scorecard and Alerter servers.2Sufficient storage should be included to contain the entities, their backup archives, administrative and transaction files, and user backgroundtask logs, such as consolidation reports.

Required Hyperion SoftwareSee the other sections in this chapter to check requirements for other required Hyperionproducts.


http://support.microsoft.com/kb/899148

http://support.microsoft.com/kb/899148

RequiredSoftware

Required For Notes

Essbase (EssbaseServer andAdministrationServicescomponents)

l Planning

l Performance Scorecard Server—for custom reporting through cube production

PerformanceManagementArchitect(optional)

l Financial Management—(Optional if you are using Classic Application Administration)—Performance Management Architect is part of the Financial Management installation

l Planning—(Optional if you are using Classic Application Administration)—PerformanceManagement Architect is part of the Planning installation

Shared Servicesl Financial Management

l Planning

l Performance Scorecard (unless using Performance Scorecard in native authenticationmode)

l Strategic Finance—Shared Services is required if importing and exporting with FinancialManagement, Planning, or Essbase, or if using a security provider other than NTLM, suchas LDAP

See “Shared ServicesRequirements” onpage 15.

Workspacel Financial Management

l Planning


Third-Party Software Notes

Microsoft .NET Framework 2.0 Required only for Performance Management Architect

1

Java tools—Java Cryptology Extension 1.2.2 Required only for Performance Scorecard Server

MDAC 2.8 (for Oracle and SQL Server)

PKZip 8.0 (command-line interface) for database backup

Required only for Strategic Finance

Strategic Finance

1If using Performance Management Architect, Microsoft .NET Framework 2.0 is installed automatically by the Planning or Financial Managementsetup program if not already installed.

Repository DatabasesProducts that require a data repository:




l Planning

l Shared Services


Relational Data Repositories Notes

l IBM DB2 9.1

l IBM DB2 8.2

If you use an IBM DB2 database for Performance Management Architect, DB2 9 Runtime Clientand DB2 .NET Data Provider 9.1.0.2 must be installed on the Performance Management ArchitectDimension server.



By default, SQL Server 2005 disables TCP/IP connections to the database. Ensure that the TCP/IP connections are enabled.

Oracle1:

l Oracle 11g2


l Oracle 10g (10.1.0.5)

l Oracle 9i (9.2.0.5

l For all supported versions of Oracle, the Oracle OLE provider and Oracle database server mustbe the same version.

l Performance Management Architect—The Oracle client must be installed on the Dimensionserver.

1For all supported versions of Oracle: 1) Includes Support for Real Application Cluster (RAC) - and ASM. Includes support for SE, SE1, and EE.The Oracle OLE provider and Oracle database server must be the same version.2Oracle 11g requires Oracle Hyperion Configuration Utility Service Fix 9.3.1.0.01.

Java Application Servers and Web ServersIf an application contains more than 500 users and 10,000 measures, deploy to a Java applicationserver cluster for increased scalability.

A Java application server is required only for:


l Planning


l Shared Services


Java Application Servers Notes


l BEA WebLogic 9.22

l BEA WebLogic 9.1









1Apache Tomcat is automatically installed on all platforms. For deployments that require high availability or failover, Hyperion recommendsusing a commercially supported Java application server that supports high availability and failover.2When manually deploying Shared Services to WebLogic 9.2, you must set the <enfore-valid-basic-auth-credentials> tag to false in the <DOMAIN_LOCATION>/<DOMAIN_NAME>/config/config.xml file.3WebSphere Express, ND, and XD Editions are supported for each supported version of WebSphere; ND and XD are supported only via manualdeployment.

The following products require a Web server:



l Planning

Web Server Notes

Windows:

l Microsoft IIS 6.0 (on Windows 2003 SP1)

l Microsoft IIS 5.0 (on Windows Server 2000 SP4)


l Performance Management Architect—Uses only IIS 6.0 or 6.0 for Web Services

l Financial Management—Uses only IIS

l Planning—Can use an internal WebLogic or WebSphere Web server

UNIX:

Apache Server 2.0.52

Not supported for:



Data ManagementThis section lists the requirements for:

l Data Integration Management

l FDM

l Data Relationship Management

l Translation Manager

l Shared Services

Server Requirementsl “Server OS/Processor ” on page 39

l “Disk Space/RAM” on page 40



l “Required Third-Party Software ” on page 41

l “Repository Databases ” on page 41


Server OS/Processor


Microsoft Windows:

l Windows 2003 SP1


32-bit x86

l Windows 2003 SP1


32–bit Pentium 4 Supported by:

l FDM Web Server—per 75 concurrent users

l Translation Manager2

l Windows 2003 SP1


32–bit Dual Pentium4, 2 GHz

Supported by:

l FDM Application Server—per 75 concurrent users

l Data Relationship Management—ApplicationServer

l Data Relationship Management—Database Server

l Windows 2003 SP1


32–bit Quad Pentium4

Supported by only FDM Database Server

HP-UX 11.113 32-bit PA-RISC Supported by only Data Integration Management

IBM AIX:

l AIX 5.3 ML3

l AIX 5.2 ML7

32-bit PowerPC Supported by:



For AIX 5.2, Shared Services requires ML8.

Oracle Enterprise Linux 44 32-bit

Red Hat Linux5:



32-bit x86 Supported by only Data Integration Management

Solaris:

l Solaris 10

l Solaris 9

32-bit SPARC Supported by:



1FDM—FDM Web Server runs on Windows 2000 server only if no other .NET applications are installed. Not recommended.2Translation Manager—Requires a Pentium 4, 800 MHz minimum.3Release 9.3.1 is the last release to support HP-UX 11.11 PA-RISC.4Oracle Enterprise Linux 4—for supporting browser-based clients only.5Red Hat Linux AS / EL—For supporting browser-based clients only.

Data Management 39

Note: FDM cannot be installed on a machine that hosts either WebSphere application server orWebLogic application server (for use with other products — FDM does not use a Javaapplication server).

Disk Space/RAM


Data Integration Management:

PowerCenter Repository Server1 150 MB 256 MB

PowerCenter Server 70 MB 256 MB

FDM Database Serverl Dependent on size of the FDM application

l Multiple HDDs to spread processing

1 GB per 75 concurrent users (2 GBminimum)

FDM folder structure Dependent on size of the FDM application

FDM Application Server 200 MB 2 GB (per 75 concurrent users)

FDM Web Server 200 MB 2 GB

Data Relationship Management-Database Server2

2 GB minimum 2 GB

Data Relationship Management-Application Server

100 MB 4 GB

Translation Manager 300 MB 512 MB minimum

1The installation program requires an additional 30 MB of disk space for temporary files. You must set the TMP environment variable to specifythe location of the files; for example, TMP=D:\temp.2If using SQL Server, run it in mixed authentication mode, not Windows-only mode.

Required Hyperion Software

Required Hyperion Software Notes

Shared Services Required for:

l Data Integration Management: PowerCenter Server—For external authentication:Shared Services or Informatica native authentication.

l Data Relationship Management-Application Server—For external authentication only


See “Shared Services Requirements” on page 15.


Required Hyperion Software Notes

Dependent on the Hyperion products that aredeployed, one or more products:

l Essbase


l Oracle's Hyperion® Enterprise®

l Planning

For FDM, the required components:

l Workbench Client

l Application Server


Requirement Notes

l Microsoft MDAC 2.6 or later—MDAC is installed by FDM.

l Excel 2000 or later

Required only forFDM ApplicationServer

l Microsoft IIS 6.0 (on Windows Server 2003)

l Microsoft MDAC 2.6 or later—MDAC is installed by FDM.

Required only forFDM Web Server

l “Optional”—Additional client software, such as Oracle SQL*Plus for Oracle and Query Analyzer for SQL Server,can be used for verifying connectivity and for troubleshooting. ODBC can also be used for troubleshooting.

l A set of client drivers:

m Microsoft SQL Server client drivers (DLLs)1

m Oracle client drivers (DLLs)

l Microsoft IIS 5.0 or later

l Microsoft .NET Framework

Required only forData RelationshipManagement -Application Server

For bridging to IIS, a vendor-supplied application server connector:

l (Windows only) Apache Tomcat connector

l WebLogic connector

l IBM HTTP server for WebSphere

Required only forTranslationManager

1If using SQL Server, client software is not required if MDAC 2.7 or later is installed. If MDAC 2.7 is installed on the application server, theinstallation program automatically updates it to the latest version. If MDAC is not installed, or if the installed version is earlier than 2.7, youmust manually install MDAC.

Repository DatabasesA repository database is required only for:


l FDM


l Shared Services

Data Management 41

Relational Data Repositories Notes

l IBM DB2 8.2

l IBM DB2 9.1

Not supported by FDM or Data Relationship Management



By default, SQL Server 2005 disables TCP/IP connections to the database. Ensure that the TCP/IP connections are enabled.

Oracle1:

l Oracle 11g 2


l Oracle 10g (10.1.0.5)

l Oracle 9i (9.2.0.5)

1For all supported versions of Oracle: 1) Includes Support for Real Application Cluster (RAC) and ASM. Includes support for SE, SE1, and EE.The Oracle OLE provider and Oracle database server must be the same version.2Oracle 11g requires Oracle Hyperion Configuration Utility Service Fix 9.3.1.0.01.

Java Application Servers and Web ServersA Java application server is required only for:


l Shared Services




l BEA WebLogic 9.22

l BEA WebLogic 9.1

l BEA WebLogic 8.16

Translation Manager supports only WebLogic 9.1.





1Apache Tomcat is automatically installed on all platforms. For deployments that require high availability or failover, Hyperion recommendsusing a commercially supported Java application server that supports high availability and failover.2When manually deploying Shared Services to WebLogic 9.2, you must set the <enfore-valid-basic-auth-credentials> tag to false in the <DOMAIN_LOCATION>/<DOMAIN_NAME>/config/config.xml file.3WebSphere Express, ND, and XD Editions are supported for each supported version of WebSphere; ND and XD are supported only via manualdeployment.



Database ConnectivityData Integration Management PowerCenter Server requires Native drivers for databaseconnectivity.

Translation Manager requires ODBC protocol and the DataDirect 5.2 SP1 driver.

Data Management 43


4Release Compatibility

In This Chapter

How to Read the Tables in This Chapter .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45

Shared Services Release Compatibility .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45

Essbase - System 9 Release Compatibility.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46

Reporting and Analysis Release Compatibility .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47

Financial Performance Management Applications Release Compatibility .. . . . . . . . . . . . . . . . . . . . . . . . . . .49

Data Management Release Compatibility .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50

How to Read the Tables in This ChapterTo ensure that you obtain the correct information from the tables in this chapter, read downeach column to identify the versions of other Hyperion products that are compatible with theproduct named at the head of the column.

For example, Planning 9.3.1 is compatible with Shared Services version 9.3.1.

Shared Services Release CompatibilityRelease 9.3.1 Hyperion products are not compatible with previous versions of Shared Services.Therefore, if you upgrade any Hyperion product to Release 9.3.1, you must upgrade SharedServices to Release 9.3.1.

However, Shared Services 9.3.1 is compatible with previous versions of Hyperion products.Therefore, you can use Shared Services 9.3.1 with previous versions of other Hyperion products.(For example, you can use Essbase 9.2.x with Shared Services 9.3.1).

How to Read the Tables in This Chapter 45

Essbase - System 9 Release CompatibilityTable 2 Essbase - System 9 Release Compatibility

Essbase 9.3.1 Administration Services9.3.1

IntegrationServices 9.3.1

ProviderServices 9.3.1

Foundation Services

Compatible Shared Servicesversions

9.3.1 9.3.1 NA 9.3.1

Compatible Smart View versions 9.3.x NA NA 9.3.x

Essbase - System 9

Compatible Essbase versions NA 9.x

7.1.6

9.x

7.1.6

9.x

7.1.6

Compatible AdministrationServices versions

9.3.x NA 9.3.x

7.1.6

NA

Compatible Provider Servicesversions

9.x 9.3.x NA NA

Compatible Integration Servicesversions

9.3.x

7.1.6

NA NA NA

Reporting and Analysis

Compatible Financial Reportingversions

9.3

9.2

NA NA NA

Compatible SQR ProductionReporting versions

9.3

9.2

NA NA NA

Compatible InteractiveReporting versions

9.3.x NA NA NA

Compatible Web Analysisversions

9.3

9.2

NA NA NA

Compatible Oracle's Hyperion®Application Builder J2EEversions

9.3

9.2

NA NA NA

Financial Performance Management Applications

Compatible Planning versions

1

9.3.x

9.2.x

4.1

9.3.x

9.2.x

4.1

NA NA

46 Release Compatibility

Essbase 9.3.1 Administration Services9.3.1

IntegrationServices 9.3.1

ProviderServices 9.3.1

Compatible FinancialManagement versions

2

9.3.x

9.2.x

4.1

NA NA NA

Compatible PerformanceScorecard versions

9.3.x

9.2.x

9.0.1

4.1

4.0.5

4.0.1

4.0

NA NA NA

Compatible Strategic Financeversions

NA NA NA NA

Data Management

Compatible Data RelationshipManagement versions

All versions through flat files NA NA NA

Compatible FDM versions 9.2

9.3

9.3.1

NA NA NA

Compatible Data IntegrationManagement versions

9.3.1 NA NA NA

1You must use the same release of Performance Management Architect as Essbase.2You must use the same release of Performance Management Architect as Essbase.

Reporting and Analysis Release CompatibilityTable 3 Reporting and Analysis Release Compatibility

Interactive Reporting9.3.1

Financial Reporting 9.3.1 SQR ProductionReporting 9.3.1

Web Analysis 9.3.1

Foundation Services

Compatible Shared Servicesversions1

9.3.1 9.3.1 9.3.1 9.3.1

Compatible Smart Viewversions

9.3.x 9.3.x 9.3.x 9.3.x

Reporting and Analysis Release Compatibility 47

Interactive Reporting9.3.1

Financial Reporting 9.3.1 SQR ProductionReporting 9.3.1

Web Analysis 9.3.1

Essbase - System 9

Compatible Essbase versions 9.3.x

9.2.x

7.2

7.1.x

9.3.x

9.2.x

7.2

7.1.x

9.3.x

9.2.x

7.2

7.1.x

9.3.x

9.2.x

7.2

7.1.x


NA NA NA NA


NA 9.3.1 NA 9.3.1

Compatible IntegrationServices versions

NA 9.3.x

9.2.x

9.0

9.3.x

9.2.x

9.0

9.3.x

9.2.x

9.0

Compatible ApplicationBuilder J2EE versions

NA NA NA NA


Compatible Planning versions NA 9.3.x

9.2.x

4.0.5

NA 9.3.x

9.2.x

4.0.5


NA 9.3.x

9.2.x

4.0.2

NA 9.3.x

9.2.x

4.0.2


NA NA NA NA


NA NA NA NA

Data Management

Compatible Data RelationshipManagement versions

NA NA NA NA

Compatible FDM versions NA NA NA NA


NA NA NA NA

1Shared Services is not needed for standalone products


Financial Performance Management ApplicationsRelease CompatibilityTable 4 Financial Performance Management Applications Release Compatibility

Planning 9.3.112 Financial Management 9.3.1

3

Performance Scorecard9.3.1

Strategic Finance9.3.1

Foundation Services


9.3.1 9.3.1 9.3.1 9.3.1

Compatible Smart Viewversions

9.3.x 9.3.x

9.2.x

NA NA

Essbase - System 9

Compatible Essbase versions 9.3.1 9.3.x

9.2.x

9.3.x

9.2.x

9.0.1

7.1.x

9.3.x

9.2.x (7.1.2 API)

7.1.x


9.3.1 9.3.x

9.2.x

NA NA


NA NA NA NA

Compatible IntegrationServices versions

NA NA 9.3.x

9.2.x

9.0.1

7.1.x

NA

Reporting and Analysis

Compatible FinancialReporting versions

9.3.1

9.3.0.1

9.3.x NA NA

Compatible SQR ProductionReporting versions

NA NA NA NA

Compatible InteractiveReporting versions

NA NA Through IR Smartcuts NA

Compatible Web Analysisversions

9.3.x

9.2.x

9.3.x Through ExtendedAnalytics

NA

Financial Performance Management Applications Release Compatibility 49

Planning 9.3.112 Financial Management 9.3.1

3

Performance Scorecard9.3.1

Strategic Finance9.3.1

Compatible Oracle'sHyperion® Application BuilderJ2EE versions

NA 9.3.x NA NA


Compatible Planning versions NA 9.3.x

9.2.x

4.1.1

The version deployedwith Essbase


9.3.1 NA 9.3.x

9.2.x

4.1.1


NA 9.3.x NA NA


NA 9.3.x NA NA

Data Management

Compatible DataRelationship Managementversions

All versions throughflat files

All versions through flat files NA NA

Compatible FDM versions The version deployedwith Essbase

9.3.x NA NA


9.3.1 9.3.x NA

1Includes Oracle's Hyperion® Workforce Planning and Capital Expense Planning2You must use the same release of Performance Management Architect as Planning.3You must use the same release of Performance Management Architect as Financial Management.

Data Management Release Compatibility

Table 5 Data Management Release Compatibility

Data Relationship Management9.3.1 and 9.3.2

FDM 9.3.1 Data IntegrationManagement 9.3.1

Foundation Services


9.3.1 NA 9.3.1

Compatible Smart View versions NA NA NA


Data Relationship Management9.3.1 and 9.3.2

FDM 9.3.1 Data IntegrationManagement 9.3.1

Essbase - System 9

Compatible Essbase versions All versions through flat files 9.3.x

9.2.x (7.1.2 API)

7.1.x

9.3.x

7.1.x


All versions through flat files NA NA


NA NA NA

Compatible Integration Servicesversions

NA NA NA


Compatible Planning versions All versions through flat files The version deployed withEssbase

9.3.x


All versions through flat files 9.3.x

9.2.x

4.1.1

9.3.x


NA NA 9.3.x


NA All versions through flat files NA

Data Management Release Compatibility 51


5Hyperion License Compliance

In This Chapter

Ensuring License Compliance... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53

Activating and Deactivating Product Features... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53

Auditing Usage ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65

Retrieving License Keys for Data Integration Management .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65

Ensuring License ComplianceOracle's Hyperion® License Server™ and standalone licenses are no longer used for licensemanagement. Instead, administrators must audit product use for all products.

To ensure compliance with your license agreement, Hyperion recommends that you activate ordeactivate features according to your license agreement and audit your usage.

If you are using Data Integration Management, you still need to retrieve license keys. See“Retrieving License Keys for Data Integration Management” on page 65.

Activating and Deactivating Product FeaturesDuring product configuration with Hyperion Configuration Utility, on the Product Optionspanel, activate or deactivate features according to your license agreement. See the “Configuringand Setting Up” chapter in the relevant product installation guide, and review your licenseagreement to identify features that you are authorized to use.

During product configuration, Hyperion Configuration Utility copiesregistry.properties to <Hyperion_Home>\common\config on the server on which youran Hyperion Configuration Utility.

After configuration (and before you validate the installation) you must open this file in any texteditor to review and specify which product options are activated. You must complete this stepto ensure you comply with your license agreement and to activate features you are licensed touse.

Note: You do not need to complete this step for the following products:


Ensuring License Compliance 53


l FDM


ä To review or edit the product options that are activated:

1 Open registry.properties—in <Hyperion_Home>\common\config on the server onwhich you ran Hyperion Configuration Utility—in any text editor

2 Review or edit the entries for the products you installed.

The file includes a line for each product and option. The format for each product feature orproduct is:

<feature_name>=true|false, true|false

The first entry indicates whether to activate the feature. The second entry is for internal useonly and should not be changed.

3 If necessary, edit the entries so that the first entry is true for products or features you are licensed touse and false for products or features you are not licensed to use. Ignore the second entry in eachline of the file.

See “About registry.properties” on page 54 for information about the options inregistry.properties.

4 Save the file.

5 Restart the Hyperion services related to any of the entries you changed.

About registry.propertiesThe values you specify in registry.properties depend on which products and features youpurchased. Consult the following tables for information about the features available for eachproduct.

l Each table represents a product purchase from the Oracle price list.

l Each row in the table represents a product feature.

l The Required Value column indicates the value that should appear for that feature inregistry.properties.

If the entry in your registry.properties file is not the same as the entry in the Value columnfor the product you purchased, edit registry.properties.

The format for each product feature or product is:

<feature_name>=true|false, true|false

Edit the first entry in each line; do not edit the second entry

Make sure to use the table for the product you purchased:

l For Hyperion Essbase - System 9, see Table 6 on page 55

54 Hyperion License Compliance

l For Hyperion System 9 Essbase Analytics, see Table 7 on page 56

l For Hyperion System 9 Enterprise Analytics, see Table 8 on page 58

l For Hyperion System 9 Enterprise Analytics and Essbase Analytics, see Table 9 on page59

l For all System 9 BI+ Modules (legacy product offerings), see Table 10 on page 61

l For all System 9 BI Modules (new product offerings from Oracle), see Table 11 on page63

l For Hyperion System 9 Planning and Hyperion Planning – System 9, see Table 12 on page64

l For Hyperion System 9 Strategic Finance and Hyperion Strategic Finance, see Table 13 onpage 65

l For Hyperion System 9 Financial Management and Hyperion Financial Management –System 9, see Table 14 on page 65

l For Hyperion® System 9 Performance Scorecard and Hyperion Performance Scorecard –System 9, see Table 15 on page 65

Table 6 Hyperion Essbase - System 9

Feature Required Value Notes

ANALYTICS_BASESOLUTION TRUE

ANALYTICS_ASO_OPT TRUE

ANALYTICS_BSO_OPT TRUE

ANALYTICS_CURRENCYCONV_OPT TRUE

ANALYTICS_PARTITIONING_OPT TRUE

ANALYTICS_BUSINESS_RULES_OPT TRUE

ANALYTICS_DATAMINING_OPT TRUE

ANALYTICS_HIGHAVAIL_OPT TRUE

ANALYTICS_SAPINTEGCONN_OPT TRUE

ANALYTICS_SSADDIN_OPT TRUE

ANALYTICS_EAS_CREATE_APP_OPT TRUE

ANALYTICS_EAS_EDIT_OTL_OPT TRUE

ANALYTICS_SQL_IF_OPT TRUE

ANALYTICS_SSTOOLKIT_OPT TRUE

ANALYTICS_TRIGGERS_OPT TRUE

Activating and Deactivating Product Features 55


ANALYTICS_SMP_OPT FALSE

ANALYTICS_64BIT_OPT TRUE

ANALYTICS_MAXCONN_OPT TRUE

ANALYTICS_RESTRICTED_OPT FALSE

ANALYTICS_INTEGSVCS_OPT TRUE

ANALYTICS_APPBUILDRNET_OPT TRUE

ANALYTICS_APPMAN_OPT FALSE

ANALYTICS_AAS_OPT TRUE

ANALYTICS_XTDQANDR_OPT TRUE

ANALYTICS_HABJ2EE_OPT TRUE

ANALYTICS_RDONLYSS_OPT FALSE

ANALYTICS_RDONLYSS_TOOL_OPT FALSE

ANALYTICS_LTD_SKU_SS_OPT FALSE

ANALYTICS_LTDAPPMAN_OPT FALSE

Hyperion Essbase Visual Explorer

ANALYTICS_VISEXPLORER_OPT True Only change this value to True if you purchased Hyperion Essbase Visual Explorer.

Table 7 Hyperion System 9 Essbase Analytics



ANALYTICS_ASO_OPT FALSE

























Hyperion System 9 BI+ Visual Explorer Option

ANALYTICS_VISEXPLORER_OPT True Only change this value to True if you purchasedHyperion System 9 BI+ Visual Explorer Option.

Hyperion System 9 BI+ Analytic High Availability ServicesOption

ANALYTICS_HIGHAVAIL_OPT True Only change this value to True if you purchasedHyperion System 9 BI+ Analytic High AvailabilityServices Option.

Hyperion System 9 Windows Developer Toolkit

ANALYTICS_SSTOOLKIT_OPT True Only change this value to True if you purchasedHyperion System 9 Windows Developer Toolkit.

ANALYTICS_APPBUILDRNET_OPT True Only change this value to True if you purchasedHyperion System 9 Windows Developer Toolkit.

Hyperion System 9 BI+ Application Builder J2EE Option

ANALYTICS_HABJ2EE_OPT True Only change this value to True if you purchasedHyperion System 9 BI+ Application Builder J2EEOption.

Hyperion System 9 BI+ Analytic Integration Connector forSAP BW Option



ANALYTICS_SAPINTEGCONN_OPT Only change this value to True if you purchasedHyperion System 9 BI+ Analytic Integration Connectorfor SAP BW Option.

Table 8 Hyperion System 9 Enterprise Analytics




ANALYTICS_BSO_OPT FALSE

ANALYTICS_CURRENCYCONV_OPT FALSE

ANALYTICS_PARTITIONING_OPT FALSE

ANALYTICS_BUSINESS_RULES_OPT FALSE






















ANALYTICS_VISEXPLORER_OPT TRUE Only change this value to True if you purchasedHyperion System 9 BI+ Visual Explorer Option.


ANALYTICS_HIGHAVAIL_OPT TRUE Only change this value to True if you purchasedHyperion System 9 BI+ Analytic High AvailabilityServices Option.


ANALYTICS_SSTOOLKIT_OPT TRUE Only change this value to True if you purchasedHyperion System 9 Windows Developer Toolkit.

ANALYTICS_APPBUILDRNET_OPT TRUE Only change this value to True if you purchasedHyperion System 9 Windows Developer Toolkit.


ANALYTICS_HABJ2EE_OPT TRUE Only change this value to True if you purchasedHyperion System 9 BI+ Application Builder J2EEOption.


ANALYTICS_SAPINTEGCONN_OPT TRUE Only change this value to True if you purchasedHyperion System 9 BI+ Analytic Integration Connectorfor SAP BW Option.

The following table contains the feature values to use when you purchase Enterprise Analyticsand Essbase, and you are deploying both in a single Essbase server/cluster.

Table 9 Hyperion System 9 Enterprise Analytics and Essbase Analytics





























ANALYTICS_VISEXPLORER_OPT TRUE Only change this value to True if you purchasedHyperion System 9 BI+ Visual Explorer Option.


ANALYTICS_HIGHAVAIL_OPT TRUE Only change this value to True if you purchasedHyperion System 9 BI+ Analytic High AvailabilityServices Option.


ANALYTICS_SSTOOLKIT_OPT TRUE Only change this value to True if you purchasedHyperion System 9 Windows Developer Toolkit.

ANALYTICS_APPBUILDRNET_OPT TRUE Only change this value to True if you purchasedHyperion System 9 Windows Developer Toolkit.




ANALYTICS_HABJ2EE_OPT TRUE Only change this value to True if you purchasedHyperion System 9 BI+ Application Builder J2EEOption.


ANALYTICS_SAPINTEGCONN_OPT TRUE Only change this value to True if you purchasedHyperion System 9 BI+ Analytic Integration Connectorfor SAP BW Option.

Table 10 All System 9 BI+ Modules (legacy product offerings)


BI+_BASESOLUTION TRUE

Hyperion System 9 BI+ Interactive Reporting

INTERRPTG_BASESOLUTION TRUE Only change this value to True if you purchased theHyperion System 9 BI+ Interactive Reporting module.

BI+ Impact Management Services

BI+_IMPACTASSMT_OPT TRUE Only change this value to True if you purchased BI+Impact Management Services.

BI+_IMPACTUPDATE_OPT TRUE Only change this value to True if you purchased BI+Impact Management Services.

System 9 BI+ Financial Reporting

FINANCRPTG_BASESOLUTION TRUE Only change this value to True if you purchased theSystem 9 BI+ Financial Reporting module.

Hyperion System 9 BI+ SAP BW Adapter for FinancialReporting & Web Analysis Option

FINANCRPTG_SAPBW_OPT TRUE Only change this value to True if you purchased HyperionSystem 9 BI+ SAP BW Adapter for Financial Reporting &Web Analysis Option.

WEBANLYSIS_SAPBW_OPT TRUE Only change this value to True if you purchased HyperionSystem 9 BI+ SAP BW Adapter for Financial Reporting &Web Analysis Option.

Hyperion System 9 BI+ Web Analysis

WEBANLYSIS_BASESOLUTION TRUE Only change this value to True if you purchased HyperionSystem 9 BI+ Web Analysis.

Hyperion System 9 BI+ SAP BW Adapter for FinancialReporting & Web Analysis Option



FINANCRPTG_SAPBW_OPT TRUE Only change this value to True if you purchased HyperionSystem 9 BI+ SAP BW Adapter for Financial Reporting &Web Analysis Option.

WEBANLYSIS_SAPBW_OPT TRUE Only change this value to True if you purchased HyperionSystem 9 BI+ SAP BW Adapter for Financial Reporting &Web Analysis Option.

Hyperion System 9 BI+ Production Reporting

PRODCTNRPTG_STNDALONE TRUE Only change this value to True if you purchased HyperionSystem 9 BI+ Production Reporting.

PRODCTNRPTG_HPITA_HPUX_OPT TRUE Only change this value to True if you purchased HyperionSystem 9 BI+ Production Reporting.

PRODCTNRPTG_RSC_HPUX_OPT TRUE Only change this value to True if you purchased HyperionSystem 9 BI+ Production Reporting.

PRODCTNRPTG_IBM_AIX_OPT TRUE Only change this value to True if you purchased HyperionSystem 9 BI+ Production Reporting.

PRODCTNRPTG_INTL_LNX_OPT TRUE Only change this value to True if you purchased HyperionSystem 9 BI+ Production Reporting.

PRODCTNRPTG_INTL_WIN_OPT TRUE Only change this value to True if you purchased HyperionSystem 9 BI+ Production Reporting.

PRODCTNRPTG_SPARC_SUN_O TRUE Only change this value to True if you purchased HyperionSystem 9 BI+ Production Reporting.

PRODCTNRPTG_SYBASE_OPT TRUE Only change this value to True if you purchased HyperionSystem 9 BI+ Production Reporting.

PRODCTNRPTG_ORACLE_OPT TRUE Only change this value to True if you purchased HyperionSystem 9 BI+ Production Reporting.

PRODCTNRPTG_INFORMIX_OPT TRUE Only change this value to True if you purchased HyperionSystem 9 BI+ Production Reporting.

PRODCTNRPTG_DDO_OPT TRUE Only change this value to True if you purchased HyperionSystem 9 BI+ Production Reporting.

PRODCTNRPTG_DB2_OPT TRUE Only change this value to True if you purchased HyperionSystem 9 BI+ Production Reporting.

PRODCTNRPTG_ODBC_OPT TRUE Only change this value to True if you purchased HyperionSystem 9 BI+ Production Reporting.

PRODCTNRPTG_TERADATA_OPT TRUE Only change this value to True if you purchased HyperionSystem 9 BI+ Production Reporting.

Hyperion System 9 BI+ SAP & SAP BW Adapter forProduction Reporting Option



PRODCTNRPTG_SAPBW_OPT TRUE Only change this value to True if you purchased HyperionSystem 9 BI+ SAP & SAP BW Adapter for ProductionReporting Option.

PRODCTNRPTG_SAPR3_OPT TRUE Only change this value to True if you purchased HyperionSystem 9 BI+ SAP & SAP BW Adapter for ProductionReporting Option.

Table 11 All System 9 BI Modules (new product offerings from Oracle)


BI+_BASESOLUTION TRUE

Hyperion Interactive Reporting – System 9

INTERRPTG_BASESOLUTION TRUE Only change this value to True if you purchased the HyperionInteractive Reporting – System 9 module.

BI+_IMPACTASSMT_OPT TRUE Only change this value to True if you purchased the HyperionInteractive Reporting – System 9 module.

BI+_IMPACTUPDATE_OPT TRUE Only change this value to True if you purchased the HyperionInteractive Reporting – System 9 module.

Hyperion Financial Reporting – System 9

FINANCRPTG_BASESOLUTION TRUE Only change this value to True if you purchased the HyperionFinancial Reporting – System 9 module.

FINANCRPTG_SAPBW_OPT TRUE Only change this value to True if you purchased the HyperionFinancial Reporting – System 9 module.

Hyperion Web Analysis – System 9

WEBANLYSIS_BASESOLUTION TRUE Only change this value to True if you purchased the Hyperion WebAnalysis – System 9 module.

WEBANLYSIS_SAPBW_OPT TRUE Only change this value to True if you purchased the Hyperion WebAnalysis – System 9 module.

Hyperion SQR Production Reporting – System 9

PRODCTNRPTG_STNDALONE PT TRUE Only change this value to True if you purchased Hyperion SQRProduction Reporting – System 9.

PRODCTNRPTG_HPITA_HPUX_OPT TRUE Only change this value to True if you purchased Hyperion SQRProduction Reporting – System 9.

PRODCTNRPTG_RSC_HPUX_OPT TRUE Only change this value to True if you purchased Hyperion SQRProduction Reporting – System 9.

PRODCTNRPTG_IBM_AIX_OPT TRUE Only change this value to True if you purchased Hyperion SQRProduction Reporting – System 9.



PRODCTNRPTG_INTL_LNX_OPT TRUE Only change this value to True if you purchased Hyperion SQRProduction Reporting – System 9.

PRODCTNRPTG_INTL_WIN_OPT TRUE Only change this value to True if you purchased Hyperion SQRProduction Reporting – System 9.

PRODCTNRPTG_SPARC_SUN_O TRUE Only change this value to True if you purchased Hyperion SQRProduction Reporting – System 9.

PRODCTNRPTG_SYBASE_OPT TRUE Only change this value to True if you purchased Hyperion SQRProduction Reporting – System 9.

PRODCTNRPTG_ORACLE_OPT TRUE Only change this value to True if you purchased Hyperion SQRProduction Reporting – System 9.

PRODCTNRPTG_INFORMIX_OPT TRUE Only change this value to True if you purchased Hyperion SQRProduction Reporting – System 9.

PRODCTNRPTG_DDO_OPT TRUE Only change this value to True if you purchased Hyperion SQRProduction Reporting – System 9.

PRODCTNRPTG_DB2_OPT TRUE Only change this value to True if you purchased Hyperion SQRProduction Reporting – System 9.

PRODCTNRPTG_ODBC_OPT TRUE Only change this value to True if you purchased Hyperion SQRProduction Reporting – System 9.

PRODCTNRPTG_TERADATA_OPT TRUE Only change this value to True if you purchased Hyperion SQRProduction Reporting – System 9.

PRODCTNRPTG_SAPBW_OPT TRUE Only change this value to True if you purchased Hyperion SQRProduction Reporting – System 9.

PRODCTNRPTG_SAPR3_OPT TRUE Only change this value to True if you purchased Hyperion SQRProduction Reporting – System 9.

Table 12 Hyperion System 9 Planning and Hyperion Planning – System 9


PLANNING_BASESOLUTION TRUE

PLANNING_OFFLINEUSE_OPT TRUE

Hyperion Workforce Planning and Hyperion System® 9Workforce Planning

PLANNING_WRKFORCEPLNG_OPT TRUE Only change this value to True if you purchasedHyperion Workforce Planning or Hyperion System® 9Workforce Planning.

Hyperion Capital Expense Planning and Hyperion System 9Capital Expense Planning



PLANNING_CAPEXPLNG_OPT FALSE Only change this value to True if you purchasedHyperion Capital Expense Planning or Hyperion System9 Capital Expense Planning.

Table 13 Hyperion System 9 Strategic Finance and Hyperion Strategic Finance


STRAGICFIN_BASESOLUTION TRUE

Hyperion System 9 Strategic Finance for Banking and Hyperion Strategic Finance for Banking

STRAGICFIN4BKG_BASESOLUTION TRUE

Table 14 Hyperion System 9 Financial Management and Hyperion Financial Management – System 9


FINANCIALMGT_BASESOLUTION TRUE

Table 15 Hyperion® System 9 Performance Scorecard and Hyperion Performance Scorecard – System 9


PERFSCORCRD_BASESOLUTION TRUE

Auditing UsageYou must audit services and users in accordance with your license agreement and the SoftwareCopy and Use Schedule.

To audit users, create a provisioning report. See “Generating Provisioning Reports” in theHyperion Security Administration Guide. A provisioning report provides a list of usersprovisioned to each application, either directly or through a group.

Retrieving License Keys for Data IntegrationManagementIf you have purchased licenses for Data Integration Management, retrieve full use license keysfrom the license_dim.doc file located within the .zip file titled “Hyperion 9.3.1 Start Here:License Files and Installation Documents” on the Oracle E-Delivery Web site.

ä To obtain the license_dim.doc file:

1 On the Oracle E-Delivery Welcome page, select a language if necessary and then click the link to continueto export validation.

Auditing Usage 65

2 Select the Hyperion Performance Management and BI product pack and a platform, and then clickGo.

3 Select Hyperion Performance Management and BI (9.3.x) Media Pack for the platform that you specified.

4 Click Download on the row for Hyperion 9.3.1 Start Here: License files and Installation Documents, andsave the file in a temporary directory.

5 Extract the contents of the downloaded file, including license_dim.doc, into the temporarydirectory.


6Planning Hyperion Product

Installations

In This Chapter

Planning Installations... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67

Preparing Databases ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71

Preparing Java Application Servers.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72

Planning InstallationsUse the following checklist to prepare for installing Hyperion products. Hyperion recommendsthat you review the checklist with your consultant at least one week prior to installation.Completing the checklist in advance of installation helps ensure a smoother, faster installation.

Table 16 Pre-installation Planning Checklist

Task Comments Check WhenCompleted ✓

Preparing the work area

Prepare a work area forconsultants who areassisting with theinstallation.

l Internet access—a direct connection outside the firewall

l Work area and computer (ideally located where the servers on which you are installingHyperion products are located), with network access

l Telephone

Ensure that you can accessthe Oracle® E-Delivery site.

Obtaining third-partylicenses

Obtain required third-partylicense keys.

Some third-party products require license keys or license files. Requesting and receivinga license key can require several days.

For Java application servers, consider which type of license works best for yourorganization. For example, you may not need a license for the highest level of functionality;a license for a lower level of functionality might meet your needs.

Preparing the software

Download the desired filesfrom the media packs for theproducts that you purchased.

Download from the Oracle® E-Delivery site.

Organize the files on the server and unzip compressed files.

Planning Installations 67

http://edelivery.oracle.com/



Ensure that the productsmeet release compatibilityrequirements.

See Chapter 4, “Release Compatibility.”

Install all third-partycomponents required byHyperion products.

For system requirements, see Chapter 3, “System Requirements.”

Ensure that you have obtained all licenses required by third-party software.

Validate that all third-partyproduct versions meetsystem requirements.

For system requirements, see Chapter 3, “System Requirements.”

Gathering requireddocumentation

Download the Hyperioninstallation and productdocumentation for theproducts that you purchased.

Download the following files from the Oracle® E-Delivery site:

l This guide, the Hyperion Installation Start Here

l Hyperion Shared Services Installation Guide

l The installation guides for the products you are installing

l Hyperion Security Administration Guide

l Hyperion Product SSL Configuration Guide, if you are using SSL

l Hyperion Installation and Configuration Troubleshooting Guide

l The documentation for the products you are installing

Preparing the hardware

Ensure that the necessaryhardware is available for yourdeployment architecture,and verify that the computersmeet system requirements.

For assistance in planning your deployment architecture, see the Hyperion System 9 BI+ Performance whitepaper, available on the Oracle Technology Network site. For systemrequirements, see Chapter 3, “System Requirements.”

Prepare each server for theHyperion productsinstallation.

l Update server software as needed. For example, ensure that any required servicepacks, hotfixes, and so on are installed.

l Disable unnecessary services.

If applicable, ensure that ITprepares the load balancer(hardware, software) or thefailover mechanism (such asVeritas Cluster Server).

Ensure that the load balancing or failover is tested and ready prior to starting theinstallation.

Check network bandwidthand latency for distant sitesand ensure that minimumrequirements are met.

Synchronize server time. When servers are not time synchronized, authentication errors that result in user accessproblems can occur between the Hyperion application servers.

68 Planning Hyperion Product Installations


http://www.oracle.com/technology/index.html


Arrange backupfunctionality.

After the installation, Hyperion advises that you perform a full backup of all servers anddatabases. After the initial backup, include servers and databases in daily backupprocedures.

Preparing databases

If necessary, install adatabase client.

l Set up database client access from the servers to the database setup.

l Set up user accounts to access the database.

l If you are using an Oracle database, test the database client with the TNSPingcommand.

If the database is installed, perform a full backup.

Prepare a database for eachHyperion product thatrequires a database forrelational storage.

To identify the products that require a database and to view the list of supporteddatabases, see Chapter 3, “System Requirements.”

For database considerations, see “Preparing Databases” on page 71 and theinstallation guides for the relevant products.

Test UDL connectivity to thedatabases you created, ifrequired for your product.

Preparing the securityinfrastructure

Collect the informationneeded to configure externaluser directories in UserManagement Console.

See “Configuring User Directories” in the Hyperion Security Administration Guide.

Note: If you are upgrading and want to support the movement of users and groupsacross Organizational Units (OUs), you must configure user directories in Shared Servicesto use a unique identity attribute to identify users and groups. See “Configuring UserDirectories” in the Hyperion Security Administration Guide.

For each server, prepare auser account withAdministrator rights. Theinstallation can be a localadministrator account.

l For Windows systems, create a user ID with Local Administrative rights to the machine.Hyperion recommends that you do not use the local system account to install.

l For UNIX systems, create a user account with Administrator privileges with controlover its area of the file system. The account that is used to install Hyperion productsmust have Read, Write, and Execute permissions on $HYPERION_HOME.

l Assign local policies as needed. (For Windows, the user ID typically requires “Act aspart of the OS, Bypass Traverse Checking, and Log-on as a batch job.”)

Create domain accounts.l DCOM account, if required for your product: hypdcom—domain user or system account

with local Administrator rights

l Hyperion administrator: hypadmin—domain user account

Planning Installations 69


Prepare a service account forexternal authenticationagainst the user directory youare using.

l Create a service account with Browse privileges for the user directory.

l Ensure that the service account name does not include special characters.

l Ensure that the service account's Distinguished Name (DN) can access the userdirectory.

l Note the user directory port.

l Be familiar with the name of a Primary Domain Controller that can access MSAD (ifapplicable).

l Ensure that the server can communicate with the user directory.

See the Hyperion Security Administration Guide.

If you are using securecommunication, ensureavailability of SSL certificatesfor all components. Hyperionrecommends using SSL forHyperion productinstallations.

See Hyperion Product SSL Configuration Guide.

Open firewall ports and fixdynamic ports if needed.

See Chapter 7, “Ports.”

If you are using OpenLDAP,consider whether you want toprovision by user or by group.If you are provisioning bygroup, decide whether to useOpenLDAP groups or externalauthentication providergroups.

See the Hyperion Security Administration Guide.

Setting up Java applicationservers and Web servers

Ensure that Java applicationservers are available forHyperion productdeployment. The applicationserver and the product thatyou are deploying must beinstalled on the samecomputer.

l To identify the products that require an application server and to view the list ofsupported application servers, see Chapter 3, “System Requirements.”

l A default product installation provides the Jakarta Tomcat Apache Web applicationserver.

l Ensure that you have obtained all required licenses.

l Ensure that you have root access to the application server installation directory. (ForWebSphere, you can set up security so that you can deploy without a root profile.See the WebSphere documentation for details.)

l For special considerations for each Java application server, see “Preparing JavaApplication Servers” on page 72.

Install a Web server to usewith Hyperion products thatrequire a Web server.

To identify the products that require a Web server and to view the list of supported Webservers, see Chapter 3, “System Requirements.”



If you are using software loadbalancing, in the Web server,prepare the load balancerplug-in to the Javaapplication server.

Resolving ports

Identify and resolve portconflicts.

Review the list of Hyperion product default ports in Chapter 7, “Ports.”

Preparing for productconfiguration

Collect the informationneeded to configure productsafter installation.

See Chapter 9, “Configuration Worksheets.”

Review your licenseagreement to confirm whichproducts you havepurchased and are licensedto use.

During configuration, activate or deactivate features based on your license agreement.After you configure each product, you must open registry.properties—in<Hyperion_Home>\common\config on the server on which you ran HyperionConfiguration Utility—to review and edit the product options. You must complete this stepto ensure you comply with your license agreement and to activate features you arelicensed to use. See Chapter 5, “Hyperion License Compliance.”

Before installing Hyperionproducts, consider thelocation of Hyperion Home.

When Hyperion products are installed, common internal and third-party components areinstalled to a central location, called Hyperion Home. Hyperion Home typically exists oneach computer within a Hyperion product deployment. The default location is C:\Hyperion (Windows) or ${Home/Hyperion} (UNIX).

On each computer, the Hyperion Home location is defined during the first productinstallation. Subsequent installations on a computer use the previously defined location.The location can be changed only by running a migration utility, so consider the locationcarefully.

Installing and configuringShared Services

Before installing otherHyperion products, installand configure SharedServices.

Shared Services is a shared infrastructure for Hyperion products. Shared Services providessecurity, authentication, user management, metadata management, and taskflowautomation.

Follow the instructions in the Hyperion Shared Services Installation Guide to install andconfigure Shared Services. See the Hyperion Security Administration Guide forinformation about configuring user directories.

Note: Some products do not require Shared Services.

Preparing DatabasesMany Hyperion products require a relational repository. Set up the databases and testconnectivity before installing Hyperion products.

Preparing Databases 71

General Considerationsl Database users must be assigned privileges to add, modify, and delete the following database

objects: tables, indexes, views, procedures, roles/authorities, sequences, and triggers. Also,users must be granted a role that assigns unlimited tablespaces. For Oracle databasesspecifically, users must be assigned the RESOURCE role.

l Some products require that you modify certain database parameters (for example, increasingheap size). See the product installation guides for detailed instructions on modifyingdatabase parameters.

l See the product installation guides for detailed procedures on creating databases.

Oraclel User IDs should have the following roles: CONNECT, RESOURCE, CREATE, CREATE

TRIGGER, DROP TRIGGER, MODIFY TRIGGER, CREATE PROCEDURE, ALTERSESSION.

l The UTF-8 character set must be set on both the client and the Oracle database.

l Install the Oracle Database full client.

IBM DB2The database must be created using UTF-8.

Preparing Java Application ServersMany Hyperion products require a Java application server.

General Considerationsl When deploying to an application server, Hyperion products cannot be installed to

directories with names that contain spaces; for example, c:\Program Files is notacceptable.

l Set all Web applications to have a session timeout that exceeds 10 minutes.

Apache Tomcatl Hyperion supports Apache Tomcat application server, which is provided on the installation

media for use with the deployment of Hyperion products. Hyperion does not supportApache Tomcat application server for use outside Hyperion product installations.


BEA WebLogicl If BEA WebLogic application server is not installed in BEA_HOME, Hyperion products

cannot be automatically deployed to WebLogic using Hyperion Configuration Utility. Ifyou install in such an environment, use the manual deployment option to create the Webarchive and use the WebLogic application deployment tool to deploy the application to therequired instance.

l The user account that installs and configures the Hyperion product being deployed musthave read and execute permission to the WebLogic installation directory.

IBM WebSpherel For WebSphere 6.0.2.11, install WebSphere 6.0 and update it first with Service Pack 2 and

then with Service Pack 11.

l On UNIX platforms, the user account that installs and configures the Hyperion productbeing deployed must have permission to create a WebSphere profile. Refer to the IBMInfoCenter for detailed instructions on granting permission to create a WebSphere profileas a non-root user.

l If WebSphere is installed as root, you must grant Write permissions to the WebSphereinstallation folder to enable Hyperion Configuration Utility to make required modificationsto WebSphere configuration files.

l Hyperion products cannot deploy to WebSphere if the WebSphere installation path containsspaces. The default WebSphere installation path for Windows is C:\Program Files\IBM\WebSphere. Change the installation path so that no spaces are included.

Oracle 10gEnsure that you have root access to the application server installation directory on AIX systems.

Preparing Java Application Servers 73


7Ports

In This Chapter

About Default Ports .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75

Shared Services Ports .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75

Essbase - System 9 Ports .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77

Reporting and Analysis Ports .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79

Financial Performance Management Applications Ports .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84

Data Management Ports .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89

About Default PortsDuring Hyperion product deployments, default port numbers for application servers areautomatically populated. During configuration, you can change the default numbers. Each portnumber must be unique. If an error message similar to “port already in use” or “bind error” isdisplayed, a port number conflict might exist.

If the default port number is not changed, the software is configured with the default values.

Shared Services PortsTable 17 Shared Services Web Application Ports

Port Type Default Port Number Where Configurable

Listen port 58080 Hyperion Configuration Utility

SSL listen port NA Application server administration console (configure manually)

Shutdown Port for Apache Tomcat 58081 Application server administration console (configure manually)

AJP connector port 58082 Application server administration console (configure manually)

About Default Ports 75

Table 18 Shared Services Default Service Ports

Service Default PortNumber

Where Configurable

Hyperion RemoteAuthenticationModule

58000 Hyperion Remote Authentication Module installation program

Additionaldynamic port (1)

Not configurable

OpenLDAP 58089l UNIX: <HSS_HOME>/openLDAP/startOpenLDAP.sh

l Windows: Run slapd -d 1 -f slapd.conf -h ldap://hostname:portnumber

l UNIX and Windows: CSS.xml:

<hub location="http://localhost:HSS Port">

<dirPort>openLDAP Port</dirPort>

</hub>

Changing the OpenLDAP PortUse this procedure if you want to run OpenLDAP on a non-default port. You cannot updatethe OpenLDAP port on the User Directories Management page in Shared Services.

ä To change the OpenLDAP port:

1 Go to the <HYPERION_HOME>/deployments/SharedServices9/AppServer/configdirectory. For example, if Shared Services is deployed on Tomcat, this directory, on Windows, could beC:\Hyperion\deployments\Tomcat5\SharedServices9\config

2 Edit the CSS.xml file and update the dirPort from the default 58089 to the custom port and saveit.

3 Do one of the following:

For Windows, change the OpenLDAP port in the Windows registry:

a. Go into regedit.

b. Go to HKEY_LOCAL_MACHINE\SOFTWARE\OpenLDAP\Parameters and change theUrls string value from ldap://:58089 to ldap://:<custom port>

For UNIX, change the OpenLDAP port in the start script:

a. Search for startOpenLDAP.sh under the <HYPERION_HOME> directory.

b. Edit the file by replacing the existing port (58089) with the custom port. Then save thechanges.

4 Restart OpenLDAP and Shared Services.

5 Restart all other System 9 products.

76 Ports

Essbase - System 9 Portsl “Essbase Ports” on page 77

l “Administration Services Ports” on page 77

l “Provider Services Ports” on page 78

l “Smart Search Ports” on page 79

Essbase PortsTable 19 Essbase Default Service Ports


Where Configurable

Essbase Agent 1423l Hyperion Configuration Utility

l Essbase configuration file (ARBORPATH\bin\Essbase.cfg)

Modify the file to include AgentPort.

For instructions, see the Essbase Technical Reference, “Essbase.cfg Configuration Settings.”

Essbase serverapplications(ESSSVR)

32768–33768 (twoports perprocess)

Essbase configuration file (ARBORPATH\bin\Essbase.cfg)

To limit the range and set the increment for these ports, modify the file to include these settings:ServerPortBegin, ServerPortEnd, PortInc

For instructions, see the Essbase Technical Reference, “Essbase.cfg Configuration Settings.”

IntegrationServices Server

3388 <AIS_HOME>/bin/ais.cfg

Add -Pportnumber

Administration Services PortsTable 20 Administration Services Web Application Ports

Port Type Default PortNumber

Where Configurable

Listen port 10080l Hyperion Configuration Utility

l Default Tomcat deployment: <aas_home>/deployments/tomcat/5.0.2.8/conf/server.xml

Parameter: Connector port

l Deployed Tomcat deployment (via Hyperion Configuration Utility): <Hyperion_Home>/deployments/<AppServNameAndVersion>/aas/conf/server.xml


l WebLogic and WebSphere: Application server administration console

Essbase - System 9 Ports 77


Where Configurable

SSL listenport

10090l Default Tomcat deployment: <aas_home>/deployments/tomcat/5.0.28/conf/

server.xml





Shutdownport forApacheTomcat

10081

For defaultTomcatdeployment only:10005



l Default Tomcat deployment: <aas_home>/deployments/tomcat/5.0.28/conf/server.xml



AJPconnectorport

10082

For defaultTomcatdeployment only:NA



l Default Tomcat deployment: NA


Provider Services PortsTable 21 Provider Services Web Application Ports


Where Configurable


l Default Tomcat deployment: <aps_home>/deployments/tomcat/5.0.28/conf/server.xml


l Deployed Tomcat deployment (via Hyperion Configuration Utility): <Hyperion_Home>/deployments/<AppServNameAndVersion>/aps/conf/server.xml



78 Ports


Where Configurable

SSL listenport

13090l Default Tomcat deployment: <aps_home>/deployments/tomcat/5.0.28/conf/

server.xml






13081

For defaultTomcatdeployment only:13005



l Default Tomcat deployment: <aps_home>/deployments/tomcat/5.0.28/conf/server.xml



AJPconnectorport

13082

For defaultTomcatdeployment only:NA



l Default Tomcat deployment: NA


Smart Search Ports

Table 22 Smart Search Web Application Ports


Where Configurable

Listen port 16080 Default Tomcat deployment: <Hyperion_Home>/deployments/tomcat5/conf/server.xml


SSL listen port NA NA

Shutdown port forApache Tomcat

16081 Default Tomcat deployment: <Hyperion_Home>/deployments/tomcat5/conf/server.xml

Parameter: Server port

AJP connector port NA NA

Reporting and Analysis Portsl “Foundation Ports” on page 80

Reporting and Analysis Ports 79

l “Financial Reporting Ports” on page 81

l “Interactive Reporting Ports” on page 82

l “Web Analysis Ports” on page 82

l “Workspace Ports” on page 83

l “Application Builder J2EE Ports” on page 83

l “Application Builder.NET Ports” on page 84

Foundation PortsTable 23 Reporting and Analysis Default Service Ports


Where Configurable

Foundation 6790 — 6810 See below for detail on each port.

Global Services Manager(GSM)

6800l Hyperion Configuration Utility

l <BIPLUS_HOME>/common/config/server.xml

<host>machine.domain</host>

<port>portNumber</port>

Core Service 6801

Name Service 6798l Hyperion Configuration Utility

l Remote Service Configurator. See the Hyperion Workspace Administrator's Guide.

l <BIPLUS_HOME>/common/config/config.dat

Parameter: Port

See the Hyperion Workspace Administrator's Guide.

l Service Broker

l Job Service

l Event Service

l Repository Service

l 6797

l 6796

l 6794

l 6795

Remote Service Configurator

See the Hyperion Workspace Administrator's Guide.

Table 24 Reporting and Analysis Web Server Port

Server Default Server Port Where Configurable

Apache and IBM 19000 <APACHE_HOME>/conf/httpd.conf

IIS and Oracle HTTP Server 80 Microsoft Internet Information Services (IIS) Manager Console. (Change the TCP portvalue setting.)

80 Ports

Financial Reporting PortsTable 25 Financial Reporting Web Application Ports

Port Type DefaultPortNumber

Where Configurable


SSL listenport

NA Application server administration console (configure manually)


8201 Application server administration console (configure manually).

Note: The port number depends on the listen port (listen port + 1).

AJPconnectorport

8202 <HYPERION_HOME>/common/httpserver/Apache/2.0.52/conf/HYSLWorkers.properties

worker.Financial_Reporting.host=hostname.company.com

worker.Financial_Reporting.port=portNumber

worker.Financial_Reporting.type=ajp13


Table 26 Financial Reporting Default Service Ports


Where Configurable

Financial Reporting Report Service Dynamic (2) <BIPLUS_HOME>/lib/fr_repserver.properties

Parameters: HRRepSvrPort1, HRRepSvrPort2

Financial Reporting SchedulerService

Dynamic <BIPLUS_HOME>/lib/fr_scheduler.properties

Parameter: HRSchdSvrPort

Financial Reporting Print Service Dynamic <BIPLUS_HOME>/lib/fr_printserver.properties

Parameter: HRPrintSvrPort

Financial Reporting CommunicationService

8299 <BIPLUS_HOME>/lib/fr_global.properties

Parameter: RMIPort

Additionaldynamic port (1)

Not configurable

Remote ADM Server port forPlanning datasource access

Dynamic HYPERION_HOME/common/ADM/VERSION/lib/ADM.properties fileon the Report Server machine

Parameter: ADM_RMI_SERVER_PORT


Interactive Reporting PortsTable 27 Interactive Reporting Default Service Ports

Service Default Port Number Where Configurable

Data Access Service (DAS) 6811, 6812 <BIPLUS_HOME>/common/config/irmconfig.xml

Default Ports = portNumber,portNumber

Interactive Reporting Service 6813, 6814 <BIPLUS_HOME>/common/config/irmconfig.xml

Default Ports = portNumber,portNumber

Job Service 6815 <BIPLUS_HOME>/common/config/irmconfig.xml

Default Ports = portNumber

Log Service 6810 <BIPLUS_HOME>/common/config/irmconfig.xml

Default Ports = portNumber

Web Analysis PortsTable 28 Web Analysis Web Application Ports


Where Configurable


Additionallisten ports(2)

Dynamic Not configurable

SSL listenport



16001 Application server administration console (configure manually).


AJPconnectorport


worker.Web_Analysis.host=hostname.company.com

worker.Web_Analysis.port=portNumber

worker.Web_Analysis.type=ajp13


82 Ports

Workspace PortsTable 29 Workspace Web Application Ports


Where Configurable


Additionallisten port (1)

Dynamic Not configurable

SSL listenport



45001 <BIPLUS_HOME>/AppServer/InstalledApps/Tomcat/5.0.28/Workspace/conf/server.xml

<Server port="portNumber" shutdown="SHUTDOWN">


AJPconnectorport


worker.Workspace.host=hostname.company.com

worker.Workspace.port=portNumber

worker.Workspace.type=ajp13


Application Builder J2EE PortsTable 30 Application Builder J2EE Web Application Ports


Where Configurable

Listen port 22080 Application server administration console (configure manually)

SSL listen port 22090 Application server administration console (configure manually)


22005 <HAB_INSTALL_DIR>/AppServer/InstalledApps/Tomcat/5.0.28/ApplicationBuilder/conf/server.xml

<Server port=”portNumber” shutdown=”SHUTDOWN”>



Application Builder.NET PortsTable 31 Application Builder.NET Web Application Ports




Shutdown port for Apache Tomcat 22081 Application server administration console (configure manually)


Financial Performance Management ApplicationsPortsl “Financial Management Ports” on page 84

l “Performance Scorecard Ports” on page 85

l “Planning Ports” on page 85

l “Strategic Finance Ports” on page 86

l “Performance Management Architect Ports” on page 86

Financial Management PortsTable 32 Financial Management Default Service Port


Where Configurable

FinancialManagementApplication Server

135 plusephemeralhigh-rangeports (1024–65536)

Windows settings—Fix DCOM ephemeral ports.

See the Microsoft support article describing how to set the ports used by DCOM: http://support.microsoft.com. Search for "restrict DCOM port."

Table 33 Financial Management Web Server Port

Web Server Port Where Configurable

80 (HTTP) or 443 (when SSL is enabled) In Microsoft Internet Information Services (IIS) Manager Console, change the TCP port valuesetting.

84 Ports

Performance Scorecard Ports

Table 34 Performance Scorecard Web Application Ports



l Application server administration console (configure manually)


Shutdown port for Apache Tomcat 18081l Hyperion Configuration Utility



AJP connector port 18082 Hyperion Configuration Utility


Table 35 Performance Scorecard Alerter Web Application Ports



l Application server administration console


Shutdown port for Apache Tomcat 18091l Hyperion Configuration Utility



AJP connector port 18092 Hyperion Configuration Utility


Planning Ports

Table 36 Planning Web Application Ports



Additional listen port (1) Dynamic Not configurable


Shutdown port for Apache Tomcat 8301 Application server administration console (configure manually)

AJP connector port 8302 Application server administration console (configure manually)

Financial Performance Management Applications Ports 85

Table 37 Planning Default Service Port

Service DefaultPortNumber

Where Configurable

PlanningRMI Server

11333 <HYPERION_HOME>/common/RMI/1.0.0/HyperionRMI_Port.properties

Parameter: registryPort

Note: If you change the port, you must run uninstallHyperionNTServiceRMI.cmd and then runinstallHyperionNTServiceRMI.cmd.

Strategic Finance PortsTable 38 Strategic Finance Default Service Port

Service DefaultPortNumber

Where Configurable

StrategicFinanceServer

7750 Strategic Finance administration tool

The default port value is in the registry. The key is in HKEY_LOCAL_MACHINE\Software\HyperionSolutions\HSFService\RPCPort. The value is a string item that contains the port number as text. Eachclient program includes a registry item (accessible with the Connect dialog box) to set port numbers for eachcontacted machine. The key for a client program connection to a server is HKEY_CURRENT_USER\Software\Hyperion Solutions\Hyperion Strategic Finance Servers\<machinename>\NetworkPort. It is also a string that contains a numeric value.

Performance Management Architect PortsTable 39 Performance Management Architect Web Application Ports


Where Configurable

Performance Management Architect UI

Listen port 19091 (canbe configuredfor SSL)

Hyperion Configuration Utility

86 Ports


Where Configurable

SSL listenport

19094 <HYPERION_HOME>/deployments/Tomcat5/EPMAWebTier/conf/server.xml

<Connector port=”<ssl_port>portNumber” disableUploadTimeout=”true”acceptCount=”100” debug=”0” scheme=”https” secure=”true”clientAuth=”false” sslProtocol=”TLS” algorithm=”“ keystoreFile=”“keystorePass=”JKS” keystoreType=”“/>

Parameters:

l algorithm: certificate algorithm

l keystoreFile: fully qualified path to the keystore file

l keystorePass: keystore password

l keystoreType: type of keystore, JKS is usually the default



l <HYPERION_HOME>/deployments/Tomcat5/EPMAWebTier/conf/server.xml

For parameters, see the application server documentation.

AJPconnectorport


l <HYPERION_HOME>/Deployments/Tomcat5/EPMAWebTier/conf/server.xml

<Connector port=”<ajp_port>portNumber” protocol=”AJP/1.3”

enableLookups=”false” debug=”0” />

Note: The connector tag should be added as a child of Server->Service tag.

Data Synchronizer Web Service (Performance Management Architect)

Listen port 19101 (canbe configuredfor SSL)

Hyperion Configuration Utility

SSL listenport

19104 <HYPERION_HOME>/deployments/Tomcat5/EPMADataSynchronizer/conf/server.xml

<Connector port=”<ssl_port>portNumber” disableUploadTimeout=”true”acceptCount=”100” debug=”0” scheme=”https” secure=”true”clientAuth=”false” sslProtocol=”TLS” algorithm=”“ keystoreFile=”“keystorePass=”JKS” keystoreType=”“/>

Parameters:

l algorithm: certificate algorithm

l keystoreFile: fully qualified path to the keystore file

l keystorePass: keystore password

l keystoreType: type of keystore, JKS is usually the default



l <HYPERION_HOME>/deployments/Tomcat5/EPMADataSynchronizer/conf/server.

xml

For parameters, see the application server documentation.

Financial Performance Management Applications Ports 87


Where Configurable

AJPconnectorport


l <HYPERION_HOME>/deployments/Tomcat5/EPMADataSynchronizer/conf/server.

xml

<Connector port=”<ajp_port>portNumber” protocol=”AJP/1.3”

enableLookups=”false” debug=”0” />

Note: The connector tag should be added as a child of Server->Service tag.

Table 40 Performance Management Architect Dimension Server Default Service Ports

Services DefaultPortNumber

Where Configurable

Server Manager 49500 BPMA_Server_Config.xml

<ServerManagerPort>portNumber</ServerManagerPort>

ProcessManager

49501 BPMA_Server_Config.xml

<Port>portNumber</Port>

web.config file under the webservices directory

<appSettings> parameter

<add key="ProcessManagerPort" value="portNumber"/>

EventSubscription

49502 BPMA_Server_Config.xml

<EventSubscriptionPort>portNumber</EventSubscriptionPort>

Event Manager 49503 BPMA_Server_Config.xml

<EventManagerPort>portNumber</EventManagerPort>

Job Manager 49504 BPMA_Server_Config.xml

<JobManagerPort>portNumber</JobManagerPort>

Engineinstances

51000–51999

BPMA_Server_Config.xml

<MinEnginePort>portNumber</MinEnginePort>

<MaxEnginePort>portNumber</MaxEnginePort>

Data AccessLayer (DB2only)

Dynamic BPMA_Server_Config.xml

Note: Performance Management Architect does not control which port DB2 uses. However, the portthat is used by DB2 can be specified in BPMA_Server_Config.xml so that Performance ManagementArchitect can connect to the database.

Table 41 Performance Management Architect Web Server Port


80 Microsoft Internet Information Services (IIS) Manager Console. (Change the TCP port value setting.)

88 Ports

Data Management Portsl “Data Integration Management Ports” on page 89

l “Translation Manager Ports” on page 90

l “FDM Ports” on page 91

l “Data Relationship Management Ports” on page 91

Data Integration Management PortsTable 42 Data Integration Management Web Services Hub Ports


Where Configurable

Listen port 7333 <WSH_HOME>, update the following files:

l config/WSHConfig.xml

<HubPortNumber>portNumber</HubPortNumber>

l WSH.wsdl

<wsdlsoap:address location="http://TCHIGATE1:portNumber/PowerCenter/services/Metadata"/>

<wsdlsoap:address location="http://TCHIGATE1:portNumber/PowerCenter/services/DataIntegration"/>

l jboss-3.2.1/server/default/deploy/jbossweb-tomcat.sar/META-INF/jboss-

service.xml

Parameter:

A HTTP/1.1 Connector on port portNumber

Note: See WebServicesProviderGuide.pdf, which is installed in /WSHub/docs.

SSL listenport

NA jboss-3.2.1/server/default/deploy/jbossweb-tomcat.sar/META-INF/jboss-service.xml

Parameter: SSL/TLS Connector configuration


NA NA

AJPconnectorport

8009 jboss-3.2.1/server/default/deploy/jbossweb-tomcat.sar/META-INF/jboss-service.xml

Parameter: AJP 1.3 Connector on port nnnn

Data Management Ports 89

Table 43 Data Integration Management Default Service Ports

Service Default Port Number Where Configurable

DataIntegrationManagementServer

4001l Hyperion Configuration Utility (if PowerCenter Server component is installed)

l INFA Workflow Manager (installed with the PowerCenter Client component)

l Native INFA PowerCenter Server Configuration Utility:

m Windows: <DIM_HOME>\Server\binpmsetup.exe (saves server configuration toWindows registry)

m UNIX: <DIM_HOME>/Server/binpmconfig (saves server configuration to the<DIM_HOME>/Server/bin/pmserver.cfg file)

DataIntegrationManagementRepositoryServer

5001

Separate port(between5002-65535) foreach repository in theRepository Server

l Hyperion Configuration Utility

l INFA PowerCenter Repository Server Configuration Utility:

m Windows: <DIM_HOME>\RepositoryServer\bin\PmRsSetup.exe (savesserver configuration to Windows registry)

m UNIX: <DIM_HOME>/RepositoryServer/binpmrsconfig (saves serverconfiguration to the <DIM_HOME>/RepositoryServer/bin/pmrepserver.cfg file)

Translation Manager PortsTable 44 Translation Manager Web Application Ports


Where Configurable


SSL listen port 14090 <TranslationManager_Home>/AppServer/InstalledApps/Tomcat/5.0.28/HTMServer/conf/server.xml



14005 Application server administration console (configure manually)

AJP connector port NA Application server administration console (configure manually)

Table 45 Translation Manager Default Service Port


Where Configurable

Translation ManagerRMI Server


l <HYPERION_HOME>/common/RMI/1.0.0/HyperionRMI_Port.properties

Parameter: registryPort

90 Ports

FDM Ports

Table 46 FDM Default Service Ports


Where Configurable

FDM loadbalancer FDMapplicationserver



For more information, see the Microsoft support article describing how to set the ports used by DCOM:http://support.microsoft.com. Search for "restrict DCOM port."

File sharing 137–139,445

Controlled by the operating system. Enable file sharing between all WebLink application servers andthe data server and set port numbers:

l NetBIOS Datagram Service = port 138

l NetBIOS Name Resolution = port 137

l NetBIOS Session Service = port 139

If NetBIOS is turned OFF, then use SMB = port 445

Firewall 135 plusephemeralhigh-rangeports (1024–65536)


For more information, see the Microsoft support article describing how to set the ports used by DCOM:http://support.microsoft.com. Search for "restrict DCOM port."

Table 47 FDM Web Server Port


80 (HTTP) or 443 (HTTPS) Microsoft Internet Information Services (IIS) Manager Console. (Change the TCP port value setting.)

Data Relationship Management Ports

Table 48 Data Relationship Management Default Service Port


Where Configurable

DataRelationshipManagement


l config.xml using the Data Relationship Management Console

l Windows settings—Fix DCOM ephemeral ports.

For more information, see the Microsoft support article describing how to set the ports used byDCOM: http://support.microsoft.com. Search for "restrict DCOM port."

Table 49 Data Relationship Management Web Server Ports

Web Server Ports Where Configurable

80 (HTTP) Microsoft Internet Information Services (IIS) Manager Console. (Change the TCP port value setting.)

443 (HTTPS)

Data Management Ports 91

92 Ports

8Changing Repository Passwords

In This Chapter

About Repository Password Maintenance ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93

Changing the Shared Services Repository Password ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93

Changing the Administration Services Repository Password... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94

Changing Reporting and Analysis Repository Passwords ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94

Changing Financial Performance Management Applications Repository Passwords ... . . . . . . . . . . . . .96

Changing Data Management Repository Passwords... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99

About Repository Password MaintenanceFor Hyperion products that require a database repository, you can change repository passwordsduring and after product deployments.

After changing database repository passwords, restart Hyperion products in the order specifiedin Appendix A, “Startup Dependencies and Default URLs.”

Caution! Change the password in the database used by Workspace only after you perform theprocedure in “Changing the Workspace Repository Password” on page 94. If otherHyperion products use the same database that Workspace uses, change theWorkspace repository password before changing the password of any other productrepository.

Changing the Shared Services Repository Password

ä To change the Shared Services repository password:

1 Stop all products registered with Shared Services.

2 Stop Shared Services.

3 In the database, change the password.

4 Run Hyperion Configuration Utility on the machine that hosts Shared Services.

5 Select the Shared Services option.

6 Select Configure Database.

About Repository Password Maintenance 93

7 Select the database type.

8 On the database configuration details panel, enter the new password.

9 When prompted, select to re-use the database.

10 Restart Shared Services according to the order specified in Appendix A, “Startup Dependencies andDefault URLs.”

Changing the Administration Services RepositoryPassword

ä To change the Administration Services repository password:

1 Stop Administration Services Console.

2 Stop Administration Services Server.


4 Run Hyperion Configuration Utility on the machine that hosts Administration Services.

5 Select the Administration Services option.

6 Select Configure Database.




10 Restart Administration Services according to the order specified in Appendix A, “Startup Dependenciesand Default URLs.”

Changing Reporting and Analysis RepositoryPasswordsl “Changing the Workspace Repository Password” on page 94

l “Changing the Financial Reporting Repository Password” on page 95

l “Changing the Web Analysis Repository Password” on page 95

Changing the Workspace Repository Password

Caution! Do not change the password in the database before you change the repositorypassword in Workspace.

94 Changing Repository Passwords

ä To change the Workspace repository password:

1 Back up the BIPlus/Common/Config folder.

2 From Remote Service Configurator, select Name Service, Repository Service, or Event Service.

Note: For information about Remote Service Configurator (RSC), see the HyperionWorkspace Administrator's Guide.

3 Click Show item properties, and select the Storage tab.

4 Change the password and click OK.

5 Repeat step 1 through step 3 for all Name Services, Repository Services, and Event Services with thesame database account. Ensure that you enter the same password for each one. If these services usedifferent database accounts, perform this step only for the services that use the account whose passwordyou are changing.

6 Close Remote Service Configurator.

7 In Local Service Configurator, click Show host properties, and select the Database tab.

8 Change the password and click OK.

This password property applies to all Local Service Configurator services on the local host,all of which use one database account.

9 Repeat step 6 and step 7 on every host that contains Local Service Configurator services, making certainto enter the password the same way each time.

10 If you are using the same database for row-level security, change the password for row-level securityfrom the Administer module.

11 Stop Interactive Reporting Base Service 1.

12 In the database, change the password, ensuring that it matches the password entered for Reportingand Analysis services.

13 Restart Interactive Reporting according to the order specified in Appendix A, “Startup Dependenciesand Default URLs.”

Changing the Financial Reporting Repository PasswordFinancial Reporting uses Workspace for connection information, so password changes forWorkspace apply to Financial Reporting.

Changing the Web Analysis Repository Password

ä To change the Web Analysis repository password:

1 Stop Web Analysis.


Changing Reporting and Analysis Repository Passwords 95

3 Go to <BIPLUS_HOME>\InstallableApps\config and back upWebAnalysis.properties.

4 Edit the WebAnalysis.properties file with the following changes:

l Change db.password-encrypted=true to db.password-encrypted=false.

l Set db.password= to the new database password.

Save and close the file.

5 In the <BIPLUS_HOME>\InstallableApps\config directory, runEncryptPasswordUtil.bat (Windows) or EncryptPasswordUtil.sh (UNIX).

6 Restart Web Analysis according to the order specified in Appendix A, “Startup Dependencies and DefaultURLs.”

Changing Financial Performance ManagementApplications Repository Passwordsl “Changing the Planning Repository Password” on page 96

l “Changing the Financial Management Repository Password” on page 97

l “Changing the Performance Management Architect Repository Password” on page 98

l “Changing the Performance Scorecard Repository Password” on page 99

Changing the Planning Repository PasswordPerform the following procedure on each Planning server.

ä To change the Planning repository password:

1 Stop Planning.


3 Run Hyperion Configuration Utility on the machine that hosts Planning.

4 Select the Planning option.

5 Select to configure the database.



8 Restart Planning according to the order specified in Appendix A, “Startup Dependencies and DefaultURLs.”

Perform the following procedure on one Planning server.


ä To change the Planning Applications repository password:

1 Stop Planning.


3 Run Hyperion Configuration Utility on the machine that hosts Planning.

4 Select the Planning option.

5 Select Data Source Configuration.

6 Select to edit the data source.

7 Select Data Source Name.



10 Enter Essbase connection information.

11 Restart Planning according to the order specified in the Appendix A, “Startup Dependencies and DefaultURLs.”

Changing the Financial Management Repository Password

ä To change the Financial Management repository password:

1 Stop Financial Management.


3 Edit UDL files directly to change the repository password:

l Double click on the UDL to open it.

l Use the Data Link properties editor to change the password.

Note: The UDL path is dependent on where the product is installed, for example:<installroot>\Hyperion\FinancialManagement.

Encrypting the Password

ä To encrypt the password:


2 In a command prompt, navigate to <installroot>\Hyperion\FinancialManagement\Server, and run EncryptHFMUDL.exe as follows: EncryptHFMUDL <Source.UDL><Dest.HFMUDL>

Note: The destination must have the extension .HFMUDL.

3 Run HFMConfigure.exe (located in <installroot>\Hyperion\FinancialManagement\Client) to switch to the new encrypted file.

Changing Financial Performance Management Applications Repository Passwords 97

4 Delete the existing UDL file or move it to a secure location.

5 Restart Financial Management according to the order specified in Appendix A, “Startup Dependenciesand Default URLs.”

ä To un-encrypt the password:


2 In a command prompt, navigate to <installroot>\Hyperion\FinancialManagement\Server, run EncryptHFMUDL.exe as follows:

a. EncryptHFMUDL <Source.HFMUDL> <FullPath\Dest.UDL>

b. If you intend to run with un-encrypted UDL:

i. Run HFMConfigure to switch to un-encrypted UDL.

ii. Delete the existing HFMUDL file or move it to a secure location.

iii. Restart Financial Management according to the order specified in Appendix A,“Startup Dependencies and Default URLs.”

c. If you are not planning to run with the un-encrypted UDL, restart FinancialManagement according to the order specified in Appendix A, “Startup Dependenciesand Default URLs.”

Changing the Performance Management ArchitectRepository Password

For the Performance Management Architect System Database

ä To change the Performance Management Architect repository password:

1 Stop all Performance Management Architect services.


3 Run Hyperion Configuration Utility on the machine that hosts Performance Management ArchitectDimension Server.

4 Select the Performance Management Architect option.





9 Restart Performance Management Architect according to the order specified in Appendix A, “StartupDependencies and Default URLs.”


For the Performance Management Architect Applications (Optional)

Note: Perform the following procedures if you are using the Interface Data Sourceconfiguration.

ä To change the Performance Management Architect Applications repository password:


2 Run Hyperion Configuration Utility.

3 Select the Performance Management Architect option.

4 Select Interface DataSource Configuration.

5 Enter Shared Services information.

6 Edit the existing DataSource link.



9 Enter Essbase connection information.


Changing the Performance Scorecard Repository Password

ä To change Performance Scorecard repository password:

1 Stop Performance Scorecard.


3 Run Hyperion Configuration Utility on the machine that hosts Performance Scorecard.

4 Select the Performance Scorecard option.





9 Restart Performance Scorecard according to the order specified in Appendix A, “Startup Dependenciesand Default URLs.”

Changing Data Management Repository Passwordsl “Changing the FDM Repository Password” on page 100

l “Changing the Data Relationship Management Repository Password” on page 100

l “Changing the Translation Manager Repository Password” on page 101

Changing Data Management Repository Passwords 99

Changing the FDM Repository Password

ä To change the FDM repository password using FDM Workbench:


2 From FDM Workbench, choose Add Application and log in.

3 Choose the application for which you want to change the repository and select Modify.

4 Select the Database tab and replace the existing password with the new password.

5 Click OK.

6 Click OK on the Application screen.

7 Ensure that you can log in to the application.

ä To change the FDM repository password using FDM Web:


2 From the FDM Web logon screen, choose Add Application and log in.

3 Choose the application for which you want to change the repository password and select Modify.

4 Click OK.

5 Click Close.

6 Ensure that you can log in to the application.

Changing the Data Relationship Management RepositoryPassword

ä To change the Data Relationship Management repository password:

1 Stop Data Relationship Management.


3 Open the Data Relationship Management console.

4 Go to Database Settings.

5 In Database Login, enter the new password.

6 To test the new password, select connect.

7 Enter the password again and select OK.

You should see a message, “Successfully connected to database.”

8 Restart Data Relationship Management according to the order specified in Appendix A, “StartupDependencies and Default URLs.”


Changing the Translation Manager Repository Password

ä To change the Translation Manager repository password:

1 Stop Translation Manager.


3 Run Hyperion Configuration Utility on the machine that hosts Translation Manager.

4 Select the Translation Manager option.



7 In the database configuration details panel, enter the new password.

8 Restart Translation Manager according to the order specified in the Appendix A, “Startup Dependenciesand Default URLs.”

Changing Data Management Repository Passwords 101


9Configuration Worksheets

In This Chapter

About Configuration... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Recommendations ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Product Options ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Shared Services Registration ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Relational Database Configuration ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Application Server Deployment .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Essbase ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Reporting and Analysis .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Performance Scorecard ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Strategic Finance... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Financial Management .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Performance Management Architect .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Planning... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

About ConfigurationHyperion Configuration Utility is installed with the first Hyperion product installation on eachmachine. You launch the utility after installation to configure installed products.

You can use the worksheets in this chapter (based on Hyperion Configuration Utility) to recordthe information required for your configuration process.

Standard configuration tasks:

l Product options—If supported by your product, select the features authorized by yourlicense agreement. See “Product Options” on page 104.

l Shared Services registration—Required for all products. See “Shared Services Registration”on page 104.

l Relational database configuration—Required for products that use a database to store andretrieve data. See “Relational Database Configuration” on page 105.

l Application server deployment—Required for products that deploy on an applicationserver. See “Application Server Deployment” on page 105.

l Specification of product-specific information:

m “Essbase” on page 106

About Configuration 103

m “Reporting and Analysis” on page 106

m “Performance Scorecard” on page 108

m “Strategic Finance” on page 109

m “Financial Management” on page 109

m “Performance Management Architect” on page 109

Tip: If errors occur, configure products individually and perform each configuration taskseparately. If errors still occur, refer to the Hyperion Installation and ConfigurationTroubleshooting Guide.

Note: To collect the information you need to configure external user directories to supportsingle sign-on and authorization in User Management Console, see the Hyperion SecurityAdministration Guide.

Recommendationsl Use the same application server, and domain or profile

l During configuration, enter only alphanumeric characters, dashes (-), dots (.) , underscores(_), and tildes (~). Tildes are only supported on Microsoft Windows. All other charactersare not supported.

Product OptionsOn the Product Options page, if appropriate, select the product features authorized by yourlicense agreement. See Chapter 5, “Hyperion License Compliance.”

During product configuration, Hyperion Configuration Utility copiesregistry.properties to <Hyperion_Home>\common\config on the server on which youran Hyperion Configuration Utility.

Important: After you configure each product, you must open registry.properties—in<Hyperion_Home>\common\config on the server on which you ran Hyperion ConfigurationUtility—to review and edit the product options. You must complete this step to ensure youcomply with your license agreement and to activate features you are licensed to use. See“Activating and Deactivating Product Features” on page 53.

Shared Services RegistrationApplies to all products that implement Shared Services functionality or plan to use SharedServices for security management and user provisioning. By default, the user you specify is pre-provisioned as admin. Thus, after configuration, you can log on to Shared Services usingadmin and password to create and provision users.

104 Configuration Worksheets

Field Description Your Information

Server name Computer (host) name for the Shared Services server

Port number Default or user-specified number

Must be unique and between 1025 and 65535.

Administrator username and password Shared Services Administrator username and password

SMTP mail server name Required only for Shared Services configuration and only for products thatuse taskflow management

SSL Enables use of Secure Sockets Layer to encrypt data. See the HyperionProduct SSL Configuration Guide.

Relational Database ConfigurationRequired for all products except Essbase - System 9, Smart View, Provider Services, and StrategicFinance.


Server name Computer name of the server that hosts the database

Port number Default port number

Name (SID for Oracle) Database name or the Oracle System identification (database instance)

User name and password Name and password of the database owner

Oracle: Data Tablespace Name of the tablespace that is used to create database tables (the logical portion of thedatabase used to allocate storage for table data).

Oracle: Index tablespace The name the existing tablespace that is used to create database indexes (the logicalportion of the database used to allocate storage for index data).

Application Server DeploymentRequired for products that deploy as Web applications to an application server. Exceptions areEssbase, Interactive Reporting, and SQR Production Reporting.


Location Path to the application server installation directory

Name Name of the server where you can access the deployed product

Port number Port number

Relational Database Configuration 105


WebLogic fields:1

WebLogic home Path to the WebLogic Home directory

WebLogic domain Name of the domain where you access the deployed product

WebSphere profile Name of the profile where you access the Web application (the web application for each deployedHyperion product uses this profile).

1A default user name and password of "hyperion" is automatically used during deployment.

EssbaseRequired to configure Essbase as a Windows service.


User Name Essbase Server system administrator user name

Password Essbase Server system administrator password

Company Name Your company name

Service Name Identifier Description that is used in the service display name

Agent Port Number Essbase Server agent port number (default—1423)

Application Start Port First port number that Essbase Server can use (default—32768)

Application End Port Highest port number that Essbase Server can use (default—33768)

Reporting and Analysisl “Workspace” on page 106

l “Financial Reporting” on page 107

l “Interactive Reporting” on page 107

l “SQR Production Reporting Engine for Interactive Reporting (Optional)” on page 108

Workspace


For Context path Part of the URL that accesses the deployed Web application

For GSM GSM host name and GSM port



Ports used by Core Services (other than the default)l Core Service (default —6801)

l Name Service (default—6798)

l GSM (default—6800)

l Service Broker (default—6797)

l Job Service (default—6796)

l Event Service (default—6794)

l Repository Service (default—6795)

Financial Reporting


Workspace, Print Service, and Scheduler Service Configuration locations

Workspace Web Application URL URL that end users use to access Workspace

Financial Reporting Print Service computers Comma-separated list of Print Server computers

Financial Reporting Scheduler Service Host name of the computer where Scheduler is installed

Report Server Configuration

Financial Reporting Server Location Hostname of computer where Report Server is installed

Interactive Reporting


For Shared Services users

Interactive Reporting URL URL to access Shared Services

Application Name of Interactive Reporting Name of the Interactive Reporting application

Project Interactive Reporting Project identification

For Clustered Deployment

Shared Directory Shared directory of clustered deployment

Local Directory Local directory of Interactive Reporting

For Interactive Reporting Alerter

Host Alerter host name

Port Alerter port number



Logon and password Username and password

Return E-mail Return E-mail address

SQR Production Reporting Engine for Interactive Reporting(Optional)


Oracle's Hyperion® SQR® ProductionReporting – System 9 binary folder,according to the selected repository type

l Oracle: <BIPLUS_HOME>\Server\Oracle\bin

l MS: SQL:<BIPLUS_HOME>\Server\ODBC\bin

l IBM: DB2:<BIPLUS_HOME>\Server\DB2\bin

MS SQL client home MS SQL client home

Repository connection stringl Oracle: TNS name

l MS SQL: ODBC name

l IBM DB2: Database alias registered by Client Configuration Assistant

Performance ScorecardRequired for clustered application server deployment.


For Shared Services registration:

Performance Scorecard URL URL of the computer to which you deploy Performance Scorecard

Performance Scorecard Application Name Name of the Performance Scorecard application to register with SharedServices

Performance Scorecard Project Project name for Performance Scorecard that you use in SharedServices

Use Shared Services for User Management Creates users in Shared Services for use in other Hyperion applications

Use Shared Services Directory Definitions Authenticates Performance Scorecard users who use Shared Services

For clustered deployment:

Shared directory Shared drive that all computers in the cluster can access

Local directory Directory created to contain temporary files


Performance Scorecard Alerter


Host and Port Name and port number (default 25) of the computer that hosts the e-mail server

ID and Password Logon ID and password used to log on to the e-mail server

Return E-mail Address Address to which undelivered alert notifications are sent

Strategic FinanceRequired to customize Strategic Finance with Shared Services.


Oracle's Hyperion® Strategic Finance Server Application name Application name

Oracle's Hyperion® Strategic Finance Server Instance ID Server instance ID

Financial ManagementAfter running Hyperion Configuration Utility, run Financial Management ConfigurationUtility. See the Hyperion Financial Management – System 9 Installation Guide.

Performance Management ArchitectTo enable configuration of Performance Management Architect, Microsoft InternetInformation Services (IIS) and .NET Framework 2.0 must be installed on the computer thathosts the Dimension Server.

PlanningRequired for Product Instance Registration:


Instance Name A name to describe the group of applications in that instance.

Web Tier Host Name Full name of machine where you installed the Web server component.

Server port Defaults to 8300. Change if necessary to port used for application server deployment.

Required for Data Source Configuration:

Strategic Finance 109


Datasource Name and Datasource Description Enter a name for the datasource you are creating and anydescription to help identify it.

Instance Name The instance you want associated with this data source.

Database Details: Server Database server

Database Details: Port Database port (defaults depending on which database you areusing (Oracle-1521; SQL-1433; DB2–50000)

Database Details: Product Name of the product you are configuring (i.e. Planning)

Database Details: Database Name of Planning database

Database Details: User Planning database username

Database Details: Password Planning database password

Essbase Server Details: Server Essbase Server name

Essbase Server Details: User Essbase Server user name

Essbase Server Details: Password Essbase Server password


10Installation Sequence

In This Chapter

About Installation Sequence... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

General Tasks ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Shared Services Tasks... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Essbase - System 9 Tasks ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Planning Tasks ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Financial Management Tasks ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Reporting and Analysis Tasks ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Performance Scorecard Tasks ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Strategic Finance Tasks ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Data Relationship Management Tasks... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

FDM Tasks ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Data Integration Management Tasks... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

User Provisioning .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

About Installation SequenceHyperion recommends that you install and configure products in the documented order.However, you can install multiple products simultaneously and then configure the products inthe documented order. If you install multiple products on one computer, use HyperionConfiguration Utility to configure the products simultaneously.

Before installing products, see the list of required Hyperion software in Chapter 3, “SystemRequirements” for that product to determine the parts of the sequence that you should follow.

Note: Upgrading from a previous release is not described in this chapter, although the sequencefor upgrading Hyperion products is approximately the same as what is presented in this section.For detailed upgrade procedures for individual products, see the product installation guides.

Note: When configuring products using Hyperion Configuration Utility, a Product Optionspanel might be displayed if you need to select product features that you are licensed touse per your license agreement.

About Installation Sequence 111

General Tasks

TASK EXCEPTION

Install and configureShared Services, andconfigure userdirectories forexternalauthentication.

Data Integration Management and FDM

Note: Data Relationship Management uses Shared Services only for external authentication. Data IntegrationManagement can use Shared Services or Informatica native authentication.

Assign roles andprovision users inShared Services.

FDM, Data Relationship Management, and Data Integration Management (for Shared Services authentication; notfor Informatica native authentication).

Shared Services Tasks

TASK REFERENCE

Install Shared Services

1. Navigate to the directory where you downloaded the product installation files.

2. Run the EXE or BIN file.

3. Select a Typical or Custom installation.

“Installing Shared Services” in theHyperion Shared ServicesInstallation Guide

Configure Shared Services

1. Start Hyperion Configuration Utility.

2. Perform these tasks:

a. Configure the database.

b. Automatically (recommended) or manually deploy to the application server.

c. Optional: Configure the mail server.

Note: Database configuration and application server deployment must be performed togetherthe first time Shared Services is configured.

“Configuring Shared Services” inthe Hyperion Shared ServicesInstallation Guide

Optional: Enable Shared Services for SSL

Enable Shared Services and the user directory for SSL. Hyperion Product SSLConfiguration Guide

Configure User Directory for External Authentication

1. Start the Shared Services server, and launch User Management Console.

2. Configure a supported user directory, such as LDAP or MSAD.

3. If you are using Netegrity SiteMinder, install Oracle's Hyperion® Remote Authentication Module™and configure Shared Services to use Single Socket Layers.

4. Identify your administrators from the user directory, and provision them with the Shared ServicesAdministrator role.

“Installing Shared Services” in theHyperion Shared ServicesInstallation Guide

Hyperion Security AdministrationGuide

112 Installation Sequence

Essbase - System 9 TasksEssbase - System 9 includes these products:

l Essbase



l Provider Services

Note: To identify the Essbase - System 9 products that are required for other Hyperion products,see Chapter 3, “System Requirements.”

TASK REFERENCE

Install Essbase - System 9 Products


2. Run the appropriate setup file.

3. Install Essbase - System 9 products in this order:

a. Essbase client1

b. Essbase Server

c. Administration Services

d. Integration Services

e. Provider Services and Smart View2

The installation chapters inthe relevant productinstallation guides

Configure Essbase - System 9 Products

1. Start Shared Services Server.


3. As required:

a. Register products with Shared Services (required for Essbase, Administration Services3 , andProvider Services).

b. Configure the database repository (required for Administration Services4 and Integration Services).

c. Automatically (recommended) or manually deploy to a Java application server (required forAdministration Services and Provider Services).

4. Perform other configuration tasks as directed by the product installation guides.

5. After you configure each product, you must open registry.properties—in <Hyperion_Home>\common\config on the server on which you ran Hyperion Configuration Utility—to review and editthe product options. You must complete this step to ensure you comply with your license agreementand to activate features you are licensed to use. See “Activating and Deactivating Product Features”on page 53.

The configuration chapters inthe relevant productinstallation guides

Optional: Enable Administration Services, Essbase, or Provider Services for SSL

Enable Administration Services for SSL. Hyperion Product SSLConfiguration Guide

Essbase - System 9 Tasks 113

TASK REFERENCE

Enable Integration Services

l For Essbase and Administration Services, enable Integration Services.

l If using SQL Interface or Hybrid Analysis, verify that you have a license for them.

“Configuring Essbase forRelational Integration” in theHyperion Essbase - System 9Installation Guide

1On UNIX platforms, when installing Essbase client and server components on the same computer, install the client first and then the server.2The Smart View installation program is distributed in the Provider Services installation image in the <APS_INSTALL>/redist folder.To install Smart View, you must run the Smart View executable separately from the Provider Services installation program. The Smart Viewinstallation program is also available from the Oracle® E-Delivery site. Smart View can be used to connect to Essbase as a data source only ifProvider Services and Essbase are installed and running.3If using Administration Services to administer an instance of Essbase that is registered with Shared Services, you must register AdministrationServices.4If you plan to use Log Analyzer, a database repository is required for Administration Services.

Planning TasksThe Planning sequence assumes that you installed and configured Shared Services, Essbase, andAdministration Services and created a database for Planning and optionally, a database forPerformance Management Architect. The Planning setup program can install PerformanceManagement Architect.

Note: Microsoft Internet Information Services (IIS) and .NET Framework 2.0 must be installedon the machine that hosts the Performance Management Architect Dimension server.If .NET Framework is not installed on the machine, it is installed automatically.

TASK REFERENCE

Install Planning



3. If installing on Windows 32-bit, select Typical to install the Planning Web Server, Planning ADM Driver,and Performance Management Architect components.

Note: If you are using Classic Application Administration instead of Performance Management Architect,select Custom and select only the Planning Web Server component. Individual components can beinstalled on different machines.

4. If installing on Windows 64-bit or UNIX, Performance Management Architect must be installed on aWindows 32-bit machine.

“Installing Database TierComponents” and“Installing the PlanningMiddle Tier” in theHyperion Planning -System 9 InstallationGuide

Configure Planning



TASK REFERENCE

1. Start Shared Services Server and Essbase Server.


3. Register with Shared Services.

4. Automatically (recommended) or manually deploy to an application server.

5. Configure a database.

6. Register a product instance.

Note: Return to the product selection panel before configuring a data source.

7. Configure a data source.

8. If you are using Performance Management Architect, for Performance Management Architect:

Note: Performance Management Architect must be configured on a Windows 32–bit machine.

a. Register with Shared Services.

b. Configure a database.

c. Automatically (recommended) or manually deploy to an application server.

d. Optional: Configure interface data sources. (Not necessary for initial installation and configuration.See the Hyperion Enterprise Performance Management Architect Administrator's Guide.)

“Configuring Planning” inthe Hyperion Planning -System 9 InstallationGuide for Windows

Perform Post-Configuration Tasks

1. After you configure each product, you must open registry.properties—in <Hyperion_Home>\common\config on the server on which you ran Hyperion Configuration Utility—to review and edit theproduct options. You must complete this step to ensure you comply with your license agreement and toactivate features you are licensed to use. See “Activating and Deactivating Product Features” on page53.

2. Install and configure Workspace.

Note: You can install and configure Financial Reporting and Web Analysis at the same time.

3. Complete Shared Services tasks.

4. If you are using Performance Management Architect, verify the Performance Management Architectinstallation.

5. Create an application using either Performance Management Architect or Classic ApplicationAdministration.

6. Verify the Planning installation.

7. Optional: Install one or more additional products:

l Oracle's Hyperion® Smart View for Office (required if using Offline Planning)

l Offline Planning

l Oracle's Hyperion® Data Integration Management Adapter for Planning

l Planning Adapter

l Financial Reporting and Web Analysis

“Post Configuration Tasks”in the Hyperion Planning -System 9 InstallationGuide

Optional: Enable Performance Management Architect and Planning for SSL

Enable Performance Management Architect and Planning for SSL. Hyperion Product SSLConfiguration Guide

Planning Tasks 115

Financial Management Tasks

TASK REFERENCE

Install Financial Management


2. Run the EXE file.

3. Select the components to install:

l To install on the server, select “Custom” and select all components you want to install, includingPerformance Management Architect.

Note: If you are using Performance Management Architect, Microsoft Internet Information Services(IIS) must be installed on the machine that hosts the Performance Management Architect Dimensionserver. .NET Framework 2.0 is also required but will be installed automatically if not detected.

l To install on the client, select “Typical”, and select the client components.

Performance Management Architect is included in a Typical install.

“Installing FinancialManagement ServerComponents” and“Installing the Client TierComponents” in theHyperion FinancialManagement – System 9Installation Guide

Configure Financial Management



3. For Financial Management:


b. Perform Financial Management configuration tasks that set up users and register FinancialManagement servers.

c. Perform tasks that are specific to Financial Management and Performance Management Architectto create a Financial Management instance.

4. If you are using Performance Management Architect, for Performance Management Architect:

a. Select Performance Management Architect.

b. Register with Shared Services.

c. Configure a database.

d. Automatically (recommended) or manually deploy to an application server.

e. Optional: Configure interface data sources. (Not necessary for initial installation and configuration.See the Hyperion Enterprise Performance Management Architect Administrator's Guide for moreinformation.)

“Configuring and Setting UpFinancial Management” inthe Hyperion FinancialManagement – System 9Installation Guide



TASK REFERENCE

1. After you configure each product, you must open registry.properties—in <Hyperion_Home>\common\config on the server on which you ran Hyperion Configuration Utility—to review and editthe product options. You must complete this step to ensure you comply with your license agreement andto activate features you are licensed to use. See “Activating and Deactivating Product Features” on page53.

2. Install and configure Workspace.

Note: You can install and configure Financial Reporting at the same time.

3. Complete Shared Services tasks.

4. If you are using Performance Management Architect, verify the Performance Management Architectinstallation.

5. Create an application view in Performance Management Architect or create an application using ClassicApplication Administration.

6. Verify Financial Management installation.

“Post Configuration Tasks”in the Hyperion FinancialManagement – System 9Installation Guide

Optional: Enable Performance Management Architect and Financial Management for SSL

Enable Performance Management Architect and Financial Management for SSL. Hyperion Product SSLConfiguration Guide

Reporting and Analysis Tasks

TASK REFERENCE

Install Reporting and Analysis

On each applicable computer:

1. If you are using Financial Management as a data source, first install the FinancialManagement ADM driver on the computer. Run the Financial Management installer andselect only the ADM Driver option.


3. Run the appropriate EXE or BIN file for each Reporting and Analysis installer:

l Services

l UIServices

l Client

l Production Reporting

l Migrator

Note: To install Workspace, you must run the Services and UIServices installers.

4. Select the components to install.

“Installing Reporting and Analysis” in theHyperion Reporting and Analysis – System 9Installation Guide for Windows and theHyperion Reporting and Analysis – System 9Installation Guide for UNIX

Configure Reporting and Analysis

Reporting and Analysis Tasks 117

TASK REFERENCE



3. For Reporting and Analysis:


b. Configure the database.

c. Automatically (recommended) or manually deploy to the application server.

d. Complete module-specific configurations.

“Configuring Reporting and Analysis” in theHyperion Reporting and Analysis – System 9Installation Guide for Windows and theHyperion Reporting and Analysis – System 9Installation Guide for UNIX

“Manually Deploying to an ApplicationServer” in the Hyperion Reporting andAnalysis – System 9 Installation Guide forWindows and the Hyperion Reporting andAnalysis – System 9 Installation Guide forUNIX


1. After you configure each product, you must open registry.properties—in<Hyperion_Home>\common\config on the server on which you ran HyperionConfiguration Utility—to review and edit the product options. You must complete thisstep to ensure you comply with your license agreement and to activate features youare licensed to use. See “Activating and Deactivating Product Features” on page 53.

2. For Web Analysis: If you are using an RDBMS as a data source or for Relational Drill-through, add the necessary drivers.

3. Set up Netegrity SiteMinder with Transparent Logon.

4. Verify the order of starting services.

5. Provision the Reporting and Analysis administrator user.

6. Launch Reporting and Analysis modules.

“Post Configuration Tasks” in the HyperionReporting and Analysis – System 9Installation Guide for Windows and theHyperion Reporting and Analysis – System 9Installation Guide for UNIX

Optional: Enable Reporting and Analysis for SSL

Enable Reporting and Analysis for SSL. Hyperion Product SSL Configuration Guide

Performance Scorecard Tasks

TASK REFERENCE

Install Performance Scorecard




Note: If you want to install Performance Scorecard Alerter or File Import/Export, you must select“Custom”.

“Installing Performance Scorecardand Components” in the HyperionPerformance Scorecard - System 9Installation Guide

Configure Performance Scorecard


TASK REFERENCE



3. For Performance Scorecard:

a. Configure the database.

b. Automatically deploy (recommended) or manually deploy to an application server.

c. Register with Shared Services.

4. After you configure each product, you must open registry.properties—in <Hyperion_Home>\common\config on the server on which you ran Hyperion Configuration Utility—toreview and edit the product options. You must complete this step to ensure you comply with yourlicense agreement and to activate features you are licensed to use. See “Activating andDeactivating Product Features” on page 53.

“Configuring PerformanceScorecard” and “ManualApplication Server DeploymentTasks” in the HyperionPerformance Scorecard - System 9Installation Guide

Optional: Enable Performance Scorecard for SSL

Enable Performance Scorecard for SSL. Hyperion Product SSLConfiguration Guide

Strategic Finance Tasks

TASK REFERENCE

Install Strategic Finance



3. Select the Strategic Finance server or client component.

“Server Installation” or “ClientInstallation” in the Hyperion StrategicFinance Installation Guide

Configure Strategic Finance


Note: Shared Services may not be used in all Strategic Finance implementations.


3. For Strategic Finance:


b. Migrate users toShared Services.

4. After you configure, you must open registry.properties—in <Hyperion_Home>\common\config on the server on which you ran Hyperion Configuration Utility—to reviewand edit the product options. You must complete this step to ensure you comply with yourlicense agreement and to activate features you are licensed to use. See “Activating andDeactivating Product Features” on page 53.

“Configuring and Setting Up StrategicFinance” in the Hyperion StrategicFinance Installation Guide

Connect the Strategic Finance Client to the Server “Connecting a Client to a StrategicFinance Server and Database” in theHyperion Strategic FinanceInstallation Guide

Strategic Finance Tasks 119

Data Relationship Management TasksYou do not need to provision users, because this product uses Shared Services only for externalauthentication.

TASK REFERENCE

Install Data Relationship Management on the Server


2. Run the EXE file for the server component or the client component.

“Installing Server Components”or “ Installing ClientComponents” in the HyperionData Relationship ManagementNTier Installation Guide

Configure Data Relationship Management

Data Relationship Management does not use Hyperion Configuration Utility.

1. On the primary Data Relationship Management server, install Shared Services.

2. Launch the Data Relationship Management Console.

3. Configure database setting.

4. Configure Shared Services connectivity settings and system classpaths. Click Enable CSS.

Note: Paths between Shared Services 9.2 and Shared Services 9.3 are different.

Note: This step is only required if you are using external or mixed authentication through CSS. Ifyou are using Data Relationship Management internal authentication, you can skip this step.

5. Configure engine servers and Web servers.

6. Start the Data Relationship Management service.

“Configuring Data RelationshipManagement” in the HyperionData Relationship ManagementNTier Installation Guide

FDM TasksYou do not need to provision users, because this product does not require Shared Services.

TASK REFERENCE

Install FDM

1. Navigate to the directory where you downloaded the productinstallation files.


“Installation” in the Hyperion Financial Data QualityManagement Installation Guide

Configure FDM


TASK REFERENCE

FDM does not use Hyperion Configuration Utility.

1. Configure these components:

l Web server

l Application server

l Load balancer

l Workbench

2. Create an FDM application.

3. Install and configure adaptors to integrate FDM with the targetapplication.

Chapters 4 – 8 of the Hyperion Financial Data QualityManagement Installation Guide

“Creating a New FDM Application” in the Hyperion FinancialData Quality Management Installation Guide

“Configuring Adapters” in the Hyperion Financial Data QualityManagement Installation Guide

Data Integration Management TasksThis product can use Shared Services for external authentication or Data IntegrationManagement configured for native Informatica authentication. This product does not requireuse of Shared Services to provision users.

TASK REFERENCE

Install Data Integration Management




“Installing and Uninstalling Data IntegrationManagement” in the Hyperion Data IntegrationManagement Installation Guide

Configure Data Integration Management

1. If you are using Shared Services for external authentication, start Shared ServicesServer.


3. Optional: Register with Shared Services.

4. Configure Data Integration Management.

5. Synchronize users.

“Configuring and Setting Up Data IntegrationManagement” in the Hyperion Data IntegrationManagement Installation Guide

User Provisioning The following tasks can be performed only by a Shared Services administrator.

Note: If using Data Relationship Management, FDM, or Data Integration Management, you donot have to perform these tasks to provision users.

Data Integration Management Tasks 121

TASK REFERENCE

Perform one or more actions:

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

l For each application, assign the Provisioning Manager role to users who are responsible for assigning roles andaccess control permissions to users of the application.

l Assign the Directory Manager role to users who are responsible for managing the native Shared Services directory.

Project Managers can create projects and add applications to projects as necessary.

Provisioning Managers for applications can provision users and groups (assign roles and access control permissions)for their applications.

Hyperion SecurityAdministrationGuide


AStartup Dependencies and

Default URLs

In This Appendix

Summary List of Services and Processes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Services and Processes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Default URLs... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Summary List of Services and ProcessesThe following Hyperion product services and processes are listed below, in their recommendedstartup order.

1. Databases for repositories. (For a list of Hyperion products that require a repositorydatabase, see Chapter 3, “System Requirements.”.)

2. Shared Services OpenLDAP

3. Shared Services application server

4. Reporting and Analysis Core Services

5. Performance Management Architect Services

6. Oracle's Hyperion® Essbase® – System 9

7. Administration Services application server

8. Oracle's Essbase® Integration Services

9. Provider Services application server

10. Reporting and Analysis (in the following order):

a. Oracle's Hyperion® Interactive Reporting – System 9

b. Financial Reporting

c. Reporting and Analysis Web server

d. Workspace application server

e. Oracle's Hyperion® Web Analysis – System 9 application server

11. Application server services or processes (in any order):

l Performance Management Architect application server

l Performance Management Architect Data Synchronizer application server

l Financial Reporting application server

Summary List of Services and Processes 123

12. Remaining services (in any order):

l Planning application server


l Oracle's Hyperion® Strategic Finance

l Performance Scorecard application server

l Performance Scorecard Alerter application server


l FDM

l Oracle's Hyperion® Data Integration Management

l Oracle's Hyperion® Translation Manager

Services and ProcessesThe services and processes discussed in this topic are listed in the order in which Hyperionrecommends they are started.

1. Shared Services OpenLDAP

Table 50 Shared Services OpenLDAP Service/Process

Windows Start Menu Command: NA

Registered Service Name: OpenLDAP-slapd

Display Name in Windows Control Panel: Hyperion S9 OpenLDAP

Description: Provides support to access the Oracle's Hyperion® Shared Services OpenLDAP repository

Windows Startup Script: <HSS_HOME>\openLDAP\StartService.bat

UNIX Startup Script: <HSS_HOME>/openLDAP/startOpenLDAP.sh

2. Shared Services Application Server

Table 51 Shared Services Application Server Services/Processes

Windows StartMenuCommand:

Start > Programs > Hyperion > Foundation Services > Start Shared Services

RegisteredService Name:

HyS9Shared Services

124 Startup Dependencies and Default URLs

Display Name inWindowsControl Panel:

Hyperion S9 Shared Services

Description: Hyperion Shared Services that support Hyperion applications, including authentication, user provisioning, task flowmanagement, and data and metadata synchronization

WindowsStartup Script:

l Tomcat, WebSphere, and WebLogic 9: <Hyperion_Home>\deployments\<AppServNameAndVersion>\bin\startSharedServices9.bat

l WebLogic 8: <HSS_Home>\AppServer\InstalledApps\<AppServName>\<Version>\SharedServices9\startSharedServices9.bat

l Oracle: <OracleInstallDir>\bin\emctl start iasconsole

<OracleInstallDir>\opmn\bin\opmnctl startall

UNIX StartupScript:

l Tomcat, WebSphere, and WebLogic 9: <Hyperion_Home>/deployments/<AppServNameAndVersion>/bin/startSharedServices9.bat

l WebLogic 8: <HSS_Home>/AppServer/InstalledApps/<AppServName>/<Version>/SharedServices9/startSharedServices9.bat

l Oracle:

<OracleInstallDir>/bin/emctl

<OracleInstallDir>/opmn/bin/opmnctl

3. Reporting and Analysis Core ServicesTable 52 Reporting and Analysis Core Services: Hyperion Interactive Reporting Base Service 1

Windows Start Menu Command: Start > Programs > Hyperion > Reporting and Analysis > Start Reporting and Analysis

Registered Service Name: HyS9Core1

Display Name in Windows Control Panel: Hyperion S9 BI+ 9.3 Core Services 1

Description: Provides core services for authorization, session management, and document publication

Windows Startup Script: <BIPLUS_HOME>\bin\startCommonServices.bat

UNIX Startup Script: <BIPLUS_HOME>/bin/startCommonServices.sh

4. Performance Management Architect ServicesTable 53 Performance Management Architect Services


Start > Programs > Hyperion > Foundation Services > Performance Management Architect > Start Dimension Server

Services and Processes 125


Process Manager: HyS9BPMA_ProcessManager

Process Manager automatically starts the following services:

l Engine Manager: HyS9EPMA_EngineManager

l Job Manager: HyS9EPMA_JobManager

l Event Manager: HyS9EPMA_EventManager

Display Namein WindowsControl Panel:

Process Manager: Hyperion S9 EPM Architect Process Manager

Process Manager automatically starts the following services:

l Engine Manager: Hyperion S9 EPM Architect Engine Manager

l Job Manager: Hyperion S9 EPM Architect Job Manager

l Event Manager: Hyperion S9 EPM Architect Event Manager

Description:l Process Manager: Manages all instances of EPM Architect Dimension Server. There is only one instance of EPM

Architect Process Manager per installation of EPM Architect.

l Engine Manager: Starts and stops instances of EPM Architect Dimension Server when requested by EPM ArchitectProcess Manager. There could be multiple instances of EPM Architect Engine Manager in the same instance of EPMArchitect (one per machine).

l Job Manager: Manages long-running tasks performed by EPM Architect.

l Event Manager: Distributes event messages between the various server processes of EPM Architect.


NA

UNIX StartupScript:

NA

Table 54 Performance Management Architect Web Services

Registered Service Name: IIS Admin Service

Display Name in Windows Control Panel: IIS Admin Service

Description: IIS Admin Service

5. Essbase

Table 55 Essbase Services/Processes

Windows Start MenuCommand:

Start > Programs > Hyperion > Essbase > Essbase

Registered ServiceName:

HyS9ESBAgent9.3.1 — hypservice

Display Name inWindows Control Panel:

Hyperion S9 BI+ Analytic Services 9.3.1 — <ServerName>

Description: Stores data with multiple dimensions and manages analytical data models, data storage, calculations, anddata security


Windows Startup Script: ARBORPATH\bin\essbase.exe

UNIX Startup Script: $ARBORPATH/bin/startEssbase.sh

6. Administration Services Application ServerTable 56 Administration Services Application Server Service/Process

Windows StartMenu Command:

Start > Programs > Hyperion > Administration Services > Start Administration Services Server


HyS9aas

Display Name inWindows ControlPanel:

Hyperion S9 Administration Services <AppServer>

Description: Controls the running of the Oracle's Essbase® Administration Services application server

Windows StartupScript:

l WebSphere, WebLogic 9, and deployed Tomcat deployment (via Hyperion Configuration Utility): <Hyperion_Home>\deployments\<AppServNameAndVersion>\bin\startaas.bat

l WebLogic 8.1.x: AASPATH\server\bin\startaas.exe

l Default Tomcat Deployment: AASPATH\server\bin\startEAS.exe

UNIX StartupScript:

l WebSphere, WebLogic 9, and deployed Tomcat deployment (via Oracle's Hyperion® Configuration Utility™):<Hyperion_Home>/deployments/<AppServNameAndVersion>/bin/startaas.sh

l WebLogic 8.1.x: <AASPATH>/server/bin/startaas.sh

7. Integration ServicesTable 57 Integration Services Service/Process

Windows Start Menu Command: Start > Programs > Hyperion > Integration Services > Integration Server

Registered Service Name: olapisvc.exe

Display Name in Windows Control Panel: Essbase Integration Server

Description: Essbase Integration Server

Windows Startup Script: <HYPERION_HOME>\AnalyticIntegrationServices\bin\olapisvc.exe

UNIX Startup Script: $HOME/Hyperion/AnalyticIntegrationServices/ais_start


8. Provider Services Application ServerTable 58 Provider Services Application Server Services/Processes


Start > Programs > Hyperion > Provider Services > Start Provider Services


HyS9aps


Hyperion S9 Provider Services <AppServer>

Description: Controls the running of an application server for Oracle's Hyperion® Provider Services


l WebSphere, Weblogic 9, and Tomcat: <Hyperion_Home>\deployments\<AppServNameAndVersion>\bin\startaps.bat

l WebLogic 8.1.x: <APS_HOME>\bin\startaps.bat

UNIX StartupScript:

l WebSphere, Weblogic 9, and Tomcat: <Hyperion_Home>/deployments/<AppServNameAndVersion>/bin/startaps.bat

l WebLogic 8.1.x: <APS_HOME>/bin/startaps.bat

9. Reporting and Analysis Services/Processes

a. Interactive Reporting

Table 59 Interactive Reporting Service/Process

Windows Start Menu Command: Start > Programs > Hyperion > Reporting and Analysis > Start Reporting and Analysis

Registered Service Name: HS9IRSvc1

Display Name in Windows ControlPanel:

Hyperion S9 BI+ 9.3 Interactive Reporting Service 1

Description: Process monitor that manages the Interactive Reporting Service, Data Access Service, InteractiveReporting Jobs processes, and the logging helper process.

Windows Startup Script: <BIPLUS_HOME>\bin\startIRM.bat

UNIX Startup Script: <BIPLUS_HOME>/bin/startIRM.sh

b. Workspace Application Server

Table 60 Workspace Application Server Services/Processes


Start > Programs > Hyperion > Reporting and Analysis > Utilities and Administration > Start Reporting and AnalysisCore Services



HyS9Workspace


Hyperion S9 BI+ 9.3 Workspace

Description: HyS9Workspace - Hyperion S9 BI+ Workspace web application for <APP_SERVER> <APP_VERSION>


l WebSphere and Tomcat: <HYPERION_HOME>\deployments\<AppServNameAndVersion>\bin\startWorkspace.bat

l WebLogic 9: <HYPERION_HOME>\deployments\WebLogic9\bin\startWorkspace.cmd

l WebLogic 8: <HYPERION_HOME>\AppServer\InstalledApps\WebLogic\8.1\WorkspaceDomain\bin\startWorkspace.bat

l Oracle: <OracleInstallDir>\opmn\bin\opmnctl startall

UNIX StartupScript:

l WebSphere, WebLogic 9, and Tomcat: <HYPERION_HOME>/deployments/<AppServNameAndVersion>/bin/startWorkspace.sh

l WebLogic 8: <BIPLUS_HOME>/AppServer/InstalledApps/WebLogic/8.1/WorkspaceDomain/bin/startWorkspace.sh

l Oracle: <OracleInstallDir>/opmn/bin/opmnctl startall

c. Financial Reporting

Table 61 Financial Reporting Services/Processes


Start > Programs > Hyperion > Reporting and Analysis > Start Financial Reporting


l Financial Reporting Java RMI Registry: HyS9FRRMI

l Financial Reporting Print Server: HyS9FRPrint

l Financial Reporting Report Server: HyS9FRReport

l Financial Reporting Scheduler Server: HyS9FRSched


l Hyperion S9 BI+ Financial Reporting Java RMI Registry

l Hyperion S9 BI+ Financial Reporting Print Server

l Hyperion S9 BI+ Financial Reporting Report Server

l Hyperion S9 BI+ Financial Reporting Scheduler Server

Description:l Financial Reporting RMI Registry Service: Provides a Java RMI Registry for Financial Reporting

l Financial Reporting Print Server: Generates PDF, batch, and scheduled job output for Financial Reporting

l Financial Reporting Report Server: Generates and formats reports and books, including specified calculations forFinancial Reporting

l Financial Reporting Scheduler Server: Responds to scheduled batch requests for Financial Reporting

l Financial Reporting Web application: Provides a Workspace module for Oracle's Hyperion® Financial Reporting –System 9


<BIPLUS_HOME>\bin\start_BIPlus.bat


UNIX StartupScript:

<BIPLUS_HOME>/bin/freporting {start|stop|restart}

d. Reporting and Analysis Web Server

Table 62 Reporting and Analysis Web Server Services/Processes


Start > Programs > Hyperion > Reporting and Analysis > Start Web Analysis


l Apache: HyS9Apache2

l IIS: IISADMIN

l IHS 6.0: IBM HTTP Server 6.0



l Apache: Hyperion S9 Apache 2.0

l IIS: IIS Admin Service



Description:l Apache: Apache/2.0.52 (Win32)

l IIS: IIS Admin Service

l IHS 6.0: IBM_HTTP_Server/6.0.2 Apache/2.0.47 (Win32)

l IHS 6.1: IBM_HTTP_Server

WindowsStartup Script(Apache only):

<HYPERION_HOME>\common\httpServers\Apache\2.0.52\bin\StartHyperionApacheService.cmd

UNIX StartupScript (Apacheonly):

<HYPERION_HOME>/common/httpServers/Apache/2.0.52/bin/apachectl {start|stop|restart}

e. Web Analysis Application Server

Table 63 Web Analysis Application Server Services/Processes


Start > Programs > Hyperion > Reporting and Analysis > Start Reporting and Analysis


HyS9WebAnalysis


Hyperion S9 BI+ 9.3 Web Analysis

Description: HyS9WebAnalysis - Hyperion S9 BI+ Web Analysis web application for <APP_SERVER> <APP_VERSION>.



l WebSphere and Tomcat: <HYPERION_HOME>\deployments\<AppServNameAndVersion>\bin\startWebAnalysis.bat

l WebLogic 9: <HYPERION_HOME>\deployments\WebLogic9\bin\startWebAnalysis.cmd

l WebLogic 8: <BIPLUS_HOME>\AppServer\InstalledApps\WebLogic\8.1\WebAnalysisDomain\bin\startWebAnalysis.bat


UNIX StartupScript:

l WebSphere, WebLogic 9, and Tomcat: <HYPERION_HOME>/deployments/<AppServNameAndVersion>/bin/startWebAnalysis.sh

l WebLogic 8: <BIPLUS_HOME>/AppServer/InstalledApps/WebLogic/8.1/WebAnalysisDomain/bin/startWebAnalysis.sh


10. Application Server Services/ProcessesThe following application server services or processes can be started in any order.

Performance Management Architect Application Server

Table 64 Performance Management Architect Application Server Services


Start > Programs > Hyperion > Foundation Services > Performance Management Architect > Start PerformanceManagement Architect Web


HyS9EPMAWebTier


Hyperion S9 EPM Architect Web

Description: EPM Architect Web

Windows Startup Script:l WebSphere, WebLogic 9, and Tomcat: <HYPERION_HOME>\deployments

\<AppServNameAndVersion>\bin\startEPMAWebTier.bat

l WebLogic 8: \Hyperion\EPMA\AppServer\InstalledApps\WebLogic\<version>\EPMAWebServer\bin\startEPMAWebTier.bat

UNIX Startup Script: NA

Performance Management Architect Data Synchronizer Application Server

Table 65 Performance Management Architect Data Synchronizer Application Server Services


Start > Programs > Hyperion > Foundation Services > Performance Management Architect > Start DataSynchronizer


HyS9EPMADataSynchronizer



Hyperion S9 EPM Architect Data Synchronization

Description: EPM Architect Data Synchronizations Engine


l WebSphere, WebLogic 9, and Tomcat: <HYPERION_HOME>\deployments\<AppServNameAndVersion>\bin\startEPMADataSynchronizer.bat

l WebLogic 8: \Hyperion\EPMA\AppServer\InstalledApps\WebLogic\<version>\EPMAWebServer\bin\startEPMADataSynchronizer.bat


Financial Reporting Application Server

Table 66 Financial Reporting Application Server Services/Processes


Start > Programs > Hyperion > Reporting and Analysis > Start Reporting and Analysis


HyS9FRWeb


Hyperion S9 BI+ 9.3 Financial Reporting Web application

Description: HyS9FRWeb - Provides a Workspace module for Financial Reporting


l WebSphere and Tomcat: <HYPERION_HOME>\deployments\<AppServNameAndVersion>\bin\startFinancialReporting.bat

l WebLogic 9: <HYPERION_HOME>\deployments\WebLogic9\bin\startFinancialReporting.cmd

l WebLogic 8: <BIPLUS_HOME>\AppServer\InstalledApps\WebLogic\8.1\FinancialReportingDomain\bin\startFinancialReporting.bat


UNIX StartupScript:

l WebSphere, WebLogic 9, and Tomcat: <HYPERION_HOME>/deployments/<AppServNameAndVersion>/bin/startFinancialReporting.sh

l WebLogic 8: <BIPLUS_HOME>/AppServer/InstalledApps/WebLogic/8.1/FinancialReportingDomain/bin/startFinancialReporting.sh


11. Remaining Product ServicesThe following product services can be started in any order.


Planning Application Server

Table 67 Planning Application Server Services/Processes


Start > Programs > Hyperion > Planning > Start Planning


HyS9Planning


Hyperion S9 Planning

Description: Provides access support for Planning Web server


l WebSphere, WebLogic 9, and Tomcat: <HYPERION_HOME>\deployments\<AppServNameAndVersion>\bin\startHyperionPlanning.bat

l WebLogic 8.1: <Planning_HOME>:\AppServer\InstalledApps\<AppServName>\<version>\HyperionPlanningDomain\startHyperionPlanning.bat

UNIX StartupScript:

l WebSphere, WebLogic 9, and Tomcat: <HYPERION_HOME>/deployments/<AppServNameAndVersion>/bin/startHyperionPlanning.sh

l WebLogic 8.1: <Planning_HOME>/AppServer/InstalledApps/<AppServName>/<version>/HyperionPlanningDomain/startHyperionPlanning.sh

l Oracle:

<OracleInstallDir>/bin/emctl

<OracleInstallDir>/opmn/bin/opmnctl

Financial Management

Table 68 Financial Management Services


Start > Programs > Hyperion > Financial Management


l HFM Service: Hyperion S9 Financial Management Service

l HFM DME Listener: Hyperion S9 Financial Management DME Listener


l HFM Service: Hyperion S9 Financial Management Service

l HFM DME Listener: Hyperion S9 Financial Management DME Listener

Description:l HFM Service: Service which perpetuates application instances for optimal login performance

l HFM DME Listener: Hyperion Financial Management DME Listener for communication with the Hyperion DataMovement Engine. If this service is stopped, the DME Web service will not be able to communicate with all HFMinstances on this server.


<Hyperion_Home>\FinancialManagement\Client\HFM.exe

UNIX StartupScript:

NA


Strategic Finance

Table 69 Strategic Finance Service

Windows Start Menu Command: Start > Programs > Hyperion > Strategic Finance > Strategic Finance

Registered Service Name: HyS9HSFsrv

Display Name in Windows Control Panel: Hyperion S9 Strategic Finance Service

Description: Provides Hyperion Strategic Finance services including entity repository management,authentication, access control, consolidation, data and metadata management

Windows Startup Script: <Hyperion_Home>\StrategicFinance\Client\hsf.exe


Performance Scorecard Application Server

Table 70 Performance Scorecard Application Server Services/Processes


Start > Hyperion > Performance Scorecard > startWebReports on <appserver>


HyS9HPS


Hyperion S9 Performance Scorecard 9.3.1.0.0 <AppServer>

Description: Starts and stops an instance of Performance Scorecard running under an application server.


l WebSphere, WebLogic 9, and Tomcat: <HYPERION_HOME>\deployments\<AppServNameAndVersion>\bin\startwebreportsDomain.bat

l WebLogic 8.1: <HPS_INSTALL_DIRECTORY>\AppServer\InstalledApps\<AppServName>\<version>\webreportsDomain\bin\startwebreports.bat

UNIX StartupScript:

l WebSphere, WebLogic 9, and Tomcat: <HYPERION_HOME>/deployments/<AppServNameAndVersion>/bin/startwebreportsDomain.sh

l WebLogic 8.1: <HPS_INSTALL_DIRECTORY>/AppServer/InstalledApps/<AppServName>/<version>/webreportsDomain/bin/startwebreports.sh

Performance Scorecard Alerter Application Server

Table 71 Performance Scorecard Alerter Application Server Services/Processes


Start > Hyperion > Performance Scorecard > startHPSAlerter on <appserver>


HyS9Alerter



Hyperion S9 Performance Scorecard Alerter 9.3.1.0.0 <AppServer>

Description: Starts and stops an instance of Performance Scorecard Alerter running under an application server.


l WebSphere, WebLogic 9, and Tomcat: <HYPERION_HOME>\deployments\<AppServNameAndVersion>\bin\startalerterDomain.bat

l WebLogic 8.1: <HPS_INSTALL_DIRECTORY>\AppServer\InstalledApps\<AppServName>\<version>\alerterDomain\bin\startalerter.bat

UNIX StartupScript:

l WebSphere, WebLogic 9, and Tomcat: <HYPERION_HOME>/deployments/<AppServNameAndVersion>/bin/startalerterDomain.sh

l WebLogic 8.1: <HPS_INSTALL_DIRECTORY>/AppServer/InstalledApps/<AppServName>/<version>/alerterDomain/bin/startalerter.sh

Data Relationship Management

Table 72 Data Relationship Management Services


Start > Programs > Hyperion > Data Relationship Management > Data Relationship Management Console

Registered Service Name:l Services: HyS9MDMSvc

l Web Publishing: HyS9MDMWebPubSvc

Display Name in WindowsControl Panel:

l Services: Hyperion Data Relationship Management

l Web Publishing: Hyperion Data Relationship Management Web Publishing

Description:l Services: HyS9MDMSvc - Hyperion Data Relationship Management Services

l Web Publishing: HyS9MDMWebPubSvc - Hyperion Data Relationship Management Web Publishing

Windows Startup Script: <HYPERION_HOME>\Master Data Management\mdm_ntier_client_http.exe


FDM

Table 73 FDM Service

Windows Start Menu Command: NA

Registered Service Name: HyS9FDMTaskManagerSrv

Display Name in Windows Control Panel: Hyperion S9 Financial Data Quality Management Task Manager Service

Description: Provides the ability to schedule Hyperion Financial Data Quality Management tasks.

Windows Startup Script: NA



Data Integration Management

Table 74 Data Integration Management Services/Processes


l Start > Programs > Hyperion > Data Integration Management > Informatica PowerCenter 7.1.5-RepServer >ModuleName

l Start > Programs > Data Integration Management > Informatica PowerCenter 7.1.5-RepServer, InformaticaPowerCenter 7.1.5-Client > ModuleName

l Start > Programs > Hyperion > Data Integration Management > Informatica PowerCenter 7.1.5-Server > ModuleName


l Repository Server: PmRepServer

l Powermart: Hyperion Data Integration Management Server

Display Namein WindowsControl Panel:

l Repository Server: Hyperion Data Integration Management Repository Server


Description:l Repository Server: Hyperion Data Integration Management Repository Server


WindowsStartupScript:

l Informatica PowerCenter 7.1.5 - RepServer > Informatica Repository Server Setup: <DIM_Install_Directory>\RepositoryServer\bin\PmRsSetup.exe

l Informatica PowerCenter 7.1.5 - Client > Designer: <DIM_Install_Directory>\Client\pmdesign.exe

l Informatica PowerCenter 7.1.5 - Client > Repository Manager: <DIM_Install_Directory>\Client\pmrepmgr.exe

l Informatica PowerCenter 7.1.5 - Client > Repository Server Administration Console: <DIM_Install_Directory>\Client\Repository Server Administration Console.msc

l Informatica PowerCenter 7.15 - Client > Workflow Manager: <DIM_Install_Directory>\Client\pmwflmgr.exe

l Informatica PowerCenter 7.1.5 - Client > Workflow Monitor: <DIM_Install_Directory>\Client\pmwfmntr.exe

l Informatica PowerCenter 7.1.5 - Server > Informatica Server Setup: <DIM_Install_Directory>\Server\bin\pmsetup.exe

UNIX StartupScript:

l Repository Server: <DIM_HOME>/Resources/bin/start_pmrepserver.sh

l PowerCenter Server: <DIM_HOME>/Resources/bin/start_pmserver.sh

Translation Manager

Table 75 Translation Manager Services/Processes


Start > Programs > Hyperion > Translation Manager > Start Server <Server Type>


l Tomcat: HTMServer

l WebSphere 5: IBMWAS5Service - HTMServerWAS5.1

l WebSphere 6: IBMWAS6Service - Hyperion HTMServer WAS60

l WebLogic 8: beasvc HyperionTMWL8.1_HTMServer

l WebLogic 9: Hyperion HyperionTM WebLogic 9.1



l Tomcat: Hyperion S9 HTMServer ATS5

l WebSphere 5: Hyperion S9 HTMServer WAS5

l WebSphere 6: Hyperion S9 HTMServer WAS6

l WebLogic 8: Hyperion S9 HyperionTM WLS8

l WebLogic 9: Hyperion S9 HyperionTM WLS9

Description: NA


NA

UNIX StartupScript:

<HTM_HOME>/AppServer/InstalledApps/<AppServer>/<version>/<domain>/bin/start<domain>.sh

Default URLsTable 76 Default URLs

Product Default URL

Oracle's Hyperion® Shared Services UserManagement Console

http://<hostname>:58080/interop

Workspace

Note: From Workspace, you can accessFinancial Management, Planning, Oracle'sEnterprise Performance ManagementArchitect, and Reporting and Analysis.

http://<WebServer>:<port>/workspace/

where <WebServer> is the Web server machine hostname and <port> is the Webserver listen port; for example, 19000 if using the Apache instance bundled with Reportingand Analysis.

Oracle's Hyperion® Performance Scorecard –System 9

http://<hostname>:18080/HPSWebReports

Oracle's Hyperion® Data RelationshipManagement

http://<hostname>/mdm_ntier

Oracle's Hyperion® Financial Data QualityManagement

http://<hostname>/HyperionFDM

Default URLs 137


BDeploying Hyperion 9.3.1

Products with Componentsfrom Previous Releases

In This Appendix

Upgrading to a Single-Release Hyperion Product Environment.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Upgrading to a Mixed-Release Hyperion Product Environment .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

If you are using multiple Hyperion products in your environment, you can upgrade all productsat one time, or you can upgrade only some of the products (a mixed-release environment). Thisappendix describes how to manage upgrades of all products or only some products and maintaininteroperability between products.

See the product installation guides for upgrade procedures for each product.

Upgrading to a Single-Release Hyperion ProductEnvironmentIf you are upgrading all Hyperion products at one time to the same release, you can upgradeusing the existing machines, upgrading directly over the existing deployment. This type ofupgrade can be on a single machine or across a complex multi-machine environment.

For example, if you are upgrading an installation of 9.3.0 products deployed on a single machineand want to upgrade all products to release 9.3.1:

Figure 1 Before Upgrading in a Single-Release Environment

Upgrading to a Single-Release Hyperion Product Environment 139

Figure 2 After Upgrading in a Single-Release Environment

Upgrading to a Mixed-Release Hyperion ProductEnvironmentIn a mixed-release upgrade, you upgrade only some Hyperion products. This scenario requiressome manual configuration, and navigation procedures in Workspace differ. See “ConfiguringProducts in a Mixed-Release Environment ” on page 142 and “Navigating in Workspace in aMixed-Release Environment” on page 143.

In addition, this scenario requires additional hardware because only one version of a modulecan run on any machine at one time.

For example, if you are upgrading an installation of Hyperion release 9.3.0 products deployedon a single machine and want to upgrade all products except Financial Management andPlanning to release 9.3.1:

Figure 3 Example 1: Before Upgrading in a Mixed-Release Environment

140 Deploying Hyperion 9.3.1 Products with Components from Previous Releases

Figure 4 Example 1: After Upgrading in a Mixed-Release Environment

Two machines are required for the deployment in a mixed-release environment. The newmachine hosts Hyperion release 9.3.1 products, and the original machine retains the release 9.3.0products. In this configuration, end users access all Hyperion content within a single, centralizedWorkspace.

In another example, if you are upgrading an installation of Hyperion release 9.3.0 productsdeployed on a single machine and want to upgrade only Financial Management and Planningto release 9.3.1:

Figure 5 Example 2: Before Upgrading in a Mixed-Release Environment

Upgrading to a Mixed-Release Hyperion Product Environment 141

Figure 6 Example 2: After Upgrading in a Mixed-Release Environment

Two machines are required for the deployment in a mixed-release environment. The newmachine hosts the Hyperion release 9.3.1 products that are required to use the upgradedFinancial Management and Oracle's Hyperion® Planning – System 9, and the original machinehosts the other products. In this configuration, end users access all Hyperion content within asingle, centralized Workspace.

Configuring Products in a Mixed-Release EnvironmentAfter upgrading in a mixed-release environment, you must perform the following configurationtasks.

ä To configure products in a mixed-release environment:

1 Create a custom HTML file based on one of the sample HTML files.

See “Sample HTML Files” on page 143.

Make appropriate changes to the application name, and to the server protocol, name, port,and (for Oracle's Hyperion® Financial Management – System 9 only) cluster.

2 Upload the sample HTML file into the appropriate machine. From the Workspace File menu, chooseImport > File.

For Example 1 in the previous section, import this HTML file into Machine 2 to managelaunching applications on Machine 1. For Example 2 in the previous section, import thisHTML file into Machine 1 to manage launching applications on Machine 1.

3 Set access permissions to the imported HTML file using the same method as for other Workspaceartifacts, granting access to users that can access the applications on Machine 1.

Users provisioned with a Reporting and Analysis role and a role for the application shouldnow be able to double-click the file and launch the application.

To allow users with only limited Oracle's Hyperion® Reporting and Analysis – System 9 roles(such as the Viewer role) to access the file, publish it as a Favorite for these users.


ä To publish the file as a Favorite:

1 Right-click the file and select Properties.

2 Select Edit Permissions.

3 Enter a user name and click Update List.

You can also publish files to groups or roles.

4 Move the user to the box on the right.

5 Select the user and click Edit.

6 Select View and Pushed and click OK.

7 Select Push this item to selected User, Groups, and Roles and click OK.

Navigating in Workspace in a Mixed-Release EnvironmentYou navigate in Workspace differently in mixed-release environments than in single-releaseenvironments.

In a single-release environment, you launch applications by clicking “Navigate” in Workspace;the application launches as a tab at the bottom of the Oracle's Hyperion® Workspace.

In a mixed-release environment, you launch applications from the Explorer module or from theFavorites menu. Applications launched from Machine 1 in the previous figures open in a separatebrowser window.

Sample HTML Files

Financial Management Sample:<html><head><script> function launchHyperionWorkspace(){ var protocol = 'http'; var hyp_server = 'workspace_web_server'; var port = '19000'; var appName = 'hfm_application_name'; var cluster = 'hfm_cluster_name'; // **** Do not edit below this line ***** var window_name = protocol+hyp_server+port; var uri = protocol + '://' + hyp_server + ":" + port + "/workspace/index.jsp?sso_token="+encodeURIComponent(parent.gModuleManager.getToken())+"&module=hfm.appcontainer&sourceApp="+encodeURIComponent(appName)+"&cluster="+encodeURIComponent(cluster);

var oldWorkspaceWindows = getWorkspaceWindows(); var oldWorkspaceWindow = oldWorkspaceWindows[window_name];


if(oldWorkspaceWindow) { try { oldWorkspaceWindow.launchRelatedContentUri(uri); } catch(e) { var newWin = window.open(uri,window_name,'toolbar=no,location=no,status=yes,personalbar=no,menubar=no,resizable=yes'); oldWorkspaceWindows[window_name] = newWin; } } else { var newWin = window.open(uri,window_name,'toolbar=no,location=no,status=yes,personalbar=no,menubar=no,resizable=yes'); oldWorkspaceWindows[window_name] = newWin; } var container = parent.gModuleManager.getModuleById(parent.gModuleManager.getStartup()); var thisModule = container.getHandler().getActiveModule(); container.getHandler().unloadModule(thisModule);}function getWorkspaceWindows(){ if(!parent.gModuleManager.gOldWorkspaceWindows) { parent.gModuleManager.gOldWorkspaceWindows = {}; }

return parent.gModuleManager.gOldWorkspaceWindows;}</script></head> <body onload="launchHyperionWorkspace()">Launching application in a new window.</body></html>

Planning Sample<html><head><script> function launchHyperionWorkspace(){ var protocol = 'http'; var hyp_server = 'workspace_web_server'; var port = '19000'; var appName = 'planning_application_name'; // **** Do not edit below this line *****


var window_name = protocol+hyp_server+port; var uri = protocol + '://' + hyp_server + ":" + port + '/workspace/index.jsp?sso_token='+encodeURIComponent(parent.gModuleManager.getToken())+'&module=HyperionPlanning.planning&sourceApp='+encodeURIComponent(appName);

var oldWorkspaceWindows = getWorkspaceWindows(); var oldWorkspaceWindow = oldWorkspaceWindows[window_name]; if(oldWorkspaceWindow) { try { oldWorkspaceWindow.launchRelatedContentUri(uri); } catch(e) { var newWin = window.open(uri,window_name,'toolbar=no,location=no,status=yes,personalbar=no,menubar=no,resizable=yes'); oldWorkspaceWindows[window_name] = newWin; } } else { var newWin = window.open(uri,window_name,'toolbar=no,location=no,status=yes,personalbar=no,menubar=no,resizable=yes'); oldWorkspaceWindows[window_name] = newWin; } var container = parent.gModuleManager.getModuleById(parent.gModuleManager.getStartup()); var thisModule = container.getHandler().getActiveModule(); container.getHandler().unloadModule(thisModule);}function getWorkspaceWindows(){ if(!parent.gModuleManager.gOldWorkspaceWindows) { parent.gModuleManager.gOldWorkspaceWindows = {}; }

return parent.gModuleManager.gOldWorkspaceWindows;}</script></head> <body onload="launchHyperionWorkspace()">Launching application in a new window.</body></html>



Index

AAdministration Services

application serverUNIX startup scripts, 127Windows service names, 127

default ports, 77install/configuration tasks, 113release compatibility, 46system requirements, 22

Apache Server, supported versions, 38Application Builder J2EE, default ports, 83Application Builder.NET, default ports, 84application servers

configuration, 105prerequisites, 70, 72

assistive technologiessystem requirements, 18

screen magnifier, 18screen reader, 18

auditing license compliance, 65authentication providers, system requirements, 15

BBEA WebLogic, supported versions, 25, 29, 37, 42

Cclient

OS, 17processor, 17

compatibility of releases, 45configuration

Essbase, 106, 108, 109Performance Scorecard Alerter, 109application server, 105description, 103Planning , 109prerequisites, 71

recommendations, 104relational database, 105Reporting and Analysis, 106

Interactive Reporting, 107Shared Services Registration, 104worksheets, 103

configuration sequence, 111

DData Integration Management

default ports, 89install/configuration tasks, 121license keys, 65release compatibility, 50system requirements, 38UNIX startup script, 136Windows service names, 136

Data Managementdefault ports, 89release compatibility, 50repository passwords, 99system requirements, 38

Data Relationship Managementdefault ports, 91default URLs, 137install/configuration tasks, 120release compatibility, 50repository passwords, 100system requirements, 38Windows service names, 135

database connectivitysystem requirements

Data Integration Management, 43Essbase, 26JDBC, 26ODBC, 26Translation Manager, 43

A B C D E F H I J L M N O P R S T U W

Index 147

database requirementsprerequisites, 69, 71

default URLs, 123Data Relationship Management, 137Financial Data Quality Management, 137Performance Scorecard, 137User Management Console, 137Workspace, 137

Disk space and RAMclient software, 19Data Management, 40Essbase - System 9, 24Financial Performance Management Applications,

35Foundation Services, 15Reporting and Analysis, 27Shared Services, 15

Domino LDAP, supported versions, 15

EEssbase

Configuration Utility Worksheets, 106default ports, 77install/configuration tasks, 113release compatibility, 46system requirements, 22UNIX startup script, 126Windows service names, 126

Essbase - System 9default ports, 77install/configuration tasks, 113release compatibility, 46system requirements, 22

FFDM

default ports, 91default URLs, 137disk space requirements, 40install/configuration tasks, 120release compatibility, 50system requirements, 38Windows service names, 135

Financial Managementconfiguration, 109default ports, 84

install/configuration tasks, 116release compatibility, 49repository passwords, 97system requirements, 33Windows service names, 133

Financial Performance Management Applicationsdefault ports, 84release compatibility, 49repository passwords, 96system requirements, 34

Financial Reportingapplication server

UNIX startup script, 132Windows service names, 132

configuration, 107default ports, 81install/configuration tasks, 117release compatibility, 47repository passwords, 95system requirements, 26UNIX startup script, 129Windows service names, 129

Firefox, supported versions, 20Foundation Services

default ports, 75release compatibility, 45repository passwords, 93system requirements, 15

Hhardware preparation, 68HP-UX

32-bit server, supported versions, 39Hyperion

components, 9overview, 9

Hyperion Home location, 71Hyperion License Server, 53

IIBM DB2 for z/OS, supported versions, 31IBM DB2 OLAP Server, supported versions, 31IBM DB2, supported versions, 28, 31, 37, 42IBM Directory Server, supported version, 15IBM Tivoli Directory Server, supported version, 15


148 Index

IBM WebSphere, supported versions, 25, 29, 38, 37,42

Informix, supported versions, 31installation

downloading documentation, 68downloading software, 67planning, 67sequence, 111

Integration Servicesinstall/configuration tasks, 113release compatibility, 46system requirements, 22UNIX startup script, 127Windows service names, 127

Interactive Reportingconfiguration, 107default ports, 82install/configuration tasks, 117release compatibility, 47system requirements, 26UNIX startup script, 128Windows service names, 128

JJava application servers

configuration, 105Essbase - System 9, 25Financial Performance Management Applications,

37prerequisites, 70, 72Reporting and Analysis, 29

Java browser plug-insystem requirements

32-bit, 2164-bit, 21

Java Runtime Environmentsystem requirements, 21

32-bit, 2164-bit, 21

Llicense compliance, 53license keys

Data Integration Management, 65licensing

prerequisites, 71

Lightweight Directory Access Protocol (LDAP), 15

MMicrosoft Active Directory, supported version, 15Microsoft IIS, supported versions, 30, 38Microsoft Internet Explorer, supported versions, 20Microsoft NTLM, supported version, 15Microsoft SQL Server, supported versions, 25, 28, 32,

37, 42Microsoft Windows

32-bit and 64–bit server, supported versions, 27,39

32-bit server, supported versions, 34Essbase — System 9, 23

64-bit server, supported versionsEssbase — System 9, 23, 34

NNetegrity SiteMinder, supported version, 16Novell eDirectory, supported version, 15

OOpenLDAP

supported versions, 15UNIX startup script, 124Windows service name, 124

Oracleapplication server, supported versions, 25, 29, 38,

42databases, supported versions, 25, 29, 32, 37, 42

Oracle Identity Management, supported version, 16order of installation, 111

Ppasswords, repository, 93Performance Management Architect

application serverWindows service names, 131

configuration, 109Data Synchronizer application server

Windows service names, 131default ports, 86install/configuration tasks, 114, 116release compatibility, 49repository passwords, 98


Index 149

system requirements, 33Web services

Windows service name, 126Windows service names, 125

Performance Scorecardapplication server


configuration, 108default ports, 85default URLs, 137install/configuration tasks, 118release compatibility, 49repository passwords, 99system requirements, 33

Performance Scorecard Alerterapplication server


configuration, 109Planning

application serverUNIX startup script, 133Windows service names, 133


portsAdministration Services, 77Application Builder J2EE, 83Application Builder.NET, 84Data Integration Management, 89Data Management, 89Data Relationship Management, 91Essbase, 77Essbase - System 9, 77FDM, 91Financial Management, 84Financial Performance Management Applications,

84Financial Reporting, 81Interactive Reporting, 82Performance Management Architect, 86Performance Scorecard, 85Planning, 85prerequisites, 71

Provider Services, 78Reporting and Analysis, 79, 80Shared Services, 75Smart Search, 79Strategic Finance, 86Translation Manager, 90Web Analysis, 82Workspace, 83

prerequisitesconfiguration, 71databases, 69Hyperion Home, 71Java application servers, 72java application servers, 70licensing, 71resolving port conflicts, 71security, 69Shared Services, 71system requirements, 68Web servers, 70

product groupingsFoundation Services, 13Data Management, 14Essbase — System 9, 13Financial Performance Management Applications,

13Reporting and Analysis, 13

product installation sequence, 111Provider Services



provisioning, tasks, 121

RRed Brick, supported versions, 32Red Hat Linux

32-bit server, supported versions, 23, 27, 39registry.properties, 53, 104relational database, configuration, 105release compatibility, 45Reporting and Analysis

configuration, 106


150 Index

default ports, 79, 80install/configuration tasks, 117release compatibility, 47repository passwords, 94system requirements, 26

Reporting and Analysis Core ServicesUNIX startup script, 125

Reporting and Analysis Core ServicesWindows service name, 125

repository passwords, 93Administration Services, 94Data Management, 99Data Relationship Management, 100Financial Management, 97Financial Performance Management Applications,

96Financial Reporting, 95Performance Scorecard, 99Planning, 96Shared Services, 93Translation Manager, 101Web Analysis, 95Workspace, 94

runtime clients, system requirements, 18

SSAP Enterprise Portal, supported version, 16SAP R/3, supported versions, 32screen magnifier, system requirements, 18screen reader, system requirements, 18screen resolution, system requirements, 18security, prerequisites, 69sequence, installation, 111service names. See Windows service namesShared Services


default ports, 75install/configuration tasks, 112OpenLDAP

UNIX startup script, 124Windows service name, 124

registration, 104release compatibility, 45system requirements, 15, 26

Smart Search

default ports, 79Solaris

32-bit server, supported versions, 23, 27, 3964-bit server, supported versions, 23

SQR Production Reportingconfiguration, 108install/configuration tasks, 117release compatibility, 47system requirements, 26

startup dependencies, 123Strategic Finance

configuration, 109default ports, 86install/configuration tasks, 119release compatibility, 49system requirements, 34Windows service names, 134

Sun Java Enterprise System, supported versions, 29Sun One, supported version, 15Sybase, supported versions, 32system requirements, 13

assistive technologies, 18client, 16

Java Runtime environment, 21OS, 17other required third-party software, 21required Hyperion software, 17Web Browser, 20Web Browser plug-in, 21

Data Management, 38database connectivity

JDBC, 26ODBC, 26

Essbasedatabase connectivity, 26server OS/processor, 23

Essbase - System 9, 22Financial Performance Management Applications,

33, 34disk space and RAM, 35Java application servers, 37repository databases, 36required third-party software, 36

Foundation Services, 15Java application servers, 29Java browser plug-in

32-bit, 21


Index 151

64-bit, 21Java Runtime Environment

32-bit, 2164-bit, 21

processor, 17Reporting and Analysis, 26, 27runtime clients, 18screen resolution, 18Shared Services

disk space and RAM, 15Translation Manager

database connectivity, 43User Directories, 15Windows clients

disk space and RAM, 19

TTeradata, supported versions, 33third-party software requirements, 21Translation Manager


default ports, 90repository passwords, 101system requirements, 38

UUNIX startup scripts, 123

Administration Services application server, 127Data Integration Management, 136Financial Reporting, 129Financial Reporting application server, 132Interactive Reporting, 128Performance Scorecard Alerter application server,

134Performance Scorecard application server, 134Planning application server, 133Provider Services application server, 128Reporting and Analysis Core Services, 125Shared Services application server, 124Shared Services OpenLDAP, 124Translation Manager application server, 136Web Analysis application server, 130Web Analysis Web server, 130Workspace application server, 128

upgradingmixed-release environment, 139sequence, 111supported upgrade paths, 11

URLs, default, 123User Directories, system requirements, 15User Management Console

default URLs, 137system requirements, 137

User Management Consoledefault URLs, 137

WWeb Analysis



Web Analysis Web serverUNIX startup script, 130Windows service names, 130

Web browser plug-insystem requirements, 21

Web servers, prerequisites, 70Windows service names, 123

Administration Services application server, 127,131

Data Integration Management, 136Data Relationship Management, 135Performance Management Architect Data

Synchronizer application server, 131Financial Data Quality Management, 135Financial Management, 133Financial Reporting, 129Financial Reporting application server, 132Interactive Reporting, 128Performance Scorecard Alerter application server,

134Performance Scorecard application server, 134Planning application server, 133Provider Services application server, 128Reporting and Analysis Core Services, 125Shared Services application server, 124Shared Services OpenLDAP, 124


152 Index

Strategic Finance, 134Translation Manager application server, 136Web Analysis application server, 130Web Analysis Web server, 130Performance Management Architect Web services,

126Workspace application server, 128

Workspaceapplication server


configuration, 106default ports, 83default URLs, 137install/configuration tasks, 117system requirements, 26


Index 153


154 Index