Hsys9 Install Start Here

HYPERION
RELEASE 9.3.1
INSTALLATION START HERE

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

Relationship 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's
Enterprise Performance Management Architect is part of the Financial Management and
Planning installations.
10 Hyperion Product Components

Upgrading Hyperion Products
2
If you are upgrading from a previous release of Hyperion products, note the following supported
upgrade 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 service
pack.
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 noted
above, and then upgrade to 9.3.1.
Check the product readmes to find out if additional upgrade paths are supported for a particular
product.
See the product installation guides for the products you are using for upgrade procedures.
11
12 Upgrading Hyperion Products
System Requirements
3
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 Requirements

This chapter describes Shared Services, Client, and product-specific system requirements for
Hyperion 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 Requirements
sections; for example: OS/Processor, disk space and RAM, and third-party software
requirements.
Disk space and RAM requirements are approximate and do not include additional possible
requirements on the machine, such as extra space needed for a VMware image. The installation
program calculates the required disk space, based on your installation choices. Disk space
estimates 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 150
total users (30 to 40 concurrent users) for one installation of a Hyperion product. For larger and
more complex deployments—a larger number of users, multiple installations of one product,
and installations of multiple products—Hyperion highly recommends that you contact
Hyperion Consulting Services to determine the appropriate number of servers for your
environment.
For information on prerequisites, see Chapter 6, “Planning Hyperion Product Installations.”
For information on current and backward compatibility with other Hyperion products, see
Chapter 4, “Release Compatibility.”
Before installing Hyperion products, verify that all system requirements and prerequisites are
met.
Note: Hyperion acknowledges and supports the backward compatibility assertions made by
third-party vendors. Therefore, where vendors assert backward compatibility, subsequent
maintenance 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 (and
remove the incompatible version from the supported matrix) or provide a maintenance
release or service fix to the Hyperion product code.
14 System Requirements
Foundation Services
l “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 Requirements

Shared Services is considered a component of other Hyperion products. In general, Shared
Services supports the same platform as the products it is used with; therefore, the system
requirements for the Shared Services server are not called out specifically. Shared Services is
included in “Client Requirements” on page 16. You can assume that Shared Services supports
the same software that is listed in each product-specific section of this chapter, unless otherwise
noted. 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 for
provisioning, depending on how often you back up OpenLDAP.
User Directories
A user directory is required for external authentication through Shared Services for all products
except 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 Requirements
Hyperion 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 *Windows 2000 Server is supported for SQR Production Reporting only.
All other Reporting and Analysis modules support Windows 2000
Windows XP Professional SP2
Professional.
l
l Windows 2003 SP1

l Windows 2000 Professional SP4*
l Windows 2000 Server SP4*
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.
2Reportingand 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 all

products except for the products
listed below.
One of the following: Applies only to Strategic

Finance
l 2 GHz (light use-Defined as fewer than 50 users connecting to the server to check entities in and
out 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 and
out or to run server-based consolidation for structures that contain more than 15 entities.)
Pentium 4.8 GHz minimum Applies only to Translation

Manager
2 GHz minimum Applies only to Data

Relationship Management
Required Hyperion Software

If you are using Smart View to access Essbase as a data source, Provider Services is required.
Client Requirements 17
Assistive Technologies
Assistive Technologies apply only to Windows operating systems and Microsoft Internet
Explorer.
Not supported for:
l Reporting and Analysis
l Oracle's Hyperion® Shared Services User Management Console
l Strategic Finance
Assistive Technologies Supported Versions
Screen reader l JAWS 7

l JAWS 6.2
l Window Eyes 5.5
Screen magnifier l MAGic 9.3

l MAGic 9.0
Screen Resolution
Hyperion products are optimized for a minimum screen resolution of 1024 x 768.
Runtime Clients
Some 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 Essbase—The Essbase runtime client is installed automatically.

l Interactive Reporting l Microsoft SQL Server 2000 SP3a Analysis Services
l SQR Production l Microsoft SQL Server 2005 SP1 Analysis Services
Reporting
l Web Analysis
l Financial Reporting l Financial Management—The version of the Financial Management ADM driver and the version of Financial
l Web Analysis Management 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 a
component named Planning ADM Driver in the Planning installer.
Clients Runtime Client
Web Analysis l 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 Hyperion
Reporting and Analysis – System 9 Installation Guide.
Planning Essbase—The Essbase runtime client is installed automatically.
Disk Space and RAM

This 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® Foundation Smart View 45 MB, 50 MB for Smart View with Oracle's
Services Hyperion® Essbase® Visual Explorer
Essbase - System 9 Essbase Runtime Client 150 MB
UNIX Essbase Runtime Client 150 MB
Essbase Administration Services 150 MB

Console
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 Management Performance Management Architect 50 MB

Applications
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 Analysis

To perform chart generation in UNIX, Financial Reporting and Web Analysis UI services require
access to a graphics display device, either real or virtual. Hyperion recommends that an X virtual
frame buffer (Xvfb) be used instead of a hardware graphics display device (because Xvfb
performs all operations in memory and does not require that a screen or input device be attached
to the computer). See the Hyperion Reporting and Analysis – System 9 Installation Guide for
UNIX.
Web Browser Client Requirements
Web Browsers
Web 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 FDM does not support Firefox.

l Microsoft Internet Explorer 6.0
l Firefox 2.0.0.3
l Firefox 1.5.0.3
Set your browser to enable JavaScript and cookies. Storing cookies on your computer is
recommended; at a minimum, allow per-session (not stored) cookies. If a Web site is a trusted
site, enable SSL (HTTPS).
Web Browser Plug-in
Planning 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 Environment

A 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 11 l 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 13 l 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-defined
functions 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 the
Financial Management Win32 client, or when running the
Financial Reporting client against a Financial Management
application.
l One of the following: l A version of Microsoft Excel is required to use Smart View
with:
m Microsoft Office 2007
m Microsoft Office 2003 m Reporting and Analysis
m Microsoft Office XP (2002) m Financial Management
m Microsoft Office 2000 m Planning
Supported Software Notes
Microsoft SQL Server (2005 SP1 or 2000 SP3a) Analysis Services client Required only for:
l Interactive Reporting
l Financial Reporting1
l Web Analysis
l SAP GUI 6.20 OLE DB for OLAP Provider Required only for Interactive Reporting
l SAP GUI 6.4 OLE DB for OLAP Provider
SAP Java Connector (JCO) 2.1.7–Optional—used to connect to SAP BW.2 Required only for:
l Financial Reporting
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 must
match.
2Configurethe 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 and
authentication 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 9
This section lists the requirements for:
l Essbase
l Integration Services
l Provider Services
l Shared Services
Server Requirements
Essbase - 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: 32-bit x86

l Windows 2003 SP1
l Windows 2000 Server SP4
l Windows 2003 SP1 (Server Enterprise Edition) 64-bit Itanium 2 Administration Services and Provider Services only
support Windows 2003 64–bit if Tomcat is used as
the application server.
l Windows 2003 SP1 (Server Enterprise Edition) 64-bit x64 l For example, AMD Opteron or Intel Xeon.
l Supported with 32–bit or 64–bit installers
except for Administration Services and
Integration Services which are supported only
with 32–bit installers.
HP-UX: 32–bit Risc Release 9.3.1 is the last release to support HP-UX
11.11 Risc.
l HP-UX 11.11
HP-UX: 64–bit Risc Release 9.3.1 is the last release to support HP-UX
11.11 Risc.
l HP-UX 11.11
Note: All products are only supported on this
processor with 32–bit installer.
l HP-UX 11.31 64-bit Itanium 2 Administration Services and Provider Services only
support HP-UX 64-bit if Tomcat is used as the
HP-UX 11.23
application server.
l
IBM AIX: 32-bit PowerPC For AIX 5.2, Shared Services requires ML8.
l AIX 5.3 ML3
l AIX 5.2 ML7
l AIX 5.3 ML3 64-bit PowerPC Supported with 32–bit or 64–bit installers except
AIX 5.2 ML7 for Administration Services which is supported only
with 32–bit installer.
l
Oracle Enterprise Linux 4 32–bit x86
Red Hat Linux: 32-bit x86

l Red Hat Linux AS 4 Update 2 with glibc-2.3.4-2.13 or
later
Solaris: 32-bit SPARC V9

l Solaris 10
l Solaris 9
l Solaris 10 64-bit SPARC V9 Supported with 32–bit or 64–bit installers except

for Administration Services which is supported only
Solaris 9
with 32–bit installer.
l
Essbase - System 9 23
Disk Space and RAM
Disk space and RAM requirements are for Hyperion products and sample applications.
Component Disk Space RAM Notes
Essbase Server1 1 GB 1 GB
Application Programming 20 MB 256 MB minimum

Interface
Analytic Administration 500 MB2 32 MB times the number of concurrent Administration Server users
Server
For example, 32 MB * 10 users = 320 MB. For detailed RAM requirements, see the
Essbase 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 Essbase
Server.
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 security l Essbase See “Shared Services Requirements” on page
mode) 15.
l Provider Services
Essbase l 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 this
release of Essbase - System 9, see Chapter 4, “Release Compatibility.”
Repository Databases
A 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.
2Forall supported versions of Oracle: 1) Includes support for RAC - Real Application Cluster and ASM. Includes support for SE, SE1, EE. The
Oracle OLE provider and Oracle database server must be the same version.
Java Application Server

If an application contains more than 500 users and 10,000 measures, deploy to a Java application
server 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 Also includes support for WebLogic Express.

l BEA WebLogic 9.1
l BEA WebLogic 8.1.63
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 recommends
using 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.
3Hyperionrelease 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 manual
deployment.
Data Source Requirements
Database Connectivity
Database Connectivity applies only to Essbase SQL Interface and Integration Services.
For more information, see the Hyperion Essbase - System 9 Installation Guide and the Essbase
Integration Services Installation Guide.
Protocols Drivers Supported Notes
ODBC DataDirect 5.2 SP1
JDBC DataDirect 3.6 build 24
Reporting and Analysis

l Interactive Reporting
l SQR Production Reporting
l Web Analysis
l Workspace
l Shared Services
Server Requirements
Reporting 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: 32-bit x86

l Windows 2003 SP1
HP-UX: 64–bit Itanium 2 Interactive Reporting services run only in 32–

bit mode.
l HP-UX 11.31
Connectivity to Interactive Reporting data
HP-UX 11.23
sources in a 64–bit operating system requires
l
a 32–bit database client.
l HP-UX 11.111 32-bit RISC
IBM AIX: 32-bit2 PowerPC For AIX 5.2, Shared Services requires ML8.
l AIX 5.3 ML3
l AIX 5.2 ML7
Red Hat Linux: 32-bit x86

l Red Hat Linux AS 4 Update 2 with glibc-2.3.4-2.13 or later
Solaris: 32-bit SPARC

l Solaris 10
l Solaris 9
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.
Disk Space and RAM

Component Disk Space RAM
Workspace 1 GB 1 GB
For services: 200 MB For services: 1 GB minimum
For importing files: 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

Reporting and Analysis requires Shared Services. See also “Shared Services Requirements” on
page 15.
Required Third-Party Software

Software Required For Notes
l One of the following Distillers: Required only for Financial

Reporting2
m Adobe Acrobat Distiller Server 6.01
m AFPL Ghostscript 8.5.1, or GNU Ghostscript 7.0.6
One of the following: Interactive Reporting

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
One of the following: l Financial Reporting

l NetWeaver BI and SAP BW 7.0 connectivity require the use of SAP JCO 2.1.7 l SQR Production
Reporting
l For Microsoft SQL Server, you need Microsoft SQL Server (2005 SP1 or 2000 SP3a) Analysis
Services. The SSAS client and SSAS server versions must match. l Web Analysis
SQL Grid connectivity (Supports SQL Grid with Oracle, IBM DB2, and Microsoft SQL Server)—Merant l Financial Reporting
drivers 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's
Hyperion® Configuration Utility™, you must choose AFPL Ghostscript 8.5.1 or GNU Ghostscript 7.0.6.
One 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)
2Forall 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.
Java Application Servers and Web Servers

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

l Sun Java Enterprise System 8.1 05Q45 Does not apply to Shared Services
l Oracle 10g Release 3 (10.1.3.1.0) Includes support for Oracle Application Server Single Sign-On, for Workspace only.
2When
3Hyperionrelease 9.3.1 is the last release to support BEA WebLogic 8.1.6.
deployment.

5Supported on Solaris platforms only, via manual deployment; auto-deployment using Hyperion Configuration Utility is not supported for Sun
Java 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 and Notes
Connectivity
Hyperion data sources: one or more of the following:1 l Interactive Reporting—C API / MDX
l Essbase l Financial Reporting—ADM
l Web Analysis—ADM
l SQR Production Reporting—DDO
l Financial Management l Financial Reporting—ADM The version of Financial

Management ADM must match
Web Analysis—ADM
the version of Financial
l
Management Server
Connectivity
l Planning l Financial Reporting—ADM l Planning data sources only

Web Analysis—ADM apply to Financial
Reporting.
l
l Web Analysis supports

Planning only for access to
Essbase cubes.
l The version of Planning
ADM must match the
release of Planning Server.
l One of the following: SQR Production Reporting—ODBC Supported only by SQR

Production Reporting —
Microsoft Access 2007
Windows only
m
m Microsoft Access 2003

m Microsoft Access XP (2002)
m Microsoft Access 2000
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 SQR Production Reporting—ODBC, JDBC,
DB2 Connect
l IBM DB2 v7x for z/OS l Interactive Reporting—ODBC Supported only by:
l SQR Production Reporting—ODBC, JDBC, l Interactive Reporting
DB2 Connect
l Web Analysis
l IBM DB2: Not supported by:

m IBM DB2 OLAP Server 8.2 l Oracle's Hyperion®
IBM DB2 OLAP Server 8.1.7a Interactive Reporting
Studio
m
l Oracle's Hyperion®
Financial Reporting Studio
l Web Analysis
l Informix 9.4 and later SQR Production Reporting—ODBC, JDBC, Supported only by SQR
SDK 2.81 Production Reporting
l Informix 9.2 and later Interactive Reporting—ODBC Supported only by Interactive

Reporting

Connectivity
l Microsoft SQL Server: l Interactive Reporting—ODBC

m Microsoft SQL Server 2005 SP12 l SQR Production Reporting—ODBC, JDBC
m Microsoft SQL Server 2000 SP3a l Web Analysis—JDBC
l Microsoft SQL Server:3 l Interactive Reporting—ODBO

m Microsoft SQL Server 2005 SP1 Analysis l Financial Reporting—ADM
Services l SQR Production Reporting—DDO
m Microsoft SQL Server 2000 SP3a Analysis l Web Analysis—ADM
Services
l OpenEdge 10.1B SQR Production Reporting—ODBC Supported only by SQR

Production Reporting
l Oracle4: l Interactive Reporting—OCI, ODBC

m Oracle 11g5 l SQR Production Reporting—OCI, ODBC,
JDBC
m Oracle 10g Release 2 (10.2.0.2)
Web Analysis—JDBC
Oracle 10g (10.1.0.5)
l
m
m Oracle 9i (9.2.0.5)
l Progress 9.1E04 SQR Production Reporting—ODBC Supported only by SQR

l Red Brick 6.3 or higher l Interactive Reporting—ODBC Supported only by:

l SQR Production Reporting—ODBC l Interactive Reporting—
Windows only
—Windows only
SAP: l Financial Reporting—BAPI

l SAP BW 3.1 or 3.5 l Interactive Reporting—ODBO
l NetWeaver BI (SAP BW) 7.0 l SQR Production Reporting—BAPI
l Web Analysis—BAPI
SAP R/3 l SQR Production Reporting—BAPI Supported only by SQR

l SAP R/3 Enterprise (mySAP ERP 2005 ) 4.6C / 6.x
l Sybase 15 l Interactive Reporting—ODBC Supported only by:

CTLIB
l Sybase ASE 12.5.1 and 12.5.2 and later l Interactive Reporting—ODBC Supported only by:
CTLIB
Connectivity
l Sybase IQ 12.6 and later l Interactive Reporting—ODBC Supported only by:

l SQR Production Reporting—ODBC l Interactive Reporting—
Windows only
—Windows only
Teradata:6 l Interactive Reporting—ODBC Supported only by:

l Teradata V12.x (Teradata ODBC driver version 12.0) l SQR Production Reporting—ODBC, l Interactive Reporting
PP2(Solaris, PA-RISC HP-UX)
l Teradata V2R6.0.x (Teradata ODBC driver version 3. l SQR Production Reporting
06) Web Analysis—JDBC
Web Analysis
l
l
l Teradata V2R5.1.x (Teradata ODBC driver version 3.
05)
Teradata (ODBC):7 l Interactive Reporting—ODBC Not supported by Financial

SQR Production Reporting—ODBC, PP2 Reporting
l Teradata V12.x (Teradata ODBC driver version 12.0) l
(Solaris, PA-RISC HP-UX)
06) l Web Analysis—JDBC
05)
Teradata (JDBC):8 l Web Analysis—JDBC Not supported by Financial

Reporting
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)
1 data sources should be consistent with compatibility matrix. See Chapter 4, “Release Compatibility”
3Microsoft SQL Server Analysis Services, supported only by Windows-based Reporting and Analysis servers
4For all supported versions of Oracle: 1) Includes support for Real Application Cluster (RAC) and ASM. Includes support for SE, SE1, and EE.
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 Applications

l Performance Management Architect
l Planning
Financial Performance Management Applications 33

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 Pentium Supported only by:

4, 2 GHz
Windows 2000 Server SP4 Financial Management Server
minimum
l l
l Database Server for Financial Management

l Planning
l Windows 2003 SP1 32-bit Dual Pentium Supported only by: Strategic Finance Server2
2, 8 GHz
Windows 2000 Server SP4
minimum
l
l Windows 2003 SP13 64-bit Itanium 2 Not supported by:

l Windows 2000 Server SP4 l Financial Management
Planning supports Windows 2003 64-bit only for Planning

Web using Tomcat.
l HP-UX 11.23 64-bit Itanium 2 Not supported by:

Planning supports HP-UX 11.23 64-bit only for Planning
Web using Tomcat.
HP-UX: 32–bit PA-RISC Supported only by Performance Scorecard

l HP-UX 11.114
IBM AIX: 32-bit PowerPC Supported only by:

l AIX 5.3 ML3 l Performance Scorecard
l AIX 5.2 ML7 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

l Red Hat Linux AS 4 Update 2 with glibc-2.
3.4-2.13 or later
Solaris: 32-bit SPARC Supported only by:

l Solaris 10 l Performance Scorecard
l Solaris 9 l Planning
1For Financial Management, also install the following DCOM hot fix from Microsoft: http://support.microsoft.com/kb/899148
2Strategic Finance Server —Requires a Dual or Quad Pentium for 50 or more users connecting to the server to check entities in and out or to
run 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.
Disk Space and RAM

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 background
task logs, such as consolidation reports.

See the other sections in this chapter to check requirements for other required Hyperion
products.

Required Required For Notes
Software
Essbase (Essbase l Planning

Server and Performance Scorecard Server—for custom reporting through cube production
Administration
l
Services
components)
Performance l Financial Management—(Optional if you are using Classic Application Administration)

Management —Performance Management Architect is part of the Financial Management installation
Architect
Planning—(Optional if you are using Classic Application Administration)—Performance
(optional)
l
Management Architect is part of the Planning installation
Shared Services l Financial Management See “Shared Services

Requirements” on
Planning
page 15.
l
l Performance Scorecard (unless using Performance Scorecard in native authentication

mode)
l Strategic Finance—Shared Services is required if importing and exporting with Financial
Management, Planning, or Essbase, or if using a security provider other than NTLM, such
as LDAP
Workspace l 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) Required only for Strategic Finance
PKZip 8.0 (command-line interface) for database backup Strategic Finance
1If using Performance Management Architect, Microsoft .NET Framework 2.0 is installed automatically by the Planning or Financial Management
setup program if not already installed.
Products that require a data repository:
l Planning
l Shared Services
Relational Data Repositories Notes
If you use an IBM DB2 database for Performance Management Architect, DB2 9 Runtime Client
and DB2 .NET Data Provider 9.1.0.2 must be installed on the Performance Management Architect
IBM DB2 9.1
Dimension server.
l
l IBM DB2 8.2
l Microsoft SQL Server 2005 SP1 By default, SQL Server 2005 disables TCP/IP connections to the database. Ensure that the TCP/
l Microsoft SQL Server 2000 SP3a IP connections are enabled.
Oracle1: l For all supported versions of Oracle, the Oracle OLE provider and Oracle database server must
be the same version.
l Oracle 11g2
Performance Management Architect—The Oracle client must be installed on the Dimension
Oracle 10g Release 2 (10.2.0.2)
l
server.
l
l Oracle 10g (10.1.0.5)

l Oracle 9i (9.2.0.5
1Forall supported versions of Oracle: 1) Includes Support for Real Application Cluster (RAC) - and ASM. Includes support for SE, SE1, and EE.

A Java application server is required only for:
l Planning
l Shared Services
Java Application Servers Notes

l BEA WebLogic 9.1



2When
deployment.
The following products require a Web server:

l Planning
Web Server Notes
Windows: l Performance Management Architect—Uses only IIS 6.0 or 6.0 for Web Services
l Microsoft IIS 6.0 (on Windows 2003 SP1) l Financial Management—Uses only IIS
l Microsoft IIS 5.0 (on Windows Server 2000 SP4) l Planning—Can use an internal WebLogic or WebSphere Web server
UNIX: Not supported for:

Apache Server 2.0.52 l Performance Management Architect
Data Management
l Data Integration Management
l FDM
l Data Relationship Management
l Translation Manager
l Shared Services
Server Requirements
l “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: 32-bit x86

l Windows 2003 SP1
l Windows 2003 SP1 32–bit Pentium 4 Supported by:

l Windows 2000 Server SP4 l FDM Web Server—per 75 concurrent users
l Translation Manager2
l Windows 2003 SP1 32–bit Dual Pentium Supported by:

4, 2 GHz
l Windows 2000 Server SP4 l FDM Application Server—per 75 concurrent users
l Data Relationship Management—Application
Server
l Data Relationship Management—Database Server
l Windows 2003 SP1 32–bit Quad Pentium Supported by only FDM Database Server
4
HP-UX 11.113 32-bit PA-RISC Supported by only Data Integration Management
IBM AIX: 32-bit PowerPC Supported by:

l AIX 5.3 ML3 l Data Integration Management
l AIX 5.2 ML7 l Translation Manager
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
l Red Hat Linux AS 4 Update 2 with glibc-2.3.
4-2.13 or later
Solaris: 32-bit SPARC Supported by:

l Solaris 10 l Data Integration Management
l Solaris 9 l Translation Manager
1FDM—FDM Web Server runs on Windows 2000 server only if no other .NET applications are installed. Not recommended.
2TranslationManager—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 or
WebLogic application server (for use with other products — FDM does not use a Java
application server).
Disk Space/RAM
Data Integration Management:
PowerCenter Repository Server1 150 MB 256 MB
PowerCenter Server 70 MB 256 MB
FDM Database Server l Dependent on size of the FDM application 1 GB per 75 concurrent users (2 GB
minimum)
l Multiple HDDs to spread processing
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- 2 GB minimum 2 GB

Database Server2
Data Relationship Management- 100 MB 4 GB

Application Server
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 specify
the 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 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 are For FDM, the required components:
deployed, one or more products:
l Workbench Client
Essbase
Application Server
l
l
l Oracle's Hyperion® Enterprise®
l Planning

Requirement Notes
l Microsoft MDAC 2.6 or later—MDAC is installed by FDM. Required only for

FDM Application
Excel 2000 or later
Server
l
l Microsoft IIS 6.0 (on Windows Server 2003) Required only for
l Microsoft MDAC 2.6 or later—MDAC is installed by FDM. FDM Web Server
l Optional—Additional client software, such as Oracle SQL*Plus for Oracle and Query Analyzer for SQL Server, can Required only for
be used for verifying connectivity and for troubleshooting. ODBC can also be used for troubleshooting. Data Relationship
Management -
A set of client drivers:
Application Server
l
m Microsoft SQL Server client drivers (DLLs)1

m Oracle client drivers (DLLs)
l Microsoft IIS 5.0 or later
l Microsoft .NET Framework
For bridging to IIS, a vendor-supplied application server connector: Required only for
Translation
(Windows only) Apache Tomcat connector Manager
l
l WebLogic connector
l IBM HTTP server for WebSphere
1Ifusing 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, the
installation program automatically updates it to the latest version. If MDAC is not installed, or if the installed version is earlier than 2.7, you
must manually install MDAC.
A repository database is required only for:
l FDM
l Shared Services
Data Management 41
Relational Data Repositories Notes
l IBM DB2 8.2 Not supported by FDM or Data Relationship Management

l IBM DB2 9.1
l Microsoft SQL Server 2005 SP1 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)
1Forall supported versions of Oracle: 1) Includes Support for Real Application Cluster (RAC) and ASM. Includes support for SE, SE1, and EE.

A Java application server is required only for:
l Shared Services
l BEA WebLogic 9.22 Translation Manager supports only WebLogic 9.1.

l BEA WebLogic 8.16

2When
deployment.
Database Connectivity
Data Integration Management PowerCenter Server requires Native drivers for database
connectivity.
Translation Manager requires ODBC protocol and the DataDirect 5.2 SP1 driver.
Data Management 43
Release Compatibility
4
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 Chapter

To ensure that you obtain the correct information from the tables in this chapter, read down
each column to identify the versions of other Hyperion products that are compatible with the
product 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 Compatibility

Release 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 Shared
Services 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 Compatibility
Table 2 Essbase - System 9 Release Compatibility
Essbase 9.3.1 Administration Services Integration Provider

9.3.1 Services 9.3.1 Services 9.3.1
Foundation Services
Compatible Shared Services 9.3.1 9.3.1 NA 9.3.1

versions
Compatible Smart View versions 9.3.x NA NA 9.3.x
Essbase - System 9
Compatible Essbase versions NA 9.x 9.x 9.x

7.1.6 7.1.6 7.1.6
Compatible Administration 9.3.x NA 9.3.x NA

Services versions
7.1.6
Compatible Provider Services 9.x 9.3.x NA NA

versions
Compatible Integration Services 9.3.x NA NA NA

versions
7.1.6
Compatible Financial Reporting 9.3 NA NA NA

versions
9.2
Compatible SQR Production 9.3 NA NA NA

Reporting versions
9.2
Compatible Interactive 9.3.x NA NA NA

Reporting versions
Compatible Web Analysis 9.3 NA NA NA

versions
9.2
Compatible Oracle's Hyperion® 9.3 NA NA NA

Application Builder J2EE
9.2
versions
Compatible Planning versions 9.3.x 9.3.x NA NA

1 9.2.x 9.2.x
4.1 4.1
46 Release Compatibility
Essbase 9.3.1 Administration Services Integration Provider
9.3.1 Services 9.3.1 Services 9.3.1
Compatible Financial 9.3.x NA NA NA

Management versions
9.2.x
2
4.1
Compatible Performance 9.3.x NA NA NA

Scorecard versions
9.2.x
9.0.1
4.1
4.0.5
4.0.1
4.0
Compatible Strategic Finance NA NA NA NA

versions
Data Management
Compatible Data Relationship All versions through flat files NA NA NA

Management versions
Compatible FDM versions 9.2 NA NA NA

9.3
9.3.1
Compatible Data Integration 9.3.1 NA NA NA

Management versions
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 Compatibility

Table 3 Reporting and Analysis Release Compatibility
Interactive Reporting Financial Reporting 9.3.1 SQR Production Web Analysis 9.3.1
9.3.1 Reporting 9.3.1
Foundation Services
Compatible Shared Services 9.3.1 9.3.1 9.3.1 9.3.1

versions1
Compatible Smart View 9.3.x 9.3.x 9.3.x 9.3.x

versions
Reporting and Analysis Release Compatibility 47

Interactive Reporting Financial Reporting 9.3.1 SQR Production Web Analysis 9.3.1
9.3.1 Reporting 9.3.1
Essbase - System 9
Compatible Essbase versions 9.3.x 9.3.x 9.3.x 9.3.x

9.2.x 9.2.x 9.2.x 9.2.x
7.2 7.2 7.2 7.2
7.1.x 7.1.x 7.1.x 7.1.x
Compatible Administration NA NA NA NA
Services versions
Compatible Provider Services NA 9.3.1 NA 9.3.1

versions
Compatible Integration NA 9.3.x 9.3.x 9.3.x

Services versions
9.2.x 9.2.x 9.2.x
9.0 9.0 9.0
Compatible Application NA NA NA NA
Builder J2EE versions
Compatible Planning versions NA 9.3.x NA 9.3.x

9.2.x 9.2.x
4.0.5 4.0.5
Compatible Financial NA 9.3.x NA 9.3.x

Management versions
9.2.x 9.2.x
4.0.2 4.0.2
Compatible Performance NA NA NA NA
Scorecard versions
Compatible Strategic Finance NA NA NA NA

versions
Data Management
Compatible Data Relationship NA NA NA NA

Management versions
Compatible FDM versions NA NA NA NA
Compatible Data Integration NA NA NA NA

Management versions
1Shared Services is not needed for standalone products
Release Compatibility
Table 4 Financial Performance Management Applications Release Compatibility
Planning 9.3.112 Financial Management 9. Performance Scorecard Strategic Finance

3.1 9.3.1 9.3.1
3
Foundation Services
Compatible Shared Services 9.3.1 9.3.1 9.3.1 9.3.1

versions
Compatible Smart View 9.3.1 9.3.x NA NA

versions
9.2.x
Essbase - System 9
Compatible Essbase versions 9.3.1 9.3.x 9.3.x 9.3.x

9.2.x 9.2.x 9.2.x (7.1.2 API)
9.0.1 7.1.x
7.1.x
Compatible Administration 9.3.1 9.3.x NA NA

Services versions
9.2.x
Compatible Provider Services NA NA NA NA

versions
Compatible Integration NA NA 9.3.x NA

Services versions
9.2.x
9.0.1
7.1.x
Compatible Financial 9.3.1 9.3.x NA NA

Reporting versions
9.3.0.1
Compatible SQR Production NA NA NA NA

Reporting versions
Compatible Interactive NA NA Through IR Smartcuts NA

Reporting versions
Compatible Web Analysis 9.3.x 9.3.x Through Extended NA

versions Analytics
9.2.x
Financial Performance Management Applications Release Compatibility 49

Planning 9.3.112 Financial Management 9. Performance Scorecard Strategic Finance
3.1 9.3.1 9.3.1
3
Compatible Oracle's NA 9.3.x NA NA

Hyperion® Application Builder
J2EE versions
Compatible Planning versions NA 9.3.x The version deployed

with Essbase
9.2.x
4.1.1
Compatible Financial 9.3.1 NA 9.3.x

Management versions
9.2.x
4.1.1
Compatible Performance NA 9.3.x NA NA

Scorecard versions
Compatible Strategic Finance NA 9.3.x NA NA

versions
Data Management
Compatible Data All versions through All versions through flat files NA NA
Relationship Management flat files
versions
Compatible FDM versions The version deployed 9.3.x NA NA

with Essbase
Compatible Data Integration 9.3.1 9.3.x NA

Management versions
1IncludesOracle's Hyperion® Workforce Planning and Capital Expense Planning

2You 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 Management FDM 9.3.1 Data Integration

9.3.1 and 9.3.2 Management 9.3.1
Foundation Services
Compatible Shared Services 9.3.1 NA 9.3.1

versions
Compatible Smart View versions NA NA NA
Data Relationship Management FDM 9.3.1 Data Integration
9.3.1 and 9.3.2 Management 9.3.1
Essbase - System 9
Compatible Essbase versions All versions through flat files 9.3.x 9.3.x
9.2.x (7.1.2 API) 7.1.x
7.1.x
Compatible Administration All versions through flat files NA NA

Services versions
Compatible Provider Services NA NA NA

versions
Compatible Integration Services NA NA NA

versions
Compatible Planning versions All versions through flat files The version deployed with 9.3.x
Essbase
Compatible Financial All versions through flat files 9.3.x 9.3.x

Management versions
9.2.x
4.1.1
Compatible Performance NA NA 9.3.x

Scorecard versions
Compatible Strategic Finance NA All versions through flat files NA

versions
Data Management Release Compatibility 51

Hyperion License Compliance
5
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 Compliance

Oracle's Hyperion® License Server™ and standalone licenses are no longer used for license
management. Instead, administrators must audit product use for all products.
To ensure compliance with your license agreement, Hyperion recommends that you activate or
deactivate 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 Features

During product configuration with Hyperion Configuration Utility, on the Product Options
panel, activate or deactivate features according to your license agreement. See the “Configuring
and Setting Up” chapter in the relevant product installation guide, and review your license
agreement to identify features that you are authorized to use.
During product configuration, Hyperion Configuration Utility copies
registry.properties to <Hyperion_Home>\common\config on the server on which you
ran Hyperion Configuration Utility.
After configuration (and before you validate the installation) you must open this file in any text
editor to review and specify which product options are activated. You must complete this step
to ensure you comply with your license agreement and to activate features you are licensed to
use.
Note: You do not need to complete this step for the following products:
l Data Integration Management
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 on
which 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 or
product is:
<feature_name>=true|false, true|false
The first entry indicates whether to activate the feature. The second entry is for internal use
only 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 to
use and false for products or features you are not licensed to use. Ignore the second entry in each
line of the file.
See “About registry.properties” on page 54 for information about the options in
registry.properties.
4 Save the file.
5 Restart the Hyperion services related to any of the entries you changed.
About registry.properties
The values you specify in registry.properties depend on which products and features you
purchased. Consult the following tables for information about the features available for each
product.
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 in
registry.properties.
If the entry in your registry.properties file is not the same as the entry in the Value column
for 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 page
59
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 page
63
l For Hyperion System 9 Planning and Hyperion Planning – System 9, see Table 12 on page
64
l For Hyperion System 9 Strategic Finance and Hyperion Strategic Finance, see Table 13 on
page 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 purchased

Hyperion System 9 BI+ Visual Explorer Option.
Hyperion System 9 BI+ Analytic High Availability Services

Option
ANALYTICS_HIGHAVAIL_OPT True Only change this value to True if you purchased

Hyperion System 9 BI+ Analytic High Availability
Services Option.
Hyperion System 9 Windows Developer Toolkit
ANALYTICS_SSTOOLKIT_OPT True Only change this value to True if you purchased

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

Hyperion System 9 BI+ Application Builder J2EE Option
ANALYTICS_HABJ2EE_OPT True Only change this value to True if you purchased

Hyperion System 9 BI+ Application Builder J2EE
Option.
Hyperion System 9 BI+ Analytic Integration Connector for

SAP BW Option

ANALYTICS_SAPINTEGCONN_OPT Only change this value to True if you purchased

Hyperion System 9 BI+ Analytic Integration Connector
for 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 purchased


Option
ANALYTICS_HIGHAVAIL_OPT TRUE Only change this value to True if you purchased

Services Option.
ANALYTICS_SSTOOLKIT_OPT TRUE Only change this value to True if you purchased

ANALYTICS_APPBUILDRNET_OPT TRUE Only change this value to True if you purchased

ANALYTICS_HABJ2EE_OPT TRUE Only change this value to True if you purchased

Option.

SAP BW Option
ANALYTICS_SAPINTEGCONN_OPT TRUE Only change this value to True if you purchased

for SAP BW Option.
The following table contains the feature values to use when you purchase Enterprise Analytics
and 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 purchased


Option
ANALYTICS_HIGHAVAIL_OPT TRUE Only change this value to True if you purchased

Services Option.
ANALYTICS_SSTOOLKIT_OPT TRUE Only change this value to True if you purchased

ANALYTICS_APPBUILDRNET_OPT TRUE Only change this value to True if you purchased


ANALYTICS_HABJ2EE_OPT TRUE Only change this value to True if you purchased

Option.

SAP BW Option
ANALYTICS_SAPINTEGCONN_OPT TRUE Only change this value to True if you purchased

for 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 the
Hyperion 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 the
System 9 BI+ Financial Reporting module.
Hyperion System 9 BI+ SAP BW Adapter for Financial

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

Reporting & Web Analysis Option

FINANCRPTG_SAPBW_OPT TRUE Only change this value to True if you purchased Hyperion
WEBANLYSIS_SAPBW_OPT TRUE Only change this value to True if you purchased Hyperion
Hyperion System 9 BI+ Production Reporting
PRODCTNRPTG_STNDALONE TRUE Only change this value to True if you purchased Hyperion
System 9 BI+ Production Reporting.
PRODCTNRPTG_HPITA_HPUX_OPT TRUE Only change this value to True if you purchased Hyperion
PRODCTNRPTG_RSC_HPUX_OPT TRUE Only change this value to True if you purchased Hyperion
PRODCTNRPTG_IBM_AIX_OPT TRUE Only change this value to True if you purchased Hyperion
PRODCTNRPTG_INTL_LNX_OPT TRUE Only change this value to True if you purchased Hyperion
PRODCTNRPTG_INTL_WIN_OPT TRUE Only change this value to True if you purchased Hyperion
PRODCTNRPTG_SPARC_SUN_O TRUE Only change this value to True if you purchased Hyperion
PRODCTNRPTG_SYBASE_OPT TRUE Only change this value to True if you purchased Hyperion
PRODCTNRPTG_ORACLE_OPT TRUE Only change this value to True if you purchased Hyperion
PRODCTNRPTG_INFORMIX_OPT TRUE Only change this value to True if you purchased Hyperion
PRODCTNRPTG_DDO_OPT TRUE Only change this value to True if you purchased Hyperion
PRODCTNRPTG_DB2_OPT TRUE Only change this value to True if you purchased Hyperion
PRODCTNRPTG_ODBC_OPT TRUE Only change this value to True if you purchased Hyperion
PRODCTNRPTG_TERADATA_OPT TRUE Only change this value to True if you purchased Hyperion
Hyperion System 9 BI+ SAP & SAP BW Adapter for

Production Reporting Option

PRODCTNRPTG_SAPBW_OPT TRUE Only change this value to True if you purchased Hyperion
System 9 BI+ SAP & SAP BW Adapter for Production
Reporting Option.
PRODCTNRPTG_SAPR3_OPT TRUE Only change this value to True if you purchased Hyperion
System 9 BI+ SAP & SAP BW Adapter for Production
Reporting 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 Hyperion
Interactive Reporting – System 9 module.
BI+_IMPACTASSMT_OPT TRUE Only change this value to True if you purchased the Hyperion
BI+_IMPACTUPDATE_OPT TRUE Only change this value to True if you purchased the Hyperion
Hyperion Financial Reporting – System 9
FINANCRPTG_BASESOLUTION TRUE Only change this value to True if you purchased the Hyperion
Financial Reporting – System 9 module.
FINANCRPTG_SAPBW_OPT TRUE Only change this value to True if you purchased the Hyperion
Financial Reporting – System 9 module.
Hyperion Web Analysis – System 9
WEBANLYSIS_BASESOLUTION TRUE Only change this value to True if you purchased the Hyperion Web
Analysis – System 9 module.
WEBANLYSIS_SAPBW_OPT TRUE Only change this value to True if you purchased the Hyperion Web
Analysis – System 9 module.
Hyperion SQR Production Reporting – System 9
PRODCTNRPTG_STNDALONE PT TRUE Only change this value to True if you purchased Hyperion SQR
Production Reporting – System 9.
PRODCTNRPTG_HPITA_HPUX_OPT TRUE Only change this value to True if you purchased Hyperion SQR
PRODCTNRPTG_RSC_HPUX_OPT TRUE Only change this value to True if you purchased Hyperion SQR
PRODCTNRPTG_IBM_AIX_OPT TRUE Only change this value to True if you purchased Hyperion SQR

PRODCTNRPTG_INTL_LNX_OPT TRUE Only change this value to True if you purchased Hyperion SQR
PRODCTNRPTG_INTL_WIN_OPT TRUE Only change this value to True if you purchased Hyperion SQR
PRODCTNRPTG_SPARC_SUN_O TRUE Only change this value to True if you purchased Hyperion SQR
PRODCTNRPTG_SYBASE_OPT TRUE Only change this value to True if you purchased Hyperion SQR
PRODCTNRPTG_ORACLE_OPT TRUE Only change this value to True if you purchased Hyperion SQR
PRODCTNRPTG_INFORMIX_OPT TRUE Only change this value to True if you purchased Hyperion SQR
PRODCTNRPTG_DDO_OPT TRUE Only change this value to True if you purchased Hyperion SQR
PRODCTNRPTG_DB2_OPT TRUE Only change this value to True if you purchased Hyperion SQR
PRODCTNRPTG_ODBC_OPT TRUE Only change this value to True if you purchased Hyperion SQR
PRODCTNRPTG_TERADATA_OPT TRUE Only change this value to True if you purchased Hyperion SQR
PRODCTNRPTG_SAPBW_OPT TRUE Only change this value to True if you purchased Hyperion SQR
PRODCTNRPTG_SAPR3_OPT TRUE Only change this value to True if you purchased Hyperion SQR
Table 12 Hyperion System 9 Planning and Hyperion Planning – System 9
PLANNING_BASESOLUTION TRUE
PLANNING_OFFLINEUSE_OPT TRUE
Hyperion Workforce Planning and Hyperion System® 9

Workforce Planning
PLANNING_WRKFORCEPLNG_OPT TRUE Only change this value to True if you purchased

Hyperion Workforce Planning or Hyperion System® 9
Workforce Planning.
Hyperion Capital Expense Planning and Hyperion System 9

Capital Expense Planning

PLANNING_CAPEXPLNG_OPT FALSE Only change this value to True if you purchased

Hyperion Capital Expense Planning or Hyperion System
9 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 Usage
You must audit services and users in accordance with your license agreement and the Software
Copy and Use Schedule.
To audit users, create a provisioning report. See “Generating Provisioning Reports” in the
Hyperion Security Administration Guide. A provisioning report provides a list of users
provisioned to each application, either directly or through a group.
Retrieving License Keys for Data Integration

Management
If you have purchased licenses for Data Integration Management, retrieve full use license keys
from 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 continue
to export validation.
Auditing Usage 65
2 Select the Hyperion Performance Management and BI product pack and a platform, and then click
Go.
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, and
save the file in a temporary directory.
5 Extract the contents of the downloaded file, including license_dim.doc, into the temporary
directory.

Planning Hyperion Product
6 Installations
In This Chapter
Planning Installations......................................................................................67
Preparing Databases ......................................................................................71
Preparing Java Application Servers.......................................................................72
Planning Installations
Use the following checklist to prepare for installing Hyperion products. Hyperion recommends
that 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 When

Completed ✓
Preparing the work area
Prepare a work area for l Internet access—a direct connection outside the firewall
consultants who are Work area and computer (ideally located where the servers on which you are installing
assisting with the
l
Hyperion products are located), with network access
installation.
l Telephone
Ensure that you can access

the Oracle® E-Delivery site.
Obtaining third-party
licenses
Obtain required third-party Some third-party products require license keys or license files. Requesting and receiving
license keys. a license key can require several days.
For Java application servers, consider which type of license works best for your
organization. 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 files Download from the Oracle® E-Delivery site.
from the media packs for the
Organize the files on the server and unzip compressed files.
products that you purchased.
Planning Installations 67
Completed ✓
Ensure that the products See Chapter 4, “Release Compatibility.”

meet release compatibility
requirements.
Install all third-party For system requirements, see Chapter 3, “System Requirements.”
components required by
Ensure that you have obtained all licenses required by third-party software.
Hyperion products.
Validate that all third-party For system requirements, see Chapter 3, “System Requirements.”
product versions meet
system requirements.
Gathering required
documentation
Download the Hyperion Download the following files from the Oracle® E-Delivery site:
installation and product
This guide, the Hyperion Installation Start Here
documentation for the
l
products that you purchased. 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 necessary For assistance in planning your deployment architecture, see the Hyperion System 9 BI
hardware is available for your + Performance whitepaper, available on the Oracle Technology Network site. For system
deployment architecture, requirements, see Chapter 3, “System Requirements.”
and verify that the computers
meet system requirements.
Prepare each server for the l Update server software as needed. For example, ensure that any required service
Hyperion products packs, hotfixes, and so on are installed.
installation.
l Disable unnecessary services.
If applicable, ensure that IT Ensure that the load balancing or failover is tested and ready prior to starting the
prepares the load balancer installation.
(hardware, software) or the
failover mechanism (such as
Veritas Cluster Server).
Check network bandwidth

and latency for distant sites
and ensure that minimum
requirements are met.
Synchronize server time. When servers are not time synchronized, authentication errors that result in user access
problems can occur between the Hyperion application servers.
68 Planning Hyperion Product Installations

Completed ✓
Arrange backup After the installation, Hyperion advises that you perform a full backup of all servers and
functionality. databases. After the initial backup, include servers and databases in daily backup
procedures.
Preparing databases
If necessary, install a l Set up database client access from the servers to the database setup.
database client. l Set up user accounts to access the database.
l If you are using an Oracle database, test the database client with the TNSPing
command.
If the database is installed, perform a full backup.
Prepare a database for each To identify the products that require a database and to view the list of supported
Hyperion product that databases, see Chapter 3, “System Requirements.”
requires a database for
For database considerations, see “Preparing Databases” on page 71 and the
relational storage.
installation guides for the relevant products.
Test UDL connectivity to the

databases you created, if
required for your product.
Preparing the security

infrastructure
Collect the information See “Configuring User Directories” in the Hyperion Security Administration Guide.
needed to configure external
Note: If you are upgrading and want to support the movement of users and groups
user directories in User
across Organizational Units (OUs), you must configure user directories in Shared Services
Management Console.
to use a unique identity attribute to identify users and groups. See “Configuring User
Directories” in the Hyperion Security Administration Guide.
For each server, prepare a l For Windows systems, create a user ID with Local Administrative rights to the machine.
user account with Hyperion recommends that you do not use the local system account to install.
Administrator rights. The
For UNIX systems, create a user account with Administrator privileges with control
installation can be a local
l
over its area of the file system. The account that is used to install Hyperion products
administrator account.
must have Read, Write, and Execute permissions on $HYPERION_HOME.
l Assign local policies as needed. (For Windows, the user ID typically requires “Act as
part 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
Completed ✓
Prepare a service account for l Create a service account with Browse privileges for the user directory.
external authentication Ensure that the service account name does not include special characters.
against the user directory you
l
are using. l Ensure that the service account's Distinguished Name (DN) can access the user
directory.
l Note the user directory port.
l Be familiar with the name of a Primary Domain Controller that can access MSAD (if
applicable).
l Ensure that the server can communicate with the user directory.
See the Hyperion Security Administration Guide.
If you are using secure See Hyperion Product SSL Configuration Guide.
communication, ensure
availability of SSL certificates
for all components. Hyperion
recommends using SSL for
Hyperion product
installations.
Open firewall ports and fix See Chapter 7, “Ports.”

dynamic ports if needed.
If you are using OpenLDAP, See the Hyperion Security Administration Guide.
consider whether you want to
provision by user or by group.
If you are provisioning by
group, decide whether to use
OpenLDAP groups or external
authentication provider
groups.
Setting up Java application

servers and Web servers
Ensure that Java application l To identify the products that require an application server and to view the list of
servers are available for supported application servers, see Chapter 3, “System Requirements.”
Hyperion product
A default product installation provides the Jakarta Tomcat Apache Web application
deployment. The application
l
server.
server and the product that
you are deploying must be l Ensure that you have obtained all required licenses.
installed on the same Ensure that you have root access to the application server installation directory. (For
computer.
l
WebSphere, 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 Java
Application Servers” on page 72.
Install a Web server to use To identify the products that require a Web server and to view the list of supported Web
with Hyperion products that servers, see Chapter 3, “System Requirements.”
require a Web server.

Completed ✓
If you are using software load

balancing, in the Web server,
prepare the load balancer
plug-in to the Java
application server.
Resolving ports
Identify and resolve port Review the list of Hyperion product default ports in Chapter 7, “Ports.”
conflicts.
Preparing for product

configuration
Collect the information See Chapter 9, “Configuration Worksheets.”

needed to configure products
after installation.
Review your license During configuration, activate or deactivate features based on your license agreement.
agreement to confirm which After you configure each product, you must open registry.properties—in
products you have <Hyperion_Home>\common\config on the server on which you ran Hyperion
purchased and are licensed Configuration Utility—to review and edit the product options. You must complete this step
to use. to ensure you comply with your license agreement and to activate features you are
licensed to use. See Chapter 5, “Hyperion License Compliance.”
Before installing Hyperion When Hyperion products are installed, common internal and third-party components are
products, consider the installed to a central location, called Hyperion Home. Hyperion Home typically exists on
location of Hyperion Home. each 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 product
installation. Subsequent installations on a computer use the previously defined location.
The location can be changed only by running a migration utility, so consider the location
carefully.
Installing and configuring

Shared Services
Before installing other Shared Services is a shared infrastructure for Hyperion products. Shared Services provides
Hyperion products, install security, authentication, user management, metadata management, and taskflow
and configure Shared automation.
Services.
Follow the instructions in the Hyperion Shared Services Installation Guide to install and
configure Shared Services. See the Hyperion Security Administration Guide for
information about configuring user directories.
Note: Some products do not require Shared Services.
Preparing Databases
Many Hyperion products require a relational repository. Set up the databases and test
connectivity before installing Hyperion products.
Preparing Databases 71
General Considerations
l 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 databases
specifically, users must be assigned the RESOURCE role.
l Some products require that you modify certain database parameters (for example, increasing
heap size). See the product installation guides for detailed instructions on modifying
database parameters.
l See the product installation guides for detailed procedures on creating databases.
Oracle
l User IDs should have the following roles: CONNECT, RESOURCE, CREATE, CREATE
TRIGGER, DROP TRIGGER, MODIFY TRIGGER, CREATE PROCEDURE, ALTER
SESSION.
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 DB2
The database must be created using UTF-8.
Preparing Java Application Servers

Many Hyperion products require a Java application server.
General Considerations
l When deploying to an application server, Hyperion products cannot be installed to
directories with names that contain spaces; for example, c:\Program Files is not
acceptable.
l Set all Web applications to have a session timeout that exceeds 10 minutes.
Apache Tomcat
l Hyperion supports Apache Tomcat application server, which is provided on the installation
media for use with the deployment of Hyperion products. Hyperion does not support
Apache Tomcat application server for use outside Hyperion product installations.

BEA WebLogic
l If BEA WebLogic application server is not installed in BEA_HOME, Hyperion products
cannot be automatically deployed to WebLogic using Hyperion Configuration Utility. If
you install in such an environment, use the manual deployment option to create the Web
archive and use the WebLogic application deployment tool to deploy the application to the
required instance.
l The user account that installs and configures the Hyperion product being deployed must
have read and execute permission to the WebLogic installation directory.
IBM WebSphere
l 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 product
being deployed must have permission to create a WebSphere profile. Refer to the IBM
InfoCenter for detailed instructions on granting permission to create a WebSphere profile
as a non-root user.
l If WebSphere is installed as root, you must grant Write permissions to the WebSphere
installation folder to enable Hyperion Configuration Utility to make required modifications
to WebSphere configuration files.
l Hyperion products cannot deploy to WebSphere if the WebSphere installation path contains
spaces. The default WebSphere installation path for Windows is C:\Program Files\IBM
\WebSphere. Change the installation path so that no spaces are included.
Oracle 10g
Ensure that you have root access to the application server installation directory on AIX systems.
Preparing Java Application Servers 73

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

During Hyperion product deployments, default port numbers for application servers are
automatically populated. During configuration, you can change the default numbers. Each port
number must be unique. If an error message similar to “port already in use” or “bind error” is
displayed, a port number conflict might exist.
If the default port number is not changed, the software is configured with the default values.
Shared Services Ports

Table 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 Port Where Configurable

Number
Hyperion Remote 58000 Hyperion Remote Authentication Module installation program

Authentication
Module Additional Not configurable
dynamic port (1)
OpenLDAP 58089 l 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 Port

Use this procedure if you want to run OpenLDAP on a non-default port. You cannot update
the 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/config
directory. For example, if Shared Services is deployed on Tomcat, this directory, on Windows, could be
C:\Hyperion\deployments\Tomcat5\SharedServices9\config
2 Edit the CSS.xml file and update the dirPort from the default 58089 to the custom port and save
it.
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 the
Urls 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 the
changes.
4 Restart OpenLDAP and Shared Services.
5 Restart all other System 9 products.
76 Ports
Essbase - System 9 Ports
l “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 Ports
Table 19 Essbase Default Service Ports

Number
Essbase Agent 1423 l 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 server 32768– Essbase configuration file (ARBORPATH\bin\Essbase.cfg)

applications 33768 (two
To limit the range and set the increment for these ports, modify the file to include these settings:
(ESSSVR) ports per
ServerPortBegin, ServerPortEnd, PortInc
process)
For instructions, see the Essbase Technical Reference, “Essbase.cfg Configuration Settings.”
Integration 3388 <AIS_HOME>/bin/ais.cfg

Services Server
Add -Pportnumber
Administration Services Ports

Table 20 Administration Services Web Application Ports
Port Type Default Port Where Configurable

Number
Listen port 10080 l 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

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

port server.xml

deployments/<AppServNameAndVersion>/aas/conf/server.xml

Shutdown 10081 l Deployed Tomcat deployment (via Hyperion Configuration Utility): <Hyperion_Home>/
port for deployments/<AppServNameAndVersion>/aas/conf/server.xml
For default
Apache
Tomcat Parameter: Connector port
Tomcat
deployment only:
Default Tomcat deployment: <aas_home>/deployments/tomcat/5.0.28/conf/
10005
l
server.xml

AJP 10082 l Deployed Tomcat deployment (via Hyperion Configuration Utility): <Hyperion_Home>/
connector deployments/<AppServNameAndVersion>/aas/conf/server.xml
For default
port
deployment only:
Default Tomcat deployment: NA
NA
l
Provider Services Ports

Table 21 Provider Services Web Application Ports

Number

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

deployments/<AppServNameAndVersion>/aps/conf/server.xml

78 Ports
Number
SSL listen 13090 l Default Tomcat deployment: <aps_home>/deployments/tomcat/5.0.28/conf/

port server.xml

deployments/<AppServNameAndVersion>/aps/conf/server.xml

Shutdown 13081 l Deployed Tomcat deployment (via Hyperion Configuration Utility): <Hyperion_Home>/
port for deployments/<AppServNameAndVersion>/aps/conf/server.xml
For default
Apache
Tomcat
deployment only:
Default Tomcat deployment: <aps_home>/deployments/tomcat/5.0.28/conf/
13005
l
server.xml

AJP 13082 l Deployed Tomcat deployment (via Hyperion Configuration Utility): <Hyperion_Home>/
connector deployments/<AppServNameAndVersion>/aps/conf/server.xml
For default
port
deployment only:
Default Tomcat deployment: NA
NA
l
Smart Search Ports

Table 22 Smart Search Web Application Ports

Number
Listen port 16080 Default Tomcat deployment: <Hyperion_Home>/deployments/tomcat5/conf/

server.xml
SSL listen port NA NA
Shutdown port for 16081 Default Tomcat deployment: <Hyperion_Home>/deployments/tomcat5/conf/

Apache Tomcat server.xml
Parameter: Server port
AJP connector port NA NA
Reporting and Analysis Ports

l “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 Ports
Table 23 Reporting and Analysis Default Service Ports

Number
Foundation 6790 — 6810 See below for detail on each port.
Global Services Manager 6800 l Hyperion Configuration Utility

(GSM) l <BIPLUS_HOME>/common/config/server.xml
Core Service 6801 <host>machine.domain</host>
<port>portNumber</port>
Name Service 6798 l 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 6797 Remote Service Configurator

l Job Service l 6796 See the Hyperion Workspace Administrator's Guide.
l Event Service l 6794
l Repository Service l 6795
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 port
value setting.)
80 Ports
Financial Reporting Ports
Table 25 Financial Reporting Web Application Ports
Port Type Default Where Configurable

Port
Number
SSL listen NA Application server administration console (configure manually)

port
Shutdown 8201 Application server administration console (configure manually).

port for
Note: The port number depends on the listen port (listen port + 1).
Apache
Tomcat
AJP 8202 <HYPERION_HOME>/common/httpserver/Apache/2.0.52/conf/HYSLWorkers.properties

connector
worker.Financial_Reporting.host=hostname.company.com
port
worker.Financial_Reporting.port=portNumber
worker.Financial_Reporting.type=ajp13
Table 26 Financial Reporting Default Service Ports

Number
Financial Reporting Report Service Dynamic (2) <BIPLUS_HOME>/lib/fr_repserver.properties
Parameters: HRRepSvrPort1, HRRepSvrPort2
Financial Reporting Scheduler Dynamic <BIPLUS_HOME>/lib/fr_scheduler.properties

Service
Parameter: HRSchdSvrPort
Financial Reporting Print Service Dynamic <BIPLUS_HOME>/lib/fr_printserver.properties
Parameter: HRPrintSvrPort
Financial Reporting Communication 8299 <BIPLUS_HOME>/lib/fr_global.properties

Service
Parameter: RMIPort
Additional Not configurable

dynamic port (1)
Remote ADM Server port for Dynamic HYPERION_HOME/common/ADM/VERSION/lib/ADM.properties file

Planning datasource access on the Report Server machine
Parameter: ADM_RMI_SERVER_PORT

Interactive Reporting Ports
Table 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 Ports

Table 28 Web Analysis Web Application Ports

Port
Number
Additional Dynamic Not configurable

listen ports
(2)

port
Shutdown 16001 Application server administration console (configure manually).

port for
Apache
Tomcat
AJP 16002 <HYPERION_HOME>/common/httpserver/Apache/2.0.52/conf/HYSLWorkers.

connector properties
port
worker.Web_Analysis.host=hostname.company.com
worker.Web_Analysis.port=portNumber
worker.Web_Analysis.type=ajp13
82 Ports
Workspace Ports
Table 29 Workspace Web Application Ports

Port
Number
Additional Dynamic Not configurable

listen port (1)

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

port for xml
Apache
<Server port="portNumber" shutdown="SHUTDOWN">
Tomcat
AJP 45002 <HYPERION_HOME>/common/httpserver/Apache/2.0.59/conf/HYSLWorkers.

connector properties
port
worker.Workspace.host=hostname.company.com
worker.Workspace.port=portNumber
worker.Workspace.type=ajp13
Application Builder J2EE Ports

Table 30 Application Builder J2EE Web Application Ports

Number
Listen port 22080 Application server administration console (configure manually)
SSL listen port 22090 Application server administration console (configure manually)
Shutdown port for 22005 <HAB_INSTALL_DIR>/AppServer/InstalledApps/Tomcat/5.0.28/

Apache Tomcat ApplicationBuilder/conf/server.xml
<Server port=”portNumber” shutdown=”SHUTDOWN”>

Application Builder.NET Ports
Table 31 Application Builder.NET Web Application Ports
Shutdown port for Apache Tomcat 22081 Application server administration console (configure manually)

Ports
l “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 Ports

Table 32 Financial Management Default Service Port

Number
Financial 135 plus Windows settings—Fix DCOM ephemeral ports.

Management ephemeral
See the Microsoft support article describing how to set the ports used by DCOM: http://
Application Server high-range
support.microsoft.com. Search for "restrict DCOM port."
ports (1024–
65536)
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 value
setting.
84 Ports
Performance Scorecard Ports
Table 34 Performance Scorecard Web Application Ports

l Application server administration console (configure manually)
Shutdown port for Apache Tomcat 18081 l 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 18091 l 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 Default Where Configurable

Port
Number
Planning 11333 <HYPERION_HOME>/common/RMI/1.0.0/HyperionRMI_Port.properties

RMI Server
Parameter: registryPort
Note: If you change the port, you must run uninstallHyperionNTServiceRMI.cmd and then run
installHyperionNTServiceRMI.cmd.
Strategic Finance Ports

Table 38 Strategic Finance Default Service Port
Service Default Where Configurable

Port
Number
Strategic 7750 Strategic Finance administration tool

Finance
The default port value is in the registry. The key is in HKEY_LOCAL_MACHINE\Software\Hyperion
Server
Solutions\HSFService\RPCPort. The value is a string item that contains the port number as text. Each
client program includes a registry item (accessible with the Connect dialog box) to set port numbers for each
contacted 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 Ports

Table 39 Performance Management Architect Web Application Ports

Number
Performance Management Architect UI
Listen port 19091 (can Hyperion Configuration Utility

be configured
for SSL)
86 Ports
Number
SSL listen 19094 <HYPERION_HOME>/deployments/Tomcat5/EPMAWebTier/conf/server.xml

port
<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
Shutdown 19092 l Hyperion Configuration Utility

port for <HYPERION_HOME>/deployments/Tomcat5/EPMAWebTier/conf/server.xml
Apache
l
Tomcat For parameters, see the application server documentation.
AJP 19093 l Hyperion Configuration Utility

connector <HYPERION_HOME>/Deployments/Tomcat5/EPMAWebTier/conf/server.xml
port
l
<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 (can Hyperion Configuration Utility

be configured
for SSL)
SSL listen 19104 <HYPERION_HOME>/deployments/Tomcat5/EPMADataSynchronizer/conf/server.xml

port
<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
Shutdown 19102 l Hyperion Configuration Utility

port for <HYPERION_HOME>/deployments/Tomcat5/EPMADataSynchronizer/conf/server.
Apache
l
xml
Tomcat
For parameters, see the application server documentation.
Financial Performance Management Applications Ports 87

Number
AJP 19103 l Hyperion Configuration Utility

connector <HYPERION_HOME>/deployments/Tomcat5/EPMADataSynchronizer/conf/server.
port
l
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 Default Where Configurable

Port
Number
Server Manager 49500 BPMA_Server_Config.xml

<ServerManagerPort>portNumber</ServerManagerPort>
Process 49501 BPMA_Server_Config.xml

Manager
<Port>portNumber</Port>
web.config file under the webservices directory
<appSettings> parameter
<add key="ProcessManagerPort" value="portNumber"/>
Event 49502 BPMA_Server_Config.xml

Subscription
<EventSubscriptionPort>portNumber</EventSubscriptionPort>
Event Manager 49503 BPMA_Server_Config.xml

<EventManagerPort>portNumber</EventManagerPort>
Job Manager 49504 BPMA_Server_Config.xml

<JobManagerPort>portNumber</JobManagerPort>
Engine 51000– BPMA_Server_Config.xml

instances 51999
<MinEnginePort>portNumber</MinEnginePort>
<MaxEnginePort>portNumber</MaxEnginePort>
Data Access Dynamic BPMA_Server_Config.xml

Layer (DB2
Note: Performance Management Architect does not control which port DB2 uses. However, the port
only)
that is used by DB2 can be specified in BPMA_Server_Config.xml so that Performance Management
Architect 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 Ports
l “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 Ports

Table 42 Data Integration Management Web Services Hub Ports

Port
Number
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 listen NA jboss-3.2.1/server/default/deploy/jbossweb-tomcat.sar/META-INF/jboss-

port service.xml
Parameter: SSL/TLS Connector configuration
Shutdown NA NA
port for
Apache
Tomcat
AJP 8009 jboss-3.2.1/server/default/deploy/jbossweb-tomcat.sar/META-INF/jboss-

connector service.xml
port
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
Data 4001 l Hyperion Configuration Utility (if PowerCenter Server component is installed)
Integration INFA Workflow Manager (installed with the PowerCenter Client component)
Management
l
Server l Native INFA PowerCenter Server Configuration Utility:

m Windows: <DIM_HOME>\Server\binpmsetup.exe (saves server configuration to
Windows registry)
m UNIX: <DIM_HOME>/Server/binpmconfig (saves server configuration to the
<DIM_HOME>/Server/bin/pmserver.cfg file)
Data 5001 l Hyperion Configuration Utility

Integration
Separate port INFA PowerCenter Repository Server Configuration Utility:
Management
l
(between Windows: <DIM_HOME>\RepositoryServer\bin\PmRsSetup.exe (saves
Repository
5002-65535) for
m
Server server configuration to Windows registry)
each repository in the
Repository Server m UNIX: <DIM_HOME>/RepositoryServer/binpmrsconfig (saves server
configuration to the <DIM_HOME>/RepositoryServer/bin/pmrepserver.
cfg file)
Translation Manager Ports

Table 44 Translation Manager Web Application Ports

Number
SSL listen port 14090 <TranslationManager_Home>/AppServer/InstalledApps/Tomcat/5.0.

28/HTMServer/conf/server.xml
Shutdown port for 14005 Application server administration console (configure manually)
Apache Tomcat
AJP connector port NA Application server administration console (configure manually)
Table 45 Translation Manager Default Service Port

Number
Translation Manager 11333 l Hyperion Configuration Utility

RMI Server l <HYPERION_HOME>/common/RMI/1.0.0/HyperionRMI_Port.properties
Parameter: registryPort
90 Ports
FDM Ports
Table 46 FDM Default Service Ports

Number
FDM load 135 plus Windows settings—Fix DCOM ephemeral ports.

balancer FDM ephemeral
For more information, see the Microsoft support article describing how to set the ports used by DCOM:
application high-range
http://support.microsoft.com. Search for "restrict DCOM port."
server ports (1024–
65536)
File sharing 137–139, Controlled by the operating system. Enable file sharing between all WebLink application servers and
445 the 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 plus Windows settings—Fix DCOM ephemeral ports.

ephemeral
For more information, see the Microsoft support article describing how to set the ports used by DCOM:
high-range
http://support.microsoft.com. Search for "restrict DCOM port."
ports (1024–
65536)
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

Number
Data 135 plus l config.xml using the Data Relationship Management Console
Relationship ephemeral
Windows settings—Fix DCOM ephemeral ports.
Management high-range
l
ports (1024– For more information, see the Microsoft support article describing how to set the ports used by
65536) DCOM: 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
Changing Repository Passwords
8
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 Maintenance

For Hyperion products that require a database repository, you can change repository passwords
during and after product deployments.
After changing database repository passwords, restart Hyperion products in the order specified
in Appendix A, “Startup Dependencies and Default URLs.”
Caution! Change the password in the database used by Workspace only after you perform the
procedure in “Changing the Workspace Repository Password” on page 94. If other
Hyperion products use the same database that Workspace uses, change the
Workspace repository password before changing the password of any other product
repository.
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 and
Default URLs.”
Changing the Administration Services Repository

Password
ä 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 Dependencies
and Default URLs.”
Changing Reporting and Analysis Repository

Passwords
l “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 repository
password 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 Hyperion
Workspace 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 the
same database account. Ensure that you enter the same password for each one. If these services use
different database accounts, perform this step only for the services that use the account whose password
you 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 certain
to 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 security
from 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 Reporting
and Analysis services.
13 Restart Interactive Reporting according to the order specified in Appendix A, “Startup Dependencies
Changing the Financial Reporting Repository Password

Financial Reporting uses Workspace for connection information, so password changes for
Workspace 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 up
WebAnalysis.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, run
EncryptPasswordUtil.bat (Windows) or EncryptPasswordUtil.sh (UNIX).
6 Restart Web Analysis according to the order specified in Appendix A, “Startup Dependencies and Default
URLs.”
Changing Financial Performance Management

Applications Repository Passwords
l “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 Password

Perform 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 Default
URLs.”
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 Default
URLs.”
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 Dependencies
ä 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 Financial
Management according to the order specified in Appendix A, “Startup Dependencies
Changing the Performance Management Architect

Repository 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 Architect
Dimension Server.
4 Select the Performance Management Architect option.
9 Restart Performance Management Architect according to the order specified in Appendix A, “Startup
Dependencies and Default URLs.”

For the Performance Management Architect Applications (Optional)
Note: Perform the following procedures if you are using the Interface Data Source
configuration.
ä 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 Dependencies
Changing Data Management Repository Passwords

l “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 Repository

Password
ä 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, “Startup
Dependencies 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 Dependencies
Changing Data Management Repository Passwords 101

Configuration Worksheets
9
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 Configuration
Hyperion Configuration Utility is installed with the first Hyperion product installation on each
machine. You launch the utility after installation to configure installed products.
You can use the worksheets in this chapter (based on Hyperion Configuration Utility) to record
the information required for your configuration process.
Standard configuration tasks:
l Product options—If supported by your product, select the features authorized by your
license 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 and
retrieve data. See “Relational Database Configuration” on page 105.
l Application server deployment—Required for products that deploy on an application
server. 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 task
separately. If errors still occur, refer to the Hyperion Installation and Configuration
Troubleshooting Guide.
Note: To collect the information you need to configure external user directories to support
single sign-on and authorization in User Management Console, see the Hyperion Security
Administration Guide.
Recommendations
l 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 characters
are not supported.
Product Options
On the Product Options page, if appropriate, select the product features authorized by your
license agreement. See Chapter 5, “Hyperion License Compliance.”
During product configuration, Hyperion Configuration Utility copies
registry.properties to <Hyperion_Home>\common\config on the server on which you
ran 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 Configuration
Utility—to review and edit the product options. You must complete this step to ensure you
comply with your license agreement and to activate features you are licensed to use. See
“Activating and Deactivating Product Features” on page 53.
Shared Services Registration

Applies to all products that implement Shared Services functionality or plan to use Shared
Services 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 using
admin 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 that
use taskflow management
SSL Enables use of Secure Sockets Layer to encrypt data. See the Hyperion
Product SSL Configuration Guide.
Relational Database Configuration

Required for all products except Essbase - System 9, Smart View, Provider Services, and Strategic
Finance.
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 the
database used to allocate storage for table data).
Oracle: Index tablespace The name the existing tablespace that is used to create database indexes (the logical
portion of the database used to allocate storage for index data).
Application Server Deployment

Required for products that deploy as Web applications to an application server. Exceptions are
Essbase, 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 deployed
Hyperion product uses this profile).
1A default user name and password of "hyperion" is automatically used during deployment.
Essbase
Required 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)

l “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® Production l Oracle: <BIPLUS_HOME>\Server\Oracle\bin

Reporting – System 9 binary folder, MS: SQL:<BIPLUS_HOME>\Server\ODBC\bin
according to the selected repository type
l
l IBM: DB2:<BIPLUS_HOME>\Server\DB2\bin
MS SQL client home MS SQL client home
Repository connection string l Oracle: TNS name

l MS SQL: ODBC name
l IBM DB2: Database alias registered by Client Configuration Assistant
Performance Scorecard
Required 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 Shared
Services
Performance Scorecard Project Project name for Performance Scorecard that you use in Shared
Services
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 Finance
Required 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 Management
After running Hyperion Configuration Utility, run Financial Management Configuration
Utility. See the Hyperion Financial Management – System 9 Installation Guide.
Performance Management Architect

To enable configuration of Performance Management Architect, Microsoft Internet
Information Services (IIS) and .NET Framework 2.0 must be installed on the computer that
hosts the Dimension Server.
Planning
Required 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 any
description 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 are
using (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

Installation Sequence
10
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 Sequence

Hyperion recommends that you install and configure products in the documented order.
However, you can install multiple products simultaneously and then configure the products in
the documented order. If you install multiple products on one computer, use Hyperion
Configuration Utility to configure the products simultaneously.
Before installing products, see the list of required Hyperion software in Chapter 3, “System
Requirements” 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 sequence
for 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 Options
panel might be displayed if you need to select product features that you are licensed to
use per your license agreement.
About Installation Sequence 111

General Tasks
TASK EXCEPTION
Install and configure Data Integration Management and FDM

Shared Services, and
Note: Data Relationship Management uses Shared Services only for external authentication. Data Integration
configure user
Management can use Shared Services or Informatica native authentication.
directories for
external
authentication.
Assign roles and FDM, Data Relationship Management, and Data Integration Management (for Shared Services authentication; not
provision users in for Informatica native authentication).
Shared Services.
Shared Services Tasks
TASK REFERENCE
Install Shared Services
1. Navigate to the directory where you downloaded the product installation files. “Installing Shared Services” in the
Hyperion Shared Services
2. Run the EXE or BIN file.
Installation Guide
3. Select a Typical or Custom installation.
Configure Shared Services
1. Start Hyperion Configuration Utility. “Configuring Shared Services” in

the Hyperion Shared Services
2. Perform these tasks:
Installation Guide
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 together
the first time Shared Services is configured.
Optional: Enable Shared Services for SSL
Enable Shared Services and the user directory for SSL. Hyperion Product SSL
Configuration Guide
Configure User Directory for External Authentication
1. Start the Shared Services server, and launch User Management Console. “Installing Shared Services” in the
Hyperion Shared Services
2. Configure a supported user directory, such as LDAP or MSAD.
Installation Guide
3. If you are using Netegrity SiteMinder, install Oracle's Hyperion® Remote Authentication Module™
and configure Shared Services to use Single Socket Layers. Hyperion Security Administration
Guide
4. Identify your administrators from the user directory, and provision them with the Shared Services
Administrator role.
112 Installation Sequence

Essbase - System 9 Tasks
Essbase - 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
1. Navigate to the directory where you downloaded the product installation files. The installation chapters in
the relevant product
2. Run the appropriate setup file.
installation guides
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
Configure Essbase - System 9 Products
1. Start Shared Services Server. The configuration chapters in

the relevant product
2. Start Hyperion Configuration Utility.
installation guides
3. As required:
a. Register products with Shared Services (required for Essbase, Administration Services3 , and
Provider 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 for
Administration 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 edit
the product options. You must complete this step to ensure you comply with your license agreement
and to activate features you are licensed to use. See “Activating and Deactivating Product Features”
on page 53.
Optional: Enable Administration Services, Essbase, or Provider Services for SSL
Enable Administration Services for SSL. Hyperion Product SSL

Configuration Guide
Essbase - System 9 Tasks 113

TASK REFERENCE
Enable Integration Services
l For Essbase and Administration Services, enable Integration Services. “Configuring Essbase for
Relational Integration” in the
If using SQL Interface or Hybrid Analysis, verify that you have a license for them.
Hyperion Essbase - System 9
l
Installation 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 View
installation program is also available from the Oracle® E-Delivery site. Smart View can be used to connect to Essbase as a data source only if
Provider 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 Administration
Services.
4If you plan to use Log Analyzer, a database repository is required for Administration Services.
Planning Tasks
The Planning sequence assumes that you installed and configured Shared Services, Essbase, and
Administration Services and created a database for Planning and optionally, a database for
Performance Management Architect. The Planning setup program can install Performance
Management Architect.
Note: Microsoft Internet Information Services (IIS) and .NET Framework 2.0 must be installed
on 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
1. Navigate to the directory where you downloaded the product installation files. “Installing Database Tier
Components” and
“Installing the Planning
3. If installing on Windows 32-bit, select Typical to install the Planning Web Server, Planning ADM Driver, Middle Tier” in the
and Performance Management Architect components. Hyperion Planning -
System 9 Installation
Note: If you are using Classic Application Administration instead of Performance Management Architect,
Guide
select Custom and select only the Planning Web Server component. Individual components can be
installed on different machines.
4. If installing on Windows 64-bit or UNIX, Performance Management Architect must be installed on a
Windows 32-bit machine.
Configure Planning

TASK REFERENCE
1. Start Shared Services Server and Essbase Server. “Configuring Planning” in

the Hyperion Planning -
System 9 Installation
3. Register with Shared Services. Guide for Windows
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.)
Perform Post-Configuration Tasks
1. After you configure each product, you must open registry.properties—in <Hyperion_Home> “Post Configuration Tasks”
\common\config on the server on which you ran Hyperion Configuration Utility—to review and edit the in the Hyperion Planning -
product options. You must complete this step to ensure you comply with your license agreement and to System 9 Installation
activate features you are licensed to use. See “Activating and Deactivating Product Features” on page Guide
53.
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 Architect
installation.
5. Create an application using either Performance Management Architect or Classic Application
Administration.
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
Optional: Enable Performance Management Architect and Planning for SSL
Enable Performance Management Architect and Planning for SSL. Hyperion Product SSL
Configuration Guide
Planning Tasks 115

Financial Management Tasks
TASK REFERENCE
Install Financial Management
1. Navigate to the directory where you downloaded the product installation files. “Installing Financial
Management Server
2. Run the EXE file.
Components” and
3. Select the components to install: “Installing the Client Tier
To install on the server, select Custom and select all components you want to install, including Components” in the
Hyperion Financial
l
Performance Management Architect.
Management – System 9
Note: If you are using Performance Management Architect, Microsoft Internet Information Services Installation Guide
(IIS) must be installed on the machine that hosts the Performance Management Architect Dimension
server. .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.
Configure Financial Management
1. Start Shared Services Server. “Configuring and Setting Up

Financial Management” in
the Hyperion Financial
3. For Financial Management: Management – System 9
a. Register with Shared Services. Installation Guide
b. Perform Financial Management configuration tasks that set up users and register Financial
Management servers.
c. Perform tasks that are specific to Financial Management and Performance Management Architect
to 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 more
information.)

TASK REFERENCE
1. After you configure each product, you must open registry.properties—in <Hyperion_Home> “Post Configuration Tasks”
\common\config on the server on which you ran Hyperion Configuration Utility—to review and edit in the Hyperion Financial
the product options. You must complete this step to ensure you comply with your license agreement and Management – System 9
to activate features you are licensed to use. See “Activating and Deactivating Product Features” on page Installation Guide
53.
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 Architect
installation.
5. Create an application view in Performance Management Architect or create an application using Classic
Application Administration.
6. Verify Financial Management installation.
Optional: Enable Performance Management Architect and Financial Management for SSL
Enable Performance Management Architect and Financial Management for SSL. Hyperion Product SSL
Configuration Guide
Reporting and Analysis Tasks

TASK REFERENCE
Install Reporting and Analysis
On each applicable computer: “Installing Reporting and Analysis” in the

Hyperion Reporting and Analysis – System 9
1. If you are using Financial Management as a data source, first install the Financial Installation Guide for Windows and the
Management ADM driver on the computer. Run the Financial Management installer and Hyperion Reporting and Analysis – System 9
select only the ADM Driver option. Installation Guide for UNIX
2. Navigate to the directory where you downloaded the product installation files.
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.
Configure Reporting and Analysis
Reporting and Analysis Tasks 117

TASK REFERENCE
1. Start Shared Services Server. “Configuring Reporting and Analysis” in the

Hyperion Reporting and Analysis – System 9
Installation Guide for Windows and the
3. For Reporting and Analysis: Hyperion Reporting and Analysis – System 9
a. Register with Shared Services. Installation Guide for UNIX
b. Configure the database. “Manually Deploying to an Application

Server” in the Hyperion Reporting and
c. Automatically (recommended) or manually deploy to the application server. Analysis – System 9 Installation Guide for
d. Complete module-specific configurations. Windows and the Hyperion Reporting and
Analysis – System 9 Installation Guide for
UNIX
1. After you configure each product, you must open registry.properties—in “Post Configuration Tasks” in the Hyperion
<Hyperion_Home>\common\config on the server on which you ran Hyperion Reporting and Analysis – System 9
Configuration Utility—to review and edit the product options. You must complete this Installation Guide for Windows and the
step to ensure you comply with your license agreement and to activate features you Hyperion Reporting and Analysis – System 9
are licensed to use. See “Activating and Deactivating Product Features” on page 53. Installation Guide for UNIX
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.
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
1. Navigate to the directory where you downloaded the product installation files. “Installing Performance Scorecard
and Components” in the Hyperion
Performance Scorecard - System 9
3. Select the components to install. Installation Guide
Note: If you want to install Performance Scorecard Alerter or File Import/Export, you must select
Custom.
Configure Performance Scorecard

TASK REFERENCE
1. Start Shared Services Server. “Configuring Performance

Scorecard” and “Manual
Application Server Deployment
3. For Performance Scorecard: Tasks” in the Hyperion
a. Configure the database. Performance Scorecard - System 9
Installation Guide
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—to
review and edit the product options. You must complete this step to ensure you comply with your
license agreement and to activate features you are licensed to use. See “Activating and
Deactivating Product Features” on page 53.
Optional: Enable Performance Scorecard for SSL
Enable Performance Scorecard for SSL. Hyperion Product SSL

Configuration Guide
Strategic Finance Tasks

TASK REFERENCE
Install Strategic Finance
1. Navigate to the directory where you downloaded the product installation files. “Server Installation” or “Client
Installation” in the Hyperion Strategic
Finance Installation Guide
3. Select the Strategic Finance server or client component.
Configure Strategic Finance
1. Start Shared Services Server. “Configuring and Setting Up Strategic

Finance” in the Hyperion Strategic
Note: Shared Services may not be used in all Strategic Finance implementations. Finance Installation Guide
3. For Strategic Finance:
a. Register with Shared Services.
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 review
and edit the product options. You must complete this step to ensure you comply with your
license agreement and to activate features you are licensed to use. See “Activating and
Deactivating Product Features” on page 53.
Connect the Strategic Finance Client to the Server “Connecting a Client to a Strategic
Finance Server and Database” in the
Hyperion Strategic Finance
Installation Guide
Strategic Finance Tasks 119

Data Relationship Management Tasks
You do not need to provision users, because this product uses Shared Services only for external
authentication.
TASK REFERENCE
Install Data Relationship Management on the Server
1. Navigate to the directory where you downloaded the product installation files. “Installing Server Components”
or “ Installing Client
2. Run the EXE file for the server component or the client component.
Components” in the Hyperion
Data Relationship Management
NTier Installation Guide
Configure Data Relationship Management
Data Relationship Management does not use Hyperion Configuration Utility. “Configuring Data Relationship
Management” in the Hyperion
1. On the primary Data Relationship Management server, install Shared Services. Data Relationship Management
2. Launch the Data Relationship Management Console. NTier Installation Guide
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. If
you 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.
FDM Tasks
You 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 product “Installation” in the Hyperion Financial Data Quality
installation files. Management Installation Guide
Configure FDM

TASK REFERENCE
FDM does not use Hyperion Configuration Utility. Chapters 4 – 8 of the Hyperion Financial Data Quality
Management Installation Guide
1. Configure these components:
“Creating a New FDM Application” in the Hyperion Financial
Web server
Data Quality Management Installation Guide
l
Application server
“Configuring Adapters” in the Hyperion Financial Data Quality
l
l Load balancer Management Installation Guide

l Workbench
2. Create an FDM application.
3. Install and configure adaptors to integrate FDM with the target
application.
Data Integration Management Tasks

This product can use Shared Services for external authentication or Data Integration
Management configured for native Informatica authentication. This product does not require
use of Shared Services to provision users.
TASK REFERENCE
Install Data Integration Management
1. Navigate to the directory where you downloaded the product installation files. “Installing and Uninstalling Data Integration
Management” in the Hyperion Data Integration
3. Select the components to install.
Configure Data Integration Management
1. If you are using Shared Services for external authentication, start Shared Services “Configuring and Setting Up Data Integration
Server. Management” in the Hyperion Data Integration
3. Optional: Register with Shared Services.
4. Configure Data Integration Management.
5. Synchronize users.
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 do
not have to perform these tasks to provision users.
Data Integration Management Tasks 121

TASK REFERENCE
Perform one or more actions: Hyperion Security

Administration
l Assign the Project Manager role to users who are responsible for creating projects and assigning applications Guide
to projects.
l For each application, assign the Provisioning Manager role to users who are responsible for assigning roles and
access 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.

Startup Dependencies and
A Default URLs
In This Appendix
Summary List of Services and Processes .............................................................. 123
Services and Processes ................................................................................. 124
Default URLs.............................................................................................. 137
Summary List of Services and Processes

The following Hyperion product services and processes are listed below, in their recommended
startup order.
1. Databases for repositories. (For a list of Hyperion products that require a repository
database, 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 Processes

The services and processes discussed in this topic are listed in the order in which Hyperion
recommends 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 Start Start > Programs > Hyperion > Foundation Services > Start Shared Services
Menu
Command:
Registered HyS9Shared Services

Service Name:
124 Startup Dependencies and Default URLs

Display Name in Hyperion S9 Shared Services
Windows
Control Panel:
Description: Hyperion Shared Services that support Hyperion applications, including authentication, user provisioning, task flow
management, and data and metadata synchronization
Windows l Tomcat, WebSphere, and WebLogic 9: <Hyperion_Home>\deployments\<AppServNameAndVersion>

Startup Script: \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 Startup l Tomcat, WebSphere, and WebLogic 9: <Hyperion_Home>/deployments/<AppServNameAndVersion>/

Script: 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 Services

Table 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 Services

Table 53 Performance Management Architect Services
Windows Start Start > Programs > Hyperion > Foundation Services > Performance Management Architect > Start Dimension Server
Menu
Command:
Services and Processes 125

Registered Process Manager: HyS9BPMA_ProcessManager
Service Name:
Process Manager automatically starts the following services:
l Engine Manager: HyS9EPMA_EngineManager
l Job Manager: HyS9EPMA_JobManager
l Event Manager: HyS9EPMA_EventManager
Display Name Process Manager: Hyperion S9 EPM Architect Process Manager

in Windows
Process Manager automatically starts the following services:
Control Panel:
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 Architect
Process Manager. There could be multiple instances of EPM Architect Engine Manager in the same instance of EPM
Architect (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.
Windows NA
Startup Script:
UNIX Startup NA
Script:
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 Menu Start > Programs > Hyperion > Essbase > Essbase
Command:
Registered Service HyS9ESBAgent9.3.1 — hypservice

Name:
Display Name in Hyperion S9 BI+ Analytic Services 9.3.1 — <ServerName>

Windows Control Panel:
Description: Stores data with multiple dimensions and manages analytical data models, data storage, calculations, and
data security

Windows Startup Script: ARBORPATH\bin\essbase.exe
UNIX Startup Script: $ARBORPATH/bin/startEssbase.sh
6. Administration Services Application Server

Table 56 Administration Services Application Server Service/Process
Windows Start Start > Programs > Hyperion > Administration Services > Start Administration Services Server
Menu Command:
Registered HyS9aas
Service Name:
Display Name in Hyperion S9 Administration Services <AppServer>

Windows Control
Panel:
Description: Controls the running of the Oracle's Essbase® Administration Services application server
Windows Startup l WebSphere, WebLogic 9, and deployed Tomcat deployment (via Hyperion Configuration Utility): <Hyperion_
Script: 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 Startup l WebSphere, WebLogic 9, and deployed Tomcat deployment (via Oracle's Hyperion® Configuration Utility™):
Script: <Hyperion_Home>/deployments/<AppServNameAndVersion>/bin/startaas.sh
l WebLogic 8.1.x: <AASPATH>/server/bin/startaas.sh
7. Integration Services
Table 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 Server
Table 58 Provider Services Application Server Services/Processes
Windows Start Start > Programs > Hyperion > Provider Services > Start Provider Services
Menu Command:
Registered HyS9aps
Service Name:
Display Name in Hyperion S9 Provider Services <AppServer>

Windows Control
Panel:
Description: Controls the running of an application server for Oracle's Hyperion® Provider Services
Windows Startup l WebSphere, Weblogic 9, and Tomcat: <Hyperion_Home>\deployments\<AppServNameAndVersion>

Script: \bin\startaps.bat
l WebLogic 8.1.x: <APS_HOME>\bin\startaps.bat
UNIX Startup l WebSphere, Weblogic 9, and Tomcat: <Hyperion_Home>/deployments/

Script: <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 Control Hyperion S9 BI+ 9.3 Interactive Reporting Service 1
Panel:
Description: Process monitor that manages the Interactive Reporting Service, Data Access Service, Interactive
Reporting 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
Windows Start Start > Programs > Hyperion > Reporting and Analysis > Utilities and Administration > Start Reporting and Analysis
Menu Core Services
Command:

Registered HyS9Workspace
Service Name:
Display Name in Hyperion S9 BI+ 9.3 Workspace

Windows Control
Panel:
Description: HyS9Workspace - Hyperion S9 BI+ Workspace web application for <APP_SERVER> <APP_VERSION>
Windows l WebSphere and Tomcat: <HYPERION_HOME>\deployments\<AppServNameAndVersion>\bin

Startup Script: \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 Startup l WebSphere, WebLogic 9, and Tomcat: <HYPERION_HOME>/deployments/<AppServNameAndVersion>/

Script: 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
Windows Start Start > Programs > Hyperion > Reporting and Analysis > Start Financial Reporting
Menu
Command:
Registered l Financial Reporting Java RMI Registry: HyS9FRRMI

Service Name: l Financial Reporting Print Server: HyS9FRPrint
l Financial Reporting Report Server: HyS9FRReport
l Financial Reporting Scheduler Server: HyS9FRSched
Display Name in l Hyperion S9 BI+ Financial Reporting Java RMI Registry

Windows Hyperion S9 BI+ Financial Reporting Print Server
Control Panel:
l
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 for
Financial 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
Windows <BIPLUS_HOME>\bin\start_BIPlus.bat
Startup Script:

UNIX Startup <BIPLUS_HOME>/bin/freporting {start|stop|restart}
Script:
d. Reporting and Analysis Web Server
Table 62 Reporting and Analysis Web Server Services/Processes
Windows Start Start > Programs > Hyperion > Reporting and Analysis > Start Web Analysis
Menu
Command:
Registered l Apache: HyS9Apache2

Service Name: l IIS: IISADMIN
l IHS 6.0: IBM HTTP Server 6.0
Display Name in l Apache: Hyperion S9 Apache 2.0

Windows IIS: IIS Admin Service
Control Panel:
l

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
Windows <HYPERION_HOME>\common\httpServers\Apache\2.0.52\bin\StartHyperionApacheService.
Startup Script cmd
(Apache only):
UNIX Startup <HYPERION_HOME>/common/httpServers/Apache/2.0.52/bin/apachectl {start|stop|

Script (Apache restart}
only):
e. Web Analysis Application Server
Table 63 Web Analysis Application Server Services/Processes
Windows Start Start > Programs > Hyperion > Reporting and Analysis > Start Reporting and Analysis
Menu
Command:
Registered HyS9WebAnalysis
Service Name:
Display Name in Hyperion S9 BI+ 9.3 Web Analysis

Windows Control
Panel:
Description: HyS9WebAnalysis - Hyperion S9 BI+ Web Analysis web application for <APP_SERVER> <APP_VERSION>.

Windows l WebSphere and Tomcat: <HYPERION_HOME>\deployments\<AppServNameAndVersion>\bin
Startup Script: \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

Script: bin/startWebAnalysis.sh
l WebLogic 8: <BIPLUS_HOME>/AppServer/InstalledApps/WebLogic/8.1/WebAnalysisDomain/
bin/startWebAnalysis.sh
10. Application Server Services/Processes

The 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
Windows Start Menu Start > Programs > Hyperion > Foundation Services > Performance Management Architect > Start Performance
Command: Management Architect Web
Registered Service HyS9EPMAWebTier

Name:
Display Name in 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
Windows Start Menu Start > Programs > Hyperion > Foundation Services > Performance Management Architect > Start Data
Command: Synchronizer
Registered Service HyS9EPMADataSynchronizer

Name:

Display Name in Hyperion S9 EPM Architect Data Synchronization
Description: EPM Architect Data Synchronizations Engine
Windows Startup l WebSphere, WebLogic 9, and Tomcat: <HYPERION_HOME>\deployments

Script: \<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
Windows Start Start > Programs > Hyperion > Reporting and Analysis > Start Reporting and Analysis
Menu Command:
Registered HyS9FRWeb
Service Name:
Display Name in Hyperion S9 BI+ 9.3 Financial Reporting Web application

Windows Control
Panel:
Description: HyS9FRWeb - Provides a Workspace module for Financial Reporting
Windows Startup l WebSphere and Tomcat: <HYPERION_HOME>\deployments\<AppServNameAndVersion>\bin

Script: \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

Script: bin/startFinancialReporting.sh
l WebLogic 8: <BIPLUS_HOME>/AppServer/InstalledApps/WebLogic/8.1/
FinancialReportingDomain/bin/startFinancialReporting.sh
11. Remaining Product Services

The following product services can be started in any order.

Planning Application Server
Table 67 Planning Application Server Services/Processes
Windows Start Start > Programs > Hyperion > Planning > Start Planning
Menu Command:
Registered HyS9Planning
Service Name:
Display Name in Hyperion S9 Planning

Windows Control
Panel:
Description: Provides access support for Planning Web server
Windows Startup l WebSphere, WebLogic 9, and Tomcat: <HYPERION_HOME>\deployments\<AppServNameAndVersion>

Script: \bin\startHyperionPlanning.bat
l WebLogic 8.1: <Planning_HOME>:\AppServer\InstalledApps\<AppServName>\<version>
\HyperionPlanningDomain\startHyperionPlanning.bat
UNIX Startup l WebSphere, WebLogic 9, and Tomcat: <HYPERION_HOME>/deployments/

Script: <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
Windows Start Start > Programs > Hyperion > Financial Management
Menu Command:
Registered l HFM Service: Hyperion S9 Financial Management Service

Service Name: l HFM DME Listener: Hyperion S9 Financial Management DME Listener
Display Name in l HFM Service: Hyperion S9 Financial Management Service

Windows Control HFM DME Listener: Hyperion S9 Financial Management DME Listener
Panel:
l
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 Data
Movement Engine. If this service is stopped, the DME Web service will not be able to communicate with all HFM
instances on this server.
Windows Startup <Hyperion_Home>\FinancialManagement\Client\HFM.exe

Script:
UNIX Startup NA
Script:

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
Windows Start Start > Hyperion > Performance Scorecard > startWebReports on <appserver>
Menu Command:
Registered HyS9HPS
Service Name:
Display Name in Hyperion S9 Performance Scorecard 9.3.1.0.0 <AppServer>

Windows Control
Panel:
Description: Starts and stops an instance of Performance Scorecard running under an application server.

Script: \bin\startwebreportsDomain.bat
l WebLogic 8.1: <HPS_INSTALL_DIRECTORY>\AppServer\InstalledApps\<AppServName>
\<version>\webreportsDomain\bin\startwebreports.bat

Script: 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
Windows Start Start > Hyperion > Performance Scorecard > startHPSAlerter on <appserver>
Menu Command:
Registered HyS9Alerter
Service Name:

Display Name in Hyperion S9 Performance Scorecard Alerter 9.3.1.0.0 <AppServer>
Windows Control
Panel:
Description: Starts and stops an instance of Performance Scorecard Alerter running under an application server.

Script: \bin\startalerterDomain.bat
l WebLogic 8.1: <HPS_INSTALL_DIRECTORY>\AppServer\InstalledApps\<AppServName>
\<version>\alerterDomain\bin\startalerter.bat
UNIX Startup l WebSphere, WebLogic 9, and Tomcat: <HYPERION_HOME>/deployments/

Script: <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
Windows Start Menu Start > Programs > Hyperion > Data Relationship Management > Data Relationship Management Console
Command:
Registered Service Name: l Services: HyS9MDMSvc

l Web Publishing: HyS9MDMWebPubSvc
Display Name in Windows l Services: Hyperion Data Relationship Management

Control Panel: 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
Windows Start l Start > Programs > Hyperion > Data Integration Management > Informatica PowerCenter 7.1.5-RepServer >
Menu ModuleName
Command:
l Start > Programs > Data Integration Management > Informatica PowerCenter 7.1.5-RepServer, Informatica
PowerCenter 7.1.5-Client > ModuleName
l Start > Programs > Hyperion > Data Integration Management > Informatica PowerCenter 7.1.5-Server > ModuleName
Registered l Repository Server: PmRepServer

Service Name: l Powermart: Hyperion Data Integration Management Server
Display Name l Repository Server: Hyperion Data Integration Management Repository Server
in Windows Powermart: Hyperion Data Integration Management Server
Control Panel:
l
Description: l Repository Server: Hyperion Data Integration Management Repository Server

l Powermart: Hyperion Data Integration Management Server
Windows l Informatica PowerCenter 7.1.5 - RepServer > Informatica Repository Server Setup: <DIM_Install_Directory>
Startup \RepositoryServer\bin\PmRsSetup.exe
Script:
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 Startup l Repository Server: <DIM_HOME>/Resources/bin/start_pmrepserver.sh

Script: l PowerCenter Server: <DIM_HOME>/Resources/bin/start_pmserver.sh
Translation Manager
Table 75 Translation Manager Services/Processes
Windows Start Start > Programs > Hyperion > Translation Manager > Start Server <Server Type>
Menu Command:
Registered Service l Tomcat: HTMServer

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

Display Name in l Tomcat: Hyperion S9 HTMServer ATS5
Windows Control WebSphere 5: Hyperion S9 HTMServer WAS5
Panel:
l
l WebSphere 6: Hyperion S9 HTMServer WAS6

l WebLogic 8: Hyperion S9 HyperionTM WLS8
l WebLogic 9: Hyperion S9 HyperionTM WLS9
Description: NA
Windows Startup NA
Script:
UNIX Startup <HTM_HOME>/AppServer/InstalledApps/<AppServer>/<version>/<domain>/bin/

Script: start<domain>.sh
Default URLs
Table 76 Default URLs
Product Default URL
Oracle's Hyperion® Shared Services User http://<hostname>:58080/interop

Management Console
Workspace http://<WebServer>:<port>/workspace/
Note: From Workspace, you can access where <WebServer> is the Web server machine hostname and <port> is the Web
Financial Management, Planning, Oracle's server listen port; for example, 19000 if using the Apache instance bundled with Reporting
Enterprise Performance Management and Analysis.
Architect, and Reporting and Analysis.
Oracle's Hyperion® Performance Scorecard – http://<hostname>:18080/HPSWebReports

System 9
Oracle's Hyperion® Data Relationship http://<hostname>/mdm_ntier

Management
Oracle's Hyperion® Financial Data Quality http://<hostname>/HyperionFDM

Management
Default URLs 137

Deploying Hyperion 9.3.1
B Products with Components
from 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 products
at one time, or you can upgrade only some of the products (a mixed-release environment). This
appendix describes how to manage upgrades of all products or only some products and maintain
interoperability between products.
See the product installation guides for upgrade procedures for each product.
Upgrading to a Single-Release Hyperion Product

Environment
If you are upgrading all Hyperion products at one time to the same release, you can upgrade
using the existing machines, upgrading directly over the existing deployment. This type of
upgrade 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 machine
and 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 Product

Environment
In a mixed-release upgrade, you upgrade only some Hyperion products. This scenario requires
some manual configuration, and navigation procedures in Workspace differ. See “Configuring
Products in a Mixed-Release Environment ” on page 142 and “Navigating in Workspace in a
Mixed-Release Environment” on page 143.
In addition, this scenario requires additional hardware because only one version of a module
can run on any machine at one time.
For example, if you are upgrading an installation of Hyperion release 9.3.0 products deployed
on a single machine and want to upgrade all products except Financial Management and
Planning 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 new
machine hosts Hyperion release 9.3.1 products, and the original machine retains the release 9.3.0
products. In this configuration, end users access all Hyperion content within a single, centralized
Workspace.
In another example, if you are upgrading an installation of Hyperion release 9.3.0 products
deployed on a single machine and want to upgrade only Financial Management and Planning
to 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 new
machine hosts the Hyperion release 9.3.1 products that are required to use the upgraded
Financial Management and Oracle's Hyperion® Planning – System 9, and the original machine
hosts the other products. In this configuration, end users access all Hyperion content within a
single, centralized Workspace.
Configuring Products in a Mixed-Release Environment

After upgrading in a mixed-release environment, you must perform the following configuration
tasks.
ä 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, choose
Import > File.
For Example 1 in the previous section, import this HTML file into Machine 2 to manage
launching applications on Machine 1. For Example 2 in the previous section, import this
HTML 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 Workspace
artifacts, 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 should
now 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 Environment

You navigate in Workspace differently in mixed-release environments than in single-release
environments.
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 the
Favorites menu. Applications launched from Machine 1 in the previous figures open in a separate
browser 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 =
,resizable=yes');
}
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 =
,resizable=yes');
}
}
else
{
var newWin =
,resizable=yes');
}
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>

A B C D E F H I J L M N O P R S T U W
Index
A recommendations, 104
Administration Services relational database, 105
application server Reporting and Analysis, 106
UNIX startup scripts, 127 Interactive Reporting, 107
Windows service names, 127 Shared Services Registration, 104
default ports, 77 worksheets, 103
install/configuration tasks, 113 configuration sequence, 111
release compatibility, 46
system requirements, 22
Apache Server, supported versions, 38
D
Data Integration Management
Application Builder J2EE, default ports, 83
default ports, 89
Application Builder.NET, default ports, 84
install/configuration tasks, 121
application servers
license keys, 65
configuration, 105
prerequisites, 70, 72
assistive technologies
UNIX startup script, 136
Windows service names, 136
screen magnifier, 18
Data Management
screen reader, 18
default ports, 89
auditing license compliance, 65
authentication providers, system requirements, 15
repository passwords, 99
B Data Relationship Management
BEA WebLogic, supported versions, 25, 29, 37, 42 default ports, 91
default URLs, 137
C release compatibility, 50
client
OS, 17
processor, 17
compatibility of releases, 45
database connectivity
configuration
system requirements
Essbase, 106, 108, 109
Data Integration Management, 43
Performance Scorecard Alerter, 109
Essbase, 26
application server, 105
JDBC, 26
description, 103
ODBC, 26
Planning , 109
Translation Manager, 43
prerequisites, 71
Index 147
database requirements install/configuration tasks, 116

prerequisites, 69, 71 release compatibility, 49
default URLs, 123 repository passwords, 97
Data Relationship Management, 137 system requirements, 33
Financial Data Quality Management, 137 Windows service names, 133
Performance Scorecard, 137 Financial Performance Management Applications
User Management Console, 137 default ports, 84
Workspace, 137 release compatibility, 49
Disk space and RAM repository passwords, 96
client software, 19 system requirements, 34
Data Management, 40 Financial Reporting
Essbase - System 9, 24 application server
Financial Performance Management Applications, UNIX startup script, 132
35 Windows service names, 132
Foundation Services, 15 configuration, 107
Reporting and Analysis, 27 default ports, 81
Shared Services, 15 install/configuration tasks, 117
Domino LDAP, supported versions, 15 release compatibility, 47
E UNIX startup script, 129
Essbase
Configuration Utility Worksheets, 106
Firefox, supported versions, 20
default ports, 77
Foundation Services
default ports, 75
Essbase - System 9
default ports, 77 H
install/configuration tasks, 113 hardware preparation, 68
release compatibility, 46 HP-UX
system requirements, 22 32-bit server, supported versions, 39
Hyperion
components, 9
F overview, 9
FDM
Hyperion Home location, 71
default ports, 91
Hyperion License Server, 53
default URLs, 137
disk space requirements, 40
install/configuration tasks, 120 I
release compatibility, 50 IBM DB2 for z/OS, supported versions, 31
system requirements, 38 IBM DB2 OLAP Server, supported versions, 31
Windows service names, 135 IBM DB2, supported versions, 28, 31, 37, 42
Financial Management IBM Directory Server, supported version, 15
configuration, 109 IBM Tivoli Directory Server, supported version, 15
default ports, 84
148 Index
IBM WebSphere, supported versions, 25, 29, 38, 37, Lightweight Directory Access Protocol (LDAP), 15
42
Informix, supported versions, 31
installation
M
Microsoft Active Directory, supported version, 15
downloading documentation, 68
Microsoft IIS, supported versions, 30, 38
downloading software, 67
Microsoft Internet Explorer, supported versions, 20
planning, 67
Microsoft NTLM, supported version, 15
sequence, 111
Microsoft SQL Server, supported versions, 25, 28, 32,
Integration Services
37, 42
Microsoft Windows
32-bit and 64–bit server, supported versions, 27,
39
32-bit server, supported versions, 34
Essbase — System 9, 23
Interactive Reporting
64-bit server, supported versions
configuration, 107
Essbase — System 9, 23, 34
default ports, 82
release compatibility, 47 N
system requirements, 26 Netegrity SiteMinder, supported version, 16
UNIX startup script, 128 Novell eDirectory, supported version, 15
O
J OpenLDAP
Java application servers supported versions, 15
configuration, 105 UNIX startup script, 124
Essbase - System 9, 25 Windows service name, 124
Financial Performance Management Applications, Oracle
37 application server, supported versions, 25, 29, 38,
prerequisites, 70, 72 42
Reporting and Analysis, 29 databases, supported versions, 25, 29, 32, 37, 42
Java browser plug-in Oracle Identity Management, supported version, 16
system requirements order of installation, 111
32-bit, 21
64-bit, 21
Java Runtime Environment
P
passwords, repository, 93
Performance Management Architect
32-bit, 21
application server
64-bit, 21
configuration, 109
L Data Synchronizer application server
license compliance, 53 Windows service names, 131
license keys default ports, 86
Data Integration Management, 65 install/configuration tasks, 114, 116
licensing release compatibility, 49
prerequisites, 71 repository passwords, 98
Index 149
system requirements, 33 Provider Services, 78

Web services Reporting and Analysis, 79, 80
Windows service name, 126 Shared Services, 75
Windows service names, 125 Smart Search, 79
Performance Scorecard Strategic Finance, 86
application server Translation Manager, 90
UNIX startup script, 134 Web Analysis, 82
Windows service names, 134 Workspace, 83
configuration, 108 prerequisites
default ports, 85 configuration, 71
default URLs, 137 databases, 69
install/configuration tasks, 118 Hyperion Home, 71
release compatibility, 49 Java application servers, 72
repository passwords, 99 java application servers, 70
system requirements, 33 licensing, 71
Performance Scorecard Alerter resolving port conflicts, 71
application server security, 69
UNIX startup script, 134 Shared Services, 71
Windows service names, 134 system requirements, 68
configuration, 109 Web servers, 70
Planning product groupings
application server Foundation Services, 13
UNIX startup script, 133 Data Management, 14
Windows service names, 133 Essbase — System 9, 13
default ports, 85 Financial Performance Management Applications,
install/configuration tasks, 114 13
release compatibility, 49 Reporting and Analysis, 13
system requirements, 33 product installation sequence, 111
ports Provider Services
Administration Services, 77 application server
Application Builder J2EE, 83 UNIX startup script, 128
Application Builder.NET, 84 Windows service names, 128
Data Integration Management, 89 default ports, 78
Data Management, 89 install/configuration tasks, 113
Data Relationship Management, 91 release compatibility, 46
Essbase, 77 system requirements, 22
Essbase - System 9, 77 provisioning, tasks, 121
FDM, 91
Financial Management, 84
Financial Performance Management Applications,
R
Red Brick, supported versions, 32
84
Red Hat Linux
Financial Reporting, 81
32-bit server, supported versions, 23, 27, 39
Interactive Reporting, 82
registry.properties, 53, 104
Performance Management Architect, 86
relational database, configuration, 105
Performance Scorecard, 85
Planning, 85
prerequisites, 71
configuration, 106
150 Index
default ports, 79, 80 default ports, 79

install/configuration tasks, 117 Solaris
release compatibility, 47 32-bit server, supported versions, 23, 27, 39
repository passwords, 94 64-bit server, supported versions, 23
system requirements, 26 SQR Production Reporting
Reporting and Analysis Core Services configuration, 108
UNIX startup script, 125 install/configuration tasks, 117
Reporting and Analysis Core Services release compatibility, 47
Windows service name, 125 system requirements, 26
repository passwords, 93 startup dependencies, 123
Administration Services, 94 Strategic Finance
Data Management, 99 configuration, 109
Data Relationship Management, 100 default ports, 86
Financial Management, 97 install/configuration tasks, 119
Financial Performance Management Applications, release compatibility, 49
96 system requirements, 34
Financial Reporting, 95 Windows service names, 134
Performance Scorecard, 99 Sun Java Enterprise System, supported versions, 29
Planning, 96 Sun One, supported version, 15
Shared Services, 93 Sybase, supported versions, 32
Translation Manager, 101 system requirements, 13
Web Analysis, 95 assistive technologies, 18
Workspace, 94 client, 16
runtime clients, system requirements, 18 Java Runtime environment, 21
OS, 17
other required third-party software, 21
S required Hyperion software, 17
SAP Enterprise Portal, supported version, 16
Web Browser, 20
SAP R/3, supported versions, 32
Web Browser plug-in, 21
screen magnifier, system requirements, 18
Data Management, 38
screen reader, system requirements, 18
database connectivity
screen resolution, system requirements, 18
JDBC, 26
security, prerequisites, 69
ODBC, 26
sequence, installation, 111
Essbase
service names. See Windows service names
database connectivity, 26
Shared Services
server OS/processor, 23
application server
Essbase - System 9, 22
Financial Performance Management Applications,
33, 34
default ports, 75
disk space and RAM, 35
Java application servers, 37
OpenLDAP
repository databases, 36
required third-party software, 36
Windows service name, 124
Foundation Services, 15
registration, 104
Java application servers, 29
Java browser plug-in
system requirements, 15, 26
32-bit, 21
Smart Search
Index 151
64-bit, 21 upgrading
Java Runtime Environment mixed-release environment, 139
32-bit, 21 sequence, 111
64-bit, 21 supported upgrade paths, 11
processor, 17 URLs, default, 123
Reporting and Analysis, 26, 27 User Directories, system requirements, 15
runtime clients, 18 User Management Console
screen resolution, 18 default URLs, 137
Shared Services system requirements, 137
disk space and RAM, 15 User Management Console
Translation Manager default URLs, 137
database connectivity, 43
User Directories, 15
Windows clients
W
Web Analysis
disk space and RAM, 19
application server
T Windows service names, 130
Teradata, supported versions, 33 default ports, 82
third-party software requirements, 21 install/configuration tasks, 117
Translation Manager release compatibility, 47
application server system requirements, 26
UNIX startup script, 136 Web Analysis Web server
Windows service names, 136 UNIX startup script, 130
default ports, 90 Windows service names, 130
repository passwords, 101 Web browser plug-in
system requirements, 38 system requirements, 21
Web servers, prerequisites, 70
U Administration Services application server, 127,
UNIX startup scripts, 123
131
Administration Services application server, 127
Data Relationship Management, 135
Performance Management Architect Data
Financial Reporting application server, 132
Synchronizer application server, 131
Financial Data Quality Management, 135
Performance Scorecard Alerter application server,
Financial Management, 133
134
Performance Scorecard application server, 134
Financial Reporting application server, 132
Planning application server, 133
Provider Services application server, 128
Performance Scorecard Alerter application server,
Reporting and Analysis Core Services, 125
134
Shared Services application server, 124
Performance Scorecard application server, 134
Shared Services OpenLDAP, 124
Planning application server, 133
Translation Manager application server, 136
Provider Services application server, 128
Web Analysis application server, 130
Reporting and Analysis Core Services, 125
Web Analysis Web server, 130
Shared Services application server, 124
Workspace application server, 128
Shared Services OpenLDAP, 124
152 Index
Strategic Finance, 134

Translation Manager application server, 136
Web Analysis application server, 130
Web Analysis Web server, 130
Performance Management Architect Web services,
126
Workspace application server, 128
Workspace
application server
configuration, 106
default ports, 83
default URLs, 137
Index 153
154 Index

Hsys9 Install Start Here

Transféré par

Informations du document

Description originale:

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Hsys9 Install Start Here

Transféré par

Droits d'auteur :

Formats disponibles

HYPERION

INSTALLATION START HERE

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

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

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

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

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

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

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

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

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

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

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® Data

10 Hyperion Product Components

About System Requirements

About System Requirements 13

Shared Services Requirements

Shared Services Server Disk Space and RAM

Disk Space 400 MB1

User Directories Notes

l IBM Tivoli Directory Server 5.2

l Netegrity SiteMinder 6 Not supported by FDM

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

Operating System Notes

l Windows 2003 SP1

l Oracle Enterprise Linux 412

Red Hat Linux3:

Processor (Windows) Notes

Pentium 4, 1.6 GHz The minimum required for all

One of the following: Applies only to Strategic

Pentium 4.8 GHz minimum Applies only to Translation

2 GHz minimum Applies only to Data

Required Hyperion Software

Assistive Technologies Supported Versions

Screen reader l JAWS 7

Screen magnifier l MAGic 9.3

Clients Runtime Client

l Financial Reporting l Essbase—The Essbase runtime client is installed automatically.

Web Analysis l Java Plug-in: 1.5.0_09 and 1.4.2_12

Planning Essbase—The Essbase runtime client is installed automatically.

Disk Space and RAM

Product Grouping Component Disk Space Notes

Essbase - System 9 Essbase Runtime Client 150 MB

UNIX Essbase Runtime Client 150 MB