1. Installation and Configuration Guide
  2. Configuring EPM System Products in a New Deployment
  3. Configuring Products in a Distributed Environment

Configuring Products in a Distributed Environment

Ensure that you meet installation and configuration requirements in a distributed environment. See Installing EPM System Products in a Distributed Environment. For information about clustering and high availability, see the Oracle Enterprise Performance Management System Deployment Options Guide.

Before you configure, ensure that you have run RCU and updated RCU schema properties on each machine in your environment.

Configuration considerations in a distributed environment:

  • You must configure Oracle Hyperion Foundation Services first. Foundation Services must be installed and configured for other products to configure successfully. Configure the web server last.

  • Create a new EPM Oracle instance on each machine.

  • If you are deploying Java web applications on a machine other than the WebLogic Administration Server machine, WebLogic Administration Server must be running.

  • Deploy all Oracle Enterprise Performance Management System products to a single WebLogic domain.

  • During configuration with EPM System Configurator, the web server machine needs connectivity to the machine hosting the Oracle Hyperion Shared Services Registry.

  • If you are using more than one web server in a deployment for load balancing and failover, configure the web server on every machine on which you want to run the web server. If you have more than one web server, you must use a load balancer (hardware or software) to route traffic to the servers, and the logical web address for the Java web application cluster should be the load balancer. If you have only one web server, the logical web address for the Java web application cluster can be the web server.

  • When configuring EPM System for high availability where multiple instances of services are running, and for using Oracle Hyperion Enterprise Performance Management System Lifecycle Management in a distributed environment, in EPM System Configurator, on the Configure Common Settings page, for LCM Export Import Location, specify a shared file system path defined using UNC syntax that is accessible from all the servers in the deployment. This enables data migration across distributed environments.

    If you are using Oracle Hyperion Financial Management in a distributed environment, configure the LCM Export Import folder with Read/Write access for all the Financial Management Application Servers in the environment.

    You must also point to the same location for Oracle Essbase Server (Linux) Full path to application location (ARBORPATH). For example, \\SharedHost\SharedLocation\data\Essbase

  • When Oracle Hyperion Profitability and Cost Management is installed and configured on a different physical server other than the one with LCM Export Import Location (shared artifact path), the common settings on the Configure Common Settings page, in EPM System Configurator must be configured to specify a shared directory path using the UNC (Universal Naming Conventon) syntax.

  • Optionally, you can configure Oracle HTTP Server to a shared drive to simplify the configuration process.

  • For Oracle Hyperion Financial Reporting linked reports to work, configure Financial Reporting so that the logical address of the Financial Reporting component is same as web server port (for example, 19000).

  • When configuring Financial Management in a distributed environment, you must select the Configure Database task for Financial Management on every machine hosting the Financial Management Application Server.

    If you are configuring an additional instance of Financial Management, when you are prompted whether to drop and re-create the tables or reuse the existing database, select Reuse the existing database.