|Important: before you begin updating your Jedox installation, read General Guidelines for Updating Jedox.
You require root rights to install and to start Jedox Web on Linux. The steps below describe how to perform an installation update with copies of existing data and settings.
Step 1 – Run the following command to stop any Jedox process:
Step 2 – Create a copy of the existing installation folder as a backup:
cp –R /opt/jedox/ps /opt/jedox/ps_copy
Note: the update installation could overwrite manually changed configuration files. Therefore you should have a backup from which it is possible to restore manually changed files.
Step 3 – Execute install.sh in a “bash” shell (other shells, such as “dash”, are not supported) to run the installation:
Use the existing ps directory as the installation directory.
Follow the instructions. Setup will prompt you for several existing data directories (OLAP, Jedox Web, and ETL Server), asking you whether you want to keep existing data or replace it with new data. If you choose to replace it, your existing data will be lost for the respective directory.
For Supervision Server, a folder with sample scripts (called “sample_scripts”) will be created. If you had custom scripts in the old installation, you must add them again after setup is complete.
Step 4 – Restore desired data
As described above, most data is kept in place when running an update installation.
Note: after updating, delay loading may take longer than usual due to potential database conversion at first start. Jedox processes should not be stopped or shutdown until delay loading has finished.
To avoid display errors, the browser cache should be cleared before starting Jedox Web.
Jedox configuration files
During the update installation Jedox Setup will create a backup copy (including a timestamp in filename) of the following configuration files:
- /opt/jedox/ps/svs-Linux-x86_64/ sep.inc.php
For Linux systems using SSO, the following additional files will be backed up within chroot:
Important: the backed-up files must be manually restored after update.
Note: Setup either modifies existing configuration files upon update (such as palo.ini), or replaces existing ones with new ones. The replace operations are necessary because of larger changes in the configuration. If you had modified configuration files in your previous installation, we recommend that you apply your changes to the new files rather than copy files from the previous version’s backup.