1. Standard Deployment Guide
  2. Scaling Out the Application Tier
  3. Scaling out Essbase Server

Scaling out Essbase Server

Complete this procedure on each host machine, for example, ESSHOST2, onto which Oracle Essbase is to be scaled out.

Because scaled-out Essbase Servers are independent, an application deployed to one server does not span across to other Essbase Servers. While creating applications, for example, using Oracle Hyperion Planning, you choose the Essbase Server that you want to use.

To scale out Essbase Server:

  1. Verify that you are logged on to the Essbase Server scale-out machine (ESSHOST2) using the deployment user.
  2. Install Essbase Server on ESSHOST2 using the instructions in Installing Essbase Server on ESSHOST1.

    In the steps, use ESSHOST2 instead of ESSHOST1 as the host name.

  3. Follow the steps in Creating Infrastructure Schemas Using Repository Creation Utility on FNDHOST1 to run the Repository Creation Utility and update RCU schema properties on ESSHOST2. Note these steps:
    • On the Select Components page, enter a unique prefix, for example ESSHOST2.
    • When modifying RCUSchema.properties in a text editor, for schemaPrefix, make sure to enter the unique prefix used on this machine, for example ESSHOST2.
  4. Configure using the steps in Configuring Essbase on ESSHOST1.
  5. On the scaleout machine, start Oracle Enterprise Performance Management System: From the Start menu, select Oracle EPM System, and then Start EPM System.