1. Deployment Options Guide
  2. Scaling EPM System Products
  3. Clustering Java Web Applications

Clustering Java Web Applications

This section assumes that you are familiar with WebLogic administration and clustering. If you are unfamiliar with these tasks, Oracle urges you to seek technical assistance before attempting to cluster an Oracle Enterprise Performance Management System Java web application.

Prerequisites

Note:

The information in this section assumes that you have installed your Java web applications on each node to be included in the cluster.

Complete these tasks before setting up a cluster for an EPM System Java web application:

  • When scaling Oracle Hyperion Foundation Services, you must create a new schema using RCU and edit RCUSchema.properties on each machine in the deployment. For information, see "Creating Infrastructure Schemas Using Repository Creation Utility" and "Updating RCU Schema Properties" in the Oracle Enterprise Performance Management System Installation and Configuration Guide.

  • When you are deploying on a machine other than the machine hosting Foundation Services, WebLogic Server Administration Server must be running on the Foundation Services host machine. If you are deploying on the same machine as Foundation Services, WebLogic Server Administration Server does not need to be running.

  • Enable either session persistence or sticky sessions (which direct all requests for a specific session to the same server) on the load balancer.

  • In distributed systems (where Oracle Essbase is installed on a different server than Oracle Hyperion Profitability and Cost Management), Oracle Hyperion Provider Services must also be installed and configured on the Profitability and Cost Management server. This is a requirement even when your configuration supports using Embedded mode for Essbase connections. In clustered systems (where more than one Profitability and Cost Management managed server is installed), Provider Services must also be installed and configured on each Profitability and Cost Management managed server node.

  • Install the EPM System product on each node that the cluster will include. Install to the same file system location on each machine. Using the same file system path on each physical machine in a cluster is important so that these environment variables can be set once for the entire cluster, rather than set and customized for each node in the cluster:

    All OS—CLASSPATH and PATH

Clustering Java Web Applications Using EPM System Configurator

You can cluster EPM System Java web applications during configuration with EPM System Configurator. Use the following general configuration sequence. This procedure assumes that the Oracle HTTP Server installed by EPM System Installer is the logical host.

Note:

When Profitability and Cost Management is scaled within a clustered environment, each module within the Profitability enterprise application must be targeted to all of the servers within the Profitability cluster.

To cluster EPM System Java web applications during configuration with EPM System Configurator:

  1. Install EPM System Java web applications on each machine in your environment.

  2. Configure the Java web application on the first machine, selecting Deploy to Application Server on the EPM System Configurator Task Selection page.

    During deployment, EPM System Configurator creates a cluster for each managed server in WebLogic.

  3. Configure the Java web application on the next machine, selecting Deploy to Application Server on the EPM System Configurator Task Selection page.

    During deployment, EPM System Configurator adds the server to the cluster in WebLogic.

    Repeat this step for any additional machines in the deployment.

  4. Configure the web server last, selecting Configure Web Server from the Foundation tasks on the EPM System Configurator Task Selection page. Then, restart the web server and Oracle Hyperion Enterprise Performance Management Workspace.

Considerations about clustering Java web applications:

  • EPM System Configurator configures a cluster for each managed server.

  • You should have only one cluster for each EPM System product. Note that EPM System Configurator creates a cluster for each managed server.

Scaling Out a Single Managed Server

To scale out the single managed server on subsequent machines:

  1. Using EPM System Installer, install the same set of Java web applications on any additional machines in the environment. Note that you cannot add or remove Java web applications when you scale out.

  2. Run EPM System Configurator from each machine to which you are scaling out.

  3. On the Task Selection panel under Hyperion Foundation, select Scale out single managed server on this machine.

    The Scale out single managed server on this machine option is only available when the following are true:

    • The WebLogic Administration Server is not installed on the current machine.

    • The single managed server is deployed on the WebLogic Administration Server.

    • The single managed server is not already scaled out on the machine.

  4. Click Next to scale out the server.

When scaling Foundation Services, you must create a new schema using RCU and edit RCUSchema.properties on each machine in the deployment. For information, see "Creating Infrastructure Schemas Using Repository Creation Utility" and "Updating RCU Schema Properties" in the Oracle Enterprise Performance Management System Installation and Configuration Guide.