Essbase Server

During installation, EPM System Installer installs OPMN and registers Essbase Server for OPMN. OPMN manages the Essbase Agent, which manages the Essbase Server.

In a Windows environment, before you launch Essbase, change the OPMN service (Oracle Process Manager (instanceName)) to start as a named user so that the shared network files are accessible.

Navigate to EPM_ORACLE_INSTANCE/bin and use the following commands to start and stop Essbase Server:

where EssbaseInstanceName is one of the following:

If you are using Essbase in a clustered environment, there are additional steps required to set up Essbase failover on both nodes of the cluster. See Setting Up Active-Passive Essbase Clusters.

The following table describes additional methods for starting and stopping Essbase Server. Note that the Essbase Server start and stop scripts redirect to OPMN.

For information about OPMN, see the Oracle® Fusion Middleware Oracle Process Manager and Notification Server Administrator's Guide Release 11g (11.1.1.2.0) (http://download.oracle.com/docs/cd/E15523_01/doc.1111/e14007/toc.htm)

Table 72.  Starting and Stopping Essbase Server

Information TypeDetails
Windows Start Menu CommandSelect Start, then Programs, then Oracle EPM System, then Essbase, then Essbase Server, and then Start Essbase

This command launches startEssbase.bat (and redirects to OPMN).

Registered Service Name

Oracle Process Manager (instanceName)

Display Name in Windows Services Control Panel

Oracle Process Manager (instanceName)

Description

N/A

Windows Startup Script
  • Essbase Server — EPM_ORACLE_INSTANCE/bin/startEssbase.bat (redirects to OPMN)

Each instance of Essbase Server has its own startup script. If you configured an additional instance of Essbase, startEssbase.bat|sh is located in additionalInstanceLocation/bin. Launch the start script from this location to launch this instance of Essbase.

  • ESSCMD — EPM_ORACLE_INSTANCE/EssbaseServer/EssbaseServerInstanceName/bin/startEsscmd.bat (also available in the /EssbaseClient directory)

  • essmsh — EPM_ORACLE_INSTANCE/EssbaseServer/EssbaseServerInstanceName/bin/startMaxl.bat (also available in the /EssbaseClient directory)

All the scripts call setEssbaseEnv.bat to set up ESSBASEPATH, ARBORPATH, and PATH before starting.

UNIX Startup Script
  • Essbase Server — EPM_ORACLE_INSTANCE/bin/startEssbase.sh (redirects to OPMN)

Each instance of Essbase Server has its own startup script. If you configured an additional instance of Essbase, startEssbase.bat|sh is located in additionalInstanceLocation/bin. Launch the start script from this location to launch this instance of Essbase.

  • ESSCMD — EPM_ORACLE_INSTANCE/EssbaseServer/EssbaseServerInstanceName/bin/startEsscmd.sh (also available in the /EssbaseClient directory)

  • essmsh — EPM_ORACLE_INSTANCE/EssbaseServer/EssbaseServerInstanceName/bin/startMaxl.sh (also available in the /EssbaseClient directory)

All the scripts call hyperionenv.doc to set up ESSBASEPATH, ARBORPATH, and PATH before starting.

When running Essbase manually from a console, the console cannot be set to UTF-8 encoding.

Windows Stop Script

Server:

  • Essbase Server — EPM_ORACLE_INSTANCE/bin/stopEssbase.bat (redirects to OPMN)

UNIX Stop Script

Server:

  • Essbase Server — EPM_ORACLE_INSTANCE/bin/stopEssbase.sh (redirects to OPMN)

Stopping Essbase Server can take some time, depending on how many Essbase applications are running on the server. To stop Essbase Server, you need Administrator permissions.

See the Oracle Essbase Database Administrator's Guide for more information about shutting down Essbase Server.

For more information about stopping Essbase Server, see the Oracle Essbase Database Administrator's Guide and the Oracle Essbase Technical Reference.