You can start and stop Jedox on Linux with the script jedox-suite.sh, located directly in the installation directory. This script is called with certain parameters:
- “Command” specifies what the user wants to do (start, restart, or stop).
- “Options” that modify implicit behavior of the script itself (–no-deps, –umount, and –no-umount).
- One or more “targets” that specify which components are to be started (any combination of olap, httpd, core, and tomcat).
“Command” is a required argument; the others are optional. When started with only a command, the script applies this command to all Jedox components.
|./jedox-suite.sh start||By default start all components of Jedox.|
|./jedox-suite.sh stop core httpd||Stops the “core” and “httpd” components of Jedox Web.|
|./jedox-suite.sh restart –no-deps olap||Restarts the OLAP component, while not restarting its dependent components (tomcat).|
Once running, the processes can be controlled by the script via their “Process ID”, not via the process name. Process IDs are saved as files in <Jedox Suite>/var/run and <Jedox Suite>/tomcat respectively.
Be aware that the jedox-suite.sh script and the <Jedox Suite>/tomcat/jedox_tomcat.sh script now both contain an INSTALL_PATH variable with the location of your Jedox jail. This makes it possible to create symlinks to those scripts and call them from wherever you want. Combined with the Debian-, CentOS- and SuSE-compatible init.d comment headers that are contained in these files, it is now possible to integrate the jedox-suite.sh into the system’s startup and shutdown process.
The jedox-suite.sh automatically tries to bind-mount “/dev”, “/proc”, and “/sys” into the jail in order to make tools like netstat (used for olap server startup) work in the chroot environment. These mounts are automatically unmounted when “./jedox-suite.sh stop” (without any further parameters) is issued.
You can enforce unmounting these directories using the –umount option and forbid unmounting using -no-umount.
OLAP start and stop handling have been changed. Starting the OLAP process means launching the process and waiting for it to completely start up and start listening on a configured port, instead of simply assuming it is up after waiting a couple of seconds.
Same applies to the OLAP process shutdown: the script waits for the shutdown to complete even if this means waiting for an hour or longer. This new default behavior can be changed by editing <Jedox Suite>/etc/rc.d/init.d/jedox_olap and changing the variables OLAP_START_TIMEOUT and OLAP_STOP_TIMEOUT.
Timeouts may also be configured for the Jedox core process in <Jedox Suite>/etc/rc.d/init.d/jedox_core and the Jedox Tomcat process in <Jedox Suite>/tomcat/jedox_tomcat.sh.