Some servers need their services stopped before other servers. The order in which servers should be stopped depends on which services are located on them. EPX must always be stopped first and started last, otherwise EPX will continue attempting to interact with Tomcat and repeatedly fail, which causes invalid workflow processing.
The table below indicates the server sequence for stopping services. For a list of which services reside on which servers, see EnterWorks Services.
| Stop servers in this order | Server name |
|---|---|
| 1 | app |
| 2 | dam |
| 3 | work-<n> |
| Do not stop the esb server. | esb |
To stop all EnterWorks services on all servers in an environment, perform these steps on each server in the order given in the table above:
- Open File Explorer and go to:
<drive>:\Enterworks\bin - Right-click Stop Enterworks and select Run as Administrator.
- A command prompt will appear and services will begin stopping.
- Once the script is finished, verify that no EnterWorks related services are
still running.
- Open Task Manager and select the Processes tab.
- Right-click either CPU or Memory on the header to bring up the list of available columns.
- Select Command line.
- Expand the width of the Command line column until you can see the path and name of any running processes.
- Verify that the following processes do not appear in the list:
-
Commons Daemon Service Runner: Any that have EnableServer in the file path. -
enable-<serviceName>-service -
Java(TM) Platform SE Binary: Any that have Enterworks or EPX in the file path.
-
- If any of the listed processes appears, right-click the process and select End Task.
EnterWorks services are now stopped.