VISULOX 5 Documentation

Updating VISULOX

This document describes the procedure to safely update VISULOX using RPM packages:

  • VISULOX Portal (vlx-portal)

  • VISULOX Connector (vlx-connector)

  • VISULOX Runtime Environment (vlx-portal-rte)

  • VISULOX Core (visulox)

  • VISULOX Runtime Environment (visulox-rte)

The upgrade procedure ensures that:

  • Existing configuration and data are preserved

  • Database migrations are applied correctly

  • Services are restarted in a controlled and auditable way

  • Downtime is minimized

This guide applies to:

  • Staging environments

  • QA servers

  • Production servers

  • Developer test servers using RPM deployment



1. Transfer files to the Server

Create a temporary folder on the server:

mkdir -p /tmp/vlx-upgrade

Copy the following files to the vlx-upgrade folder:

- vlx-portal-rte-5.0.1-1.el9.x86_64.rpm
- vlx-portal-5.0.1-1.el9.x86_64.rpm
- vlx-connector-5.0.1-1.el9.x86_64.rpm

- visulox-rte-1.2.0-1.el9.x86_64.rpm
- vlx-core.5.0.1-1.el9.x86_64.rpm

2. Upgrade RPM Packages

Stop running services:

sudo systemctl stop vlx-portal
sudo systemctl stop vlx-connector
sudo visulox stop

Update VISULOX:

cd /tmp/vlx-upgrade

# VISULOX Portal
sudo dnf upgrade vlx-portal-rte-*.rpm -y
sudo dnf upgrade vlx-portal-*.rpm -y
sudo dnf upgrade vlx-connector-*.rpm -y

# VISULOX Core
sudo dnf upgrade visulox-rte-1.2.0-1.el9.x86_64.rpm
sudo dnf upgrade vlx-5.0.1-1.el9.x86_64.rpm

This will:

  • Replace binaries

  • Preserve configuration files

  • Keep database intact

  • Maintain system users and permissions

Start services after update:

sudo visulox start
sudo systemctl start vlx-portal
sudo systemctl start vlx-connector

3. Apply Database Migrations

Check current migration version:

sudo /opt/visulox-portal/bin/vlx-portald migrate \
  --migration-version \
  -c /opt/visulox-portal/configs/config.json

Apply pending migrations:

sudo /opt/visulox-portal/bin/vlx-portald migrate \
  --up \
  -c /opt/visulox-portal/configs/config.json

Notes:

  • If no migrations are required, nothing will be applied.

  • If migrations fail, the RPM may be missing required migration files.

  • Check logs for errors:

sudo journalctl -u vlx-portal -n 50

4. Verify Upgrade

Check Portal status:

sudo systemctl status vlx-portal.service

Check Connector status:

sudo systemctl status vlx-connector.service

Check Running Processes

ps auxwwf | grep "vlx\|visulox"

Check Portal logs

tail -f /var/log/visulox-portal/portal.log

Check Connector logs

tail -f /var/log/visulox-portal-connector/connector.log

Check system logs

sudo journalctl -u vlx-portal -n 100
sudo journalctl -u vlx-connector -n 100

5. Post-Upgrade Validation Checklist

Verify:

  • Portal web interface loads

  • Users can login

  • Sessions can be started

  • Connector connects correctly

  • LDAP / AD authentication works (if enabled)

  • No migration errors in logs

  • No service restart loops

6 Rollback Procedure (if required)

If upgrade fails, reinstall the previous RPM version:

sudo dnf downgrade vlx-portal-<previous-version>.rpm -y
sudo dnf downgrade vlx-connector-<previous-version>.rpm -y
sudo dnf downgrade vlx-portal-rte-<previous-version>.rpm -y

Then restart services:

sudo systemctl restart vlx-portal
sudo systemctl restart vlx-connector