Sunteți pe pagina 1din 330

Oracle® Enterprise Performance Management System

Installation and Configuration Guide Release 11.1.2.3 Updated: November 2013

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 respective owners.

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

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS:

Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle 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 not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

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

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 and Production

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

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

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

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 in a 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

Financial Reporting Maintenance Release Installation Prerequisites

191

Maintenance Release Installation Prerequisites if You Are Using Oracle Web Services Manager

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 that had some Java web applications deployed to a single managed server and some Java web applications 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 Maintenance Installation

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 Earlier Release

214

Copying Files for Temporary Use During Configuration

215

Replicating Data

216

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 Provider Services 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 Server Environment

243

Updating Planning References to a Rehosted Server Environment and Upgrading Applications

243

Updating Profitability and Cost Management References to a Rehosted Essbase Server

246

Updating Strategic Finance References to a Rehosted Essbase Server or Financial Management 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

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

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

 

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

Documentation Accessibility

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

Access to Oracle Support

Oracle customers 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.

1 About EPM System Product Installations
1 About EPM System Product Installations
1 About EPM System Product Installations

1

1 About EPM System Product Installations
1 About EPM System Product Installations
1 About EPM System Product Installations
1 About EPM System Product Installations

About EPM System Product Installations

1 About 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 Products

Check the Oracle Documentation Library (http://www.oracle.com/technology/documentation/ epm.html) on Oracle® Technology Network to see whether an updated version of this guide is available.

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

l

Oracle Hyperion Foundation Services

m

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

m

Optionally, Oracle HTTP Server

m

Oracle WebLogic Server

m

Oracle Hyperion EPM Architect

m

Oracle Hyperion Calculation Manager

m

Oracle 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

l

Oracle Hyperion Reporting and Analysis

m

Oracle Hyperion Reporting and Analysis Framework

m

Oracle Hyperion Interactive Reporting

m

Oracle Hyperion Financial Reporting

m

Oracle Hyperion SQR Production Reporting

m

Oracle Hyperion Web Analysis

l

Oracle's Hyperion Financial Performance Management Applications

m

Oracle Hyperion Planning (including Oracle Hyperion Capital Asset Planning, Oracle Hyperion Workforce Planning, and Oracle Hyperion Public Sector Planning and Budgeting)

m

Oracle Hyperion Financial Management

m

Oracle Hyperion Performance Scorecard

m

Oracle Hyperion Strategic Finance

m

Oracle Hyperion Profitability and Cost Management

m

Oracle Hyperion Disclosure Management

m

Oracle Hyperion Financial Close Management

l

Oracle's Data Management

m

Oracle Hyperion Financial Data Quality Management

m

Oracle Hyperion Financial Data Quality Management, Enterprise Edition

m

Oracle Data Relationship Management

Assumed Knowledge

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

l

Security and server administration skills

l

Windows administration skills and or UNIX/Linux administration skills

l

Java web application server administration skills.

l

A strong understanding of your organization's security infrastructure, including authentication providers such as Oracle Internet Directory, LDAP, or Microsoft Active Directory, and use of SSL

l

A strong understanding of your organization's database and server environments

l

A strong understanding of your organization's network environment and port usage

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

Middleware Home

A Middleware home consists of the Oracle WebLogic Server home, and, optionally, one or more Oracle homes, including EPM Oracle home. A Middleware home can reside on a local file system or on a remote shared disk that is accessible through Network File System (NFS).

The Middleware home location is defined during the first product installation on the computer. Subsequent installations on the computer use the previously defined location. The default installation directory is Oracle/Middleware. The Middleware home location is referred to as MIDDLEWARE_HOME throughout this document.

EPM Oracle Home

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

Components of EPM System products are installed in the EPM Oracle home directory under the Middleware home. The default EPM Oracle home location is MIDDLEWARE_HOME/ EPMSystem11R1. In addition, common internal components used by the products are installed in EPM Oracle home. Choose the location carefully to ensure that the location has enough disk space for all products that you are installing on the machine. You cannot change the location.

The EPM Oracle home location is defined in the system environment variable called EPM_ORACLE_HOME. The EPM Oracle home location is referred to as EPM_ORACLE_HOME throughout this document.

In a distributed environment, the EPM Oracle home directory structure must be the same on each machine.

EPM Oracle Instance

An EPM Oracle instance contains one or more system components such as Oracle HTTP Server, Essbase Server, as well as one or more Java web applications in one or more domains. The directory structure of an Oracle instance is separate from the directory structure of the Oracle home. It can reside anywhere; it need not be within the Middleware home directory.

The default location for the EPM Oracle instance is MIDDLEWARE_HOME/user_projects/ epmsystem1. The EPM Oracle instance location is referred to as EPM_ORACLE_INSTANCE throughout this document.

Java web applications are deployed to MIDDLEWARE_HOME/user_projects/domains/

domainName.

Typically, if you are installing all products on a single machine, for the first product you configure, you create a new EPM Oracle instance. For each product after that, you modify the existing EPM Oracle instance. If you are installing in a distributed environment, create a new EPM Oracle instance on each machine.

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

About the Shared Services Registry

The Oracle Hyperion Shared Services Registry is part of the database that you configure for Foundation Services. Created the first time that you configure EPM System products, the Shared Services Registry simplifies configuration by storing and reusing the following information for most EPM System products that you install:

l

Initial configuration values such as database settings and deployment settings

l

The computer names, ports, servers, and URLs you use to implement multiple, integrated, EPM System products and components

l

Essbase failover content

Configuration changes that you make for one product are automatically applied to other products used in the deployment.

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

Characters Supported for Installation and Configuration

The following characters are supported during installation and configuration with Oracle Hyperion Enterprise Performance Management System Installer and Oracle Hyperion Enterprise Performance Management System Configurator.

Table 1

Characters Supported for Installation and Configuration

Fields

Supported Characters

Blocked Characters

 

PATH

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

All others

 

Host name

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

All others

 

EPM System supports IPv6 addresses. However, during installation and configuration, you must enter the host name, not the IPv6 address.

 

User name

Alphanumeric characters including non-English (extended and double-byte) characters, except for the blocked characters

+ * /

#

[

]

{

}

(

)

;

:

,

@ ! “

Fields

Supported Characters

Blocked Characters

 

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

Alphanumeric characters including non-English (extended and double-byte) characters, except for the blocked characters

+ . - * \ / #

[

]

{

}

(

)

;

: , @

!

MIDDLEWARE_

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

Do not use any of the following symbols or symbol combinations in the directory that you specify for EPM_ORACLE_HOME or MIDDLEWARE_HOME during installation or EPM_ORACLE_INSTANCE during configuration:

HOME, EPM_

ORACLE_HOME and

 

EPM_ORACLE_

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.

INSTANCE

/t

 

\t

\b

.

2 EPM System Architecture
2 EPM System Architecture
2 EPM System Architecture

2

2 EPM System Architecture
2 EPM System Architecture
2 EPM System Architecture
2 EPM System Architecture

EPM System Architecture

2 EPM 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 Architecture

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

A middle-tier application server is required. WebLogic Server is provided with a default

installation. You can also use another supported application server. See the Oracle Enterprise Performance Management System Certification Matrix (http://www.oracle.com/technetwork/ middleware/ias/downloads/fusion-certification-100350.html) for a list of supported application servers.

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

The following sections contain diagrams that illustrate the component architecture for EPM System products. To obtain information about the communication between EPM System components, see “Oracle Enterprise Performance Management System Communication Flows”

in the EPM System 11.1.2.3 Documentation Library (Deployment and Installation tab) at http://

Note:

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

Tip:

For optimum viewing of the component architecture diagrams in PDF format, try increasing the view magnification to 120%.

Disclosure Management Components

format, try increasing the view magnification to 120%. Disclosure Management Components 2 2 EPM System Architecture

Essbase Components

Essbase Components Essbase Components 2 3

FDM Components

FDM Components FDMEE Components 2 4 EPM System Architecture

FDMEE Components

FDM Components FDMEE Components 2 4 EPM System Architecture

Financial Close Management Components

Financial Close Management Components Stand-Alone Financial Close Management Deployment Requirements for Test and

Stand-Alone Financial Close Management Deployment Requirements for Test and Production

A stand-alone version of Financial Close Management can be deployed independently of other EPM System products in a two-server deployment as specified below. The following specification supports 500 users (175 active).

Table 2

Financial Close Management Deployment Specifications

Machine

 

Products

Processor/

 

Memory

Server 1

l

WebLogic Admin Server

4

Core 2 CPU –

l

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

16GB

l

Oracle SOA Suite

l

Oracle HTTP Server

Server 2

l

Financial Close Management Java Web application (Close Manager and Account Reconciliation Manager)

4

Core 2 CPU –

16GB

l

FDMEE Java Web application

Financial Management Components

Financial Management Components 2 6 EPM System Architecture

Performance Management Architect Components

Performance Management Architect Components Performance Management Architect Components 2 7

Planning Components

Planning Components 2 8 EPM System Architecture

Profitability and Cost Management Components

Profitability and Cost Management Components Profitability and Cost Management Components 2 9

Reporting and Analysis Components

Reporting and Analysis Components Strategic Finance Components 3 0 EPM System Architecture

Strategic Finance Components

Reporting and Analysis Components Strategic Finance Components 3 0 EPM System Architecture

Stand-AloneStrategic Finance Deployment Requirements for Test and Production

A stand-alone version of Strategic Finance can be deployed independently of other EPM System products in a one-server deployment as specified below. The following specification supports 50 active users.

Table 3

Strategic Finance Deployment Specifications

Machine

Products

Processor/Memory

Server 1

l

Shared Services Java Web application

4 Core 2 CPU – 16GB on Windows 2008 R2

l

Strategic Finance Web application

l

Strategic Finance Server

l

Oracle HTTP Server

3 Preparing Your Environment
3 Preparing Your Environment
3 Preparing Your Environment

3

3 Preparing Your Environment
3 Preparing Your Environment
3 Preparing Your Environment
3 Preparing Your Environment

Preparing Your Environment

3 Preparing 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 Updates

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

Resolving Port Conflicts

For information about default port numbers for EPM System products, including where the port can be configured, see Appendix A, “ Ports.”.

Disabling User Access Control

In Windows 2008 environments, disable User Access Control (UAC) on each server in the deployment. This can be done through User Accounts in the Control Panel by clicking on Change User Account Control Settings, and then dragging the slider to Never notify.

UAC must remain disabled in order for EPM System server components to function properly. UAC can be enabled on end-user client desktops.

Setting the DCOM Default Authentication Level (Windows

2008)

For machines hosting products that require .NET Framework 4.0, the DCOM default authentication level should be set to Connect (this is the default value).

ä To set the authentication level for DCOM to Connect:

1 In the Control Panel, select Administrative Tools and then Component Services.

2 Navigate to Component Services, then Computers, and then My Computer.

3 Right-click My Computer and select Properties.

4 Select the Default Properties tab.

5 For Default Authentication Level, select Connect.

Note:

For earlier Windows versions, set the value to None.

Synchronizing Clocks

The clock on each server must be synchronized to within one second difference. To accomplish this, point each server to the same network time server. Refer to your operating system documentation for more information.

Resolving Host Names

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

EPM System uses 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|sh). An archive of the utility (epmsys_hostname.zip) is available in EPM_ORACLE_HOME/ common/config/11.1.2.0. Run the utility after installation and before configuration.

Disabling Anti-virus Software

Antivirus software can cause performance issues with EPM System products if, each time you access any resource on the server, the antivirus software tries to open and scan the object. To prevent these issues, exclude the EPM Oracle home directory from automatic antivirus scans and scan this directory only at scheduled times.

Shared File System

If you are configuring for high availability, you must set up a shared file system using UNC syntax that is accessible from all the servers in the deployment for the following:

l

Oracle Hyperion Enterprise Performance Management System Lifecycle Management artifacts

l

Reporting and Analysis Repository data

l

Essbase Server (UNIX) application location (ARBORPATH)

l

Performance Scorecard attachment files

Optionally, you can also use the shared file system for the following:

l

Installation files downloaded from Oracle Software Delivery Cloud

l

Oracle HTTP Server configuration files to simplify configuration in a distributed environment

l

Strategic Finance data

l

FDMEE application data

l

Essbase Studio sample and customer data source text files

Preparing User Accounts

Windows:

l

Do not use the Administrator user to install and configure. Run EPM System Installer and EPM System Configurator as a user with administrator rights. Install and configure as an administrator and as the same user for all EPM System products.

l

Assign local policies if required by your product. For Windows, the user ID typically requires “Act as part of the OS, Bypass Traverse Checking, Log on as a batch job, and Log-on as a service.”

l

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

l

When you upgrade, apply a maintenance release, or patch this server, use the same user account that was used to install and configure the earlier release.

UNIX

l

Prepare a user account (not the root user). Install and configure as the same user for all EPM System products. On UNIX machines, for all Oracle products, the user that is installing must be part of the same group; the group must have write permission to the central inventory (oraInventory).

l

If you have installed any other Oracle products, the user who will be installing EPM System products must be in the same group as the user who installed the other Oracle products. For example, both users must be part of oinstall. If you are upgrading EPM System products,

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

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

l

Contain at least one uppercase letter

l

Contain at least one numeral

l

Be at least eight characters long

l

Contain no special characters

Disk Space and RAM

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

Client Disk Space and RAM

Disk space and RAM requirements are approximate. The installation program checks for twice the required disk space, based on your product installation choices.

The recommended RAM requirement for all clients is 1 GB.

Note:

Web browser clients have no disk space requirements beyond those of the Web browser.

Product Family

Component

Disk Space (Minimum) 1

Notes

EPM System Installer

EPM System Installer and all EPM System product assemblies

16

GB

After installation, the installation files and assemblies can be removed.

Foundation Services

Common client components

400

MB

 
 

Smart View for Office

100

MB

 
 

Performance Management Architect

20

MB

File generator and batch client components only

Essbase

Essbase Runtime Client

150

MB

 
 

Administration Services Console

300

MB

 
 

Integration Services Console

90

MB

 
 

Essbase Studio Console

80

MB

 

Reporting and Analysis

Oracle Hyperion Financial Reporting Studio

400

MB

 

Product Family

Component

Disk Space (Minimum) 1

Notes

 

Oracle Hyperion Interactive Reporting Studio

700

MB

 
 

Oracle Hyperion Dashboard Development Services

190

MB

 
 

Oracle Hyperion SQR Production Reporting Studio

90

MB

 
 

Oracle Hyperion SQR Production Reporting Activator

30

MB

 
 

Production Reporting Remote

10

MB

 
 

Production Reporting Viewer

40

MB

 
 

Oracle Hyperion Web Analysis Studio

40

MB

 

Financial Performance Management 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

 

1 Disk space does not include the common client components installed on the machine with Foundation Services.

Server Disk Space and RAM

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

Component

Disk Space (Minimum)

RAM (Minimum)

WebLogic Server

1.4

GB

500 MB

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

 

Oracle HTTP Server (optional component)

1.2

GB

1 GB

Common Oracle libraries

900

MB

NA

Shared Services

800

MB 1

1.5 GB

Component

Disk Space (Minimum)

RAM (Minimum)

Performance Management Architect

 

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 Programming Interface

40

MB

256

MB

Administration Services

1

GB 2

32 MB multiplied by the number of concurrent Administration Services users

 

For example, 32 MB * 10 users = 320 MB

Integration Services

 

340

MB

256

MB

Provider Services

 

680

MB

340

MB

Essbase Studio Server

 

120

MB

256

MB

Reporting and Analysis Framework

2

GB

1

GB

For services: 400 MB

For services: 1 GB

 

For importing files: 2 GB

Financial Reporting

 

400

MB

1 GB

 

Interactive Reporting

1

GB

1 GB

 

Production Reporting

 

400

MB

256

MB

Web Analysis

2

GB

1

GB

Financial Management Server

 

64

GB (10 GB available)

4

GB

Database Server for Financial Management

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

GB 4

Strategic Finance Server

 

700

MB 5

2

GB

Profitability and Cost Management

8

GB

2

GB

Disclosure Management

8

GB

4

GB

FDM Database Server

l

Dependent on size of the FDM application

1

GB per 75 concurrent users (2 GB minimum)

l

Multiple HDDs to spread processing

 

FDM folder structure

Dependent on size of the FDM application

NA

 

Component

Disk Space (Minimum)

RAM (Minimum)

FDM Application Server

400

MB

2

GB per 75 concurrent users

FDM Web Server

400

MB

2

GB

FDMEE

300

MB

2

GB

Data Relationship Management Database Server

15 GB

2

GB

Data Relationship Management Application Server

500

MB

2

GB

1 This number is for the base Shared Services installation. If using Lifecycle Management functionality, Oracle recommends that you significantly increase disk space because application artifacts are exported and stored in the Shared Services file system.

2 Allow extra disk space for data files and outline files that are copied to Administration Services during data loading and outline editing, respectively.

3 Requirements for Oracle SOA Suite are not included.

4 1 GB includes Performance Scorecard and Alerter servers.

5 Sufficient storage should be included to contain the entities, their backup archives, administrative and transaction files, and user background task logs, such as consolidation reports.

Note:

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

Preparing a Database

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

EPM System supports 32-bit as well as 64-bit versions of all supported databases; however, the version of the database should match the operating system. For example, a 64-bit database version can be used only on a 64-bit operating system.

In general, the database should be in the same data center as the EPM System deployment. To prevent timeout issues when configuring with EPM System Configurator, you cannot locate a database in a remote location where there is latency.

For simplicity and ease of deployment, you can use one database repository for all products (with the exceptions noted below). In some cases you might want to configure separate databases for products. Consider performance, rollback procedures for a single application or product, and disaster recovery plans.

The following products and product components require unique databases:

l

Performance Management Architect interface data source

l

Extended Analytics for Financial Management and Extended Analytics for Strategic Finance

l

Planning – Each Planning application should have its own repository.

l

Performance Scorecard

l

Data Relationship Management. See the Oracle Hyperion Data Relationship Management Installation Guide.

Upgrade Note!

If you are upgrading from a previous release of EPM System products, see Chapter 11, “Upgrading EPM System Products” for information about replicating or reusing databases.

Using an Oracle Database

This section includes information about Oracle database installation, database creation, required roles and privileges, sizing guidelines, and configuration.

Note:

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

Oracle Database Creation Considerations

The database must be created using Unicode Transformation Format UTF-8 encoding (character set). Oracle supports the following character sets with UTF-8 encoding:

l

AL32UTF8 (UTF-8 encoding for ASCII platforms)

l

UTF8 (backward-compatible encoding for Oracle)

l

UTFE (UTF-8 encoding for EBCDIC platforms)

Oracle Database Privileges

The following privileges must be granted to the owners of the database schemas:

l

CREATE ANY SYNONYM

l

CREATE CLUSTER

l

CREATE INDEXTYPE

l

CREATE PROCEDURE

l

CREATE SEQUENCE

l

CREATE SESSION

l

CREATE TABLE

l

CREATE TRIGGER

l

CREATE TYPE

l

CREATE VIEW

l

DROP ANY SYNONYM

l

UNLIMITED TABLESPACE

Oracle Database Sizing Guidelines

Oracle recommends that you set tablespaces with Auto Extend ON. The following table describes the Oracle Database sizing guidelines.

Product

Sizing Guideline

 

Shared Services & EPM Workspace

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

Performance

Oracle recommends starting with at least 250MB.

Management

Architect

Administration

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

Services

Essbase Studio

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

Reporting and

The amount of space needed depends on the aggregate size of the objects that you plan to store in the repository. Oracle recommends starting with at least 250 MB, which provides space to expand the Reporting and Analysis repository without having to increase the data file or tablespace. A shared pool size of 60 MB is used during configuration with EPM System Configurator.

Analysis

Planning and

l

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

Calculation Manager

l

200 MB for applications with 15,000 or fewer total members

Note:

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

Financial

l

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

Management and

200 MB for applications with 15,000 or fewer total members

Calculation Manager

l

Note:

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

Performance

500 MB

 

Scorecard

 

Profitability and Cost Management

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—All

l

Consider a global view of tablespaces and allocate one or more tablespaces in order to spread out tables created by EPM System products.

products

l

Tablespaces can be shared with other applications.

l

Create a separate tablespace for indexes to improve performance. This action requires CREATE TABLESPACE system privileges.

l

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

Reporting and

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

Analysis

Financial

Set up a temporary tablespace greater than 1GB.

Management

FDM

See the Oracle Hyperion Financial Data Quality Management Adapter for Financial Management DBA Guide.

Data

l

Set the initial tablespace size to 1 GB

Relationship

Extents to 500 MB

Management

l

l

Turn Auto Extend ON

See the Oracle Hyperion Data Relationship Management Installation Guide

Other Parameters

The following table describes other Oracle Database parameters.

Product

Other Parameters

General/AllProducts

Set ALTER SYSTEM SET as follows:

ALTER SYSTEM SET processes=1000 SCOPE=SPFILE;

Financial Management

Set Oracle OPEN_CURSORS to 5000.

Performance Scorecard

Set Oracle OPEN_CURSORS to 1500 or greater.

FDM

See the Oracle Hyperion Financial Data Quality Management Adapter for Financial Management DBA Guide.

Operating System Configuration for Oracle Database

For Reporting and Analysis, set the necessary environment variables:

l

(UNIX/Linux)

m

ORACLE_HOME

m

PATH

m

(Solaris/Linux) LD_LIBRARY_PATH

m

(AIX) LIBPATH

m

(HP) SHLIB_PATH

Enabling Statement Caching for Financial Management

If you use Oracle Database Client 10.2.x or 11.1.x for Financial Management, you must set the StmtCacheSize registry setting for Oracle OLE DB to 10 on all Financial Management application servers. This is due to a memory issue in Oracle Provider for OLE DB.

The registry setting path is:

Hkey_Local_Machine\Software\Oracle\Key_Homename\Oledb

Note that the 11.2.x Oracle Database Client should not be changed.

ä To resolve the high memory usage:

1 Enable Statement Caching.

The configured value must not be zero. The recommended value is between and 1 and 10.

2 Edit the following registry value:

Hkey_Local_Machine\Software\Oracle\Key_Homename\Oledb Value Name:

StmtCacheSize Value (decimal): 1

where Key_Homename refers to the appropriate Oracle Home

3 Stop and restart the HFM application processes.

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

Using an Existing Oracle Database Client

For a new installation, if you want to use your existing Oracle Database Client instead of the one installed with EPM System, during EPM System installation clear the selection from Oracle Database Client 32-bit and Oracle Database Client 64-bit under Foundation Services. Then, after installing and configuring Oracle EPM System, perform the following steps:

1. On the machine hosting Foundation Services, update the TNS_ADMIN environment variable to point to the location of the existing Oracle Database Client's tnsnames.ora file location.

2. Move TNS entries from EPM_ORACLE_INSTANCE/user_projects/config/dbclient/

tnsnames.ora (which is populated during database configuration) to the existing tnsnames.ora file. Copy the entire file contents and append to the existing contents of the

tnsnames.ora file.

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

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

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

1. On the machine hosting Foundation Services, update the TNS_ADMIN environment variable to point to the location of the existing Oracle Database Client's tnsnames.ora file location.

2. Move TNS entries from EPM_ORACLE_INSTANCE/user_projects/config/dbclient/

tnsnames.ora to the existing tnsnames.ora file. Copy the entire file contents and append to the existing contents of your tnsnames.ora file.

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

<MIDDLEWARE_HOME>\dbclient32\BIN;

<MIDDLEWARE_HOME>\dbclient64\BIN;

Using a Microsoft SQL Server Database

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

Microsoft SQL Server Database Creation Requirements

When creating a Microsoft SQL Server database for use as a repository, ensure that you set these options:

l

Set READ_COMMITTED_SNAPSHOT = ON

l

Set ALLOW_SNAPSHOT_ISOLATION = ON

l

Select the SQL Server and Windows authentication option when you set the security properties for the database.

l

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

Microsoft SQL Server Roles and Privileges

Database users must be assigned ownership of the database, which provides DB_OWNER privileges,

and BULK_INSERT.

Note:

For FDM, Windows accounts that run MSSQL Server Windows service must have read access to the FDM Data folder.

Microsoft SQL Server Sizing Guidelines

The following table describes the Microsoft SQL Server sizing guidelines.

Product

Sizing Guideline

 

Shared Services

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

EPM Workspace

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

Performance

Oracle recommends starting with at least 250 MB.

Management

Architect

Administration

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

Services

Essbase Studio

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

Planning and

l

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

Calculation Manager

l

200 MB for applications with 15,000 or fewer total members

Note:

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

Financial

l

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

Management and

200 MB for applications with 15,000 or fewer total members

Calculation Manager

l

Note:

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

Performance

500 MB

 

Scorecard

 

Profitability and Cost Management

Oracle recommends starting with at least 250 MB.

Data Relationship

l

Set the initial file size to 1 GB

Management

l

Turn on Auto Growth and set to 10%

FDM

See the Oracle Hyperion Financial Data Quality Management Adapter for Financial Management DBA Guide.

Using an IBM DB2 Database

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

IBM DB2 Installation Information

During IBM DB2 installation, consider:

l

When installing IBM DB2, clear the OLAP Starter Kit option.

l

For Performance Management Architect, ensure that your DB2 database is installed on a different computer, and not on the Dimension Server machine where the DB2 9 Runtime Client and DB2 .NET Data Provider must be installed.

Note:

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

l

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

l

For Reporting and Analysis, ensure that the IBM DB2 Client Application Enabler is installed on the computers on which you install services. For Core Services and Job Factory Service, if you use an IBM DB2 RDBMS, and Reporting and Analysis Services are on separate machines, use the Client Application Enabler to create a client connection to the Reporting and Analysis database.

IBM DB2 Database Creation Considerations

For the best compatibility with non-ASCII character sets, an IBM DB2 database must be created using Unicode Transformation Format UTF-8 encoding (character set). Use of UTF-8 is required if you need multilingual support (multicharacter set support).

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

IBM DB2 Roles and Privileges

Database users must be assigned the following privileges:

l

CREATETAB

l

BINDADD

l

CONNECT

IBM DB2 Sizing Guidelines

The following table describes the IBM DB2 sizing guidelines.

Product

Sizing Guideline

Shared Services

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

EPM Workspace

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

Performance

Oracle recommends starting with at least 250 MB.

Management

Architect

Administration

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

Services