Sometimes, stopping the application server process improperly, by closing the application server window, is necessary; for example, if the application server is corrupted and is not processing client requests.
To stop the application improperly, use a method for the operating system on which Essbase Server runs:
For UNIX platforms, kill the ESSSVR process.
You can use the ps output to identify individual applications. If an application freezes, you can stop the application by using this command:
kill -9 <pid>
For Windows, choose a method:
Perform a Windows operating system End Task.
Windows does not display process IDs for individual Essbase applications—all of the running Essbase applications are displayed as undifferentiated ESSSVR processes, preventing you from stopping a single application in the event that the application freezes.
You can find the process ID for individual application servers in the EPM_ORACLE_HOME/logs/essbase/essbase.log file. When the server starts, a line like the following is displayed in the Essbase Server log:
Application [Sample] started with process id [225]