Before you begin:
- 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.
A) Migration exclusive User Rights
For migration of a Jedox installation you have usually to export Jedox Reports and Jedox Integrator projects and then import them in the new Jedox installation. Additionally, you have to copy your databases.
Restart all palo processes.
B) Migration inclusive Users with their User Rights
If you also want to migrate all users with their rights, then you also have to copy the database “System”.
Restart all palo processes and execute final steps of point D to adapt the internal connection.
C) Migration inclusive Users with User Rights into an identical directory structure
If you install an identical directory structure on the new server, then you can also proceed as follows:
- Perform the Jedox installation on the new server.
- Stop the palo processes on the new and old system.
- Replace the following directories on the new server (completely) by the corresponding directories of the old server:
Jedox_Installation_directory/Data/ (here only the subdirectories)
(Note: Per default the Jedox_Installation_directory is /opt/Jedox/ps)
- Restart all palo processes and execute final steps of point D to adapt the internal connection.
D) Final steps for point B and C
The internal connection must be reset as follows:
- Delete or rename the file Jedox_Installation_directory/httpd/app/etc/config.php.
- Check that all palo processes have successfully completed their restarts. If there are big databases, then the palo process needs more time (if there is in olap_server.log the line “Delay loading finished” after the last line with content “Starting to listen…”, then all databases are loaded completely).
- Stop the Jedox processes and then restart Jedox Setup via the script “install.sh”. Choose the same directory and an upgrading message will prompt on the console.
It may happen that the Upgrade-Installation overwrites manually changed configuration files. Make sure you have a backup from which you can restore manually changed files.
The variant C has the advantage that all users as well as their rights, settings, and tasks are migrated. But this only works when all paths are identical. Adapted Supervision Server scripts must be manually reviewed and changes made in the old script files must be transferred manually into the new script files.