Epm Install

Oracle Enterprise Performance Management System
Installation and Configuration Guide

Release 11.1.2.3
Updated: May 2015
EPM System Installation and Configuration Guide, 11.1.2.3
Copyright 2008, 2015, 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 is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of
the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS:
Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or
documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable
Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure,
modification, and adaptation of the programs, including any operating system, integrated software, any programs installed
on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs.
No other rights are granted to the U.S. Government.
This software or hardware 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 that may create a risk of
personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all
appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates
disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective
owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under
license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the
AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark
of The Open Group.
This software or hardware and documentation may provide access to or information about 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 unless otherwise set forth in an applicable agreement
between you and Oracle. 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, except as set forth in an applicable agreement
between you and Oracle.
Contents
Documentation Accessibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Chapter 1. About EPM System Product Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

About EPM System Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Assumed Knowledge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
About Middleware Home, EPM Oracle Home, and EPM Oracle Instance . . . . . . . . . . . . . 19
About the Shared Services Registry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Characters Supported for Installation and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 20
Chapter 2. EPM System Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

About EPM System Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Disclosure Management Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Essbase Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
FDM Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
FDMEE Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Financial Close Management Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Stand-Alone Financial Close Management Deployment Requirements for Test and
Production . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Financial Management Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Performance Management Architect Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Planning Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Profitability and Cost Management Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Reporting and Analysis Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Strategic Finance Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Stand-AloneStrategic Finance Deployment Requirements for Test and Production . . . 33
Chapter 3. Preparing Your Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Preparing Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Applying Windows Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Resolving Port Conflicts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Disabling User Access Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
iii
Setting the DCOM Default Authentication Level (Windows 2008) . . . . . . . . . . . . . . . 36
Synchronizing Clocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Resolving Host Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Disabling Anti-virus Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Shared File System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Preparing User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Disk Space and RAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Client Disk Space and RAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Server Disk Space and RAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Preparing a Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Using an Oracle Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Using a Microsoft SQL Server Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Using an IBM DB2 Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Preparing Java Web Application Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
WebLogic Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
IBM WebSphere . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Preparing Web Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Oracle HTTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Microsoft Internet Information Services (IIS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Preparing Web Browsers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Browser Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Enabling ActiveX (Reporting and Analysis) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Support Matrix for High Availability and Load Balancing . . . . . . . . . . . . . . . . . . . . . . . . 56
Chapter 4. Downloading Files for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Downloading the Installation Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Chapter 5. Installing EPM System Products in a New Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Installation Checklist for a New Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Deploying to a Shared Drive Environment (UNIX) . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Financial Close Management (Close Manager and Account Reconciliation Manager)
Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Installation Prerequisites and Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Web Server Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Configuring X11 for Financial Reporting and Production Reporting (AIX and HP-
UX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Installation Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Installing EPM System Products in a Distributed Environment . . . . . . . . . . . . . . . . . . . . 81
Integrating Oracle BI EE with EPM System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Installing EPM System Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
iv
Welcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Destination/Middleware Home . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Installation Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Product Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Performing Silent Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Loading Saved Selections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Modifying Response Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Installing EPM System Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Client Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Downloading and Extracting Client Installers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Installing Individual EPM System Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Installing EPM System Clients from EPM Workspace . . . . . . . . . . . . . . . . . . . . . . . . 95
Installing EPM System Clients From EPM System Installer . . . . . . . . . . . . . . . . . . . . 96
Installing Multiple Versions of Financial Reporting Studio on a Client Machine . . . . . 97
Performing Silent Client Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Default Installation Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Chapter 6. Configuring EPM System Products in a New Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

About EPM System Configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Configuration Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Ensuring that Host Names Resolve . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Creating Infrastructure Schemas Using Repository Creation Utility . . . . . . . . . . . . . 101
Configuration Prerequisites for Financial Close Management . . . . . . . . . . . . . . . . . 103
Configuration Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Configuring Products in a Distributed Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Configuring Products in an SSL-Enabled Environment . . . . . . . . . . . . . . . . . . . . . . . . . 107
Configuring Products for Manual Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Configuring Products for WebSphere Application Server . . . . . . . . . . . . . . . . . . . . . . . . 108
Product Configuration Task Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Configuring EPM System Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Refreshing EPM Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
EPM System Configurator Task Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Configure Oracle Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Task Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Configure Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Deploy to Application Server Specify WebLogic Domain Information . . . . . . . . . 120
Deploy to Application Server: Oracle WebLogic . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Foundation Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
v
Performance Management Architect Configuration Tasks . . . . . . . . . . . . . . . . . . . 132
Essbase Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Reporting and Analysis ConfigurationTasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Planning Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Financial Management Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Performance Scorecard Configure Attachment Files Location . . . . . . . . . . . . . . . 147
Strategic Finance Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Financial Close Management Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . 148
FDMEE Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
FDM Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Performing Silent Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Setting Up Essbase in Standalone Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Deploying Financial Management, Financial Reporting, and Web Analysis on Windows in
a UNIX-Based EPM System Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
What Happens During Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Troubleshooting Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Chapter 7. Manually Deploying EPM System Java Web Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Assumptions and Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Manually Deploying Java Web Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Additional Postdeployment Steps for FDMEE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Configuring JMS Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Extending a Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Manually Configuring Oracle HTTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Chapter 8. Deploying EPM System Products to WebSphere Application Server . . . . . . . . . . . . . . . . . . . . . . . 169

Additional Postdeployment Steps for FDMEE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Configuring IBM HTTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Validating WebSphere Application Server Deployments . . . . . . . . . . . . . . . . . . . . . . . . 175
Chapter 9. Performing Manual Configuration Tasks in a New Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Essbase Manual Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Setting User Limits on 64-bit AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Enabling Client Lookup by Cluster Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Reporting and Analysis Manual Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Financial Close Management Manual Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . 179
Setting Up the Keystore for Message Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Configuring the WebLogic Domain to OID, MSAD, SunOne . . . . . . . . . . . . . . . . . . 182
Start Managed Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Raising the Maximum Capacity in the Connection Pool . . . . . . . . . . . . . . . . . . . . . 183
vi
Increasing the Connection Pool of the External LDAP Provider . . . . . . . . . . . . . . . . 184
FDMEE Manual Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Chapter 10. Performing a Maintenance Release Installation for EPM System Products . . . . . . . . . . . . . . . . . 187
Maintenance Release Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Financial Close Management Maintenance Release Installation Checklist . . . . . . . . . . . . 188
Downloading and Extracting Installation Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Performing Maintenance Release Installation Prerequisite Tasks . . . . . . . . . . . . . . . . . . 190
Essbase Maintenance Release Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . 191
Business Rules Maintenance Release and Upgrade Installation Prerequisites . . . . . . . 192
Financial Reporting Maintenance Release Installation Prerequisites . . . . . . . . . . . . . 193
Maintenance Release Installation Prerequisites if You Are Using Oracle Web Services
Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Installing and Configuring EPM System Products in a Maintenance Installation . . . . . . . 194
Maintenance Installation Deployments to a Single Managed Server . . . . . . . . . . . . . . . . 197
Scenario 1: You either deployed all Java web applications to their own managed servers,
or deployed all Java web applications to a single managed server in Release 11.1.2.0,
11.1.2.1, or Release 11.1.2.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Scenario 2: You were working in a Release 11.1.2.1 or Release 11.1.2.2 environment that
had some Java web applications deployed to a single managed server and some Java web
applications deployed to their own managed servers . . . . . . . . . . . . . . . . . . . . . . . . 199
Performing Manual Configuration Tasks in a Maintenance Installation . . . . . . . . . . . . . 200
General Manual Configuration Tasks in a Maintenance Installation . . . . . . . . . . . . . 200
EPM Workspace Manual Configuration Tasks in a Maintenance Installation . . . . . . 200
Performance Management Architect Manual Configuration Tasks in a Maintenance
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Essbase Manual Configuration Tasks in a Maintenance Installation . . . . . . . . . . . . . 201
Essbase Studio Manual Configuration Tasks in a Maintenance Installation . . . . . . . . 202
Planning Manual Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Profitability and Cost Management Manual Configuration Tasks . . . . . . . . . . . . . . . 204
Strategic Finance Manual Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
FDM Manual Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Maintenance Installation Deployments to WebSphere Application Server . . . . . . . . . 205
Validating the Deployment and Generating a Deployment Report . . . . . . . . . . . . . . . . . 205
Performing a Maintenance Release Installation for EPM System Clients . . . . . . . . . . . . . 206
Chapter 11. Upgrading EPM System Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

About Upgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Supported Upgrade Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Upgrading Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Upgrade Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
vii
Backing Up the Earlier Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Performing Product-Specific Upgrade Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . 212
Business Rules Maintenance Release and Upgrade Installation Prerequisites . . . . . . . 213
Downloading and Preparing Files for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Preparing Data for Upgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Exporting Shared Services Data from the Earlier Release . . . . . . . . . . . . . . . . . . . . . 215
Exporting Financial Management and Strategic Finance Data from the Earlier
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Copying Files for Temporary Use During Configuration . . . . . . . . . . . . . . . . . . . . . 217
Replicating Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Replicating the Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Stopping EPM System Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Uninstalling the Earlier Release of EPM System Products . . . . . . . . . . . . . . . . . . . . . . . . 227
Installing EPM System Products for an Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Configuring EPM System Products in an Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
What Happens During Shared Services Data Import . . . . . . . . . . . . . . . . . . . . . . . . 233
Upgrading a Distributed Deployment of Reporting and Analysis . . . . . . . . . . . . . . . 234
Starting EPM System Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Validating the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Performing Manual Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Updating References to a Rehosted Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Updating References to a Rehosted Essbase Server . . . . . . . . . . . . . . . . . . . . . . . . . 236
Updating Provider Services References to a Rehosted Essbase Server . . . . . . . . . . . . . 238
Updating Administration Services References to a Rehosted Essbase Server or Provider
Services Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Updating Essbase Studio References to a Rehosted Environment . . . . . . . . . . . . . . . 240
Updating Reporting and Analysis References to a Rehosted Server Environment . . . . 243
Updating Performance Management Architect References to a Rehosted Server
Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Updating Planning References to a Rehosted Server Environment and Upgrading
Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Updating Profitability and Cost Management References to a Rehosted Essbase
Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
Updating Strategic Finance References to a Rehosted Essbase Server or Financial
Management Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
Updating Performance Scorecard References to a Rehosted Essbase Server . . . . . . . . 249
Updating Integration Services References to a Rehosted Server Environment . . . . . . 249
Upgrading Applications from the Earlier Release to the Current Release . . . . . . . . . . . . . 250
Performing Manual Configuration Tasks in an Upgrade . . . . . . . . . . . . . . . . . . . . . . . . 251
Performance Management Architect Upgrade Tasks . . . . . . . . . . . . . . . . . . . . . . . . 251
viii
Essbase Upgrade Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Essbase Studio Upgrade Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Reporting and Analysis Upgrade Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
Planning Upgrade Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
Financial Management Upgrade Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
Strategic Finance Upgrade Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
FDMEE Upgrade Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
FDM Upgrade Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
Upgrading Smart View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
Upgrading from an Environment with Multiple Releases . . . . . . . . . . . . . . . . . . . . . . . . 261
Upgrading From an Environment with a Single Instance of Shared Services . . . . . . . 261
Upgrading From an Environment with Two Instances of Shared Services . . . . . . . . . 261
Repeating the Upgrade Process for Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
Chapter 12. Starting and Stopping EPM System Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

Using a Single Script to Start Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
Launching Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
Chapter 13. Validating the Installation and Verifying Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269

Validating the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Using EPM System Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Diagnostics Performed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
Generating a Deployment Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
Verifying Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
Verifying Shared Services Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
Verifying EPM Workspace Deployment and Products in EPM Workspace . . . . . . . . 272
Additional Verification for Financial Close Management . . . . . . . . . . . . . . . . . . . . . 273
Verifying Administration Services Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
Verifying Provider Services Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
Validating a Financial Close Management Deployment . . . . . . . . . . . . . . . . . . . . . . . . . 274
Appendix A. Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279

Default Ports and Shared Services Registry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
WebLogic Administration Server Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
WebSphere Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
WebSphere Application Server Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
IBM HTTP Server Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
Oracle Enterprise Manager Java Web Application Port . . . . . . . . . . . . . . . . . . . . . . . . . 281
SOA Server Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
ix
SSL Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
Foundation Services Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
Foundation Services Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
Performance Management Architect Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
Calculation Manager Java Web Application Ports . . . . . . . . . . . . . . . . . . . . . . . . . . 282
Essbase Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
Essbase Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
Administration Services Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
Provider Services Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
Essbase Studio Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
Reporting and Analysis Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
Reporting and Analysis Framework Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
Financial Reporting Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
Interactive Reporting Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
Web Analysis Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
Financial Performance Management Applications Ports . . . . . . . . . . . . . . . . . . . . . . . . 286
Financial Management Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
Financial Close Management Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
Planning Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
Performance Scorecard Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
Strategic Finance Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
Profitability and Cost Management Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
Disclosure Management Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
Data Management Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
FDM Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
FDMEE Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
Data Relationship Management Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
Appendix B. JDBC URL Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293

JDBC Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
URL for Oracle RAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
LDAP-Based URL for Oracle Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
URL for SSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
Appendix C. Database Information for Financial Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295

Database Connection Pooling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
x
Appendix D. EPM System Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
EPM System Services and Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
Web Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
Foundation Services Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
Performance Management Architect Dimension Server Services . . . . . . . . . . . . . . . 302
Performance Management Architect Application Server . . . . . . . . . . . . . . . . . . . . . 303
Performance Management Architect Data Synchronizer Application Server . . . . . . . 303
Calculation Manager Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
Essbase Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
Administration Services Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
Integration Services Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
Essbase Studio Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
Provider Services Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
Hyperion Reporting and Analysis Framework - Agent Service . . . . . . . . . . . . . . . . . 310
Reporting and Analysis Framework Application Server . . . . . . . . . . . . . . . . . . . . . . 310
Financial Reporting Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
Web Analysis Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
Planning Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
Financial Management Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
Financial Management Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
Strategic Finance Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
Strategic Finance Web Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
Performance Scorecard Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
Performance Scorecard Alerter Application Server . . . . . . . . . . . . . . . . . . . . . . . . . 317
Profitability and Cost Management Application Server . . . . . . . . . . . . . . . . . . . . . . 317
Disclosure Management Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
Financial Close Management Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
Data Relationship Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
FDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
FDMEE Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
xi
xii
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support.
For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://
www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
13
14
Documentation Feedback
Send feedback on this documentation to: epmdoc_ww@oracle.com

Follow EPM Information Development on these social media sites:
LinkedIn - http://www.linkedin.com/groups?gid=3127051&goback=.gmp_3127051
Twitter - http://twitter.com/hyperionepminfo
Facebook - http://www.facebook.com/pages/Hyperion-EPM-Info/102682103112642
Google+ - https://plus.google.com/106915048672979407731/#106915048672979407731/posts
YouTube - http://www.youtube.com/user/OracleEPMWebcasts
15
16
About EPM System Product
1 Installations
In This Chapter
About EPM System Products..............................................................................17
Assumed Knowledge.......................................................................................18
About Middleware Home, EPM Oracle Home, and EPM Oracle Instance .............................19
About the Shared Services Registry ......................................................................20
Characters Supported for Installation and Configuration...............................................20
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 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 Hyperion Foundation Services
m Foundation Services (includes Oracle Hyperion Shared Services and Oracle Hyperion
Enterprise Performance Management Workspace)
m Optionally, Oracle HTTP Server
m Oracle WebLogic Server
m Oracle Hyperion EPM Architect
m Oracle Hyperion Calculation Manager
m Oracle Smart View for Office
l Oracle Essbase
m Oracle Essbase
m Oracle Essbase Administration Services
m Oracle Essbase Integration Services
m Oracle Hyperion Provider Services
m Oracle Essbase Studio
17
l Oracle Hyperion Reporting and Analysis
m Oracle Hyperion Reporting and Analysis Framework
m Oracle Hyperion Interactive Reporting
m Oracle Hyperion Financial Reporting
m Oracle Hyperion SQR Production Reporting
m Oracle Hyperion Web Analysis
l Oracle's Hyperion Financial Performance Management Applications
m Oracle Hyperion Planning (including Oracle Hyperion Capital Asset Planning, Oracle
Hyperion Workforce Planning, and Oracle Hyperion Public Sector Planning and
Budgeting)
m Oracle Hyperion Financial Management
m Oracle Hyperion Performance Scorecard
m Oracle Hyperion Strategic Finance
m Oracle Hyperion Profitability and Cost Management
m Oracle Hyperion Disclosure Management
m Oracle Hyperion Financial Close Management
l Oracle's Data Management
m Oracle Hyperion Financial Data Quality Management
m Oracle Hyperion Financial Data Quality Management, Enterprise Edition
m Oracle Data Relationship Management
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
l Windows administration skills and or UNIX/Linux administration skills
l Java web application server administration skills.
l 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
l A strong understanding of your organization's database and server environments
l A strong understanding of your organization's network environment and port usage
18
About Middleware Home, EPM Oracle Home, and EPM
Oracle Instance
Middleware Home
A Middleware home consists of the Oracle WebLogic Server home, and, optionally, one or more
Oracle homes, including EPM Oracle home. A Middleware home can reside on a local file system
or on a remote shared disk that is accessible through Network File System (NFS).
The Middleware home location is defined during the first product installation on the computer.
Subsequent installations on the computer use the previously defined location. The default
installation directory is Oracle/Middleware. The Middleware home location is referred to as
MIDDLEWARE_HOME throughout this document.
EPM Oracle Home

An Oracle home contains installed files necessary to host a specific product, and resides within
the directory structure of the Middleware home. The EPM Oracle home contains files for EPM
System products.
Components of EPM System products are installed in the EPM Oracle home directory under
the Middleware home. The default EPM Oracle home location is MIDDLEWARE_HOME/
EPMSystem11R1. In addition, common internal components used by the products are installed
in EPM Oracle home. 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 EPM Oracle home location is defined in the system environment variable called
EPM_ORACLE_HOME. The EPM Oracle home location is referred to as EPM_ORACLE_HOME
throughout this document.
In a distributed environment, the EPM Oracle home directory structure must be the same on
each machine.
EPM Oracle Instance

An EPM Oracle instance contains one or more system components such as Oracle HTTP Server,
Essbase Server, as well as one or more Java web applications in one or more domains. The
directory structure of an Oracle instance is separate from the directory structure of the Oracle
home. It can reside anywhere; it need not be within the Middleware home directory.
The default location for the EPM Oracle instance is MIDDLEWARE_HOME/user_projects/
epmsystem1. The EPM Oracle instance location is referred to as EPM_ORACLE_INSTANCE
throughout this document.
Java web applications are deployed to MIDDLEWARE_HOME/user_projects/domains/
domainName.
Typically, if you are installing all products on a single machine, for the first product you
configure, you create a new EPM Oracle instance. For each product after that, you modify the
existing EPM Oracle instance. If you are installing in a distributed environment, create a new
EPM Oracle instance on each machine.
19
In a UNIX environment, you can deploy to a shared drive by installing to a shared drive and
then configuring each machine to deploy to a different EPM Oracle instance. See Deploying to
a Shared Drive Environment (UNIX) on page 70.
About the Shared Services Registry

The Oracle Hyperion Shared Services Registry is part of the database that you configure for
Foundation Services. Created the first time that you configure EPM System products, the Shared
Services Registry simplifies configuration by storing and reusing the following information for
most EPM System products that you install:
l Initial configuration values such as database settings and deployment settings
l The computer names, ports, servers, and URLs you use to implement multiple, integrated,
EPM System products and components
l Essbase failover content
Configuration changes that 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 Oracle Hyperion Shared Services Console. See the Oracle Enterprise
Performance Management System Lifecycle Management Guide.
Characters Supported for Installation and

Configuration
The following characters are supported during installation and configuration with Oracle
Hyperion Enterprise Performance Management System Installer and Oracle Hyperion
Enterprise Performance Management System Configurator.
Table 1 Characters Supported for Installation and Configuration
Fields Supported Characters Blocked Characters
PATH Alphanumeric, dash (-), underscores (_), periods ( . ), and All others
tildes (~). Tildes are supported only on Microsoft
Windows.
Host name Alphanumeric, dash (-), and dot(.). All others

EPM System supports IPv6 addresses. However, during
installation and configuration, you must enter the host
name, not the IPv6 address.
User name Alphanumeric characters including non-English (extended +*/#[]{}();:,@!

and double-byte) characters, except for the blocked
characters
20
Fields Supported Characters Blocked Characters
Clusters, database Alphanumeric characters including non-English (extended +.-*\/#[]{}();:,@!

names, and other and double-byte) characters, except for the blocked
general fields such as characters
DSN names
MIDDLEWARE_ For MIDDLEWARE_HOME: Alphanumeric characters, "_", Do not use any of the following symbols or symbol
HOME, EPM_ "-" and "~" on Windows. combinations in the directory that you specify for
ORACLE_HOME and EPM_ORACLE_HOME or MIDDLEWARE_HOME
For EPM_ORACLE_INSTANCE: Alphanumeric characters,
EPM_ORACLE_ during installation or EPM_ORACLE_INSTANCE
"_", "-" The first character in every folder in the EPM_
INSTANCE during configuration:
ORACLE_INSTANCE path must be a-z, A-Z, or 0-9.
/t
\t
\b
21
22
EPM System Architecture
2
In This Chapter
About EPM System Architecture ..........................................................................23
Disclosure Management Components ...................................................................24
Essbase Components......................................................................................25
FDM Components ..........................................................................................26
FDMEE Components .......................................................................................26
Financial Close Management Components..............................................................27
Financial Management Components.....................................................................28
Performance Management Architect Components......................................................29
Planning Components .....................................................................................30
Profitability and Cost Management Components .......................................................31
Reporting and Analysis Components.....................................................................32
Strategic Finance Components ...........................................................................32
About EPM System Architecture

EPM System is a multi-tier application environment that mainly utilizes thin-client architecture
for end-user access, requiring only a supported browser on the client machine. Network traffic
between the client and middle-tier server(s) generally does not exceed more than normal Web
traffic.
A middle-tier application server is required. WebLogic Server is provided with a default
installation. You can also use another supported application server. See the Oracle Enterprise
Performance Management System Certification Matrix (http://www.oracle.com/technetwork/
middleware/ias/downloads/fusion-certification-100350.html) for a list of supported application
servers.
The data tier is comprised of two components that store data differently. In Essbase
environments, the data is stored and calculated in the database on the server file system. In
Financial Management environments, the application framework, metadata, and textual data
are stored in a relational repository.
The following sections contain diagrams that illustrate the component architecture for EPM
System products. To obtain information about the communication between EPM System
components, see Oracle Enterprise Performance Management System Communication Flows
in the EPM System 11.1.2.3 Documentation Library (Deployment and Installation tab) at http://
www.oracle.com/technology/documentation/epm.html.
23
Note: The Oracle Enterprise Performance Management System Standard Deployment Guide
presents Oracles best-practice approach for deploying EPM System products. This
approach is based on creating a base deployment of the products and then scaling out the
services to handle the needed capacity. This document is available in the EPM System
11.1.2.3 Documentation Library (Deployment and Installation tab) at http://
www.oracle.com/technology/documentation/epm.html.
For information about using EPM System on the Oracle Exalytics In-Memory Machine,
see the Oracle Enterprise Performance Management System (EPM System) / Business
Intelligence White Papers Library (http://www.oracle.com/technetwork/middleware/bi-
foundation/resource-library-090986.html).
Tip: For optimum viewing of the component architecture diagrams in PDF format, try
increasing the view magnification to 120%.
Disclosure Management Components
24
Essbase Components
25
FDM Components
FDMEE Components
26
Financial Close Management Components
Stand-Alone Financial Close Management Deployment

Requirements for Test and Production
A stand-alone version of Financial Close Management can be deployed independently of other
EPM System products in a two-server deployment as specified below. The following specification
supports 500 users (175 active).
Table 2 Financial Close Management Deployment Specifications
Machine Products Processor/

Memory
Server 1 l WebLogic Admin Server 4 Core 2 CPU

16GB
l Foundation Services Java Web application (EPM Workspace and Shared Services)
l Oracle SOA Suite
l Oracle HTTP Server
Server 2 l Financial Close Management Java Web application (Close Manager and Account Reconciliation 4 Core 2 CPU
Manager) 16GB
l FDMEE Java Web application
27
Financial Management Components
28
Performance Management Architect Components
29
Planning Components
30
Profitability and Cost Management Components
31
Reporting and Analysis Components
Strategic Finance Components
32
Stand-AloneStrategic Finance Deployment Requirements for
Test and Production
A stand-alone version of Strategic Finance can be deployed independently of other EPM System
products in a one-server deployment as specified below. The following specification supports
50 active users.
Table 3 Strategic Finance Deployment Specifications
Machine Products Processor/Memory
Server 1 l Shared Services Java Web application 4 Core 2 CPU 16GB on Windows 2008 R2
l Strategic Finance Web application
l Strategic Finance Server
33
34
Preparing Your Environment
3
In This Chapter
Preparing Servers ..........................................................................................35
Preparing User Accounts ..................................................................................37
Disk Space and RAM ......................................................................................38
Preparing a Database .....................................................................................41
Preparing Java Web Application Servers.................................................................51
Preparing Web Servers ....................................................................................52
Preparing Web Browsers ..................................................................................54
Support Matrix for High Availability and Load Balancing...............................................56
Preparing Servers
Applying Windows Updates

For each server in the deployment, apply Windows updates and reboot before installing and
configuring.
Resolving Port Conflicts

For information about default port numbers for EPM System products, including where the
port can be configured, see Appendix A, Ports..
Disabling User Access Control

In Windows 2008 environments, disable User Access Control (UAC) on each server in the
deployment. This can be done through User Accounts in the Control Panel by clicking on Change
User Account Control Settings, and then dragging the slider to Never notify.
UAC must remain disabled in order for EPM System server components to function properly.
UAC can be enabled on end-user client desktops.
35
Setting the DCOM Default Authentication Level (Windows
2008)
For machines hosting products that require .NET Framework 4.0, the DCOM default
authentication level should be set to Connect (this is the default value).
To set the authentication level for DCOM to Connect:

1 In the Control Panel, select Administrative Tools and then Component Services.
2 Navigate to Component Services, then Computers, and then My Computer.
3 Right-click My Computer and select Properties.
4 Select the Default Properties tab.
5 For Default Authentication Level, select Connect.
Note: For earlier Windows versions, set the value to None.
Synchronizing Clocks
The clock on each server must be synchronized to within one second difference. To accomplish
this, point each server to the same network time server. Refer to your operating system
documentation for more information.
Resolving Host Names

The canonical host name of each server must be the same when accessed from within the server
and from other servers in the deployment. You may want to create a local hosts file on each
server to resolve host name issues.
EPM System uses Javas canonical host name resolution for resolving host names. To validate
host names as resolved by Java, EPM System provides a utility (epmsys_hostname.bat|sh).
An archive of the utility (epmsys_hostname.zip) is available in EPM_ORACLE_HOME/common/
config/11.1.2.0. Run the utility after installation and before configuration.
Disabling Anti-virus Software

Antivirus software can cause performance issues with EPM System products if, each time you
access any resource on the server, the antivirus software tries to open and scan the object. To
prevent these issues, exclude the EPM Oracle home directory from automatic antivirus scans
and scan this directory only at scheduled times.
36
Shared File System
If you are configuring for high availability, you must set up a shared file system using UNC
syntax that is accessible from all the servers in the deployment for the following:
l Oracle Hyperion Enterprise Performance Management System Lifecycle Management
artifacts
l Reporting and Analysis Repository data
l Essbase Server (UNIX) application location (ARBORPATH)
l Performance Scorecard attachment files
Optionally, you can also use the shared file system for the following:
l Installation files downloaded from Oracle Software Delivery Cloud
l Oracle HTTP Server configuration files to simplify configuration in a distributed
environment
l Strategic Finance data
l FDMEE application data
l Essbase Studio sample and customer data source text files
Preparing User Accounts

Windows:
l Do not use the Administrator user to install and configure. Run EPM System Installer and
EPM System Configurator as a user with administrator rights. Install and configure as an
administrator and as the same user for all EPM System products.
l Assign local policies if required by your product. For Windows, the user ID typically requires
Act as part of the OS, Bypass Traverse Checking, Log on as a batch job, and Log-on as a
service.
l Before installing in a Windows 2008 environment, ensure that you disable User Account
Control (UAC). See Disabling User Access Control on page 35.
l When you upgrade, apply a maintenance release, or patch this server, use the same user
account that was used to install and configure the earlier release.
UNIX
l Prepare a user account (not the root user). Install and configure as the same user for all EPM
System products. On UNIX machines, for all Oracle products, the user that is installing must
be part of the same group; the group must have write permission to the central inventory
(oraInventory).
l If you have installed any other Oracle products, the user who will be installing EPM System
products must be in 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,
37
follow this requirement even if you used multiple users to install components in previous
releases.
The password for the account used to install and configure must conform to the following
guidelines:
l Contain at least one uppercase letter
l Contain at least one numeral
l Be at least eight characters long
l Contain no special characters
Disk Space and RAM

This section describes client and server disk space and RAM requirements for EPM System
products.
Client Disk Space and RAM

Disk space and RAM requirements are approximate. The installation program checks for twice
the required disk space, based on your product installation choices.
The recommended RAM requirement for all clients is 1 GB.
Note: Web browser clients have no disk space requirements beyond those of the Web browser.
Product Family Component Disk Space (Minimum)1 Notes
EPM System Installer EPM System Installer and all EPM 16 GB After installation, the installation
System product assemblies files and assemblies can be
removed.
Foundation Services Common client components 400 MB
Smart View for Office 100 MB
Performance Management 20 MB File generator and batch client

Architect components only
Essbase Essbase Runtime Client 150 MB
Administration Services Console 300 MB
Integration Services Console 90 MB
Essbase Studio Console 80 MB
Reporting and Analysis Oracle Hyperion Financial Reporting 400 MB

Studio
38
Product Family Component Disk Space (Minimum)1 Notes
Oracle Hyperion Interactive 700 MB

Reporting Studio
Oracle Hyperion Dashboard 190 MB

Development Services
Oracle Hyperion SQR Production 90 MB

Reporting Studio
Oracle Hyperion SQR Production 30 MB

Reporting Activator
Production Reporting Remote 10 MB
Production Reporting Viewer 40 MB
Oracle Hyperion Web Analysis 40 MB

Studio
Financial Performance Offline Planning 280 MB

Management Applications
Financial Management Client 100 MB
Strategic Finance Client 700 MB
Disclosure Management 300 MB
Oracle's Data Management FDM Workbench 200 MB
1Disk space does not include the common client components installed on the machine with Foundation Services.
Server Disk Space and RAM

Disk space and RAM requirements are approximate and do not include additional possible
requirements on the machine. The installation program checks for twice the required disk space,
based on your product installation choices. Disk space estimates include documentation help
files (if applicable) and EPM System components.
Component Disk Space (Minimum) RAM (Minimum)
WebLogic Server 1.4 GB 500 MB

(includes WebLogic, JDK, utils,
JRockit, and Modules)
Oracle HTTP Server (optional 1.2 GB 1 GB

component)
Common Oracle libraries 900 MB NA
Shared Services 800 MB1 1.5 GB
39
Performance Management 125 MB 1 GB for Dimension Server

Architect
512 MB each for Web Tier and Data Synchronizer
Calculation Manager 45 MB 256 MB
Essbase Server 2 GB 1 GB
Application Programming 40 MB 256 MB

Interface
Administration Services 1 GB2 32 MB multiplied by the number of concurrent

Administration Services users
For example, 32 MB * 10 users = 320 MB
Integration Services 340 MB 256 MB
Provider Services 680 MB 340 MB
Essbase Studio Server 120 MB 256 MB
Reporting and Analysis 2 GB 1 GB

Framework
For services: 400 MB For services: 1 GB
For importing files: 2 GB
Financial Reporting 400 MB 1 GB
Interactive Reporting 1 GB 1 GB
Production Reporting 400 MB 256 MB
Web Analysis 2 GB 1 GB
Financial Management Server 64 GB (10 GB available) 4 GB
Database Server for Financial 24 GB 4 GB

Management
Financial Close Management 3 8 GB 4GB
Planning 8 GB (10 GB available) 2 GB
Performance Scorecard 4 GB recommended 1 GB4
Strategic Finance Server 700 MB5 2 GB
Profitability and Cost 8 GB 2 GB

Management
Disclosure Management 8 GB 4 GB
FDM Database Server l Dependent on size of the FDM application 1 GB per 75 concurrent users (2 GB minimum)
l Multiple HDDs to spread processing
FDM folder structure Dependent on size of the FDM application NA
40
FDM Application Server 400 MB 2 GB per 75 concurrent users
FDM Web Server 400 MB 2 GB
FDMEE 300 MB 2 GB
Data Relationship Management 15 GB 2 GB

Database Server
Data Relationship Management 500 MB 2 GB

Application Server
1This number is for the base Shared Services installation. If using Lifecycle Management functionality, Oracle recommends that you significantly
increase disk space because application artifacts are exported and stored in the Shared Services file system.
2Allow extra disk space for data files and outline files that are copied to Administration Services during data loading and outline editing,
respectively.
3Requirements for Oracle SOA Suite are not included.
41 GB includes Performance Scorecard and Alerter servers.
5Sufficient storage should be included to contain the entities, their backup archives, administrative and transaction files, and user background
task logs, such as consolidation reports.
Note: For data storage and binary installation, Essbase supports the use of a disk array device.
Preparing a Database
Before you install and configure most EPM System products, create a database using a supported
RDBMS (Oracle Database, Microsoft SQL Server, or IBM DB2).
EPM System supports 32-bit as well as 64-bit versions of all supported databases; however, the
version of the database should match the operating system. For example, a 64-bit database
version can be used only on a 64-bit operating system.
In general, the database should be in the same data center as the EPM System deployment. To
prevent timeout issues when configuring with EPM System Configurator, you cannot locate a
database in a remote location where there is latency.
For simplicity and ease of deployment, you can use one database repository for all products (with
the exceptions noted below). In some cases you might want to configure separate databases for
products. Consider performance, rollback procedures for a single application or product, and
disaster recovery plans.
The following products and product components require unique databases:
l Performance Management Architect interface data source
l Extended Analytics for Financial Management and Extended Analytics for Strategic Finance
l Planning Each Planning application should have its own repository.
l Performance Scorecard
l Data Relationship Management. See the Oracle Hyperion Data Relationship Management
Installation Guide.
41
Upgrade Note!
If you are upgrading from a previous release of EPM System products, see Chapter 11,
Upgrading EPM System Products for information about replicating or reusing databases.
Using an Oracle Database

This section includes information about Oracle database installation, database creation, required
roles and privileges, sizing guidelines, and configuration.
Note: EPM System Installer installs the Oracle Database client automatically if it is required on
a machine (Windows only). To use an existing Oracle Database client, see Using an
Existing Oracle Database Client on page 45.
Oracle Database Creation Considerations

The database must be created using Unicode Transformation Format UTF-8 encoding
(character set). Oracle supports the following character sets with UTF-8 encoding:
l AL32UTF8 (UTF-8 encoding for ASCII platforms)
l UTF8 (backward-compatible encoding for Oracle)
l UTFE (UTF-8 encoding for EBCDIC platforms)
Oracle Database Privileges

The following privileges must be granted to the owners of the database schemas:
l CREATE ANY SYNONYM
l CREATE CLUSTER
l CREATE INDEXTYPE
l CREATE PROCEDURE
l CREATE SEQUENCE
l CREATE SESSION
l CREATE TABLE
l CREATE TRIGGER
l CREATE TYPE
l CREATE VIEW
l DROP ANY SYNONYM
l UNLIMITED TABLESPACE
42
Oracle Database Sizing Guidelines
Oracle recommends that you set tablespaces with Auto Extend ON.
The following table describes the Oracle Database sizing guidelines.
Product Sizing Guideline
Shared Services & Start with 100 MB, and add more as the number of migrations with Lifecycle Management and the number of audit
EPM Workspace records increases.
Performance Oracle recommends starting with at least 250MB.

Management
Architect
Administration The amount of space needed depends on the metadata created; Oracle recommends starting with at least 32
Services MB.
Essbase Studio The amount of space needed depends on the metadata created; Oracle recommends starting with at least 32
MB.
Reporting and The amount of space needed depends on the aggregate size of the objects that you plan to store in the repository.
Analysis Oracle recommends starting with at least 250 MB, which provides space to expand the Reporting and Analysis
repository without having to increase the data file or tablespace. A shared pool size of 60 MB is used during
configuration with EPM System Configurator.
Planning and l 100 MB for applications with 5,000 or fewer total members
Calculation Manager l 200 MB for applications with 15,000 or fewer total members
Note: You can adjust the size of the system table database to match the size of the application.
Financial l 100 MB for applications with 5,000 or fewer total members

Management and 200 MB for applications with 15,000 or fewer total members
Calculation Manager
l
Performance 500 MB
Scorecard
Profitability and Cost Oracle recommends starting with at least 250 MB.
Management
FDM See the Oracle Hyperion Financial Data Quality Management Adapter for Financial Management DBA Guide.
Oracle Database Configuration Considerations
Tablespace Considerations
The following table describes the Oracle Database tablespace considerations.
43
Product Tablespace Considerations
GeneralAll l Consider a global view of tablespaces and allocate one or more tablespaces in order to spread out tables created
products by EPM System products.
l Tablespaces can be shared with other applications.
l Create a separate tablespace for indexes to improve performance. This action requires CREATE TABLESPACE system
privileges.
l Ensure that the SEGMENT SPACE MANAGEMENT parameter is set to AUTO when you create tablespace, to improve
performance.
Reporting and Dedicate a tablespace to Reporting and Analysis. Determine the tablespaces to be used as the default tablespace
Analysis and the temporary tablespace for this user. Do not use the SYSTEM tablespace.
Financial Set up a temporary tablespace greater than 1GB.

Management
Data l Set the initial tablespace size to 1 GB

Relationship Extents to 500 MB
Management
l
l Turn Auto Extend ON

See the Oracle Hyperion Data Relationship Management Installation Guide
Other Parameters
The following table describes other Oracle Database parameters.
Product Other Parameters
General/AllProducts Set ALTER SYSTEM SET as follows:

ALTER SYSTEM SET processes=1000 SCOPE=SPFILE;
Financial Management Set Oracle OPEN_CURSORS to 5000.
Performance Scorecard Set Oracle OPEN_CURSORS to 1500 or greater.
Operating System Configuration for Oracle Database

For Reporting and Analysis, set the necessary environment variables:
l (UNIX/Linux)
m ORACLE_HOME
m PATH
m (Solaris/Linux) LD_LIBRARY_PATH
m (AIX) LIBPATH
m (HP) SHLIB_PATH
44
Enabling Statement Caching for Financial Management
If you use Oracle Database Client 10.2.x or 11.1.x for Financial Management, you must set the
StmtCacheSize registry setting for Oracle OLE DB to 10 on all Financial Management
application servers. This is due to a memory issue in Oracle Provider for OLE DB.
The registry setting path is:
Hkey_Local_Machine\Software\Oracle\Key_Homename\Oledb
Note that the 11.2.x Oracle Database Client should not be changed.
To resolve the high memory usage:

1 Enable Statement Caching.
The configured value must not be zero. The recommended value is between and 1 and 10.
2 Edit the following registry value:
Hkey_Local_Machine\Software\Oracle\Key_Homename\Oledb Value Name:
StmtCacheSize Value (decimal): 1
where Key_Homename refers to the appropriate Oracle Home

3 Stop and restart the HFM application processes.
In addition, if you are using System 11 on a 64-bit operating system with a 10g database, the
Oracle OLE provider on all Financial Management servers must be at least 10.2.0.4.21+. If you
are using 32-bit with 10g, the OLE provider must be at least as high a version as your database
server. If you are running 32-bit or 64-bit and using 11.1.0.6 or 11.1.0.7 OLE Provider, you must
upgrade to Oracle Database Client 11.1.0.7.33+.
Using an Existing Oracle Database Client

For a new installation, if you want to use your existing Oracle Database Client instead of the one
installed with EPM System, during EPM System installation clear the selection from Oracle
Database Client 32-bit and Oracle Database Client 64-bit under Foundation Services. Then, after
installing and configuring Oracle EPM System, perform the following steps:
1. On the machine hosting Foundation Services, update the TNS_ADMIN environment variable
to point to the location of the existing Oracle Database Client's tnsnames.ora file location.
2. Move TNS entries from EPM_ORACLE_INSTANCE/user_projects/config/dbclient/
tnsnames.ora (which is populated during database configuration) to the existing
tnsnames.ora file. Copy the entire file contents and append to the existing contents of the
tnsnames.ora file.
Replacing the EPM System-Installed Oracle Database Client with A Different Oracle
Database Client
If you want to use your existing Oracle Database Client instead of the one installed with EPM
System, and you already installed the Oracle Database Client during installation of EPM System,
45
then, after installing and configuring Oracle EPM System, perform the following steps. This
procedure applies to new installations or maintenance installations.
1. On the machine hosting Foundation Services, update the TNS_ADMIN environment variable
to point to the location of the existing Oracle Database Client's tnsnames.ora file location.
2. Move TNS entries from EPM_ORACLE_INSTANCE/user_projects/config/dbclient/
tnsnames.ora to the existing tnsnames.ora file. Copy the entire file contents and append
to the existing contents of your tnsnames.ora file.
3. Remove the following EPM System embedded Oracle Database Client BIN paths from the
PATH environment variable in order to avoid conflicts:
<MIDDLEWARE_HOME>\dbclient32\BIN;
<MIDDLEWARE_HOME>\dbclient64\BIN;
Using a Microsoft SQL Server Database

This section includes information about SQL Server database creation, required roles and
privileges, and sizing guidelines.
Microsoft SQL Server Database Creation Requirements

When creating a Microsoft SQL Server database for use as a repository, ensure that you set these
options:
l Set READ_COMMITTED_SNAPSHOT = ON
l Set ALLOW_SNAPSHOT_ISOLATION = ON
l Select the SQL Server and Windows authentication option when you set the security
properties for the database.
l All products support Latin Collation for the SQL Server database. Create a database that is
case insensitive and use this statement: SQL_Latin1_General_CP1_CI_AS.
Microsoft SQL Server Roles and Privileges

Database users must be assigned ownership of the database, which provides DB_OWNER privileges,
and BULK_INSERT.
Note: For FDM, Windows accounts that run MSSQL Server Windows service must have read
access to the FDM Data folder.
Microsoft SQL Server Sizing Guidelines

The following table describes the Microsoft SQL Server sizing guidelines.
46
Shared Services Start with 100 MB, and add more as the number of migrations with Lifecycle Management and the number of
audit records increases.
EPM Workspace The space needed depends on the aggregate size of the objects that you plan to store in the repository. Oracle
recommends starting with at least 250 MB, which provides space to expand the EPM Workspace repository without
having to increase the data file or tablespace. A shared pool size of 60 MB is used during configuration with EPM
System Configurator.
Performance Oracle recommends starting with at least 250 MB.

Management
Architect
Administration The space needed depends on the metadata created; Oracle recommends starting with at least 32 MB.
Services
Essbase Studio The space needed depends on the metadata created; Oracle recommends starting with at least 32 MB.

Calculation Manager
l
Performance 500 MB
Scorecard
Profitability and Cost Oracle recommends starting with at least 250 MB.
Management
Data Relationship l Set the initial file size to 1 GB

Management l Turn on Auto Growth and set to 10%
Using an IBM DB2 Database

This section includes information about IBM DB2 database installation, database creation,
required roles and privileges, sizing guidelines, and configuration.
IBM DB2 Installation Information

During IBM DB2 installation, consider:
l When installing IBM DB2, clear the OLAP Starter Kit option.
l For Performance Management Architect, ensure that your DB2 database is installed on a
different computer, and not on the Dimension Server machine where the DB2 9 Runtime
Client and DB2 .NET Data Provider must be installed.
47
Note: If DB2 9 Runtime Client is installed on the Performance Management Architect
computer, verify that an entry exists in the Global Assembly Cache.
l If you use an IBM DB2 database for Financial Management, DB2 Runtime Client and
DB2 .NET Data Provider must be installed on the same machine as the Financial
Management Application Server.
l For Reporting and Analysis, ensure that the IBM DB2 Client Application Enabler is installed
on the computers on which you install services. For Core Services and Job Factory Service,
if you use an IBM DB2 RDBMS, and Reporting and Analysis Services are on separate
machines, use the Client Application Enabler to create a client connection to the Reporting
and Analysis database.
IBM DB2 Database Creation Considerations

For the best compatibility with non-ASCII character sets, an IBM DB2 database must be created
using Unicode Transformation Format UTF-8 encoding (character set). Use of UTF-8 is
required if you need multilingual support (multicharacter set support).
Use the Client Configuration Assistant to set up a database alias that enables the EPM System
product to connect to the database. Be sure to select Register this Database for ODBC and As
a System Data Source.
IBM DB2 Roles and Privileges

Database users must be assigned the following privileges:
l CREATETAB
l BINDADD
l CONNECT
IBM DB2 Sizing Guidelines

The following table describes the IBM DB2 sizing guidelines.
Shared Services Start with 100 MB, and add more as the number of migrations with Lifecycle Management and the number of
audit records increases.
EPM Workspace The space needed depends on the aggregate size of the objects that you plan to store in the repository. Oracle
recommends starting with at least 250 MB, which provides space to expand the EPM Workspace repository without
having to increase the data file or tablespace. A shared pool size of 60 MB is used during configuration with EPM
Performance Oracle recommends starting with at least 250 MB.

Management
Architect
Administration The space needed depends on the metadata created; Oracle recommends starting with at least 32 MB.
Services
48
Essbase Studio The space needed depends on the metadata created; Oracle recommends starting with at least 32 MB.

Calculation Manager
l
Performance 500 MB
Scorecard
IBM DB2 Database Configuration Considerations

The following table describes IBM DB2 database configuration considerations.
GeneralAll Tablespace requirements:

products
Specify automatic storage for user and temporary tablespaces, as shown in the following example:
CREATE TABLESPACE <name> MANAGED BY AUTOMATIC STORAGE
CREATE TEMPORARY TABLESPACE TEMPTS
CREATE USER TEMPORARY TABLESPACE USRTMP MANAGED BY AUTOMATIC STORAGE
CREATE LONG TABLESPACE LONGTS
Change settings as follows:

UPDATE DB CFG FOR <name> USING AUTO_MAINT ON;
UPDATE DB CFG FOR <name> USING AUTO_TBL_MAINT ON;
UPDATE DB CFG FOR <name> USING AUTO_RUNSTATS ON;
Shared l Increase bufferpool to 32768.

Services and
Essbase
Studio
Performance l Increase the heap size:

Management
LOGFILSZ to 4096
Architect
m
m APPLHEAPSZ to 8192
m STMTHEAP to 10240
l Ensure that the user has privileges to create tablespaces and buffer pools.
l Ensure that the user has been granted the right to use the temporary tablespace.
49
Planning Before you configure Planning, you must configure the database with a large enough tablespace (having a page size of
at least 32 K) in order to support the Planning tables.
The following sample SQL script creates the necessary buffer pool and tablespace. Change the names and the disk
location to reflect your needs. By default, the tablespace is named HSPSPACE8_1 and is created in the C:\DB2DATA
\HSPSPACE8_1 directory. The other settings are also defaults; the administrator should adjust the settings as
appropriate for the environment.
Example:
CREATE BUFFERPOOL hsppool8_1 SIZE 250 PAGESIZE 32 K;
CREATE REGULAR TABLESPACE hspspace8_1 PAGESIZE 32 K
MANAGED BY SYSTEM USING ('c:\db2data\hspspace8_1')
EXTENTSIZE 32 OVERHEAD 24.1 PREFETCHSIZE 8
TRANSFERRATE 0.9 BUFFERPOOL HSPPOOL8_1;
The database administrator must ensure that the user who logs on to the Planning relational database has rights to use
the new tablespace.
Performance ScorecardSpecific IBM DB2 Database Configuration Requirements

You must complete the following procedure before you configure Performance Scorecard.
To prepare the IBM DB2 server:

1 Increase the database log size to 6500.
2 Modify this script with information specific to your database:
SET HPSDB=<hpsdatabase>
SET ADMIN=<adminusername>
SET ADMINPWD=<adminpassword>
SET TBSFILE=<table space file location>
SET TMPFILE=<temp file location>
DB2 CONNECT TO %HPSDB% USER %ADMIN% USING %ADMINPWD%
DB2 UPDATE DATABASE CONFIGURATION FOR %HPSDB% USING APPLHEAPSZ 512
DB2 CREATE BUFFERPOOL HPS_BP SIZE 250 PAGESIZE 32 K
DB2 TERMINATE
DB2STOP
DB2START
DB2 CONNECT TO %HPSDB% USER %ADMIN% USING %ADMINPWD%
DB2 CREATE REGULAR TABLESPACE HPS_SPACE1 PAGESIZE 32 K MANAGED BY SYSTEM USING
('%TBSFILE%') EXTENTSIZE 32 OVERHEAD 24.1 PREFETCHSIZE 32 TRANSFERRATE 0.9 BUFFERPOOL
HPS_BP
DB2 COMMENT ON TABLESPACE HPS_SPACE1 IS 'HPS Table Space'
DB2 GRANT USE OF TABLESPACE HPS_SPACE1 TO PUBLIC
DB2 CREATE SYSTEM TEMPORARY TABLESPACE HPS_TEMP PAGESIZE 32 K MANAGED BY SYSTEM USING
('%TMPFILE%') EXTENTSIZE 32 OVERHEAD 24.1 PREFETCHSIZE 32 TRANSFERRATE 0.9 BUFFERPOOL
HPS_BP DB2 COMMENT ON TABLESPACE HPS_TEMP IS 'HPS Temporary Table Space'
DB2 TERMINATE
DB2STOP
DB2
50
3 Save the file as name.bat.
4 From the Command Center, execute the script.
5 Windows 2003 users, perform these steps:
a. Select Control Panel, then Computer Management, and then Users and Groups.
b. On the User Accounts box, click Advanced.
c. Select DB2Admin, right-click and select Properties.
d. On the Properties box, select Member Of.
e. Select Users, click Remove, and click Save.
Preparing Java Web Application Servers

Many EPM System products require a Java web application server. To identify the products that
require a Java web application server, see Chapter 2, EPM System Architecture.
WebLogic Server
l Oracle provides a limited-use license of WebLogic Server for use with EPM System products.
Typically, EPM System Installer installs WebLogic Server for you.
l However, if you have an existing WebLogic Server installation and want to use it instead of
the WebLogic Server installed by EPM System Installer, note the Middleware home location
for the WebLogic Server installation. During installation, you must install EPM System
products to this same Middleware home. If EPM System Installer detects an existing
WebLogic Server installation in the installation location, it does not install WebLogic Server.
For additional information about using WebLogic Server in a distributed environment, see
Installing EPM System Products in a Distributed Environment on page 81.
IBM WebSphere
l On UNIX platforms, the user account that installs and configures the EPM System product
being deployed must have permission to create a WebSphere profile. Refer to the IBM
InfoCenter for detailed instructions on granting permission to create a WebSphere profile
as a non-root user.
l Install the plug-ins from the IBM WebSphere 7.0.0.23 supplemental components CD. They
are required for Reporting and Analysis.
l When you are installing WebSphere, do not install the Web Services Gateway component
of the WebSphere Application Server Network Deployment. The Web Services Gateway
component expects messages in SOAP 1.1 format; however, EPM System generates messages
in SOAP 1.0 format.
51
Preparing Web Servers
Oracle HTTP Server

You can choose to install Oracle HTTP Server during the installation of Foundation Services,
using the Oracle HTTP Server silent installer. You can also configure Oracle HTTP Server to a
shared drive location to simplify configuration in a distributed environment.
Caution! Before you install EPM System products, ensure you meet the installation
prerequisites for Oracle HTTP Server and review the Oracle HTTP Server installation
documentation and Release Notes for details. For additional information, see Web
Server Installation Prerequisites on page 78.
Microsoft Internet Information Services (IIS)

The following products require IIS to be installed with ASP.NET support enabled before
configuration of the EPM System product:
l Performance Management Architect Service (Dimension Server)
l Financial Management
l Strategic Finance
l FDM
l Data Relationship Management
Notes about IIS:

l If .NET is not detected, EPM System Installer will install it.
l On Windows 2008, the required server roles are provided by EPM System Configurator.
l If IIS is chosen as the Web server during configuration, you must allow all unknown ISAPI
extensions through the Internet Information Services Manager.
l You must select Enable Parent Paths in IIS configuration properties.
l If you are using Smart View and Financial Management in a Windows 2003 Server 64-bit
environment, you must disable IIS recycling based on memory consumption.
l On Windows 2008, if you are configuring products that require IIS, EPM System
Configurator automatically installs Windows server roles for IIS if they are not already
installed. On Windows Server 2003, you are prompted for the installation CD or the path
to Windows Server 2003 files to install the required IIS files.
Verifying the IIS Installation

To verify the IIS installation, ensure that the IIS services are running:
l IIS Admin Service
52
l World Wide Web Publishing Service
If you do not see the services for IIS, ensure that IIS is installed.
Enabling Existing .NET 4.0 Framework (Windows 2003)

Performance Management Architect requires .NET 4.0 Framework on the machine where you
install the Dimension server. If .NET 4.0 Framework is not installed on your machine, EPM
System Installer automatically installs it for you.
If you are using Windows 2003 and .NET 4.0 is installed, you must register and enable .NET 4.0
with IIS.
To enable .NET 4.0 on Windows 2003 machines:

1 Open IIS Manager.
2 In the left pane, select Web Service Extensions.
3 If ASP.NET 4.0 is listed in the right pane, enable it by ensuring that the Status column is set to
Allowed.
4 If ASP.NET 4.0 is not listed in the right pane and .NET 4.0 is installed, register .NET 4.0 with IIS:
a. From the command prompt, go to: C:\Windows\Microsoft.NET\Framework
\v4.0.30319
b. Enter aspnet_regiis.exe iru.
c. Repeat steps 13.
32Bit/64Bit Microsoft IIS 6.0/7.0 Support

Microsoft IIS 6.0 can be configured to support 32-bit application runtimes or 64-bit application
runtimes on 64-bit operating systems. Microsoft IIS 6.0 cannot be configured to support both
simultaneously. Therefore, in general, when installing and configuring EPM System products
with Microsoft IIS 6.0, install 32-bit runtimes and 64-bit runtimes for EPM System Web tier
components on different computers.
Specifically, Strategic Finance (32-bit) cannot be deployed on the same computer where
Financial Management (64-bit) is deployed. On 32-bit platforms, all EPM System products can
coexist.
Note: For IIS 7 (the default on Windows 2008 systems), 32-bit and 64-bit components can
coexist. However, for Strategic Finance, you need to install IIS 6.0 compatibility mode
when running IIS 7.0.
Using IIS in a Localized Environment

In a localized environment, the following conditions are required to successfully configure EPM
System on IIS:
53
For IIS 7:
l The IIS site name should not be localized; it should be Default Web Site in English on any
machine, localized or not
l IIS should have an application pool called DefaultAppPool
l The DefaultAppPool must have ID = 1
l The physical path for the default web site should be: %SystemDrive%\inetpub\wwwroot
For IIS 6:
l The IIS site name should not be localized; it should be Default Web Site in English on any
machine, localized or not
l IIS should have an application pool called DefaultAppPool
l The DefaultAppPool must have ID = 1
l Verify this ID in C:\WINDOWS\system32\inetsrv\MetaBase.xml:
<IIsWebServer Location ="/LM/W3SVC/1"
AppPoolId="DefaultAppPool"
DefaultDoc="Default.htm,Default.asp,index.htm,iisstart.htm"
ServerBindings=":80:"
ServerComment="Default Web Site"
ServerSize="1"
>
</IIsWebServer>
Or, if you know the ID of the Default Web Site and it is not 1, you can use the following
scripts to assign the ID = 1. For example, if the ID is 1111, the following scripts can be used
to assign ID = 1:
CSCRIPT %SYSTEMDRIVE%\Inetpub\AdminScripts\adsutil.vbs STOP_SERVER W3SVC/1111
CSCRIPT %SYSTEMDRIVE%\Inetpub\AdminScripts\adsutil.vbs MOVE W3SVC/1111
W3SVC/1
CSCRIPT %SYSTEMDRIVE%\Inetpub\AdminScripts\adsutil.vbs START_SERVER W3SVC/1
l The IIS Server physical path should be: c:\inetpub\wwwroot (where c: is the system
drive, or use the drive where Windows 2003 is installed)
Preparing Web Browsers

This section contains required browser settings and information about enabling ActiveX for
Reporting and Analysis.
Browser Settings
Ensure that browser preferences and options are enabled:
l For Internet Explorer and Firefox:
m Enable JavaScript.
54
m Enable cookies. The preferred setting is to allow cookies to be stored on your computer.
The minimum requirement is to allow per-session level cookies.
m Allow pop-up windows.
l For Firefox version 17.x, install the Remote XUL Manager:
1. Install the Remote XUL Manager add-on (https://addons.mozilla.org/en-us/firefox/
addon/remote-xul-manager/).
2. In Firefox, select Tools, then Web Developer, and then Remote XUL Manager.
3. Add your company's domain name (for example, mycompany.com) to the list, and click
Add.
4. Restart Firefox.
l For Internet Explorer 7:
1. Select Tools, then Internet Options, and click the Security tab.
2. Click Custom level, and then find the Miscellaneous section.
3. Ensure that the setting for Include local directory path when uploading files to a server
is set to Enable.
l For Internet Explorer 9:
1. Select Tools and then Compatibility View Settings.
2. Make sure that the EPM Workspace URL is not enabled for Compatibility View. Also,
uncheck all available options at the bottom of the pop-up window.
l For Internet Explorer (Reporting and Analysis only), enable ActiveX. See Enabling ActiveX
(Reporting and Analysis) on page 56.
l Add the URL for EPM Workspace to the trusted zone:
1. Select Tools, then Internet Options, and click the Security tab.
2. Select Trusted Sites, and then click Sites.
3. Add the EPM Workspace URL to the list.
l For Internet Explorer, customize security settings:
1. In Internet Explorer, select Tools, then Internet Options, then the Security tab.
2. Select the zone containing Oracle servers and click the Custom level button.
3. In the Miscellaneous section, enable Access data sources across domains and Allow script-
initiated windows without size or position constraints.
l If you are using Internet Explorer with EPM Workspace in Norwegian, you need to change
the Language Preferences settings as follows:
1. In Internet Explorer, select Tools, then Internet Options, and click the Languages button.
2. In the Language Preferences dialog box, select each of the Norwegian settings, and then
click Remove.
3. Click Add, and then add a user-defined value called no and click OK.
55
4. In the Language field, select the new User Defined [no] entry, and then click Move up to
move this entry to the top of the list.
5. Click OK.
You can now view EPM System products in Norwegian using Internet Explorer.
Note: After you click OK, the custom language setting in Language Preferences dialog
box changes to Norwegan (Bokmal) [no], which is different from the default
Norwegian (Bokmal) [ne-NO] setting.
Enabling ActiveX (Reporting and Analysis)

To enable EPM System Java web applications to function properly, Internet Explorer must be
configured to enable support for ActiveX technologies.
EPM System products do not download ActiveX components to the browser. Instead, only
HTML, JavaScript, and XML are sent to and by the client browser.
Guidelines to enable XML components:
l In the browser security settings, enable ActiveX controls and plug-in execution by setting
Run ActiveX controls and plug-ins to Enable.
l Enable ActiveX controls and plug-in execution by adding the Project Reporting and
Analysis site as a trusted site and changing the custom security settings for trusted sites.
l Provide group policies that define the controls required for handling XML (the MS XML
parser and XMLHTTPRequest controls) and enable these administrator approved controls
for all sites or for select trusted sites.
l All other ActiveX controls and plug-ins remain disabled. Group policies can be implemented
by zone by enabling the controls for sites in the trusted zone.
l For Active X enabled controls, enable the setting Script ActiveX controls marked safe for
scripting.
Support Matrix for High Availability and Load Balancing

The tables in this section list the supported clustering methodologies for EPM System
components by product group and indicate whether high availability and load balancing are
supported for each component. The tables also include notes and references to additional
information. Use this table to help plan your environment.
Session failover is not supported for EPM System Java web applications.
For information about clustering Java web applications deployed to IBM WebSphere, see the
WebSphere documentation.
EPM System components support vertical scaling as follows:
l Windows-based Java web applications except for Financial Management and Strategic
Finance Java web applications
56
l Essbase Server
l UNIX-based components
The following components do not support vertical scaling:

l Performance Management Architect Dimension Server
l All Financial Management components
l Financial Close Management and Account Reconciliation Manager
l Disclosure Management
l All Strategic Finance components
l All FDM components
l Integration Services components
Table 4 Foundation Services Clustering
Product/ Supported High Load References

Component Methodology Availability Balancing Notes
Foundation WebLogic Yes Yes To configure l Automatic deployment: Clustering Java Web
Services clustering with Lifecycle Applications Using EPM System Configurator in
Managed EPM System Management the Oracle Enterprise Performance Management
Server Configurator for high System Deployment Options Guide
(includes availability
Manual deployment: Clustering Java Web
Shared when Shared
l
Services and Services is set Applications in a WebLogic Manual Deployment

EPM up for high in the Oracle Enterprise Performance Management
Workspace availability, System Deployment Options Guide
Java Web you must set
applications) up a shared
disk.
Performance WebLogic Yes Yes None l Automatic deployment: Clustering Java Web
Management clustering with Applications Using EPM System Configurator in
Architect Java EPM System the Oracle Enterprise Performance Management
Web Configurator System Deployment Options Guide
Application
l Manual deployment: Clustering Java Web
Applications in a WebLogic Manual Deployment
in the Oracle Enterprise Performance Management
System Deployment Options Guide
Management clustering with Applications Using EPM System Configurator in
Architect Data EPM System the Oracle Enterprise Performance Management
Synchronizer Configurator System Deployment Options Guide
Java Web
Application l Manual deployment: Clustering Java Web
57
Calculation WebLogic Yes Yes None l Automatic deployment: Clustering Java Web
Manager Java clustering with Applications Using EPM System Configurator in
Web EPM System the Oracle Enterprise Performance Management
Application Configurator System Deployment Options Guide
Performance Oracle Yes No None l Performance Management Architect Dimension

Management Clusterware Server Clustering and Failover in the Oracle
Architect clustering for Enterprise Performance Management System
Dimension failover Deployment Options Guide
Server and
other l Oracle Clusterware documentation
processes
58
Table 5 Essbase Clustering

Essbase Server l Active-passive Yes Active- l Active-passive clusters l Active-passive clustering

clustering with active support failover with (Windows): Configuring
Microsoft clusters write-back. Active-Passive Essbase
Clustering configured Clusters (Windows) in the
Active-active clusters
Services with Oracle Enterprise Performance
l
are read-only.
(Windows) Provider Management System
Services Deployment Options Guide
l Active-passive support The following EPM System
clustering with load- products support Essbase l Active-passive clustering
EPM System balancing. active-passive failover: (UNIX): Configuring Active-
Configurator Passive Essbase Clusters
(UNIX) l FDMEE (UNIX) in the Oracle Enterprise
Active-active l Planning Performance Management
System Deployment Options
l
clustering with Administration
Guide
l
Provider Services
Services Essbase Studio l Active-active clustering:
Configuring Active-Active
l
l Financial Reporting Essbase Clusters in the Oracle

Studio Enterprise Performance
l Web Analysis Management System
Deployment Options Guide
The following EPM System
products do not support
Essbase active-passive
failover:
l Integration Services
l Interactive Reporting
l FDM
l Oracle Essbase
Analytics Link for
Hyperion Financial
Management
Administration WebLogic Yes Yes l Automatic deployment:

Services Java clustering with EPM Clustering Java Web
Web System Applications Using EPM System
Application Configurator Configurator in the Oracle
Enterprise Performance
Management System
l Manual deployment:
Clustering Java Web
Applications in a WebLogic
Manual Deployment in the
Oracle Enterprise Performance
Management System
59
Provider WebLogic Yes Yes None l Automatic deployment:

Services Java clustering with EPM Clustering Java Web
Web System Applications Using EPM System
Application Configurator Configurator in the Oracle
Enterprise Performance
Management System
l Manual deployment:
Clustering Java Web
Applications in a WebLogic
Manual Deployment in the
Oracle Enterprise Performance
Management System
Integration None No No None None

Services
Essbase Studio None No No None None
Table 6 Reporting and Analysis Clustering

Reporting WebLogic Yes Yes None l Automatic deployment: Clustering Java Web
and Analysis clustering with Applications Using EPM System Configurator in the
Framework EPM System Oracle Enterprise Performance Management System
Java Web Configurator Deployment Options Guide
Application
l Manual deployment: Clustering Java Web Applications
in a WebLogic Manual Deployment in the Oracle
Enterprise Performance Management System
Financial WebLogic Yes Yes None l Automatic deployment: Clustering Java Web
Reporting clustering with Applications Using EPM System Configurator in the
Java Web EPM System Oracle Enterprise Performance Management System
Application Configurator Deployment Options Guide
(includes
Financial l Manual deployment: Clustering Java Web Applications
Reporting in a WebLogic Manual Deployment in the Oracle
Print Server) Enterprise Performance Management System
Web Analysis WebLogic Yes Yes None l Automatic deployment: Clustering Java Web
Java Web clustering with Applications Using EPM System Configurator in the
Application EPM System Oracle Enterprise Performance Management System
Configurator Deployment Options Guide
60
Reporting Virtual Yes Yes None Clustering Reporting and Analysis in the Oracle Enterprise
and Analysis clustering Performance Management System Deployment Options
Framework through EPM Guide
Services and Workspace
Common
Libraries
Interactive Virtual Yes Yes None Clustering Reporting and Analysis in the Oracle Enterprise
Reporting clustering Performance Management System Deployment Options
Services through EPM Guide
Workspace
Table 7 Financial Performance Management Applications Clustering

Planning Java WebLogic Yes Yes None l Automatic deployment: Clustering Java Web
Web Application clustering with Applications Using EPM System Configurator in the
EPM System Oracle Enterprise Performance Management System
Planning RMI None No No None None

Registry
Financial Clustering with Yes Yes None Clustering Financial Management Servers in the Oracle
Management EPM System Enterprise Performance Management System Deployment
Server Configurator Options Guide
Financial WebLogic Yes Yes None l Automatic deployment: Clustering Java Web
Management clustering with Applications Using EPM System Configurator in the
(includes Web
Services and l Manual deployment: Clustering Java Web Applications
ADF Web in a WebLogic Manual Deployment in the Oracle
applications) Enterprise Performance Management System
Financial Clustering with Yes Yes None Load Balancing Financial Management, Strategic Finance,
Management a Web server or or FDM IIS Web Applications on IIS in the Oracle Enterprise
Web Services IIS third-party Performance Management System Deployment Options
Web Application load balancer Guide
(IIS)
Management IIS a Web server or or FDM IIS Web Applications on IIS in the Oracle Enterprise
Web Application third-party Performance Management System Deployment Options
(IIS) load balancer Guide
61
Lifecycle third-party Performance Management System Deployment Options
Management load balancer Guide
Web Services IIS
Web Application
(IIS)
Smart View IIS third-party Performance Management System Deployment Options
Web Application load balancer Guide
(IIS)
Scorecard Java clustering with Applications Using EPM System Configurator in the
Web Application EPM System Oracle Enterprise Performance Management System
Profitability and WebLogic Yes Yes None l Automatic deployment: Clustering Java Web
Cost clustering with Applications Using EPM System Configurator in the
Management EPM System Oracle Enterprise Performance Management System
Java Web Configurator Deployment Options Guide
Application
Disclosure WebLogic Yes Yes None l Automatic deployment: Clustering Java Web
Financial Close WebLogic Yes Yes None l Automatic deployment: Clustering Java Web
(includes Close EPM System Oracle Enterprise Performance Management System
Manager and Configurator Deployment Options Guide
Account
Reconciliation l Manual deployment: Clustering Java Web Applications
Manager Java in a WebLogic Manual Deployment in the Oracle
Web Enterprise Performance Management System
Applications) Deployment Options Guide
l Load balancing: Configuring High Availability for
Oracle Fusion Middleware SOA Suite in the Oracle
Fusion Middleware High Availability Guide
62
Strategic None No No None

Finance Server
Strategic WebLogic Yes Yes None l Automatic deployment: Clustering Java Web
Finance Java clustering with Applications Using EPM System Configurator in the
Web Application EPM System Oracle Enterprise Performance Management System
Strategic Clustering with Yes Yes None Load Balancing Financial Management, Strategic Finance,
Finance IIS Web a Web server or or FDM IIS Web Applications on IIS in the Oracle Enterprise
Application (IIS) third-party Performance Management System Deployment Options
load balancer Guide
Table 8 Data Management Products Clustering

FDM Clustering with Yes Yes None l Database software documentation

Application the FDM
FDM Clusters in the Oracle Enterprise
Server proprietary
l
Performance Management System
load balancer
l Oracle Hyperion Financial Data Quality
Management Configuration Guide
FDM None Yes No The load balancer None

proprietary is designed to be
load balancer installed in more
than one place in
an environment. If
the primary load
balancer becomes
unavailable,
clients use a
secondary load
balancer.
FDM IIS Web Clustering with Yes Yes None Load Balancing Financial Management,
Application a Web server or Strategic Finance, or FDM IIS Web Applications
third-party on IIS in the Oracle Enterprise Performance
load balancer Management System Deployment Options
Guide
FDM Task None No No None None

Manager
63
FDMEE WebLogic Yes Yes None l Automatic deployment: Clustering Java

clustering with Web Applications Using EPM System
EPM System Configurator in the Oracle Enterprise
Configurator Performance Management System
Applications in a WebLogic Manual
Deployment in the Oracle Enterprise
Data Clustering with No Yes Multiple Microsoft l Data Relationship Management Clusters
Relationship a Web server or IIS instances are in the Oracle Enterprise Performance
Management third-party deployed in an Management System Deployment Options
IIS Web load balancer active-active Guide
Application configuration.
l Configuring Load Balancing for Data
Relationship Management Web
Applications in the Oracle Data
Relationship Management Installation
Guide
Data Clustering with No Yes Multiple l Data Relationship Management Clusters

Relationship Data application servers in the Oracle Enterprise Performance
Management Relationship are deployed in a Management System Deployment Options
Application Management primary-secondary Guide
Server proprietary configuration.
Configuring Host Machines in the Oracle
load balancing l
Data Relationship Management Installation
Guide
64
Downloading Files for
4 Installation
In This Chapter
Downloading the Installation Files .......................................................................65
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.

2 Download the following files from the Oracle Enterprise Performance Management System media pack
on the Oracle Software Delivery Cloud (http://edelivery.oracle.com/) site into /
download_location. Note that some files are posted by platform; ensure that you download files
for the platform you are using.
l EPM System Installer (in EPM System Release 11.1.2.3.0 for platformName
(Part 1)
l 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 the Oracle Software Delivery Cloud 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 Unzip the EPM System Installer into /download_location.
If you are prompted that any files already exist, click Yes to overwrite the files.
Tip: Use a zip file extraction program that can handle long path names, such as 7-Zip.
Unzip to a directory with no spaces in the name.

4 Unzip the installation assemblies into the same directory (/download_location).
65
If you are prompted that any files or common components already exist, click Yes to
overwrite the files.
The assemblies are automatically unzipped into an /assemblies directory.
If you downloaded files to a central location, ensure that 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. Unzip files for each operating system
in a separate folder.
l EPM System Release 11.1.2.3.0 for platformName (Part 1)
Note the following information about preparing files for a distributed environment:
l Even though you need these four ZIP files on each machine in the environment, install
Foundation Services Java web applications on only one machine (unless multiple Java
web applications are required for clustering).
l On the machine on which you plan to administer the WebLogic Server, you must install
all Java web applications for all applications you plan to deploy on any machine in the
environment. For more information, see Installing EPM System Products in a
Distributed Environment on page 81.
5 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.
66
Installing EPM System Products
5 in a New Deployment
In This Chapter
Installation Checklist for a New Installation .............................................................67
Financial Close Management (Close Manager and Account Reconciliation Manager) Installation
Checklist ....................................................................................................71
Installation Prerequisites and Requirements ............................................................76
Installation Sequence .....................................................................................81
Installing EPM System Products in a Distributed Environment ........................................81
Integrating Oracle BI EE with EPM System...............................................................82
Installing EPM System Products ..........................................................................83
Performing Silent Installations ............................................................................90
Installing EPM System Clients ............................................................................92
EPM System Installer installs Web and services components. Additionally, when you configure
EPM System products, you configure databases.
Clients are installed with standalone installers, with the exception of:
l Integration Services Console
l FDM Workbench
l Performance Management Architect Batch Client
l Production Reporting Studio, Viewer, and Activator
Installation Checklist for a New Installation

EPM System deployment follows this workflow. Each part of the workflow is described in the
sections as noted in the table below:
Note: If you are installing Financial Close Management, follow the installation and
configuration sequence described in Financial Close Management (Close Manager and
Account Reconciliation Manager) Installation Checklist on page 71.
67
Note: Upgrade Note!
If you are upgrading from an earlier release of EPM System products, use EPM System
Installer and EPM System Configurator to install products in a new environment,
following the process in Chapter 11, Upgrading EPM System Products. Upgrading does
not apply to moving from Release 11.1.2.0, 11.1.2.1, or Release 11.1.2.2 to Release 11.1.2.3.
If you are moving from Release 11.1.2.0, 11.1.2.1, or Release 11.1.2.2 to Release 11.1.2.3,
Use the Apply Maintenance Release option in EPM System Installer, and see Chapter 10,
Performing a Maintenance Release Installation for EPM System Products.
Task Reference
1. Meet the system requirements. Oracle Enterprise Performance Management System Certification Matrix (http://www.
oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.
html)
2. Plan the installation and perform prerequisite Chapter 3, Preparing Your Environment
tasks.
3. Prepare the installation files. Chapter 4, Downloading Files for Installation
4. Install EPM System products. Chapter 5, Installing EPM System Products in a New Deployment
Ensure that you meet any installation prerequisites that apply to your environment.
Installation Prerequisites and Requirements on page 76.
Tip: Before you begin, determine the type of installation you plan to perform:
l New installation
l Maintenance release installation
l Re-installation
For details on each installation type, see Installation Type on page 87.
Upgrade Note!
If you are upgrading from an earlier release, you must choose New Installation and
install in a new installation location.
See Chapter 11, Upgrading EPM System Products.
68
Task Reference
5. Configure EPM System products using EPM Chapter 6, Configuring EPM System Products in a New Deployment
Ensure that you meet any configuration prerequisites that apply to your environment.
See Configuration Prerequisites on page 100.
Note: In a distributed environment, configure Foundation Services first. Foundation
Services must be installed and configured in order for other products to configure
successfully.
Configure other EPM System products, and then configure the Web server last: (Select
the Foundation Services Configure Web Server task.) Then, restart the Web server and
refresh EPM Workspace. If you configured Oracle HTTP Server to a shared drive, you can
simply restart the Web server and refresh EPM Workspace; you do not have to reconfigure
the Web server. See Refreshing EPM Workspace on page 114.
For more information about required configuration sequence, see Configuration
Sequence on page 105.
Note: If you are enabling SSL in your deployment, see the Oracle Enterprise
Performance Management System Security Configuration Guide before you configure.
Different SSL configurations have implications for the choices you make during
configuration using EPM System Configurator. Also, there are additional post-
configuration tasks when deploying an SSL configuration.
6. Optionally, manually deploy EPM System Chapter 7, Manually Deploying EPM System Java Web Applications
Java web applications.
7. Any time you deploy additional products,

reconfigure the Web Server and then restart it
(or simply restart it if you configured Oracle
HTTP Server to a shared drive) on each machine
hosting Foundation Services.
Then, refresh EPM Workspace on each
Foundation Services host machine in your
deployment.
See Refreshing EPM Workspace on page
114.
8. Perform any required manual configuration Chapter 9, Performing Manual Configuration Tasks in a New Deployment
tasks for your products.
9. Start EPM System services. Chapter 12, Starting and Stopping EPM System Products
10. Validate the installation using Oracle Chapter 13, Validating the Installation and Verifying Deployment
Hyperion Enterprise Performance Management
System Diagnostics and verify deployment.
11. Enable external authentication and Oracle Enterprise Performance Management System User Security Administration Guide
provision users.
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.
69
Deploying to a Shared Drive Environment (UNIX)
For UNIX environments, you can deploy to a shared drive (not supported for Windows). When
you deploy to a shared drive, you can:
l Install once, and configure on each machine
l Review the configuration for a distributed setup from a single machine
l Review logs for different machines from a single machine
l Enable patching in a single place
l Simplify disaster recovery setup
The following procedure describes an overview of the process of deploying EPM System products
to a shared drive. Use this procedure along with the installation checklist. See the Installation
Checklist for a New Installation on page 67 for details.
EPM System supports the following types of shared drives:
l Any SAN storage device with a shared disk file system supported on the installation platform
l Any NAS device over a supported network protocol
This procedure assumes that you perform the installation as the same user on all machines and
that the user's home directory is the same on all machines, for example an NFS share.
Deploying to a shared drive environment:

1 Map all the machines in the deployment to the same network share.
2 Run EPM System Installer on one machine to install all EPM System components on the shared drive.
During installation, on the Destination/Middleware Home page, specify a directory on the
shared drive.
3 Run EPM System Configurator on each machine in the environment.

l For each machine, on the Oracle Instance configuration page, for Home directory for EPM
Oracle instances specify the same EPM Oracle instance home, and for EPM Oracle
Instance name specify a new EPM Oracle instance name. For example, after
configuration, the directory structure for EPM_ORACLE_INSTANCE looks like:
/user_projects
/node1
/node2
/nodeN
domains/epmsystem
l For each machine, configure only the components to be run on the machine.
l Configure Foundation Services first, on the machine that is to be the WebLogic
Administration Server.
l The Set Up Shared Services and Registry Database Connection configuration page
displays only on the first machine.
70
4 Complete the configuration on each machine and close EPM System Configurator before moving on to
configure another machine.
Financial Close Management (Close Manager and

Account Reconciliation Manager) Installation
Checklist
For Financial Close Management, you must install Oracle SOA Suite and all its required patches.
Note: If you are applying the maintenance release to move from Financial Close Management
Release 11.1.2.1 or Release 11.1.2.2 to Release 11.1.2.3, see Financial Close Management
Maintenance Release Installation Checklist on page 188.
Note the following about Financial Close Management installation:

l In a distributed environment, you must install Oracle SOA Suite on the following machines
in the deployment, although you need to configure it on only one machine (the machine
on which you want to run SOA Server): Financial Close Management, WebLogic
Administration Server, Foundation Services, and if you are integrating with these products:
Financial Management (Java web application), Financial Reporting (Java web application),
FDM (Java web application).
l Oracle SOA Suite and EPM System must be deployed to the same WebLogic domain.
l If you have an existing Oracle SOA Suite installation you plan to use with Financial Close
Management, you must install EPM System products to this same Middleware home.
l Typically, EPM System Installer installs WebLogic Server for you. If you have an existing
WebLogic Server installation and want to use it instead of the WebLogic Server installed by
EPM System Installer, it must be the version supported by EPM System. Note the
Middleware home location for the WebLogic Server installation. During installation, you
must install EPM System products to this same Middleware home. If EPM System Installer
detects an existing WebLogic Server installation in the installation location, it does not install
WebLogic Server.
If the existing WebLogic Server version is not the correct version for EPM System, you must
either uninstall the current version, install the correct version, or upgrade to the correct
version before running EPM System Installer.
The following tables provide an overview of the installation and configuration process for Oracle
SOA Suite and Financial Close Management in the following scenarios:
l In a new deployment, where you have not installed or configured any EPM System products.
l In an existing deployment, where you have already installed and configured some EPM
System products and now want to extend the deployment to include Financial Close
Management and Oracle SOA Suite.
71
Table 9 Roadmap for Installing and Configuring Oracle SOA Suite and Financial Close Management in a new EPM System Deployment
Task Reference
Install EPM System products. Installing EPM System

Products on page 83.
Note: In a distributed environment, on the machine on which you plan to administer the WebLogic Server,
you must install all Java web applications for all applications you plan to deploy on any machine in the In addition, for a distributed
environment. environment, ensure that you
review Installing EPM System
If Oracle SOA Suite is to be installed on a machine separate from EPM System products, you must also
Products in a Distributed
install Foundation Services on the SOA machine.
Environment on page 81
After installation, apply patch 16788543. for additional requirements.
A default installation of EPM System installs WebLogic Server, which is required for Oracle SOA Suite. The
WebLogic Administration Server is installed and deployed on the Foundation Services machine.
Caution! After installation, do not proceed with configuring EPM System products using EPM System
Configurator until you have completed the following Oracle SOA Suite configuration steps.
If you are using Microsoft SQL Server, review XA Configuration Required to Start the SOA Infrastructure http://download.oracle.
on Microsoft SQL Server 2008 in the Oracle Fusion Middleware Release Notes 11g Release 1 (11.1. com/docs/cd/E15523_01/
1) for Microsoft Windows (32-Bit). relnotes.1111/e10132/soa.
htm#CDEIFEAC
Run the Repository Creation Utility and install Oracle SOA Suite. Creating Infrastructure
Schemas Using Repository
Note: In a distributed environment, you must install Oracle SOA Suite on the following machines in the
Creation Utility on page
deployment, although you need to configure it on only one machine (the machine on which you want to
101 and Installing Oracle
run SOA Server): Financial Close Management, WebLogic Administration Server, Foundation Services, and
SOA Suite on page 103
if you are integrating with these products, Financial Management (web application), Financial Reporting
(web application), FDM (Web application).
Configure Oracle SOA Suite, creating a new WebLogic domain. You must also install any required Oracle Configuring and Starting
Fusion Middleware patches, available on My Oracle Support. Oracle SOA Suite on page
103
Note: In a distributed environment note the following additional step:
and
l If Oracle SOA Suite is on a machine separate from EPM System products, you must also install
Foundation Services on the SOA machine. Chapter 5, Installing EPM
System Products in a New
If Oracle SOA Suite is configured on a machine separate from the WebLogic Administration Server
Deployment
l
machine, use the pack command on the machine hosting the WebLogic Administration Server to pack
the domain, and then use the unpack command to unpack it on the machine hosting the SOA Tip: Review the SOA startup
Server. logs for any errors and resolve
the errors before proceeding
If you plan to configure SOA clusters, configure the clusters at this point. See Configuring High Availability with EPM System
for Oracle Fusion Middleware SOA Suite in the Oracle Fusion Middleware High Availability Guide for Configurator. You can also
information about configuring SOA clusters. view the status of SOA in
Enterprise Manager Console.
Stop the SOA managed server. Stop WebLogic Server if it is on the same machine as Foundation
Services.
72
Task Reference
Configure EPM System products, selecting all required configuration tasks except Deploy to SOA for Configuring EPM System
Close Manager, and Deploy to SOA and Deploy to SOA for FDM EE for Account Reconciliation Products on page 111
Manager.
During deployment, you must extend the WebLogic domain created during Oracle SOA Suite
deployment.
If you want to manually deploy the Java web applications, do so now. See Chapter 7, Manually Deploying
EPM System Java Web Applications.
Note: Note the following information about configuring in a distributed environment:
l You must configure Foundation Services first.
l When configuring Financial Close Management in a distributed environment, ensure that the WebLogic
Administration Server is running before you start EPM System Configurator.
l If you are deploying EPM System products to a domain hosted on another machine (and the domain
was not created with EPM System Configurator), you must make manual updates to jps-config.
xml and system-jazn.xml on the Administration Server box.
See step 19 on page 157 and step 20 on page 161 of Chapter 7, Manually Deploying EPM System
Java Web Applications.
Start WebLogic Administration Server and then the SOA managed server. Configuring and Starting
Oracle SOA Suite on page
103
Start EPM System Configurator and select Deploy to SOA for Close Manager, and Deploy to SOA and Configuring EPM System
Deploy to SOA for FDM EE for Account Reconciliation Manager. Products on page 111
If you are deploying EPM System products to a domain hosted on another machine (and the domain was
not created with EPM System Configurator), you must also select the Configure Web Server task.
Restart WebLogic Administration Server.
If you change the configuration at any time to change the logical address of the Java web applications
(using the Update Logical Address for Web Applications page of EPM System Configurator, you must
perform the following tasks:
l For Close Manager:
1. Make sure there are no running tasks or alerts.
2. Start EPM System Configurator and from the Task Selection page, from the Financial Close,
Financial Close Management section, select Deploy to SOA.
3. Click Next, continue with the configuration, and then click Finish.
l For Account Reconciliation Manager:
1. Make sure there are no open periods. If there are open periods, lock them. Make sure there are
no running DataLoads.
2. Start EPM System Configurator and from the Task Selection page, from the Financial Close, Account
Reconcilation section, select Deploy to SOA and Deploy to SOA for FDM EE.
4. Unlock any locked periods.
l For both: Connect to soainfra datasource and run the following query:
UPDATE WFTASKDISPLAY SET httpport = <LWA Port> , httpsport=0,
hostname = <LWA Host> WHERE URI like '/workflow/%';
73
Task Reference
In a distributed environment, if Oracle SOA Suite is on a machine separate from EPM System products, Chapter 6, Configuring EPM
ensure that you have installed Foundation Services on the SOA machine. Then, on the SOA machine, start System Products in a New
EPM System Configurator and configure with the default selected configuration tasks (Configure Common Deployment
Settings, Configure Database, Configure Oracle Configuration Manager). During database
configuration, specify the Foundation Services database information you entered when you configured the
Foundation Services machine.
Tip: You can ignore any messages about Shared Services registration failing.
Perform manual configuration tasks for Financial Close Management. Financial Close Management
Manual Configuration Tasks
on page 179
Stop the SOA server, and then start EPM System products, the SOA Server and Financial Close Management Chapter 12, Starting and
in the order listed. Stopping EPM System
Products, and Financial
Close Management
Application Server on page
318
Validate the installation and verify deployment. Chapter 13, Validating the
Installation and Verifying
Deployment
If you have already installed and configured some EPM System products, you can add Financial
Close Management and Oracle SOA Suite to the existing deployment using the following
roadmap:
Table 10 Roadmap for Installing and Configuring Oracle SOA Suite and Financial Close Management in an Existing EPM System Deployment
Task Reference
Install Financial Close Management. Installing EPM System Products

on page 83.
Note: In a distributed environment, on the machine on which you plan to administer the WebLogic
Server, you must install all Java web applications for all applications you plan to deploy on any In addition, for a distributed
machine in the environment. environment, ensure that you
review Installing EPM System
After installation, apply patch 16788543.
Products in a Distributed
A default installation of EPM System installs WebLogic Server, which is required for Oracle SOA Suite. Environment on page 81 for
The WebLogic Administration Server is installed and deployed on the Foundation Services additional requirements.
machine.
Configurator until you have completed the following Oracle SOA Suite configuration steps.
If you are using Microsoft SQL Server, review XA Configuration Required to Start the SOA Infrastructure http://download.oracle.com/
on Microsoft SQL Server 2008 in the Oracle Fusion Middleware Release Notes 11g Release 1 (11. docs/cd/E15523_01/relnotes.
1.1) for Microsoft Windows (32-Bit). 1111/e10132/soa.
htm#CDEIFEAC
74
Task Reference
Run the Repository Creation Utility and install Oracle SOA Suite. Creating Infrastructure Schemas
Using Repository Creation Utility
Note: In a distributed environment, you must install Oracle SOA Suite on the following machines in
on page 101 and Installing
the deployment, although you need to configure it on only one machine (the machine on which you
Oracle SOA Suite on page 103
want to run SOA Server): Financial Close Management, WebLogic Administration Server, Foundation
Services, and if you are integrating with these products, Financial Management (Web application),
Financial Reporting (Web application), FDM (Web application).
From the WebLogic Administration Server machine, configure Oracle SOA Suite. Configuring and Starting Oracle
SOA Suite on page 103 and
Note: During configuration, you must extend the WebLogic domain created during initial EPM System
Chapter 5, Installing EPM System
deployment.
Products in a New Deployment
You must also install any required Oracle Fusion Middleware patches, available on My Oracle
Tip: Review the SOA startup logs
Support.
for any errors and resolve the errors
Note: In a distributed environment note the following additional step: before proceeding with EPM
System Configurator. You can also
l If Oracle SOA Suite is on a machine separate from EPM System products, you must install view the status of SOA in Enterprise
Foundation Services on the SOA machine. Manager Console.
l If Oracle SOA Suite is configured on a machine separate from the WebLogic Administration Server
machine, use the pack command on the machine hosting the WebLogic Administration Server
to pack the domain, and then use the unpack command to unpack it on the machine hosting
the SOA Server.
Tip: You might need to restart the WebLogic Administration Server prior to starting the SOA managed
server.
If you plan to configure SOA clusters, configure the clusters at this point. See Configuring High
Availability for Oracle Fusion Middleware SOA Suite in the Oracle Fusion Middleware High
Availability Guide for information about configuring SOA clusters.
Stop the SOA managed server. Stop WebLogic Server if it is on the same machine as Foundation
Services.
Configure EPM System products, selecting all required configuration tasks except Deploy to SOA Configuring EPM System
for Close Manager, and Deploy to SOA and Deploy to SOA for FDM EE for Account Reconciliation Products on page 111
Manager.
During deployment, you must extend the WebLogic domain created during EPM System
deployment.
If you want to manually deploy the Java web applications, do so now. See Chapter 7, Manually
Deploying EPM System Java Web Applications.
You must also complete the Foundation Services Configure Web Server task.
When configuring Financial Close Management in a distributed environment, ensure that the WebLogic
Administration Server is running before you start EPM System Configurator.
Start WebLogic Administration Server and then the SOA managed server. Configuring and Starting Oracle
SOA Suite on page 103
Start EPM System Configurator and select Deploy to SOA for Close Manager, and Deploy to SOA Configuring EPM System
and Deploy to SOA for FDM EE for Account Reconciliation Manager. Products on page 111
Restart WebLogic Administration Server.
75
Task Reference
In a distributed environment, if Oracle SOA Suite is on a machine separate from EPM System products,
ensure that you have installed Foundation Services on the SOA machine. Then, on the SOA machine,
start EPM System Configurator and configure with the default selected configuration tasks (Configure
Common Settings, Configure Database, Configure Oracle Configuration Manager). During
database configuration, specify the Foundation Services database information you entered when you
configured the Foundation Services machine.
Tip: You can ignore any messages about Shared Services registration failing.
Perform postconfiguration tasks for Financial Close Management. Financial Close Management
Manual Configuration Tasks on
page 179
Stop the SOA server, and then start EPM System products, the SOA Server and Financial Close Chapter 12, Starting and
Management in the order listed. Stopping EPM System Products,
and Financial Close Management
Application Server on page 318
Restart EPM Workspace to access Financial Close Management from EPM Workspace.
Validate the installation and verify deployment. Chapter 13, Validating the
Installation and Verifying
Deployment
Installation Prerequisites and Requirements

Subtopics
l Web Server Installation Prerequisites
l Configuring X11 for Financial Reporting and Production Reporting (AIX and HP-UX)
Note the following installation prerequisites.

l Review the system requirements in the Oracle Enterprise Performance Management System
Certification Matrix (http://www.oracle.com/technetwork/middleware/ias/downloads/
fusion-certification-100350.html).
l See Chapter 3, Preparing Your Environment for installation prerequisites for preparing a
database, preparing IIS for products that require it, and preparing Web browsers.
l Download files required for installation. See Chapter 4, Downloading Files for
Installation. Review the Media Pack Readme on the Oracle Software Delivery Cloud to see
which products are required or optional for use with your products.
l For Calculation Manager to work on Internet Explorer and Firefox, you must install Adobe
Flash Player.
l If you plan to deploy EPM System products in an SSL-enabled environment, review the
Oracle Enterprise Performance Management System Security Configuration Guide before you
install and configure. The SSL implementation you choose affects the options you choose
during configuration. Optionally, you can deploy non SSL and reconfigure to use SSL. See
the Oracle Enterprise Performance Management System Security Configuration Guide.
76
l If you are installing on Windows 2008, disable UAC before installing. UAC must be disabled
to install, configure, and run EPM System products. UAC can be enabled on end-user client
desktops.
l Ensure that there is 1 GB of temp space available. You can specify an alternate /tmp directory
if needed.
l Before you install Essbase on a 32-bit or 64-bit Linux system, install the following packages:
m compat-libstdc++-33-3.2.3-47.3 or higher
m libaio-0.3.105-2 or higher
l For Planning on Red Hat Enterprise Linux AS Release 4, you must upgrade to glibc 2.5 on
the Linux server. See the Linux documentation for details.
l If you are installing on the same machine on which Oracle Business Intelligence Enterprise
Edition or Oracle Business Intelligence Publisher are installed, install into two different
Middleware homes. Future patch sets for EPM System and Oracle BI EE will be released at
different times, which would create constraints for the upgrades of a merged Fusion
Middleware Home.
For information about Fusion Middleware, see http://www.oracle.com/technetwork/
documentation/index.html#middleware.
l If you are installing and configuring FDMEE, Oracle Data Integrator is automatically
installed and configured for you. The database for Oracle Data Integrator is in same database
as FDMEE and the Oracle Data Integrator agent application is deployed in same JVM as
FDMEE. Optionally, you can install ODI Studio using ODI_Studio_11123.zip.
l FDMEE is required for Account Reconciliation Manager in Financial Close Management.
l If you are installing any of the following products, you must also install the Financial
Management ADM Driver:
m Web Analysis
m Financial Reporting
m Strategic Finance
m FDM
m FDMEE
EPM System Installer installs a Windows version of the driver on Windows machines. EPM
System Installer installs a UNIX version of the driver on all platforms for use with Oracle BI
EE.
l If you have an existing Oracle SOA Suite installation you plan to use with Financial Close
Management, note the Middleware home location for the Oracle SOA Suite installation.
During installation, you must install EPM System products to this same Middleware home.
l Typically, EPM System Installer installs WebLogic Server for you. If you have an existing
WebLogic Server installation and want to use it instead of the WebLogic Server installed by
EPM System Installer, it must be the version supported by EPM System. Note the
Middleware home location for the WebLogic Server installation. During installation, you
77
must install EPM System products to this same Middleware home. If EPM System Installer
detects an existing WebLogic Server installation in the installation location, it does not install
WebLogic Server.
If the existing WebLogic Server version is not the correct version for EPM System, you must
either uninstall the current version, install the correct version, or upgrade to the correct
version before running EPM System Installer.
l For Financial Reporting, install the fonts that are used when designing a report in Financial
Reporting Studio on the server that is hosting the Financial Reporting Java web application
server. Because PDF generation can now be run on a UNIX server, the fonts used in report
design in Financial Reporting Studio must be available on the Financial Reporting Java web
application aerver, otherwise, the default system font on the Financial Reporting Studio Java
web application aerver is used and results are not as expected.
Only True Type fonts are supported; open source fonts are not supported.
l To prepare Interactive Reporting for printing on UNIX, 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.
l For AIX and HP-UX, configure X11 for Financial Reporting Print Server. For Production
Reporting jobs with charts, you must also configure X11
You must also set the DISPLAY variable for Production Reporting in order to generate charts.
See Configuring X11 for Financial Reporting and Production Reporting (AIX and HP-
UX) on page 79.
l Install Microsoft Excel on the FDM Server machine.
l Install Microsoft Office Professional before installing Disclosure Management. To use
Disclosure Management Client, when you install Microsoft Office, you must select .NET
programmability support for Word and Excel.
l If you are installing Strategic Finance using Terminal Services, switch your session to
installation mode before you run EPM System Installer (change user /install).
Web Server Installation Prerequisites

Optionally, EPM System Installer installs Oracle HTTP Server during the installation of
Foundation Services, using the Oracle HTTP Server silent installer. If you choose not to install
Oracle HTTP Server, for example in a development environment, EPM System Installer installs
an embedded WebLogic HTTP Server as part of Foundation Services that acts as a proxy server.
In a production environment, Oracle recommends that you install Oracle HTTP Server for use
with WebLogic. If you are deploying to WebSphere, you must use IBM HTTP Server.
If you are installing Oracle HTTP Server, ensure that you meet the installation prerequisites for
Oracle HTTP Server and review the Oracle HTTP Server installation documentation and Release
Notes for details on certified operating systems and supported UNIX / Linux packages and
important installation issues and workarounds.
78
l For Oracle HTTP Server system requirements information, go to: http://www.oracle.com/
technology/software/products/ias/files/fusion_requirements.htm.
l For Oracle HTTP Server certification information, go to: http://www.oracle.com/
technology/software/products/ias/files/fusion_certification.html.
l For Oracle HTTP Server installation information, see the Oracle HTTP Server installation
documentation: http://download.oracle.com/docs/cd/E15523_01/webtier.htm) and
Release Notes (http://download.oracle.com/docs/cd/E15523_01/relnotes.htm.
l For Oracle HTTP Server installation issues and workarounds, see the readme for your
platform: http://download.oracle.com/docs/cd/E15523_01/relnotes.htm.
On AIX, if you are using Oracle HTTP Server with Oracle Database, you must run
rootpre.sh as the root user before you install Oracle HTTP Server. Run this script once on
each machine in the deployment. The file is in SystemInstaller-11120-aix.zip. For details
see the Oracle Fusion Middleware Release Notes 11g Release 1 (11.1.1) for AIX Based Systems
(64-Bit) (http://download.oracle.com/docs/cd/E15523_01/doc.1111/e14771/toc.htm).
On Windows, ensure that you have a paging file size of at least 512 MB. Do not select the option
to automatically manage paging file size.
During installation with EPM System Installer, check the Installation status for information
about Oracle HTTP Server installation status. If Oracle HTTP Server installation fails, check the
logs for details. The logs report information from the Oracle HTTP Server silent installer. You
can find the logs in:
l Windows: EPM_ORACLE_HOME/diagnostics/logs/ohs
l UNIX: EPM_ORACLE_HOME/diagnostics/logs/install/common-ohs-oui-
out.log
You can also review the Oracle HTTP Server product logs. For more information about Web
server logs, see the Oracle Enterprise Performance Management System Installation and
Configuration Troubleshooting Guide.
Configuring X11 for Financial Reporting and Production

Reporting (AIX and HP-UX)
Financial Reporting Print Server uses Oracle Outside In Image Export technology. Outside In
Image Export requires X11 for the AIX and HP-UX platforms, which is supported either with
Xvfb or x11vnc.
Enabling Xvfb for AIX 5L
To enable Xvfb:
1 Log on to the computer on which you are running the Reporting and Analysis Java web application server
components as the root user.
79
2 Determine whether Virtual Frame Buffer support is available on your computer by issuing the following
command:
lslpp -l X11.vfb
3 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
4 Start Xvfb:
/usr/bin/X11/X -force -vfb :1
where :1 is the a display number not already in use.
Enabling Xvfb for HP-UX
To enable Xvfb:
1 Log on to the computer on which you are running the Reporting and Analysis Java web application server
components as the root user.
2 Determine whether Virtual Frame Buffer support is available on your computer by issuing the following
command:
swlist -l product | grep 'Xserver cumulative patch'
3 Ensure that the patch level installed on your system corresponds with HP's recommended level (currently
PHSS_31293).
4 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
5 Edit /etc/X11/X1screens by adding these lines to the end of the file:
ServerOptions
ServerMode XVfb
6 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 Java 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 the Reporting and Analysis Java web application server components start scripts.
80
You can set display for Financial Reporting by editing
setCustomParamsFinancialReporting.bat|.sh in EPM_ORACLE_INSTANCE/bin/
deploymentScripts.
Note: Only the Financial Reporting Java web application server component and Production
Reporting require DISPLAY to be set. Production Reporting requires DISPLAY in order
to generate charts using the New Graphics feature.
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.
Note that EPM System Installer installs WebLogic Server on each machine where you install a
Web tier or Service tier component, including Essbase Server. The .jar files that are installed
as part of WebLogic Server and Oracle common directory are used by EPM System Configurator
as well as common services. Note that WebLogic Server does not need to run on the Essbase
Server.
OPMN is installed with Foundation Services on all machines where EPM System Configurator
is used because OPMN is used to create the EPM Oracle instance structure.
If you want to install Essbase in standalone mode (not using Foundation Services), you can skip
the installation for Foundation Services Java web applications. However, you must configure
the Shared Services Registry database. To configure the Shared Services Registry database
without installing Foundation Services, see Setting Up Essbase in Standalone Mode on page
152.
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
l The number of users
l The frequency of concurrent use by multiple users
l Any requirements your organization has for high availability
l Your organization's security requirements
See Chapter 2, EPM System Architecture for sample architecture diagrams to help plan your
deployment.
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
81
computer. Once you have installed, configured, and validated the components on that machine,
you can repeat the process on another machine.
Note the following information about installing and configuring in a distributed environment.
Installation considerations in a distributed environment:
l In a distributed environment, EPM Oracle home must be the same on each machine. For
example, if the path for EPM Oracle home is /Oracle/Middleware on the first machine
you configure, it must be /Oracle/Middleware on all the machines in the deployment.
l Foundation Services is required on only one machine in the deployment, unless multiple
Java web application instances are required for clustering, or if you are using Financial Close
Management, if Oracle SOA Suite is on a machine separate from EPM System products, you
must also install Foundation Services on the SOA machine.
l Optionally, Oracle HTTP Server is installed with Foundation Services.
l On the machine on which you plan to administer the WebLogic Server, you must install all
Java web applications for all applications you plan to deploy on any machine in the
environment. (The WebLogic Administration Server is installed and deployed on the
Foundation Services machine.)
l On each remote machine in a distributed environment, install the Java web applications you
plan to run on that machine and then use EPM System Configurator to deploy the Java web
applications automatically, or manually deploy the Java web applications.
Note that EPM System Installer installs WebLogic Server on each machine (for Web tier and
Service tier components) in a distributed environment.
l If you are using IIS as the Web server, install each IIS application so that it is co-located with
an IIS Web server.
l If you are installing in multiple environments (for example, Development, Test, and
Production), install Foundation Services products in each environment.
l If you are installing Financial Management Web and Financial Management Services on the
same machine, they must be installed and configured in the same EPM Oracle instance.
l For IIS 6.0, you cannot install some 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 Strategic Finance (32-
bit) cannot be deployed on the same computer where Financial Management (64-bit) is
deployed. On 32-bit platforms, all EPM System products can co-exist. For IIS 7 (the default
on Windows 2008 systems), 32-bit and 64-bit components can co-exist.
l Web Analysis supports connectivity to Financial Management data sources only for
Financial Management servers that are registered in the same Shared Services Registry as
Web Analysis.
Integrating Oracle BI EE with EPM System

l If you are installing EPM System on the same machine on which Oracle BI EE or BI Publisher
are installed, install into two different Middleware homes. Future patch sets for EPM System
82
and Oracle BI EE will be released at different times, which would create constraints for the
upgrades of a merged Fusion Middleware Home.
For information about Fusion Middleware, see http://www.oracle.com/technetwork/
documentation/index.html#middleware.
l If you plan to integrate Oracle BI EE or BI Publisher with EPM Workspace, after installation,
see the Oracle Enterprise Performance Management System Deployment Options Guide.
l To integrate EPM Workspace Release 11.1.2.3 with Oracle BI EE Release 11.1.1.7, see
Configuring for Integration with EPM Workspace in the Oracle Fusion Middleware
System Administrator's Guide for Oracle Business Intelligence Enterprise Edition (http://
docs.oracle.com/cd/E28280_01/bi.1111/e10541/toc.htm). If you used the EPM Workspace
integration with Oracle BI EE Release 10g, then you can upgrade to Oracle BI EE Release
11.1.1.7, but the integration with EPM Workspace is not upgraded. You must reconfigure
for the integration using the procedures that are described in Oracle Fusion Middleware
System Administrator's Guide for Oracle Business Intelligence Enterprise Edition (http://
docs.oracle.com/cd/E28280_01/bi.1111/e10541/toc.htm).
l (UNIX) If you are using Oracle BI EE as the data source for Essbase, after configuration you
must set additional environment variables for the Oracle BI EE driver before launching
Essbase. See the Oracle Enterprise Performance Management System Deployment Options
Guide.
l For Oracle BI EE integration with Financial Management, after installing Oracle BI EE,
before you can import from or set up a connection to Financial Management data sources,
you must ensure that the Financial Management ADM driver is installed on the system
running the Oracle BI JavaHost process.
Perform the following tasks:
1. Using EPM System Installer, install the Financial Management ADM driver on the
machine running the Oracle BI JavaHost process.
2. Using EPM System Configurator, provide database connection details for Shared
Services and for Financial Management. In the Configure DCOM page, provide a
domain user that is the user connecting to the Financial Management server.
3. After configuration, edit opmn.xml on each system running the Oracle BI JavaHost
process to include environment variables required by Financial Management. See the
Oracle Enterprise Performance Management System Deployment Options Guide.
Installing EPM System Products

You can install EPM System products using the graphical user interface, using the console mode
interface, or using a silent mode installation response file.
When you install EPM System products, choose which type of installation to perform:
l New installation (also used for upgrades).
l Apply maintenance release, if you are moving from Release 11.1.2.0, 11.1.2.1, or Release
11.1.2.2 to Release 11.1.2.3.
83
l Re-install this release
Note the following about installation:

l If you have already installed SOA Suite and WebLogic Server, but have not yet installed EPM
System products, during installation, select Apply Maintenance Release first to install the
latest WebLogic Server, and then select New Installation to continue with the installation of
EPM System products.
l On Windows machines, do not use the Administrator user to install and configure. Run
EPM System Installer and EPM System Configurator as a user with administrator rights.
Install, configure and run EPM System Diagnostics as the same user for all EPM System
products. If you are using Windows 2008, install with UAC disabled. UAC must be disabled
to install, configure, and run EPM System products. UAC can be enabled on end-user client
desktops.
l On UNIX machines, do not use the root user to install and configure. Install, configure
and run EPM System Diagnostics as the same user for all EPM System products. On UNIX
machines, for all Oracle products, the user that is installing must be part of the same group;
the group must have write permission to the central inventory (oraInventory).
l You cannot run EPM System Installer at the same time that you are running another instance
of an Oracle Universal Installer (such as the installer for Oracle Database).
l Run EPM System Installer from a mapped drive, not from a UNC address.
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.
l (Windows) From a Windows console, change to the root directory to which you
extracted the EPM System Installer files and enter installTool.cmd -console.
l Create a silent installation response file. See Performing Silent Installations on page
90.
l (UNIX) Change to the root directory to which you extracted the EPM System Installer
files and enter ./installTool.sh.
files and enter ./installTool.sh -console.
You can specify an alternate tmp directory by using the -tmp parameter. For example: ./
installTool.sh -tmp /templocation.
EPM System Installer performs some initial checks while launching. If you see a message
that User Account Control (UAC) is enabled on Windows 2008 systems, disable UAC,
reboot, and then restart EPM System Installer.
EPM System Installer launches.
84
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.
2 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 (*).
3 Review and complete each page of EPM System Installer, clicking or selecting Next to move to the next
page.
In console mode, enter the number beside the selection you want.
Tip: 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.
The following table provides links where you can find more details about each page of EPM
System Installer.
Table 11 EPM System Installer Pages
Page Reference
Welcome Welcome on page 86
Destination/MiddleWare Home Destination/Middleware Home on page 86
Installation Type Installation Type on page 87
Product Selection Product Selection on page 88
Confirmation Confirmation on page 89
4 When installation is complete, click or select Configure to configure the products using EPM System
Configurator, or click or select Finish to close EPM System Installer.
Note: If you are installing Financial Close Management, note that it requires additional steps
before you configure with EPM System Configurator. See the Financial Close
Management (Close Manager and Account Reconciliation Manager) Installation
Checklist on page 71 for the process to follow.
85
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 or
select Next to continue the installation.
EPM System Installer checks for the following:

l Whether the computer host name resolves 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.
l Whether your system has a supported operating system.
l Whether your system meets minimum memory requirements to run the installation.
l Whether the user installing has administrator privileges (Windows only).
l Whether your system meets environment variable prerequisites.
l Whether the inventory is writable.
l Whether there is 1 GB of temp space available.
l Basic pre-installation checks for WebLogic Server.
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 host name, the host name resolves to the first
entry in your hosts file. To prevent potential communication problems in a distributed
environment, ensure 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/Middleware Home
Specify the destination for the installation location, or browse to a location and select it, and
then click or select Next. The default location is Oracle/Middleware.
The destination you specify becomes the Middleware home. By default EPM System Installer
creates a default EPM Oracle home under the Middleware home. The default location is Oracle/
Middleware/EPMSystem11R1.
See About Middleware Home, EPM Oracle Home, and EPM Oracle Instance on page 19.
Do not use any of the following symbol combinations in the directory that you specify for
EPM_ORACLE_HOME during installation:
/t
86
\t
\b
Note the following information about the Middleware home:

l Ensure that this destination has enough disk space to install all the products that you want
to install on this machine.
See Disk Space and RAM on page 38 for disk space requirements.
l You select a Middleware home for each machine in your environment.
In a distributed environment, EPM Oracle home must be the same on each machine. For
example, if the path for EPM Oracle home is /Oracle/Middleware on the first machine
you configure, it must be /Oracle/Middleware on all the machines in the deployment.
l 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 Middleware
home is listed as the default installation destination, and you cannot change it.
l The destination path cannot contain spaces; for example, c:\Program Files is not
acceptable (unless you use short path notation).
l The first character must be an alphanumeric character.
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.
Installation Type
Select an installation type, and then click or select Next. If an installation type is not applicable
on this machine, the option is unavailable.
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.
Choose from the following installation types:

l New installation
m Choose this option if you are installing an EPM System product for the first time on this
computer.
m Choose this option if you want to install additional components that you did not initially
install.
87
m Choose this option if you are upgrading from an earlier release of EPM System products.
You must install to a new installation location on a machine with an existing earlier
release of EPM System products or to a new machine.
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.
l Apply maintenance release
This option is selected for you if you already installed Release 11.1.2.0, 11.1.2.1, or Release
11.1.2.2.
If you are applying the maintenance release, you must first stop all EPM System services.
If you are applying the maintenance release, EPM System Installer applies the release to all
installed 11.1.2.0, 11.1.2.1, or 11.1.2.2 products. You cannot apply the maintenance release
to only some products in your deployment.
Product Selection
Select the products and product components to install, and then click or select Next.
When Apply Maintenance Release is the installation type, EPM System Installer applies the
release to all installed Release 11.1.2.0, 11.1.2.1, or Release 11.1.2.2 products. You cannot apply
the maintenance release to only some products in your deployment. On the Product Selection
page, you cannot make any selections or deselections.
The following table describes the options for product selection.
Table 12 Product Selection Options
Action Details
Select the products You can expand and collapse the entries to select or clear specific options for each product and
components to install. component.
Uncheck all / Check all Select Check all to select all the products, or Uncheck all to clear all the products. This option is not
available if you are applying a maintenance release.
Hide/Show unavailable To see only products for which installation assemblies are available, select Hide Unavailable Product
products. Components.
To see all products, select Show Unavailable Product Components.
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
88
installing. If a product is unavailable on the Product Selection page, ensure that the
assemblies are in the correct location.
l 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.
l The Shared Services and EPM Workspace Java web applications are installed when you install
the Foundation Services Java web applications.
l If you selected New Installation and you have already installed this release of a product,
the product is unavailable in the Product Selection page.
l In some cases, a component is selected, but is unavailable (you can't clear it), because it is
required for another selected component.
Confirmation
Review the summary of products to be installed. If necessary, click or select Back and make
corrections. Click or select 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 or if you have done a new installation as an upgrade.
l Re-install if this is a reinstallation of the same release of this EPM System product.
l Maintenance if this is a maintenance installation to move from EPM System Release 11.1.2.0,
11.1.2.1, or Release 11.1.2.2 to Release 11.1.2.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 89.
Saving Installation Selections

If you plan to install this same set of components 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 or select Save, browse to a location, specify a file
name, and click or select 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
91.
89
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.
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 Navigate to the directory that contains EPM System Installer.
2 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.
3 Proceed through EPM System Installer, specifying the options that you want to record.
Installation options are recorded in the response file. You can modify the response file later
to change installation options.
You are now ready to run the installation in silent mode.
4 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.
5 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.
Upgrade Note!
Silent response files are not compatible between EPM System Release 11.1.1.0, Release 11.1.2.1,
11.1.2.2 and Release 11.1.2.3. If you created silent response files for use with any earlier release
of EPM System products, you must re-create them for use with EPM System Release 11.1.2.3.
90
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 or select Save, browse to a location, specify a file name, and click or select 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 or select Load,
browse to the saved selections file, and click or select 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 Middleware home and keep only the product components
that you want to install on this machine.
To modify a response file:

1 Open the response file in any text editor. The file is in XML format.
2 Edit the file using the following options.
l <HyperionHome>Location of the Middleware home.
l <SelectedProducts>Product components to install to specific tiers. Make changes
in <Product name>, <ProductComponent name>, <InstallTier>, and
<Component>.
l <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.
3 Save the file in XML format.
91
Installing EPM System Clients
Subtopics
l Client Installation Prerequisites
l Downloading and Extracting Client Installers
l Installing Individual EPM System Clients
l Installing EPM System Clients from EPM Workspace
l Installing EPM System Clients From EPM System Installer
l Installing Multiple Versions of Financial Reporting Studio on a Client Machine
l Performing Silent Client Installations
l Default Installation Directories
Client Installation Prerequisites

Review these prerequisites before installing EPM System clients:
l Planning Offline Client: Install Microsoft Excel and Smart View on the same machine.
The Planning Java web application need not be installed on the same machine, but it must
be running.
Although Planning Offline is supported for 64-bit operating systems, it is not supported for
64-bit Smart View installations. If you use Planning Offline with Smart View, you must use
the 32-bit version of Smart View and the 32-bit version of Microsoft Office.
l Predictive Planning: Install Microsoft Excel and Smart View on the same machine, with
access to Planning.
l Smart View: Install Microsoft Excel with the Visual Basic option. Smart View requires .Net
4.0.
l Strategic Finance: To enable use of Smart View with Strategic Finance, install the Smart
View client before installing the Strategic Finance client.
l Performance Management Architect File Generator: Install Microsoft Excel with "Visual
Basic for Applications" to use Performance Management Architect File Generator from the
Excel File menu.
l Interactive Reporting: After a user has installed Interactive Reporting client (with the ability
to use for all users), subsequent users should run the regServers.bat script (located in
EPM_ORACLE_HOME\products\biplus\bin) in order to run Dashboard Studio and
Dashboard Architect applications.
Downloading and Extracting Client Installers

You use client installers when Installing Individual EPM System Clients and when Installing
EPM System Clients from EPM Workspace.
92
To download and extract the EPM System client installers:
1 On your local computer, create client installer folder; for example,
EPM_Clients_unzipped.
2 From Oracle Software Delivery Cloud, download ClientInstallers-11123.zip.
3 Extract the contents of downloaded file into the folder that you created in step 1.
Extracting the contents of the downloaded file creates subfolders in client installer
folder that contain the installer files, as follows:
l DisclosureManagement/DiscManAddIn/DiscManSetup.msi
l DisclosureManagement/taxodesigner/TaxonomyDesigner.msi
l EPMAClients/EPMAClients.exe
l EssbaseAdministrationServicesConsole/EASConsole.exe
l EssbaseClient/EssbaseClient.exe
l EssbaseStudio/EssbaseStudioConsole.exe
l FinancialManagementClient/HFMClient.exe and HFMClientx64.exe
l FinancialReportingStudio/FinancialReportingStudio.exe
l OracleInteractiveReportingClients/
OracleInteractiveReportingClients.exe
l Planning/OfflinePlanning.exe and PlanningSVExtensions.msi
l PredictivePlanning/predictiveplanning.exe and predictiveplanning-
x64.exe
l ProductionReportingRemoteClient/
OracleProductionReportingRemote.exe
l Smartview/SmartView.exe and Smartview/SmartView-x64.exe
l StrategicFinanceClient/HSFClient.exe and HSFClient-x64.exe
Installing Individual EPM System Clients

Subtopics
l Running an EPM System Client Installer
l Running an EPM System Client Installer From the Command Line
The following EPM System clients have their own Windows installers:
l Disclosure Management
l Integration Services Console Client
Installed whenever EIS Server is selected in EPM System Installer.
l Essbase Administration Services Console
l Essbase Client
93
The Essbase Client installer is Windows only. On UNIX, Essbase Client is installed with
Essbase Server.
l Essbase Studio Console
l Financial Management Console
l Financial Reporting Studio
l Interactive Reporting (Oracle Hyperion Interactive Reporting Studio and Dashboard
Development Services)
l Planning Admin Extension
l Planning Offline Client
l Predictive Planning (module of Planning)
l Performance Management Architect (File Generator)
Batch Client is installed by EPM System Installer whenever EPMA Web Tier is selected
for installation.
l Production Reporting Remote Client
Production Reporting Activator, Oracle Hyperion SQR Production Reporting Developer,
and Production Reporting Viewer are installed always with the Production Reporting
engine.
l Smart View
l Strategic Finance Client
Upgrade Note!
If you have installed a client in a previous release using a Windows installer, you do not need to
uninstall the earlier release of the client.
If you have installed a client in a previous release using EPM System Installer, you must uninstall
the client before using a Windows installer to install the new version if the client.
Running an EPM System Client Installer
Note: If you are using terminal services to install clients, switch your session to installation mode
(change user /install) before running any EPM System client installer.
To run an EPM System client installer:

1 From client installer folder, open the subfolder for the client installer and then double-
click the client installer file name.
See Downloading and Extracting Client Installers on page 92 for the subfolders and
installer names.
Note that Financial Management, Predictive Planning, Smart View, and Strategic Finance
have both 32-bit and 64-bit installers. For Financial Management, the 64-bit installer installs
94
some client components that are 64-bit, but Financial Management and its dependent files
are 32-bit.
2 Proceed through the installation wizard, and click Finish when the installation is complete.
Note: To enable Function Grids in Smart View, install Financial Reporting Smart View Provider:
Navigate to EPM_ORACLE_HOME/common/epmstatic/reporting_analysis/
client and run FRSVProvider.msi, and then restart Microsoft Excel .
Running an EPM System Client Installer From the Command Line

You can run an EPM System client installer from the command line using the following
parameters:
Table 13 Command Line Options for Client Installations
Option Usage
/v"command line options" Specifies command line options to be passed to the client installer.
/s Runs the client installer as a silent installer.
/qn Makes the installation non-interactive.
INSTALLDIR= Specifies the installation directory.

Note: If the EPM_ORACLE_HOME environment variable is defined, the client installation ignores
the INSTALLDIR= value and install the clients in EPM_ORACLE_HOME:
l*v log file path and name Logs installation information in the specified file.
Installing EPM System Clients from EPM Workspace

If you have installed and configured EPM Workspace, you can download and launch installers
for the following clients from EPM Workspace:
l Disclosure Management Taxonomy Designer
l Financial Management Client
l Offline Planning
l Planning Admin Extension
l Predictive Planning
l Smart View
l Strategic Finance Client
To run an EPM System client installer from EPM Workspace:

1 Copy the client installer from client installer folder and place it in a folder on the EPM
Workspace server.
95
See Downloading and Extracting Client Installers on page 92 for information on client
installer folder.
See Table 14 for information on where to place client installers in EPM Workspace.
Table 14 Where to Place Client Installers in EPM Workspace
EPM System Client Installer Location in EPM Workspace

Client
Disclosure DisclosureManagement/taxodesigner/ EPM_ORACLE_HOME/common/epmstatic/

Management TaxonomyDesigner.msi wspace/disclosure_mgmt/taxodesigner/
Taxonomy TaxonomyDesigner.msi
Designer
Financial FinancialManagementClient/HFMClient. EPM_ORACLE_HOME/common/epmstatic/

Management exe wspace/hfm/HFMClient.exe
Client
Note: You cannot install the 64-bit version of Financial
Management Client from EPM Workspace.
Offline Planning/OfflinePlanning.exe EPM_ORACLE_HOME/common/epmstatic/

Planning wspace/OfflinePlanning/Client/
OfflinePlanning.exe
Planning Planning/PlanningSVExtensions.msi EPM_ORACLE_HOME/common/epmstatic/

Admin wspace/PlanningSmartviewExtension/
Extension PlanningSVExtension.msi
Predictive PredictivePlanning/predictiveplanning. EPM_ORACLE_HOME/common/epmstatic/

Planning exe wspace/predictive_planning/
predictiveplanning.exe
Note: You cannot install the 64-bit version of
Predictive Planning from EPM Workspace.
Smart View Smartview/SmartView.exe EPM_ORACLE_HOME/common/epmstatic/

wspace/SmartView.exe
Note: You cannot install the 64-bit version of Smart
View from EPM Workspace.
Strategic StrategicFinanceClient/HSFClient.exe EPM_ORACLE_HOME/common/epmstatic/

Finance Client wspace/hsf/Client/HSFClient.exe
Note: You cannot install the 64-bit version of Strategic
Finance Client from EPM Workspace.
2 Select Tools, then Install, and then select the product to install.
Installing EPM System Clients From EPM System Installer

You can use EPM System Installer to install EPM System clients that do no have their own
Windows installer.
To install EPM System clients from EPM System Installer:

1 Launch EPM System Installer.
2 On the Product Selection panel, select the client(s) to install.
3 Continue through the panels in EPM System Installer.
96
Installing Multiple Versions of Financial Reporting Studio on
a Client Machine
You can install more than one version of Financial Reporting Studio (for example a test and a
development version) on a client machine for versions 11.1.2.3 and later only. The installed
versions of Financial Reporting Studio are displayed in the Microsoft Windows Start menu folder
and shortcuts, as well as in the Uninstall panel.
Note: Each Financial Reporting Studio version installed on a client machine must be installed
in a different directory.
To install Financial Reporting Studio:

1 In EPM Workspace, select Tools, then Install, and then Financial Reporting Studio.
2 After the download is complete, close all browsers and then run the Financial Reporting Studio installer
as an administrator.
Note: If a machine has multiple versions of Financial Reporting Studio installed, only one release
can be accessed at a time.
To access a Financial Reporting Studio version:

1 From the Microsoft Windows Start menu, select Oracle, then Financial Reporting Studio <version
number>, and then Register Financial Reporting Studio <version number>, where <version
number> is the Financial Reporting Studio release to use.
2 To launch the Financial Reporting Studio version registered in the previous step, from the Microsoft
Windows Start menu, select Oracle, then the folder Financial Reporting Studio <version number>, and
then Financial Reporting Studio <version number> .
Performing Silent Client Installations

Administrators can enable silent installations. When silent installations are enabled, you can
include the silent installation command in scripts to automate the process, so that you do not
need to specify settings each time you perform an installation.
To perform a silent installation of any EPM System client other than Disclosure
Management, use this command:
installer file name /s /v"/qn INSTALLDIR=installation directory /l*v log
file path and name"
To perform a silent installation of Disclosure Management, use this command:

DiscManSetup.msi /qn INSTALLDIR=installation directory /l*v log file
name
97
Note: For installer file names, see Downloading and Extracting Client Installers on page 92.
For information about command-line parameters, see Table 13 on page 95.
Default Installation Directories

Table 15 Default Client Installation Directories
Client Default Installation Directory
Disclosure Management c:/Program Files/Oracle Hyperion Disclosure Management
Administration Services Console EPM_ORACLE_HOME/products/Essbase/eas/console
Essbase Client EPM_ORACLE_HOME/products/Essbase/EssbaseClient
Essbase Studio Console EPM_ORACLE_HOME/products/Essbase/EssbaseStudio/console
Financial Management Client EPM_ORACLE_HOME/products/FinancialManagement
Financial Reporting Studio EPM_ORACLE_HOME/products/FinancialReportingStudio
Interactive Reporting EPM_ORACLE_HOME/products/biplus
Performance Management Architect EPM_ORACLE_HOME/products/Foundation/BPMA/EPMAFileGenerator
Planning Admin Extension 32-bit

C:.Program Files/Oracle/Planning extension for Smart View
64-bit
C:.Program Files (x86)/Oracle/Planning extension for Smart View
Planning Offline EPM_ORACLE_HOME/products/OfflinePlanning
Predictive Planning C:/Program Files/Oracle/Crystal Ball
Production Reporting EPM_ORACLE_HOME/products/biplus
Smart View C:/Oracle/SmartView
Strategic Finance EPM_ORACLE_HOME/products/hsf/Client
98
Configuring EPM System
6 Products in a New Deployment
In This Chapter
About EPM System Configurator..........................................................................99
Configuration Prerequisites ............................................................................. 100
Configuration Sequence................................................................................. 105
Configuring Products in a Distributed Environment ................................................... 106
Configuring Products in an SSL-Enabled Environment ............................................... 107
Configuring Products for Manual Deployment......................................................... 108
Configuring Products for WebSphere Application Server ............................................. 108
Product Configuration Task Summary .................................................................. 108
Configuring EPM System Products ..................................................................... 111
EPM System Configurator Task Reference ............................................................. 115
Performing Silent Configurations ....................................................................... 150
Setting Up Essbase in Standalone Mode.............................................................. 152
Deploying Financial Management, Financial Reporting, and Web Analysis on Windows in a UNIX-
Based EPM System Deployment ....................................................................... 153
What Happens During Configuration ................................................................... 153
Troubleshooting Configuration .......................................................................... 154
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 on which EPM System products are installed. (EPM System clients do not
require configuration.)
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.
99
Configuration Prerequisites
Subtopics
l Ensuring that Host Names Resolve
l Creating Infrastructure Schemas Using Repository Creation Utility
l Configuration Prerequisites for Financial Close Management
Configuration prerequisite notes:

l When you are deploying on a machine other than the machine hosting Foundation Services,
ensure that WebLogic Server Administration Server is running on the Foundation Services
host machine (FNDHOST1): On the Foundation Services host machine, start WebLogic Server
Administration Server by selecting Start, then All Programs, then Oracle WebLogic, then User
Projects, then EPMSystem, and then Start Admin Server for WebLogic Server.)
l Ensure that host names resolve properly for each machine in the deployment. See Ensuring
that Host Names Resolve on page 101.
l If you want to deploy Java web applications to a single managed server, you must be using
WebLogic Server and have a 64-bit operating system.
l For database configuration tasks, ensure that the database is running.
l On UNIX systems, ensure that ulimit is 4096. You can query for the current ulimit setting
with the following command: ulimit -n.
l If you plan to deploy EPM System products in an SSL-enabled environment, review the
Oracle Enterprise Performance Management System Security Configuration Guide before you
configure. The SSL implementation that you choose affects the options that you select during
configuration. Optionally, you can deploy non SSL and reconfigure to use SSL. See the Oracle
Enterprise Performance Management System Security Configuration Guide.
l If you are using one of the following products, see Creating Infrastructure Schemas Using
Repository Creation Utility on page 101.
m Financial Close Management
m Profitability and Cost Management, and plan to use Oracle Web Services Manager to
automate Profitability and Cost Management tasks
m FDMEE, and plan to use the RuleService/SetupService or plan to integrate FDMEE with
Account Reconciliation Manager, Peoplesoft Commitment Control for Budget Write-
back and Validation, or Fusion Financials for Budget Write-back.
m Financial Management if you are using Web Services.
m Provider Services, if you plan to use Essbase Web Services.
l If you are using Financial Close Management, see Configuration Prerequisites for Financial
Close Management on page 103.
100
Ensuring that Host Names Resolve
Before configuring, ensure that the host name resolves properly for each machine in the
deployment. EPM System uses Javas canonical host name resolution for resolving host names.
To validate host names as resolved by Java, EPM System provides a utility
(epmsys_hostname.bat).
To ensure that host names resolve:

1 Set the JAVA_HOME variable. From a command prompt, enter set JAVA_HOME=pathToJAVA.
For example, for the default location that EPM System Installer uses for Java, enter the following
command: set JAVA_HOME=c:\oracle\middleware\jdk160_35.
2 Unzip epmsys_hostname.zip, in EPM_ORACLE_HOME/common/config/11.1.2.0.
3 From a command prompt, change to the directory to which you unzipped the utility, and then enter the
following command:
epmsys_hostname.bat hostName
4 Review the results in the command line.
For example:
InetAddress details of host hostNameAddress is xx.xxx.xxx.xxxName is hostNameCanonical
Name is hostName.mycompany.com
5 If you see the error Unable to determine the host details, to resolve the host name, create a local
hosts file and add an entry for this server.
Creating Infrastructure Schemas Using Repository Creation

Utility
The Repository Creation Utility (RCU) is used to create multiple schemas to support different
Oracle Fusion Middleware products such as Oracle SOA Suite (SOA) and Oracle Web Services
Manager (OWSM). Some EPM System products use these Middleware technologies, so you
must use RCU to create the required schemas to support the Middleware infrastructure.
If you will be using Oracle Web Services Manager for use with Financial Close Management,
Profitability and Cost Management, FDMEE, Financial Management, Provider Services, or Data
Relationship Management, you must install the Repository Creation Utility (RCU) before
configuring these EPM System products. The RCU creates the required schemas to work with
Oracle Web Services Manager (OWSM). Oracle Web Services Manager is automatically installed,
but not configured, with EPM Workspace.
In addition, Financial Close Management relies on SOA technology and requires RCU to create
the SOA schemas. Use the following procedure to create the required infrastructure for SOA
and OWSM.
To create schemas using the Repository Creation Utility:

1 Download the Repository Creation Utility from the Oracle Enterprise Performance Management System
Media Pack on Oracle EDelivery.
101
2 Navigate to the Installer-RCU folder.
3 Copy rcuHome.zip to the location in which you want to install the Repository Creation Utility, and
extract the contents.
4 From rcuHome/bin, run the Repository Creation Utility using the appropriate file for your operating
system:
l For Windows, run rcu.bat
l For UNIX, run ./rcu
Note: Ignore any messages about using a non-AL32UTF8 database.
The new database schema is required for Metadata Services and does not reflect the EPM
System product databases.
5 Click Create, and then click Next.
6 On the Database Connection Details page, specify a user with DBA or SYSDBA privileges, such as
sys.
7 On the Select Components page, perform these tasks:
l For Financial Close Management, Profitability and Cost Management, FDMEE,
Financial Management, Provider Services, or Data Relationship Management: Expand
AS Common Schemas and select Metadata Services, if it is not already selected.
l Additionally, for Financial Close Management: Expand SOA and BPM Infrastructure
and select the following SOA infrastructure components: SOA Infrastructure and User
Messaging Service. (You need not select Business Activity Monitoring (BAM).)
For Identity Management, OID is selected by default. Do not select Oracle Identity
Federation.
l Make a note of the Schema Owner names for all the components because you need them
to configure Oracle Web Services Manager.
8 On the Schema Passwords page, Oracle recommends that you select Use same passwords for all
schemas. Make a note of this password.
9 On the Summary page, review the selections, and then click Create.
10 On the Completion Summary page, click Close.
For additional information on the Repository Creation Utility, see the Oracle Fusion
Middleware Repository Creation Utility Users Guide 11g Release 1 (11.1.1).
102
Configuration Prerequisites for Financial Close Management
Subtopics
l Installing Oracle SOA Suite
l Configuring and Starting Oracle SOA Suite
Before you can configure Financial Close Management, you must install, configure, and start
Oracle SOA Suite.
Installing Oracle SOA Suite

The following procedure provides an overview of the Oracle SOA Suite installation procedure.
For more information about this procedure, see the Oracle Fusion Middleware Installation
Guide for Oracle SOA Suite 11g Release 1 http://download.oracle.com/docs/cd/E15523_01/doc.
1111/e13925/overview.htm#sthref12. This roadmap contains documentation links for the steps
that follow.
To install Oracle SOA Suite:

1 Ensure that you meet all the prerequisites and system requirements described in the Oracle Fusion
Middleware Installation Guide for Oracle SOA Suite 11g Release 1.
Note: Oracle SOA Suite requires WebLogic Server, which is installed with a default
installation of EPM System.
2 Ensure that you have installed and run the Repository Creation Utility (RCU) to create the required
schemas for Oracle SOA Suite. See Creating Infrastructure Schemas Using Repository Creation Utility
on page 101.
3 Download Oracle SOA Suite from the Oracle Enterprise Performance Management System Media Pack
on Oracle EDelivery, and then install it using the default options. If you have already installed EPM
System products, install to the same Middleware home, for example: Oracle/Middleware.
During installation, use the JDK in the EPM System installation (MIDDLEWARE_HOME/
JDK160_35).
4 When the installation is complete, configure Oracle SOA Suite. See Configuring and Starting Oracle
SOA Suite on page 103.
Configuring and Starting Oracle SOA Suite

Ensure that you have installed Oracle SOA Suite as described in Installing Oracle SOA Suite
on page 103. Before you configure Financial Close Management, you must configure and start
Oracle SOA Suite.
The following procedure provides an overview of the Oracle SOA Suite configuration procedure.
For more information about this procedure, see the Configuring Oracle SOA Suite chapter of
the Oracle Fusion Middleware Installation Guide for Oracle SOA Suite 11g Release 1 http://
download.oracle.com/docs/cd/E15523_01/doc.1111/e13925/configure.htm#CACEEJJJ.
103
To configure Oracle SOA Suite:
1 From the WebLogic Administration Server machine, run the Oracle Fusion Middleware Configuration
Wizard to configure a WebLogic domain, and choose the products that you want to configure in that
domain. To start the Configuration Wizard, from SOA_ORACLE_HOME/common/bin (or
MIDDLEWARE_HOME/oracle_common/common/bin), run config.sh (UNIX) or
config.cmd (Windows).
Note that EPM System and Oracle SOA Suite must be deployed to the same domain. The
choice you make for the domain depends on your deployment scenario:
l In a new deployment, where you have not yet configured EPM System products, you
must create a new WebLogic domain.
l In an existing deployment, where you have already configured EPM System products
and now want to extend the deployment to include Financial Close Management and
Oracle SOA Suite, you must extend the existing WebLogic domain created during EPM
System deployment.
Note the following additional details for this step. Note that not all steps are listed, only
those that require specific selections for Financial Close Management.
l During creating/extending domain, select the following products: Oracle SOA Suite and
all common Oracle components, including Oracle Enterprise Manager, Oracle WSM
Policy Manager, Oracle JRF WebServices Asynchronous Services, and Oracle JRF, if they
are not already selected.
l Select the default JDK. Oracle recommends that you select Production Mode. (When
using Production Mode, when you start WebLogic Administration Server, when you
are prompted to enter a user name and password, enter the user name and password
that you entered during the configuration of the Administration Server domain.)
l When you configure the JDBC datasources, enter the database details that you entered
when you ran RCU.
l Use the default settings for the server port. By default, the Administration Server port
is 7001 and the soa_server1 port is 8001.
2 Start WebLogic Administration Server and the Oracle SOA Suite managed servers using the WebLogic
Administration Console.
l To start the WebLogic Administration Server, run the following command:
MIDDLEWARE_HOME/user_projects/domains/domainName/
startWebLogic.cmd
l To start the SOA Managed Server, run the following command: MIDDLEWARE_HOME/
user_projects/domains/domainName/bin/startManagedWebLogic.cmd
soa_server1.
The Oracle SOA Server must be running before you can configure Financial Close
Management.
104
Tip: SOA setup usually runs on two servers - an Admin Server running on port 7001, which
hosts the Enterprise Management application, and a managed server running on port
8001, which hosts the SOA infrastructure. Log in to http://host:7001/em with your
domain user name and password and check the status of both servers.
See the Financial Close Management (Close Manager and Account Reconciliation Manager)
Installation Checklist on page 71 for the process to follow next.
You must configure EPM System products according to the configuration sequence noted in
Financial Close Management (Close Manager and Account Reconciliation Manager)
Installation Checklist on page 71. Then, perform manual configuration tasks.
Configuration Sequence
Foundation Services must be installed and configured for other products to configure
successfully. In general, for a new deployment, 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.
Upgrade Note!
See Upgrading Checklist on page 209 for details about the configuration sequence when you
are upgrading from an earlier release of EPM System products.
Configuration sequence notes:
l Configure Foundation Services first. Foundation Services must be installed and configured
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.
l Configure the Web server last. (Select the Foundation Services Configure Web Server
task.) Then, restart the Web server and refresh EPM Workspace. If you configured Oracle
HTTP Server to a shared drive, you can simply restart the Web server and refresh EPM
Workspace; you do not have to reconfigure the Web server. See Refreshing EPM
Workspace on page 114.
l Complete the configuration on each machine and close EPM System Configurator before
launching EPM System Configurator on another machine.
l When you configure in a distributed environment, you 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, which lets the machine know the location of the
Shared Services Registry.
l If you deploy any additional products, reconfigure the Web Server and then restart it (or
simply restart it if you configured Oracle HTTP Server to a shared drive) on each machine
hosting Foundation Services.
Then, refresh EPM Workspace on each Foundation Services host machine in your
deployment.
105
See Refreshing EPM Workspace on page 114.
l You must perform the Configure Database task at the same time as or before you perform
the Deploy to Application Server task.
l When configuring Financial Management in a distributed environment, you must install
all IIS Web applications and Java Web applications on the same machine, and perform the
Deploy to Application Server task and the Financial Management Configure Web Server
task on the same machine.
l If you are configuring Financial Close Management, there is a required configuration
sequence. See Financial Close Management (Close Manager and Account Reconciliation
Manager) Installation Checklist on page 71.
l Automatic Web server configuration with EPM System Configurator is supported only for
the Web server installed by EPM System Installer (Oracle HTTP Server or the proxy Web
Server) or IIS.
l You must also run the Financial Management Configure DCOM task if it has not already
been run on the machines hosting Financial Reporting Server, Web Analysis, FDMEE,
Strategic Finance, and FDM.
l After you have completed configuration, perform any required manual configuration tasks
required for your product.
For information about clustering or scaling EPM System, see the Oracle Enterprise Performance
Management System Deployment Options Guide.
Configure the following products after you have completed all the configuration tasks using
EPM System Configurator:
l Data Relationship Management. See the Oracle Data Relationship Management Installation
Guide.
l FDM. The tasks in EPM System Configurator register 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.
Note: If you want to install Essbase in standalone mode (not using Foundation Services), you
can skip the installation for Foundation Services Java web applications. However, you
must still configure the Shared Services Registry. To configure the Shared Services Registry
without installing Foundation Services, you run EPM System Configurator from the
command line using the forceRegistry option. See Setting Up Essbase in Standalone
Mode on page 152.
Configuring Products in a Distributed Environment

Ensure that you meet installation requirements in a distributed environment. See Installing
EPM System Products in a Distributed Environment on page 81. For information about
clustering and high availability, see the Oracle Enterprise Performance Management System
Deployment Options Guide.
106
Configuration considerations in a distributed environment:
l You must configure Foundation Services first. Foundation Services must be installed and
configured for other products to configure successfully. Configure the Web server last.
l Create a new EPM Oracle instance on each machine.
l If you are deploying Java web applications on a machine other than the WebLogic
Administration Server machine, WebLogic Administration Server must be running.
l Deploy all EPM System products to a single WebLogic domain.
The exceptions to this requirement are documented in Deploying Financial Management,
Financial Reporting, and Web Analysis on Windows in a UNIX-Based EPM System
Deployment on page 153.
l During configuration with EPM System Configurator, the Web server machine needs
connectivity to the machine hosting the Shared Services Registry.
l If you are using more than one Web server in a deployment for load balancing and failover,
configure the Web server on every machine on which you want to run the Web server. If
you have more than one Web server, you must use a load balancer (hardware or software)
to route traffic to the servers, and the logical Web address for the Java web application cluster
should be the load balancer. If you have only one Web server, the logical Web address for
the Java web application cluster can be the Web server.
l When configuring EPM System for high availability where multiple instances of services are
running, you must point to the same location on a shared disk in these fields in EPM System
Configurator:
m Lifecycle Management LCM Export Import Location
m Reporting and Analysis Framework Repository Directory
For example, \\SharedHost\SharedLocation\data\RM1
m Essbase Server (UNIX) Full path to application location (ARBORPATH)
For example, \\SharedHost\SharedLocation\data\Essbase
m Performance Scorecard - Configure Attachment Files Location. The path cannot be a
UNC path.
For example, \\SharedHost\SharedLocation\data\HPS
l Optionally, you can configure Oracle HTTP Server to a shared drive to simplify the
configuration process.
Configuring Products in an SSL-Enabled Environment

If you are configuring EPM System products for SSL, the configuration sequence and selections
that you make during configuration depend on the type of SSL implementation you choose. See
the Oracle Enterprise Performance Management System Security Configuration Guide for more
information. Optionally, you can deploy non SSL and reconfigure to use SSL. See the Oracle
Enterprise Performance Management System Security Configuration Guide.
107
Note: Essbase supports only one-way SSL using self-signed certificates by default. Using default
certificates is recommended for use only in a test environment. Oracle recommends that
you use certificates from well-known third party CAs in a production environment. See
the Oracle Enterprise Performance Management System Security Configuration Guide for
details.
Configuring Products for Manual Deployment

If you plan to manually deploy EPM System Java web applications, launch EPM System
Configurator with the /configtool-manual.bat|.sh command. Perform required
configuration tasks except for the Deploy to Application Server task and the Configure Web
Server task. Then, perform additional manual steps.
See Configuring EPM System Products on page 111 and then Chapter 7, Manually Deploying
Configuring Products for WebSphere Application

Server
If you plan to deploy EPM System Java web applications to WebSphere Application Server,
launch EPM System Configurator with the /configtool-manual.bat|.sh command.
Perform required configuration tasks except for the Deploy to Application Server task and the
Configure Web Server task. Then, perform additional manual steps.
See Configuring EPM System Products on page 111 and then Chapter 8, Deploying EPM
System Products to WebSphere Application Server.
Product Configuration Task Summary

Configuration notes:
l EPM System Configurator performs pre-configuration tasks and registers products with
Shared Services during configuration. You need not select these tasks; they are automatically
performed when needed.
l Shared Services Registry database configuration appears once on each machine that you
configure.
l Clients do not require configuration and are not included in these tables.
The following table summarizes the configuration options available for Foundation Services
products.
108
Table 16 Foundation Services Configuration Task Summary
Configure Deploy to Application Server Product-specific Configuration Tasks

Database
Foundation X X l Configure Common Settings

Services
This selection deploys Shared l Configure Oracle Configuration Manager
Services and the EPM Workspace Set up Connection to Oracle BI and Publisher (Optional)
Java web applications.
l
l (Upgrades only) Import data from earlier release

l Configure Web Server
l Configure Logical Address for Web Applications
(Optional)
l Scale out compact server on this machine
Performance X (Windows X X
Management only)
This selection deploys Web Tier and Configure Dimension Server
Architect
Data Synchronizer Java web
applications.
Calculation X X
Manager
The following table summarizes the configuration options available for Essbase products.
Table 17 Essbase Configuration Task Summary
Configure Deploy to Product-specific Configuration Tasks

Database Application Server
Essbase X
Configure Essbase Server
Administration X X X
Services
(Upgrades only) Import data from earlier release
Provider Services X X
(Upgrades only) Import data from earlier release
Essbase Studio X (Required for X

Essbase Studio
Configure Essbase Studio Location for Sample and Customer Data
catalog)
Source Text Files
Integration Services X
Configure Essbase Integration Services
The following table summarizes the configuration options available for Reporting and Analysis
products.
109
Table 18 Reporting and Analysis Configuration Task Summary

Database Application
Server
Reporting and X X X
Analysis
l Configure Reporting and Analysis Services
l Configure Framework Services
l Configure Financial Reporting RMI Ports
l On the servers hosting Financial Reporting Server and Web Analysis, you must
also select the Financial Management Configure DCOM task.
Production X
Reporting
l SQR Production Reporting
The following table summarizes the configuration options available for Financial Performance
Management Applications products.
Table 19 Financial Performance Management Applications Product Configuration Task Summary

Server
Financial X X X
Management (All
Configure DCOM
configuration tasks
l
are Windows only) l Configure Application Server

l Configure Application Cluster
l (Upgrades only) Upgrade applications from earlier release
Planning X X X
Configure RMI Server
Performance X X X
Scorecard
Configure Attachment Files Location
Profitability and X X
Cost Management
Strategic Finance X X
l Configure Port and Data Folder
l WebServices Configuration
l You must also run the Financial Management Configure DCOM task if
it has not already been run on the machines hosting Strategic Finance.
Disclosure X X
Management
110
Server
Financial Close X X X
Management Close
Deploy to SOA
Manager
l
l Configure Content Management System Location (Optional)
Financial Close X X X
Management
Configure Content Management System Location (Optional)
Account
l
Reconciliation l Deploy to SOA for FDM EE

Manager l Deploy to SOA
The following table summarizes the configuration options available for Data Management
products.
Table 20 Data Management Product Configuration Task Summary

Server
FDM X
l Configure FDM Web Application
l Configure FDM Server
been run on the machines hosting FDM.
FDMEE X X X
l Register HFM Adapter
been run on the machines hosting FDMEE.
Configuring EPM System Products

Run EPM System Configurator on each machine 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 20.
Note: On Windows machines, do not use the Administrator user to install and configure.
Run EPM System Installer and EPM System Configurator as a user with administrator
rights. Install, configure and run EPM System Diagnostics as the same user for all EPM
System products. If you are using Windows 2008, configure with UAC disabled. UAC
must be disabled to install, configure, and run EPM System products. UAC can be enabled
on end-user client desktops.
111
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. On UNIX machines, for all Oracle
products, the user that is installing must be part of the same group; the group must have
write permission to the central inventory (oraInventory).
Note: When you upgrade or apply the maintenance release, install and configure using the same
user that was used to install and configure the earlier release.
To configure EPM System products:

1 Choose a method to launch EPM System Configurator:
l On the last page of EPM System Installer, click or select Configure.
l From the Start menu, select Programs, then Oracle EPM System, and then EPM System
Configurator (all instances).
l Change to EPM_ORACLE_HOME/common/config/version_number and then launch
configtool.bat (.sh).
l To run EPM System Configurator in console mode, launch it from the command line
using the console parameter. For example EPM_ORACLE_HOME/common/config/
version_number/startconfigtool.bat -console.
l For silent configurations, see Performing Silent Configurations on page 150.
l If you are manually deploying Java web applications, launch EPM System Configurator
from the command line using EPM_ORACLE_HOME/common/config/
version_number/configtool-manual.bat (.sh).
After configuration is complete, see Chapter 7, Manually Deploying EPM System Java
Web Applications for more information.
l If you are deploying to WebSphere Application Server, launch EPM System
Configurator from the command line using EPM_ORACLE_HOME/common/config/
version_number/configtool-manual.bat (.sh).
After configuration is complete, see Chapter 8, Deploying EPM System Products to

WebSphere Application Server..
Tip: If you launch EPM System Configurator from EPM_ORACLE_INSTANCE, EPM

System Configurator configures the existing EPM Oracle instance and does not display
the Configure Oracle Instance page.
EPM System Configurator performs initial checks, checking for the following:
l Environment variables are set
l .oracle.products is present
l All required .jars are present
l Windows system32 is in the PATH
112
l There is a valid EPM Oracle home
l When Essbase in installed, that OPMN is also installed on the machine
l When Financial Management is installed, that the Authentication Level for DCOM is
set correctly.
2 Review and complete each page of EPM System Configurator, clicking or selecting Next to move to the
next page.
In console mode, enter the number beside the selection you want.
The following table provides links where you can find more details about each page of EPM
Page Reference
Oracle Instance Configure Oracle Instance on page 115
Task selection Task Selection on page 116
Set Up Shared Ensure that the database is started and that you have created a database.
Services and
If you have not already created the database, see Preparing a Database on page 41.
Registry
Database Enter the information as described in Set Up Shared Services and Registry Database Connection on page
Connection 125.
Configure Ensure that the database is started and that you have created a database.
database
Enter the information as described in Configure Database on page 117.
Application Enter the information as described in Deploy to Application Server: Oracle WebLogic on page 121.
server
deployment
Product-specific For detailed procedures to configure each product, see the sections:
configuration
Foundation Configuration Tasks on page 123
tasks
l
l Performance Management Architect Configuration Tasks on page 132

l Essbase Configuration Tasks on page 132
l Reporting and Analysis ConfigurationTasks on page 137
l Planning Configuration Tasks on page 139
l Financial Management Configuration Tasks on page 139
l Performance Scorecard Configure Attachment Files Location on page 147
l Strategic Finance Configuration Tasks on page 147
l Financial Close Management Configuration Tasks on page 148
l FDM Configuration Tasks on page 150
3 (Optional) To save the configuration selections in a response file for silent configuration, click or select
Save, browse to a location, specify a file name, and click or select Save.
This procedure creates an editable file that can be used as a response file for silent
configuration. See Performing Silent Configurations on page 150.
4 Confirm the configuration tasks to complete, and then click or select Next.
113
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 EPM_ORACLE_INSTANCE/diagnostics/logs/config/configtool.log.
When configuration finishes, the status of each task is displayed. Configuration results are
noted in EPM_ORACLE_INSTANCE/diagnostics/logs/config/
configtool_summary.log.
5 Click or select Task Panel to return to the Task Selection page to complete additional configuration
tasks.
6 Configure the Web Server last.
7 Click or select Finish.
If configuration is successful, perform any required manual configuration tasks, start
services, and validate service startup.
See Chapter 9, Performing Manual Configuration Tasks in a New Deployment,,
Chapter 12, Starting and Stopping EPM System Products and Chapter 13, Validating the
Installation and Verifying Deployment.
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.
l See the Oracle Enterprise Performance Management System Installation and Configuration
Troubleshooting Guide for information about resolving configuration issues.
l If you see errors related to the Oracle HTTP Server installation, ensure that you have
met the Oracle HTTP Server installation prerequisites. See Web Server Installation
Prerequisites on page 78.
l If Oracle Configuration Manager is not available during configuration, EPM System
Configurator shows that the Configure Oracle Configuration Manager task failed.
When the Oracle Configuration Manager is available, restart EPM System Configurator
and select the Configure Oracle Configuration Manager task.
8 Refresh EPM Workspace.
If you are using Financial Close Management, see the Financial Close Management (Close
Manager and Account Reconciliation Manager) Installation Checklist on page 71 for the
process to follow next.
Refreshing EPM Workspace

If you deploy any additional products, reconfigure the Web Server and then restart it (or simply
restart it if you configured Oracle HTTP Server to a shared drive) on each machine hosting
Foundation Services.
114
Then, refresh EPM Workspace on each Foundation Services host machine in your deployment.
To refresh EPM Workspace:

1 Start a browser session.
2 Access EPM Workspace by accessing the following URL:
http://FNDHOST1:9000/workspace/refresh
In this URL, use port 9000, which is the managed server port where EPM Workspace is
available, not the Oracle HTTP Server port.
3 At the Login screen, enter admin and the deployment password.
You should get a success message.
4 Repeat these steps on each Foundation Services host machine in your deployment.
EPM System Configurator Task Reference

Subtopics
l Configure Oracle Instance
l Task Selection
l Configure Database
l Deploy to Application Server Specify WebLogic Domain Information
l Deploy to Application Server: Oracle WebLogic
l Foundation Configuration Tasks
l Performance Management Architect Configuration Tasks
l Essbase Configuration Tasks
l Reporting and Analysis ConfigurationTasks
l Planning Configuration Tasks
l Financial Management Configuration Tasks
l Performance Scorecard Configure Attachment Files Location
l Strategic Finance Configuration Tasks
l Financial Close Management Configuration Tasks
l FDMEE Configuration Tasks
l FDM Configuration Tasks
Configure Oracle Instance

Specify a new or an existing EPM Oracle instance for the deployment.
EPM System Configurator deploys dynamic components of EPM System products (components
that can change during run-time) in the EPM Oracle instance directory. The default EPM Oracle
instance location is MIDDLEWARE_HOME/user_projects/epmsystem1.
115
Typically, if you are installing all products on a single machine, for the first product you
configure, create a new EPM Oracle instance. For each product after that, modify the existing
EPM Oracle instance.
If you are installing in a distributed environment, create a new EPM Oracle instance on each
machine.
You can scale up or scale out by installing and configuring additional instances. See the Oracle
Enterprise Performance Management System Deployment Options Guide.
The following table describes options for EPM Oracle Instance configuration.
EPM System Description Your

Configurator Information
Home directory Specify the directory in which to create the EPM Oracle instance. The default EPM Oracle instance
for EPM Oracle location is MIDDLEWARE_HOME/user_projects. To modify an existing EPM Oracle instance,
instances browse to the EPM Oracle instance location.
EPM Oracle Specify a name for the EPM Oracle instance. The default EPM Oracle instance name is
Instance name epmsystem1. To modify an existing EPM Oracle instance, specify the EPM Oracle instance
name.
Task Selection
Select the products and tasks to configure for this machine, or click or select Next to select
all the required tasks.
Task selection notes:

l In a new installation, all required tasks are selected by default.
l You can clear tasks that you want to perform later.
l Select Check All or Uncheck All to select or clear all tasks.
l You cannot clear mandatory tasks, which are selected by default. If the task is unavailable
(grey) and selected (checked), the task is performed and you cannot clear it.
l EPM System Configurator automatically performs 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 locate Shared Services.
l The EPM Workspace Java web application and the Shared Services Java web application are
deployed when you select the Hyperion Foundation Deploy to Application Server task.
116
Configure Database
Specify the database settings to use for the products that you selected on the Task Selection
page. You can specify database connection information for each product separately, or use
the same settings for multiple selected products.
For ease of deployment and simplicity, for a new installation, you can use one database for all
products. 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. Oracle recommends that Close Manager and Account Reconciliation Manager use the
same database schema.
Database configuration notes:
l Ensure that the database is set up.
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 Enterprise Performance
Management System Certification Matrix (http://www.oracle.com/technetwork/
middleware/ias/downloads/fusion-certification-100350.html) for a list of supported
databases for each product.
l If you are configuring an additional instance of Financial Management, Performance
Management Architect, or FDMEE for scaleout purposes, during database configuration,
when you are prompted whether to drop and re-create the tables or reuse the existing
database, select Reuse the existing database.
l If you are configuring an Oracle database, EPM System Configurator checks that the
database was created with the correct character set. If not, you are prompted to correct it.
l The schemas for the EPM System databases are documented and are available in a ZIP file
(EPM Data Models Release 11.1.2.3) posted in the Oracle Documentation Library (http://
www.oracle.com/technology/documentation/epm.html) on Oracle Technology Network,
on the Deployment and Installation tab.
Upgrade Note!
Note the following about database configuration if you are upgrading:
l Select Upgrade the existing databases to the current release from... and select the release
number.
l If you are upgrading, and you have been using Oracle Hyperion Business Rules, you must
perform prerequisite tasks for migrating business rules before you configure. See Business
Rules Maintenance Release and Upgrade Installation Prerequisites on page 213. EPM
System Configurator migrates the rules to Calculation Manager rules during database
configuration. The rules are exported to EPMData/planning/hbrRules.xml.
The following table describes options for database configuration.
117
Configurator Fields Information
Database Type Select the database type.
Upgrade the existing Upgrade Note!

databases to the current
If you are upgrading from an earlier release, select Upgrade the existing databases to the
release from...
current release from... and then select the release.
Note: This task assumes that you have created the database. If you have not created a
database, see Preparing a Database on page 41
Product Name Select the product or products for which to specify database connection information.
Changes you make apply to all selected products.
Server For each product, specify the name of the computer or server hosting the database.
For Oracle RAC, specify the VIP name or one of the node names as the server name.
Port For each product, select the default or specify a custom server port number on which the
database listens.
Service Name or SID, or For each product, specify the name of the database.
Database Name
If you are using an Oracle RAC database, specify the RAC service name.
During configuration of Financial Management with Oracle Database, EPM System
Configurator configures Financial Management to use the Oracle Database clients that were
installed with EPM System Configurator and updates the tnsnames.ora entry using a fixed
name.
User Name For each product, enter the database user name.
Password For each product, enter the database user password.
Advanced database Click or select to specify additional information for selected products. See Advanced Options
options for selected rows for Database Configuration (Optional) on page 119.
(Optional)
You can use this option to configure Oracle RAC or to use an LDAP-based JDBC URL. Any
values you enter on the Advanced Database Options page override the values entered on
the main Database Configuration page.
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 the Oracle Enterprise Performance Management System Certification Matrix
(http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-
certification-100350.html).
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
118.
Setting Up Microsoft SQL Server Windows Authentication
To set up Windows authentication for a SQL Server connection:

1 Configure SQL Server to use Windows authentication.
118
2 Grant your Windows account appropriate access to your database.
3 From the configuration task list, select Configure Database.
4 From the database list, select SQL Server.
5 Specify all database information except for Username and Password.
You must also specify a domain user for Windows services on the Common Settings page of
EPM System Configurator, in Run Windows Services as non-local system account. See Configure
Common Settings on page 123.
Advanced Options for Database Configuration (Optional)

The following table describes advanced options for database configuration.

Edit and use modified Select to specify a JDBC URL for the database connection.
JDBC URL
JDBC URL Enter additional attributes for the database connection.

If you enter a JDBC URL, it overrides the values that you entered in the Configure Database
page.
For an Oracle database, you can enter an LDAP-based JDBC URL.
See Appendix B, JDBC URL Attributes for more information.
Use secure connection to Select to enable secure communication to the database.

the database (SSL)
To use an SSL-enabled JDBC connection, you must also enter specific parameters.
See Appendix B, JDBC URL Attributes for more information.
See the Oracle Enterprise Performance Management System Security Configuration
Guide to see whether selecting this option is appropriate for your SSL implementation.
Trusted Keystore Enter or browse to the location of the keystore.
Trusted Keystore Enter the password for the keystore.

Password
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.
Index Tablespace To specify the database tablespaces in which the indexes are created, select the index
location.
119
Deploy to Application Server Specify WebLogic Domain
Information
Specify information about the WebLogic domain to which to deploy the Java web
applications.
You deploy all EPM System products to one domain.
Note: If you are using Financial Close Management, EPM System and Oracle SOA Suite must
be deployed to the same domain. If you have already configured Oracle SOA Suite, deploy
EPM System products to the same domain.
If you are deploying EPM System products to a domain hosted on another machine and
the domain was not created with EPM System Configurator, you must make manual
updates to jps-config.xml and system-jazn.xml on the Administration Server box.
See step 19 on page 157 and step 20 on page 161 of Chapter 7, Manually Deploying
The following table describes options to define the WebLogic Server domain.
EPM System Configurator Fields Description Your

Information
Deploy Web applications to an Specify whether to deploy Java web applications to an existing domain or to a new
existing domain/Deploy Web domain.
applications to a new domain. The
If you create a new domain, the WebLogic Administration Server for this domain
Administration Server for this
is created on this machine.
domain will be created on this
machine.
Domain Name To define a new domain, enter a domain name. The default domain name is
EPMSystem.
To deploy to an existing domain, specify the domain to use for deployment.
Administration Server Host For an existing domain, specify the Administration Server Host.
Administration Server Port Accept the default port; or, to change the default, enter a port number that does
not conflict with other applications installed on your machine.
Administrator User Enter the Administrator user name for the domain. By default, EPM System
Configurator uses epm_admin.
Administrator Password Enter the Administrator password or enter a new password for a new domain.
Tip: Make a note of this password.
Confirm Administrator Password If you are defining a new domain, confirm the Administrator password.
120
Deploy to Application Server: Oracle WebLogic
Specify the application server options, or click or select Next to accept the default entries.
The following table describes options for WebLogic application server deployment
configuration.
Deploy all EPM System products to a single WebLogic domain. The exceptions to this
requirement are documented in Deploying Financial Management, Financial Reporting, and
Web Analysis on Windows in a UNIX-Based EPM System Deployment on page 153.

Fields
Deploy the web Select this option for a deployment to a single managed server.
applications to a
If you select this option, all selected Java web applications are deployed to a single managed
single managed
server in WebLogic.
server
This option is available only:
l When you are creating a new domain or extending an existing domain created in EPM System
Configurator Release 11.1.2.3 on the machine hosting WebLogic Administration Server.
l When you are vertically scaling to the same machine and the same domain and there is an
existing single managed server.
l When you are applying a maintenance release installation, unless you deployed to a single
managed server in the earlier release, you must redeploy the Java web applications on all
machines in the deployment. Then, you can restart EPM System Configurator and select this
option.
To add products to a single managed server on a machine other than the machine hosting
Foundation Services, select Scale out compact server on this machine.
Deploying Java web applications to a single managed server reduces memory requirements and
reduces startup time. You can have only one single managed server in an EPM System deployment.
You can scale out the single managed server.
When you select this option, all managed server names are changed to EPMServer0, and all
ports are changed to 9000 or 9443 (SSL). If you change a port, it is reflected in all the rows.
If you deselect this option after it is selected, the port values revert to the default individual ports;
and if already configured to a different port, the values revert to the user-provided ports.
Ear/War Select the components to deploy.
Managed Server Displays the WebLogic Managed Server name.

Name
Port 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 Appendix A, Ports.
121
Fields
SSL Port Accept the default port or specify the SSL port to use for deployment. Specifying this port sets up
SSL using the Java application server's default certificates. See the Oracle Enterprise Performance
Management System Security Configuration Guide for recommendations on updating the Java
application server with a valid certificate.
If you are using SSL, you must disable the non-SSL port (or redirect it to the SSL port) in your Java
application server after configuration to ensure secure communication.
Status Indicates the deployment status
Deployment notes:
l Deploy all products to a single domain.
l To specify the logical address the products use to connect to the Java web application server,
use the Update Logical Address for Web Applications task. Select this task when the Java
web applications do not communicate with the Java web application server directly, as in
the following scenarios:
m You have set up a cluster with a load balancer.
m You are using an SSL offloader.
See Configure Logical Address for Web Applications on page 127.

l By default, EPM System Configurator deploys 32-bit binaries to 32-bit application servers
on 32-bit operating systems, and 64-bit binaries to 64-bit application servers on 64-bit
operating systems.
l The EPM Workspace Java web application and the Shared Services Java web application are
deployed when you select the Hyperion Foundation Deploy to Application Server task.
l If you are implementing a custom authentication module, you must include its Java archive
(.jar) in the EPM Product classpath. See the Oracle Enterprise Performance Management
System Security Configuration Guide for detailed procedures to implement a custom
authentication module.
What Happens During Deployment: WebLogic Server

Deployment notes:
l EPM System Configurator deploys each application to the WebLogic Server domain you
specified. For a new domain, the domain is created when the first application is deployed.
Each application runs in a separate JVM, except for Shared Services, and EPM Workspace,
which run together and are deployed to the same managed server, or if you deploy multiple
Java web applications to a single managed server.
l EPM System Configurator deploys the applications to MIDDLEWARE_HOME/
user_projects/domains/domainName.
l EPM System Configurator deploys Oracle Enterprise Manager automatically when it
deploys the first Java web application.
122
l Start and stop scripts are created in EPM_ORACLE_INSTANCE/bin/.
l For each application, in EPM_ORACLE_INSTANCE/bin/deploymentScripts there is a
setCustomParamsProduct.bat file (.sh extension for UNIX), where you can change
JAVA_OPTIONS when using start scripts.
l EPM System Configurator creates a cluster for each managed server.
Foundation Configuration Tasks

Subtopics
l Configure Common Settings
l Set Up Shared Services and Registry Database Connection
l Configure Logical Address for Web Applications
l Configure Oracle Configuration Manager
l Set up Connection to Oracle BI EE and Publisher
l Set Shared Services Admin User and Password
l Scale Out Compact Server on This Machine
l Foundation Services Import Data From Earlier Release
Configure Common Settings
Specify settings for all products on all machines that have been identified in the Shared
Services Registry so far, or click or select Next to accept the default values.
The Configure Common Settings page appears once per EPM System deployment.
If you configure on another machine and change any of these options, your new selections apply
for all products and machines that you have not configured. If you reconfigure on a machine,
the new settings apply to any products that you reconfigure and to future configurations.
The following table describes options for common settings configuration.

Create Windows Services Select to configure each service as a Windows service that starts automatically when you
for configured start Windows.
components (Windows
only)
123
Run Windows Services Select to specify a non-local system account to configure Windows services, and then specify
as non-local system a user name and password. This user should be a member of the Administrators group.
account
Note: Oracle recommends that you select this option. If you are using Reporting and Analysis
in a distributed environment, you must update the service to run as a user who has read-
write access to the shared data folder.
If you do not select this option, EPM System Configurator creates Windows services using the
local system account. Before you start the services, change them to use the appropriate
domain account
User name Enter the user name for the user to launch the Windows services. If you leave this field blank,
EPM System Configurator creates the services using the local system account.
Password Enter the password for the user used to launch Windows services.
Use SSL for Web Depending on your SSL implementation, select to use SSL communication for all Java web
application server applications. If this option is selected, URLs are in the form https.
communications
Note: Selecting this option does not enable secure communication for the Java web
(requires manual
application server and does not create and load certificates into JREs and JDKs. See Oracle
configuration)
Enterprise Performance Management System Security Configuration Guide for more
information.
Optionally, you can deploy non SSL and reconfigure to use SSL. See the Oracle Enterprise
Performance Management System Security Configuration Guide.
Mail Server Host 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.
Port Specify the mail server port number or accept the default value. If you are using SSL to
communicate with the mail server, enter an SSL port.
Administrator's Email Specify the administrator's e-mail address to use for notifications.
Address
Use SSL to communicate Select to use SSL communication for all e-mail communication.
with mail server
Use authentication to Specify whether the mail server requires authentication, and then specify a user name and
send email password.
User Name Specify the user name for the SMTP server.
Password Specify the password for the SMTP server.
124
LCM Export Import Enter the location from which to export and import Lifecycle Management artifacts.
Location
If you have a clustered environment and plan to use Lifecycle Management to migrate
artifacts, specify a shared drive location. The shared location must be accessible to all Shared
Services instances. When artifacts are exported using Lifecycle Management, the content is
exported to a path on a shared disk; when imported, the content is read from the exported
location on the shared disk.
For example, to specify a shared drive location on Windows, enter \\sharedHost
\sharedLocation; on UNIX, enter: /sharedHost/sharedLocation.
After configuration, restart all instances of Shared Services.

For each instance, start Shared Services as a service using the login of a domain user who
has access to the shared disk/folder.
Set Up Shared Services and Registry Database Connection
Specify the settings for the Shared Services and Registry database.
When you initially configure EPM System products, you configure a database for use by
Foundation Services, which includes the Shared Services Registry.
When you configure the Shared Services and Registry 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.
If you are configuring an Oracle database, EPM System Configurator checks that the database
was created with the correct character set. If not, you are prompted to correct it.
For a list of supported databases, see the Oracle Enterprise Performance Management System
Certification Matrix (http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-
certification-100350.html).
For database prerequisites for this release, see Preparing a Database on page 41.
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 118.
For more information about the Shared Services Registry, see About the Shared Services
Registry on page 20.
Note: This task assumes that you have created the database. If you have not created a database,
see Preparing a Database on page 41.
If you uninstall EPM System products and then reinstall into the same location, you cannot
reuse the Shared Services and Registry database.
125
Upgrade Notes!
l If you are upgrading from an earlier release, select Perform first-time configuration of Shared
Services database and enter database connection information for a new database.
l If you are upgrading from Release 11.1.1.4, and you configured all EPM System products to
use one database, you are alerted that pre-existing Shared Services tables have been detected
in the database. When prompted to drop and recreate the tables, select Yes.
Note: If you are applying the maintenance release to move from Release 11.1.2.0, 11.1.2.1, or
Release 11.1.2.2 to Release 11.1.2.3, select Connect to a previously configured Shared
Services database.
The following table describes options for Shared Services and Registry Database configuration.

Connect to a previously When you first configure the Shared Services and Registry database, choose Perform first-
configured Shared time configuration of Shared Services database. This database includes the Shared
Services database/ Services Registry, which is used to store common information for all products.
Perform first-time
When you configure in a distributed environment, you must configure the Shared Services
configuration of Shared
database on every machine. On the first machine, you are setting up the Shared Services
Services database
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.
Upgrade Note!
If you are upgrading from an earlier release, select Perform first-time configuration of
Shared Services database and enter database connection information for a new
database.
If you are applying the maintenance release to move from Release 11.1.2.0, 11.1.2.1, or
Release 11.1.2.2 to Release 11.1.2.3, select Connect to a previously configured Shared
Services database and select a release number.
Database Type Select the database type.
Server Specify the name of the database server where the Shared Services database should be
created.
For Oracle RAC, specify the VIP name or one of the node names as the server name.
Port Select the default or specify a custom Shared Services server port number on which the
database listens.
Service Name or SID, or Specify the name of the Shared Services database.
Database Name
If you are using an Oracle RAC database, specify the RAC service name.
User Name Enter the name of the database user.
Password Enter the password of the database user.
126
Advanced options Click or select to specify additional information.

(Optional)
For more information on these options, see Advanced Options for Database Configuration
(Optional) on page 119.
You can use this option to configure Oracle RAC or an LDAP-based JDBC URL.
Configure Logical Address for Web Applications
Specify the logical address details to use for Java web applications, or click or select Next to
accept the defaults:
Use this option to change the logical address for a deployed Java web application, for example
if you are using a load balancer. This task lets you change the logical address without redeploying
the Java web application. You can select this task during initial Java web application deployment.
Note: You need to perform this task on only one machine in the deployment.
The following table describes options for configuring the logical addresses to use for Java web
applications.

Fields
Set the logical Select whether to apply the same address to all Java web applications or to apply a different address
Web address for to each Java web application
all the Web
applications to /
Set the logical
Web address for
each Web
application
individually to
Product Shows the components for which a Java web application is deployed
Component
Host For each enabled module, review the host name to which this Web server proxies requests.
Port Review or update the port numbers for the application server listen ports for the applications. The
port here must match the listen port of the deployed application.
SSL Port Review or update the SSL port of the logical Web address.
If you are using SSL, you should disable the non-SSL port (or redirect it to the SSL port) in your
Java application server after configuration to ensure secure communication.
127
Fields
Context Review the context path. The context path is the part of the URL that accesses the deployed Java
web application. For example, in the following URL, workspace is the context path:
http://webserverhost.example.com:19000/workspace
Note: Use fully qualified host names for all entries. For example,
webserverhost.example.com.
Configure Oracle Configuration Manager
Specify the contact information to use for notifications from My Oracle Support and Oracle
Configuration Manager.
Oracle Configuration Manager collects machine configuration information and installed Oracle
software information on a regular basis and uploads it to My Oracle Support. Click or select
View Details for more information.
EPM System Configurator displays this page on the first machine you configure and uses the
values for each additional machine in the deployment.
If you want to change the options or update the password, use the Oracle Configuration
Manager tools in EPM_ORACLE_HOME/ccr/bin.
The following table describes options for registering for Oracle Configuration Manager.
EPM System Configurator Fields Description Your Information
Email Enter the E-mail address to use for notifications from MyOracle
Support.
View Details Click or select View Details to see information about Oracle Support
policies.
I wish to receive security updates via My Specify whether you want to receive security updates.
Oracle Support
My Oracle Support password Enter your My Oracle Support password.
Note: EPM System Installer installs Oracle Configuration Manager for you in
EPM_ORACLE_HOME/ccr.
For more information about Oracle Configuration Manager, see http://docs.oracle.com/cd/

E24625_01/index.htm.
128
Set up Connection to Oracle BI EE and Publisher
Use this task for integrating EPM Workspace with Oracle BI EE Release 10.1.3.4.2+. Before
performing this configuration task, see the Oracle Enterprise Performance Management System
Deployment Options Guide for prerequisite tasks and manual configuration tasks.
To integrate EPM Workspace with Oracle BI EE Release 11.1.1.7, see Configuring for
Integration with EPM Workspace in the Oracle Fusion Middleware System Administrator's
Guide for Oracle Business Intelligence Enterprise Edition (http://docs.oracle.com/cd/E28280_01/
bi.1111/e10541/toc.htm).
Specify the configuration information for EPM Workspace to work with Oracle BI EE and
BI Publisher.
You must reconfigure the Web server after you perform this task. If the Web server is on this
machine, select Configure Web Server at the same time you select Connection to Oracle BI EE and
Publisher.
The following table describes options for configuring EPM Workspace to work with Oracle BI
EE and BI Publisher.
EPM System Configurator Description Your Information

Fields
Set up Oracle BI EE
Host Specify the host where Oracle BI EE is installed.
Port Specify the port on which Oracle BI EE listens.
SSL Port If you are using SSL, specify the SSL port.
URL Context Review the context path. The context path is the part of the URL that accesses the
deployed Java web application. The default value is /analytics.
Set up Oracle BI Publisher
Host Specify the host where BI Publisher is installed.
Port Specify the port on which Oracle Business Intelligence Publisher listens.
SSL Port If you are using SSL, specify the SSL port.
URL Context Review the context path. The context path is the part of the URL that accesses the
deployed Java web application. The default value is /xmlpserver.
Set Shared Services Admin User and Password
For hardened security, reset the password for the Shared Services admin user. Optionally,
specify an admin name other than the default, admin.
EPM System Configurator creates a preprovisioned user (called admin by default), which enables
you to log on to Shared Services after configuration to create and provision users. EPM System
129
Configurator requires you to specify a new admin password during configuration. After
configuration, make subsequent changes to the admin user password in the Shared Services
Console. See the Oracle Enterprise Performance Management System Security Configuration
Guide.
The following table describes options for resetting the Shared Services admin user password.
EPM System Description Your Information

Configurator Fields
Admin Name Optionally, specify a name other than the default name admin for the Shared Services
administrator user.
Password Enter a new password for the Shared Services admin user.
Tip: Make a note of this password.
Re-type Password To confirm the new password, re-enter the password for the Shared Services admin user.
Scale Out Compact Server on This Machine

If you have deployed EPM System Java web applications to a single managed server, use this
option to scale out the server.
The Scale out compact server on this machine option is only available when the following are
true:
l The WebLogic Administration Server is not installed on the current machine.
l The single managed server is deployed on the WebLogic Administration Server.
l The single managed server is not already scaled out on the machine.
See Scaling Out a Single Managed Server in the Oracle Enterprise Performance Management
System Deployment Options Guide.
Configure Web Server
Specify Web server information, or click or select 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 deploy any additional products, reconfigure the Web Server and then restart it (or simply
restart it if you configured Oracle HTTP Server to a shared drive) on each machine hosting
Foundation Services.
Then, refresh EPM Workspace on each Foundation Services host machine in your deployment.
See Refreshing EPM Workspace on page 114.
Note: Enabling SSL for the Web server requires manual configuration. See the Oracle Enterprise
Performance Management System Security Configuration Guide.
130
The following table describes options for the Web server configuration.

Fields
Web Server Type Select the Web server.

To manually configure a Web server, select Setup Registry for manual web server configuration.
See Manually Configuring Oracle HTTP Server on page 165 for details on manually configuring a
Web server.
Web Server Port Specify the Web server port. If you use SSL, ensure that the port number that you enter is a secure
port.
HTTP Server Specify or browse to the location of the Web server.

Location
If you are using Oracle HTTP Server, you can configure to a shared drive location to simplify
configuration in a distributed environment. Click Advanced Options and then specify the shared drive
location. This shared location must be accessible from all web servers in the deployment and must
a UNC path, not a mapped drive.
Note: If you are deploying components to both Windows and UNIX, and if Oracle HTTP Server is on
both, you cannot configure to a shared drive; you must configure to a local drive.
Set the logical Select this option if you want EPM System Configurator to set the logical Web address for all Java
web address for web applications to the Web Server. Use this option if you want to use the Web server as the load
the web balancer.
applications to
If you do not select this option, EPM System Configurator uses the address of the physical Java web
this web server
application as the logical address.
Component Review the components for which the Web server is being configured.
Foundation Services Import Data From Earlier Release

This option is available only if you are upgrading from an earlier release. If you are not upgrading,
skip this section. You must have already exported Shared Services data from the earlier release
to complete this task.
Upgrade Note!
If you are upgrading from an earlier release, specify the location from which to import Shared
Services data. You must specify the full path to hssmigratedata.zip, which is created
with the Shared Services Upgrade Utility.
If you have not yet exported Shared Services data from the earlier release, see Exporting Shared
Services Data from the Earlier Release on page 215.
Select this task only if you also select or have already completed the Deploy to Application
Server task for Foundation Services.
For more information about what happens during this configuration task, see What Happens
During Shared Services Data Import on page 233.
131
Performance Management Architect Configuration Tasks
Configure Dimension Server
Specify the following options to configure Dimension Server ports, or click or select Next to
accept the defaults.
The following table describes options for Dimension Server port configuration.
Dimension Server Port Specify the port to use, or click or select Next to keep the default port.
Dimension Server .JNI Bridge Port Specify the port to use, or click or select Next to keep the default port.
Essbase Configuration Tasks

Subtopics
l Configure Essbase Server
l Configure Essbase Integration Services
l Configure Essbase Studio Location for Sample and Customer Data Source Text Files
l Administration Services Import Data From Earlier Release
l Provider Services Import Data From Earlier Release
Configure Essbase Server
Specify the configuration information for Essbase Server, or click or select Next to accept the
default settings. In general, Oracle recommends that you keep the default settings. However,
if you are upgrading from an earlier release of Essbase, for Full path to application location
(ARBORPATH), specify the existing location or the replicated location of the Essbase
application directory. The default location might not be correct.
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 ARBORPATH/bin). In addition, it specifies
environment variables in a file used to launch Essbase Server.
The following table describes the configuration options for Essbase Server.
132
Table 21 Essbase Server Configuration

Fields
Essbase Cluster Specify a cluster name to create a cluster to provide active-passive Essbase failover support with
Name write-back capabilities. You can include only two Essbase instances in a cluster.
When you configure the first instance of Essbase on the first machine, you define the cluster. When
you configure the second instance of Essbase on the second machine, select Assign to Existing
Cluster, select the cluster, and then click OK to add this Essbase Server to the cluster you created
on the first machine.
The Essbase cluster name must be unique in a deployment environment. It cannot contain special
characters or spaces.
See Configuring Active-Passive Essbase Clusters (Windows) or Configuring Active-Passive
Essbase Clusters (UNIX) in the Oracle Enterprise Performance Management System Deployment
Options Guide.
Agent Port Number Accept the default port number on which the Essbase listens for client requests. If you change the
default value, enter a port number that is not used by other programs.
Select Active to enable the agent to listen on this port.
SSL Agent Port Specify the SSL port on which Essbase listens for client requests.
Number
Select Active to enable the agent to listen on this port.
Start Port Accept the default number or enter the first port number on which the Essbase Server listens for
client requests.
The port value is stored in essbase.cfg (in ARBORPATH/bin).
End Port Enter the greatest 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.
Full path to The location for applications.

application
You can specify the path using universal naming convention (UNC) format. Oracle recommends
location
using UNC if you are configuring Essbase for high availability on UNIX.
(ARBORPATH)
Note: Previous versions of Essbase used ARBORPATH to refer to the installation location.
If you are setting up an Essbase cluster on UNIX, the application location must be a shared drive
or a UNC path. When you configure the second machine in the cluster, the location must match the
location you specified for the first machine in the cluster.
Upgrade Note!
If you are upgrading from an earlier release of Essbase, specify the existing location or the replicated
location of the Essbase application directory. The default location might not be correct.
133
Fields
Set the language to The ESSLANG variable is a locale definition. For example, to support American English, set ESSLANG
be used by to English_UnitedStates.Latin1@Binary.
Essbase
Based on the value you specify, EPM System Configurator updates setEssbaseEnv.bat (in
(ESSLANG)
EPM_ORACLE_INSTANCE/EssbaseServer/essbaseserver1/bin) with the ESSLANG
value and Essbase uses this value.
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), 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 134.
For the full list of supported ESSLANG values, see Oracle Essbase Database Administrator's
Guide.
Deploy Essbase in Select to use legacy security for Essbase Server instead of Shared Services security.
standalone mode
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
non-English languages, 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.
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.
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.
134
Note: If the ESSLANG variable is changed after applications are created on an Essbase Server
computer, those applications cannot be started.
To avoid possible database corruption, the ESSLANG locale specification must be the same on
client and Essbase Server in the following situations:
l The client is not Unicode-enabled.
l A Unicode-enabled client saves an outline over an existing outline on a version of the Essbase
Server that is not Unicode-enabled.
l A Unicode-enabled client saves an outline to a non-Unicode application on a Unicode-
enabled 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.
Configure Essbase Integration Services

This configuration task adds the Integration Services start script to the single EPM System start
script; however, no EPM System Configurator pages appear, and you need not enter information.
Select Configure Essbase Integration Services from the Task Selection page and proceed
through EPM System Configurator.
Configure Essbase Studio Location for Sample and Customer Data Source
Text Files
Specify the location to be used for sample file installation or for text files that will be used
as data sources, or click or select Next to accept the default.
The following table describes options for Essbase Studio Location for Sample and Customer
Data Source Text Files configuration.

Fields
Server datafile Specify the location to be used for sample file installation or for text files that will be used as data
location sources. By default the location is EPM_ORACLE_INSTANCE/BPMS/bpms1/datafiles.
Upgrade Note!
If you are upgrading from an earlier release, specify the existing location or the replicated location
for the Essbase Studio data files.
135
Administration Services Import Data From Earlier Release
skip this section. You must have already prepared data from the earlier release to complete this
task.
Upgrade Note!
If you are upgrading from an earlier release, specify the location from which to import
Administration Services data.
If you have not yet prepared data from the earlier release for upgrading, see Copying Files for
Temporary Use During Configuration on page 217.
This task is available only if you also select or have already completed the Configure Database
task for Administration Services.
During configuration, this data is moved to the Shared Services Registry and the files are no
longer used.
Provider Services Import Data From Earlier Release

skip this section. You must have already prepared data from the earlier release to complete this
task.
Upgrade Note!
If you are upgrading from an earlier release, specify the location from which to import
Provider Services data.
If you have not yet prepared data from the earlier release for upgrading, see Copying Files for
Temporary Use During Configuration on page 217.
This task is available only if you also select or have already completed the Deploy to Application
Server task for Provider Services.
During configuration, this data is moved to the Shared Services Registry and the files are no
longer used.
136
Reporting and Analysis ConfigurationTasks
Subtopics
l Configure Reporting and Analysis Framework Services
l Configure Reporting and Analysis Framework Agent Ports
l SQR Production Reporting
Note: On the Financial Reporting Server machine, you must also select the Financial
Management Configure DCOM task.
Configure Reporting and Analysis Framework Services
Specify the following Reporting and Analysis Framework service information, or click or
select Next to accept the defaults:
The following table describes options for Reporting and Analysis Framework Services
configuration.

Fields
Repository Specify the directory where the Reporting and Analysis repository data is stored; for example: EPM_
Directory ORACLE_INSTANCE/ReportingAnalysis/data/RM1.
If you are configuring for high availability, the repository directory must be a writable shared drive. All
Reporting and Analysis instances must use the same shared file system location, for example: \
\SharedHost\SharedLocation\data\RM1
Note: If you are running this service as a Windows service, use a UNC path instead of a mapped
drive. Doing so prevents potential permissions errors than can occur when Windows attempts to create
a mapped drive at startup.
Upgrade Note!
If you are upgrading from an earlier release, specify the existing location or the replicated location for
the Reporting and Analysis repository.
Port Range Specify the port range to use for Reporting and Analysis Framework services.
Configure Reporting and Analysis Services
Specify the following options to configure Interactive Reporting services, or click or select
Next to accept the defaults.
The following table describes options for Interactive Reporting service configuration.
137
Configurator Fields
Port Range Specify the range of ports to use, or click or select Next to keep the default port
ranges.
Configure Financial Reporting RMI Ports
Specify the following options to configure the Financial Reporting RMI port range, or click
or select Next to accept the defaults.
The following table describes options for Financial Reporting RMI port configuration.

Configurator Fields
Port Range Specify the range of ports to use, or click or select Next to keep the default port
ranges.
Configure Reporting and Analysis Framework Agent Ports
Specify the following options to configure Reporting and Analysis Agent ports, or click or
select Next to accept the defaults.
The following table describes options for Reporting and Analysis Framework Agent port
configuration.
Agent Port Specify the port to use, or click or select Next to keep the default port ranges.
Agent RMI Port Specify the port to use, or click or select Next to keep the default port ranges.
SQR Production Reporting

This task creates shortcuts for Production Reporting; however, no EPM System Configurator
page appears, and you need not enter information.
138
Select SQR Production Reporting from the Task Selection page and proceed through EPM
Planning Configuration Tasks
Configure Planning RMI Server
Specify the following options to configure the Planning RMI Server port, or click or select
Next to accept the defaults.
The following table describes options for Planning RMI Server port configuration.
Port Specify the port to use, or click or select Next to keep the default port.
Financial Management Configuration Tasks

Subtopics
l Financial Management Configure DCOM
l Financial Management Configure Application Server
l Financial Management Configure Cluster
l Financial Management Configure Web Server
l Financial Management Configure Web Application
l Financial Management Enable Smart View Provider
l Financial Management Enable Life Cycle Management Provider
l Financial Management Enable Web Services
l Web Server Configuration Advanced Options
l Financial Management Upgrade Applications from Earlier Release
You must run EPM System Configurator as an administrator to configure Financial

Management.
Financial Management Configure 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.
139
Note: You must run as a Domain or Local Administrator with Group Policies rights to configure
the DCOM user.
Because all Financial Management application server processes are run under an administrator
identity (the specified Windows admin user), 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.

Fields
Domain User Specify the user name.

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: " / \ [ ] : ; | = ,
+*?<>&
l 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.
l 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 Enter the password again to confirm it.

Password
Enable DCOM Select to enable DCOM on this machine.

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 for Windows 2003 to None and for Windows 2008 to Connect. 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
l 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.
140
l 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.
l Sets the DCOM Run as identity for all Financial Management application processes
l 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
Configurator to re-enter the DCOM user name and password. Perform this task on the Web
tier and on the Services tier for Financial Management.
Financial Management Configure Application Server
Specify the application server information, or click or select Next to accept the defaults.
The following table describes options for Financial Management application server
configuration.

Max App Server Accept the default value or enter the time interval in seconds between when a change is made
Delay to an application and when the change is visible to users accessing the application through
another application server.
Max Data Sync Accept the default value or enter the time interval in seconds between when a change is made
Delay to data and when the change is visible to users accessing the data through another application
server.
Database Specify the number of maximum pooled relational database connections for the application.
Connection Pool Financial Management requires approximately 25 relational database connections per
Size application.
For more information about pooled database connections, see Appendix C, Database
Information for Financial Management.
DME Listener Port Specify the port to use, or click or select Next to keep the default port.
Financial Management Configure 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 cluster configuration.
141
Fields
Defined Clusters 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.
When you add a cluster, specify the cluster name, and select Use Sticky Server if you want to direct
all requests for a specific session to the same server.
Upgrade Note!
This list displays all clusters that you configured in the earlier 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 earlier release.
Available Select the server that you want to include in the cluster, and click or select Add.
Servers
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.
Servers in the The list displays all servers in the currently selected cluster. To remove a server from the list, select it
Cluster and click or select Remove.
Upgrade Note!
If you installed the upgraded version on a new server, make sure to add the upgraded server name
to the cluster and remove the earlier release server.
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.
Financial Management Configure Web Server
Select the components that you want to enable as IIS web applications in IIS or click or select
Next to accept the default.
Financial Management ASP.NET Web service is deployed as part of Financial Management Web
Server configuration.
The following table describes options for Financial Management Web server configuration.
142
EPM System Configurator Description Your
Fields Information
Configure IIS for Financial Select to enable Financial Management as an IIS web application in IIS, and then
Management Web specify the options for the Financial Management Web server. See Financial
Application Management Configure Web Application on page 143.
Configure IIS to Enable Smart Select to enable Smart View as an IIS web application in IIS, and then specify the
View Provider options for the Smart View Web server. See Financial Management Enable Smart
View Provider on page 144.
Configure IIS to Enable Select to enable Lifecycle Management as an IIS web application in IIS. See Financial
Lifecycle Management Management Enable Life Cycle Management Provider on page 144.
Configure IIS to Financial Select to enable the Financial Management Web Services IIS web application in IIS.
Management Web Services See Financial Management Enable Web Services on page 145.
Web Session Timeout Accept the default or specify the timeout in minutes.
This value applies to all the Financial Management IIS web applications in IIS.
Financial Management Configure Web Application
Configure the Web server for Financial Management or click or select Next to accept the
defaults.
The following table describes options for Financial Management Web application configuration.

Web Server Accept the default or enter or browse to the path for the Financial Management Web installation
Installation Directory directory.
Note: The default location is the directory in which the Web components were installed; for
example: EPM_ORACLE_HOME/products/FinancialManagement/Web/HFM.
Virtual Directory Accept the default or enter the virtual directory name; for example: HFM.
Name
Advanced Options Click or select Advanced Options to specify additional options for the Web server
configuration.
See Financial Management Web Application Advanced Options on page 143.
Financial Management Web Application Advanced Options
Specify additional options for the Financial Management Web application.
The following table describes advanced options for Financial Management Web application
configuration.
143
Fields
Max Upload File Enter a maximum size for loading Web files.
Size
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 MB, you change the setting for maximum upload file
size to 200,000,000 bytes.
Response Buffer Enter a maximum size for extracting Web files.

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

Web Server Enter the location in which Smart View was installed or use the default location.
Installation Directory
Note: The default location is EPM_ORACLE_HOME/products/
FinancialManagement/Web/HFMOfficeProvider.
Virtual Directory Name Enter the virtual directory name for Smart View, or use the default virtual directory.
The default directory name is HFMOfficeProvider.
Advanced Options Click or select to specify advanced options for Smart View configuration. See Web Server
Configuration Advanced Options on page 145.
Financial Management Enable Life Cycle Management Provider
Configure the Web server for Lifecycle Management.
The following table describes options for Financial Management Lifecycle Management
configuration.
144
Web Server Installation Enter the location in which Lifecycle Management was installed, or use the default
Directory location.
FinancialManagement/Web/HFMLCMService.
Virtual Directory Name Review the virtual directory name for Lifecycle Management.
The default directory name is hfmlcmservice.
Advanced Options Click or select to specify advanced options for Lifecycle Management configuration. See Web
Server Configuration Advanced Options on page 145.
Financial Management Enable Web Services
Configure the Web server for Financial Management Web Services.
The following table describes options for Financial Management Web Services configuration.

Web Server Enter the location in which Financial Management Web Services was installed, or use the
Installation Directory default location.
FinancialManagement/Web/HFMApplicationService.
Virtual Directory Name Review the virtual directory name for Financial Management Web Services.
The default directory name is hfmapplicationservice.
Advanced Options Click or select to specify advanced options for Financial Management Web Services
configuration. See Web Server Configuration Advanced Options on page 145.
Web Server Configuration Advanced Options
Specify additional options for the Smart View, Lifecycle Management, and Financial
Management Web Services Web server configuration.
The following table describes the advanced options for Smart View, Lifecycle Management, and
Financial Management Web Services Web server configuration.
145
Max Upload File Size Enter a maximum size for loading Web files.
(Web services only)
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 MB, 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.
(Web services only)
Enable HTTP Specify whether to enable compression for communication between the Web browser and
Compression the Web application.
By default, compression is on.
Enable Proxy Server If you use a proxy server between the Web server and client, select this option and set a time
Keep Alive interval, in seconds, for the connection.
Keep Alive Interval (in If you use a proxy server between the Web server and client, select this option and set a time
seconds) interval, in seconds, for the connection.
Always warn when client Select to warn of a newer add-in version.

version is newer (Smart
View Provider only)
Always force client to Select to upgrade to the latest add-in version to ensure client and server version
upgrade (Smart View compatibility.
Provider only)
Financial Management Upgrade Applications from Earlier Release

skip this section.
Upgrade Note!
Select Upgrade Applications from Earlier Release from the Task Selection page and proceed
through EPM System Configurator.
Note that there is no EPM System Configurator page for this task and you need not enter
information.
This task is available only if you also select or have already completed the Configure Database
and Configure Financial Management DCOM tasks for Financial Management.
During the execution of this task, EPM System Configurator upgrades Financial Management
applications from the earlier release to the current release.
146
Performance Scorecard Configure Attachment Files
Location
Accept the default location to access Performance Scorecard files or specify a new directory,
and then select or click or select Next.
The following table describes Performance Scorecard configuration options.

Fields
Performance Accept the default location, or specify a different directory to access Performance Scorecard
Scorecard - files.
Configure
Files are stored in EPM_ORACLE_INSTANCE/HPS/hpsfiles but if you want to use a symbolic
attachment files
link or drive mapping to the storage location, enter the symbolic link name or drive map path
location
here.
If you are configuring for high availability, you must specify a shared drive location.
For example, \\SharedHost\SharedLocation\data\HPS
Upgrade Note!
If you are upgrading from an earlier release, specify the existing location or the replicated location
for the Performance Scorecard files.
Strategic Finance Configuration Tasks

Subtopics
l Strategic Finance Configure Port and Data Folder
l Strategic Finance Configure Web Services
Strategic Finance Configure Port and Data Folder
Specify the location of the Strategic Finance data directory, or click or select Next to accept
the default.
The following table describes options for Strategic Finance configuration.

Data Directory Accept the default, or specify the location for Strategic Finance data.
Location
Upgrade Note!
If you are upgrading from an earlier release of Strategic Finance, specify the existing location
or the replicated location of the data directory for the earlier release.
147
Service Port Accept the default port, or specify a Strategic Finance service port.
Strategic Finance Configure Web Services
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 Description Your Information

Fields
Enable Web Service 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.
Strategic Finance Server Accept the default, or specify the Strategic Finance server to associate with.
Financial Close Management Configuration Tasks

Subtopics
l Configure Content Management System Location (Optional)
l Deploy to SOA
l Deploy to SOA for FDM EE
Configure Content Management System Location (Optional)

If you have an existing content management system, you can configure Financial Close
Management to link to the documents stored in it.
Specify the location of a Document Management System to use.
The following table describes options for Financial Close Management custom settings
configuration.
148
Fields
URL Enter the URL of the system hosting the Document Management system.
For example for Release 10g, enter:
http://host:port/
For example for Release 11g, enter:

http://host:port/_dav/cs/
See the Oracle Enterprise Performance Management System Certification Matrix (http://www.oracle.
com/technetwork/middleware/ias/downloads/fusion-certification-100350.html) for information
about supported document management systems.
Deploy to SOA
Note that this configuration task has a required configuration sequence.
See Financial Close Management (Close Manager and Account Reconciliation Manager)
Installation Checklist on page 71 for more information.
Select Deploy to SOA from the Task Selection page and proceed through EPM System
Configurator. You must restart WebLogic Administration Server after completing this task.
information.
If you configured a mail server host on the Common Settings page of EPM System Configurator,
during the execution of the Deploy to SOA task EPM System Configurator uses that
information to configure the SOA email driver.
During the execution of this task, EPM System Configurator embeds information about these
products in the SOA component and then deploys the SOA composites:
l FDM
l Financial Reporting
Deploy to SOA for FDM EE

This task is required only if you are using Account Reconciliation Manager. The task is available
only if you have installed and configured FDMEE.
Note that this configuration task has a required configuration sequence. See Financial Close
Management (Close Manager and Account Reconciliation Manager) Installation Checklist on
page 71 for more information.
149
Select Deploy to SOA for FDM EE from the Task Selection page and proceed through EPM
System Configurator. You must restart WebLogic Administration Server after completing
this task.
information.
FDMEE Configuration Tasks

Select Register HFM Adapter from the Task Selection page and proceed through EPM System
Configurator.
No EPM System Configurator page appears, and you need not enter information.
FDM Configuration Tasks

Subtopics
l Configure FDM Server
l Configure FDM Web Application
These tasks update the Shared Services Registry with information about FDM and register FDM
with Shared Services; however, no EPM System Configurator pages appear, and you need not
enter information. See the Oracle Hyperion Financial Data Quality Management Configuration
Guide for additional information about configuring FDM.
Configure FDM Server
Select Configure FDM Server from the Task Selection page and proceed through EPM System
Configurator.
Configure FDM Web Application
Select Configure FDM Web Application 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.
150
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.
Note: If you are performing a silent configuration using Remote Desktop, run it using an admin
console session. (Launch Remote Desktop using mstsc /admin).
To record configuration settings and run a silent configuration:

1 Navigate to the directory that contains EPM System Configurator. By default, the directory is
EPM_ORACLE_HOME/common/config/version_number.
2 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 need not 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:
EPM_ORACLE_HOME/common/config/version_number/configResponse.xml.
3 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 page
to continue with more configuration tasks.) If you return to the Task Selection page,
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 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.
5 From the command line, enter a command:
configtool.bat -silent filename or ./configtool.sh -silent filename.
The configuration runs in the background.
You can also record configuration settings from within EPM System Configurator. To record
configuration settings, during configuration, on the Configuration Confirmation page, click or
select Save, browse to a location, specify a file name, and click or select Save. The file is saved in
the same format as for silent configurations.
151
Upgrade Note!
Silent response files are not compatible between earlier releases and Release 11.1.2.3. If you
created silent response files for use with any earlier release of EPM System, you must re-create
them for use with EPM System Release 11.1.2.3.
You can modify the response file later to change configuration options.
If you are configuring a vertically scaled environment, you do not need separate silent response
files with unique ports if you add the following entry to the response file:
<auto_port_tick>true</auto_port_tick>
You can use the same silent response file in different environments even when each environment
has a different set of passwords for the database, WebLogic, and the Shared Services Admin user.
For security reasons, in the generated silent file, password values are stored in encrypted format
but EPM System Configurator also supports unencrypted format. Oracle recommends that you
change the password properties for Database, WebLogic, and Shared Services in the silent file
to the following format:
Database Password
<property name="password" encrypt="true">clearTextPasword</property>
Weblogic Admin Password in applicationServerDeployment section

<property name="adminUser">epm_admin</property>
<property name="adminPassword" encrypt="true">clearTextPasword</property>
Shared Services Admin Password in bean name="customConfiguration" for Foundation

<property name="adminUserName">admin</property>
<property name="adminPassword" encrypt="true">clearTextPasword</property>
Copy a version of the file for each environment and replace clearTextPassword with the
appropriate password for that environment. After executing the silent file for each environment,
for security reasons, if the file is writable by EPM System Configurator, the password is stored
in the file in an encrypted format.
Setting Up Essbase in Standalone Mode

If you want to install Essbase in standalone mode (not using Shared Services), you can skip the
installation for Foundation Services Java web applications. However, you must still configure
the Shared Services Registry database. To configure the Shared Services Registry database
without installing Foundation Services Java web applications, 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 Foundation Services.
To configure the Shared Services Registry without installing Foundation Services Java web
applications:
1 Start EPM System Configurator from the command line, including the forceRegistry option:
152
l From a Windows console, change to EPM_ORACLE_HOME/common/config/
version_number, and then enter configtool.bat forceRegistry.
l On UNIX, change to EPM_ORACLE_HOME/common/config/version_number and
then enter ./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

2 Proceed through the configuration, entering the database details for the Shared Services Registry.
Note: If you set up Essbase in standalone mode and want to switch to Shared Services mode,
use Administration Services. See Oracle Essbase Administration Services Online Help.
Deploying Financial Management, Financial Reporting,

and Web Analysis on Windows in a UNIX-Based EPM
System Deployment
All Java web applications in an EPM System deployment must be deployed on either all Windows
machines or on all UNIX machines. However, if your Java web applications are deployed on
UNIX, you must deploy Financial Management, Financial Reporting, and Web Analysis Java
web applications on Windows using EPM System Configurator, deploying to a separate domain
on Windows. This is required because Financial Management runs only on Windows, and
Financial Reporting and Web Analysis support Financial Management as a data source only on
Windows.
What Happens During Configuration

During product configuration, EPM System Configurator completes these actions:
l Performs the configuration tasks that you selected
l Configures each product to start as a Windows service, if you select this option on the
Configure Common Settings page during configuration
l Creates a default Shared Services Administrator role in Native Directory when you configure
Foundation 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.
l If you are configuring products on Windows 2008 that require IIS, EPM System
Configurator automatically installs Windows server roles for IIS if they are not already
153
installed. On Windows Server 2003, you are prompted for the installation CD or the path
to Windows Server 2003 files to install the required IIS files.
Troubleshooting Configuration
Configuration results are noted in EPM_ORACLE_INSTANCE/diagnostics/logs/config/
configtool_summary.log.
If you encounter errors, perform these tasks:

l Configure products individually.
l See the Oracle 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.
Tip: EPM System Configurator provides a script, ziplogs, in EPM_ORACLE_INSTANCE/bin.

You can run this script to provide files to Support for troubleshooting installation and
configuration issues. This tool collects all log files, including logs for installation,
configuration, and validation and registry reports if you have used those tools, and saves
them in ZIP file in EPM_ORACLE_INSTANCE/diagnostics/ziplogs.
154
Manually Deploying EPM
7 System Java Web Applications
In This Chapter
Assumptions and Prerequisites......................................................................... 155
Manually Deploying Java Web Applications .......................................................... 155
Manually Configuring Oracle HTTP Server.............................................................. 165
For detailed information about managing Java web applications with WebLogic Server, see
http://download.oracle.com/docs/cd/E15523_01/wls.htm.
Assumptions and Prerequisites

l You are an experienced Java web application server administrator. If you are not an
experienced Java web application server administrator, you should automatically configure
and deploy EPM System Java web applications using EPM System Configurator.
l You have installed EPM System products using EPM System Installer on all machines in the
environment.
Manually Deploying Java Web Applications

To manually deploy EPM System Java web applications:
1 Launch EPM System Configurator using the following command and perform all required configuration
tasks except for the Configure Web Server task. Note that the Deploy to Application Server task is
not available.
Windows:
EPM_ORACLE_HOME/common/config/
version_number/configtool-manual.bat
UNIX:
version_number/configtool-manual.sh
Launching EPM System Configurator with this command hides the Java web application
deployment tasks and skips the product registration with Shared Services task.
155
See Chapter 6, Configuring EPM System Products in a New Deployment.
2 Repeat step 1 on each machine in a distributed environment.
3 Launch the Fusion Middleware Configuration Wizard: From the command line, change the directory to
MIDDLEWARE_HOME/oracle_common/common/bin and launch config.cmd (Windows) or
config.sh (UNIX).
4 Select Create a New WebLogic Domain and then click Next.
Note: All EPM System products must be deployed to the same domain. If you have already
deployed EPM System products, select Extend an Existing WebLogic Domain.
Additionally, if you are using Financial Close Management, EPM System and Oracle
SOA Suite must be deployed to the same domain. If you have already configured
Oracle SOA Suite, deploy EPM System products to the same domain by selecting
Extend an Existing WebLogic Domain.
A list displays all the Java web applications installed in the Middleware home. For EPM
System products, the list is generated from the configuration templates that were installed
during installation with EPM System Installer.
5 Select Generate a domain configured automatically to support the following products, then select
the EPM System Java web applications you want to deploy, and then click Next.
Oracle recommends that you simultaneously configure all Java web applications.
6 Enter the domain name and location and then click Next.
By default, the domain location is MIDDLEWARE_HOME/user_projects/domains.
7 Enter a user name and password for the domain administrator, and a domain description, and then
click Next.
8 Select a WebLogic domain startup mode (Development or Production), specify which JDK to use, and
then click Next.
You must select Production mode. Oracle recommends that you select the default JDK.
9 Configure the JDBC data sources, and then click Next.
For each Java web application, specify the database connection information that you entered
during database configuration with EPM System Configurator.
If you configured different databases for different products, enter database connection
information separately for each Java web application. Select the Java web application, and
then enter the connection information.
Tip: EPMSystemRegistry is the Shared Services and Registry database.
The Configuration Wizard tests the database connection.

10 Review the Connection Result log, and then click Next.
156
11 For Managed Servers, Clusters and Machines, on the Configure Managed Servers panel, review the
default listen ports and optionally change them. See Appendix A, Ports for a list of default ports.
Note: If you change the ports from the defaults, you must also change them in the stop
scripts located in MIDDLEWARE_HOME/user_projects/domains/EPMSYstem/
bin.
12 For a distributed deployment, for Managed Servers, Clusters and Machines, on the Configure
Machines panel, create a machine for each machine in the deployment.
13 For each managed server, assign the managed server to a machine.
14 (Optional) For Managed Servers, Clusters and Machines, on the Configure Clusters panel, you can
set up a cluster. You can also set up a cluster after you've completed the deployment. For details on
Java web application server clustering, see Clustering Java Web Applications in a WebLogic Manual
Deployment in the Oracle Enterprise Performance Management System Deployment Options Guide.
15 Review the Configuration Summary, and then click Create to create the domain and deploy the Java
web applications.
Java web applications are deployed in offline mode.
16 For a distributed deployment:
a. Start the Node Manager on each machine in the deployment.
b. On the WebLogic Administration Server machine, pack the domain that you created.
c. Copy the pack to each machine in the deployment.
d. Unpack on each machine in the deployment.
WebLogic Server unpacks all Java web applications on each machine in the deployment. On
each machine, it runs the managed servers that you associated with the machine.
17 In a distributed deployment, on each machine other than the machine hosting WebLogic Administration
Server, navigate to the domain location and change the current the EPM Oracle instance name (for
example, epmsystem1) to the actual EPM Oracle instance name for that instance (for example,
epmsystem2) in all files.
18 On the machine hosting WebLogic Administration Server, start WebLogic Administration Server and
navigate to the WebLogic Administration Console. Check that the Node Manager for each machine in
the deployment is reachable. If not: synchronize Node Managers using nmEnroll command.
19 Open MIDDLEWARE_HOME/user_projects/domains/domainName/config/
fmwconfig/system-jazn-data.xml in a text editor, and after the last </grant> line in the file,
add the following: (Note that these changes are also required if you deployed EPM System products to
a domain hosted on another machine and the domain was not created with EPM System Configurator.)
Oracle provides EPM_ORACLE_HOME/common/config/11.1.2.0/resources/
deployment/xml/custom-jazn-data.xml.
<?xml version='1.0' encoding='utf-8'?>

<custom-jazn-data>
<jazn-policy>
<grant>
<grantee>
157
<codesource>
<url>file:${EPM_ORACLE_HOME}/common/CSS/11.1.2.0/lib/css.jar</url>
</codesource>
</grantee>
<permissions>
<permission>
<class>oracle.security.jps.service.policystore.PolicyStoreAccessPermis
sion</class>
<name>context=APPLICATION,name=*</name>
<actions>getApplicationPolicy</actions>
</permission>
</permissions>
</grant>
<grant>
<grantee>
<codesource>
<url>file:${EPM_ORACLE_HOME}/common/jlib/11.1.2.0/lib/registry-
api.jar</url>
</codesource>
</grantee>
<permissions>
<permission>
<class>oracle.security.jps.service.credstore.CredentialAccessPerm
ission</class>
<name>context=SYSTEM,mapName=epm_sys_reg_cred_map,keyName=*</name>
<actions>read,write,update,delete</actions>
</permission>
</permissions>
</grant>
<grant>
<grantee>
<codesource>
<url>file:${EPM_ORACLE_HOME}/common/raframeworkrt/11.1.2.0/lib/
annotation.jar</url>
</codesource>
</grantee>
<permissions>
<permission>
ission</class>
<name>context=SYSTEM,mapName=repository_cred_map,keyName=*</name>
</permission>
</permissions>
</grant>
<grant>
<grantee>
<codesource>
<url>file:${EPM_ORACLE_HOME}/products/Essbase/eas/server/lib/
eascsf.jar</url>
</codesource>
</grantee>
<permissions>
<permission>
ission</class>
158
<name>context=SYSTEM,mapName=CSF_EAS_MAP,keyName=*</name>
</permission>
</permissions>
</grant>
<grant>
<grantee>
<codesource>
<url>file:${common.components.home}/modules/
oracle.wsm.agent.common_11.1.1/wsm-agent-core.jar</url>
</codesource>
</grantee>
<permissions>
<permission>
<class>oracle.wsm.security.WSIdentityPermission</class>
<name>resource=SHAREDSERVICES</name>
<actions>assert</actions>
</permission>
</permissions>
</grant>
<grant>
<grantee>
<codesource>
</codesource>
</grantee>
<permissions>
<permission>
<name>resource=SHAREDSERVICES(11.1.2.0)</name>
</permission>
</permissions>
</grant>
<grant>
<grantee>
<codesource>
</codesource>
</grantee>
<permissions>
<permission>
<name>resource=FCCTaskExecutionComposite</name>
</permission>
</permissions>
</grant>
<grant>
<grantee>
<codesource>
</codesource>
</grantee>
159
<permissions>
<permission>
<name>resource=FinancialClose</name>
</permission>
</permissions>
</grant>
<grant>
<grantee>
<codesource>
</codesource>
</grantee>
<permissions>
<permission>
<name>resource=FINANCIALCLOSE</name>
</permission>
</permissions>
</grant>
<grant>
<grantee>
<codesource>
</codesource>
</grantee>
<permissions>
<permission>
<name>resource=AccountReconciliation</name>
</permission>
</permissions>
</grant>
<grant>
<grantee>
<codesource>
</codesource>
</grantee>
<permissions>
<permission>
<name>resource=ACCOUNTRECONCILIATION</name>
</permission>
</permissions>
</grant>
<grant>
<grantee>
<codesource>
<url>file:${soa.oracle.home}/soa/modules/oracle.soa.workflow_11.1.
160
1/bpm-services.jar</url>
</codesource>
</grantee>
<permissions>
<permission>
<class>oracle.security.jps.JpsPermission</class>
<name>IdentityAssertion</name>
<actions>*</actions>
</permission>
</permissions>
</grant>
<grant>
<grantee>
<codesource>
</codesource>
</grantee>
<permissions>
<permission>
<class>oracle.security.jps.JpsPermission</class>
<name>VerificationService.createInternalWorkflowContext</name>
</permission>
</permissions>
</grant>
<grant>
<grantee>
<codesource>
</codesource>
</grantee>
<permissions>
<permission>
ission</class>
<name>credstoressp.credstore.BPM-CRYPTO.BPM-CRYPTO</name>
<actions>read,write</actions>
</permission>
</permissions>
</grant>
</jazn-policy>
</custom-jazn-data>
20 Open MIDDLEWARE_HOME/user_projects/domains/domainName/config/
fmwconfig/jps-config.xml in a text editor and make the following changes. (Note that these
changes are also required if you deployed EPM System products to a domain hosted on another machine
and the domain was not created with EPM System Configurator.
l To the <serviceInstances> set in the document, add the following:
<serviceInstance provider="jaas.login.provider" name="idstore.loginmodule">
<description>Identity Store Login Module</description>
<property
value="oracle.security.jps.internal.jaas.module.idstore.IdStoreLoginModule"
name="loginModuleClassName" />
<property value="REQUIRED" name="jaas.login.controlFlag" />
161
<property value="true" name="debug" />
<property value="true" name="addAllRoles" />
</serviceInstance>
Modify the existing <serviceInstances> idstore.ldap to add the

virtualize property:
<serviceInstance provider="idstore.ldap.provider" name="idstore.ldap">
...
<property name="virtualize" value="true"/>
</serviceInstance>
</serviceInstances>
l To the <jpsContexts default="default"> section, add the following:
<serviceInstanceRef ref="idstore.loginmodule" />
21 (Optional) To simplify the startup of WebLogic servers, edit the boot.properties file on every server
in the domain to provide the domain user and password. This file is located in MIDDLEWARE_HOME/
user_projects/domains/domainName/servers/product/security.
Oracle provides processBootProperties.* scripts to generate boot properties for all
managed servers.
Note: Note that these inputs are stored in clear text until the servers are started, after which
this data is encrypted by WebLogic.
22 Create symlinks using the following commands:
UNIX:
"ln -s SOURCE_FILE TARGET_FILE"
Windows 2008:
"cmd /c mklink TARGET_FILE SOURCE_FILE"
For the following files:

l "EPM_ORACLE_HOME/common/SharedServices/11.1.2.0/lib/audit-
client.jar" to "EPM_DOMAIN_HOME/lib/audit-client.jar"
l "EPM_ORACLE_HOME/common/SharedServices/11.1.2.0/lib/wlpool.jar" to
"EPM_DOMAIN_HOME/lib/wlpool.jar"
l "EPM_ORACLE_HOME/common/CSS/11.1.2.0/lib/css.jar" to
"EPM_DOMAIN_HOME/lib/css.jar"
l "EPM_ORACLE_HOME/common/CSS/11.1.2.0/lib/ldapbp.jar" to
"EPM_DOMAIN_HOME/lib/ldapbp.jar"
l "EPM_ORACLE_HOME/common/jlib/11.1.2.0/registry-api.jar" to
"EPM_DOMAIN_HOME/lib/registry-api.jar"
l "EPM_ORACLE_HOME/common/jlib/11.1.2.0/ctg_custom.jar" to
"EPM_DOMAIN_HOME/lib/ctg_custom.jar"
l "EPM_ORACLE_HOME/common/misc/11.1.2.0/opencsv-1.8.jar" to
"EPM_DOMAIN_HOME/lib/opencsv-1.8.jar"
162
23 Start the WebLogic Administration Console and then start the managed servers.
Note that when you manually deploy Java web applications, use the start scripts in
DOMAIN_HOME/bin.
You can start Java web applications on all machines using the Weblogic Administration
Console. To do so, you must first run MIDDLEWARE_HOME/oracle_common/common/
bin/setNMProps.sh(cmd) to modify nodemanager.properties.
Additionally, StartScriptEnabled must be set to true (for example,

StartScriptEnabled=true) in MIDDLEWARE_HOME/wlserver_10.3/common/
nodemanager/nodemanager.properties to start Java Web applications on all
machines.
During the managed server startup, the Shared Services Registry is updated with values for
the EPM System Java web applications you deployed.
24 Stop all EPM System Java web applications.
25 Perform manual steps for Financial Close Management:
Go to EPM_ORACLE_INSTANCE/bin and run the following commands:
epmsys_registry.bat addproperty #APP_SERVER_ID/@adminUser ADMIN_USER
epmsys_registry.bat addencryptedproperty #APP_SERVER_ID/@adminPassword
ADMIN_PASSWORD
Where APP_SERVER_ID is the ID of the WebLogic AppServer component in the Shared

Services Registry.
For more information about editing the Shared Services Registry, see Updating the Shared
Services Registry in the Oracle Enterprise Performance Management System Deployment
Options Guide.
26 Launch EPM System Configurator using the following command and select the Configure Web Server
task.
Windows:
version_number/configtool-manual.bat
UNIX:
version_number/configtool-manual.sh
EPM System Configurator performs the registration with Shared Services and Configure
Web Server tasks.
If you are also want to configure Essbase while you are manually deploying Java web
applications, when you first ran configtool-manual.sh, the Configure Essbase Server
task was not available. It is available in this second pass of configuration, so if needed, select
it now.
27 For Financial Close Management: Start WebLogic Administration Server and then the SOA managed
server. Then, start EPM System Configurator and select Deploy to SOA for Close Manager, and Deploy
to SOA and Deploy to SOA for FDM EE for Account Reconciliation Manager.
163
28 If you are using FDMEE, perform additional manual steps. See Additional Postdeployment Steps for
FDMEE on page 164.
29 If you using Oracle Web Services Manager, perform additional manual steps. See Configuring JMS
Servers on page 165.
30 Start all EPM System services and Java web applications. When you manually deploy Java web
applications, use the start scripts in DOMAIN_HOME/bin.
Tip: You can also start Java web applications on all machines using the Weblogic
Administration Console. To do so, you must first run MIDDLEWARE_HOME/
oracle_common/common/bin/setNMProps.sh(cmd) to modify
nodemanager.properties.
To validate the installation and verify deployment, see Chapter 13, Validating the
For clustering, see Clustering Java Web Applications in a WebLogic Manual Deployment
in the Oracle Enterprise Performance Management System Deployment Options Guide.
Tip: If you need to redeploy a Java web application after you have successfully deployed, replace
the EAR file, delete the tmp folder for the managed server, and then start the application.
For information about clustering Java Web applications in a manual deployment, see the Oracle
Additional Postdeployment Steps for FDMEE

If you are manually deploying FDMEE, perform the following procedures after you deploy to
configure Oracle Data Integrator with FDMEE.
To complete the FDMEE deployment:

1 Stop all EPM System Java Web applications.
2 Start WebLogic Administration Console and log in.
3 Target odiMasterRepository and odiWorkRepository datasources to ErpIntegrator.
4 Save changes.
5 Navigate to MIDDLEWARE_HOME/oracle_common/common/bin and launch wlst.cmd|sh.
6 Execute the following commands:
connect(adminUser, adminPassword, adminUrl)
createCred(map="oracle.odi.credmap", key="SUPERVISOR", user="SUPERVISOR",
password="SUNOPSIS", desc="ODI SUPERVISOR Credential")
createCred(map="oracle.odi.credmap", key="ODI-DOMAIN", user=adminUser,
password=adminPassword, desc="ODI-DOMAIN Credential")
.
164
Where adminUser and adminPassword are the WebLogic administrator user and
password and adminUrl is the WebLogic Admin URL.
7 Start the FDMEE Java web application.
Configuring JMS Servers

If you are using Financial Management Web Services, FDMEE, or Financial Close Management,
you must configure JMS Servers when you manually deploy web applications.
To configure JMS Servers:

1 Stop all managed servers.
2 From a command prompt, navigate to MIDDLEWARE_HOME/wlserver_10.3/server/bin and
run setWLSEnv.cmd|.sh.
3 Run the following command:
MIDDLEWARE_HOME/oracle_common/webservices/bin/jrfws-async-createUDDs.py --domain_home
domain_home_directory --cluster your_cluster_name
Where your_cluster_name is the cluster name for the HFMWeb managed server.
4 Repeat step 3 for the ERPIntegrator managed server and the FinancialClose managed server.
Extending a Deployment
If you have deployed only some EPM System Java web applications, you can extend the
deployment by deploying additional Java web applications. For example, if you previously
deployed Planning, you can extend the deployment to deploy Profitability and Cost
Management. Use the manual deployment steps in this chapter, however, instead of selecting
Create a New WebLogic Domain, select Extend an Existing WebLogic Domain.
Manually Configuring Oracle HTTP Server

You can choose to manually configure the Oracle HTTP Server installed by EPM System Installer
instead of configuring it with EPM System Configurator.
If you are using a supported Web server other than the Oracle HTTP Server that is installed by
EPM System Installer, you must manually configure the Web server.
Manual Web server configuration notes:
l To configure IHS, see Configuring IBM HTTP Server on page 172.
l Manual configuration of IIS is not supported.
This section assumes you have already used EPM System Configurator to configure EPM System
components and deployed Java web applications manually or by using EPM System
Configurator.
165
To manually configure Oracle HTTP Server:
1 Launch EPM System Configurator: Change to EPM_ORACLE_INSTANCE\BIN and then launch
configtool.bat|sh.
2 In EPM System Configurator, on the Task Selection panel, select Uncheck All, expand Hyperion
Foundation, select Configure Web Server, and then click Next.
3 In Configure Web Server, from Web Server Type, select Setup Registry for manual web server
configuration and click Next.
4 Complete the steps in EPM System Configurator and when configuration is complete, click Finish.
EPM System Configurator creates autogenerated files in EPM_ORACLE_INSTANCE/
httpConfig/autogenerated/ohs to simplify manual web server configuration.
5 Copy the autogenerated files to a location of your choice related to your installation of Oracle HTTP
Server.
6 If you configured Oracle HTTP Server and EPM System components to use SSL, update files as follows:
l Update the port in ssl.conf in the "Listen" directive and in the <VirtualHost> tree-
directive.
l Update the port in httpd.conf in the "Listen" directive to any port other than the SSL
port.
l Update the port in HYSL-WebLogic-autogenerated.conf in the <VirtualHost>
tree-directive to any port other than the SSL port.
7 Update HYSL-WebLogic-autogenerated.conf as follows:
l If necessary, update all "LoadModule" directives so that the ${ORACLE_HOME}
environment variable is correct.
l Update the OHS_LISTEN_PORT alias and replace it with the actual value, for example
<VirtualHost *:OHS_LISTEN_PORT> would be <VirtualHost *:19000>.
l Update the following lines with actual file location:
Include "conf/epm_online_help.conf"
Include "conf/epm_rewrite_rules.conf"
Include "conf/epm.conf"
For example:
Include "path_to_conf_files/epm_online_help.conf"
Include "path_to_conf_files/epm_rewrite_rules.conf"
Include "path_to_conf_files/epm.conf"
8 In the Oracle HTTP Server installation folder, browse to httpd.conf, open it in a text editor, and make
the following changes:
a. Comment all the lines that contain ssl.conf and mod_wl_ohs.conf.
b. Add the following lines to the end of the file:
166
l Include path_to_modified_conf_files/HYSL-WebLogic-
autogenerated.conf
l Include path_to_modified_conf_files/ssl.conf
where ssl.conf is the autogenerated file
You can use UNC-style paths on Windows only if the Oracle HTTP Server Windows
Service is running as a user account that has network access and has "Logon as a service"
rights.
c. Update the "Listen" directive with the actual web server's port.
9 If you are using Financial Close Management, perform the following tasks:
a. On the machine hosting the Web Server, copy the autogenerated file
EPM_ORACLE_INSTANCE/httpConfig/autogenerated/soa/mod_wl_ohs.conf
and rename it to mod_wl_soa_ohs.conf.
b. Open mod_wl_soa_ohs.conf in a text editor and replace
soa_server_host:soa_server_port and
admin_server_host:admin_server_port with the actual values for the SOA host
and port and the WebLogic Administration Server host and port.
c. Copy the modified mod_wl_soa_ohs.conf to EPM_ORACLE_INSTANCE/
httpConfig/ohs/config/OHS/ohs_component/conf.
d. Open EPM_ORACLE_INSTANCE/httpConfig/ohs/config/OHS/ohs_component/
httpd.conf in a text editor and add the following line inside of the <VirtualHost>
tag:
Include conf/mod_wl_soa_ohs.conf"
For example:
<VirtualHost *:19000>
include "conf/mod_wl_ohs.conf"
Include "conf/epm_online_help.conf"
Include "conf/epm_rewrite_rules.conf"
Include "conf/epm.conf"
Include "conf/mod_wl_soa_ohs.conf"
</VirtualHost>
e. Restart Oracle HTTP Server.
10 Update the WEB_SERVER component in the Shared Services Registry so that the port property is the
actual value of the port on which Oracle HTTP Server is running. For example, to change the actual port
to 19000:
a. Generate a registry report by launching EPM_ORACLE_INSTANCE\bin
\epmsys_registry.bat. Enter the Shared Services database password when
prompted.
b. Look for the WEB_SERVER component with properties "type" = MANUAL, "port" =
-1, and "instance_home" with the EPM_ORACLE_INSTANCE that is configured.
c. Look for the object id for the WEB_SERVER component, and copy it into following
command:
167
EPM_ORACLE_INSTANCE/bin/epmsys_registry.bat updateproperty #object_id/
@property_name property_value
For example:
EPM_ORACLE_INSTANCE/bin/epmsys_registry.bat updateproperty
#df17801dfc1dca40S24e400aa13a736f8a46S7921/@port 19000
11 Restart Oracle HTTP Server and EPM System servers.
168
Deploying EPM System Products
8 to WebSphere Application
Server
In This Chapter
Additional Postdeployment Steps for FDMEE ......................................................... 172
Configuring IBM HTTP Server ............................................................................ 172
Validating WebSphere Application Server Deployments ............................................. 175
You can deploy EPM System Products to WebSphere Application Server using the process
outlined in this chapter. An EPM System deployment cannot deploy Java web applications to
both WebLogic and WebSphere.
This chapter assumes that you are an experienced Java web application server administrator.
WebSphere deployment notes:
l WebLogic Server is always installed with EPM System on every machine in the deployment
even if you are using WebSphere Application Server.
l Deployment to a single managed server is not supported for WebSphere Application Server.
l You must deploy all EPM System products to a single profile.
l You can also deploy Oracle Enterprise Manager.
l These steps assume that you are using the script provided with EPM System installation
(runWASDeployment.bat|sh). Additional steps could be required if you deploy using the
WebSphere Configuration Wizard, however those steps are not included in this procedure.
l The runWASDeployment.bat|sh script supports single box configuration only. To extend
the deployment, use the Websphere Configuration Wizard. See Extending the WebSphere
Deployment in the Oracle Enterprise Performance Management System Deployment Options
Guide.
l If you are applying a maintenance release to move to Release 11.1.2.3 and you deployed Java
web applications to WebSphere Application Server, follow the procedures in Chapter 10,
Performing a Maintenance Release Installation for EPM System Products..
To manually deploy EPM System Java web applications to WebSphere Application Server:
1 Install WebSphere Application Server Network Deployment if it is not already installed. For a single
machine development environment, you can install WebSphere Application Server Base Edition.
169
In addition, install IBM HTTP Server and its required Plugins. Note that if you are deploying
EPM System products that also use IIS, IIS and IBM HTTP Server have the same default
port. Install IBM HTTP Server using a different default port to avoid a port conflict.
If you are using Insight (Interactive Reporting Web Client), install IBM HTTP Server and
Reporting and Analysis Java web applications on the same machine.
2 After installing WebSphere, perform the following tasks:
l (UNIX only) Edit WAS_HOME/bin/wsadmin.sh to move the $PERF_JVM_OPTIONS
statement before the $javaOption statement.
l Apply Fix Pack 23+ to update WebSphere, the WebSphere SDK, for IBM HTTP Server,
and Plugins. See http://www-01.ibm.com/support/docview.wss?uid=swg24032493:
3 Install EPM System products using EPM System Installer.
4 Set the WAS_HOME system environment variable to point to the installation location for WebSphere
Application Server, for example c:/program files/IBM/WebSphere/AppServer.
5 Copy ALBAN*.ttf from EPM_ORACLE_HOME/../jdk160_29/jre/lib/fonts to
WAS_HOME/java/jre/lib/fonts.
6 Launch EPM System Configurator using the following command and perform all required configuration
tasks except for the Configure Web Server task. Note that the Deploy to Application Server task is
not available. Note also that you must configure Essbase Server later in the process.
EPM_ORACLE_HOME/common/config/11.1.2.0/configtool-manual.bat|.sh
Launching EPM System Configurator with this command hides the Java web application
deployment tasks and skips the Essbase product registration with Shared Services task.
If you need additional details about configuring EPM System, see Configuring EPM System
Products on page 111.
7 Deploy the Java web applications to WebSphere by running the following script (note that you do not
have to shut down WebSphere if it is already running):
EPM_ORACLE_INSTANCE/bin/deployment/runWASDeployment.bat|sh
Enter a new administrator user name and password for the WebSphere Integrated Solutions
Console, and then provide values for the script for the following parameters, or press
Enter to select the default values (default values are noted in parentheses). Specify unique
values for each parameter.
l Deployment Manager Profile Name (DM_PROFILE_NAME = EPMSystemDMProfile)
l Application Server Profile Name (PROFILE_NAME = EPMSystemProfile)
l Cell Name (CELL_NAME = EPMSystemCell)
l Deployment Manager Node Name (NODE_NAME = EPMSystemNode)
l Application Server Node Name (APP_NODE_NAME = EPMSystemAppNode)
If there are no profiles, the script creates one. In addition, the script performs some
configuration tasks.
170
When the deployment is done, Configuration Complete displays and then the window
closes.
8 After the Java web applications are deployed, run the following scripts to start the deployment manager
and node agent:
WAS_HOME/profiles/DM_PROFILE_NAME/bin/startManager.bat[sh]
WAS_HOME/profiles/PROFILE_NAME/bin/startNode.bat[sh]
If you are using WebSphere AS, run the following script instead:
WAS_HOME/profiles/PROFILE_NAME/bin/startServer.bat[sh] SERVER_NAME
where SERVER_NAME is the server name you specified. The default server name is
EPMServer.
9 Log in to the WebSphere Administration Console (Integrated Solutions Console), (https://
localhost:port/ibm/console/login.do?action=secure).
Tip: To determine the port number for the Integrated Solutions Console, open WAS_HOME/
profiles/DM_PROFILE_NAME/properties/portdef.props and search for the
WC_adminhost_secure property.
10 Stop all the EPM System servers.
To stop applications, log in to the Integrated Solutions Console. Select Servers, then Server
Types, then WebSphere application servers, then select the application server to stop, and then
click Stop. You can also start or stop a Java web application using the scripts: WAS_HOME/
profiles/PROFILE_NAME/bin/start[stop]Server.bat[sh] SERVER_NAME.
This step is required to prepare the Shared Services Registry for Web Server configuration.
Note that For WebSphere ND you must start servers. For WebSphere AS you can start
applications only.
11 Manually configure the Web server. See Configuring IBM HTTP Server on page 172.
12 (Optional) For clustered Java web applications, configure the logical addresses for the Web applications
by launching EPM System Configurator and selecting the Foundation task Configure Logical Address
for Web Applications to set the logical addresses for the Java web applications' host and port to the
manually configured Web Server.
13 If you are using FDMEE, perform additional tasks to configure Oracle Data Integrator. See Additional
Postdeployment Steps for FDMEE on page 172.
14 Validate the deployment.
See Validating WebSphere Application Server Deployments on page 175.
To scale out the WebSphere deployment, see the Oracle Enterprise Performance Management
Tip: Check the log files in EPM_ORACLE_INSTANCE/diagnostics/logs/config/

configtool-wasdeployment.log and WAS_HOME/profiles/
ApplicationServerProfileNamelogs/serverName.
171
Additional Postdeployment Steps for FDMEE
If you are using FDMEE, perform additional tasks to configure Oracle Data Integrator.
To configure FDMEE with Oracle Data Integrator:

1 For WebSphere ND, start the deployment manager and stop the node agent:
WAS_HOME/profiles/PROFILE_NAME/bin/stopNode.bat[sh]
For WebSphere AS, start the server:

WAS_HOME/profiles/PROFILE_NAME/bin/startServer.bat[sh] SERVER_NAME
MIDDLEWARE_HOME/oracle_common/common/bin/wsadmin.cmd[sh] -profileName
DM_PROFILE_NAME -user WAS_ADMIN_USER -password WAS_ADMIN_PASSWORD -conntype SOAP
3 Execute the following commands:
Opss.createCred(map="oracle.odi.credmap", key="SUPERVISOR", user="SUPERVISOR",
password="SUNOPSIS", desc="ODI SUPERVISOR Credential")
Opss.createCred(map="oracle.odi.credmap", key="ODI-DOMAIN", user="<WAS_USER>",

password="<WAS_PASSWORD>", desc="ODI-DOMAIN Credential")
AdminConfig.save()
4 Start the node and restart the FDMEE Server.
Configuring IBM HTTP Server

After deploying Java web applications, configure IBM HTTP Server.
To configure IBM HTTP Server:

1 If they are not already started, run the following scripts to start the deployment manager and node agent:
2 Launch EPM System Configurator using the following command and select the Foundation Configure
Web Server task.
EPM_ORACLE_HOME/common/config/11.1.2.0/configtool-manual.bat|.sh
If you also want to configure Essbase while you are deploying Java web applications, when
you first ran configtool-manual.sh, the Configure Essbase Server task was not available.
It is available in this second pass of configuration, so if needed, select it now.
3 On the Configure Web Server page, select Setup Registry for manual web server configuration.
4 After configuration is complete, open EPM_ORACLE_INSTANCE/httpConfig/
autogenerated/ihs/HYSL-Websphere-autogenerated.conf in a text editor and make
the following changes:
172
a. Replace all entries of HTTP_SERVER_ROOT_FOLDER with the path to IBM HTTP Server
(for example /home/IBM/HTTPServer).
b. Replace all entries of PLUGINS_ROOT_FOLDER with HTTP_SERVER_ROOT_FOLDER/
Plugins (for example /home/IBM/HTTPServer/Plugins).
c. Because most offerings of IBM HTTP Server are 32-bit software (and the 64-bit
Supplements also contain 32-bit Plugin binaries), you must load the correct plug-ins
for your operating system type by commenting (#) or uncommenting the following
lines:
l If your operating system is 64-bit (except Solaris x64 or HP-UX for Itanium),
uncomment this line: #LoadModule was_ap22_module
"PLUGINS_ROOT_FOLDER/bin/32bits/mod_was_ap22_http.dll"
l If your operating system is 32-bit or Solaris x64 or HP-UX for Itanium,
uncomment this line: LoadModule was_ap22_module
"PLUGINS_ROOT_FOLDER/bin/mod_was_ap22_http.dll"
d. Add the following lines if you extended the deployment:

<IfModule !headers_module>
LoadModule headers_module modules/mod_headers.so
</IfModule>
e. Comment or uncomment the following line depending on your preference for online
Help.
Include conf/epm_online_help.conf
If you want to run Help locally, comment this line. Leave the line uncommented to run
Help from the hosted Oracle server. See Installing and Configuring Online Help in
the Oracle Enterprise Performance Management System Deployment Options Guide.
f. Change the mod_was_ap22_http extension for your operating system: (dll for
Windows, so for Unix).
g. Replace all entries of IHS_LISTEN_PORT with the port number for your Web server.
Tip: To determine the port number, open WAS_HOME/HTTPServer/conf/

httpd.conf and search for Listen.
h. If you are using Insight (Interactive Reporting Web Client), make the following edits:
l Comment or delete the following line:
RewriteRule ^/InsightInstaller/(.*) /raframework/zeroadmin/component/Insight/
$1 [PT]
l Add the following line in HYSL-Websphere-autogenerated.conf:
AliasMatch /InsightInstaller/(.*) "EPM_ORACLE_HOME/products/biplus/
InstallableApps/raframework/zeroadmin/component/Insight/$1"
where EPM_ORACLE_HOME is the EPM_ORACLE_HOME on the server where IBM

HTTP Server is installed. If EPM System is installed on a different machine or in
173
a different user home directory (for example, on UNIX), you must copy the entire
Insight directory to a location accessible for IBM HTTP Server.
5 Open EPM_ORACLE_INSTANCE/httpConfig/autogenerated/ihs/plugin-cfg.xml
in a text editor and make the following changes:
a. Replace all entries of PLUGINS_ROOT_FOLDER with HTTP_SERVER_ROOT_FOLDER/
Plugins (for example /home/IBM/HTTPServer/Plugins).
b. For non-SSL configurations, replace all entries of IHS_PORT with the port number for
your Web server.
c. For SSL configurations, replace all entries of IHS_SSL_PORT with your HTTP SSL port.
6 In an environment with multiple machines, perform the following tasks. In a single machine environment,
you can skip this step.
a. Generate plugin-cfg.xml file using the WebSphere utility: Launch
GenPluginCfg.bat|sh from WAS_HOME/profiles/DM_PROFILE_NAME/bin.
plugin-cfg.xml is generated in WAS_HOME/profiles/DM_PROFILE_NAME/

config/cells.
b. Perform the following steps for every clustered EPM System Java web application:
i. Open the newly generated plugin-cfg.xml file in a text editor.
ii. Find the required ServerCluster component. It should contain information
about physical servers.
iii. Copy the required CloneID property and its value to the appropriate server in
EPM_ORACLE_INSTANCE/httpConfig/autogenerated/ihs/plugin-
cfg.xml.
7 Copy plugin-cfg.xml, epm_online_help.conf, and HYSL-Websphere-
autogenerated.conf from EPM_ORACLE_INSTANCE/httpConfig/autogenerated/
ihs to HTTP_SERVER_ROOT_FOLDER/conf.
8 Edit HTTP_SERVER_ROOT_FOLDER/conf/httpd.conf, make the following changes, and then
save the file:
a. Comment (#) the following line at the end of the file, if the line exists.
LoadModule WebSpherePluginConfig pathToPlugin.cfg
b. Add the following line at the end of the file:
Include conf/HYSL-Websphere-autogenerated.conf
9 Update the Shared Services Registry with the actual value for the Web Server port (the
WEB_SERVER node) by running the following command:
EPM_ORACLE_INSTANCE/bin/epmsys_registry.bat[sh] updateproperty WEB_SERVER/@port
ACTUAL_PORT_VALUE
where ACTUAL_PORT_VALUE is the actual IBM HTTP Server port. This is the same port
number you updated in the file earlier in this procedure.
If there is more than one web server in the deployment, use the Object ID of the
WEB_SERVER component that has type MANUAL and port -1. For example:
174
EPM_ORACLE_INSTANCE/bin/epmsys_registry.bat[sh] updateproperty #objectIDNumber/@port
ACTUAL_PORT_VALUE
10 Restart IBM HTTP Server by launching the following command or by starting the Windows service:
For UNIX: HTTP_SERVER_ROOT_FOLDER/bin/apachectl restart
For Windows: Launch the Windows service. If the service does not exist, run the following
command to install the service, and then start it in the Windows Services Control Panel:
HTTP_SERVER_ROOT_FOLDER/bin/apache -k install
11 Check that the IBM HTTP Server port was added to the virtual host under WebSphere: Log in to the
WebSphere Administration Console (Integrated Solutions Console) (https://localhost:port/
ibm/console/login.do?action=secure). Select Environment, then Virtual hosts. Click the
virtual host that you used for EPM System products (by default it is default_host). If the port is not
listed, open Host Aliases properties and add the IBM HTTP Server port, and then click Save at the top
of the page.
Perform this step for each machine in a distributed environment.
12 Restart all EPM System application servers and services.
Stop and restart the deployment manager and node agent by running the following scripts:
To stop:
WAS_HOME/profiles/DM_PROFILE_NAME/bin/stopManager.bat[sh]
WAS_HOME/profiles/PROFILE_NAME/bin/stopNode.bat[sh]
To restart:
13 For FDMEE only, perform the following steps:
a. Log in to EPM Workspace and launch FDMEE by selecting Navigate, then Administer,
and then ERP Integrator.
b. In ERP Integrator, click any link, for example Data Load Rule, and then close the page.
c. Log in to IBM Console and restart the FDMEE Server.
Validating WebSphere Application Server Deployments

To validate a WebSphere deployment, run EPM System Diagnostics. See Chapter 13, Validating
the Installation and Verifying Deployment.
175
176
Performing Manual
9 Configuration Tasks in a New
Deployment
In This Chapter
Essbase Manual Configuration Tasks .................................................................. 177
Reporting and Analysis Manual Configuration Tasks ................................................. 178
Financial Close Management Manual Configuration Tasks ......................................... 179
FDMEE Manual Configuration Tasks.................................................................... 184
After configuration, you must configure user directories, provision the functional administrator,
and deactivate the default administrator (admin) account. See Oracle Enterprise Performance
Management System User Security Administration Guide.
To set up EPM System components to work with Oracle Web Services Manager, see the Oracle
See the Oracle Enterprise Performance Management System Deployment Options Guide for
additional optional tasks you can perform to customize your deployment.
See your product's Administration Guide for additional tasks to perform.
Essbase Manual Configuration Tasks

Subtopics
l Setting User Limits on 64-bit AIX
l Enabling Client Lookup by Cluster Name
The following table describes Essbase postconfiguration tasks.
Table 22 Essbase Postconfiguration Tasks
Task Reference
(UNIX) Set User Limits on 64-bit AIX. Setting User Limits on 64-bit AIX on
page 178
Enable clients to look up Essbase by cluster name instead of URL. Enabling Client Lookup by Cluster
Name on page 178
If you are using Essbase on the Oracle Exalytics In-Memory Machine, edit Essbase.cfg to
set OracleHardwareAcceleration TRUE.
177
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 Value
time (seconds) unlimited
file (blocks) unlimited
data (kbytes) unlimited
stack (kbytes) No higher than 128 MB for 64-bit and 64 MB for 32-bit
memory (kbytes) unlimited
coredump (blocks) unlimited
nofiles (descriptors) 4096, with a maximum of less than 32,000
Enabling Client Lookup by Cluster Name

Essbase clients can use a URL to connect to an Essbase cluster, in the form: http(s)://
host:port/aps/Essbase?ClusterName=clusterName. To simplify login, Essbase clients
can use the cluster name directly instead of the URL. If you want to enable client login using the
cluster name, you must first specify a property to configure Provider Services. The cluster name
is resolved by the Provider Services servers specified in configuration files:
To enable lookup by cluster name:

1 Modify essbase.cfg and essbase.properties as follows:
l For server-to-server communication, modify essbase.cfg to specify the Provider
Services server to use, in the following format, separating each URL with a semicolon:
ApsResolver http(s)://host:port/aps
l For client-to-server communication, modify essbase.properties to specify the
Provider Services server to use, in the following format:
ApsResolver=http(s)://apshost1:port/aps
2 Restart Essbase after updating these files.
Upgrade Note!
After upgrading, update the ApsResolver setting in all essbase.cfg files (those installed
for the servers, and those installed for the Essbase clients.
Reporting and Analysis Manual Configuration Tasks

The following table describes Reporting and Analysis postconfiguration tasks.
178
Table 23 Reporting and Analysis Postconfiguration Tasks
Task Reference
For Reporting and Analysis Framework on IPV6 systems, update default-domain.cfg, in EPM_ORACLE_HOME/
common/raframeworkrt/11.1.2.0/lib, to include the following entry at the end of the file:
policies:iiop:server_address_mode_policy:publish_hostname="true"
Financial Close Management Manual Configuration

Tasks
Subtopics
l Setting Up the Keystore for Message Protection
l Configuring the WebLogic Domain to OID, MSAD, SunOne
l Start Managed Servers
l Raising the Maximum Capacity in the Connection Pool
l Increasing the Connection Pool of the External LDAP Provider
This section describes additional tasks required to configure Financial Close Management.
Perform these tasks after you install and configure Oracle SOA Suite and Financial Close
Management.
Caution! You must perform these tasks before you can start and run Financial Close
Management. Perform the tasks in the order in which they are listed.
The following table describes Financial Close Management postfiguration tasks.
Note: For the procedures that follow, note that if you selected Production Mode when you
created the WebLogic domain, to make changes in the WebLogic Administration Console
you must first click Lock & Edit in the Change Center. After you make the changes, click
Activate Changes in the Change Center.
Table 24 Financial Close Management Postconfiguration Tasks
Task Reference
Set up the keystore for message protection. Setting Up the Keystore for
Message Protection on page
181
Configure the SOA Server to connect to Oracle Internet Directory, Microsoft Active Directory (MSAD), Configuring the WebLogic
or SunOne. Domain to OID, MSAD, SunOne
on page 182
179
Task Reference
Start managed servers in order. Start Managed Servers on page

183
If you are using Microsoft SQL Server, remove EDNLocalTxDataSource and EDNDataSource.
In some cases, SOA contexts are configured with EPM System Configurator. If SOA contexts are not step 9 in Manually Configuring
automatically configured, you must manually configure the SOA contexts. Oracle HTTP Server on page 165
Manual configuration is required in the following cases:
l If you manually deployed the Java web applications.
l You configured the Web Server in a different instance than Financial Close Management.
l The SOA and the WSM-PM Java web applications are deployed to different managed servers/
clusters.
If you change the configuration at any time to change the logical address of the Java web applications
(using the Update Logical Address for Web Applications page of EPM System Configurator, you must
perform the following tasks:
l For Close Manager:
1. Make sure there are no running tasks or alerts.
Financial Close Management section, select Deploy to SOA.
l For Account Reconciliation Manager:
1. Make sure there are no open periods. If there are open periods, lock them. Make sure there
are no running DataLoads.
Account Reconcilation section, select Deploy to SOA and Deploy to SOA for FDM EE.
4. Unlock any locked periods.
l For both: Connect to soainfra datasource and run the following query:
UPDATE WFTASKDISPLAY SET httpport = <LWA Port> , httpsport=0,
hostname = <LWA Host> WHERE URI like '/workflow/%';
Raise the maximum capacity of the connection pool. Raising the Maximum Capacity in
the Connection Pool on page
183
Increase the connection pool of the external LDAP provider. Increasing the Connection Pool
of the External LDAP Provider on
page 184
If you are working in a clustered environment with Financial Close Management and SOA, to ensure Enterprise Manager
that the email password is configured for all servers, the password used to authenticate email (as documentation
entered on the Common Settings configuration task panel), must be of the type Use Clear Text
Password. To change the password type, use Enterprise Manager.
After performing these steps you can also configure Account Reconciliation Manager to work
with FDMEE and create and manage Integration Types. See the Oracle Hyperion Financial Close
Management Administrator's Guide. You can download integration xml files from My Oracle
Support.
180
Setting Up the Keystore for Message Protection
To set up the keystore for message protection:
1 First, create a keystore using the keytool command:
Go to /Oracle/Middleware/user_projects/$DOMAIN_HOME/config/fmwconfig in
the server running the WebLogic Administration Server hosting your EPM System domain
and execute the following command:
keytool -genkeypair -keyalg RSA -alias aliasName -keypass password -keystore
keystoreName.jks -storepass password -validity 3600
Note: If the keytool command is not recognized, the Path environmental variable might
not include JDK. Add the JDK to the Path variable using the following command: set
PATH=%PATH%;C:\Oracle\Middleware\JDK160_35\bin\;.;.
For additional information, see How to Create and Use a Java Keystore in the Setting up
the Keystore for Message Protection section of the Oracle Fusion Middleware Security and
Administrator's Guide for Web Services 11g Release 1 (11.1.1). (http://download.oracle.com/
docs/cd/E14571_01/web.1111/b32511/setup_config.htm#BABJHIBI).
2 Next, set up message protection for Web Services:
a. Log in to Enterprise Manager (http://WebLogicAdminServerHost:7001/em)
using WebLogic administrator credentials.
b. Expand WebLogic Domain and then select EPMSystem (or the domain name used for the
EPM System deployment).
c. Right-click EPMSystem, select Security, and then select Security Provider Configuration.
d. Scroll to the Keystore section, expand the section, and then click Configure.
e. For Keystore Path, enter the path and name for the keystore that you created, for
example ./EPMKeystore.jks).
f. Enter the keystore password that you used when creating the keystore and confirm it.
g. Enter an alias and password for both Signature Key and Encryption Key, using the alias
and password that you used when creating the keystore. Confirm the passwords, and
then click OK. The alias and password for the signature and encryption keys define the
string alias and password used to store and retrieve the keys.
3 Log out and restart Oracle Enterprise Manager Fusion Middleware Control so the changes take effect,
and then restart EPM System managed servers.
For details about setting up message protection, see http://docs.oracle.com/cd/E17904_01/web.

1111/b32511/setup_config.htm#BABHIBHA in the Oracle Fusion Middleware Security and
Administrator's Guide for Web Services 11g Release 1 (11.1.1).
181
Configuring the WebLogic Domain to OID, MSAD, SunOne
This procedure is required to configure the WebLogic domain, or in the case of Financial Close
Management the SOA Server, to communicate with an external provider, such as OID, MSAD,
or SunOne. Shared Services must also be configured to work with this external provider. Follow
the sections specific to your provider.
Note: Financial Close Management does not support Shared Services Native Directory. The
Web services features of Profitability and Cost Management, Provider Services, FDMEE,
and Financial Management do not work with Shared Services Native Directory. See the
Oracle Hyperion Enterprise Performance Management System User and Role Security
Guide for more information.
To connect OID, MSAD, or SunOne to the SOA Server:

1 Log in to the WebLogic Administration Console if you are not already logged in.
2 Click Security Realms on the left, click myrealm, and then click the Providers tab.
3 Click Add, enter the following details, and then click OK.
For OID:
l Name - OID
l Type - OracleIntenetDirectoryAuthenticator
For MSAD:
l Name - MSAD
l Type - ActiveDirectoryAuthenticator
For SunOne:
l Name - SunOne
You can ignore the prompt to restart the server; you will be restarting at the end of this
procedure.
4 Click the provider you just added, click the Provider Specific tab, enter the following details for your
provider, and then click OK.
l Host
l Port
l Principal
l Credential
l User Base DB
l Group Base DB
l User from Name Filter (MSAD only)
182
l User Name Attribute (MSAD only)
You can leave the rest of the default values unchanged.

5 Click OID, MSAD,or SunOne, and for Control Flag, select SUFFICIENT.
6 Restart WebLogic Server.
Start Managed Servers

Start each managed server in the following order:
l WebLogic Administration Server
l Hyperion Foundation Services Managed Server
l Oracle HTTP Server - Oracle Process Manager (ohsInstanceInstanceNumber)
l In any order:
m Financial Close Management Java web application
m Financial Management Web Services Managed Server, if youre using Financial
Management with Financial Close Management
m FDM Web application, if youre using FDM with Financial Close Management
m Financial Reporting Java web application, if youre using Financial Reporting with
Financial Close Management
m FDMEE, if you are using Account Reconciliation Manager.
l Oracle SOA managed server
Raising the Maximum Capacity in the Connection Pool

If necessary, fine tune the data source to size the connection pool.
To raise the maximum capacity in the connection pool:

1 In the WebLogic Administration Console (http://
WebLogic_Admin_Host:WebLogic_Admin_Port/console), select Services, then JDBC,
and then Datasources.
2 Select your data source, then Connection Pool, and then Maximum Capacity.
3 Edit settings to increase capacity as follows:
l
If resource errors specific to these data sources are logged, increase their capacity:
l EDNDataSource (Oracle Database only)
l EDNLocalTxDataSource (Oracle Database only)
l mds-owsm
183
l mds-soa
l EPMSystemRegistry
l OraSDPMDataSource
l SOADataSource
l SOALocalTxDataSource
Note: You can increase the capacity for each data source by a different amount, depending on
the needs for your installation.
If the Financial Close Management log includes this error message: java.sql.SQLException:
Could not retrieve datasource via JNDI url 'jdbc/data source'
weblogic.jdbc.extensions.PoolDisabledSQLException:
weblogic.common.resourcepool.ResourceDisabledException: Pool data
source is Suspended, cannot allocate resources to applications..], then you
have exceeded the maximum connections allowed in the connection pool for the specified data
source, and you need to increase the capacity of the connection pool.
Increasing the Connection Pool of the External LDAP Provider

To increase the connection pool of external LDAP provider:
1 Shut down all servers (Admin with all managed server) if they are running.
2 Go to domain_home\config\fmwconfig\ovd\default.
3 Make a backup of adapters.os_xml.
4 Open adapters.os_xml and find <ldap id="XYZ" version="0">, where XYZ is the name
of the external LDAP provider configured from WebLogic Admininstration Console.
5 Change <maxPoolSize> from 10 to 100 or 150. For example:
<pageSize>1000</pageSize>
<referals>false</referals>
<heartBeatInterval>60</heartBeatInterval>
<timeout>120000</timeout>
<maxPoolSize>100</maxPoolSize>
<maxPoolWait>1000</maxPoolWait>
<maxPoolChecks>10</maxPoolChecks>
<quickFail>false</quickFail>
<escapeSlashes>true</escapeSlashes>
<kerberos>false</kerberos>
<useDNS>No</useDNS>
</ldap>
FDMEE Manual Configuration Tasks

The following table describes FDMEE postconfiguration tasks.
184
Table 25 FDMEE Postconfiguration Tasks
Task Reference
For FDMEE used with Account Reconciliation Manager: If you change the configuration at any time to change the logical
address of the Java web applications (using the Update Logical Address for Web Applications page of EPM System
Configurator, you must perform the following tasks:
1. Make sure there are no running DataLoads.
2. Start EPM System Configurator and from the Task Selection page, from the Financial Close, Account Reconcilation section,
select Deploy to SOA and Deploy to SOA for FDM EE.
4. Connect to soainfra datasource and run the following query:
UPDATE WFTASKDISPLAY SET httpport = <LWA Port> , httpsport=0, hostname =
<LWA Host> WHERE URI like '/workflow/%';
185
186
Performing a Maintenance
10 Release Installation for EPM
System Products
In This Chapter
Maintenance Release Installation Checklist........................................................... 187
Financial Close Management Maintenance Release Installation Checklist......................... 188
Downloading and Extracting Installation Files......................................................... 189
Performing Maintenance Release Installation Prerequisite Tasks ................................... 190
Installing and Configuring EPM System Products in a Maintenance Installation................... 194
Maintenance Installation Deployments to a Single Managed Server ............................... 197
Performing Manual Configuration Tasks in a Maintenance Installation ............................. 200
Validating the Deployment and Generating a Deployment Report .................................. 205
Performing a Maintenance Release Installation for EPM System Clients ........................... 206
If you are applying the maintenance release to move from EPM System Release 11.1.2.0, Release
11.1.2.1, or Release 11.1.2.2 to Release 11.1.2.3, use the procedures in this chapter.
Maintenance installation notes:
l You cannot configure Oracle HTTP Server to a shared drive when you apply a maintenance
release installation.
l If you deployed Java web applications to a single managed server, you must deploy in the
same way in this release.
l If you deployed Java web applications to WebSphere Application Server, you can apply the
maintenance release installation only if you used runWASDeployment.bat|sh in the
previous release to deploy the Java web applications and if the topology has not changed.
Additional steps would be required if you deployed using the WebSphere Configuration
Wizard, however those steps are not included in this procedure.
l You must log in as the same user that installed and configured the previous release.
Maintenance Release Installation Checklist

Note: If you are applying the maintenance release to Financial Close Management, follow the
installation and configuration sequence described in Financial Close Management
Maintenance Release Installation Checklist on page 188.
187
Table 26 Maintenance release installation checklist
Task Reference
Meet the system requirements. Oracle Enterprise Performance Management System Certification Matrix
(http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-
If your database environment needs to be upgraded,
certification-100350.html)
perform the database upgrade before you proceed. See
the database documentation for details.
Download and extract the installation files. Downloading and Extracting Installation Files on page 189
Perform the maintenance release installation prerequisite Performing Maintenance Release Installation Prerequisite Tasks on page
tasks. 190
Install and configure EPM System products. Installing and Configuring EPM System Products in a Maintenance
Installation on page 194
Perform any required manual configuration tasks for your Performing Manual Configuration Tasks in a Maintenance Installation on
products. page 200
Validate the installation using EPM System Diagnostics and Validating the Deployment and Generating a Deployment Report on page
generate a deployment report. 205
Financial Close Management Maintenance Release

Installation Checklist
The following table provides an overview of the installation and configuration process for Oracle
SOA Suite and Financial Close Management if you are moving from Financial Close
Management Release 11.1.2.1 or Release 11.1.2.2 to Release 11.1.2.3.
Note the following about applying the maintenance release to Financial Close Management:
l The maintenance release installation option is supported only from Financial Close
Management Release 11.1.2.1 or Release 11.1.2.2.
l Before you are apply the maintenance release, make sure there are no schedules with an
Open status.
l If you want to add Account Reconciliation Manager to your Financial Close Management
deployment, you must first install the 11.1.2.3 Release of the Financial Close Management
Close Manager Java web application using the Apply Maintenance Release option in EPM
System Installer. Then, install the Financial Close Management Reconciliation Manager Java
web Application Java web application using the New installation option in EPM System
Installer.
l If .NET Framework is not installed, EPM System Installer installs it for you.
Table 27 Roadmap for Applying the Maintenance Release to Financial Close Management
Task Reference
Shut down all EPM System, WebLogic, and SOA services.
188
Task Reference
Install Financial Close Management Release 11.1.2.3 on the machine hosting Financial Close
Management Release 11.1.2.1 or Release 11.1.2.2.
Note: During installation, Apply Maintenance Release is selected for you. EPM System Installer selects
all available products; you must apply the maintenance release to all EPM System products in the
deployment.
After installation, apply patch 16788543.
Configurator until you have completed the following Oracle SOA Suite upgrade steps.
Before upgrading SOA Suite, back up the SOA database. Oracle Fusion Middleware
Patching Guide 11g Release 1
Upgrade Oracle SOA Suite components to PS6 and then apply any required patches. The following list
provides an overview of the steps: Tip: Review the SOA startup
logs for any errors and resolve
1. Update the existing software (SOA components).
the errors before proceeding
2. If you are using Microsoft SQL Server, apply patch number 16400937 for Release 11.1.1.7.0. with EPM System Configurator.
3. Upgrade the RCU schemas. For more information see Starting the Patch Set Assistant in the Oracle You can also view the status of
Fusion Middleware Patching Guide 11g Release 1. During this step, the following schemas are SOA in Enterprise Manager
Console.
upgraded: _SOAINFRA, _MDS and _ORASDPM.
4. Run the SOA Upgrade Script to upgrade the WebLogic domain. For more information see Run soa-
upgrade.py to Update the Policy Store and Deploy a Shared Library in the Oracle Fusion
Middleware Patching Guide 11g Release 1.
Configure EPM System products, selecting all required configuration tasks except for Deploy to SOA
for Close Manager, and Deploy to SOA and Deploy to SOA for FDM EE for Account Reconciliation
Manager. including database configuration and Java web application deployment for Shared Services
and Financial Close Management.
Start WebLogic Administration Server and then the SOA managed server.
Start EPM System Configurator and select Deploy to SOA for Close Manager, and Deploy to SOA and
Deploy to SOA for FDM EE for Account Reconciliation Manager.
Shut down all the servers and restart them (SOA Server, WebLogic Administration Server).
Stop the SOA server, and then start EPM System products, the SOA Server and Financial Close Financial Close Management
Management in the order listed. Application Server on page
318
Update product integration types by importing the Release 11.1.2.3 versions of all product integration Managing Integration Types in
files. The product integration files are posted on My Oracle Support. the Oracle Financial Close
Management Administrator's
Guide.
Downloading and Extracting Installation Files

Download the EPM System files from the Oracle Enterprise Performance Management System
media pack on the Oracle Software Delivery Cloud (http://edelivery.oracle.com/). Oracle
recommends that you download files to a shared drive. See Chapter 4, Downloading Files for
Installation for details on downloading and extracting installation files.
189
Performing Maintenance Release Installation
Prerequisite Tasks
Subtopics
l Essbase Maintenance Release Installation Prerequisites
l Business Rules Maintenance Release and Upgrade Installation Prerequisites
l Financial Reporting Maintenance Release Installation Prerequisites
l Maintenance Release Installation Prerequisites if You Are Using Oracle Web Services Manager
If you are applying the maintenance release to move from EPM System Release 11.1.2.0,
Release 11.1.2.1, or Release 11.1.2.2 to Release 11.1.2.3, perform the following tasks before
you install and configure:
1 Apply any required PSEs before proceeding with maintenance the installation.
To review the list of defects fixed between earlier releases, use the Defects Fixed Finder. This
tool enables you to identify the products you own and your current implementation release.
With a single click, the tool quickly produces a customized report of fixed-defect descriptions
with their associated platforms and patch numbers. This tool is available here:
https://support.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=1292603.1
2 Stop all EPM System services and processes, and restart IIS.
Check to make sure that all processes are stopped; some processes, such as CASSecurity,
are left running even after Windows services are all stopped.
3 Back up the Shared Services Registry database.
4 Generate a deployment report:
a. Open a command line window and navigate to EPM_ORACLE_INSTANCE/bin.
b. Run the command epmsys_registry.bat|.sh report deployment.
By default, the report is saved as EPM_ORACLE_INSTANCE/diagnostics/reports/
deployment_report_YYYYMMDD_HHMMSS.html.
5 If you have disabled or deleted any of the global roles (in particular the Shared Services Global roles)
that are in the Shared Services Registry, they must be restored and provisioned to the Admin user for
the maintenance configuration process to work correctly.
6 Ensure that the external authentication provider is online before you start EPM System Configurator.
7 If you are applying the maintenance release to move from Essbase Release 11.1.2.0 or Release 11.1.2.1
to Release 11.1.2.3, you must first export linked reporting object information from the earlier release
database, and then delete the linked reporting objects. After applying the maintenance release, import
the exported linked reporting objects. See Essbase Maintenance Release Installation Prerequisites
on page 191.
8 If you are performing a maintenance installation on UNIX and you had Financial Management on this
platform in the previous release, you must first uninstall Financial Management Web Services.
9 If you are using Business Rules in Release 11.1.2.0 or 11.1.2.1, you must migrate to Calculation
Manager rules in Release 11.1.2.3. Before migrating business rules, you must perform prerequisite
190
tasks. See Business Rules Maintenance Release and Upgrade Installation Prerequisites on page
192. If you are applying a maintenance installation from Release 11.1.2.2, you can skip this step.
10 If you are moving from Financial Close Management Release 11.1.2.1 or Release 11.1.2.2, see
Financial Close Management Maintenance Release Installation Checklist on page 188
11 If you are applying the maintenance release to move from Strategic Finance Release 11.1.2.0 or
11.1.2.1 to Release 11.1.2.3, you must convert the Strategic Finance database using a conversion
utility. Oracle recommends that you back up the database before converting it. Apply Strategic Finance
Release 11.1.2.1.000 Patch Set Exception (PSE): 13776302 and then run the conversion utility.
12 If you are using Oracle Web Services Manager with EPM System products, upgrade the OWSM MDS
schema. See Maintenance Release Installation Prerequisites if You Are Using Oracle Web Services
Manager on page 193.
13 Stop all the services for EPM System products.
Note that you must manually stop the Integration Services service manually using the Task
Manager. (Look for olapisvr.exe in the Processes).
Do not start services for a product until the product's configuration tasks are complete.
Essbase Maintenance Release Installation Prerequisites

If you are applying the maintenance release to move from Essbase Release 11.1.2.0, Release
11.1.2.1, or Release 11.1.2.2 to Release 11.1.2.3, you must first export linked reporting object
(LRO) information from the earlier release database, and then delete the linked reporting objects.
After installing and configuring, you import the exported linked reporting objects.
To export linked reporting objects from Essbase Release 11.1.2.0, Release 11.1.2.1, or Release
11.1.2.2:
1 On the machine hosting the earlier release installation, back up the application linked reporting object
data to a specified directory by using the following MAXL command:
EXPORT database DBS-NAME LRO to server directory directoryName;
For example:
MAXL> EXPORT database Sample.Basic LRO to server directory V1;
In this example, Sample.Basic LRO data is exported to Sample-Basic-V1 in

ARBORPATH/app.
2 Remove the application linked reporting object data with the following MAXL command:
ALTER database DBS-NAME delete LRO all
For example:
MAXL> ALTER database sample.basic delete LRO all;
3 Shut down the earlier release Essbase server.
There are additional steps you perform after installing and configuring Essbase Release 11.1.2.3.
191
Business Rules Maintenance Release and Upgrade
Installation Prerequisites
If you are applying the maintenance release to move from Release 11.1.2.0 or Release 11.1.2.1
to Release 11.1.2.3, or if you are upgrading from an earlier release, and if you have been using
Business Rules in the earlier release, you must migrate to Calculation Manager rules in Release
11.1.2.3. Before migrating business rules, you must perform prerequisite tasks.
If you are applying a maintenance installation from Release 11.1.2.2, you can skip this step.
To prepare to migrate Business Rules, perform the following tasks in your current Business
Rules environment before installing Release 11.1.2.3:
1 In Business Rules, within the Rule Editor, remove the associated outline (that is, the design time location)
from each business rule. After you do this, the Associated Outline drop-down list should display the text,
Select Outline.
2 On the Locations tab of the Rule Editor, ensure that each business rule has a valid launch location,
which must be an absolute location. Although All Locations is valid in Business Rules, when you
migrate business rules, you must provide the details of a specific launch location (that is, the application
type---Planning or Essbase, the server name, the application name, and the database or plan type). If
you want a business rule to be valid for multiple launch locations, you must provide the details for each
location. The locations must be in different applications; you cannot migrate the same business rule to
different plan types in the same application within Calculation Manager.
If the rule is a part of a sequence, then the launch location of the rule within the sequence
must be one of the launch locations listed in the Locations tab of the rule.
3 On the Access Privileges tab of the Rule Editor, ensure that each business rule has security defined for
a specific location or locations and not All Locations. If multiple locations are defined for a business
rule on its Locations tab, you must add security for each location individually.
4 Do not modify rules in Calculation Manager until migration is completed.
5 If you are using Business Rules with Planning, as a precaution, create a backup of the rules: Use
Administration Services to export the rules to XML in Business Rules format. If you are upgrading from
Release 11.1.1.4, also export the rules to Calculation Manager format. EPM System Configurator exports
the rules during database configuration for use during application upgrade.
6 If you are an Essbase-only Business Rules user, you must export business rules. To export the Essbase
rule from Business Rules:
a. From Administration Services Console, right-click the Business Rules node and select
Export.
b. Export the rules in Business Rules format and then select all of the Essbase rules in the
repository. If you are upgrading from Release 11.1.1.4, also export the rules to
Calculation Manager format.
c. Specify the location to save the XML file, and then click OK. If you are upgrading, the
location should be a shared drive that is accessible from the upgraded environment.
Make a note of the location. You import the file later in the process.
192
During configuration with EPM System Configurator, rules are prepared for migration when
you perform the Configure Database task.
After configuration, there are additional tasks you perform to import and migrate business rules.
Financial Reporting Maintenance Release Installation

Prerequisites
It is no longer necessary to install Financial Reporting Print Server separately as it is included
by default with the Financial Reporting Java web Application on all platforms. No separate
Financial Reporting Print Server service is created. However, before installing Financial
Reporting, if you were working in Release 11.1.2.0 or Release 11.1.2.1, meet the following
prerequisites:
l If you were working in Release 11.1.2.0:
1. Uninstall Financial Reporting Studio using uninstall.cmd in EPM_ORACLE_HOME/
uninstall.
2. Delete the HRPrinter drivers from the Printers list using the Windows Control Panel.
3. Disable Hyperion Financial Reporting - Print Service in Windows Services Microsoft
Management Console, Console and then delete the following Windows registry entries
(back up the registry before you proceed):
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_FRPRINTSERVICE
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\Application
\FRPrintService
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\FRPrintService
l If you were working in Release 11.1.2.1:
1. Remove Hyperion Financial Reporting - Print Service using
FRRemovePrintServer.cmd in /Program Files [(x86)]/Oracle/
FinancialReportingStudio/products/financialreporting/install/bin.
This removes both the Windows service and the HRPrinter drivers.
2. Uninstall Financial Reporting Studio using Windows Control Panel Add\Remove
Programs (Windows XP or Windows 2003) or Programs and Features (Windows 7 or
Windows 2008).
3. Delete the folder /Program Files/Oracle/FinancialReportingStudio.
Maintenance Release Installation Prerequisites if You Are

Using Oracle Web Services Manager
If you are using Profitability and Cost Management, Financial Close Management, FDMEE,
Financial Management, Provider Services or Data Relationship Management with Oracle Web
Services Manager, upgrade the OWSM MDS schema and update Oracle Web Services Manager
to Release 11.1.1.7.0.
193
l Update the _MDS Schema. For more information see Starting the Patch Set Assistant and
Checking for Invalid Database Objects in the Oracle Fusion Middleware Patching Guide
11g Release 1.
l Update configurations and stores. For more information, see the Oracle Fusion Middleware
Patching Guide 11g Release 1.
l Update the Oracle Web Services Manager repository. See Adding New OWSM Pre-Defined
Policies in the Oracle Fusion Middleware Patching Guide 11g Release 1.
You can find Oracle Fusion Middleware Patching Guide 11g Release 1 on the Fusion Middleware
page of the Oracle Documentation Library. .
Installing and Configuring EPM System Products in a

Maintenance Installation
When you apply the maintenance release, install and configure using the same user that was
used to install and configure the earlier release.
To install EPM System products in a maintenance installation:

1 Launch EPM System Installer:
l (Windows) Double-click installTool.cmd in the root directory to which you
extracted the EPM System Installer files.
files and enter ./installTool.sh.
2 Step through EPM System Installer, making the following selections:
l On the Destination screen, click Next. You cannot change the destination. You must
apply the maintenance release on top of your existing EPM System installation.
l Apply Maintenance Release is selected for you; click Next.
l In Product Selection, click Next. You cannot change the product selection.
You must apply the maintenance release to all EPM System products in the deployment.
You cannot apply the maintenance release to only some products.
On the Product Selection page, you cannot make any selections or deselections.
If you are applying the maintenance release to an existing deployment, and you plan to
add new EPM System products to the existing deployment, install and configure existing
products first. After configuration is complete, install any new products.
Note that Integration Services is now installed with the Essbase Server.
l If you are installing any of the following products, you must also install the Financial
Management ADM Driver:
m Web Analysis
m Financial Reporting
194
m Strategic Finance
m FDM
m FDMEE
EPM System Installer installs a Windows version of the driver on Windows machines.
EPM System Installer installs a UNIX version of the driver on all platforms for use with
Oracle BI EE.
3 When installation is complete, click or select Finish.
Note: If you are installing Financial Close Management, note that it requires additional steps
before you configure with EPM System Configurator. See Financial Close
Management Maintenance Release Installation Checklist on page 188.
4 Repeat the installation steps on each machine in the deployment.
5 On the machine hosting Foundation Services, launch EPM System Configurator: from the Start menu,
select All Programs, then Oracle EPM System, then EPM System Configurator (all instances).
If you deployed Java web applications to to WebSphere Application Server, launch EPM
System Configurator with the /configtool-manual.bat|.sh command.
6 In Oracle Instance, specify the existing EPM Oracle instance to which to apply the configuration.
7 On the Shared Services and Registry Database Connection screen, select Connect to a previously
configured Shared Services database, and then review the database connection information for Shared
Services Registry and the user name and password of the database account to use for accessing the
database.
8 In Task Selection, clear the selection (uncheck) from Uncheck All, select the top node of Foundation
Services, and then click Next.
This option selects only the preconfiguration tasks for Foundation Services.
9 Continue through the panels, and when the configuration is complete, click Finish.
10 Run the Shared Services Registry repair script from the machine hosting Foundation Services to help
avoid problems during configuration:
a. Run the repair script using the preview option to detect any problems:
From a command prompt, change to EPM_ORACLE_INSTANCE/bin and run the
following command:
epmsys_registry.bat|.sh preview
Any errors are reported to the console but no changes are made to the Shared Services
Registry. If there are no errors, skip to step 12 on page 196.
b. If the repair script detects any problems, run the script again in repair mode:
epmsys_registry.bat|.sh repair
11 Generate another deployment report so that it reflects any changes the repair script made in the Shared
Services Registry.
195
Consult with Oracle Support if the report does not match the actual configuration of your
deployment environment.
12 Launch EPM System Configurator again: On the machine hosting Foundation Services, from the Start
menu, select All Programs, then Oracle EPM System, then EPM System Configurator (all
instances).
In a distributed environment, you must configure Foundation Services first. Foundation
Services must be installed and configured for other products to configure successfully.
13 In Oracle Instance, specify the existing EPM Oracle instance to which to apply the configuration.
14 On the Shared Services and Registry Database Connection screen, select Connect to a previously
configured Shared Services database, and then review the database connection information for Shared
Services Registry and the user name and password of the database account to use for accessing the
database.
15 On the component configuration page, make selections as needed and then click Next. You must
complete all Pending tasks in EPM System Configurator.
l EPM System Configurator preselects all required configuration tasks for the products
in this EPM Oracle instance.
l Optionally you can clear the selection from the Foundation Configure Web Server
task.
If you want to validate Foundation Services immediately after configuration, retain the
selection for Configure Web Server. Otherwise, configure the Web server after all
other EPM System products have been configured.
l If you are deploying Java web applications to WebSphere Application Server, perform
required configuration tasks except for the Deploy to Application Server task and the
Configure Web Server task. Then, perform additional manual steps.
l If some products were deployed to a single managed server in the earlier release, they
are deployed the same way in this release. If you want to change how products are
deployed, after the maintenance deployment is complete, you can redeploy.
l You cannot configure Oracle HTTP Server to a shared drive when you apply a
maintenance release installation.
l Optionally, you can manually deploy EPM System Java web applications. See Chapter 7,
Manually Deploying EPM System Java Web Applications
16 Step through the remaining pages in EPM System Configurator.
Oracle recommends that you maintain existing configuration settings during the
maintenance configuration. After the deployment is complete, you can reconfigure if
required to make any configuration changes.
196
If you need information about any of the pages, click Help, or see Chapter 6, Configuring
EPM System Products in a New Deployment.
l On the Database Configuration page, you need only make changes if the database
connection details need to be updated.
l Do not start services for a product until the product's configuration tasks are complete.
17 Repeat the configuration steps for each EPM Oracle instance or server in the deployment.
18 After you have configured all other EPM System products, configure the Web server last: On the machine
hosting Foundation Services, launch EPM System Configurator and select Configure Web Server from
the Foundation tasks.
19 Start EPM System products. On each machine in the deployment, select Start, then All Programs, then
Oracle EPM System, EPM_ORACLE_INSTANCE, then Foundation Services, and then Start EPM
System.
20 For clients that have a new client installer in Release 11.1.2.3, applying the maintenance release
installation option does not update the client software. You must install the client using the client
installer. See Installing EPM System Clients on page 92.
For Predictive Planning, note the following:
l Upgrade all Predictive Planning client versions at the same time, so that all users can
see new features.
l Administrators should make Form setup changes using the updated Predictive Planning
version. Making changes with older versions can result in loss of Form setup data.
During the maintenance configuration process for Profitability and Cost Management, Stage
Object Calculation artifacts from Release 11.1.2.2 applications are replaced with Calculation
Rules of type Calculated Measure in Release 11.1.2.3.
Maintenance Installation Deployments to a Single

Managed Server
Subtopics
l Scenario 1: You either deployed all Java web applications to their own managed servers, or deployed all Java web
applications to a single managed server in Release 11.1.2.0, 11.1.2.1, or Release 11.1.2.2
l Scenario 2: You were working in a Release 11.1.2.1 or Release 11.1.2.2 environment that had some Java web
applications deployed to a single managed server and some Java web applications deployed to their own managed
servers
If you are applying the maintenance release from Release 11.1.2.0, Release 11.1.2.1, or Release
11.1.2.2 to Release 11.1.2.3, see the following scenarios for additional details about deploying to
a single managed server.
197
Note: On UNIX platforms, if you are applying the maintenance release from Release 11.1.2.1
or Release 11.1.2.2 to Release 11.1.2.3 on a single managed server, the Financial
Management Web Service must be uninstalled.
Scenario 1: You either deployed all Java web applications to

their own managed servers, or deployed all Java web
applications to a single managed server in Release 11.1.2.0,
11.1.2.1, or Release 11.1.2.2
This scenario assumes:
l If you deployed to a single managed server, you must have manually deployed all Java web
applications to a single managed server and did not deploy anything using EPM System
Configurator. (Note however that deploying to a single managed server was not supported
in Release 11.1.2.0.)
l You want to deploy all Release 11.1.2.3 Java web applications to a single managed server
In this scenario, because deploying to a single managed server is not possible while you are
applying the maintenance release, you first deploy each Web application to its own managed
server, then deploy the Web applications to a single managed server. Perform the following steps:
1. Install and configure EPM System products using the Apply Maintenance Release option.
During configuration with EPM System Configurator, deploy each Java web application to
its own managed server. (On the "Deploy to Application Server" page, do not select Deploy
the web applications to a single managed server.
2. Ensure that the single managed server EPMServer0 is assigned to a machine.
a. Start WebLogic Administration Server.
b. Log in to WebLogic Administration Console.
c. Select Environment, then Servers, and them EPMServer0.
d. Check if Machine is selected for the server.
If Machine is not select for the server, select Lock & Edit, and then select the local host
machine from the drop down list
e. Click Save to activate the changes.
3. From the WebLogic Administration Server machine, deploy all or some of the Java web
applications to a single managed server: In EPM System Configurator, select the "Deploy to
Application Server" task for each product that you want to include in the single managed
server. On the "Deploy to Application Server" page, select Deploy the web applications to a
single managed server.
198
Scenario 2: You were working in a Release 11.1.2.1 or
Release 11.1.2.2 environment that had some Java web
applications deployed to a single managed server and some
Java web applications deployed to their own managed servers
This scenario assumes:
l You deployed some of the Java web applications to their own managed servers in Release
11.1.2.1 or Release 11.1.2.2
l You deployed some of the Java web applications to a single managed server in Release
11.1.2.1 or Release 11.1.2.2
l You want to maintain these deployment scenarios in Release 11.1.2.2
Perform the following steps:

1. Install EPM System products using the Apply Maintenance Release option.
2. Ensure that the single managed server EPMServer0 is assigned to a machine.
a. Start WebLogic Administration Server.
b. Log in to WebLogic Administration Console.
c. Select Environment, then Servers, and them EPMServer0.
d. Check if Machine is selected for the server.
If Machine is not select for the server, select Lock & Edit, and then select the local host
machine from the drop down list
e. Click Save to activate the changes.
3. Configure the Java web applications that were deployed to a single managed server: In EPM
System Configurator, select the Deploy to Application Server task for any one of the Java
web applications that was deployed to a single managed server, and select Deploy the web
applications to a single managed server. (The remaining Java web applications are
automatically selected.)
4. Configure the Java web applications that were deployed to their own managed servers: In
EPM System Configurator, select the "Deploy to Application Server" task for each product
for which you originally deployed to its own managed server. Do not select Deploy the web
applications to a single managed server.
199
Performing Manual Configuration Tasks in a
Subtopics
l General Manual Configuration Tasks in a Maintenance Installation
l EPM Workspace Manual Configuration Tasks in a Maintenance Installation
l Performance Management Architect Manual Configuration Tasks in a Maintenance Installation
l Essbase Manual Configuration Tasks in a Maintenance Installation
l Essbase Studio Manual Configuration Tasks in a Maintenance Installation
l Planning Manual Configuration Tasks
l Profitability and Cost Management Manual Configuration Tasks
l Strategic Finance Manual Configuration Tasks
l FDM Manual Configuration Tasks
l Maintenance Installation Deployments to WebSphere Application Server
General Manual Configuration Tasks in a Maintenance

Installation
l If you applied the maintenance release to move to Release 11.1.2.3, after you configure, clear
cached files from the Web browser. This ensures that the browser uses the correct Javascript
files.
l Delete the contents of MIDDLEWARE_HOME/user_projects/domains/EPMSystem/
precompiled and MIDDLEWARE_HOME/user_projects/domains/EPMSystem/
precompiledJSPs folders.
EPM Workspace Manual Configuration Tasks in a

After applying a maintenance release, newly-supported languages appear in the list of possible
languages; however you must manually add any new languages to the Assigned Languages list.
Select Navigate, then Administer, and then WorkspaceServerSettings. Select Supported Locales and
add the desired locales.
Performance Management Architect Manual Configuration

Tasks in a Maintenance Installation
If you applied the maintenance release to move from Release 11.1.2.0 or 11.1.2.1 to Release
11.1.2.3, and if a Financial Management application contains shared dimensions, right-click the
application in the Application View pane and select Activate All Associations. This is required to
support the dynamic properties that were introduced in Release 11.1.2.2 for Extended
Dimensionality.
200
Essbase Manual Configuration Tasks in a Maintenance
Installation
Subtopics
l Importing Linked Reporting Objects
l Importing Business Rules to Calculation Manager for use with Essbase
Importing Linked Reporting Objects

If you are applying the maintenance release to move from Essbase Release 11.1.2.0 or Release
11.1.2.1, you must import linked reporting objects from the earlier release.
Before you complete this step, you must have exported the linked reporting objects from Release
11.1.2.0 or 11.1.2.1. See Essbase Maintenance Release Installation Prerequisites on page 191.
To import linked reporting objects:

1 Start Essbase Server.
2 Run the following MAXL command to import the linked reporting object data from the earlier release
backup directory:
IMPORT database DBS-NAME LRO from server directory
directoryName
For example:
MAXL> IMPORT database Sample.Basic LRO from server directory
Sample-Basic-V1;
Importing Business Rules to Calculation Manager for use with Essbase

If you are applying the maintenance release to move from Essbase Release 11.1.2.0 or 11.1.2.1
to Release 11.1.2.3, and you are an Essbase-only Business Rules user, you must migrate Business
Rules rules to Calculation Manager.
Ensure that you exported rules as described in Performing Maintenance Release Installation
Prerequisite Tasks on page 190.
To import Business Rules to Calculation Manager for use with Essbase:

1 From Calculation Manager, select File, and then Import.
2 Browse to the XML file that you exported and then click Import.
201
Essbase Studio Manual Configuration Tasks in a
If you used the Apply Maintenance Release option to move from Essbase Studio Release
11.1.2.0, 11.1.2.1 or 11.1.2.2 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 Ensure that Essbase Studio Server is running.
2 From the EPM_ORACLE_INSTANCE/bin directory, run one of the following scripts:
start_BPMS_bpms1_CommandLineClient.bat|sh
A command window called the CPL Shell is displayed.

3 At the prompt, enter a valid Essbase Studio host name, administrator user name, and password.
Note: You must have Essbase Studio administrator privileges to use the reinit command.
4 At the prompt, enter the following command:
reinit
5 Enter exit to close the CPL Shell.
The Essbase Studio catalog is now ready for use.
Planning Manual Configuration Tasks

If you are working in Oracle Project Financial Planning or Public Sector Planning and Budgeting,
before you upgrade applications, you must perform additional steps.
Upgrading Applications
If you applied the maintenance release to move from Planning Release 11.1.2.0, 11.1.2.1, or
11.1.2.2, you must run the Upgrade Wizard and use the Upgrade Applications page. From EPM
Workspace, select Navigate, then Administer, then Planning Administration and then click Upgrade
Wizard. On the Upgrade Applications page, select one or more applications and from the Action
menu, select Upgrade, and then click OK to proceed. See Updating Planning References to a
Rehosted Server Environment and Upgrading Applications on page 245 for additional details.
Migrating Business Rules to Calculation Manager for use with Planning

If you applied the maintenance release to move from Planning Release 11.1.2.0, or Release
11.1.2.1, and you were using Business Rules rules, you must migrate the rules to Calculation
Manager rules, and then migrate rules security.
202
Before you migrate, ensure that user directories and native users with the same SID are available
when you upgrade Shared Services.
Ensure that the Planning applications are upgraded to the current release and are available in
Calculation Manager under SYSTEM View.
To migrate Business Rules rules to Calculation Manager rules:

1 In Calculation Manager, select the migrated Planning application, and then select Migrate.
The data that was exported during database configuration with EPM System Configurator
is imported to Calculation Manager.
2 Repeat for each Planning application.
3 Deploy the rules from Calculation Manager to Planning. See the Oracle Hyperion Calculation Manager
Designer's Guide.
After migrating business rules and rules security, if any of the rules had multiple launch
locations and you migrated to more than one location, Calculation Manager creates a rule
for the first migration, and shortcuts for all subsequent migrations. If the rule had rule-level
variables, for the shortcuts that are created in the application in the new environment , its
variables are moved to the Plan level. In this scenario, test rules in your environment to
ensure that they work as expected.
Migrating Business Rules Security for use with Planning

If your upgraded application used Business Rules, administrators can migrate launch access
permissions on business rules and their projects from Business Rules to Calculation Manager
business rules in Planning using the HBRMigrateSecurity.cmd utility.
The HBRMigrateSecurity.cmd utility:
l Overwrites launch access permissions that are already assigned to business rules in the
specified Planning application.
l Migrates access permissions only for users and groups that are provisioned for the specified
Planning application in Shared Services Console.
To migrate access permissions on business rules and their folders:

1 Before running HBRMigrateSecurity.cmd:
l Ensure that you have migrated business rules from Business Rules to Calculation
Manager.
l Ensure that you have deployed the business rules to Planning.
2 At the command line, from the planning1 directory, enter this command and its parameters,
separating each by a space:
HBRMigrateSecurity.cmd [-f:passwordFile] /A:appname /U:admin /F:output
file
203
Table 28 HBRMigrateSecurity Parameters
Parameter Purpose Required?
[-f:passwordFile] Optional: If an encrypted password file is set up, use as the first parameter in the command No
line to read the password from the full file path and name specified in passwordFile.
/A:appname Specify the Planning application to which to migrate launch access permissions for business Yes
rules
/U:admin Specify the administrator's user name Yes
/F:output file Specify the name of the XML output file, including its full path if it is not in the Yes
planning1 directory. This file contains a log of the transaction, and helps with
troubleshooting.
/? Print the syntax and options for HBRMigrateSecurity.cmd No
3 If prompted, enter your password.
For example:
HBRMigrateSecurity.cmd /A:appname /U:admin /F:C:\temp
\HBRExportedSecurity.xml
Profitability and Cost Management Manual Configuration

Tasks
If you want to install Profitability and Cost Management sample applications, first complete the
maintenance release installation and configuration. Next, rerun EPM System Installer and from
the Product Selection panel, from the Profitability and Cost Management section, select
Profitability and Cost Management Samples.
To set up Profitability and Cost Management to work with Oracle Web Services Manager, see
the Oracle Enterprise Performance Management System Deployment Options Guide.
Strategic Finance Manual Configuration Tasks

l After configuring the maintenance release, move transaction logs to a new location: Copy
the logs from EPM_ORACLE_HOME/logs/hsf/userlogs to EPM_ORACLE_INSTANCE/
diagnostics/logs/hsf/userlogs.
FDM Manual Configuration Tasks

After installing and configuring the maintenance release, update MIDDLEWARE_HOME/
user_projects/config/dbclient/tnsnames.ora to include entries for the Oracle
Database Client that was installed by EPM System Installer in MIDDLEWARE_HOME/
dbclient32 and MIDDLEWARE_HOME/dbclient64 so that the Schema Update Utility can
connect to the database.
204
Maintenance Installation Deployments to WebSphere
Application Server
After installing and configuring EPM System components, complete the following steps to
deploy the Java web applications.
To deploy to WebSphere Application Server:

1 Back up all databases, and then back up profiles using the manageprofiles command.
2 Stop Node Manager and all EPM System servers.
3 From a command line, change to EPM_ORACLE_INSTANCE/bin/deployment and run the
following script:
runWASDeployment.bat[sh] -cellName EPMSystemCell -profileName
EPMSystemDMProfile -nodeName EPMSystemNode -customProfile EPMSystemProfile -appNode
EPMSystemAppNode -username admin -password password -maintenance
When the deployment is done, Configuration Complete displays and then the window
closes.
4 Start all Java web applications.
5 Launch EPM System Configurator again with the /configtool-manual.bat|.sh command, and
select the Foundation Configure Web Server task.
6 Perform the IBM HTTP Server configuration steps.
See Configuring IBM HTTP Server on page 172.
Validating the Deployment and Generating a

Deployment Report
Validate the deployment. Once the validation report shows no errors, generate a deployment
report.
To validate the deployment and generate a deployment report:

1 From the Start Menu, choose Programs, then Oracle EPM System, then instanceName, then Foundation
Services and then EPM System Diagnostics.
2 To view results, navigate to EPM_ORACLE_INSTANCE/diagnostics/reports and open
validation_report_date_time.html.
3 Resolve any errors, and then run the report again.
See the Oracle Enterprise Performance Management System Installation and Configuration
Troubleshooting Guide for help resolving errors.
4 In a distributed environment, run EPM System Diagnostics on each machine in the deployment.
5 Generate a deployment report:
205
Performing a Maintenance Release Installation for

EPM System Clients
If you are applying the maintenance release to move to Release 11.1.2.3, you must uninstall the
earlier release of the client before you install the new release. For Financial Reporting Studio,
there are additional prerequisites. See Financial Reporting Maintenance Release Installation
For clients that have a new client installer in Release 11.1.2.3, applying the maintenance release
installation option in EPM System Installer does not update the client software. You must install
the client using the client installer.
For details about client installers, see Installing EPM System Clients on page 92.
206
Upgrading EPM System Products
11
In This Chapter
About Upgrading ......................................................................................... 208
Upgrading Checklist ..................................................................................... 209
Upgrade Installation Prerequisites ..................................................................... 212
Downloading and Preparing Files for Installation ..................................................... 214
Preparing Data for Upgrading ........................................................................... 215
Stopping EPM System Services......................................................................... 226
Uninstalling the Earlier Release of EPM System Products ........................................... 227
Installing EPM System Products for an Upgrade ...................................................... 227
Configuring EPM System Products in an Upgrade .................................................... 228
Starting EPM System Services .......................................................................... 235
Validating the Installation ............................................................................... 235
Performing Manual Configuration Tasks ............................................................... 235
Updating References to a Rehosted Environment .................................................... 236
Upgrading Applications from the Earlier Release to the Current Release........................... 250
Performing Manual Configuration Tasks in an Upgrade ............................................. 251
Upgrading Smart View ................................................................................... 260
Upgrading from an Environment with Multiple Releases ............................................. 261
Repeating the Upgrade Process for Applications ..................................................... 262
This chapter describes the upgrade process for EPM System products. To upgrade EPM System
products to Release 11.1.2.3, you deploy Release 11.1.2.3 software in a new location and move
applications and data to the new deployment.
Note: Upgrading does not apply to moving from Release 11.1.2.0 , 11.1.2.1, or 11.1.2.2 to Release
11.1.2.3. Use the Apply Maintenance Release option in EPM System Installer instead.
See Maintenance Release Installation Checklist on page 187. When you apply the
maintenance release, you need not follow the upgrade procedures described in this
chapter.
207
Note: If you have installed a client in a previous release using a Windows installer, you do not
need to uninstall the earlier release of the client. If you have installed a client in a previous
release using EPM System Installer, you must uninstall the client before using a Windows
installer to install the new version of the client. No configuration is required. If you have
an earlier release of Financial Reporting Studio, see Financial Reporting Maintenance
Release Installation Prerequisites on page 193 for additional requirements.
About Upgrading
When using EPM System products, the term upgrade is defined as follows: The process of
deploying a new software release and moving applications, data, and provisioning information
from the earlier deployment to the new deployment.
You can repeat the upgrade process as needed to get the latest data from the previous release.
See Repeating the Upgrade Process for Applications on page 262.
To upgrade EPM System products to Release 11.1.2.3, you install and configure Release 11.1.2.3
software in a new location and move applications and data to the new deployment environment.
There are two supported scenarios:
l Install EPM System on a new machine or machines. You can either reuse the existing database
and data, or replicate the database and data to a new machine.
If you are upgrading to a new machine, you must upgrade to one with the same operating
system. For example, if the earlier release was on a Windows operating system, you must
upgrade to a Windows operating system. If the earlier release was on a Linux operating
system, you must upgrade to a Linux operating system. Within the operating system
constraint, you can switch between versions and editions of the operating system as well as
32-bit and 64-bit variations. For example, you can upgrade from 32-bit Windows 2003 to
64-bit Windows 2008R2.
l Install EPM System on the existing machine or machines (Oracle recommends that you
install in a new installation location). You can either reuse the existing database and data,
or replicate the database and data to a new machine.
Caution! If you want to maintain your earlier release environment, you must install on a
new machine and you must replicate data.
Logs related to upgrading are located in EPM_ORACLE_INSTANCE/diagnostics/logs/

upgrades. For more information about logging during upgrades, see the Oracle Enterprise
Performance Management System Installation and Configuration Troubleshooting Guide.
Supported Upgrade Paths

You can upgrade to EPM System Release 11.1.2.3 from the following releases:
208
Table 29 Supported upgrade paths
Upgrade Path From Release ... To Release 11.1.2.3
11.1.2.x 11.1.2.3
Note that when moving from Release 11.1.2.x to Release 11.1.2.3, you use the "Apply
Maintenance Release" option in EPM System Installer, instead of following the documented
upgrade procedures.
Note: For Financial Close Management, applying the maintenance release is supported
only from Release 11.1.2.1 and 11.1.2.2.
11.1.1.4.x Upgrade to Release 11.1.2.3
Release 11.1.1.0.x to 11.1.1.3.x Apply the maintenance release to Release 11.1.1.4 and then upgrade to Release 11.1.
2.3.
9.3.3.x Upgrade to Release 11.1.2.2 and then apply the maintenance release to Release 11.1.
2.3.
An environment that includes multiple See Upgrading from an Environment with Multiple Releases on page 261.
releases, which can include an environment
with one instance of Shared Services or an
environment with two instances of Shared
Services
Note: If you are starting from Release 9.2.0.3+, 9.3.0.x, 9.3.1.x (except for Oracle Essbase
9.3.1.4.1, 9.3.1.5, 9.3.1.6, and 9.3.1.7), or 11.1.1.x, Oracle recommends that you first upgrade to
Release 11.1.1.3, then apply the maintenance release to Release 11.1.1.4, and then upgrade to
Release 11.1.2.3. If you are starting from an earlier release, Oracle recommends that you upgrade
to the highest level release that directly supports upgrade from your starting release. Security
Synchronization between Essbase and Shared Services was removed in Essbase Release 9.3,
starting with Release 9.3.1.4.1. Essbase and Oracle Hyperion Shared Services Release 11.1.1.3,
however, still synchronize security information. For this reason, if you are using Oracle Essbase
Release 9.3.1.4.1, 9.3.1.5, 9.3.1.6, or 9.3.1.7, you must first upgrade all products to Release 9.3.3,
then upgrade to Release 11.1.2.2, and then apply the maintenance release to Release 11.1.2.3.
Upgrading Checklist
The following table identifies the high-level tasks that you perform to upgrade EPM System
products. You must perform tasks in this order and you must complete the entire checklist.
The process described in this chapter assumes that you upgrade one product at a time and
indicates where a sequence is required.
Note: If you are upgrading from an environment with multiple releases, see Upgrading from
an Environment with Multiple Releases on page 261.
209
Table 30 Upgrading Checklist
Task Reference Check When

Completed
Go through the tasks in the following section once for all EPM System products at one time.
Preparing to Upgrade
1. Review release compatibility, system requirements, and l Oracle Enterprise Performance

other prerequisites for this release. Management System Certification Matrix
(http://www.oracle.com/technetwork/
If your database environment needs to be upgraded, perform
the database upgrade before you proceed. See the database middleware/ias/downloads/fusion-
documentation for details. certification-100350.html)
2. Prepare the new environment for the new Release 11.1.2. l Chapter 3, Preparing Your Environment
3 installation.
Note: Create a new database to store Shared Services data.
(However, if you are upgrading from Release 11.1.1.4 and you
used one database repository for all products, you do not need
to create a new database for Shared Services. The Shared
Services tables will be dropped during configuration.)
Tip: In preparation for a new installation, you can use a
worksheet to note the machines on which earlier release
products are installed, and the machines on which you plan
to install the new release products. You can refer to this
information in subsequent procedures.
3. Perform upgrade-specific prerequisite tasks. Upgrade Installation Prerequisites on page

212
4. Download and prepare the installation files. Downloading and Preparing Files for
Installation on page 214
5. Prepare data for upgrading. Preparing Data for Upgrading on page 215
6. Stop EPM System services if you are upgrading on the same Stopping EPM System Services on page
machine. 226
7. Uninstall the earlier release of EPM System products. Uninstalling the Earlier Release of EPM System
Products on page 227
Oracle recommends that you uninstall if you are upgrading to
the same machine.
210
Completed
Iterate through the following checklist items for each product, one product at a time, in the following order:
l Foundation Services.
l Essbase Server and all other Essbase products. Note that after configuring other Essbase products, you must also configure the Web
server. After configuration, restart the Web Server and EPM Workspace.
l All other EPM System products, in any order. Note that after configuring each product, you must also configure the Web server. After
configuration, restart the Web Server and EPM Workspace.
Tip: Oracle recommends that after completing each step, you return to this checklist so that you perform the upgrade steps in the correct
order.
Installing and Configuring
8. Install EPM System products (choosing the New l Installing EPM System Products for an
installation option) in a new installation location. Upgrade on page 227 for information
specific to installation when you are
Tip: After installation, use the EPM System Defects Fixed
Finder on My Oracle Support (https://support.oracle.com/ upgrading
oip/faces/secure/km/DocumentDisplay.jspx?id=1292603. l Chapter 5, Installing EPM System Products
1) to determine whether any patches are required for your in a New Deployment for general
environment. If required, apply the patches after installation. information about installation
9. Configure Release 11.1.2.3 products. l Configuring EPM System Products in an

Upgrade on page 228 for information
You must configure Foundation Services first. Foundation
specific to configuration when you are
Services must be installed and configured for other products
to configure successfully. upgrading
Caution! If you have already configured the Web server and

you configure any additional products, you must run EPM
System Configurator again and select the Foundation Services
Configure Web Server task. Then, restart the Web server and
EPM Workspace.
10. Start EPM System services. Chapter 12, Starting and Stopping EPM
System Products
Validating the Installation
11 Using EPM System Diagnostics, validate the installation. Chapter 13, Validating the Installation and
Verifying Deployment
Performing Post-Configuration Tasks
12. Complete product-specific manual configuration tasks. Chapter 9, Performing Manual Configuration
Tasks in a New Deployment
13. If products have been rehosted on a new server, make Updating References to a Rehosted
updates, such as updating data source connections. Environment on page 236
211
Completed
14. Upgrade applications for the following products from the Upgrading Applications from the Earlier
earlier release to the current release: Release to the Current Release on page 250
l FDM
Note that Planning applications are upgraded using the

Upgrade Wizard, which also includes steps for rehosting. Other
applications are upgraded during configuration.
15. Perform product-specific upgrade tasks for products that Performing Manual Configuration Tasks in an
you upgraded. Upgrade on page 251
For clients that have a new client installer in Release 11.1.2.3, upgrading does not update the
client software. You must install the client using the client installer. See Installing EPM System
Clients on page 92.
For Predictive Planning, note the following:
l Upgrade all Predictive Planning client versions at the same time, so that all users can see
new features.
l Administrators should make Form setup changes using the updated Predictive Planning
version. Making changes with older versions can result in loss of Form setup data.
Upgrade Installation Prerequisites

Subtopics
l Backing Up the Earlier Release
l Performing Product-Specific Upgrade Prerequisites
l Business Rules Maintenance Release and Upgrade Installation Prerequisites
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 for Release
11.1.1.4 products, see the Oracle Enterprise Performance Management System Backup and
Recovery Guide.
Performing Product-Specific Upgrade Prerequisites

Ensure that you meet the following product-specific requirements:
l If you are upgrading from Release 11.1.1.4 and Shared Services was configured with NTLM
as an external user directory you must migrate users before you upgrade:
In 11.1.1.4, migrate NTLM Users to another user directory (usually Active Directory). Also,
remove NTLM from the list of configured user directories. Detailed procedures are in
212
Release 11.1.1.4 Oracle Enterprise Performance Management System Security Configuration
Guide.
l If you are using Business Rules, you must migrate to Calculation Manager rules in Release
11.1.2.3. You must perform prerequisite steps before you upgrade. See Business Rules
Maintenance Release and Upgrade Installation Prerequisites on page 213.
l For Financial Reporting, if both the source and target machines are Windows server
machines, ensure that the SMB 2.0 protocol is disabled on both the source and target
machines before performing the upgrade.
l For Strategic Finance, you must convert the Strategic Finance database using a conversion
utility. Oracle recommends that you back up the database before converting it. Apply
Strategic Finance Release 11.1.2.1.000 Patch Set Exception (PSE): 13776302 and then run
the conversion utility.
l For FDMEE, for any data rules that were not run in Release 11.1.1.4, specify a default value
for the scenario dimension. If you do not specify a default value, these rules are not accessible
in the new release. If you were using Performance Management Architect Essbase
applications in Release 11.1.1.4, use Refresh Metadata in Target Application before proceeding
to do any data load.
l For FDM, when you are using Financial Management, Essbase, Planning, or Hyperion
Enterprise as target systems, the target system clients must be installed on the same server
as FDM.
l If you are using FDM and you are using IIS as the Web Server to host EPM Workspace, you
must install the FDM Web application and the EPM Workspace Java web application on
the same box.
When you are done with this step, return to the Upgrading Checklist on page 209.
Business Rules Maintenance Release and Upgrade

Installation Prerequisites
If you are applying the maintenance release to move from Release 11.1.2.0 or Release 11.1.2.1
to Release 11.1.2.3, or if you are upgrading from an earlier release, and if you have been using
Business Rules in the earlier release, you must migrate to Calculation Manager rules in Release
11.1.2.3. Before migrating business rules, you must perform prerequisite tasks.
If you are applying a maintenance installation from Release 11.1.2.2, you can skip this step.
To prepare to migrate Business Rules, perform the following tasks in your current Business
Rules environment before installing Release 11.1.2.3:
1 In Business Rules, within the Rule Editor, remove the associated outline (that is, the design time location)
from each business rule. After you do this, the Associated Outline drop-down list should display the text,
Select Outline.
2 On the Locations tab of the Rule Editor, ensure that each business rule has a valid launch location,
which must be an absolute location. Although All Locations is valid in Business Rules, when you
migrate business rules, you must provide the details of a specific launch location (that is, the application
213
type---Planning or Essbase, the server name, the application name, and the database or plan type). If
you want a business rule to be valid for multiple launch locations, you must provide the details for each
location. The locations must be in different applications; you cannot migrate the same business rule to
different plan types in the same application within Calculation Manager.
If the rule is a part of a sequence, then the launch location of the rule within the sequence
must be one of the launch locations listed in the Locations tab of the rule.
3 On the Access Privileges tab of the Rule Editor, ensure that each business rule has security defined for
a specific location or locations and not All Locations. If multiple locations are defined for a business
rule on its Locations tab, you must add security for each location individually.
4 Do not modify rules in Calculation Manager until migration is completed.
5 If you are using Business Rules with Planning, as a precaution, create a backup of the rules: Use
Administration Services to export the rules to XML in Business Rules format. If you are upgrading from
11.1.1.4, also export the rules to Calculation Manager format. EPM System Configurator exports the
rules during database configuration for use during application upgrade.
6 If you are an Essbase-only Business Rules user, you must export business rules. To export the Essbase
rule from Business Rules:
a. From Administration Services Console, right-click the Business Rules node and select
Export.
b. Export the rules in Business Rules format and then select all of the Essbase rules in the
repository. If you are upgrading from 11.1.1.4, also export the rules to Calculation
Manager format.
c. Specify the location to save the XML file, and then click OK. If you are upgrading, the
location should be a shared drive that is accessible from the upgraded environment.
Make a note of the location. You import the file later in the process.
During configuration with EPM System Configurator, rules are prepared for migration when
you perform the Configure Database task.
After configuration, there are additional tasks you perform to import and migrate business rules.
Downloading and Preparing Files for Installation

Download files for Release 11.1.2.3 and extract the zip file contents. See Chapter 4, Downloading
Files for Installation.
214
Preparing Data for Upgrading
Subtopics
l Exporting Shared Services Data from the Earlier Release
l Exporting Financial Management and Strategic Finance Data from the Earlier Release
l Copying Files for Temporary Use During Configuration
l Replicating Data
l Replicating the Databases
Exporting Shared Services Data from the Earlier Release

To use data from the earlier release of Shared Services, you export the data using a utility, and
then copy the resulting file to the machine hosting the new installation. During configuration,
EPM System Configurator extracts the necessary data for use in the current release.
Note: The database, Shared Services, and OpenLDAP must be running before you perform this
procedure.
Note: Before you migrate Shared Services data, ensure that the admin user is provisioned for
the Essbase Server. You can remove this provisioning after the upgrade is complete.
To export Shared Services data from the earlier release:

1 If you have not already done so, download files for Release 11.1.2.3 and extract the contents of the
System Installer ZIP file.
If you have not yet downloaded the System Installer ZIP file (Oracle Hyperion
Enterprise Performance Management System Installer, Fusion Edition
Release 11.1.2.3 for platformName), download it from the Oracle Software Delivery
Cloud. See Chapter 4, Downloading Files for Installation.
2 In the SystemInstallerExtractLocation/Migration directory, look for
HSSMigrate.zip and extract the contents to the HYPERION_HOME directory on the machine
hosting the earlier release of Shared Services.
3 From a command line, run the following script from the HYPERION_HOME/Migrate directory:
hssmigrate.bat|sh
The utility searches for Shared Services configuration files and prompts you for
confirmation.
Tip: To ensure successful export of Lifecycle Management data from Release 11.1.1.4 on
UNIX, set executable permissions on set_hyphome_servername_1.sh, in $home/.
215
4 At the prompt, review the location from which the utility will extract Shared Services configuration files.
If the path is correct, press Enter. If the path is not correct, enter 2, specify the correct path, and then
press Enter.
Tip: The path you enter should be the path for the CSS.xml, Domain.xml, and
WorkflowEngine.properties files, for example: HYPERION_HOME/AppServer/
InstalledApps/WebServerName/WebServerVersion.
The utility creates a file, hssmigratedata.zip, in HYPERION_HOME/migrate, that stores

the Shared Services data.
Tip: If the utility reports errors, review the logs in HYPERION_HOME/migrate/logs,

correct any errors, and then re-run the utility to generate a new ZIP file that replaces
the existing file.
5 Copy hssmigratedata.zip from HYPERION_HOME/migrate to the machine on which you plan
to host the new release of Shared Services, or make the file available on a shared drive. (If you are
installing on the same machine, make sure the location is outside of HYPERION_HOME.)
You specify the location during configuration.
6 In a distributed installation, for some products, if products will be installed on a machine or machines
other than the machine hosting Shared Services, copy hssmigratedata.zip to each machine.
This step is required for Essbase Studio, Web Analysis, and Performance Scorecard.
Create the MIDDLEWARE_HOME directory if it does not exist. You must specify this
MIDDLEWARE_HOME during installation.
For more information about what happens during Shared Services data import, see What
Happens During Shared Services Data Import on page 233.
Exporting Financial Management and Strategic Finance Data

from the Earlier Release
For Financial Management, you must prepare for provisioning for the Application Creator and
Financial Management Administrator roles for groups that previously had these rights. You
export provisioning information, and during database configuration later in the upgrade
process, the provisioning is automatically performed.
If you customized Strategic Finance files in the earlier release, you export the data using a utility,
and then copy the resulting file to the machine hosting the new installation. These steps are
required only if there are customizations to these files. If no customizations have been made to
these files, you can skip this step; use the base files that are installed with Release 11.1.2.3.
l .coa: chart of accounts files
l .drs: default report spec files
l .alc: alcar file
216
l .alt: alcar template
l currencies_user.xml
l convert.idx
To export Financial Management and Strategic Finance data from the earlier release:
System Installer ZIP file to any machines hosting Financial Management and Strategic Finance.
If you have not yet downloaded the System Installer ZIP file (Oracle Hyperion
Enterprise Performance Management System Installer, Fusion Edition
Release 11.1.2.3 for platformName), download it from the Oracle Software Delivery
Cloud. See Chapter 4, Downloading Files for Installation.
HSSMigrate.zip and extract the contents to the HYPERION_HOME directory on all machines
hosting the earlier release of Financial Management and Strategic Finance.
3 On machines hosting Financial Management, perform the following steps:
a. From a command line, run the following script from the HYPERION_HOME/Migrate
directory:
hfmmigrate.bat
The utility searches for Financial Management files and generates a zip file with their
contents in HYPERION_HOME/migrate/temp/HFM.
b. Create a zip file of the contents of the folder: HYPERION_HOME/migrate/temp/HFM.
c. Copy the zip file to the machine on which you plan to host the new release of Financial
Management and unzip it in MIDDLEWARE_HOME/EPMData
4 On machines hosting Strategic Finance, perform the following steps:
a. From a command line, run the following script from the HYPERION_HOME/Migrate
directory:
hsfmigrate.bat
The utility searches for Strategic Finance files and generates a zip file with their contents
in HYPERION_HOME/migrate/temp/HSF.
b. Create a zip file of the contents of the folder: HYPERION_HOME/migrate/temp/HFM.
c. Copy the zip file to the machine on which you plan to host the new release of Strategic
Finance and unzip it in MIDDLEWARE_HOME/EPMData
Copying Files for Temporary Use During Configuration

If you are upgrading Provider Services or Administration Services, some files from the earlier
release of EPM System are required during configuration of the new release. You must make the
217
files available on a shared drive or copy them from the earlier release installation to the machine
hosting the new installation for use during configuration with EPM System Configurator.
During configuration with EPM System Configurator, this data is moved to the Shared Services
Registry and the files are no longer used.
To copy the files required for configuration:

1 On the machine hosting the new release installation, prepare a temporary location to store files from
the earlier release.
During configuration, you specify the location of these files. By default, EPM System
Configurator looks for the data in MIDDLEWARE_HOME/EPMData.
2 Copy the following files from the earlier release installation to the directory that you just created:
Table 31 Files for Temporary Use During Configuration
Product Files to Copy for Temporary Use
Provider Services Copy the following three Provider Services files to a single folder with no subfolders (for example EPMData/aps):
l essbase.properties, from HYPERION_HOME/products/Essbase/aps/bin
l datasources.xml, from HYPERION_HOME/products/Essbase/aps/bin
l domain.db, from HYPERION_HOME/products/Essbase/aps/data
Additionally, copy smart slice definitions located in HYPERION_HOME/products/Essbase/aps/data/

cubeviews. Copy the entire cubeviews directory structure.
Administration l Copy the entire storage directory structure located at HYPERION_HOME/products/Essbase/eas/

Services storage.
Reporting and server.xml, located in HYPERION_HOME/common/workspacert/9.5.0.0/common/config/dynamic/

Analysis UUID, where UUID is the dynamic ID for the folder.
If there is more than one UUID folder, retrieve server.xml from the folder that contains irdas_default.txt.
Make note of the location to which you replicate the data. During postconfiguration tasks for Interactive Reporting,
you specify the location of this file when you import DAS data sources.
Replicating Data
When you upgrade to EPM System Release 11.1.2.3, you use the data from the earlier release in
one of two ways:
l You can replicate the data to a new machine, making it accessible from the new installation
environment. For example, use this option if you want to maintain the earlier release
environment.
During product configuration with EPM System Configurator, you specify the new,
replicated location for data when you configure the product data directory locations.
Note: Oracle recommends that you replicate data.
218
l You can leave the data on the existing machine, making the drive shareable. If you choose
to leave data on the existing machine, you can skip the procedures in this section. During
product configuration with EPM System Configurator, you specify the existing data
location. You can choose this option only if you no longer need to maintain the earlier release
environment.
Note: For Essbase, you can choose this option only if the data is on a supported type of
shared drive, such as a SAN drive.
To replicate product data files:

1 On the shared drive or machine hosting the data for the new release, create directories to store the
replicated product data.
Tip: This location is the data storage location for Release 11.1.2.3, so store data in a
meaningful, permanent location. You might choose to specify a location for each
product, for example: EPMData/productName. Do not store data in the directory that
is to be used as EPM_ORACLE_INSTANCE, which in a default installation is Oracle/
Middleware/user_projects/epmsystem1. (EPM_ORACLE_INSTANCE must be
an empty directory.)
2 Replicate data as noted in the following table for each EPM System component.
During configuration during an upgrade, EPM System Configurator prompts you for the
data location.
Table 32 Data to Replicate for Upgrading
Product Data to Replicate
Essbase Essbase provides a tool to help with replicating data. See Preparing Essbase Data for Upgrading on page 220. In
addition, note the following:
If you are installing this release of Essbase on a new machine, gather additional data from the machine hosting the
earlier release installation:
l Make a list of the ODBC DSNs defined on the machine so that you can redefine them on the new machine. Perform
this step for Essbase and Integration Services.
l Make a list of JAVA options (ESS_JVM_OPTIONn) that are set on the machine so that you can redefine them on
the new machine.
Note: You can provide a UNC path for ARBORPATH. When you use a UNC path, table spaces and disk volumes must
also be in UNC format.
Essbase Studio Text files that are used as data sources. These files were stored by default in HYPERION_HOME/products/Essbase/
EssbaseStudio/Server/datafiles.
Note: Make note of the location to which you replicate the data. During configuration with EPM System Configurator,
you enter this location on the Configure Essbase Studio Location for Sample and Customer Data Source Text
Files configuration page.
Administration Copy the following file from the machine hosting the Release 11.1.1.4 installation to the data storage location: EAS_
Services HOME/server/lib/cryptix32.jar.
219
Product Data to Replicate
Reporting and Data files.

Analysis
By default these files were stored in HYPERION_HOME/products/Foundation/workspace/data/RM1_
servername.
you enter this location on the Reporting and Analysis Framework Services configuration page, for Repository
Directory.
Performance Attachment and note files.

Scorecard
By default these files were stored in the /attachments and /notes directories in following location:HYPERION_
HOME/deployments/WEB_SERVER/webappsconf.
you enter this location on the Performance Scorecard configuration page, for Specify directory to store Performance
Scorecard files.
Strategic Data files.

Finance
By default these files were stored in HYPERION_HOME/products/hsf/HSFData.
Note: Make note of the location to which you replicate the data files. During configuration with EPM System
Configurator, you enter this location on the Strategic Finance configuration page.
FDM Data files. For each application, copy the entire data directory structure. To see the location of the source application
data: From Workbench client, select Add Application, select the application, click Modify and then note the data
location. Repeat for each application.
The FDM data directory on the new machine should be a UNC share and should be available to the DCOM user used
to configure FDM. This directory structure must be replicated to the new environment if it is not accessible from the new
environment.
Note: Make note of the location to which you replicate the FDM data directory. During FDM configuration, for each
application, you specify the new data directory.
Preparing Essbase Data for Upgrading

The Essbase Staging Tool simplifies preparing data for upgrade. If you need to replicate data,
use the following procedure. You must replicate all applications. If you do not want some of the
applications in the upgraded environment, delete them after completing the entire upgrade
process.
Notes:
l The Essbase Server must be running before you launch the Essbase Staging Tool. The tool
shuts down the Server as needed. To ensure data integrity, disable logins and make sure no
users are active before starting the Staging Tool.
l If the ESSLANG environment variable is not set on the machine on which you are running
Staging Tool, the Staging Tool sets the value to
English_UnitedStates.Latin1@Binary. The ESSLANG value for the Staging Tool
should be same as the ESSLANG value for the Essbase Server.
l On a 64-bit Linux system, before you run the Staging Tool, install the 64-bit version of the
libaio package version 0.3.105-2 or higher.
220
If you are upgrading from an earlier release and an application has more than 127 linked
reporting objects, perform the following procedure to export linked reporting objects before
you run the Staging Tool.
Tip: To determine how many linked reporting objects an application has, use the MAXL
command query database DBS-NAME list lro all;, for example, MAXL> query
database sample.basic list lro all;.
To export linked reporting objects:

1 On the machine hosting the earlier release of Essbase, export linked reporting objects by backing up
the application linked reporting object data to a specified directory by using the following MAXL
command:
EXPORT database DBS-NAME LRO to server directory directoryName;
For example:
MAXL> EXPORT database Sample.Basic LRO to server directory V1;
In this example, Sample.Basic LRO data is exported to Sample-Basic-V1 in

ARBORPATH/app, where ARBORPATH is the server ARBORPATH.
2 Delete the linked reporting objects from the earlier release application with the following MAXL
command:
ALTER database DBS-NAME delete LRO all;
For example:
MAXL> ALTER database sample.basic delete LRO all;
3 Move the application to Release 11.1.2.3 using the Staging Tool, described in the next procedure.
4 Note that you must manually import the linked reporting objects later in the upgrade process.
Tip: If you want to maintain your earlier release environment, reimport the linked reporting
objects on the source system after the upgrade process is complete.
To prepare Essbase data for upgrading perform the following tasks on the machine hosting
the earlier release installation:
1 Oracle recommends that you perform data validation for Essbase applications:
l Start Essbase Server.
l Use the MaxL command alter system resync sss to sync up security information.
l For BSO applications, use the MaxL command alter database
applicationName.databaseName validate using default error_file;
against the database. If the validation returns errors, revert to a backup that is free of
errors or fix the errors before you proceed with the upgrade.
l Use the following MaxL commands to search for user and group errors: display
group all failed_sss_migration; and display user all
221
failed_sss_migration;. If the commands return any errors, resolve the errors
before proceeding.
l Stop Essbase Server and back up all application files, database files, and the security file.
l Restart Essbase Server and then in Administration Services Console, run a full
restructure on the database.
2 Using Administration Services, edit Application Properties for each application (select General then
Startup) to ensure that Start application when Essbase Server starts is NOT selected.
You can also view this property for all applications using the MAXL command display
application all; to ensure that autostartup is set to FALSE for all applications. (Use
the MAXL command alter application DBSName disable autostartup; to turn
off the property for each application as needed.)
System Installer ZIP file.
If you have not yet downloaded the System Installer ZIP file, download it from the Oracle
Software Delivery Cloud. See Chapter 4, Downloading Files for Installation.
Extract the contents to a directory that does not have spaces in the name.
EssStagingTool.zip and extract the contents to any empty directory
(EssStagingToolExtractLocation) on the machine hosting the earlier release of Essbase.
For Windows, use the version of the Staging Tool for the platform from which you are
upgrading. For example, if you are upgrading from a 32-bit machine to a 64-bit machine,
use the 32-bit Staging Tool.
5 From a command line, run the following script from the EssStagingToolExtractLocation
directory:
essStage.bat|sh username [agentPort]
where username is the name of any Essbase user who is an administrator. agentPort is
optional and specifies the port on which the Essbase instance is running. The default value
is 1423.
6 When prompted, enter the administrator password.
The Staging Tool queries Essbase for a list of applications and the disk volumes that are
defined, and for ASO applications it queries for a list of table spaces that are defined.
7 At the prompt, review the list of methods for preparing data for upgrade, and then select a method:
l Same-named disk volumes, table spaces, and ARBORPATH on source and target. This
option is the fastest. If you select this method, the system you are upgrading on must
use the same disk volume, table spaces, and ARBORPATH as the earlier release.
l Differently-named disk volumes, table spaces, or ARBORPATH on source and target. If you
select this method, you can specify a different disk volume, table spaces, or
222
ARBORPATH on the system you are upgrading to than what is defined on the earlier
release system.
Note: If you select this method, make note of the new ARBORPATH location. During
configuration with EPM System Configurator, you enter this location on the
Essbase configuration page, for Full path to application location (ARBORPATH).
l Consolidated disk volumes or tablespaces on target by exporting data. Select this method
if you want to consolidate disk volumes on the system to which you are upgrading. This
method exports data to text files so that you can later import them on the upgraded
system. Because this method is the slowest, use it only if you need to consolidate disk
volumes, for example if the source machine has volumes defined for c, d, and e drives
and the target machine has only c and d drives. This option performs some data
validation during export.
8 Select whether you want to apply this method to all applications or to only some applications.
Note that all applications must be replicated to ensure the integrity of the essbase.sec
file. If you select only some applications, you must select a second method of preparing the
data for all remaining applications.
If you select Yes for Select all applications, proceed to step 11.
9 If you selected No for Select all applications, enter the number for each application to which you want
to apply the first data preparation method that you selected. When you are finished selecting
applications, press Enter.
10 If you selected No for Select all applications, select the data preparation method to use for all of the
remaining applications.
If you selected Same-named disk volumes, table spaces, and ARBORPATH on source and
target or Differently-named disk volumes, table spaces, or ARBORPATH on source and target,
the Staging Tool automatically selects Consolidated disk volumes or tablespaces on target by
exporting data for the remaining applications.
11 Depending on the data preparation method that you selected, the next steps vary:
l If you selected Same-named disk volumes, table spaces, and ARBORPATH on source and
target, enter Y to proceed with preparing data.
The Staging Tool prepares essbase.cfg, essbase.sec, data, and applications for file
transfer.
l If you selected Differently-named disk volumes, table spaces, or ARBORPATH on source
and target:
a. Specify a new ARBORPATH location for the machine on which you are upgrading
and then press Enter. The ARBORPATH for the current release is displayed in
parentheses for your reference.
223
Tip: The ARBORPATH that you specify cannot be the directory that is to be used as
EPM_ORACLE_INSTANCE, which in a default installation is Oracle/
Middleware/user_projects/epmsystem1. (EPM_ORACLE_INSTANCE
must be an empty directory.)
Tip: ARBORPATH is the location for applications; previous releases used

ARBORPATH to refer to the installation location. ESSBASEPATH is now used to
define the installation location. For more information, see Understanding
How Essbase Files Are Stored in the Oracle Essbase Database Administrator's
Guide.
b. If prompted, specify a new disk volume for the machine on which you are upgrading
and then press Enter. The disk volume for the current release is displayed in
parentheses for your reference.
c. If prompted, specify a new default tablespace for the machine on which you are
upgrading and then press Enter. The default tablespace for the current release is
displayed in parentheses for your reference. (This step applies only to ASO
applications.)
d. Enter Y to proceed with preparing data.
The Staging Tool prepares essbase.cfg, essbase.sec, data, and applications for file
transfer, updating internal references to ARBORPATH, disk volumes, and tablespaces as
needed. Later in the upgrade process you must run a script (editagtsec.msh) to
update disk volume settings in essbase.sec for the relocated applications.
l If you selected Consolidated disk volumes or tablespaces on target by exporting data:
a. Specify the directory to which to export data, and then enter Y to proceed with
preparing data.
The tool prepares a list of data to export, and then copies the data to the export
directory you specified. It shuts down Essbase before copying files. If it cannot shut
down Essbase, you are prompted to shut down Essbase.
b. If you are prompted to shut down Essbase, shut it down, and then press Enter to
continue.
The Staging Tool prepares data files, exported data along with a script to import it, and
a script for editing the security file.
Note that with this option, you must perform additional tasks later in the process: You
must run a script (editagtsec.msh) to update disk volume settings in
essbase.sec for the relocated applications. You must manually import LROs and data
later in the upgrade process using a script (importdata.msh).
The Staging Tool displays the processing status for each application.
If the Staging Tool displays the error Cannot open file [%s] for sample applications,
you can ignore the message. EPM System Installer installs sample applications on the new
host machine.
224
Note that the Staging Tool copies all of the files and directories under the specified
ARBORPATH, disk volume locations, and tablespace locations.
12 Review the methods for transferring the processed files, select a method, and then enter Y to continue.
l Automatically copy files to a mounted or mapped file system. If you select this option, the
Staging Tool prompts you for the mounted drive location for each of the destination
ARBORPATH, table space, disk volume, and export data directory directories. Specify the
mounted path of the same ARBORPATH path that you specified during the data
preparation method. The destination path for tablespace should map to the tablespace
specified in the data preparation method. The destination path for disk volume path
should map to complete paths and not just to disk volume.
Specify an existing, empty directory.
If errors occur during file transfer, the Staging Tool closes and shuts down Essbase.
The Staging Tool also prepares a file with file transfer instructions. If the copy process
fails for any reason, follow the instructions in EssStagingToolExtractLocation/
work/FileTransferSteps.txt to manually copy the data to the machine on which
you plan to upgrade Essbase.
l Get a list of file transfer instructions. If you select this option, the Staging Tool exports
data and prepares a file with file transfer instructions. Review
EssStagingToolExtractLocation/work/FileTransferSteps.txt for details
and follow the steps to manually copy the data to the machine on which you plan to
upgrade Essbase.
l Exit. If there were any failures or errors during the application processing, you can exit,
correct the errors, and restart the Staging Tool.
Delete the working directory so the Staging Tool can recreate it.
The Staging Tool notes when the file transfer is complete and shuts down Essbase.
13 If needed, update the files on the target machine to ensure that they have the same owner as the user
who will install Essbase.
EssStagingToolExtractLocation/work/FileTransferSteps.txt includes the list
of files to update.
14 (Optional) Review the log file, EssStagingToolExtractLocation/essStaging.log, for
details of the Staging Tool actions.
You can use the log during configuration with EPM System Configurator to remind you of
the options you specified.
If you realize that you made mistakes in your entries for the Staging Tool, you can rerun it.
15 On the target machine hosting the new release, make required updates to essbase.cfg: Update the
DISKVOLUMES, SSAUDIT, SSAUDITR, and TransactionLogLocation settings to reflect new
directory locations.
225
Note: The Staging Tools copies ARBORPATH/app/appname/dbname/Replay, which is related
to the transaction logging and replay feature. Because Oracle recommends a fresh
implementation of transaction logging and replay in any given Essbase release, Oracle
recommends that you delete these files on the upgraded system before you proceed. As a
best practice, the files in the LOGLOCATION and Replay directories should be backed up
periodically.
When you have finished preparing Essbase data for upgrading, return to Replicating Data on
page 218 to replicate data for other EPM System products.
Replicating the Databases

Optionally, replicate the entire database or databases to a new machine or machines. Oracle
recommends that you replicate the databases.
During database configuration with EPM System Configurator, specify the new product
database location.
Note the following about replicating databases:
l If the database version needs to be updated, perform the database upgrade before replicating
data.
l If you want to maintain the earlier release installation, you must replicate the databases.
l You do not need to replicate the Shared Services database. Shared Services requires a new
database and data from the earlier release is imported during configuration.
l If you are upgrading from Essbase Studio Release 11.1.1.4, ensure that the data is valid before
you upgrade to ensure successful upgrade.
l For Financial Management and MS SQL Server, if you are restoring a backup of an existing
database in a new environment, make sure that the current database user has access to the
imported database objects. This can be accomplished using a script such as
master.sp_change_users_login.
Stopping EPM System Services

If you are installing Release 11.1.2.3 on the same machine as the earlier release installation, stop
all EPM System services. If you need details about stopping services, see Chapter 12, Starting
and Stopping EPM System Products.
226
Uninstalling the Earlier Release of EPM System
Products
Oracle recommends that you uninstall earlier releases of EPM System products unless you want
to maintain the earlier release environment. During uninstallation, when prompted whether
you want to delete all the files and directories in the EPM Oracle home directory, select No unless
you have moved your data to another location.
Note: If you are upgrading on the existing machine, and you want to uninstall the earlier release,
you must uninstall before you install Release 11.1.2.3. (Oracle recommends that you
install Release 11.1.2.3 on a new machine.) You cannot uninstall the earlier release of
Shared Services after you upgrade to the new release on the same machine.
If you are upgrading FDM on the existing machine, you must uninstall the earlier release
before you proceed.
Tip: If you choose not to uninstall the earlier release and you are upgrading on the existing
machine, you might need to edit the PATH variable to remove all references to the earlier
release. This can prevent you from reaching the character limit for the PATH variable when
you configure.
Installing EPM System Products for an Upgrade

Install EPM System products using EPM System Installer, as described in Chapter 5, Installing
EPM System Products in a New Deployment.
Note the following about installing EPM System products in an upgrade:
l When you upgrade, install and configure using the same user that was used to install and
configure the earlier release.
l For each machine, you can install all the products that you plan to host on that machine at
one time. For additional requirements for a distributed installation, see Installing EPM
System Products in a Distributed Environment on page 81.
l If you are installing on the same machine, in a new location, you must install and configure
using the same user that was used to install and configure the earlier release.
l Oracle recommends that you install Release 11.1.2.3 on a new machine.
l If you are installing on the same machine as the earlier release, EPM System Installer warns
you that the earlier release might no longer work after you install the current release.
227
Configuring EPM System Products in an Upgrade
After you install, use EPM System Configurator to configure EPM System products.
Caution! Do not proceed with configuration until you have exported Shared Services data
from the earlier release. See Exporting Shared Services Data from the Earlier
Release on page 215.
Upgrade configuration notes:

l Ensure that the external authentication provider is online before you start EPM System
Configurator.
l Before starting EPM System Configurator, copy cryptix32.jar from the Administration
Services data storage location (for example EPMDATA/EAS) to EPM_ORACLE_HOME/
upgrades/eas/lib.
l You must configure Foundation Services first. Foundation Services must be installed and
configured for other products to configure successfully.
l In a distributed environment, for Shared Services, perform the Configure Database and
Import data from earlier release tasks on each machine on which Shared Services is installed
before configuring any other products. For other products, you perform the import data
tasks on only one machine in a distributed environment.
l Configure Essbase and Essbase products next.
l You must perform the Configure Database task at the same time as or before you perform
the Deploy to Application Server task.
l Because you are configuring products one at a time, configure the Web server after each
product. (Select the Foundation Services Configure Web Server task.) After configuration,
restart the Web server and EPM Workspace.
l You must deploy all EPM System products to a single WebLogic domain. The exceptions
to this requirement are documented in Deploying Financial Management, Financial
Reporting, and Web Analysis on Windows in a UNIX-Based EPM System Deployment on
page 153.
l If you are upgrading multiple instances of Essbase, for each instance that you are upgrading
from, you must create a new instance in Release 11.1.2.3. See Configuring and Starting
Additional Instances of Essbase Server in the Oracle Enterprise Performance Management
The following table describes the tasks that you must select in EPM System Configurator and
describes the tasks EPM System Configurator performs during upgrade. For details about
running EPM System Configurator, see Chapter 6, Configuring EPM System Products in a New
Deployment or click Help.
228
Note: For all products other than Shared Services, during product database configuration, select
Upgrade the existing databases to the current release from... and select a release number.
Then, enter connection information for the existing or replicated database.
To launch EPM System Configurator, from the Start menu, select Programs, then Oracle
EPM System, and then EPM System Configurator (all instances).
Table 33 Required Configuration Tasks During Upgrade
Product Configuration Tasks What Happens During Upgrade
All products Configure Oracle Instance

Typically, if you are installing all products on a single machine, for the
first product you configure, you create a new EPM Oracle instance. For
each product after that, you modify the existing EPM Oracle instance. If
you are installing in a distributed environment, create a new EPM Oracle
instance on each machine.
Shared l Configure Common Settings Imports Shared Services data from the
Services earlier release. For more information about
Configure Database
this process, see What Happens During
l
l Configure Oracle Configuration Manager Shared Services Data Import on page

l Configure Web Server 233.
l Deploy to Application Server Note: You see applications in EPM
Workspace and provisioning information in
Import data from earlier release
Shared Services only after a product is
l
reregistered and applications are migrated.

During Shared Services database configuration, select Perform first-
time configuration of Shared Services database, and then enter You see EPM Workspace preferences
connection information for a new database. upgraded from the earlier release only after
you have upgraded all EPM System
If you configured all EPM System products to use one database, you are components and you have started Reporting
alerted that pre-existing Shared Services tables have been detected in and Analysis Framework. In addition, users
the database. When prompted to drop and recreate the tables, select must be provisioned with a Reporting and
Yes. Analysis role other than IR HTML Viewer or
For the Deploy to Application Server configuration task, deploy to a new IR WebClient Viewer.
WebLogic domain.
For the Import Data From Earlier Release configuration task, specify the
location from which to import Shared Services data. You must specify the
full path to hssmigratedata.zip, which is created with the Shared
Services Upgrade Utility.
Caution! Perform this task only once on a machine.
In a distributed environment, perform the Configure Database and
Import data from earlier release tasks on each machine on which
Shared Services is installed before configuring any other products.
When you are done with this step, return to the Upgrading Checklist on
page 209.
229
Essbase l Configure Essbase Server Registers applications with Shared Services

and upgrades applications.
On the Configure Essbase Server page, for Full path to application Note: When you upgrade from an earlier
location (ARBORPATH),: release, a backup of the security file for the
If you are upgrading to a new machine, specify the location of the earlier release is created before the security
file is upgraded. The security file backup,
l
data that you copied after using the Staging Tool.
Essbase.Bak_preUpgrade, is in
l If you are upgrading to a new location on the same machine, and you ARBORPATH/bin. Unlike the Essbase_
did not replicate data to a new location, specify the location of the timestamp.bak file, which regularly
existing Essbase data. backs up the latest state of Essbase
security, this pre-upgrade backup file is kept
Note: If you replicated data to a new machine, and if you selected
intact and is not subsequently updated by
Differently-named disk volumes, table spaces, or ARBORPATH on
further operations.
source and target or Consolidated disk volumes or tablespaces on
target by exporting data during data replication, you must run a script
immediately after configuring Essbase to update the Essbase security file
to reflect the disk volumes on the upgraded system. The Essbase Staging
Tool provides a script to update the settings in the security file
(essbase.sec):
Start the Essbase Server and EPM System services. Navigate to
ARBORPATH/app on the machine that is hosting the upgraded Essbase
Server and run the following script using MaxL:
%ARBORPATH%/bin/startMaxl.bat -u
userName editagtsec.msh
where userName is the Administrator user name to connect to the

upgraded Essbase server. The script prompts you to enter the
password.
Note: editagtsec.msh could be empty in some scenarios. For
example, when you launched the Staging Tool, the Staging Tool reports
on existing volumes. If no volumes are listed, editagtsec.msh is
empty.
Provider l Deploy to Application Server Moves data from the earlier release into the
Services Shared Services Registry. Moves
Import Data From Earlier Release
essbase.properties to EPM_
l
l Configure Web Server (Foundation task) ORACLE_INSTANCE/aps/bin and

merges its contents with the essbase.
For the Import Data From Earlier Release task, specify the location of properties file installed with Release 11.
the existing or replicated data. 1.2.3.
Administration l Configure Database Moves data from the earlier release into the
Services Shared Services Registry.
l Deploy to Application Server
l Import Data From Earlier Release
l Configure Web Server (Foundation task)
For the Import Data From Earlier Release task, specify the location of
the existing or replicated data
230
Essbase Studio l Configure Database Upgrades the Essbase Studio catalog and
the database.
l Configure Essbase Studio Location for Sample and Customer Data
Source Text Files EPM System Configurator performs the
l Configure Web Server (Foundation task) following tasks during the upgrade process:
1. Exports metadata from the source
On the Configure Essbase Studio Location for Sample and Customer catalog to an external xml file (EPM_
Data Source Text Files page, specify the location of the existing or ORACLE_HOME/tmp/studio_
replicated Essbase Studio data. dump.xml).
2. Renames the source catalog tables and
constraints by replacing the prefix cp_
with the prefix cc_.
3. Creates new catalog tables with the
prefix cp_.
4. Imports metadata from studio_
dump.xml into the new catalog.
5. Converts metadata objects from the
earlier release to the structure for the
upgraded release.
6. Deletes studio_dump.xml if the
upgrade succeeds.
Note: If database configuration fails during
upgrade, see the Oracle Enterprise
Installation and Configuration
Troubleshooting Guide. Maintain the
Release 11.1.1.4 environment until the
upgrade is complete.
Integration l Configure Essbase Integration Services

Services
page 209.
Performance l Configure Database Updates the database.

Management Deploy to Application Server Updating the database could take some
Architect
l
Configure Web Server (Foundation task) time to complete, based on the content and
size of the database being upgraded. Do not
l
l Configure Dimension Server interrupt this task while it is running.
page 209.
Calculation l Configure Database Updates the database.

Manager l Deploy to Application Server
page 209.
231
Reporting and l Configure Database Updates Web Analysis application settings.

Analysis Updates the database.
l Deploy to Application Server
l Configure Reporting and Analysis Framework Services
On the Reporting and Analysis Framework Services configuration page,

for Repository Directory, specify the location of the existing or replicated
data.
page 209.
Planning l Configure Database Updates the database.

l Deploy to Application Server If you have been using Business Rules, EPM
Configure Web Server (Foundation task) System Configurator exports the rules during
database configuration to EPMData/
l
planning/hbrRules.xml for use in the

When you are done with this step, return to the Upgrading Checklist on application upgrade process, when the rules
page 209. are migrated to Calculation Manager.
You perform application upgrade later in the
upgrade process.
Financial l Configure Database Upgrades applications by converting

Management database tables, and registers applications
Deploy to Application Server
with Shared Services.
l
Configure DCOM
Note: Perform the application upgrade
l
l Configure Application Server only once, regardless of how many Financial

l Configure Application Cluster Management application servers are
configured.
l Configure Web Server (Financial Management task)
l Upgrade applications from earlier release
You must select Upgrade applications from earlier release. Note that
there is no EPM System Configurator page for this task and you need not
enter information.
Note: Depending on the number and size of applications you are
upgrading, this task can take some time.
page 209.
232
Performance l Configure Database Updates the database.

Scorecard l Deploy to Application Server
l Configure Attachment Files Location
On the Performance Scorecard Specify directory to store Performance

Scorecard files configuration page, specify the location in which to store
files.
page 209.
Profitability l Configure Database Updates the database and reregisters all

and Cost Deploy to Application Server upgraded Profitability and Cost
Management Management applications with Shared
l
l Configure Web Server (Foundation task) Services.
page 209.
Strategic l Configure Data directory Updates the database.

Finance l WebServices Configuration
On the Strategic Finance Configuration configuration page, specify the

location of the existing or replicated data.
page 209.
Disclosure N/A. Use the Apply Maintenance Release option during installation.
Management
Financial Close N/A. Use the Apply Maintenance Release option during installation.
Management
FDM l Configure Database (for FDMEE) Registers FDM with Shared Services.
l Deploy to Application Server (for FDMEE) Updates the FDMEE database.
l Configure FDM Web Application You complete configuration in FDM and
l Configure FDM Server upgrade applications later in the upgrade
process.
page 209.
What Happens During Shared Services Data Import

During configuration, with the Foundation Import data from earlier release task, EPM System
Configurator extracts the contents of hssmigratedata.zip and imports the data to Shared
Services Release 11.1.2.3.
233
EPM System Configurator imports the following data:
l Security (including application roles)
l Projects and Application IDs
l Taskflow information
l Audit information
l CSS.xml
Logs related to the import process are written to EPM_ORACLE_INSTANCEdiagnostics/logs/

upgrades/foundation/hss_upgrade_ps2.log and to the console. If there are any errors
during the import process, you can rerun just the Import data from earlier release task.
EPM System Configurator performs the following tasks:
l Updates all DN-based identities to their corresponding GUID-based identities.
l Moves Native Directory to last in the search order.
l Imports projects (application groups) into the Shared Services Registry.
l Imports application IDs into the Shared Services Registry. Note that application nodes are
created but are not visible until the applications are registered later in the upgrade process.
If you are moving task flows, note that task flow permissions are moved to roles as follows:
Table 34 How permission types are moved to roles
Permission Type Role Name
Grant Read Run Taskflow
Grant Write or Grant Manage Manage Taskflow
Deny Read, Deny Write, or Deny Manage No mapping
None No mapping
Upgrading a Distributed Deployment of Reporting and

Analysis
If you are upgrading a distributed deployment of Reporting and Analysis, note that the
distributed configuration is not automatically replicated in the upgrade as it was in earlier releases
when you upgraded. You must set up the distributed configuration in the Release 11.1.2.3
environment. Use the Upgrading Checklist, but repeat the installation and configuration steps
as needed, as described in the following procedure.
To configure a distributed deployment of Reporting and Analysis in an upgrade scenario:

1 Install and configure the first host. During configuration with EPM System Configurator, for the product
database configuration, select Upgrade the existing databases to the current release from... and
select a release number. Then, enter connection information for the existing or replicated database.
234
2 For a subsequent host that already existed in the previous deployment, install and configure the host.
During configuration with EPM System Configurator, for the product database configuration, select
Upgrade the existing databases to the current release from... and select a release number. Then,
enter connection information for the existing or replicated database.
3 To add a host that did not exist in the previous deployment, install and configure on the new host. During
configuration with EPM System Configurator, for the product database configuration, select Connect to
a previously configured database. Then, enter connection information for the existing or replicated
database.
Starting EPM System Services

Start EPM System services before you proceed. See Chapter 12, Starting and Stopping EPM
System Products.

Use EPM System Diagnostics to validate the installation. See Chapter 13, Validating the
Performing Manual Configuration Tasks

You must perform any required product-specific postconfiguration tasks before you proceed.
See Chapter 9, Performing Manual Configuration Tasks in a New Deployment.
235
Updating References to a Rehosted Environment
Subtopics
l Updating References to a Rehosted Essbase Server
l Updating Provider Services References to a Rehosted Essbase Server
l Updating Administration Services References to a Rehosted Essbase Server or Provider Services Server
l Updating Essbase Studio References to a Rehosted Environment
l Updating Reporting and Analysis References to a Rehosted Server Environment
l Updating Performance Management Architect References to a Rehosted Server Environment
l Updating Planning References to a Rehosted Server Environment and Upgrading Applications
l Updating Profitability and Cost Management References to a Rehosted Essbase Server
l Updating Strategic Finance References to a Rehosted Essbase Server or Financial Management Server
l Updating Performance Scorecard References to a Rehosted Essbase Server
l Updating Integration Services References to a Rehosted Server Environment
If you are upgrading by installing EPM System products on a new host machine, you need to
update references for some products to reflect the new host name and port number. Perform
the rehosting steps for Essbase first. Make sure EPM System services are started before you
proceed.
Updating References to a Rehosted Essbase Server

Subtopics
l Mapping Essbase Server Host Names to Cluster Names
l Updating Internal Essbase References to a Rehosted Essbase Server
If the Essbase Server host and port has changed since the earlier release, you must update
references to the Essbase Server within Shared Services Registry (to map the server name to a
cluster name), within Essbase, and within other products that use Essbase as a data source.
Note: Some products have additional steps if other servers have been rehosted.
Update the Essbase Server host information in the following places:
Table 35 Updating References to the Essbase Server Host
Essbase Server Host Reference For Information on How to Update
Map Essbase Server names to cluster names. Mapping Essbase Server Host Names to Cluster Names on page 237
You must perform this step before you update
references for other products.
Update Essbase Server references within Essbase. Updating Internal Essbase References to a Rehosted Essbase Server on page
238
You must perform this step before you update
references for other products.
236
Essbase Server Host Reference For Information on How to Update
For products that use Essbase as a data source, if the l Provider Services Updating Provider Services References to a Rehosted
Essbase Server host or port has changed since the Essbase Server on page 238
earlier release, update references to the Essbase
Administration Services Updating Administration Services References to a
Server.
l
Rehosted Essbase Server or Provider Services Server on page 239
Perform these steps after you install and configure Essbase Studio Updating Essbase Studio References to a Rehosted
each product.
l
Environment on page 240
Note: The steps for Performance Management Reporting and Analysis Updating Reporting and Analysis References to a
Architect are required even if Essbase Server has not
l
Rehosted Server Environment on page 243
been rehosted.
l Performance Management Architect Updating Performance Management
Architect References to a Rehosted Server Environment on page 245
l Planning Updating Planning References to a Rehosted Server Environment
and Upgrading Applications on page 245
l Profitability and Cost Management Updating Profitability and Cost
Management References to a Rehosted Essbase Server on page 248
l Strategic Finance Updating Strategic Finance References to a Rehosted
Essbase Server or Financial Management Server on page 248
l Performance Scorecard Updating Performance Scorecard References to a
Rehosted Essbase Server on page 249
Mapping Essbase Server Host Names to Cluster Names

To simplify the rehosting process for products that use Essbase as a data source, perform this
task to map the server host name to the cluster name. This allows other EPM System products
to connect to Essbase by cluster name.
You must perform this step before you update references for other products. This step adds
search-and-replace host pairs to the Shared Services Registry that other products use to update
their Essbase host environments.
Note: Performance Management Architect requires this step even if the Essbase Server has not
been rehosted.
To map Essbase Server host names to cluster names:

1 Add the ApsResolver property to essbase.cfg and essbase.properties.
See Enabling Client Lookup by Cluster Name on page 178.
2 From a command prompt on the machine hosting Shared Services, navigate to the following directory:
EPM_ORACLE_INSTANCE/bin/upgrades.
3 Run the following script:
updateEssbaseServer oldEssbaseServerHost ClusterNameForNewHost
If products connect to Essbase Server using the default port, for

oldEssbaseServerHost, specify Servername. Run the script again and for
oldEssbaseServerHost specify server name:port.
237
If products connect to Essbase Server using a non-default port, run the script only once and
for oldEssbaseServerHost, specify server name:port.
Tip: The default cluster name is EssbaseCluster-1. The cluster name is case sensitive.
The utility stores the mapping information between the earlier release of Essbase Server and
the new logical cluster name in the Shared Services Registry.
4 Repeat for each Essbase Server instance.
Updating Internal Essbase References to a Rehosted Essbase Server

You must map Essbase Server names to cluster names before you perform this step. See Mapping
Essbase Server Host Names to Cluster Names on page 237.
If the Essbase Server host has changed since the earlier release, you must update internal
references to the host. This step updates partition definitions and alias locations.
To update internal references to a rehosted Essbase Server:

1 From a command prompt on the machine hosting Essbase, navigate to the following directory:
EPM_ORACLE_INSTANCE/bin/upgrades.
2 Run the following script, and then enter the administrator password when prompted:
EssbaseUpdateEssbaseServer.bat|sh newHost:port userName
Where newHost is any alias or fully qualified name or IP address for the upgraded machine
and userName is an Essbase administrator user provisioned in Release 11.1.2.3. The default
port is 1423.
The utility updates the host for all location aliases and partition definitions for all Essbase
applications.
3 Repeat for each Essbase Server instance.
Review the log file, EPM_ORACLE_INSTANCE/diagnostics/logs/essbase/

EssbaseRehost.log, for details of the script actions.
If you are configuring all Essbase products at one time, continue to the next section. Otherwise,
when you are done with this step, return to the Upgrading Checklist on page 209.
Updating Provider Services References to a Rehosted

Essbase Server
You must perform Essbase Server rehosting steps before you perform this step. See Updating
References to a Rehosted Essbase Server on page 236.
If the Essbase Server host has changed since the earlier release, you must make updates so that
Provider Services recognizes the new Essbase data source.
238
To update internal references to a rehosted Essbase Server:
1 From a command prompt, navigate to the following directory: EPM_ORACLE_INSTANCE/bin/
upgrades.
ApsUpdateEssbaseServer.bat|sh
Execute this utility once.
To update internal references to a rehosted Oracle Business Intelligence Enterprise Edition
Server, see the Oracle Hyperion Provider Services Administration Guide.
Updating Administration Services References to a Rehosted

Essbase Server or Provider Services Server
If the Essbase Server host and port have changed since the earlier release, you must make updates
so that Administration Services recognizes the new Essbase data source. After upgrading, review
and update the list of servers in the Administration Services Console.
To update Administration Services references to a rehosted Essbase Server:

1 Log in to the Administration Services Console.
The Essbase Servers from the previous installation are listed.
2 Review the list of Essbase Servers.
3 Add, update, or delete servers as needed for the new deployment environment.
When you add a new server, the Add Essbase Server dialog box displays a list of available
servers that are in the upgraded installation, which it reads from the Shared Services Registry.
Delete previous Essbase hosts from the Enterprise tree.
For details, see Administration Services Online Help.

If the Provider Services Server host and port have changed since the earlier release, you must
make updates so that Administration Services recognizes the new location.
To update Administration Services references to a rehosted Provider Services Server:

1 Log in to the Administration Services Console.
The Provider Services Servers from the earlier installation are listed.
2 Review the list of servers.
3 Add, update, or delete servers as needed for the new deployment environment.
239
When you add a new server, in the Add Provider Server dialog box, enter the Provider hosts
for the new installation: click URL (the Provider URL box is updated), and ensure that the
port is correct. From the Authenticating Essbase Server menu select the active Essbase and
then click OK.
4 Delete previous Provider Services Server hosts from the Provider Servers tree.
Updating Essbase Studio References to a Rehosted

Environment
Subtopics
l Updating Essbase Studio References to a Rehosted Essbase Server
l Updating Cube Linkages
l Updating Essbase Studio References to a Rehosted Performance Management Architect Server or to Text Files Used
as Data Sources
After upgrade, Essbase Server connections and deployed cubes are affected by changes in host,
port, or data encryption information for the underlying Essbase Server instances or clusters, or
for anyEssbase Studio Server instances.
You must update references to those server instances and clusters in Essbase Studio.
Table 36 Updating References to the Essbase Server Host and the Essbase Studio Host
Task Reference
If Essbase Server host and port have been moved to a new location, update Updating Essbase Studio References to a Rehosted
Essbase Studio references to the Essbase Server. Essbase Server on page 241
If the Essbase Studio Server host and port have been moved to a new location Updating Cube Linkages on page 242
and you have deployed applications that point to the earlier release Essbase
Studio Server location, update the cube linkage of those deployed applications to
point to the new Essbase Studio Server instance.
If Performance Management Architect has been moved to a new location, then for Updating Essbase Studio References to a Rehosted
all Performance Management Architect data source connections that point to the Performance Management Architect Server or to Text
earlier release location, edit the connection properties to reflect the new server Files Used as Data Sources on page 242
location.
If text files were moved to a non-default directory, edit the connection properties Updating Essbase Studio References to a Rehosted
for any text file connections to point to the new location. Performance Management Architect Server or to Text
Files Used as Data Sources on page 242
240
Updating Essbase Studio References to a Rehosted Essbase Server
To update references to a rehosted Essbase Server instance or cluster:

1 In Essbase Studio Console, select Tools, and then Rehost Essbase Connections.
2 In Rehost Essbase Connections, select the connection to rehost under Essbase connections.
The old cluster name or Essbase host and port number, and, if applicable, data encryption
method, are displayed under Host/Port/Encryption in Catalog.
3 Under New Host/Port/Encryption, enter the new cluster name or new host name, port number, and, if
applicable, data encryption method.
Note: For Essbase Server clusters, only the cluster name is required. The port number is not
required. By default, the new cluster name is displayed in the New Host/Port/
Encryption column.
Use the following syntax:

l For an Essbase Server instance, no data encryption, enter:
host:port
l For an Essbase Server instance, with data encryption, enter:
host:port:ssl
l For an Essbase Server cluster, no data encryption, enter:
cluster_name
4 Optional: Click Test Connection to validate the entry that you made under New Host/Port/
Encryption.
Note: Essbase Studio does not validate entries as you enter them. You must click Test
Connection to validate the information that you entered.
5 Select an Update Deployment History option for the currently selected Essbase Server connection:
l Update the host name and port number for all deployment historyReplaces all old Essbase
Server host and port references to the new host and port that you specified.
This is the default option.
l Replicate the last successful deployment history and update the copy onlyMakes a copy
of the last successful deployment history listing, and then updates the copy with the new
host and port information, and the date and time of the rehosting.
Tip: When selecting the Replicate option, after the update is complete, each rehosted
Essbase model displays twice in the Metadata Navigator: once with the old
host:port information and once with the new host:port and, if required, data
encryption information.
241
Note: Deployment history is updated only for successfully rehosted Essbase Server
connections.
6 Click Update.
7 For the rehosting status of each Essbase Server connection that is rehosted, check the Update
Status column in the Rehost Essbase Connections dialog box.
If the rehost is successful, the Host/Port/Encryption in Catalog column is updated with the
new cluster or host and port information and, if applicable, encryption information. If the
rehost fails, an error message is displayed.
Note: If other Essbase Server connections have the same old host:port setting, rehosting
one server instance rehosts all other server instances.
Updating Cube Linkages
After upgrade or if Essbase Studio has moved to another server, to update the cube linkage
for cubes built using Essbase Studio:
1 In Essbase Studio Console, select Tools, and then Update Cube Linkage.
2 Select Update all Essbase applications and databases to link to the current Essbase Studio Server
(all Essbase instances must be started).
All Essbase applications and databases will be linked to the Essbase Studio Server to which
you are currently connected.
Note: All Essbase instances or clusters must be running for the cube linkage update to take
effect.
3 Optional: To keep all Essbase applications running after the update, clear the Stop all Essbase
applications after the update check box.
The default is to stop all Essbase applications after update.
4 Click Update.
A message indicates that the cube linkage update is successful.
If unsuccessful, an error message shows the details.
5 To exit, click Close.
Updating Essbase Studio References to a Rehosted Performance

Management Architect Server or to Text Files Used as Data Sources
If Performance Management Architect has been moved to a new host or port from the earlier
release installation, then for all Performance Management Architect data source connections
that point to the earlier release location, edit the connection properties to reflect the new server
location. If text files used as data sources have moved to a non-default location, edit the
connection properties.
242
You edit the data source connection information in Essbase Studio.
To edit the properties of a data source:

1 In Essbase Studio Console, from the Source Navigator, select the Data Sources tab.
2 Under Data Sources in the physical tree, right-click the data source to edit and select Properties.
3 Complete the following tasks in the Parameters section of the dialog box.
Dimension Server sources:
a. In Server Name, modify the name of the computer where Performance Management
Architect resides.
b. To modify the port number, ensure that the Default check box next to Port is cleared,
and enter the new port number.
c. Modify the User Name and Password for this instance of Performance Management
Architect.
Text file sources:
a. To modify the Location of the text file data source, click Browse.
b. In the Text File Location dialog box, select the directory that contains the text file data
source you want to access.
Note: You can select only one directory per data source. Essbase Studio does not support
text files from different subdirectories within the same directory.
c. Review the files listed under Contents of selected directory to ensure that this is the text
file data source you want to select.
4 Click Apply, and then click OK.
Updating Reporting and Analysis References to a Rehosted

Server Environment
Subtopics
l Updating Financial Reporting References to a Rehosted Essbase Server
l Updating Web Analysis References to a Rehosted Essbase Server
l Updating References to a Rehosted Production Reporting Server
243
Table 37 Upgrade Tasks for Reporting and Analysis
Upgrade Task Reference
Financial Reporting - If the Essbase Server host and port have changed Updating Financial Reporting References to a Rehosted
since the earlier release, make updates so that Financial Reporting Essbase Server on page 244
recognizes the new Essbase data source.
Financial Reporting - Update Provider Services data sources if the Provider In EPM Workspace, from the Tools menu, select Database
Services host has changed. Connection Manager, select the database connection and
then click Edit to enter new connection information.
Web Analysis - If the Essbase Server host and port have changed since Updating Web Analysis References to a Rehosted Essbase
the earlier release, make updates so that Web Analysis recognizes the Server on page 244
new Essbase data source.
If the Production Reporting Server has moved to a new server for this Updating References to a Rehosted Production Reporting
release, update references to the new server. Server on page 245
Updating Financial Reporting References to a Rehosted Essbase Server

If the Essbase Server host and port has changed since the earlier release, update references to the
Essbase Server host within Financial Reporting where Essbase is used as a data source.
Before you proceed, make sure the Financial Reporting service is started.
To update Financial Reporting references to a rehosted Essbase Server:

upgrades.
FRUpdateEssbaseServer.bat|.sh
Updating Web Analysis References to a Rehosted Essbase Server

Essbase Server host within Web Analysis where Essbase is used as a data source.
To update Web Analysis references to a rehosted Essbase Server:

upgrades.
WebAnalysisUpdateEssbaseServer.bat|sh
244
Updating References to a Rehosted Production Reporting Server
If you installed Production Reporting on a different host than the earlier release, run the
reshostSQRConfig utility to remap the SQR engine-related metadata from the earlier release
host to the new host in the database. You do not need to run this utility if you installed Production
Reporting on the same host as the earlier release.
Shut down all Reporting and Analysis Framework services before running the utility.
To update references to a rehosted Production Reporting Server:

ReportingAnalysis/SDK.
rehostSQRConfig.bat|sh host1 host2
where host1 is the host name for the machine from which you are upgrading, and host2 is
the host name for the upgraded machine.
The script updates tables to reflect the new host.
Updating Performance Management Architect References to

a Rehosted Server Environment
Even if Essbase Server has not been rehosted, you must perform the procedure in Mapping
Essbase Server Host Names to Cluster Names on page 237.
Once those steps are completed, Performance Management Architect automatically updates its
references to rehosted Essbase Servers; running a script is not required.
Updating Planning References to a Rehosted Server

Environment and Upgrading Applications
Use the Planning Upgrade Wizard to update references to rehosted data sources and to upgrade
Planning applications. For example, if the Essbase Server host and port have changed since the
earlier release, you must update data sources and update mappings from Planning applications
to reporting applications. If the relational data source has changed, you must update data source
connections. The Planning Upgrade Wizard enables you to update multiple data sources and
reporting applications simultaneously.
245
Caution! You must update references to rehosted data sources before you upgrade
applications.
Note: Before updating references to data sources, ensure that the Essbase server and the
relational database are running.
To update references to data sources and upgrade applications:

1 From EPM Workspace, select Navigate, then Administer, then Planning Administration and then click
Upgrade Wizard. Log in as an administrator user that has Dimension Editor or Application Creator role.
2 On the Update Data Sources page, review the relational database information and the Essbase server
information for each Planning data source. If the Essbase server host and port have changed during
upgrade, or if the relational database has moved to a new host, update the information.
l To update multiple relational databases with the same information:
a. On the bottom of the page, select the data sources to which to apply relational
database updates.
b. Under Update Relational Information, enter the new database information.
c. Click Apply to Selected.
l To update multiple Essbase servers with the same information:
a. On the bottom of the page, select the data sources to which to apply Essbase
information updates.
b. Under Update Essbase Information, enter the new Essbase server information.
Note that you can specify the Essbase cluster name.
l To update each data source individually:
a. On the bottom of the page, select the data sources to which to apply the updates.
b. Enter the new information for each data source.
3 Choose an option:
l Click Reset to undo the updates.
l Click Validate to test the connections to the selected data sources, and fix any issues that
are noted.
l Click Save to save the updates to the selected data sources.
4 Click Next to proceed to the Upgrade Applications page.
5 On the Upgrade Applications page, review the Relational Server and Essbase Server details and
confirm that they are correct. If the details are not correct, click Previous and make the corrections.
Then select one or more applications and from the Action menu, select Upgrade, and then click OK to
proceed.
246
Applications that have already been upgraded are not available. The Status column indicates
the upgrade status of each application.
The selected applications are upgraded and reregistered with Shared Services. For
applications created in Release 9.3.3, the Upgrade Wizard upgrades identities in the Planning
schema. After upgrade, applications are associated with the same project that they were
associated with before upgrading. Any applications that were not associated with a project
are assigned to the default Shared Services project.
The administrator user that is upgrading the applications is assigned the Provisioning
Manager role for those applications.
A message shows the pass and failure status. The Status column shows the details for each
application. The logs show details for the upgrade for all applications.
Upgrade log files are created for each upgraded application in EPM_ORACLE_INSTANCE/
diagnostics/logs/planning/
PlanningAppUpgradeLog_application_name.txt.
6 Click Next.
7 For updates from Release 11.1.2+ only: On the Update Reporting Essbase Servers page, review or
update the Essbase server information for reporting applications.
Only applications that have already been upgraded and that have reporting applications
created on an Essbase server (other than the default Essbase server) are listed.
l To update multiple reporting applications with the same information:
a. On the bottom of the page, select the applications to which to apply the updates.
b. Under Update Reporting Essbase Information, enter the new Essbase server
information.
l To update each reporting application individually:
a. On the bottom of the page, select the reporting applications to which to apply the
updates.
b. Enter the new Essbase server information for each application.
8 Choose an option:
l Click Reset to undo the updates.
l Click Validate to test the connections to the selected Essbase servers, and fix any issues
that are noted.
l Click Save to save the updates to the selected Essbase servers.
9 Click Cancel.
Note: If you do not see the updates reflected in the Planning application, stop and then restart
the Planning server.
247
Updating Profitability and Cost Management References to
a Rehosted Essbase Server
If the Essbase Server host and port have changed since the earlier release, make updates so that
Profitability and Cost Management recognizes the new location.
To update Profitability and Cost Management references to a rehosted Essbase Server:

upgrades.
HPMUpdateEssbaseServer.bat
Updating Strategic Finance References to a Rehosted

Essbase Server or Financial Management Server
If the Essbase Server host and port have changed since the earlier release, make updates so that
Strategic Finance recognizes the new location. This procedure is also required if the Financial
Management Server has changed since the earlier release.
To update Strategic Finance references to a rehosted Essbase Server or Financial

Management Server:
1 In Strategic Finance, from the Server menu, select Update Connections.
The Update Connections dialog box displays all of the batches and maps that exist on the
Strategic Finance Server.
2 From the Connection Type list, select the appropriate connection type.
3 Select the batch or map items related to a rehosted server, enter the new server name, and then click
Update Selected.
4 Repeat these steps for each rehosted server and its associated batch or map items.
248
Updating Performance Scorecard References to a Rehosted
Essbase Server
Essbase Server host within Performance Scorecard where Essbase is used as a data source.
To update Performance Scorecard references to a rehosted Essbase Server:

1 In Performance Scorecard, select Administration, and then Data Source List.
2 Select the name of the external data source and then click Edit.
3 Select each tab to change general settings and required dimension mappings, and then click Save.
Updating Integration Services References to a Rehosted

Server Environment
You must perform the following upgrade tasks for Integration Services.
Table 38 Upgrade Tasks for Integration Services
If the Integration Services Server host has changed since the earlier release (for example if See the Oracle Essbase Integration
you upgraded to a new machine), redefine the Integration Services ODBC DSNs on the machine Services System Administrator's Guide for
hosting the new installation using the same names. details.
For Integration Services-deployed applications, update drill-through to point to the new Specifying an Alternate Integration
Integration Server location. This ensures that the application outline files are updated with the Server for Drill-Through Reports on page
new Integration Server connection information. 249
Specifying an Alternate Integration Server for Drill-Through Reports

For already-deployed Essbase applications, for each OLAP metaoutline, perform the following
procedure.
To specify an alternate Integration Services server for drill-through reports:

1 In the OLAP Metaoutline main window, select a metaoutline name.
2 Right-click the metaoutline name and from the menu, select Properties, and then select the Drill-
Through Reports tab.
3 In the Alternate Integration Server text box, enter the machine name and port number (separated by
a colon) of the new Integration Server instance that is now used for executing drill-through reports.
249
If you are using Integration Server on the default port, you do not need to specify the port
number.
4 Click OK.
You must perform a member load or select Update Drillthrough Data from the Outline menu after
making these changes.
Upgrading Applications from the Earlier Release to the

Current Release
If you have not already done so, upgrade applications for the following products from the earlier
release to the current release:
l If you have been using Oracle Hyperion Public Sector Planning and Budgeting or Oracle
Project Financial Planning, perform optional steps before you upgrade the Planning
applications to take advantage of new features. See the Oracle Hyperion Planning Readme.
l Planning, using the Upgrade Wizard. See Updating Planning References to a Rehosted
Server Environment and Upgrading Applications on page 245. Note that if the Essbase
Server host has changed since the earlier release, you also use the Upgrade Wizard to update
references to data sources before you upgrade applications.
l FDM, using the Schema Update Utility. See the Oracle Hyperion Financial Data Quality
Management Configuration Guide for information about upgrading FDM applications.
Applications for the following products are upgraded automatically:

l Essbase applications are updated automatically during configuration with EPM System
Configurator.
l Financial Management applications are upgraded during configuration with EPM System
Configurator (during Upgrade applications from earlier release task).
l Profitability and Cost Management applications are upgraded during configuration with
EPM System Configurator.
250
Performing Manual Configuration Tasks in an Upgrade
Subtopics
l Performance Management Architect Upgrade Tasks
l Essbase Upgrade Tasks
l Essbase Studio Upgrade Tasks
l Reporting and Analysis Upgrade Tasks
l Planning Upgrade Tasks
l Financial Management Upgrade Tasks
l Strategic Finance Upgrade Tasks
l FDMEE Upgrade Tasks
l FDM Upgrade Tasks
Performance Management Architect Upgrade Tasks

Table 39 Performance Management Architect Upgrade Tasks
If you have interface data sources, in EPM Workspace, select Navigate, Administer, Configure Interface Data
Source, and on the Configure Interface Data Sources page, select Import Data Sources from an old release.
To ensure that Performance Management Architect displays correctly after upgrading, have all users delete temporary
internet files in Internet Explorer.
If a Financial Management application contains shared dimensions, right-click the application in the Application View
pane and select Activate All Associations. This is required to support the dynamic properties that were introduced
in Release 11.1.2.2 for Extended Dimensionality.
Review differences in default property values from earlier versions and if necessary set new property values. Oracle Hyperion
Enterprise
Performance
Management
Architect
Administrator's
Guide
Because new validations were added in this release, applications that validated successfully in an earlier release Oracle Hyperion
might not validate in the current release. Review and resolve validation errors and warnings. Enterprise
Performance
To validate each application, right-click the application in the Application Library and select Validate. Validation
Management
errors are reported in the Job Console.
Architect
Administrator's
Guide
After upgrading, applications might display as Out of sync with deployment. Redeploy all out-of-sync
applications.
All applications should have the status In sync with deployment before proceeding.
When you are done with these steps, return to the Upgrading Checklist on page 209.
251
Essbase Upgrade Tasks
Subtopics
l Importing Essbase Data and Linked Reporting Objects
l Manually Import Linked Reporting Objects
l Importing Business Rules to Calculation Manager for use with Essbase
Perform the following upgrade tasks for Essbase.
Table 40 Essbase Upgrade Tasks
If you upgraded to a new machine, redefine the Essbase ODBC DSNs on the machine hosting the
new installation.
If you upgraded to a new machine, specify any JAVA options on the new machine.
If you replicated data to a new machine, and if you selected Consolidated disk volumes or Importing Essbase Data and
tablespaces on target by exporting data, run a script to import Essbase data and linked reporting Linked Reporting Objects on page
objects. 252
If the upgraded application has more than 127 linked reporting objects, manually import the linked Manually Import Linked Reporting
reporting objects. Objects on page 253
Oracle recommends that you make a backup of the applications. This ensures that the backup is of
the upgraded format.
If you are an Essbase-only Business Rules user, you must migrate the Business Rules rules to Importing Business Rules to
Calculation Manager. Calculation Manager for use with
Essbase on page 253
Importing Essbase Data and Linked Reporting Objects

If you replicated data to a new machine, and if you selected Consolidated disk volumes or
tablespaces on target by exporting data during data replication, you must run a script to import
the Essbase data and linked reporting objects on the upgraded system. The Essbase Staging Tool
provides a script to perform this task.
To import data and linked reporting objects on the upgraded machine:

Navigate to the export data directory you defined during data replication on the machine that
is hosting the upgraded Essbase Server and run the following script using MaxL:
%ARBORPATH%/bin/startMaxl.bat -u userName importdata.msh
where userName is the Administrator user name to connect to the upgraded Essbase server. The
script prompts you to enter the password.
252
Manually Import Linked Reporting Objects
If the upgraded application has more than 127 linked reporting objects, manually import the
linked reporting objects.
To import linked reporting objects:

1 Start Essbase Server.
2 Run the following MaxL command to import the linked reporting object data from the earlier release
backup directory: (The Staging Tool replicated the linked reporting objects with the rest of the Essbase
data.)
IMPORT database DBS-NAME LRO from server directory directoryName;
For example:
MAXL> IMPORT database Sample.Basic LRO from server directory
Sample-Basic-V1;
Importing Business Rules to Calculation Manager for use with Essbase

Ensure that you exported rules as described in Performing Product-Specific Upgrade
To import Business Rules to Calculation Manager for use with Essbase:

1 From Calculation Manager, select File, and then Import.
2 Browse to the XML file that you exported and then click Import.
Essbase Studio Upgrade Tasks

The following are tasks for upgrading Essbase Studio to Release 11.1.2.3.
Table 41 Essbase Studio Upgrade Tasks
Task Reference
Starting with release 11.1.2, the template for drill-through to FDM URLs is changed. If you are upgrading from Sample FDM URL
release 11.1.1.4 to 11.1.2.3, update any drill-through reports to FDM created in Essbase Studio. The URLs for Template in the
these reports should be changed to use the new template. Oracle Essbase
Studio User's Guide
(Optional) When you upgrade, Essbase Studio properties from the earlier release are not retained. If you want to
use the same settings in the upgraded release, you must re-enter them.
To customize Essbase Studio properties, see Oracle Essbase Studio User's Guide.
253
Reporting and Analysis Upgrade Tasks
Subtopics
l Configuring Reporting and Analysis Framework Service Properties
l Configuring Java Web Application Properties
l Importing DAS Data Sources
l Assigning New Interactive Reporting Roles
Perform the following upgrade tasks for Reporting and Analysis.
Table 42 Upgrade Tasks for Reporting and Analysis
Optionally, configure Reporting and Analysis Framework Service Configuring Reporting and Analysis Framework Service Properties on
properties. page 254
Optionally, configure Reporting and Analysis Framework Java web Configuring Java Web Application Properties on page 254
application properties.
Import DAS datasources. Importing DAS Data Sources on page 255
Assign new roles IR WebClient Viewer and IR HTML Viewer to Assigning New Interactive Reporting Roles on page 255
allow users to open BQY documents or job outputs.
For Interactive Reporting, update dashboard objects. JavaScript update information in the Impact Manager section in the
Oracle Hyperion Reporting and Analysis Framework Administrator's
Guide
Configuring Reporting and Analysis Framework Service Properties

When you upgrade, Reporting and Analysis Framework Service properties from the earlier
release are not retained.
To configure Reporting and Analysis Framework Service properties:

1 In EPM Workspace, select Navigate, then Administer, then Reporting and Analysis, and then
Services.
2 Right-click a service, select Properties, review the property settings, and reset them if needed.
See the Oracle Hyperion Reporting and Analysis Framework Administrator's Guide for more
information.
Configuring Java Web Application Properties

When you upgrade, Reporting and Analysis Framework Java web application properties from
the earlier release are not retained.
254
To configure Reporting and Analysis Framework Java web application properties:
1 In EPM Workspace, select Navigate, then Administer, then Reporting and Analysis, and then Web
Applications.
2 Right-click a Java web application, select Properties, review the property settings, and reset them if
needed.
See the Oracle Hyperion Reporting and Analysis Framework Administrator's Guide for more
information.
Importing DAS Data Sources

Perform this step from the machine hosting Interactive Reporting or copy server.xml locally
before importing.
To import DAS data sources:

1 Open the Services section of EPM Workspace (select Navigate, then Administer, then Reporting and
Analysis, and then Services).
2 In the Services tab, select an Interactive Reporting Data Access service and click Properties.
3 Select the Data Sources tab and click Import.
4 Select the source server.xml file from the file system and click OK.
Specify the location of the server.xml that you copied during data replication.
After you click OK, the new data sources are displayed.
5 Optional: Add new data sources, or modify or remove existing data sources.
6 Click OK to exit from the Data Sources tab.
Assigning New Interactive Reporting Roles

Two roles have been added to restrict users' access to information based on roles:
l IR HTML Viewer role - required to open a BQY document or Job Output in the HTML
viewer.
l IR WebClient Viewer role - required to open a BQY document or Job Output in the
Interactive Reporting plugin.
After you upgrade, assign users these two roles as needed; the new roles are not assigned by
default. You can assign roles in one of two ways:
l Use Shared Services to provision roles. For more information, see the Oracle Enterprise
Performance Management System User Security Administration Guide.
l Use a Java SDK program to perform a bulk assignment of the new roles to users and groups.
See EPM_ORACLE_HOME/products/biplus/SDK/samples/java/AddNewRole.java
for more details on this program and the Hyperion Reporting and Analysis Framework
Developers Guide for details on how to run SDK programs.
255
Planning Upgrade Tasks

Subtopics
l Migrating Business Rules to Calculation Manager for use with Planning
l Migrating Business Rule Security
Migrating Business Rules to Calculation Manager for use with Planning

If you were using Business Rules rules, migrate the rules to Calculation Manager rules.
Before you migrate, ensure that user directories and native users with the same SID are available
when you upgrade Shared Services.
Ensure that the Planning applications are upgraded to the current release and are available in
Calculation Manager under SYSTEM View.
To migrate Business Rules rules to Calculation Manager rules:

1 In Calculation Manager, select the migrated Planning application, and then select Migrate.
The data that was exported during database configuration with EPM System Configurator
is imported to Calculation Manager.
2 Repeat for each Planning application.
3 Deploy the rules from Calculation Manager to Planning. See the Oracle Hyperion Calculation Manager
Designer's Guide.
After migrating business rules and rules security, if any of the rules had multiple launch locations
and you migrated to more than one location, Calculation Manager creates a rule for the first
migration, and shortcuts for all subsequent migrations. If the rule had rule-level variables, for
the shortcuts that are created in the application in the new environment , its variables are moved
to the Plan level. In this scenario, test rules in your environment to ensure that they work as
expected.
Migrating Business Rule Security

If your upgraded application used Business Rules, administrators can migrate launch access
permissions on business rules and their projects from Business Rules to Calculation Manager
business rules in Planning using the HBRMigrateSecurity.cmd utility.
The HBRMigrateSecurity.cmd utility:
l Overwrites launch access permissions that are already assigned to business rules in the
specified Planning application.
l Migrates access permissions only for users and groups that are provisioned for the specified
Planning application in Shared Services Console.
256
To migrate access permissions on business rules and their folders:
1 Before running HBRMigrateSecurity.cmd:
l Ensure that you have migrated business rules from Oracle Hyperion Business Rules to
Calculation Manager.
l Ensure that you have deployed the business rules to Planning.
2 At the command line, from the planning1 directory, enter this command and its parameters,
separating each by a space:
HBRMigrateSecurity.cmd [-f:passwordFile] /A:appname /U:admin /F:output
file
Table 43 HBRMigrateSecurity Parameters
Parameter Purpose Required?
[-f:passwordFile] Optional: If an encrypted password file is set up, use as the first parameter in the command No
line to read the password from the full file path and name specified in passwordFile.
/A:appname Specify the Planning application to which to migrate launch access permissions for business Yes
rules
/U:admin Specify the administrator's user name Yes
/F:output file Specify the name of the XML output file, including its full path if it is not in the Yes
planning1 directory. This file contains a log of the transaction, and helps with
troubleshooting.
/? Print the syntax and options for HBRMigrateSecurity.cmd No
3 If prompted, enter your password.
For example:
HBRMigrateSecurity.cmd /A:appname /U:admin /F:C:\temp
\HBRExportedSecurity.xml
Financial Management Upgrade Tasks

Perform the following upgrade tasks for Financial Management.
Table 44 Upgrade Tasks for Financial Management
Reregister applications in EPM Workspace. Reregistering Applications in EPM Workspace on page 258
If you changed cluster names during the upgrade, you must recreate task
flows using the new cluster name.
257
Reregistering Applications in EPM Workspace
To register applications in EPM Workspace:

1 From the Navigate menu, select Consolidation Administration, then Manage Applications, and then
Reregister Applications.
2 Select a cluster, select an application, and then review and update as needed the values for cluster/
server, User Management Project, and security URL.
3 Click Register.
4 Repeat for each application.
5 After all applications are registered, restart Foundation Services and the Web server.
Strategic Finance Upgrade Tasks

Note: If you are using the Strategic Finance client as a standalone program, Strategic Finance
converts the data to the upgraded format when you open the existing.alc files in the new
release. 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 can also force
one or more entities in the database by using the Strategic Finance Administrator Utility.
Table 45 Strategic Finance Upgrade Tasks
Task Reference
If you are upgrading from Release 11.1.1.4, use the Strategic Upgrading Strategic Finance Provisioning Information on page 258
Finance migration utility to move Strategic Finance provisioning
from the earlier release to the current release.
Upgrading Strategic Finance Provisioning Information

If you are upgrading from Release 11.1.1.4, use the Strategic Finance migration utility to move
Strategic Finance provisioning information from the earlier release to the current release.
Note: Shared Services Release 11.1.2.3 must be running
To upgrade provisioning information:

1 Navigate to EPM_ORACLE_HOME/products/hsf/scripts and open setenv.bat in a text
editor.
2 Specify the EPM_ORACLE_INSTANCE location in this portion of the file:
258
rem ******* EPM_ORACLE_INSTANCE needs to be defined, please complete the environment
variable definition below
rem * ex:
rem * set EPM_ORACLE_INSTANCE=C:\Oracle\Middleware\user_projects\epmsystem1
rem *
rem *******
set EPM_ORACLE_INSTANCE=
In a default installation, EPM_ORACLE_INSTANCE is Oracle/Middleware/

user_projects/epmsystem1.
3 From a command prompt, navigate to the following directory:
EPM_ORACLE_HOME/products/hsf/scripts
ProvisioningMigrator.cmd /S:earlerReleaseServerName /U:userName
where userName is the admin user.
FDMEE Upgrade Tasks

Perform the following upgrade tasks for FDMEE.
Table 46 FDMEE Upgrade Tasks
Task Reference
If you have target applications with a data load method not based on FDM, create period mappings before Updating Period
running any data loads. Due to a difference in structure of period mappings, period mappings are not upgraded Mappings on page
from Release 11.1.1.4 to Release 11.1.2.3. 259
Updating Period Mappings
To update period mappings:

1 In FDMEE, select Period Mapping under Setup .
2 Define Global Period Mapping and if required, add Application Period mapping.
To refresh metadata:
1 In FDMEE, select Target Application.
2 Select the application and then click Refresh Metadata.
See the Oracle Hyperion Financial Data Quality Management, Enterprise Edition Administrator's
Guide for details.
259
FDM Upgrade Tasks
After installing and configuring the upgrade, update user_projects\config\dbclient
\tnsnames.ora to include entries for the Oracle Database Client that was installed by EPM
System Installer in MIDDLEWARE_HOME/dbclient32 and MIDDLEWARE_HOME/dbclient64 so
that the Schema Update Utility can connect to the database.
If you are upgrading, configure FDM and upgrade applications. When you are upgrading FDM,
configuration tasks include:
l Configuring Web server components
l Configuring Task Manager
l Configuring application server components
l Configuring Load Balance Manager
l Configuring Workbench
l Upgrading applications using the Schema Update Utility. If you replicated data to a new
location, you are first prompted to add applications. When you add applications, for each
application, specify the replicated FDM data folder and the database information.
l Configuring adapters
l If the earlier release of FDM did not use Shared Services security, transferring users and
groups for the first time to Shared Services.
See the Oracle Hyperion Financial Data Quality Management Configuration Guide for
information about upgrading FDM.
Upgrading Smart View

You can upgrade Smart View in one of several ways:
l Have users install Smart View from EPM Workspace: from the Tools menu, select Install
and then Smart View.
l Install Smart View on client machines using the Smart View installer. See Installing EPM
System Clients on page 92. You can also launch this installer to install Smart View silently.
l If you want to use Smart View Release 11.1.2.3 with an earlier release of EPM System
products, review the Oracle Hyperion Enterprise Performance Management System
Certification Matrix for supported versions.
260
Upgrading from an Environment with Multiple Releases
Subtopics
l Upgrading From an Environment with a Single Instance of Shared Services
l Upgrading From an Environment with Two Instances of Shared Services
If you are upgrading from an environment with multiple releases, use the following information
to plan your upgrade. There are several scenarios; use the procedure appropriate for your
deployment. Note that in these scenarios, you must upgrade all EPM System products to the
current release.
Upgrading From an Environment with a Single Instance of

Shared Services
If you are upgrading from an environment with a single instance of Shared Services (Release
11.1.1.4), perform the upgrade as documented in Upgrading Checklist on page 209.
Perform the upgrade for Release 11.1.1.4 products first. Note that you must configure
Foundation Services first. Next, perform the upgrade tasks for all Release 9.3.3 products.
Note: If you are upgrading multiple instances of Essbase, for each instance that you are
upgrading from, you must create a new instance in Release 11.1.2.3.
Upgrading From an Environment with Two Instances of

Shared Services
If you are upgrading from an environment with two instances of Shared Services (Release 11.1.1.3
or 11.1.1.4 or 9.3.3 and Release 11.1.2), upgrade using the following procedure.
To upgrade an environment that has two instances of Shared Services:

1 Using EPM System Installer, use the Apply maintenance release option to move Foundation Services,
Financial Close Management, and Disclosure Management from 11.1.2.0 or 11.1.2.1 to Release
11.1.2.3.
If you are applying the maintenance release to Financial Close Management, see Financial
Close Management Maintenance Release Installation Checklist on page 188.
2 Use EPM System Configurator to configure Foundation Services, Financial Close Management, and
Disclosure Management.
During database configuration for Foundation Services, select Upgrade existing database to
the current release from.. and select a release number, and then select Import Data From Earlier
Release.
3 Perform any required post-configuration tasks for these products. See Chapter 9, Performing Manual
Configuration Tasks in a New Deployment.
261
4 Using the Upgrading Checklist, upgrade all Release 11.1.1.4 products except Shared Services to Release
11.1.2.3. Note that you do not need to install Shared Services again. However, you do have to export
Shared Services data and perform a configuration task. Perform the upgrade tasks product by product
in the following order:
l Foundation Services. Perform the tasks to export Shared Services data. See Exporting
Shared Services Data from the Earlier Release on page 215. During configuration with
EPM System Configurator, when you configure Shared Services, select only Import Data
From Earlier Release.
l Essbase
l All other products
Note: If you are upgrading multiple instances of Essbase, for each instance that you are
upgrading from, you must create a new instance in Release 11.1.2.3.
For information about the upgrade process, see the Upgrading Checklist on page 209.
5 Disclosure Management mappings from Release 11.1.2.0 or 11.1.2.1 or 11.1.2.2 are migrated to
Release 11.1.2.3 when you open a report in the Disclosure Management Client. (Mappings are migrated
separately for each report.) Oracle recommends running the migration by opening a Master Document
(not a doclet). All doclet files must be stored in _doclets to successfully complete the migration.
Repeating the Upgrade Process for Applications

The upgrade logic in this release is based on deploying a new software release and moving
applications, data, and provisioning information from the earlier deployment to the new
deployment. This approach allows the upgrade process to be repeatable. You start with a new
database, delete existing configurations, and repeat the upgrade process as documented.
To repeat the upgrade process for applications:

1 Back up the existing 11.1.2.3 deployment.
2 For every machine in the deployment, rename the existing user_projects folder to another name,
removing it from use.
3 Reconfigure the deployment by following the regular 11.1.2.3 upgrade procedure as documented in the
Upgrading Checklist on page 209.
l Use a new database for the Shared Services Registry
l Reuse the replicated product databases (from the previous release)
Note: You can repeat this step as needed to get the latest data from the previous release.
262
Starting and Stopping EPM
12 System Products
In This Chapter
Using a Single Script to Start Services................................................................. 263
Launching Clients ........................................................................................ 264
This chapter describes how to start and stop EPM System services and applications and provides
default URLs for EPM System clients.
Before you start any services or processes, start all databases used as repositories. Once the
databases are started, there is no required start order for EPM System with the exception of
Financial Close Management.
Caution! If you started the SOA Server to configure Financial Close Management, stop it
before starting EPM System services. If you are using Financial Close Management,
see the required service startup order in Financial Close Management Application
Server on page 318.
Note: If you selected Run Windows Services as non-local system account and specified a user name
and password on the Configure Common Settings panel of EPM System Configurator,
Windows services are started using the specifed user name. If you do not specify a user
name and password, EPM System Configurator 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 EPM_ORACLE_INSTANCE/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. The single start script works by calling
the individual start scripts for every product.
The user running the start script should be a member of the Administrators group.
To start EPM System services:

1 Select Start, then Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE_NAME, then
Foundation Services, and then Start EPM System.
263
2 Run this start script on each machine in your environment.
After the single start script completes, you can run EPM System Diagnostics to determine which
services on a machine are running. See Chapter 13, Validating the Installation and Verifying
Deployment.
A single stop script, stop.bat|sh is also installed in EPM_ORACLE_INSTANCE/bin. Running
the stop script on a machine in your EPM System deployment stops all EPM System products
on that machine.
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.
To connect from a server or client to a Java web application, you must use the Web Server port
(machine_name:web_server_port) in the URL. For example, machine_name:19000 is the
default for Oracle HTTP Server and machine_name:9000 is the default for the proxy server.
Table 47 Launching Clients
Client URL Script or Other Launch Method
Oracle Hyperion http:// From the Start menu, select Programs, then Oracle EPM System, then EPM_ORACLE_
Shared Services WebServer:Port/ INSTANCE, then Foundation Services, and then Shared Services URL.
Console interop/
Note: The Start menu item is available only on the machine on which you installed the
Web server.
EPM Workspace http:// From the Start menu, select Programs, then Oracle EPM System, then EPM_ORACLE_
WebServer:Port/ INSTANCE, then Workspace, and then Workspace URL.
workspace/
Note: The Start menu item is available only on the machine on which you installed the
Web server.
Data http://drm_web_ From the Start menu, select Programs, then Oracle EPM System, then EPM_ORACLE_
Relationship server_name/drm- INSTANCE, then Data Relationship Management, and then Web Client.
Management web-client
Web Client
Data http://drm_web_ From the Start menu, select Programs, then Oracle EPM System, then EPM_ORACLE_
Relationship server_name/drm- INSTANCE, then Data Relationship Management, and then Migration Utility.
Management migration-client
Migration Utility
Data N/A From a Windows command line prompt, run EPM_ORACLE_HOME/products/

Relationship DataRelationshipManagement/client/batch-client/drm-batch-
Management client.exe
Batch Client
Disclosure N/A N/A

Management
264
Administration http:// From the Start menu, select Programs, then Oracle EPM System, then EPM_ORACLE_
Services WebServer:port/ INSTANCE, then Essbase, then Essbase Administration Services, and then Start
Console easconsole/console. Administration Services Console.
html
Integration N/A From the Start menu, select Programs, then Oracle EPM System, then EPM_ORACLE_
Services INSTANCE, then Essbase, then Integration Services, and then Console.
Console
Or
EPM_ORACLE_HOME/products/Essbase/eis/console/bin/
startOlapbldr.bat
Essbase Client NA From the Start menu, select Programs, then Oracle EPM System, then EPM_ORACLE_
INSTANCE, then Essbase, and then Essbase Client.
Essbase Studio NA From the Start menu, select Programs, then Oracle EPM System, then EPM_ORACLE_
Console INSTANCE, then Essbase, then Essbase Studio, and then Essbase Studio Console.
Or
EPM_ORACLE_HOME/products/Essbase/EssbaseStudio/Console/
startStudio.bat
FDM Web Client http:// N/A

WebServerName/
HyperionFDM
FDM Workbench N/A From the Start menu, select Programs, then Oracle EPM System, then EPM_ORACLE_
Client INSTANCE, then Financial Data Quality Management, then Workbench, and then
Workbench Client.
Financial N/A From the Start menu, select Programs, then Oracle EPM System, then EPM_ORACLE_
Management INSTANCE, then Financial Management, and then Financial Management.
Client
Or
For 32-bit:
EPM_ORACLE_HOME/products/FinancialManagement/Client/HFM.exe
For 64-bit:
EPM_ORACLE_HOME/products/FinancialManagement/Client/32bit/
HFM.exe
Financial N/A From the Start menu, select Programs, then Oracle, and then Financial Reporting
Reporting Studio.
Studio
Or
%ProgramFiles%/Oracle/FinancialReportingStudio/HReports.exe
265
Interactive N/A From the Start menu, select Programs, then Oracle EPM System, then EPM_ORACLE_
Reporting INSTANCE, then Reporting and Analysis, then Interactive Reporting, and then
Dashboard Architect.
From the Start menu, select Programs, then Oracle EPM System, then EPM_ORACLE_
INSTANCE, then Reporting and Analysis, then Interactive Reporting, and then
Dashboard Studio.
INSTANCE, then Reporting and Analysis, then Interactive Reporting, and then Studio.
Interactive N/A From the Start menu, select Programs, then Oracle EPM System, then EPM_ORACLE_
Reporting INSTANCE, then Reporting and Analysis, then Interactive Reporting, and then Studio.
Studio
Or
EPM_ORACLE_HOME/products/biplus/bin/brioqry.exe
Performance N/A File Generator:

Management
Architect
INSTANCE, then Performance Management Architect Clients, and then Start EPMA File
Generator.
Or
EPM_ORACLE_HOME/products/Foundation/BPMA/EPMAFileGenerator/
bin/EPMAFileGenerator.exe
Batch Client:
INSTANCE, then Performance Management Architect, and then Start EPMA Batch
Client.
Or
EPM_ORACLE_HOME/products/Foundation/BPMA/EPMABatchClient/
epma-batch-client.bat
Planning Offline N/A None
Predictive N/A None

Planning
Production N/A From the Start menu, select Programs, then Oracle EPM System, then EPM_ORACLE_
Reporting INSTANCE, then Reporting and Analysis, and then Production Reporting Studio or
Production Reporting Viewer.
Smart View NA Use the Smart View menu or Oracle Smart View for Office ribbon in Microsoft Excel,
Microsoft Word, or Microsoft PowerPoint.
Strategic NA From the Start menu, select Programs, then Oracle, and then Strategic Finance.
Finance Client
Or
EPM_ORACLE_HOME/products/hsf/bin/HSF.exe
Strategic From the Start menu, select Programs, then Oracle EPM System, then EPM_ORACLE_
Finance Server INSTANCE, then Strategic Finance, then Server, and then Server Administration
Administration
Or
EPM_ORACLE_HOME/products/hsf/bin/HSFAdmin.exe
266
Oracle Hyperion The Sun Java plug-in is From the Start menu, select Programs, then Oracle EPM System, then EPM_ORACLE_
Web Analysis installed when Web Analysis INSTANCE, then Reporting and Analysis, and then Web Analysis URL.
Studio Studio is first used. To start
Web Analysis Studio, in your
Web browser's Address bar,
enter the Web Analysis
Studio URL http://
WebServer:Port/
WebAnalysis
267
268
Validating the Installation and
13 Verifying Deployment
In This Chapter
Validating the Installation ............................................................................... 269
Generating a Deployment Report....................................................................... 271
Verifying Deployment .................................................................................... 272
Validating a Financial Close Management Deployment .............................................. 274

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.
You must install, configure, and run EPM System Diagnostics as the same user.
Prerequisites
Before using EPM System Diagnostics, complete these prerequisites:
l Install EPM System products. See Chapter 5, Installing EPM System Products in a New
Deployment.
l Use EPM System Configurator to perform all configuration tasks required for each product.
See Chapter 6, Configuring EPM System Products in a New Deployment.
l Perform postconfiguration tasks.
See Chapter 9, Performing Manual Configuration Tasks in a New Deployment.
l Start EPM System services.
See Chapter 12, Starting and Stopping EPM System Products.
Using EPM System Diagnostics

To run EPM System Diagnostics:
1 Choose a method:
l (Windows) In EPM_ORACLE_INSTANCE/bin, double-click validate.bat.
269
l From the Start Menu, choose Programs, then Oracle EPM System, then instanceName,
then Foundation Services, and then EPM System Diagnostics.
l (UNIX) From a console, change to EPM_ORACLE_INSTANCE/bin, and then enter
validate.sh.
Progress is shown in the command window.

2 To view results, navigate to EPM_ORACLE_INSTANCE/diagnostics/reports and open
validation_report_date_time.html.
3 Look for failed tests, and diagnose and fix problems.
EPM System Diagnostics creates a ZIP file of all the logs in EPM_ORACLE_INSTANCE/
logszips for your convenience.
For more information about logs, see Oracle Enterprise Performance Management System
Installation and Configuration Troubleshooting Guide.
4 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.
5 In a distributed environment, run EPM System Diagnostics on each machine in the deployment.
The report captures the following information:

l Test date and time
l Test Status: Passed or Failed for each test
l Service: Type of test for each test
l Test Description: A detailed description of each test
l Duration: Duration of each test
l Test start time
l Test end time
l Total test duration
Diagnostics Performed
The following list highlights the Oracle Hyperion Enterprise Performance Management System
Diagnostics tests performed for EPM System products.
l CFG: Configuration - Checks whether all configuration tasks have been completed
l DB: Database - Checks connection to database host:port;databaseName
l EXT: External Authentication - Checks Native Directory external authentication provider
configuration
l HTTP: http - Checks availability of HTTP context for all components configured for the
Web server.
l SSO:
270
m Checks status of Shared Services security (Native Directory as well as external
directories)
m Checks availability of login to Shared Services, Taskflows, Audit, Shared Services Java
web application, and Oracle Hyperion Enterprise Performance Management System
Lifecycle Management
l WEB: Web application - Checks availability of Java web application on host:port
l Additional product-specific tests
Generating a Deployment Report

After completing an EPM System deployment, you can generate a deployment report that lists
this information:
l EPM Deployment Topology Report
m Logical Web Addresses all logical Java web applications and all Web servers that are
configured
m Application Tier Components the components configured for each EPM Instance in
this deployment, including the Java web application URL and domain name for each
Java web application
m Database Connections all databases configured for EPM System products
m User Directories user directories used by EPM System products; configured security
providers are listed in the same order as configured in Shared Services
m Data Directories data directories used by EPM System products, indicating the
directories that need to be on a shared file system
l EPM Deployment History Report configuration history of activities on the specified date
for each server in the deployment
This report can help you to resolve any issues that might arise in your deployment. For example,
you can use the report to verify that there is only one WebLogic domain and that the deployment
points to the correct number of database schemas. The deployment report is created from the
Shared Services Registry database. You can generate the report from any server in the
deployment, and it does require EPM System services to be running.
The report has additional sections that show deployment history
To generate a deployment report:

1 Open a command line window and navigate to EPM_ORACLE_INSTANCE/bin.
2 Run the command epmsys_registry.bat|.sh report deployment.
271
You can add an optional file name argument to the command to save the HTML report with
a different file name or location. For example, this command saves the report as c:/
epm_setup/epm_deployment.html:
epmsys_registry.bat|.sh report deployment c:/epm_setup/

epm_deployment
Verifying Deployment
Subtopics
l Verifying Shared Services Deployment
l Verifying EPM Workspace Deployment and Products in EPM Workspace
l Additional Verification for Financial Close Management
l Verifying Administration Services Deployment
l Verifying Provider Services Deployment
Verifying Shared Services Deployment

To verify deployment:
1 From the Start menu, select Programs, then Oracle EPM System, then instanceName, then Foundation
Services, and then Shared Services URL. Or, using a Web browser, open:
http://Hostname.Example.Com:WebServerListenPort/interop/
2 Log on to Shared Services.
3 Review the output for the WebLogic managed server in MIDDLEWARE_HOME/user_projects/
domains/EPMSystem/servers/SERVER_NAME/logs.
4 Review the product logs in EPM_ORACLE_INSTANCE/diagnostics/logs. You can also review
the diagnostics reports in EPM_ORACLE_INSTANCE/diagnostics/reports.
Verifying EPM Workspace Deployment and Products in EPM

Workspace
1 From the Start menu, select Programs, then Oracle EPM System, then instanceName, then
Workspace, and then Workspace URL. Or, using a Web browser, open
http://Hostname.Example.Com:WebServerListenPort/workspace/
2 Review the output for your WebLogic managed server in MIDDLEWARE_HOME/user_projects/
272
4 From the EPM Workspace Help menu, select About and in the Details section verify the list of installed
products.
5 Launch each listed product from EPM Workspace. The following products can be launched from EPM
Workspace:
l Reporting and Analysis Framework
l Financial Reporting
l Oracle Hyperion SQR Production Reporting
l Web Analysis
l Planning
l Performance Scorecard
l Profitability and Cost Management
Before you can access Profitability and Cost Management in EPM Workspace and verify
deployment, you must perform some initial tasks. See the Oracle Hyperion Profitability
and Cost Management Administrator's Guide.
l Performance Management Architect
l Calculation Manager
l FDMEE
l Financial Close Management. To perform additional verification for Financial Close
Management, see Additional Verification for Financial Close Management on page
273.
Additional Verification for Financial Close Management

To verify that the Oracle SOA Server and Financial Close Management are communicating:
1 After you launch Financial Close Management, create a schedule with a range that includes today's
date.
2 Create a task using the Basic Task Type on today's date, but set the start time to be earlier than the
current time.
3 Go to Manage Schedules, highlight the schedule, run Set Status, and then change status to Open.
4 Click Open and open the schedule in the Task List view.
The task should go from a pending to a running state (green triangle), because the task is
past its scheduled start time.
273
Verifying Administration Services Deployment
1 Using a Web browser, open:
WebServer:port/easconsole/console.html
2 Log on to Administration Services using the Java Web Start console.

Verifying Provider Services Deployment

1 Using a Web browser, open:
http://Hostname.Example.Com:WebServerListenPort/aps/APS
Validating a Financial Close Management Deployment

Financial Close Management Validation Tool scans the system configuration settings needed
for successful functioning of Financial Close Management. Oracle recommends that you run
Financial Close Management Validation Tool after you complete the installation and
configuration steps to test that the components for Financial Close Management are correctly
deployed and configured.
To use Financial Close Management Validation Tool:

1 From a Web browser, open the following URL:
FCMHOST:FCMPORT/fcc/faces/oracle/apps/epm/fcc/ui/page/FCCValidation.jspx
where FCMHOST is the machine where Financial Close Management is configured and
FCMPORT is port 8700. You can find this information from WebLogic Administration
Console. To view this information, log in to the Administration Console and navigate to
Environment, and then Servers.
2 Log in to the Financial Close Management Validation Tool with a user from the external provider. If there
are issues with the external provider configuration, log on with any seeded user (seeded both on
274
WebLogic Server and Shared Services native directory) and run the tool to identify issues with the external
provider configuration.
3 Review the status for each of the following:
Table 48 Validation tests for Financial Close Management
Validation Item Results
Admin Server Host

Port
Status (running/shutdown)
Foundation Services Host

Server
Port
Status
Data Sources targeted
Financial Close Host

Managed Server
Port
Status
SOA Server Host

Port
Status
SOA-infra status
FCM Web Application Version

Status
DB Type
Foreign JNDI EDN JMS (for SQL Server)

SOA JMS
Authentication Providers EPM Identity Asserter Provider information

Lib OVD configuration status
External Idstores Lists the external Identity store configuration. The tool lists the values used for the configuration. You must
ensure that the entered values are correct.
SOA composites List of SOA composites with their status
OWSM Keystore The keystore referenced in jps-config.xml and if it actually exists.
4 Look for failed tests, diagnose, and fix problems.

5 Run Financial Close Management Validation Tool again until all tests pass.
275
The second half of the Financial Close Management Validation Tool has a utility that
generates a test Main Orchestration Process, deploys it to a SOA server, and starts a test task.
A table displays the status for each task, the possible cause of any errors, and the steps to fix
it. Before proceeding, verify that the user logged in to the Financial Close Management
Validation Tool is also a user in Shared Services.
6 Click Validate Test Schedule.
The Validate Test Schedule button is enabled only if all the required configuration tests in
Table 48 pass without errors.
7 Review the status of the following tasks:
l SOA Composite Deployment
l Business Event
l Composite Instance
l FCM Basic Task
l Human Workflow
In case of any errors, the test SOA Composite and the test FCCTaskExecutionComposite
instance are not deleted and you can see more details of the error from the Enterprise
Manager console. If all the validation items are successful, then the test composite and
instance are deleted.
To use Account Reconciliation Validation Tool:

1 From a Web browser, open the following URL to run the Account Reconciliation Manager Validation Tool.
FCMHOST:FCMPORT/arm/faces/oracle/apps/epm/arm/ui/page/common/ARMValidation.jspx
where FCMHOST is the machine where Financial Close Management is configured and
FCMPORT is the listening port of the FinancialClose0 managed Server in the WebLogic
Administration Console. You can find this information from WebLogic Administration
Console. To view this information, log in to the Administration Console and navigate to
Environment, and then Servers.
2 Log in to the Account Reconciliation Validation Tool with the Shared Services Admin user.
3 Click Validate Account Reconciliation Manager Configuration.
4 Review the status for each of the following:
Table 49 Validation tests for Financial Close Management
Admin Server Host

Port
Status (running/shutdown)
276
Foundation Services Host

Server
Port
Status
Financial Close Host

Managed Server
Port
Status
SOA Server Host

Port
Status
SOA-infra status
ARM Web Application Version

Status
DB Type
Authentication Providers Provider (Configured/Not)

Control Flag (Sufficient/Not)
External Authenticators Lists the authentication providers
SOA Composites List of SOA composites with their status
Foreign JNDI EDN JMS (for SQL Server)

SOA JMS
OWSM Keystore Lists the external identity store configuration. The tool only lists the values used for the configuration. It
is the responsibility of the customer to make sure that the entered values are correct. Warning can be
ignored.
5 Look for failed tests, diagnose, and fix problems.

6 Run Account Reconciliation Validation Tool again until all tests pass.
277
278
Ports
A
In This Appendix
Default Ports and Shared Services Registry ........................................................... 279
WebLogic Administration Server Port .................................................................. 280
WebSphere Ports......................................................................................... 280
Oracle Enterprise Manager Java Web Application Port ............................................... 281
SOA Server Port .......................................................................................... 281
SSL Ports ................................................................................................. 281
Foundation Services Ports .............................................................................. 281
Essbase Ports ............................................................................................ 283
Reporting and Analysis Ports ........................................................................... 284
Financial Performance Management Applications Ports ............................................. 286
Data Management Ports ................................................................................ 289
This appendix contains information about default port numbers for EPM System products
including where the port can be configured.
Caution! These ports are not meant to be used to access a product. For information on starting
a product, see Chapter 12, Starting and Stopping EPM System Products..
Default Ports and Shared Services Registry

During the configuration process, default port numbers for most EPM System products are
automatically populated in Shared Services Registry. During configuration using EPM System
Configurator, you can change the default numbers. Each port number on the machine must be
unique. (The same product on different machines can have the same port number.) If an error
message similar to port already in use or bind error is displayed, a port number conflict may
exist.
If the default port is already in use on the machine, or if there is a conflict, EPM System
Configurator will not continue. If the default port number is not changed, the software is
configured with the default values.
279
WebLogic Administration Server Port
Table 50 WebLogic Administration Server Port
Default Port Number Where Configurable
7001 The WebLogic Administration Server port is specified during configuration. To change the default port, use the
WebLogic Administration Console.
WebSphere Ports
Subtopics
l WebSphere Application Server Port
l IBM HTTP Server Port
WebSphere Application Server Port

Table 51 WebSphere Application Server Port
9043 The WebSphere Application Server port is specified during configuration. To change the default port, use the
WebSphere Administration Console.
IBM HTTP Server Port

Table 52 IBM HTTP Server Port
Default Port Where Configurable

Number
80 The IBM HTTP Server port is specified during IBM HTTP Server installation. You can change the default port in the <IHS>/
conf/httpd.conf file. See Configuring IBM HTTP Server in the Oracle Enterprise Performance Management System
Installation and Configuration Guide.
Note: Both IBM HTTP Server and IIS Web Server use 80 as their default port. If you are using
WebSphere, you must change one of these defaults so that there is no port conflict.
280
Oracle Enterprise Manager Java Web Application Port
Table 53 Oracle Enterprise Manager Java Web Application Port
7001 The Oracle Enterprise Manager Java Web Application port is configured when you create the domain in EPM System
Configurator.
SOA Server Port

Table 54 SOA Server Port
8001 WebLogic Server Admin Console
SSL Ports
For more information about configuring SSL ports, see Oracle Enterprise Performance
Management System Security Configuration Guide.
Foundation Services Ports

See these sections for information about Foundation Services ports:
l Foundation Services Ports on page 281
l Performance Management Architect Ports on page 282
l Calculation Manager Java Web Application Ports on page 282
Foundation Services Ports

The following table describes the Foundation Services Managed Server Java web application
ports and where you can configure them. Foundation Services Managed Server includes Shared
Services, EPM Workspace, and Foundation Web Service.
Table 55 Foundation Services Java Web Application Ports
Port Type Default Port Number Where Configurable
Listen port 28080 EPM System Configurator
SSL listen port 28443 EPM System Configurator
281
Table 56 Web Server Ports
Server Default Server Port Where Configurable
Oracle HTTP 19000 MIDDLEWARE_HOME/user_projects/epmsystem1/httpConfig/ohs/config/

Server OHS/ohs_component/httpd.conf configurable in the EPM System Configurator.
IIS 80 Microsoft Internet Information Services (IIS) Manager Console. Change the TCP port value
setting.
443 (SSL)
Performance Management Architect Ports

Table 57 Performance Management Architect Java Web Application Ports
Performance Management Architect Java Web Application
Listen port 19091 (can be configured for SSL) EPM System Configurator
Data Synchronizer Java Web Application (Performance

Management Architect)
Listen port 19101 (can be configured for SSL) EPM System Configurator
Table 58 Performance Management Architect Server Ports
Services Default Port Number Where Configurable
Performance Management Architect Dimension Server 5251 EPM System Configurator
Net JNI Bridge 5255 EPM System Configurator
Table 59 Performance Management Architect Web Services (IIS) Port
Default Web Server Port Where Configurable
80 (HTTP) or 443 (when SSL is enabled) Microsoft Internet Information Services (IIS) Manager Console. Change the TCP port value
setting.
Calculation Manager Java Web Application Ports

Table 60 Calculation Manager Java Web Application Ports
282
Essbase Ports
See these sections for information about Essbase ports:
l Essbase Ports on page 283
l Administration Services Ports on page 284
l Provider Services Ports on page 284
l Essbase Studio Ports on page 284
Essbase Ports
Table 61 Essbase Default Service Ports
Service Default Port Number Where Configurable
Essbase Agent 1423 EPM System Configurator
Essbase server applications 3276833768 (two ports per EPM System Configurator
(ESSSVR) process)
Essbase SSL Agent 6423 EPM System Configurator
Integration Services Server 3388 EPM_ORACLE_HOME/products/Essbase/eis/bin/ais.cfg
Add -Pportnumber
Note: Starting in release 11.1.1, if you do not specify Essbase port numbers in EPM System
Configurator, the default ports are used.
Table 62 OPMN (Oracle Process Manager and Notification Server) Default Ports
Oracle Notification Server 6711 Open the opmn.xml file and modify the local parameter. Then save the file.
Local Port
Oracle Notification Server 6712 Open the opmn.xml file and modify the remote parameter. Then save the file.
Remote Port
283
Administration Services Ports
Table 63 Administration Services Java Web Application Ports
Provider Services Ports

Table 64 Provider Services Java Web Application Ports
Essbase Studio Ports

Table 65 Essbase Studio Server Ports
Listen port 5300 EPM_ORACLE_INSTANCE/BPMS/bpms1/bin/server.properties
Parameters: transport.port=new port number
HTTP listen port 12080 EPM_ORACLE_INSTANCE/BPMS/bpms1/bin/server.properties
Parameters: server.httpPort=new port number
Reporting and Analysis Ports

See these sections for information about Oracle Hyperion Reporting and Analysis ports:
l Reporting and Analysis Framework Ports on page 285
l Financial Reporting Ports on page 285
l Interactive Reporting Ports on page 286
l Web Analysis Ports on page 286
284
Reporting and Analysis Framework Ports
Table 66 Reporting and Analysis Framework Java Web Application Ports
Table 67 Reporting and Analysis Framework Default Service Ports
Reporting and Analysis 6860 EPM System Configurator

Framework Agent
Reporting and Analysis 6861 EPM System Configurator

Framework Agent RMI
Reporting and Analysis 68006805 l Use EPM System Configurator when you are installing or
Framework Services configuring Reporting and Analysis Framework Services for
Each service listed in this table is
l Global Services Manager assigned a port within the range, the first machine.
(GSM) either the default range 68006805 l To change a port number or find out the exact port used by
Core Service or the range specified during a particular component: from EPM Workspace, select
configuration. Navigate, then Administer, then Reporting and Analysis, then
l
l Service Broker Services, and then the Properties dialog box of Reporting
l Job Service and Analysis Framework Services.
l Event Service
l Repository Service
Financial Reporting Ports

Table 68 Financial Reporting Java Web Application Ports
Table 69 Financial Reporting Default Service Ports
Service Default Port Number Where

Configurable
RMI Services 8205-8228 EPM System

and Remote Configurator
Each Financial Reporting Java Web Application uses two ports, one for RMI services and one for
ADM Server
Remote ADM Server (e.g., first Financial Reporting Java Web Application uses ports 8205 and
8206).
285
Interactive Reporting Ports
Table 70 Interactive Reporting Default Service Ports
l Interactive Reporting 6810, 6811 (Log Service) l Use EPM System Configurator when you are installing or configuring
Logging Service Reporting and Analysis Framework Services for the first machine.
6812, 6813 (Intelligence
l Interactive Reporting Service): l To change a port number or find out the exact port used by a
Intelligence Service particular component: from EPM Workspace, select Navigate, then
6814, 6815 (Data Access
Data Access Service (DAS) Administer, then Reporting and Analysis, then Services, and then
Service)
the Properties dialog of Reporting and Analysis Framework Services
l
l Interactive Reporting Job 6816, 6817 (Job Service)

Service
Web Analysis Ports

Table 71 Web Analysis Java Web Application Ports
Financial Performance Management Applications

Ports
See these sections for information about Oracle's Hyperion Financial Performance Management
Applications ports:
l Financial Management Ports on page 287
l Financial Close Management Ports on page 287
l Planning Ports on page 288
l Performance Scorecard Ports on page 288
l Strategic Finance Ports on page 289
l Profitability and Cost Management Ports on page 289
l Disclosure Management Ports on page 289
286
Financial Management Ports
Table 72 Financial Management Java Web Application Port
Table 73 Financial Management Default Service Port
Service Default Port Where Configurable

Number
Financial 135-plus Windows settingsFix DCOM ephemeral ports.

Management Service ephemeral high-
See the Microsoft support article describing how to set the ports used by DCOM: http://
range ports (1024
support.microsoft.com. Search for "restrict DCOM port."
5536)
Financial 9097 EPM System Configurator

Management DME
Listener Service (for
use with Performance
Management
Architect)
Financial 9099 Update Oracle Hyperion Shared Services Registry

Management ADM
Listener Service
Table 74 Financial Management IIS Web Application Port
80 (HTTP) or 443 (when SSL is enabled) In Microsoft Internet Information Services (IIS) Manager Console, change the TCP port value
setting.
Note: The Financial Management IIS Web Applications: Financial Management Web Services
IIS Web Application,Financial Management Smart View IIS Web Application, Financial
Management IIS Web Application, and Financial Management LCM IIS Web
Application.
Financial Close Management Ports

The following table describes the Financial Close Management ports and where you can
configure them.
Table 75 Financial Close Management Close Manager and Account Reconciliation Manager Java Web Application Ports
Type of Port Default Port Number Where Configurable
287
Planning Ports
Table 76 Planning Java Web Application Ports
Table 77 Planning RMI Server Port
Planning RMI Server 11333 EPM System Configurator
Performance Scorecard Ports

Table 78 Performance Scorecard Java Web Application Ports
The following table describes the Performance Scorecard Alerter Java web application ports and
where you can configure them.
Table 79 Performance Scorecard Alerter Java Web Application Ports
288
Strategic Finance Ports
Table 80 Strategic Finance Default Service Port

Number
Strategic 7750 EPM System Configurator

Finance Server
Note: If you change this port, you must also change it for each Strategic Finance client in the
Connection dialog box.
Table 81 Strategic Finance Web Server Port
80 (HTTP) or 443 (when SSL is enabled) Microsoft Internet Information Services (IIS) Manager Console. (Change the TCP port value
setting.)
Table 82 Strategic Finance Web Application Port
Profitability and Cost Management Ports

Table 83 Profitability and Cost Management Java Web Application Ports
Disclosure Management Ports

Table 84 Disclosure Management Java Web Application Ports
Data Management Ports

See these sections for information about Oracle's Data Management ports.
289
l FDM Ports on page 290
l FDMEE Ports on page 290
l Data Relationship Management Ports on page 291
FDM Ports
The following table describes the FDM default service ports and where you can configure them.
Table 85 FDM Default Service Ports

Number
FDM load 135-plus Windows settingsFix DCOM ephemeral ports.

balancer ephemeral
For more information, see the Microsoft support article describing how to set the ports used by DCOM:
andFDM high-range
http://support.microsoft.com. Search for restrict DCOM port.
application ports (1024
server 65536)
File sharing 137139, Controlled by the operating system. By default, file sharing is enabled between all FDMapplication servers
445 and the data server. Default port numbers are the following:
l NetBIOS Datagram Service = port 138
l NetBIOS Name Resolution = port 137
l NetBIOS Session Service = port 139
If NetBIOS is turned OFF, then use SMB = port 445
Firewall 135 plus Windows settingsFix DCOM ephemeral ports.

ephemeral
For more information, see the Microsoft support article describing how to set the ports used by DCOM:
high-range
http://support.microsoft.com. Search for "restrict DCOM port."
ports (1024
65536)
Note: For FDM, the DCOM port 135 must be open if you are running in a DMZ environment.
The following table describes the FDM Web server port and where you can configure it.
Table 86 FDM Web Server (IIS) Port
setting.)
FDMEE Ports
The following table describes the FDMEE Java web application ports and where you can
configure them.
290
Table 87 FDMEE Java Web Application Ports
Data Relationship Management Ports

The following table describes the Data Relationship Management default service ports and where
you can configure them.
Table 88 Data Relationship Management Default Service Port
Data Relationship Management 52005400 drm-config.xml using the Data Relationship Management Console.
server applications
The following table describes the Data Relationship Management Web server ports and where
you can configure them.
Table 89 Data Relationship Management Web Server Ports
Default Web Server Ports Where Configurable
setting.)
291
292
JDBC URL Attributes
B
In This Appendix
JDBC Drivers.............................................................................................. 293
JDBC Drivers
During configuration, on the Configure Database page, click Advanced to specify additional
JDBC parameters, which are used by EPM System JDBC drivers to connect to the database.
The following table describes the format to use to enter the parameters if you are using JDBC
drivers.
Database Format
Oracle Database jdbc:oracle:thin:@hostname:port:SID
SQL Server jdbc:weblogic:sqlserver://hostname:port;databaseName=databaseName
DB2 jdbc:weblogic:db2://hostname:port;databaseName=databaseName;DynamicSections=3000
The following table describes additional information about the parameters:
Property SQL Server DB2
LOADLIBRARYPATH Yes Yes
MAXPOOLEDSTATEMENTS Yes Yes
ALTERNATESERVERS Yes Yes
CONNECTIONRETRYCOUNT Yes Yes
CONNECTIONRETRYDELAY Yes Yes
LOADBALANCING Yes Yes
DYNAMICSECTIONS Yes
CREATEDEFAULTPACKAGE Yes
REPLACEPACKAGE Yes
293
Property SQL Server DB2
DATABASENAME Yes Yes
For Oracle Database parameters, see the Oracle Thin JDBC Driver documentation.
URL for Oracle RAC

To provide client-side failover and load-balancing for Oracle RAC, enter the URL in the form
of:
jdbc:oracle:thin:@(DESCRIPTION=
@ (LOAD_BALANCE=on)
@ (ADDRESS=(PROTOCOL=TCP)(HOST=host1) (PORT=1521))
@ (ADDRESS=(PROTOCOL=TCP)(HOST=host2)(PORT=1521))
@ (CONNECT_DATA=(SERVICE_NAME=service_name)))
LDAP-Based URL for Oracle Database

Oracle Database supports authentication using an LDAP server. To use LDAP-based database
authentication, enter the URL in the following format:
jdbc:oracle:thin:@ldap://oid:5000/mydb1,cn=OracleContext,dc=myco,dc=com
URL for SSL

To enable SSL for the JDBC connections, during configuration, on the Configure Database page,
click Advanced and select Use secure connection to the database (SSL).
Use the following additional parameters when JDBC SSL is selected and you are using DB2 or
Microsoft SQL Server.
l ENCRYPTIONMETHOD=SSL
l TRUSTSTORE=Path to trust store
l TRUSTSTOREPASSWORD=trust store password
l VALIDATESERVERCERTIFICATE="true"
Use the following URL format when JDBC SSL is selected and you are using Oracle Database.
jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=tcps)
(HOST=host1)(PORT=1521))
(CONNECT_DATA=(SERVICE_NAME=servicename)
294
Database Information for
C Financial Management
In This Appendix
Database Connection Pooling .......................................................................... 295
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 EPM System Configurator
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.
l A pool of eight connections per application is reserved for error handling.
l 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. The DME Listener
process also consumes up to eight connections. These connections stay open for as long as this
process is running.
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
295
hardware and quantity of data being written. In general, users with Write access may use 5 10
connections.
Financial Management opens the defined number of connections when an application is first
opened. The connections are then available for subsequent users of the system. If a user process
requests a connection, and all connections are in use, the system polls the connection pool for
a 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 EPM System Configurator.
Connections are application-specific. The default pool is created only after an application is
opened. When all users are logged out of an application and all Web sessions have been closed,
the application shuts down and all database connections owned by that application are released.
When all open applications shut down, the eight connections reserved for application server
activity are released as well. If any one application remains open, the application server
connections stay open as well.
If the Financial Management Service is running, connections are allocated and released on an
application basis. When no users are logged in to a given application, it shut downs and all
connections consumed by that application are released.
If the Financial Management Service is not running, then after the last user logs out of an
application all connections allocated for that application are released. If the Financial
Management Service is running, then connections are released when the machine is restarted
or when the service is stopped and all users log out of a given application.
Note: Note that application processes do not shut down even when all users have logged out of
all applications if the Financial Management Service is running, because the service
perpetuates application instances. In addition, in an environment with more than one
Financial Management application server, all users might need to log out of all
applications on all servers before the application process shuts down and the database
connections are released. In both cases, you must also stop the Financial Management
service.
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)
l Application B is logged on: 8 connections (plus system)
l Application C is logged on: 8 connections (plus system)
296
l System connections: 59 (8 plus 17 per application)
l Total connections: 83
Note: Total connections could grow by 96 if all application connection pools expand to the
system maximum as defined in EPM System Configurator (default is 40).
l Application B is logged off (no users)
l All users log off all applications
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)
l Application A is logged on (server 2): 8 connections (plus system)
l System connections: 50 (8 plus 17 per application per application server)
l Application A (server 2) is logged off (no users)
l All users log off all applications
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.
297
298
EPM System Services
D
In This Appendix
EPM System Services and Processes .................................................................. 300
This appendix provides details about start menus, service names, and start and stop scripts for
each EPM System component.
Note that Start menu items for Java web applications are available only on the machine on which
the Web server is installed.
You can monitor the health and performance of the EPM System Java web applications using
Oracle Enterprise Manager, which is automatically deployed with Oracle Hyperion Enterprise
Performance Management System Configurator if you deploy Java web applications with Oracle
WebLogic Server. You can see the status of the servers and the Java web applications running,
the servers they are running on, and the ports they are listening on. See Using Enterprise
Manager to Monitor EPM System Java Web Applications in the Oracle Enterprise Performance
Management System Deployment Options Guide.
299
EPM System Services and Processes
Subtopics
l Web Server
l Foundation Services Application Server
l Performance Management Architect Dimension Server Services
l Performance Management Architect Application Server
l Performance Management Architect Data Synchronizer Application Server
l Calculation Manager Application Server
l Essbase Server
l Administration Services Server
l Integration Services Server
l Essbase Studio Server
l Provider Services Application Server
l Hyperion Reporting and Analysis Framework - Agent Service
l Reporting and Analysis Framework Application Server
l Financial Reporting Application Server
l Web Analysis Application Server
l Planning Application Server
l Financial Management Services
l Financial Management Application Server
l Strategic Finance Server
l Strategic Finance Web Application
l Performance Scorecard Application Server
l Performance Scorecard Alerter Application Server
l Profitability and Cost Management Application Server
l Disclosure Management Application Server
l Financial Close Management Application Server
l Data Relationship Management
l FDM
l FDMEE Application Server
If you deploy components to a single managed server, the managed server name is
EPMServerN, where N is 0 for the managed server, and 1 or higher if you scale out the single
managed server.
Web Server
The following table describes the services and processes for the Web server if you used the Oracle
HTTP Server installed by EPM System Installer.
The Oracle HTTP Server service is managed with OPMN.
For information about OPMN, see the Oracle Fusion Middleware Oracle Process Manager and
Notification Server Administrator's Guide Release 11g (11.1.1.2.0) (http://
download.oracle.com/docs/cd/E15523_01/doc.1111/e14007/toc.htm)
300
Table 90 Web Server Services and Processes
Information Details
Type
Display Name l Oracle Process Manager (ohsInstanceInstanceNumber)

in Windows IIS: IIS Admin Service
Services
l
Control Panel l IBM HTTP Server 7.0
Description l OPMN Service for OHS

l 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.
l IHS: IBM_HTTP_Server/7.0.0.17 (Win32)
Windows EPM_ORACLE_INSTANCE/bin/startOHS.bat
Startup Script
Note that this start script redirects Oracle HTTP Server to start using OPMN. The OPMN start script opmnctl.bat is
(For Oracle
located in EPM_ORACLE_INSTANCE/httpConfig/ohs/bin.
HTTP Server
installed by
EPM System
Installer only)
UNIX Startup EPM_ORACLE_INSTANCE/bin/startOHS.sh

Script (For
Note that this start script redirects Oracle HTTP Server to start using OPMN. The OPMN start script opmnctl is located
Oracle HTTP
in EPM_ORACLE_INSTANCE/httpConfig/ohs/bin
Server
installed by
EPM System
Installer only)
Windows Stop EPM_ORACLE_INSTANCE/bin/stopOHS.bat

Script (For
Oracle HTTP
Server
installed by
EPM System
Installer only)
UNIX Stop EPM_ORACLE_INSTANCE/bin/stopOHS.sh

Script (For
Oracle HTTP
Server
installed by
EPM System
Installer only)
Foundation Services Application Server

The following table describes the services and processes for the Oracle Hyperion Foundation
Services application server, which includes Oracle Hyperion Shared Services, and Oracle
Hyperion Enterprise Performance Management Workspace Java web applications.
301
Table 91 Foundation Services Application Server Services and Processes
Information Type Details
Windows Start Select Start, then Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE_NAME, then Foundation
Menu Command Services, and then Start FoundationServices
Registered Service HyS9FoundationServices_instanceName

Name
Display Name in Oracle Hyperion Foundation Services - Managed Server (instanceName)

Windows Services
Control Panel
Description Hyperion Foundation Services support Hyperion applications, including authentication, user provisioning, task flow
management, data and metadata synchronization
Windows Startup EPM_ORACLE_INSTANCE/bin/startFoundationServices.bat

Script
UNIX Startup Script EPM_ORACLE_INSTANCE/bin/startFoundationServices.sh
Windows Stop EPM_ORACLE_INSTANCE/bin/stopFoundationServices.bat

Script
UNIX Stop Script EPM_ORACLE_INSTANCE/bin/stopFoundationServices.sh
Performance Management Architect Dimension Server

Services
The following table describes the services and processes for the Performance Management
Architect services.
Note: When the Dimension Server and the database are hosted on different servers, startup time
can take several minutes, because Performance Management Architect makes calls to the
database during startup.
Table 92 Performance Management Architect Services
Windows Start Menu N/A

Command
Registered Service Name HYS9EPMAServer_instanceName
Display Name in Windows Oracle Hyperion EPMA Server (instanceName)

Services Control Panel
Description Hyperion EPM Architect Dimension Server provides the back services needed by the EPMA Web Tier,
including dimensionality, applications, and the jobs console.
302
Windows Startup Script EPM_ORACLE_INSTANCE/bin/StartEpmaServer.bat
UNIX Startup Script NA
Windows Stop Script l Process Manager: EPM_ORACLE_INSTANCE/bin/stopEpmaServer.bat
UNIX Stop Script NA
Performance Management Architect Application Server

The following table describes the services and processes for the Performance Management
Architect application server.
Table 93 Performance Management Architect Application Server Services and Processes
Windows Start Menu Select Start, then Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE_NAME, then Foundation
Command Services, then Performance Management Architect, and then startEpmaWebReports
Registered Service HyS9EPMAWebTier_instanceName

Name
Display Name in Oracle Hyperion EPMA Web Tier - Java Web Application (instanceName)
Windows Services
Control Panel
Description Provide access service to EPMA Web Server
Windows Startup EPM_ORACLE_INSTANCE/bin/startEpmaWebReports.bat

Script
UNIX Startup Script EPM_ORACLE_INSTANCE/bin/startEpmaWebReports.sh
Windows Stop Script EPM_ORACLE_INSTANCE/bin/stopEpmaWebReports.bat
UNIX Stop Script EPM_ORACLE_INSTANCE/bin/stopEpmaWebReports.sh
In addition, Performance Management Architect has a Web tier component that runs in IIS.
Performance Management Architect Data Synchronizer

Application Server
The following table describes the services and processes for the Oracle Hyperion EPM Architect
Data Synchronizer application server.
303
Table 94 Performance Management Architect Data Synchronizer Application Server Services
Windows Start Menu Select Start, then Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE_NAME, then Foundation
Command Services, then Performance Management Architect, and then startEPMADataSync
Registered Service HyS9EPMADataSynchronizer_instanceName

Name
Display Name in Oracle Hyperion EPMA Data Synchronizer - Java Web Application (instanceName)
Windows Services
Control Panel
Description Provide access service to EPMA Data Synchronizer Web Server
Windows Startup EPM_ORACLE_INSTANCE/bin/startEPMADataSync.bat

Script
UNIX Startup Script EPM_ORACLE_INSTANCE/bin/startEPMADataSync.sh
Windows Stop Script EPM_ORACLE_INSTANCE/bin/stopEPMADataSync.bat
UNIX Stop Script EPM_ORACLE_INSTANCE/bin/stopEPMADataSync.sh
Calculation Manager Application Server

The following table describes the services and processes for Oracle Hyperion Calculation
Manager.
Table 95 Calculation Manager Services and Processes
Windows Start Menu Select Start, then Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE_NAME, then Calculation
Command Manager, and then Start CalcMgr
Registered Service HyS9CALC_instanceName

Name
Display Name in Oracle Hyperion CALC Manager - Java Web Application (instanceName)
Windows Services
Control Panel
Description Provide access service to CALC Manager Web Server
Windows Startup Script EPM_ORACLE_INSTANCE/bin/startCalcMgr.bat
UNIX Startup Script EPM_ORACLE_INSTANCE/bin/startCalcMgr.sh
Windows Stop Script EPM_ORACLE_INSTANCE/bin/stopCalcMgr.bat
UNIX Stop Script EPM_ORACLE_INSTANCE/bin/stopCalcMgr.sh
304
Essbase Server
During installation, Oracle Hyperion Enterprise Performance Management System Installer
installs OPMN and registers Essbase Server for OPMN. OPMN manages the Essbase Agent,
which manages the Essbase Server.
Navigate to EPM_ORACLE_INSTANCE/bin and use the following commands to start and stop
Essbase Server:
l opmnctl startall
l opmnctl stopall
If you are using Essbase in a clustered environment, there are additional steps required to set up
Essbase failover on both nodes of the cluster. See Editing OPMN.XML for Active-Passive
Essbase Clusters in the Oracle Enterprise Performance Management System Deployment Options
Guide.
The following table describes additional methods for starting and stopping Essbase Server. Note
that the Essbase Server start and stop scripts redirect to OPMN.
For information about OPMN, see the Oracle Fusion Middleware Oracle Process Manager and
Notification Server Administrator's Guide Release 11g (11.1.1.2.0) (http://
download.oracle.com/docs/cd/E15523_01/doc.1111/e14007/toc.htm)
Table 96 Starting and Stopping Essbase Server
Information Details
Type
Windows Select Start, then Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE_NAME, then Essbase, then
Start Menu Essbase Server, and then Start Essbase
Command
This command launches startEssbase.bat (and redirects to OPMN).
Registered Oracle Process Manager_instanceName

Service Name
Display Name Oracle Process Manager_instanceName

in Windows
Services
Control Panel
Description OPMN service for Essbase (instanceName)
305
Information Details
Type
Windows l Essbase Server EPM_ORACLE_INSTANCE/bin/startEssbase.bat (redirects to OPMN)

Startup
Script Each instance of Essbase Server has its own startup script. If you configured an additional instance of Essbase,
startEssbase.bat|sh is located in additionalInstanceLocation/bin. Launch the start script from this
location to launch this instance of Essbase.
l ESSCMD EPM_ORACLE_INSTANCE/EssbaseServer/EssbaseServerInstanceName/bin/
startEsscmd.bat (also available in the /EssbaseClient directory)
l essmsh EPM_ORACLE_INSTANCE/EssbaseServer/EssbaseServerInstanceName/bin/startMaxl.
bat (also available in the /EssbaseClient directory)
All the scripts call setEssbaseEnv.bat to set up ESSBASEPATH, ARBORPATH, and PATH before starting.
UNIX Startup l Essbase Server EPM_ORACLE_INSTANCE/bin/startEssbase.sh (redirects to OPMN)

Script
Each instance of Essbase Server has its own startup script. If you configured an additional instance of Essbase,
startEssbase.bat|sh is located in additionalInstanceLocation/bin. Launch the start script from this
location to launch this instance of Essbase.
l ESSCMD EPM_ORACLE_INSTANCE/EssbaseServer/EssbaseServerInstanceName/bin/
startEsscmd.sh (also available in the /EssbaseClient directory)
l essmsh EPM_ORACLE_INSTANCE/EssbaseServer/EssbaseServerInstanceName/bin/startMaxl.
sh (also available in the /EssbaseClient directory)
All the scripts call setEssbaseEnv.sh to set up ESSBASEPATH, ARBORPATH, and PATH before starting.
When running Essbase manually from a console, the console cannot be set to UTF-8 encoding.
Windows Stop Server:

Script
l Essbase Server EPM_ORACLE_INSTANCE/bin/stopEssbase.bat (redirects to OPMN)
UNIX Stop Server:

Script
l Essbase Server EPM_ORACLE_INSTANCE/bin/stopEssbase.sh (redirects to OPMN)
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.
See the Oracle Essbase Database Administrator's Guide for more information about shutting
down Essbase Server.
For more information about stopping Essbase Server, see the Oracle Essbase Database
Administrator's Guide and the Oracle Essbase Technical Reference.
Administration Services Server

The following table describes the services and processes for the Oracle Essbase Administration
Services server.
306
Table 97 Administration Services Application Server Service/Process
Windows Start Menu Select Start, then Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE_NAME, then Essbase, then
Command Essbase Administration Services, and then Start EssbaseAdminServices
Registered Service Hys9eas_instanceName

Name
Display Name in Oracle Hyperion Administration Services - Java Web Application (instanceName)
Windows Services
Control Panel
Description HyS9eas - Controls the running of an Applications Server
Windows Startup EPM_ORACLE_INSTANCE/bin/startEssbaseAdminServices.bat

Script
UNIX Startup Script EPM_ORACLE_INSTANCE/bin/startEssbaseAdminServices.sh
Windows Stop Script EPM_ORACLE_INSTANCE/bin/stopEssbaseAdminServices.bat
UNIX Stop Script EPM_ORACLE_INSTANCE/bin/startEssbaseAdminServices.sh
Integration Services Server

The following table describes the services and processes for the Integration Services server.
Table 98 Integration Services Server Service/Process
Windows Start Select Start, then Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE_NAME, then Essbase, then
Menu Command Integration Services, and then Start Essbase Integration Server1
Registered Service Essbase Integration Server_instanceName

Name
Display Name in Oracle Hyperion Integration Services (instanceName)

Windows Services
Control Panel
Description N/A
Windows Startup EPM_ORACLE_INSTANCE/bin/startEisServer.bat

Script
UNIX Startup EPM_ORACLE_INSTANCE/bin/startEisServer.sh

Script
Windows Stop EPM_ORACLE_INSTANCE/bin/stopEisServer.bat

Script
Note that you must manually stop the Integration Services service manually using the Task Manager.
307
UNIX Stop Script EPM_ORACLE_INSTANCE/bin/stopEisServer.sh
Note that you must manually stop the Oracle Essbase Integration Services service by stopping the process.
1For 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 99 Essbase Studio Server
Windows Start Menu Select Start, then Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE_NAME, then Essbase,
Command then Essbase Studio, and then Start Server
Registered Service HYS9EssbaseStudio_instanceName

Name
Display Name in Oracle Hyperion Essbase Studio Server (instanceName)

Windows Services
Control Panel
Description NA
Windows Startup EPM_ORACLE_INSTANCE/bin/startBPMS_bpms1_Server.bat

Script
UNIX Startup Script EPM_ORACLE_INSTANCE/bin/startBPMS_bpms1_Server.sh
Windows Stop Script EPM_ORACLE_INSTANCE/bin/stopBPMS_bpms1_Server.bat
UNIX Stop Script EPM_ORACLE_INSTANCE/bin/stopBPMS_bpms1_Server.sh
By default, Essbase Studio Server runs in the background on UNIX. This behavior is controlled
by a combination of an Essbase Studio Server property (server.runInBackground), EPM
System environment variables, and startServer.sh.
To start Essbase Studio Server in the foreground on UNIX:

1. In the Essbase Studio server.properties file, set the server.runInBackground
property to false or comment it out.
The server.properties file is located in EPM_ORACLE_INSTANCE/user_projects/
epmsystem1/BPMS/bpms/bin/server.properties. See Oracle Essbase Studio User's
Guide for information on this property.
2. Set these variables in the environment where you plan to run startServer.sh:
EPM_ORACLE_INSTANCE=/installationPath/Oracle/Middleware/user_projects/epmsystem1
308
EPM_ORACLE_HOME=/installationPath/Oracle/Middleware/EPMSystem11R1
JAVA_HOME="${EPM_ORACLE_HOME}/../jdk160_21/jre"
JAVA_OPTIONS="-DESSBASE_STUDIO_INSTANCE=${EPM_ORACLE_INSTANCE}/BPMS/bpms1
-DsuppressAPSProductInfo=true"
3. Edit the Essbase Studio startServer.sh shell as follows:
startServer.sh is located in EPM_ORACLE_HOME/products/Essbase/
EssbaseStudio/Server/startServer.sh.
l Locate the last line of the file:

nohup "${JAVA_HOME}/bin/java" -Xms128m -Xmx768m $JAVA_OPTIONS jar
"${EPM_ORACLE_HOME}/products/Essbase/EssbaseStudio/Server/server.jar" >/dev/null
&
l Remove nohup from the beginning of the line, the STDOUT to null direction (>/dev/
null), and the background processing command (&) from the line; for example:
"${JAVA_HOME}/bin/java" -Xms128m -Xmx768m $JAVA_OPTIONS -jar "${EPM_ORACLE_HOME}/
products/Essbase/EssbaseStudio/Server/server.jar"
4. Start Oracle Essbase Studio Server by running the following statement: ./
startServer.sh.
Provider Services Application Server

The following table describes the services and processes for the Oracle Hyperion Provider
Services application server.
Table 100 Provider Services Application Server Services and Processes
Windows Start Select Start, then Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE_NAME, then Essbase, then
Menu Command Provider Services, and then Start AnalyticProviderServices
Registered Service HyS9aps_instanceName

Name
Display Name in Oracle Hyperion Provider Services - Java Web Application (instanceName)
Windows Services
Control Panel
Description Provide access service to Hyperion Provider Services
Windows Startup EPM_ORACLE_INSTANCE/bin/startAnalyticProviderServices.bat

Script
UNIX Startup Script EPM_ORACLE_INSTANCE/bin/startAnalyticProviderServices.sh
Windows Stop EPM_ORACLE_INSTANCE/bin/stopAnalyticProviderServices.bat

Script
UNIX Stop Script EPM_ORACLE_INSTANCE/bin/stopAnalyticProviderServices.sh
309
Hyperion Reporting and Analysis Framework - Agent Service
The following table describes the services and processes for the Reporting and Analysis
Framework Agent.
Table 101 Reporting and Analysis Framework Agent
Windows Start Menu Select Start, then Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE_NAME, then Reporting
Command and Analysis, and then Start RA Framework Agent
Registered Service HyS9RaFrameworkAgent_instanceName

Name
Display Name in Oracle Hyperion Reporting and Analysis Framework (instanceName)

Windows Services
Control Panel
Description HyS9RaFrameworkAgent - Hyperion Reporting and Analysis Framework Agent
Windows Startup EPM_ORACLE_INSTANCE/bin/startRaFrameworkAgent.bat

Script
UNIX Startup Script EPM_ORACLE_INSTANCE/bin/startRaFrameworkAgent.sh
Windows Stop Script EPM_ORACLE_INSTANCE/bin/stopRaFrameworkAgent.bat
UNIX Stop Script EPM_ORACLE_INSTANCE/bin/stopRaFrameworkAgent.sh
Services and Processes Started with Reporting and Analysis Framework

Agent Service
When the Reporting and Analysis Framework Agent is started, these additional services and
processes are started:
l Oracle Hyperion Interactive Reporting process.
l Reporting and Analysis Framework common services and processes
Reporting and Analysis Framework Application Server

The following table describes the services and processes for the Reporting and Analysis
Framework application server.
310
Table 102 Reporting and Analysis Framework Application Server
Windows Start Select Start, then Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE_NAME, then Reporting and
Menu Command Analysis, then Start RA Framework
This menu item starts:
l Reporting and Analysis Framework Java web application
l Oracle Hyperion Reporting and Analysis Framework Agent Service
Registered Service HyS9RaFramework_instanceName

Name
Display Name in Oracle Hyperion Reporting and Analysis Framework - Java Web Application (instanceName)
Windows Services
Control Panel
Description HyS9RaFramework - Hyperion Reporting and Analysis Framework web application
Windows Startup EPM_ORACLE_INSTANCE/bin/startRaFramework.bat

Script
UNIX Startup EPM_ORACLE_INSTANCE/bin/startRaFramework.sh

Script
Windows Stop EPM_ORACLE_INSTANCE/bin/stopRaFramework.bat

Script
UNIX Stop Script EPM_ORACLE_INSTANCE/bin/stopRaFramework.sh
Financial Reporting Application Server

The following table describes the services and processes for the Financial Reporting application
server, which includes the Financial Reporting Print Server.
Table 103 Financial Reporting Application Server Services and Processes
Windows Start Menu Select Start, then Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE_NAME, then Reporting
Command and Analysis, and then Start FinancialReporting
Registered Service HyS9FRReports_instanceName

Name
Display Name in Oracle Hyperion Financial Reporting - Java Web Application (instanceName)
Windows Services
Control Panel
Description Provide access service to Hyperion Financial Reporting Web Server
Windows Startup EPM_ORACLE_INSTANCE/bin/startFinancialReporting.bat

Script
UNIX Startup Script EPM_ORACLE_INSTANCE/bin/startFinancialReporting.sh
311
Windows Stop Script EPM_ORACLE_INSTANCE/bin/stopFinancialReporting.bat
UNIX Stop Script EPM_ORACLE_INSTANCE/bin/stopFinancialReporting.sh
Web Analysis Application Server

The following table describes the services and processes for the Oracle Hyperion Web Analysis
application server.
Table 104 Web Analysis Application Server Services and Processes
Windows Start Select Start, then Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE_NAME, then Reporting and
Menu Command Analysis, and then Start Reporting and Analysis Web Analysis
Registered Service HyS9WebAnalysis_instanceName

Name
Display Name in Oracle Hyperion Web Analysis - Java Web Application (instanceName)
Windows Control
Description Provide access service to Hyperion Web Analysis - Web Application
Windows Startup EPM_ORACLE_INSTANCE/bin/startWebAnalysis.bat

Script
UNIX Startup Script EPM_ORACLE_INSTANCE/bin/startWebAnalysis.sh
Windows Stop EPM_ORACLE_INSTANCE/bin/stopWebAnalysis.bat

Script
UNIX Stop Script EPM_ORACLE_INSTANCE/bin/stopWebAnalysis.sh
Planning Application Server

The following table describes the services and processes for the Planning application server.
Table 105 Planning Application Server Services and Processes
Windows Start Menu Select Start, then Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE_NAME, then Planning,
Command and then Start Planning
Registered Service HyS9Planning_instanceName

Name
312
Display Name in Oracle Hyperion Planning - Java Web Application (instanceName)

Windows Services
Control Panel
Description Provides access service to Planning Web server
Windows Startup EPM_ORACLE_INSTANCE/bin/startPlanning.bat

Script
UNIX Startup Script EPM_ORACLE_INSTANCE/bin/startPlanning.sh
Windows Stop Script EPM_ORACLE_INSTANCE/bin/stopPlanning.bat
UNIX Stop Script EPM_ORACLE_INSTANCE/bin/stopPlanning.sh
In addition, Oracle Hyperion Planning uses the Hyperion RMI Registry.
Table 106 Hyperion RMI Registry Application Server Services and Processes
Windows Start Menu Command N/A
Registered Service Name Hyperion RMI Registry_instanceName
Display Name in Windows Services Control Panel Oracle Hyperion RMI Registry (instanceName)
Description N/A
Windows Startup Script EPM_ORACLE_INSTANCE/startRMI.bat
UNIX Startup Script EPM_ORACLE_HOME/common/RMI/11.1.2.0/HyperionRMIService
Windows Stop Script EPM_ORACLE_INSTANCE/stopRMI.bat
UNIX Stop Script N/A
Financial Management Services

The following table describes the services and processes for Financial Management.
Table 107 Financial Management Services and Processes
Information Details
Type
Windows Start
Menu
Command
313
Information Details
Type
Registered l HYS9FinancialManagementService_instanceName
Service Name l HYS9 FinancialManagemen DMEListener_instanceName
l HYS9FinancialManagementWebServiceManager_instanceName
Display Name l Oracle Hyperion Financial Management Management Service (instanceName)

in Windows Oracle Hyperion Financial Management DME Listener (instanceName)
Services
l
Control Panel l Oracle Hyperion Financial Management Web Service Manager (instanceName)
Description l Hyperion Financial Management Service: Service which perpetuates application instances for optimal login
performance
l 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 not be able to communicate
with all HFM instances on this server.
l Manages the session information for connection in the Financial Management web server.
Windows l EPM_ORACLE_INSTANCE/bin/startHFMManagementService.bat
Startup Script l EPM_ORACLE_INSTANCE/bin/startHFMDMEListener.bat
l EPM_ORACLE_INSTANCE/bin/startHFMWebServiceManager.bat
UNIX Startup NA
Script
Windows Stop l EPM_ORACLE_INSTANCE/bin/stopHFMManagementService.bat

Script l EPM_ORACLE_INSTANCE/bin/stopHFMDMEListener.bat
l EPM_ORACLE_INSTANCE/bin/stopHFMWebServiceManager.bat
UNIX Stop NA
Script
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.
Financial Management Application Server

The following table describes the services and processes for the Financial Management Java web
application server, which includes FM Web services and FM ADF Java web application.
314
Table 108 Financial Management Java Web Application Services and Processes
Windows Start Menu Select Start, then Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE_NAME, then Financial
Command Management, and then Start HFMWeb
Registered Service HyS9FinancialManagementWeb_instanceName

Name
Display Name in Oracle Hyperion Financial Management - Web Tier (instanceName)

Windows Services
Control Panel
Description Provides JEE support to Financial Management.
Windows Startup Script EPM_ORACLE_INSTANCE/bin/startHFMWeb.bat
Windows Stop Script EPM_ORACLE_INSTANCE/bin/stopHFMWeb.bat
UNIX Stop Script NA
In addition, Financial Management has a Web tier component that runs in IIS.
Strategic Finance Server

The following table describes the services and processes for Strategic Finance.
Table 109 Strategic Finance Services and Processes
Windows Start Menu Select Start, then Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE_NAME, then Strategic
Command Finance, then Server, and then Start Strategic Finance Service
Registered Service HYS9HsfSrv_instanceName

Name
Display Name in Oracle Hyperion Strategic Finance - Server (instanceName)

Windows Services
Control Panel
Description Provides Oracle Hyperion Strategic Finance, Fusion Edition services including entity repository management,
authentication, access control, consolidation, data and metadata management
Windows Startup EPM_ORACLE_INSTANCE/bin/startStrategicFinanceService.bat

Script
Windows Stop Script EPM_ORACLE_INSTANCE/bin/stopStrategicFinanceService.bat
UNIX Stop Script NA
315
Strategic Finance Web Application
The following table describes the services and processes the Strategic Finance Web application.
Table 110 Strategic Finance Application Server Services and Processes
Windows Start Menu Select Start, then Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE_NAME, then Strategic
Command Finance, and then Start HSFWeb
Registered Service Name HyS9HsfWeb_instanceName
Display Name in Windows Oracle Hyperion Strategic Finance - Java Web Application (instanceName)
Description Provide access service to HSF Web Server.
Windows Startup Script EPM_ORACLE_INSTANCE/bin/startHsfWeb.bat
UNIX Startup Script
Windows Stop Script EPM_ORACLE_INSTANCE/bin/stopHsfWeb.bat
UNIX Stop Script
In addition, Oracle Hyperion Strategic Finance has a Web tier component that runs in IIS.
Performance Scorecard Application Server

The following table describes the services and processes for the Performance Scorecard
application server.
Note: If you are using Essbase as a data source for Performance Scorecard, you must start Oracle
Essbase first.
Table 111 Performance Scorecard Application Server Services and Processes
Windows Start Menu Select Start, then Programs, then Oracle EPM System, then Scorecard, and then Start HpsWebReports
Command
Registered Service Name WebReports
Display Name in Windows Oracle Hyperion Performance Scorecard WebReports - Java Web Application (instanceName)
Description Oracle Hyperion Performance Scorecard Web Reports - Java Web Application (instanceName)
Windows Startup Script EPM_ORACLE_INSTANCE/bin/startHpsWebReports.bat
316
UNIX Startup Script EPM_ORACLE_INSTANCE/bin/startHpsWebReports.sh
Windows Stop Script EPM_ORACLE_INSTANCE/bin/stopHpsWebReports.bat
UNIX Stop Script EPM_ORACLE_INSTANCE/bin/stopHpsWebReports.sh
Performance Scorecard Alerter Application Server

The following table describes the services and processes for the Oracle Hyperion Performance
Scorecard Alerter application server.
Table 112 Performance Scorecard Alerter Application Server Services and Processes
Windows Start Menu Command Select Start, then Programs, then Oracle EPM System, then Scorecard, and then Start HpsAlerter
Registered Service Name HyS9HPSAlerter_instanceName
Display Name in Windows Services Oracle Hyperion Performance Scorecard Alerter - Java Web Application (instanceName)
Control Panel
Description Oracle Hyperion Performance Scorecard Alerter - Java Web Application
Windows Startup Script EPM_ORACLE_INSTANCE/bin/startHpsAlerter.bat
UNIX Startup Script EPM_ORACLE_INSTANCE/bin/startHpsAlerter.sh
Windows Stop Script EPM_ORACLE_INSTANCE/bin/stopHpsAlerter.bat
UNIX Stop Script EPM_ORACLE_INSTANCE/bin/stopHpsAlerter.sh
Profitability and Cost Management Application Server

The following table describes the services and processes for Oracle Hyperion Profitability and
Cost Management.
Table 113 Profitability and Cost Management Services and Processes
Windows Start Menu Select Start, then Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE_NAME, then Profitability,
Command and then Start Profitability
Registered Service HyS9HyS9PftWeb_instanceName

Name
Display Name in Oracle Hyperion Profitability - Java Web Application (instanceName)

Windows Services
Control Panel
317
Description Provides a Workspace module for Profitability.
Windows Startup EPM_ORACLE_INSTANCE/bin/startProfitability.bat

Script
UNIX Startup Script EPM_ORACLE_INSTANCE/bin/startProfitability.sh
Windows Stop Script EPM_ORACLE_INSTANCE/bin/stopProfitability.bat
UNIX Stop Script EPM_ORACLE_INSTANCE/bin/stopProfitability.sh
Disclosure Management Application Server

The following table describes the services and processes for Oracle Hyperion Disclosure
Management.
Table 114 Disclosure Management Services and Processes
Windows Start Select Start, then Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE_NAME, then Disclosure
Menu Command Management, and then Start Disclosure Management
Registered Service HyS9Disclosure_instanceName

Name
Display Name in Oracle Hyperion Disclosure Management - Java Web Application (instanceName)
Windows Services
Control Panel
Description Provide access service to Disclosure Management
Windows Startup EPM_ORACLE_INSTANCE/bin/startDisclosureManagement.bat

Script
UNIX Startup Script EPM_ORACLE_INSTANCE/bin/startDisclosureManagement.sh
Windows Stop EPM_ORACLE_INSTANCE/bin/stopDisclosureManagement.bat

Script
UNIX Stop Script EPM_ORACLE_INSTANCE/bin/stopDisclosureManagement.sh
Financial Close Management Application Server

The following table describes the services and processes for the Financial Close Management
application server, which includes Close Manager and Account Reconciliation Manager.
318
Note: Ensure that you complete the post-configuration tasks before you start Financial Close
Management. See Financial Close Management Manual Configuration Tasks on page
179.
Caution! If you started the SOA Server to configure Financial Close Management, stop it
before starting Oracle Enterprise Performance Management System services.
Note: Before you start Financial Close Management, note the following server startup order:
l WebLogic Administration Server

l Hyperion Foundation Services Managed Server
l Oracle HTTP Server - Oracle Process Manager (ohsInstanceInstanceNumber)
l In any order:
m Financial Close Management Java web application
m Financial Management Web Services Managed Server, if youre using Oracle Hyperion
Financial Management with Financial Close Management
m FDM Web application, if youre using FDM with Financial Close Management
m Financial Reporting Java web application, if youre using Oracle Hyperion Financial
Reporting with Oracle Hyperion Financial Close Management
m FDMEE, if you are using Account Reconciliation Manager.
l Oracle SOA managed server
Table 115 Financial Close Management Services and Processes
Command Close, and then Start FinancialClose
Registered Service HyS9FinancialClose_instanceName

Name
Display Name in Oracle Hyperion Financial Close Management - Java Web Application (instanceName)
Windows Services
Control Panel
Description Provide access service to Financial Close Manager Java Web Application
Windows Startup EPM_ORACLE_INSTANCE/bin/startFinancialClose.bat

Script
UNIX Startup Script EPM_ORACLE_INSTANCE/bin/startFinancialClose.sh
Windows Stop Script EPM_ORACLE_INSTANCE/bin/stopFinancialClose.bat
UNIX Stop Script EPM_ORACLE_INSTANCE/bin/stopFinancialClose.sh
319
Data Relationship Management
The following table describes the services and processes for Data Relationship Management.
Table 116 Data Relationship Management Services and Processes
Windows Start Menu From the Start menu, select Programs, then Oracle EPM System, then Data Relationship Management, then
Command Configuration Console or EPM_ORACLE_HOME/ products/DataRelationshipManagement/server/
bin/drm-server-console.exe
Registered Service Oracle DRM Server Processes

Name
Display Name in Oracle DRM Server Processes

Windows Services
Control Panel
Description Handles starting and stopping of required server applications in the Oracle DRM environment
Windows Startup Net start Oracle DRM Server Processes

Command
Windows Stop Net stop Oracle DRM Server Processes

Command
UNIX Stop Script: NA
In addition, Oracle Data Relationship Management has a Web tier component that runs in IIS.
FDM
The following table describes the services and processes for FDM.
Table 117 FDM Task Manager Services and Processes
Command Data Quality Management, then Task Manager, and then Task Manager
Registered Service HyS9FDMTaskManagerSrv_instanceName

Name
Display Name in Oracle Hyperion Financial Data Quality Management - Task Manager (instanceName)
Windows Services
Control Panel
Description Provides the ability to schedule Hyperion Financial Data Quality Management tasks
Windows Startup EPM_ORACLE_INSTANCE/bin/startFDMTaskManager.bat

Script
320
Windows Stop Script EPM_ORACLE_INSTANCE/bin/stopFDMTaskManager.bat
UNIX Stop Script NA
In addition, Oracle Hyperion Financial Data Quality Management has a Web tier component
that runs in IIS.
FDMEE Application Server

The following table describes the services and processes for Oracle Hyperion Financial Data
Quality Management, Enterprise Edition.
Table 118 FDMEE Services and Processes
Windows Start Menu Select Start, then Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE_NAME, then FDM
Command Enterprise Edition, and the Start ErpIntegrator
Registered Service HyS9aifWeb_instanceName

Name
Display Name in Oracle Hyperion FDM Enterprise Edition - Java Web Application (instanceName)
Windows Services
Control Panel
Description Provides a Workspace module for ERPI
Windows Startup EPM_ORACLE_INSTANCE/bin/startERPIntegrator.bat

Script
UNIX Startup Script EPM_ORACLE_INSTANCE/bin/startERPIntegrator.sh
Windows Stop Script EPM_ORACLE_INSTANCE/bin/stopERPIntegrator.bat
UNIX Stop Script EPM_ORACLE_INSTANCE/bin/stopERPIntegrator.sh
321
322
Glossary
active-active high availability system A system in which all the Disaster Recovery The ability to safeguard against natural or
available members can service requests, and no member is unplanned outages at a production site by having a recovery
idle. An active-active system generally provides more strategy for applications and data to a geographically
scalability options than an active-passive system. Contrast separate standby site.
with active-passive high availability system.
EPM Oracle home A subdirectory of Middleware home
active-passive high availability system A system with active containing the files required by EPM System products. The
members, which are always servicing requests, and passive EPM Oracle home location is specified during installation
members that are activated only when an active member with EPM System Installer.
fails. Contrast with active-active high availability system.
EPM Oracle instance A directory containing active, dynamic
application server cluster A loosely joined group of components of EPM System products (components that
application servers running simultaneously, working can change during run-time). You define the EPM Oracle
together for reliability and scalability, and appearing to instance directory location during configuration with EPM
users as one application server instance. See also vertical System Configurator.
application cluster and horizontal application cluster.
external authentication Logging on to Oracle EPM System
assemblies Installation files for EPM System products or products with user information stored outside the
components. application. The user account is maintained by the EPM
System, but password administration and user
asymmetric topology An Oracle Fusion Middleware Disaster
authentication are performed by an external service, using
Recovery configuration that is different across tiers on the
a corporate directory such as Oracle Internet Directory
production site and standby site. For example, an
(OID) or Microsoft Active Directory (MSAD).
asymmetric topology can include a standby site with fewer
hosts and instances than the production site. failover The ability to switch automatically to a redundant
standby database, server, or network if the primary
backup A duplicate copy of an application instance.
database, server, or network fails or is shut down. A system
cluster An array of servers or databases that behave as a that is clustered for failover provides high availability and
single resource which share task loads and provide failover fault tolerance through server redundancy and fault-
support; eliminates one server or database as a single point tolerant hardware, such as shared disks.
of failure in a system.
hardware cluster a collection of computers that provides a
cluster interconnect A private link used by a hardware cluster single view of network services (for example, an IP address)
for heartbeat information, to detect node failure. or application services (such as databases and Web servers)
to clients of these services. Each node in a hardware cluster
cluster services Software that manages cluster member
is a standalone server that runs its own processes. These
operations as a system. With cluster services, you can define
processes can communicate with one another to form what
a set of resources and services to monitor through a
looks like a single system that cooperatively provides
heartbeat mechanism between cluster members and to
applications, system resources, and data to users.
move these resources and services to a different cluster
member as efficiently and transparently as possible.
323
high availability A system attribute that enables an migration The process of copying applications, artifacts, or
application to continue to provide services in the presence users from one environment or computer to another; for
of failures. This is achieved through removal of single points example, from a testing environment to a production
of failure, with fault-tolerant hardware, as well as server environment.
clusters; if one server fails, processing requests are routed to
migration log A log file that captures all application migration
another server.
actions and messages.
horizontal application server cluster A cluster with application
migration snapshot A snapshot of an application migration
server instances on different machines.
that is captured in the migration log.
identity A unique identification for a user or group in
native authentication The process of authenticating a user
external authentication.
name and password from within the server or application.
installation assemblies Product installation files that plug in
Oracle home A directory containing the installed files
to EPM System Installer.
required by a specific product, and residing within the
Java web application server cluster An active-active application directory structure of Middleware home. See also
server cluster of Java Virtual Machines (JVMs). Middleware home.
lifecycle management The process of migrating an permission A level of access granted to users and groups for
application, a repository, or individual artifacts across managing data or other users and groups.
product environments.
provisioning The process of granting users and groups
load balancer Hardware or software that directs the requests specific access permissions to resources.
to individual application servers in a cluster and is the only
proxy server A server acting as an intermediary between
point of entry into the system.
workstation users and the Internet to ensure security.
load balancing Distribution of requests across a group of
relational database A type of database that stores data in
servers, which helps to ensure optimal end user
related two-dimensional tables. Contrast with
performance.
multidimensional database.
locale A computer setting that specifies a location's
repository Storage location for metadata, formatting, and
language, currency and date formatting, data sort order, and
annotation information for views and queries.
the character set encoding used on the computer. Essbase
uses only the encoding portion. See also encoding, restore An operation to reload data and structural
ESSLANG. information after a database has been damaged or
destroyed, typically performed after shutting down and
logical address for web applications An aliased reference used
restarting the database.
to identify the internal host name, port, and context of a
Web application. In a clustered or high-availability role The means by which access permissions are granted to
environment, this is the alias name that establishes a single users and groups for resources.
internal reference for the distributed components. In EPM
scalability The ability to resize a system, making it larger or
System, a nonclustered logical address for a web application
smaller. With regard to increases, "scale vertically" or "scale
defaults to the physical host running the web application.
up" refers to expanding a single machine's capability. To
managed server An application server process running in its "scale horizontally" or "scale out" refers to adding more
own Java Virtual Machine (JVM). machines.
Middleware home A directory that includes the Oracle security agent A Web access management provider (for
WebLogic Server home and can also include the EPM Oracle example, Oracle Access Manager, Oracle Single Sign-On, or
home and other Oracle homes. A Middleware home can CA SiteMinder) that protects corporate Web resources.
reside on a local file system or on a remote shared disk that
is accessible through NFS.
324
security platform A framework enabling Oracle EPM System WebLogic Server home A subdirectory of Middleware home
products to use external authentication and single sign-on. containing installed files required by a WebLogic Server
instance. WebLogic Server home is a peer of Oracle homes.
shared disks See shared storage.
Shared Services Registry The part of the Shared Services

repository that manages EPM System deployment
information for most EPM System products, including
installation directories, database settings, computer names,
ports, servers, URLs, and dependent service data.
shared storage A set of disks containing data that must be

available to all nodes of a failover cluster; also called shared
disks.
silent response files Files providing data that an installation

administrator would otherwise be required to provide.
Response files enable EPM System Installer or EPM System
Configurator to run without user intervention or input.
single point of failure Any component in a system that, if it

fails, prevents users from accessing the normal
functionality.
single sign-on (SSO) The ability to log on once and then access
multiple applications without being prompted again for
authentication.
symmetric topology An Oracle Fusion Middleware Disaster

Recovery configuration that is identical across tiers on the
production site and standby site. In a symmetric topology,
the production site and standby site have the identical
number of hosts, load balancers, instances, and
applications. The same ports are used for both sites. The
systems are configured identically and the applications
access the same data.
token An encrypted identification of one valid user or group

on an external authentication system.
upgrade The process of deploying a new software release and

moving applications, data, and provisioning information
from an earlier deployment to the new deployment.
user directory A centralized location for user and group

information, also known as a repository or provider.
Popular user directories include Oracle Internet Directory
(OID), Microsoft Active Directory (MSAD), and Sun Java
System Directory Server.
vertical application server cluster A cluster with multiple

application server instances on the same machine.
325
326

Epm Install

Cargado por

Información del documento

Derechos de autor

Formatos disponibles

Compartir este documento

Compartir o incrustar documentos

Opciones para compartir

¿Le pareció útil este documento?

¿Este contenido es inapropiado?

Copyright:

Formatos disponibles

Epm Install

Cargado por

Copyright:

Formatos disponibles

Oracle Enterprise Performance Management System

Installation and Configuration Guide

Chapter 1. About EPM System Product Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Chapter 2. EPM System Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Chapter 3. Preparing Your Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Chapter 4. Downloading Files for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Chapter 5. Installing EPM System Products in a New Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Chapter 6. Configuring EPM System Products in a New Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Chapter 7. Manually Deploying EPM System Java Web Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Chapter 8. Deploying EPM System Products to WebSphere Application Server . . . . . . . . . . . . . . . . . . . . . . . 169

Chapter 9. Performing Manual Configuration Tasks in a New Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Chapter 11. Upgrading EPM System Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

Chapter 12. Starting and Stopping EPM System Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

Chapter 13. Validating the Installation and Verifying Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269

Appendix A. Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279

Appendix B. JDBC URL Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293

Appendix C. Database Information for Financial Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295

Access to Oracle Support

Send feedback on this documentation to: epmdoc_ww@oracle.com

About EPM System Products

EPM Oracle Home

EPM Oracle Instance

About the Shared Services Registry

Characters Supported for Installation and

Table 1 Characters Supported for Installation and Configuration

Fields Supported Characters Blocked Characters

Host name Alphanumeric, dash (-), and dot(.). All others

User name Alphanumeric characters including non-English (extended +*/#[]{}();:,@!

Clusters, database Alphanumeric characters including non-English (extended +.-*\/#[]{}();:,@!

About EPM System Architecture

Disclosure Management Components

Stand-Alone Financial Close Management Deployment

Table 2 Financial Close Management Deployment Specifications

Machine Products Processor/

Server 1 l WebLogic Admin Server 4 Core 2 CPU

Strategic Finance Components

Table 3 Strategic Finance Deployment Specifications

Machine Products Processor/Memory

Applying Windows Updates

Resolving Port Conflicts

Disabling User Access Control

To set the authentication level for DCOM to Connect:

Note: For earlier Windows versions, set the value to None.

Resolving Host Names

Disabling Anti-virus Software

Preparing User Accounts

Disk Space and RAM

Client Disk Space and RAM

Product Family Component Disk Space (Minimum)1 Notes

Foundation Services Common client components 400 MB

Smart View for Office 100 MB

Performance Management 20 MB File generator and batch client

Essbase Essbase Runtime Client 150 MB

Administration Services Console 300 MB

Integration Services Console 90 MB

Essbase Studio Console 80 MB

Reporting and Analysis Oracle Hyperion Financial Reporting 400 MB

Oracle Hyperion Interactive 700 MB

Oracle Hyperion Dashboard 190 MB

Oracle Hyperion SQR Production 90 MB

Oracle Hyperion SQR Production 30 MB

Production Reporting Remote 10 MB

Production Reporting Viewer 40 MB

Oracle Hyperion Web Analysis 40 MB