This article describes an update to a Jedox installation on Linux with data copying of existing data and settings.
Before you begin:
- Create a backup of your Jedox data (spreadsheets, reports, and DBs).
- Create a backup of your manually adapted Jedox config files.
- You must have root rights to install and to start Jedox Web on Linux
- Before you upgrade a production system, we recommend that you perform the update on a test system and check it with appropriate plausibility tests.
The following description applies to updates from version 7.0 (SRx) to version 7.1 (SRx):
Step 1 – Stop Jedox
Step 2 – Create a copy of the existing installation folder (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 – Installation
Execute install.sh in a “bash” shell (other shells, such as “dash”, are not supported):
Use the existing ps directory as 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, 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 used a custom script, you need to re-add it after setup has finished.
Step 4 – Restore desired data (Stop before Jedox):
As described above, most data is kept in place when running an update installation. If you manually need to replace content, you can do the following:
Example: cp -R < source > < target >
For the Jedox configuration file, the command is as follows:
cp -R opt/jedox/ps_copy/Data/palo.ini /opt/jedox/ps/Data/
For the other files the paths are listed below. You can use these for the copy command:
|1) Please 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.|