â ď¸Important: Services must be stopped and restarted in the correct order. When stopping, stop the Task server first, then the app servers, then the databases. When restarting, reverse the order: start the databases first, then the app servers, then the Task server.
Stop the app server services
To stop the app server services, follow these steps on the server running the app servers.
Open Task Manager, then click the Details tab, then click Services.
Locate Admin Service for OpenEdge in the services list.
Right-click Admin Service for OpenEdge, then click Stop.
Monitor Task Manager and wait for all _proapsv instances and all Java.exe instances to end.
If the client is running Apache Tomcat on the same server, locate Apache Tomcat in the services list, right-click it, then click Stop.
Restart the app server services
Once the services have stopped, restart them in the following order.
In the services list, right-click Apache Tomcat, then click Start. Confirm that the Tomcat instance reappears in Task Manager.
Right-click Admin Service for OpenEdge, then click Start.
Monitor Task Manager â Java.exe instances should appear first, followed by _proapsv instances beginning to spawn.
đNote: Steps 1 and 2 above apply only if Apache Tomcat is running on the same server. If it is not applicable, begin from step 2.
Alternative: restart PASOE using a batch file
If SecureDocs and related APIs are down, you can restart PASOE by running a batch file directly on the web or application server.
On the web or application server, open File Explorer and go to C:\prodisk\proclaim\batch.
Run the appropriate batch file for your environment.
Confirm that the app server instance reappears in Task Manager.
Confirm the restart
Once services have been restarted, check whether you can log in to confirm the restart was successful.
Versions of Apache Tomcat supported by Proclaim
The following Progress Knowledge Base Article explains which version of Apache Tomcat are supported.