A system administrator may run Essbase Server as a background process when working in batch mode (for example, when using a UNIX shell script or Windows .bat file to run multiple tasks, such as starting and logging onto Essbase Server, loading data, and running calculation scripts and report).
Also, on Windows, running Essbase Server as a background process allows a system administrator to use Windows settings to improve performance of applications running in the foreground.
If you start Essbase Server in the background, these conditions apply:
You cannot shut down Essbase Server from the Agent. You must use MaxL or ESSCMD.
You cannot access the application server window to monitor a running application. You must access this information from the application log (ARBORPATH/app/appname/appname.log).
You cannot monitor Essbase Server activity using the Agent. You must access this information from the Essbase Server log (EPM_ORACLE_HOME/logs/essbase/essbase.log).
You can run instances of the Agent as Windows services. You must first use EPM System Configurator to register the service. See the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide.
To start Essbase Server in the background on UNIX or on Windows systems utilizing a UNIX-like shell such as MKS, enter the following command at a command prompt:
startEssbase.sh -b &
Using the ampersand (&) at the end of the command is optional; however, if you do not use “&,” the command prompt is not returned after Essbase Server is started.
On Windows, unless you are using a UNIX-like shell such as MKS, the ampersand (&) has no effect. Essbase Server starts in the background, but control of the command prompt is not returned. You may need to press the Enter key twice before the command prompt returns. |
On UNIX systems, to find out if Essbase Server is already running in the background, enter the following command at a command prompt:
ps -ef | grep ESS
If Essbase Server is running in the background, it appears in the process list.