1.4Starting/stopping cmsWorks
Starting the server
The starting scripts reside in the directory <cmsWorks-installdir>/run/ and are named cmsworks.sh (Linux / *ix) or cmsworks.bat (Windows). These scripts start the application server and all services that are listed in the file <cmsworks-installdir>/run/batches/cmsstart.batch.
Check the cmsWorks status after start
To check the status of a newly started cmsWorks instance one may login to the telnet server shell and use the command "service status". This will list all available (micro-)services in cmsWorks and show their status ("starting", "running", "stopping", "stopped"). If all services are running, the server state should be "fully functioning".
In case problems occurred, the command "exception" used in the telnet server shell may give hints of the nature of these problems. The command "log" can also redirect the cmsWorks logging to the shell in real-time. The commands "exception" and "log" are described in detail in logging for debugging.
Stopping the server gracefully
Normally, it is not necessary to restart these services or even the complete application server. If a restart is desired, the server can be stopped via the cmsWorks built-in telnet server. To accomplish this, telnet has to be installed on the machine you connect from. The following sequence will then stop the server (use the correct port as given in the topas.properties file):
$ telnet localhost 8050
This is topas-server "cmsWorks server instance".
password: *******
cms# email off
cms# shutdown
This example points to "telnet localhost 8050" and therefore assumes that the cmsWorks server is installed on the same machine. If this is not the case, "localhost" has to be replaced with the IP or name of the machine the cmsWorks server is installed at. Additionally, the port (8050) may have been altered, too.
Of course, if no internal database server service is running within cmsWorks, you could simply kill the java process of cmsWorks to shut down the complete server. If an internal database server service is running in cmsWorks, it is highly advisable to shutdown the server via the telnet server shell, so that the database is closed correctly.