Stopping Endeca Server

Stopping the Oracle Endeca Server application makes it unavailable for WebLogic Server clients.

You can manually stop the Oracle Endeca Server application from the WebLogic Server Administration Console. Note that it is not necessary to stop Endeca Server in order to shut down WebLogic Server; in this case, WebLogic Server will stop Endeca Server as part of its shut-down procedure.

To stop the Oracle Endeca Server application:

Make sure that the Administration Server for the Endeca domain is running.
From your browser, access the Administration Server console using this syntax:
```
http://admin_server_host:admin_server_port/console
```
For example:
```
http://web007:7001/console
```
At the Administration Console login screen, log in with the administrator user name and password.
In the Domain Structure pane, click Deployments (in the endeca_domain tree).
In the Deployments table, check the oracle.endecaserver Web application. Its State should be "Active" and its Health should be "OK", as in this abbreviated example:
In the Deployments table, click Stop, and select one of the stop options:
- When work completes: Specifies that WebLogic Server waits for the Endeca Server application to finish its work and for all currently connected users to disconnect.
- Force Stop Now: Specifies that WebLogic Server stops the Endeca Server application immediately, regardless of the work that is being performed and the users that are connected.
- Stop, but continue servicing administration requests: Specifies that WebLogic Server stops the Endeca Server application once all its work has finished, but then puts the application in Administration Mode so it can be accessed for administrative purposes.
In the Stop Application Assistant, click Yes.

As a result, the Endeca Server application is stopped and its State now changes to "Prepared".

Note: If the Endeca Server application is in a "Prepared" (i.e., stopped) state when you shut down WebLogic Server, then the application is not automatically re-started when you start WebLogic Server. In this case, you must manually start Endeca Server.

Note that if you forcibly shut down any of the WebLogic Servers in the WebLogic domain that is hosting the Endeca Server cluster, there is a chance that the Dgraph processes or the Cluster Coordinator processes from the Endeca Server will be left running (this is because the Cluster Coordinator process runs in a separate JVM and the Dgraph process is not a Java process). Therefore, upon subsequent startup of the WebLogic Server, the Endeca Server software checks whether in this WebLogic domain any Dgraph or Cluster Coordinator processes are running and then shuts them down.