Configuring and Starting Additional Instances of Essbase Server

You can install Essbase Server once and configure multiple additional instances. Configure the first instance as usual using EPM System Configurator. For subsequent instances, specify a new instance during configuration.

For subsequent instances, you can configure only the 32-bit version of Essbase on 32-bit systems and the 64-bit version of Essbase on 64-bit systems. Configuring a 32-bit version of Essbase on a 64-bit system is not supported when you configure additional instances.

  To configure an additional instance of Essbase Server on the same machine:

  1. After you have configured the first instance of Essbase Server, launch EPM System Configurator on the same machine.

  2. On the “Configure a New or Existing EPM Oracle Instance” page, specify the location for the additional instance of Essbase Server.

    The default location for a subsequent instance is MIDDLEWARE_HOME/user_projects/epmsystemN, where N is the number of the instance.

  3. On the Essbase Server Configuration page, specify the following information:

    • A unique Essbase instance name

    • A unique agent port number

    • A unique SSL agent port number

    • A unique port range. The range of ports used by one Essbase Server instance must not overlap the range of ports used by another instance or any other products.

      The port numbers for the additional instance of Essbase Server are stored in the essbase.cfg file for this installation.

    • For ARBORPATH: If this instance is in a cluster with another instance, this instance must have the same application location as the first instance. If this instance is not in a cluster with another instance the ARBORPATH can be different.

  4. Complete configuration with EPM System Configurator.

  5. To prevent a port conflict in OPMN, you must manually edit opmn.xml. See Modifying OPMN for an Additional Instance of Essbase.

Each instance of Essbase Server has its own OPMN and its own startup script. To start an additional instance of Essbase Server, use the startEssbase.bat|.sh script for this instance, in EssbaseInstanceLocation/bin.

Each instance has its own log file in EssbaseInstanceLocation/diagnostics/logs/essbase.