You are on page 1of 264

Oracle Hyperion Enterprise Performance Management System

Installation and Configuration Guide RELEASE 11.1.1.3 Updated: February 2011

EPM System Installation and Configuration Guide, 11.1.1.3 Copyright 2008, 2011, 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

Documentation Accessibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Chapter 1. About EPM System Product Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 About EPM System Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Assumed Knowledge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 The EPM System Product Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Installing EPM System Products in a Distributed Environment . . . . . . . . . . . . . . . . . . . . 15 About the Hyperion Home Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Installation Documentation Roadmap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Chapter 2. Preparing for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Downloading the Installation Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Component Installation By Tier and Installation Assemblies . . . . . . . . . . . . . . . . . . . . . . 20 Foundation Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Essbase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Reporting and Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Financial Performance Management Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Data Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Download File Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Chapter 3. Installing EPM System Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Installation Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Upgrade Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Characters Supported for Installation and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 49 Installing EPM System Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Welcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Installation Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Product Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Upgrade Homes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Contents

iii

Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Performing Silent Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Loading Saved Selections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Modifying Response Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Installing Additional Instances of Essbase Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Chapter 4. Configuring EPM System Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 About EPM System Configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 About the Shared Services Registry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Satisfying Initial Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Upgrade Configuration Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Configuration Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Configuring Products in a Single-Machine Environment . . . . . . . . . . . . . . . . . . . . . . 68 Configuring Products in a Distributed Environment . . . . . . . . . . . . . . . . . . . . . . . . . 68 Configuring Products in an SSL-Enabled Environment . . . . . . . . . . . . . . . . . . . . . . . 68 Upgrade Configuration Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Product Configuration Task Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Using EPM System Configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Task Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Shared Services and Registry Database Configuration . . . . . . . . . . . . . . . . . . . . . . . . 75 Upgrade Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Enable Separately Licensed Product Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 EPM System Common Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Database Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Deploy to Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Application Server Deployment: Oracle Application Server . . . . . . . . . . . . . . . . . . . . 83 Application Server Deployment: Oracle | BEA WebLogic . . . . . . . . . . . . . . . . . . . . . . 84 Application Server Deployment: WebSphere . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Application Server Deployment: Embedded Java Container . . . . . . . . . . . . . . . . . . . . 87 Cluster Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 EPM WorkspaceSpecific Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Performance Management ArchitectSpecific Tasks (Optional) . . . . . . . . . . . . . . . . 92 EssbaseSpecific Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 PlanningSpecific Tasks (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Financial ManagementSpecific Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Reporting and AnalysisSpecific Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Strategic FinanceSpecific Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 FDMSpecific Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 Performing Silent Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

iv

Contents

Setting Up the Shared Services Registry Without Installing Shared Services . . . . . . . . . . . 109 What Happens During Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Troubleshooting Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Chapter 5. Starting and Stopping EPM System Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Using a Single Script to Start Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Summary List of Services and Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Services and Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Databases for Repositories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Corporate User Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Shared Services OpenLDAP or Oracle Internet Directory . . . . . . . . . . . . . . . . . . . . . 113 Shared Services Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 EPM Workspace Agent (CMC Agent) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 EPM Workspace UI (CMC UI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 EPM Workspace Web Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 Performance Management Architect Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Essbase Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Administration Services Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 Smart Search Command Line Utility Application Server . . . . . . . . . . . . . . . . . . . . . 121 Integration Services Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Essbase Studio Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 Provider Services Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 Reporting and Analysis Services and Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Remaining Services or Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 EPM Workspace Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 Launching Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 Chapter 6. Validating the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 About EPM System Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 Using EPM System Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 Foundation Services Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 Essbase Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Reporting and Analysis Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Financial Performance Management Applications Diagnostics . . . . . . . . . . . . . . . . . . . . 140 Data Management Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 Chapter 7. Performing Postconfiguration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 General Postconfiguration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 Increasing the JVM Memory Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Contents

Shared Services Postconfiguration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Performance Management Architect Postconfiguration Tasks . . . . . . . . . . . . . . . . . . . . 144 EPM Workspace Postconfiguration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Essbase Postconfiguration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Setting User Limits on 64-bit AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 Integration Services Postconfiguration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 Administration Services Postconfiguration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 Provider Services Postconfiguration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Essbase Studio Postconfiguration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Updating the Essbase Studio Catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Reporting and Analysis Postconfiguration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 Preparing the Financial Reporting Print Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 Configuring X11 for Web Application Server Components for Financial Reporting and Web Analysis (UNIX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 Configuring SAP Data Source Access and Authentication . . . . . . . . . . . . . . . . . . . . 150 Setting Up Environment Variables for Financial Reporting and Web Analysis for NonEnglish Characters (UNIX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Setting up the Environment Variables for Production Reporting (UNIX) . . . . . . . . . 152 Preparing Interactive Reporting for Printing (UNIX) . . . . . . . . . . . . . . . . . . . . . . . 153 Configuring Fonts (UNIX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Financial Reporting ConfigurationEnabling the Provider Services Driver . . . . . . . 154 Recreating the Executables (Production Reporting Only) (UNIX) . . . . . . . . . . . . . . 154 Planning Postconfiguration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 Configuring Offline Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 (UNIX) Configuring the Planning Locale for Use in Non-English Environments . . . 156 Financial Management Postconfiguration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 Configuring Settings for IIS 5.0 Isolation Mode (Optional) . . . . . . . . . . . . . . . . . . . 157 Strategic Finance Postconfiguration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 Performance Scorecard Postconfiguration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 FDM Postconfiguration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 ERP Integrator Postconfiguration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 Preparing ERP Integrator for Use with Microsoft SQL Server . . . . . . . . . . . . . . . . . . 158 Data Relationship Management Postconfiguration Tasks . . . . . . . . . . . . . . . . . . . . . . . . 159 Chapter 8. Upgrading EPM System Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 About Upgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 Improvements in This Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 Upgrade and Migrate Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 Supported Upgrade Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 What Happens During Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

vi

Contents

Upgrade Documentation Not Provided . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 About Upgrading Only Some EPM System Products . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Limitations of Using Shared Services with Earlier Releases of Other Products . . . . . . 166 Limitations of Using Performance Management Architect 11.1.1.x with Earlier Releases of Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Upgrading Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 Determine Which Products To Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 Backing Up the Earlier Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 Ensure That ProductSpecific Prerequisites Are Met . . . . . . . . . . . . . . . . . . . . . . . 169 Installing and Configuring EPM System Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 Upgrading Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 Upgrading Planning Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 Upgrading Financial Management Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 Moving Classic Applications to Performance Management Architect . . . . . . . . . . . . 173 Migrating Business Rules to Calculation Manager . . . . . . . . . . . . . . . . . . . . . . . . . . 175 Performing Security Related Upgrade Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 Provisioning Planning Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 Transferring Users and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 Implementing the Unique Identity Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 Additional Product-Specific Upgrade Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 Refreshing the Performance Management Architect User Interface . . . . . . . . . . . . . . 180 Upgrading Essbase to Release 11.1.1.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 Upgrading Reporting and Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 Upgrading Strategic Finance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 Working in an Environment with Multiple Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 Using Reporting and Analysis 11.1.1.3 with Earlier Releases of Planning . . . . . . . . . . 186 Using Earlier Releases of Administration Services . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Upgrading from EPM System Release 9.3.x After Working in An Environment with Multiple Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 Chapter 9. Reconfiguring EPM System Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 Reconfiguring for SSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 Redeploying to a Different Web Application Server Type . . . . . . . . . . . . . . . . . . . . . . . . 193 Redeploying from the Embedded Java Container or WebSphere to WebLogic Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 Redeploying Applications from Oracle Application Server to WebLogic Server . . . . . 194 Changing Repository Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Changing the Shared Services and Registry Repository Password . . . . . . . . . . . . . . . 195 Changing EPM System Product Repository Passwords . . . . . . . . . . . . . . . . . . . . . . 195

Contents

vii

Changing the Planning Applications Repository Password . . . . . . . . . . . . . . . . . . . . 196 Changing the Performance Management Architect Interface Datasource Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 Changing the FDM Repository Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 Changing the Data Relationship Management Repository Password . . . . . . . . . . . . . 197 Reconfiguring Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 Chapter 10. Deployment Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 Considerations for Distributed Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 Adding Servers to a Financial Management Deployment . . . . . . . . . . . . . . . . . . . . . . . . 200 Chapter 11. Uninstalling EPM System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 Uninstalling EPM System Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 Performing a Silent Uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 Chapter 12. License Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 Ensuring License Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 Activating and Deactivating Product Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 Auditing Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 Appendix A. What Happens During Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207 What Happens During Shared Services Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207 Files Installed in the Foundation Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 Common Files installed in the HYPERION_HOME Directory . . . . . . . . . . . . . . . . . 208 What Happens During EPM Workspace Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 Files Installed in the EPM Workspace Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 What Happens During Performance Management Architect Installation . . . . . . . . . . . . 211 Files Installed in the Performance Management Architect Directory . . . . . . . . . . . . . 212 What Happens During Calculation Manager Installation . . . . . . . . . . . . . . . . . . . . . . . . 212 Files Installed in the Calculation Manager Directory . . . . . . . . . . . . . . . . . . . . . . . . 212 What Happens During Smart View Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 Files Installed in the Smart View Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 What Happens During Essbase Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 Files Installed in the Essbase Server Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 Files Installed in the Essbase Client Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 What Happens During Essbase Studio Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 Files Installed in the Essbase Studio Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 What Happens During Integration Services Installation . . . . . . . . . . . . . . . . . . . . . . . . . 216 Files Installed in the Integration Services Directory . . . . . . . . . . . . . . . . . . . . . . . . . 216 What Happens During Administration Services Installation . . . . . . . . . . . . . . . . . . . . . 218 Files Installed in the Administration Services Directory . . . . . . . . . . . . . . . . . . . . . . 218

viii

Contents

What Happens During Provider Services Installation . . . . . . . . . . . . . . . . . . . . . . . . . . 219 Files Installed in the Provider Services Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 What Happens During Smart Search Command Line Utility Installation . . . . . . . . . . . . 219 Files Installed in the Smart Search Command Line Utility Directory . . . . . . . . . . . . . 220 What Happens During Reporting and Analysis Installation . . . . . . . . . . . . . . . . . . . . . . 220 Files Installed in the Reporting and Analysis Directory . . . . . . . . . . . . . . . . . . . . . . 220 What Happens During Planning Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 Files Installed in the Planning Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 What Happens During Financial Management Installation . . . . . . . . . . . . . . . . . . . . . . 221 Files Installed in the Financial Management Directory . . . . . . . . . . . . . . . . . . . . . . . 222 What Happens During Performance Scorecard Installation . . . . . . . . . . . . . . . . . . . . . . 222 Files Installed in the Performance Scorecard Directory . . . . . . . . . . . . . . . . . . . . . . 223 What Happens During Strategic Finance Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 Files Installed in the Strategic Finance Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 What Happens During Profitability and Cost Management Installation . . . . . . . . . . . . . 224 Files Installed in the Profitability and Cost Management Directory . . . . . . . . . . . . . . 224 What Happens During FDM Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 Files Installed in the FDM Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 What Happens During Data Relationship Management Installation . . . . . . . . . . . . . . . . 225 Appendix B. Optional Manual Configuration for Essbase Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 Manually Configuring the Essbase Server Environment (UNIX) . . . . . . . . . . . . . . . . . . . 227 Specifying Parameters in hyperionenv.doc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 Changing ESS_JVM_OPTION and ESS_CSS_JVM_OPTION . . . . . . . . . . . . . . . . . 229 Changing JvmModuleLocation (UNIX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230 Optional Manual Configuration for Integration Services (UNIX) . . . . . . . . . . . . . . . 231 Optional Manual Configuration for Administration Services (UNIX) . . . . . . . . . . . . 233 Optional Manual Configuration for Provider Services (UNIX) . . . . . . . . . . . . . . . . . 233 Manually Configuring the Essbase Server Environment (Windows) . . . . . . . . . . . . . . . . 233 Updating the Environment Manually for Essbase Server . . . . . . . . . . . . . . . . . . . . . 234 Setting JVMMODULELOCATION (Windows) . . . . . . . . . . . . . . . . . . . . . . . . . . . 234 Configuring the 32-bit Runtime Client on a 64-bit Windows Platform . . . . . . . . . . . 235 Optional Manual Configuration for Integration Services (Windows) . . . . . . . . . . . . 236 Optional Manual Configuration for Administration Services (Windows) . . . . . . . . . 236 Optional Manual Configuration for Essbase Studio (Windows) . . . . . . . . . . . . . . . . 236 Optional Manual Configuration for Provider Services (Windows) . . . . . . . . . . . . . . 236 Appendix C. Essbase 32-Bit and 64-Bit Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 Essbase 32-Bit and 64-Bit Client and Server Compatibility . . . . . . . . . . . . . . . . . . . . . . . 239 Essbase API Compatibility on 32-Bit and 64-Bit Platforms . . . . . . . . . . . . . . . . . . . . . . . 240

Contents

ix

Appendix D. JDBC URL Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241 Appendix E. Database Information for Financial Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 Database Connection Pooling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 Encrypting UDL Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 Appendix F. Updating the Shared Services Registry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247 Understanding the Shared Services Registry Component Hierarchy . . . . . . . . . . . . . . . . 247 Making Corrections to the Shared Services Registry . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 Viewing the Components in the Shared Services Registry . . . . . . . . . . . . . . . . . . . . . 249 Deleting a Component Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250 Updating a Component Property . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250 Updating the Host and Port for Financial Management Logical Web Applications . . . . . 251 Appendix G. Enabling an X Virtual Frame Buffer for Financial Reporting and Web Analysis . . . . . . . . . . . . . . 253 Enabling Xvfb for AIX 5L . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253 Enabling Xvfb for Solaris 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253 Enabling Xvfb for Solaris 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 Enabling Xvfb for Oracle Enterprise Linux/Red Hat Enterprise Linux . . . . . . . . . . . . . . . 254 Enabling Xvfb for HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255 Setting the DISPLAY Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257

Contents

Documentation Accessibility

Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at http://www.oracle.com/accessibility/.

Accessibility of Code Examples in Documentation


Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.

Accessibility of Links to External Web Sites in Documentation


This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.

Access to Oracle Support for Hearing-Impaired Customers


Oracle customers have access to electronic support through My Oracle Support or by calling Oracle Support at 1.800.223.1711. Hearing-impaired customers in the U.S. who wish to speak to an Oracle Support representative may use a telecommunications relay service (TRS). Information about the TRS is available at http://www.fcc.gov/cgb/consumerfacts/trs.html/, and a list of telephone numbers is available at http://www.fcc.gov/cgb/dro/trsphonebk.html. International hearing-impaired customers should use the TRS at +1.605.224.1837. An Oracle Support engineer will respond to technical issues according to the standard service request process.
11

12

Documentation Accessibility

1
In This Chapter

About EPM System Product Installations

About EPM System Products..............................................................................13 Assumed Knowledge.......................................................................................13 The EPM System Product Installation Checklist .........................................................14 Installing EPM System Products in a Distributed Environment ........................................15 About the Hyperion Home Directory......................................................................16 Installation Documentation Roadmap ...................................................................17

About EPM System Products


Check the Oracle Documentation Library (http://www.oracle.com/technology/documentation/ epm.html) on Oracle Technology Network to see whether an updated version of this guide is available. Oracle Hyperion Enterprise Performance Management System products form a comprehensive Enterprise Performance Management system that integrates modular suites of financial management applications with the most comprehensive business intelligence capabilities for reporting and analysis. Major components of EPM System products:
l

Oracle's Hyperion Foundation Services Oracle Essbase Oracle's Hyperion Reporting and Analysis Oracle's Hyperion Financial Performance Management Applications Oracle's Data Management

For information about the products and components in each of these product families, see Oracle Hyperion Enterprise Performance Management System Installation Start Here.

Assumed Knowledge
This guide is for administrators who install, configure, and manage EPM System products. It assumes the following knowledge:
l

Security and server administration skills Windows administration skills and or UNIX/Linux administration skills
About EPM System Products

13

Web application server administration skills A strong understanding of your organization's security infrastructure, including authentication providers such as Oracle Internet Directory, LDAP, or Microsoft Active Directory, and use of SSL A strong understanding of your organization's database and server environments A strong understanding of your organization's network environment and port usage

The EPM System Product Installation Checklist


Oracle Hyperion Enterprise Performance Management System Installer, Fusion Edition installs components on three tiers:
l

Client tier Services tier Web tier, which includes the Java Application Server tier and the Web server tier

Additionally, when you configure EPM System products, you set up databases on the Data tier. For more information about EPM System product architecture, see Oracle Hyperion Enterprise Performance Management System Installation Start Here. EPM System installation follows this workflow. Each part of the workflow is described in the guides as noted in the table below:
Task Plan the installation. Prepare the installation files. Meet the system requirements and prerequisites. Reference Installation Planning Checklist in Oracle Hyperion Enterprise Performance Management System Installation Start Here Chapter 2, Preparing for Installation System requirements in the Oracle Hyperion Enterprise Performance Management System Certification Matrix (http://www.oracle.com/technology/products/bi/hyperion-supportedplatforms.html) and Installation Planning Checklist in Oracle Hyperion Enterprise Performance Management System Installation Start Here Chapter 3, Installing EPM System Products Tip: Before you begin, determine the type of installation you will be performing:
l l l l

Install EPM System products.

New installation Upgrade from a previous release Maintenance release installation Re-installation

For details on each installation type, see Installation Type on page 53.

14

About EPM System Product Installations

Task Configure EPM System products.

Reference Chapter 4, Configuring EPM System Products Note: In a distributed environment, configure Oracle's Hyperion Shared Services first. Shared Services must be installed, configured, and running for other products to configure successfully. Note: In an SSL-enabled environment, configure Shared Services first, selecting Enable SSL for communications. Then, set up Shared Services for SSL and make sure Shared Services is running in SSL mode before you configure other EPM System products.

(Optional) Manually deploy if you did not automatically deploy Java Web applications to a Web application server. Confirm that EPM System services are started. Validate the installation using Oracle's Hyperion Enterprise Performance Management System Diagnostics. Perform any required postconfiguration tasks for your products. Enable external authentication and provision users. (Optional) Enable Shared Services and the user directory for SSL, and then enable installed products for SSL.

Oracle Hyperion Enterprise Performance Management System Manual Deployment Guide

Chapter 5, Starting and Stopping EPM System Products Chapter 6, Validating the Installation

Chapter 7, Performing Postconfiguration Tasks

Oracle Hyperion Enterprise Performance Management System Security Administration Guide Oracle Hyperion Enterprise Performance Management System SSL Configuration Guide

Tip: During installation, configuration, and validation, keep a list of all user names and

passwords that you use to create or modify the system, including the applications with which they are associated and their purpose. Upgrade Note! If you are upgrading from a previous release of EPM System products, use EPM System Installer and Oracle's Hyperion Enterprise Performance Management System Configurator to upgrade products on each machine in your deployment. See Chapter 8, Upgrading EPM System Products.

Installing EPM System Products in a Distributed Environment


You typically install EPM System products in a distributed environment. The number of computers you need depends on several factors, including:
l

The size of the applications


15

Installing EPM System Products in a Distributed Environment

The number of users The frequency of concurrent use by multiple users Any requirements your organization has for high availability Your organization's security requirements

EPM System Installer simplifies the task of installing components in a distributed computing environment. You can install, configure, and validate any components you want on any computer. Once you have installed, configured, and validated the components on that machine, you can repeat the process on another machine.For more information about planning a distributed installation, see EPM System Product Deployment in Oracle Hyperion Enterprise Performance Management System Installation Start Here and Oracle Hyperion Enterprise Performance Management System High Availability Guide. For information about which assemblies you need on each machine in a distributed environment, see Chapter 2, Preparing for Installation. You install Shared Services on only one machine in the deployment.
Note: If you are installing in multiple environments (for example, Development, Test, and

Production), install Foundation Services products in each environment.

About the Hyperion Home Directory


The Hyperion home directory location is defined during the first product installation on the computer. Subsequent installations on the computer use the previously defined location. All EPM System products are installed in directories under the Hyperion home directory. In addition, common internal and third-party components used by the products are installed in the Hyperion home directory. Choose the location carefully to ensure that the location has enough disk space for all products that you are installing on the machine. You cannot change the location. The Hyperion home directory location is defined in the system environment variable called HYPERION_HOME (Windows) or .hyperion.'hostname' in the home directory of the user installing EPM System products (UNIX). The default location is C:/Hyperion (Windows) or $HOME/hyperion (UNIX). The Hyperion home directory location is referred to as HYPERION_HOME throughout this document.
Note: To ensure that EPM System Installer has the permissions required to modify the

HYPERION_HOME location, Oracle requires that all EPM System applications be installed using the same user account. For information about common files installed in HYPERION_HOME, see Files Installed in the Foundation Directory on page 208.

16

About EPM System Product Installations

Installation Documentation Roadmap


You can find EPM System installation documentation on the Oracle Documentation Library (http://www.oracle.com/technology/documentation/epm.html) on Oracle Technology Network. For system requirements, you can find the Oracle Hyperion Enterprise Performance Management System Certification Matrix at http://www.oracle.com/technology/products/bi/ hyperion-supported-platforms.html. Table 1 lists the documents to consult for instructions on performing essential installation tasks.
Table 1

Documentation That You Need Related Documentation Oracle Hyperion Enterprise Performance Management System Certification Matrix (http://www.oracle.com/technology/products/bi/hyperion-supported-platforms. html) Oracle Hyperion Enterprise Performance Management System Installation Start Here Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide

Task Meeting system requirements

Planning the installation Installing and configuring EPM System products Automatically deploying EPM System products Starting EPM System products Validating the installation Upgrading EPM System products

l l l l l

Securing EPM System and provisioning users

Oracle Hyperion Enterprise Performance Management System Security Administration Guide

Table 2 lists the documents to consult for additional installation tasks that you might need to perform.
Table 2

Documentation That You Might Need Related Documentation Oracle Hyperion Enterprise Performance Management System Manual Deployment Guide Oracle Hyperion Enterprise Performance Management System Installation and Configuration Troubleshooting Guide Oracle Hyperion Enterprise Performance Management System Backup and Recovery Guide Oracle Hyperion Enterprise Performance Management System Lifecycle Management Guide Oracle Hyperion Enterprise Performance Management System SSL Configuration Guide Oracle Hyperion Enterprise Performance Management System High Availability Guide

Task Manually deploying EPM System products Troubleshooting installations Creating a backup of product and application data Migrating from one environment to another Enabling SSL Clustering EPM System applications for high availability

Installation Documentation Roadmap

17

18

About EPM System Product Installations

2
In This Chapter

Preparing for Installation

Downloading the Installation Files .......................................................................19 Component Installation By Tier and Installation Assemblies ..........................................20

Downloading the Installation Files


To download the installation files:
1
Create a directory to store the EPM System files.

You can download files to a shared drive, or to each machine in your deployment. If you are installing from a network drive, map this drive. This directory is referred to as / download_location in this procedure.
Tip: Oracle recommends that you download files to a shared drive.

Download the following files from the Oracle Enterprise Performance Management System page of the Oracle E-Delivery (http://edelivery.oracle.com/) site into /download_location:
l

EPM System Installer (Oracle Hyperion Enterprise Performance


Management System Installer, Fusion Edition Release 11.1.1.3.0).

ZIP files for the products you purchased. ZIP files include installation assemblies (product plug-in installation files for EPM System Installer). Review the Media Pack Readme on Oracle E-Delivery to see which ZIP files to download depending on the products you purchased. (To see the Media Pack Readme, once you have selected the media pack, click Readme.)

3 4

Unzip the EPM System Installer into /download_location.

If you are prompted that any files already exist, click Yes to overwrite the files.
Unzip the installation assemblies into the same directory (/download_location).

If you are prompted that any files or common components already exist, click Yes to overwrite the files. The assemblies are unzipped into an /assemblies directory. If you downloaded files to multiple machines in your deployment, on each machine, you need to unzip only the assemblies for the products or product components that you are installing on that machine.

Downloading the Installation Files

19

For information about which assemblies to use for product components, see Component Installation By Tier and Installation Assemblies on page 20. If you downloaded files to a central location, make sure you unzip the following common files. If you downloaded files to multiple machines in your deployment, on each machine in the deployment, unzip the following common files:
l

Oracle Hyperion Enterprise Performance Management System Installer, Fusion Edition Release 11.1.1.3.0 Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 1 of 4 Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 2 of 4 Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 3 of 4 Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 4 of 4

Note: Even though you need the EPM-FoundationServices ZIP files on each machine in the

environment, install Shared Services on only one machine.

The /assemblies directory should include a subdirectory for each product that you want to install on this machine. Ensure that the /assemblies directory looks as follows:
assemblies/ product/ version/ assembly.dat

Note: ProductRef.inf might be in the /assemblies directory. It can remain without

causing problems. EPM System Installer can install a product only if the installation assembly files for the product are downloaded and unzipped to the correct location.

Component Installation By Tier and Installation Assemblies


Use the information in this section to help plan which ZIP files to download and which assemblies are required for EPM System product components.
Tip: Oracle recommends that you download ZIP files to a shared drive. If you follow this

recommendation, you do not need to use the following tables to determine which ZIP files are required for each product component.

20

Preparing for Installation

The following sections describe the components and services available for installation on each tier (Client, Web, and Services) for each product when you install using the option Choose components individually. Most components and services that are installed are the same if you install using the option Choose components by tier. The following components are available only if you select Choose components individually during installation:
l

Choices for 32bit and 64bit for Oracle Essbase products If you select Choose components by tier, EPM System Installer installs 32-bit on all platforms, except for platforms that are 64-bit only.

Oracle's Hyperion SQR Production Reporting Remote Oracle Hyperion Strategic Finance, Fusion Edition Reader Client Strategic Finance Integration with Financial Management Services Strategic Finance Integration with Enterprise Service FDM Server Financial Management Adapter

The following tables also describe the ZIP files and installation assemblies required to install each component.

Foundation Services
The following table describes the components installed on each tier for Foundation Services products and the ZIP files and installation assemblies required to install that component.
Note: The commonComponents assembly is required for all products. The tools and productCommonComponents assemblies are required for all server and Web applications. These assemblies are in Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 1 of 4 and Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 2 of 4.

Component Installation By Tier and Installation Assemblies

21

Client Tier Shared Services

Web Tier

Services Tier

Component:
l l

Shared Services Web Application OpenLDAP Service (installed with productCommonComponents assembly) HRAM (Windows only, installed automatically with sharedServices assembly)

Required assemblies:
l l l l

commonComponents productCommonComponents tools sharedServices

Required download files:


l

Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 1 of 4 Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 2 of 4 Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 4 of 4

22

Preparing for Installation

Client Tier

Web Tier

Services Tier

Oracle Enterprise Performance Management Workspace, Fusion Edition Component: Workspace Web Application and Portlets Required assemblies:
l l l l l l

Component: Workspace Services and Common Libraries Required assemblies:


l l l l l l l

commonComponents productCommonComponents tools biplus_workspace_webapp workspace_configlibs biplus_portlets_webapp

commonComponents productCommonComponents tools productCommonComponents biplus_core_services workspace_configlibs biplus_migration_utility

Required download files:


l

Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 1 of 4 Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 2 of 4 Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 3 of 4

Required download files:


l

Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 1 of 4 Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 2 of 4 Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 3 of 4

l l

Component Installation By Tier and Installation Assemblies

23

Client Tier

Web Tier

Services Tier

Oracle Hyperion Smart View for Office, Fusion Edition for Office Component: Smart View Client (Windows only) Required assemblies:
l l

commonComponents
svc_client

Required download files:


l

Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1. 3.0 Part 1 of 4 Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1. 3.0 Part 4 of 4

24

Preparing for Installation

Client Tier

Web Tier

Services Tier

Oracle Hyperion EPM Architect, Fusion Edition Component:


l

Component:
l

Component:
l

Performance Management Architect Batch client Performance Management Architect File Generator (Windows only)

Performance Management Architect Web Application Performance Management Architect Data Synchronizer Service

Performance Management Architect Dimension Server Service (Windows only)

Required assemblies:
l l l l

Required assemblies: Required assemblies:


l l l l l

commonComponents productCommonComponents tools bpm_architect_services

commonComponents productCommonComponents tools bpm_architect_webapp bpm_architect_datasync

commonComponents
l

bpm_architect_batch_client
l

bpm_architect_generator
l

productCommonComponents
l

Required download files:


l

Required download files:


l

Required download files:


l

Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1. 3.0 Part 1 of 4 Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1. 3.0 Part 2 of 4 Oracle Hyperion Enterprise Performance Management Architect, Fusion Edition Release 11.1.1.3.0

Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 1 of 4 Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 2 of 4 Oracle Hyperion Enterprise Performance Management Architect, Fusion Edition Release 11.1.1.3.0

Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 1 of 4 Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 2 of 4 Oracle Hyperion Enterprise Performance Management Architect, Fusion Edition Release 11.1.1.3.0

Component Installation By Tier and Installation Assemblies

25

Client Tier Hyperion Calculation Manager

Web Tier

Services Tier

Component:
l

Calculation Manager Web Application

Required assemblies:
l l l l

commonComponents productCommonComponents tools calc

Required download files:


l

Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 1 of 4 Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 2 of 4 Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 3 of 4

26

Preparing for Installation

Client Tier Common (for all product installations) Component:


l

Web Tier

Services Tier

Component:
l

Oracle Hyperion Planning, Fusion Edition ADM driver (installed automatically)

Populates the HYPERION_HOME/common directory commonComponents (required for all component installations) productCommonComponents1 tools (required for all Server and Web tier component installations) essbaseProductCommonComponents

Required assemblies:
l

l l

Required download files:


l

Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 1 of 4 Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 2 of 4

1The

Configuration and Monitoring Console is installed with the productCommonComponents assembly when you select any of the following: Shared Services Web tier, EPM Workspace Web tier, EPM Workspace services tier, Oracle Hyperion Financial Reporting, Fusion Edition client tier, Financial Reporting Web tier, Financial Reporting services tier, Oracle's Hyperion Web Analysis Web tier.

Essbase
The following table describes the components installed on each tier for Essbase products and the ZIP files and installation assemblies required to install that component.
Note: The commonComponents assembly is required for all products. The tools and productCommonComponents assemblies are required for all server and Web applications. These assemblies are in Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 1 of 4 and Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 2 of 4.

Component Installation By Tier and Installation Assemblies

27

Client Tier Essbase Component:


l l

Web Tier

Services Tier

Component:
l l

Essbase Client 32bit Essbase Client 64bit

Essbase Services Server 32bit Essbase Services Server 64bit commonComponents productCommonComponents tools essbase_services (32bit and 64bit) essbaseProductCommonComponents essbaseAddins

(Includes Essbase API and Spreadsheet Add-in. Note that Spreadsheet Add-in is installed only with the 32bit installation and only if Microsoft Excel is installed on the machine) Required assemblies:
l l l

Required assemblies:
l l l l l l

commonComponents essbase_client essbaseAddins

Required download files:


l

Required download files:


l

Hyperion Enterprise Performance Management System Foundation Services Release 11.1. 1.3.0 Part 1 of 4 Oracle Essbase Client Release 11.1.1.3.0

Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 1 of 4 Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 2 of 4 Oracle Essbase Client Release 11. 1.1.3.0 Oracle Essbase Server Release 11. 1.1.3.0

28

Preparing for Installation

Client Tier

Web Tier

Services Tier

Oracle Essbase Administration Services Component:


l

Component:
l

Essbase Administration Services Client (Windows only) commonComponents essbase_administration_ services_client essbaseAddins

Administration Services 32bit Web Application Administration Services 64bit Web Application Oracle's Hyperion Business Rules (installed automatically) commonComponents productCommonComponents tools essbase_administration_services_ webapp essbaseAddins

Required assemblies:
l l

Required assemblies:
l

Required download files:


l

l l l

Hyperion Enterprise Performance Management System Foundation Services Release 11.1. 1.3.0 Part 1 of 4 Oracle Essbase Client Release 11.1.1.3.0

Required download files:


l

Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 1 of 4 Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 2 of 4 Oracle Essbase Client Release 11.1.1.3.0 Oracle Essbase Server Release 11.1.1.3.0

Component Installation By Tier and Installation Assemblies

29

Client Tier Oracle Essbase Integration Services Component:


l

Web Tier

Services Tier

Component:
l l

Essbase Integration Services Client (Windows only) commonComponents

Essbase Integration Services 32bit Essbase Integration Services 64bit commonComponents productCommonComponents tools essbase_integration_services essbaseAddins

Required assemblies:
l l l

Required assemblies:
l

essbase_integration_services
l

essbaseAddins
l l l

Required download files:


l

Hyperion Enterprise Performance Management System Foundation Services Release 11.1. 1.3.0 Part 1 of 4 Oracle Essbase Client Release 11.1.1.3.0 Oracle Essbase Server Release 11.1.1.3.0

Required download files:


l

Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 1 of 4 Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 2 of 4 Oracle Essbase Client Release 11. 1.1.3.0 Oracle Essbase Server Release 11. 1.1.3.0

30

Preparing for Installation

Client Tier Oracle Hyperion Provider Services

Web Tier

Services Tier

Component:
l

Provider Services Web Application commonComponents productCommonComponents tools analytic_services_provider_webapp essbaseAddins

Required assemblies:
l l l l l

Required download files:


l

Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 1 of 4 Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 2 of 4 Oracle Hyperion Provider Services Release 11.1.1.3.0 Oracle Essbase Client Release 11.1.1.3.0

Component Installation By Tier and Installation Assemblies

31

Client Tier Oracle Essbase Studio Component: Essbase Studio Client (Windows only) Required assemblies: commonComponents

Web Tier

Services Tier

Component: Essbase Studio Server Required assemblies:


l

commonComponents productCommonComponents tools essbase_studio_services essbaseAddins

l l l

essbase_studio
l

essbaseAddins
l l

Required download files:


l

Hyperion Enterprise Performance Management System Foundation Services Release 11.1. 1.3.0 Part 1 of 4 Oracle Essbase Client Release 11.1.1.3.0

Required download files:


l

Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 1 of 4 Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 2 of 4 Oracle Essbase Client Release 11. 1.1.3.0 Oracle Essbase Server Release 11. 1.1.3.0

32

Preparing for Installation

Client Tier

Web Tier

Services Tier

Oracle Hyperion Smart Search Command Line Utility Component: Smart Search Command Line Utility Web Application Required assemblies:
l l l l

commonComponents productCommonComponents tools essbase_smartsearch_ webapp essbaseAddins

Required download files:


l

Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 1 of 4 Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 2 of 4 Oracle Essbase Client Release 11.1.1.3.0 Oracle Essbase Server Release 11.1.1.3.0

Smart View Component: Smart View with Oracle Essbase Visual Explorer Client (Windows only) Required assemblies:
l l

commonComponents svchve_client

Required download files:


l

Hyperion Enterprise Performance Management System Foundation Services Release 11.1. 1.3.0 Part 1 of 4 Oracle Essbase Client Release 11.1.1.3.0

Component Installation By Tier and Installation Assemblies

33

Reporting and Analysis


The following table describes the components installed on each tier for Reporting and Analysis products and the ZIP files and installation assemblies required to install that component.
Note: The commonComponents assembly is required for all products. The tools and productCommonComponents assemblies are required for all server and Web applications. These assemblies are in Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 1 of 4 and Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 2 of 4.

Client Tier Oracle's Hyperion Interactive Reporting Component:


l

Web Tier

Services Tier

Component:
l

Interactive Reporting Studio Client (Windows only) Interactive Reporting Dashboard Development Services (Windows only) commonComponents productCommonComponents (Interactive Reporting Dashboard Development Services only) biplus_interactive_reporting_client biplus_dds essbaseProductCommonComponents

Interactive Reporting Services commonComponents productCommonComponents tools biplus_interactive_reporting_services biplus_core_services biplus_configlibs

Required assemblies:
l l l l l l

Required assemblies:
l l

l l l

Required download files:


l

Required download files:


l

Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 1 of 4 Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 2 of 4 Hyperion Interactive Reporting Release 11.1.1.3.0

Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 1 of 4 Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 2 of 4 Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 3 of 4 Hyperion Interactive Reporting Release 11.1.1.3.0

34

Preparing for Installation

Client Tier Financial Reporting Component: Financial Reporting Studio Client (Windows only) Required assemblies: commonComponents

Web Tier

Services Tier

Component: Financial Reporting Web Application Required assemblies:


l

Component:
l

Financial Reporting Reports Server Service Financial Reporting Print Server Service (Windows only) Financial Reporting Scheduler Server Service commonComponents productCommonComponents tools biplus_financial_reporting_services biplus_configlibs biplus_financial_reporting_common essbaseProductCommonComponents hfm_client, if you are using Financial Reporting with Financial Management hfm_common, required for Financial Management components

commonComponents productCommonComponents tools biplus_financial_reporting_webapp biplus_configlibs biplus_financial_reporting_common essbaseProductCommonComponents hfm_client, if you are using Financial Reporting with Financial Management hfm_common, required for Financial Management components

l l l l l l l

productCommonComponents
l

biplus_financial_reporting_client
l

biplus_configlibs
l

Required assemblies:
l l l l l

biplus_financial_reporting_common
l

essbaseProductCommonComponents
l

hfm_client, if you are using Financial Reporting with Oracle Hyperion Financial Management, Fusion Edition hfm_common, required for Financial Management components

l l

Required download files:


l

Required download files:


l

Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 1 of 4
l

Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 1 of 4 Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 2 of 4 Oracle Hyperion Financial Reporting, Fusion Edition Release 11.1.1.3.0 Oracle Hyperion Financial Management, Fusion Edition Release 11.1.1.3.0

Required download files:


l

Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 2 of 4
l

Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 1 of 4 Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 2 of 4 Oracle Hyperion Financial Reporting, Fusion Edition Release 11.1.1.3.0 Oracle Hyperion Financial Management, Fusion Edition Release 11.1.1.3.0

Oracle Hyperion Financial Reporting, Fusion Edition Release 11.1.1.3.0


l

Oracle Hyperion Financial Management, Fusion Edition Release 11.1.1.3.0

Component Installation By Tier and Installation Assemblies

35

Client Tier Production Reporting Component: (All components on client tier are Windows only)
l l l l

Web Tier

Services Tier

Component:
l l

SQR Production Reporting DB2 Engine SQR Production Reporting DDO Engine SQR Production Reporting Informix Engine SQR Production Reporting ODBC Engine SQR Production Reporting Oracle Engine SQR Production Reporting Sybase Engine SQR Production Reporting Teradata Engine (UNIX only) commonComponents productCommonComponents tools biplus_product_reporting_services biplus_product_reporting_common essbaseProductCommonComponents

SQR Production Reporting Studio


l

SQR Production Reporting Activator SQR Production Reporting Remote SQR Production Reporting Viewer commonComponents biplus_product_reporting_client biplus_product_reporting_common
l l l l

Required assemblies:
l l l

Required assemblies:
l l l l l l

Required download files:


l

Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 1 of 4 Hyperion SQR Production Reporting Release 11.1.1.3.0

Required download files:


l

Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 1 of 4 Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 2 of 4 Hyperion SQR Production Reporting Release 11.1.1.3.0

36

Preparing for Installation

Client Tier Web Analysis

Web Tier

Services Tier

Component: Web Analysis Web Application Required assemblies:


l l l l l l l

commonComponents productCommonComponents tools biplus_webanalysis_webapp biplus_configlibs essbaseProductCommonComponents hfm_client, if you are using Web Analysis with Financial Management hfm_common, required for Financial Management components

Required download files:


l

Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 1 of 4 Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 2 of 4 Hyperion Web Analysis Release 11.1.1.3.0 Oracle Hyperion Financial Management, Fusion Edition Release 11.1.1.3.0

Financial Performance Management Applications


The following table describes the components installed on each tier for Financial Performance Management Applications products and the ZIP files and installation assemblies required to install that component.
Note: The commonComponents assembly is required for all products. The tools and productCommonComponents assemblies are required for all server and Web applications. These assemblies are in Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 1 of 4 and Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 2 of 4.

Component Installation By Tier and Installation Assemblies

37

Client Tier Planning Component:


l

Web Tier

Services Tier

Component: Planning Web Application Required assemblies:


l l l l

Planning Off-line Client commonComponents offlinePlanning

Required assemblies:
l l

commonComponents planning productCommonComponents tools rmi essbaseProductCommonComponents essbase_services

Required download files:


l

Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 1 of 4 Oracle Hyperion Planning, Fusion Edition Release 11.1. 1.3.0

l l l

Required download files:


l

Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 1 of 4 Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 2 of 4 Oracle Hyperion Planning, Fusion Edition Release 11.1. 1.3.0 Oracle Essbase Server Release 11.1.1.3.0

38

Preparing for Installation

Client Tier

Web Tier

Services Tier

Financial Management (All components are Windows only) Component:


l l

Component:
l l

Component:
l

Financial Management Client Financial Management Sample Applications Financial Management ADM Driver commonComponents hfm_client hfm_common

Financial Management Web Applications Financial Management Smart View Provider commonComponents productCommonComponents tools hfm_webapp hfm_common

Financial Management Application Server commonComponents productCommonComponents tools hfm_services hfm_common

Required assemblies:
l l l l l

Required assemblies:
l l l l l

Required assemblies:
l l l

Required download files:


l

Required download files:


l

Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 1 of 4 Oracle Hyperion Financial Management, Fusion Edition Release 11.1.1.3.0

Required download files:


l

Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 1 of 4 Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 2 of 4 Oracle Hyperion Financial Management, Fusion Edition Release 11.1.1.3.0

Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 1 of 4 Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 2 of 4 Oracle Hyperion Financial Management, Fusion Edition Release 11.1.1.3.0

Component Installation By Tier and Installation Assemblies

39

Client Tier

Web Tier

Services Tier

Oracle Hyperion Performance Scorecard, Fusion Edition Component:


l

Performance Scorecard Web Reports Web Application Performance Scorecard Alerter Web Application Performance Scorecard ETL Web Application commonComponents productCommonComponents tools hps_webapp essbaseProductCommonComponents

Required assemblies:
l l l l l

Required download files:


l

Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 1 of 4 Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 2 of 4 Oracle Hyperion Performance Scorecard, Fusion Edition Release 11.1.1.3.0

40

Preparing for Installation

Client Tier

Web Tier

Services Tier

Strategic Finance (All components are Windows only) Component:


l l l

Component:
l

Component:
l l

Strategic Finance Client Strategic Finance Reader Client Strategic Finance Integration with Financial Management (Client)1 Strategic Finance Integration with Enterprise (Client)2 commonComponents productCommonComponents (Strategic Finance Integration with Financial Management only) tools (Strategic Finance Integration with Financial Management only) hsf_client hsf_reader_client essbaseProductCommonComponents (Strategic Finance Client and Strategic Finance Integration with Financial Management only)

Strategic Finance Web Services commonComponents productCommonComponents tools hsf_server

Strategic Finance Service Strategic Finance Integration with Financial Management (Service)3 Strategic Finance Integration with Enterprise (Service)4

Required assemblies:
l l

l l

Required assemblies:
l l

Required download files:


l

Note: Strategic Finance integration with Essbase and Planning is automatically installed. Required assemblies:
l l l l

Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 1 of 4 Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 2 of 4 Oracle Hyperion Strategic Finance, Fusion Edition Release 11.1.1.3.0

commonComponents productCommonComponents tools hsf_server essbaseProductCommonComponents (required only for Strategic Finance Service and Strategic Finance Integration with Financial Management Services)

l l l

Required download files:


l

Required download files:


l

Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 1 of 4
l

Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 1 of 4 Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 2 of 4 Oracle Hyperion Strategic Finance, Fusion Edition Release 11.1.1.3.0

Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 2 of 4
l

Oracle Hyperion Strategic Finance, Fusion Edition Release 11.1.1.3.0

Component Installation By Tier and Installation Assemblies

41

Client Tier

Web Tier

Services Tier

Oracle Hyperion Profitability and Cost Management, Fusion Edition Component: Profitability Web Application Required assemblies:
l l l l l

commonComponents productCommonComponents tools hpm essbaseProductCommonComponents

Required download files:


l

Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 1 of 4 Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 2 of 4 Oracle Hyperion Profitability and Cost Management, Fusion Edition Release 11.1.1.3.0

1You 2You

must also install the Financial Management client. must first install the Enterprise client. 3You must also install the Financial Management client. 4You must first install the Enterprise client.

Data Management
The following table describes the components installed on each tier for Data Management products and the ZIP files and installation assemblies required to install that component.
Note: The commonComponents assembly is required for all products. The tools and productCommonComponents assemblies are required for all server and Web applications. These assemblies are in Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 1 of 4 and Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 2 of 4.

42

Preparing for Installation

Client Tier

Web Tier

Services Tier

Oracle Hyperion Financial Data Quality Management, Fusion Edition (All components are Windows only) Component: FDM Workbench Client Required assemblies:
l l l

Component: FDM Web Application Required assemblies:


l l l l

Component:
l l l

FDM Load Balancer FDM Task Manager FDM Server commonComponents productCommonComponents tools fdm

commonComponents productCommonComponents fdm

commonComponents productCommonComponents tools fdm

Required assemblies:
l l l

Required download files:


l

Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1. 3.0 Part 1 of 4 Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1. 3.0 Part 2 of 4 Oracle Hyperion Financial Data Quality Management, Fusion Edition Release 11.1.1. 3.0

Required download files:


l l

Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 1 of 4 Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 2 of 4

Required download files:


l

Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 1 of 4 Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 2 of 4 Oracle Hyperion Financial Data Quality Management, Fusion Edition Release 11. 1.1.3.0

l l

Oracle Hyperion Financial Data Quality Management, Fusion Edition Release 11.1.1.3.0

For any adapters you are licensed to use, download the required adapters:
l

Oracle Hyperion Financial Data Quality Management Adapter Suite, Fusion Edition Release 11.1.1.3.0 Oracle Hyperion Financial Data Quality Management Source Adapter for SAP Release 11.1.1.3.0 Oracle Hyperion Financial Data Quality Management Adapter for Financial Management, Fusion Edition

Component Installation By Tier and Installation Assemblies

43

Client Tier

Web Tier

Services Tier

Oracle Hyperion Financial Data Quality Management ERP Integration Adapter for Oracle Applications Component: Performance Manager Integrator Web Application Required assemblies:
l l l l l

commonComponents productCommonComponents tools aif essbaseProductCommonComponents

Required download files:


l

Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 1 of 4 Hyperion Enterprise Performance Management System Foundation Services Release 11.1.1.3.0 Part 2 of 4 Oracle Hyperion Financial Data Quality Management ERP Integration Adapter for Oracle Applications Release 11.1.1.3.0

Download File Contents


The following table describes the contents of each download file on E-Delivery. Use this table to help plan your EPM System installation, if necessary.
Tip: To see the ZIP file name for each download file, see E-Delivery.

Table 3

Download File Contents Assemblies


l l

ZIP File Name Oracle Hyperion Provider Services Release 11.1.1.3.0

analytic_provider_services_webapp essbaseAddins hpm

Oracle Hyperion Profitability and Cost Management, Fusion Edition Release 11.1.1.3.0

44

Preparing for Installation

ZIP File Name Oracle Hyperion Enterprise Performance Management Architect, Fusion Edition Release 11.1.1.3.0

Assemblies
l l l l l

bpm_architect_batch_client bpm_architect_datasync bpm_architect_generator bpm_architect_services bpm_architect_webapp biplus_configlibs biplus_financial_reporting_client biplus_financial_reporting_common biplus_financial_reporting_services biplus_financial_reporting_webapp commonComponents essbaseProductCommonComponents productCommonComponents tools biplus_core_services biplus_migration_utility biplus_portlets_webapp biplus_workspace_webapp workspace_configlibs calc sharedServices svc_client biplus_configlibs biplus_dds biplus_interactive_reporting_client biplus_interactive_reporting_services N/A. Contains EPM System Installer essbase_administration_services_client essbase_client essbase_studio essbaseAddins svchve_client

Oracle Hyperion Financial Reporting, Fusion Edition Release 11.1.1.3.0

l l l l l

Hyperion Enterprise Performance Management System Foundation Services Release 11. 1.1.3.0 Part 1 of 4 Hyperion Enterprise Performance Management System Foundation Services Release 11. 1.1.3.0 Part 2 of 4

l l l

Hyperion Enterprise Performance Management System Foundation Services Release 11. 1.1.3.0 Part 3 of 4

l l l l l l

Hyperion Enterprise Performance Management System Foundation Services Release 11. 1.1.3.0 Part 4 of 4 Hyperion Interactive Reporting Release 11.1.1.3.0

l l

l l l l

Oracle Hyperion Enterprise Performance Management System Installer, Fusion Edition Release 11.1.1.3.0 Oracle Essbase Client Release 11.1.1.3.0

l l l l l

Component Installation By Tier and Installation Assemblies

45

ZIP File Name Oracle Essbase Server Release 11.1.1.3.0

Assemblies
l l l l l l

essbase_administration_services_webapp essbase_integration_services essbase_services essbase_smartsearch_webapp essbase_studio_services essbaseAddins fdm N/A N/A N/A aif hfm_client hfm_common hfm_services hfm_webapp hps_webapp hsf_client hsf_reader_client hsf_server offlinePlanning planning rmi biplus_product_reporting_client biplus_product_reporting_common biplus_product_reporting_services N/A. Contains Smart View installer. biplus_configlibs biplus_webanalysis_webapp

Oracle Hyperion Financial Data Quality Management, Fusion Edition Release 11.1.1.3. 0 Oracle Hyperion Financial Data Quality Management Adapter Suite, Fusion Edition Release 11.1.1.3.0 Oracle Hyperion Financial Data Quality Management Source Adapter for SAP Release 11.1.1.3.0 Oracle Hyperion Financial Data Quality Management Adapter for Financial Management, Fusion Edition Oracle Hyperion Financial Data Quality Management ERP Integration Adapter for Oracle Applications Release 11.1.1.3.0 Oracle Hyperion Financial Management, Fusion Edition Release 11.1.1.3.0

l l l l

Oracle Hyperion Performance Scorecard, Fusion Edition Release 11.1.1.3.0 Oracle Hyperion Strategic Finance, Fusion Edition Release 11.1.1.3.0

l l l

Oracle Hyperion Planning, Fusion Edition Release 11.1.1.3.0

l l l

Hyperion SQR Production Reporting Release 11.1.1.3.0

l l l

Oracle Hyperion Smart View for Office, Fusion Edition Release 11.1.1.3.0 Hyperion Web Analysis Release 11.1.1.3.0

l l

46

Preparing for Installation

3
In This Chapter

Installing EPM System Products

Installation Sequence .....................................................................................47 Characters Supported for Installation and Configuration...............................................49 Installing EPM System Products ..........................................................................49 Performing Silent Installations ............................................................................60 Installing Additional Instances of Essbase Server ......................................................62

Installation Sequence
EPM System Installer enables you to install, configure, and deploy multiple products on a machine at one time. EPM System Installer installs components in the correct order, so you can select as many products as you want to install on a machine at one time. Before installing products, see Installation Planning Checklist in Oracle Hyperion Enterprise Performance Management System Installation Start Here and review the system requirements in the Oracle Hyperion Enterprise Performance Management System Certification Matrix (http:// www.oracle.com/technology/products/bi/hyperion-supported-platforms.html). Review the Media Pack Readme on Oracle E-Delivery to see which products are required or optional for use with your products. You can also install Smart View from a standalone executable. See Oracle Hyperion Smart View for Office User's Guide and the Oracle Hyperion Smart View for Office Readme.
Note: If you want to install Essbase in standalone mode (not using Shared Services), you can

skip the installation for Shared Services. However, you must configure the Oracle's Hyperion Shared Services Registry database. To configure the Shared Services Registry database without installing Shared Services, see Setting Up the Shared Services Registry Without Installing Shared Services on page 109. The following EPM System products are not installed and configured using EPM System Installer:
l

Oracle's Hyperion Data Integration Management If you are installing Data Integration Management, see the Hyperion Data Integration Management Installation Guide.

Installation Sequence

47

Data Integration Management Adapters. If you are installing Data Integration Management Adapters, see the Hyperion Data Integration Management Installation Guide.

Oracle Hyperion Data Relationship Management, Fusion Edition If you are installing Data Relationship Management, see the Oracle Hyperion Data Relationship Management Installation Guide.

Installation Prerequisites
Note the following installation prerequisites.
l

If you are applying the maintenance release to move from EPM System release 11.1.1.0, 11.1.1.1, or 11.1.1.2 to EPM System Release 11.1.1.3, or if you are reinstalling EPM System products, you must first stop all the services for EPM System products. If you plan to install the Strategic Finance Integration with Enterprise, you must install the Enterprise client first. If you plan to use SSL in a UNIX environment, before you install and configure EPM System, download and install the Apache 2.2.8 binaries that support SSL. During EPM Workspace configuration, select the SSL-capable Apache installation instead of the default EPM System installation. See Configure EPM Workspace Web Server on page 89. If you are using Planning in a Redhat or Oracle Enterprise Linux environment and you are using Simplified Chinese, you must specify LANG=zh_CN.GB18030 (instead of LANG=zh_CN.utf8) in one of two ways:
m

In the OS system locale variable (if you have not already set it) before you install and configure Planning In setCustomParamsHyperionPlanning.sh after you install and configure Planning

Upgrade Installation Prerequisites


If you are upgrading from a previous release, note the following installation prerequisites.
l

Uninstall FDM, and then reboot the machine. If your installation of Integration Services is earlier than Release 9.3, you must manually uninstall that release before using EPM System Installer to install Release 11.1.1.x. If the Windows service for Integration Services does not work after you install Release 11.1.1.x, reboot the machine on which the Integration Services service is running.

Stop all the services for EPM System products. If you are upgrading Performance Management Architect, see Performance Management Architect Upgrade Installation Prerequisites on page 49. Note that ERP Integrator does not support Oracle Application Server. Also note that all products that are accessible from EPM Workspace must be deployed to the same Web

48

Installing EPM System Products

application server to which EPM Workspace is deployed. Thus, if your previous EPM System deployment used Oracle Application Server, and you want to install ERP Integrator, you must redeploy your existing installation to a commonly-supported Web application server (Oracle WebLogic Server).

Performance Management Architect Upgrade Installation Prerequisites


Before you upgrade Performance Management Architect, perform the following tasks:
1 2
Perform a database backup. Allow enough space for the database to double in size.
Note: If the upgrade is unsuccessful, there may be inconsistencies and you must begin the

upgrade process again using the database backup.

Characters Supported for Installation and Configuration


The following characters are supported during installation and configuration with EPM System Installer and EPM System Configurator.
Table 4

Characters Supported for Installation and Configuration Supported Characters Alphanumeric, dash (-), underscores (_), periods ( . ), and tildes (~). Tildes are supported only on Microsoft Windows. Alphanumeric, dash (-), and dot(.), Alphanumeric characters including non-English (extended and double-byte) characters, except for the blocked characters Alphanumeric characters including non-English (extended and double-byte) characters, except for the blocked characters Blocked Characters All others

Fields PATH

Host name User name

All others +.*/#[]{}();:,@!

Clusters, database names, and other general fields such as DSN names

+.-*\/#[]{}();:,@!

Installing EPM System Products


You can install EPM System products in any of the following ways: using the graphical user interface, using the console mode interface, or with no interaction using a silent mode installation response file. When you install EPM System products, you choose which type of installation to perform:
l

New installation
Characters Supported for Installation and Configuration

49

Upgrade from a previous release Apply maintenance release Re-install this release

For each type of installation, you can choose whether to install EPM System products by tier or by individual component. Select Choose components by tier to install all the product components for the selected products by tier (Client, Web application, and Services). You still have the option to specify installation location and the products to install. If you want more control over which services and components are installed for each product component, select Choose components individually. Oracle recommends that you install EPM System products by tier. See Appendix A, What Happens During Installation.
Note: On Windows machines, run EPM System Installer and EPM System Configurator as an

administrator. Install and configure as the same user for all EPM System products.
Note: On UNIX machines, do not use the root user to install and configure. Install and

configure as the same user for all EPM System products. If you are using Oracle Application Server, you must install and configure EPM System products using the same user you used to install Oracle Application Server. If you have installed any other Oracle products, the user that will be installing EPM System products must be part of the same group as the user who installed the other Oracle products. For example, both users must be part of oinstall. If you are upgrading EPM System products, follow this requirement even if you used multiple users to install components in previous releases. Upgrade Note! If you are upgrading from a previous release, stop all services related to the products you are installing before you install. Use EPM System Installer and EPM System Configurator to upgrade products on each machine in your deployment.

To install EPM System products:


1
Choose a method:
l

(Windows) Double-click installTool.cmd in the root directory to which you extracted the EPM System Installer files. (Windows) From a Windows console, change to the root directory to which you extracted the EPM System Installer files and enter installTool.cmd -console. Create a silent installation response file. See Performing Silent Installations on page 60. (UNIX) Change to the root directory to which you extracted the EPM System Installer files and type ./installTool.sh. (UNIX) Change to the root directory to which you extracted the EPM System Installer files and type ./installTool.sh -console.

50

Installing EPM System Products

EPM System Installer launches.


Tip: The first page of EPM System Installer might open hidden behind other windows if

you navigate away from the EPM System Installer window or try to reposition the initial window. Press Alt+Tab to switch to the first page of the wizard.

Select a language.

Throughout EPM System Installer, if a component is not available for installation in the language you selected, it is shaded in color and marked with an asterisk (*).

Review and complete each page of EPM System Installer, clicking or selecting Next to move to the next page.

The following table provides links where you can find more details about each page of EPM System Installer.
Table 5

EPM System Installer Pages Reference Welcome on page 52 Destination on page 52 Installation Type on page 53 Product Selection on page 54 Upgrade Homes on page 57 Confirmation on page 58 Progress on page 59 Summary on page 59

Page Welcome Destination Installation Type Product Selection Upgrade Homes Confirmation Progress Summary

When installation is complete, click Configure to configure the products using EPM System Configurator, or click Finish to close EPM System Installer.

For more information about configuring Hyperion products, see Chapter 4, Configuring EPM System Products. After you install and configure the products, start the services as described in Chapter 5, Starting and Stopping EPM System Products. You can then use EPM System Diagnostics to validate that the installation was successful and that the components are communicating. See Chapter 6, Validating the Installation.

Installing EPM System Products

51

Welcome
Review the prerequisites carefully before you continue the installation. When you have
confirmed that your system meets the prerequisites to run EPM System Installer, click Next to continue the installation. EPM System Installer checks whether your system has a supported operating system and meets minimum memory requirements to run the installation, and whether the user installing has administrator privileges. EPM System Installer also attempts to discover the computer host name. Depending on how the computer is configured, the computer host name might resolve to an IP address. If the machine host name resolves to an IP address, EPM System Installer provides a warning. Oracle recommends that you resolve this issue and provide a host name instead of an IP address before proceeding. A check mark indicates that your system meets EPM System Installer prerequisites. If any of the prerequisite items do not display a check mark, and you choose to continue, the installation might not succeed.
Tip: If you are using a hosts file to resolve your hostname, the host name resolves to the first entry in your hosts file. To prevent potential communication problems in a distributed environment, make sure that the first entry in your hosts file is the machine's fully qualified

domain name so that the fully qualified name is stored in the Shared Services Registry.

Destination
Specify the destination for the installation location, or browse to a location and select it, and
then click Next. If you are reinstalling EPM System products on this machine, adding products to your installation, or applying the maintenance release, the existing location for the Hyperion home directory is listed as the default installation destination, and you cannot change it.
Caution!

The destination path cannot contain spaces; for example, c:\Program Files is not acceptable (unless you use short path notation).

The destination you specify becomes the Hyperion home directory. See About the Hyperion Home Directory on page 16. Ensure that this destination has enough disk space to install all the products that you want to install on this machine. You select an installation destination and Hyperion home directory for each machine in your environment. See Oracle Hyperion Enterprise Performance Management System Installation Start Here for disk space requirements.

52

Installing EPM System Products

Note: If you previously used EPM System Installer, and you saved the installation selections to

a file, you can load the selections to prepopulate the installation destination and the products to install. Doing so is useful if you are installing the same products on multiple machines. Click Load, browse to the saved selections file, and click Open. Upgrade Note! If you are upgrading EPM System products on this machine, the existing location for the Hyperion home directory is listed as the default installation destination, and you cannot change it.

Installation Type
Select an installation type, and then click Next. If an installation type is not applicable on
this machine, the option is unavailable. Choose from the following installation types:
l

New installation Choose this option if you are installing an EPM System product for the first time on this computer, or if you are installing an additional instance of Essbase Server. When you install an additional instance of Essbase Server, the Essbase installation directory is appended with n for subsequent installations. See Installing Additional Instances of Essbase Server on page 62. Choose this option if you want to install additional components that you did not initially install. If the New Installation option is not available, your machine might have an improperly deleted previous version of EPM System products. Search for and rename vpd.properties (usually in the /windows directory for Windows or $HOME for UNIX) on the machine. For additional troubleshooting tips, see Oracle Hyperion Enterprise Performance Management System Installation and Configuration Troubleshooting Guide.

Upgrade from a previous release Choose this option if you have a previous version of this EPM System product installed. If you are upgrading, you must first stop all EPM System services. See Upgrade Installation Prerequisites on page 48.

Apply maintenance release Choose this option if you already installed release 11.1.1.x. This release provides a maintenance release for release 11.1.1.x. If you are applying the maintenance release, you must first stop all EPM System services.

Installing EPM System Products

53

If you are applying the maintenance release to only some products in your deployment, see Release Compatibility in the Oracle Hyperion Enterprise Performance Management System Installation Start Here.
l

Re-install this release Choose this option if you already installed this version of this EPM System product and want to reinstall it, for example if you need to repair an existing installation. If you are reinstalling EPM System products, you must first stop all EPM System services. If you installed multiple instances of Essbase Server, you can reinstall only the first instance. If you need to reinstall a subsequent instance of Essbase Server, you must first uninstall it.

Note: You cannot combine installation types in one session. For example, you cannot perform

a new installation of one product at the same time you perform a reinstallation of another product. For each type of installation, you can choose one of the following options:
l

Select Choose Components By Tier if you want to install all the components, by tier, for the selected products. You still have the option to specify installation location and the products to install. This is the simplest path, and is recommended unless you want to customize the installation. If multiple instances of Essbase are installed, you can only reinstall the first instance. Select Choose Components Individually if you want more control over which services and components are installed for each product component.

See Appendix A, What Happens During Installation for more information about what is installed for each type of installation. Some components are available only if you select Choose Components Individually. Upgrade Note! If you are upgrading existing EPM System products on a machine and the option to Upgrade from a previous release is not available, create an override file. See Oracle Hyperion Enterprise Performance Management System Installation and Configuration Troubleshooting Guide.

Product Selection
If you selected Choose Components By Tier, select the tier or tiers, products, and components
to install, and then click Next. If you selected Choose Components Individually, select the products and product components to install, and then click Next. For information about what is installed on each tier, see Component Installation By Tier and Installation Assemblies on page 20.

54

Installing EPM System Products

Generally, you can install any combination of components on any computer. Note the following about product selection:
l

Products are available for installation only if the assemblies are downloaded to the correct location and the selected component is supported on the platform on which you are installing. If a product is unavailable on the Product Selection page, ensure that the assemblies are in the correct location. See Chapter 2, Preparing for Installation. For Troubleshooting tips, see Oracle Hyperion Enterprise Performance Management System Installation and Configuration Troubleshooting Guide Select a product component to see information and status about it in the lower portion of the screen. If Microsoft Internet Information Server (IIS) is required for your installation, and it is not installed, a warning is noted in the lower portion of the screen, and you cannot proceed until you install IIS. If you are installing on an unsupported platform, a warning is displayed. You can install only Smart View Client or Smart View with Visual Explorer Client, not both, at the same time. If you selected New Installation, and you have already installed this release of a product, the product is unavailable in the Product Selection page, except for Essbase. (You can install multiple instances of Essbase. See Installing Additional Instances of Essbase Server on page 62.) In some cases, a component is selected, but is unavailable (you can't deselect it), because it is required for another selected component. You cannot install 32-bit components on a 64-bit system on which 64-bit components are already installed. You must install the 32-bit components on another system or install all of the 32-bit components on a 32-bit system. Specifically FDM (32-bit) and Strategic Finance (32-bit) cannot be deployed on the same computer where Financial Management (64-bit) and Performance Management Architect (64-bit) are deployed. On 32-bit platforms, all EPM System products can co-exist.

Upgrade Note!
l

If you selected Upgrade From a Previous Release, and you have already installed or upgraded to this release of a product, that product is unavailable in the Product Selection page. If you selected Upgrade From a Previous Release, the Product Selection page displays the version number next to a previous release of a product that you are upgrading, or displays Unknown if EPM System Configurator cannot determine the version number. If your product is deployed with Foundation Services, you must upgrade all Foundation Services products. You must upgrade all Reporting and Analysis products, if applicable to your deployment. For client tier components of Performance Management Architect, you must choose New Installation, even if you are upgrading from a previous release of Performance Management Architect. The client components were not available in previous releases, so they are not available when you choose Upgrade From a Previous Release.

Installing EPM System Products

55

You cannot upgrade from a 32bit version of a product to a 64bit version of the same product. To install the 64bit version of the product, you must select New Installation.
Choose Components By Tier

Figure 1

The following table describes the options if you select Choose Components by Tier.
Table 6

Choose Components By Tier Installation Options Details EPM System Installer automatically selects all product components available for installation on the selected tier. Components are available for installation if you downloaded the installation assemblies and extracted them to the proper /assemblies directory. The EPM System Installer automatically selects any required components for the selected product. You can choose to install all the products you want on a particular machine at one time. EPM System Installer installs them in the correct order. EPM System Installer prompts you if a dependent component must be selected. Note: A component with a version number or Re-install next to it indicates that it has already been installed. Select a different installation type to install the component (reinstall or upgrade). Tip: Click a cell to see a description of your selection in the box at the bottom of the window.

Action To install by tier, select the deployment tier to install Client, Web app, or Services. Clear any products that you do not want to install for the selected tier.

Clear the deployment tiers that you do not want to install on this machine. Hide/Show unavailable products.

When you deselect a tier, EPM System Installer deselects all products and components for that tier.

To see only products for which installation assemblies are available, select Hide Unavailable Products. To see all products, select Show Unavailable Products.

56

Installing EPM System Products

Figure 2

Choose Components Individually

The following table describes the options if you select Choose Components Individually.
Table 7

Choose Components Individually Installation Options Details You can expand and collapse the entries to select or clear specific options for each product and component. Select Check all to select all the products, or Uncheck all to clear all the products. To see only products for which installation assemblies are available, select Hide Unavailable Products. To see all products, select Show Unavailable Products.

Action Select the products and product components to install. Uncheck all / Check all Hide/Show unavailable products.

If you are installing additional instances of Essbase, see Installing Additional Instances of Essbase Server on page 62.

Upgrade Homes
This page is displayed only if you are upgrading from a previous release. If you are not upgrading, skip this section. Upgrade Note!

If you selected Upgrade from a previous release:


1
Review the existing installation locations of the previous release for each product that you are upgrading. Make a change if necessary by clicking the Browse button and navigating to the installation location you want.

For Reporting and Analysis, the product home can be a comma-separated list.

Installing EPM System Products

57

EPM System Installer finds information about previous releases from the vpd.properties file. (For FDM and Smart View, EPM System Installer finds this information in the Windows registry instead.)

Specify whether you want EPM System Installer to uninstall previous releases of the software. Selecting this option removes previous versions of the software but retains data and configuration files. It also removes Start menu items from the previous release. Oracle recommends that you select this option.

If you are upgrading multiple instances of Essbase on one machine, only one instance is shown in the Upgrade Homes page. To upgrade a different instance, click Browse for the Essbase product home and browse to the Essbase instance that you want to upgrade. To upgrade more than one Essbase instance, run EPM System Installer multiple times, selecting a different Essbase product home each time.
Figure 3 Upgrade Homes

Confirmation
Review the summary of products to be installed. If necessary, click Back and make
corrections. Click Next to begin the installation. EPM System Installer warns you if there is insufficient disk space. The Install Type column notes one of the following:
l

Install if this is a new installation. Upgrade if this installation is an upgrade from a previous release of EPM System products. Re-install if this is a reinstallation of the same release of this EPM System product.

58

Installing EPM System Products

Maintenance if this is a maintenance installation to move from EPM System products Release 11.1.1.0, 11.1.1.1, or 11.1.1.2 to Release 11.1.1.3.

To save your installation selections to perform the same installation on another computer, or to use as the basis for a response file for silent installation, see Saving Installation Selections on page 59.

Saving Installation Selections


If you plan to install this same set of components to the same named Hyperion home directory location on another computer, you can save the installation selections in a file. You can then load the selections on another computer during installation to prepopulate EPM System Installer pages for Destination and Product Selection.

To save the installation selections, click Save, browse to a location, specify a file name, and
click Save. This procedure creates an editable file that can be used as the basis for a response file for silent installation. For information about using a response file, see Loading Saved Selections on page 61.

Progress
To cancel the installation, click Cancel.
EPM System Installer starts to display the progress indicator after it has prepared the list of assemblies to install. This might take several minutes, depending on how many products you selected. EPM System Installer displays progress incrementally as each assembly's installation is complete. When you click Cancel, EPM System Installer waits until the current assembly completes installing and then stops. It does not undo installations for assemblies that were already installed. Use EPM System Uninstaller to remove assemblies that were installed. See Chapter 11, Uninstalling EPM System.
Note: Creating Oracle Inventory sets up infrastructure for future service fixes.

Summary
Review the installation summary, and then click Configure to launch EPM System
Configurator or click Finish to close EPM System Installer. EPM System Installer indicates the success or failure of the installation. If any part of the installation failed, EPM System Installer notes which assembly failed to install. Check the log files for more information about the errors. You can find the log files in HYPERION_HOME/
Installing EPM System Products

59

logs/install. There is a log file for each assembly, named product-install.log; for example, hss-install.log, and a log file for installation, installTool-install.log.

For more information about configuring EPM System products, see Chapter 4, Configuring EPM System Products. After you install and configure the products, start the services as described in Chapter 5, Starting and Stopping EPM System Products. You can then use EPM System Diagnostics to validate that the installation was successful and that the components are communicating. See Chapter 6, Validating the Installation.

Performing Silent Installations


Silent installations automate the installation process so that you can install EPM System products on multiple computers without manually specifying installation settings on each machine.
Note: You can also perform a silent installation if you are applying a maintenance release or if

you are upgrading. To enable silent installation, record your installation settings in a response file. You can then run a silent installation from the command line, using the installation options that were saved in the response file.

To record installation settings and run a silent installation:


1 2
Navigate to the directory that contains EPM System Installer. From a command line, run a command:
installTool.cmd -record filename

for Windows or
installTool.sh -record filename

for UNIX, where filename includes an absolute path or file name for the response file. The file is saved in XML format, but you do not have to save the file with a .xml extension. EPM System Installer launches.
Tip: The first page of EPM System Installer might open hidden behind other windows (if

you navigate away from the EPM System Installer window, or try to reposition the initial window). Press Alt+Tab to switch to the first page of the wizard.

Proceed through EPM System Installer, specifying the options that you want to record. For additional information about installation options, see Installing EPM System Products on page 49.

Installation options are recorded in the response file, which is in XML format. You can modify the response file later to change installation options.

60

Installing EPM System Products

You are now ready to run the installation in silent mode.

4 5

Copy the response file to the machine on which you want to run the installation. You can also copy the file to a network drive that is accessible from the machines on which you want to install. From the command line, enter a command:
installtool.cmd -silent filename

for Windows or
installtool.sh -silent filename

for UNIX. The installation runs in the background.


Note: Silent response files are not compatible between EPM System Release 11.1.1.0, Release

11.1.1.1, and 11.1.1.2. If you created silent response files for use with EPM System Release 11.1.1.0 or 11.1.1.1, you must re-create them for use with EPM System Release 11.1.1.2. If you are applying the maintenance release to go to Release 11.1.1.3, you need to re-create silent response files only if you are installing ERP Integrator.

Loading Saved Selections


You can also record installation settings from within EPM System Installer.

To record installation settings, during installation, on the Installation Confirmation page,


click Save, browse to a location, specify a file name, and click Save. The file is saved in the same format as for silent installations.

To play back the installation using the same installation destination and product component
selections, start EPM System Installer, and on the Destination page, click Load, browse to the saved selections file, and click Open.

Modifying Response Files


After you create a response file, you can modify it to customize the installation options for certain machines. For example, you might create a master silent file for all products, and then for each machine, change the location of the Hyperion home directory and keep only the product components you want to install on this machine.

To modify a response file:


1 2
Open the response file in any text editor. The file is in XML format. Edit the file using the following options.
l

<HyperionHome>Location of the Hyperion home directory.

Performing Silent Installations

61

<SelectedProducts>Product components to install to specific tiers. Make changes in <Product name>, <ProductComponent name>, <InstallTier>, and <Component>. <Product name>The name of the product. Enclose product names in quotes, as they

are XML attributes.


l

<ProductComponent name>The component of the product. Enclose component

names in quotes, because they are XML attributes.


l

<InstallTier>The installation tier for the component installation (Client, Service,

WebApplication).
l

<Component> The services to install.

Save the file in XML format.

Installing Additional Instances of Essbase Server


You can install multiple instances of Essbase Server on one computer. Additional instances are installed in the same Hyperion home directory and share the same Shared Services. Complete the installation and configuration of the first instance before you proceed. To install an additional instance of Essbase Server, choose New Installation in EPM System Installer. The destination directory for the installation is updated with n. For example, if the first instance of Essbase Server is installed in HYPERION_HOME/products/essbase, the second installation directory is HYPERION_HOME/products/essbase-2.
Note: The additional installation is a separate installation of Essbase Server and does not share

the security configuration or objects of other Essbase Server installations on the same computer. When multiple instances of Essbase Server are installed on one computer, you must specify a different port number and port range for each instance. By default, the first instance of Essbase Server uses port number 1423, which you specify in EPM System Configurator. Specify a different port number and port range for each additional instance during configuration with EPM System Configurator. See Configuring and Starting an Additional Instance of Essbase Server on page 96.

62

Installing EPM System Products

4
In This Chapter

Configuring EPM System Products

About EPM System Configurator..........................................................................63 Satisfying Initial Requirements ...........................................................................64 Configuration Sequence...................................................................................66 Product Configuration Task Summary ....................................................................69 Using EPM System Configurator ..........................................................................72 Performing Silent Configurations ....................................................................... 108 Setting Up the Shared Services Registry Without Installing Shared Services ...................... 109 What Happens During Configuration ................................................................... 110 Troubleshooting Configuration .......................................................................... 110

About EPM System Configurator


EPM System Configurator is installed with the first EPM System product installed on a computer and is used to configure all products installed on the computer. Use EPM System Configurator on each computer to which EPM System products are installed. (The Client tier does not require configuration.) EPM System Configurator provides these tasks for configuration and reconfiguration of EPM System products. Not all tasks are required for all products.
l

Configure Database for Shared Servicesthe database that you configure for Shared Services, which holds the Shared Services Registry. Common SettingsEPM System Configurator displays the Common Settings page once on each machine you configure. Configure Product OptionsTo comply with your license agreement, select the product features that you are authorized to use. Configure Database for productsTo store and retrieve application data in a database. Deploy to Application ServerTo deploy the application to a Web application server. Product-specific configuration tasks for products that require it.

Note: EPM System Configurator also registers products with Shared Services during

configuration. You do not need to select this task; all products that require it are automatically registered.

About EPM System Configurator

63

Use the configuration worksheets throughout this chapter to plan your configuration and to document the configuration steps for your company if required for disaster recovery. EPM System Configurator creates a preprovisioned user called admin that enables you to log on to Shared Services after configuration using admin/password to create and provision users. Oracle recommends that you change this password immediately in Oracle's Hyperion Shared Services Console.

About the Shared Services Registry


The Shared Services Registry is part of the database that you configure for Shared Services. Created the first time you configure EPM System products, the Shared Services Registry simplifies configuration by storing and re-using the following information for most EPM System products that you install:
l

Initial configuration values such as database settings and deployment settings The computer names, ports, servers, and URLs you use to implement multiple, integrated, Hyperion products and components Dependent service data

Configuration changes you make for one product are automatically applied to other products used in the deployment. You can view and manage the contents of the Shared Services Registry using Lifecycle Management in the Shared Services Console. See Oracle Hyperion Enterprise Performance Management System Lifecycle Management Guide. Upgrade Note! When you upgrade from a previous release of EPM System products, EPM System Configurator updates the Shared Services Registry for products that you upgrade. If you are not upgrading all of the EPM System products in your deployment, see Chapter 8, Upgrading EPM System Products for important information about editing the Shared Services Registry to enable use of mixed product releases.

Satisfying Initial Requirements


The following table describes the tasks to perform if you are using EPM System Configurator for the first time.
Table 8

Configuration Requirements Reference System requirements in the Oracle Hyperion Enterprise Performance Management System Certification Matrix (http://www.oracle.com/technology/products/bi/hyperion-supported-platforms.html) and Installation Planning Checklist in Oracle Hyperion Enterprise Performance Management System Installation Start Here

Task Satisfy system and product-specific requirements.

64

Configuring EPM System Products

Task Gather the information you need to configure products. Install a Java application server and a Web server if required for your product. Prepare a relational database to use for storage.

Reference Using EPM System Configurator on page 72

Application server documentation, and additional information in Oracle Hyperion Enterprise Performance Management System Installation Start Here

Relational database documentation, and additional information in Oracle Hyperion Enterprise Performance Management System Installation Start Here

Upgrade Configuration Prerequisites


Upgrade Note! Note the following prerequisites if you are upgrading.
l

If you are upgrading from a previous release, and you manually deployed EPM System products using Oracle Application Server, you must manually undeploy all products before you start EPM System Configurator. If you are upgrading Planning Release 9.2.x in a UNIX environment, copy the HspJSHome.properties and HBRServer.properties files from your current installation to HYPERION_HOME/products/Planning/config before you configure. If you are upgrading from WebSphere 6.0.x to WebSphere 6.1, you must migrate application environments. See WebSphere Upgrade Configuration Prerequisites on page 65.

WebSphere Upgrade Configuration Prerequisites


If you are upgrading EPM System products from Release 9.3.x, and you are also upgrading from WebSphere 6.0.x to WebSphere 6.1.x, you must perform the following procedure to migrate application environments after you install EPM System products and before you configure them with EPM System Configurator.

To migrate the WebSphere application environment:


1 2
Leave the existing profile located in HYPERION_HOME/deployments/WebSphere6 as is. Edit the WebSphere properties file in HYPERION_HOME/common/config/9.5.0.0/ resources/websphere/resources/websphere.properties to change the deployment.dir property to a new, different directory. Run the WebSphere profile creation script manually, pointing to the directory you specified in the previous step.

For example, if the new directory name you specified is ./deployments/WAS61, run the following script:

Satisfying Initial Requirements

65

WAS61_HOME/bin/manageprofiles.sh -create -profileName hyslProfile -profilePath / deployments/WAS61/profile -templatePath "WAS_HOME\profileTemplates\default" -nodeName hyslNode -cellName hyslCell -hostName hitqew2k3-7 -portsFile hyphome/common/ config/9.5.0.0/resources/websphere/resources/profile-portsdef.props

Perform a migration from the previous profile to the new profile.

For example:
WAS61_HOME/bin/WASPreUpgrade.sh <BACKUP_DIR> <WAS60_HOME> WAS61_HOME/bin/WASPostUpgrade.sh <BACKUP_DIR> -profileName hyslProfile

After you configure EPM System products using EPM System Configurator, new applications are deployed to the new WebSphere 6.1.x profile. Applications for EPM System products that you do not upgrade are also in the new WebSphere 6.1.x profile.
Note: The folder for the previous profile (for example, HYPERION_HOME/deployments/ WebSphere6) remains. Do not delete it.

Configuration Sequence
In general, for a new installation, Oracle recommends that for each machine, you configure all EPM System products at the same time for the products installed on the machine. By default, EPM System Configurator preselects all products for you. Shared Services must be installed and configured for other products to configure successfully. The configuration sequence for various deployment scenarios is described in the following sections. Upgrade Note! If you are upgrading from a previous release of EPM System products, you can only configure one product at a time, and you must configure in a required order. See Upgrade Configuration Sequence on page 69.
Note: By default, EPM System Configurator uses the same database for all products you

configure at one time. To use a different database for each product, perform the Configure Database task separately for each product. In some cases you might want to configure separate databases for products. If you have already configured EPM Workspace and you deploy any additional products that are in EPM Workspace, you must run EPM System Configurator again and select the EPM Workspace Configure Web Server task. In this release, the following products and components are integrated in EPM Workspace:
l

EPM Workspace Financial Reporting Web Analysis Financial Management

66

Configuring EPM System Products

FDM Performance Scorecard Planning Performance Management Architect Profitability and Cost Management Calculation Manager ERP Integrator Oracle Business Intelligence Publisher Oracle Business Intelligence Enterprise Edition

Optional: The following products are not integrated in EPM Workspace, and although not required in most cases, Oracle recommends that you configure the Web server for these products using EPM Workspace Web server configuration.
l

Shared Services Administration Services Provider Services

Note: For drill through functionality, you are required to configure the Web server for these

products using EPM Workspace Web server configuration. If you do not want to use EPM Workspace Web server configuration for these products, see the Oracle Hyperion Enterprise Performance Management System Manual Deployment Guide. The following two optional administrative tasks have a required sequence:
l

Before you configure Performance Management Architect interface datasources, first configure and deploy Shared Services and Performance Management Architect. Shared Services must be running. Before you configure Planning clusters (select the Planning task Planning Cluster Management), first configure and deploy Shared Services. Shared Services must be running.

Configure the following products after you have completed all the configuration tasks using EPM System Configurator:
l

Data Relationship Management. See the Oracle Hyperion Data Relationship Management Installation Guide. FDM. FDM has only one task in EPM System Configurator. It registers the FDM Web server in the Shared Services Registry. The remainder of the configuration is done in FDM. See the Oracle Hyperion Financial Data Quality Management Configuration Guide. Data Integration Management. See the Hyperion Data Integration Management Installation Guide.

Configuration Sequence

67

Note: If you want to install Essbase in standalone mode (not using Shared Services), you can

skip the installation for Shared Services. However, you must still configure the Shared Services Registry. To configure the Shared Services Registry without installing Shared Services, you run EPM System Configurator from the command line using the forceRegistry option. See Setting Up the Shared Services Registry Without Installing Shared Services on page 109.

Configuring Products in a Single-Machine Environment


Oracle recommends that for each machine, you configure all EPM System products at the same time for the products installed on the machine. If you are configuring multiple products on a machine simultaneously, EPM System Configurator configures them in the correct order. Shared Services must be installed and configured for other products to configure successfully. After you have completed configuration, perform the postconfiguration tasks required for your product. See Chapter 7, Performing Postconfiguration Tasks.

Configuring Products in a Distributed Environment


Configure the products on the machine on which you installed Shared Services first, and ensure that Shared Services is running. Shared Services must be installed, configured, and running for other products to configure successfully. Then, for each machine in the deployment, configure all EPM System products at one time for the products installed on the machine. After you have completed configuration, perform the postconfiguration tasks required for your product. See Chapter 7, Performing Postconfiguration Tasks.

Configuring Products in an SSL-Enabled Environment


If you are configuring EPM System products for SSL, configure in this order: 1. Configure Shared Services first. To configure Shared Services, select the Foundation tasks on the Product Selection page of EPM System Configurator: Common Settings, Configure Database, Deploy to Application Server. On the Common Settings page, select Enable SSL for communications. 2. Set up Shared Services for SSL. See Oracle Hyperion Enterprise Performance Management System SSL Configuration Guide. 3. Make sure Shared Services is running. 4. Configure the rest of the EPM System products. 5. Set up other EPM System products for SSL. See Oracle Hyperion Enterprise Performance Management System SSL Configuration Guide.

68

Configuring EPM System Products

Upgrade Configuration Sequence


Upgrade Note! If you are upgrading from a previous release of EPM System products, you can configure only one product at a time, and you must configure in this order: 1. Configure Shared Services. To configure Shared Services, select the Foundation tasks on the Product Selection page of EPM System Configurator: Common Settings, Configure Database, Deploy to Application Server. Upgrade is selected by default. 2. Start Shared Services if it is not already started and validate that it is running. 3. Configure EPM Workspace. 4. Configure the rest of the products, one product at a time. 5. Configure EPM Workspace Web Server again. You must complete the Web Server Configuration task for EPM Workspace last to ensure that all products are configured to work with EPM Workspace. 6. Perform postconfiguration tasks for each product that you upgraded. See Chapter 7, Performing Postconfiguration Tasks. During an upgrade, throughout EPM System Configurator, port numbers of the previous installation are displayed by default.

Product Configuration Task Summary


The following tables summarize the configuration tasks for each product. All products are automatically registered with Shared Services during configuration. EPM System Configurator displays the Common Settings page once on each machine that you configure. Clients do not require configuration and are not included in these tables.
Note: The Upgrade column reflects products that have an Upgrade task in EPM System

Configurator. Not all products that are upgradeable have an upgrade task. For information about products that are not upgradeable, see Chapter 8, Upgrading EPM System Products. The following table summarizes the configuration options available for Foundation Services products.
Table 9

Foundation Services Configuration Task Summary Product Options Configure Database X Deploy to Application Server X Product-specific Configuration Tasks Upgrade Postconfiguration Tasks X (Optional)

Shared Services

Product Configuration Task Summary

69

Product Options Calculation Manager Performance Management Architect

Configure Database X X (Windows only)

Deploy to Application Server X X

Product-specific Configuration Tasks

Upgrade

Postconfiguration Tasks

N/A X (Optional)
l

Interface Datasource Configuration (Windows only) X Configure Web Server X (Optional)

EPM Workspace

X
l

The following table summarizes the configuration options available for Essbase products.
Table 10

Essbase Product Configuration Task Summary Product Options Configure Database Deploy to Application Server Product-specific Configuration Tasks X
l

Upgrade

Postconfiguration Tasks X (Required for UNIX)

Essbase

X Essbase Custom Configuration X

Administration Services

X (Required only if you are using Business Rules with Planning or Log Analyzer features)

Provider Services Smart Search Command Line Utility Essbase Studio X (Required for Essbase Studio catalog)

X X

N/A

X (Optional)

Integration Services

The following table summarizes the configuration options available for Reporting and Analysis products.

70

Configuring EPM System Products

Table 11

Reporting and Analysis Product Configuration Task Summary Product Options Configure Database Deploy to Application Server X Product-specific Configuration Tasks X
l l

Upgrade

Postconfiguration Tasks X

Reporting and Analysis

Note: You configure the Reporting and Analysis database through EPM Workspace.

X Service Configuration Configure Financial Reporting Server

The following table summarizes the configuration options available for Financial Performance Management Applications products.
Table 12

Financial Performance Management Applications Product Configuration Task Summary Product Options Configure Database X Deploy to Application Server Product-specific Configuration Tasks X
l l l l

Upgrade

Postconfiguration Tasks X

Financial Management (All configuration tasks are Windows only)

X Configure DCOM Configure Application Server Configure Application Cluster Register Application Servers/ Cluster Configure Web Server (Optional) Configure Data Source for Extended Analytics X

l l

Performance Scorecard Planning X

X X

X X X (Optional)
l

X X

Manage Planning Clusters N/A

Profitability and Cost Management Strategic Finance (All configuration tasks are Windows only) X

X
l l

X Configure Data Folder WebServices Configuration

The following table summarizes the configuration options available for Data Management products.

Product Configuration Task Summary

71

Table 13

Data Management Product Configuration Task Summary Product Options Configure Database Deploy to Application Server Product-specific Configuration Tasks X
l

Upgrade

Postconfiguration Tasks X

FDM (All configuration tasks are Windows only) ERP Integrator Data Relationship Management X X

N/A Configure FDM Server N/A N/A

X X

Using EPM System Configurator


Run EPM System Configurator on each computer hosting the products to configure or reconfigure. For a list of characters supported during configuration with EPM System Configurator, see Characters Supported for Installation and Configuration on page 49.
Note: On Windows machines, run EPM System Installer and EPM System Configurator as an administrator. On UNIX machines, do not use the root user to install and configure.

Install and configure as the same user for all EPM System products. On UNIX systems, if you are using Oracle Application Server, you must install and configure EPM System products using the same user you used to install Oracle Application Server.

To configure EPM System products:


1
Choose a method to launch EPM System Configurator:
l

On the last page of EPM System Installer, click Configure. From the Start menu, select Programs, then Oracle EPM System, then Foundation Services, and then EPM System Configurator. Double-click configtool.bat from HYPERION_HOME/common/config/ version_number. From a Windows console, change to HYPERION_HOME/common/config/ version_number, and then enter startconfigtool.bat -console. Create a silent configuration response file. See Performing Silent Configurations on page 108. On UNIX, change to HYPERION_HOME/common/config/version_number and then type ./configtool.sh. On UNIX, change to HYPERION_HOME/common/config/version_number and then type ./configtool.sh console

72

Configuring EPM System Products

Review and complete each page of EPM System Configurator, clicking Next to move to the next page.

The following table provides links where you can find more details about each page of EPM System Configurator.

Page Task selection Shared Services and Registry database configuration EPM System common settings Enable separately licensed product options Configure database

Reference Task Selection on page 74 Ensure that the database is started and that you have created a database as described in Preparing a Database in Oracle Hyperion Enterprise Performance Management System Installation Start Here. Enter the information as described in Shared Services and Registry Database Configuration on page 75. EPM System Common Settings on page 78

Select the product features that you are authorized to use based on your license agreement. See Enable Separately Licensed Product Options on page 77 and Chapter 12, License Compliance

Ensure that the database is started and that you have created a database as described in Preparing a Database in Oracle Hyperion Enterprise Performance Management System Installation Start Here. Enter the information as described in Database Configuration on page 78.

Application server deployment Product-specific configuration tasks

Enter the information as described in Deploy to Application Server on page 81. Note: For simplicity, Oracle recommends that you use the same application server, and domain or profile, for all products that you install. For detailed procedures to configure each product, see the sections:
l l l l l l l l

EPM WorkspaceSpecific Configuration Tasks on page 89 Performance Management ArchitectSpecific Tasks (Optional) on page 92 EssbaseSpecific Tasks on page 94 PlanningSpecific Tasks (Optional) on page 97 Financial ManagementSpecific Tasks on page 99 Reporting and AnalysisSpecific Tasks on page 106 Strategic FinanceSpecific Tasks on page 107 FDMSpecific Configuration Tasks on page 107

Confirm the configuration tasks to complete, and then click Next.

EPM System Configurator displays the status of the configuration process. Configuration time depends on the products and tasks that you selected. Progress is recorded in
HYPERION_HOME/logs/config/configtool.log

When configuration finishes, the status of each task is displayed. Configuration results are noted in HYPERION_HOME/logs/config/configtool_summary.log.

Click Task Panel to return to the Task Selection page to complete additional configuration tasks.
73

Using EPM System Configurator

Optional: After you configure all the products on this machine, to validate the installation, click Validate. See Chapter 6, Validating the Installation.

On Windows machines, if you selected Create Windows Services for configured components, the services are started at the completion of the configuration.
Note: The OpenLDAP service (OpenLDAP-slapd) and Hyperion Financial Management

- Management Service" must be started manually. Essbase Studio does not have a Windows service. Use the .bat files to start it manually. On UNIX machines, the services are started at the completion of the configuration.

Click Finish.

If configuration is successful, perform any required postconfiguration tasks. See Chapter 7, Performing Postconfiguration Tasks. Terminating configuration for a particular product does not terminate the entire process. Configuration continues for the other products. EPM System Configurator displays error messages on a summary page after the configuration process completes. If errors are displayed, perform these tasks:
l

Review the log files. See the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Troubleshooting Guide for information about resolving configuration issues.

Task Selection
Select the products and tasks to configure for this machine, or click Next to select all the
required tasks. If you installed multiple instances of Essbase, choose the instance that you want to configure. The instances appear in the Task Selection page as Essbase and Essbase-n. Note the following about task selection:
l

In a new installation all required tasks are selected by default. You can clear tasks you want to perform later. Select Check All or Uncheck All to quickly select or deselect all tasks. You cannot deselect mandatory tasks, which are selected by default. If the task is unavailable (grey) and selected (checked), the task will be performed and you cannot deselect it. EPM System Configurator automatically performs some common tasks the first time you configure any component of a product, such as Shared Services registration. EPM System Configurator uses the Shared Services Registry to find the location of Shared Services.

74

Configuring EPM System Products

For ease of deployment and simplicity, you can use one database for all products, which is the default when you configure all products at the same time.
Caution!

To use a different database for each product, perform the Configure Database task separately for each product. In some cases you might want to configure separate databases for products. Consider performance, roll-back procedures for a single application or product, and disaster recovery plans.

If you are applying the maintenance release, you do not need to configure the database, and registration with Shared Services is not performed. (Essbase Studio is an exception. For Essbase Studio, configure the database if you are applying the maintenance release, and select Connect to a previously configured database.) Upgrade Note!
l

You can configure only one product at a time. Because you are required to configure Shared Services first, only the required tasks for Shared Services are selected the first time you configure. For products that have the Upgrade Tasks option, you must select it to perform upgrade procedures automatically.

Shared Services and Registry Database Configuration


Specify the settings for the Shared Services and Shared Services Registry database.
The first time you configure EPM System products, you configure a database for use by Shared Services, which includes the Shared Services Registry. When you configure the Shared Services database, EPM System Configurator ensures that the database is connected and is a supported database type. If a database is detected, you may be prompted to choose whether to use the detected database or create a database. For a list of supported databases, see the Oracle Hyperion Enterprise Performance Management System Certification Matrix (http://www.oracle.com/technology/products/bi/hyperionsupported-platforms.html). For database prerequisites for this release, see Oracle Hyperion Enterprise Performance Management System Installation Start Here. You can use Windows Authentication for SQL Server connections if you use Microsoft SQL Server database. See Setting Up Microsoft SQL Server Windows Authentication on page 80. For more information about the Shared Services Registry, see About the Shared Services Registry on page 64.

Using EPM System Configurator

75

Note: This task assumes that you have already created the database. If you have not yet created

a database, see Preparing a Database in Oracle Hyperion Enterprise Performance Management System Installation Start Here. If you uninstalled EPM System products Release 11.1.1.0 or Release 11.1.1.1 and then reinstall into the same location, you cannot re-use the Shared Services and Shared Services Registry database. Upgrade Note! If you are upgrading a Shared Services database, EPM System Configurator creates the registry during the upgrade configuration. The following table describes options for Shared Services and Registry Database configuration.

EPM System Configurator Fields Connect to a previously configured Shared Services database/ Perform 1st-time configuration of Shared Services database

Description When you first configure Shared Services, choose Perform 1st-time configuration of Shared Services database. This database includes the Shared Services Registry, which is used to store common information for all products. When you configure in a distributed environment, you must configure the Shared Services database on every machine. On the first machine, you are setting up the Shared Services Registry. For configurations on subsequent machines, choose Connect to a previously configured Shared Services database. In this case, you are letting the machine know the location of the Shared Services Registry. For some products, you can use this same database to store product information. In this case, each product has its own table in this database. See Installation Planning Checklist in Oracle Hyperion Enterprise Performance Management System Installation Start Here for additional information about database preparation for each product. Upgrade Note! If you are upgrading from a previous release, Connect to a previously configured Shared Services database is selected by default. Do not change the selection. During upgrade, the only database information you can change is user name and password.

Your Information

Database Type Server Port Service Name or SID, or Database Name Username Password

Select the database type. Specify the name of the database server where the Shared Services database should be created. Select the default or specify a custom Shared Services server port number on which the database listens. Specify the name of the Shared Services database. If you are using an Oracle RAC database, specify the RAC service name. Enter the name of the database user. Enter the password of the database user. Note: If the password changes, reconfigure as described in Chapter 9, Reconfiguring EPM System Products.

76

Configuring EPM System Products

EPM System Configurator Fields Advanced options (Optional)

Description Click to specify additional information. For more information on these options, see Advanced Options for Database Configuration (Optional) on page 80. You can use this option to configure Oracle RAC.

Your Information

Note: EPM System Configurator configures the Shared Services database when you click Next.

If you later have to click Back, you must select Connect to a previously configured Shared Services database and reenter the Shared Services database information.

Upgrade Tasks
This option is available only if you are upgrading from a previous release. If you are not upgrading, skip this section. Upgrade Note!

If you are upgrading EPM System products from a previous release, select this option for
the product that you want to upgrade. This task performs upgrade tasks automatically for the selected product; however no upgrade-specific page appears during configuration, and you do not have to enter any information.

Enable Separately Licensed Product Options


Select the product features that you are authorized to use based on your license agreement.
For some products, this step enables you to select only those product features that you have purchased. The features available depend on your purchase and licensing agreements. For information, see Chapter 12, License Compliance. You specify product options only for the following products:
l

Planning. For Planning, you can select Capital Asset Planning or Workforce Planning if you are licensed to use those modules. Selecting these options enables features for those modules. Strategic Finance. For Strategic Finance you can select Strategic Finance for Banking if you are licensed to use it.

The following table describes options for Product Options configuration.


EPM System Configurator Product/Options Description Select the product components that you are licensed to use. Your Information

Using EPM System Configurator

77

EPM System Common Settings


Specify settings for all products on all machines that have been identified in the Shared
Services Registry so far, or click Next to accept the default values. If you configure on another machine and change any of these options, your new selections apply for all products and machines you have not configured. If you reconfigure on a machine, the new settings apply to any products you reconfigure and to future configurations. The following table describes options for common settings configuration.
EPM System Configurator Fields Create Windows Services for configured components (Windows only) Enable SSL for communications Description Select to configure each service as a Windows service that starts automatically when you start Windows. Your Information

Select to enable SSL communication for all Web applications. If this option is selected, URLs are in the form https. If you enable SSL, in the EPM Workspace Web server configuration page, you must select SSL Enabled and then specify the SSL port used by the Web server. See Configure EPM Workspace Web Server on page 89. Note: Selecting this option does not enable secure communication for the Web application server, and does not create and load certificates into JREs and JDKs. See Oracle Hyperion Enterprise Performance Management System SSL Configuration Guide for more information. If you want to change from an SSL-enabled environment to a non-SSL-enabled environment or vice versa, see Reconfiguring for SSL on page 193. Modifying this option is not sufficient.

SMTP Mail Server

For products that integrate an e-mail feature, which uses standard Simple Mail Transfer Protocol (SMTP) protocol, specify the outgoing mail (SMTP) server. To enable e-mail alerts, you must specify the SMTP server name. Specify the administrator's e-mail address to use for notifications. Specify whether the SMTP server requires authentication, and then specify a user name and password. Specify the user name for the SMTP server. Specify the password for the SMTP server.

Admin Email SMTP Server requires authentication User Name Password

Database Configuration
Specify the database settings to use for the products that you selected on the Task Selection
page. For ease of deployment and simplicity, for a new installation, you can use one database for all products, which is the default when you configure all products at the same time. To use a different
78
Configuring EPM System Products

database for each product, perform the Configure Database task separately for each product. In some cases you might want to configure separate databases for products. Consider performance, roll-back procedures for a single application or product, and disaster recovery plans. See Oracle Hyperion Enterprise Performance Management System Installation Start Here. When you configure EPM System products to use a database, EPM System Configurator ensures that the database is connected and is a supported database type. For a list of supported databases for this release, see Oracle Hyperion Enterprise Performance Management System Certification Matrix (http://www.oracle.com/technology/products/bi/hyperion-supported-platforms.html). Ensure that the database is set up as described in Preparing a Database in Oracle Hyperion Enterprise Performance Management System Installation Start Here. The first time you configure, a default database name is displayed. Change the defaults to match the name of the database and user you already created. Note the following about database configuration:
l

A database type might not be available if one of the selected products doesnt support it. In this case, configure this product separately. See the Oracle Hyperion Enterprise Performance Management System Certification Matrix (http://www.oracle.com/technology/products/bi/ hyperion-supported-platforms.html) for a list of supported databases for each product.

Upgrade Note! Note the following about database configuration if you are upgrading:
l

Select Connect to a previously configured database. However, if you are upgrading from Planning Release 9.2.x, select Perform 1st-time configuration of database and enter the database details for the existing database. When you run the Configure Database task for Performance Management Architect, it may take a long time to complete. Do not interrupt this task while it is running.

The following table describes options for database configuration.


EPM System Configurator Fields Database configuration for the following products Description Confirm the list of products for which you want to configure the database. The list displayed depends on the products you initially selected to configure. To create different databases for each product, select only one product at a time and run EPM System Configurator again to configure the database for another product. Select a configured database, or specify the name of a new database to configure. Note: This task assumes that you have created the database. If you have not created a database, see Preparing a Database in Oracle Hyperion Enterprise Performance Management System Installation Start Here. Upgrade Note! If you are upgrading from a previous release, Connect to a previously configured database is selected by default. For most products, Oracle recommends that you select this option. If you are upgrading from Planning Release 9.2.x, select Perform 1st-time configuration of database. Your Information

Connect to a previously configured database/ Perform 1st-time configuration of database

Using EPM System Configurator

79

EPM System Configurator Fields Database type Server Port Service Name or SID, or Database Name Username Password

Description Select the database type. Specify the name of the computer or server hosting the database. Select the default or specify a custom server port number on which the database listens. Specify the name of the database. If you are using an Oracle RAC database, specify the RAC service name. Enter the database user name. Enter the database user password. Note: If the password changes, reconfigure as described in Changing Repository Passwords on page 195.

Your Information

Advanced Options (Optional)

Click to specify additional information. See Advanced Options for Database Configuration (Optional) on page 80. You can use this option to configure Oracle RAC.

You can use Windows Authentication for SQL Server connections if you use Microsoft SQL Server database. See Setting Up Microsoft SQL Server Windows Authentication on page 80.

Setting Up Microsoft SQL Server Windows Authentication


To set up Windows authentication for a SQL Server connection:
1 2 3 4 5
Configure SQL Server to use Windows authentication. Grant your Windows account appropriate access to your database. From the configuration task list, select Configure Database. From the database list, select SQL Server. Specify all database information except for Username and Password.

Advanced Options for Database Configuration (Optional)


The following table describes advanced options for database configuration.

EPM System Configurator Fields JDBC URL

Description Enter additional attributes for the connection. See Appendix D, JDBC URL Attributes for additional information. If you enter a JDBC URL, it overrides the values you entered in the database configuration page.

Your Information

80

Configuring EPM System Products

EPM System Configurator Fields

Description

Your Information

Additional configuration for Oracle Data Tablespace Enter the name of an existing tablespace used to store table data. The data tablespace is the logical portion of the database used to allocate storage for table data.

Additional configuration for Financial Management Database Connection Link (UDL) Accept the default or specify a different UDL file. The Database Connection Link (UDL) defines the database connection information for Financial Management applications. EPM System Configurator provides a default UDL file for use with Financial Management. Upgrade Note! If you are upgrading from a previous release of Financial Management, choose the UDL file that you used with the previous release. Number of pooled DB connections Specify the number of maximum pooled relational database connections for the application, or use the default value of 40. Financial Management requires approximately 25 relational database connections per application. For more information about pooled database connections, see Appendix E, Database Information for Financial Management. Encrypt UDL Specify whether to encrypt the UDL file. Oracle recommends that you encrypt the UDL file. See Encrypting UDL Files on page 245.

Deploy to Application Server


Select the application server and deployment type.
Note the following information about deploying:
l

You can deploy multiple products to one application server, in a single profile (WebSphere) or domain (WebLogic Server). For simplicity, Oracle recommends that you use the same application server, and domain or profile. A Web application server might not be available if one of the selected products doesnt support it. In this case, configure this product separately. See the Oracle Hyperion Enterprise Performance Management System Certification Matrix (http://www.oracle.com/technology/ products/bi/hyperion-supported-platforms.html) for a list of supported Web application servers for each product. EPM Workspace and the application being integrated must be deployed to the same Web application server type. For example, if EPM Workspace is deployed to Oracle Application Server, Performance Management Architect must also be deployed to Oracle Application Server. If an application being integrated does not support the EPM Workspace Web

Using EPM System Configurator

81

application server, you can redeploy EPM Workspace to a commonly supported Web application server (WebLogic Server), or perform a separate deployment.
l

If you are implementing a custom authentication module, you must include its Java archive (.jar) in the EPM Product classpath. The most reliable method of adding the custom authentication module Java archive to a J2EE Web application classpath is to add it to the classpath in the enterprise or Web archive (.ear or .war) of an application before you deploy it. See the Oracle Hyperion Enterprise Performance Management System Security Administration Guide for detailed procedures to perform before you run EPM System Configurator.

Note the following information about automatic deployment:


l

Only 32-bit application servers are supported for auto-deployment. For products that support it, to deploy to 64-bit application servers, install the 64-bit binaries for those products using the Choose components individually option in EPM System Installer and then follow the manual deployment instructions in Oracle Hyperion Enterprise Performance Management System Manual Deployment Guide.

Note the following information about manual deployment:


l

Run EPM System Configurator on each application server machine. Select the Manual option in the Web application server deployment page. You must perform this step to update the Shared Services Registry and lay down the .ear and .war files. Specify the correct hostname and port information. If necessary, use the advanced Set Up option to configure access using a logical address.

See the Oracle Hyperion Enterprise Performance Management System Manual Deployment Guide for deployment procedures for each application server and product. The following table describes options for application server deployment configuration.
EPM System Configurator Fields Select Server: Automatic/ Manual Description Your Information

Select the Web Application Server you installed, and then specify whether you want to deploy automatically or manually. If you select Embedded Java Container, you can deploy only automatically. If you are deploying your product to one application server, decide between these deployment options:
l

AutomaticDeploys all files to the application server. In most cases, no other deployment tasks are required. ManualEPM System Configurator places the necessary Web archives (EAR or WAR) in directories to enable manual deployment at a future time.

If you select Manual, see the Oracle Hyperion Enterprise Performance Management System Manual Deployment Guide for details.

82

Configuring EPM System Products

Note: For information about preparing the application server, see Oracle Hyperion Enterprise

Performance Management System Installation Start Here.

Application Server Deployment: Oracle Application Server


Specify the application server options, or click Next to accept the default entries.
EPM System Configurator creates a group for each deployed Web application, with the same name as the Server. The following table describes options for Oracle application server deployment configuration.
EPM System Configurator Fields Location Description Your Information

Enter the path to the application server installation directory; for example:
l l

Windows C:/Oracle/product/OracleAS UNIX/Linux /opt/app/oracle/product/OracleAS

Ear/War Name Advanced Set up

Select the components to deploy. Displays the server name. If you have set up a cluster, or plan to set one up, click Set up. See Cluster Setup on page 88. If you do not select Set up, EPM System Configurator adds this deployment to a default cluster with the name Default. For more information about clustering, see Oracle Hyperion Enterprise Performance Management System High Availability Guide. For more information about clustering Shared Services, see the white papers available at http://www.oracle.com/technology/products/bi/resource-library.html.

What Happens During Deployment: Oracle


EPM System Configurator deploys the application to:
HYPERION_HOME/deployments/AppServNameAndVersion

Under this directory, the bin directory contains start and stop scripts for all deployed applications. For each application, there is also a setCustomParamsProduct.bat file (.sh extension for UNIX), where JAVA_OPTIONS can be changed when using start scripts.

Using EPM System Configurator

83

Application Server Deployment: Oracle | BEA WebLogic


Specify the application server options, or click Next to accept the default entries.
Note: You cannot deploy Web applications using EPM System Configurator when the Admin

Server port for WebLogic Server has been changed to a non-default port. To deploy using EPM System Configurator, change the Admin server port to 7001 and re-deploy. On WebLogic Server, a default user name and password of hyperion is used to administer the domain. You can manually change the credentials after deploying. The following table describes options for WebLogic application server deployment configuration.
EPM System Configurator Fields Location Description Your Information

Enter the path to the application server installation directory. For example:
l l

Windows c:/bea/weblogic92 UNIX /opt/bea/weblogic92

Domain

Displays the default name of the domain where you access the application. All applications deploy to the same domain. To change the domain name, see What Happens During Deployment: WebLogic Server on page 85. Select the components to deploy. Displays the server name. Accept the default port, or, to change the default, enter a port number that does not conflict with other applications installed on your machine. See Ports in Oracle Hyperion Enterprise Performance Management System Installation Start Here. Accept the default port or specify the SSL Port to use for automatic deployment. Specifying this port sets up SSL using the Java application server's default certificates. See the Oracle Hyperion Enterprise Performance Management System SSL Configuration Guide for recommendations on updating the Java application server with a valid certificate. If you are using SSL, you must clear the non-SSL port in your Java application server after configuration to ensure secure communication. See Oracle Hyperion Enterprise Performance Management System Manual Deployment Guide.

Ear/War Name Port

SSL Port

Advanced Set up

If you have set up a cluster, or plan to set one up, click Set up. See Cluster Setup on page 88. If you do not select Set up, EPM System Configurator adds this deployment to a default cluster with the name Default. For more information about clustering, see Oracle Hyperion Enterprise Performance Management System High Availability Guide. For more information about clustering Shared Services, see the white papers available at http://www.oracle.com/technology/products/bi/resource-library.html.

84

Configuring EPM System Products

Upgrade Note! During configuration, you might see one of the following error messages:
l

"Application HPSWEBREPORTS cannot be deployed to server HPSWEBREPORTS because it has already been deployed to server webreportsDomain." Application eas cannot be deployed to server eas because it has already been deployed to server "aas."

If either of those messages are displayed, , change the server name on WebLogic Application Server Deployment panel to the name specified in the error message. For example, for Performance Scorecard, change the server name from "HPSWEBREPORTS" to "webreportsDomain." For Administration Services, change the server name from "eas" to "aas." Then you can proceed with the configuration.

What Happens During Deployment: WebLogic Server


EPM System Configurator deploys each application to the same WebLogic Server domain. The domain is created when the first application is deployed. Each application runs in a separate JVM. EPM System Configurator deploys the application to
HYPERION_HOME/deployments/AppServNameAndVersion.

Under this directory, the bin directory contains start and stop scripts for all deployed applications. For each application, there is also a setCustomParamsProduct.bat file (.sh extension for UNIX), where JAVA_OPTIONS can be changed when using start scripts. To change the default profile directory, modify the deployment directory parameter in weblogic.properties, which is in:
HYPERION_HOME/common/config/9.5.0.0/resources/AppServName/resources. Note: Oracle does not recommended changing other parameters in this file.

Application Server Deployment: WebSphere


Specify the application server options, or click Next to accept the default entries.
The following table describes options for WebSphere application server deployment configuration.

Using EPM System Configurator

85

EPM System Configurator Fields Location

Description

Your Information

Enter the path to the application server installation directory.


l

For example, WebSphere Base:


m m

Windows c:/WebSphere/AppServer UNIX /opt/WebSphere/AppServer Windows c:/IBM/WebSphere/Express61/AppServer UNIX /opt/IBM/WebSphere/Express61/AppServer

For example, WebSphere Express:


m m

If disk space is inadequate, EPM System Configurator places java.io.tempdir in HYPERION_ HOME/temp. After deployment, the temp directory is deleted. Profile Displays the name of the profile where you access the application. By default, all applications deploy to the same profile. To change the profile name, see What Happens During Deployment: WebSphere on page 86. Select the components to deploy. Displays the server name. Accept the default port, or, to change the default, enter a port number that does not conflict with other applications installed on your machine. See Ports in Oracle Hyperion Enterprise Performance Management System Installation Start Here. Accept the default port, or specify the SSL port to use for automatic deployment. Specifying this port sets up SSL using the Java application server's default certificates. See the Oracle Hyperion Enterprise Performance Management System SSL Configuration Guide for recommendations on updating the Java application server with a valid certificate. If you are using SSL, you must clear the non-SSL port in your Java application server after configuration to ensure secure communication. See Oracle Hyperion Enterprise Performance Management System Manual Deployment Guide. Advanced Set up If you have set up a cluster, or plan to set one up, click Set up. See Cluster Setup on page 88. If you do not select Set up, EPM System Configurator adds this deployment to a default cluster with the name Default. For more information about clustering, see Oracle Hyperion Enterprise Performance Management System High Availability Guide. For more information about clustering Shared Services, see the white papers available at http://www.oracle.com/technology/products/bi/resource-library.html.

Ear/War Name Port

SSL Port

What Happens During Deployment: WebSphere


EPM System Configurator deploys each application to the same WebSphere profile. The profile is created when the first application is deployed. Each application runs in a separate JVM. EPM System Configurator deploys the application to
HYPERION_HOME/deployments/AppServNameAndVersion.

86

Configuring EPM System Products

Under this directory, the bin directory contains start and stop scripts for all deployed applications. For each application, there is also a setCustomParamsProduct.bat file (.sh extension for UNIX), where JAVA_OPTIONS can be changed when using start scripts. To change the default profile directory, modify the deployment directory parameter in websphere.properties in
HYPERION_HOME/common/config/9.5.0.0/resources/AppServName/resources. Note: Oracle does not recommended changing other parameters in this file.

Web Server Plug-ins Directory


If requested, specify the installation location of the Web server plug-ins.
EPM System Configurator displays this page only if it cannot find the plug-ins.

Application Server Deployment: Embedded Java Container


Specify the application server options, or click Next to accept the default entries.
The following table describes options for the Embedded Java Container application server deployment configuration.
EPM System Configurator Fields Ear/War Name Port Description Your Information

Select the components to deploy. Displays the server name. Accept the default port, or, to change the default, enter a port number that does not conflict with other applications installed on your machine. See Ports in Oracle Hyperion Enterprise Performance Management System Installation Start Here. Accept the default port, or specify the SSL port to use for automatic deployment. Specifying this port sets up SSL using the Java application server's default certificates. See the Oracle Hyperion Enterprise Performance Management System SSL Configuration Guide for recommendations on updating the Java application server with a valid certificate. If you are deploying manually, see the Oracle Hyperion Enterprise Performance Management System SSL Configuration Guide. If you are using SSL, you must clear the non-SSL port in your Java application server after configuration to ensure secure communication. See Oracle Hyperion Enterprise Performance Management System Manual Deployment Guide.

SSL Port

Using EPM System Configurator

87

EPM System Configurator Fields Advanced Set up

Description

Your Information

If you have set up a cluster, or plan to set one up, click Set up. See Cluster Setup on page 88. If you do not select Set up, EPM System Configurator adds this deployment to a default cluster with the name Default. For more information about clustering, see Oracle Hyperion Enterprise Performance Management System High Availability Guide. For more information about clustering Shared Services, see the white papers available at http://www.oracle.com/technology/products/bi/resource-library.html.

What Happens During Deployment: Embedded Java Container


EPM System Configurator deploys the application to:
HYPERION_HOME/deployments/AppServNameAndVersion

Under this directory, the bin directory contains start and stop scripts for all deployed applications. For each application, there is also a setCustomParamsProduct.bat file (.sh extension for UNIX), where JAVA_OPTIONS can be changed when using start scripts.

Cluster Setup
If you selected Set up, specify the following:
The following table describes options for cluster setup configuration.
EPM System Configurator Fields Edit default cluster Description Your Information

Specify a new URL for the cluster to use by default. (Specifying this URL does not create the cluster. ) You should have only one cluster for Shared Services, EPM Workspace, Performance Management Architect, Reporting and Analysis, Calculation Manager, and ERP Integrator. EPM System Configurator creates a cluster for these products and uses it as the default cluster. You cannot define a new cluster for these products.

Define new cluster

Specify the URL to use as the default for the cluster you will create. (Specifying this URL does not create the cluster.) Provide a logical or physical address only. If you selected Enable SSL for communications on the Common Settings page, make sure the cluster URL you override with uses an SSL port.

Add to existing cluster

Specify the URL to add to the cluster. Provide a logical or physical address only to be associated with the Web application.

To manage clusters for Planning, in EPM System Configurator, select Manage Planning Clusters from the Task Selection Panel for Planning.
88
Configuring EPM System Products

For information about clustering EPM System products, see Oracle Hyperion Enterprise Performance Management System High Availability Guide. For more information about clustering Shared Services, see the white papers available at http://www.oracle.com/technology/ products/bi/resource-library.html. Upgrade Note! For Performance Management Architect, you must use cluster names that are the same as the instance names that were used in Performance Management Architect configuration in the previous release.

EPM WorkspaceSpecific Configuration Tasks


Configure EPM Workspace Services
Specify the following EPM Workspace service information, or click Next to accept the
defaults: The following table describes options for EPM Workspace Services configuration.
EPM System Configurator Fields Repository Directory Description Your Information

Specify the directory where the Reporting and Analysis repository data is stored; for example: HYPERION_HOME/products/Foundation/worskpace/data/directoryName. If you are replicating repositories, specify a write-able, shared drive. Upgrade Note! If you are upgrading from a previous release, ensure that the repository location of the previous release is specified.

Port Ranges

Specify the port range to use for EPM Workspace services.

Configure EPM Workspace Web Server


Specify EPM Workspace Web server information, or click Next to accept the defaults.
Information in this page comes from applications already deployed and recorded in the Shared Services Registry and applications you are deploying in this configuration sequence. If you later deploy any additional products that are in EPM Workspace, run EPM System Configurator again and select the EPM Workspace Web Server Configuration task. Components for the following products can be listed:
l

EPM Workspace Financial Reporting


Using EPM System Configurator

89

Web Analysis Financial Management FDM Performance Scorecard Planning Performance Management Architect Profitability and Cost Management Calculation Manager ERP Integrator BI Publisher BI Publisher is included in this list only after you have completed prerequisite steps. See Integrating BI Publisher into EPM Workspace on page 91.

Oracle BI EE Oracle BI EE is included in this list only after you have completed prerequisite steps. See Integrating Oracle BI EE into EPM Workspace on page 92.

Optional: The following products are not integrated in EPM Workspace, and although not required in most cases, Oracle recommends that you configure the Web server for these products using EPM Workspace Web server configuration.
l

Shared Services Administration Services Provider Services

Note: For drill through functionality, you are required to configure the Web server for these

products using EPM Workspace Web server configuration. If you do not want to use EPM Workspace Web server configuration for these products, see the Oracle Hyperion Enterprise Performance Management System Manual Deployment Guide. The following table describes options for EPM Workspace Web server configuration.
EPM System Configurator Fields Select Web Server Port Description Your Information

Select the Web server. Specify the Web server port. If you enable SSL, make sure the port number you enter is a secure port. If you are using SSL in a UNIX environment, specify the port number for the SSL-capable Apache installation that you installed instead of the port number for the default EPM System installation. See Installation Prerequisites on page 48.

90

Configuring EPM System Products

EPM System Configurator Fields SSL Enabled Location of Web Server

Description

Your Information

Select whether to enable SSL. Specify or browse to the location of the Web server. This field is not required if you are using IIS. If you are using SSL in a UNIX environment, select the SSL-capable Apache installation that you installed instead of the default EPM System installation. See Installation Prerequisites on page 48.

Component Host Context

Select the check box adjacent to each module to integrate with EPM Workspace. For each enabled module, review the host name to which this Web server will proxy requests. Review the context path. The context path is the part of the URL that accesses the deployed Web application. For example, in the following URL, workspace is the context path:
http://webserverhost.example.com:19000/workspace

Port

Review the port numbers for the application server listen ports for the applications. The port here must match the listen port of the deployed application. For Embedded Java Container, this port is the AJP listen port, not the HTTP listen port.

Note: Use fully qualified host names for all entries. For example, webserverhost.example.com.

When Reporting and Analysis Web applications are distributed between two or more machines, or when configuring a Web server on a machine other than where the application server(s) are installed, you must provide the following:
l

The correct application server hostnamesSpecify the machine name and port as part of the EPM System Configurator. Web server plug-in portsManually enter the information in the Web server plug-in configuration files.

See Oracle Hyperion Enterprise Performance Management System Manual Deployment Guide for details on the required manual configuration.

Integrating BI Publisher into EPM Workspace


Before you can integrate BI Publisher into EPM Workspace, you must complete the prerequisite steps described in the Oracle Business Intelligence Publisher Administrator's and Developer's Guide. The following provides an overview of the process:

To integrate BI Publisher into EPM Workspace:


1
Register the BI Publisher server with EPM Workspace and Shared Services.

Using EPM System Configurator

91

2 3

Configure the BI Publisher server to use the CSS security model. Use EPM System Configurator to configure the EPM Workspace Web server to proxy to the Oracle Business Intelligence Publisher server. On the Task Selection page, select the EPM Workspace Web Server Configuration task. See Configure EPM Workspace Web Server on page 89.

Integrating Oracle BI EE into EPM Workspace


Before you can integrate Oracle BI EE into EPM Workspace, you must complete prerequisite steps. For information about prerequisite steps for integrating Oracle BI EE with EPM Workspace, see the Oracle Business Intelligence New Features Guide. After you have completed these prerequisite steps, use EPM System Configurator to configure the EPM Workspace Web server to proxy to the Oracle Business Intelligence Enterprise Edition server. On the Task Selection page, select the EPM Workspace Web Server Configuration task. See Configure EPM Workspace Web Server on page 89.

Performance Management ArchitectSpecific Tasks (Optional)


Creating an Interface Datasource is required if you want to use interface tables in Performance Management Architect. Interface tables provide a database interface that enables the import of metadata and data from external systems into the Dimension Library. However, this task is not necessary for initial configuration. See the Oracle Hyperion Enterprise Performance Management Architect Administrator's Guide. You configure the tables by creating data source links that can be used during import profile creation and data synchronization.

Interface Datasources Configuration (Optional)


Specify whether you want to create, edit, or delete a datasource link.
Interface data source configuration is available only on the machine on which the Dimension Server is installed. You must register with Shared Services before you can perform this task.
Note: Make sure to use a database other than your repository database for interface datasource.

See Preparing a Database in Oracle Hyperion Enterprise Performance Management System Installation Start Here. The following table describes options for Performance Management Architect interface datasource configuration.

92

Configuring EPM System Products

EPM System Configurator Fields Create a new datasource link

Description Select Create a new datasource link, click Next, and then: 1. Choose the database type. See Interface Datasource Database Type (Optional) on page 93. 2. Specify the interface datasource database properties. See Interface Datasource Details (Optional) on page 93.

Your Information

Edit an existing datasource link

Select Edit an existing datasource link, click Next, and then: 1. Choose the datasource to edit. See Select Datasource to Edit or Delete (Optional) on page 94. 2. Modify the datasource properties. See Interface Datasource Details (Optional) on page 93.

Delete a datasource link

Select Delete a datasource link, click Next, and then choose the instance to delete. See Select Datasource to Edit or Delete (Optional) on page 94.

Interface Datasource Database Type (Optional)


Select the specific database type (Oracle, SQL or DB2) and click Next.

Interface Datasource Details (Optional)


To create or edit an interface datasource, specify the database details.
The following table describes options for Performance Management Architect interface datasource details configuration.

EPM System Configurator Fields Database Type Datasource Name Server Port SID (Oracle) or Database (MS SQL Server or IBM DB2) User Password

Description Displays the database type. Accept the default name, or enter a name for the data source. Accept the default name, or enter the name of the server hosting the database. (The default displays based on the database type.) Accept the default port number, or enter the port number of the server hosting the database. (The default displays based on the database type.) Enter the database name to use as an interface data source.

Your Information

Enter the user name for the database used as the interface data source. Enter the password for the database used as the interface data source.

Using EPM System Configurator

93

EPM System Configurator Fields Create interface tables

Description Select to create the interface tables in the database. Oracle recommends that you select this option.

Your Information

Select Datasource to Edit or Delete (Optional)


If you chose Edit an existing datasource link or Delete a datasource link, select the datasource
to edit or delete. Optional: If you are deleting a datasource, select Delete interface tables to delete the database tables.

EssbaseSpecific Tasks
Configure the instance of Essbase Server that you selected on the Task Selection page.

Essbase Server Configuration


Specify the configuration information for Essbase Server, or click Next to accept the default
settings. In general, Oracle recommends that you keep the default settings. EPM System Configurator configures the instance of Essbase that you selected on the Task Selection page. If you installed an additional instance of Essbase Server, it is displayed as Essbasen on the Task Selection page. For additional information about configuring an additional instance of Essbase Server, see Configuring and Starting an Additional Instance of Essbase Server on page 96. During configuration, if you do not select Essbase in Standalone mode, EPM System Configurator automatically registers Essbase with Shared Services and writes the Shared Services connection information to essbase.cfg. In addition, it specifies environment variables in a file used to launch Essbase Server. For more information about the environment variables, see Appendix B, Optional Manual Configuration for Essbase Products. The following table describes the configuration options for Essbase Server.
Table 14

Essbase Server Configuration Description Accept the default port number on which the Essbase Server listens for client requests. If you change the default value, be sure to enter a port number that is not used by other programs. The port value is stored in essbase.cfg. Your Information

EPM System Configurator Fields Agent Port Number

Start Port

Enter the first port number that Essbase Server tries to use to connect.

94

Configuring EPM System Products

EPM System Configurator Fields End Port

Description Enter the highest port number that Essbase Server can use to connect. Essbase uses at least two ports for each application. For a large number of applications, you need a larger port range.

Your Information

Full path to application location (ARBORPATH)

The location for applications. Note: Previous versions of Essbase used ARBORPATH to refer to the installation location. Upgrade Note! If you are upgrading from a previous release of Essbase, specify the same application location you used in the previous release.

Set the language to be used by Essbase (ESSLANG)

The ESSLANG variable is a locale definition. For example, to support American English, you can set ESSLANG to English_UnitedStates.Latin1@Binary. Verify the operating system locale setting on your computer and select the matching ESSLANG value. The ESSLANG setting for a computer must agree with the locale setting of the computers operating system. In addition, on a Windows machine, the ESSLANG value and the system locale must match the language of the Planning application that you plan to take offline. You must choose the correct ESSLANG setting for Essbase products to start successfully. The ESSLANG setting can affect the function of applications and databases. On Windows, if ESSLANG is already set on the computer (for example, if you have already installed Essbase, or if you are upgrading from a previous release), the current value is selected by default. On UNIX platforms, the ESSLANG setting defaults to English (Latin I) regardless of the setting in the operating system. For more details about ESSLANG, see ESSLANG Variable on page 95. For the full list of supported ESSLANG values, see Oracle Essbase Database Administrator's Guide. Upgrade Note! If you are upgrading from a previous release of Essbase, the ESSLANG value from the previous release displays by default, and you cannot change it.

Deploy Essbase in standalone mode

Select to use legacy security for Essbase Server instead of Shared Services security. This option is not available if you use the -forceRegistry option to start EPM System Configurator.

ESSLANG Variable
Each Essbase Server installation requires that you set an ESSLANG value. See the topic on managing file encoding in the Oracle Essbase Database Administrator's Guide. The default value for ESSLANG is English (Latin1). For examples of ESSLANG values for languages other than English, see the list of supported locales in the Unicode-mode applications topic in the Oracle Essbase Database Administrator's Guide. During configuration, EPM System Configurator writes the ESSLANG value that you specify to the Shared Services Registry and to the launch file used to start Essbase.

Using EPM System Configurator

95

For Administration Services and Provider Services, there is no prompt to specify the ESSLANG value; it is set to the default value "English_UnitedStates.Latin1@Binary." For Administration Services, the ESSLANG value is stored in HYPERION_HOME/products/essbase/eas/ server/OlapAdmin.properties; for Provider Services, it is stored in HYPERION_HOME/ products/Essbase/aps/bin/Essbase.properties.

Managing ESSLANG Settings


The ESSLANG environment variable on the Essbase Server computer must retain the locale value of an application for as long as that application is in use.
Note: If the ESSLANG variable is changed after applications are created on an Essbase Server

computer, those applications cannot be started. Clients also use locales. ESSLANG variables are optional for clients. If ESSLANG is not defined on a client, the locale specified for the operating system is used. Client and Essbase locale values must be the same for non-Unicode-mode clients and applications. For Unicode-mode applications, client and Essbase locale values can be different. To avoid possible database corruption, the ESSLANG locale specification must be the same on client and Essbase Server when:
l

The client is not Unicode-enabled A Unicode-enabled client saves an outline over an existing outline on a version of the Essbase Server that is not Unicode-enabled A Unicode-enabled client saves an outline to a non-Unicode application on a Unicodeenabled Essbase Server

The ESSLANG locale specifications on clients and Essbase Server computers can be different when a Unicode-enabled client views and updates an outline belonging to a Unicode-mode application. For products that use Essbase RTC in a non-English environment, you must set ESSLANG manually on the client.

Configuring and Starting an Additional Instance of Essbase Server


To configure an additional instance of Essbase Server on Windows:
1 2
During configuration with EPM System Configurator, select Essbase-n on the Task Selection Panel, where n is the instance that you want to configure. On the Essbase Server Configuration page, specify a unique agent port and port range for the additional instance of Essbase Server. The range of ports used by one Essbase Server instance must not overlap the range of ports used by another instance or any other products.

The port numbers for the additional instance of Essbase Server are stored in the essbase.cfg file for this installation. In addition, the setting InstanceID is created in the

96

Configuring EPM System Products

essbase.cfg file for this installation, so that each instance of Essbase Server has its own

log file directory. Each instance of Essbase Server has its own startup script. To start an additional instance of Essbase Server, use the startEssbase.cmd|.sh script for this installation.

PlanningSpecific Tasks (Optional)


Creating a cluster for Planning is optional because a default cluster is created for you when you configure the Planning database. Configure Planning clusters after you have configured and deployed Shared Services. Shared Services must be running.

Planning Cluster Management (Optional)


Select whether to create, edit, delete, activate, or reassociate a cluster.
A cluster is a name for a group of Planning applications and can contain one or many applications. Each application gets associated with a cluster when an application is created. You can designate a cluster as the active cluster during cluster creation or at any time by choosing Manage Planning Clusters in EPM System Configurator. You must configure the database before you can create or edit a cluster. The default cluster is created after you complete all the other Planning configuration tasks. To add a new Planning server to an existing configuration, run the Activate Cluster task from each Planning server machine. The following table describes options for Planning cluster configuration.
EPM System Configurator Fields Create Cluster Edit Cluster Delete Cluster Activate Cluster Description Your Information

Select Create Cluster, click Next, and then specify the cluster properties. See Planning Cluster Management Cluster Properties (Optional) on page 98. Select Edit Cluster, click Next, choose the cluster to edit, and then modify the cluster properties. See Edit Planning Cluster (Optional) on page 98. Select Delete Cluster, click Next, and then choose the cluster to delete. See Planning Cluster Management Cluster Properties (Optional) on page 98. Select Activate Cluster, click Next, and then choose the cluster to activate. See Planning Cluster Management Cluster Properties (Optional) on page 98. When you activate a cluster, only applications associated with that cluster are displayed in EPM Workspace.

Using EPM System Configurator

97

EPM System Configurator Fields Re-Associate Cluster and Application

Description

Your Information

Select Re-Associate Cluster and Application, click Next, and then choose the cluster and the application to associate. See Planning Cluster Management Cluster Properties (Optional) on page 98. Applications get associated with a cluster when an application is created, and that association can be modified by selecting Re-Associate Cluster and Application. This is useful, for example, if you decide that you want an application associated with a different server.

Planning Cluster Management Cluster Properties (Optional)


Choose from the following options, depending on your selection in the Planning Cluster
Management page:
l

If you selected Create Cluster, specify the following options: The following table describes options for creating Planning clusters.

EPM System Configurator Fields Cluster Name Web Tier Host Name

Description Specify a name for the cluster or accept the default. Enter the full name of the machine where you installed the Planning Web server component. Note: In a multiserver environment, this machine should be the load balancer, and in a single server environment, it is the same as the Planning server.

Your Information

Server Port Activate Cluster

Accept the default server port or make a change if necessary. The port number should be the port used for application server deployment. Select if you want to display only those applications in EPM Workspace that are associated with this cluster. If you want to see all applications in EPM Workspace, do not select this check box.

If you selected Edit Cluster, select the cluster to edit, click Next, and then edit the cluster properties. See Edit Planning Cluster (Optional) on page 98. If you selected Delete Cluster, select the clusters to delete. If you selected Activate Cluster, select the cluster to activate. If you selected Re-Associate Cluster and Application, select the cluster name, and then the application with which you want to associate it.

Edit Planning Cluster (Optional)


Edit the options for an existing cluster.
The following table describes options for editing Planning clusters.

98

Configuring EPM System Products

EPM System Configurator Fields Web Tier Host Name

Description Enter the full name of the machine where you installed the Planning Web server component. Note: In a multi-server environment, this machine should be the load balancer, and in a single server environment, it is the same as the Planning server.

Your Information

Server Port SSL Activate as Active Cluster

Accept the default server port or make a change if necessary. The port number should be the port used for application server deployment. Select to enable SSL (Secure Sockets Layer). Select to display the applications in EPM Workspace that are associated with this cluster.

Financial ManagementSpecific Tasks


You must run EPM System Configurator as an administrator to configure Financial Management.

Configure Financial Management DCOM


Specify the Distributed Component Object Model (DCOM) account information to
configure DCOM security. You must specify the Windows administrator under whose identity the application server processes are launched. Perform this task on the machines that host the Financial Management Web server tier and on the Services tier.
Note: You must run as a Domain or Local Administrator with Group Policies rights to configure

the DCOM user. All Financial Management application server processes are run under an administrator identity (the specified Windows admin user), so no other administrator is required to log on to the application server to start the application server processes. The following table describes options for Financial Management DCOM configuration.

Using EPM System Configurator

99

EPM System Configurator Fields Domain User

Description

Your Information

Specify the user name. By default, EPM System Configurator lists the user name for the user who is logged in and running EPM System Configurator. Note these limitations for the domain and user name:
l

A user name cannot duplicate any other user or group name of the computer being administered. A user name can contain up to 20 uppercase and lowercase letters. A user name cannot consist solely of periods ( . ) and spaces and cannot contain these special characters: " / \ [ ] : ; | = , +*?<>& Do not use a single quotation mark ( ) in a user name. A user with a single quotation mark in the user name cannot log on to Financial Management. You cannot use an IP address as a domain name when you configure the user account.

Password

Enter the password. The password can contain up to 14 characters and is case-sensitive. The system does not verify the password, so ensure that the password that you use is valid. Note: If the entries that you make require changing the local security policy on the system, you must log off and log on again to commit the changes.

Re-type Password Enable DCOM on this machine

Enter the password again to confirm it. Select to enable DCOM on this machine. This option is available for the Application services and Web tier installation of Financial Management. This option is not available if DCOM is already enabled on the computer. This option enables DCOM for the entire computer. Enabling DCOM makes possible the launching of servers and connecting to objects by remote clients for the machine. It also sets the DCOM Default Authentication level to None for the computer. The Enable DCOM step is required for Financial Management client components to communicate with Financial Management application server components when the application server is on a different computer. It also enables the Financial Management client and application server computers to be on different domains.

After you enter the Windows administrator information, EPM System Configurator performs these steps:
l

Creates the Windows admin user (DCOM user) on the local machine if the user does not exist. Adds the user to the local Administrators group. The Financial Management administrator user or group must be a member of the local Administrators group on each application server. Assigns these local security policies to the admin user: Act as part of the operating system and Log on as a batch job. These local security rights must be enabled for users on each Financial Management application server. Sets the DCOM Run as identity for all Financial Management application processes. Sets DCOM Launch permissions for users.

If the DCOM user password changes, or if you want to use a different DCOM user name and password, ensure that the user settings are valid and working, and then use EPM System
100 Configuring EPM System Products

Configurator to reenter the DCOM user name and password. Perform this task on the Web tier and on the Services tier for Financial Management.

Configure Financial Management Application Server


Specify the application server information, or click Next to accept the defaults.
The following table describes options for Financial Management application server configuration.
EPM System Configurator Fields Working Folder Description Your Information

Accept the default, or enter or browse to the path for the Server Working Folder. The Server Working folder stores system-generated files, such as reports. The default Server Working Folder location is HYPERION_HOME/products/FinancialManagement/Server Working Folder. Note: When you use multiple application servers, each server should have its own working folder. Application servers should not share working folders, because temporary files might be overwritten.

Max App Server Delay Max Data Sync Delay Creator Group

Accept the default value or enter the time interval in seconds between when a change is made to an application and when the change is visible to users accessing the application through another application server. Accept the default value or enter the time interval in seconds between when a change is made to data and when the change is visible to users accessing the data through another application server. Accept the default value or enter the Creator Group name. Only the users in the Application Creator Group can create Financial Management applications.

Administrator Group

Accept the default value or enter the Administrator Group name. Only the users in the Administrator Group can access administrative tasks. The Administrator Group must be a group that has already been defined in Shared Services. If you do not specify the Administrator Group, the DCOM user will have access to system administrative tasks.

Configure Financial Management Server/Cluster


Specify the names of the application servers that participate in the cluster.
An application server cluster is a set of application servers running the same application. Clustered application servers provide load balancing and failover capability and enable the servers to be transparently maintained while applications remain available for users. The following table describes options for Financial Management server/cluster configuration.

Using EPM System Configurator 101

EPM System Configurator Fields Defined Clusters

Description

Your Information

Select the cluster for which you want to specify servers. This list displays all clusters you have specified on any machine in the installation. You can also add, edit, or remove a cluster. EPM System creates a default cluster if none exist. Upgrade Note! This list displays all clusters that you configured in the previous release. If no clusters exist, EPM System Configurator creates a default cluster. You must use cluster names that are the same as the instance names that were used for Financial Management configuration in the previous release.

Servers in the Cluster Available Servers

The list displays all servers in the currently selected cluster. To remove a server from the list, select it and click Remove. Select the server that you want to include in the cluster, and click Add. The list displays all available servers. If there is only one server, it is listed here. Servers already in a cluster are not available and are not listed.

If you use multiple application servers connected to one database server, you must ensure that the system clocks on the application servers are synchronized. If the clocks are not synchronized, the data being viewed might not be current.
Note: The synchronization between Financial Management application servers is based on

system time. Changing the clock can affect this synchronization. For the time change to and from Daylight Savings Time, Oracle recommends that you stop the servers before the time change and restart them afterward.

Register Financial Management Server/Cluster


Register the server or cluster before accessing applications.
You can perform this task on each machine in the installation. Specify the server or cluster you want this Web application to communicate with. The following table describes options for Financial Management server/cluster registration.
EPM System Configurator Fields Available Servers/Cluster Description Select the server or cluster that you want to register and click Add. This list displays all the defined clusters and individual servers. Registered Servers/Cluster To remove a server or cluster from the list to register, select it and click Remove. This list displays registered servers or clusters. Your Information

102 Configuring EPM System Products

Configure Financial Management Web Server


Select the components that you want to enable as Web applications in IIS or click Next to
accept the default. The following table describes options for Financial Management Web server configuration.
EPM System Configurator Fields Configure IIS for Financial Management Web Application Configure IIS to Enable Smart View Provider Configure IIS to Enable Lifecycle Management Description Select to enable Financial Management as a Web application in IIS, and then specify the options for the Financial Management Web server. See Configure Financial Management Web Application on page 103. Select to enable Smart View as a Web application in IIS, and then specify the options for the Smart View Web server. See Financial Management Enable Smart View Provider on page 104. Select to enable Lifecycle Management as a Web application in IIS. Your Information

Configure Financial Management Web Application


Configure the Web server for Financial Management or click Next to accept the defaults.
The following table describes options for Financial Management Web application configuration.
EPM System Configurator Fields Web Server Installation Directory Description Accept the default or enter or browse to the path for the Financial Management Web installation directory. Note: The default location is the directory in which the Web components were installed, for example: HYPERION_HOME/products/FinancialManagement/Web/HFM. Virtual Directory Name Web Session Timeout Advanced Options Accept the default or enter the virtual directory name; for example: HFM. Accept the default or specify the timeout in minutes. Click Advanced Options to specify additional options for the Web server configuration. See Financial Management Web Application Advanced Options on page 103. Your Information

Financial Management Web Application Advanced Options Specify additional options for the Financial Management Web server.
The following table describes advanced options for Financial Management Web application configuration.
Using EPM System Configurator 103

EPM System Configurator Fields File Transfer Directory

Description

Your Information

Browse to the path for the directory for the load, extract, and log files, or use the default location; for example, HYPERION_HOME/products/FinancialManagement/Web/HFM/FileTransfer. The File Transfer directory should be located outside of the virtual directory. If it is located under the virtual directory, you should set No Execute rights on the File Transfer directory. You must create a file transfer directory for load and extract log files and temporary files. When you specify the file transfer directory, the system performs these steps:
l l

Creates the file transfer directory, if it does not exist Assigns the IIS users Windows permissions of Read, Write, and Execute

Max Upload File Size

Enter a maximum size for loading Web files. If you use IIS 6.0, you can set the ASP file size properties for loading and extracting files on the Web. Oracle recommends that you use the default file size properties unless you experience problems during loading and extracting. However, if you load or extract huge files and send large amounts of data to the browser and experience errors, you can change the file size settings. For example, if you load large files, you might receive a 403 error message if the maximum upload file size is set too low. In this case, you must increase the maximum file size. You enter the file size in bytes, so if you expect to load files of 200 megabytes, you change the setting for maximum upload file size to 200,000,000 bytes.

Response Buffer Size

Enter a maximum size for extracting Web files.

If you run IIS 5.0 Isolation mode in IIS 6.0 on Windows 2003, after you create Web directories and set ASP properties, you must manually set two additional IIS properties for the application protection and authentication level. See Configuring Settings for IIS 5.0 Isolation Mode (Optional) on page 157.

Financial Management Enable Smart View Provider


Configure the Web server for Smart View.
The following table describes options for Financial Management Smart View Provider configuration.

EPM System Configurator Fields Web Server Installation Directory

Description Enter the location in which Smart View was installed or use the default location. Note: The default location is HYPERION_HOME/products/FinancialManagement/ Web/HFMOfficeProvider. Enter the virtual directory name for Smart View or use the default virtual directory. The default directory name is HFMOfficeProvider.

Your Information

Virtual Directory Name

104 Configuring EPM System Products

EPM System Configurator Fields Web Session Timeout

Description Accept the default, or enter the Web session timeout value in seconds. Note: The default session timeout is 360 seconds. You should set the timeout option to a length of time appropriate for your Smart View sessions.

Your Information

Advanced Options

Click to specify advanced options for Smart View configuration. See Smart View Web Server Configuration Advanced Options on page 105.

Smart View Web Server Configuration Advanced Options Specify additional options for the Smart View Web server configuration.
The following table describes advanced options for Smart View Web server configuration.

EPM System Configurator Fields Enable HTTP Compression

Description Specify whether to enable compression for communication between the Web browser and the Web application. By default, compression is on.

Your Information

Enable proxy server connection keep alive Keep Alive Interval (in seconds) Always warn when client version is newer Always force client to upgrade

If you use a proxy server between the Web server and client, select this option and set a time interval, in seconds, for the connection. If you use a proxy server between the Web server and client, select this option and set a time interval, in seconds, for the connection. Select to warn of a newer add-in version. Select to upgrade to the latest add-in version to ensure client and server version compatibility.

Configure Financial Management Data Source for Extended Analytics


Optional: Specify DSN information for Extended Analytics.
If you do not want to specify Data Source Name (DSN) information for Extended Analytics, skip this task. This task is available for the services tier installation of Financial Management. The Extended Analytics feature enables you to use Essbase to analyze data and produce reports. You use a data source name (DSN) to specify the relational database destination for Extended Analytics. The following table describes options for Financial Management Extended Analytics configuration.
Using EPM System Configurator 105

EPM System Configurator Fields DSN Name

Description

Your Information

Enter the data source name. (The UDL must already be created.)

DSN Path

Enter or browse for the data source path. The DSN Path is the UDL for Extended Analytics. You must have already created this UDL file. You can encrypt this UDL file if you name it with the extension .hfmudl. See Encrypting UDL Files on page 245.

Index Tablespace

Optional: To specify the database tablespaces in which the Financial Management data tables and indexes are created, select the index location. Note: For Oracle and IBM DB2 SMS, you can specify only a data tablespace; index tablespaces are not used.

Data Tablespace

Optional: To specify the database tablespaces in which the Financial Management data tables and indexes are created, select the data table location.

To select a different UDL file after initial configuration, create the UDL file, rerun EPM System Configurator, select Configure Financial Management for Extended Analytics, and specify the new DSN. You should not use the relational database and UDL file for Extended Analytics that you use for your Financial Management applications. You should create a database for the exported star schema and data, and a UDL file that points to the database.
Note: When you use multiple servers with the Extended Analytics feature, you must set up each

application server so that these elements are the same on all servers: Clock Setting, Data Source, and UDL File.

Reporting and AnalysisSpecific Tasks


Configure Reporting and Analysis services.

Reporting and Analysis Service Configuration


Specify the following options to configure Reporting and Analysis services, or click Next to
accept the defaults. The following table describes options for Reporting and Analysis service configuration.
EPM System Configurator Fields Service Name/Port Range Description For each listed Reporting and Analysis Interactive Reporting service, specify the range of ports to use, or click Next to keep the default port ranges. Your Information

106 Configuring EPM System Products

Strategic FinanceSpecific Tasks


During configuration, EPM System Configurator creates a default instance for Strategic Finance.

Strategic Finance Configuration


Specify the location of the Strategic Finance data directory, or click Next to accept the default.
The following table describes options for Strategic Finance configuration.

EPM System Configurator Fields Data Directory

Description The location for Strategic Finance data. Upgrade Note! If you are upgrading from a previous release of Strategic Finance, specify the location of the data directory for the previous release.

Your Information

When you are prompted for the Directory for Server data files, do not specify the Strategic Finance data directory in a file share directory on a remote server or in an NAS (Network Attached Storage) area. Specify the data directory as a local hard drive or SAN (Storage Area Network array).

Configure Strategic Finance Web Server


Specify the following options to configure the Strategic Finance Web server:
The following table describes options for Strategic Finance Web server configuration.

EPM System Configurator Fields Enable Web Service Select Strategic Finance Server

Description Select to activate the Strategic Finance Web services Application Programming Interface for the Web. This must be enabled for the interface to FDM to work. Accept the default, or specify the Strategic Finance server to associate with.

Your Information

FDMSpecific Configuration Tasks


This task updates the Shared Services Registry with information about FDM and registers FDM with Shared Services; however, no pages appear, and you do not have to enter any information. See the Oracle Hyperion Financial Data Quality Management Configuration Guide for additional information about configuring FDM.
Using EPM System Configurator 107

Configure FDM Server


Select Configure FDM Server from the Task Selection page and proceed through EPM System
Configurator.

Performing Silent Configurations


Silent configurations automate the configuration process so that you can configure EPM System products on multiple computers without manually specifying configuration settings on each machine. To enable silent configurations, record your configuration settings in a response file. You can then run a silent configuration from the command line, using the configuration options that were saved in the response file.

To record configuration settings and run a silent configuration:


1 2
Navigate to the directory that contains EPM System Configurator. By default, the directory is HYPERION_HOME/common/config/9.5.0.0. From a command line prompt, enter configtool.bat record filename or ./ configtool.sh record filename, where filename includes an absolute path or file name.

The file is saved in XML format, but you do not have to save the file with a .xml extension. EPM System Configurator launches. If you do not specify a file name, EPM System Configurator creates the file for you: HYPERION_HOME/common/config/9.5.0.0/configResponse.xml.

Proceed through the EPM System Configurator, specifying the options that you want to record.
Note: When you are recording silent configurations, you can proceed through EPM System

Configurator only one time. (You cannot select go back to the Product Selection Panel to continue with more configuration tasks.) If you return to the Task Selection Panel, the response file is rerecorded. Configuration options are recorded in the response file, which is in XML format. Passwords are saved in encrypted format in the response file. You are now ready to configure products in silent mode.

4 5

Copy the response file to the machine on which you configure products. You can also copy the file to a network drive that is accessible from the machines you want to configure. From the command line, enter a command:
configtool.bat -silent filename or ./configtool.sh -silent filename.

The configuration runs in the background.

108 Configuring EPM System Products

Note: Silent response files are not compatible between EPM System Release 11.1.1.0, Release

11.1.1.1, and 11.1.1.2. If you created silent response files for use with EPM System Release 11.1.1.0 or 11.1.1.1, you must re-create them for use with EPM System Release 11.1.1.2. If you are applying the maintenance release to go to Release 11.1.1.3, you need to re-create silent response files only if you are installing ERP Integrator. You can modify the response file later to change configuration options.
Tip: To change the password later, open the response file in a text editor, enter the password in clear text, and change the <encrypted> parameter to false. The next time you perform

a silent configuration using this response file, EPM System Configurator encrypts the password and reverts the <encrypted> parameter to true.

Setting Up the Shared Services Registry Without Installing Shared Services


If you want to install Essbase in standalone mode (not using Shared Services), you can skip the installation for Shared Services. However, you must still configure the Shared Services Registry database. To configure the Shared Services Registry database without installing Shared Services, you run EPM System Configurator from the command line using the forceRegistry option. This option forces the Shared Services and Registry Database Configuration page to display during configuration so you can enter database details for the Shared Services Registry. EPM System Configurator populates the database with tables for the Shared Services Registry, but not for Shared Services.

To configure the Shared Services Registry without installing Shared Services:


1
Start EPM System Configurator from the command line, including the forceRegistry option:
l

From a Windows console, change to HYPERION_HOME/common/config/ version_number, and then enter configtool.bat forceRegistry. On UNIX, change to HYPERION_HOME/common/config/version_number and then type ./configtool.sh forceRegistry.

The forceRegistry option also works with EPM System Configurator in silent mode and in console mode, for example:
configtool.bat|.sh -forceRegistry -record configtool.bat|.sh -forceRegistry -silent configtool.bat|.sh -forceRegistry -console

Proceed through the configuration, entering the database details for the Shared Services Registry.

Setting Up the Shared Services Registry Without Installing Shared Services 109

What Happens During Configuration


During product configuration, EPM System Configurator completes these actions:
l

Performs the configuration tasks you selected. Configures help for products in EPM Workspace. Starts all the services on this machine. Configures each product to start as a Windows service, if you select this option on the Common Settings page during configuration. An exception is Integration Services, which is configured to start as a Windows service during installation. Creates a default Shared Services Administrator role in Native Directory when you configure Shared Services. This is the only preprovisioned user created. Subsequently, when you use EPM System Configurator to register products with Shared Services, the Shared Services Administrator role is provisioned with the product administrator role. Make sure to change this password right away in the Shared Services Console.

Troubleshooting Configuration
All configuration warnings and errors are logged as follows:
HYPERION_HOME/logs/config

If you encounter errors, perform these tasks:


l

Configure products individually. See the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Troubleshooting Guide for information about configuration checks, debugging using logs, troubleshooting methodology, and solutions to common configuration issues.

110 Configuring EPM System Products

5
In This Chapter

Starting and Stopping EPM System Products

Using a Single Script to Start Services................................................................. 111 Summary List of Services and Processes .............................................................. 112 Services and Processes ................................................................................. 113 Launching Clients ........................................................................................ 133

This chapter identifies how to start EPM System products and lists them in the order in which Oracle recommends that they be started. This chapter also provides default URLs for EPM System products. Before you start any services or processes, start all databases used as repositories.
Note: Some services or processes take longer than others to start, and startup times may vary

by computer. EPM System Installer creates Windows services using the local system account. Before you start the services, change them to use the appropriate domain account.

Using a Single Script to Start Services


EPM System Installer installs a single start script in HYPERION_HOME/products/bin, called start.bat|sh. Running the single start script on a machine in your EPM System deployment starts all EPM System services installed on that machine.
Note: Hyperion Financial Management - Management Service" must be started manually.

The single start script works by calling the individual start scripts for every product in the recommended startup order, specified in Summary List of Services and Processes on page 112. Before you can use a service in this list, services preceding it in the list must be started. When you use the single start script, some services may start before services they depend on start (because startup times vary). When this happens, you may need to wait to use some services while other services finish initializing.

Using a Single Script to Start Services 111

After running the single start script, you can run EPM System Diagnostics to determine which services on a machine are running. See Chapter 6, Validating the Installation. Wait at least two minutes after running the single start script before running EPM System Diagnostics, to allow services enough time to start. A single stop script, stop.bat|sh is also installed in HYPERION_HOME/products/bin. Running the stop script on a machine in your EPM System deployment stops all EPM System products on that machine.
Note: On WebLogic Server, batch files have a .cmd extension instead of a .bat extension.

Summary List of Services and Processes


The following EPM System product services and processes are listed below in their recommended startup order. 1. Databases for repositories. 2. Any corporate user directories that you plan to configure for use with Shared Services. 3. Shared Services OpenLDAP, or Oracle Internet Directory, depending on which is used as Shared Services Native Directory. 4. Shared Services application server 5. Oracle's Hyperion Remote Authentication Module 6. EPM Workspace Agent (CMC Agent) 7. EPM Workspace Web server 8. Performance Management Architect Services 9. Essbase Server 10. Administration Services application server 11. Smart Search Command Line Utility application server 12. Integration Services Server 13. Essbase Studio Server 14. Provider Services application server 15. Reporting and Analysis (in any order): a. Financial Reporting Services b. Web Analysis application server 16. Remaining services or processes (in any order):
l

Performance Management Architect application server Performance Management Architect Data Synchronizer application server Financial Reporting application server Calculation Manager application server

112 Starting and Stopping EPM System Products

Planning application server Financial Management service Strategic Finance service Performance Scorecard application server Performance Scorecard Alerter application server Profitability and Cost Management application server Data Relationship Management services FDM Task Manager service Hyperion ERPI - Web Application

17. EPM Workspace application server

Services and Processes


The services and processes discussed in this topic are listed in the order in which Oracle recommends that they be started.

Databases for Repositories


Databases for repositories.

Corporate User Directories


Any corporate user directories that you plan to configure for use with Shared Services. See the vendor documentation for startup instructions.

Shared Services OpenLDAP or Oracle Internet Directory


Note: See Oracle Internet Directory documentation for more information.

The following table describes the services and processes for Shared Services OpenLDAP.
Table 15

Shared Services OpenLDAP Service/Process Details NA OpenLDAP-slapd Hyperion Foundation OpenLDAP

Information Type Windows Start Menu Command Registered Service Name Display Name in Windows Services Control Panel

Services and Processes 113

Information Type Description Windows Startup Script UNIX Startup Script Windows Stop Script UNIX Stop Script

Details Provides support to access the Shared Services OpenLDAP repository


HYPERION_HOME/products/Foundation/openLDAP/startService.bat HYPERION_HOME/products/Foundation/openLDAP/startOpenLDAP.sh HYPERION_HOME/products/Foundation/openLDAP/stopService.bat HYPERION_HOME/products/Foundation/openLDAP/stopOpenLDAP.sh

Shared Services Application Server


The following table describes the services and processes for the Shared Services application server.
Table 16

Shared Services Application Server Services and Processes Details Select Start, then Programs, then Oracle EPM System, then Foundation Services, and then Start Shared Services HyS9Shared Services Hyperion Foundation Shared Services - Web Application

Information Type Windows Start Menu Command Registered Service Name Display Name in Windows Services Control Panel Description Windows Startup Script UNIX Startup Script Windows Stop Script UNIX Stop Script

Hyperion Shared Services that support Hyperion applications, including authentication, user provisioning, task flow management, data and metadata synchronization
HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/startSharedServices9. bat HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/startSharedServices9. sh HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/stopSharedServices9. bat HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/stopSharedServices9. sh

Stopping Shared Services on WebLogic Server


On WebLogic Server, if a message that suggests using the FORCESHUTDOWN command is displayed, use the FORCESHUTDOWN command to stop Shared Services server.

114 Starting and Stopping EPM System Products

To stop Shared Services server on WebLogic Server using the FORCESHUTDOWN


command:

1 2 3

In a text editor, open the stop script. In the file, find SHUTDOWN, and replace it with FORCESHUTDOWN. Save and execute the file.

Starting and Stopping Remote Authentication Module


Use Remote Authentication Module in a UNIX environment when you are using NTLM for authentication. To start and stop Remote Authentication Module, use startHRAM.bat|sh and stopHRAM.bat|sh, in HYPERION_HOME/products/Foundation/server/scripts.

EPM Workspace Agent (CMC Agent)


The following table describes the services and processes for the EPM Workspace Agent.
Table 17

EPM Workspace Agent: Configuration and Monitoring Console Details Select Start, then Programs, then Oracle EPM System, then Workspace, and then Start Workspace Agent Services. HyS9Core1 Hyperion Workspace - Agent Service

Information Type Windows Start Menu Command Registered Service Name Display Name in Windows Services Control Panel Description Windows Startup Script UNIX Startup Script Windows Stop Script UNIX Stop Script

HyS9Core1, Provides service infrastructure to run services locally


HYPERION_HOME/common/workspacert/9.5.0.0/bin/startAgent.bat HYPERION_HOME/common/workspacert/9.5.0.0/bin/startAgent.sh HYPERION_HOME/common/workspacert/9.5.0.0/bin/stopAgent.bat HYPERION_HOME/common/workspacert/9.5.0.0/bin/stopAgent.sh

Services and Processes Started with EPM Workspace Agent


When the EPM Workspace Agent is started, these additional services and processes are started, in the following order: 1. EPM Workspace common processes and Interactive Reporting process. 2. Annotation Service The following table describes the services and processes for the Annotation Service.
Services and Processes 115

Table 18

Annotation Service Details HyS9Annotation Hyperion Annotation Server HyS9Annotation - Provides Annotation support for Hyperion products.

Information Type Registered Service Name Display Name in Windows Services Control Panel Description

EPM Workspace UI (CMC UI)


The following table describes the services and processes for the EPM Workspace user interface.
Table 19

EPM Workspace UI: Configuration and Monitoring Console Details Select Start, then Programs, then Oracle EPM System, then Workspace, then Utilities and Administration, and then Start Workspace Agent UI
HYPERION_HOME/commmon/workspacert/9.5.0.0/bin/startUI.bat

Information Type Windows Start Menu Command Windows Startup Script Windows Stop Script UNIX Startup Script UNIX Startup Script UNIX Stop Script

HYPERION_HOME/commmon/workspacert/9.5.0.0/bin/stopUI.bat

HYPERION_HOME/commmon/workspacert/9.5.0.0/bin/startUI.sh HYPERION_HOME/commmon/workspacert/9.5.0.0/bin/startUI.sh HYPERION_HOME/commmon/workspacert/9.5.0.0/bin/stopUI.sh

EPM Workspace Web Server


The following table describes the services and processes for the EPM Workspace Web server.
Table 20

EPM Workspace Web Server Services and Processes Details


l l l

Information Type Registered Service Name

Embedded Java Container: HyS9Apache2 IIS: IISADMIN IHS 6.1: IBMHTTPServer6.1 Embedded Java Container: Hyperion Apache 2.0 IIS: IIS Admin Service IHS 6.1: IBM HTTP Server 6.1

Display Name in Windows Services Control Panel

l l l

116 Starting and Stopping EPM System Products

Information Type Description

Details
l l

Embedded Java Container: Apache IIS: Enables this server to administer Web and FTP services. If this service is stopped, the server will be unable to run Web, FTP, NNTP, or SMTP sites or configure IIS. If this service is disabled, any services that explicitly depend on it will fail to start. IHS 6.1: IBM_HTTP_Server

Windows Startup Script (Embedded Java Container only) UNIX Startup Script (Embedded Java Container only) Windows Stop Script (Embedded Java Container only) UNIX Stop Script (Embedded Java Container only)

HYPERION_HOME/common/httpServers/Apache/2.0.59/bin/Apache.exe

HYPERION_HOME/common/httpServers/Apache/2.0.59/bin/apachectl {start|restart}

NA

HYPERION_HOME/common/httpServers/Apache/2.0.59/bin/apachectl stop

Performance Management Architect Services


The following table describes the services and processes for the Performance Management Architect services.
Table 21

Performance Management Architect Services Details Select Start, then Programs, then Oracle EPM System, then Foundation Services, then Performance Management Architect, and then Start Dimension Server Process Manager: HyS9BPMA_ProcessManager Process Manager automatically starts the following services:
l l l l

Information Type Windows Start Menu Command Registered Service Name

Engine Manager: HyS9BPMA_EngineManager Job Manager: HyS9BPMA_JobManager Event Manager: HyS9BPMA_EventManager .NET JNI Bridge: HyS9BPMA_NetJNIBridge

Services and Processes 117

Information Type Display Name in Windows Services Control Panel

Details Process Manager: Hyperion EPM Architect - Process Manager Process Manager automatically starts the following services:
l l l l

Engine Manager: Hyperion EPM Architect - Engine Manager Job Manager: Hyperion BPM Architect - Job Manager Event Manager: Hyperion BPM Architect - Event Manager .NET JNI Bridge: Hyperion EPM Architect - .NET JNI Bridge 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. 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). Job Manager: Manages long-running tasks performed by EPM Architect. Event Manager: Distributes event messages between the various server processes of EPM Architect. .NET JNI Bridge: Acts as a bridge between .NET process and CSS

Description

l l l

Windows Startup Script UNIX Startup Script Windows Stop Script UNIX Stop Script

NA NA NA NA

For information on additional Performance Management Architect services, see Performance Management Architect Application Server on page 125 and Performance Management Architect Data Synchronizer Application Server on page 125. The following table describes the services and processes for the Performance Management Architect Web services.
Table 22

Performance Management Architect Web Services Details IISAdmin IIS Admin Service Enables this server to administer Web and FTP services. If this service is stopped, the server will be unable to run Web, FTP, NNTP, or SMTP sites or configure IIS. If this service is disabled, any services that explicitly depend on it will fail to start.

Information Type Registered Service Name Display Name in Windows Services Control Panel Description

118 Starting and Stopping EPM System Products

Essbase Server
The following table describes the services and processes for the Essbase Server services.
Table 23

Essbase Server Services and Processes Details Select Start, then Programs, then Oracle EPM System, then Essbase, then Essbase Server, and then Essbase This command launches startEssbase.cmd. Hys9ESBAgent11.1.1_servername Hyperion Essbase Services 11.1.1 - ServiceName

Information Type Windows Start Menu Command Registered Service Name Display Name in Windows Services Control Panel Description Windows Startup Script

Essbase Server Service


l l l

Essbase Server ESSBASEPATH/bin/startEssbase.cmd ESSCMD ESSBASEPATH/bin/startEsscmd.cmd essmsh ESSBASEPATH/bin/startMaxl.cmd

All the scripts call setEssbaseEnv.cmd to set up ESSBASEPATH, ARBORPATH, and PATH before starting. Each instance of Essbase Server has its own startup script. UNIX Startup Script
l l l

Essbase Server ESSBASEPATH/bin/startEssbase.sh ESSCMD ESSBASEPATH/bin/startEsscmd.sh essmsh ESSBASEPATH/bin/startMaxl.sh

All the scripts call hyperionenv.doc to set up ESSBASEPATH, ARBORPATH, and PATH before starting. Each instance of Essbase Server has its own startup script. Windows Stop Script UNIX Stop Script NA NA

Start Essbase Server using the Start menu command or startEssbase.cmd to ensure that environment variables are set. When starting Essbase for the first time, you must enter a company name, user name and password. No password is required on subsequent startups.
Note: If you installed an additional instance of Essbase, startEssbase.sh is located in HYPERION_HOME/products/Essbase-n/EssbaseServer/bin. Launch the start

script from this location to launch this instance of Essbase. When multiple instances of Essbase Server are installed on one computer, you must specify a unique port number for each instance. By default, the first instance of Essbase Server uses port number 1423, which is specified in EPM System Configurator. Specify a different port number
Services and Processes 119

for the second instance during configuration with EPM System Configurator. You connect to subsequent installations by specifying the machine name and the agent port number, in the form: machineName:agentPort when connecting. Stopping Essbase Server can take some time, depending on how many Essbase applications are running on the server. To stop Essbase Server, you need Administrator permissions. You can use any of the following methods:
l

Administration Services Console: In the Enterprise View, right-click the Essbase Server node and then select Stop. MaxL: Use the alter system shutdown; command. Agent: If you started Agent in the foreground, you can use the quit command. ESSCMD: Use the SHUTDOWNSERVER command. When running Essbase Server as a Windows service, do not stop the service from Windows Services Control Panel.

Caution!

For more information about stopping Essbase Server, see the Oracle Essbase Database Administrator's Guide and the Oracle Essbase Technical Reference.

Administration Services Application Server


The following table describes the services and processes for the Administration Services application server.
Table 24

Administration Services Application Server Service/Process Details Select Start, then Programs, then Oracle EPM System, then Essbase, then Administration Services, and then Start Administration Services Hys9eas Hyperion Administration Services - Web Application

Information Type Windows Start Menu Command Registered Service Name Display Name in Windows Services Control Panel Description Windows Startup Script UNIX Startup Script Windows Stop Script UNIX Stop Script

Controls the running of an Applications Server


HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/starteas.bat

HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/starteas.sh HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/stopeas.bat HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/stopeas.sh

120 Starting and Stopping EPM System Products

Note: When you start Administration Server, ARBORPATH is set internally to: EAS_HOME/ server. This internal setting overrides (but does not replace) the value for the ARBORPATH system environment variable, if it is set on the same computer. EAS_HOME is

the directory where you install Administration Services.

Smart Search Command Line Utility Application Server


The following table describes the services and processes for the Smart Search Command Line Utility application server.
Table 25

Smart Search Command Line Utility Application Server Details Select Start, then Programs, then Oracle EPM System, then Essbase, then Smart Search, and then Start Essbase Provider (Embedded Java Container) HyS9SmartSearch Hyperion Smart Search Web Application HyS9SmartSearchControls the running of an Applications Server
HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/ startSmartSearch.bat

Information Type Windows Start Menu Command Registered Service Name Display Name in Windows Services Control Panel Description Windows Startup Script UNIX Startup Script Windows Stop Script UNIX Stop Script

NA
HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/ stopSmartSearch.bat

NA

Integration Services Server


The following table describes the services and processes for the Integration Services server.
Table 26

Integration Services Server Service/Process Details Select Start, then Programs, then Oracle EPM System, then Essbase, then Integration Services, and then Server1 Hyperion Integration Services Hyperion Integration Services

Information Type Windows Start Menu Command Registered Service Name Display Name in Windows Services Control Panel Description

Hyperion Integration Services

Services and Processes 121

Information Type Windows Startup Script UNIX Startup Script

Details
HYPERION_HOME/products/Essbase/eis/server/bin/startup.bat

$HOME/Hyperion/products/Essbase/eis/server/ais_start

Note: Running ais_start automatically configures the environment by calling is.sh and starts Integration Services. Windows Stop Script UNIX Stop Script
1For

HYPERION_HOME/products/Essbase/eis/server/bin/shutdownEIS.bat $HOME/Hyperion/products/Essbase/eis/server/ais_stop

more information on starting and stopping Integration Services Server from the command line, on other startup switches for the

olapisvr command, and on using the ais.cfg file, see the Essbase Integration Services System Administrator's Guide.

Essbase Studio Server


The following table describes the services and processes for the Essbase Studio server.
Table 27

Essbase Studio Server Details Select Start, then Programs, then Oracle EPM System, then Essbase, then Essbase Studio, and then Start Server NA NA NA
HYPERION_HOME/products/Essbase/EssbaseStudio/Server/startServer.bat HYPERION_HOME/products/Essbase/EssbaseStudio/Server/startServer.sh HYPERION_HOME/products/Essbase/EssbaseStudio/Server/stopServer.bat HYPERION_HOME/products/Essbase/EssbaseStudio/Server/stopServer.sh

Information Type Windows Start Menu Command Registered Service Name Display Name in Windows Services Control Panel Description Windows Startup Script UNIX Startup Script Windows Stop Script UNIX Stop Script

Provider Services Application Server


The following table describes the services and processes for the Provider Services application server.
Table 28

Provider Services Application Server Services and Processes Details Select Start, then Programs, then Oracle EPM System, then Essbase, then Provider Services, and then Start Provider Services

Information Type Windows Start Menu Command

122 Starting and Stopping EPM System Products

Information Type Registered Service Name Display Name in Windows Services Control Panel Description Windows Startup Script UNIX Startup Script Windows Stop Script UNIX Stop Script

Details HyS9aps Hyperion Provider Services - Web Application

Controls the running of an Applications Server


HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/startaps.bat

HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/startaps.sh HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/stopaps.bat HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/stopaps.sh

Reporting and Analysis Services and Processes


Financial Reporting
The following table describes the services and processes for Financial Reporting.
Table 29

Financial Reporting Services and Processes Details Select Start, then Programs, then Oracle EPM System, then Reporting and Analysis, and then Start Financial Reporting

Information Type Windows Start Menu Command Registered Service Name

l l l l

Hyperion Financial Reporting Java RMI Registry: HyS9FRRMI Hyperion Financial Reporting Print Server: HyS9FRPrint Hyperion Financial Reporting Report Server: HyS9FRReport Hyperion Financial Reporting Scheduler Server: HyS9FRSched Hyperion Financial Reporting - Java RMI Registry Hyperion Financial Reporting - Print Server Hyperion Financial Reporting - Report Server Hyperion Financial Reporting - Scheduler Server

Display Name in Windows Services Control Panel

l l l l

Services and Processes 123

Information Type Description

Details Hyperion Financial Reporting RMI Registry Service: HyS9FRRMI - Provides a Java RMI Registry for Financial Reporting Hyperion Financial Reporting Print Server: HyS9FRPrint - Generates PDF, batch, and scheduled job output for Financial Reporting Hyperion Financial Reporting Report Server: HyS9FRReport - Generates and formats reports and books, including specified calculations for Financial Reporting Hyperion Financial Reporting Scheduler Server: HyS9FRSched - Responds to scheduled batch requests for Financial Reporting

l l

Windows Startup Script UNIX Startup Script Windows Stop Script UNIX Stop Script

HYPERION_HOME/deployments/AppServerNameAndVersion/bin/startFinancialReporting.bat

HYPERION_HOME/products/biplus/bin/freporting start

HYPERION_HOME/deployments/AppServerNameAndVersion/bin/stopFinancialReporting.bat

HYPERION_HOME/products/biplus/bin/freporting stop

Web Analysis Application Server


The following table describes the services and processes for the Web Analysis application server.
Table 30

Web Analysis Application Server Services and Processes Details Select Start, then Programs, then Oracle EPM System, then Reporting and Analysis, and then Start Web Analysis HyS9WebAnalysis Hyperion Web Analysis - Web Application HyS9WebAnalysis - Hyperion Web Analysis - Web Application web application for AppServerNameAndVersion.
HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/startWebAnalysis.bat

Information Type Windows Start Menu Command Registered Service Name Display Name in Windows Control Description Windows Startup Script UNIX Startup Script Windows Stop Script UNIX Stop Script

HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/startWebAnalysis.sh HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/stopWebAnalysis.bat HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/stopWebAnalysis.sh

Remaining Services or Processes


The following application server services or processes can be started in any order.
124 Starting and Stopping EPM System Products

Performance Management Architect Application Server


The following table describes the services and processes for the Performance Management Architect application server.
Table 31

Performance Management Architect Application Server Services and Processes Details Select Start, then Programs, then Oracle EPM System, then Foundation Services, then Performance Management Architect, and then Start Performance Management Architect Web HyS9EPMAWebTier Hyperion EPM Architect - Web Application

Information Type Windows Start Menu Command Registered Service Name Display Name in Windows Services Control Panel Description Windows Startup Script UNIX Startup Script Windows Stop Script UNIX Stop Script

Hyperion EPM Architect Web


HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/startEPMAWebServer. bat HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/startEPMAWebServer. sh HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/stopEPMAWebServer. bat HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/stopEPMAWebServer.sh

Performance Management Architect Data Synchronizer Application Server


The following table describes the services and processes for the Performance Management Architect Data Synchronizer application server.
Table 32

Performance Management Architect Data Synchronizer Application Server Services Details Select Start, then Programs, then Oracle EPM System, then Foundation Services, then Performance Management Architect, and then Start Data Synchronizer HyS9EPMADataSynchronizer Hyperion EPM Architect Data Synchronization - Web Application

Information Type Windows Start Menu Command Registered Service Name Display Name in Windows Services Control Panel Description Windows Startup Script

Hyperion EPM Architect Data Synchronizations Engine


HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/ startEPMADataSynchronizer.bat

Services and Processes 125

Information Type UNIX Startup Script Windows Stop Script UNIX Stop Script

Details
HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/ startEPMADataSynchronizer.sh HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/ stopEPMADataSynchronizer.bat HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/ stopEPMADataSynchronizer.sh

Financial Reporting Application Server


The following table describes the services and processes for the Financial Reporting application server.
Table 33

Financial Reporting Application Server Services and Processes Details Select Start, then Programs, then Oracle EPM System, then Reporting and Analysis, and then Start Financial Reporting HyS9FRWeb Hyperion Financial Reporting - Web application

Information Type Windows Start Menu Command Registered Service Name Display Name in Windows Services Control Panel Description Windows Startup Script UNIX Startup Script Windows Stop Script UNIX Stop Script

HyS9FRWeb - Provides a Workspace module for Financial Reporting


HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/ startFinancialReporting.bat HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/ startFinancialReporting.sh HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/ stopFinancialReporting.bat HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/ stopFinancialReporting.sh

Calculation Manager
The following table describes the services and processes for Calculation Manager.
Table 34

Calculation Manager Services and Processes Details Select Start, then Programs, then Oracle EPM System, then Calculation Manager, and then Start CALC

Information Type Windows Start Menu Command

126 Starting and Stopping EPM System Products

Information Type Registered Service Name Display Name in Windows Services Control Panel Description Windows Startup Script UNIX Startup Script Windows Stop Script UNIX Stop Script

Details HyS9CALC Hyperion CALC Manager - Web Application Provide access service to CALC Manager Web Server
HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/startcalcmgr.bat HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/startcalcmgr.sh HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/stopcalcmgr.bat HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/stopcalcmgr.sh

Planning Application Server


The following table describes the services and processes for the Planning application server.
Table 35

Planning Application Server Services and Processes Details Select Start, then Programs, then Oracle EPM System, then Planning, and then Start Planning HyS9Planning Hyperion Planning - Web Application

Information Type Windows Start Menu Command Registered Service Name Display Name in Windows Services Control Panel Description Windows Startup Script UNIX Startup Script Windows Stop Script UNIX Stop Script

Provides access support for Planning Web server


HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/ startHyperionPlanning.bat HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/ startHyperionPlanning.sh HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/ stopHyperionPlanning.bat HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/ stopHyperionPlanning.sh

Financial Management
The following table describes the services and processes for Financial Management.

Services and Processes 127

Table 36

Financial Management Services and Processes Details Select Start, then Programs, then Oracle EPM System, then Financial Management, and then Financial Management Hyperion Financial Management Service: Hyperion S9 Financial Management Service Hyperion Financial Management DME Listener: Hyperion S9 Financial Management DME Listener Hyperion Financial Management Web Service Manager: HFMWebServiceManager Hyperion Financial Management Service: Hyperion Financial Management Management Service Hyperion Financial Management DME Listener: Hyperion Financial Management DME Listener Hyperion Financial Management Web Service Manager: Hyperion Financial Management Web Service Manager Hyperion Financial Management Service: Service which perpetuates application instances for optimal login performance Hyperion Financial Management DME Listener: Hyperion Financial Management IP Listener for communication with the Hyperion Data Movement Engine. If this service is stopped, the DME Web service will be unable to communicate with all HFM instances on this server. Hyperion Financial Management Web Service Manager: Manages the session information for connection in the Financial Management web server.

Information Type Windows Start Menu Command Registered Service Name

l l l

Display Name in Windows Services Control Panel Description

l l l

Windows Startup Script UNIX Startup Script Windows Stop Script UNIX Stop Script

HYPERION_HOME/products/FinancialManagement/Client/HFM.exe

NA NA NA

Note: The synchronization between Financial Management application servers is based on

system time. Changing the clock can affect this synchronization. For the time change to and from Daylight Savings Time, Oracle recommends that you stop the servers before the time change and restart them afterward.

Strategic Finance
The following table describes the services and processes for Strategic Finance.
Table 37

Strategic Finance Services and Processes Details Select Start, then Programs, then Oracle EPM System, then Strategic Finance, then Server, and then Start Strategic Finance Service HyHSFSrv

Information Type Windows Start Menu Command Registered Service Name

128 Starting and Stopping EPM System Products

Information Type Display Name in Windows Services Control Panel Description Windows Startup Script UNIX Startup Script Windows Stop Script UNIX Stop Script

Details Hyperion Strategic Finance Service Provides Oracle Hyperion Strategic Finance, Fusion Edition services including entity repository management, authentication, access control, consolidation, data and metadata management.
HYPERION_HOME/products/hsf/server/StartHSFService.bat

NA
HYPERION_HOME/products/hsf/server/StopHSFService.bat

NA

Performance Scorecard Application Server


The following table describes the services and processes for the Performance Scorecard application server.
Table 38

Performance Scorecard Application Server Services and Processes Details Select Start, then Programs, then Oracle EPM System, then Scorecard, and then Start Scorecard HyS9HPSWebReports Hyperion Performance Scorecard Web Reports - Web Application

Information Type Windows Start Menu Command Registered Service Name Display Name in Windows Services Control Panel Description Windows Startup Script UNIX Startup Script Windows Stop Script UNIX Stop Script

Provides scorecarding methodologies to measure and monitor business performance.


HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/startHPSWebReports. bat HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/startHPSWebReports. sh HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/ stopHPSWebReports. bat HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/stopHPSWebReports.sh

Performance Scorecard Alerter Application Server


The following table describes the services and processes for the Performance Scorecard Alerter application server.

Services and Processes 129

Table 39

Performance Scorecard Alerter Application Server Services and Processes Details Select Start, then Programs, then Oracle EPM System, then Scorecard, and then Start Alerter Service HyS9HPSAlerter Hyperion Performance Scorecard Alerter - Web Application

Information Type Windows Start Menu Command Registered Service Name Display Name in Windows Services Control Panel Description Windows Startup Script UNIX Startup Script Windows Stop Script UNIX Stop Script

Notifies subscribers by e-mail when the performance of key measures, scorecards, or other points of vital information, depart from an acceptable range.
HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/startHPSAlerter.bat

HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/startHPSAlerter.sh HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/stopHPSAlerter.bat HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/stopHPSAlerter.sh

Profitability and Cost Management


The following table describes the services and processes for Profitability and Cost Management.
Table 40

Profitability and Cost Management Services and Processes Details Select Start, then Programs, then Oracle EPM System, then Profitability, and then Start Profitability HyS9PftWeb Hyperion Profitability - Web Application

Information Type Windows Start Menu Command Registered Service Name Display Name in Windows Services Control Panel Description Windows Startup Script UNIX Startup Script Windows Stop Script UNIX Stop Script

Provides a Workspace module for Profitability


HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/startProfitability. bat HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/startProfitability. sh HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/stopProfitability. bat HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/stopProfitability.sh

130 Starting and Stopping EPM System Products

Data Relationship Management


The following table describes the services and processes for Data Relationship Management.
Table 41

Data Relationship Management Services and Processes Details


l

Information Type Windows Start Menu Command

Services: Select Start, then Programs, then Oracle EPM System, then Data Relationship Management, and then Data Relationship Management Console Web Publishing: Select Start, then Programs, then Oracle EPM System, then Data Relationship Management, then Web Publishing, and then Web Publishing Console Services: HyS9MDMSvc Web Publishing: HyS9MDMWebPubSvc Services: Oracle Hyperion Data Relationship Management Web Publishing: Oracle Hyperion Data Relationship Management Web Publishing Services: HyS9MDMSvc - Oracle Hyperion Data Relationship Management Services Web Publishing: HyS9MDMWebPubSvc - Oracle Hyperion Data Relationship Management Web Publishing

Registered Service Name Display Name in Windows Services Control Panel Description

l l

l l

l l

Windows Startup Script UNIX Startup Script Windows Stop Script UNIX Stop Script:

NA NA NA NA

FDM
The following table describes the services and processes for FDM.
Table 42

FDM Task Manager Services and Processes Details Select Start, then Programs, then Oracle EPM System, then Financial Data Quality Management, then Task Manager, and then Task Manager HyS9FDMTaskManagerSrv Hyperion Financial Data Quality Management - Task Manager Provides the ability to schedule Hyperion Financial Data Quality Management tasks. NA NA NA

Information Type Windows Start Menu Command Registered Service Name Display Name in Windows Services Control Panel Description Windows Startup Script UNIX Startup Script Windows Stop Script

Services and Processes 131

Information Type UNIX Stop Script

Details NA

ERP Integrator
The following table describes the services and processes for ERP Integrator.
Table 43

ERP Integrator Services and Processes Details Select Start, then Programs, then Oracle EPM System, then Performance Management Integrator, and then Start aif. HyS9aifWeb Hyperion ERPI - Web Application

Information Type Windows Start Menu Command Registered Service Name Display Name in Windows Services Control Panel Description Windows Startup Script UNIX Startup Script Windows Stop Script UNIX Stop Script

Provides a Workspace module for ERPI.


HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/startERPIntegrator. cmd HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/startERPIntegrator. sh HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/stopERPIntegrator. cmd HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/stopERPIntegrator.sh

EPM Workspace Application Server


Start EPM Workspace application server last. The following table describes the services and processes for the EPM Workspace application server.
Table 44

EPM Workspace Application Server Services and Processes Details Select Start, then Programs, then Oracle EPM System, then Workspace, and then Start Workspace HyS9Workspace Hyperion Workspace - Web Application

Information Type Windows Start Menu Command Registered Service Name Display Name in Windows Services Control Panel Description

HyS9Workspace - Hyperion Workspace - Web application web application for APP_SERVER APP_VERSION

132 Starting and Stopping EPM System Products

Information Type Windows Startup Script UNIX Startup Script Windows Stop Script UNIX Stop Script

Details
HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/startWorkspace.bat HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/startWorkspace.sh HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/stopWorkspace.bat HYPERION_HOME/deployments/APP_SERVER_NAME_AND_VERSION/bin/stopWorkspace.sh

Launching Clients
This section describes how to launch EPM System clients. It lists default URLs and script names as appropriate. Most clients can also be started using the Windows Start menu. The following table describes the URLs and scripts for launching EPM System clients.
Table 45

Launching Clients URL


http://Server:Port/ interop/ http://Server:Port/ workspace/

Client Shared Services Console EPM Workspace From EPM Workspace, you can access the following products:
l l l

Script or Other Launch Method NA From the Start menu, select Programs, then Oracle EPM System, then Workspace, and then Workspace URL.

Financial Management Planning Performance Management Architect Calculation Manager Performance Scorecard Profitability and Cost Management Reporting and Analysis ERP Integrator NA Use the Hyperion menu or Hyperion ribbon in Microsoft Excel, Microsoft Word, or Microsoft PowerPoint.
HYPERION_HOME/products/Essbase/eas/console/ bin/admincon.exe

l l l

l l

Smart View Administration Services Console

http://server:port/ easconsole/console. html

Integration Services Console Essbase Studio Console

NA NA

HYPERION_HOME/products/Essbase/eis/console/ bin/startclient.bat HYPERION_HOME/products/Essbase/ EssbaseStudio/Console/startStudio.bat

Launching Clients 133

Client Smart Search Command Line Utility Console Strategic Finance Client Data Relationship Management Client Data Relationship Management Web Publishing Client FDM Console

URL NA NA NA

Script or Other Launch Method


HYPERION_HOME/products/Essbase/SmartSearch/ StartSmartSearchProvider.bat HYPERION_HOME/products/hsf/Client/HSF.exe HYPERION_HOME/master data management/mdm_ ntier_client_http.exe

http://Server_Name/ mdm_web http://WebServerName/ HyperionFDM

NA NA

134 Starting and Stopping EPM System Products

6
In This Chapter

Validating the Installation

About EPM System Diagnostics ........................................................................ 135 Prerequisites.............................................................................................. 135 Using EPM System Diagnostics......................................................................... 135 Foundation Services Diagnostics ...................................................................... 136 Essbase Diagnostics .................................................................................... 138 Reporting and Analysis Diagnostics ................................................................... 139 Financial Performance Management Applications Diagnostics...................................... 140 Data Management Diagnostics ........................................................................ 141

About EPM System Diagnostics


EPM System Diagnostics tests the connectivity of installed and configured EPM System components. Run EPM System Diagnostics on each machine in the deployment. The results of the tests are saved in HTML format.

Prerequisites
Before using EPM System Diagnostics, complete these prerequisites:
l

Install EPM System products. See Chapter 3, Installing EPM System Products. Use EPM System Configurator to perform all configuration tasks required for each product. See Chapter 4, Configuring EPM System Products.

Using EPM System Diagnostics


To run EPM System Diagnostics:
1
Choose a method:
l

(Windows) In HYPERION_HOME/common/validation/version number, doubleclick validate.bat. Launch EPM System Diagnostics from the last page of EPM System Configurator.

About EPM System Diagnostics 135

From the Start Menu, choose Programs, then Oracle EPM System, then Foundation Services, and then EPM System Diagnostics. (UNIX) From a console, change to HYPERION_HOME/common/validation/ version number, then type validate.sh.

Progress is shown in the command window.

2 3

To view results, navigate to HYPERION_HOME/common/validation/version number/ reports and open validation_report_date_time.html. Look for failed tests, and diagnose and fix problems.

EPM System Diagnostics creates a ZIP file of all the logs in HYPERION_HOME/logszips for your convenience. For more information about logs, see Oracle Hyperion Enterprise Performance Management System Installation and Configuration Troubleshooting Guide.

Run EPM System Diagnostics again and view the report to verify that problems are solved.
Note: Clicking Refresh in the browser does not refresh the report output.

The report captures the following information:


l

Test date and time Test Status: Passed or Failed for each test Service: Type of test for each test Test Description: A detailed description of each test Duration: Duration of each test Test start time Test end time Total test duration

Foundation Services Diagnostics


The following table describes the EPM System Diagnostics tests performed for Foundation Services products.

136 Validating the Installation

Product/ Component Shared Services

Type of Test CFG: Configuration DB: Database EXT: External Authentication OPN: OpenLDAP OPN: OpenLDAP SSO WEB: Web application

Test Performed Checks whether all configuration tasks have been completed Checks connection to database host:port;databaseName Checks Native Directory external authentication provider configuration Checks if global roles number no less than 16 Checks connection to OpenLDAP Checks availability of login to Shared Services Checks availability of Web application interop on host:port Checks whether all configuration tasks have been completed Checks connection to database host:port;databaseName Checks external authentication provider configuration Checks availability of Shared Services Checks availability of HTTP context for products registered with EPM Workspace using EPM Workspace Web server configuration: Confirms that applications that are registered with EPM Workspace are reachable Checks availability of login to EPM Workspace For each application deployed with EPM Workspace, confirms there is a valid Web server entry in the Shared Services Registry Validates that EPM Workspace services are running and communicating:
l l l

EPM Workspace

CFG: Configuration DB: Database EXT: External Authentication HSS: Shared Services HTTP: http LOG: Login SSO REG: Registry SDKC: SDK Checker

GSM service Repository service Interactive Reporting service

HTTP: http (Windows only) WEB: Web application

Check string LoadModule jk_module modules/mod_jk in HYPERION_HOME/


common/httpServers/Apache/2.0.59/conf/httpd.conf

Checks availability of Web application workspace on host:port

Foundation Services Diagnostics 137

Product/ Component Performance Management Architect

Type of Test CFG: Configuration DB: Database DSC: EPMA Dimension Server Configuration PMAE: EPMA Service PMAJ: EPMA Service PMAP: EPMA Service EXT: External Authentication HSS Shared Services WEB: Web application WEB: Web application

Test Performed Checks whether all configuration tasks have been completed Checks connection to database host:port;databaseName Checks whether the Dimension Server service started

Checks whether the Event Manager service is available Checks whether the Job Manager service is available Checks whether the Process Manager service is available Checks external authentication provider configuration Checks availability of Shared Services Checks availability of Web application awb on host:port Checks availability of Web application DataSync on host:port Checks whether all configuration tasks have been completed Checks connection to database host:port;databaseName Checks Native Directory external authentication provider configuration Checks availability of Shared Services Checks availability of Web application calcmgr on host:port

Calculation Manager

CFG: Configuration DB: Database EXT: External Authentication HSS: Shared Services WEB: Web application

Essbase Diagnostics
The following table describes the EPM System Diagnostics tests performed for Essbase products.

138 Validating the Installation

Product/Component Essbase

Type of Test CFG: Configuration EAS: Essbase Server EAS: Essbase Server SVR: Essbase Java API EXT: External Authentication HSS: Shared Services

Test Performed Checks whether all configuration tasks have been completed Checks whether Essbase server is running on host:port Checks connection to Essbase Server with MAXL Checks connection to Essbase using the Essbase Java API Checks Native Directory external authentication provider configuration Checks availability of Shared Services Checks whether all configuration tasks have been completed Checks Native Directory external authentication provider configuration Checks availability of Shared Services Checks availability of Web application aps on host:port Checks whether all configuration tasks have been completed Checks connection to database host:port;databaseName Checks Native Directory external authentication provider configuration Checks availability of Shared Services Checks availability of Web application eas on host:port Checks availability of Web application hbrlauncher on host:port Checks connection to database host:port;databaseName Checks whether all configuration tasks have been completed Checks connection to database host:port;databaseName Checks whether Essbase Studio server is running on host:port Checks Native Directory external authentication provider configuration Checks availability of Shared Services Checks whether all configuration tasks have been completed Checks availability of Web application EssbaseSearch on host:port Checks whether EQD Excel Add-in is registered to Excel.

Provider Services

CFG: Configuration EXT: External Authentication HSS: Shared Services WEB: Web application

Administration Services

CFG: Configuration DB: Database EXT: External Authentication HSS: Shared Services Web application Web application DB: Database

Essbase Studio

CFG: Configuration DB: Database ESS: Essbase Studio Server EXT: External Authentication HSS: Shared Services

Smart Search Command Line Utility Essbase Client

CFG: Configuration WEB: Web application WR: Windows Registry

Reporting and Analysis Diagnostics


The following table describes the EPM System Diagnostics tests performed for Reporting and Analysis products.
Reporting and Analysis Diagnostics 139

Component Reporting and Analysis

Type of Test CFG: Configuration SVR: Essbase Java API

Test Performed Checks whether all configuration tasks have been completed Checks connection to Essbase using the Essbase Java API Checks availability of Web application hr on host:port Checks availability of Web application WebAnalysis on host:port

Financial Reporting Web Analysis

WEB: Web application WEB: Web application

Financial Performance Management Applications Diagnostics


The following table describes the EPM System Diagnostics tests performed for Financial Performance Management Applications products.

Product/Component Planning

Type of Test CFG: Configuration DB: Database EXT: External Authentication HSS: Shared Services WEB: Web application

Test Performed Checks whether all configuration tasks have been completed Checks connection to database host:port;databaseName Checks Native Directory external authentication provider configuration Checks availability of Shared Services Checks availability of Web application HyperionPlanning on host:port Checks whether all configuration tasks have been completed Checks connection to database host:port;databaseName Checks Native Directory external authentication provider configuration Checks whether Financial Management cluster registration was successful Checks whether Financial Management server registration was successful Checks whether Financial Management service is working Checks whether Financial Management Web server startup was successful Checks whether the application server is started Checks availability of Shared Services Checks whether LCMServer startup was successful Checks whether Smart View Web server startup was successful

Financial Management

CFG: Configuration DB: Database EXT: External Authentication CCFG: HFM Cluster configuration SVR: Server Registration SVR: HFM Service Validation WSVR: HFM Web server ASC: HFM Application Server Configuration HSS: Shared Services LCM: Lifecycle Management Server SVCS: Smart View Server

140 Validating the Installation

Product/Component Performance Scorecard

Type of Test CFG: Configuration DB: Database EXT: External Authentication HSS: Shared Services WEB: Web application WEB: Web application

Test Performed Checks whether all configuration tasks have been completed Checks connection to database host:port;databaseName Checks Native Directory external authentication provider configuration Checks availability of Shared Services Checks availability of Web application HPSWebReports on host:port Checks availability of Web application HPSAlerter on host:port Checks whether all configuration tasks have been completed Checks Native Directory external authentication provider configuration Checks availability of Shared Services Checks availability of the Strategic Finance Web services Checks whether all configuration tasks have been completed Checks connection to database host:port;databaseName Checks Native Directory external authentication provider configuration Checks availability of Shared Services Checks availability of Web application profitability on host:port

Strategic Finance

CFG: Configuration EXT: External Authentication HSS: Shared Services WEB: Strategic Finance Web service

Profitability and Cost Management

CFG: Configuration DB: Database EXT: External Authentication HSS: Shared Services WEB: Web application

Data Management Diagnostics


The following table describes the EPM System Diagnostics tests performed for Data Management products.
Component FDM Type of Test CFG: Configuration EXT: External Authentication HSS: Shared Services ERP Integrator CFG: Configuration DB: Database EXT: External Authentication HSS: Shared Services WEB: Web App Test Performed Checks whether all configuration tasks have been completed Checks Native Directory external authentication provider configuration Checks availability of Shared Services Checks whether all configuration tasks have been completed Checks connection to database host:port;databaseName Checks Native Directory external authentication provider configuration Checks availability of Shared Services Checks availability of Web application aif on host:port

Data Management Diagnostics 141

142 Validating the Installation

7
In This Chapter

Performing Postconfiguration Tasks

General Postconfiguration Tasks........................................................................ 143 Shared Services Postconfiguration Tasks .............................................................. 144 Performance Management Architect Postconfiguration Tasks ....................................... 144 EPM Workspace Postconfiguration Tasks .............................................................. 145 Essbase Postconfiguration Tasks ....................................................................... 145 Integration Services Postconfiguration Tasks.......................................................... 146 Administration Services Postconfiguration Tasks ..................................................... 147 Provider Services Postconfiguration Tasks............................................................. 148 Essbase Studio Postconfiguration Tasks............................................................... 148 Reporting and Analysis Postconfiguration Tasks ...................................................... 149 Planning Postconfiguration Tasks....................................................................... 155 Financial Management Postconfiguration Tasks ...................................................... 156 Strategic Finance Postconfiguration Tasks ............................................................ 157 Performance Scorecard Postconfiguration Tasks ..................................................... 157 FDM Postconfiguration Tasks ........................................................................... 158 ERP Integrator Postconfiguration Tasks ................................................................ 158 Data Relationship Management Postconfiguration Tasks ............................................ 159

Some products require additional steps after configuration.

General Postconfiguration Tasks


The following table describes general postconfiguration tasks for EPM System products.
Table 46

General Postconfiguration Tasks Reference Increasing the JVM Memory Allocation on page 144 Oracle Hyperion Enterprise Performance Management System Security Administration Guide

Task Optional: Increase the JVM memory allocation for your Web Application Server Optional: Harden security for EPM System products.

General Postconfiguration Tasks 143

Increasing the JVM Memory Allocation


Depending on the size of your environment, you might need to increase the heap size for your Web application server to optimize performance. While the default can be used in a test environment (single server type configuration), the heap size must be increased for use in a production environment (multiple servers). To increase the heap size for the Windows service, update the Windows registry for Windows services using regedit. For HKEY_LOCAL_MACHINE\SOFTWARE\Hyperion Solutions \Product Component\ServiceName, update the JVMOptionX (where X is 1, 2, ...) whose value starts with -Xmx.

To increase the JVM memory allocation:


1
Edit your start script to specify the desired heap sizes.

Oracle recommends a maximum setting of 1024. (Size is in megabytes.) For example, you can change the custom startup scripts. For Shared Services, open
HYPERION_HOME/deployments/app_server/bin/ setCustomParamsSharedServices.bat|.sh and modify the Xms128m Xmx1024m

entry.

Restart the Windows service or the script for the product.

Shared Services Postconfiguration Tasks


The following table describes Shared Services postconfiguration tasks.
Table 47

Shared Services Postconfiguration Tasks Reference Configuring NTLM in Oracle Hyperion Enterprise Performance Management System Security Administration Guide Oracle Hyperion Enterprise Performance Management System Security Administration Guide

Task (Optional) Enable Remote Authentication Module if you are implementing security using an NTLM provider and using UNIX on the computer where the EPM System application software is installed. (Remote Authentication Module is installed with Oracle's Hyperion Foundation Services.)

Optional: You can set up Shared Services to use Oracle Internet Directory as the Native Directory instead of using OpenLDAP, which is installed and used by default.

Performance Management Architect Postconfiguration Tasks


The following table describes Performance Management Architect postconfiguration tasks.

144 Performing Postconfiguration Tasks

Table 48

Performance Management Architect Postconfiguration Tasks Reference WebLogic Server application server documentation

Task (WebLogic Server only) After you deploy Performance Management Architect, depending on your environment, you might need to increase the Max Thread execution time (defined by the StuckThreadMaxTime attribute value) for the application server. Increasing this value prevents long processes from terminating. Optional: Perform server administration tasks.

Administering Servers in the Hyperion Enterprise Performance Management Architect Administrators Guide Oracle Hyperion Enterprise Performance Management Architect Administrator's Guide

Optional: Edit settings in the bpma_server_config.xml file. The BPMA_Server_Config.xml file has two main elements, DimensionServer and log4net. The DimensionServer section contains settings that are specific to internal workings of the Dimension Server and other related processes. The log4net section contains settings that are used by the log4net module which is used to log warnings, errors, and so on.

EPM Workspace Postconfiguration Tasks


The following table describes EPM Workspace postconfiguration tasks.
Table 49

EPM Workspace Postconfiguration Tasks Reference Oracle Business Intelligence New Features Guide Oracle Enterprise Performance Management Workspace Administrator's Guide

Task Optional: If you are using Oracle Business Intelligence Suite Enterprise Edition, configure it to work with EPM Workspace. Optional: Use the Configuration and Monitoring Console (CMC) to customize the configuration for EPM Workspace services, Reporting and Analysis services, Annotations services, EPM Workspace Web Applications (properties only), and Web Analysis Web Applications (properties only). During configuration with EPM System Configurator, EPM System Configurator sets up default values for the services. Use the Configuration and Monitoring Console to customize the services.

Essbase Postconfiguration Tasks


The following table describes Essbase postconfiguration tasks.
Table 50

Essbase Postconfiguration Tasks Reference Appendix B, Optional Manual Configuration for Essbase Products

Task Optional: Manually configure Essbase.

EPM Workspace Postconfiguration Tasks 145

Task (UNIX) Set User Limits on 64-bit AIX. If you install both Essbase Client and Integration Services together, edit the PATH environment variable to ensure that the Essbase Client bin path is before the Integration Services bin path. For example: HYPERION_HOME/products/Essbase/EssbaseClient/bin should come before HYPERION_HOME/products/Essbase/eis/server/bin. If you are using Oracle Essbase Spreadsheet Add-in as a Power User instead of as an Administrator, you must manually set ESSBASEPATH.

Reference Setting User Limits on 64-bit AIX on page 146

Setting User Limits on 64-bit AIX


When running Essbase Server on a 64-bit AIX platform, you must change the user limits to increase the size of a data segment. The following table lists suggested values:

User Limit time (seconds) file (blocks) data (kbytes) stack (kbytes) memory (kbytes) coredump (blocks) nofiles (descriptors)

Value unlimited 2097151 unlimited No higher than 128 MB for 64-bit and 64 MB for 32-bit unlimited 2097151 unlimited

Integration Services Postconfiguration Tasks


The following table describes Integration Services postconfiguration tasks.
Table 51

Integration Services Postconfiguration Tasks Reference Appendix B, Optional Manual Configuration for Essbase Products. Configuring Data Sources in Oracle Essbase Integration Services System Administrator's Guide

Task Optional: Update the environment manually. Configure data sources. To create OLAP models or build metaoutlines, you must connect Integration Services to a database that contains metadata (the OLAP Metadata Catalog database) and to a database in which needed users data is stored (the Data Source database).

146 Performing Postconfiguration Tasks

Task Create an OLAP Metadata Catalog

Reference Creating, Upgrading, and Deleting OLAP Metadata Catalogs in Oracle Essbase Integration Services System Administrator's Guide Connecting to Server Components and Data Sources in Oracle Essbase Integration Services System Administrator's Guide Mapping JDBC Data Sources (Teradata and Oracle Users Only) in Oracle Essbase Integration Services System Administrator's Guide Setting Up the Sample Applications in Oracle Essbase Integration Services System Administrator's Guide

Connect to Server Components and Data Sources

If you are using the XML Import/Export feature, map JDBC Data Sources

Optional: Set up sample applications.

Administration Services Postconfiguration Tasks


The following table describes Administration Services postconfiguration tasks.
Table 52

Administration Services Postconfiguration Tasks Reference

Task If Administration Services cannot connect to Shared Services because it times out, edit EAS_HSS_RETRY_ COUNT in HYPERION_HOME/deployments/AppServerNameAndVersion/bin/setCustomParamseas. bat to increase the value. For example: In HYPERION_HOME/deployments/Tomcat5/bin/setCustomParamseas.bat, in JAVA_ OPTS, add or edit: -DEAS_HSS_RETRY_COUNT=n, where n is the number of times to retry, in one-second intervals. If you are using Oracle Application Server through HTTP proxy, and the Administration Services Console is installed on the same machine as the HTTP server or the Administration Services Server, append the following parameter to the lax.nl.java.option.additional argument in admincon.lax: -DCLIENT_SERVER_DIFF_MC=true If you are using Administration Services in a clustered environment, add the following to the java options in ORACLE_HOME/opmn/conf/opmn.xml on the machine on which Administration Services is deployed:
-DCLIENT_SERVER_DIFF_MC=true

If you have configured the Web server to act as a reverse proxy for Administration Services, and the Web server is installed on the same machine as Administration Services, you must either include the Java argument -DCLIENT_ SERVER_DIFF_MC=true in the script used to start Administration Services, or append the parameter to the lax.nl.java.option.additional argument in admincon.lax. If you are using Administration Services on UNIX with Oracle Application Server, set environment variables in the Oracle Application Server Application Server Console. Optional Manual Configuration for Administration Services (UNIX) on page 233

Administration Services Postconfiguration Tasks 147

Task Optional: Install and configure SAP/R3 if you are using SAP R/3 as a data source

Reference Administration Services Online Help

Provider Services Postconfiguration Tasks


The following table describes Provider Services postconfiguration tasks.
Table 53

Provider Services Postconfiguration Tasks Reference Optional Manual Configuration for Provider Services (UNIX) on page 233

Task If you are using Provider Services on UNIX with Oracle Application Server, set environment variables in the Oracle Application Server Application Server Console.

Essbase Studio Postconfiguration Tasks


The following table describes Essbase Studio postconfiguration tasks.
Table 54

Essbase Studio Postconfiguration Tasks Reference Oracle Essbase Studio User's Guide Updating the Essbase Studio Catalog on page 148

Task Optional: Customize Essbase Studio server.properties file or configure the Administration Services Console Launch File. If you used the Apply Maintenance Release option to move from Essbase Studio Release 11.1.1 or 11.1.1.1 to this release, you must update the Essbase Studio catalog.

Updating the Essbase Studio Catalog


If you used the Apply Maintenance Release option to move from Essbase Studio Release 11.1.1 or 11.1.1.1 to this release, you must update the Essbase Studio catalog after installation and configuration. You update the catalog by issuing the reinit command in the Essbase Studio command line client. This updates the catalog with the latest release procedures.

To update the Essbase Studio catalog:


1 2
Ensure that Essbase Studio Server is running. From the HYPERION_HOME/products/essbase/EssbaseStudio/Server directory, run one of the following scripts:

Windows:
startCommandLineClient.bat

148 Performing Postconfiguration Tasks

UNIX
startCommandLineClient.sh

A command window called the CPL Shell is displayed.

At the prompt, enter a valid administrator user name and password.


Note: You must have Essbase Studio administrator privileges to use the reinit command.

4 5

At the prompt, enter the following command:


reinit

Enter exit to close the CPL Shell.

The Essbase Studio catalog is now ready for use.

Reporting and Analysis Postconfiguration Tasks


The following table describes Reporting and Analysis postconfiguration tasks.
Table 55

Reporting and Analysis Postconfiguration Tasks Reference Oracle Hyperion Financial Reporting Studio User's Guide Preparing the Financial Reporting Print Server on page 150 Configuring X11 for Web Application Server Components for Financial Reporting and Web Analysis (UNIX) on page 150 Configuring SAP Data Source Access and Authentication on page 150 Setting Up Environment Variables for Financial Reporting and Web Analysis for Non-English Characters (UNIX) on page 151

Task Optional: Customize initial user preferences for Financial Reporting by editing fr_repserver.properties. Prepare the print server for Financial Reporting. The Print Server runs only on Microsoft Windows. (UNIX) Configure X11 for Web application server components for Financial Reporting and Web Analysis. To configure Reporting and Analysis to access SAP JAVA Connector (SAP JCo) data sources and optionally to authenticate users against an SAP server, install the SAP JCo files to each Reporting and Analysis component machine. (UNIX) Set up environment variables for Financial Reporting and Web Analysis for non-English Characters. For Web Analysis: If you are using an RDBMS as a data source or for relational drill through, add the necessary drivers. (UNIX) Set up environment variables for Production Reporting. Prepare Interactive Reporting for printing. Optional: Configure fonts for UNIX systems. To enable High Availability (HA) using Provider Services, enable Provider Services driver support for Financial Reporting.

Setting up the Environment Variables for Production Reporting (UNIX) on page 152 Preparing Interactive Reporting for Printing (UNIX) on page 153 Configuring Fonts (UNIX) on page 153 Financial Reporting ConfigurationEnabling the Provider Services Driver on page 154

Reporting and Analysis Postconfiguration Tasks 149

Task Optional: (UNIX) Recreate the executables for Production Reporting.

Reference Recreating the Executables (Production Reporting Only) (UNIX) on page 154

Preparing the Financial Reporting Print Server


To print cell documents, the corresponding print applications (Microsoft Word, Excel and PowerPoint) on the Print Server machine must have the following characteristics:
l

Be properly installed Be properly registered for printing in the computers registry Be available to the SYSTEM account Have access to, and be able to print from, the printers installed by Financial Reporting (HRPrinter1-5). The SYSTEM account issues all print requests, so it is important that the applications can print using the Print Servers printers.

To optimize the print server, disable the following items:


l

All add-ins (including Oracle's Hyperion add-ins) from all Microsoft Office applications To enhance application launch time and consume system resources. If enabled, it may display UI components that require user input. SmartTags (Office 2002+)To enhance performance. Office AssistantOffice Assistant prompts the user for input, which halts printing.
Tip: Dedicate a machine for use as a print server, ensuring that add-ins are not used.

Configuring X11 for Web Application Server Components for Financial Reporting and Web Analysis (UNIX)
To perform chart generation, the Reporting and Analysis Web application server components require access to a graphics display device, either real or virtual. Oracle recommends that you use an X virtual frame buffer (Xvfb) instead of a hardware graphics display device, because Xvfb performs all operations in memory and does not require that any screens or input devices be attached to the machine. For details about enabling Xvfb, see Appendix G, Enabling an X Virtual Frame Buffer for Financial Reporting and Web Analysis.

Configuring SAP Data Source Access and Authentication


To configure Reporting and Analysis to access SAP JAVA Connector (SAP JCo) data sources and optionally to authenticate users against an SAP server, install the SAP JCo files to each Reporting and Analysis component machine.

150 Performing Postconfiguration Tasks

To configure Reporting and Analysis to use SAP as a data source and optionally to use SAP
as an authentication provider:

Obtain the SAP JCo files from:


l

Your SAP distribution. Download from the SAP Web site as a registered user at https://service.sap.com/ connectors

(Windows) After Reporting and Analysis installation:

a. Place the SAP JCo binaries in HYPERION_HOME/common/SAP/bin. b. Place the SAP JCo java archives (JAR files) in HYPERION_HOME/common/SAP/lib c. Expand the JAR file, using the convenience utility, in
HYPERION_HOME/common/SAP/lib/explodejarUsingJRE.bat|sh

UNIX: After Reporting and Analysis installation, place the SAP JCo binaries in HYPERION_HOME/ common/SAP/bin. Place the SAP JCo java archives (.jar files) in HYPERION_HOME/common/SAP/ lib Optional: To configure Reporting and Analysis to use SAP as an authentication provider:

a. Download these files from the SAP Enterprise Portal EP60 SP2 or higher:
l

com.sap.security.core.jar com.sap.security.api.jar sap.logging.jar iaik_jce.jar iaik_jce_export.jar (if using the export version of the IAIK-JCE libraries)

into
HYPERION_HOME/common/SAP/lib

b. After installation, expand the JAR files, using the convenience utility, in
HYPERION_HOME/common/SAP/lib/explodejarUsingJRE.bat|sh

Setting Up Environment Variables for Financial Reporting and Web Analysis for Non-English Characters (UNIX)
The following environment variables must be properly initialized in order to run Financial Reporting or Web Analysis objects that include metadata containing non-English characters:
l

LANG (UNIX) LC_ALL (UNIX) ESSLANG (if Essbase is used as a data source) (UNIX and Windows)

To initialize, use login scripts, or edit:


l

LANG, LC_ALL (UNIX):


m

For Financial Reporting:


Reporting and Analysis Postconfiguration Tasks 151

HYPERION_HOME/products/biplus/bin/freporting.env

and
HYPERION_HOME/deployments/vendor/bin/setCustomParamsFinancialReporting.sh
m

For Web Analysis:


HYPERION_HOME/products/biplus/InstallableApps/config/wa_env.sh

ESSLANG (UNIX and Windows):


m

For Financial Reporting:


HYPERION_HOME/products/biplus/lib/fr.env

For Web Analysis:


(UNIX) HYPERION_HOME/products/biplus/InstallableApps/config/wa_env.sh

or
(Windows) HYPERION_HOME/products/biplus/InstallableApps/config/WebAnalysis.env

Note: For Web Analysis, EPM System Configurator uses the existing ESSLANG environment

variable if it is already set, and appends it to the Web Analysis environment setup script. However, if ESSLANG is not already specified when you deploy Web Analysis, you need to specify it in the appropriate environment setup script.
Note: If you are using Oracle Application Server on UNIX, in addition to using a script to set

the environment variables, you must specify the environment variables in the Oracle Application Server Application Server Console, by setting the Server properties for the OC4J instance.

Setting up the Environment Variables for Production Reporting (UNIX)


You run a script to set the environment variables. The scripts are in specified database directories.

To configure the environment variables, locate the environment scripts in the following
directories:
HYPERION_HOME/products/biplus/bin/SQR/Server/db_name/bin

or, for the 64bit version:


HYPERION_HOME/products/biplus/bin/SQR/Server/db_name/bin64

where db_name is the name of the database. The following databases are supported: Oracle, Sybase, Informix, DB2, ODBC, DDO, and Teradata.
l

For all databases, the following script configures the basic environment variables:
m

For C Shell: source setenv.csh For Bourne or Korn Shell: setenv.sh

152 Performing Postconfiguration Tasks

For the DDO database, the following script configures additional environment variables:
m

For C Shell: source setjre.csh For Bourne or Korn Shell: setjre.sh

In addition, for jobs with charts, configure X11 display as described in Appendix G, Enabling an X Virtual Frame Buffer for Financial Reporting and Web Analysis.

Preparing Interactive Reporting for Printing (UNIX)


To prepare Interactive Reporting for printing:
1 2
Ensure that Acrobat Reader is installed. If the installation location for Acrobat Reader is not in the PATH, set a new environment variable: PATH_TO_ACROREAD, where the path is the Acrobat Reader installation location.

Configuring Fonts (UNIX)


Perform these procedures if you want nice-looking fonts. Interactive Reporting Service must be configured with appropriate fonts to ensure that BQY documents in EPM Workspace have a consistent look and feel with the Web Client. You must make Type1, TrueType, or OpenType fonts available to Interactive Reporting Service. The configured fonts must support characters for all intended languages. EPM System Installer installs Andale WT font in HYPERION_HOME/products/biplus/ fonts directory and configures Interactive Reporting Service to use it. This font supports most characters from Western European languages as well as Chinese, Japanese and Korean. Customers must use fonts appropriate for their usage. For example, when using Western European languages, for Windows-like look and feel, you could download Microsofts TrueType Web fonts and configure as below:

To make Microsofts TrueType Web fonts available to EPM Workspace:


1 2 3
Download the Microsoft TrueType Web fonts from:

http://sourceforge.net/projects/corefonts/ or other source.


Create a directory to store the font files. If using downloaded Microsoft fonts, extract each file (*.exe) into the newly created directory using the cabextract utility located in INSTALL_HOME/bin/, as below:
BIPLUS_HOME/bin/cabextract -d directory CAB file

Create a fonts.dir file in the directory containing the font files using the ttmkfdir utility. The ttmkfdir utility can be downloaded from the following URL:

http://packages.qa.debian.org/t/ttmkfdir.html

Reporting and Analysis Postconfiguration Tasks 153

5 6

Add the fonts.dir directory to environment variable FONT_PATH, or add it to BQ_FONT_PATH environment variable inside BIPLUS_HOME/bin/services.sh. Restart Interactive Reporting Service.

Financial Reporting ConfigurationEnabling the Provider Services Driver


To enable High Availability (HA) using Provider Services, you must enable Provider Services driver support for Financial Reporting. For Financial Reporting: On each computer where one or more of the following are installed:
l

Financial Reporting Report Server Financial Reporting Scheduler Financial Reporting Web application Financial Reporting Studio

Do the following: 1. Edit HYPERION_HOME/products/biplus/lib/fr_global.properties. 2. Change UseEssbaseEDS=0 to UseEssbaseEDS=1. 3. Uncomment (remove hash) EssbaseEDSServer=, and assign it your APS server hostname.

Recreating the Executables (Production Reporting Only) (UNIX)


For Production Reporting for Sybase, Oracle, Informix, DB2, and Teradata, ensure that you have the proper database client software installed on the same machine as Production Reporting. Production Reporting for ODBC and DDO does not require any additional libraries. If you have your own user-defined functions, if a new version of the database libraries becomes available, or to apply OS-level patches, then you need to re-link the product as described in this section. The Production Reporting script uses standard environment variables for each database to identify the location of the libraries. You must re-create the executables if the version of the operating system or database client software is different from when the original executables were created. You find the versions by using the following command line flag:
-id

To re-create the executables, type the following commands from a shell:


cd HYPERION_HOME/products/biplus/bin/SQR/Server/db_name/lib ./sqrmake

154 Performing Postconfiguration Tasks

where db_name is the name of one of the following database names: Oracle, Informix, DB2, Sybase, ODBC, DDO, or Teradata.
HYPERION_HOME and SQRDIR are required to re-create the executables. SQRDIR should be set to HYPERION_HOME/products/biplus/bin/SQR/Server/db_name/bin.

Planning Postconfiguration Tasks


The following table describes Planning postconfiguration tasks.
Table 56

Planning Postconfiguration Tasks Reference

Task If you applied the maintenance release to move from Planning Release 11.1.1.x to release 11.1.1.3, you must log on and click Migrate for each application. If you are using Offline Planning, perform the postconfiguration tasks.

Configuring Offline Planning on page 155 and Oracle Hyperion Planning Administrator's Guide

If you are using Planning in a Redhat or Oracle Enterprise Linux environment and you are using Simplified Chinese, you must specify LANG=zh_CN.GB18030 (instead of LANG=zh_CN.utf8) in one of two ways:
l l

In the OS system locale variable (if you have not already set it) before you install and configure Planning In setCustomParamsHyperionPlanning.sh after you install and configure Planning (UNIX) Configuring the Planning Locale for Use in Non-English Environments on page 156

(UNIX) Configure the Planning locale for a non-English UNIX environment.

Configuring Offline Planning


To configure Offline Planning:
1
Because Offline Planning Provider terminates when a user without proper access takes a form offline, administrators must give users the following permissions:
l

Read and write permissions for the following directories and subdirectories: HYPERION_HOME/products/Planning/Offline/myanalytics and HYPERION_HOME/products/Planning/offline/offlinedata. Read and execute permissions for c:/windows/system32/msvcr71.dll.

2 3

Install Smart View. Enable the form for offline use and assign appropriate roles. See the Oracle Hyperion Planning Administrator's Guide.

Planning Postconfiguration Tasks 155

(UNIX) Configuring the Planning Locale for Use in NonEnglish Environments


To configure the Planning locale for use in a non-English UNIX environment:
1
In HYPERION_HOME/deployments/AppServerNameAndVersion/bin, edit setCustomParamsHyperionPlanning.sh to include these items:
l

The appropriate ESSLANG value The appropriate LANG value The appropriate LC_CTYPE

ESSLANG, LANG and LC_TYPE should be assigned the same locale.

For example, for simplified Chinese:


ESSLANG=SimplifiedChinese_China.UTF-8@Binary; export ESSLANG LANG=zh_CN.UTF-8; export LANG LC_CTYPE=zh_CN.UTF-8; export LC_CTYPE

Make sure the ESSLANG value you set in setCustomParamsHyperionPlanning.sh matches the ESSLANG value set for Essbase Server (set with EPM System Configurator or by editing HYPERION_HOME/products/Essbase/EssbaseServer/hyperionenv.doc).

Financial Management Postconfiguration Tasks


The following table describes Financial Management postconfiguration tasks.
Table 57

Financial Management Postconfiguration Tasks Reference Oracle Hyperion Financial Management Administrator's Guide

Task If you use the Financial Management Win32 client, or if you selected the ADM Client component during installation to work with Financial Reporting and Web Analysis, you must register servers and clusters and enable DCOM using the HFMRegCluster utility. If you have configured Financial Management Web Applications, use Internet Information Services (IIS) Manager to set the Web Service Extensions Active Server Pages to Allowed. If you applied the maintenance release to move from Release 11.1.1.2 to Release 11.1.1.3, you must run the Schema Upgrade Utility. Upgrade Note! Upgrade applications using the Schema Upgrade Utility. Optional: Configure Settings for IIS 5.0 Isolation Mode

Using the Financial Management Schema Upgrade Utility on page 172 Using the Financial Management Schema Upgrade Utility on page 172 Configuring Settings for IIS 5.0 Isolation Mode (Optional) on page 157

156 Performing Postconfiguration Tasks

Configuring Settings for IIS 5.0 Isolation Mode (Optional)


Before you install Financial Management, you install and configure IIS. However, if you run IIS 5.0 Isolation mode in IIS 6.0 on Windows 2003, after you run EPM System Configurator and create your Web directories, you must manually set two additional IIS properties for the Application Protection and Authentication Level.

To set the properties for IIS 5.0 Isolation mode:


1 2 3 4 5 6 7 8 9
Select Start, then Programs, then Administrative Tools, and then Internet Services Manager. Expand Internet Information Services and its subdirectories, and right-click the virtual directory for Financial Management; for example, HFM, and select Properties. On the Virtual Directory tab, from the list for Application Protection, change the setting to High (Isolated). Close Internet Services Manager. Select Start, then Programs, then Administrative Tools, and then Component Services. Expand the directories, and select COM+ Applications. Select the Financial Management Web site; for example, IIS (Default Web Site//Root/HFM). Right-click the Web site and select Properties. On the Security tab, from the list in the Authentication Level for Calls, change the setting to None.

Strategic Finance Postconfiguration Tasks


The following table describes Strategic Finance postconfiguration tasks.
Table 58

Strategic Finance Postconfiguration Tasks Reference Chapter 2, Performing Server-Related Tasks and Chapter 3, Working With Databases in the Hyperion Strategic Finance Administrator's Guide Managing Entities on Strategic Finance Servers in the Hyperion Strategic Finance User's Guide.

Task Set up servers and databases.

Connect the Strategic Finance client to the server. If you have configured Strategic Finance Web services, use Internet Information Services (IIS) Manager to set the Web Service Extensions Active Server Pages to Allowed.

Performance Scorecard Postconfiguration Tasks


The following table describes Performance Scorecard postconfiguration tasks.

Strategic Finance Postconfiguration Tasks 157

Table 59

Performance Scorecard Postconfiguration Tasks Reference Oracle Hyperion Enterprise Performance Management System Lifecycle Management Guide

Task During configuration, EPM System Configurator registers Performance Scorecard with the default port (19000) for EPM Workspace Web Server configuration. If you are using a different port or protocol, then after deployment, you must edit the .instance file that is created during configuration. To edit the .instance file, use Lifecycle Management to export Hyperion Performance Scorecard Registration artifacts to the file system, use a text editor to edit the context id and lcmCallBack parameters in the instance file on the file system, save your edits, then use Lifecycle Management to import the Hyperion Performance Scorecard Registration artifacts back into the application. Note: The instance file is considered an artifact in Lifecycle Management. The instance file artifact is displayed in the Lifecycle Management artifact listing under the Deployment Metadata node in Shared Services Console. In the Oracle's Hyperion Shared Services Console View Pane, expand Application Groups, then Foundation, and Deployment Metadata. Then in the artifact listing, expand Registration, then Applications, and Hyperion Performance Scorecard.

FDM Postconfiguration Tasks


The following table describes FDM postconfiguration tasks.
Table 60

FDM Postconfiguration Tasks Reference Oracle Hyperion Financial Data Quality Management Configuration Guide

Task Configure FDM and create FDM applications. EPM System Configurator only registers FDM with Shared Services. The remainder of the configuration is done in FDM.

ERP Integrator Postconfiguration Tasks


The following table describes ERP Integrator postconfiguration tasks.
Table 61

ERP Integrator Postconfiguration Tasks Reference Preparing ERP Integrator for Use with Microsoft SQL Server on page 158 Oracle Hyperion Financial Data Quality Management ERP Integration Adapter for Oracle Applications Administrator's Guide

Task If you are using ERP Integrator with Microsoft SQL Server, perform manual steps. Configure Oracle Data Integrator to work with ERP Integrator.

Preparing ERP Integrator for Use with Microsoft SQL Server


If you are using ERP Integrator with Microsoft SQL Server, you must perform additional steps to update references to the database.

To prepare ERP Integrator for use with Microsoft SQL Server:


1
Navigate to the following deployment folder for the ERP Integrator Web application.

158 Performing Postconfiguration Tasks

HYPERION_HOME/deployments/AppServerNameAndVersion/ERPIntegrator/webapps/aif

2 3 4 5

Open the following file in a text editor:


WEB-INF/classes/com/hyperion/aif/gl/common/setup/userinterface/DataBindings.cpx

Using the Match Case search option, search and replace all instances of _Oracle with the following:
l

_SQLServer if you are using Microsoft SQL Server.

Save the file. Restart the ERP Integrator Web service.

Data Relationship Management Postconfiguration Tasks


The following table describes Data Relationship Management postconfiguration tasks.
Table 62

Data Relationship Management Postconfiguration Tasks Reference Oracle Hyperion Data Relationship Management Installation Guide

Task Install and configure Data Relationship Management.

Data Relationship Management Postconfiguration Tasks 159

160 Performing Postconfiguration Tasks

8
In This Chapter

Upgrading EPM System Products

About Upgrading ......................................................................................... 161 About Upgrading Only Some EPM System Products.................................................. 165 Upgrading Checklist ..................................................................................... 167 Prerequisites.............................................................................................. 168 Installing and Configuring EPM System Products ..................................................... 170 Upgrading Applications.................................................................................. 170 Performing Security Related Upgrade Tasks........................................................... 175 Additional Product-Specific Upgrade Tasks ........................................................... 180 Working in an Environment with Multiple Releases................................................... 182

This chapter describes the upgrade process for EPM System products and covers only upgrades of software in place. This means that the earlier release is on the computer that you are upgrading. Use this chapter in conjunction with the Oracle Hyperion Enterprise Performance Management System Installation Start Here and the Oracle Hyperion Enterprise Performance Management System Certification Matrix (http://www.oracle.com/technology/products/bi/hyperionsupported-platforms.html) to perform upgrades to Release 11.1.1.x products.
Note: If you are upgrading only some EPM System products in your deployment, you must also

read About Upgrading Only Some EPM System Products on page 165.

About Upgrading
Improvements in This Release
This release contains improvements that facilitate the installation, configuration and upgrade process easier.

About Upgrading 161

Process Installation

Improvements
l l l l l

Enables installation of multiple products Installs all products and components in one pass per computer Provides a new location for product homes (all products are installed under HYPERION_HOME/products) Permits installation by tier or component for multiple products Enables uninstallation of earlier releases of products Through the Shared Services Registry, eliminates repetitive entry of configuration information across products (the registry is located within the Shared Services database) Significantly reduces the number of tasks required to configure EPM System products Upgrades the database from the earlier release Executes an upgrade task that moves necessary information (such as property files) to the Shared Services Registry

Configuration

l l l

Upgrade and Migrate Terminology


When using Hyperion products, the terms upgrade and migrate are defined as follows:
l

Upgrade: The process of replacing an earlier software release with a current release or replacing one product with another Migrate: The process of copying applications, artifacts, or users from one environment or computer to another; for example, from a testing environment to a production environment

Note: The term upgrade does not apply to moving from Release 11.1.1.x to Release 11.1.1.3.

Use the Apply Maintenance Release option in EPM System Installer instead. See Installation Type on page 53. When you apply the maintenance release, you do not need to follow the upgrade procedures described in this chapter.

Supported Upgrade Paths


You can upgrade to EPM System Release 11.1.1.x from the following releases and their associated maintenance releases:
l

9.3.x 9.2.1 9.2.0.3

If you are already using Release 11.1.1.x, choose the Apply Maintenance Release option during installation. See Installation Type on page 53 If you are using a release earlier than Release 9.2.0.3, you must first upgrade to Release 9.2.1 or 9.3.x and then upgrade to Release 11.1.1.x. For upgrade procedures for the earlier release, see the product installation guides for the products that you are using.

162 Upgrading EPM System Products

Note: If you are upgrading Financial Management from a release earlier than Release 9.2.0.3,

and you choose an intermediate upgrade to Release 9.3.1, make sure you use the updated Schema Upgrade Utility provided with Release 9.3.1.4.02. It is not necessary to apply the Release 9.3.1.4.00 Service Pack to Release 9.3.1, however applying this updated utility to the Release 9.3.1 upgraded environment is required for upgrade to Release 11.1.1.x.

Direct Upgrades
Most products can be directly upgraded to the 11.1.1.x release. For a direct upgrade, you can install and configure with the earlier release on the same machine. You are prompted whether to uninstall the earlier release. After products are upgraded, you cannot use earlier releases on newer applications.

Upgrades Requiring Uninstall


FDM cannot be directly upgraded. You must uninstall the earlier release and install the current release.
Note: You must reboot the server after you uninstall FDM.

What Happens During Upgrades


The new EPM System Installer and EPM System Configurator have automated many of the upgrade steps that were previously required.

What Happens During Installation and Configuration


These are important functions performed by EPM System Installer and EPM System Configurator: EPM System Installer
l

Enables installation of multiple products in one machine in one pass Enables uninstallation of earlier releases but retains property, configuration, and data files needed for the upgrade process Runs scripts in the background to transfer required information to the current release

EPM System Configurator


l

During the Configure Database task, creates the Shared Services Registry During configuration, registers products with the Shared Services Registry (no task needs to be selected) Executes upgrade scripts to bring required configuration information into the Shared Services Registry automatically

About Upgrading 163

In the following table, actions performed by EPM System Installer and EPM System Configurator are outlined by component/product:
Product Common Components Shared Services Automated Actions by EPM System Installer and EPM System Configurator Moves Registry.properties (licensing information) This only applies to upgrades from releases 9.2.1 or 9. 3.1
l l l l

Creates Shared Services Registry tables Updates existing database to this release Upgrades OpenLDAP provisioning information to current release Brings security configuration information into Shared Services Registry (css.xml file) Note: Information from the css.xml file is uploaded to the Shared Services Registry. The css.xml file is no longer available for editing locally.

Performance Management Architect EPM Workspace and Reporting and Analysis (includes Financial Reporting, Web Analysis, Production Reporting, and Interactive Reporting)

Upgrades database schema and all data in it to Release 11.1.1.x format

Reads existing server.xml for setup, GSM, LSM, and DB access info, IR services, and retrieves portal services UUID, ports and home location from database. For any missing services, adds default and disabled entries. Collects existing datasources from server.xml and persists them in the registry. Writes registry values for all Foundation Services and Oracle's Hyperion Interactive Reporting services Ensures that services are added and enabled Updates the repository location Removes Authentication and Name Server service entries in the V8_service_agent table Upgrades existing SQL scripts

l l l l l l

Note: During upgrade, the previous location BIPLUS_HOME/data/RM1_hostname) is used, so do not delete it. Smart View Essbase NA Upgrades security file. Note: For most products, during configuration, EPM System Configurator creates a preprovisioned user called admin that enables you to log on to Shared Services after configuration using admin/password to create and provision users. However, after you upgrade Essbase, you have the same set of users that you had in the previous release; the admin user is not configured during an Essbase upgrade. Administration Services (including Business Rules) Integration Services Provider Services
l

Moves storage directory from HYPERION_HOME/AdminServices to HYPERION_HOME/products/


Essbase/eas

l l

Moves HBRServer.properties to the Shared Services Registry Upgrades database to new release

NA Copies domain.db from the old installation location to the new location Copies essbase.properties to essbase.properties.950

l l

Smart Search Command Line Utility

NA

164 Upgrading EPM System Products

Product Planning

Automated Actions by EPM System Installer and EPM System Configurator


l

For 9.3.x upgrades, upgrades the Planning System database and for 9.2.x upgrades, creates the Planning System database Upgrades Planning applications Copies HspJSHome.properties, and HBRServer.properties to new location Configuration is fully incorporated into the EPM System Configurator Database upgraded by Financial Management Schema Upgrade utility Moves Notes and attachments Upgrades database to new release

l l

Financial Management Performance Scorecard Strategic Finance FDM

l l

l l

NA NA

Upgrade Documentation Not Provided


Upgrade documentation for the following products is not covered in this guide:
l

For FDM configuration, see the Oracle Hyperion Financial Data Quality Management Configuration Guide. For Data Relationship Management installation and configuration, see the Oracle Hyperion Data Relationship Management Installation Guide. For Data Integration Management installation and configuration, see the Hyperion Data Integration Management Installation Guide.

About Upgrading Only Some EPM System Products


This section provides an overview of how to work with multiple releases of EPM System, where not all products are upgraded to Release 11.1.1.x. These products require upgrade to Release 11.1.1.3:
l

Shared Services EPM Workspace Performance Management Architect Reporting and Analysis

An earlier release of the following products can be used, however, the Shared Services Registry must be updated in order for these products to operate properly in a mixed version environment. See Working in an Environment with Multiple Releases on page 182.
l

Essbase and Administration Services, required only if you are using Performance Management Architect to create Essbase applications.

About Upgrading Only Some EPM System Products 165

Planning (Oracle Hyperion Workforce Planning, Fusion Edition, and Oracle Hyperion Capital Asset Planning, Fusion Edition) Financial Management Performance Scorecard

An earlier release of the following products can be used without requiring edits to the Shared Services Registry:
l

Strategic Finance Oracle's Hyperion Data Integration Management Data Relationship Management

See Release Compatibility in the Oracle Hyperion Enterprise Performance Management System Installation Start Here for the list of releases that are supported for each product. For an overview of the steps for working with multiple releases, see Upgrading Checklist on page 167.

Limitations of Using Shared Services with Earlier Releases of Other Products


If you are using Shared Services 11.1.1.x with earlier releases of other products, Oracle Internet Directory (OID) cannot be used as Native directory. You must use openLDAP.

Limitations of Using Performance Management Architect 11.1.1.x with Earlier Releases of Planning
To use Performance Management Architect 11.1.1.x with earlier releases of Planning, note these restrictions.

Using Performance Management Architect Features


If you are using Planning Release 9.3.1 with Performance Management Architect Release 11.1.1.x, you can use all features available except that new attribute types (Boolean, Date, and Number) are not supported (only text is supported). The Manage Data Source dialog is not supported and you cannot create data sources while deploying.

Using Planning Flat Files From 9.3.1


If you are using flat files created in an earlier release of Planning, see the Appendix of the Oracle Hyperion Enterprise Performance Management Architect Administrators Guide for information about the updates required for using the flat files in Release 11.1.1.x.

166 Upgrading EPM System Products

Upgrading Checklist
The following table identifies the high-level tasks that you perform to upgrade EPM System products. Some tasks apply only if you are working in an environment with multiple releases, where you are not upgrading all EPM System products.
Task Sequence 1. Review release compatibility, system requirements, and other prerequisites for this release. In particular, review release compatibility to ensure that you upgrade required EPM System components and system requirements to check whether you need to upgrade any third party components. Additional Information Oracle Hyperion Enterprise Performance Management System Installation Start Here and the Oracle Hyperion Enterprise Performance Management System Certification Matrix (http://www.oracle. com/technology/products/bi/ hyperion-supported-platforms.html) The earlier product release installation guide Prerequisites on page 168 The earlier product release installation guide Chapter 3, Installing EPM System Products

2. Back up required information (for example, databases and applications) from the earlier release. 3. Perform any upgrade-specific prerequisite tasks. 4. Stop all EPM System processes and services. 5. Install EPM System products (choosing Upgrade from an earlier release option) for the products that you are upgrading. Make sure to complete installation prerequisites for upgrading. See Upgrade Installation Prerequisites on page 48. Note: For client tier components of Performance Management Architect you must choose New Installation, even if you are upgrading from a previous release. The client components were not available in previous releases, so they are not available when you choose Upgrade From a Previous Release. 6. Configure Shared Services, and validate that Shared Services is running. Note: To configure Shared Services, in EPM System Configurator, select the Foundation tasks on the Product Selection page: Common Settings, Configure Database, Deploy to Application Server. Upgrade is selected by default. 7. Configure EPM Workspace. 8. Configure other products one at a time. 9. Using EPM System Configurator, perform the Web Server Configuration task under EPM Workspace again. Select all the components you want to configure to work with EPM Workspace. 10. Confirm that services are started, and start them if they are not started. 11. Using EPM System Diagnostics, validate the installation. 12. Complete postconfiguration product-specific tasks.

Chapter 4, Configuring EPM System Products

Chapter 4, Configuring EPM System Products Chapter 4, Configuring EPM System Products Configure EPM Workspace Services on page 89 Chapter 5, Starting and Stopping EPM System Products Chapter 6, Validating the Installation Chapter 7, Performing Postconfiguration Tasks

Upgrading Checklist 167

Task Sequence 13. Perform product-specific upgrade tasks for products that you upgraded:
l

Additional Information Upgrading Applications on page 170 and Additional Product-Specific Upgrade Tasks on page 180

If you are using Financial Management, use the Schema Upgrade Utility to upgrade applications, register applications with Shared Services, and transfer users and groups.
m

Before running the Schema Upgrade Utility, stop all Financial Management services and processes. Restart services after running the Schema Upgrade Utility.

m l l

If you are using Planning, register applications in Shared Services using Planning. Use Performance Management Architect Application Upgrade if you want to change from Classic application administration to Performance Management Architect application administration. Perform any other product-specific upgrade tasks Performing Security Related Upgrade Tasks on page 175

14. OptionalIf you are using Shared Services security for the first time, transfer users and groups to Shared Services. Note: If you want to use Performance Management Architect with Essbase, you must externalize Essbase users for both Essbase and Administration Services. The following steps apply if you are working in an environment with multiple releases, where not all products are upgraded to the latest release. 15. If you are not upgrading all products in your environment, back up the Shared Services Registry database. 16. If you are using 9.3.x releases of any of the following products, update the Shared Services Registry with information about the products.
l

Oracle Hyperion Enterprise Performance Management System Backup and Recovery Guide Working in an Environment with Multiple Releases on page 182

Essbase and Administration Services, required only if you are using Performance Management Architect to create Essbase applications. Planning (Oracle Hyperion Workforce Planning, Fusion Edition, and Oracle Hyperion Capital Asset Planning, Fusion Edition) Financial Management Performance Scorecard
l

l l

17. If you did not upgrade the following products, perform product-specific tasks:
l l

Planning Administration Services

If you are using an earlier release of Planning, see Using Reporting and Analysis 11.1.1.3 with Earlier Releases of Planning on page 186 If you are using an earlier release of Administration Services, see Using Earlier Releases of Administration Services on page 189

Prerequisites
Before upgrading, ensure you have performed all prerequisite tasks:

168 Upgrading EPM System Products

Review the Oracle Hyperion Enterprise Performance Management System Certification Matrix (http://www.oracle.com/technology/products/bi/hyperion-supportedplatforms.html) and Oracle Hyperion Enterprise Performance Management System Installation Start Here for information about the software and hardware requirements for Release 11.1.1.x, release compatibility with earlier releases, and database and Java application server requirements. Ensure that you have backed up information from the earlier release. Complete installation prerequisites for upgrading. See Upgrade Installation Prerequisites on page 48. Perform any product-specific prerequisite tasks.

Determine Which Products To Upgrade


Release 11.1.1.x is backward compatible with Releases 11.1.1.x, 9.3.x and 9.2.x. For example, after you upgrade Shared Services and EPM Workspace to Release 11.1.1.x, you can still work with Planning or Financial Management Release 9.2.x, Release 9.3.x or Release 11.1.1.0. Consult the Release Compatibility table and Limitations section in Oracle Hyperion Enterprise Performance Management System Installation Start Here to identify which product releases work together.

Backing Up the Earlier Release


Before you proceed with an upgrade, ensure that you have backed up information from the earlier release including databases, applications and other files. For instructions, see the documentation from the earlier release.

Ensure That ProductSpecific Prerequisites Are Met


Ensure that you meet the following requirements for the specified products:
l

If you manually deployed EPM System products using Oracle Application Server, you must manually undeploy all products before you start EPM System Configurator. Before upgrading Shared Services, check that all applications are assigned to a project because they cannot be 'unassigned' when you upgrade. If you are using Strategic Finance with the built-in NTLM security in your previous release, before upgrading you need to perform an additional task. Using the previous release, either migrate existing Strategic Finance built-in NTLM users to Active Directory or native users in Shared Services before upgrading Strategic Finance.
Note: If you are also upgrading from a previous release of Shared Services, you may migrate

Strategic Finance built-in NTLM users to NTLM users under Shared Services for this release only. This is not an optimal solution since NTLM services is being retired in Shared Services.

Prerequisites 169

Before upgrading Strategic Finance, ensure that all server entities are checked in. Copy any custom files and client-defined fields to another directory before installing the new release.

Installing and Configuring EPM System Products


Use this guide for detailed instructions to perform the following tasks:
l

Install EPM System products. Configure EPM System products. Perform required post configuration tasks. Confirm that services are running. Validate that products are properly installed and configured.

Upgrading Applications
You perform various postconfiguration tasks to upgrade products to Release 11.1.1.x.

Upgrading Planning Applications


Planning applications are automatically upgraded during configuration. However, you must register each application in Shared Services:
Note: If you applied the 11.1.1.x maintenance release to an existing 11.1.1.x installation, the

applications are not automatically upgraded. You must log on to each application and click the Migrate button.

To register Planning applications with Shared Services:


1
Do one of the following:
l

For Classic applications: a. Within EPM Workspace , select Classic Application Administration, then Planning Administration. b. Register each application in Shared Services. For Performance Management Architect applications: a. Within EPM Workspace , open Application Library. b. Right-click on each Planning application, then select Reregister c. Click Reregister

Select Navigate, then Applications, then Planning, and then Refresh.

All applications should appear on the list.

170 Upgrading EPM System Products

If you are upgrading from Planning release 9.3.x or later to the current release, you must provision users. See Provisioning Planning Users on page 175.

Upgrading Financial Management Applications


If you want to use applications from prior releases, you must use the Schema Upgrade utility to upgrade the applications. This utility which is installed in the Server directory when Financial Management is installed, runs on the application server. It performs several functions: upgrades applications by converting database tables, registers applications with Shared Services, and migrates users and their roles from the earlier release. Prerequisites Before you use the Schema Upgrade utility, you must complete these tasks:
l

Shared Services must be installed, configured and running, and you must create a project. Financial Management must be registered in Shared Services, which configures external authentication. You must configure Financial Management and you must have an available Financial Management Web server.
Note: If your RDBMS is configured to use a comma (,) as a decimal character, you must

change that configuration to use a period (.) since the utility assumes that the decimal character is a period. Once you have completed running the upgrade utility, you may change it back again.
Note: Web data grids that you created in prior releases with Java applets are supported after

you upgrade, however, data grids that you created using HTML in prior releases are not supported or viewable after you run the upgrade utility.
l

Before running the Financial Management Schema Upgrade Utility, stop all Financial Management services and processes on all application servers.

When you run the utility, the Schema Upgrade utility upgrades all applications. If it is determined that security needs to be migrated, the migration utility is launched on the first instance and used for subsequent applications. To use the utility, you need to know the Shared Services URL, the Financial Management project to which you want to migrate, the Web URL used for security administration, and an administrator name and password. It converts the tables and migrates the users from your Financial Management application to Shared Services for all applications. Security Migration The Schema Upgrade utility assigns these roles to all Financial Management Application Administrators when an application is upgraded:
l

Dimension Editor Application Creator

Upgrading Applications 171

Financial Management Application Creator

These roles are required to access both Performance Management Architect and Classic Application Administration.
Note: The Load System role that enables users to load metadata is not automatically assigned.

For information on assigning roles, see the Oracle Hyperion Enterprise Performance Management System Security Administration Guide. If you are upgrading an application from an earlier release, during the upgrading process, the system stores security load files used in the user migration in your system Temp directory, so you can also review that directory for results. The security filenames are HFMSecurityFile_application name_month-date-year.sec. Oracle recommends that after completing the upgrading process, you manually extract the security files from each application to save for backup and future reference. Users are validated during the upgrading process, so users who no longer exist in external security do not load. After upgrading, you can view results in the log file in the system Temp directory. The log file is named HFMSecurityFile_application name_month-date-year.log.
Note: The utility recognizes the security files based on the application name and month, date,

and year. If for any reason the upgrading process fails and you restart it on a different day, you must manually adjust and reload the files.

Using the Financial Management Schema Upgrade Utility


To upgrade applications:
1
Navigate to the Financial Management installation directory, and locate the Server directory, for example:
C:/Hyperion/products/FinancialManagement/Server.

2 3 4 5

Stop all Financial Management services and processes on all application servers. From the Server directory, double-click the Upgrade utility file, HFM Schema Upgrade.exe. From the Schema Upgrade window, click Connect to connect to the Financial Management database.

All applications with the defined database are displayed in the Available Applications section.
For Error Handling, select an option:
l

Halt on Any Error Ignore Errors and Continue

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

For Log File Name, enter an upgrade error log name.

172 Upgrading EPM System Products

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

For Logging Options, select an option:


l

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

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

Click Upgrade.

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

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

If the utility detects that users need to be migrated, the User Migration dialog box is displayed.

10 From User Migration, enter the information to provision the application and click OK:
a. For User Management URL, enter the URL that you use for Shared Services, for example, http://Shared Services server:58080/interop. b. For User Management Project, enter the name of the project that you created. c. For Financial Management Web Server URL for Security Administration, enter the Financial Management URL for security administration. d. For Administrator Logon, enter the domain, username, and password. The user must be a Shared Services administrator.
Note: After you specify this information the first time, the system uses it to upgrade

subsequent applications.

11 When you receive the Processing Complete message, click OK. 12 Optional: To view the error log after upgrading, click View Log. 13 Click Close. 14 Restart services.

Moving Classic Applications to Performance Management Architect


To use Performance Management Architect for application administration, you use the procedure in this section.
Note: Applications must be upgraded to Release 11.1.1.x before they are moved.

If you move an application created in Classic Application Administration to Performance Management Architect, the application cannot return to Classic Application Administration.
Upgrading Applications 173

Tasks To Complete Before You Move Applications


l

If you are using flat files created in an earlier release of Planning, see the Appendix of the Oracle Hyperion Enterprise Performance Management Architect Administrators Guide for information about the updates required for using the flat files in Release 11.1.1.x. Before moving a Classic Planning application to Performance Management Architect, remove any spaces in the names of attribute dimensions. For example, rename an attribute called Extra Small to ExtraSmall Before a Classic Planning application is moved to Performance Management Architect, all users must be logged off the application. You can notify users by sending a broadcast message, as described in Using Broadcast Messaging in the Oracle Hyperion Planning Administrator's Guide. To enable support for Performance Management Architect applications, the Financial Management Application Server must have IIS installed. However, the ASP components need not be enabled.

To move upgraded applications to Performance Management Architect:


1 2
In Workspace, select Navigate, then Administer, and then Application Upgrade. Review the Welcome screen, and click Next.

The Upgrade Summary page displays the applications to which the user has access to upgrade (this information is provided from the Shared Services server. If an application cannot be upgraded, an explanation is provided.)

3 4 5 6 7 8

On the Select Applications page, add applications that you want to upgrade to the Applications to Upgrade list and click Next. Review the summary of applications to upgrade, and click Next to execute the upgrade. Click Finish to view the upgrade process in the Job Console. Open the Application Library to confirm that the applications are in Performance Management Architect. Navigate to Dimension Library, and review the dimensions that were added to Performance Management Architect. Open the application.

Note: If the transfer of applications to Performance Management Architect is not successful,

you can view detailed information about the transfer in the Import Job log in the Job Console.
Note: When a Planning application is moved to Performance Management Architect, the first

occurrence of a member in Planning is shared, after the upgrade, the member remains shared, and the hierarchies in Planning and Performance Management Architect are identical.

174 Upgrading EPM System Products

Migrating Business Rules to Calculation Manager


If you are using Planning and want to migrate your existing business rules to Calculation Manager, see Part III, Managing Business Rules, of the Oracle Hyperion Enterprise Performance Management Architect Administrator's Guide.

Migrating Business Rules Security


After you migrate business rules to Calculation Manager and deploy Planning applications, you must migrate business rules security. See the Oracle Hyperion Planning Administrator's Guide.

Performing Security Related Upgrade Tasks


This section outlines tasks related to the external authentication and the unique identity attribute.

Provisioning Planning Users


After you upgrade from Planning release 9.3.x or later to the current release, you must provision the owner of your Planning applications with the Dimension Editor role and the Application Creator role. Perform this step before you log in to Planning. See the Oracle Hyperion Enterprise Performance Management System Security Administration Guide for more information.

Transferring Users and Groups


If you are using a product (such as Essbase, Strategic Finance, or Performance Scorecard) and did not use Shared Services security before, use these procedures to transfer users and groups for the first time to Shared Services.
Note: If you used Shared Services security in the earlier release, you can skip this procedure.

Transferring Essbase Users and Groups to Shared Services


By default, Essbase is externally configured when installed. If this is the first time using Shared Services security, you must transfer Essbase Server and existing Essbase users and groups to Shared Services security mode.
Caution!

When you migrate to Shared Services, Essbase users and groups are converted to equivalent roles in Shared Services. Shared Services creates a read-only superuser with the user ID named admin. If Essbase contains a user ID named admin, that user ID cannot be migrated to Shared Services. Before migrating, change the admin user ID (for example, from admin to asadmin). To edit the security file in your Essbase installation, use Administration Services Console or MaxL.

Performing Security Related Upgrade Tasks 175

For detailed instructions, see the online help for Administration Services.

Transferring Administration Services Users and Groups


Use the Externalize Users Wizard in Administration Services to transfer Administration Services users to Shared Services. The wizard detects any users who are currently authenticated through native Essbase security, or who were externally authenticated earlier than this release. The wizard attempts to match native users with corresponding users in external authentication providers that your organization has configured for authentication through Shared Services, or with users in the native Shared Services directory. If a match is not found in an external provider, you can choose to create the user as a native Shared Services user, or if the user is no longer needed natively or in Shared Services, you can go back and delete the native user. To run this wizard for Administration Services users, you must have native Administrator permissions and must already be externalized to Shared Services. To run this wizard for Essbase users, you must have native Administrator (formerly Supervisor) permissions.
Note: All external authentication providers must be running when you run the migration. If a

matching user is found, security information for the user is migrated to Shared Services. The wizard attempts to externalize all native users who have not yet been externalized; therefore, you can run this wizard iteratively to externalize all users.
Note: The currently logged-on Administration Server user is the only user visible under the

Administration Server node (under Users) in Enterprise View. However, the Externalize Users Wizard enables you to migrate all users who exist on Administration Server, even though you cannot view the users in Enterprise View. For detailed instructions, see the online help for Administration Services.

Transferring Financial Management Users to Shared Services


Financial Management users and their roles are transferred to Shared Services using the Schema Upgrade Utility. See Upgrading Financial Management Applications on page 171.

Transferring Existing Performance Scorecard Users to Shared Services


If this is the first time you have configured Performance Scorecard for use with Shared Services , you must transfer the users and user groups from Performance Scorecard . Before performing a transfer, the following tasks must be performed:
l

Ensure that the Performance Scorecard Administrator exists in Shared Services, and has been assigned the security role of Provisioning Manager.

176 Upgrading EPM System Products

Ensure that the Performance Scorecard application has been registered and assigned to a project in Shared Services. Ensure that all employee e-mail addresses are in a valid and correct format, such as user@domain.domain_suffix. If there is a user with an incorrect e-mail address, transfer might fail.

To transfer users and groups to Shared Services from Performance Scorecard:


1 2 3 4
Ensure the Shared Services server is running. Log on to Performance Scorecard as an Administrator. From Performance Scorecard, select Administration then User Provisioning Migration.

The Shared Services Administrator For Migration page is displayed.


Enter the User ID and Password for the Administrator.

The transfer administrator must exist in Shared Services, and assigned as Provisioning Manager.

5 6

Click Next to display the Pre-Migration Check page. Click Perform Pre-Migration Check to verify existing data, and create database tables for the migration. As the verification progresses, appropriate status messages are displayed. A message is shown when the pre-migration progress check is complete. Click OK to dismiss the message and continue. Click Next to display the Externalize Users page.

The page shows a list of all users in the model, their details and service provider. The Migration Action status is displayed as Migrate.

8 9

For each user that you DO NOT WANT to include in the migration, click Edit. The Migration dialog box is displayed. From Migration Action, select Do Not Migrate for the selected user, then click Save.

This user will not be included in the one-time migration. In future, if the user needs to be added to the Shared Services list, you must add the user individually.

10 Repeat step 9 for each user that you want to exclude from the migration. 11 Optional: When the list of users is complete, select the Externalize Groups tab to select the groups that
you want to migrate.

The page shows a list of all groups in the model, the details and service provider. The Migration Action status is displayed as Migrate.

12 For each group that you DO NOT WANT to include in the migration, click Edit.
The Migration dialog box is displayed.

13 From Migration Action, select Do Not Migrate for the selected group, then click Save.
This group will not be included in the one time migration. In future, if the group needs to be added to the Shared Services list, you must add the group individually.

14 Repeat step 13 for each group that you want to exclude from the migration. 15 When the list of groups is complete, click Next to display the Migration to Shared Services page.

Performing Security Related Upgrade Tasks 177

16 Click Test migration.


A confirmation is displayed when the test migration process has been successfully completed. Click OK to dismiss the message. If a problem is indicated in the migration status messages, correct any errors and try again.

17 Click Migrate to begin the migration process.


The progress of the migration is indicated by the Migration status messages. A message is displayed to advise the migration has been successfully completed. All migrated users and groups are displayed, and have the inherited Performance Scorecard attributes for their security roles.

Transferring Existing Strategic Finance Users to Shared Services


If this is the first time you have configured Strategic Finance for use with Shared Services , you must transfer the users and user groups from Strategic Finance.
Note: Before you can perform this task, you must go to Shared Services and set up the user name

you are using for the installation as a Provisioning Manager and Administrator. Refer to the Oracle Hyperion Enterprise Performance Management System Security Administration Guide.
Caution!

If you are using Strategic Finance with the built-in NTLM security in your previous release, before upgrading you need to perform an additional task. Before upgrading, use the previous release to migrate existing Strategic Finance built-in NTLM users to either Active Directory or native users in Shared Services

Note: If you are also upgrading from a previous release of Shared Services, for this release only,

you may migrate Strategic Finance built-in NTLM users to NTLM users under Shared Services. However, this is not an optimal solution since NTLM services are being phased out for support by Shared Services.

To migrate existing Strategic Finance users to Shared Services:


1 2 3
From the Windows desktop select Start, then Programs, then Hyperion Solutions, then Strategic Finance, then Server, and then Server Administrator. When the Administrator utility prompts to ask if you wish to start migrating Strategic Finance users and user group to the newShared Services, click OK. In the Users dialog box, select an option from the Migration Action column for each user in Strategic Finance to define how each will be migrated, then click OK.

For each user, the table lists the following information:


l

The Name column lists the name of the user name as it exists in Strategic Finance.

178 Upgrading EPM System Products

The User ID column lists the name of the user name as it exists in the Standard NTLM Provider. The New Shared Services ID column lists the name of the user name as it exists in Shared Services. This column will be empty if the user does not yet exist in Shared Services. The Role column lists the user group role to be assigned in Shared Services as the user group will be created in Shared Services. The Status column indicates if the user name has been located or not. The Migration Action column enables you to define how each user will be migrated. If a user does not exist in an external directory (NTLM, MSAD, or LDAP), select one of the following options:
m

The Create Native User option will create a new user name in an external directory and migrate the user name over. If a user currently exists in Shared Services, select one of the following options: The Map to Existing User option will migrate the Strategic Finance user over to the corresponding user name in an external directory. The Dont Migrate option will not copy the user to Shared Services.

In the User Groups dialog box, select an option from the Migration Action column and the Role column for each user group in the Name column to define how each will be migrated, then click Finish.

For each user group, the table lists the following information:
l

The Name column lists the name of the user group as it exists in Strategic Finance. The Shared Services Name column lists the name of the user group as it exists in Shared Services. This column will be empty if the user does not yet exist in Shared Services. The Role column enables you to define how each user will be migrated. The Migration Action column enables you to define how each user will be migrated. If a user group does not exist in Shared Services, select one of the following options:
m

The Create Native Group option will create a new user group in Shared Services and migrate the user group over. If a user group currently exists in Shared Services, select one of the following options: The Merge option will merge the Strategic Finance user group with the corresponding user group in Shared Services. The Dont Migrate option will not copy the user group to Shared Services. Once users and user groups have been migrated from Strategic Finance to Shared Services, the Users tab of the Administrator utility will no longer be displayed, as all related functionality has been moved over to Shared Services. To verify, you can check the log file that automatically displays when the migration is complete.

Performing Security Related Upgrade Tasks 179

Transferring FDM Users to Shared Services


Use the User Provisioning Migration utility to provision users in a current FDM application to Shared Services. See the Oracle Hyperion Financial Data Quality Management Configuration Guide for detailed instructions.

Implementing the Unique Identity Attribute


After you upgrade, if you were using the location-specific identity attribute DN, Oracle recommends that you use a provider-specific identity attribute, (for example, orclguid for OID, nsuniqueid for SunONE, and ObjectGUID for MSAD). See the Oracle Hyperion Enterprise Performance Management System Security Administration Guide for information.

Additional Product-Specific Upgrade Tasks


Refreshing the Performance Management Architect User Interface
To ensure that the text labels are displayed correctly in the Performance Management Architect user interface, after upgrading, delete temporary internet files in Internet Explorer.

Upgrading Essbase to Release 11.1.1.x


The following are product specific tasks for upgrading Essbase to Release 11.1.1.x.

Upgrading Essbase Databases


After upgrading, you can restore databases from earlier releases of Essbase Server from backups. Before proceeding, familiarize yourself with using MaxL statements. See the MaxL section of the Oracle Essbase Technical Reference.

To upgrade Essbase databases to Release 11.1.1.x:


1 2 3
Select a database or load an application. Use the alter database validate MaxL statement against the upgraded database. If the validation returns to the log file only LRO-related errors, restore data from the earlier backup and re-create the LROs:

a. Either restore data from a backup of the database that does not contain LROs, or load from a database export. b. Restart the database in Essbase Release 11.1.1.x. Essbase upgrades the database to Release 11.1.1.x format, if the database is restored.

180 Upgrading EPM System Products

c. Validate the database by using the alter database validate MaxL statement. d. Recreate the LROs, using the LISTLINKEDOBJECTS output as a guide. You may need to manually review the output from LISTLINKEDOBJECTS to verify completeness.

4 5

Upon successful completion, unload the database, and then back up the Release 11.1.1.x database files. Repeat these steps for each database that you want to upgrade.

Note: Essbase Server upgrades a database when the database is started. Upgraded kernel files are

not backward-compatible with the earlier release.

How Cache Sizes are Affected by Upgrades


If you are currently running Essbase using direct I/O, and you plan to use buffered I/O (the default) after the upgrade, you may need to reduce the cache size settings. For information about I/O access modes and about setting cache sizes, see the Oracle Essbase Database Administrator's Guide.

Upgrading Reporting and Analysis


If you are using Web Analysis, or Oracle's Hyperion SQR Production Reporting, there is an additional upgrade task to perform.

Upgrading Web Analysis


To decrypt previously stored passwords:
1 2 3
Log on to EPM Workspace Agent Configuration and Monitoring Console (CMC). In Web Application Configuration View, open properties for the Web Analysis Web Application. Switch to the Other tab and set DecryptOldPasswords to Yes.

Upgrading Production Reporting


To update SQR Server locations:
1 2 3
Log on to Service Configurator. Open Job Factory (JF) properties, PR tab. Update locations for all Production Reporting (PR) servers using new locations, for example: C:/ Hyperion/products/biplus/bin/SQR/Server/Oracle/bin.

Additional Product-Specific Upgrade Tasks 181

Upgrading Strategic Finance


Data Conversion After Upgrade
If you are using the Strategic Finance client as a standalone program, data conversion is simple. After the software is installed, open your existing.alc files in the new release, and Strategic Finance converts your data to the upgraded format. Save the converted file. If you are using a Client-Server implementation and point the upgraded Strategic Finance server to an existing database during configuration, it converts that database upon first startup, and as each entity is opened at user request. The administrator may also force one or more entities in the database by using the Strategic Finance Administrator Utility.

New Port Used by Strategic Finance


In releases earlier than 9.3.x, Strategic Finance used port 1493. Since Release 9.3.x, the default port used for Strategic Finance is 7750. It may be necessary to select the new port number for connections configured on workstations that had clients installed previously.

Upgrading Customized Systems


Copy custom files and client-defined fields to another directory before removing the earlier release. After installing this release and restarting the client or server, copy custom files to the program directories of the client and server:
Caution!

If the client or server starts without these files, your customizations are not implemented.

custom.coa files. E.g.your company.coa


currdata.dat consdata.dat convert.idx

Working in an Environment with Multiple Releases


To enable EPM System products from the 9.3.x release to work with the current release of Shared Services (a mixed release environment), you must update the Shared Services Registry. During configuration of 11.1.1.x products, EPM System Configurator automatically updates the Shared Services Registry with components for each product. For 9.3.x products, you must create these components manually by editing the Shared Services Registry. The epmsys_registry utility is provided to make these edits.

182 Upgrading EPM System Products

These steps are required only for 9.3.x releases of EPM System products (9.3.1 for Essbase); they are not required if you are using 9.2.x releases of EPM System products. The following products are supported in this scenario:
l

Financial Management Performance Scorecard Planning Essbase and Administration Services, required only if you are using Performance Management Architect to create Essbase applications.

To update the Shared Services Registry with information for applicable 9.3.x products:
1
Make sure you have upgraded to the current release of Shared Services and backed up the Shared Services Registry database.

When you upgrade to the current release of Shared Services, templates are installed to HYPERION_HOME/common/config/9.5.0.0/resources/mixedrelease. The templates are provided to simplify making updates to the Shared Services Registry.
Tip: Back up the templates before you proceed. You might need to refer to them later.

Review which template files you need to edit, based on the products you have.
Table 63

Templates for Working in a Mixed-Release Environment When to Use If you are using Essbase release 9.3.1 with Performance Management Architect to create Essbase applications. If you are using Planning release 9.3.x. If you are using Performance Scorecard release 9.3.x. What it Does Creates the 9.3.1 Essbase component hierarchy and adds entries for one or more instances of Essbase Server release 9.3.1 and Administration Services to the Shared Services Registry. Creates the 9.3.x Planning component hierarchy and adds entries for one or more instances of the Planning release 9.3.x Web application to the Shared Services Registry. Creates the 9.3.x Performance Scorecard component hierarchy and adds entries for one or more instances of the Performance Scorecard release 9.3.x Web Reports Web application to the Shared Services Registry. Creates the 9.3.x Financial Management component hierarchy and adds entries for one or more instances of Financial Management release 9.3.x Web application, cluster, and server to the Shared Services Registry.

File Name Essbase.xml

Planning.xml

Scorecard.xml

FinancialManagement. xml

If you are using Financial Management release 9.3.x.

If you have already used one of the previous files for a product, and later add an additional server, Web application, or cluster, use the following files to make additional updates to the Shared Services Registry.

Working in an Environment with Multiple Releases 183

Table 64

Templates to Use if You Are Adding an Additional Server, Web Application, or Cluster When to Use If you are using Essbase release 9.3.1 with Performance Management Architect to create Essbase applications, and you want to add one or more additional Essbase Servers to the Shared Services Registry. Caution! Use this file only after you have used Essbase.xml. What it Does Adds entries for one or more additional instances of Essbase Server release 9.3.1 to the Shared Services Registry. Adds entries for one or more additional Administration Services release 9.3.1 Web applications to the Shared Services Registry. Adds entries for one or more additional instances of the Planning 9.3.x Web application to the Shared Services Registry. Adds entries for one or more additional instances of the Performance Scorecard 9.3.x Web Reports Web application to the Shared Services Registry. Adds entries for one or more additional instances of the Financial Management 9.3.x Web application to the Shared Services Registry. Adds entries for one or more additional instances of the Financial Management 9.3.x cluster to the Shared Services Registry.

File Name Essbase_server.xml

Essbase_eas.xml

If you are using Administration Services release 9.3.1 with Performance Management Architect to create Essbase applications, and you want to add one or more additional Administration Services Web applications to the Shared Services Registry. Caution! Use this file only after you have used Essbase.xml.

Planning_webapp.xml

If you are using Planning release 9.3.x, and you want to add one or more additional Planning Web applications to the Shared Services Registry. Caution! Use this file only after you have used Planning.xml.

Scorecard_webapp.xml

If you are using Performance Scorecard release 9.3.x, and you want to add one or more additional Performance Scorecard Web Reports Web applications to the Shared Services Registry. Caution! Use this file only after you have used Scorecard.xml.

FinancialManagement_ webapp.xml

If you are using Financial Management release 9.3.x, and you want to add one or more additional Financial Management Web applications to the Shared Services Registry. Caution! Use this file only after you have used FinancialManagement.xml.

FinancialManagement_ cluster.xml

If you are using Financial Management release 9.3.x, and you want to add one or more additional Financial Management clusters to the Shared Services Registry. Caution! Use this file only after you have used FinancialManagement.xml. Tip: If you create a new cluster after you've completed this procedure, you must update this file again.

FinancialManagement_ server.xml

If you are using Financial Management release 9.3.x, and you want to add one or more additional Financial Management Servers to the Shared Services Registry. Caution! Use this file only after you have used FinancialManagement.xml.

Adds entries for one or more additional instances of Financial Management Server release 9.3. x to the Shared Services Registry.

On a machine hosting the 11.1.x EPM System software, edit one or more of the files in any text editor according to the instructions in the file. The files are in:
HYPERION_HOME/common/config/9.5.0.0/resources/mixedrelease

You have to make the edits on one machine only.


Note: If you enter any non-English characters while editing the templates, save the file using

UTF-8 encoding.
184 Upgrading EPM System Products

On the machine on which you edited the templates, go to HYPERION_HOME/common/config/9. 5.0.0 and for each file that you edited, run the following command:
epmsys_registry.bat createcomponenthierarchy resources/mixedrelease/file

where file is the name of the file you edited in the previous step. For each product, run epmsys_registry with the following files first: Essbase.xml, Planning.xml, Scorecard.xml, and FinancialManagement.xml. For UNIX, enter:
epmsys_registry.sh createcomponenthierarchy resources/mixedrelease/file

where file is the name of the file you edited in the previous step. For example, if you have the 9.3.x release of Essbase, Planning, and Financial Management, and you have two Planning Web applications, run the following commands:
epmsys_registry createcomponenthierarchy resources/mixedrelease/Essbase.xml epmsys_registry createcomponenthierarchy resources/mixedrelease/Planning.xml epmsys_registry createcomponenthierarchy resources/mixedrelease/ FinancialManagement.xml

The epmsys_registry utility updates the Shared Services Registry with the information you entered in the files. If you later add an additional Planning Web application, run the following command:
epmsys_registry createcomponenthierarchy resources/mixedrelease/Planning_webapp.xml

If you are using Financial Management Release 9.3.1, from the directory HYPERION_HOME/ common/config/9.5.0.0, execute the following command:
epmsys_registry addfile FINANCIAL_MANAGEMENT_PRODUCT/@EPMA_deployUI resources/ mixedrelease/HFM_EPMA_deployUI.xml

You should see the response The new property has been added to the component.

If you are using Essbase Release 9.3.1, from the directory HYPERION_HOME/common/config/9. 5.0.0, execute the following command:
epmsys_registry addfile ESSBASE_PRODUCT/@EPMA_deployUI resources/mixedrelease/ Essbase_EPMA_deployUI.xml

You should see the response The new property has been added to the component.

Run EPM System Configurator and configure EPM Workspace Web Server again. (On the Task Selection page, select the EPM Workspace Web Server Configuration task.)

Keep all products selected. You must complete the Web Server Configuration task for EPM Workspace last to ensure that all products are configured to work with EPM Workspace.

Restart the EPM Workspace Web Application and Shared Services.

Working in an Environment with Multiple Releases 185

Tip: If you realize that you made a mistake in the template files after you have already run epmsys_registry, you need to make additional edits to the Shared Services Registry to

correct the error. See Appendix F, Updating the Shared Services Registry.
Caution!

Run epmsys_registry only once with the following files: Essbase.xml, Planning.xml, Scorecard.xml, and FinancialManagement.xml.

Using Reporting and Analysis 11.1.1.3 with Earlier Releases of Planning


If you are using an earlier release of Planning with EPM Workspace 11.1.1.x and Shared Services 11.1.1.x, you must perform additional configuration steps.
Note: EPM System Installer installs the Planning ADM driver for the versions of Planning listed

in the following sections. However, if you have installed a service fix for Planning, the Planning .jar and .dll or .so files for the ADM driver must be in sync with the current version of Planning. So, for example, if you are using Planning Release 9.3.1.1.10, make sure to follow the service fix installation instructions in the Planning Readme.

Using Reporting and Analysis 11.1.1.3 with Planning 11.1.1.2


To use Reporting and Analysis 11.1.1.3 with Planning 11.1.1.2:
1 2 3 4 5 6
Stop all Financial Reporting services and the Hyperion Workspace - Agent Service. Back up and rename the folder HYPERION_HOME/common/ADM/Planning/9.5.0.0 to HYPERION_HOME/common/ADM/Planning/11.1.1.3. Rename the folder HYPERION_HOME/common/ADM/Planning/11.1.1.2 to HYPERION_HOME/common/ADM/Planning/9.5.0.0. Back up and rename the folder HYPERION_HOME/common/EssbaseRTC/9.5.0.0 to HYPERION_HOME/common/EssbaseRTC/11.1.1.3. Rename the folder HYPERION_HOME/common/EssbaseRTC/11.1.1.2 to HYPERION_HOME/ common/EssbaseRTC/9.5.0.0. Restart the services that you stopped in Step1.

Using Reporting and Analysis 11.1.1.3 with Planning 11.1.1.1


To use Reporting and Analysis 11.1.1.3 with Planning 11.1.1.1:
1 2
Stop all Financial Reporting services and the Hyperion Workspace - Agent Service. Back up and rename the folder HYPERION_HOME/common/ADM/Planning/9.5.0.0 to HYPERION_HOME/common/ADM/Planning/11.1.1.3.

186 Upgrading EPM System Products

3 4 5 6

Rename the folder HYPERION_HOME/common/ADM/Planning/11.1.1.1 to HYPERION_HOME/common/ADM/Planning/9.5.0.0. Back up and rename the folder HYPERION_HOME/common/EssbaseRTC/9.5.0.0 to HYPERION_HOME/common/EssbaseRTC/11.1.1.3. Rename the folder HYPERION_HOME/common/EssbaseRTC/11.1.1.1 to HYPERION_HOME/ common/EssbaseRTC/9.5.0.0. Restart the services that you stopped in step 1.

Using Reporting and Analysis 11.1.1.3 with Planning 11.1.1.0


To use Reporting and Analysis 11.1.1.3 with Planning 11.1.1.0:
1 2 3 4 5 6
Stop all Financial Reporting services and the Hyperion Workspace - Agent Service. Back up and rename the folder HYPERION_HOME/common/ADM/Planning/9.5.0.0 to HYPERION_HOME/common/ADM/Planning/11.1.1.3. Rename the folder HYPERION_HOME/common/ADM/Planning/11.1.1.0 to HYPERION_HOME/common/ADM/Planning/9.5.0.0. Back up and rename the folder HYPERION_HOME/common/EssbaseRTC/9.5.0.0 to HYPERION_HOME/common/EssbaseRTC/11.1.1.3. Rename the folder HYPERION_HOME/common/EssbaseRTC/11.1.1.0 to HYPERION_HOME/ common/EssbaseRTC/9.5.0.0. Restart the services that you stopped in step 1.

Using Reporting and Analysis 11.1.1.x with Planning 9.3.1:


To use Reporting and Analysis 11.1.1.x with Planning 9.3.1:
1
Edit fr.env in Hyperion_Home/products/biplus/lib as follows:
#ADM_HP_HOME=%HYPERION_HOME%/common/ADM/Planning/9.5.0 ADM_HP_HOME=%HYPERION_HOME%/common/ADM/Planning/9.3.1.0

For WebLogic, WebSphere, or Tomcat: In setCustomParamsFinancialReporting.cmd, which is found in HYPERION_HOME/deployments/AppServerType/bin/, make sure the version number in the following entry is 9.3.1.0: HYPERION_HOME/common/ADM/Planning/ version/bin. For Oracle Application Server, add the following library search path variable for your OC4J instance in Oracle Application Server console: HYPERION_HOME/common/ADM/Planning/version/ bin where version is the version of Planning that is installed. For Oracle Application Server, edit /Oracle_Home/j2ee/FinancialReporting/config/ application.xml and insert the following lines just before the entry that sets the library path to biplus/lib:
<library path="${HYPERION_HOME}\common\ADM\Planning\9.3.1.0\lib"/> <library path="C:\Hyperion\products\biplus\lib" />

Working in an Environment with Multiple Releases 187

Note: Do not remove any values from application.xml.

Restart Financial Reporting Web application and Financial Reporting Report Server service.

Using Reporting and Analysis 11.1.1.x with Planning 9.3.0.1


To use Reporting and Analysis 11.1.1.x with Planning 9.3.0.1
1
Edit fr.env to point to the correct location as follows:

The fr.env file can be found in Hyperion_Home/products/biplus/lib.


#ADM_HP_HOME=%HYPERION_HOME%/common/ADM/Planning/9.5.0 ADM_HP_HOME=%HYPERION_HOME%/common/ADM/Planning/9.3.0

For WebLogic, WebSphere, or Tomcat: In setCustomParamsFinancialReporting.cmd, which is found in HYPERION_HOME/deployments/AppServerType/bin/, make sure the version number in the following entry is 9.3.0: HYPERION_HOME/common/ADM/Planning/version/ bin. For Oracle Application Server, add the following library search path variable for your OC4J instance in Oracle Application Server console: HYPERION_HOME/common/ADM/Planning/version/ bin where version is the version of Planning that is installed. For Oracle Application Server, edit /Oracle_Home/j2ee/FinancialReporting/config/ application.xml and insert the following lines just before the entry that sets the library path to biplus/lib:
<library path="${HYPERION_HOME}\common\ADM\Planning\9.3.0\lib"/> <library path="C:\Hyperion\products\biplus\lib" /> Note: Do not remove any values from application.xml.

Restart Financial Reporting Services.

Using Reporting and Analysis 11.1.1.x with Planning 9.2.1


To use Reporting and Analysis 11.1.1.x with Planning 9.2.1:
1
Edit fr.env to point to the correct location as follows:

The fr.env file can be found in Hyperion_Home/products/biplus/lib.


#ADM_HP_HOME=%HYPERION_HOME%/common/ADM/Planning/9.5.0 ADM_HP_HOME=%HYPERION_HOME%/common/ADM/Planning/9.2.1

For WebLogic, WebSphere, or Tomcat: In setCustomParamsFinancialReporting.cmd, which is found in HYPERION_HOME/deployments/AppServerType/bin/, make sure the version number in the following entry is 9.2.1: HYPERION_HOME/common/ADM/Planning/version/ bin. For Oracle Application Server, add the following library search path variable for your OC4J instance in Oracle Application Server console: HYPERION_HOME/common/ADM/Planning/version/ bin where version is the version of Planning that is installed.

188 Upgrading EPM System Products

For Oracle Application Server, edit /Oracle_Home/j2ee/FinancialReporting/config/ application.xml and insert the following lines just before the entry that sets the library path to biplus/lib:
<library path="${HYPERION_HOME}\common\ADM\Planning\9.2.1\lib"/> <library path="C:\Hyperion\products\biplus\lib" /> Note: Do not remove any values from application.xml.

Restart Financial Reporting Services.

Using Reporting and Analysis 11.1.1.x with Planning 9.2.0.3


To use Reporting and Analysis 11.1.1.x with Planning 9.2.0.3:
1
Edit fr.env to point to the correct location as follows:

The fr.env file can be found in Hyperion_Home/products/biplus/lib.


#ADM_HP_HOME=%HYPERION_HOME%/common/ADM/Planning/9.5.0 ADM_HP_HOME=%HYPERION_HOME%/common/ADM/Planning/9.2.0

For WebLogic, WebSphere, or Tomcat: In setCustomParamsFinancialReporting.cmd, which is found in HYPERION_HOME/deployments/AppServerType/bin/, make sure the version number in the following entry is 9.2.0: HYPERION_HOME/common/ADM/Planning/version/ bin. For Oracle Application Server, add the following library search path variable for your OC4J instance in Oracle Application Server console: HYPERION_HOME/common/ADM/Planning/version/ bin where version is the version of Planning that is installed. For Oracle Application Server, edit /Oracle_Home/j2ee/FinancialReporting/config/ application.xml and insert the following lines just before the entry that sets the library path to biplus/lib:
<library path="${HYPERION_HOME}\common\ADM\Planning\9.2.0\lib"/> <library path="C:\Hyperion\products\biplus\lib" /> Note: Do not remove any values from application.xml.

Restart Financial Reporting Services.

Using Earlier Releases of Administration Services


If you are upgrading Provider Services from Release 9.2.0.3 to Release 11.1.1.x, and if you are not upgrading Administration Services from 9.2.0.3, then, you must complete the following steps: 1. Close the Administration Services Console. 2. Copy APS_11.1.1_INSTALL_PATH/lib/ess_es_gui.jar to EAS_INSTALL/ console/lib (overwrite the existing ess_es_gui.jar file).

Working in an Environment with Multiple Releases 189

3. Restart the Administration Services Console. 4. Administer through the Hyperion Provider Services node in the Administration Services Console.

Upgrading from EPM System Release 9.3.x After Working in An Environment with Multiple Releases
If you have been working in an environment with multiple releases, where not all products were upgraded to EPM System Release 11.1.1.x, and now you want to upgrade products to the current release, you must first update the Shared Services Registry to remove the information for applicable 9.3.x products. After you update the Shared Services Registry, you can proceed with upgrading EPM System products. The following Release 9.3.x products are supported in this scenario:
l

Financial Management Performance Scorecard Planning Essbase and Administration Services

Tip: For more information about editing the Shared Services Registry, see Appendix F,

Updating the Shared Services Registry.

To upgrade a product from Release 9.3.x after you have been working in an environment
with multiple releases:

1 2

Back up the Shared Services Registry. On a machine hosting the 11.1.x EPM System software, go to HYPERION_HOME/common/ config/9.5.0.0 and run the following command:
epmsys_registry view componentType

where componentType is one of the following values, depending on which 9.3.x product you have installed:
l

Planning_Product Essbase_Product Financial_Management_Product Performance_Scorecard_Product

3 4

From the display, note the Component ID. Run the following command:
HYPERION_HOME/common/config/9.5.0.0/epmsys_registry updateproperty #componentID/ @version 9.5.0.0

190 Upgrading EPM System Products

where componentID is the component's ID you found when you viewed the component hierarchy.

Run the following command to get the Component IDs of the logical Web applications that are associated with the product.
HYPERION_HOME/common/config/9.5.0.0/epmsys_registry view componentType/ Logical_Web_App

where componentType is one of the following, depending on which product you have:
l

Planning_Product Essbase_Product Financial_Management_Product Performance_Scorecard_Product

6 7

From the display, note the Component ID or IDs. For each Logical_Web_App Component ID, run the following command:
HYPERION_HOME/common/config/9.5.0.0/epmsys_registry updateproperty #componentID/ @version 9.5.0.0

where componentID is the component's ID you found when you viewed the component hierarchy.

8 9

Repeat the previous steps for each applicable 9.3.x product. Upgrade applicable 9.3.x products, following the steps in Upgrading Checklist on page 167.

10 Restart EPM Workspace and Shared Services.

Working in an Environment with Multiple Releases 191

192 Upgrading EPM System Products

9
In This Chapter

Reconfiguring EPM System Products

Reconfiguring for SSL.................................................................................... 193 Redeploying to a Different Web Application Server Type............................................. 193 Changing Repository Passwords........................................................................ 195 Reconfiguring Ports ...................................................................................... 197

EPM System Configurator enables you to reconfigure products to incorporate changes in your environment. To reconfigure, launch EPM System Configurator on the computer hosting the product, and follow the procedures in Chapter 4, Configuring EPM System Products. Note the following information about reconfiguring:
l

If you are reconfiguring the application server for Shared Services, you must also reconfigure the relational database. If you reconfigure a database, restart the Web application server afterward. If you reconfigure to change a port or server, you must also reconfigure the EPM Workspace Web server and then restart the EPM Workspace Web application.

Reconfiguring for SSL


If you want to change from an SSL-enabled environment to a non-SSL enabled environment, or vice versa, you must use EPM System Configurator to reconfigure all EPM System products, selecting the following configuration tasks:
l

Common Settings Change the Enable SSL for communications option Deploy to Application Server Redeploy all Web applications Configure Web server Reconfigure the Web server

Redeploying to a Different Web Application Server Type


If you have already installed and configured EPM System products and deployed applications to a Web application server, and you want to deploy to a different Web application server type, you can do so using the following procedures. You can redeploy while you are applying a

Reconfiguring for SSL 193

maintenance release or at any time by running EPM System Configurator and selecting the new Web application server type for deployment.
Note: You cannot mix Web application server types for the deployment within a single

installation of EPM System. You must redeploy all Web applications to the same Web application server type if you want to change the Web application server type.

Redeploying from the Embedded Java Container or WebSphere to WebLogic Server


If you previously deployed products to Embedded Java Container or WebSphere, you can redeploy to WebLogic Server during configuration with EPM System Configurator.

To migrate the EPM System product deployment from the Embedded Java Container or
WebSphere to WebLogic Server:

1 2 3

Stop all the services for EPM System products and for the Web application server (Hyperion Apache 2.0 service or the WebSphere service). Navigate to HYPERION_HOME/common/httpServers/Apache/2.0.59/conf/ and open httpd.conf in a text editor. Scroll to the end of file and make the following edits, depending on your Web application server.
l

For Embedded Java container, remove the lines starting with Include conf/ HYSLTomcat-autogenerated.conf (the number of these directives depends on the number of configured components). For WebSphere, remove the lines starting with Include conf/ WebSphereautogenerated.conf (the number of these directives depends on the number of configured components).

4 5

Start EPM System Configurator, and select the Deploy to Application Server task for all the currently deployed applications. During configuration, select WebLogic Server. Configure EPM Workspace Web Server last.

You must complete the Web Server Configuration task for EPM Workspace last to ensure that all products are configured to work with EPM Workspace.

Redeploying Applications from Oracle Application Server to WebLogic Server


To redeploy applications from the Oracle Application Server to WebLogic Server:
1 2
Stop all the Web applications and services for EPM System products and stop all Oracle Application Server OPMN services. Start EPM System Configurator, and select the Deploy to Application Server tasks for all the currently deployed applications. During configuration, select WebLogic Server.

194 Reconfiguring EPM System Products

Configure EPM Workspace Web Server last.

You must complete the Web Server Configuration task for EPM Workspace last to ensure that all products are configured to work with EPM Workspace.

Changing Repository Passwords


For EPM System products that require a database repository, you can change repository passwords after product deployments. After changing database repository passwords, restart EPM System products as described in Chapter 5, Starting and Stopping EPM System Products.

Changing the Shared Services and Registry Repository Password


If you are working in a distributed environment, repeat this procedure on each machine in the deployment.

To change the password for the Shared Services and Registry repository:
1 2 3 4 5 6 7
Using the database administration console, change the password of the user account that was used to configure the Shared Services database. Stop EPM System Web applications and services and processes. Start EPM System Configurator, and under the Foundation tasks, select Configure Database. On the Shared Services and Registry Database Configuration page, select Connect to a previously configured Shared Services database. Keeping the existing database and user, enter the new password for the user account that was used to configure the Shared Services database. Continue the configuration, and click Finish when you are done. Restart the Web applications and services and processes.

Changing EPM System Product Repository Passwords


To change the password for the repository for EPM System products other than Shared
Services:

1 2 3 4

Using the database administration console, change the password of the user account that was used to configure the EPM System product database. Stop EPM System Web applications and services and processes. Start EPM System Configurator, and under the product you want to configure, select Configure Database. On the Database Configuration page, select Perform 1st-time configuration of database.

Changing Repository Passwords 195

5 6 7 8

Specify the existing database and user, and enter the new password for the user account that was used to configure the EPM System product database. When you are prompted to choose whether to Drop and recreate tables or Reuse the existing database, select Reuse the existing database. Continue the configuration, and click Finish when you are done. Restart the Web application and services and processes.

Changing the Planning Applications Repository Password


Use Edit Datasource in the Classic Planning Application wizard to change the Applications repository password. See Oracle Hyperion Planning Administrator's Guide.

Changing the Performance Management Architect Interface Datasource Password


Perform the following procedure if you are using the Interface Data Source configuration with Performance Management Architect applications.

To change the Performance Management Architect Interface Data Source password:


1 2 3 4 5 6
In the database, change the password. Run EPM System Configurator. On the Task Selection page, in the Performance Management Architect area, select Interface DataSource Configuration. Select Edit an existing datasource link, and then select the datasource link. On the database configuration details page, enter the new password. Deselect Create Interface Tables, if it is selected. Continue the configuration, and click Finish when you are done.

Changing the FDM Repository Password


To change the FDM repository password using FDM Workbench:
1 2 3 4 5 6 7
In the database, change the password. From FDM Workbench, choose Add Application and log in. Choose the application for which you want to change the repository and select Modify. Select the Database tab and replace the existing password with the new password. Click OK. Click OK on the Application screen. Ensure that you can log in to the application.

196 Reconfiguring EPM System Products

To change the FDM repository password using FDM Web:


1 2 3 4 5 6
In the database, change the password. From the FDM Web logon screen, choose Add Application and log in. Choose the application for which you want to change the repository password and select Modify. Click OK. Click Close. 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 2 3 4 5 6 7 8
Stop Data Relationship Management. In the database, change the password. Open the Data Relationship Management console. Go to Database Settings. In Database Login, enter the new password. To test the new password, select connect. Enter the password again and select OK.

You should see a message, Successfully connected to database.


Restart Data Relationship Management.

Reconfiguring Ports
For information about ports, port numbers, and how to configure ports, see Ports in Oracle Hyperion Enterprise Performance Management System Installation Start Here.

Reconfiguring Ports 197

198 Reconfiguring EPM System Products

10
In This Chapter

Deployment Scenarios

Considerations for Distributed Environments.......................................................... 199 Adding Servers to a Financial Management Deployment ............................................ 200

Considerations for Distributed Environments


Note the following about product installations if you are working in a distributed environment:
l

If you are installing multiple instance of Essbase Server on a single computer, see Installing Additional Instances of Essbase Server on page 62. EPM System products support only one instance of Shared Services. A single instance of a product does not recognize a second instance of Shared Services. You can have only one instance of Shared Services in a deployment. For EPM Workspace, EPM System Configurator requires that you install the Web server and the Web application server on the same machine (the machine on which you install EPM Workspace). If you want to have the Web server and the Web application server on separate machines, you must perform manual configuration steps. See the Oracle Hyperion Enterprise Performance Management System Manual Deployment Guide for information. If you are using Financial Management and EPM Workspace with IIS, you must install Financial Management Web applications and EPM Workspace on the same box. If you are using FDM and EPM Workspace with IIS, you must install the FDM Web application and EPM Workspace on the same box. EPM Workspace and the application being integrated must be deployed to the same Web application server type. For example, if EPM Workspace is deployed to Oracle Application Server, Performance Management Architect must also be deployed to Oracle Application Server. If an application being integrated does not support the EPM Workspace Web application server, redeploy EPM Workspace to a commonly supported Web application server (Oracle WebLogic Server). When using Financial Management as a data source, for performance reasons, running both Reporting and Analysis and Financial Management on a Windows platform is highly recommended. Deploying Financial Management and Reporting and Analysis in a mixed environment of Windows and UNIX may result in unsatisfactory performance. You can have only one instance of Financial Reporting Scheduler service running in your environment.

Considerations for Distributed Environments 199

Adding Servers to a Financial Management Deployment


The following procedure defines an overview of the recommended process for adding servers to the Financial Management environment, defining clusters, and adding servers to the clusters.

To add servers to your Financial Management environment:


1 2 3 4 5
After you install Financial Management on a new server or servers, run EPM System Configurator on all new servers and select the Configure Application Server task. Run EPM System Configurator on any one application server and select the Configure Application Cluster task to define clusters and add or remove servers to clusters. Run EPM System Configurator on any application or Web server and select the Register Application Servers/Cluster task. Restart EPM Workspace services. In EPM Workspace, register each application against the preferred cluster. See the Oracle Enterprise Performance Management Workspace Administrator's Guide.

200 Deployment Scenarios

11
In This Chapter

Uninstalling EPM System

Uninstalling EPM System Products ..................................................................... 201 Performing a Silent Uninstallation...................................................................... 203

You can uninstall this release of EPM System products using EPM System Uninstaller. You can also perform a silent uninstallation. When you uninstall EPM System products, EPM System Uninstaller:
l

Stops and removes installed services. Un-deploys installed Web applications. Removes desktop icons and start menu icons. Clears the product installation directory of all files. Removes appropriate entries from the Windows registry. Removes appropriate entries from the Shared Services Registry. Removes appropriate entries (such as virtual directories) from IIS. Removes appropriate entries from the OUI inventory (Oracle installation files list used for patching purposes). When you uninstall EPM System products, EPM System Uninstaller removes everything from the installation directory. Before you uninstall, be sure to back up any files you want to keep that are in HYPERION_HOME. For information about backing up files, see Oracle Hyperion Enterprise Performance Management System Backup and Recovery Guide. EPM System Uninstaller does preserve the Essbase / app directory, security file (essbase.sec), and configuration file (essbase.cfg).

Caution!

Uninstalling EPM System Products


To uninstall EPM System products:
1
Choose a method:
l

(Windows) In HYPERION_HOME/uninstall, double-click uninstall.cmd.

Uninstalling EPM System Products 201

(Windows) In the Windows Control Panel, select Add or Remove Programs, select Hyperion EPM System, and click Change/Remove. (Windows) From a Windows console, change to HYPERION_HOME/uninstall/, and then enter uninstall.cmd. From the Start menu, select Programs, then Oracle EPM System, then Foundation Services, and then Uninstall EPM System. (UNIX) Change to the HYPERION_HOME/uninstall directory and type ./ uninstall.sh. (UNIX) Change to the HYPERION_HOME/uninstall directory and type ./ uninstall.sh console.

2 3

Exit other programs before you continue, and then click Next. Select the products to uninstall, and then click Next. All components of the selected products are uninstalled.

For example, if you uninstall any Essbase component, EPM System Uninstaller uninstalls all Essbase components. All installed products are selected by default. Select Deselect All Products to clear the selections for all products, and then select only the products you want to uninstall. If multiple versions of Essbase Server are installed, select the instance to uninstall. Determine the instance by looking at the installation location in the Location column. If you uninstall any Reporting and Analysis component, all other Reporting and Analysis components are disabled.

4 5

Specify whether you want to delete all the files and directories in the Hyperion home directory.

If you select this option, data and customized files will be deleted.
Confirm the products to uninstall, and then click Next.

EPM System Uninstaller displays progress incrementally as each assembly's uninstallation is complete.
Note: To cancel the uninstallation, click Cancel. When you click Cancel, EPM System

Uninstaller stops the uninstallation of the current assembly and rolls that assembly back to an installed state. It does not undo uninstallations for assemblies that were already uninstalled. EPM System Uninstaller indicates the success or failure of the uninstallation. If any part of the uninstallation failed, EPM System Uninstaller notes which assembly failed to uninstall. Check the log files for more information about the errors. You can find the log files in HYPERION_HOME/logs/install. There is a log file for each assembly, named productinstall.log; for example, hss-install.log.

Click Finish to close EPM System Uninstaller.

202 Uninstalling EPM System

Performing a Silent Uninstallation


Silent uninstallations automate the uninstallation process so that you can uninstall EPM System products on multiple computers without manually specifying uninstallation settings on each machine. To uninstall EPM System products on multiple computers using the same uninstallation options, record a response file during installation. You can then run a silent uninstallation from the command line, using the options that were saved in the response file.

To run a silent uninstallation:


1
Copy the response file that you created during installation to the machine on which you want to run the uninstallation. You can also copy the file to a network drive that is accessible from the machines on which you want to uninstall.

For information about recording a response file during installation, see Performing Silent Installations on page 60.

From the command line, enter a command:


uninstall.cmd -silent filename

for Windows or
uninstall.sh -silent filename

for UNIX. The uninstallation runs in the background.

Performing a Silent Uninstallation 203

204 Uninstalling EPM System

12
In This Chapter

License Compliance

Ensuring License Compliance........................................................................... 205 Activating and Deactivating Product Features......................................................... 205 Auditing Usage ........................................................................................... 205

This chapter describes the licensing compliance requirements for a new installation of EPM System products.

Ensuring License Compliance


To ensure compliance with your license agreement, Oracle recommends that you:
l

Activate or deactivate features according to your license agreement. See Activating and Deactivating Product Features on page 205. Audit your usage. See Auditing Usage on page 205.

Activating and Deactivating Product Features


During product configuration with EPM System Configurator, on the Product Options page, for some products you must activate or deactivate features according to your license agreement. See Chapter 4, Configuring EPM System Products and review your license agreement to identify features that you are authorized to use. For information about viewing which options you activated, see the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Troubleshooting Guide

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 Oracle Hyperion Enterprise Performance Management System Security Administration Guide. A

Ensuring License Compliance 205

provisioning report provides a list of users provisioned to each application, either directly or through a group.

206 License Compliance

A
In This Appendix

What Happens During Installation

What Happens During Shared Services Installation .................................................. 207 What Happens During EPM Workspace Installation .................................................. 210 What Happens During Performance Management Architect Installation ........................... 211 What Happens During Calculation Manager Installation ............................................. 212 What Happens During Smart View Installation ........................................................ 213 What Happens During Essbase Installation ........................................................... 213 What Happens During Essbase Studio Installation ................................................... 215 What Happens During Integration Services Installation .............................................. 216 What Happens During Administration Services Installation.......................................... 218 What Happens During Provider Services Installation ................................................. 219 What Happens During Smart Search Command Line Utility Installation............................ 219 What Happens During Reporting and Analysis Installation .......................................... 220 What Happens During Planning Installation ........................................................... 221 What Happens During Financial Management Installation........................................... 221 What Happens During Performance Scorecard Installation.......................................... 222 What Happens During Strategic Finance Installation ................................................. 223 What Happens During Profitability and Cost Management Installation ............................. 224 What Happens During FDM Installation................................................................ 224 What Happens During Data Relationship Management Installation ................................ 225

During installation, EPM System Installer installs components and services for the products that you select and creates Start menu items under All Users.

What Happens During Shared Services Installation


During a typical installation, EPM System Installer performs the following operations:
l

Installs EPM System common components to HYPERION_HOME/common. For information about HYPERION_HOME and a list of directories created, see Common Files installed in the HYPERION_HOME Directory on page 208.

Installs these components:


m

OpenLDAP database (stores security-services-related data)

What Happens During Shared Services Installation 207

Shared Services server Shared Services Help Oracle's Hyperion Remote Authentication Module

Adds shortcuts to the Start menu.

Files Installed in the Foundation Directory


Shared Services files are installed in HYPERION_HOME/products/Foundation. The following table describes the files and folders installed in the /Foundation directory.
Table 65

Foundation Installation Directories Contents Files for uninstalling Shared Services


InstallableAppswar and ear files and scripts and other files needed to deploy an application; as part of preparing a war or ear file for deployment, the war file MAY be unpacked here and some files modified, then the war or ear file repacked, ready for deployment

Directory
_uninst AppServer

bin BPMA CALC openLDAP server SmartView temp workspace

Shared Services start and stop scripts Performance Management Architect files Calculation Manager files OpenLDAP database files Shared Services executable files, default relational database files, Java class files, and server locale files Smart View files Location for temporary files EPM Workspace files

Common Files installed in the HYPERION_HOME Directory


Various files are installed in the HYPERION_HOME/common directory by a default installation of Shared Services. Some common components, and thus some files and directories, are optional and might not be installed. The following table describes the files and folders installed in the HYPERION_HOME/common directory.
Table 66

Common Component Directories Created in the Common Directory Contents Analytic Data Model files

Directory
ADM

208 What Happens During Installation

Directory
appServers Axis calc-client-sdk CLS, CLS-64 config CSS docs epmstage EssbaseJavaAPI EssbaseRTC, EssbaseRTC-64 httpServers HyperionLookAndFeel import_export JakartaCommons JavaMail JCE JDBC JRE, JRE-64 loggers Microsoft.NETFramework (Windows only) MSXML (Windows only) Naming ODBC, ODBC-64 pma-client-sdk RMI SAP, SAP-64 Search SharedServices

Contents Application server files Web services components

License services APIs EPM System Configurator files Files to support EPM System external authentication Product documentation files Files to support OUI inventory Java driver used when embedding Essbase in other applications Essbase runtime client used when embedding Essbase in other applications Web server files for batteries included installation Installer user interface files LifeCycle management files Common development library files Files to support sending e-mail through Java JCE files for encryption, key generation and agreement, and MAC JDBC files Java Runtime Environment files Files for external authentication logging Microsoft .Net files Microsoft XML parsers JNDI files ODBC drivers Performance Management Architect SDK common libraries RMI files Placeholder directory for SAP files to be copied Smart Search Command Line Utility common files Supporting files for Shared Services

What Happens During Shared Services Installation 209

Directory
utilities

Contents Utilities to change the location of EPM System Home and export, import, or validate provisioning data Supporting files for EPM System Diagnostics Supporting files for EPM System Diagnostics Visual C runtime library files EPM Workspace Agent Service Common XML components

validation Velocity VisualCRedistributable workspacert XML

The following table describes other files and folders installed in the HYPERION_HOME directory.
Table 67

Other Common Directories Contents A central location for storing the required Java application server specific files for each product A directory for each product to store log files. For more information about log files, see the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Troubleshooting Guide The log files belonging to most Hyperion products are created in HYPERION_HOME/logs. Log files are created in a product-specific directory. For example, Shared Services logs are created in HYPERION_HOME/logs/ SharedServices9. Installation logs for each product are located Installation logs for all products are located in HYPERION_HOME/logs/ install/product. The first time you run Oracle's Hyperion Enterprise Performance Management System Diagnostics, it creates logszip.

Directory
deployments logs

Opatch oui products uninstall upgrades

Oracle patching tool files Oracle installation files A directory for each product's product files. Each product's directory structure is described later in this chapter. Files to support the uninstallation process

What Happens During EPM Workspace Installation


EPM Workspace files are installed in HYPERION_HOME/products/Foundation/workspace.

Files Installed in the EPM Workspace Directory


The following table describes the files and folders installed in the /workspace directory.

210 What Happens During Installation

Table 68

EPM Workspace Installation Directories Contents Files for uninstalling EPM Workspace EPM Workspace and Web Analysis static content (online Help) EPM Workspace utilities, start and stop scripts Common files for EPM Workspace configuration Physical location of EPM Workspace services Database scripts are used by EPM System Configurator to create the database repository schema Sample files Annotation scripts EPM Workspace war/ear files Common library files for EPM Workspace Log files for EPM Workspace Utility for migration from previous releases SDK files

Directory
_uninst AppServer bin common data database docs install InstallableApps lib logs MigrationUtility SDK syncCSSId

What Happens During Performance Management Architect Installation


By default, the EPM System Installer performs these operations when you install Performance Management Architect:
l

Copies software files to the Performance Management Architect installation directory, creates the virtual directory in IIS, installs .NET Framework 2.0 if not installed, and installs C++ Runtime libraries. Installs some services. (For a list of services, see Performance Management Architect Services on page 117) Additional services are installed during configuration, and services do not start until you configure with EPM System Configurator. Sets up a virtual directory in IIS for the Dimension Server.

What Happens During Performance Management Architect Installation 211

Files Installed in the Performance Management Architect Directory


Performance Management Architect files are installed in HYPERION_HOME/products/ Foundation/BPMA. The following table describes the files and folders installed in the /BPMA directory.
Table 69

Performance Management Architect Installation Directories Contents Files for uninstalling Performance Management Architect Files required for Java application server deployment for Dimension server and Data Synchronization server Shared libraries for Performance Management Architect Files for using the Performance Management Architect Batch client, which provides a command line tool to access Performance Management Architect Files for the ADS file generator tool SQL files required for relational database configuration

Directory
_uninst AppServer

Common EPMABatchClient

EPMAFileGenerator (Wiindows only) Server (Windows only) temp

What Happens During Calculation Manager Installation


Calculation Manager components are installed in HYPERION_HOME/products/Foundation/
CALC.

Files Installed in the Calculation Manager Directory


The following table describes the files and folders installed in the /CALC directory.
Table 70

Calculation Manager Installation Directories Contents Files to uninstall Calculation Manager. Application server deployment files Configuration files Hyperion Calculation Manager library files and utilities

Directory
_uninst AppServer config lib

212 What Happens During Installation

What Happens During Smart View Installation


If you use EPM System Installer to install Smart View, Smart View files are installed in HYPERION_HOME/products/Foundation/SmartView or HYPERION_HOME/products/
Essbase/SmartView.

If you installed Smart View using the standalone executable, files are installed in HYPERION_HOME/Smartview. See Oracle Hyperion Smart View for Office User's Guide for more information.

Files Installed in the Smart View Directory


The following table describes the files and folders installed in the /SmartView directory.
Table 71

Smart View Installation Directories Contents


l l l l l

Directory
bin

Smart View DLLs


BIPLusConnector.dll for Oracle Crystal Ball, Fusion Edition HSTbar.xla, the Smart View toolbar smartview.bas, containing VBA function declarations hve.exe, the Visual Explorer executable

cfg

The configuration properties file (properties.xml) for Smart View, which contains the URL location for the Provider Services that is used by default when Smart View is launched Smart View documentation

Docs

What Happens During Essbase Installation


By default, EPM System Installer performs the following operations when you install Essbase.
l

Installs Essbase Server software files to the HYPERION_HOME/products/Essbase/ EssbaseServer directory. If you install an additional instance of Essbase Server on the same computer, it is installed in HYPERION_HOME/products/Essbase-n/EssbaseServer. Creates the file, setEssbaseEnv.cmd, to store environment variables for Windows installations. Creates the file, hyperionenv.doc, to store parameters for UNIX installations. Installs the appropriate version of Java Runtime Environment (JRE) to the HYPERION_HOME/common/JRE directory, and sets the JVMMODULELOCATION variable in the essbase.cfg file.

For a list of files supplied with or required by API to compile programs, see the Oracle Essbase API Reference.
What Happens During Smart View Installation 213

For additional information about what happens when you install and configure multiple instances of Essbase Server, see Configuring and Starting an Additional Instance of Essbase Server on page 96.

Files Installed in the Essbase Server Directory


The following table describes the files and folders installed in the /EssbaseServer directory.
Table 72

Essbase Installation Directories Contents Libraries and header files necessary for using MaxL. You do not have to install or use the API to use MaxL, but the directory is created so that MaxL will work. Essbase application files, as they are created. Essbase sample applications and associated databases.

Directory
api

app

bin java locale

Essbase Server files Java software to support the Java-based features of Essbase NLS files necessary for Essbase supported languages. During the Essbase Server installation, you select a value for the ESSLANG environment variable, which applies to all languages, including English.

localized perlmod

Localized files Files required to add the MaxL Perl Module (essbase.pm), which enables you to embed MaxL statements in Perl programs. You must install Perl. See the documentation in this directory and the MaxL section of the Oracle Essbase Technical Reference.

Files Installed in the Essbase Client Directory


When you install the Essbase Client, some or all of the directories listed in the following table are created in the HYPERION_HOME/products/Essbase/EssbaseClient directory: During Essbase Client installation, EPM System Installer sets ESSBASEPATH to the client installation location, as a user variable (Windows) or in hyperionenv.doc (UNIX). Previous versions of Essbase used ARBORPATH to refer to the installation location. The following table describes the files and folders installed in the /EssbaseClient directory.
Table 73

Essbase Client Installation Directories Contents Essbase API files Essbase program files for running Oracle Essbase Spreadsheet Add-in The installation program adds essexcln.xll to Excel to point Excel to the correct bin directory.

Directory
api bin

214 What Happens During Installation

Directory
hve JavaAPI locale localized perlmod

Contents Visual Explorer files. Help files for Oracle Essbase Visual Explorer Character-set files necessary for Essbase Server supported languages Localized files Files required to add the MaxL Perl Module (essbase.pm), which enables you to embed MaxL statements in Perl programs. You must install Perl. See the documentation in this directory and the MaxL section of the Oracle Essbase Technical Reference.

What Happens During Essbase Studio Installation


By default, the EPM System Installer performs these operations when you install Essbase Studio:
l

Installs Essbase Studio files in HYPERION_HOME/products/essbase/EssbaseStudio. Installs common components to the HYPERION_HOME/common directory. Installs the Essbase Studio service, which you can choose to start when you configure with EPM System Configurator.

Files Installed in the Essbase Studio Directory


The following table describes the files and folders installed in the /EssbaseStudio directory.
Table 74

Essbase Studio Installation Directories Contents The Essbase Studio Console executable file, EssbaseStudio.exe. Also contains these Eclipse-specific subdirectories: configuration, features, plugins, storage,
workspace. EASLaunch.properties file

Directory
console

console/eas Server

The Essbase Studio Server startup file, startServer.bat. Also contains the server.properties file. Some settings are manually configurable after installation and configuration. See the Oracle Essbase Studio User's Guide or Oracle Essbase Studio Online Help for more information.

Server/database Server/datafiles Server/ess_ japihome

SQL files for creating the Essbase Studio repository The default directory for storing flat files that will serve as data sources for Essbase Studio Server. Java API classes Note: Do not edit the essbase.properties file in server/ess_japihome/bin.

What Happens During Essbase Studio Installation 215

Directory
Server/sqlscripts

Contents SQL scripts that you can use to create a Essbase Studio catalog database. Scripts are included for supported RDBMS.

What Happens During Integration Services Installation


Integration Services files are installed in HYPERION_HOME/products/Essbase/eis. When you install Integration Services software, EPM System Installer:
l

Creates directories and copies program files, scripts, and Help files to the location you specify. Adds entries to the Windows Registry for Integration Services.

The specific changes made to the computer depend on the operating system, whether you are installing server or client software, and which components of Integration Services you choose to install. When you install the Integration Services server software on UNIX computers, EPM System Installer performs the these actions:
l

Copies program files, scripts, and Help to the created directories on the local drive. Copies shared library files to the esslib directory. Creates is.csh and is.sh shell script files for updating the UNIX operating environment and installs them to the directory you created during installation. Creates a sample odbc.ini in the ODBC/Merant/5.2 directory for use in configuring relational data sources for ODBC.

Files Installed in the Integration Services Directory


The following table describes the files and folders installed in the /eis directory.
Table 75

Integration Services Installation Directories Contents Integration Services Console software

Directory
console/bin console/docs console/locale console/localized server/batch server/bin server/esscript

National language support files Localized files Empty. Later, the batch directory will store scheduler scripts for batch jobs that you create. Integration Services software Empty. Later, the esscript directory will contain ESSCMD scripts you create.

216 What Happens During Installation

Directory
server/lib server/loadinfo

Contents Files used for the import and export of Integration Services metadata Empty. Later, the loadinfo directory will contain directories representing session IDs, which will contain the reject files created during member loads and data loads. National language support files Localized files Contains the server log file, which is created when you first run Integration Services SQL script files to create, drop, and upgrade tables for an OLAP Metadata Catalog in each of the supported databases. For example, you can use oc_create_db2.sql to create OLAP Metadata Catalog tables in a DB2 database. Contains odbc.ini. It also includes the directories and files for the DataDirect ODBC installation and the readme file containing the latest DataDirect ODBC information. DataDirect ODBC PDF documentation is located in Merant/5.2/docs.

server/locale console/localized server/log server/ocscript

(UNIX only) HYPERION_


HOME/common/ODBC/ Merant/5.2 or HYPERION_ HOME/common/ODBC-64/ Merant/5.2 server/samples

Three subdirectories:
l l l

samples/spreadsheets samples/tbcdbase samples/tbcmodel

server/samples/ spreadsheets server/samples/ tbcdbase

Sample Essbase spreadsheets in Excel formats SQL script files and batch files to create tables and load data for the standard TBC sample application database and the Hybrid Analysis-enabled TBC sample application database. SQL script files and batch files to load data for the standard OLAP model (TBC Model) and metaoutline (TBC Metaoutline) and the Hybrid Analysis-enabled OLAP model (HA TBC Model) and metaoutline (HA TBC Metaoutline) in the TBC_MD sample application OLAP Metadata Catalog database. SQL script files to load data for the Unicode OLAP model (Sample_unicode) and metaoutline (Sample_ unicode_meta) in the TBC_MD_U sample application OLAP Metadata Catalog database. For manual sample application setup, you create tables for TBC_MD and TBC_MD_U with SQL script files in the ocscript directory.

server/samples/ tbcmodel

XML files to load data for the standard OLAP model (TBC Model) and metaoutline (TBC Metaoutline) and the Hybrid Analysis-enabled OLAP model (HA TBC Model) and metaoutline (HA TBC Metaoutline) in the TBC_MD sample application OLAP Metadata Catalog database. (Oracle only) XML files to load data for the Unicode OLAP model (Sample_unicode) and metaoutline (Sample_unicode_meta) in the TBC_MD_U sample application OLAP Metadata Catalog database.

server/temp

Temporary files

What Happens During Integration Services Installation 217

What Happens During Administration Services Installation


The default installation directory for Administration Services is HYPERION_HOME/products/
Essbase/eas.

EPM System Installer performs the following operations when you install Administration Services:
l

On Windows, creates the EAS_HOME environment variable on the system. Installs and configures Embedded Java Container during the Administration Services installation. Adds shortcuts to the Start menu. Installs and configures Business Rules software and documentation.

Files Installed in the Administration Services Directory


The following table describes the files and folders installed in the /eas directory.
Table 76

Administration Services Installation Directories Contents Startup scripts for the deployed Web application server. However, the recommend procedure is to launch Administration Services from the start menu or from HYPERION_HOME/deployments/AppServer/bin/ starteas.bat. Administration Services Console executable files, Java class files, Business Rules plug-in files, and temporary files created by the console installation Startup scripts and executables for Administration Services Console Java libraries for Administration Services Console Temporary directory for Administration Services Console Administration Services executable files, default relational database files, Java class files, Business Rules server files, and server locale files Files required by EPM System Configurator for deployment Administration Services Server binaries Administration Services Server jar files Locale files for Essbase RTC Documentation launch files for localized documentation

Directory
bin

console

console/bin console/lib console/temp server

server/AppServer server/bin server/lib server/locale server/localized storage

218 What Happens During Installation

Note: If you are using SAP R/3 as a data source, to configure Administration Services to work

with SAP/R3, see Administration Services Online Help for information on how to install and configure SAP/R3.

What Happens During Provider Services Installation


Provider Services files are installed in HYPERION_HOME/products/Essbase/aps. EPM System Installer performs the following operations when you install Provider Services:
l

Installs EPM System common components to the HYPERION_HOME/common directory. By default, installs Embedded Java Container application server. On Windows, adds shortcuts to the Start menu. Creates an environment variable APS_HOME on Windows, which contains the path of the Provider Services installation.

Files Installed in the Provider Services Directory


The following table describes the files and folders installed in the /aps directory.
Table 77

Provider Services Installation Directories Contents Application server files configured by EPM System Configurator Executable program files and server setting files for Provider Services A database file that Provider Services uses by default to store user names, server names, and other domain information Java API interface source Help files Third-party libraries
essconfiguration.jar file used by EPM System Configurator

Directory
Appserver bin data devtools docs external lib redist samples

Smart View client installation executable files Sample programs that you can use to test Provider Services software and start developing client programs

What Happens During Smart Search Command Line Utility Installation


Smart Search Command Line Utility files are installed in HYPERION_HOME/products/ Essbase/SmartSearch.

What Happens During Provider Services Installation 219

Files Installed in the Smart Search Command Line Utility Directory


The following table describes the files and folders installed in the /SmartSearch directory.
Table 78

Smart Search Command Line Utility Installation Directories Contents Files required for Java application server deployment for Smart Search Command Line Utility Smart Search Command Line Utility configuration files and templates for rendering search results.
Jar files needed to run Oracle Hyperion Smart Search Command Line Utility

Directory
AppServer hysl lib

What Happens During Reporting and Analysis Installation


Reporting and Analysis files are installed in HYPERION_HOME/products/biplus.

Files Installed in the Reporting and Analysis Directory


The following table describes the files and folders installed in the /biplus directory.
Table 79

Reporting and Analysis Installation Directories Contents Files to uninstall Reporting and Analysis Web Analysis files Product binaries plus start, stop scripts Subdirectories for common items Product temp data subdirectories Design architect and studio product-specific files, such as templates and scripts Help, samples Font files Files laid down and used during installation and configuration
.war and .ear files and .war- and .ear-preparation scripts .jar files

Directory
_uninst appsinfo bin common data DDS docs fonts install InstallableApps lib logs

Log files

220 What Happens During Installation

Directory
temp

Contents Temporary file storage

What Happens During Planning Installation


Planning files are installed in HYPERION_HOME/products/Planning. By default, the EPM System Installer performs these operations:
l

Copies Planning software files to the installation directory. Copies common components to the HYPERION_HOME directory that you specify. Installs the appropriate versions of Java Run-time Environment (JRE). Copies file to create a common RMI registry, called HyperionRMIRegistry, for products such as Planning and Oracle's Hyperion Business Rules.

Files Installed in the Planning Directory


The following table describes the files and folders installed in the /Planning directory.
Table 80

Planning Installation Directories Contents Uninstallation files for Planning Files required for Java application server deployment for Planning Executables, bat files, sh files and cmd files including Planning utilities. Also included are Smartview.exe and Offline.exe. Planning properties and ico files
Jar files needed to run Planning

Directory
_uninst AppServer bin

config lib/lib64 Offline

Files needed to run Offline Planning

What Happens During Financial Management Installation


Financial Management files are installed in HYPERION_HOME/products/ FinancialManagement. By default, EPM System Installer performs these operations when you install Financial Management:
l

Copies common components to the HYPERION_HOME directory that you specify Installs the Java Runtime Environment (JRE) version
What Happens During Planning Installation 221

Installs the ADM driver, HsvADMDriver.dll, in HYPERION_HOME/products/


FinancialManagement/client

If you do not have Microsoft Data Access Component (MDAC) installed on the application server, EPM System Installer installs it. The MDAC installation process can be time-consuming and requires that you reboot your computer.

Files Installed in the Financial Management Directory


The following table describes the files and folders installed in the /FinancialManagement directory.
Table 81

Financial Management Installation Directories Contents Uninstallation files for Financial Management Files for facilitating upgrades
dlls and executable files for Win32 client and Web tier client dlls shared between the Application tier and Web tier

Directory
_uninst bin Client Common Consultant Utilities Documentation HAL70AdapterInstall Install Sample Apps Server Server Working Folder Web Web Server Web Services

Utilities for viewing error logs Help files Files for installing Oracle's Hyperion Application Link 7.0 Adapter Files to install and configure the Smart View provider Sample applications and instructions for loading sample files
dlls for Application Server tier

Report style sheets and templates Smart View provider, Web pages, and Web help files
dlls needed to run the Web server

Web Service Manager executable

What Happens During Performance Scorecard Installation


Performance Scorecard files are installed in HYPERION_HOME/products/ PerformanceScorecard.

222 What Happens During Installation

Files Installed in the Performance Scorecard Directory


The following table describes the files and folders installed in the /PerformanceScorecard directory.
Table 82

Performance Scorecard Installation Directories Contents Files needed to uninstall Performance Scorecard Files required for Java application server deployment for Performance Scorecard Scripts to start and stop HPSWebReports and HPSAlerter Initialization and upgrade scripts used to create a new Performance Scorecard database or to upgrade an existing one, depending on your choice during configuration Files that enable you to use the ETL Import/Export utility to load and extract data

Directory
_uninst AppServer bin db

tools

What Happens During Strategic Finance Installation


Strategic Finance files are installed in HYPERION_HOME/products/hsf.

Files Installed in the Strategic Finance Directory


The following table describes the files and folders installed in the /hsf directory.
Table 83

Strategic Finance Installation Directories Contents Batch files to start and stop Strategic Finance Executables and files for running the Strategic Finance Client Server entities, access control, maps, batches, server consolidation data and other Strategic Finance server database information. Executables for the Strategic Finance server and administration utility Files for uninstalling Strategic Finance

Directory
bin Client HSFData

Server uninstall ValidationLibs WebServer

Oracle Hyperion Strategic Finance, Fusion Edition Web services components

What Happens During Strategic Finance Installation 223

What Happens During Profitability and Cost Management Installation


Profitability and Cost Management software components are installed in HYPERION_HOME/ products/Profitability.

Files Installed in the Profitability and Cost Management Directory


The following table describes the files and folders installed in the /Profitability directory.
Table 84

Profitability and Cost Management Installation Directories Contents Files for uninstalling Profitability and Cost Management Files required for Java application server deployment for Profitability and Cost Management Batch files for starting and stopping Profitability and Cost Management SQL scripts required for creating the production database Files used for configuration user interface Provides sample data files, including a metadata xml file to create a Profitability and Cost Management application in Oracle Hyperion EPM Architect, Fusion Edition and a staging dump file to import model data into a Oracle Hyperion Profitability and Cost Management, Fusion Edition application

Directory
_uninst AppServer bin database lib samples

What Happens During FDM Installation


FDM files are installed in HYPERION_HOME/products/FinancialDataQuality. ERP Integrator files are also installed in this location.

Files Installed in the FDM Directory


The following table describes the files and folders installed in the /FinancialDataQuality directory.
Table 85

Directory
_uninst ApplicationServer AppServer

Contents Files to uninstall Oracle Hyperion Financial Data Quality Management, Fusion Edition Application Configuration executable and the application server dll file Files required for Java application server deployment for Oracle Hyperion Financial Data Quality Management ERP Integration Adapter for Oracle Applications

224 What Happens During Installation

Directory
bin common database InstallScripts lib LoadBalanceManager odi

Contents Scripts to start and stop Hyperion ERPI - Web Application (HyS9aifWeb) Files required for registration with Shared Services Scripts to create database objects Script files used during the installation process Files required for configuration with EPM System Configurator Load Balance Manger Configuration executable and Load Balance Manager dll files
l l

\scenarios stores scenarios for use with Oracle Data Integrator

\topology stores logical schemas related to Oracle Data Integrator

SharedComponents

Components shared between the Web client, Workbench, configuration tools, application server, and task manager Configuration executable and Task Manager dll files Web Configuration executable, Web Configuration dll file, and Web site setup, dll, and html files

TaskManager WebServerComponents

What Happens During Data Relationship Management Installation


For information about the Oracle Hyperion Data Relationship Management, Fusion Edition installation, see the Oracle Hyperion Data Relationship Management Installation Guide.

What Happens During Data Relationship Management Installation 225

226 What Happens During Installation

B
In This Appendix

Optional Manual Configuration for Essbase Products

Manually Configuring the Essbase Server Environment (UNIX) ...................................... 227 Manually Configuring the Essbase Server Environment (Windows) ................................. 233

Manually Configuring the Essbase Server Environment (UNIX)


During installation, EPM System Installer performs these tasks:
l

Creates .hyperion.'hostname', which defines the Hyperion home directory. Creates hyperionenv.doc, which specifies default parameters for starting Essbase. Provides start scripts for the Korn shell.

Each Hyperion home directory has its own hyperionenv.doc file and startEssbase.sh file. During configuration, EPM System Configurator:
l

Updates hyperionenv.doc with values you specify if they differ from the default values. Updates essbase.cfg with the port values you specify. For information about essbase.cfg, see Oracle Essbase Technical Reference. Updates essbase.cfg with the JVMMODULELOCATION setting to designate the installation location of JRE. For information about designating a different, specific instance of JRE, see Changing JvmModuleLocation (UNIX) on page 230.

EPM System Configurator does not update the .cshrc or .profile environment files. To start Essbase, Oracle provides a script, startEssbase.sh. The script calls hyperionenv.doc, which sets the required parameters, and starts Essbase. By default, if you do not configure Essbase with EPM System Configurator, hyperionenv.doc is populated with default values so you can use startEssbase.sh to start Essbase in standalone mode (without Shared Services authentication). The following information is provided if you prefer to configure manually or want to change the configuration later, or want to update the script for a different shell. (Oracle provides scripts for the Korn shell.)

Manually Configuring the Essbase Server Environment (UNIX) 227

Note: After installing and updating the environment, you must log off the server and log on

again for the changes to take effect.


Note: If you installed an additional instance of Essbase, it is installed in HYPERION_HOME/ products/essbase-n. This instance has its own copy of hyperionenv.doc, essbase.cfg, and startEssbase.sh.

Specifying Parameters in hyperionenv.doc


The hyperionenv.doc file is written in Korn shell. If you are using another shell, be sure to use syntax appropriate for it. The following tables describes the variables in hyperionenv.doc:
Parameter ARBORPATH PATH HYPERION_ HOME LD_LIBRARY_ PATH Description Location of applications and data To more quickly access Essbase Server components, add $ESSBASEPATH/bin to the PATH. Installation location for all EPM System products System library path. Update the library path variable appropriate for the operating system you are using.
l l l l

Default Value
HYPERION_HOME/products/Essbase/ EssbaseServer/app $ESSBASEPATH/bin

HYPERION_HOME/products/Essbase/ EssbaseServer/

HP-UX SHLIB_PATH IBM AIX LIBPATH Linux LD_LIBRARY_PATH Solaris LD_LIBRARY_PATH


HYPERION_HOME/products/Essbase/ EssbaseServer English_UnitedStates.Latin1@Binary HYPERION_HOME/common/ODBC/Merant/5.2/ odbc.ini

ESSBASEPATH ESSLANG ODBCINI LD_PRELOAD (HPUX RISC only)

Installation location of Essbase client Locale definition Location of odbc.ini You must set the environment variable LD_PRELOAD on HPUX RISC. Caution! Failure to set LD_PRELOAD on HPUX RISC platforms might result in Essbase terminating abnormally. Setting LD_PRELOAD in UNIX environment scripts (such as .profile) is not recommended, as unexpected consequences might occur.

export LD_PRELOAD=HYPERION_HOME/ common/JRE/1.5.0/lib/ PA_RISC2.0/server/libjvm.sl

228 Optional Manual Configuration for Essbase Products

Changing ESS_JVM_OPTION and ESS_CSS_JVM_OPTION


The environment variables ESS_JVM_OPTION# (0 through 9) and ESS_CSS_JVM_OPTION# (0 through 9) are available to address any platform and JRE version-specific options required by JVM. If required for your environment, these settings are written to the hyperionenv.doc file during installation. If you are running JRE 1.5.0 on Solaris, the ESS_JVM_OPTION and ESS_CSS_JVM_OPTION environment variables are required:
l

ESS_JVM_OPTION1If using JVM for custom-defined functions, custom-defined macros,

data mining, triggers, or external authentication supplied by Oracle.


l

ESS_CSS_JVM_OPTION1If using the security platform supplied by Oracle.

You must set these environment variables to use -Xusealtsigs, which is a special Java argument. -Xusealtsigs is the only setting required for this release.

To set ESS_JVM_OPTION1 and ESS_CSS_JVM_OPTION1:


Add the environment setting in the appropriate file and format for your system. The following table provides examples of environment settings.

Shell C

Environment File .cshrc

Variable and String ESS_JVM_OPTION1: setenv ESS_JVM_OPTION1 "-Xusealtsigs" ESS_CSS_JVM_OPTION1: setenv ESS_CSS_JVM_OPTION1 "-Xusealtsigs"

Bourne or Korn Shell

.profile

ESS_JVM_OPTION1: ESS_JVM_OPTION1=-Xusealtsigs; export ESS_JVM_OPTION1; ESS_CSS_JVM_OPTION1: ESS_JVM_CSS_OPTION1=-Xusealtsigs; export ESS_CSS_JVM_OPTION1;

Changing the Location of Shared Services Log Files (Optional)


Use this information if you want to change the location of Shared Services configuration log files. The default location of Shared Services configuration log files depends on the application server on which Shared Services is deployed. To change the location where log files are written, use the ESS_CSS_JVM_OPTION# environment variable. Be sure to use a # that does not conflict with other ESS_CSS_JVM_OPTION variables used in your environment.

Manually Configuring the Essbase Server Environment (UNIX) 229

To set ESS_CSS_JVM_OPTION2:
1
(UNIX) Add the environment variable in the appropriate file and format for your system.

The following table provides examples of environment settings.


Shell C Bourne or Korn Shell Environment File .cshrc .profile Variable and String setenv ESS_CSS_JVM_OPTION2 "-Djava.io.tmpdir=location ESS_CSS_JVM_OPTION2=-Djava.io.tmpdir=location export ESS_CSS_JVM_OPTION2;

where location is the full pathname. For example: /vol1/server/csslog. OR

(Windows) At a command prompt, type:


set ESS_CSS_JVM_OPTION2= -Djava.io.tmpdir=location

For example:
set ESS_CSS_JVM_OPTION2= -Djava.io.tmpdir=c:/csslog

Changing JvmModuleLocation (UNIX)


The JVMMODULELOCATION setting in the essbase.cfg file enables you to designate a specific installation of JRE for use with Essbase, and is required to enable Data Mining, Shared Services, custom defined functions, triggers, and external authentication. This setting is particularly useful if you have multiple versions of Java installed on the Essbase Server computer. During Essbase Server configuration, the correct setting for JVMMODULELOCATION is automatically added to essbase.cfg. To change the JVMMODULELOCATION parameters, you must specify the full path and file name of the Java Virtual Machine (JVM) library. The location and name of the library varies, depending on the JRE version and the operating system that you are using, as shown in the following table.
Note: To run 64bit Essbase on any 64bit operating system requires a 64bit JVM.

The following table provides the location and name of the JVM library file for different operating systems.
Platform (JRE version) Solaris 32bit (JRE 1.5.0) Solaris 64bit (JRE 1.5.0_05) Location and Name of JVM Library File $HYPERION_HOME/common/JRE/Sun/1.5.0/lib/sparc/server/libjvm.so $HYPERION_HOME/common/JRE-64/Sun/1.5.0/lib/sparcv9/server/ libjvm.so

230 Optional Manual Configuration for Essbase Products

Platform (JRE version) Linux (JRE 1.5.0_05) Linux (JRE-64 1.5.0) IBM AIX 32bit (JRE 1.5.0) IBM AIX 64bit (JRE 1.5.0) HP-UX 32-bit (JRE 1.5.1_01) HP-UX 64-bit (JRE 1.5.1_01)

Location and Name of JVM Library File $HYPERION_HOME/common/JRE/Sun/1.5.0/lib/i386/server/libjvm.so $HYPERION_HOME/common/JRE-64/Sun/1.5.0/lib/i386/server/libjvm.so $HYPERION_HOME/common/JRE/IBM/1.5.0/bin/classic/libjvm.so $HYPERION_HOME/common/JRE-64/IBM/1.5.0/bin/classic/libjvm.so $HYPERION_HOME/common/JRE/HP/1.5.0/lib/PA_RISC2.0/server/ libjvm.sl $HYPERION_HOME/common/JRE-IA64/HP/1.5.0/lib/IA64W/server/ libjvm.so

Managing Memory with JvmModuleLocation


If you are not using Data Mining, Shared Services, custom defined functions, triggers, or external authentication, you can reduce the amount of memory used by editing essbase.cfg and setting JvmModuleLocation to null (empty). If you are using these features, and need to reduce the amount of memory used, then you can reduce the JVM heap size by setting the following environment variables:
ESS_JVM_OPTION3=-Xms16m ESS_JVM_OPTION4=-Xmx16m

Because the default minimum and maximum for JVM heap size are different for different platforms and versions, set the correct value for your environment. For example, see the following as a reference: http://publib.boulder.ibm.com/infocenter/wasinfo/v4r0/index.jsp? topic=/com.ibm.support.was.doc/html/Java_SDK/1132680.html.

Optional Manual Configuration for Integration Services (UNIX)


EPM System Configurator provides configuration scripts is.csh and is.sh, for updating environment variables. If necessary, update the scripts for your shell. Both shell scripts set the following environment variables: The following table describes the environment variables for Integration Services on UNIX.
Table 86

Environment Variables Required for Integration Services on UNIX Purpose and Default Setting Specifies the directory where the Integration Services software is installed. Specifies the directory where the common Hyperion components are installed. $HOME/Hyperion

Name ISHOME HYPERION_HOME

Manually Configuring the Essbase Server Environment (UNIX) 231

Name ARBORPATH

Purpose and Default Setting Specifies the location of Essbase applications. $ISHOME

ESSBASEPATH ISLOADINFO

Location of Essbase client Specifies a directory location for the reject files created during a member load or data load. $ISHOME/loadinfo

ISODBC ODBCINI

%HYPERION_HOME%/common/Merant/ODBC/5.2 Optional. Specifies the location and name of the file containing the DSN configuration for ODBC.
$HYPERION_HOME/common/ODBC/Merant/5.2/odbc.ini

TEMP

Specifies a directory for temporary files. /tmp

JAVA_HOME Library path (Platform):


l l l

Specifies the JRE location. For example, for 64bit AIX, the location is $HYPERION_HOME/common/ JRE-64/IBM/1.5.0. Specifies the list of directories to search for software libraries. The default setting is the current library path list, with the following entries added to the end of the list: $ISHOME/bin; $ISHOME/esslib $HYPERION_HOME/ODBC/Merant/5.2/lib;

LIBPATH (AIX) SHLIB_PATH (HP-UX) LD_LIBRARY_PATH (Solaris) LD_LIBRARY_PATH (Linux)

CLASSPATH PATH

$HYPERION_HOME/common/CSS/9.5.0.0/lib/css-9_5_0.jar

Specifies the list of directories to search for software programs and libraries. The default setting is the current PATH list, with the following entry added to the end of the list: $ISHOME/bin:

Update the UNIX environment by adding is.csh or is.sh to the login script of the user who runs the Integration Services software.

To include the is.csh or is.sh script in your login scripts:


1 2
In a text editor, open the login script file for the user (typically, hyperion) who runs Integration Services. Add a new line to the file.
l

If you use Korn shell, type:


. /full_path_to_directory/is.sh

If you use C shell, type:


source /full_path_to_directory/is.csh

232 Optional Manual Configuration for Essbase Products

Optional Manual Configuration for Administration Services (UNIX)


To start Administration Services, Oracle provides a script, starteas.sh. The script calls setCustomParamseas.sh, which sets the required parameters and starts Administration Services. If you are using Oracle Application Server on UNIX, setCustomParamseas.sh is not provided. You must specify the environment variables in the Oracle Application Server Application Server Console, by setting the Server properties for the OC4J instance. The following table describes the environment variables for Administration Services on UNIX.
Table 87

Environment Variables Required for Administration Services on UNIX Default Value


HYPERION_HOME/products/Essbase/eas HYPERION_HOME/products/Essbase/eas/server HYPERION_HOME/products/Essbase/eas/server HYPERION_HOME/products/Essbase/eas/server/bin:$PATH

Parameter Name EASHOME ARBORPATH ESSBASEPATH PATH

In addition, specify the ESSLANG value if it is not already set on the machine.

Optional Manual Configuration for Provider Services (UNIX)


To start Provider Services, Oracle provides a script, startaps.sh. The script calls setCustomParamsaps.sh, which sets the required parameters and starts Provider Services. If you are using Oracle Application Server on UNIX, setCustomParamsaps.sh is not provided. You must specify the environment variables in the Oracle Application Server Application Server Console, by setting the Server properties for the OC4J instance. The following table describes the environment variables for Provider Services on UNIX.
Table 88

Environment Variables Required for Provider Services on UNIX Default Value


HYPERION_HOME/products/Essbase/aps %ESS_ES_HOME%/bin;%ARBORPATH%/bin;%PATH%

Parameter Name ESS_ES_HOME PATH

Manually Configuring the Essbase Server Environment (Windows)


During Essbase Client installation, EPM System Installer:
Manually Configuring the Essbase Server Environment (Windows) 233

Sets ESSBASEPATH to the Essbase client installation location as a user variable (Windows) and adds it to the PATH. Note that this is a new variable. Previous versions of Essbase used ARBORPATH to refer to the installation location. ARBORPATH now refers to the application location.

Sets ARBORPATH as a user variable (Windows).

During Essbase Server installation, EPM System Installer does not set environment variables. Instead, batch files are provided to start Essbase (startEssbase.cmd), ESSCMD (startEsscmd.cmd), and essmsh (startMaxl.cmd). All the scripts call setEssbaseEnv.cmd to set up ESSBASEPATH, ARBORPATH, and PATH before starting. If you've installed multiple instances of Essbase Server, each instance has its own startup script. During Essbase Server configuration, EPM System Configurator:
l

Specifies the environment variables ESSLANG and ARBORPATH in a file used to launch Essbase. Updates essbase.cfg with the port values that you specified. For information about essbase.cfg, see Oracle Essbase Technical Reference. Updates essbase.cfg with the JVMMODULELOCATION setting to designate the installation location of JRE. For information about designating a different, specific instance of JRE, see Setting JVMMODULELOCATION (Windows) on page 234.

The following information is provided in the event that you prefer to configure manually or want to change the configuration later.

Updating the Environment Manually for Essbase Server


Essbase Server relies on variables set in setEssbaseEnv.cmd. To run Essbase Server, use startEssbase.cmd, which calls setEssbaseEnv.cmd. Ensure that the following environment variables are set appropriately:
l

ESSBASEPATH ARBORPATH ESSLANG PATH

Setting JVMMODULELOCATION (Windows)


The JVMMODULELOCATION setting in the essbase.cfg file enables you to designate a specific installation of JRE for use with Essbase, and is required to enable Data Mining, Shared Services, custom defined functions, triggers, and external authentication. This setting is particularly useful if you have multiple versions of Java installed on the Essbase Server computer.

234 Optional Manual Configuration for Essbase Products

During Essbase Server configuration, the correct setting for JVMMODULELOCATION is automatically added to essbase.cfg. To change JVMMODULELOCATION parameters, you must specify the full path and file name of the Java Virtual Machine (JVM) library. The location and name of the library varies, depending on the JRE version and the operating system that you are using.
Note: To run 64bit Essbase on any 64bit operating system requires a 64bit JVM.

The following table shows where the JRE and jvm.dll files are installed:

Platform (JRE version) 32-bit Windows: JRE JVM.DLL 64-bit Windows (Itanium): JRE JVM.DLL 64-bit Windows on AMD Opteron and Intel Xeon: JRE JVM.DLL

JRE and JVM.DLL Locations

HYPERION_HOME/common/jre/sun/1.5.0 HYPERION_HOME/common/jre/sun/1.5.0/bin/server/jvm.dll

HYPERION_HOME/common/JRE-IA64/Sun/1.4.2 HYPERION_HOME/common/JRE-IA64/Sun/1.4.2/bin/server/jvm.dll

HYPERION_HOME/common/JRE-AMD64/Sun/1.5.0 HYPERION_HOME/common/JRE-AMD64/Sun/1.5.0bin/server/jvm.dll

Configuring the 32-bit Runtime Client on a 64-bit Windows Platform


If you want to use 32bit and 64bit client applications on the same machine, and you don't want to have to recompile applications, use the following procedure.

To install and use the 32-bit Runtime Client on a 64-bit Microsoft Windows machine:
1 2 3 4
Record the value of the HYPERION_HOME system environment variable. From a command prompt or from a shell window on which the HYPERION_HOME value does not conflict with existing Essbase 64-bit client or server installations, install the 32-bit client. After the 32-bit client installation is completed, restore the system environment variable HYPERION_HOME to the value noted in Step 1. On the 64-bit machine, run the precompiled 32-bit client program from a command prompt or from a shell window on which ARBORPATH and ESSBASEPATH are set to the installation directory of the 32bit Runtime Client and PATH is set to include the bin subdirectory under the ARBORPATH directory.

For information on Application Programming Interface and Runtime Client, see the Oracle Essbase API Reference.

Manually Configuring the Essbase Server Environment (Windows) 235

Optional Manual Configuration for Integration Services (Windows)


During installation, EPM System Installer specifies environment variables for Integration Services in the start scripts used to start Oracle Essbase Integration Services HYPERION_HOME/products/Essbase/eis/server/bin/startup.bat (for the server) and HYPERION_HOME/products/Essbase/eis/console/bin/startclient.bat (for the console). The startup scripts set the following environment variables:
l

ARBORPATH ISHOME ESSBASEPATH

Optional Manual Configuration for Administration Services (Windows)


Oracle Essbase Administration Services requires the following environment variables:
l

ESSLANG ESSBASEPATH EAS_HOME

The console finds files through admincon.lax and the server uses setCustomParamseas.bat to set variables. EPM System Installer installs admincon.lax and EPM System Configurator creates setCustomParamseas.bat when the you deploy to the Web application server.

Optional Manual Configuration for Essbase Studio (Windows)


During installation, Oracle Hyperion Enterprise Performance Management System Installer, Fusion Edition specifies environment variables for Essbase Studio in the start file used to launch Essbase Studio HYPERION_HOME/products/Essbase/EssbaseStudio/Server/ startServer.bat. For additional customization, see Configuring the Server Properties File and Configuring the Administration Services Console Launch File in the Oracle Essbase Studio User's Guide.

Optional Manual Configuration for Provider Services (Windows)


Ensure that the following variables are set appropriately:

236 Optional Manual Configuration for Essbase Products

APS_HOME APS_HOME is set as an environment variable after installation and

configuration.
l

ESS_ES_HOME Set ESS_ES_HOME in HYPERION_HOME/products/Essbase/aps/bin/ startcmd.cmd to point to APS_HOME. ESS_ES_HOME is required to launch the command-

line administration utility for Provider Services.


l

JAVA_HOME Set JAVA_HOME in HYPERION_HOME/products/Essbase/aps/bin/ startcmd.cmd. JAVA_HOME is required to run Java API samples. ESSLANG Ensure that the ESSLANG value is correct for your locale in HYPERION_HOME/ products/Essbase/aps/bin/essbase.properties. By default, ESSLANG is set to US

English. You can perform additional configuration by editing HYPERION_HOME/products/Essbase/ aps/bin/essbase.properties. See the Oracle Hyperion Provider Services Administration Guide.

Manually Configuring the Essbase Server Environment (Windows) 237

238 Optional Manual Configuration for Essbase Products

C
In This Appendix

Essbase 32-Bit and 64-Bit Compatibility

Essbase 32-Bit and 64-Bit Client and Server Compatibility ......................................... 239 Essbase API Compatibility on 32-Bit and 64-Bit Platforms.......................................... 240

Essbase 32-Bit and 64-Bit Client and Server Compatibility


The following table summarizes the compatibility of 32-bit and 64-bit clients and servers with Essbase Server:

Client 32-bit Essbase Administration Services Console 32-bit Essbase Administration Services Console 64-bit Essbase Administration Services Console 32-bit Essbase Studio Console 32-bit Essbase Studio Console 64-bit Essbase Studio Console 32-bit Essbase Integration Services Console 32-bit Essbase Integration Services Console 32-bit Smart View 32-bit Oracle Hyperion Smart View for Office, Fusion Edition 32-bit Essbase Administration Services Console 64-bit Essbase Administration Services Console 32-bit Java API or XMLA client application 64-bit Java API or XMLA client application

Server 32-bit Administration Server 64-bit Administration Server 64-bit Administration Server 32-bit Essbase Studio Server 64-bit Essbase Studio Server 64-bit Oracle Essbase Studio Server 32-bit Essbase Integration Server 64-bit Essbase Integration Server 32-bit Provider Services 64-bit Provider Services 32-bit Provider Services 64-bit Provider Services 32-bit Provider Services 64-bit Provider Services

Essbase Server: Platform to Which Client Can Connect 32-bit, 64-bit 32-bit, 64-bit 64-bit 32-bit, 64-bit 32-bit, 64-bit 64-bit 32-bit , 64-bit 32-bit , 64-bit 32-bit, 64-bit 64-bit 32-bit, 64-bit 64-bit 32-bit, 64-bit 64-bit

Essbase 32-Bit and 64-Bit Client and Server Compatibility 239

Essbase API Compatibility on 32-Bit and 64-Bit Platforms


Essbase provides APIs for 32-bit and 64-bit platforms, which you can use to write and compile client programs that interface with Essbase Server.
l

Client programs developed for 32-bit platforms using the Essbase C API or Visual Basic API can run on 32-bit platforms and connect to either 32-bit or 64-bit Essbase Server. Precompiled client programs developed using the 32-bit Essbase Visual Basic API can run on 64-bit Windows platforms connecting to 64-bit Essbase Server, as long as the 32-bit runtime environment is set up as according to the documented instructions. Client programs developed for 64-bit platforms using the Essbase C API:
m

Can run on 64-bit platforms and connect to 32-bit or 64-bit Essbase Servers Cannot run on 32-bit platforms Client programs developed for 64-bit platforms do not require the #pragma directive to set the byte alignment.

Caution!

You cannot develop a client program for 64-bit Windows using the Essbase Visual Basic API.

The following table summarizes the compatibility of client programs developed with Essbase APIs:
Client Development: Platform with API Version 32-bit C API / Runtime Client 32-bit VB API / Runtime Client Platform on which Client Can Run 32-bit 32-bit Windows 64-bit Windows 32-bit Java (API or XMLA client application) 32-bit embedded Java (API client application) 64-bit C API / Runtime Client 64-bit Java (API or XMLA client application) 64-bit embedded Java (API client application) 64-bit 64-bit Oracle Hyperion Provider Services server 32-bit Provider Services server Essbase Server: Platforms to Which Client Can Connect 32-bit, 64-bit 32-bit, 64-bit 64-bit 32-bit, 64-bit 32-bit, 64-bit 32-bit, 64-bit 64-bit 64-bit

For information on the compatibility of 32-bit and 64-bit EPM System clients and servers with Essbase Server, see Essbase 32-Bit and 64-Bit Client and Server Compatibility on page 239.

240 Essbase 32-Bit and 64-Bit Compatibility

D
Database Oracle Database SQL Server DB2 Format

JDBC URL Attributes

During configuration, on the Configure Database page, click Advanced to specify additional JDBC parameters, which are used by Hyperion JDBC drivers to connect to the database. The following table describes the format to use to enter the parameters:

jdbc:hyperion:oracle://host:port;property1=value1;property2=value2;... propertyN=valueN jdbc:hyperion:sqlserver://host:port;property1=value1;property2=value2;... propertyN=valueN jdbc:hyperion:db2://host:port;property1=value1;property2=value2;... propertyN=valueN

Use the following information about the parameters. For additional information about the parameters, see DataDirect Connect for JDBC Help in HYPERION_HOME/common/JDBC/ DataDirect/3.7/help/help.htm. The following table describes additional information about the parameters:
Property SERVICENAME1 SID2 LOADLIBRARYPATH MAXPOOLEDSTATEMENTS ALTERNATESERVERS CONNECTIONRETRYCOUNT CONNECTIONRETRYDELAY LOADBALANCING DYNAMICSECTIONS CREATEDEFAULTPACKAGE REPLACEPACKAGE Oracle Database Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes SQL Server DB2

241

Property DATABASENAME3
1You 2You

Oracle Database

SQL Server Yes

DB2 Yes

must provide either SERVICENAME or SID for Oracle Database. must provide either SERVICENAME or SID for Oracle Database. 3Required for DB2 and SQL Server

To provide client-side failover and load-balancing for Oracle RAC, use the following attributes:
l

AlternateServers ConnectionRetryCount LoadBalancing

For example, to configure Oracle RAC, enter the URL in the form of:
jdbc:hyperion:oracle://hssrac-1-vip: 1521;ServiceName=hssrac;AlternateServers=hssrac-2-vip:1521.

242 JDBC URL Attributes

E
In This Appendix

Database Information for Financial Management

Database Connection Pooling .......................................................................... 243 Encrypting UDL Files ..................................................................................... 245

Database Connection Pooling


During Financial Management configuration, you specify the maximum number of relational database connections used by each application. Financial Management uses connection pooling to communicate with the database. Connection pooling enables more efficient database utilization and does not require that each user be set up in the relational repository. During configuration, EPM System Configurator enables you to specify the number of pooled database connections. The number of connections that you specify in the configuration utility is the maximum number of pooled connections consumed by an application. The pool starts with eight connections. If, after a certain number of attempts, the pool is unable to service a request for an additional connection, it adds eight more connections. The system continues adding blocks of eight connections until it reaches the maximum number of connections defined in the utility. If the system needs an additional connection beyond this limit, a temporary connection is created to service the request, which is closed after the task is complete. The system also creates additional connection pools that are reserved for system use and are not used for user activity. The system-use pools are divided into these connection types:
l

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

In general, 25 connections are dedicated to system-level activities: eight connections reserved for each application server, and 17 connections reserved for each application. Connection use is dependent on the activity type. Users with Read access, which are the majority of users in an application, generally use one or no connections. Users with Write access can consume more connections, as they write to the database. The number of connections consumed by a user with Write access, for example, a consolidator, depends on the application server hardware and quantity of data being written. In general, users with Write access may use 5 10 connections.
Database Connection Pooling 243

Financial Management opens the defined number of connections when an application is first opened. The connections are then available for subsequent users of the system. If a user process requests a connection, and all connections are in use, the system polls the connection pool for a short time, waiting for an available connection. If no connection is available, the system creates eight connections and adds them to the pool. The connection pool is limited to the total that you define in the configuration utility. Connections are application-specific. The default pool is created only after an application is opened. However, connections are not released on an application basis; they are released on an application server basis. Thus, all connections are not released until the application server has no Financial Management users accessing any application. Financial Management also supports Extended Analytics, which enables extracting data to a relational database for use with other systems, such as Analytic Services. The extract process has a dedicated connection pool that is created when a star schema is created. The default pool is 16 temporary connections that are destroyed when the processing is complete.

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

Application A is logged on: 8 connections (plus system) Application B is logged on: 8 connections (plus system) Application C is logged on: 8 connections (plus system) System connections: 59 (8 plus 17 per application) Total connections: 83
Note: Total connections could grow by 96 if all application connection pools expand to the

system maximum as defined in the configuration utility (default is 40).


l

Application B is logged off (no users) Total connections: 83 All users log off all applications Total connections: 0

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

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

244 Database Information for Financial Management

Application A (server 2) is logged off (no users) Total connections: 33 All users log off all applications Total connections: 0

At times, connectivity between the application server and the database server might be lost because of network issues, for example. If the system detects that a connection is no longer valid, it attempts to re-create the connection. Deleting applications also consumes the default number of pooled connections. Before deleting an application, Financial Management opens the application to verify security access, consuming the default number of connections. After security is validated, the system deletes the application.

Encrypting UDL Files


During Financial Management configuration, EPM System Configurator creates an unencrypted UDL file by default. In the Advanced Database Options page, you can choose whether to encrypt the file. Financial Management provides a utility to encrypt the UDL file used by the application server to communicate with the database if you chose not to encrypt it during configuration. Based on the UDL file extension, Financial Management detects whether the file is encrypted. If the file extension is .UDL, the system assumes that the file is not encrypted. If the file extension is .HFMUDL, the system assumes that the file is encrypted. To encrypt the UDL file, you can use the EncryptHFMUDL utility in the FinancialManagement/Server directory. The usage is EncryptHFMUDL MyUDL.UDL MyUDL.HFMUDL.
Note: You can encrypt the UDL file during configuration with EPM System Configurator. See

Advanced Options for Database Configuration (Optional) on page 80.

To encrypt the UDL file, at an MS-DOS command prompt, type EncryptHFMUDL


MyUDL.UDL MyUDL.HFMUDL, where MyUDL.UDL is the location and name of your original UDL file, and MyUDL.HFMUDL is the location for the encrypted UDL file.
Note: The encrypted UDL file extension must be .HFMUDL. After encrypting the file, you can

delete the original unencrypted file.

To unencrypt a UDL file, at an MS-DOS command prompt, enter EncryptHFMUDL


MyUDL.HFMUDL MyUDL.UDL /u, where MyUDL.HFMUDL is the location for the encrypted UDL file and MyUDL.UDL is the location and name for the unencrypted UDL file.

Encrypting UDL Files 245

246 Database Information for Financial Management

F
In This Appendix

Updating the Shared Services Registry

Understanding the Shared Services Registry Component Hierarchy ................................ 247 Making Corrections to the Shared Services Registry.................................................. 249 Updating the Host and Port for Financial Management Logical Web Applications ................ 251

Use this appendix only if you are working in an environment with multiple releases, used the information in Working in an Environment with Multiple Releases on page 182 to update the Shared Services Registry, and realize that you made a mistake when you updated the Shared Services Registry. This appendix also includes information about updating component properties for a Financial Management logical Web application. You use the epmsys_registry utility (epmsys_registry.sh on UNIX) to make any required changes to the Shared Services Registry.

Understanding the Shared Services Registry Component Hierarchy


To make corrections to the Shared Services Registry, you have to understand its structure. During configuration of 11.1.1.x products, EPM System Configurator automatically updates the Shared Services Registry with components for each product. For 9.3.x products, you create these components and specify component properties manually by editing the Shared Services Registry. If you made a mistake while updating the Shared Services Registry for 9.3.x components, you can either delete the component, or update a component property. The following illustration shows a subset of the structure of the Shared Services Registry hierarchy. It shows information only for the 9.3.x products for which you updated the registry. These are the component type names you need to know to edit the Shared Services Registry.

Understanding the Shared Services Registry Component Hierarchy 247

For Financial Management, the Shared Services Registry stores the list of clusters and servers, but not the relationship between the clusters and servers. Each component in a hierarchy has its own component properties. To make corrections to the Shared Services Registry, you also have to know the component property names. When you edited the templates, you entered values for each component property. For example, the ESSBASE_PRODUCT component includes the following component properties:
l

host

248 Updating the Shared Services Registry

agent_PortNumber

To find the component properties for any component, you can look at the product's template. The name and location of each template is described in Working in an Environment with Multiple Releases on page 182. Or, you can use a command to view the component in the Shared Services Registry. See Viewing the Components in the Shared Services Registry on page 249.

Making Corrections to the Shared Services Registry


To make corrections to the Shared Services Registry:
1 2
Back up the Shared Services Registry. On a machine hosting the 11.1.x Oracle Hyperion Enterprise Performance Management System software, go to HYPERION_HOME/common/config/9.5.0.0 and run the following command:
epmsys_registry view componentType

You need to view the component hierarchy to get information required to delete a component or update a component property. For information see Viewing the Components in the Shared Services Registry on page 249.

Depending on the required corrections, delete a component or update a component property.

For example, you might need to delete a component if you inadvertently updated the Shared Services Registry with an incorrect product. For information see Deleting a Component Instance on page 250. Or, you might need to update a component property if you inadvertently updated the Shared Services Registry with an incorrect port number. For information see Updating a Component Property on page 250.

If you've made changes for Oracle Hyperion Planning, Fusion Edition, Oracle Hyperion Performance Scorecard, Fusion Edition, or Financial Management, run Oracle's Hyperion Enterprise Performance Management System Configurator and configure EPM Workspace Web Server again. (On the Task Selection page, select the EPM Workspace Web Server Configuration task.) Then, restart the EPM Workspace Web Application. Restart Oracle's Hyperion Shared Services.

Viewing the Components in the Shared Services Registry


Before you can delete a component or update a component property, you need to view the component hierarchy.

To view the component hierarchy, go to HYPERION_HOME/common/config/9.5.0.


0 and use the following command:
epmsys_registry view componentType

Making Corrections to the Shared Services Registry 249

where componentType is the name of the component in the Shared Services Registry. See Understanding the Shared Services Registry Component Hierarchy on page 247 for details on component type names. This command displays all the components in the specified hierarchy, displaying only the immediate children of the component. The information is displayed in the console. For example, to view all the components in the ESSBASE_PRODUCT hierarchy, run:
epmsys_registry view SYSTEM9/ESSBASE_PRODUCT

For example, to view the Web application for Essbase Server, enter the following command:
epmsys_registry view SYSTEM9/ESSBASE_PRODUCT/ESSBASE_SERVER

From the display, note the following information about components you want to delete or update:
l

Component ID for any components you want to delete or update Component property names and values for any components you want to update

Deleting a Component Instance


You delete a component instance by referring to the component's ID that is displayed when you view the component hierarchy.

To delete a component from the component hierarchy, go to HYPERION_HOME/


common/config/9.5.0.0 and run the following command:
epmsys_registry deletecomponent #componentID

where componentID is the component's ID that you found when you viewed the component hierarchy. On UNIX, run:
epmsys_registry.sh deletecomponent \#componentID

Deleting a node does not delete its children.


Tip: If you are deleting a product node, first delete all the children of the node and then delete

the product node.


Caution!

Make sure to delete the correct component.

Updating a Component Property


You update a component property by referring to the component ID and the component property name that are displayed when you view the component hierarchy.

250 Updating the Shared Services Registry

To update a component property, go to HYPERION_HOME/common/config/9.5.0.


0 and run the following command:
epmsys_registry updateproperty #componentID/@componentProperty value

where componentID is the component's ID you found when you viewed the component hierarchy, componentProperty is the component property name you want to update, and value is the new value for the component property. On UNIX, run:
epmsys_registry.sh updateproperty \#componentID/@componentProperty value

Component property names are case sensitive.


Tip: Look for the component property names in the section called Properties when you view

the component hierarchy. In addition, you can update the host a component is running on using the property name host. For example, to change the port number for the Oracle Essbase Server with the component ID 99999 to port number 1425, enter the following command:
epmsys_registry updateproperty #99999/@agent_PortNumber 1425

Updating the Host and Port for Financial Management Logical Web Applications
You can edit the Oracle's Hyperion Shared Services Registry to update the host or port for a Oracle Hyperion Financial Management, Fusion Edition logical Web application.

To update the host or port for a Financial Management logical web application:
1 2
Use the following command to get the component ID for the logical web application:
epmsys_registry view SYSTEM9/FINANCIAL_MANAGEMENT_PRODUCT/LOGICAL_WEB_APP

Use the following command to update the host or port component property:
epmsys_registry updateproperty #componentID/@componentProperty value

where the componentID is the ID you found in step 1 and where componentProperty is host, port, or SSL_Port .

Updating the Host and Port for Financial Management Logical Web Applications 251

252 Updating the Shared Services Registry

G
In This Appendix

Enabling an X Virtual Frame Buffer for Financial Reporting and Web Analysis

Enabling Xvfb for AIX 5L ................................................................................. 253 Enabling Xvfb for Solaris 9 .............................................................................. 253 Enabling Xvfb for Solaris 10 ............................................................................ 254 Enabling Xvfb for Oracle Enterprise Linux/Red Hat Enterprise Linux ................................ 254 Enabling Xvfb for HP-UX ................................................................................. 255 Setting the DISPLAY Variable ........................................................................... 255

Enabling Xvfb for AIX 5L


To enable Xvfb:
1 2
Log on to the computer that will run the Reporting and Analysis Web application server components as the root user. Determine whether Virtual Frame Buffer support is available on your computer by issuing the following command:
lslpp -l X11.vfb

If X11.vfb is not installed, install it from your AIX installation media. After installing the package, apply the latest PTF from:

http://techsupport.services.ibm.com

Start Xvfb:
/usr/bin/X11/X -force -vfb :1

where :1 is the a display number not already in use.

Enabling Xvfb for Solaris 9


To enable Xvfb:
1 2
Log on to the computer that will run the Reporting and Analysis Web application server components as the root user. Obtain and compile the X11R6 source distribution from:

Enabling Xvfb for AIX 5L 253

ftp://x.org/, or obtain and install the binary distribution from ftp://www.ferret.noaa.gov/ special_request/xvfb/solaris

Start Xvfb:

/usr/X11R6/bin/Xvfb :1 -screen 0 1152x900x8 &

where :1 is the a display number not already in use.

Enabling Xvfb for Solaris 10


To enable Xvfb:
1 2
Log on to the computer that will run theReporting and Analysis Web application server components as the root user. Determine whether Virtual Frame Buffer support is available on your computer by issuing the following command:
pkgchk -l SUNWxwsrv

3 4

If SUNWxwsrv is not installed, install it from the Solaris installation media. Start Xvfb:

/usr/openwin/bin/Xvfb :1 > /dev/null 2>&1 &

where :1 is the a display number not in use.

Enabling Xvfb for Oracle Enterprise Linux/Red Hat Enterprise Linux


To enable Xvfb:
1 2
Log on to the computer that will run theReporting and Analysis Web application server components as the root user. Determine whether Virtual Frame Buffer support is available on your computer by issuing the following command:
rpm -aq | grep -i 'vfb'

Note: If Xvfb is not installed, install it from your installation media, RHN, or ULN Web

site.

Start Xvfb:

/usr/X11R6/bin/Xvfb :1 -screen 0 1152x900x8 &

where :1 is the a display number not already in use.

254 Enabling an X Virtual Frame Buffer for Financial Reporting and Web Analysis

Enabling Xvfb for HP-UX


To enable Xvfb:
1 2
Log on to the computer that will run the Reporting and Analysis Web application server components as the root user. Determine whether Virtual Frame Buffer support is available on your computer by issuing the following command:
swlist -l product | grep 'Xserver cumulative patch'

3 4

Ensure that the patch level installed on your system corresponds with HP's recommended level (currently PHSS_31293). Copy /etc/X11/X0screens to /etc/X11/X1screens, where 1 is a display number not already in use; for example:
cp /etc/X11/X0screens /etc/X11/X1screens

Edit /etc/X11/X1screens by adding these lines to the end of the file:


ServerOptions ServerMode XVfb

Start Xvfb:
nohup /usr/bin/X11/Xvfb :1 -screen 0 1024x800x8 \ -pn -fp /usr/lib/X11/fonts/misc -sp /etc/X11/SecurityPolicy &

where :1 is the display number not already in use.

Setting the DISPLAY Variable


Prior to starting the Reporting and Analysis Web application server components on UNIX, set the DISPLAY environment variable to an available physical or virtual (Xvfb) graphics device address; for example:
DISPLAY=hostname:0.0 ; export DISPLAY

For the sake of convenience, it is recommended that DISPLAY be initialized automatically by editing theReporting and Analysis Web application server components start scripts.
Note: Only the Financial Reporting and Web Analysis Oracle's Hyperion Reporting and Analysis

Web application server components require DISPLAY be set. The Oracle Enterprise Performance Management Workspace, Fusion Edition component does not require access to X11.
Tip: Display can be set for Oracle Hyperion Financial Reporting, Fusion Edition and Oracle's Hyperion Web Analysis by editing setCustomParamsFinancialReporting.sh and setCustomParamsWebAnalysis.sh in HYPERION_HOME/deployments/AppServer/ bin.

Enabling Xvfb for HP-UX 255

Note: If you are using Oracle Application Server on UNIX, in addition to using a script to set the environment variables, you must specify the DISPLAY environment variable in the

Oracle Application Server Application Server Console, by setting the Server properties for the OC4J instance.

256 Enabling an X Virtual Frame Buffer for Financial Reporting and Web Analysis

Index

A
Administration Services application server UNIX startup scripts, 120 Windows service names, 120 environment variables on UNIX, 233 environment variables on Windows, 236 installation folders, 218 postconfiguration tasks, 147 starting, 120 upgrading in a mixed release environment, 189 upgrading security tasks, 176 ais.cfg file, 122 application server deployment Embedded Java Container, 87 general information, 81 Oracle Application Server, 83 redeploying, 193 time changes, 102 WebLogic, 84 WebSphere, 85 applications, upgrading, 170 ARBORPATH, 95, 233 assemblies, 19, 20, 21. See also installation assemblies auditing license compliance, 205 automatic deployment, 82. See also application server deployment

B
Business Rules upgrading postconfiguration tasks, 175

C
Calculation Manager installation folders, 212 launching from EPM Workspace, 133 starting, 126

UNIX startup script, 126 upgrading postconfiguration tasks, 175 Windows Service Name, 126 Windows startup script, 126 Capital Asset Planning, 77 checklist installing, 14 upgrading, 167 client/server compatibility, Essbase, 239 clustering, 88 common settings, 78 configuration, 143. See also postconfiguration tasks configuration sequence distributed environment, 68 overview, 66 single machine, 68 SSL, 68 upgrade, 69 configuring, 88, 193. See also reconfiguring application server deployment, 81 clusters for Planning, 97 command line, 108 common settings, 78 database, 78, 80 Embedded Java Container deployment, 87 EPM Workspace, 89 Essbase, 94 Essbase multiple instances, 96 FDM, 107 Financial Management, 99 logs, 110 Oracle Application Server deployment, 83 overview, 63 Performance Management Architect, 92 Planning, 97 prerequisites, 64 procedure, 72 product options, 77

Index 257

Reporting and Analysis, 106 sequence, 66 Shared Services registration, 75 silent, 108 SSL, 78 Strategic Finance, 107 task selection, 74 task summary, 69 troubleshooting, 110 upgrade process, 163 upgrade tasks, 77 WebLogic deployment, 84 WebSphere deployment, 85 connection pooling, 243 corporate user directories, 113

Reporting and Analysis, 139 DISPLAY variable, 255 distributed installation, 15 documentation, 17 downloading documentation, 17 installation files, 19 DSN, 105

E
E-delivery, 19 eas_home, 236 Embedded Java Container deployment, 87 encrypting UDL files, 245 environment variables Administration Services on Windows, 236 Administration Services on UNIX, 233 Essbase Server on UNIX, 227 Essbase Server on Windows, 233 Essbase Studio, 236 Integration Services on UNIX, 231 Integration Services on Windows, 236 Provider Services on UNIX, 233 Provider Services on Windows, 236 EPM System products overview, 13 EPM Workspace application server UNIX startup script, 132 Windows service names, 132 configuring, 89 default URLs, 133 installation folders, 210 postconfiguration tasks, 145 starting, 116 EPM Workspace Web server UNIX startup script, 116 Windows service names, 116 epmsys_registry utility, 182, 247 ERP Integrator installation folders, 224 postconfiguration tasks, 158 starting, 132 Windows service names, 132 error logs

D
Data Management diagnostics, 141 installation assemblies, 42 Data Relationship Management default URLs, 133 installation folders, 225 postconfiguration tasks, 159 repository passwords, 197 starting, 131 Windows service names, 131 database configuration, 78 advanced options, 80 Shared Services, 75 database connection pooling, 243 databases for repositories starting, 113 DCOM, 99 default URLs, 133 deployment, 81 Embedded Java Container, 87 Oracle Application Server, 83 WebLogic, 84 WebSphere, 85 deployment scenarios, 199 diagnostics, 135 Data Management, 141 Essbase, 138 Financial Performance Management Applications, 140 Foundation Services, 136
258 Index

configuration, 73 diagnostics, 136 installation, 60, 210 troubleshooting, 110 uninstalling, 202 ESS_CSS_JVM_OPTION, 229 ESS_JVM_OPTION, 229 Essbase diagnostics, 138 installation assemblies, 27 postconfiguration tasks, 145 upgrading security tasks, 175 Essbase Server configuring, 94 configuring multiple instances, 96 environment variables on Windows, 233 installation folders, 213 installing multiple instances, 62 legacy security, 95 manually configuring on UNIX, 227 manually configuring on Windows, 234 multiple instances, 62 starting, 119 starting multiple instances, 96 UNIX startup script, 119 Windows service names, 119 Essbase Server environment variables on Windows, 233 installing multiple instances, 62 manually configuring on Windows, 234 Essbase Server configuring, 94 configuring multiple instances, 96 installation folders, 213 legacy security, 95 manually configuring on UNIX, 227 starting, 119 UNIX startup script, 119 Windows service names, 119 Essbase Studio environment variables, 236 installation folders, 215 postconfiguration tasks, 148 starting, 122 UNIX startup scripts, 122 Windows startup scripts, 122 essbase.cfg file, 94, 227, 233, 234

ESSBASEPATH, 233 ESSLANG , 95, 96

F
failover Oracle RAC, 242 FDM configuring, 107 default URLs, 133 installation folders, 224 postconfiguration tasks, 158 repository passwords, 196 starting, 131 upgrading security tasks, 180 Windows service names, 131 Financial Management configuring, 99 database connection pooling, 243 DCOM configuration, 99 DSN configuration, 105 installation folders, 221 launching from EPM Workspace, 133 postconfiguration tasks, 156 Schema Upgrade Utility, 172 starting, 127 UDL file encryption, 245 upgrading postconfiguration tasks, 171 upgrading security tasks, 176 Windows service names, 127 Financial Performance Management Applications diagnostics, 140 installation assemblies, 37 Financial Reporting application server UNIX startup script, 126 Windows service names, 126 UNIX startup script, 123 Windows service names, 123 Financial Reporting configuration High Availability driver, 154 Foundation Services diagnostics, 136 installation assemblies, 21

G
groups, upgrading, 175

Index 259

H
Hyperion home directory, 16, 52, 208 hyperionenv.doc, 213, 227, 228

I
IBM AIX setting user limits on 64-bit platforms, 146 installation assemblies, 19 Data Management, 42 downloading, 19 Essbase, 27 Financial Performance Management Applications, 37 Foundation Services, 21 Reporting and Analysis, 34 installation checklist, 14 installation documentation, 17 installation files, preparing, 19 installation folders Administration Services, 218 Calculation Manager, 212 Data Relationship Management , 225 EPM Workspace, 210 ERP Integrator , 224 Essbase, 213 Essbase Studio, 215 FDM, 224 Financial Management, 221 Integration Services, 216 Performance Management Architect, 211 Performance Scorecard, 222 Planning, 221 Profitability and Cost Management, 224 Provider Services, 219 Reporting and Analysis, 220 Shared Services, 207 Smart Search Command Line Utility, 219 Smart View, 213 Strategic Finance, 223 installing, 62 by component, 53, 54 by tier, 53, 54 cancelling, 59 destination, 52 distributed environment, 15 location, 16 logs, 60
260 Index

procedure, 49 sequence, 47 silent, 59, 60, 61 types, 53 upgrade process, 163 instance. See clustering Integration Services environment variables, 236 environment variables on UNIX, 231 installation folders, 216 postconfiguration tasks, 146 starting, 121 UNIX startup script, 121 Windows service names, 121 Interactive Reporting starting and stopping services, 115 interface datasources, 92 changing passwords, 196

J
JDBC URL, 80 JDBC URL attributes, 241 JVMMODULELOCATION, 230, 234

L
legacy security, Essbase Server, 95 license compliance, 205 load balancing Oracle RAC, 242 logs configuration, 73, 110 diagnostics, 136 installation, 60, 210 uninstalling, 202

M
maintenance release, 53 manual deployment, 82. See also application server deployment Microsoft SQL Server Windows Authentication, 80 mixed release environment, 182, 247 multiple instances of Essbase Server, 62

N
new installation, 53

O
OpenLDAP UNIX startup script, 113 Windows service name, 113 Oracle Application Server deployment, 83 Oracle Internet Directory, 113 Oracle RAC, 80, 241

P
passwords changing, 195 Performance Management Architect application server Windows service names, 125 configuring, 92 Data Synchronizer application server Windows service names, 125 installation folders, 211 interface datasource password, 196 launching from EPM Workspace, 133 postconfiguration tasks, 144 starting, 117 upgrading postconfiguration tasks, 173 Web services Windows service name, 118 Windows service names, 117 Performance Scorecard application server UNIX startup script, 129 Windows service names, 129 default URLs, 133 installation folders, 222 launching from EPM Workspace, 133 postconfiguration tasks, 157 starting, 129 upgrading security tasks, 176 Performance Scorecard Alerter application server UNIX startup script, 129 Windows service names, 129 Planning application server UNIX startup script, 127 Windows service names, 127 applications password, 196 clustering, 97, 98

configuring, 97 installation folders, 221 launching from EPM Workspace, 133 postconfiguration tasks, 155 starting, 127 upgrading in a mixed release environment, 186 upgrading postconfiguration tasks, 170 ports, 197. See also SSL port reconfiguring, 197 postconfiguration tasks, 143 Administration Services, 147 Data Relationship Management , 159 EPM Workspace, 145 ERP Integrator , 158 Essbase, 145 Essbase Studio, 148 FDM Adapters, 158 Financial Management, 156 general tasks, 143 Integration Services, 146 Performance Management Architect, 144 Performance Scorecard, 157 Planning, 155 Provider Services, 148 Reporting and Analysis, 149 Shared Services, 144 Strategic Finance, 157 upgrading, 170 Calculation Manager, 175 Financial Management, 171 Performance Management Architect, 173 Planning, 170 Reporting and Analysis, 181 Strategic Finance, 182 prerequisites, 19 installation and configuration, 13 upgrading, 168 product options, 77 Profitability and Cost Management installation folders, 224 launching from EPM Workspace, 133 starting, 130 UNIX startup scripts, 130 Windows service name, 130 Windows startup script, 130 Provider Services application server

Index 261

UNIX startup script, 122 Windows service names, 122 environment variables, 236 environment variables on UNIX, 233 installation folders, 219 manually configuring on UNIX, 233 manually configuring on Windows, 236 postconfiguration tasks, 148 starting, 122

R
RAC, 80, 241 reconfiguring, 193 passwords, 195 ports, 197 SSL, 193 Web application server, 193 redeploying, 193 registration, Shared Services, 75 registry. See Shared Services Registry reinstalling, 53 procedure, 49 release numbers supported for upgrading, 162 Reporting and Analysis configuring, 106 diagnostics, 139 installation assemblies, 34 installation folders, 220 launching from EPM Workspace, 133 postconfiguration tasks, 149 starting, 123 upgrading postconfiguration tasks, 181 repository passwords, changing, 195 response files silent configuration, 108 silent installation, 60, 61

S
security hardening, 143 upgrading, 175 sequence configuring, 66 installing, 47 upgrading, 167 server/client compatibility, Essbase, 239

service names. See Windows service names setEssbaseEnv.cmd, 213, 234 Shared Services application server UNIX startup script, 114 Windows service names, 114 changing log file location, 229 installation folders, 207 OpenLDAP UNIX startup script, 113 Windows service name, 113 postconfiguration tasks, 144 starting, 114 Shared Services Console default URLs, 133 Shared Services Registry, 64, 75 editing for a mixed release environment, 182, 247 silent configuration, 108 response files, 108 silent installation, 60, 61 response file, 59 silent uninstallation, 203 Smart Search Command Line Utility application server UNIX startup script, 121 Windows service names, 121 installation folders, 219 starting, 121 Smart View installation folders, 213 SSL, 91. See also SSL port configuration sequence, 68 configuring, 78 enabling, 78 enabling for Workspace Web Server, 91 reconfiguring, 193 SSL port Embedded Java Container, 87 WebLogic, 84 WebSphere, 86 start script, 111 start.bat file, 111 startEssbase.cmd file, 97 startEssbase.sh file, 227 starting products script, 111 start order, 112

262 Index

startup dependencies, 111 stop script, 111 stop.bat file, 111 stopping products, 111 Strategic Finance configuring, 107 installation folders, 223 postconfiguration tasks, 157 starting, 128 upgrading postconfiguration tasks, 182 Windows service names, 128 Strategic Finance for Banking, 77

T
task selection, configuration, 74 troubleshooting, 54, 110, 135

U
UDL file, 81 encryption and unencryption, 245 undeploying, 201 uninstalling, 201 before upgrading, 163 silent, 203 unique identity attribute, 180 UNIX startup scripts, 111 Administration Services application server, 120, 121 Calculation Manager, 126 EPM Workspace Web server, 116 EPM Workspace application server, 132 Essbase Studio Server, 122 Financial Reporting, 123 Financial Reporting application server, 126 Integration Services, 121 Performance Scorecard Alerter application server, 129 Performance Scorecard application server, 129 Planning application server, 127 Profitability and Cost Management, 130 Provider Services application server, 122 Essbase Server, 119 Shared Services application server, 114 Shared Services OpenLDAP, 113 Web Analysis application server, 124 upgrade homes, 57

upgrading, 53, 161 applications, 170 checklist, 167 configuration sequence, 69 configuration tasks, 77 mixed release environment, 182, 247 partial upgrade , 182 postconfiguration tasks, 170 Calculation Manager, 175 Financial Management, 171 Performance Management Architect, 173 Planning, 170 Reporting and Analysis, 181 Strategic Finance, 182 prerequisites, 168 procedure, 49 security tasks, 175 supported paths, 162 troubleshooting, 54 unique identity attribute, 180 users and groups, 175 what happens during, 163 URLs, default, 133 user limits 64bit AIX, 146 users, upgrading, 175

W
Web Analysis application server UNIX startup script, 124 Windows service names, 124 Web application server clustering, 88 redeploying, 193 WebLogic deployment, 84 single domain, 85 WebSphere deployment, 85 single profile, 86 Windows service names, 111 Administration Services application server, 120, 125 Calculation Manager, 126 Data Relationship Management, 131 EPM Workspace Web server, 116
Index 263

EPM Workspace application server, 132 ERP Integrator, 132 FDM, 131 Financial Management, 127 Financial Reporting, 123 Financial Reporting application server, 126 Integration Services, 121 Performance Management Architect, 117 Performance Management Architect Data Synchronizer application server, 125 Performance Management Architect Web services, 118 Performance Scorecard application server, 129 Performance Scorecard Alerter application server, 129 Planning application server, 127 Profitability and Cost Management, 130 Provider Services application server, 122 Essbase Server, 119 Shared Services application server, 114 Shared Services OpenLDAP, 113 Smart Search Command Line Utility application server, 121 Strategic Finance, 128 Web Analysis application server, 124 Windows startup scripts Administration Services, 120 Calculation Manager, 126 EPM Workspace, 115, 116, 132 Essbase Server, 119 Essbase Studio Server, 122 Integration Services, 121 Profitability and Cost Management, 130 Provider Services, 122 Reporting and Analysis, 123 Shared Services, 114 Smart Search Command Line Utility, 121 Workforce Planning, 77

Z
zip files, 20 downloading, 19

X
Xvfb for AIX 5L, 253 for Enterprise Linux, 254 for HP-UX, 255 for Solaris 10, 254 for Solaris 9, 253 setting the display, 255
264 Index