oracle® enterprise performance management...

Oracle® Enterprise Performance Management System

Installation and Configuration Guide

Release 11.1.2.3

Updated: November 2013

EPM System Installation and Configuration Guide, 11.1.2.3

Copyright © 2008, 2013, Oracle and/or its affiliates. All rights reserved.

Authors: EPM Information Development Team

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respectiveowners.

This software and related documentation are provided under a license agreement containing restrictions on use anddisclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement orallowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit,perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilationof this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you findany 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 ofthe U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS:

Programs, software, databases, and related documentation and technical data delivered to U.S. Government customersare "commercial computer software" or "commercial technical data" pursuant to the applicable Federal AcquisitionRegulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, andadaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, tothe extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, CommercialComputer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software or hardware is developed for general use in a variety of information management applications. It is notdeveloped or intended for use in any inherently dangerous applications, including applications that may create a risk ofpersonal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take allappropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliatesdisclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

This software or hardware and documentation may provide access to or information on content, products, and servicesfrom third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of anykind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsiblefor any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Documentation Accessibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

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

About EPM System Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Assumed Knowledge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

About Middleware Home, EPM Oracle Home, and EPM Oracle Instance . . . . . . . . . . . . . 17

About the Shared Services Registry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Characters Supported for Installation and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 18

Chapter 2. EPM System Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

About EPM System Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Disclosure Management Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Essbase Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

FDM Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

FDMEE Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Financial Close Management Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Stand-Alone Financial Close Management Deployment Requirements for Test andProduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Financial Management Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Performance Management Architect Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Planning Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Profitability and Cost Management Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Reporting and Analysis Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Strategic Finance Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Stand-AloneStrategic Finance Deployment Requirements for Test and Production . . . 31

Chapter 3. Preparing Your Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Preparing Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Applying Windows Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Resolving Port Conflicts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Disabling User Access Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Setting the DCOM Default Authentication Level (Windows 2008) . . . . . . . . . . . . . . . 34

Synchronizing Clocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Resolving Host Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Disabling Anti-virus Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Shared File System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Preparing User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Disk Space and RAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Client Disk Space and RAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Server Disk Space and RAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Contents iii

Preparing a Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Using an Oracle Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Using a Microsoft SQL Server Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Using an IBM DB2 Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Preparing Java Web Application Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

WebLogic Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

IBM WebSphere . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Preparing Web Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Oracle HTTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Microsoft Internet Information Services (IIS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Preparing Web Browsers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Browser Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Enabling ActiveX (Reporting and Analysis) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Support Matrix for High Availability and Load Balancing . . . . . . . . . . . . . . . . . . . . . . . . 54

Chapter 4. Downloading Files for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Downloading the Installation Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

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

Installation Checklist for a New Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Deploying to a Shared Drive Environment (UNIX) . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Financial Close Management (Close Manager and Account Reconciliation Manager)Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Installation Prerequisites and Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Web Server Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Configuring X11 for Financial Reporting and Production Reporting (AIX and HP-UX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Installation Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Installing EPM System Products in a Distributed Environment . . . . . . . . . . . . . . . . . . . . 79

Integrating Oracle BI EE with EPM System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Installing EPM System Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Welcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Destination/Middleware Home . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Installation Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Product Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Performing Silent Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Loading Saved Selections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Modifying Response Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Installing EPM System Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

iv Contents

Client Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Downloading and Extracting Client Installers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Installing Individual EPM System Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Installing EPM System Clients from EPM Workspace . . . . . . . . . . . . . . . . . . . . . . . . 93

Installing EPM System Clients From EPM System Installer . . . . . . . . . . . . . . . . . . . . 94

Installing Multiple Versions of Financial Reporting Studio on a Client Machine . . . . . 94

Performing Silent Client Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Default Installation Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

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

About EPM System Configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Configuration Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Ensuring that Host Names Resolve . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Creating Infrastructure Schemas Using Repository Creation Utility . . . . . . . . . . . . . . 99

Configuration Prerequisites for Financial Close Management . . . . . . . . . . . . . . . . . 101

Configuration Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Configuring Products in a Distributed Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Configuring Products in an SSL-Enabled Environment . . . . . . . . . . . . . . . . . . . . . . . . . 105

Configuring Products for Manual Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Configuring Products for WebSphere Application Server . . . . . . . . . . . . . . . . . . . . . . . . 106

Product Configuration Task Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Configuring EPM System Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Refreshing EPM Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

EPM System Configurator Task Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Configure Oracle Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Task Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Configure Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Deploy to Application Server — Specify WebLogic Domain Information . . . . . . . . . 118

Deploy to Application Server: Oracle WebLogic . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Foundation Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Performance Management Architect Configuration Tasks . . . . . . . . . . . . . . . . . . . 130

Essbase Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Reporting and Analysis ConfigurationTasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Planning Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Financial Management Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Performance Scorecard — Configure Attachment Files Location . . . . . . . . . . . . . . . 145

Strategic Finance Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Financial Close Management Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . 146

FDMEE Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Contents v

FDM Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Performing Silent Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Setting Up Essbase in Standalone Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Deploying Financial Management, Financial Reporting, and Web Analysis on Windows ina UNIX-Based EPM System Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

What Happens During Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Troubleshooting Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

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

Assumptions and Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Manually Deploying Java Web Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Additional Postdeployment Steps for FDMEE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Configuring JMS Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Extending a Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Manually Configuring Oracle HTTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

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

Additional Postdeployment Steps for FDMEE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Configuring IBM HTTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Validating WebSphere Application Server Deployments . . . . . . . . . . . . . . . . . . . . . . . . 173

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

Essbase Manual Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Setting User Limits on 64-bit AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

Enabling Client Lookup by Cluster Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

Reporting and Analysis Manual Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . 176

Financial Close Management Manual Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . 177

Setting Up the Keystore for Message Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Configuring the WebLogic Domain to OID, MSAD, SunOne . . . . . . . . . . . . . . . . . . 180

Start Managed Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Raising the Maximum Capacity in the Connection Pool . . . . . . . . . . . . . . . . . . . . . 181

Increasing the Connection Pool of the External LDAP Provider . . . . . . . . . . . . . . . . 182

FDMEE Manual Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Chapter 10. Performing a Maintenance Release Installation for EPM System Products . . . . . . . . . . . . . . . . . 185

Maintenance Release Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Financial Close Management Maintenance Release Installation Checklist . . . . . . . . . . . . 186

Downloading and Extracting Installation Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

Performing Maintenance Release Installation Prerequisite Tasks . . . . . . . . . . . . . . . . . . 188

Essbase Maintenance Release Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . 189

Business Rules Maintenance Release and Upgrade Installation Prerequisites . . . . . . . 190

vi Contents

Financial Reporting Maintenance Release Installation Prerequisites . . . . . . . . . . . . . 191

Maintenance Release Installation Prerequisites if You Are Using Oracle Web ServicesManager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

Installing and Configuring EPM System Products in a Maintenance Installation . . . . . . . 192

Maintenance Installation Deployments to a Single Managed Server . . . . . . . . . . . . . . . . 195

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

Scenario 2: You were working in a Release 11.1.2.1 or Release 11.1.2.2 environment thathad some Java web applications deployed to a single managed server and some Java webapplications deployed to their own managed servers . . . . . . . . . . . . . . . . . . . . . . . . 197

Performing Manual Configuration Tasks in a Maintenance Installation . . . . . . . . . . . . . 198

General Manual Configuration Tasks in a Maintenance Installation . . . . . . . . . . . . . 198

EPM Workspace Manual Configuration Tasks in a Maintenance Installation . . . . . . 198

Performance Management Architect Manual Configuration Tasks in a MaintenanceInstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

Essbase Manual Configuration Tasks in a Maintenance Installation . . . . . . . . . . . . . 199

Essbase Studio Manual Configuration Tasks in a Maintenance Installation . . . . . . . . 200

Planning Manual Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

Profitability and Cost Management Manual Configuration Tasks . . . . . . . . . . . . . . . 202

Strategic Finance Manual Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

FDM Manual Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

Maintenance Installation Deployments to WebSphere Application Server . . . . . . . . . 203

Validating the Deployment and Generating a Deployment Report . . . . . . . . . . . . . . . . . 203

Performing a Maintenance Release Installation for EPM System Clients . . . . . . . . . . . . . 204

Chapter 11. Upgrading EPM System Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

About Upgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

Supported Upgrade Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

Upgrading Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

Upgrade Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

Backing Up the Earlier Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

Performing Product-Specific Upgrade Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . 210

Business Rules Maintenance Release and Upgrade Installation Prerequisites . . . . . . . 211

Downloading and Preparing Files for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212

Preparing Data for Upgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

Exporting Shared Services Data from the Earlier Release . . . . . . . . . . . . . . . . . . . . . 213

Exporting Financial Management and Strategic Finance Data from the EarlierRelease . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214

Copying Files for Temporary Use During Configuration . . . . . . . . . . . . . . . . . . . . . 215

Replicating Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

Contents vii

Replicating the Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224

Stopping EPM System Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224

Uninstalling the Earlier Release of EPM System Products . . . . . . . . . . . . . . . . . . . . . . . . 225

Installing EPM System Products for an Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

Configuring EPM System Products in an Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226

What Happens During Shared Services Data Import . . . . . . . . . . . . . . . . . . . . . . . . 231

Upgrading a Distributed Deployment of Reporting and Analysis . . . . . . . . . . . . . . . 232

Starting EPM System Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

Validating the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

Performing Manual Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

Updating References to a Rehosted Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234

Updating References to a Rehosted Essbase Server . . . . . . . . . . . . . . . . . . . . . . . . . 234

Updating Provider Services References to a Rehosted Essbase Server . . . . . . . . . . . . . 236

Updating Administration Services References to a Rehosted Essbase Server or ProviderServices Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

Updating Essbase Studio References to a Rehosted Environment . . . . . . . . . . . . . . . 238

Updating Reporting and Analysis References to a Rehosted Server Environment . . . . 241

Updating Performance Management Architect References to a Rehosted ServerEnvironment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

Updating Planning References to a Rehosted Server Environment and UpgradingApplications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

Updating Profitability and Cost Management References to a Rehosted EssbaseServer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

Updating Strategic Finance References to a Rehosted Essbase Server or FinancialManagement Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

Updating Performance Scorecard References to a Rehosted Essbase Server . . . . . . . . 247

Updating Integration Services References to a Rehosted Server Environment . . . . . . 247

Upgrading Applications from the Earlier Release to the Current Release . . . . . . . . . . . . . 248

Performing Manual Configuration Tasks in an Upgrade . . . . . . . . . . . . . . . . . . . . . . . . 249

Performance Management Architect Upgrade Tasks . . . . . . . . . . . . . . . . . . . . . . . . 249

Essbase Upgrade Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

Essbase Studio Upgrade Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251

Reporting and Analysis Upgrade Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252

Planning Upgrade Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254

Financial Management Upgrade Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255

Strategic Finance Upgrade Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256

FDMEE Upgrade Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257

FDM Upgrade Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258

Upgrading Smart View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258

Upgrading from an Environment with Multiple Releases . . . . . . . . . . . . . . . . . . . . . . . . 259

viii Contents

Upgrading From an Environment with a Single Instance of Shared Services . . . . . . . 259

Upgrading From an Environment with Two Instances of Shared Services . . . . . . . . . 259

Repeating the Upgrade Process for Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260

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

Using a Single Script to Start Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

Launching Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262

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

Validating the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265

Using EPM System Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265

Diagnostics Performed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266

Generating a Deployment Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267

Verifying Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268

Verifying Shared Services Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268

Verifying EPM Workspace Deployment and Products in EPM Workspace . . . . . . . . 268

Additional Verification for Financial Close Management . . . . . . . . . . . . . . . . . . . . . 269

Verifying Administration Services Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270

Verifying Provider Services Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270

Validating a Financial Close Management Deployment . . . . . . . . . . . . . . . . . . . . . . . . . 270

Appendix A. Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275

Default Ports and Shared Services Registry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275

WebLogic Administration Server Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276

WebSphere Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276

WebSphere Application Server Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276

IBM HTTP Server Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276

Oracle Enterprise Manager Java Web Application Port . . . . . . . . . . . . . . . . . . . . . . . . . 277

SOA Server Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

SSL Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

Foundation Services Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

Foundation Services Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

Performance Management Architect Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278

Calculation Manager Java Web Application Ports . . . . . . . . . . . . . . . . . . . . . . . . . . 278

Essbase Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279

Essbase Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279

Administration Services Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280

Provider Services Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280

Essbase Studio Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280

Contents ix

Reporting and Analysis Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280

Reporting and Analysis Framework Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281

Financial Reporting Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281

Interactive Reporting Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282

Web Analysis Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282

Financial Performance Management Applications Ports . . . . . . . . . . . . . . . . . . . . . . . . 282

Financial Management Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283

Financial Close Management Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283

Planning Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284

Performance Scorecard Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284

Strategic Finance Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285

Profitability and Cost Management Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285

Disclosure Management Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285

Data Management Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285

FDM Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286

FDMEE Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286

Data Relationship Management Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287

Appendix B. JDBC URL Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289

JDBC Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289

URL for Oracle RAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290

LDAP-Based URL for Oracle Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290

URL for SSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290

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

Database Connection Pooling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291

Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292

Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293

Appendix D. EPM System Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295

EPM System Services and Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296

Web Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296

Foundation Services Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297

Performance Management Architect Dimension Server Services . . . . . . . . . . . . . . . 298

Performance Management Architect Application Server . . . . . . . . . . . . . . . . . . . . . 299

Performance Management Architect Data Synchronizer Application Server . . . . . . . 299

Calculation Manager Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300

Essbase Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301

Administration Services Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302

Integration Services Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303

x Contents

Essbase Studio Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304

Provider Services Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305

Hyperion Reporting and Analysis Framework - Agent Service . . . . . . . . . . . . . . . . . 306

Reporting and Analysis Framework Application Server . . . . . . . . . . . . . . . . . . . . . . 306

Financial Reporting Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307

Web Analysis Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308

Planning Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308

Financial Management Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309

Financial Management Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310

Strategic Finance Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311

Strategic Finance Web Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312

Performance Scorecard Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312

Performance Scorecard Alerter Application Server . . . . . . . . . . . . . . . . . . . . . . . . . 313

Profitability and Cost Management Application Server . . . . . . . . . . . . . . . . . . . . . . 313

Disclosure Management Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314

Financial Close Management Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 314

Data Relationship Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316

FDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316

FDMEE Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323

Contents xi

xii Contents

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website athttp://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle SupportOracle customers 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

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs

14 Documentation Accessibility

1About EPM System Product

Installations

In This Chapter

About EPM System Products.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

Assumed Knowledge... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

About Middleware Home, EPM Oracle Home, and EPM Oracle Instance ... . . . . . . . . . . . . . . . . . . . . . . . . . .17

About the Shared Services Registry .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

Characters Supported for Installation and Configuration... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

About EPM System ProductsCheck 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 isavailable.

Oracle Enterprise Performance Management System products form a comprehensive EnterprisePerformance Management system that integrates modular suites of financial managementapplications with the most comprehensive business intelligence capabilities for reporting andanalysis. Major components of EPM System products:

l Oracle Hyperion Foundation Services

m Foundation Services (includes Oracle Hyperion Shared Services and Oracle HyperionEnterprise Performance Management Workspace)

m Optionally, Oracle HTTP Server

m Oracle WebLogic Server

m Oracle Hyperion EPM Architect

m Oracle Hyperion Calculation Manager

m Oracle Hyperion 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

About EPM System Products 15

http://www.oracle.com/technology/documentation/epm.html



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, OracleHyperion Workforce Planning, and Oracle Hyperion Public Sector Planning andBudgeting)

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 KnowledgeThis guide is for administrators who install, configure, and manage EPM System products. Itassumes 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, includingauthentication providers such as Oracle Internet Directory, LDAP, or Microsoft ActiveDirectory, 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

16 About EPM System Product Installations

About Middleware Home, EPM Oracle Home, and EPMOracle Instance

Middleware Home

A Middleware home consists of the Oracle WebLogic Server home, and, optionally, one or moreOracle homes, including EPM Oracle home. A Middleware home can reside on a local file systemor 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 defaultinstallation directory is Oracle/Middleware. The Middleware home location is referred to asMIDDLEWARE_HOME throughout this document.

EPM Oracle Home

An Oracle home contains installed files necessary to host a specific product, and resides withinthe directory structure of the Middleware home. The EPM Oracle home contains files for EPMSystem products.

Components of EPM System products are installed in the EPM Oracle home directory underthe Middleware home. The default EPM Oracle home location is MIDDLEWARE_HOME/EPMSystem11R1. In addition, common internal components used by the products are installedin EPM Oracle home. Choose the location carefully to ensure that the location has enough diskspace 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 calledEPM_ORACLE_HOME. The EPM Oracle home location is referred to as EPM_ORACLE_HOMEthroughout this document.

In a distributed environment, the EPM Oracle home directory structure must be the same oneach 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. Thedirectory structure of an Oracle instance is separate from the directory structure of the Oraclehome. 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_INSTANCEthroughout 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 youconfigure, you create a new EPM Oracle instance. For each product after that, you modify theexisting EPM Oracle instance. If you are installing in a distributed environment, create a newEPM Oracle instance on each machine.

About Middleware Home, EPM Oracle Home, and EPM Oracle Instance 17

In a UNIX environment, you can deploy to a shared drive by installing to a shared drive andthen configuring each machine to deploy to a different EPM Oracle instance. See “Deploying toa Shared Drive Environment (UNIX)” on page 68.

About the Shared Services RegistryThe Oracle Hyperion Shared Services Registry is part of the database that you configure forFoundation Services. Created the first time that you configure EPM System products, the SharedServices Registry simplifies configuration by storing and reusing the following information formost 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 otherproducts used in the deployment.

You can view and manage the contents of the Shared Services Registry using LifecycleManagement in the Oracle Hyperion Shared Services Console. See the Oracle EnterprisePerformance Management System Lifecycle Management Guide.

Characters Supported for Installation andConfigurationThe following characters are supported during installation and configuration with OracleHyperion Enterprise Performance Management System Installer and Oracle HyperionEnterprise Performance Management System Configurator.

Table 1 Characters Supported for Installation and Configuration

Fields Supported Characters Blocked Characters

PATH Alphanumeric, dash (-), underscores (_), periods ( . ), andtildes (~). Tildes are supported only on Microsoft Windows.

All others

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

EPM System supports IPv6 addresses. However, duringinstallation and configuration, you must enter the hostname, not the IPv6 address.

All others

User name Alphanumeric characters including non-English (extendedand double-byte) characters, except for the blockedcharacters

+ * / # [ ] { } ( ) ; : , @ ! “


Fields Supported Characters Blocked Characters

Clusters, databasenames, and othergeneral fields such asDSN names

Alphanumeric characters including non-English (extendedand double-byte) characters, except for the blockedcharacters

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

MIDDLEWARE_HOME, EPM_ORACLE_HOME andEPM_ORACLE_INSTANCE

For MIDDLEWARE_HOME: Alphanumeric characters, "_","-" and "~" on Windows.

For EPM_ORACLE_INSTANCE: Alphanumeric characters,"_", "-" The first character in every folder in the EPM_ORACLE_INSTANCE path must be a-z, A-Z, or 0-9.

Do not use any of the following symbols or symbolcombinations in the directory that you specify forEPM_ORACLE_HOME or MIDDLEWARE_HOMEduring installation or EPM_ORACLE_INSTANCEduring configuration:

/t

\t

\b

.

Characters Supported for Installation and Configuration 19

2EPM System Architecture

In This Chapter

About EPM System Architecture ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21

Disclosure Management Components ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

Essbase Components.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

FDM Components ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

FDMEE Components .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

Financial Close Management Components... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

Financial Management Components... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26

Performance Management Architect Components.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27

Planning Components .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28

Profitability and Cost Management Components ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

Reporting and Analysis Components.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30

Strategic Finance Components ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30

About EPM System ArchitectureEPM System is a multi-tier application environment that mainly utilizes thin-client architecturefor end-user access, requiring only a supported browser on the client machine. Network trafficbetween the client and middle-tier server(s) generally does not exceed more than normal Webtraffic.

A middle-tier application server is required. WebLogic Server is provided with a defaultinstallation. You can also use another supported application server. See the Oracle EnterprisePerformance Management System Certification Matrix (http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html) for a list of supported applicationservers.

The data tier is comprised of two components that store data differently. In Essbaseenvironments, the data is stored and calculated in the database on the server file system. InFinancial Management environments, the application framework, metadata, and textual dataare stored in a relational repository.

The following sections contain diagrams that illustrate the component architecture for EPMSystem products. To obtain information about the communication between EPM Systemcomponents, 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.

About EPM System Architecture 21

http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html


http://www.oracle.com/technology/documentation/epm.htm


Note: The Oracle Enterprise Performance Management System Standard Deployment Guidepresents Oracle’s best-practice approach for deploying EPM System products. Thisapproach is based on creating a base deployment of the products and then scaling out theservices to handle the needed capacity. This document is available in the EPM System11.1.2.3 Documentation Library (Deployment and Installation tab) at http://www.oracle.com/technology/documentation/epm.html.

Tip: For optimum viewing of the component architecture diagrams in PDF format, tryincreasing the view magnification to 120%.

Disclosure Management Components

22 EPM System Architecture



Essbase Components

Essbase Components 23

FDM Components

FDMEE Components


Financial Close Management Components

Stand-Alone Financial Close Management DeploymentRequirements for Test and ProductionA stand-alone version of Financial Close Management can be deployed independently of otherEPM System products in a two-server deployment as specified below. The following specificationsupports 500 users (175 active).

Table 2 Financial Close Management Deployment Specifications

Machine Products Processor/Memory

Server 1l WebLogic Admin Server

l Foundation Services Java Web application (EPM Workspace and Shared Services)

l Oracle SOA Suite

l Oracle HTTP Server

4 Core 2 CPU –16GB

Server 2l Financial Close Management Java Web application (Close Manager and Account Reconciliation

Manager)

l FDMEE Java Web application

4 Core 2 CPU –16GB

Financial Close Management Components 25

Financial Management Components


Performance Management Architect Components

Performance Management Architect Components 27

Planning Components


Profitability and Cost Management Components

Profitability and Cost Management Components 29

Reporting and Analysis Components

Strategic Finance Components


Stand-AloneStrategic Finance Deployment Requirements forTest and ProductionA stand-alone version of Strategic Finance can be deployed independently of other EPM Systemproducts in a one-server deployment as specified below. The following specification supports50 active users.

Table 3 Strategic Finance Deployment Specifications

Machine Products Processor/Memory

Server 1l Shared Services Java Web application

l Strategic Finance Web application

l Strategic Finance Server


4 Core 2 CPU – 16GB on Windows 2008 R2

Strategic Finance Components 31

3Preparing Your Environment

In This Chapter

Preparing Servers .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33

Preparing User Accounts .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

Disk Space and RAM .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36

Preparing a Database ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39

Preparing Java Web Application Servers.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49

Preparing Web Servers .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50

Preparing Web Browsers .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52

Support Matrix for High Availability and Load Balancing... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54

Preparing Servers

Applying Windows UpdatesFor each server in the deployment, apply Windows updates and reboot before installing andconfiguring.

Resolving Port ConflictsFor information about default port numbers for EPM System products, including where theport can be configured, see Appendix A, “ Ports.”.

Disabling User Access ControlIn Windows 2008 environments, disable User Access Control (UAC) on each server in thedeployment. This can be done through User Accounts in the Control Panel by clicking on ChangeUser 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.

Preparing Servers 33

Setting the DCOM Default Authentication Level (Windows2008)For machines hosting products that require .NET Framework 4.0, the DCOM defaultauthentication 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 ClocksThe clock on each server must be synchronized to within one second difference. To accomplishthis, point each server to the same network time server. Refer to your operating systemdocumentation for more information.

Resolving Host NamesThe canonical host name of each server must be the same when accessed from within the serverand from other servers in the deployment. You may want to create a local hosts file on eachserver to resolve host name issues.

EPM System uses Java’s canonical host name resolution for resolving host names. To validatehost 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 SoftwareAntivirus software can cause performance issues with EPM System products if, each time youaccess any resource on the server, the antivirus software tries to open and scan the object. Toprevent these issues, exclude the EPM Oracle home directory from automatic antivirus scansand scan this directory only at scheduled times.

34 Preparing Your Environment

Shared File SystemIf you are configuring for high availability, you must set up a shared file system using UNCsyntax that is accessible from all the servers in the deployment for the following:

l Oracle Hyperion Enterprise Performance Management System Lifecycle Managementartifacts

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 distributedenvironment

l Strategic Finance data

l FDMEE application data

l Essbase Studio sample and customer data source text files

Preparing User AccountsWindows:

l Do not use the Administrator user to install and configure. Run EPM System Installer andEPM System Configurator as a user with administrator rights. Install and configure as anadministrator 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 aservice.”

l Before installing in a Windows 2008 environment, ensure that you disable User AccountControl (UAC). See “Disabling User Access Control ” on page 33.

l When you upgrade, apply a maintenance release, or patch this server, use the same useraccount 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 EPMSystem products. On UNIX machines, for all Oracle products, the user that is installing mustbe 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 Systemproducts must be in the same group as the user who installed the other Oracle products. Forexample, both users must be part of oinstall. If you are upgrading EPM System products,

Preparing User Accounts 35

follow this requirement even if you used multiple users to install components in previousreleases.

The password for the account used to install and configure must conform to the followingguidelines:

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

Client Disk Space and RAMDisk space and RAM requirements are approximate. The installation program checks for twicethe 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 EPMSystem product assemblies

16 GB After installation, the installationfiles and assemblies can beremoved.

Foundation Services Common client components 400 MB

Smart View for Office 100 MB

Performance ManagementArchitect

20 MB File generator and batch clientcomponents 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 ReportingStudio

400 MB


Product Family Component Disk Space (Minimum)1 Notes

Oracle Hyperion InteractiveReporting Studio

700 MB

Oracle Hyperion DashboardDevelopment Services

190 MB

Oracle Hyperion SQR ProductionReporting Studio

90 MB

Oracle Hyperion SQR ProductionReporting Activator

30 MB

Production Reporting Remote 10 MB

Production Reporting Viewer 40 MB

Oracle Hyperion Web AnalysisStudio

40 MB

Financial PerformanceManagement Applications

Offline Planning 280 MB

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 RAMDisk space and RAM requirements are approximate and do not include additional possiblerequirements on the machine. The installation program checks for twice the required disk space,based on your product installation choices. Disk space estimates include documentation helpfiles (if applicable) and EPM System components.

Component Disk Space (Minimum) RAM (Minimum)

WebLogic Server

(includes WebLogic, JDK, utils,JRockit, and Modules)

1.4 GB 500 MB

Oracle HTTP Server (optionalcomponent)

1.2 GB 1 GB

Common Oracle libraries 900 MB NA

Shared Services 800 MB1 1.5 GB

Disk Space and RAM 37


Performance ManagementArchitect

125 MB 1 GB for Dimension Server

512 MB each for Web Tier and Data Synchronizer

Calculation Manager 45 MB 256 MB

Essbase Server 2 GB 1 GB

Application ProgrammingInterface

40 MB 256 MB

Administration Services 1 GB2 32 MB multiplied by the number of concurrentAdministration 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 AnalysisFramework

2 GB

For services: 400 MB

For importing files: 2 GB

1 GB

For services: 1 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 FinancialManagement

24 GB 4 GB

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 CostManagement

8 GB 2 GB

Disclosure Management 8 GB 4 GB

FDM Database Serverl Dependent on size of the FDM application

l Multiple HDDs to spread processing

1 GB per 75 concurrent users (2 GB minimum)

FDM folder structure Dependent on size of the FDM application NA



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 ManagementDatabase Server

15 GB 2 GB

Data Relationship ManagementApplication Server

500 MB 2 GB

1This number is for the base Shared Services installation. If using Lifecycle Management functionality, Oracle recommends that you significantlyincrease 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 backgroundtask logs, such as consolidation reports.

Note: For data storage and binary installation, Essbase supports the use of a disk array device.

Preparing a DatabaseBefore you install and configure most EPM System products, create a database using a supportedRDBMS (Oracle Database, Microsoft SQL Server, or IBM DB2).

EPM System supports 32-bit as well as 64-bit versions of all supported databases; however, theversion of the database should match the operating system. For example, a 64-bit databaseversion 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. Toprevent timeout issues when configuring with EPM System Configurator, you cannot locate adatabase in a remote location where there is latency.

For simplicity and ease of deployment, you can use one database repository for all products (withthe exceptions noted below). In some cases you might want to configure separate databases forproducts. Consider performance, rollback procedures for a single application or product, anddisaster 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 ManagementInstallation Guide.

Preparing a Database 39

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 DatabaseThis section includes information about Oracle database installation, database creation, requiredroles and privileges, sizing guidelines, and configuration.

Note: EPM System Installer installs the Oracle Database client automatically if it is required ona machine (Windows only). To use an existing Oracle Database client, see “Using anExisting Oracle Database Client” on page 43.

Oracle Database Creation ConsiderationsThe 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 PrivilegesThe 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


Oracle Database Sizing GuidelinesOracle recommends that you set tablespaces with Auto Extend ON.

The following table describes the Oracle Database sizing guidelines.

Product Sizing Guideline

Shared Services &EPM Workspace

Start with 100 MB, and add more as the number of migrations with Lifecycle Management and the number of auditrecords increases.

PerformanceManagementArchitect

Oracle recommends starting with at least 250MB.

AdministrationServices

The amount of space needed depends on the metadata created; Oracle recommends starting with at least 32 MB.

Essbase Studio The amount of space needed depends on the metadata created; Oracle recommends starting with at least 32 MB.

Reporting andAnalysis

The amount of 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 Reporting and Analysisrepository without having to increase the data file or tablespace. A shared pool size of 60 MB is used duringconfiguration with EPM System Configurator.

Planning andCalculation Manager

l 100 MB for applications with 5,000 or fewer total members


Note: You can adjust the size of the system table database to match the size of the application.

FinancialManagement andCalculation Manager




PerformanceScorecard

500 MB


Oracle recommends starting with at least 250 MB.

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.


Product Tablespace Considerations

General—Allproducts

l Consider a global view of tablespaces and allocate one or more tablespaces in order to spread out tables createdby 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 systemprivileges.

l Ensure that the SEGMENT SPACE MANAGEMENT parameter is set to AUTO when you create tablespace, to improveperformance.


Dedicate a tablespace to Reporting and Analysis. Determine the tablespaces to be used as the default tablespaceand the temporary tablespace for this user. Do not use the SYSTEM tablespace.

FinancialManagement

Set up a temporary tablespace greater than 1GB.


DataRelationshipManagement

l Set the initial tablespace size to 1 GB

l Extents to 500 MB

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


Enabling Statement Caching for Financial ManagementIf you use Oracle Database Client 10.2.x or 11.1.x for Financial Management, you must set theStmtCacheSize registry setting for Oracle OLE DB to 10 on all Financial Managementapplication 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, theOracle OLE provider on all Financial Management servers must be at least 10.2.0.4.21+. If youare using 32-bit with 10g, the OLE provider must be at least as high a version as your databaseserver. If you are running 32-bit or 64-bit and using 11.1.0.6 or 11.1.0.7 OLE Provider, you mustupgrade to Oracle Database Client 11.1.0.7.33+.

Using an Existing Oracle Database ClientFor a new installation, if you want to use your existing Oracle Database Client instead of the oneinstalled with EPM System, during EPM System installation clear the selection from OracleDatabase Client 32-bit and Oracle Database Client 64-bit under Foundation Services. Then, afterinstalling and configuring Oracle EPM System, perform the following steps:

1. On the machine hosting Foundation Services, update the TNS_ADMIN environment variableto 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 existingtnsnames.ora file. Copy the entire file contents and append to the existing contents of thetnsnames.ora file.

Replacing the EPM System-Installed Oracle Database Client with A Different OracleDatabase Client

If you want to use your existing Oracle Database Client instead of the one installed with EPMSystem, and you already installed the Oracle Database Client during installation of EPM System,


then, after installing and configuring Oracle EPM System, perform the following steps. Thisprocedure applies to new installations or maintenance installations.

1. On the machine hosting Foundation Services, update the TNS_ADMIN environment variableto 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 appendto the existing contents of your tnsnames.ora file.

3. Remove the following EPM System embedded Oracle Database Client BIN paths from thePATH environment variable in order to avoid conflicts:

<MIDDLEWARE_HOME>\dbclient32\BIN;<MIDDLEWARE_HOME>\dbclient64\BIN;

Using a Microsoft SQL Server DatabaseThis section includes information about SQL Server database creation, required roles andprivileges, and sizing guidelines.

Microsoft SQL Server Database Creation RequirementsWhen creating a Microsoft SQL Server database for use as a repository, ensure that you set theseoptions:

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 securityproperties for the database.

l All products support Latin Collation for the SQL Server database. Create a database that iscase insensitive and use this statement: SQL_Latin1_General_CP1_CI_AS.

Microsoft SQL Server Roles and PrivilegesDatabase 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 readaccess to the FDM Data folder.

Microsoft SQL Server Sizing GuidelinesThe following table describes the Microsoft SQL Server sizing guidelines.



Shared Services Start with 100 MB, and add more as the number of migrations with Lifecycle Management and the number ofaudit records increases.

EPM Workspace The space needed depends on the aggregate size of the objects that you plan to store in the repository. Oraclerecommends starting with at least 250 MB, which provides space to expand the EPM Workspace repository withouthaving to increase the data file or tablespace. A shared pool size of 60 MB is used during configuration with EPMSystem Configurator.




The space needed depends on the metadata created; Oracle recommends starting with at least 32 MB.

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










500 MB



Data RelationshipManagement

l Set the initial file size to 1 GB

l Turn on Auto Growth and set to 10%


Using an IBM DB2 DatabaseThis section includes information about IBM DB2 database installation, database creation,required roles and privileges, sizing guidelines, and configuration.

IBM DB2 Installation InformationDuring 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 adifferent computer, and not on the Dimension Server machine where the DB2 9 RuntimeClient and DB2 .NET Data Provider must be installed.


Note: If DB2 9 Runtime Client is installed on the Performance Management Architectcomputer, verify that an entry exists in the Global Assembly Cache.

l If you use an IBM DB2 database for Financial Management, DB2 Runtime Client andDB2 .NET Data Provider must be installed on the same machine as the FinancialManagement Application Server.

l For Reporting and Analysis, ensure that the IBM DB2 Client Application Enabler is installedon 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 separatemachines, use the Client Application Enabler to create a client connection to the Reportingand Analysis database.

IBM DB2 Database Creation ConsiderationsFor the best compatibility with non-ASCII character sets, an IBM DB2 database must be createdusing Unicode Transformation Format UTF-8 encoding (character set). Use of UTF-8 isrequired if you need multilingual support (multicharacter set support).

Use the Client Configuration Assistant to set up a database alias that enables the EPM Systemproduct to connect to the database. Be sure to select “Register this Database for ODBC and Asa System Data Source.”

IBM DB2 Roles and PrivilegesDatabase users must be assigned the following privileges:

l CREATETAB

l BINDADD

l CONNECT

IBM DB2 Sizing GuidelinesThe 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 ofaudit records increases.

EPM Workspace The space needed depends on the aggregate size of the objects that you plan to store in the repository. Oraclerecommends starting with at least 250 MB, which provides space to expand the EPM Workspace repository withouthaving to increase the data file or tablespace. A shared pool size of 60 MB is used during configuration with EPMSystem Configurator.




The space needed depends on the metadata created; Oracle recommends starting with at least 32 MB.



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










500 MB

IBM DB2 Database Configuration ConsiderationsThe following table describes IBM DB2 database configuration considerations.


General—Allproducts

Tablespace requirements:

Specify automatic storage for user and temporary tablespaces, as shown in the following example:

CREATE TABLESPACE <name> MANAGED BY AUTOMATIC STORAGECREATE TEMPORARY TABLESPACE TEMPTSCREATE USER TEMPORARY TABLESPACE USRTMP MANAGED BY AUTOMATIC STORAGECREATE 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;

SharedServices andEssbaseStudio

l Increase bufferpool to 32768.


l Increase the heap size:

m LOGFILSZ to 4096

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.



Planning Before you configure Planning, you must configure the database with a large enough tablespace (having a page size ofat 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 disklocation 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 asappropriate 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 usethe new tablespace.

Performance Scorecard–Specific 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 512DB2 CREATE BUFFERPOOL HPS_BP SIZE 250 PAGESIZE 32 KDB2 TERMINATEDB2STOPDB2STARTDB2 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_BPDB2 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 TERMINATEDB2STOPDB2


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 ServersMany EPM System products require a Java web application server. To identify the products thatrequire a Java web application server, see Chapter 2, “EPM System Architecture.”

WebLogic Serverl 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 ofthe WebLogic Server installed by EPM System Installer, note the Middleware home locationfor the WebLogic Server installation. During installation, you must install EPM Systemproducts to this same Middleware home. If EPM System Installer detects an existingWebLogic 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 79.

IBM WebSpherel 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 IBMInfoCenter for detailed instructions on granting permission to create a WebSphere profileas a non-root user.

l Install the plug-ins from the IBM WebSphere 7.0.0.23 supplemental components CD. Theyare required for Reporting and Analysis.

l When you are installing WebSphere, do not install the Web Services Gateway componentof the WebSphere Application Server Network Deployment. The Web Services Gatewaycomponent expects messages in SOAP 1.1 format; however, EPM System generates messagesin SOAP 1.0 format.

Preparing Java Web Application Servers 49

Preparing Web Servers

Oracle HTTP ServerYou 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 ashared drive location to simplify configuration in a distributed environment.

Caution! Before you install EPM System products, ensure you meet the installationprerequisites for Oracle HTTP Server and review the Oracle HTTP Server installationdocumentation and Release Notes for details. For additional information, see “WebServer Installation Prerequisites” on page 76.

Microsoft Internet Information Services (IIS)The following products require IIS to be installed with ASP.NET support enabled beforeconfiguration 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 ISAPIextensions through the Internet Information Services Manager.

l If you are using Smart View and Financial Management in a Windows 2003 Server 64-bitenvironment, you must disable IIS recycling based on memory consumption.

l On Windows 2008, if you are configuring products that require IIS, EPM SystemConfigurator automatically installs Windows server roles for IIS if they are not alreadyinstalled. On Windows Server 2003, you are prompted for the installation CD or the pathto Windows Server 2003 files to install the required IIS files.

Verifying the IIS InstallationTo verify the IIS installation, ensure that the IIS services are running:

l IIS Admin Service

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 youinstall the Dimension server. If .NET 4.0 Framework is not installed on your machine, EPMSystem 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.0with 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 toAllowed.

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

32–Bit/64–Bit Microsoft IIS 6.0/7.0 SupportMicrosoft IIS 6.0 can be configured to support 32-bit application runtimes or 64-bit applicationruntimes on 64-bit operating systems. Microsoft IIS 6.0 cannot be configured to support bothsimultaneously. Therefore, in general, when installing and configuring EPM System productswith Microsoft IIS 6.0, install 32-bit runtimes and 64-bit runtimes for EPM System Web tiercomponents on different computers.

Specifically, Strategic Finance (32-bit) cannot be deployed on the same computer whereFinancial Management (64-bit) is deployed. On 32-bit platforms, all EPM System products cancoexist.

Note: For IIS 7 (the default on Windows 2008 systems), 32-bit and 64-bit components cancoexist. However, for Strategic Finance, you need to install IIS 6.0 compatibility modewhen running IIS 7.0.

Using IIS in a Localized EnvironmentIn a localized environment, the following conditions are required to successfully configure EPMSystem on IIS:

For IIS 7:

Preparing Web Servers 51

l The IIS site name should not be localized; it should be “Default Web Site” in English on anymachine, 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 anymachine, 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 followingscripts to assign the ID = 1. For example, if the ID is 1111, the following scripts can be usedto 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 systemdrive, or use the drive where Windows 2003 is installed)

Preparing Web BrowsersThis section contains required browser settings and information about enabling ActiveX forReporting and Analysis.

Browser SettingsEnsure that browser preferences and options are enabled:

l For Internet Explorer and Firefox:

m Enable JavaScript.

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

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

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 changethe 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 thenclick Remove.

3. Click Add, and then add a user-defined value called no and click OK.

4. In the Language field, select the new User Defined [no] entry, and then click Move up tomove this entry to the top of the list.

5. Click OK.

Preparing Web Browsers 53

https://addons.mozilla.org/en-us/firefox/addon/remote-xul-manager/

https://addons.mozilla.org/en-us/firefox/addon/remote-xul-manager/

You can now view EPM System products in Norwegian using Internet Explorer.

Note: After you click OK, the custom language setting in Language Preferences dialogbox changes to Norwegan (Bokmal) [no], which is different from the defaultNorwegian (Bokmal) [ne-NO] setting.

Enabling ActiveX (Reporting and Analysis)To enable EPM System Java web applications to function properly, Internet Explorer must beconfigured to enable support for ActiveX technologies.

EPM System products do not download ActiveX components to the browser. Instead, onlyHTML, 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 andAnalysis 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 XMLparser and XMLHTTPRequest controls) and enable these administrator approved controlsfor all sites or for select trusted sites.

l All other ActiveX controls and plug-ins remain disabled. Group policies can be implementedby 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 forscripting.”

Support Matrix for High Availability and Load BalancingThe tables in this section list the supported clustering methodologies for EPM Systemcomponents by product group and indicate whether high availability and load balancing aresupported for each component. The tables also include notes and references to additionalinformation. 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 theWebSphere documentation.

EPM System components support vertical scaling as follows:

l Windows-based Java web applications except for Financial Management and StrategicFinance Java web applications

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/Component

SupportedMethodology

HighAvailability

LoadBalancing Notes

References

FoundationServicesManagedServer(includesSharedServices andEPMWorkspaceJava Webapplications)

WebLogicclustering withEPM SystemConfigurator

Yes Yes To configureLifecycleManagementfor highavailabilitywhen SharedServices is setup for highavailability,you must setup a shareddisk.

l Automatic deployment: “Clustering Java WebApplications Using EPM System Configurator” inthe Oracle Enterprise Performance ManagementSystem Deployment Options Guide

l Manual deployment: “Clustering Java WebApplications in a WebLogic Manual Deployment”in the Oracle Enterprise Performance ManagementSystem Deployment Options Guide

PerformanceManagementArchitect JavaWebApplication


Yes Yes Nonel Automatic deployment: “Clustering Java Web

Applications Using EPM System Configurator” inthe Oracle Enterprise Performance ManagementSystem Deployment Options Guide


PerformanceManagementArchitect DataSynchronizerJava WebApplication





Support Matrix for High Availability and Load Balancing 55

Product/Component


HighAvailability

LoadBalancing Notes

References

CalculationManager JavaWebApplication





PerformanceManagementArchitectDimensionServer andotherprocesses

OracleClusterwareclustering forfailover

Yes No Nonel “Performance Management Architect Dimension

Server Clustering and Failover” in the OracleEnterprise Performance Management SystemDeployment Options Guide

l Oracle Clusterware documentation


Table 5 Essbase Clustering

Product/Component


HighAvailability

LoadBalancing Notes

References

Essbase Serverl Active-passive

clustering withMicrosoftClusteringServices(Windows)

l Active-passiveclustering withEPM SystemConfigurator(UNIX)

l Active-activeclustering withProviderServices

Yes Active-activeclustersconfiguredwithProviderServicessupportload-balancing.

l Active-passive clusterssupport failover withwrite-back.

l Active-active clustersare read-only.

The following EPM Systemproducts support Essbaseactive-passive failover:

l FDMEE

l Planning

l AdministrationServices

l Essbase Studio

l Financial ReportingStudio

l Web Analysis

The following EPM Systemproducts do not supportEssbase active-passivefailover:

l Integration Services

l Interactive Reporting

l FDM

l Oracle EssbaseAnalytics Link forHyperion FinancialManagement

l Active-passive clustering(Windows): “ConfiguringActive-Passive EssbaseClusters (Windows)” in theOracle Enterprise PerformanceManagement SystemDeployment Options Guide

l Active-passive clustering(UNIX): “Configuring Active-Passive Essbase Clusters(UNIX)” in the Oracle EnterprisePerformance ManagementSystem Deployment OptionsGuide

l Active-active clustering:“Configuring Active-ActiveEssbase Clusters” in the OracleEnterprise PerformanceManagement SystemDeployment Options Guide

AdministrationServices JavaWebApplication

WebLogicclustering with EPMSystemConfigurator

Yes Yes l Automatic deployment:

“Clustering Java WebApplications Using EPM SystemConfigurator” in the OracleEnterprise PerformanceManagement SystemDeployment Options Guide

l Manual deployment:“Clustering Java WebApplications in a WebLogicManual Deployment” in theOracle Enterprise PerformanceManagement SystemDeployment Options Guide


Product/Component


HighAvailability

LoadBalancing Notes

References

ProviderServices JavaWebApplication

WebLogicclustering with EPMSystemConfigurator

Yes Yes Nonel Automatic deployment:

“Clustering Java WebApplications Using EPM SystemConfigurator” in the OracleEnterprise PerformanceManagement SystemDeployment Options Guide

l Manual deployment:“Clustering Java WebApplications in a WebLogicManual Deployment” in theOracle Enterprise PerformanceManagement SystemDeployment Options Guide

IntegrationServices

None No No None None

Essbase Studio None No No None None

Table 6 Reporting and Analysis Clustering

Product/Component


HighAvailability

LoadBalancing Notes

References

Reportingand AnalysisFrameworkJava WebApplication



Applications Using EPM System Configurator” in theOracle Enterprise Performance Management SystemDeployment Options Guide

l Manual deployment: “Clustering Java Web Applicationsin a WebLogic Manual Deployment” in the OracleEnterprise Performance Management SystemDeployment Options Guide

FinancialReportingJava WebApplication(includesFinancialReportingPrint Server)





Web AnalysisJava WebApplication






Product/Component


HighAvailability

LoadBalancing Notes

References

Reportingand AnalysisFrameworkServices andCommonLibraries

Virtualclusteringthrough EPMWorkspace

Yes Yes None “Clustering Reporting and Analysis” in the Oracle EnterprisePerformance Management System Deployment OptionsGuide

InteractiveReportingServices

Virtualclusteringthrough EPMWorkspace

Yes Yes None “Clustering Reporting and Analysis” in the Oracle EnterprisePerformance Management System Deployment OptionsGuide

Table 7 Financial Performance Management Applications Clustering

Product/Component


HighAvailability

LoadBalancing Notes

References

Planning JavaWeb Application





Planning RMIRegistry


FinancialManagementServer

Clustering withEPM SystemConfigurator

Yes Yes None “Clustering Financial Management Servers” in the OracleEnterprise Performance Management System DeploymentOptions Guide

FinancialManagementJava WebApplication(includes WebServices andADF Webapplications)





FinancialManagementWeb Services IISWeb Application(IIS)

Clustering witha Web server orthird-partyload balancer

Yes Yes None “Load Balancing Financial Management, Strategic Finance,or FDM IIS Web Applications on IIS” in the Oracle EnterprisePerformance Management System Deployment OptionsGuide

FinancialManagement IISWeb Application(IIS)




Product/Component


HighAvailability

LoadBalancing Notes

References

FinancialManagementLifecycleManagementWeb Services IISWeb Application(IIS)



FinancialManagementSmart View IISWeb Application(IIS)



PerformanceScorecard JavaWeb Application





Profitability andCostManagementJava WebApplication





DisclosureManagementJava WebApplication





Financial CloseManagement(includes CloseManager andAccountReconciliationManager JavaWebApplications)





l Load balancing: “Configuring High Availability forOracle Fusion Middleware SOA Suite” in the OracleFusion Middleware High Availability Guide


Product/Component


HighAvailability

LoadBalancing Notes

References

StrategicFinance Server

None No No None

StrategicFinance JavaWeb Application





StrategicFinance IIS WebApplication (IIS)



Table 8 Data Management Products Clustering

Product/Component


HighAvailability

LoadBalancing Notes

References

FDMApplicationServer

Clustering withthe FDMproprietaryload balancer

Yes Yes Nonel Database software documentation

l “FDM Clusters” in the Oracle EnterprisePerformance Management SystemDeployment Options Guide

l Oracle Hyperion Financial Data QualityManagement Configuration Guide

FDMproprietaryload balancer

None Yes No The load balanceris designed to beinstalled in morethan one place inan environment. Ifthe primary loadbalancer becomesunavailable,clients use asecondary loadbalancer.

None

FDM IIS WebApplication


Yes Yes None “Load Balancing Financial Management,Strategic Finance, or FDM IIS Web Applicationson IIS” in the Oracle Enterprise PerformanceManagement System Deployment OptionsGuide

FDM TaskManager



Product/Component


HighAvailability

LoadBalancing Notes

References

FDMEE WebLogicclustering withEPM SystemConfigurator

Yes Yes Nonel Automatic deployment: “Clustering Java

Web Applications Using EPM SystemConfigurator” in the Oracle EnterprisePerformance Management SystemDeployment Options Guide

l Manual deployment: “Clustering Java WebApplications in a WebLogic ManualDeployment” in the Oracle EnterprisePerformance Management SystemDeployment Options Guide

DataRelationshipManagementIIS WebApplication


No Yes Multiple MicrosoftIIS instances aredeployed in anactive-activeconfiguration.

l “Data Relationship Management Clusters”in the Oracle Enterprise PerformanceManagement System Deployment OptionsGuide

l “Configuring Load Balancing for DataRelationship Management WebApplications” in the Oracle DataRelationship Management InstallationGuide

DataRelationshipManagementApplicationServer

Clustering withDataRelationshipManagementproprietaryload balancing

No Yes Multipleapplication serversare deployed in aprimary-secondaryconfiguration.

l “Data Relationship Management Clusters”in the Oracle Enterprise PerformanceManagement System Deployment OptionsGuide

l “Configuring Host Machines” in the OracleData Relationship Management InstallationGuide


4Downloading Files for

Installation

In This Chapter

Downloading the Installation Files .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

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 youare 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 packon 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 filesfor the platform you are using.

l EPM System Installer (in EPM System Release 11.1.2.3.0 forplatformName (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 whichZIP files to download depending on the products you purchased. (To see the MediaPack 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).

Downloading the Installation Files 63

http://edelivery.oracle.com/



If you are prompted that any files or common components already exist, click Yes tooverwrite 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 commonfiles. If you downloaded files to multiple machines in your deployment, on each machinein the deployment, unzip the following common files. Unzip files for each operating systemin 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, installFoundation Services Java web applications on only one machine (unless multiple Javaweb applications are required for clustering).

l On the machine on which you plan to administer the WebLogic Server, you must installall Java web applications for all applications you plan to deploy on any machine in theenvironment. For more information, see “Installing EPM System Products in aDistributed Environment” on page 79.

5 The /assemblies directory should include a subdirectory for each product that you want to installon 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 withoutcausing problems.

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

64 Downloading Files for Installation

5Installing EPM System Products

in a New Deployment

In This Chapter

Installation Checklist for a New Installation ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65

Financial Close Management (Close Manager and Account Reconciliation Manager) InstallationChecklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69

Installation Prerequisites and Requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74

Installation Sequence ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79

Installing EPM System Products in a Distributed Environment .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79

Integrating Oracle BI EE with EPM System.... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80

Installing EPM System Products .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81

Performing Silent Installations ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87

Installing EPM System Clients .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89

EPM System Installer installs Web and services components. Additionally, when you configureEPM 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 InstallationEPM System deployment follows this workflow. Each part of the workflow is described in thesections as noted in the table below:

Note: If you are installing Financial Close Management, follow the installation andconfiguration sequence described in “Financial Close Management (Close Manager andAccount Reconciliation Manager) Installation Checklist” on page 69.

Installation Checklist for a New Installation 65

Note: Upgrade Note!

If you are upgrading from an earlier release of EPM System products, use EPM SystemInstaller and EPM System Configurator to install products in a new environment,following the process in Chapter 11, “Upgrading EPM System Products.” Upgrading doesnot 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 prerequisitetasks.

Chapter 3, “Preparing Your Environment”

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

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

Upgrade Note!

If you are upgrading from an earlier release, you must choose “New Installation” andinstall in a new installation location.

See Chapter 11, “Upgrading EPM System Products.”

66 Installing EPM System Products in a New Deployment




Task Reference

5. Configure EPM System products using EPMSystem Configurator.

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

Note: In a distributed environment, configure Foundation Services first. FoundationServices must be installed and configured in order for other products to configuresuccessfully.

Configure other EPM System products, and then configure the Web server last: (Selectthe Foundation Services “Configure Web Server” task.) Then, restart the Web server andrefresh EPM Workspace. If you configured Oracle HTTP Server to a shared drive, you cansimply restart the Web server and refresh EPM Workspace; you do not have to reconfigurethe Web server. See “Refreshing EPM Workspace” on page 112.

For more information about required configuration sequence, see “ConfigurationSequence” on page 103.

Note: If you are enabling SSL in your deployment, see the Oracle EnterprisePerformance Management System Security Configuration Guide before you configure.Different SSL configurations have implications for the choices you make duringconfiguration using EPM System Configurator. Also, there are additional post-configuration tasks when deploying an SSL configuration.

6. Optionally, manually deploy EPM SystemJava web applications.

Chapter 7, “Manually Deploying EPM System 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 OracleHTTP Server to a shared drive) on each machinehosting Foundation Services.

Then, refresh EPM Workspace on eachFoundation Services host machine in yourdeployment.

See “Refreshing EPM Workspace” on page112.

8. Perform any required manual configurationtasks for your products.

Chapter 9, “Performing Manual Configuration Tasks in a New Deployment”

9. Start EPM System services. Chapter 12, “Starting and Stopping EPM System Products”

10. Validate the installation using OracleHyperion Enterprise Performance ManagementSystem Diagnostics and verify deployment.

Chapter 13, “Validating the Installation and Verifying Deployment”

11. Enable external authentication andprovision users.

Oracle Enterprise Performance Management System User Security Administration Guide

Tip: During installation, configuration, and validation, keep a list of all user names andpasswords that you use to create or modify the system, including the applications withwhich they are associated and their purpose.

Installation Checklist for a New Installation 67

Deploying to a Shared Drive Environment (UNIX)For UNIX environments, you can deploy to a shared drive (not supported for Windows). Whenyou 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 productsto a shared drive. Use this procedure along with the installation checklist. See the “InstallationChecklist for a New Installation” on page 65 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 andthat 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 theshared 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 EPMOracle instances specify the same EPM Oracle instance home, and for EPM OracleInstance name specify a new EPM Oracle instance name. For example, afterconfiguration, the directory structure for EPM_ORACLE_INSTANCE looks like:

/user_projects/node1/node2/nodeNdomains/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 WebLogicAdministration Server.

l The Set Up Shared Services and Registry Database Connection configuration pagedisplays only on the first machine.


4 Complete the configuration on each machine and close EPM System Configurator before moving on toconfigure another machine.

Financial Close Management (Close Manager andAccount Reconciliation Manager) InstallationChecklistFor 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 ManagementRelease 11.1.2.1 or Release 11.1.2.2 to Release 11.1.2.3, see “Financial Close ManagementMaintenance Release Installation Checklist” on page 186.

Note the following about Financial Close Management installation:

l In a distributed environment, you must install Oracle SOA Suite on the following machinesin the deployment, although you need to configure it on only one machine (the machineon which you want to run SOA Server): Financial Close Management, WebLogicAdministration 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 CloseManagement, 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 existingWebLogic Server installation and want to use it instead of the WebLogic Server installed byEPM System Installer, it must be the version supported by EPM System. Note theMiddleware home location for the WebLogic Server installation. During installation, youmust install EPM System products to this same Middleware home. If EPM System Installerdetects an existing WebLogic Server installation in the installation location, it does not installWebLogic Server.

If the existing WebLogic Server version is not the correct version for EPM System, you musteither uninstall the current version, install the correct version, or upgrade to the correctversion before running EPM System Installer.

The following tables provide an overview of the installation and configuration process for OracleSOA 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 EPMSystem products and now want to extend the deployment to include Financial CloseManagement and Oracle SOA Suite.

Financial Close Management (Close Manager and Account Reconciliation Manager) Installation Checklist 69

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.

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

If Oracle SOA Suite is to be installed on a machine separate from EPM System products, you must alsoinstall Foundation Services on the SOA machine.

After installation, apply patch 16788543.

A default installation of EPM System installs WebLogic Server, which is required for Oracle SOA Suite. TheWebLogic Administration Server is installed and deployed on the Foundation Services machine.

Caution! After installation, do not proceed with configuring EPM System products using EPM SystemConfigurator until you have completed the following Oracle SOA Suite configuration steps.

“Installing EPM SystemProducts” on page 81.

In addition, for a distributedenvironment, ensure that youreview “Installing EPM SystemProducts in a DistributedEnvironment” on page 79for additional requirements.

If you are using Microsoft SQL Server, review “XA Configuration Required to Start the SOA Infrastructureon Microsoft SQL Server 2008 ” in the Oracle® Fusion Middleware Release Notes 11g Release 1 (11.1.1) for Microsoft Windows (32-Bit).

http://download.oracle.com/docs/cd/E15523_01/relnotes.1111/e10132/soa.htm#CDEIFEAC

Run the Repository Creation Utility and install Oracle SOA Suite.

Note: In a distributed environment, you must install Oracle SOA Suite on the following machines in thedeployment, although you need to configure it on only one machine (the machine on which you want torun SOA Server): Financial Close Management, WebLogic Administration Server, Foundation Services, andif you are integrating with these products, Financial Management (web application), Financial Reporting(web application), FDM (Web application).

“Creating InfrastructureSchemas Using RepositoryCreation Utility” on page99 and “Installing OracleSOA Suite” on page 101

Configure Oracle SOA Suite, creating a new WebLogic domain. You must also install any required OracleFusion Middleware patches, available on My Oracle Support.

Note: In a distributed environment note the following additional step:

l If Oracle SOA Suite is on a machine separate from EPM System products, you must also installFoundation Services on the SOA machine.

l If Oracle SOA Suite is configured on a machine separate from the WebLogic Administration Servermachine, use the pack command on the machine hosting the WebLogic Administration Server to packthe domain, and then use the unpack command to unpack it on the machine hosting the SOA Server.

If you plan to configure SOA clusters, configure the clusters at this point. See “Configuring High Availabilityfor Oracle Fusion Middleware SOA Suite” in the Oracle® Fusion Middleware High Availability Guide forinformation about configuring SOA clusters.

“Configuring and StartingOracle SOA Suite” on page101

and

Chapter 5, “Installing EPMSystem Products in a NewDeployment”

Tip: Review the SOA startuplogs for any errors and resolvethe errors before proceedingwith EPM SystemConfigurator. You can alsoview the status of SOA inEnterprise Manager Console.

Stop the SOA managed server. Stop WebLogic Server if it is on the same machine as Foundation Services.






Task Reference

Configure EPM System products, selecting all required configuration tasks except “Deploy to SOA” forClose Manager, and “Deploy to SOA” and “Deploy to SOA for FDM EE” for Account Reconciliation 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 DeployingEPM 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 WebLogicAdministration 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 domainwas 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 155 and step 20 on page 159 of Chapter 7, “Manually Deploying EPM SystemJava Web Applications.”

“Configuring EPM SystemProducts ” on page 109

Start WebLogic Administration Server and then the SOA managed server. “Configuring and StartingOracle SOA Suite” on page101

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.

If you are deploying EPM System products to a domain hosted on another machine (and the domain wasnot created with EPM System Configurator), you must also select the “Configure Web Server” task.

“Configuring EPM SystemProducts ” on page 109

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 mustperform 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 areno running DataLoads.

2. Start EPM System Configurator and from the Task Selection page, from the Financial Close, AccountReconcilation 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/%';


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, startEPM System Configurator and configure with the default selected configuration tasks (“Configure CommonSettings,” “Configure Database,” “Configure Oracle Configuration Manager”). During databaseconfiguration, specify the Foundation Services database information you entered when you configured theFoundation Services machine.

Tip: You can ignore any messages about Shared Services registration failing.

Chapter 6, “Configuring EPMSystem Products in a NewDeployment”

Perform manual configuration tasks for Financial Close Management. “Financial Close ManagementManual Configuration Tasks ”on page 177

Stop the SOA server, and then start EPM System products, the SOA Server and Financial Close Managementin the order listed.

Chapter 12, “Starting andStopping EPM SystemProducts,” and “FinancialClose ManagementApplication Server” on page314

Validate the installation and verify deployment. Chapter 13, “Validating theInstallation and VerifyingDeployment”

If you have already installed and configured some EPM System products, you can add FinancialClose Management and Oracle SOA Suite to the existing deployment using the followingroadmap:

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.

Note: In a distributed environment, on the machine on which you plan to administer the WebLogicServer, you must install all Java web applications for all applications you plan to deploy on anymachine in the environment.


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 EPMSystem Configurator until you have completed the following Oracle SOA Suite configuration steps.

“Installing EPM System Products”on page 81.

In addition, for a distributedenvironment, ensure that you review“Installing EPM System Products ina Distributed Environment” on page79 for additional requirements.

If you are using Microsoft SQL Server, review “XA Configuration Required to Start the SOAInfrastructure on Microsoft SQL Server 2008 ” in the Oracle® Fusion Middleware Release Notes 11gRelease 1 (11.1.1) for Microsoft Windows (32-Bit).


Run the Repository Creation Utility and install Oracle SOA Suite.

Note: In a distributed environment, you must install Oracle SOA Suite on the following machinesin the deployment, although you need to configure it on only one machine (the machine on whichyou want to run SOA Server): Financial Close Management, WebLogic Administration Server,Foundation Services, and if you are integrating with these products, Financial Management (Webapplication), Financial Reporting (Web application), FDM (Web application).

“Creating Infrastructure SchemasUsing Repository Creation Utility” onpage 99 and “Installing OracleSOA Suite” on page 101






Task Reference

From the WebLogic Administration Server machine, configure Oracle SOA Suite.

Note: During configuration, you must extend the WebLogic domain created during initial EPMSystem deployment.

You must also install any required Oracle Fusion Middleware patches, available on My OracleSupport.

Note: In a distributed environment note the following additional step:

l If Oracle SOA Suite is on a machine separate from EPM System products, you must installFoundation Services on the SOA machine.

l If Oracle SOA Suite is configured on a machine separate from the WebLogic Administration Servermachine, use the pack command on the machine hosting the WebLogic Administration Serverto pack the domain, and then use the unpack command to unpack it on the machine hostingthe SOA Server.

Tip: You might need to restart the WebLogic Administration Server prior to starting the SOA managedserver.

If you plan to configure SOA clusters, configure the clusters at this point. See “Configuring HighAvailability for Oracle Fusion Middleware SOA Suite” in the Oracle® Fusion Middleware HighAvailability Guide for information about configuring SOA clusters.

“Configuring and Starting OracleSOA Suite” on page 101 andChapter 5, “Installing EPM SystemProducts in a New Deployment”

Tip: Review the SOA startup logsfor any errors and resolve the errorsbefore proceeding with EPM SystemConfigurator. You can also view thestatus of SOA in Enterprise ManagerConsole.

Stop the SOA managed server. Stop WebLogic Server if it is on the same machine as FoundationServices.

Configure EPM System products, selecting all required configuration tasks except “Deploy to SOA”for Close Manager, and “Deploy to SOA” and “Deploy to SOA for FDM EE” for Account ReconciliationManager.

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, “ManuallyDeploying 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 theWebLogic Administration Server is running before you start EPM System Configurator.

“Configuring EPM System Products ”on page 109

Start WebLogic Administration Server and then the SOA managed server. “Configuring and Starting OracleSOA Suite” on page 101

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.

“Configuring EPM System Products ”on page 109

Restart WebLogic Administration Server.

In a distributed environment, if Oracle SOA Suite is on a machine separate from EPM Systemproducts, ensure that you have installed Foundation Services on the SOA machine. Then, on theSOA machine, start EPM System Configurator and configure with the default selected configurationtasks (“Configure Common Settings,” “Configure Database,” “Configure Oracle ConfigurationManager”). During database configuration, specify the Foundation Services database informationyou 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 ManagementManual Configuration Tasks ” onpage 177


Task Reference

Stop the SOA server, and then start EPM System products, the SOA Server and Financial CloseManagement in the order listed.

Chapter 12, “Starting and StoppingEPM System Products,” and“Financial Close ManagementApplication Server” on page 314

Restart EPM Workspace to access Financial Close Management from EPM Workspace.

Validate the installation and verify deployment. Chapter 13, “Validating theInstallation and VerifyingDeployment”

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 SystemCertification 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 adatabase, preparing IIS for products that require it, and preparing Web browsers.

l Download files required for installation. See Chapter 4, “Downloading Files forInstallation”. Review the Media Pack Readme on the Oracle Software Delivery Cloud to seewhich products are required or optional for use with your products.

l For Calculation Manager to work on Internet Explorer and Firefox, you must install AdobeFlash Player.

l If you plan to deploy EPM System products in an SSL-enabled environment, review theOracle Enterprise Performance Management System Security Configuration Guide before youinstall and configure. The SSL implementation you choose affects the options you chooseduring configuration. Optionally, you can deploy non SSL and reconfigure to use SSL. Seethe Oracle Enterprise Performance Management System Security Configuration Guide.

l If you are installing on Windows 2008, disable UAC before installing. UAC must be disabledto install, configure, and run EPM System products. UAC can be enabled on end-user clientdesktops.

l Ensure that there is 1 GB of temp space available. You can specify an alternate /tmp directoryif 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 onthe Linux server. See the Linux documentation for details.

l If you are installing on the same machine on which Oracle Business Intelligence EnterpriseEdition or Oracle Business Intelligence Publisher are installed, install into two differentMiddleware homes. Future patch sets for EPM System and Oracle BI EE will be released atdifferent times, which would create constraints for the upgrades of a merged FusionMiddleware 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 automaticallyinstalled and configured for you. The database for Oracle Data Integrator is in same databaseas FDMEE and the Oracle Data Integrator agent application is deployed in same JVM asFDMEE. 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 FinancialManagement 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. EPMSystem Installer installs a UNIX version of the driver on all platforms for use with Oracle BIEE.

l If you have an existing Oracle SOA Suite installation you plan to use with Financial CloseManagement, 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 existingWebLogic Server installation and want to use it instead of the WebLogic Server installed byEPM System Installer, it must be the version supported by EPM System. Note theMiddleware home location for the WebLogic Server installation. During installation, youmust install EPM System products to this same Middleware home. If EPM System Installerdetects an existing WebLogic Server installation in the installation location, it does not installWebLogic Server.

If the existing WebLogic Server version is not the correct version for EPM System, you musteither uninstall the current version, install the correct version, or upgrade to the correctversion before running EPM System Installer.

l For Financial Reporting, install the fonts that are used when designing a report in FinancialReporting Studio on the server that is hosting the Financial Reporting Java web applicationserver. Because PDF generation can now be run on a UNIX server, the fonts used in report

Installation Prerequisites and Requirements 75

http://www.oracle.com/technetwork/documentation/index.html#middleware


design in Financial Reporting Studio must be available on the Financial Reporting Java webapplication aerver, otherwise, the default system font on the Financial Reporting Studio Javaweb 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 isinstalled. If the installation location for Acrobat Reader is not in the PATH, set a newenvironment variable: PATH_TO_ACROREAD, where the path is the Acrobat Readerinstallation location.

l For AIX and HP-UX, configure X11 for Financial Reporting Print Server. For ProductionReporting 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 77.

l Install Microsoft Excel on the FDM Server machine.

l Install Microsoft Office Professional before installing Disclosure Management. To useDisclosure Management Client, when you install Microsoft Office, you must select .NETprogrammability support for Word and Excel.

l If you are installing Strategic Finance using Terminal Services, switch your session toinstallation mode before you run EPM System Installer (change user /install).

Web Server Installation PrerequisitesOptionally, EPM System Installer installs Oracle HTTP Server during the installation ofFoundation Services, using the Oracle HTTP Server silent installer. If you choose not to installOracle HTTP Server, for example in a development environment, EPM System Installer installsan 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 usewith 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 forOracle HTTP Server and review the Oracle HTTP Server installation documentation and ReleaseNotes for details on certified operating systems and supported UNIX / Linux packages andimportant installation issues and workarounds.

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 installationdocumentation: http://download.oracle.com/docs/cd/E15523_01/webtier.htm) andRelease Notes (http://download.oracle.com/docs/cd/E15523_01/relnotes.htm.

l For Oracle HTTP Server installation issues and workarounds, see the readme for yourplatform: http://download.oracle.com/docs/cd/E15523_01/relnotes.htm.


http://www.oracle.com/technology/software/products/ias/files/fusion_requirements.htm

http://www.oracle.com/technology/software/products/ias/files/fusion_requirements.htm

http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html

http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html

http://download.oracle.com/docs/cd/E15523_01/webtier.htm

http://download.oracle.com/docs/cd/E15523_01/relnotes.htm

http://download.oracle.com/docs/cd/E15523_01/relnotes.htm

On AIX, if you are using Oracle HTTP Server with Oracle Database, you must runrootpre.sh as the root user before you install Oracle HTTP Server. Run this script once oneach machine in the deployment. The file is in SystemInstaller-11120-aix.zip. For detailssee 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 optionto automatically manage paging file size.

During installation with EPM System Installer, check the Installation status for informationabout Oracle HTTP Server installation status. If Oracle HTTP Server installation fails, check thelogs for details. The logs report information from the Oracle HTTP Server silent installer. Youcan 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 Webserver logs, see the Oracle Enterprise Performance Management System Installation andConfiguration Troubleshooting Guide.

Configuring X11 for Financial Reporting and ProductionReporting (AIX and HP-UX)Financial Reporting Print Server uses Oracle Outside In Image Export technology. Outside InImage Export requires X11 for the AIX and HP-UX platforms, which is supported either withXvfb 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 servercomponents as the root user.

2 Determine whether Virtual Frame Buffer support is available on your computer by issuing the followingcommand:

lslpp -l X11.vfb

3 If X11.vfb is not installed, install it from your AIX installation media. After installing the package, applythe 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.

Installation Prerequisites and Requirements 77

http://download.oracle.com/docs/cd/E15523_01/doc.1111/e14771/toc.htm



http://techsupport.services.ibm.com

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 servercomponents as the root user.

2 Determine whether Virtual Frame Buffer support is available on your computer by issuing the followingcommand:

swlist -l product | grep 'Xserver cumulative patch'

3 Ensure that the patch level installed on your system corresponds with HP's recommended level (currentlyPHSS_31293).

4 Copy /etc/X11/X0screens to /etc/X11/X1screens, where 1 is a display number notalready 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 VariablePrior 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 deviceaddress; for example:

DISPLAY=hostname:0.0 ; export DISPLAY

For the sake of convenience, it is recommended that DISPLAY be initialized automatically byediting the Reporting and Analysis Java web application server components start scripts.

You can set display for Financial Reporting by editingsetCustomParamsFinancialReporting.bat|.sh in EPM_ORACLE_INSTANCE/bin/deploymentScripts.

Note: Only the Financial Reporting Java web application server component and ProductionReporting require DISPLAY to be set. Production Reporting requires DISPLAY in orderto generate charts using the New Graphics feature.


Installation SequenceEPM System Installer enables you to install, configure, and deploy multiple products on amachine at one time. EPM System Installer installs components in the correct order, so you canselect 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 aWeb tier or Service tier component, including Essbase Server. The .jar files that are installedas part of WebLogic Server and Oracle common directory are used by EPM System Configuratoras well as common services. Note that WebLogic Server does not need to run on the EssbaseServer.

OPMN is installed with Foundation Services on all machines where EPM System Configuratoris 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 skipthe installation for Foundation Services Java web applications. However, you must configurethe Shared Services Registry database. To configure the Shared Services Registry databasewithout installing Foundation Services, see “Setting Up Essbase in Standalone Mode” on page150.

Installing EPM System Products in a DistributedEnvironmentYou typically install EPM System products in a distributed environment. The number ofcomputers 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 yourdeployment.

EPM System Installer simplifies the task of installing components in a distributed computingenvironment. You can install, configure, and validate any components you want on anycomputer. 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. Forexample, if the path for EPM Oracle home is /Oracle/Middleware on the first machineyou configure, it must be /Oracle/Middleware on all the machines in the deployment.

Installation Sequence 79

l Foundation Services is required on only one machine in the deployment, unless multipleJava web application instances are required for clustering, or if you are using Financial CloseManagement, if Oracle SOA Suite is on a machine separate from EPM System products, youmust 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 allJava web applications for all applications you plan to deploy on any machine in theenvironment. (The WebLogic Administration Server is installed and deployed on theFoundation Services machine.)

l On each remote machine in a distributed environment, install the Java web applications youplan to run on that machine and then use EPM System Configurator to deploy the Java webapplications automatically, or manually deploy the Java web applications.

Note that EPM System Installer installs WebLogic Server on each machine (for Web tier andService 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 withan IIS Web server.

l If you are installing in multiple environments (for example, Development, Test, andProduction), install Foundation Services products in each environment.

l If you are installing Financial Management Web and Financial Management Services on thesame 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-bitcomponents are already installed. You must install the 32-bit components on another systemor 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) isdeployed. On 32-bit platforms, all EPM System products can co-exist. For IIS 7 (the defaulton Windows 2008 systems), 32-bit and 64-bit components can co-exist.

l Web Analysis supports connectivity to Financial Management data sources only forFinancial Management servers that are registered in the same Shared Services Registry asWeb Analysis.

Integrating Oracle BI EE with EPM Systeml 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 Systemand Oracle BI EE will be released at different times, which would create constraints for theupgrades 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 Workspaceintegration with Oracle BI EE Release 10g, then you can upgrade to Oracle BI EE Release11.1.1.7, but the integration with EPM Workspace is not upgraded. You must reconfigurefor the integration using the procedures that are described in Oracle® Fusion MiddlewareSystem 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 youmust set additional environment variables for the Oracle BI EE driver before launchingEssbase. See the Oracle Enterprise Performance Management System Deployment OptionsGuide.

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 systemrunning the Oracle BI JavaHost process.

Perform the following tasks:

1. Using EPM System Installer, install the Financial Management ADM driver on themachine running the Oracle BI JavaHost process.

2. Using EPM System Configurator, provide database connection details for SharedServices and for Financial Management. In the Configure DCOM page, provide adomain user that is the user connecting to the Financial Management server.

3. After configuration, edit opmn.xml on each system running the Oracle BI JavaHostprocess to include environment variables required by Financial Management. See theOracle Enterprise Performance Management System Deployment Options Guide.

Installing EPM System ProductsYou can install EPM System products using the graphical user interface, using the console modeinterface, 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 Release11.1.2.2 to Release 11.1.2.3.

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 EPMSystem products, during installation, select Apply Maintenance Release first to install thelatest WebLogic Server, and then select New Installation to continue with the installation ofEPM System products.

Installing EPM System Products 81

http://docs.oracle.com/cd/E28280_01/bi.1111/e10541/toc.htm




l On Windows machines, do not use the Administrator user to install and configure. RunEPM 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 Systemproducts. If you are using Windows 2008, install with UAC disabled. UAC must be disabledto install, configure, and run EPM System products. UAC can be enabled on end-user clientdesktops.

l On UNIX machines, do not use the root user to install and configure. Install, configureand run EPM System Diagnostics as the same user for all EPM System products. On UNIXmachines, 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 instanceof 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 youextracted the EPM System Installer files.

l (Windows) From a Windows console, change to the root directory to which youextracted the EPM System Installer files and enter installTool.cmd -console.

l Create a silent installation response file. See “Performing Silent Installations” on page87.

l (UNIX) Change to the root directory to which you extracted the EPM System Installerfiles and enter ./installTool.sh.

l (UNIX) Change to the root directory to which you extracted the EPM System Installerfiles 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 messagethat User Account Control (UAC) is enabled on Windows 2008 systems, disable UAC,reboot, and then restart EPM System Installer.

EPM System Installer launches.

Tip: The first page of EPM System Installer might open hidden behind other windows ifyou navigate away from the EPM System Installer window or try to reposition the initialwindow. 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 thelanguage 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 nextpage.

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 thelist of assemblies to install. This might take several minutes, depending on how manyproducts you selected. EPM System Installer displays progress incrementally as eachassembly's installation is complete.

The following table provides links where you can find more details about each page of EPMSystem Installer.

Table 11 EPM System Installer Pages

Page Reference

Welcome “Welcome” on page 83

Destination/MiddleWare Home “Destination/Middleware Home” on page 84

Installation Type “Installation Type” on page 85

Product Selection “Product Selection” on page 86

Confirmation “Confirmation” on page 87

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

Note: If you are installing Financial Close Management, note that it requires additional stepsbefore you configure with EPM System Configurator. See the “Financial CloseManagement (Close Manager and Account Reconciliation Manager) InstallationChecklist” on page 69 for the process to follow.

Welcome

ä Review the prerequisites carefully before you continue the installation. When you haveconfirmed that your system meets the prerequisites to run EPM System Installer, click orselect 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 nameresolves to an IP address, EPM System Installer provides a warning. Oracle recommendsthat you resolve this issue and provide a host name instead of an IP address beforeproceeding.

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 theprerequisite items do not display a check mark, and you choose to continue, the installationmight not succeed.

Tip: If you are using a hosts file to resolve your host name, the host name resolves to the firstentry in your hosts file. To prevent potential communication problems in a distributedenvironment, ensure that the first entry in your hosts file is the machine's fully qualifieddomain 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, andthen click or select Next. The default location is Oracle/Middleware.

The destination you specify becomes the Middleware home. By default EPM System Installercreates a default EPM Oracle home under the Middleware home. The default location isOracle/Middleware/EPMSystem11R1.

See “About Middleware Home, EPM Oracle Home, and EPM Oracle Instance” on page 17.

Do not use any of the following symbol combinations in the directory that you specify forEPM_ORACLE_HOME during installation:

/t

\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 wantto install on this machine.

See “Disk Space and RAM” on page 36 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. Forexample, if the path for EPM Oracle home is /Oracle/Middleware on the first machineyou 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 yourinstallation, or applying the maintenance release, the existing location for the Middlewarehome 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 notacceptable (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 toa file, you can load the selections to prepopulate the installation destination and theproducts to install. Doing so is useful if you are installing the same products on multiplemachines. 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 applicableon this machine, the option is unavailable.

Note: You cannot combine installation types in one session. For example, you cannot performa new installation of one product at the same time you perform a reinstallation of anotherproduct.

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

m Choose this option if you want to install additional components that you did not initiallyinstall.

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 earlierrelease 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 wantto 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 Release11.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 allinstalled 11.1.2.0, 11.1.2.1, or 11.1.2.2 products. You cannot apply the maintenance releaseto 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 therelease to all installed Release 11.1.2.0, 11.1.2.1, or Release 11.1.2.2 products. You cannot applythe maintenance release to only some products in your deployment. On the Product Selectionpage, 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 productscomponents to install.

You can expand and collapse the entries to select or clear specific options for each product and component.

Uncheck all / Check all Select “Check all” to select all the products, or “Uncheck all” to clear all the products. This option is notavailable if you are applying a maintenance release.

Hide/Show unavailableproducts.

To see only products for which installation assemblies are available, select Hide Unavailable ProductComponents.

To see all products, select Show Unavailable Product Components.

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

l Products are available for installation only if the assemblies are downloaded to the correctlocation and the selected component is supported on the platform on which you areinstalling. If a product is unavailable on the Product Selection page, ensure that theassemblies are in the correct location.

l Select a product component to see information and status about it in the lower portion ofthe 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 cannotproceed until you install IIS. If you are installing on an unsupported platform, a warning isdisplayed.

l The Shared Services and EPM Workspace Java web applications are installed when you installthe 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 isrequired for another selected component.


Confirmation

ä Review the summary of products to be installed. If necessary, click or select Back and makecorrections. 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, orto use as the basis for a response file for silent installation, see “Saving Installation Selections”on page 87.

Saving Installation SelectionsIf you plan to install this same set of components on another computer, you can save theinstallation selections in a file. You can then load the selections on another computer duringinstallation 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 filename, and click or select Save.

This procedure creates an editable file that can be used as the basis for a response file for silentinstallation. For information about using a response file, see “Loading Saved Selections” on page88.

Performing Silent InstallationsSilent installations automate the installation process so that you can install EPM System productson multiple computers without manually specifying installation settings on each machine.

To enable silent installation, record your installation settings in a response file. You can thenrun a silent installation from the command line, using the installation options that were savedin 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

Performing Silent Installations 87

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 laterto 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 thefile 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 releaseof EPM System products, you must re-create them for use with EPM System Release 11.1.2.3.

Loading Saved SelectionsYou 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. Thefile is saved in the same format as for silent installations.

ä To play back the installation using the same installation destination and product componentselections, 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 FilesAfter you create a response file, you can modify it to customize the installation options for certainmachines. 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 componentsthat 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 changesin <Product name>, <ProductComponent name>, <InstallTier>, and<Component>.

l <Product name>—The name of the product. Enclose product names in quotes, as theyare XML attributes.

l <ProductComponent name>—The component of the product. Enclose componentnames 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.

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 PrerequisitesReview 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 mustbe running.

Although Planning Offline is supported for 64-bit operating systems, it is not supported for64-bit Smart View installations. If you use Planning Offline with Smart View, you must usethe 32-bit version of Smart View and the 32-bit version of Microsoft Office.

Installing EPM System Clients 89

l Predictive Planning: Install Microsoft Excel and Smart View on the same machine, withaccess to Planning.

l Smart View: Install Microsoft Excel with the Visual Basic option. Smart View requires .Net4.0.

l Strategic Finance: To enable use of Smart View with Strategic Finance, install the SmartView client before installing the Strategic Finance client.

l Performance Management Architect File Generator: Install Microsoft Excel with "VisualBasic for Applications" to use Performance Management Architect File Generator from theExcel File menu.

l Interactive Reporting: After a user has installed Interactive Reporting client (with the abilityto use for all users), subsequent users should run the regServers.bat script (located inEPM_ORACLE_HOME\products\biplus\bin) in order to run Dashboard Studio andDashboard Architect applications.

Downloading and Extracting Client InstallersYou use client installers when Installing Individual EPM System Clients and when InstallingEPM System Clients from EPM Workspace.

ä 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 installerfolder 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

The Essbase Client installer is Windows only. On UNIX, Essbase Client is installed withEssbase Server.

l Essbase Studio Console

l Financial Management Console

l Financial Reporting Studio

l Interactive Reporting (Oracle Hyperion Interactive Reporting Studio and DashboardDevelopment 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 selectedfor 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 Reportingengine.

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 touninstall the earlier release of the client.

If you have installed a client in a previous release using EPM System Installer, you must uninstallthe 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 90 for the subfolders andinstaller names.

Note that Financial Management, Predictive Planning, Smart View, and Strategic Financehave both 32-bit and 64-bit installers. For Financial Management, the 64-bit installer installssome client components that are 64-bit, but Financial Management and its dependent filesare 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 LineYou can run an EPM System client installer from the command line using the followingparameters:

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 ignoresthe INSTALLDIR= value and install the clients in EPM_ORACLE_HOME:


Option Usage

l*v log file path and name Logs installation information in the specified file.

Installing EPM System Clients from EPM WorkspaceIf you have installed and configured EPM Workspace, you can download and launch installersfor 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 EPMWorkspace server.

See “Downloading and Extracting Client Installers” on page 90 for information onclient 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 SystemClient

Client Installer Location in EPM Workspace

DisclosureManagementTaxonomyDesigner

DisclosureManagement/taxodesigner/TaxonomyDesigner.msi

EPM_ORACLE_HOME/common/epmstatic/wspace/disclosure_mgmt/taxodesigner/TaxonomyDesigner.msi

FinancialManagementClient

FinancialManagementClient/HFMClient.exe

Note: You cannot install the 64-bit version of FinancialManagement Client from EPM Workspace.

EPM_ORACLE_HOME/common/epmstatic/wspace/hfm/HFMClient.exe

OfflinePlanning

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

PlanningAdminExtension

Planning/PlanningSVExtensions.msi EPM_ORACLE_HOME/common/epmstatic/wspace/PlanningSmartviewExtension/PlanningSVExtension.msi


EPM SystemClient

Client Installer Location in EPM Workspace

PredictivePlanning

PredictivePlanning/predictiveplanning.exe

Note: You cannot install the 64-bit version ofPredictive Planning from EPM Workspace.

EPM_ORACLE_HOME/common/epmstatic/wspace/predictive_planning/predictiveplanning.exe

Smart View Smartview/SmartView.exe

Note: You cannot install the 64-bit version of SmartView from EPM Workspace.

EPM_ORACLE_HOME/common/epmstatic/wspace/SmartView.exe

StrategicFinance Client

StrategicFinanceClient/HSFClient.exe

Note: You cannot install the 64-bit version of StrategicFinance Client from EPM Workspace.

EPM_ORACLE_HOME/common/epmstatic/wspace/hsf/Client/HSFClient.exe

2 Select Tools, then Install, and then select the product to install.

Installing EPM System Clients From EPM System InstallerYou can use EPM System Installer to install EPM System clients that do no have their ownWindows 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.

Installing Multiple Versions of Financial Reporting Studio ona Client MachineYou can install more than one version of Financial Reporting Studio (for example a test and adevelopment version) on a client machine for versions 11.1.2.3 and later only. The installedversions of Financial Reporting Studio are displayed in the Microsoft Windows Start menu folderand shortcuts, as well as in the Uninstall panel.

Note: Each Financial Reporting Studio version installed on a client machine must be installedin 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 installeras an administrator.


Note: If a machine has multiple versions of Financial Reporting Studio installed, only one releasecan 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 <versionnumber>, and then Register Financial Reporting Studio <version number>, where <versionnumber> is the Financial Reporting Studio release to use.

2 To launch the Financial Reporting Studio version registered in the previous step, from the MicrosoftWindows Start menu, select Oracle, then the folder Financial Reporting Studio <version number>, andthen Financial Reporting Studio <version number> .

Performing Silent Client InstallationsAdministrators can enable silent installations. When silent installations are enabled, you caninclude the silent installation command in scripts to automate the process, so that you do notneed to specify settings each time you perform an installation.

ä To perform a silent installation of any EPM System client other than DisclosureManagement, use this command:

installer file name /s /v"/qn INSTALLDIR=installation directory /l*v logfile 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

Note: For installer file names, see “Downloading and Extracting Client Installers” on page 90.For information about command-line parameters, see Table 13 on page 92.

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


Client Default Installation Directory

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


6Configuring EPM System

Products in a New Deployment

In This Chapter

About EPM System Configurator.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97

Configuration Prerequisites .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98

Configuration Sequence... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Configuring Products in a Distributed Environment .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Configuring Products in an SSL-Enabled Environment .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Configuring Products for Manual Deployment.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Configuring Products for WebSphere Application Server .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Product Configuration Task Summary ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Configuring EPM System Products .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

EPM System Configurator Task Reference ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Performing Silent Configurations ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Setting Up Essbase in Standalone Mode... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Deploying Financial Management, Financial Reporting, and Web Analysis on Windows in a UNIX-Based EPM System Deployment .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

What Happens During Configuration ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Troubleshooting Configuration ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

About EPM System ConfiguratorEPM System Configurator is installed with the first EPM System product installed on a computerand is used to configure all products installed on the computer. Use EPM System Configuratoron each computer on which EPM System products are installed. (EPM System clients do notrequire configuration.)

Use the configuration worksheets throughout this chapter to plan your configuration and todocument the configuration steps for your company if required for disaster recovery.

About EPM System Configurator 97

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 Serviceshost machine (FNDHOST1): On the Foundation Services host machine, start WebLogic ServerAdministration Server by selecting Start, then All Programs, then Oracle WebLogic, then UserProjects, then EPMSystem, and then Start Admin Server for WebLogic Server.)

l Ensure that host names resolve properly for each machine in the deployment. See “Ensuringthat Host Names Resolve” on page 99.

l If you want to deploy Java web applications to a single managed server, you must be usingWebLogic 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 settingwith the following command: ulimit -n.

l If you plan to deploy EPM System products in an SSL-enabled environment, review theOracle Enterprise Performance Management System Security Configuration Guide before youconfigure. The SSL implementation that you choose affects the options that you select duringconfiguration. Optionally, you can deploy non SSL and reconfigure to use SSL. See the OracleEnterprise Performance Management System Security Configuration Guide.

l If you are using one of the following products, see “Creating Infrastructure Schemas UsingRepository Creation Utility” on page 99.

m Financial Close Management

m Profitability and Cost Management, and plan to use Oracle Web Services Manager toautomate Profitability and Cost Management tasks

m FDMEE, and plan to use the RuleService/SetupService or plan to integrate FDMEE withAccount 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 FinancialClose Management” on page 101.

98 Configuring EPM System Products in a New Deployment

Ensuring that Host Names ResolveBefore configuring, ensure that the host name resolves properly for each machine in thedeployment. EPM System uses Java’s 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 followingcommand: 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 thefollowing 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 localhosts file and add an entry for this server.

Creating Infrastructure Schemas Using Repository CreationUtilityThe Repository Creation Utility (RCU) is used to create multiple schemas to support differentOracle Fusion Middleware products such as Oracle SOA Suite (SOA) and Oracle Web ServicesManager (OWSM). Some EPM System products use these Middleware technologies, so youmust 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 DataRelationship Management, you must install the Repository Creation Utility (RCU) beforeconfiguring these EPM System products. The RCU creates the required schemas to work withOracle 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 createthe SOA schemas. Use the following procedure to create the required infrastructure for SOAand 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.

Configuration Prerequisites 99

2 Navigate to the Installer-RCU folder.

3 Copy rcuHome.zip to the location in which you want to install the Repository Creation Utility, andextract the contents.

4 From rcuHome/bin, run the Repository Creation Utility using the appropriate file for your operatingsystem:

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

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: ExpandAS Common Schemas and select Metadata Services, if it is not already selected.

l Additionally, for Financial Close Management: Expand SOA and BPM Infrastructureand select the following SOA infrastructure components: SOA Infrastructure and UserMessaging Service. (You need not select Business Activity Monitoring (BAM).)

For Identity Management, OID is selected by default. Do not select Oracle IdentityFederation.

l Make a note of the Schema Owner names for all the components because you need themto configure Oracle Web Services Manager.

8 On the Schema Passwords page, Oracle recommends that you select Use same passwords for allschemas. 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® FusionMiddleware Repository Creation Utility User’s Guide 11g Release 1 (11.1.1).


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 startOracle SOA Suite.

Installing Oracle SOA SuiteThe following procedure provides an overview of the Oracle SOA Suite installation procedure.For more information about this procedure, see the Oracle® Fusion Middleware InstallationGuide 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 stepsthat follow.

ä To install Oracle SOA Suite:

1 Ensure that you meet all the prerequisites and system requirements described in the Oracle® FusionMiddleware Installation Guide for Oracle SOA Suite 11g Release 1.

Note: Oracle SOA Suite requires WebLogic Server, which is installed with a defaultinstallation of EPM System.

2 Ensure that you have installed and run the Repository Creation Utility (RCU) to create the requiredschemas for Oracle SOA Suite. See “Creating Infrastructure Schemas Using Repository Creation Utility”on page 99.

3 Download Oracle SOA Suite from the “Oracle Enterprise Performance Management System” Media Packon Oracle EDelivery, and then install it using the default options. If you have already installed EPMSystem 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 OracleSOA Suite” on page 101.

Configuring and Starting Oracle SOA SuiteEnsure that you have installed Oracle SOA Suite as described in “Installing Oracle SOA Suite”on page 101. Before you configure Financial Close Management, you must configure and startOracle 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 ofthe 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.

Configuration Prerequisites 101

http://download.oracle.com/docs/cd/E15523_01/doc.1111/e13925/overview.htm#sthref12

http://download.oracle.com/docs/cd/E15523_01/doc.1111/e13925/overview.htm#sthref12

http://download.oracle.com/docs/cd/E15523_01/doc.1111/e13925/configure.htm#CACEEJJJ

http://download.oracle.com/docs/cd/E15523_01/doc.1111/e13925/configure.htm#CACEEJJJ

ä To configure Oracle SOA Suite:

1 From the WebLogic Administration Server machine, run the Oracle Fusion Middleware ConfigurationWizard to configure a WebLogic domain, and choose the products that you want to configure in thatdomain. To start the Configuration Wizard, from SOA_ORACLE_HOME/common/bin (orMIDDLEWARE_HOME/oracle_common/common/bin), run config.sh (UNIX) orconfig.cmd (Windows).

Note that EPM System and Oracle SOA Suite must be deployed to the same domain. Thechoice you make for the domain depends on your deployment scenario:

l In a new deployment, where you have not yet configured EPM System products, youmust create a new WebLogic domain.

l In an existing deployment, where you have already configured EPM System productsand now want to extend the deployment to include Financial Close Management andOracle SOA Suite, you must extend the existing WebLogic domain created during EPMSystem deployment.

Note the following additional details for this step. Note that not all steps are listed, onlythose that require specific selections for Financial Close Management.

l During creating/extending domain, select the following products: Oracle SOA Suite andall common Oracle components, including Oracle Enterprise Manager, Oracle WSMPolicy Manager, Oracle JRF WebServices Asynchronous Services, and Oracle JRF, if theyare not already selected.

l Select the default JDK. Oracle recommends that you select Production Mode. (Whenusing Production Mode, when you start WebLogic Administration Server, when youare prompted to enter a user name and password, enter the user name and passwordthat you entered during the configuration of the Administration Server domain.)

l When you configure the JDBC datasources, enter the database details that you enteredwhen you ran RCU.

l Use the default settings for the server port. By default, the Administration Server portis 7001 and the soa_server1 port is 8001.

2 Start WebLogic Administration Server and the Oracle SOA Suite managed servers using the WebLogicAdministration 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 CloseManagement.


Tip: SOA setup usually runs on two servers - an Admin Server running on port 7001, whichhosts the Enterprise Management application, and a managed server running on port8001, which hosts the SOA infrastructure. Log in to http://host:7001/em with yourdomain 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 69 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 69. Then, perform manual configuration tasks.

Configuration SequenceFoundation Services must be installed and configured for other products to configuresuccessfully. In general, for a new deployment, Oracle recommends that for each machine, youconfigure 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 207 for details about the configuration sequence when youare upgrading from an earlier release of EPM System products.

Configuration sequence notes:

l Configure Foundation Services first. Foundation Services must be installed and configuredfor 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 OracleHTTP Server to a shared drive, you can simply restart the Web server and refresh EPMWorkspace; you do not have to reconfigure the Web server. See “Refreshing EPMWorkspace” on page 112.

l Complete the configuration on each machine and close EPM System Configurator beforelaunching EPM System Configurator on another machine.

l When you configure in a distributed environment, you configure the Shared Servicesdatabase on every machine. On the first machine, you are setting up the Shared ServicesRegistry. For configurations on subsequent machines, choose “Connect to a previouslyconfigured Shared Services database,” which lets the machine know the location of theShared Services Registry.

l If you deploy any additional products, reconfigure the Web Server and then restart it (orsimply restart it if you configured Oracle HTTP Server to a shared drive) on each machinehosting Foundation Services.

Then, refresh EPM Workspace on each Foundation Services host machine in yourdeployment.

Configuration Sequence 103

See “Refreshing EPM Workspace” on page 112.

l You must perform the “Configure Database” task at the same time as or before you performthe “Deploy to Application Server” task.

l When configuring Financial Management in a distributed environment, you must installall IIS Web applications and Java Web applications on the same machine, and perform theDeploy to Application Server task and the Financial Management Configure Web Servertask on the same machine.

l If you are configuring Financial Close Management, there is a required configurationsequence. See “Financial Close Management (Close Manager and Account ReconciliationManager) Installation Checklist” on page 69.

l Automatic Web server configuration with EPM System Configurator is supported only forthe Web server installed by EPM System Installer (Oracle HTTP Server or the proxy WebServer) or IIS.

l You must also run the Financial Management “Configure DCOM” task if it has not alreadybeen 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 tasksrequired for your product.

For information about clustering or scaling EPM System, see the Oracle Enterprise PerformanceManagement System Deployment Options Guide.

Configure the following products after you have completed all the configuration tasks usingEPM System Configurator:

l Data Relationship Management. See the Oracle Data Relationship Management InstallationGuide.

l FDM. The tasks in EPM System Configurator register the FDM Web server in the SharedServices Registry. The remainder of the configuration is done in FDM. See the OracleHyperion Financial Data Quality Management Configuration Guide.

Note: If you want to install Essbase in standalone mode (not using Foundation Services), youcan skip the installation for Foundation Services Java web applications. However, youmust still configure the Shared Services Registry. To configure the Shared Services Registrywithout installing Foundation Services, you run EPM System Configurator from thecommand line using the –forceRegistry option. See “Setting Up Essbase in StandaloneMode” on page 150.

Configuring Products in a Distributed EnvironmentEnsure that you meet installation requirements in a distributed environment. See “InstallingEPM System Products in a Distributed Environment” on page 79. For information aboutclustering and high availability, see the Oracle Enterprise Performance Management SystemDeployment Options Guide.


Configuration considerations in a distributed environment:

l You must configure Foundation Services first. Foundation Services must be installed andconfigured 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 WebLogicAdministration 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 SystemDeployment ” on page 151.

l During configuration with EPM System Configurator, the Web server machine needsconnectivity 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. Ifyou 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 clustershould be the load balancer. If you have only one Web server, the logical Web address forthe Java web application cluster can be the Web server.

l When configuring EPM System for high availability where multiple instances of services arerunning, you must point to the same location on a shared disk in these fields in EPM SystemConfigurator:

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

For example, \\SharedHost\SharedLocation\data\HPS

l Optionally, you can configure Oracle HTTP Server to a shared drive to simplify theconfiguration process.

Configuring Products in an SSL-Enabled EnvironmentIf you are configuring EPM System products for SSL, the configuration sequence and selectionsthat you make during configuration depend on the type of SSL implementation you choose. Seethe Oracle Enterprise Performance Management System Security Configuration Guide for moreinformation. Optionally, you can deploy non SSL and reconfigure to use SSL. See the OracleEnterprise Performance Management System Security Configuration Guide.

Configuring Products in an SSL-Enabled Environment 105

Note: Essbase supports only one-way SSL using self-signed certificates by default. Using defaultcertificates is recommended for use only in a test environment. Oracle recommends thatyou use certificates from well-known third party CAs in a production environment. Seethe Oracle Enterprise Performance Management System Security Configuration Guide fordetails.

Configuring Products for Manual DeploymentIf you plan to manually deploy EPM System Java web applications, launch EPM SystemConfigurator with the /configtool-manual.bat|.sh command. Perform requiredconfiguration tasks except for the “Deploy to Application Server” task and the “Configure WebServer” task. Then, perform additional manual steps.

See “Configuring EPM System Products ” on page 109 and then Chapter 7, “Manually DeployingEPM System Java Web Applications.”

Configuring Products for WebSphere ApplicationServerIf 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 109 and then Chapter 8, “Deploying EPMSystem Products to WebSphere Application Server.”

Product Configuration Task SummaryConfiguration notes:

l EPM System Configurator performs pre-configuration tasks and registers products withShared Services during configuration. You need not select these tasks; they are automaticallyperformed when needed.

l Shared Services Registry database configuration appears once on each machine that youconfigure.

l Clients do not require configuration and are not included in these tables.

The following table summarizes the configuration options available for Foundation Servicesproducts.


Table 16 Foundation Services Configuration Task Summary

ConfigureDatabase

Deploy to Application Server Product-specific Configuration Tasks

FoundationServices

X X

This selection deploys SharedServices and the EPM WorkspaceJava web applications.

l Configure Common Settings

l Configure Oracle Configuration Manager

l Set up Connection to Oracle BI and Publisher (Optional)

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


X (Windowsonly)

X

This selection deploys Web Tier andData Synchronizer Java webapplications.

X

Configure Dimension Server

CalculationManager

X X

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

Table 17 Essbase Configuration Task Summary

ConfigureDatabase

Deploy toApplication Server

Product-specific Configuration Tasks

Essbase X

Configure Essbase Server


X X X

(Upgrades only) Import data from earlier release

Provider Services X X

(Upgrades only) Import data from earlier release

Essbase Studio X (Required forEssbase Studiocatalog)

X

Configure Essbase Studio Location for Sample and Customer DataSource Text Files

Integration Services X

Configure Essbase Integration Services

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

Product Configuration Task Summary 107

Table 18 Reporting and Analysis Configuration Task Summary

ConfigureDatabase

Deploy toApplicationServer



X X X

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 mustalso select the Financial Management “Configure DCOM” task.

ProductionReporting

X

l SQR Production Reporting

The following table summarizes the configuration options available for Financial PerformanceManagement Applications products.

Table 19 Financial Performance Management Applications Product Configuration Task Summary

ConfigureDatabase



FinancialManagement (Allconfiguration tasksare Windows only)

X X X

l Configure DCOM

l Configure Application Server

l Configure Application Cluster


l (Upgrades only) Upgrade applications from earlier release

Planning X X X

Configure RMI Server


X X X

Configure Attachment Files Location

Profitability andCost Management

X X

Strategic Finance X X

l Configure Port and Data Folder

l WebServices Configuration

l You must also run the Financial Management “Configure DCOM” task ifit has not already been run on the machines hosting Strategic Finance.

DisclosureManagement

X X


ConfigureDatabase



Financial CloseManagement CloseManager

X X X

l Deploy to SOA

l Configure Content Management System Location (Optional)

Financial CloseManagementAccountReconciliationManager

X X X


l Deploy to SOA for FDM EE

l Deploy to SOA

The following table summarizes the configuration options available for Data Managementproducts.

Table 20 Data Management Product Configuration Task Summary

ConfigureDatabase



FDM X

l Configure FDM Web Application

l Configure FDM Server

l You must also run the Financial Management “Configure DCOM” task if it has not alreadybeen run on the machines hosting FDM.

FDMEE X X X

l Register HFM Adapter

l You must also run the Financial Management “Configure DCOM” task if it has not alreadybeen run on the machines hosting FDMEE.

Configuring EPM System Products Run EPM System Configurator on each machine hosting the products to configure orreconfigure.

For a list of characters supported during configuration with EPM System Configurator, see“Characters Supported for Installation and Configuration” on page 18.

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 administratorrights. Install, configure and run EPM System Diagnostics as the same user for all EPMSystem products. If you are using Windows 2008, configure with UAC disabled. UACmust be disabled to install, configure, and run EPM System products. UAC can be enabledon end-user client desktops.

Configuring EPM System Products 109

Note: On UNIX machines, do not use the root user to install and configure. Install andconfigure as the same user for all EPM System products. On UNIX machines, for all Oracleproducts, the user that is installing must be part of the same group; the group must havewrite permission to the central inventory (oraInventory).

Note: When you upgrade or apply the maintenance release, install and configure using the sameuser 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 SystemConfigurator (all instances).

l Change to EPM_ORACLE_HOME/common/config/version_number and then launchconfigtool.bat (.sh).

l To run EPM System Configurator in console mode, launch it from the command lineusing 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 148.

l If you are manually deploying Java web applications, launch EPM System Configuratorfrom 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 JavaWeb Applications” for more information.

l If you are deploying to WebSphere Application Server, launch EPM SystemConfigurator 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 toWebSphere Application Server.”.

Tip: If you launch EPM System Configurator from EPM_ORACLE_INSTANCE, EPMSystem Configurator configures the existing EPM Oracle instance and does not displaythe “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


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

2 Review and complete each page of EPM System Configurator, clicking or selecting Next to move to thenext 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 EPMSystem Configurator.

Page Reference

Oracle Instance “Configure Oracle Instance ” on page 113

Task selection “Task Selection” on page 114

Set Up SharedServices andRegistryDatabaseConnection

Ensure that the database is started and that you have created a database.

If you have not already created the database, see “Preparing a Database” on page 39.

Enter the information as described in “Set Up Shared Services and Registry Database Connection” on page123.

Configuredatabase

Ensure that the database is started and that you have created a database.


Enter the information as described in “Configure Database” on page 115.

Applicationserverdeployment

Enter the information as described in “Deploy to Application Server: Oracle WebLogic” on page 119.

Product-specificconfigurationtasks

For detailed procedures to configure each product, see the sections:

l “Foundation Configuration Tasks” on page 121

l “Performance Management Architect Configuration Tasks ” on page 130

l “Essbase Configuration Tasks” on page 130

l “Reporting and Analysis ConfigurationTasks” on page 135

l “Planning Configuration Tasks” on page 136

l “Financial Management Configuration Tasks” on page 137

l “Performance Scorecard — Configure Attachment Files Location” on page 145

l “Strategic Finance Configuration Tasks” on page 145

l “Financial Close Management Configuration Tasks” on page 146

l “FDM Configuration Tasks” on page 148

3 (Optional) To save the configuration selections in a response file for silent configuration, click or selectSave, 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 silentconfiguration. See “Performing Silent Configurations” on page 148.

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

Configuring EPM System Products 111

EPM System Configurator displays the status of the configuration process.

Configuration time depends on the products and tasks that you selected. Progress is recordedin EPM_ORACLE_INSTANCE/diagnostics/logs/config/configtool.log.

When configuration finishes, the status of each task is displayed. Configuration results arenoted 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 configurationtasks.

6 Configure the Web Server last.

7 Click or select Finish.

If configuration is successful, perform any required manual configuration tasks, startservices, 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 theInstallation 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 errormessages 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 ConfigurationTroubleshooting Guide for information about resolving configuration issues.

l If you see errors related to the Oracle HTTP Server installation, ensure that you havemet the Oracle HTTP Server installation prerequisites. See “Web Server InstallationPrerequisites” on page 76.

l If Oracle Configuration Manager is not available during configuration, EPM SystemConfigurator shows that the “Configure Oracle Configuration Manager” task failed.When the Oracle Configuration Manager is available, restart EPM System Configuratorand select the “Configure Oracle Configuration Manager” task.

8 Refresh EPM Workspace.

If you are using Financial Close Management, see the “Financial Close Management (CloseManager and Account Reconciliation Manager) Installation Checklist” on page 69 for theprocess to follow next.

Refreshing EPM WorkspaceIf you deploy any additional products, reconfigure the Web Server and then restart it (or simplyrestart it if you configured Oracle HTTP Server to a shared drive) on each machine hostingFoundation Services.


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 isavailable, 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 (componentsthat can change during run-time) in the EPM Oracle instance directory. The default EPM Oracleinstance location is MIDDLEWARE_HOME/user_projects/epmsystem1.

EPM System Configurator Task Reference 113

Typically, if you are installing all products on a single machine, for the first product youconfigure, create a new EPM Oracle instance. For each product after that, modify the existingEPM Oracle instance.

If you are installing in a distributed environment, create a new EPM Oracle instance on eachmachine.

You can scale up or scale out by installing and configuring additional instances. See the OracleEnterprise Performance Management System Deployment Options Guide.

The following table describes options for EPM Oracle Instance configuration.

EPM SystemConfigurator

Description YourInformation

Home directoryfor EPM Oracleinstances

Specify the directory in which to create the EPM Oracle instance. The default EPM Oracle instancelocation is MIDDLEWARE_HOME/user_projects. To modify an existing EPM Oracle instance,browse to the EPM Oracle instance location.

EPM OracleInstance name

Specify a name for the EPM Oracle instance. The default EPM Oracle instance name isepmsystem1. 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 selectall 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 youconfigure any component of a product, such as Shared Services registration. EPM SystemConfigurator uses the Shared Services Registry to locate Shared Services.

l The EPM Workspace Java web application and the Shared Services Java web application aredeployed when you select the Hyperion Foundation Deploy to Application Server task.


Configure Database

ä Specify the database settings to use for the products that you selected on the Task Selectionpage. You can specify database connection information for each product separately, or usethe same settings for multiple selected products.

For ease of deployment and simplicity, for a new installation, you can use one database for allproducts. In some cases, you might want to configure separate databases for products. Considerperformance, roll-back procedures for a single application or product, and disaster recoveryplans. Oracle recommends that Close Manager and Account Reconciliation Manager use thesame 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 doesn’t support it. Inthis case, configure this product separately. See the Oracle Enterprise PerformanceManagement System Certification Matrix (http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html) for a list of supporteddatabases for each product.

l If you are configuring an additional instance of Financial Management, PerformanceManagement Architect, or FDMEE for scaleout purposes, during database configuration,when you are prompted whether to drop and re-create the tables or reuse the existingdatabase, select Reuse the existing database.

l If you are configuring an Oracle database, EPM System Configurator checks that thedatabase 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 releasenumber.

l If you are upgrading, and you have been using Oracle Hyperion Business Rules, you mustperform prerequisite tasks for migrating business rules before you configure. See “BusinessRules Maintenance Release and Upgrade Installation Prerequisites” on page 211. EPMSystem Configurator migrates the rules to Calculation Manager rules during databaseconfiguration. The rules are exported to EPMData/planning/hbrRules.xml.

The following table describes options for database configuration.







EPM SystemConfigurator Fields


Database Type Select the database type.

Upgrade the existingdatabases to the currentrelease from...

Upgrade Note!

If you are upgrading from an earlier release, select “Upgrade the existing databases to thecurrent release from...” and then select the release.

Note: This task assumes that you have created the database. If you have not created adatabase, see “Preparing a Database” on page 39

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

Service Name or SID, orDatabase Name

For each product, specify the name of the database.

If you are using an Oracle RAC database, specify the RAC service name.

During configuration of Financial Management with Oracle Database, EPM SystemConfigurator configures Financial Management to use the Oracle Database clients that wereinstalled with EPM System Configurator and updates the tnsnames.ora entry using a fixedname.

User Name For each product, enter the database user name.

Password For each product, enter the database user password.

Advanced databaseoptions for selected rows(Optional)

Click or select to specify additional information for selected products. See “Advanced Optionsfor Database Configuration (Optional)” on page 117.

You can use this option to configure Oracle RAC or to use an LDAP-based JDBC URL. Anyvalues you enter on the Advanced Database Options page override the values entered onthe main Database Configuration page.

When you configure EPM System products to use a database, EPM System Configurator ensuresthat the database is connected and is a supported database type. For a list of supported databasesfor 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 SQLServer database. See “Setting Up Microsoft SQL Server Windows Authentication” on page116.

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.




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 ofEPM System Configurator, in Run Windows Services as non-local system account. See “ConfigureCommon Settings” on page 121.

Advanced Options for Database Configuration (Optional)The following table describes advanced options for database configuration.



Edit and use modifiedJDBC URL

Select to specify a JDBC URL for the database connection.

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

For an Oracle database, you can enter an LDAP-based JDBC URL.

See Appendix B, “JDBC URL Attributes” for more information.

Use secure connection tothe database (SSL)

Select to enable secure communication to the database.

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 ConfigurationGuide to see whether selecting this option is appropriate for your SSL implementation.

Trusted Keystore Enter or browse to the location of the keystore.

Trusted KeystorePassword

Enter the password for the keystore.

For Oracle

Data Tablespace Enter the name of an existing tablespace used to store table data. The data tablespace isthe 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 indexlocation.


Deploy to Application Server — Specify WebLogic DomainInformation

ä Specify information about the WebLogic domain to which to deploy the Java webapplications.

You deploy all EPM System products to one domain.

Note: If you are using Financial Close Management, EPM System and Oracle SOA Suite mustbe deployed to the same domain. If you have already configured Oracle SOA Suite, deployEPM System products to the same domain.

If you are deploying EPM System products to a domain hosted on another machine andthe domain was not created with EPM System Configurator, you must make manualupdates to jps-config.xml and system-jazn.xml on the Administration Server box.See step 19 on page 155 and step 20 on page 159 of Chapter 7, “Manually DeployingEPM System Java Web Applications.”

The following table describes options to define the WebLogic Server domain.

EPM System Configurator Fields Description YourInformation

Deploy Web applications to anexisting domain/Deploy Webapplications to a new domain. TheAdministration Server for thisdomain will be created on thismachine.

Specify whether to deploy Java web applications to an existing domain or to a newdomain.

If you create a new domain, the WebLogic Administration Server for this domainis created on this machine.

Domain Name To define a new domain, enter a domain name. The default domain name isEPMSystem.

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 doesnot conflict with other applications installed on your machine.

Administrator User Enter the Administrator user name for the domain. By default, EPM SystemConfigurator 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.


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

Deploy all EPM System products to a single WebLogic domain. The exceptions to thisrequirement are documented in “Deploying Financial Management, Financial Reporting, andWeb Analysis on Windows in a UNIX-Based EPM System Deployment ” on page 151.

EPM SystemConfiguratorFields


Deploy the webapplications to asingle managedserver

Select this option for a deployment to a single managed server.

If you select this option, all selected Java web applications are deployed to a single managedserver in WebLogic.

This option is available only:

l When you are creating a new domain or extending an existing domain created in EPM SystemConfigurator 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 anexisting single managed server.

l When you are applying a maintenance release installation, unless you deployed to a singlemanaged server in the earlier release, you must redeploy the Java web applications on allmachines in the deployment. Then, you can restart EPM System Configurator and select thisoption.

To add products to a single managed server on a machine other than the machine hostingFoundation Services, select Scale out compact server on this machine.

Deploying Java web applications to a single managed server reduces memory requirements andreduces 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 allports 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 ServerName

Displays the WebLogic Managed Server name.

Port Accept the default port; or, to change the default, enter a port number that does not conflict withother applications installed on your machine.

See Appendix A, “ Ports.”




SSL Port Accept the default port or specify the SSL port to use for deployment. Specifying this port sets upSSL using the Java application server's default certificates. See the Oracle Enterprise PerformanceManagement System Security Configuration Guide for recommendations on updating the Javaapplication 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 Javaapplication 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 Javaweb applications do not communicate with the Java web application server directly, as inthe 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 125.

l By default, EPM System Configurator deploys 32-bit binaries to 32-bit application serverson 32-bit operating systems, and 64-bit binaries to 64-bit application servers on 64-bitoperating systems.

l The EPM Workspace Java web application and the Shared Services Java web application aredeployed 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 ManagementSystem Security Configuration Guide for detailed procedures to implement a customauthentication module.

What Happens During Deployment: WebLogic ServerDeployment notes:

l EPM System Configurator deploys each application to the WebLogic Server domain youspecified. 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 multipleJava 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 itdeploys the first Java web application.


l Start and stop scripts are created in EPM_ORACLE_INSTANCE/bin/.

l For each application, in EPM_ORACLE_INSTANCE/bin/deploymentScripts there is asetCustomParamsProduct.bat file (.sh extension for UNIX), where you can changeJAVA_OPTIONS when using start scripts.

l EPM System Configurator creates a cluster for each managed server.

Foundation Configuration Tasks

Subtopics


l Set Up Shared Services and Registry Database Connection

l Configure Logical Address for Web Applications


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 SharedServices 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 applyfor 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 Servicesfor configuredcomponents (Windowsonly)

Select to configure each service as a Windows service that starts automatically when youstart Windows.




Run Windows Servicesas non-local systemaccount

Select to specify a non-local system account to configure Windows services, and then specifya user name and password. This user should be a member of the Administrators group.

Note: Oracle recommends that you select this option. If you are using Reporting and Analysisin 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 thelocal system account. Before you start the services, change them to use the appropriatedomain 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 Webapplication servercommunications(requires manualconfiguration)

Depending on your SSL implementation, select to use SSL communication for all Java webapplications. If this option is selected, URLs are in the form https.

Note: Selecting this option does not enable secure communication for the Java webapplication server and does not create and load certificates into JREs and JDKs. See OracleEnterprise Performance Management System Security Configuration Guide for moreinformation.

Optionally, you can deploy non SSL and reconfigure to use SSL. See the Oracle EnterprisePerformance Management System Security Configuration Guide.

Mail Server Host For products that integrate an e-mail feature, which uses standard Simple Mail TransferProtocol (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 tocommunicate with the mail server, enter an SSL port.

Administrator's EmailAddress

Specify the administrator's e-mail address to use for notifications.

Use SSL to communicatewith mail server

Select to use SSL communication for all e-mail communication.

Use authentication tosend email

Specify whether the mail server requires authentication, and then specify a user name andpassword.

User Name Specify the user name for the SMTP server.

Password Specify the password for the SMTP server.




LCM Export ImportLocation

Enter the location from which to export and import Lifecycle Management artifacts.

If you have a clustered environment and plan to use Lifecycle Management to migrateartifacts, specify a shared drive location. The shared location must be accessible to all SharedServices instances. When artifacts are exported using Lifecycle Management, the content isexported to a path on a shared disk; when imported, the content is read from the exportedlocation 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 whohas 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 byFoundation Services, which includes the Shared Services Registry.

When you configure the Shared Services and Registry database, EPM System Configuratorensures 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 databasewas 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 SystemCertification 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 39.

You can use Windows Authentication for SQL Server connections if you use Microsoft SQLServer database. See “Setting Up Microsoft SQL Server Windows Authentication” on page 116.

For more information about the Shared Services Registry, see “About the Shared ServicesRegistry” on page 18.

Note: This task assumes that you have created the database. If you have not created a database,see “Preparing a Database” on page 39.

If you uninstall EPM System products and then reinstall into the same location, you cannotreuse the Shared Services and Registry database.




Upgrade Notes!

l If you are upgrading from an earlier release, select Perform first-time configuration of SharedServices 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 touse one database, you are alerted that pre-existing Shared Services tables have been detectedin 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, orRelease 11.1.2.2 to Release 11.1.2.3, select Connect to a previously configured SharedServices database.

The following table describes options for Shared Services and Registry Database configuration.



Connect to a previouslyconfigured SharedServices database/Perform first-timeconfiguration of SharedServices database

When you first configure the Shared Services and Registry database, choose Perform first-time configuration of Shared Services database. This database includes the SharedServices Registry, which is used to store common information for all products.

When you configure in a distributed environment, you must configure the Shared Servicesdatabase on every machine. On the first machine, you are setting up the Shared ServicesRegistry. For configurations on subsequent machines, choose Connect to a previouslyconfigured Shared Services database. In this case, you are letting the machine know thelocation 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 ofShared 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, orRelease 11.1.2.2 to Release 11.1.2.3, select Connect to a previously configured SharedServices 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 becreated.

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

Service Name or SID, orDatabase Name

Specify the name of the Shared Services database.

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.




Advanced options(Optional)

Click or select to specify additional information.

For more information on these options, see “Advanced Options for Database Configuration(Optional)” on page 117.

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 toaccept the defaults:

Use this option to change the logical address for a deployed Java web application, for exampleif you are using a load balancer. This task lets you change the logical address without redeployingthe 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 webapplications.



Set the logicalWeb address forall the Webapplications to /Set the logicalWeb address foreach Webapplicationindividually to

Select whether to apply the same address to all Java web applications or to apply a different addressto each Java web application

ProductComponent

Shows the components for which a Java web application is deployed

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. Theport 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 yourJava application server after configuration to ensure secure communication.




Context Review the context path. The context path is the part of the URL that accesses the deployed Javaweb 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 OracleConfiguration Manager.

Oracle Configuration Manager collects machine configuration information and installed Oraclesoftware information on a regular basis and uploads it to My Oracle Support. Click or selectView Details for more information.

EPM System Configurator displays this page on the first machine you configure and uses thevalues for each additional machine in the deployment.

If you want to change the options or update the password, use the Oracle ConfigurationManager 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 Supportpolicies.

I wish to receive security updates via MyOracle Support

Specify whether you want to receive security updates.

My Oracle Support password Enter your My Oracle Support password.

Note: EPM System Installer installs Oracle Configuration Manager for you inEPM_ORACLE_HOME/ccr.

For more information about Oracle Configuration Manager, see http://docs.oracle.com/cd/E24625_01/index.htm.


http://docs.oracle.com/cd/E24625_01/index.htm

http://docs.oracle.com/cd/E24625_01/index.htm

Set up Connection to Oracle BI EE and PublisherUse this task for integrating EPM Workspace with Oracle BI EE Release 10.1.3.4.2+. Beforeperforming this configuration task, see the Oracle Enterprise Performance Management SystemDeployment Options Guide for prerequisite tasks and manual configuration tasks.

To integrate EPM Workspace with Oracle BI EE Release 11.1.1.7, see “Configuring forIntegration with EPM Workspace” in the Oracle® Fusion Middleware System Administrator'sGuide 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 andBI Publisher.

You must reconfigure the Web server after you perform this task. If the Web server is on thismachine, select Configure Web Server at the same time you select Connection to Oracle BI EE andPublisher.

The following table describes options for configuring EPM Workspace to work with Oracle BIEE and BI Publisher.

EPM System ConfiguratorFields

Description Your Information

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 thedeployed 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 thedeployed 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 enablesyou to log on to Shared Services after configuration to create and provision users. EPM System




Configurator requires you to specify a new admin password during configuration. Afterconfiguration, make subsequent changes to the admin user password in the Shared ServicesConsole. See the Oracle Enterprise Performance Management System Security ConfigurationGuide.

The following table describes options for resetting the Shared Services admin user password.



Admin Name Optionally, specify a name other than the default name admin for the Shared Servicesadministrator 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 MachineIf you have deployed EPM System Java web applications to a single managed server, use thisoption to scale out the server.

The Scale out compact server on this machine option is only available when the following aretrue:

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 ManagementSystem 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 SharedServices 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 simplyrestart it if you configured Oracle HTTP Server to a shared drive) on each machine hostingFoundation Services.

Then, refresh EPM Workspace on each Foundation Services host machine in your deployment.

See “Refreshing EPM Workspace” on page 112.

Note: Enabling SSL for the Web server requires manual configuration. See the Oracle EnterprisePerformance Management System Security Configuration Guide.


The following table describes options for the Web server configuration.



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 163 for details on manually configuring aWeb server.

Web Server Port Specify the Web server port. If you use SSL, ensure that the port number that you enter is a secureport.

HTTP ServerLocation

Specify or browse to the location of the Web server.

If you are using Oracle HTTP Server, you can configure to a shared drive location to simplifyconfiguration in a distributed environment. Click Advanced Options and then specify the shared drivelocation. This shared location must be accessible from all web servers in the deployment and musta UNC path, not a mapped drive.

Note: If you are deploying components to both Windows and UNIX, and if Oracle HTTP Server is onboth, you cannot configure to a shared drive; you must configure to a local drive.

Set the logicalweb address forthe webapplications tothis web server

Select this option if you want EPM System Configurator to set the logical Web address for all Javaweb applications to the Web Server. Use this option if you want to use the Web server as the loadbalancer.

If you do not select this option, EPM System Configurator uses the address of the physical Java webapplication as the logical address.

Component Review the components for which the Web server is being configured.

Foundation Services — Import Data From Earlier ReleaseThis 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 releaseto complete this task.

Upgrade Note!

ä If you are upgrading from an earlier release, specify the location from which to import SharedServices data. You must specify the full path to hssmigratedata.zip, which is createdwith the Shared Services Upgrade Utility.

If you have not yet exported Shared Services data from the earlier release, see “Exporting SharedServices Data from the Earlier Release” on page 213.

Select this task only if you also select or have already completed the “Deploy to ApplicationServer” task for Foundation Services.

For more information about what happens during this configuration task, see “What HappensDuring Shared Services Data Import” on page 231.


Performance Management Architect Configuration Tasks

Configure Dimension Server

ä Specify the following options to configure Dimension Server ports, or click or select Next toaccept 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 thedefault 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 Essbaseapplication directory. The default location might not be correct.

During configuration, if you do not select “Essbase in Standalone mode,” EPM SystemConfigurator automatically registers Essbase with Shared Services and writes the Shared Servicesconnection information to essbase.cfg (in ARBORPATH/bin). In addition, it specifiesenvironment variables in a file used to launch Essbase Server.

The following table describes the configuration options for Essbase Server.


Table 21 Essbase Server Configuration



Essbase ClusterName

Specify a cluster name to create a cluster to provide active-passive Essbase failover support withwrite-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. Whenyou configure the second instance of Essbase on the second machine, select Assign to ExistingCluster, select the cluster, and then click OK to add this Essbase Server to the cluster you createdon the first machine.

The Essbase cluster name must be unique in a deployment environment. It cannot contain specialcharacters or spaces.

See “Configuring Active-Passive Essbase Clusters (Windows)” or “Configuring Active-PassiveEssbase Clusters (UNIX)” in the Oracle Enterprise Performance Management System DeploymentOptions Guide.

Agent Port Number Accept the default port number on which the Essbase listens for client requests. If you change thedefault 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 PortNumber

Specify the SSL port on which Essbase listens for client requests.

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 forclient 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 needa larger port range.

Full path toapplicationlocation(ARBORPATH)

The location for applications.

You can specify the path using universal naming convention (UNC) format. Oracle recommendsusing UNC if you are configuring Essbase for high availability on UNIX.

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 driveor a UNC path. When you configure the second machine in the cluster, the location must match thelocation 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 replicatedlocation of the Essbase application directory. The default location might not be correct.




Set the language tobe used byEssbase(ESSLANG)

The ESSLANG variable is a locale definition. For example, to support American English, set ESSLANGto English_UnitedStates.Latin1@Binary.

Based on the value you specify, EPM System Configurator updates setEssbaseEnv.bat (inEPM_ORACLE_INSTANCE/EssbaseServer/essbaseserver1/bin) with the ESSLANGvalue and Essbase uses this value.

Verify the operating system locale setting on your computer and select the matching ESSLANGvalue. The ESSLANG setting for a computer must agree with the locale setting of the computer’soperating system.

In addition, on a Windows machine, the ESSLANG value and the system locale must match thelanguage of the Planning application that you plan to take offline.

You must choose the correct ESSLANG setting for Essbase products to start successfully. TheESSLANG 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 installedEssbase), the current value is selected by default.

On UNIX platforms, the ESSLANG setting defaults to English (Latin I) regardless of thesetting in the operating system.

For more details about ESSLANG, see “ESSLANG Variable” on page 132.

For the full list of supported ESSLANG values, see Oracle Essbase Database Administrator'sGuide.

Deploy Essbase instandalone mode

Select to use legacy security for Essbase Server instead of Shared Services security.

This option is not available if you use the -forceRegistry option to start EPM SystemConfigurator.

ESSLANG Variable

Each Essbase Server installation requires that you set an ESSLANG value. See the topic onmanaging file encoding in the Oracle Essbase Database Administrator's Guide.

The default value for ESSLANG is English (Latin1). For examples of ESSLANG values fornon-English languages, see the list of supported locales in the Unicode-mode applications topicin the Oracle Essbase Database Administrator's Guide.

During configuration, EPM System Configurator writes the ESSLANG value that you specify tothe 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 ESSLANGvalue; 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 valueof an application for as long as that application is in use.


Note: If the ESSLANG variable is changed after applications are created on an Essbase Servercomputer, those applications cannot be started.

To avoid possible database corruption, the ESSLANG locale specification must be the same onclient 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 EssbaseServer 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 whena Unicode-enabled client views and updates an outline belonging to a Unicode-modeapplication.

For products that use Essbase RTC in a non-English environment, you must set ESSLANGmanually on the client.

Configure Essbase Integration ServicesThis configuration task adds the Integration Services start script to the single EPM System startscript; however, no EPM System Configurator pages appear, and you need not enter information.

ä Select Configure Essbase Integration Services from the Task Selection page and proceedthrough EPM System Configurator.

Configure Essbase Studio Location for Sample and Customer Data SourceText Files

ä Specify the location to be used for sample file installation or for text files that will be usedas data sources, or click or select Next to accept the default.

The following table describes options for Essbase Studio Location for Sample and CustomerData Source Text Files configuration.



Server datafilelocation

Specify the location to be used for sample file installation or for text files that will be used as datasources. 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 locationfor the Essbase Studio data files.


Administration Services Import Data From Earlier ReleaseThis option is available only if you are upgrading from an earlier release. If you are not upgrading,skip this section. You must have already prepared data from the earlier release to complete thistask.

Upgrade Note!

ä If you are upgrading from an earlier release, specify the location from which to importAdministration Services data.

If you have not yet prepared data from the earlier release for upgrading, see “Copying Files forTemporary Use During Configuration” on page 215.

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

Provider Services Import Data From Earlier ReleaseThis option is available only if you are upgrading from an earlier release. If you are not upgrading,skip this section. You must have already prepared data from the earlier release to complete thistask.

Upgrade Note!

ä If you are upgrading from an earlier release, specify the location from which to importProvider Services data.

If you have not yet prepared data from the earlier release for upgrading, see “Copying Files forTemporary Use During Configuration” on page 215.

This task is available only if you also select or have already completed the “Deploy to ApplicationServer” task for Provider Services.

During configuration, this data is moved to the Shared Services Registry and the files are nolonger used.


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 FinancialManagement “Configure DCOM” task.

Configure Reporting and Analysis Framework Services

ä Specify the following Reporting and Analysis Framework service information, or click orselect Next to accept the defaults:

The following table describes options for Reporting and Analysis Framework Servicesconfiguration.



RepositoryDirectory

Specify the directory where the Reporting and Analysis repository data is stored; for example: EPM_ORACLE_INSTANCE/ReportingAnalysis/data/RM1.

If you are configuring for high availability, the repository directory must be a writable shared drive. AllReporting 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 mappeddrive. Doing so prevents potential permissions errors than can occur when Windows attempts to createa mapped drive at startup.

Upgrade Note!

If you are upgrading from an earlier release, specify the existing location or the replicated location forthe 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 selectNext to accept the defaults.

The following table describes options for Interactive Reporting service configuration.




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 clickor select Next to accept the defaults.

The following table describes options for Financial Reporting RMI port configuration.



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 orselect Next to accept the defaults.

The following table describes options for Reporting and Analysis Framework Agent portconfiguration.


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 ReportingThis task creates shortcuts for Production Reporting; however, no EPM System Configuratorpage appears, and you need not enter information.

ä Select SQR Production Reporting from the Task Selection page and proceed through EPMSystem Configurator.

Planning Configuration Tasks

Configure Planning RMI Server


ä Specify the following options to configure the Planning RMI Server port, or click or selectNext 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 FinancialManagement.

Financial Management — Configure DCOM

ä Specify the Distributed Component Object Model (DCOM) account information toconfigure DCOM security.

You must specify the Windows administrator under whose identity the application serverprocesses are launched. Perform this task on the machines that host the Financial ManagementWeb server tier and on the Services tier.

Note: You must run as a Domain or Local Administrator with Group Policies rights to configurethe DCOM user.

Because all Financial Management application server processes are run under an administratoridentity (the specified Windows admin user), no other administrator is required to log on to theapplication server to start the application server processes.

The following table describes options for Financial Management DCOM configuration.




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 consistsolely 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 theuser 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 systemdoes 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 mustlog off and log on again to commit the changes.

Re-typePassword

Enter the password again to confirm it.

Enable DCOMon this machine

Select to enable DCOM on this machine.

This option is available for the Application services and Web tier installation of Financial Management.This option is not available if DCOM is already enabled on the computer.

This option enables DCOM for the entire computer. Enabling DCOM makes possible the launching ofservers and connecting to objects by remote clients for the machine. It also sets the DCOM DefaultAuthentication level for Windows 2003 to None and for Windows 2008 to Connect. The Enable DCOMstep is required for Financial Management client components to communicate with FinancialManagement 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 differentdomains.

After you enter the Windows administrator information, EPM System Configurator performsthese steps:

l Creates the Windows admin user (DCOM user) on the local machine if the user does notexist

l Adds the user to the local Administrators group. The Financial Management administratoruser or group must be a member of the local Administrators group on each applicationserver.

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 eachFinancial 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 andpassword, 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 Webtier 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 serverconfiguration.



Max App ServerDelay

Accept the default value or enter the time interval in seconds between when a change is madeto an application and when the change is visible to users accessing the application throughanother application server.

Max Data SyncDelay

Accept the default value or enter the time interval in seconds between when a change is madeto data and when the change is visible to users accessing the data through another applicationserver.

DatabaseConnection PoolSize

Specify the number of maximum pooled relational database connections for the application.Financial Management requires approximately 25 relational database connections perapplication.

For more information about pooled database connections, see Appendix C, “DatabaseInformation 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 theservers to be transparently maintained while applications remain available for users.

The following table describes options for Financial Management cluster configuration.




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 directall 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 SystemConfigurator creates a default cluster.

You must use cluster names that are the same as the instance names that were used for FinancialManagement configuration in the earlier release.

AvailableServers

Select the server that you want to include in the cluster, and click or select Add.

The list displays all available servers. If there is only one server, it is listed here. Servers already in acluster are not available and are not listed.

Servers in theCluster

The list displays all servers in the currently selected cluster. To remove a server from the list, select itand click or select Remove.

Upgrade Note!

If you installed the upgraded version on a new server, make sure to add the upgraded server nameto the cluster and remove the earlier release server.

If you use multiple application servers connected to one database server, you must ensure thatthe 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 onsystem time. Changing the clock can affect this synchronization. For the time change toand from Daylight Savings Time, Oracle recommends that you stop the servers before thetime 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 selectNext to accept the default.

Financial Management ASP.NET Web service is deployed as part of Financial Management WebServer configuration.

The following table describes options for Financial Management Web server configuration.




Configure IIS for FinancialManagement WebApplication

Select to enable Financial Management as an IIS web application in IIS, and thenspecify the options for the Financial Management Web server. See “FinancialManagement — Configure Web Application” on page 141.

Configure IIS to Enable SmartView Provider

Select to enable Smart View as an IIS web application in IIS, and then specify theoptions for the Smart View Web server. See “Financial Management — Enable SmartView Provider” on page 142.

Configure IIS to EnableLifecycle Management

Select to enable Lifecycle Management as an IIS web application in IIS. See “FinancialManagement — Enable Life Cycle Management Provider” on page 142.

Configure IIS to FinancialManagement Web Services

Select to enable the Financial Management Web Services IIS web application in IIS.See “Financial Management — Enable Web Services” on page 143.

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

The following table describes options for Financial Management Web application configuration.



Web ServerInstallation Directory

Accept the default or enter or browse to the path for the Financial Management Web installationdirectory.

Note: The default location is the directory in which the Web components were installed; forexample: EPM_ORACLE_HOME/products/FinancialManagement/Web/HFM.

Virtual DirectoryName

Accept the default or enter the virtual directory name; for example: HFM.

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

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




Max Upload FileSize

Enter a maximum size for loading Web files.

If you use IIS 6.0, you can set the ASP file size properties for loading and extracting files on the Web.Oracle recommends that you use the default file size properties unless you experience problemsduring loading and extracting. However, if you load or extract huge files and send large amounts ofdata 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 uploadfile size is set too low. In this case, you must increase the maximum file size. You enter the file sizein bytes, so if you expect to load files of 200 MB, you change the setting for maximum upload filesize to 200,000,000 bytes.

Response BufferSize

Enter a maximum size for extracting Web files.

Financial Management — Enable Smart View Provider

ä Configure the Web server for Smart View.

The following table describes options for Financial Management Smart View Providerconfiguration.




Enter the location in which Smart View was installed or use the default location.

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 ServerConfiguration Advanced Options” on page 143.

Financial Management — Enable Life Cycle Management Provider

ä Configure the Web server for Lifecycle Management.

The following table describes options for Financial Management Lifecycle Managementconfiguration.




Web Server InstallationDirectory

Enter the location in which Lifecycle Management was installed, or use the default location.

Note: The default location is EPM_ORACLE_HOME/products/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 “WebServer Configuration Advanced Options” on page 143.

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.




Enter the location in which Financial Management Web Services was installed, or use thedefault location.

Note: The default location is EPM_ORACLE_HOME/products/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 Servicesconfiguration. See “Web Server Configuration Advanced Options” on page 143.

Web Server Configuration Advanced Options

ä Specify additional options for the Smart View, Lifecycle Management, and FinancialManagement Web Services Web server configuration.

The following table describes the advanced options for Smart View, Lifecycle Management, andFinancial Management Web Services Web server configuration.




Max Upload File Size(Web services only)

Enter a maximum size for loading Web files.

If you use IIS 6.0, you can set the ASP file size properties for loading and extracting files onthe Web. Oracle recommends that you use the default file size properties unless youexperience problems during loading and extracting. However, if you load or extract huge filesand send large amounts of data to the browser and experience errors, you can change thefile size settings.

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

Response Buffer Size(Web services only)

Enter a maximum size for extracting Web files.

Enable HTTPCompression

Specify whether to enable compression for communication between the Web browser andthe Web application.

By default, compression is on.

Enable Proxy ServerKeep Alive

If you use a proxy server between the Web server and client, select this option and set a timeinterval, in seconds, for the connection.

Keep Alive Interval (inseconds)

If you use a proxy server between the Web server and client, select this option and set a timeinterval, in seconds, for the connection.

Always warn when clientversion is newer (SmartView Provider only)

Select to warn of a newer add-in version.

Always force client toupgrade (Smart ViewProvider only)

Select to upgrade to the latest add-in version to ensure client and server version compatibility.

Financial Management Upgrade Applications from Earlier ReleaseThis option is available only if you are upgrading from an earlier release. If you are not upgrading,skip this section.

Upgrade Note!

ä Select Upgrade Applications from Earlier Release from the Task Selection page and proceedthrough EPM System Configurator.

Note that there is no EPM System Configurator page for this task and you need not enterinformation.

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 Managementapplications from the earlier release to the current release.


Performance Scorecard — Configure Attachment FilesLocation

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



PerformanceScorecard -Configureattachment fileslocation

Accept the default location, or specify a different directory to access Performance Scorecard files.

Files are stored in EPM_ORACLE_INSTANCE/HPS/hpsfiles but if you want to use a symboliclink or drive mapping to the storage location, enter the symbolic link name or drive map path 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 locationfor 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 acceptthe default.

The following table describes options for Strategic Finance configuration.



Data DirectoryLocation

Accept the default, or specify the location for Strategic Finance data.

Upgrade Note!

If you are upgrading from an earlier release of Strategic Finance, specify the existing locationor the replicated location of the data directory for the earlier release.

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.



Enable Web Service Select to activate the Strategic Finance Web services Application Programming Interfacefor 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 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 CloseManagement 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 settingsconfiguration.



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 informationabout supported document management systems.




Deploy to SOANote that this configuration task has a required configuration sequence.

See “Financial Close Management (Close Manager and Account Reconciliation Manager)Installation Checklist” on page 69 for more information.

ä Select Deploy to SOA from the Task Selection page and proceed through EPM SystemConfigurator. You must restart WebLogic Administration Server after completing this task.


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 thatinformation to configure the SOA email driver.

During the execution of this task, EPM System Configurator embeds information about theseproducts in the SOA component and then deploys the SOA composites:


l FDM

l Financial Reporting

Deploy to SOA for FDM EEThis task is required only if you are using Account Reconciliation Manager. The task is availableonly if you have installed and configured FDMEE.

Note that this configuration task has a required configuration sequence. See “Financial CloseManagement (Close Manager and Account Reconciliation Manager) Installation Checklist” onpage 69 for more information.

ä Select Deploy to SOA for FDM EE from the Task Selection page and proceed through EPMSystem Configurator. You must restart WebLogic Administration Server after completingthis task.


FDMEE Configuration Tasks

ä Select Register HFM Adapter from the Task Selection page and proceed through EPM SystemConfigurator.

No EPM System Configurator page appears, and you need not enter information.


FDM Configuration Tasks

Subtopics



These tasks update the Shared Services Registry with information about FDM and register FDMwith Shared Services; however, no EPM System Configurator pages appear, and you need notenter information. See the Oracle Hyperion Financial Data Quality Management ConfigurationGuide for additional information about configuring FDM.

Configure FDM Server

ä Select Configure FDM Server from the Task Selection page and proceed through EPM SystemConfigurator.

Configure FDM Web Application

ä Select Configure FDM Web Application from the Task Selection page and proceed throughEPM System Configurator.

Performing Silent ConfigurationsSilent configurations automate the configuration process so that you can configure EPM Systemproducts on multiple computers without manually specifying configuration settings on eachmachine.

To enable silent configurations, record your configuration settings in a response file. You canthen run a silent configuration from the command line, using the configuration options thatwere saved in the response file.

Note: If you are performing a silent configuration using Remote Desktop, run it using an adminconsole 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 isEPM_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 SystemConfigurator only one time. (You cannot select go back to the Product Selection pageto 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. Passwordsare 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 anetwork 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 recordconfiguration settings, during configuration, on the Configuration Confirmation page, click orselect Save, browse to a location, specify a file name, and click or select Save. The file is saved inthe same format as for silent configurations.

Upgrade Note!

Silent response files are not compatible between earlier releases and Release 11.1.2.3. If youcreated silent response files for use with any earlier release of EPM System, you must re-createthem 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 responsefiles 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 environmenthas 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 formatbut EPM System Configurator also supports unencrypted format. Oracle recommends that youchange the password properties for Database, WebLogic, and Shared Services in the silent fileto the following format:

Database Password<property name="password" encrypt="true">clearTextPasword</property>

Weblogic Admin Password in applicationServerDeployment section<property name="adminUser">epm_admin</property>

Performing Silent Configurations 149

<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 theappropriate 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 storedin the file in an encrypted format.

Setting Up Essbase in Standalone ModeIf you want to install Essbase in standalone mode (not using Shared Services), you can skip theinstallation for Foundation Services Java web applications. However, you must still configurethe Shared Services Registry database. To configure the Shared Services Registry databasewithout installing Foundation Services Java web applications, you run EPM System Configuratorfrom the command line using the –forceRegistry option. This option forces the “SharedServices and Registry Database Configuration” page to display during configuration so you canenter database details for the Shared Services Registry. EPM System Configurator populates thedatabase with tables for the Shared Services Registry, but not for Foundation Services.

ä To configure the Shared Services Registry without installing Foundation Services Java webapplications:

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

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 andthen enter ./configtool.sh —forceRegistry.

The –forceRegistry option also works with EPM System Configurator in silent modeand 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 EPMSystem DeploymentAll Java web applications in an EPM System deployment must be deployed on either all Windowsmachines or on all UNIX machines. However, if your Java web applications are deployed onUNIX, you must deploy Financial Management, Financial Reporting, and Web Analysis Javaweb applications on Windows using EPM System Configurator, deploying to a separate domainon Windows. This is required because Financial Management runs only on Windows, andFinancial Reporting and Web Analysis support Financial Management as a data source only onWindows.

What Happens During ConfigurationDuring 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 configureFoundation Services. This is the only preprovisioned user created. Subsequently, when youuse EPM System Configurator to register products with Shared Services, the Shared ServicesAdministrator role is provisioned with the product administrator role.

l If you are configuring products on Windows 2008 that require IIS, EPM SystemConfigurator automatically installs Windows server roles for IIS if they are not alreadyinstalled. On Windows Server 2003, you are prompted for the installation CD or the pathto Windows Server 2003 files to install the required IIS files.

Troubleshooting ConfigurationConfiguration 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 ConfigurationTroubleshooting Guide for information about configuration checks, debugging using logs,troubleshooting methodology, and solutions to common configuration issues.

Deploying Financial Management, Financial Reporting, and Web Analysis on Windows in a UNIX-Based EPM System Deployment 151

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 andconfiguration issues. This tool collects all log files, including logs for installation,configuration, and validation and registry reports if you have used those tools, and savesthem in ZIP file in EPM_ORACLE_INSTANCE/diagnostics/ziplogs.


7Manually Deploying EPM

System Java Web Applications

In This Chapter

Assumptions and Prerequisites.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Manually Deploying Java Web Applications .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Manually Configuring Oracle HTTP Server.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

For detailed information about managing Java web applications with WebLogic Server, seehttp://download.oracle.com/docs/cd/E15523_01/wls.htm.

Assumptions and Prerequisitesl You are an experienced Java web application server administrator. If you are not an

experienced Java web application server administrator, you should automatically configureand 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 theenvironment.

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 configurationtasks except for the “Configure Web Server” task. Note that the “Deploy to Application Server” task isnot available.

Windows:

EPM_ORACLE_HOME/common/config/version_number/configtool-manual.bat

UNIX:

EPM_ORACLE_HOME/common/config/version_number/configtool-manual.sh

Launching EPM System Configurator with this command hides the Java web applicationdeployment tasks and skips the product registration with Shared Services task.

Assumptions and Prerequisites 153

http://download.oracle.com/docs/cd/E15523_01/wls.htm

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 toMIDDLEWARE_HOME/oracle_common/common/bin and launch config.cmd (Windows) orconfig.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 alreadydeployed EPM System products, select “Extend an Existing WebLogic Domain.”Additionally, if you are using Financial Close Management, EPM System and OracleSOA Suite must be deployed to the same domain. If you have already configuredOracle 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 EPMSystem products, the list is generated from the configuration templates that were installedduring installation with EPM System Installer.

5 Select Generate a domain configured automatically to support the following products, then selectthe 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 thenclick Next.

8 Select a WebLogic domain startup mode (Development or Production), specify which JDK to use, andthen 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 enteredduring database configuration with EPM System Configurator.

If you configured different databases for different products, enter database connectioninformation separately for each Java web application. Select the Java web application, andthen 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.

154 Manually Deploying EPM System Java Web Applications

11 For Managed Servers, Clusters and Machines, on the Configure Managed Servers panel, review thedefault 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 stopscripts located in MIDDLEWARE_HOME/user_projects/domains/EPMSYstem/bin.

12 For a distributed deployment, for Managed Servers, Clusters and Machines, on the ConfigureMachines 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 canset up a cluster. You can also set up a cluster after you've completed the deployment. For details onJava web application server clustering, see “Clustering Java Web Applications in a WebLogic ManualDeployment” 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 Javaweb 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. Oneach 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 AdministrationServer, navigate to the domain location and change the current the EPM Oracle instance name (forexample, 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 andnavigate to the WebLogic Administration Console. Check that the Node Manager for each machine inthe 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 toa 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>

Manually Deploying Java Web Applications 155

<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.PolicyStoreAccessPermission</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.CredentialAccessPermission</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> <class>oracle.security.jps.service.credstore.CredentialAccessPermission</class> <name>context=SYSTEM,mapName=repository_cred_map,keyName=*</name> <actions>read,write,update,delete</actions> </permission> </permissions> </grant> <grant> <grantee> <codesource> <url>file:${EPM_ORACLE_HOME}/products/Essbase/eas/server/lib/eascsf.jar</url> </codesource> </grantee> <permissions> <permission>


<class>oracle.security.jps.service.credstore.CredentialAccessPermission</class> <name>context=SYSTEM,mapName=CSF_EAS_MAP,keyName=*</name> <actions>read,write,update,delete</actions> </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> <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(11.1.2.0)</name> <actions>assert</actions> </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=FCCTaskExecutionComposite</name> <actions>assert</actions> </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=FinancialClose</name> <actions>assert</actions> </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=FINANCIALCLOSE</name> <actions>assert</actions> </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=AccountReconciliation</name> <actions>assert</actions> </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=ACCOUNTRECONCILIATION</name> <actions>assert</actions> </permission> </permissions> </grant> <grant> <grantee>


<codesource> <url>file:${soa.oracle.home}/soa/modules/oracle.soa.workflow_11.1.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> <url>file:${soa.oracle.home}/soa/modules/oracle.soa.workflow_11.1.1/bpm-services.jar</url> </codesource> </grantee> <permissions> <permission> <class>oracle.security.jps.JpsPermission</class> <name>VerificationService.createInternalWorkflowContext</name> <actions>read,write,update,delete</actions> </permission> </permissions> </grant> <grant> <grantee> <codesource> <url>file:${soa.oracle.home}/soa/modules/oracle.soa.workflow_11.1.1/bpm-services.jar</url> </codesource> </grantee> <permissions> <permission> <class>oracle.security.jps.service.credstore.CredentialAccessPermission</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 thesechanges are also required if you deployed EPM System products to a domain hosted on another machineand 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" /> <property value="true" name="debug" /> <property value="true" name="addAllRoles" /> </serviceInstance>

Modify the existing <serviceInstances> “idstore.ldap” to add thevirtualize 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 serverin 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 allmanaged servers.

Note: Note that these inputs are stored in clear text until the servers are started, after whichthis 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"

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 inDOMAIN_HOME/bin.

You can start Java web applications on all machines using the Weblogic AdministrationConsole. 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 allmachines.

During the managed server startup, the Shared Services Registry is updated with values forthe 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_USERepmsys_registry.bat addencryptedproperty #APP_SERVER_ID/@adminPassword ADMIN_PASSWORD

Where APP_SERVER_ID is the ID of the WebLogic AppServer component in the SharedServices Registry.

For more information about editing the Shared Services Registry, see “Updating the SharedServices Registry” in the Oracle Enterprise Performance Management System DeploymentOptions Guide.

26 Launch EPM System Configurator using the following command and select the “Configure Web Server”task.

Windows:

EPM_ORACLE_HOME/common/config/version_number/configtool-manual.bat

UNIX:

EPM_ORACLE_HOME/common/config/version_number/configtool-manual.sh

EPM System Configurator performs the registration with Shared Services and ConfigureWeb Server tasks.

If you are also want to configure Essbase while you are manually deploying Java webapplications, when you first ran configtool-manual.sh, the Configure Essbase Servertask was not available. It is available in this second pass of configuration, so if needed, selectit now.


27 For Financial Close Management: Start WebLogic Administration Server and then the SOA managedserver. Then, start EPM System Configurator and select Deploy to SOA for Close Manager, and Deployto SOA and Deploy to SOA for FDM EE for Account Reconciliation Manager.

28 If you are using FDMEE, perform additional manual steps. See “Additional Postdeployment Steps forFDMEE” on page 162.

29 If you using Oracle Web Services Manager, perform additional manual steps. See “Configuring JMSServers” on page 163.

30 Start all EPM System services and Java web applications. When you manually deploy Java webapplications, use the start scripts in DOMAIN_HOME/bin.

Tip: You can also start Java web applications on all machines using the WeblogicAdministration Console. To do so, you must first run MIDDLEWARE_HOME/oracle_common/common/bin/setNMProps.sh(cmd) to modifynodemanager.properties.

To validate the installation and verify deployment, see Chapter 13, “Validating theInstallation and Verifying Deployment.”

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, replacethe 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 OracleEnterprise Performance Management System Deployment Options Guide.

Additional Postdeployment Steps for FDMEE

If you are manually deploying FDMEE, perform the following procedures after you deploy toconfigure 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") .

Where adminUser and adminPassword are the WebLogic administrator user andpassword 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 andrun 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 DeploymentIf you have deployed only some EPM System Java web applications, you can extend thedeployment by deploying additional Java web applications. For example, if you previouslydeployed Planning, you can extend the deployment to deploy Profitability and CostManagement. 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 ServerYou can choose to manually configure the Oracle HTTP Server installed by EPM System Installerinstead of configuring it with EPM System Configurator.

If you are using a supported Web server other than the Oracle HTTP Server that is installed byEPM 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 170.

l Manual configuration of IIS is not supported.

Manually Configuring Oracle HTTP Server 163

This section assumes you have already used EPM System Configurator to configure EPM Systemcomponents and deployed Java web applications manually or by using EPM SystemConfigurator.

ä To manually configure Oracle HTTP Server:

1 Launch EPM System Configurator: Change to EPM_ORACLE_INSTANCE\BIN and then launchconfigtool.bat|sh.

2 In EPM System Configurator, on the Task Selection panel, select Uncheck All, expand HyperionFoundation, select Configure Web Server, and then click Next.

3 In Configure Web Server, from Web Server Type, select Setup Registry for manual web serverconfiguration 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 HTTPServer.

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

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

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 WindowsService 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 fileEPM_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 replacesoa_server_host:soa_server_port andadmin_server_host:admin_server_port with the actual values for the SOA hostand 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 theactual value of the port on which Oracle HTTP Server is running. For example, to change the actual portto 19000:

a. Generate a registry report by launching EPM_ORACLE_INSTANCE\bin\epmsys_registry.bat. Enter the Shared Services database password whenprompted.

b. Look for the WEB_SERVER component with properties "type" = MANUAL, "port"= -1, and "instance_home" with the EPM_ORACLE_INSTANCE that is configured.

Manually Configuring Oracle HTTP Server 165

c. Look for the object id for the WEB_SERVER component, and copy it into followingcommand:

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.


8Deploying EPM SystemProducts to WebSphere

Application Server

In This Chapter

Additional Postdeployment Steps for FDMEE ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Configuring IBM HTTP Server .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Validating WebSphere Application Server Deployments ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

You can deploy EPM System Products to WebSphere Application Server using the processoutlined in this chapter. An EPM System deployment cannot deploy Java web applications toboth 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 deploymenteven 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 theWebSphere Configuration Wizard, however those steps are not included in this procedure.

l The runWASDeployment.bat|sh script supports single box configuration only. To extendthe deployment, use the Websphere Configuration Wizard. See “Extending the WebSphereDeployment” in the Oracle Enterprise Performance Management System Deployment OptionsGuide.

l If you are applying a maintenance release to move to Release 11.1.2.3 and you deployed Javaweb 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 singlemachine development environment, you can install WebSphere Application Server Base Edition.

167

In addition, install IBM HTTP Server and its required Plugins. Note that if you are deployingEPM System products that also use IIS, IIS and IBM HTTP Server have the same defaultport. 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 andReporting 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_OPTIONSstatement 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 WebSphereApplication Server, for example c:/program files/IBM/WebSphere/AppServer.

5 Copy ALBAN*.ttf from EPM_ORACLE_HOME/../jdk160_29/jre/lib/fonts toWAS_HOME/java/jre/lib/fonts.

6 Launch EPM System Configurator using the following command and perform all required configurationtasks except for the “Configure Web Server” task. Note that the “Deploy to Application Server” task isnot 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 applicationdeployment tasks and skips the Essbase product registration with Shared Services task.

If you need additional details about configuring EPM System, see “Configuring EPM SystemProducts ” on page 109.

7 Deploy the Java web applications to WebSphere by running the following script (note that you do nothave 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 SolutionsConsole, and then provide values for the script for the following parameters, or pressEnter to select the default values (default values are noted in parentheses). Specify uniquevalues 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 someconfiguration tasks.

168 Deploying EPM System Products to WebSphere Application Server

http://www-01.ibm.com/support/docview.wss?uid=swg24032493

When the deployment is done, “Configuration Complete” displays and then the windowcloses.

8 After the Java web applications are deployed, run the following scripts to start the deployment managerand 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 isEPMServer.

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, openWAS_HOME/profiles/DM_PROFILE_NAME/properties/portdef.props andsearch 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 ServerTypes, then WebSphere application servers, then select the application server to stop, and thenclick 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 startapplications only.

11 Manually configure the Web server. See “Configuring IBM HTTP Server” on page 170.

12 (Optional) For clustered Java web applications, configure the logical addresses for the Web applicationsby launching EPM System Configurator and selecting the Foundation task “Configure Logical Addressfor Web Applications” to set the logical addresses for the Java web applications' host and port to themanually configured Web Server.

13 If you are using FDMEE, perform additional tasks to configure Oracle Data Integrator. See “AdditionalPostdeployment Steps for FDMEE” on page 170.

14 Validate the deployment.

See “Validating WebSphere Application Server Deployments” on page 173.

To scale out the WebSphere deployment, see the Oracle Enterprise Performance ManagementSystem Deployment Options Guide.

Tip: Check the log files in EPM_ORACLE_INSTANCE/diagnostics/logs/config/configtool-wasdeployment.log and WAS_HOME/profiles/ApplicationServerProfileNamelogs/serverName.

169

Additional Postdeployment Steps for FDMEEIf 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 ServerAfter 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 ConfigureWeb 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, whenyou 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 makethe following changes:


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-bitSupplements also contain 32-bit Plugin binaries), you must load the correct plug-insfor your operating system type by commenting (#) or uncommenting the followinglines:

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

Include conf/epm_online_help.conf

If you want to run Help locally, comment this line. Leave the line uncommented to runHelp from the hosted Oracle server. See “Installing and Configuring Online Help” inthe Oracle Enterprise Performance Management System Deployment Options Guide.

f. Change the mod_was_ap22_http extension for your operating system: (dll forWindows, 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 IBMHTTP Server is installed. If EPM System is installed on a different machine or in

Configuring IBM HTTP Server 171

a different user home directory (for example, on UNIX), you must copy the entireInsight directory to a location accessible for IBM HTTP Server.

5 Open EPM_ORACLE_INSTANCE/httpConfig/autogenerated/ihs/plugin-cfg.xmlin 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 foryour 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: LaunchGenPluginCfg.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 informationabout physical servers.

iii. Copy the required CloneID property and its value to the appropriate server inEPM_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 thensave 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 (theWEB_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 portnumber 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 theWEB_SERVER component that has type MANUAL and port -1. For example:


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 followingcommand 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 theWebSphere Administration Console (Integrated Solutions Console) (https://localhost:port/ibm/console/login.do?action=secure). Select Environment, then Virtual hosts. Click thevirtual host that you used for EPM System products (by default it is default_host). If the port is notlisted, open Host Aliases properties and add the IBM HTTP Server port, and then click Save at the topof 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 DeploymentsTo validate a WebSphere deployment, run EPM System Diagnostics. See Chapter 13, “Validatingthe Installation and Verifying Deployment.”

Validating WebSphere Application Server Deployments 173

9Performing Manual

Configuration Tasks in a NewDeployment

In This Chapter

Essbase Manual Configuration Tasks ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Reporting and Analysis Manual Configuration Tasks ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

Financial Close Management Manual Configuration Tasks .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

FDMEE Manual Configuration Tasks... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

After configuration, you must configure user directories, provision the functional administrator,and deactivate the default administrator (admin) account. See Oracle Enterprise PerformanceManagement System User Security Administration Guide.

To set up EPM System components to work with Oracle Web Services Manager, see the OracleEnterprise Performance Management System Deployment Options Guide.

See the Oracle Enterprise Performance Management System Deployment Options Guide foradditional 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” onpage 176

Enable clients to look up Essbase by cluster name instead of URL. “Enabling Client Lookup by ClusterName” on page 176

If you are using Essbase on the Oracle Exalytics In-Memory Machine, edit Essbase.cfg toset OracleHardwareAcceleration TRUE.

Essbase Manual Configuration Tasks 175

Setting User Limits on 64-bit AIXWhen running Essbase Server on a 64-bit AIX platform, you must change the user limits toincrease 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 NameEssbase 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 clientscan use the cluster name directly instead of the URL. If you want to enable client login using thecluster name, you must first specify a property to configure Provider Services. The cluster nameis 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 ProviderServices 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 theProvider 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 installedfor the servers, and those installed for the Essbase clients.

Reporting and Analysis Manual Configuration TasksThe following table describes Reporting and Analysis postconfiguration tasks.

176 Performing Manual Configuration Tasks in a New Deployment

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 ConfigurationTasks

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

Caution! You must perform these tasks before you can start and run Financial CloseManagement. 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 youcreated the WebLogic domain, to make changes in the WebLogic Administration Consoleyou must first click Lock & Edit in the Change Center. After you make the changes, clickActivate 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 forMessage Protection” on page179

Configure the SOA Server to connect to Oracle Internet Directory, Microsoft Active Directory (MSAD),or SunOne.

“Configuring the WebLogicDomain to OID, MSAD, SunOne”on page 180

Financial Close Management Manual Configuration Tasks 177

Task Reference

Start managed servers in order. “Start Managed Servers” on page181

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 notautomatically configured, you must manually configure the SOA contexts.

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.

step 9 in “Manually ConfiguringOracle HTTP Server” on page 163

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


l For Account Reconciliation Manager:

1. Make sure there are no open periods. If there are open periods, lock them. Make sure thereare 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:


Raise the maximum capacity of the connection pool. “Raising the Maximum Capacity inthe Connection Pool” on page181

Increase the connection pool of the external LDAP provider. “Increasing the Connection Poolof the External LDAP Provider” onpage 182

If you are working in a clustered environment with Financial Close Management and SOA, to ensurethat the email password is configured for all servers, the password used to authenticate email (asentered on the “Common Settings” configuration task panel), must be of the type “Use Clear TextPassword”. To change the password type, use Enterprise Manager.

Enterprise Managerdocumentation

After performing these steps you can also configure Account Reconciliation Manager to workwith 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 OracleSupport.

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 inthe server running the WebLogic Administration Server hosting your EPM System domainand 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 mightnot 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 upthe Keystore for Message Protection” section of the Oracle Fusion Middleware Security andAdministrator'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 theEPM 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, forexample ./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 aliasand password that you used when creating the keystore. Confirm the passwords, andthen click OK. The alias and password for the signature and encryption keys define thestring 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.


http://download.oracle.com/docs/cd/E14571_01/web.1111/b32511/setup_config.htm#BABJHIBI

http://download.oracle.com/docs/cd/E14571_01/web.1111/b32511/setup_config.htm#BABJHIBI

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 andAdministrator's Guide for Web Services 11g Release 1 (11.1.1).

Configuring the WebLogic Domain to OID, MSAD, SunOneThis procedure is required to configure the WebLogic domain, or in the case of Financial CloseManagement 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. Followthe sections specific to your provider.

Note: Financial Close Management does not support Shared Services Native Directory. TheWeb services features of Profitability and Cost Management, Provider Services, FDMEE,and Financial Management do not work with Shared Services Native Directory. See theOracle Hyperion Enterprise Performance Management System User and Role SecurityGuide 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 thisprocedure.

4 Click the provider you just added, click the Provider Specific tab, enter the following details for yourprovider, and then click OK.

l Host

l Port

l Principal

l Credential


http://docs.oracle.com/cd/E17904_01/web.1111/b32511/setup_config.htm#BABHIBHA

http://docs.oracle.com/cd/E17904_01/web.1111/b32511/setup_config.htm#BABHIBHA

l User Base DB

l Group Base DB

l User from Name Filter (MSAD only)

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 you’re using FinancialManagement with Financial Close Management

m FDM Web application, if you’re using FDM with Financial Close Management

m Financial Reporting Java web application, if you’re using Financial Reporting withFinancial Close Management

m FDMEE, if you are using Account Reconciliation Manager.

l Oracle SOA managed server

Raising the Maximum Capacity in the Connection PoolIf 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

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 onthe 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 youhave exceeded the maximum connections allowed in the connection pool for the specified datasource, 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 nameof 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 TasksThe following table describes FDMEE postconfiguration tasks.

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 logicaladdress of the Java web applications (using the “Update Logical Address for Web Applications” page of EPM SystemConfigurator, 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:


FDMEE Manual Configuration Tasks 183

10Performing a Maintenance

Release Installation for EPMSystem Products

In This Chapter

Maintenance Release Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Financial Close Management Maintenance Release Installation Checklist. . . . . . . . . . . . . . . . . . . . . . . . . 186

Downloading and Extracting Installation Files.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

Performing Maintenance Release Installation Prerequisite Tasks ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

Installing and Configuring EPM System Products in a Maintenance Installation... . . . . . . . . . . . . . . . . 192

Maintenance Installation Deployments to a Single Managed Server .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

Performing Manual Configuration Tasks in a Maintenance Installation ... . . . . . . . . . . . . . . . . . . . . . . . . . . 198

Validating the Deployment and Generating a Deployment Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

Performing a Maintenance Release Installation for EPM System Clients .. . . . . . . . . . . . . . . . . . . . . . . . . . 204

If you are applying the maintenance release to move from EPM System Release 11.1.2.0, Release11.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 maintenancerelease installation.

l If you deployed Java web applications to a single managed server, you must deploy in thesame way in this release.

l If you deployed Java web applications to WebSphere Application Server, you can apply themaintenance release installation only if you used runWASDeployment.bat|sh in theprevious 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 ConfigurationWizard, 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 theinstallation and configuration sequence described in “Financial Close ManagementMaintenance Release Installation Checklist” on page 186.

Maintenance Release Installation Checklist 185

Table 26 Maintenance release installation checklist

Task Reference

Meet the system requirements.

If your database environment needs to be upgraded,perform the database upgrade before you proceed. Seethe database documentation for details.

Oracle Enterprise Performance Management System Certification Matrix(http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html)

Download and extract the installation files. “Downloading and Extracting Installation Files” on page 187

Perform the maintenance release installation prerequisitetasks.

“Performing Maintenance Release Installation Prerequisite Tasks” on page188

Install and configure EPM System products. “Installing and Configuring EPM System Products in a MaintenanceInstallation” on page 192

Perform any required manual configuration tasks for yourproducts.

“Performing Manual Configuration Tasks in a Maintenance Installation” onpage 198

Validate the installation using EPM System Diagnostics andgenerate a deployment report.

“Validating the Deployment and Generating a Deployment Report” on page203

Financial Close Management Maintenance ReleaseInstallation ChecklistThe following table provides an overview of the installation and configuration process for OracleSOA Suite and Financial Close Management if you are moving from Financial CloseManagement 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 CloseManagement 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 anOpen status.

l If you want to add Account Reconciliation Manager to your Financial Close Managementdeployment, you must first install the 11.1.2.3 Release of the Financial Close ManagementClose Manager Java web application using the Apply Maintenance Release option in EPMSystem Installer. Then, install the Financial Close Management Reconciliation Manager Javaweb Application Java web application using the New installation option in EPM SystemInstaller.

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.

186 Performing a Maintenance Release Installation for EPM System Products



Task Reference

Install Financial Close Management Release 11.1.2.3 on the machine hosting Financial CloseManagement Release 11.1.2.1 or Release 11.1.2.2.

Note: During installation, Apply Maintenance Release is selected for you. EPM System Installer selectsall available products; you must apply the maintenance release to all EPM System products in thedeployment.


Caution! After installation, do not proceed with configuring EPM System products using EPM SystemConfigurator until you have completed the following Oracle SOA Suite upgrade steps.

Before upgrading SOA Suite, back up the SOA database.

Upgrade Oracle SOA Suite components to PS6 and then apply any required patches. The following listprovides an overview of the steps:

1. Update the existing software (SOA components).

2. If you are using Microsoft SQL Server, apply patch number 16400937 for Release 11.1.1.7.0.

3. Upgrade the RCU schemas. For more information see “Starting the Patch Set Assistant” in the Oracle®Fusion Middleware Patching Guide 11g Release 1. During this step, the following schemas areupgraded: _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® FusionMiddleware Patching Guide 11g Release 1.

Oracle® Fusion MiddlewarePatching Guide 11g Release 1

Tip: Review the SOA startuplogs for any errors and resolvethe errors before proceedingwith EPM System Configurator.You can also view the status ofSOA in Enterprise ManagerConsole.

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 ReconciliationManager. including database configuration and Java web application deployment for Shared Servicesand 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 CloseManagement in the order listed.

“Financial Close ManagementApplication Server” on page314

Update product integration types by importing the Release 11.1.2.3 versions of all product integrationfiles. The product integration files are posted on My Oracle Support.

“Managing Integration Types” inthe Oracle Financial CloseManagement Administrator'sGuide.

Downloading and Extracting Installation FilesDownload the EPM System files from the “Oracle Enterprise Performance Management System”media pack on the Oracle Software Delivery Cloud (http://edelivery.oracle.com/). Oraclerecommends that you download files to a shared drive. See Chapter 4, “Downloading Files forInstallation” for details on downloading and extracting installation files.

Downloading and Extracting Installation Files 187


Performing Maintenance Release InstallationPrerequisite 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 beforeyou 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. Thistool 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 descriptionswith 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 forthe 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.1to Release 11.1.2.3, you must first export linked reporting object information from the earlier releasedatabase, and then delete the linked reporting objects. After applying the maintenance release, importthe exported linked reporting objects. See “Essbase Maintenance Release Installation Prerequisites”on page 189.

8 If you are performing a maintenance installation on UNIX and you had Financial Management on thisplatform 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 CalculationManager rules in Release 11.1.2.3. Before migrating business rules, you must perform prerequisite



tasks. See “Business Rules Maintenance Release and Upgrade Installation Prerequisites” on page190. 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 186

11 If you are using Oracle Web Services Manager with EPM System products, upgrade the OWSM MDSschema. See “Maintenance Release Installation Prerequisites if You Are Using Oracle Web ServicesManager” on page 191.

12 Stop all the services for EPM System products.

Note that you must manually stop the Integration Services service manually using the TaskManager. (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 PrerequisitesIf you are applying the maintenance release to move from Essbase Release 11.1.2.0, Release11.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 Release11.1.2.2:

1 On the machine hosting the earlier release installation, back up the application linked reporting objectdata 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 inARBORPATH/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.

Performing Maintenance Release Installation Prerequisite Tasks 189

Business Rules Maintenance Release and UpgradeInstallation PrerequisitesIf you are applying the maintenance release to move from Release 11.1.2.0 or Release 11.1.2.1to Release 11.1.2.3, or if you are upgrading from an earlier release, and if you have been usingBusiness Rules in the earlier release, you must migrate to Calculation Manager rules in Release11.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 BusinessRules 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 youmigrate business rules, you must provide the details of a specific launch location (that is, the applicationtype---Planning or Essbase, the server name, the application name, and the database or plan type). Ifyou want a business rule to be valid for multiple launch locations, you must provide the details for eachlocation. The locations must be in different applications; you cannot migrate the same business rule todifferent 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 sequencemust 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 fora specific location or locations and not “All Locations.” If multiple locations are defined for a businessrule 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: UseAdministration Services to export the rules to XML in Business Rules format. If you are upgrading fromRelease 11.1.1.4, also export the rules to Calculation Manager format. EPM System Configurator exportsthe 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 Essbaserule from Business Rules:

a. From Administration Services Console, right-click the Business Rules node and selectExport.

b. Export the rules in Business Rules format and then select all of the Essbase rules in therepository. If you are upgrading from Release 11.1.1.4, also export the rules toCalculation Manager format.

c. Specify the location to save the XML file, and then click OK. If you are upgrading, thelocation 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 whenyou perform the “Configure Database” task.

After configuration, there are additional tasks you perform to import and migrate business rules.

Financial Reporting Maintenance Release InstallationPrerequisitesIt is no longer necessary to install Financial Reporting Print Server separately as it is includedby default with the Financial Reporting Java web Application on all platforms. No separateFinancial Reporting Print Server service is created. However, before installing FinancialReporting, if you were working in Release 11.1.2.0 or Release 11.1.2.1, meet the followingprerequisites:

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 MicrosoftManagement 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_FRPRINTSERVICEHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\Application\FRPrintServiceHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\FRPrintService

l If you were working in Release 11.1.2.1:

1. Remove “Hyperion Financial Reporting - Print Service” usingFRRemovePrintServer.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\RemovePrograms (Windows XP or Windows 2003) or Programs and Features (Windows 7 orWindows 2008).

3. Delete the folder /Program Files/Oracle/FinancialReportingStudio.

Maintenance Release Installation Prerequisites if You AreUsing Oracle Web Services ManagerIf you are using Profitability and Cost Management, Financial Close Management, FDMEE,Financial Management, Provider Services or Data Relationship Management with Oracle WebServices Manager, upgrade the OWSM MDS schema and update Oracle Web Services Managerto Release 11.1.1.7.0.

Performing Maintenance Release Installation Prerequisite Tasks 191

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

l Update configurations and stores. For more information, see the Oracle® Fusion MiddlewarePatching Guide 11g Release 1.

l Update the Oracle Web Services Manager repository. See “Adding New OWSM Pre-DefinedPolicies” in the Oracle® Fusion Middleware Patching Guide 11g Release 1.

You can find Oracle® Fusion Middleware Patching Guide 11g Release 1 on the Fusion Middlewarepage of the Oracle Documentation Library. .

Installing and Configuring EPM System Products in aMaintenance InstallationWhen you apply the maintenance release, install and configure using the same user that wasused 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 youextracted the EPM System Installer files.

l (UNIX) Change to the root directory to which you extracted the EPM System Installerfiles 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 mustapply 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 toadd new EPM System products to the existing deployment, install and configure existingproducts 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 FinancialManagement 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 withOracle BI EE.

3 When installation is complete, click or select Finish.

Note: If you are installing Financial Close Management, note that it requires additional stepsbefore you configure with EPM System Configurator. See “Financial CloseManagement Maintenance Release Installation Checklist” on page 186.

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 EPMSystem 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 previouslyconfigured Shared Services database, and then review the database connection information for SharedServices Registry and the user name and password of the database account to use for accessing thedatabase.

8 In Task Selection, clear the selection (uncheck) from Uncheck All, select the top node of FoundationServices, 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 helpavoid 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 thefollowing command:

epmsys_registry.bat|.sh preview

Any errors are reported to the console but no changes are made to the Shared ServicesRegistry. If there are no errors, skip to step 12 on page 194.

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

Installing and Configuring EPM System Products in a Maintenance Installation 193




Consult with Oracle Support if the report does not match the actual configuration of yourdeployment environment.

12 Launch EPM System Configurator again: On the machine hosting Foundation Services, from the Startmenu, select All Programs, then Oracle EPM System, then EPM System Configurator (allinstances).

In a distributed environment, you must configure Foundation Services first. FoundationServices 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 previouslyconfigured Shared Services database, and then review the database connection information for SharedServices Registry and the user name and password of the database account to use for accessing thedatabase.

15 On the component configuration page, make selections as needed and then click Next. You mustcomplete all Pending tasks in EPM System Configurator.

l EPM System Configurator preselects all required configuration tasks for the productsin 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 theselection for “Configure Web Server”. Otherwise, configure the Web server after allother EPM System products have been configured.

l If you are deploying Java web applications to WebSphere Application Server, performrequired 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, theyare deployed the same way in this release. If you want to change how products aredeployed, after the maintenance deployment is complete, you can redeploy.

l You cannot configure Oracle HTTP Server to a shared drive when you apply amaintenance 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 themaintenance configuration. After the deployment is complete, you can reconfigure ifrequired to make any configuration changes.


If you need information about any of the pages, click Help, or see Chapter 6, “ConfiguringEPM System Products in a New Deployment.”

l On the Database Configuration page, you need only make changes if the databaseconnection 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 machinehosting Foundation Services, launch EPM System Configurator and select “Configure Web Server” fromthe Foundation tasks.

19 Start EPM System products. On each machine in the deployment, select Start, then All Programs, thenOracle EPM System, EPM_ORACLE_INSTANCE, then Foundation Services, and then Start EPMSystem.

20 For clients that have a new client installer in Release 11.1.2.3, applying the maintenance releaseinstallation option does not update the client software. You must install the client using the clientinstaller. See “Installing EPM System Clients” on page 89.

For Predictive Planning, note the following:

l Upgrade all Predictive Planning client versions at the same time, so that all users cansee new features.

l Administrators should make Form setup changes using the updated Predictive Planningversion. Making changes with older versions can result in loss of Form setup data.

During the maintenance configuration process for Profitability and Cost Management, StageObject Calculation artifacts from Release 11.1.2.2 applications are replaced with CalculationRules of type Calculated Measure in Release 11.1.2.3.

Maintenance Installation Deployments to a SingleManaged 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 Release11.1.2.2 to Release 11.1.2.3, see the following scenarios for additional details about deploying toa single managed server.

Maintenance Installation Deployments to a Single Managed Server 195

Note: On UNIX platforms, if you are applying the maintenance release from Release 11.1.2.1or Release 11.1.2.2 to Release 11.1.2.3 on a single managed server, the FinancialManagement Web Service must be uninstalled.

Scenario 1: You either deployed all Java web applications totheir own managed servers, or deployed all Java webapplications to a single managed server in Release 11.1.2.0,11.1.2.1, or Release 11.1.2.2This scenario assumes:

l If you deployed to a single managed server, you must have manually deployed all Java webapplications to a single managed server and did not deploy anything using EPM SystemConfigurator. (Note however that deploying to a single managed server was not supportedin 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 areapplying the maintenance release, you first deploy each Web application to its own managedserver, 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 toits own managed server. (On the "Deploy to Application Server" page, do not select Deploythe 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 hostmachine 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 webapplications to a single managed server: In EPM System Configurator, select the "Deploy toApplication Server" task for each product that you want to include in the single managedserver. On the "Deploy to Application Server" page, select Deploy the web applications to asingle managed server.


Scenario 2: You were working in a Release 11.1.2.1 orRelease 11.1.2.2 environment that had some Java webapplications deployed to a single managed server and someJava web applications deployed to their own managed serversThis scenario assumes:

l You deployed some of the Java web applications to their own managed servers in Release11.1.2.1 or Release 11.1.2.2

l You deployed some of the Java web applications to a single managed server in Release11.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 hostmachine 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 EPMSystem Configurator, select the “Deploy to Application Server” task for any one of the Javaweb applications that was deployed to a single managed server, and select Deploy the webapplications to a single managed server. (The remaining Java web applications areautomatically selected.)

4. Configure the Java web applications that were deployed to their own managed servers: InEPM System Configurator, select the "Deploy to Application Server" task for each productfor which you originally deployed to its own managed server. Do not select Deploy the webapplications to a single managed server.

Maintenance Installation Deployments to a Single Managed Server 197

Performing Manual Configuration Tasks in aMaintenance Installation

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

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 aMaintenance InstallationAfter applying a maintenance release, newly-supported languages appear in the list of possiblelanguages; however you must manually add any new languages to the Assigned Languages list.

Select Navigate, then Administer, and then WorkspaceServerSettings. Select Supported Locales andadd the desired locales.

Performance Management Architect Manual ConfigurationTasks in a Maintenance InstallationIf you applied the maintenance release to move from Release 11.1.2.0 or 11.1.2.1 to Release11.1.2.3, and if a Financial Management application contains shared dimensions, right-click theapplication in the Application View pane and select Activate All Associations. This is required tosupport the dynamic properties that were introduced in Release 11.1.2.2 for ExtendedDimensionality.


Essbase Manual Configuration Tasks in a MaintenanceInstallation

Subtopics

l Importing Linked Reporting Objects

l Importing Business Rules to Calculation Manager for use with Essbase

Importing Linked Reporting ObjectsIf you are applying the maintenance release to move from Essbase Release 11.1.2.0 or Release11.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 Release11.1.2.0 or 11.1.2.1. See “Essbase Maintenance Release Installation Prerequisites” on page 189.

ä 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 releasebackup 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 EssbaseIf you are applying the maintenance release to move from Essbase Release 11.1.2.0 or 11.1.2.1to Release 11.1.2.3, and you are an Essbase-only Business Rules user, you must migrate BusinessRules rules to Calculation Manager.

Ensure that you exported rules as described in “Performing Maintenance Release InstallationPrerequisite Tasks” on page 188.

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

Performing Manual Configuration Tasks in a Maintenance Installation 199

Essbase Studio Manual Configuration Tasks in aMaintenance InstallationIf you used the “Apply Maintenance Release” option to move from Essbase Studio Release11.1.2.0, 11.1.2.1 or 11.1.2.2 to this release, you must update the Essbase Studio catalog afterinstallation and configuration.

You update the catalog by issuing the reinit command in the Essbase Studio command lineclient. 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 TasksIf you are working in Oracle Project Financial Planning or Public Sector Planning and Budgeting,before you upgrade applications, you must perform additional steps.

Upgrading ApplicationsIf you applied the maintenance release to move from Planning Release 11.1.2.0, 11.1.2.1, or11.1.2.2, you must run the Upgrade Wizard and use the Upgrade Applications page. From EPMWorkspace, select Navigate, then Administer, then Planning Administration and then click UpgradeWizard. On the Upgrade Applications page, select one or more applications and from the Actionmenu, select Upgrade, and then click OK to proceed. See “Updating Planning References to aRehosted Server Environment and Upgrading Applications” on page 243 for additional details.

Migrating Business Rules to Calculation Manager for use with PlanningIf you applied the maintenance release to move from Planning Release 11.1.2.0, or Release11.1.2.1, and you were using Business Rules rules, you must migrate the rules to CalculationManager rules, and then migrate rules security.


Before you migrate, ensure that user directories and native users with the same SID are availablewhen you upgrade Shared Services.

Ensure that the Planning applications are upgraded to the current release and are available inCalculation 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 Configuratoris imported to Calculation Manager.

2 Repeat for each Planning application.

3 Deploy the rules from Calculation Manager to Planning. See the Oracle Hyperion Calculation ManagerDesigner's Guide.

After migrating business rules and rules security, if any of the rules had multiple launchlocations and you migrated to more than one location, Calculation Manager creates a rulefor the first migration, and shortcuts for all subsequent migrations. If the rule had rule-levelvariables, for the shortcuts that are created in the application in the new environment , itsvariables are moved to the Plan level. In this scenario, test rules in your environment toensure that they work as expected.

Migrating Business Rules Security for use with PlanningIf your upgraded application used Business Rules, administrators can migrate launch accesspermissions on business rules and their projects from Business Rules to Calculation Managerbusiness 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 thespecified Planning application.

l Migrates access permissions only for users and groups that are provisioned for the specifiedPlanning 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 CalculationManager.

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

Performing Manual Configuration Tasks in a Maintenance Installation 201

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 commandline to read the password from the full file path and name specified in passwordFile.

No

/A:appname Specify the Planning application to which to migrate launch access permissions for businessrules

Yes

/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 theplanning1 directory. This file contains a log of the transaction, and helps withtroubleshooting.

Yes

/? 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 ConfigurationTasksIf you want to install Profitability and Cost Management sample applications, first complete themaintenance release installation and configuration. Next, rerun EPM System Installer and fromthe Product Selection panel, from the Profitability and Cost Management section, selectProfitability and Cost Management Samples.

To set up Profitability and Cost Management to work with Oracle Web Services Manager, seethe Oracle Enterprise Performance Management System Deployment Options Guide.

Strategic Finance Manual Configuration Tasksl If you are applying the maintenance release to move from Release 11.1.2.0 or 11.1.2.1 to

Release 11.1.2.3, after installing and configuring, you must convert the Strategic Financedatabase using a conversion utility. See the Strategic Finance Release 11.1.2.1.000 Patch SetException (PSE): 13776302.

l After configuring the maintenance release, move transaction logs to a new location: Copythe logs from EPM_ORACLE_HOME/logs/hsf/userlogs to EPM_ORACLE_INSTANCE/diagnostics/logs/hsf/userlogs.


FDM Manual Configuration TasksAfter installing and configuring the maintenance release, update MIDDLEWARE_HOME/user_projects/config/dbclient/tnsnames.ora to include entries for the OracleDatabase Client that was installed by EPM System Installer in MIDDLEWARE_HOME/dbclient32 and MIDDLEWARE_HOME/dbclient64 so that the Schema Update Utility canconnect to the database.

Maintenance Installation Deployments to WebSphereApplication ServerAfter installing and configuring EPM System components, complete the following steps todeploy 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 thefollowing 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 windowcloses.

4 Start all Java web applications.

5 Launch EPM System Configurator again with the /configtool-manual.bat|.sh command, andselect the Foundation “Configure Web Server” task.

6 Perform the IBM HTTP Server configuration steps.

See “Configuring IBM HTTP Server” on page 170.

Validating the Deployment and Generating aDeployment ReportValidate the deployment. Once the validation report shows no errors, generate a deploymentreport.

ä To validate the deployment and generate a deployment report:

1 From the Start Menu, choose Programs, then Oracle EPM System, then instanceName, then FoundationServices and then EPM System Diagnostics.

Validating the Deployment and Generating a Deployment Report 203

2 To view results, navigate to EPM_ORACLE_INSTANCE/diagnostics/reports and openvalidation_report_date_time.html.

3 Resolve any errors, and then run the report again.

See the Oracle Enterprise Performance Management System Installation and ConfigurationTroubleshooting 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:




Performing a Maintenance Release Installation forEPM System ClientsIf you are applying the maintenance release to move to Release 11.1.2.3, you must uninstall theearlier release of the client before you install the new release. For Financial Reporting Studio,there are additional prerequisites. See “Financial Reporting Maintenance Release InstallationPrerequisites” on page 191.

For clients that have a new client installer in Release 11.1.2.3, applying the maintenance releaseinstallation option in EPM System Installer does not update the client software. You must installthe client using the client installer.

For details about client installers, see “Installing EPM System Clients” on page 89.


11Upgrading EPM System Products

In This Chapter

About Upgrading ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

Upgrading Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

Upgrade Installation Prerequisites .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

Downloading and Preparing Files for Installation ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212

Preparing Data for Upgrading ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

Stopping EPM System Services... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224

Uninstalling the Earlier Release of EPM System Products .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

Installing EPM System Products for an Upgrade ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

Configuring EPM System Products in an Upgrade ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226

Starting EPM System Services ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

Validating the Installation ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

Performing Manual Configuration Tasks .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

Updating References to a Rehosted Environment .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234

Upgrading Applications from the Earlier Release to the Current Release... . . . . . . . . . . . . . . . . . . . . . . . . 248

Performing Manual Configuration Tasks in an Upgrade .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

Upgrading Smart View ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258

Upgrading from an Environment with Multiple Releases ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259

Repeating the Upgrade Process for Applications ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260

This chapter describes the upgrade process for EPM System products. To upgrade EPM Systemproducts to Release 11.1.2.3, you deploy Release 11.1.2.3 software in a new location and moveapplications 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 Release11.1.2.3. Use the “Apply Maintenance Release” option in EPM System Installer instead.See “Maintenance Release Installation Checklist” on page 185. When you apply themaintenance release, you need not follow the upgrade procedures described in thischapter.

205

Note: If you have installed a client in a previous release using a Windows installer, you do notneed to uninstall the earlier release of the client. If you have installed a client in a previousrelease using EPM System Installer, you must uninstall the client before using a Windowsinstaller to install the new version of the client. No configuration is required. If you havean earlier release of Financial Reporting Studio, see “Financial Reporting MaintenanceRelease Installation Prerequisites” on page 191 for additional requirements.

About UpgradingWhen using EPM System products, the term upgrade is defined as follows: The process ofdeploying a new software release and moving applications, data, and provisioning informationfrom 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 260.

To upgrade EPM System products to Release 11.1.2.3, you install and configure Release 11.1.2.3software 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 databaseand 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 operatingsystem. For example, if the earlier release was on a Windows operating system, you mustupgrade to a Windows operating system. If the earlier release was on a Linux operatingsystem, you must upgrade to a Linux operating system. Within the operating systemconstraint, you can switch between versions and editions of the operating system as well as32-bit and 64-bit variations. For example, you can upgrade from 32-bit Windows 2003 to64-bit Windows 2008R2.

l Install EPM System on the existing machine or machines (Oracle recommends that youinstall 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 anew 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 EnterprisePerformance Management System Installation and Configuration Troubleshooting Guide.

Supported Upgrade PathsYou can upgrade to EPM System Release 11.1.2.3 from the following releases:

206 Upgrading EPM System Products

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 "ApplyMaintenance Release" option in EPM System Installer, instead of following the documentedupgrade procedures.

Note: For Financial Close Management, applying the maintenance release is supportedonly 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 multiplereleases, which can include an environmentwith one instance of Shared Services or anenvironment with two instances of SharedServices

See “Upgrading from an Environment with Multiple Releases” on page 259.

Note: If you are starting from Release 9.2.0.3+, 9.3.0.x, 9.3.1.x (except for Oracle Essbase9.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 toRelease 11.1.1.3, then apply the maintenance release to Release 11.1.1.4, and then upgrade toRelease 11.1.2.3. If you are starting from an earlier release, Oracle recommends that you upgradeto the highest level release that directly supports upgrade from your starting release. SecuritySynchronization 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 EssbaseRelease 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 ChecklistThe following table identifies the high-level tasks that you perform to upgrade EPM Systemproducts. 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 andindicates where a sequence is required.

Note: If you are upgrading from an environment with multiple releases, see “Upgrading froman Environment with Multiple Releases” on page 259.

Upgrading Checklist 207

Table 30 Upgrading Checklist

Task Reference Check WhenCompleted

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, andother prerequisites for this release.

If your database environment needs to be upgraded, performthe database upgrade before you proceed. See the databasedocumentation for details.

l Oracle Enterprise PerformanceManagement System Certification Matrix(http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html)

2. Prepare the new environment for the new Release 11.1.2.3 installation.

Note: Create a new database to store Shared Services data.(However, if you are upgrading from Release 11.1.1.4 and youused one database repository for all products, you do not needto create a new database for Shared Services. The SharedServices tables will be dropped during configuration.)

Tip: In preparation for a new installation, you can use aworksheet to note the machines on which earlier releaseproducts are installed, and the machines on which you planto install the new release products. You can refer to thisinformation in subsequent procedures.

l Chapter 3, “Preparing Your Environment”

3. Perform upgrade-specific prerequisite tasks. “Upgrade Installation Prerequisites” on page210

4. Download and prepare the installation files. “Downloading and Preparing Files forInstallation” on page 212

5. Prepare data for upgrading. “Preparing Data for Upgrading” on page 213

6. Stop EPM System services if you are upgrading on the samemachine.

“Stopping EPM System Services” on page224

7. Uninstall the earlier release of EPM System products.

Oracle recommends that you uninstall if you are upgrading tothe same machine.

“Uninstalling the Earlier Release of EPM SystemProducts” on page 225






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 Webserver. 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. Afterconfiguration, 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 correctorder.

Installing and Configuring

8. Install EPM System products (choosing the Newinstallation option) in a new installation location.

Tip: After installation, use the EPM System Defects FixedFinder on My Oracle Support (https://support.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=1292603.1) to determine whether any patches are required for yourenvironment. If required, apply the patches after installation.

l “Installing EPM System Products for anUpgrade” on page 225 for informationspecific to installation when you areupgrading

l Chapter 5, “Installing EPM System Productsin a New Deployment” for generalinformation about installation

9. Configure Release 11.1.2.3 products.

You must configure Foundation Services first. FoundationServices must be installed and configured for other productsto configure successfully.

Caution! If you have already configured the Web server andyou configure any additional products, you must run EPMSystem Configurator again and select the Foundation ServicesConfigure Web Server task. Then, restart the Web server andEPM Workspace.

l “Configuring EPM System Products in anUpgrade” on page 226 for informationspecific to configuration when you areupgrading

10. Start EPM System services. Chapter 12, “Starting and Stopping EPMSystem Products”

Validating the Installation

11 Using EPM System Diagnostics, validate the installation. Chapter 13, “Validating the Installation andVerifying Deployment”

Performing Post-Configuration Tasks

12. Complete product-specific manual configuration tasks. Chapter 9, “Performing Manual ConfigurationTasks in a New Deployment”

13. If products have been rehosted on a new server, makeupdates, such as updating data source connections.

“Updating References to a RehostedEnvironment” on page 234

Upgrading Checklist 209





14. Upgrade applications for the following products from theearlier release to the current release:

l FDM

Note that Planning applications are upgraded using theUpgrade Wizard, which also includes steps for rehosting. Otherapplications are upgraded during configuration.

“Upgrading Applications from the EarlierRelease to the Current Release” on page 248

15. Perform product-specific upgrade tasks for products thatyou upgraded.

“Performing Manual Configuration Tasks in anUpgrade ” on page 249

For clients that have a new client installer in Release 11.1.2.3, upgrading does not update theclient software. You must install the client using the client installer. See “Installing EPM SystemClients” on page 89.

For Predictive Planning, note the following:

l Upgrade all Predictive Planning client versions at the same time, so that all users can seenew features.

l Administrators should make Form setup changes using the updated Predictive Planningversion. 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 ReleaseBefore you proceed with an upgrade, ensure that you have backed up information from theearlier release including databases, applications, and other files. For instructions for Release11.1.1.4 products, see the Oracle Enterprise Performance Management System Backup andRecovery Guide.

Performing Product-Specific Upgrade PrerequisitesEnsure 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 NTLMas 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


Release 11.1.1.4 Oracle Enterprise Performance Management System Security ConfigurationGuide.

l If you are using Business Rules, you must migrate to Calculation Manager rules in Release11.1.2.3. You must perform prerequisite steps before you upgrade. See “Business RulesMaintenance Release and Upgrade Installation Prerequisites” on page 211.

l For Financial Reporting, if both the source and target machines are Windows servermachines, ensure that the SMB 2.0 protocol is disabled on both the source and targetmachines before performing the upgrade.

l For FDMEE, for any data rules that were not run in Release 11.1.1.4, specify a default valuefor the scenario dimension. If you do not specify a default value, these rules are not accessiblein the new release. If you were using Performance Management Architect Essbaseapplications in Release 11.1.1.4, use Refresh Metadata in Target Application before proceedingto do any data load.

l For FDM, when you are using Financial Management, Essbase, Planning, or HyperionEnterprise as target systems, the target system clients must be installed on the same serveras FDM.

l If you are using FDM and you are using IIS as the Web Server to host EPM Workspace, youmust install the FDM Web application and the EPM Workspace Java web application onthe same box.

When you are done with this step, return to the “Upgrading Checklist” on page 207.

Business Rules Maintenance Release and UpgradeInstallation PrerequisitesIf you are applying the maintenance release to move from Release 11.1.2.0 or Release 11.1.2.1to Release 11.1.2.3, or if you are upgrading from an earlier release, and if you have been usingBusiness Rules in the earlier release, you must migrate to Calculation Manager rules in Release11.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 BusinessRules 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 youmigrate business rules, you must provide the details of a specific launch location (that is, the applicationtype---Planning or Essbase, the server name, the application name, and the database or plan type). Ifyou want a business rule to be valid for multiple launch locations, you must provide the details for eachlocation. The locations must be in different applications; you cannot migrate the same business rule todifferent plan types in the same application within Calculation Manager.

Upgrade Installation Prerequisites 211

If the rule is a part of a sequence, then the launch location of the rule within the sequencemust 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 fora specific location or locations and not “All Locations.” If multiple locations are defined for a businessrule 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: UseAdministration Services to export the rules to XML in Business Rules format. If you are upgrading from11.1.1.4, also export the rules to Calculation Manager format. EPM System Configurator exports therules 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 Essbaserule from Business Rules:

a. From Administration Services Console, right-click the Business Rules node and selectExport.

b. Export the rules in Business Rules format and then select all of the Essbase rules in therepository. If you are upgrading from 11.1.1.4, also export the rules to CalculationManager format.

c. Specify the location to save the XML file, and then click OK. If you are upgrading, thelocation 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 whenyou perform the “Configure Database” task.

After configuration, there are additional tasks you perform to import and migrate business rules.

Downloading and Preparing Files for InstallationDownload files for Release 11.1.2.3 and extract the zip file contents. See Chapter 4, “DownloadingFiles for Installation.”



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 ReleaseTo use data from the earlier release of Shared Services, you export the data using a utility, andthen 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 thisprocedure.

Note: Before you migrate Shared Services data, ensure that the admin user is provisioned forthe 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 theSystem Installer ZIP file.

If you have not yet downloaded the System Installer ZIP file (Oracle HyperionEnterprise Performance Management System Installer, Fusion Edition

Release 11.1.2.3 for platformName), download it from the Oracle Software DeliveryCloud. See Chapter 4, “Downloading Files for Installation.”


2 In the SystemInstallerExtractLocation/Migration directory, look forHSSMigrate.zip and extract the contents to the HYPERION_HOME directory on the machinehosting 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 forconfirmation.

Tip: To ensure successful export of Lifecycle Management data from Release 11.1.1.4 onUNIX, set executable permissions on set_hyphome_servername_1.sh, in $home/.

Preparing Data for Upgrading 213

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

Tip: The path you enter should be the path for the CSS.xml, Domain.xml, andWorkflowEngine.properties files, for example: HYPERION_HOME/AppServer/InstalledApps/WebServerName/WebServerVersion.

The utility creates a file, hssmigratedata.zip, in HYPERION_HOME/migrate, that storesthe 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 replacesthe existing file.

5 Copy hssmigratedata.zip from HYPERION_HOME/migrate to the machine on which you planto host the new release of Shared Services, or make the file available on a shared drive. (If you areinstalling 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 machinesother 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 thisMIDDLEWARE_HOME during installation.

For more information about what happens during Shared Services data import, see “WhatHappens During Shared Services Data Import” on page 231.

Exporting Financial Management and Strategic Finance Datafrom the Earlier ReleaseFor Financial Management, you must prepare for provisioning for the Application Creator andFinancial Management Administrator roles for groups that previously had these rights. Youexport provisioning information, and during database configuration later in the upgradeprocess, 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 arerequired only if there are customizations to these files. If no customizations have been made tothese 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


l .alt: alcar template

l currencies_user.xml

l convert.idx

ä To export Financial Management and Strategic Finance 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 theSystem Installer ZIP file to any machines hosting Financial Management and Strategic Finance.

If you have not yet downloaded the System Installer ZIP file (Oracle HyperionEnterprise Performance Management System Installer, Fusion Edition

Release 11.1.2.3 for platformName), download it from the Oracle Software DeliveryCloud. See Chapter 4, “Downloading Files for Installation.”


2 In the SystemInstallerExtractLocation/Migration directory, look forHSSMigrate.zip and extract the contents to the HYPERION_HOME directory on all machineshosting 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/Migratedirectory:

hfmmigrate.bat

The utility searches for Financial Management files and generates a zip file with theircontents 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 FinancialManagement 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/Migratedirectory:

hsfmigrate.bat

The utility searches for Strategic Finance files and generates a zip file with their contentsin 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 StrategicFinance and unzip it in MIDDLEWARE_HOME/EPMData

Copying Files for Temporary Use During ConfigurationIf you are upgrading Provider Services or Administration Services, some files from the earlierrelease of EPM System are required during configuration of the new release. You must make the


files available on a shared drive or copy them from the earlier release installation to the machinehosting the new installation for use during configuration with EPM System Configurator.

During configuration with EPM System Configurator, this data is moved to the Shared ServicesRegistry 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 fromthe earlier release.

During configuration, you specify the location of these files. By default, EPM SystemConfigurator 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.


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


server.xml, located in HYPERION_HOME/common/workspacert/9.5.0.0/common/config/dynamic/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 DataWhen you upgrade to EPM System Release 11.1.2.3, you use the data from the earlier release inone of two ways:

l You can replicate the data to a new machine, making it accessible from the new installationenvironment. For example, use this option if you want to maintain the earlier releaseenvironment.

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.


l You can leave the data on the existing machine, making the drive shareable. If you chooseto leave data on the existing machine, you can skip the procedures in this section. Duringproduct configuration with EPM System Configurator, you specify the existing datalocation. You can choose this option only if you no longer need to maintain the earlier releaseenvironment.

Note: For Essbase, you can choose this option only if the data is on a supported type ofshared 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 thereplicated product data.

Tip: This location is the data storage location for Release 11.1.2.3, so store data in ameaningful, permanent location. You might choose to specify a location for eachproduct, for example: EPMData/productName. Do not store data in the directory thatis to be used as EPM_ORACLE_INSTANCE, which in a default installation isOracle/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 thedata 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 218. Inaddition, note the following:

If you are installing this release of Essbase on a new machine, gather additional data from the machine hosting theearlier release installation:

l Make a list of the ODBC DSNs defined on the machine so that you can redefine them on the new machine. Performthis 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 onthe new machine.

Note: You can provide a UNC path for ARBORPATH. When you use a UNC path, table spaces and disk volumes mustalso 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 TextFiles configuration page.


Copy the following file from the machine hosting the Release 11.1.1.4 installation to the data storage location: EAS_HOME/server/lib/cryptix32.jar.


Product Data to Replicate


Data files.

By default these files were stored in HYPERION_HOME/products/Foundation/workspace/data/RM1_servername.

Note: Make note of the location to which you replicate the data. During configuration with EPM System Configurator,you enter this location on the Reporting and Analysis Framework Services configuration page, for Repository Directory.


Attachment and note files.

By default these files were stored in the /attachments and /notes directories in following location:HYPERION_HOME/deployments/WEB_SERVER/webappsconf.

Note: Make note of the location to which you replicate the data. During configuration with EPM System Configurator,you enter this location on the Performance Scorecard configuration page, for Specify directory to store PerformanceScorecard files.

StrategicFinance

Data files.

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 SystemConfigurator, 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 applicationdata: From Workbench client, select Add Application, select the application, click Modify and then note the datalocation. 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 usedto configure FDM. This directory structure must be replicated to the new environment if it is not accessible from the newenvironment.

Note: Make note of the location to which you replicate the FDM data directory. During FDM configuration, for eachapplication, you specify the new data directory.

Preparing Essbase Data for UpgradingThe 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 theapplications in the upgraded environment, delete them after completing the entire upgradeprocess.

Notes:

l The Essbase Server must be running before you launch the Essbase Staging Tool. The toolshuts down the Server as needed. To ensure data integrity, disable logins and make sure nousers are active before starting the Staging Tool.

l If the ESSLANG environment variable is not set on the machine on which you are runningStaging Tool, the Staging Tool sets the value toEnglish_UnitedStates.Latin1@Binary. The ESSLANG value for the Staging Toolshould 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 thelibaio package version 0.3.105-2 or higher.


If you are upgrading from an earlier release and an application has more than 127 linkedreporting objects, perform the following procedure to export linked reporting objects beforeyou run the Staging Tool.

Tip: To determine how many linked reporting objects an application has, use the MAXLcommand query database DBS-NAME list lro all;, for example, MAXL> querydatabase 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 upthe application linked reporting object data to a specified directory by using the following MAXLcommand:

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 inARBORPATH/app, where ARBORPATH is the server ARBORPATH.

2 Delete the linked reporting objects from the earlier release application with the following MAXLcommand:

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 reportingobjects on the source system after the upgrade process is complete.

ä To prepare Essbase data for upgrading perform the following tasks on the machine hostingthe 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 databaseapplicationName.databaseName validate using default error_file;

against the database. If the validation returns errors, revert to a backup that is free oferrors or fix the errors before you proceed with the upgrade.

l Use the following MaxL commands to search for user and group errors: displaygroup all failed_sss_migration; and display user all


failed_sss_migration;. If the commands return any errors, resolve the errorsbefore 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 fullrestructure on the database.

2 Using Administration Services, edit Application Properties for each application (select General thenStartup) 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 displayapplication all; to ensure that autostartup is set to FALSE for all applications. (Usethe MAXL command alter application DBSName disable autostartup; to turnoff the property for each application as needed.)

3 If you have not already done so, download files for Release 11.1.2.3 and extract the contents of theSystem Installer ZIP file.

If you have not yet downloaded the System Installer ZIP file, download it from the OracleSoftware Delivery Cloud. See Chapter 4, “Downloading Files for Installation.”

Extract the contents to a directory that does not have spaces in the name.


4 In the SystemInstallerExtractLocation/Migration directory, look forEssStagingTool.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 areupgrading. 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 EssStagingToolExtractLocationdirectory:

essStage.bat|sh username [agentPort]

where username is the name of any Essbase user who is an administrator. agentPort isoptional and specifies the port on which the Essbase instance is running. The default valueis 1423.

6 When prompted, enter the administrator password.

The Staging Tool queries Essbase for a list of applications and the disk volumes that aredefined, 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. Thisoption is the fastest. If you select this method, the system you are upgrading on mustuse 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 youselect this method, you can specify a different disk volume, table spaces, or


ARBORPATH on the system you are upgrading to than what is defined on the earlierrelease system.

Note: If you select this method, make note of the new ARBORPATH location. Duringconfiguration with EPM System Configurator, you enter this location on theEssbase configuration page, for Full path to application location (ARBORPATH).

l Consolidated disk volumes or tablespaces on target by exporting data. Select this methodif you want to consolidate disk volumes on the system to which you are upgrading. Thismethod exports data to text files so that you can later import them on the upgradedsystem. Because this method is the slowest, use it only if you need to consolidate diskvolumes, for example if the source machine has volumes defined for c, d, and e drivesand the target machine has only c and d drives. This option performs some datavalidation 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.secfile. If you select only some applications, you must select a second method of preparing thedata 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 wantto apply the first data preparation method that you selected. When you are finished selectingapplications, press Enter.

10 If you selected No for Select all applications, select the data preparation method to use for all of theremaining applications.

If you selected Same-named disk volumes, table spaces, and ARBORPATH on source andtarget 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 byexporting 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 andtarget, enter Y to proceed with preparing data.

The Staging Tool prepares essbase.cfg, essbase.sec, data, and applications for filetransfer.

l If you selected Differently-named disk volumes, table spaces, or ARBORPATH on sourceand target:

a. Specify a new ARBORPATH location for the machine on which you are upgradingand then press Enter. The ARBORPATH for the current release is displayed inparentheses for your reference.


Tip: The ARBORPATH that you specify cannot be the directory that is to be used asEPM_ORACLE_INSTANCE, which in a default installation is Oracle/Middleware/user_projects/epmsystem1. (EPM_ORACLE_INSTANCEmust be an empty directory.)

Tip: ARBORPATH is the location for applications; previous releases usedARBORPATH to refer to the installation location. ESSBASEPATH is now used todefine the installation location. For more information, see “UnderstandingHow Essbase Files Are Stored” in the Oracle Essbase Database Administrator'sGuide.

b. If prompted, specify a new disk volume for the machine on which you are upgradingand then press Enter. The disk volume for the current release is displayed inparentheses for your reference.

c. If prompted, specify a new default tablespace for the machine on which you areupgrading and then press Enter. The default tablespace for the current release isdisplayed in parentheses for your reference. (This step applies only to ASOapplications.)

d. Enter Y to proceed with preparing data.

The Staging Tool prepares essbase.cfg, essbase.sec, data, and applications for filetransfer, updating internal references to ARBORPATH, disk volumes, and tablespaces asneeded. Later in the upgrade process you must run a script (editagtsec.msh) toupdate 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 withpreparing data.

The tool prepares a list of data to export, and then copies the data to the exportdirectory you specified. It shuts down Essbase before copying files. If it cannot shutdown Essbase, you are prompted to shut down Essbase.

b. If you are prompted to shut down Essbase, shut it down, and then press Enter tocontinue.

The Staging Tool prepares data files, exported data along with a script to import it, anda script for editing the security file.

Note that with this option, you must perform additional tasks later in the process: Youmust run a script (editagtsec.msh) to update disk volume settings inessbase.sec for the relocated applications. You must manually import LROs and datalater 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 newhost machine.


Note that the Staging Tool copies all of the files and directories under the specifiedARBORPATH, 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, theStaging Tool prompts you for the mounted drive location for each of the destinationARBORPATH, table space, disk volume, and export data directory directories. Specify themounted path of the same ARBORPATH path that you specified during the datapreparation method. The destination path for tablespace should map to the tablespacespecified in the data preparation method. The destination path for disk volume pathshould 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 processfails for any reason, follow the instructions in EssStagingToolExtractLocation/work/FileTransferSteps.txt to manually copy the data to the machine on whichyou plan to upgrade Essbase.

l Get a list of file transfer instructions. If you select this option, the Staging Tool exportsdata and prepares a file with file transfer instructions. ReviewEssStagingToolExtractLocation/work/FileTransferSteps.txt for detailsand follow the steps to manually copy the data to the machine on which you plan toupgrade 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 userwho will install Essbase.

EssStagingToolExtractLocation/work/FileTransferSteps.txt includes the listof files to update.

14 (Optional) Review the log file, EssStagingToolExtractLocation/essStaging.log, fordetails of the Staging Tool actions.

You can use the log during configuration with EPM System Configurator to remind you ofthe 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 theDISKVOLUMES, SSAUDIT, SSAUDITR, and TransactionLogLocation settings to reflect newdirectory locations.


Note: The Staging Tools copies ARBORPATH/app/appname/dbname/Replay, which is relatedto the transaction logging and replay feature. Because Oracle recommends a freshimplementation of transaction logging and replay in any given Essbase release, Oraclerecommends that you delete these files on the upgraded system before you proceed. As abest practice, the files in the LOGLOCATION and Replay directories should be backed upperiodically.

When you have finished preparing Essbase data for upgrading, return to “Replicating Data” onpage 216 to replicate data for other EPM System products.

Replicating the DatabasesOptionally, replicate the entire database or databases to a new machine or machines. Oraclerecommends that you replicate the databases.

During database configuration with EPM System Configurator, specify the new productdatabase location.

Note the following about replicating databases:

l If the database version needs to be updated, perform the database upgrade before replicatingdata.

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 newdatabase 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 beforeyou upgrade to ensure successful upgrade.

l For Financial Management and MS SQL Server, if you are restoring a backup of an existingdatabase in a new environment, make sure that the current database user has access to theimported database objects. This can be accomplished using a script such asmaster.sp_change_users_login.


Stopping EPM System ServicesIf you are installing Release 11.1.2.3 on the same machine as the earlier release installation, stopall EPM System services. If you need details about stopping services, see Chapter 12, “Startingand Stopping EPM System Products.”



Uninstalling the Earlier Release of EPM SystemProductsOracle recommends that you uninstall earlier releases of EPM System products unless you wantto maintain the earlier release environment. During uninstallation, when prompted whetheryou want to delete all the files and directories in the EPM Oracle home directory, select No unlessyou 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 youinstall Release 11.1.2.3 on a new machine.) You cannot uninstall the earlier release ofShared 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 releasebefore you proceed.

Tip: If you choose not to uninstall the earlier release and you are upgrading on the existingmachine, you might need to edit the PATH variable to remove all references to the earlierrelease. This can prevent you from reaching the character limit for the PATH variable whenyou configure.


Installing EPM System Products for an UpgradeInstall EPM System products using EPM System Installer, as described in Chapter 5, “InstallingEPM 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 andconfigure the earlier release.

l For each machine, you can install all the products that you plan to host on that machine atone time. For additional requirements for a distributed installation, see “Installing EPMSystem Products in a Distributed Environment” on page 79.

l If you are installing on the same machine, in a new location, you must install and configureusing 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 warnsyou that the earlier release might no longer work after you install the current release.


Uninstalling the Earlier Release of EPM System Products 225

Configuring EPM System Products in an UpgradeAfter you install, use EPM System Configurator to configure EPM System products.

Caution! Do not proceed with configuration until you have exported Shared Services datafrom the earlier release. See “Exporting Shared Services Data from the EarlierRelease” on page 213.

Upgrade configuration notes:

l Ensure that the external authentication provider is online before you start EPM SystemConfigurator.

l Before starting EPM System Configurator, copy cryptix32.jar from the AdministrationServices 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 andconfigured for other products to configure successfully.

l In a distributed environment, for Shared Services, perform the Configure Database andImport data from earlier release tasks on each machine on which Shared Services is installedbefore configuring any other products. For other products, you perform the import datatasks 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 performthe “Deploy to Application Server” task.

l Because you are configuring products one at a time, configure the Web server after eachproduct. (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 exceptionsto this requirement are documented in “Deploying Financial Management, FinancialReporting, and Web Analysis on Windows in a UNIX-Based EPM System Deployment ” onpage 151.

l If you are upgrading multiple instances of Essbase, for each instance that you are upgradingfrom, you must create a new instance in Release 11.1.2.3. See “Configuring and StartingAdditional Instances of Essbase Server” in the Oracle Enterprise Performance ManagementSystem Deployment Options Guide.

The following table describes the tasks that you must select in EPM System Configurator anddescribes the tasks EPM System Configurator performs during upgrade. For details aboutrunning EPM System Configurator, see Chapter 6, “Configuring EPM System Products in a NewDeployment” or click Help.


Note: For all products other than Shared Services, during product database configuration, selectUpgrade 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 OracleEPM 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 thefirst product you configure, you create a new EPM Oracle instance. Foreach product after that, you modify the existing EPM Oracle instance. Ifyou are installing in a distributed environment, create a new EPM Oracleinstance on each machine.

SharedServices





l Deploy to Application Server

l Import data from earlier release

During Shared Services database configuration, select Perform first-time configuration of Shared Services database, and then enterconnection information for a new database.

If you configured all EPM System products to use one database, you arealerted that pre-existing Shared Services tables have been detected inthe database. When prompted to drop and recreate the tables, selectYes.

For the Deploy to Application Server configuration task, deploy to a newWebLogic domain.

For the Import Data From Earlier Release configuration task, specify thelocation from which to import Shared Services data. You must specify thefull path to hssmigratedata.zip, which is created with the SharedServices Upgrade Utility.

Caution! Perform this task only once on a machine.

In a distributed environment, perform the Configure Database andImport data from earlier release tasks on each machine on whichShared Services is installed before configuring any other products.

When you are done with this step, return to the “Upgrading Checklist” onpage 207.

Imports Shared Services data from theearlier release. For more information aboutthis process, see “What Happens DuringShared Services Data Import” on page231.

Note: You see applications in EPMWorkspace and provisioning information inShared Services only after a product isreregistered and applications are migrated.

You see EPM Workspace preferencesupgraded from the earlier release only afteryou have upgraded all EPM Systemcomponents and you have startedReporting and Analysis Framework. Inaddition, users must be provisioned with aReporting and Analysis role other than IRHTML Viewer or IR WebClient Viewer.

Configuring EPM System Products in an Upgrade 227


Essbasel Configure Essbase Server

On the Configure Essbase Server page, for Full path to applicationlocation (ARBORPATH),:

l If you are upgrading to a new machine, specify the location of thedata that you copied after using the Staging Tool.

l If you are upgrading to a new location on the same machine, and youdid not replicate data to a new location, specify the location of theexisting Essbase data.

Note: If you replicated data to a new machine, and if you selectedDifferently-named disk volumes, table spaces, or ARBORPATH onsource and target or Consolidated disk volumes or tablespaces ontarget by exporting data during data replication, you must run a scriptimmediately after configuring Essbase to update the Essbase security fileto reflect the disk volumes on the upgraded system. The Essbase StagingTool provides a script to update the settings in the security file(essbase.sec):

Start the Essbase Server and EPM System services. Navigate toARBORPATH/app on the machine that is hosting the upgraded EssbaseServer 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 theupgraded Essbase server. The script prompts you to enter the password.

Note: editagtsec.msh could be empty in some scenarios. Forexample, when you launched the Staging Tool, the Staging Tool reportson existing volumes. If no volumes are listed, editagtsec.msh isempty.

Registers applications with Shared Servicesand upgrades applications.

Note: When you upgrade from an earlierrelease, a backup of the security file for theearlier release is created before the securityfile is upgraded. The security file backup,Essbase.Bak_preUpgrade, is inARBORPATH/bin. Unlike the Essbase_timestamp.bak file, which regularlybacks up the latest state of Essbasesecurity, this pre-upgrade backup file is keptintact and is not subsequently updated byfurther operations.

ProviderServices


l Import Data From Earlier Release

l Configure Web Server (Foundation task)

For the Import Data From Earlier Release task, specify the location ofthe existing or replicated data.

Moves data from the earlier release into theShared Services Registry. Movesessbase.properties to EPM_ORACLE_INSTANCE/aps/bin andmerges its contents with the essbase.properties file installed with Release11.1.2.3.




l Import Data From Earlier Release


For the Import Data From Earlier Release task, specify the location ofthe existing or replicated data

Moves data from the earlier release into theShared Services Registry.



Essbase Studiol Configure Database

l Configure Essbase Studio Location for Sample and Customer DataSource Text Files


On the Configure Essbase Studio Location for Sample and CustomerData Source Text Files page, specify the location of the existing orreplicated Essbase Studio data.

Upgrades the Essbase Studio catalog andthe database.

EPM System Configurator performs thefollowing tasks during the upgrade process:

1. Exports metadata from the sourcecatalog to an external xml file (EPM_ORACLE_HOME/tmp/studio_dump.xml).

2. Renames the source catalog tables andconstraints by replacing the prefix cp_with the prefix cc_.

3. Creates new catalog tables with theprefix cp_.

4. Imports metadata from studio_dump.xml into the new catalog.

5. Converts metadata objects from theearlier release to the structure for theupgraded release.

6. Deletes studio_dump.xml if theupgrade succeeds.

Note: If database configuration failsduring upgrade, see the Oracle EnterprisePerformance Management SystemInstallation and ConfigurationTroubleshooting Guide. Maintain theRelease 11.1.1.4 environment until theupgrade is complete.

IntegrationServices

l Configure Essbase Integration Services






l Configure Dimension Server


Updates the database.

Updating the database could take sometime to complete, based on the content andsize of the database being upgraded. Do notinterrupt this task while it is running.

CalculationManager












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


Updates Web Analysis application settings.Updates the database.

Planningl Configure Database





If you have been using Business Rules, EPMSystem Configurator exports the rules duringdatabase configuration to EPMData/planning/hbrRules.xml for use in theapplication upgrade process, when therules are migrated to Calculation Manager.

You perform application upgrade later in theupgrade process.

FinancialManagement



l Configure DCOM

l Configure Application Server

l Configure Application Cluster

l Configure Web Server (Financial Management task)

l Upgrade applications from earlier release


You must select Upgrade applications from earlier release. Note thatthere is no EPM System Configurator page for this task and you need notenter information.

Note: Depending on the number and size of applications you areupgrading, this task can take some time.


Upgrades applications by convertingdatabase tables, and registers applicationswith Shared Services.

Note: Perform the application upgradeonly once, regardless of how many FinancialManagement application servers areconfigured.






l Configure Attachment Files Location


On the Performance Scorecard Specify directory to store PerformanceScorecard files configuration page, specify the location in which to storefiles.



Profitability andCostManagement





Updates the database and reregisters allupgraded Profitability and CostManagement applications with SharedServices.

StrategicFinance

l Configure Data directory

l WebServices Configuration


On the Strategic Finance Configuration configuration page, specify thelocation of the existing or replicated data.




N/A. Use the Apply Maintenance Release option during installation.

Financial CloseManagement

N/A. Use the Apply Maintenance Release option during installation.

FDMl Configure Database (for FDMEE)

l Deploy to Application Server (for FDMEE)





Registers FDM with Shared Services.

Updates the FDMEE database.

You complete configuration in FDM andupgrade applications later in the upgradeprocess.

What Happens During Shared Services Data ImportDuring configuration, with the Foundation Import data from earlier release task, EPM SystemConfigurator extracts the contents of hssmigratedata.zip and imports the data to SharedServices Release 11.1.2.3.


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 anyerrors 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 arecreated 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 andAnalysisIf you are upgrading a distributed deployment of Reporting and Analysis, note that thedistributed configuration is not automatically replicated in the upgrade as it was in earlier releaseswhen you upgraded. You must set up the distributed configuration in the Release 11.1.2.3environment. Use the Upgrading Checklist, but repeat the installation and configuration stepsas 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 productdatabase configuration, select Upgrade the existing databases to the current release from... andselect a release number. Then, enter connection information for the existing or replicated database.


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, selectUpgrade 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. Duringconfiguration with EPM System Configurator, for the product database configuration, select Connect toa previously configured database. Then, enter connection information for the existing or replicateddatabase.

Starting EPM System ServicesStart EPM System services before you proceed. See Chapter 12, “Starting and Stopping EPMSystem Products.”


Validating the InstallationUse EPM System Diagnostics to validate the installation. See Chapter 13, “Validating theInstallation and Verifying Deployment.”

Performing Manual Configuration TasksYou must perform any required product-specific postconfiguration tasks before you proceed.See Chapter 9, “Performing Manual Configuration Tasks in a New Deployment.”


Starting EPM System Services 233

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 toupdate references for some products to reflect the new host name and port number. Performthe rehosting steps for Essbase first. Make sure EPM System services are started before youproceed.

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 updatereferences to the Essbase Server within Shared Services Registry (to map the server name to acluster 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.

You must perform this step before you updatereferences for other products.

“Mapping Essbase Server Host Names to Cluster Names” on page 235

Update Essbase Server references within Essbase.

You must perform this step before you updatereferences for other products.

“Updating Internal Essbase References to a Rehosted Essbase Server” on page236


Essbase Server Host Reference For Information on How to Update

For products that use Essbase as a data source, if theEssbase Server host or port has changed since theearlier release, update references to the EssbaseServer.

Perform these steps after you install and configureeach product.

Note: The steps for Performance ManagementArchitect are required even if Essbase Server has notbeen rehosted.

l Provider Services — “Updating Provider Services References to a RehostedEssbase Server” on page 236

l Administration Services — “Updating Administration Services References to aRehosted Essbase Server or Provider Services Server” on page 237

l Essbase Studio — “Updating Essbase Studio References to a RehostedEnvironment” on page 238

l Reporting and Analysis — “Updating Reporting and Analysis References to aRehosted Server Environment” on page 241

l Performance Management Architect — “Updating Performance ManagementArchitect References to a Rehosted Server Environment” on page 243

l Planning — “Updating Planning References to a Rehosted Server Environmentand Upgrading Applications” on page 243

l Profitability and Cost Management — “Updating Profitability and CostManagement References to a Rehosted Essbase Server” on page 246

l Strategic Finance — “Updating Strategic Finance References to a RehostedEssbase Server or Financial Management Server” on page 246

l Performance Scorecard — “Updating Performance Scorecard References to aRehosted Essbase Server” on page 247

Mapping Essbase Server Host Names to Cluster NamesTo simplify the rehosting process for products that use Essbase as a data source, perform thistask to map the server host name to the cluster name. This allows other EPM System productsto connect to Essbase by cluster name.

You must perform this step before you update references for other products. This step addssearch-and-replace host pairs to the Shared Services Registry that other products use to updatetheir Essbase host environments.

Note: Performance Management Architect requires this step even if the Essbase Server has notbeen 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 176.

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, foroldEssbaseServerHost, specify Servername. Run the script again and foroldEssbaseServerHost specify server name:port.

Updating References to a Rehosted Environment 235

If products connect to Essbase Server using a non-default port, run the script only once andfor 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 andthe new logical cluster name in the Shared Services Registry.

4 Repeat for each Essbase Server instance.

Updating Internal Essbase References to a Rehosted Essbase ServerYou must map Essbase Server names to cluster names before you perform this step. See “MappingEssbase Server Host Names to Cluster Names” on page 235.

If the Essbase Server host has changed since the earlier release, you must update internalreferences 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 machineand userName is an Essbase administrator user provisioned in Release 11.1.2.3. The defaultport is 1423.

The utility updates the host for all location aliases and partition definitions for all Essbaseapplications.

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

Updating Provider Services References to a RehostedEssbase ServerYou must perform Essbase Server rehosting steps before you perform this step. See “UpdatingReferences to a Rehosted Essbase Server ” on page 234.

If the Essbase Server host has changed since the earlier release, you must make updates so thatProvider Services recognizes the new Essbase data source.


ä 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 EditionServer, see the Oracle Hyperion Provider Services Administration Guide.

Updating Administration Services References to a RehostedEssbase Server or Provider Services ServerYou must perform Essbase Server rehosting steps before you perform this step. See “UpdatingReferences to a Rehosted Essbase Server ” on page 234.

If the Essbase Server host and port have changed since the earlier release, you must make updatesso that Administration Services recognizes the new Essbase data source. After upgrading, reviewand 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 availableservers 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 mustmake 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.


When you add a new server, in the Add Provider Server dialog box, enter the Provider hostsfor the new installation: click URL (the Provider URL box is updated), and ensure that theport is correct. From the Authenticating Essbase Server menu select the active Essbase andthen click OK.

4 Delete previous Provider Services Server hosts from the Provider Servers tree.


Updating Essbase Studio References to a RehostedEnvironment

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

You must perform Essbase Server rehosting steps before you perform this step. See “UpdatingReferences to a Rehosted Essbase Server ” on page 234.

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, orfor 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, updateEssbase Studio references to the Essbase Server.

“Updating Essbase Studio References to a RehostedEssbase Server” on page 239

If the Essbase Studio Server host and port have been moved to a new locationand you have deployed applications that point to the earlier release EssbaseStudio Server location, update the cube linkage of those deployed applications topoint to the new Essbase Studio Server instance.

“Updating Cube Linkages” on page 240

If Performance Management Architect has been moved to a new location, then forall Performance Management Architect data source connections that point to theearlier release location, edit the connection properties to reflect the new serverlocation.

“Updating Essbase Studio References to a RehostedPerformance Management Architect Server or to TextFiles Used as Data Sources” on page 240

If text files were moved to a non-default directory, edit the connection propertiesfor any text file connections to point to the new location.

“Updating Essbase Studio References to a RehostedPerformance Management Architect Server or to TextFiles Used as Data Sources” on page 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 encryptionmethod, 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, ifapplicable, data encryption method.

Note: For Essbase Server clusters, only the cluster name is required. The port number is notrequired. 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 TestConnection 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 history—Replaces all old EssbaseServer 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 only—Makes a copyof the last successful deployment history listing, and then updates the copy with the newhost and port information, and the date and time of the rehosting.

Tip: When selecting the Replicate option, after the update is complete, each rehostedEssbase model displays twice in the Metadata Navigator: once with the oldhost:port information and once with the new host:port and, if required, dataencryption information.


Note: Deployment history is updated only for successfully rehosted Essbase Serverconnections.

6 Click Update.

7 For the rehosting status of each Essbase Server connection that is rehosted, check the UpdateStatus column in the Rehost Essbase Connections dialog box.

If the rehost is successful, the Host/Port/Encryption in Catalog column is updated with thenew cluster or host and port information and, if applicable, encryption information. If therehost fails, an error message is displayed.

Note: If other Essbase Server connections have the same old host:port setting, rehostingone 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 linkagefor 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 whichyou are currently connected.

Note: All Essbase instances or clusters must be running for the cube linkage update to takeeffect.

3 Optional: To keep all Essbase applications running after the update, clear the Stop all Essbaseapplications 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 PerformanceManagement Architect Server or to Text Files Used as Data SourcesIf Performance Management Architect has been moved to a new host or port from the earlierrelease installation, then for all Performance Management Architect data source connectionsthat point to the earlier release location, edit the connection properties to reflect the new serverlocation. If text files used as data sources have moved to a non-default location, edit theconnection properties.


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

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 datasource you want to access.

Note: You can select only one directory per data source. Essbase Studio does not supporttext files from different subdirectories within the same directory.

c. Review the files listed under Contents of selected directory to ensure that this is the textfile data source you want to select.

4 Click Apply, and then click OK.


Updating Reporting and Analysis References to a RehostedServer 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

You must perform Essbase Server rehosting steps before you perform this step. See “UpdatingReferences to a Rehosted Essbase Server ” on page 234.


Table 37 Upgrade Tasks for Reporting and Analysis

Upgrade Task Reference

Financial Reporting - If the Essbase Server host and port have changedsince the earlier release, make updates so that Financial Reportingrecognizes the new Essbase data source.

“Updating Financial Reporting References to a RehostedEssbase Server” on page 242

Financial Reporting - Update Provider Services data sources if the ProviderServices host has changed.

In EPM Workspace, from the Tools menu, select DatabaseConnection Manager, select the database connection andthen click Edit to enter new connection information.

Web Analysis - If the Essbase Server host and port have changed sincethe earlier release, make updates so that Web Analysis recognizes thenew Essbase data source.

“Updating Web Analysis References to a Rehosted EssbaseServer” on page 242

If the Production Reporting Server has moved to a new server for thisrelease, update references to the new server.

“Updating References to a Rehosted Production ReportingServer” on page 243

Updating Financial Reporting References to a Rehosted Essbase ServerYou must perform Essbase Server rehosting steps before you perform this step. See “UpdatingReferences to a Rehosted Essbase Server ” on page 234.

If the Essbase Server host and port has changed since the earlier release, update references to theEssbase 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:



FRUpdateEssbaseServer.bat|.sh

Updating Web Analysis References to a Rehosted Essbase ServerYou must perform Essbase Server rehosting steps before you perform this step. See “UpdatingReferences to a Rehosted Essbase Server ” on page 234.

If the Essbase Server host and port has changed since the earlier release, update references to theEssbase Server host within Web Analysis where Essbase is used as a data source.

ä To update Web Analysis references to a rehosted Essbase Server:



WebAnalysisUpdateEssbaseServer.bat|sh


Updating References to a Rehosted Production Reporting ServerIf you installed Production Reporting on a different host than the earlier release, run thereshostSQRConfig utility to remap the SQR engine-related metadata from the earlier releasehost to the new host in the database. You do not need to run this utility if you installed ProductionReporting 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:

1 From a command prompt, navigate to the following directory: EPM_ORACLE_INSTANCE/bin/ReportingAnalysis/SDK.


rehostSQRConfig.bat|sh host1 host2

where host1 is the host name for the machine from which you are upgrading, and host2 isthe host name for the upgraded machine.

The script updates tables to reflect the new host.


Updating Performance Management Architect References toa Rehosted Server EnvironmentYou must perform Essbase Server rehosting steps before you perform this step. See “UpdatingReferences to a Rehosted Essbase Server ” on page 234.

Even if Essbase Server has not been rehosted, you must perform the procedure in “MappingEssbase Server Host Names to Cluster Names” on page 235.

Once those steps are completed, Performance Management Architect automatically updates itsreferences to rehosted Essbase Servers; running a script is not required.

Updating Planning References to a Rehosted ServerEnvironment and Upgrading ApplicationsYou must perform Essbase Server rehosting steps before you perform this step. See “UpdatingReferences to a Rehosted Essbase Server ” on page 234.

Use the Planning Upgrade Wizard to update references to rehosted data sources and to upgradePlanning applications. For example, if the Essbase Server host and port have changed since theearlier release, you must update data sources and update mappings from Planning applicationsto reporting applications. If the relational data source has changed, you must update data sourceconnections. The Planning Upgrade Wizard enables you to update multiple data sources andreporting applications simultaneously.


Caution! You must update references to rehosted data sources before you upgradeapplications.

Note: Before updating references to data sources, ensure that the Essbase server and therelational 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 clickUpgrade 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 serverinformation for each Planning data source. If the Essbase server host and port have changed duringupgrade, 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 relationaldatabase 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 Essbaseinformation 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 thatare 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 andconfirm 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 toproceed.


Applications that have already been upgraded are not available. The Status column indicatesthe upgrade status of each application.

The selected applications are upgraded and reregistered with Shared Services. Forapplications created in Release 9.3.3, the Upgrade Wizard upgrades identities in the Planningschema. After upgrade, applications are associated with the same project that they wereassociated with before upgrading. Any applications that were not associated with a projectare assigned to the default Shared Services project.

The administrator user that is upgrading the applications is assigned the ProvisioningManager role for those applications.

A message shows the pass and failure status. The Status column shows the details for eachapplication. 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 orupdate the Essbase server information for reporting applications.

Only applications that have already been upgraded and that have reporting applicationscreated 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 serverinformation.


l To update each reporting application individually:

a. On the bottom of the page, select the reporting applications to which to apply theupdates.

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 issuesthat 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 restartthe Planning server.



Updating Profitability and Cost Management References toa Rehosted Essbase ServerYou must perform Essbase Server rehosting steps before you perform this step. See “UpdatingReferences to a Rehosted Essbase Server ” on page 234.

If the Essbase Server host and port have changed since the earlier release, make updates so thatProfitability and Cost Management recognizes the new location.

ä To update Profitability and Cost Management references to a rehosted Essbase Server:



HPMUpdateEssbaseServer.bat


Updating Strategic Finance References to a RehostedEssbase Server or Financial Management ServerYou must perform Essbase Server rehosting steps before you perform this step. See “UpdatingReferences to a Rehosted Essbase Server ” on page 234.

If the Essbase Server host and port have changed since the earlier release, make updates so thatStrategic Finance recognizes the new location. This procedure is also required if the FinancialManagement Server has changed since the earlier release.

ä To update Strategic Finance references to a rehosted Essbase Server or FinancialManagement 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 theStrategic 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 clickUpdate Selected.

4 Repeat these steps for each rehosted server and its associated batch or map items.



Updating Performance Scorecard References to a RehostedEssbase ServerYou must perform Essbase Server rehosting steps before you perform this step. See “UpdatingReferences to a Rehosted Essbase Server ” on page 234.

If the Essbase Server host and port has changed since the earlier release, update references to theEssbase 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 RehostedServer EnvironmentYou 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 ifyou upgraded to a new machine), redefine the Integration Services ODBC DSNs on the machinehosting the new installation using the same names.

See the Oracle Essbase IntegrationServices System Administrator's Guide fordetails.

For Integration Services-deployed applications, update drill-through to point to the newIntegration Server location. This ensures that the application outline files are updated with thenew Integration Server connection information.

“Specifying an Alternate IntegrationServer for Drill-Through Reports” on page247

Specifying an Alternate Integration Server for Drill-Through ReportsFor already-deployed Essbase applications, for each OLAP metaoutline, perform the followingprocedure.

ä 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 bya colon) of the new Integration Server instance that is now used for executing drill-through reports.


If you are using Integration Server on the default port, you do not need to specify the portnumber.

4 Click OK.

You must perform a member load or select Update Drillthrough Data from the Outline menu aftermaking these changes.


Upgrading Applications from the Earlier Release to theCurrent ReleaseIf you have not already done so, upgrade applications for the following products from the earlierrelease to the current release:

l If you have been using Oracle Hyperion Public Sector Planning and Budgeting or OracleProject Financial Planning, perform optional steps before you upgrade the Planningapplications to take advantage of new features. See the Oracle Hyperion Planning Readme.

l Planning, using the Upgrade Wizard. See “Updating Planning References to a RehostedServer Environment and Upgrading Applications” on page 243. Note that if the EssbaseServer host has changed since the earlier release, you also use the Upgrade Wizard to updatereferences to data sources before you upgrade applications.

l FDM, using the Schema Update Utility. See the Oracle Hyperion Financial Data QualityManagement 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 SystemConfigurator.

l Financial Management applications are upgraded during configuration with EPM SystemConfigurator (during “Upgrade applications from earlier release” task).

l Profitability and Cost Management applications are upgraded during configuration withEPM System Configurator.


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 DataSource, 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 temporaryinternet files in Internet Explorer.

If a Financial Management application contains shared dimensions, right-click the application in the Application Viewpane and select Activate All Associations. This is required to support the dynamic properties that were introducedin 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 HyperionEnterprisePerformanceManagementArchitectAdministrator'sGuide

Because new validations were added in this release, applications that validated successfully in an earlier releasemight not validate in the current release. Review and resolve validation errors and warnings.

To validate each application, right-click the application in the Application Library and select Validate. Validationerrors are reported in the Job Console.

Oracle HyperionEnterprisePerformanceManagementArchitectAdministrator'sGuide

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

Performing Manual Configuration Tasks in an Upgrade 249

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 thenew 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 ortablespaces on target by exporting data, run a script to import Essbase data and linked reportingobjects.

“Importing Essbase Data andLinked Reporting Objects” on page250

If the upgraded application has more than 127 linked reporting objects, manually import the linkedreporting objects.

“Manually Import Linked ReportingObjects” on page 251

Oracle recommends that you make a backup of the applications. This ensures that the backup is ofthe upgraded format.

If you are an Essbase-only Business Rules user, you must migrate the Business Rules rules toCalculation Manager.

“Importing Business Rules toCalculation Manager for use withEssbase” on page 251


Importing Essbase Data and Linked Reporting ObjectsIf you replicated data to a new machine, and if you selected Consolidated disk volumes ortablespaces on target by exporting data during data replication, you must run a script to importthe Essbase data and linked reporting objects on the upgraded system. The Essbase Staging Toolprovides 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 thatis 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. Thescript prompts you to enter the password.


Manually Import Linked Reporting ObjectsIf the upgraded application has more than 127 linked reporting objects, manually import thelinked 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 releasebackup directory: (The Staging Tool replicated the linked reporting objects with the rest of the Essbasedata.)

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 EssbaseEnsure that you exported rules as described in “Performing Product-Specific UpgradePrerequisites” on page 210.

ä 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 TasksThe 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 fromrelease 11.1.1.4 to 11.1.2.3, update any drill-through reports to FDM created in Essbase Studio. The URLs forthese reports should be changed to use the new template.

“Sample FDM URLTemplate” in theOracle EssbaseStudio User's Guide

(Optional) When you upgrade, Essbase Studio properties from the earlier release are not retained. If you want touse the same settings in the upgraded release, you must re-enter them.

To customize Essbase Studio properties, see Oracle Essbase Studio User's Guide.


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

“Configuring Reporting and Analysis Framework Service Properties” onpage 252

Optionally, configure Reporting and Analysis Framework Java webapplication properties.

“Configuring Java Web Application Properties” on page 252

Import DAS datasources. “Importing DAS Data Sources” on page 253

Assign new roles “IR WebClient Viewer” and “IR HTML Viewer” toallow users to open BQY documents or job outputs.

“Assigning New Interactive Reporting Roles” on page 253

For Interactive Reporting, update dashboard objects. JavaScript update information in the “Impact Manager” section in theOracle Hyperion Reporting and Analysis Framework Administrator'sGuide

Configuring Reporting and Analysis Framework Service PropertiesWhen you upgrade, Reporting and Analysis Framework Service properties from the earlierrelease are not retained.

ä To configure Reporting and Analysis Framework Service properties:

1 In EPM Workspace, select Navigate, then Administer, then Reporting and Analysis, and thenServices.

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

Configuring Java Web Application PropertiesWhen you upgrade, Reporting and Analysis Framework Java web application properties fromthe earlier release are not retained.


ä To configure Reporting and Analysis Framework Java web application properties:

1 In EPM Workspace, select Navigate, then Administer, then Reporting and Analysis, and then WebApplications.

2 Right-click a Java web application, select Properties, review the property settings, and reset them ifneeded.

See the Oracle Hyperion Reporting and Analysis Framework Administrator's Guide for moreinformation.

Importing DAS Data SourcesPerform this step from the machine hosting Interactive Reporting or copy server.xml locallybefore importing.

ä To import DAS data sources:

1 Open the Services section of EPM Workspace (select Navigate, then Administer, then Reporting andAnalysis, 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 RolesTwo 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 HTMLviewer.

l IR WebClient Viewer role - required to open a BQY document or Job Output in theInteractive Reporting plugin.

After you upgrade, assign users these two roles as needed; the new roles are not assigned bydefault. You can assign roles in one of two ways:

l Use Shared Services to provision roles. For more information, see the Oracle EnterprisePerformance 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.javafor more details on this program and the Hyperion Reporting and Analysis FrameworkDeveloper’s Guide for details on how to run SDK programs.



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 PlanningIf 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 availablewhen you upgrade Shared Services.

Ensure that the Planning applications are upgraded to the current release and are available inCalculation 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 Configuratoris imported to Calculation Manager.

2 Repeat for each Planning application.

3 Deploy the rules from Calculation Manager to Planning. See the Oracle Hyperion Calculation ManagerDesigner's Guide.

After migrating business rules and rules security, if any of the rules had multiple launch locationsand you migrated to more than one location, Calculation Manager creates a rule for the firstmigration, and shortcuts for all subsequent migrations. If the rule had rule-level variables, forthe shortcuts that are created in the application in the new environment , its variables are movedto the Plan level. In this scenario, test rules in your environment to ensure that they work asexpected.

Migrating Business Rule SecurityIf your upgraded application used Business Rules, administrators can migrate launch accesspermissions on business rules and their projects from Business Rules to Calculation Managerbusiness 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 thespecified Planning application.

l Migrates access permissions only for users and groups that are provisioned for the specifiedPlanning 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 Oracle Hyperion Business Rules toCalculation 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:outputfile

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 commandline to read the password from the full file path and name specified in passwordFile.

No

/A:appname Specify the Planning application to which to migrate launch access permissions for businessrules

Yes

/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 theplanning1 directory. This file contains a log of the transaction, and helps withtroubleshooting.

Yes

/? 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 TasksPerform 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 256

If you changed cluster names during the upgrade, you must recreate taskflows using the new cluster name.


Reregistering Applications in EPM Workspace

ä To register applications in EPM Workspace:

1 From the Navigate menu, select Consolidation Administration, then Manage Applications, and thenReregister 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 Financeconverts the data to the upgraded format when you open the existing.alc files in the newrelease. If you are using a Client-Server implementation and point the upgraded StrategicFinance server to an existing database during configuration, it converts that database uponfirst startup, and as each entity is opened at user request. The administrator can also forceone 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 StrategicFinance migration utility to move Strategic Finance provisioningfrom the earlier release to the current release.

“Upgrading Strategic Finance Provisioning Information” on page 256

Upgrading Strategic Finance Provisioning Information

If you are upgrading from Release 11.1.1.4, use the Strategic Finance migration utility to moveStrategic 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 texteditor.

2 Specify the EPM_ORACLE_INSTANCE location in this portion of the file:


rem ******* EPM_ORACLE_INSTANCE needs to be defined, please complete the environment variable definition belowrem * ex:rem * set EPM_ORACLE_INSTANCE=C:\Oracle\Middleware\user_projects\epmsystem1rem * 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 TasksPerform 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 beforerunning any data loads. Due to a difference in structure of period mappings, period mappings are not upgradedfrom Release 11.1.1.4 to Release 11.1.2.3.

“Updating PeriodMappings” on page257


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'sGuide for details.


FDM Upgrade TasksAfter installing and configuring the upgrade, update user_projects\config\dbclient\tnsnames.ora to include entries for the Oracle Database Client that was installed by EPMSystem Installer in MIDDLEWARE_HOME/dbclient32 and MIDDLEWARE_HOME/dbclient64 sothat 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 newlocation, you are first prompted to add applications. When you add applications, for eachapplication, 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 andgroups for the first time to Shared Services.

See the Oracle Hyperion Financial Data Quality Management Configuration Guide forinformation about upgrading FDM.

Upgrading Smart ViewYou can upgrade Smart View in one of several ways:

l Have users install Smart View from EPM Workspace: from the Tools menu, select Installand then Smart View.

l Install Smart View on client machines using the Smart View installer. See “Installing EPMSystem Clients” on page 89. 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 Systemproducts, review the Oracle Hyperion Enterprise Performance Management SystemCertification Matrix for supported versions.


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 informationto plan your upgrade. There are several scenarios; use the procedure appropriate for yourdeployment. Note that in these scenarios, you must upgrade all EPM System products to thecurrent release.

Upgrading From an Environment with a Single Instance ofShared ServicesIf you are upgrading from an environment with a single instance of Shared Services (Release11.1.1.4), perform the upgrade as documented in “Upgrading Checklist” on page 207.

Perform the upgrade for Release 11.1.1.4 products first. Note that you must configureFoundation 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 areupgrading from, you must create a new instance in Release 11.1.2.3.

Upgrading From an Environment with Two Instances ofShared ServicesIf you are upgrading from an environment with two instances of Shared Services (Release 11.1.1.3or 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 Release11.1.2.3.

If you are applying the maintenance release to Financial Close Management, see “FinancialClose Management Maintenance Release Installation Checklist” on page 186.

2 Use EPM System Configurator to configure Foundation Services, Financial Close Management, andDisclosure Management.

During database configuration for Foundation Services, select Upgrade existing database tothe current release from.. and select a release number, and then select Import Data From EarlierRelease.

3 Perform any required post-configuration tasks for these products. See Chapter 9, “Performing ManualConfiguration Tasks in a New Deployment.”

Upgrading from an Environment with Multiple Releases 259

4 Using the Upgrading Checklist, upgrade all Release 11.1.1.4 products except Shared Services to Release11.1.2.3. Note that you do not need to install Shared Services again. However, you do have to exportShared Services data and perform a configuration task. Perform the upgrade tasks product by productin the following order:

l Foundation Services. Perform the tasks to export Shared Services data. See “ExportingShared Services Data from the Earlier Release” on page 213. During configuration withEPM System Configurator, when you configure Shared Services, select only Import DataFrom Earlier Release.

l Essbase

l All other products

Note: If you are upgrading multiple instances of Essbase, for each instance that you areupgrading 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 207.

5 Disclosure Management mappings from Release 11.1.2.0 or 11.1.2.1 or 11.1.2.2 are migrated toRelease 11.1.2.3 when you open a report in the Disclosure Management Client. (Mappings are migratedseparately 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 ApplicationsThe upgrade logic in this release is based on deploying a new software release and movingapplications, data, and provisioning information from the earlier deployment to the newdeployment. This approach allows the upgrade process to be repeatable. You start with a newdatabase, 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 207.

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.


12Starting and Stopping EPM

System Products

In This Chapter

Using a Single Script to Start Services... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

Launching Clients .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262

This chapter describes how to start and stop EPM System services and applications and providesdefault URLs for EPM System clients.

Before you start any services or processes, start all databases used as repositories. Once thedatabases are started, there is no required start order for EPM System with the exception ofFinancial Close Management.

Caution! If you started the SOA Server to configure Financial Close Management, stop itbefore starting EPM System services. If you are using Financial Close Management,see the required service startup order in “Financial Close Management ApplicationServer” on page 314.

Note: If you selected Run Windows Services as non-local system account and specified a user nameand 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 username and password, EPM System Configurator creates Windows services using the localsystem account. Before you start the services, change them to use the appropriate domainaccount.

Using a Single Script to Start ServicesEPM System Installer installs a single start script in EPM_ORACLE_INSTANCE/bin, calledstart.bat|sh. Running the single start script on a machine in your EPM System deploymentstarts all EPM System services installed on that machine. The single start script works by callingthe 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, thenFoundation Services, and then Start EPM System.

Using a Single Script to Start Services 261

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 whichservices on a machine are running. See Chapter 13, “Validating the Installation and VerifyingDeployment.”

A single stop script, stop.bat|sh is also installed in EPM_ORACLE_INSTANCE/bin. Runningthe stop script on a machine in your EPM System deployment stops all EPM System productson that machine.

Launching ClientsThis section describes how to launch EPM System clients. It lists default URLs and script namesas 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 thedefault 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 HyperionShared ServicesConsole

http://WebServer:Port/interop/

From the Start menu, select Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE, then Foundation Services, and then Shared Services URL.

Note: The Start menu item is available only on the machine on which you installed theWeb server.

EPM Workspace http://WebServer:Port/workspace/

From the Start menu, select Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE, then Workspace, and then Workspace URL.

Note: The Start menu item is available only on the machine on which you installed theWeb server.

DataRelationshipManagementWeb Client

http://drm_web_server_name/drm-web-client

From the Start menu, select Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE, then Data Relationship Management, and then Web Client.

DataRelationshipManagementMigration Utility

http://drm_web_server_name/drm-migration-client

From the Start menu, select Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE, then Data Relationship Management, and then Migration Utility.

DataRelationshipManagementBatch Client

N/A From a Windows command line prompt, run EPM_ORACLE_HOME/products/DataRelationshipManagement/client/batch-client/drm-batch-client.exe


N/A N/A

262 Starting and Stopping EPM System Products


AdministrationServicesConsole

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

From the Start menu, select Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE, then Essbase, then Essbase Administration Services, and then StartAdministration Services Console.

IntegrationServicesConsole

N/A From the Start menu, select Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE, then Essbase, then Integration Services, and then 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 StudioConsole

NA From the Start menu, select Programs, then Oracle EPM System, then EPM_ORACLE_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://WebServerName/HyperionFDM

N/A

FDM WorkbenchClient

N/A From the Start menu, select Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE, then Financial Data Quality Management, then Workbench, and thenWorkbench Client.

FinancialManagementClient

N/A From the Start menu, select Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE, then Financial Management, and then Financial Management.

Or

For 32-bit:

EPM_ORACLE_HOME/products/FinancialManagement/Client/HFM.exe

For 64-bit:

EPM_ORACLE_HOME/products/FinancialManagement/Client/32bit/HFM.exe

FinancialReportingStudio

N/A From the Start menu, select Programs, then Oracle, and then Financial Reporting Studio.

Or

%ProgramFiles%/Oracle/FinancialReportingStudio/HReports.exe

InteractiveReporting

N/A From the Start menu, select Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE, then Reporting and Analysis, then Interactive Reporting, and thenDashboard Architect.

From the Start menu, select Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE, then Reporting and Analysis, then Interactive Reporting, and thenDashboard Studio.

From the Start menu, select Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE, then Reporting and Analysis, then Interactive Reporting, and then Studio.

Launching Clients 263


InteractiveReportingStudio

N/A From the Start menu, select Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE, then Reporting and Analysis, then Interactive Reporting, and then Studio.

Or

EPM_ORACLE_HOME/products/biplus/bin/brioqry.exe


N/A File Generator:

From the Start menu, select Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE, then Performance Management Architect Clients, and then Start EPMA FileGenerator.

Or

EPM_ORACLE_HOME/products/Foundation/BPMA/EPMAFileGenerator/bin/EPMAFileGenerator.exe

Batch Client:

From the Start menu, select Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE, then Performance Management Architect, and then Start EPMA BatchClient.

Or

EPM_ORACLE_HOME/products/Foundation/BPMA/EPMABatchClient/epma-batch-client.bat

Planning Offline N/A None

PredictivePlanning

N/A None

ProductionReporting

N/A From the Start menu, select Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE, then Reporting and Analysis, and then Production Reporting Studio orProduction Reporting Viewer.

Smart View NA Use the Smart View menu or Oracle Hyperion Smart View for Office ribbon in MicrosoftExcel, Microsoft Word, or Microsoft PowerPoint.

StrategicFinance Client

NA From the Start menu, select Programs, then Oracle, and then Strategic Finance.

Or

EPM_ORACLE_HOME/products/hsf/bin/HSF.exe

StrategicFinance ServerAdministration

From the Start menu, select Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE, then Strategic Finance, then Server, and then Server Administration

Or

EPM_ORACLE_HOME/products/hsf/bin/HSFAdmin.exe

Oracle HyperionWeb AnalysisStudio

The Sun Java plug-in isinstalled when Web AnalysisStudio is first used. To startWeb Analysis Studio, in yourWeb browser's Address bar,enter the Web AnalysisStudio URL http://WebServer:Port/WebAnalysis

From the Start menu, select Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE, then Reporting and Analysis, and then Web Analysis URL.

264 Starting and Stopping EPM System Products

13Validating the Installation and

Verifying Deployment

In This Chapter

Validating the Installation ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265

Generating a Deployment Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267

Verifying Deployment .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268

Validating a Financial Close Management Deployment .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270

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

You must install, configure, and run EPM System Diagnostics as the same user.

PrerequisitesBefore using EPM System Diagnostics, complete these prerequisites:

l Install EPM System products. See Chapter 5, “Installing EPM System Products in a NewDeployment.”

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.

Validating the Installation 265

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

Progress is shown in the command window.

2 To view results, navigate to EPM_ORACLE_INSTANCE/diagnostics/reports and openvalidation_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 SystemInstallation 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 PerformedThe following list highlights the Oracle Hyperion Enterprise Performance Management SystemDiagnostics 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 providerconfiguration

l HTTP: http - Checks availability of HTTP context for all components configured for theWeb server.

l SSO:

266 Validating the Installation and Verifying Deployment

m Checks status of Shared Services security (Native Directory as well as externaldirectories)

m Checks availability of login to Shared Services, Taskflows, Audit, Shared Services Javaweb application, and Oracle Hyperion Enterprise Performance Management SystemLifecycle Management

l WEB: Web application - Checks availability of Java web application on host:port

l Additional product-specific tests

Generating a Deployment ReportAfter completing an EPM System deployment, you can generate a deployment report that liststhis information:

l EPM Deployment Topology Report

m Logical Web Addresses — all logical Java web applications and all Web servers that areconfigured

m Application Tier Components — the components configured for each EPM Instance inthis deployment, including the Java web application URL and domain name for eachJava web application

m Database Connections — all databases configured for EPM System products

m User Directories — user directories used by EPM System products; configured securityproviders are listed in the same order as configured in Shared Services

m Data Directories — data directories used by EPM System products, indicating thedirectories that need to be on a shared file system

l EPM Deployment History Report — configuration history of activities on the specified datefor 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 deploymentpoints to the correct number of database schemas. The deployment report is created from theShared Services Registry database. You can generate the report from any server in thedeployment, 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.


Generating a Deployment Report 267

You can add an optional file name argument to the command to save the HTML report witha 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 FoundationServices, 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 reviewthe diagnostics reports in EPM_ORACLE_INSTANCE/diagnostics/reports.

Verifying EPM Workspace Deployment and Products in EPMWorkspace


1 From the Start menu, select Programs, then Oracle EPM System, then instanceName, thenWorkspace, 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/domains/EPMSystem/servers/SERVER_NAME/logs.



4 From the EPM Workspace Help menu, select About and in the Details section verify the list of installedproducts.

5 Launch each listed product from EPM Workspace. The following products can be launched from EPMWorkspace:

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 verifydeployment, you must perform some initial tasks. See the Oracle Hyperion Profitabilityand Cost Management Administrator's Guide.

l Performance Management Architect

l Calculation Manager

l FDMEE

l Financial Close Management. To perform additional verification for Financial CloseManagement, see “Additional Verification for Financial Close Management” on page269.

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

2 Create a task using the Basic Task Type on today's date, but set the start time to be earlier than thecurrent 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 ispast its scheduled start time.

Verifying Deployment 269

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 DeploymentFinancial Close Management Validation Tool scans the system configuration settings neededfor successful functioning of Financial Close Management. Oracle recommends that you runFinancial Close Management Validation Tool after you complete the installation andconfiguration steps to test that the components for Financial Close Management are correctlydeployed 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 andFCMPORT is port 8700. You can find this information from WebLogic AdministrationConsole. To view this information, log in to the Administration Console and navigate toEnvironment, and then Servers.

2 Log in to the Financial Close Management Validation Tool with a user from the external provider. If thereare issues with the external provider configuration, log on with any seeded user (seeded both on


WebLogic Server and Shared Services native directory) and run the tool to identify issues with the externalprovider 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 ServicesServer

Host

Port

Status

Data Sources targeted

Financial CloseManaged Server

Host

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

Validating a Financial Close Management Deployment 271

The second half of the Financial Close Management Validation Tool has a utility thatgenerates 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 fixit. Before proceeding, verify that the user logged in to the Financial Close ManagementValidation 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 inTable 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 FCCTaskExecutionCompositeinstance are not deleted and you can see more details of the error from the EnterpriseManager console. If all the validation items are successful, then the test composite andinstance 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 andFCMPORT is the listening port of the FinancialClose0 managed Server in the WebLogicAdministration Console. You can find this information from WebLogic AdministrationConsole. To view this information, log in to the Administration Console and navigate toEnvironment, 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)



Foundation ServicesServer

Host

Port

Status


Financial CloseManaged Server

Host

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. Itis the responsibility of the customer to make sure that the entered values are correct. Warning can beignored.

5 Look for failed tests, diagnose, and fix problems.

6 Run Account Reconciliation Validation Tool again until all tests pass.

Validating a Financial Close Management Deployment 273

APorts

In This Appendix

Default Ports and Shared Services Registry .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275

WebLogic Administration Server Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276

WebSphere Ports.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276

Oracle Enterprise Manager Java Web Application Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

SOA Server Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

SSL Ports .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

Foundation Services Ports .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

Essbase Ports .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279

Reporting and Analysis Ports .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280

Financial Performance Management Applications Ports .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282

Data Management Ports .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285

This appendix contains information about default port numbers for EPM System productsincluding where the port can be configured.

Caution! These ports are not meant to be used to access a product. For information on startinga product, see Chapter 12, “Starting and Stopping EPM System Products.”.

Default Ports and Shared Services RegistryDuring the configuration process, default port numbers for most EPM System products areautomatically populated in Shared Services Registry. During configuration using EPM SystemConfigurator, you can change the default numbers. Each port number on the machine must beunique. (The same product on different machines can have the same port number.) If an errormessage similar to “port already in use” or “bind error” is displayed, a port number conflict mayexist.

If the default port is already in use on the machine, or if there is a conflict, EPM SystemConfigurator will not continue. If the default port number is not changed, the software isconfigured with the default values.

Default Ports and Shared Services Registry 275

WebLogic Administration Server PortTable 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 theWebLogic Administration Console.

WebSphere Ports

Subtopics

l WebSphere Application Server Port

l IBM HTTP Server Port

WebSphere Application Server PortTable 51 WebSphere Application Server Port


9043 The WebSphere Application Server port is specified during configuration. To change the default port, use theWebSphere Administration Console.

IBM HTTP Server PortTable 52 IBM HTTP Server Port

Default PortNumber

Where Configurable

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 SystemInstallation and Configuration Guide.

Note: Both IBM HTTP Server and IIS Web Server use 80 as their default port. If you are usingWebSphere, you must change one of these defaults so that there is no port conflict.

276 Ports

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

SOA Server Port

Table 54 SOA Server Port


8001 WebLogic Server Admin Console

SSL PortsFor more information about configuring SSL ports, see Oracle Enterprise PerformanceManagement System Security Configuration Guide.

Foundation Services PortsSee these sections for information about Foundation Services ports:

l “Foundation Services Ports” on page 277

l “Performance Management Architect Ports” on page 278

l “Calculation Manager Java Web Application Ports” on page 278

Foundation Services PortsThe following table describes the Foundation Services Managed Server Java web applicationports and where you can configure them. Foundation Services Managed Server includes SharedServices, 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

Oracle Enterprise Manager Java Web Application Port 277

Table 56 Web Server Ports

Server Default Server Port Where Configurable

Oracle HTTPServer

19000 MIDDLEWARE_HOME/user_projects/epmsystem1/httpConfig/ohs/config/OHS/ohs_component/httpd.conf configurable in the EPM System Configurator.

IIS 80

443 (SSL)

Microsoft Internet Information Services (IIS) Manager Console. Change the TCP port valuesetting.

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 (PerformanceManagement 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 valuesetting.

Calculation Manager Java Web Application Ports

Table 60 Calculation Manager Java Web Application Ports



278 Ports



Essbase PortsSee these sections for information about Essbase ports:

l “Essbase Ports” on page 279

l “Administration Services Ports” on page 280

l “Provider Services Ports” on page 280

l “Essbase Studio Ports” on page 280

Essbase PortsTable 61 Essbase Default Service Ports

Service Default Port Number Where Configurable

Essbase Agent 1423 EPM System Configurator

Essbase server applications(ESSSVR)

32768–33768 (two ports perprocess)

EPM System Configurator

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 SystemConfigurator, the default ports are used.

Table 62 OPMN (Oracle Process Manager and Notification Server) Default Ports


Oracle Notification ServerLocal Port

6711 Open the opmn.xml file and modify the “local” parameter. Then save the file.

Oracle Notification ServerRemote Port

6712 Open the opmn.xml file and modify the “remote” parameter. Then save the file.

Essbase Ports 279

Administration Services PortsTable 63 Administration Services Java Web Application Ports




Provider Services PortsTable 64 Provider Services Java Web Application Ports




Essbase Studio PortsTable 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 PortsSee these sections for information about Oracle Hyperion Reporting and Analysis ports:

l “Reporting and Analysis Framework Ports” on page 281

l “Financial Reporting Ports” on page 281

l “Interactive Reporting Ports” on page 282

l “Web Analysis Ports” on page 282

280 Ports

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 AnalysisFramework Agent

6860 EPM System Configurator

Reporting and AnalysisFramework Agent RMI


Reporting and AnalysisFramework Services

l Global Services Manager(GSM)

l Core Service

l Service Broker

l Job Service

l Event Service

l Repository Service

6800–6805

Each service listed in this table isassigned a port within the range,either the default range 6800–6805or the range specified duringconfiguration.

l Use EPM System Configurator when you are installing orconfiguring Reporting and Analysis Framework Services forthe first machine.

l To change a port number or find out the exact port used bya particular component: from EPM Workspace, selectNavigate, then Administer, then Reporting and Analysis, thenServices, and then the Properties dialog box of Reportingand Analysis Framework Services.

Financial Reporting Ports

Table 68 Financial Reporting Java Web Application Ports




Table 69 Financial Reporting Default Service Ports

Service Default Port Number WhereConfigurable

RMI Servicesand RemoteADM Server

8205-8228

Each Financial Reporting Java Web Application uses two ports, one for RMI services and one forRemote ADM Server (e.g., first Financial Reporting Java Web Application uses ports 8205 and 8206).

EPM SystemConfigurator

Reporting and Analysis Ports 281

Interactive Reporting PortsTable 70 Interactive Reporting Default Service Ports


l Interactive ReportingLogging Service

l Interactive ReportingIntelligence Service

l Data Access Service (DAS)

l Interactive Reporting JobService

6810, 6811 (Log Service)

6812, 6813 (IntelligenceService):

6814, 6815 (Data AccessService)

6816, 6817 (Job Service)

l Use EPM System Configurator when you are installing or configuringReporting and Analysis Framework Services for the first machine.

l To change a port number or find out the exact port used by aparticular component: from EPM Workspace, select Navigate, thenAdminister, then Reporting and Analysis, then Services, and thenthe Properties dialog of Reporting and Analysis Framework Services

Web Analysis PortsTable 71 Web Analysis Java Web Application Ports




Financial Performance Management ApplicationsPortsSee these sections for information about Oracle's Hyperion Financial Performance ManagementApplications ports:

l “Financial Management Ports” on page 283

l “Financial Close Management Ports” on page 283

l “Planning Ports” on page 284

l “Performance Scorecard Ports” on page 284

l “Strategic Finance Ports” on page 285

l “Profitability and Cost Management Ports” on page 285

l “Disclosure Management Ports” on page 285

282 Ports

Financial Management PortsTable 72 Financial Management Java Web Application Port




Table 73 Financial Management Default Service Port

Service Default PortNumber

Where Configurable

FinancialManagement Service

135-plusephemeral high-range ports (1024–5536)

Windows settings–Fix DCOM ephemeral ports.

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

FinancialManagement DMEListener Service (foruse with PerformanceManagementArchitect)


FinancialManagement ADMListener Service

9099 Update Oracle Hyperion Shared Services Registry

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

Note: The Financial Management IIS Web Applications: Financial Management Web ServicesIIS Web Application,Financial Management Smart View IIS Web Application, FinancialManagement IIS Web Application, and Financial Management LCM IIS WebApplication.

Financial Close Management PortsThe following table describes the Financial Close Management ports and where you canconfigure them.

Table 75 Financial Close Management Close Manager and Account Reconciliation Manager Java Web Application Ports

Type of Port Default Port Number Where Configurable


Financial Performance Management Applications Ports 283



Planning PortsTable 76 Planning Java Web Application Ports




Table 77 Planning RMI Server Port


Planning RMI Server 11333 EPM System Configurator

Performance Scorecard PortsTable 78 Performance Scorecard Java Web Application Ports




The following table describes the Performance Scorecard Alerter Java web application ports andwhere you can configure them.

Table 79 Performance Scorecard Alerter Java Web Application Ports




284 Ports

Strategic Finance PortsTable 80 Strategic Finance Default Service Port


Where Configurable

StrategicFinance Server


Note: If you change this port, you must also change it for each Strategic Finance client in theConnection 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 valuesetting.)

Table 82 Strategic Finance Web Application Port




Profitability and Cost Management PortsTable 83 Profitability and Cost Management Java Web Application Ports




Disclosure Management PortsTable 84 Disclosure Management Java Web Application Ports




Data Management PortsSee these sections for information about Oracle's Data Management ports.

Data Management Ports 285

l “FDM Ports” on page 286

l “FDMEE Ports” on page 286

l “Data Relationship Management Ports” on page 287

FDM PortsThe following table describes the FDM default service ports and where you can configure them.

Table 85 FDM Default Service Ports


Where Configurable

FDM loadbalancerandFDMapplicationserver

135-plusephemeralhigh-rangeports (1024–65536)

Windows settings–Fix DCOM ephemeral ports.

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

File sharing 137–139,445

Controlled by the operating system. By default, file sharing is enabled between all FDMapplication serversand 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 plusephemeralhigh-rangeports (1024–65536)

Windows settings—Fix DCOM ephemeral ports.

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

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



FDMEE PortsThe following table describes the FDMEE Java web application ports and where you canconfigure them.

286 Ports

Table 87 FDMEE Java Web Application Ports




Data Relationship Management PortsThe following table describes the Data Relationship Management default service ports and whereyou can configure them.

Table 88 Data Relationship Management Default Service Port


Data Relationship Managementserver applications

5200–5400 drm-config.xml using the Data Relationship Management Console.

The following table describes the Data Relationship Management Web server ports and whereyou can configure them.

Table 89 Data Relationship Management Web Server Ports

Default Web Server Ports Where Configurable


Data Management Ports 287

288 Ports

BJDBC URL Attributes

In This Appendix

JDBC Drivers .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289

JDBC DriversDuring configuration, on the Configure Database page, click Advanced to specify additionalJDBC 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 JDBCdrivers.

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

JDBC Drivers 289

Property SQL Server DB2

DATABASENAME Yes Yes

For Oracle Database parameters, see the Oracle Thin JDBC Driver documentation.

URL for Oracle RACTo provide client-side failover and load-balancing for Oracle RAC, enter the URL in the formof:

dbc:hyperion:oracle//server1:1521;ServiceName=TEST;AlternateServers=(server2:1521,server3:1521,server4:1521);LoadBalancing=true

LDAP-Based URL for Oracle DatabaseOracle Database supports authentication using an LDAP server. To use LDAP-based databaseauthentication, enter the URL in the following format:

jdbc:oracle:thin:@ldap://oid:5000/mydb1,cn=OracleContext,dc=myco,dc=com

URL for SSLTo 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 orMicrosoft 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)

)

)

290 JDBC URL Attributes

CDatabase Information for

Financial Management

In This Appendix

Database Connection Pooling ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291

Database Connection PoolingDuring Financial Management configuration, you specify the maximum number of relationaldatabase connections used by each application. Financial Management uses connection poolingto communicate with the database. Connection pooling enables more efficient databaseutilization 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 pooleddatabase connections. The number of connections that you specify in EPM System Configuratoris the maximum number of pooled connections consumed by an application. The pool startswith eight connections. If, after a certain number of attempts, the pool is unable to service arequest for an additional connection, it adds eight more connections. The system continuesadding blocks of eight connections until it reaches the maximum number of connections definedin the utility. If the system needs an additional connection beyond this limit, a temporaryconnection 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 notused 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. Theuser 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 reservedfor each application server, and 17 connections reserved for each application. The DME Listenerprocess also consumes up to eight connections. These connections stay open for as long as thisprocess is running.

Connection use is dependent on the activity type. Users with Read access, which are the majorityof users in an application, generally use one or no connections. Users with Write access canconsume more connections, as they write to the database. The number of connections consumedby a user with Write access, for example, a consolidator, depends on the application server

Database Connection Pooling 291

hardware and quantity of data being written. In general, users with Write access may use 5 – 10connections.

Financial Management opens the defined number of connections when an application is firstopened. The connections are then available for subsequent users of the system. If a user processrequests a connection, and all connections are in use, the system polls the connection pool fora short time, waiting for an available connection. If no connection is available, the system createseight connections and adds them to the pool. The connection pool is limited to the total thatyou define in EPM System Configurator.

Connections are application-specific. The default pool is created only after an application isopened. 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 serveractivity are released as well. If any one application remains open, the application serverconnections stay open as well.

If the Financial Management Service is running, connections are allocated and released on anapplication basis. When no users are logged in to a given application, it shut downs and allconnections consumed by that application are released.

If the Financial Management Service is not running, then after the last user logs out of anapplication all connections allocated for that application are released. If the FinancialManagement Service is running, then connections are released when the machine is restartedor 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 ofall applications if the Financial Management Service is running, because the serviceperpetuates application instances. In addition, in an environment with more than oneFinancial Management application server, all users might need to log out of allapplications on all servers before the application process shuts down and the databaseconnections are released. In both cases, you must also stop the Financial Managementservice.

Financial Management also supports Extended Analytics, which enables extracting data to arelational database for use with other systems, such as Analytic Services. The extract process hasa dedicated connection pool that is created when a star schema is created. The default pool is 16temporary connections that are destroyed when the processing is complete.

Example 1Three applications on one application server, default maximum connection pooling is used (40connections)

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)

292 Database Information for Financial Management

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 thesystem 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 2One application on two application servers, default maximum connection pooling is used (40connections)

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 lostbecause 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 deletingan application, Financial Management opens the application to verify security access, consumingthe default number of connections. After security is validated, the system deletes the application.

Database Connection Pooling 293

294 Database Information for Financial Management

DEPM System Services

In This Appendix

EPM System Services and Processes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296

This appendix provides details about start menus, service names, and start and stop scripts foreach EPM System component.

Note that Start menu items for Java web applications are available only on the machine on whichthe Web server is installed.

You can monitor the health and performance of the EPM System Java web applications usingOracle Enterprise Manager, which is automatically deployed with Oracle Hyperion EnterprisePerformance Management System Configurator if you deploy Java web applications with OracleWebLogic 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 EnterpriseManager to Monitor EPM System Java Web Applications” in the Oracle Enterprise PerformanceManagement System Deployment Options Guide.

295

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 isEPMServerN, where N is 0 for the managed server, and 1 or higher if you scale out the singlemanaged server.

Web ServerThe following table describes the services and processes for the Web server if you used the OracleHTTP 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 andNotification Server Administrator's Guide Release 11g (11.1.1.2.0) (http://download.oracle.com/docs/cd/E15523_01/doc.1111/e14007/toc.htm)

296 EPM System Services



Table 90 Web Server Services and Processes

InformationType

Details

Display Namein WindowsServicesControl Panel

l Oracle Process Manager (ohsInstanceInstanceNumber)

l IIS: IIS Admin Service

l IBM HTTP Server 7.0

Descriptionl 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 torun Web, FTP, NNTP, or SMTP sites or configure IIS. If this service is disabled, any services that explicitly depend onit will fail to start.

l IHS: IBM_HTTP_Server/7.0.0.17 (Win32)

WindowsStartup Script(For OracleHTTP Serverinstalled byEPM SystemInstaller only)

EPM_ORACLE_INSTANCE/bin/startOHS.bat

Note that this start script redirects Oracle HTTP Server to start using OPMN. The OPMN start script opmnctl.bat islocated in EPM_ORACLE_INSTANCE/httpConfig/ohs/bin.

UNIX StartupScript (ForOracle HTTPServerinstalled byEPM SystemInstaller only)

EPM_ORACLE_INSTANCE/bin/startOHS.sh

Note that this start script redirects Oracle HTTP Server to start using OPMN. The OPMN start script opmnctl is locatedin EPM_ORACLE_INSTANCE/httpConfig/ohs/bin

Windows StopScript (ForOracle HTTPServerinstalled byEPM SystemInstaller only)

EPM_ORACLE_INSTANCE/bin/stopOHS.bat

UNIX StopScript (ForOracle HTTPServerinstalled byEPM SystemInstaller only)

EPM_ORACLE_INSTANCE/bin/stopOHS.sh

Foundation Services Application ServerThe following table describes the services and processes for the Oracle Hyperion FoundationServices application server, which includes Oracle Hyperion Shared Services, and OracleHyperion Enterprise Performance Management Workspace Java web applications.

EPM System Services and Processes 297

Table 91 Foundation Services Application Server Services and Processes

Information Type Details

Windows StartMenu Command

Select Start, then Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE_NAME, then FoundationServices, and then Start FoundationServices

Registered ServiceName

HyS9FoundationServices_instanceName

Display Name inWindows ServicesControl Panel

Oracle Hyperion Foundation Services - Managed Server (instanceName)

Description Hyperion Foundation Services support Hyperion applications, including authentication, user provisioning, task flowmanagement, data and metadata synchronization

Windows StartupScript

EPM_ORACLE_INSTANCE/bin/startFoundationServices.bat

UNIX Startup Script EPM_ORACLE_INSTANCE/bin/startFoundationServices.sh

Windows StopScript

EPM_ORACLE_INSTANCE/bin/stopFoundationServices.bat

UNIX Stop Script EPM_ORACLE_INSTANCE/bin/stopFoundationServices.sh

Performance Management Architect Dimension ServerServicesThe following table describes the services and processes for the Performance ManagementArchitect services.

Note: When the Dimension Server and the database are hosted on different servers, startup timecan take several minutes, because Performance Management Architect makes calls to thedatabase during startup.

Table 92 Performance Management Architect Services


Windows Start MenuCommand

N/A

Registered Service Name HYS9EPMAServer_instanceName

Display Name in WindowsServices Control Panel

Oracle Hyperion EPMA Server (instanceName)

Description Hyperion EPM Architect Dimension Server provides the back services needed by the EPMA Web Tier,including dimensionality, applications, and the jobs console.



Windows Startup Script EPM_ORACLE_INSTANCE/bin/StartEpmaServer.bat

UNIX Startup Script NA

Windows Stop Scriptl Process Manager: EPM_ORACLE_INSTANCE/bin/stopEpmaServer.bat

UNIX Stop Script NA

Performance Management Architect Application ServerThe following table describes the services and processes for the Performance ManagementArchitect application server.

Table 93 Performance Management Architect Application Server Services and Processes



Select Start, then Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE_NAME, then FoundationServices, then Performance Management Architect, and then startEpmaWebReports


HyS9EPMAWebTier_instanceName


Oracle Hyperion EPMA Web Tier - Java Web Application (instanceName)

Description Provide access service to EPMA Web Server


EPM_ORACLE_INSTANCE/bin/startEpmaWebReports.bat

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 SynchronizerApplication ServerThe following table describes the services and processes for the Oracle Hyperion EPM ArchitectData Synchronizer application server.


Table 94 Performance Management Architect Data Synchronizer Application Server Services



Select Start, then Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE_NAME, then FoundationServices, then Performance Management Architect, and then startEPMADataSync


HyS9EPMADataSynchronizer_instanceName


Oracle Hyperion EPMA Data Synchronizer - Java Web Application (instanceName)

Description Provide access service to EPMA Data Synchronizer Web Server


EPM_ORACLE_INSTANCE/bin/startEPMADataSync.bat

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 ServerThe following table describes the services and processes for Oracle Hyperion CalculationManager.

Table 95 Calculation Manager Services and Processes



Select Start, then Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE_NAME, then CalculationManager, and then Start CalcMgr


HyS9CALC_instanceName


Oracle Hyperion CALC Manager - Java Web Application (instanceName)

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


Essbase ServerDuring installation, Oracle Hyperion Enterprise Performance Management System Installerinstalls 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 stopEssbase Server:

l opmnctl startall

l opmnctl stopall

If you are using Essbase in a clustered environment, there are additional steps required to set upEssbase failover on both nodes of the cluster. See “Editing OPMN.XML for Active-PassiveEssbase Clusters” in the Oracle Enterprise Performance Management System Deployment OptionsGuide.

The following table describes additional methods for starting and stopping Essbase Server. Notethat the Essbase Server start and stop scripts redirect to OPMN.

For information about OPMN, see the Oracle® Fusion Middleware Oracle Process Manager andNotification 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

InformationType

Details

WindowsStart MenuCommand

Select Start, then Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE_NAME, then Essbase, thenEssbase Server, and then Start Essbase

This command launches startEssbase.bat (and redirects to OPMN).

RegisteredService Name

Oracle Process Manager_instanceName


Oracle Process Manager_instanceName

Description OPMN service for Essbase (instanceName)




InformationType

Details

WindowsStartupScript

l Essbase Server — EPM_ORACLE_INSTANCE/bin/startEssbase.bat (redirects to OPMN)

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 thislocation 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 StartupScript

l Essbase Server — EPM_ORACLE_INSTANCE/bin/startEssbase.sh (redirects to OPMN)

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 thislocation 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 StopScript

Server:

l Essbase Server — EPM_ORACLE_INSTANCE/bin/stopEssbase.bat (redirects to OPMN)

UNIX StopScript

Server:

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 arerunning on the server. To stop Essbase Server, you need Administrator permissions.

See the Oracle Essbase Database Administrator's Guide for more information about shuttingdown Essbase Server.

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

Administration Services ServerThe following table describes the services and processes for the Oracle Essbase AdministrationServices server.


Table 97 Administration Services Application Server Service/Process



Select Start, then Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE_NAME, then Essbase, thenEssbase Administration Services, and then Start EssbaseAdminServices


Hys9eas_instanceName


Oracle Hyperion Administration Services - Java Web Application (instanceName)

Description HyS9eas - Controls the running of an Applications Server


EPM_ORACLE_INSTANCE/bin/startEssbaseAdminServices.bat

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 ServerThe following table describes the services and processes for the Integration Services server.

Table 98 Integration Services Server Service/Process



Select Start, then Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE_NAME, then Essbase, thenIntegration Services, and then Start Essbase Integration Server1


Essbase Integration Server_instanceName


Oracle Hyperion Integration Services (instanceName)

Description N/A


EPM_ORACLE_INSTANCE/bin/startEisServer.bat

UNIX StartupScript

EPM_ORACLE_INSTANCE/bin/startEisServer.sh

Windows StopScript

EPM_ORACLE_INSTANCE/bin/stopEisServer.bat

Note that you must manually stop the Integration Services service manually using the Task Manager.



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 theolapisvr command, and on using the ais.cfg file, see the Essbase Integration Services System Administrator's Guide.

Essbase Studio ServerThe following table describes the services and processes for the Essbase Studio server.

Table 99 Essbase Studio Server



Select Start, then Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE_NAME, then Essbase,then Essbase Studio, and then Start Server


HYS9EssbaseStudio_instanceName


Oracle Hyperion Essbase Studio Server (instanceName)

Description NA


EPM_ORACLE_INSTANCE/bin/startBPMS_bpms1_Server.bat

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 controlledby a combination of an Essbase Studio Server property (server.runInBackground), EPMSystem 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.runInBackgroundproperty 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'sGuide 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


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 ServerThe following table describes the services and processes for the Oracle Hyperion ProviderServices application server.

Table 100 Provider Services Application Server Services and Processes



Select Start, then Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE_NAME, then Essbase, thenProvider Services, and then Start AnalyticProviderServices


HyS9aps_instanceName


Oracle Hyperion Provider Services - Java Web Application (instanceName)

Description Provide access service to Hyperion Provider Services


EPM_ORACLE_INSTANCE/bin/startAnalyticProviderServices.bat

UNIX Startup Script EPM_ORACLE_INSTANCE/bin/startAnalyticProviderServices.sh

Windows StopScript

EPM_ORACLE_INSTANCE/bin/stopAnalyticProviderServices.bat

UNIX Stop Script EPM_ORACLE_INSTANCE/bin/stopAnalyticProviderServices.sh


Hyperion Reporting and Analysis Framework - Agent ServiceThe following table describes the services and processes for the Reporting and AnalysisFramework Agent.

Table 101 Reporting and Analysis Framework Agent



Select Start, then Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE_NAME, then Reportingand Analysis, and then Start RA Framework Agent


HyS9RaFrameworkAgent_instanceName


Oracle Hyperion Reporting and Analysis Framework (instanceName)

Description HyS9RaFrameworkAgent - Hyperion Reporting and Analysis Framework Agent


EPM_ORACLE_INSTANCE/bin/startRaFrameworkAgent.bat

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 FrameworkAgent ServiceWhen the Reporting and Analysis Framework Agent is started, these additional services andprocesses are started:

l Oracle Hyperion Interactive Reporting process.

l Reporting and Analysis Framework common services and processes

Reporting and Analysis Framework Application ServerThe following table describes the services and processes for the Reporting and AnalysisFramework application server.


Table 102 Reporting and Analysis Framework Application Server



Select Start, then Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE_NAME, then Reporting andAnalysis, 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


HyS9RaFramework_instanceName


Oracle Hyperion Reporting and Analysis Framework - Java Web Application (instanceName)

Description HyS9RaFramework - Hyperion Reporting and Analysis Framework web application


EPM_ORACLE_INSTANCE/bin/startRaFramework.bat

UNIX StartupScript

EPM_ORACLE_INSTANCE/bin/startRaFramework.sh

Windows StopScript

EPM_ORACLE_INSTANCE/bin/stopRaFramework.bat

UNIX Stop Script EPM_ORACLE_INSTANCE/bin/stopRaFramework.sh

Financial Reporting Application ServerThe following table describes the services and processes for the Financial Reporting applicationserver, which includes the Financial Reporting Print Server.

Table 103 Financial Reporting Application Server Services and Processes



Select Start, then Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE_NAME, then Reportingand Analysis, and then Start FinancialReporting


HyS9FRReports_instanceName


Oracle Hyperion Financial Reporting - Java Web Application (instanceName)

Description Provide access service to Hyperion Financial Reporting Web Server


EPM_ORACLE_INSTANCE/bin/startFinancialReporting.bat

UNIX Startup Script EPM_ORACLE_INSTANCE/bin/startFinancialReporting.sh



Windows Stop Script EPM_ORACLE_INSTANCE/bin/stopFinancialReporting.bat

UNIX Stop Script EPM_ORACLE_INSTANCE/bin/stopFinancialReporting.sh

Web Analysis Application ServerThe following table describes the services and processes for the Oracle Hyperion Web Analysisapplication server.

Table 104 Web Analysis Application Server Services and Processes



Select Start, then Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE_NAME, then Reporting andAnalysis, and then Start Reporting and Analysis Web Analysis


HyS9WebAnalysis_instanceName

Display Name inWindows Control

Oracle Hyperion Web Analysis - Java Web Application (instanceName)

Description Provide access service to Hyperion Web Analysis - Web Application


EPM_ORACLE_INSTANCE/bin/startWebAnalysis.bat

UNIX Startup Script EPM_ORACLE_INSTANCE/bin/startWebAnalysis.sh

Windows StopScript

EPM_ORACLE_INSTANCE/bin/stopWebAnalysis.bat

UNIX Stop Script EPM_ORACLE_INSTANCE/bin/stopWebAnalysis.sh

Planning Application ServerThe following table describes the services and processes for the Planning application server.

Table 105 Planning Application Server Services and Processes



Select Start, then Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE_NAME, then Planning,and then Start Planning


HyS9Planning_instanceName




Oracle Hyperion Planning - Java Web Application (instanceName)

Description Provides access service to Planning Web server


EPM_ORACLE_INSTANCE/bin/startPlanning.bat

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 ServicesThe following table describes the services and processes for Financial Management.

Table 107 Financial Management Services and Processes

InformationType

Details

Windows StartMenuCommand


InformationType

Details

RegisteredService Name

l HYS9FinancialManagementService_instanceName

l HYS9 FinancialManagemen DMEListener_instanceName

l HYS9FinancialManagementWebServiceManager_instanceName


l Oracle Hyperion Financial Management – Management Service (instanceName)

l Oracle Hyperion Financial Management – DME Listener (instanceName)

l Oracle Hyperion Financial Management – Web Service Manager (instanceName)

Descriptionl 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 withthe Hyperion Data Movement Engine. If this service is stopped, the DME Web service will not be able to communicatewith all HFM instances on this server.

l Manages the session information for connection in the Financial Management web server.

WindowsStartup Script

l EPM_ORACLE_INSTANCE/bin/startHFMManagementService.bat

l EPM_ORACLE_INSTANCE/bin/startHFMDMEListener.bat

l EPM_ORACLE_INSTANCE/bin/startHFMWebServiceManager.bat

UNIX StartupScript

NA

Windows StopScript

l EPM_ORACLE_INSTANCE/bin/stopHFMManagementService.bat

l EPM_ORACLE_INSTANCE/bin/stopHFMDMEListener.bat

l EPM_ORACLE_INSTANCE/bin/stopHFMWebServiceManager.bat

UNIX StopScript

NA

Note: The synchronization between Financial Management application servers is based onsystem time. Changing the clock can affect this synchronization. For the time change toand from Daylight Savings Time, Oracle recommends that you stop the servers before thetime change and restart them afterward.

Financial Management Application ServerThe following table describes the services and processes for the Financial Management Java webapplication server, which includes FM Web services and FM ADF Java web application.


Table 108 Financial Management Java Web Application Services and Processes



Select Start, then Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE_NAME, then FinancialManagement, and then Start HFMWeb


HyS9FinancialManagementWeb_instanceName


Oracle Hyperion Financial Management - Web Tier (instanceName)

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 ServerThe following table describes the services and processes for Strategic Finance.

Table 109 Strategic Finance Services and Processes



Select Start, then Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE_NAME, then StrategicFinance, then Server, and then Start Strategic Finance Service


HYS9HsfSrv_instanceName


Oracle Hyperion Strategic Finance - Server (instanceName)

Description Provides Oracle Hyperion Strategic Finance, Fusion Edition services including entity repository management,authentication, access control, consolidation, data and metadata management


EPM_ORACLE_INSTANCE/bin/startStrategicFinanceService.bat


Windows Stop Script EPM_ORACLE_INSTANCE/bin/stopStrategicFinanceService.bat

UNIX Stop Script NA


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



Select Start, then Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE_NAME, then StrategicFinance, and then Start HSFWeb

Registered Service Name HyS9HsfWeb_instanceName


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 ServerThe following table describes the services and processes for the Performance Scorecardapplication server.

Note: If you are using Essbase as a data source for Performance Scorecard, you must start OracleEssbase first.

Table 111 Performance Scorecard Application Server Services and Processes



Select Start, then Programs, then Oracle EPM System, then Scorecard, and then Start HpsWebReports

Registered Service Name WebReports


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



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 ServerThe following table describes the services and processes for the Oracle Hyperion PerformanceScorecard 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 ServicesControl Panel

Oracle Hyperion Performance Scorecard Alerter - Java Web Application (instanceName)

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 ServerThe following table describes the services and processes for Oracle Hyperion Profitability andCost Management.

Table 113 Profitability and Cost Management Services and Processes



Select Start, then Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE_NAME, then Profitability,and then Start Profitability


HyS9HyS9PftWeb_instanceName


Oracle Hyperion Profitability - Java Web Application (instanceName)



Description Provides a Workspace module for Profitability.


EPM_ORACLE_INSTANCE/bin/startProfitability.bat

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 ServerThe following table describes the services and processes for Oracle Hyperion DisclosureManagement.

Table 114 Disclosure Management Services and Processes



Select Start, then Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE_NAME, then DisclosureManagement, and then Start Disclosure Management


HyS9Disclosure_instanceName


Oracle Hyperion Disclosure Management - Java Web Application (instanceName)

Description Provide access service to Disclosure Management


EPM_ORACLE_INSTANCE/bin/startDisclosureManagement.bat

UNIX Startup Script EPM_ORACLE_INSTANCE/bin/startDisclosureManagement.sh

Windows StopScript

EPM_ORACLE_INSTANCE/bin/stopDisclosureManagement.bat

UNIX Stop Script EPM_ORACLE_INSTANCE/bin/stopDisclosureManagement.sh

Financial Close Management Application ServerThe following table describes the services and processes for the Financial Close Managementapplication server, which includes Close Manager and Account Reconciliation Manager.


Note: Ensure that you complete the post-configuration tasks before you start Financial CloseManagement. See “Financial Close Management Manual Configuration Tasks ” on page177.

Caution! If you started the SOA Server to configure Financial Close Management, stop itbefore 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 you’re using Oracle HyperionFinancial Management with Financial Close Management

m FDM Web application, if you’re using FDM with Financial Close Management

m Financial Reporting Java web application, if you’re using Oracle Hyperion FinancialReporting 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



Select Start, then Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE_NAME, then FinancialClose, and then Start FinancialClose


HyS9FinancialClose_instanceName


Oracle Hyperion Financial Close Management - Java Web Application (instanceName)

Description Provide access service to Financial Close Manager Java Web Application


EPM_ORACLE_INSTANCE/bin/startFinancialClose.bat

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


Data Relationship ManagementThe following table describes the services and processes for Data Relationship Management.

Table 116 Data Relationship Management Services and Processes



From the Start menu, select Programs, then Oracle EPM System, then Data Relationship Management, thenConfiguration Console or EPM_ORACLE_HOME/ products/DataRelationshipManagement/server/bin/drm-server-console.exe


Oracle DRM Server Processes


Oracle DRM Server Processes

Description Handles starting and stopping of required server applications in the Oracle DRM environment

Windows StartupCommand

Net start “Oracle DRM Server Processes”


Windows StopCommand

Net stop “Oracle DRM Server Processes”

UNIX Stop Script: NA

In addition, Oracle Data Relationship Management has a Web tier component that runs in IIS.

FDMThe following table describes the services and processes for FDM.

Table 117 FDM Task Manager Services and Processes



Select Start, then Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE_NAME, then FinancialData Quality Management, then Task Manager, and then Task Manager


HyS9FDMTaskManagerSrv_instanceName


Oracle Hyperion Financial Data Quality Management - Task Manager (instanceName)

Description Provides the ability to schedule Hyperion Financial Data Quality Management tasks


EPM_ORACLE_INSTANCE/bin/startFDMTaskManager.bat




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 componentthat runs in IIS.

FDMEE Application ServerThe following table describes the services and processes for Oracle Hyperion Financial DataQuality Management, Enterprise Edition.

Table 118 FDMEE Services and Processes



Select Start, then Programs, then Oracle EPM System, then EPM_ORACLE_INSTANCE_NAME, then FDMEnterprise Edition, and the Start ErpIntegrator


HyS9aifWeb_instanceName


Oracle Hyperion FDM Enterprise Edition - Java Web Application (instanceName)

Description Provides a Workspace module for ERPI


EPM_ORACLE_INSTANCE/bin/startERPIntegrator.bat

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


Glossary

active-active high availability system A system in which all the

available members can service requests, and no member is

idle. An active-active system generally provides more

scalability options than an active-passive system. Contrast

with active-passive high availability system.

active-passive high availability system A system with active

members, which are always servicing requests, and passive

members that are activated only when an active member

fails. Contrast with active-active high availability system.

application server cluster A loosely joined group of

application servers running simultaneously, working

together for reliability and scalability, and appearing to

users as one application server instance. See also vertical

application cluster and horizontal application cluster.

assemblies Installation files for EPM System products or

components.

asymmetric topology An Oracle Fusion Middleware Disaster

Recovery configuration that is different across tiers on the

production site and standby site. For example, an

asymmetric topology can include a standby site with fewer

hosts and instances than the production site.

backup A duplicate copy of an application instance.

cluster An array of servers or databases that behave as a

single resource which share task loads and provide failover

support; eliminates one server or database as a single point

of failure in a system.

cluster interconnect A private link used by a hardware cluster

for heartbeat information, to detect node failure.

cluster services Software that manages cluster member

operations as a system. With cluster services, you can define

a set of resources and services to monitor through a

heartbeat mechanism between cluster members and to

move these resources and services to a different cluster

member as efficiently and transparently as possible.

Disaster Recovery The ability to safeguard against natural or

unplanned outages at a production site by having a recovery

strategy for applications and data to a geographically

separate standby site.

EPM Oracle home A subdirectory of Middleware home

containing the files required by EPM System products. The

EPM Oracle home location is specified during installation

with EPM System Installer.

EPM Oracle instance A directory containing active, dynamic

components of EPM System products (components that

can change during run-time). You define the EPM Oracle

instance directory location during configuration with EPM

System Configurator.

external authentication Logging on to Oracle EPM System

products with user information stored outside the

application. The user account is maintained by the EPM

System, but password administration and user

authentication are performed by an external service, using

a corporate directory such as Oracle Internet Directory

(OID) or Microsoft Active Directory (MSAD).

failover The ability to switch automatically to a redundant

standby database, server, or network if the primary

database, server, or network fails or is shut down. A system

that is clustered for failover provides high availability and

fault tolerance through server redundancy and fault-

tolerant hardware, such as shared disks.

hardware cluster a collection of computers that provides a

single view of network services (for example, an IP address)

or application services (such as databases and Web servers)

to clients of these services. Each node in a hardware cluster

is a standalone server that runs its own processes. These

processes can communicate with one another to form what

looks like a single system that cooperatively provides

applications, system resources, and data to users.

Glossary 319

high availability A system attribute that enables an

application to continue to provide services in the presence

of failures. This is achieved through removal of single points

of failure, with fault-tolerant hardware, as well as server

clusters; if one server fails, processing requests are routed to

another server.

horizontal application server cluster A cluster with application

server instances on different machines.

identity A unique identification for a user or group in

external authentication.

installation assemblies Product installation files that plug in

to EPM System Installer.

Java web application server cluster An active-active application

server cluster of Java Virtual Machines (JVMs).

lifecycle management The process of migrating an

application, a repository, or individual artifacts across

product environments.

load balancer Hardware or software that directs the requests

to individual application servers in a cluster and is the only

point of entry into the system.

load balancing Distribution of requests across a group of

servers, which helps to ensure optimal end user

performance.

locale A computer setting that specifies a location's

language, currency and date formatting, data sort order, and

the character set encoding used on the computer. Essbase

uses only the encoding portion. See also encoding,

ESSLANG.

logical address for web applications An aliased reference used

to identify the internal host name, port, and context of a

Web application. In a clustered or high-availability

environment, this is the alias name that establishes a single

internal reference for the distributed components. In EPM

System, a nonclustered logical address for a web application

defaults to the physical host running the web application.

managed server An application server process running in its

own Java Virtual Machine (JVM).

Middleware home A directory that includes the Oracle

WebLogic Server home and can also include the EPM Oracle

home and other Oracle homes. A Middleware home can

reside on a local file system or on a remote shared disk that

is accessible through NFS.

migration The process of copying applications, artifacts, or

users from one environment or computer to another; for

example, from a testing environment to a production

environment.

migration log A log file that captures all application migration

actions and messages.

migration snapshot A snapshot of an application migration

that is captured in the migration log.

native authentication The process of authenticating a user

name and password from within the server or application.

Oracle home A directory containing the installed files

required by a specific product, and residing within the

directory structure of Middleware home. See also

Middleware home.

permission A level of access granted to users and groups for

managing data or other users and groups.

provisioning The process of granting users and groups

specific access permissions to resources.

proxy server A server acting as an intermediary between

workstation users and the Internet to ensure security.

relational database A type of database that stores data in

related two-dimensional tables. Contrast with

multidimensional database.

repository Storage location for metadata, formatting, and

annotation information for views and queries.

restore An operation to reload data and structural

information after a database has been damaged or

destroyed, typically performed after shutting down and

restarting the database.

role The means by which access permissions are granted to

users and groups for resources.

scalability The ability to resize a system, making it larger or

smaller. With regard to increases, "scale vertically" or "scale

up" refers to expanding a single machine's capability. To

"scale horizontally" or "scale out" refers to adding more

machines.

security agent A Web access management provider (for

example, Oracle Access Manager, Oracle Single Sign-On, or

CA SiteMinder) that protects corporate Web resources.

320 Glossary

security platform A framework enabling Oracle EPM System

products to use external authentication and single sign-on.

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.

WebLogic Server home A subdirectory of Middleware home

containing installed files required by a WebLogic Server

instance. WebLogic Server home is a peer of Oracle homes.

Glossary 321

322 Glossary

Index

Symbols.NET installation, 51

AActiveX, enabling, 54Administration Services

application serverUNIX startup scripts, 302Windows service names, 302

default ports, 280starting, 302

ais.cfg file, 304application server deployment

time changes, 140WebLogic, 119

applications, upgrading, 248apply maintenance release, 185ARBORPATH, 131architecture, EPM System, 21assemblies, 63

Bbrowsers, 52. See also Web browsersbusiness rules

migrating , 254migrating launch access permissions, 201migrating to Calculation Manager rules, 188, 190,

200, 211, 254upgrading to Calculation Manager rules, 210

CCalculation Manager

launching from EPM Workspace, 262starting, 300UNIX startup script, 300Windows Service Name, 300

Windows startup script, 300Calculation Manager, default ports, 278checklist

applying maintenance release, 185installing, 65upgrading, 207

clustering, 104clustering methodologies per product, 54common settings, 121configuration, 175. See also postconfiguration tasksconfiguration sequence

overview, 103SSL, 105upgrading, 226

configuringcommand line, 148common settings, 121database, 115, 117distributed environment, 104Essbase, 130FDM, 148Financial Close Management, 146Financial Management, 137instance home, 113logs, 151overview, 97Performance Scorecard, 145prerequisites, 98procedure, 109Reporting and Analysis, 135sequence, 103shared drive, 68Shared Services registration, 123silent, 148SSL, 121Strategic Finance, 145task selection, 114task summary, 106

A B C D E F H I J L M N O P R S T U V W X Z

Index 323

troubleshooting, 151upgrade procedure, 226Web server, 128WebLogic deployment, 119

connection pooling, 291

DData Relationship Management

default ports, 287default URLs, 262starting, 316Windows service names, 316

database configuration, 115advanced options, 117Shared Services, 123

database connection pooling, 291database requirements

IBM DB2, 45Microsoft SQL Server, 44Oracle Database, 40

database roles and privilegesIBM DB2, 46Microsoft SQL Server, 44Oracle Database, 40

databasesIBM DB2 requirements, 45Microsoft SQL Server requirements, 44Oracle Database requirements, 40preparing, 39

DCOM, 137default URLs, 262deploying Web applications manually, 153deployment

verifying, 268WebLogic, 119

diagnostics, 265Disclosure Management

default ports, 285starting, 314Windows service name, 314Windows startup script, 314

Disclosure Managementstarting, 314Windows service name, 314Windows startup script, 314

disk space and RAM requirementsclient software, 36

server software, 37DISPLAY variable, 78distributed installation, 79downloading

installation files, 63

EEPM Oracle Home, 17, 84EPM Oracle Instance, 17EPM Oracle instance, 113EPM System Diagnostics, 265EPM System products

overview, 15EPM Workspace

default URLs, 262FDMEE, default ports, 286FDMEE

postconfiguration tasks, 183starting, 317Windows service names, 317

error logsdiagnostics, 266troubleshooting, 151upgrading, 206

Essbasemaintenance release installation prerequisites, 189postconfiguration tasks, 175rehosting, 234standalone mode, 150

Essbase, default ports, 279Essbase Server

configuring, 130legacy security, 132starting, 301starting with OPMN, 301UNIX startup script, 301

Essbase Studiostarting, 304UNIX startup scripts, 304Windows startup scripts, 304

Essbase Studio, default ports, 280essbase.cfg file, 130, 131ESSLANG , 132Lifecycle Management export import location, 123exporting data, 216


324 Index

FFDM

configuring, 148default URLs, 262starting, 316Windows service names, 316

FDM, default ports, 286Financial Close Management

configuring, 146starting, 314UNIX startup scripts, 314Windows service name, 314Windows startup script, 314

Financial Close Managementconfiguration prerequisites, 101installation prerequisites, 69maintenance release installation prerequisites, 186,

191postconfiguration tasks, 177

Financial Managementapplication server

Windows service names, 310configuring, 137database connection pooling, 291DCOM configuration, 137default ports, 283launching from EPM Workspace, 262starting, 309, 310statement caching, 43Windows service names, 309

Financial Managementapplication server

Windows service names, 310configuring, 137database connection pooling, 291DCOM configuration, 137default ports, 283launching from EPM Workspace, 262starting, 309, 310Windows service names, 309

Financial Reportingapplication server

UNIX startup script, 307Windows service names, 307

default ports, 281Foundation Services

application server


default ports, 277starting, 297

HHBRMigrateSecurity.cmd utility, 201

IIBM AIX

setting user limits on 64-bit platforms, 176IBM DB2 database requirements, 45

roles and privileges, 46size, 46tablespace, 47

IBM HTTP Server, 276configuring, 170

IIS, 50installation

validating, 265installation assemblies, 63

downloading, 63installation checklist, 65

maintenance release, 185installation files, preparing, 63installation prerequisites, 74

Financial Close Management, 69Oracle HTTP Server, 76

installingby component, 85, 86by tier, 85, 86destination, 84distributed environment, 79procedure, 81sequence, 79shared drive, 68silent, 87, 88types, 85

instance home, configuring, 113Oracle BI EE integration, 80Integration Services

starting, 303UNIX startup script, 303Windows service names, 303

Interactive Reportingstarting and stopping, 306


Index 325

Interactive Reporting, default ports, 282

JJava application servers. See Web application serversJava web application servers, 49JDBC URL attributes, 289JDBC URLs, 117

LLDAP-based JDBC URLs, 117, 289legacy security, Essbase Server, 132Lifecycle Management

configuring for high availability, 123logs

configuration, 151diagnostics, 266Oracle HTTP Server, 77upgrading, 206, 232zip file of all logs for troubleshooting, 151

Mmaintenance installation, 85maintenance release

installation checklist, 185installation prerequisites, 188

Financial Close Management, 186, 188, 189, 191manual deployment, 106, 153manual Web server configuration, 163Microsoft Internet Information Services (IIS), 50Microsoft SQL Server database requirements, 44

roles and privileges, 44size, 44

Microsoft SQL Server Windows Authentication, 116Middleware Home, 17, 84migrating

business rules, 254launch permissions to business rules, 201

Nnew installation, 85

OOPMN

starting Essbase Server, 301OPMN default ports, 279

Oracle Configuration Manager, configuring, 126Oracle Database requirements, 40

roles and privileges, 40size, 41tablespace, 41

Oracle Enterprise Manager deployment, 120Oracle HTTP Server

installation logs, 77manual configuration, 163

Oracle HTTP Server Web serverUNIX startup script, 296Windows service names, 296

Oracle HTTP Server installation prerequisites, 76Oracle instance, 113Oracle RAC, 116, 117, 125, 289Oracle SOA Suite installation prerequisites, 69Oracle Software Delivery Cloud, 63

PPerformance Management Architect

application serverWindows service names, 299

Data Synchronizer application serverWindows service names, 299

default ports, 278launching from EPM Workspace, 262starting, 298Windows service names, 298

Performance Scorecardapplication server


configuring, 145default ports, 284default URLs, 262launching from EPM Workspace, 262starting, 312

Performance Scorecard Alerterapplication server


Planningapplication server


launching from EPM Workspace, 262starting, 308


326 Index

Planning, default ports, 284ports, 275, 277postconfiguration tasks, 175

FDMEE , 183Essbase, 175Financial Close Management, 177general tasks, 198Reporting and Analysis, 176

prerequisites, 63configuration, 98installation, 74

Financial Close Management, 69, 74Oracle HTTP Server, 76Oracle SOA Suite, 69

installation and configuration, 16maintenance release, 188

Financial Close Management, 186, 188, 189, 191upgrading, 210

Profitability and Cost Managementlaunching from EPM Workspace, 262starting, 313UNIX startup scripts, 313Windows service name, 313Windows startup script, 313

Profitability Managementdefault ports, 285

Provider Servicesapplication server


starting, 305Provider Services, default ports, 280

RRAC, 116, 125, 289registration, Shared Services, 123registry. See Shared Services Registryrehosting, 234reinstalling, 85

procedure, 81release numbers supported for upgrading, 206replicating data, 216Reporting and Analysis

configuring, 135default ports, 280launching from EPM Workspace, 262postconfiguration tasks, 176

Reporting and Analysis Frameworkapplication server


starting, 306response files

silent configuration, 148silent installation, 87, 88

Ssequence

configuring, 103installing, 79upgrading, 207

service names. See Windows service namesshared drive, 68Shared Services

default ports, 277Shared Services Console

default URLs, 262Shared Services Registry, 18, 123

ports, 275silent configuration, 148

response files, 148silent installation, 87, 88

response file, 87single managed server deployment, 119size guidelines

IBM DB2, 46Microsoft SQL Server, 44Oracle Database, 41

SOA serverstarting, 102

SSL, 125, 277. See also SSL portconfiguration sequence, 105configuring, 121enabling, 125ports, 277

SSL configuration, 105SSL port

WebLogic, 120standalone mode for Essbase, 150start script, 261start scripts

manually deployed Web applications, 161, 162startup dependencies, 261statement caching in Financial Management, 43


Index 327

stop script, 261Strategic Finance

configuring, 145default ports, 285starting, 311, 312Windows service names, 311, 312

Ttablespace

IBM DB2, 47Oracle Database, 41

task selection, configuration, 114tiers, EPM System architecture, 21troubleshooting, 151, 265

UUNIX startup scripts, 261

Administration Services application server, 302,306

Calculation Manager, 300Essbase Studio Server, 304Financial Close Management, 314Financial Reporting application server, 307Foundation Services application server, 297Integration Services, 303Interactive Reporting, 306Oracle HTTP Server Web server, 296Performance Scorecard Alerter application server,

313Performance Scorecard application server, 312Planning application server, 308Profitability and Cost Management, 313Provider Services application server, 305Essbase Server, 301Web Analysis application server, 308

upgrading, 85, 205applications, 248checklist, 207configuring, 226database preparation, 39from an environment with multiple releases, 259logs, 206postconfiguration steps, 249preparing data, 213prerequisites, 210procedure, 81

rehosting procedures, 234replicating data, 216supported paths, 206

URLs, default, 262user limits

64–bit AIX, 176UTF8, 40, 46utilities

HBRMigrateSecurity, 201

Vvalidating installation, 265verifying deployment

WebLogicAdministration Services, 270Calculation Manager, 269EPM Workspace, 268FDMEE, 269Financial Close Management, 269Financial Management, 269Financial Reporting, 269Performance Management Architect, 269Performance Scorecard, 269Planning, 269Production Reporting, 269Profitability and Cost Management, 269Provider Services, 270Shared Services, 268Web Analysis, 269

vertical scaling, 54

WWeb Analysis

application serverUNIX startup script, 308Windows service names, 308

Web Analysis, default ports, 282Web application servers, 49

IBM WebSphere, 49Web applications

deploying in a distributed environment, 79manually deploying, 153

Web browserpreparing, 52settings, 52

Web server


328 Index

configuring, 128manually configuring, 163

Web servers, 50Microsoft Internet Information Services (IIS), 50

WebLogicdeployment, 119manually deploying, 153single managed server deployment, 119

WebLogic Admin Server port, 276WebLogic Server, 49WebSphere, 49, 276WebSphere Application Server

applying a maintenance release installation, 185deploying Web applications, 167

Windows service names, 261Performance Management Architect application

server, 299, 302, 306Calculation Manager, 300Data Relationship Management, 316Disclosure Management, 314FDMEE, 317FDM, 316Financial Close Management, 314Financial Management, 309Financial Management application server, 310Financial Reporting application server, 307Foundation Services application server, 297Integration Services, 303Oracle HTTP Server Web server, 296Performance Management Architect, 298Performance Management Architect Data

Synchronizer application server, 299Performance Scorecard application server, 312Performance Scorecard Alerter application server,

313Planning application server, 308Profitability and Cost Management, 313Provider Services application server, 305Strategic Finance, 311, 312Web Analysis application server, 308

Windows startup scriptsAdministration Services, 302Calculation Manager, 300Disclosure Management, 314Essbase Studio Server, 304Financial Close Management, 314Foundation Services , 297

Integration Services, 303Interactive Reporting, 306Oracle HTTP Server Web server , 296Profitability and Cost Management, 313Provider Services, 305Reporting and Analysis Framework, 306Essbase Server, 301

XXvfb

for AIX 5L, 77for HP-UX, 78setting the display, 78

Zzip files

downloading, 63


Index 329


330 Index

oracle® enterprise performance management...

Documents