Update Relution

Follow these steps to update your Relution installation.

Due to changes in the database migration it is mandatory to update from version 2.7 to version 3.2 before updating to the latest version of Relution.

From version 2.7 to 3.2

Docker

Edit the docker-compose.yml and replace

  image: {productSmall}/{productSmall}:2.7

with

  image: {productSmall}/{productSmall}:3.2

Updating Relution is then as simple as:

cd /opt/relution/
docker-compose pull
docker-compose up --detach
Make sure to replace docker_relution with the name of the Relution container (“container_name”) you’ve specified in your docker-compose.yml if the name deviates from our template.

This will pull the docker image for Relution version 3.2 before restarting the containers. The Relution service will be unavailable for a minute or two until the containers have finished rebooting.

Linux

  1. Download the Relution 3.2 ZIP archive.

  2. Stop the Relution service

  3. Ensure the service’s Java processes have terminated

  4. Backup your Relution database

  5. Uninstall the Relution service

    • run <INSTALL_DIR>/bin/uninstall_init.sh as root

  6. Backup the installation directory

    • e.g. mv <INSTALL_DIR> <INSTALL_DIR>.bak

  7. Extract the ZIP archive to <INSTALL_DIR>

  8. Copy <INSTALL_DIR>.bak/config-admin to <INSTALL_DIR>/config-admin

  9. Run sudo java -jar setup.jar and follow the on-screen instructions.

    • We recommend to install Relution as a system service

    • Relution will detect if the system uses sysv-init or systemd

  10. Wait for the Relution service to start

    • The database is be migrated to the latest version

    • The system configuration is moved to the database

Windows Server

  1. Download the Relution 3.2 ZIP archive

  2. Stop the Relution service

  3. Ensure the service’s Java processes have terminated

  4. Backup your Relution database

  5. Uninstall the Relution service

    • run <INSTALL_DIR>\bin\uninstall_service.bat as Administrator

  6. Backup the installation directory

    • e.g. move <INSTALL_DIR> <INSTALL_DIR>.bak

  7. Extract the ZIP archive to <INSTALL_DIR>

  8. Copy <INSTALL_DIR>.bak\conf\* into <INSTALL_DIR>\conf\

    • Do not copy the file gofer.conf

  9. Run java -jar setup.jar from an administrative shell and follow the on-screen instructions

    • Do install Relution as a Windows service, this is the only way to start Relution on Windows

  10. Wait for the Relution service to start

    • The database is be migrated to the latest version

    • The system configuration is moved to the database

From version 3.2 or newer to latest version

Docker

  image: {productSmall}/{productSmall}:3.2

with

  image: {productSmall}/{productSmall}:latest

Updating Relution is then as simple as:

cd /opt/relution/
docker-compose pull
docker-compose up --detach
Make sure to replace docker_relution with the name of the Relution container (“container_name”) you’ve specified in your docker-compose.yml if the name deviates from our template.

This will pull the latest docker image for each container before restarting the containers. The Relution service will be unavailable for a minute or two until the containers have finished rebooting.

Manual update

  1. Download the latest Relution package

  2. Stop the Relution service

  3. Backup your Relution database

  4. Backup the installation directory

    • e.g. mv <INSTALL_DIR> <INSTALL_DIR>.bak

  5. Extract the ZIP archive to <INSTALL_DIR>

  6. Copy <INSTALL_DIR>.bak/conf/sql.conf to <INSTALL_DIR>/conf/sql.conf

  7. Start the Relution service

  8. Wait for the Relution service to start

    • Configuration is migrated to <INSTALL_DIR>/application.yml

    • The database is migrated to the latest version

From version 4.x to latest version

Docker

Edit the docker-compose.yml file and replace

  image: {productSmall}/{productSmall}:xxx

with

  image: {productSmall}/{productSmall}:latest

Updating Relution is then as simple as:

cd /opt/relution/
docker-compose pull
docker-compose up --detach
Make sure to replace docker_relution with the name of the Relution container (“container_name”) you’ve specified in your docker-compose.yml if the name deviates from our template.

This will pull the latest docker image for each container before restarting the containers. The Relution service will be unavailable for a minute or two until the containers have finished rebooting.

Manual update

  1. Download the latest Relution package

  2. Stop the Relution service

  3. Backup your Relution database

  4. Backup the installation directory

    • e.g. mv <INSTALL_DIR> <INSTALL_DIR>.bak

  5. Extract the ZIP archive to <INSTALL_DIR>

  6. Copy <INSTALL_DIR>.bak/application.yml to <INSTALL_DIR>/application.yml

  7. Start the Relution service

  8. Wait for the Relution service to start

    • The database is migrated to the latest version

Scriptable/Automatic update (Linux only)

  1. Backup your Relution database

  2. cd <INSTALL_DIR>

  3. ./bin/update.sh

Checklist after an update

  • Do Relution apps on mobile devices need an update?

  • Do custom CSS files need an update?

  • Do enrolled devices still respond? (Send a “refresh device info” action)

  • Does enrollment for each platform still work?