Starting and stopping Kronodoc

Kronodoc is started by starting the Web server under which it is running. For this the installation has a shell script called start_kronodoc_web_server:

$ /home/kronodoc/kd40/httpd/support/start_kronodoc_web_server

This should be run with the privileges of the user ID with which Kronodoc is installed, except if the port number used by Kronodoc is below 1024, as such privileged ports are available only to root.

On an Oracle database installation, Oracle needs to be running before Kronodoc and its Web server are started.

Similarly, the stop_kronodoc_web_server shell script can be used for  stopping the Kronodoc system:

$ /home/kronodoc/kd40/httpd/support/stop_kronodoc_web_server

On an Oracle database installation, Oracle should only be stopped after Kronodoc has been stopped.

The restart_kronodoc_web_server shell script can be used to stop and start Kronodoc in an orderly manner, for instance to force configuration changes edited in configuration files to take effect:

$ /home/kronodoc/kd40/httpd/support/restart_kronodoc_web_server

In order for the Web server to start automatically every time your computer is booted, you have to add the server daemon starting command as given by the installation script into the list of commands executed by the operating system upon system start. A sample script, Kronodoc Kronodoc.sh, for doing this on each supported platform is available in the httpd/support directory.