Updating a Jedox installation based on Linux VM

Home  >>  Allgemein  >>  Updating a Jedox installation based on Linux VM

Updating a Jedox installation based on Linux VM

On August 9, 2019, Posted by , In Allgemein, With No Comments

to update a Jedox installation you will need to consider the requirements in the Jedox setup guide to make sure you actually can update from your current version to desired version directly. Please note that not all Jedox versions can be upgraded to the latest and greatest version of Jedox. It is recommended to run upgrade process for every major release number. So if you want to upgrade from 6.x to 2019.x you will have to upgrade to 2018.x in between. Which version is able to be updated to what number you can find in the corresponding Jedox setup guide on www.jedox.com or contact me with private message.

First of all it is always recommended to create a snapshot of your server. If it is a virtual server this can be very simply done with management console of the VM (eg HyperV, VMWare, VirtualBox, proxmox or similar).
Before taking a snapshot, please make sure the Jedox is not active/running its services. As Jedox is running in memory the snapshot of the harddrive might be inconsistent/corrput. In worst case scenario this could mean that you have no ability to roll-back to the snapshot.

  1. Stopping Jedox Server
    root@xxxxxxx:~# /opt/jedox/ps/stopserver.sh
  2. Taking snapshot of server
    Go to management console and create a snapshot to be able to roll back. this might take a few minutes depending on the size of the server.
  3. Backing up Jedox data
    some people might say it is redundant to create a copy of the Jedox folder as you have the snapshot. But if you want to compare files before and after setup (such as configuration files) I highly recommend to keep a temporary copy of the installation folder. As configuration files get overwritten and adjusted you might not find all your settings after upgrade in place.
    cp -a /opt/jedox/ps /opt/jedox/ps_bak
  4. Download installation routine from Jedox and upload to server
    Now it is time to bring the installation files from Jedox to your server. Download from here https://www.jedox.com/en/services/downloads/ and upload the file Jedox_2019_2_lin.tar to your server. Personally I use WinSCP you upload files but you might also use other tools to do so.
    Once the file is uploaded extract all the data from the archive to desired folder (outside Jedox installation folder). I use /root for this temporary file storage and run command:
    tar -xf Jedox_2019_2_lin.tar

  5. Installation of new Jedox version
    Now it is time to start the upgrade procedure by running
    ./install.sh (the Jedox services are still turned off)
    You will need to accept the license agreement by scrolling to the very end (hold space bar to scroll page down). At the end you will find the follwoing question:
    Do you accept the previously read EULA ? [y|N]: y
    Now you will be prompted for path
    Please enter the path to where you want the Jedox Suite to be installed. You may use TAB to autocomplete.
    Default [/opt/jedox/ps]:

    Just hit enter to keep the default (my case) or specify your install path (auto complete with tab does not work here!)
    Installation is compatible with currect setup.
    proceeding with setup.
    => Upgrading /opt/jedox/ps containing Jedox 19.1 with 64bit components

    Jedox will run a test to make sure you really can upgrade from current version (2019.1 in my case) to the desired version (2019.2 in my case).
    Then more questions to define which components you want to install:
    Do you want to install SAP components [y|N]: N
    No SAP components will be installed.
    I don’t need it. If you watn to install SAP components you will have to place the SAPJCo driver to some folder and specify. Jedox will then copy for your folder to its installation folder.
    Please enter which user should run and own the Jedox Suite:
    Default [jedoxweb]:

    I do not specify any other user and keep it like it is. So just hit enter.
    Same for the group:
    Please enter which group should run and own the Jedox Suite:
    Default [jedoxweb]:

    Now Jedox will create a Backup folder of your database and upgrade the system
    The Jedox OLAP-server 64bit version will be installed.
    Backing up configuration and database files…

    ATTENTION! Do you also want a backup of OLAP's data folder ? [Y|n] Y
    Have I mentioned I like having a backup of everything? 🙂
    Copy OLAP's data folder to backup folder. It may take some time… done.
    Cleaning the installation folder…
    Copying relevant files back into your installation directory…done.
    Starting backup handling…

    Jedox is purging the installation but keeps the configuration in a specific folder for you to restore afterwards.
    In case you have already done this upgrade before and haven’t deleted the backup folder now is your chance.
    Do you want to delete the backup folder '/opt/jedox/ps/upgrade_7_4_27052019232343'? [y/N]N
    Again I like to keep stuff and rather delete at the time I want.
    The suite will now be installed. This might take a while … OK.
    The magic is now happening… Please stand by.
    Now there will be some tricky question which you will have to be VERY careful with as the meaning is not very clear.
    The directory /opt/jedox/ps/storage exists. Shall I overwrite it? [y|N]: N
    If you think a it’s only bringing the new demo inside and keep the rest. Way wrong! It’ll delete the folder and replace with default one –> all your web reports: bye bye. Not such a great idea if you have some content already. So I select N.
    I will use existing storage data!
    The directory /opt/jedox/ps/Data exists. Shall I overwrite it? [y|N]:N
    Same for the Data folder containing all your databases (Dimensions, Cubes, data, everything,…) Please,… do not delete that.
    I will use existing data!
    What is this servers name ? (If no DNS-Server is running take the IP) [xxxxxxx.xxxxxxx.com]:
    You can specify a DNS name to be used in httpd.conf.
    What is this servers IP-Address ? [xxx.xxx.xxx.xxx]:
    Normally it should detect from eth0 automatically otherwise please specify. This is used also for httpd.conf. If okay, just hit enter.
    Who should get administrative e-mails regarding this server ? [webmaster@xxxxxxx.xxxxxxx.com]:
    This one is rather obvious and also goes to httpd.conf. This is not the email for the Task Scheduler inside of Jedox!
    Which IP-address should the OLAP server run on ("all" for all interfaces) ? [all]:
    Normally it should be on all unless you want a specific setup. this can also be changed in palo.ini afterwards.
    Which port should the OLAP server run on ? [7777]:
    Adjust to your desires. I do not recommend to use standard ports. When software gets more and more popular and services are running in cloud environment one should pick individual ports to prevent from simple port scanning for know software.
    Which IP-address should the HTTP server listen on ("all" for all interfaces) ? [all]:
    Successfully configured to listen at port 80 on all interfaces in httpd.conf.
    This should be the same as IP for OLAP.
    Which IP-address should the Spreadsheet server run on ? []:
    Which port should the Spreadsheet server run on ? [8193]:
    Successfully configured SSS host and port 8193 in ui_backend_config.xml.
    There is no need to adjust the spreadsheet server as long it is running on the same machine. Just leave default settings.
    Which AJP-address should the Tomcat server run on ? []:
    Which AJP port should the Tomcat server run on ? [8010]:
    Successfully configured AJP host and port 8010 in server.xml.
    Which HTTP-address should the Tomcat server run on ? []:
    Which HTTP port should the ETL Tomcat server run on ? [7775]:
    Successfully configured HTTP host and port 7775 in server.xml.
    Successfully configured ETL-server host and port 7775 in etl-mngr.properties.
    Successfully configured Scheduler server host and port 7775 in etl-mngr.properties.
    Which HTTP-address should the RPC Tomcat server run on ? []:
    Which HTTP port should the RPC Tomcat server run on ? [7776]:
    Successfully configured HTTP host and port 7776 in server.xml.
    Writing final configuration to httpd.conf…done.

    I do not like to open the Jedox Integrator service to be called from outside although there is a credential needed (by now). Therefore I keep it locked to internal access only.
    Internet connection is available.
    The Marketplace is fully operative.
    The Jedox-Suite is now configured.
    Start the Jedox-Suite services by running "/opt/jedox/ps/jedox-suite.sh start"

    Installation is done. Now we have to check the settings in following configuration files (now you will see why it is important to have a backup accessible; folder „ps_bak“).
  6. Restore configuration
    SVS include: if you have set up the SVS you need to bring back your script to sep.inc.php
    nano /opt/jedox/ps/svs-Linux-x86_64/sep.inc.php
    Replace the include from sample script to custom script
    include './sample_scripts/sep.inc.default.php';
    eg to:
    include './custom_scripts/sep.inc.consysmo.php';
    Next once is the SSL certificates (if you have used them). The configuration in httpd.conf should be still there. Please check if the SSL is still turned on with this line in httpd.conf
    Define SSL

    Those lins should NOT have # at the front (comment sign).
    You might need to bring the crt/pem/key/ files back. This is depending on which folder you used for storing the certificates. I use individual folder as they come from Let’s Encrypt. You might also use link or mount to bring in the certificates eg from /etc/letsencrpyt/live/domain_name/ (careful: /etc from letsencrypt is NOT /etc from Jedox as Jedox is running in cage with chroot). So command would look like:
    cp /etc/letsencrypt/live/domain_name/* /opt/jedox/ps/etc/httpd/domain_name
    Don’t forget to change owner to jedoxweb:jedoxweb
    chown -R jedoxweb:jedoxweb /opt/jedox/ps/etc/httpd/domain_name
    Please also check all configuration steps for core / web frontend to adjust SSL settings as they have changed in version 2019.2
    Please see:
    Also you might need to change the memory settings in Tomcat service in /opt/jedox/ps/tomcat-etl/bin/setenv.sh
    line: export PaloTomcat_Max_Memory=4096
  7. Start Jedox Suite
    Now you should be able to start the Jedox Suite with
    The first startup might take some more time as usual depending what changes have to be done to your databases and how big they are. Please be patient on first startup.

Schreibe einen Kommentar