QMetry Online and Offline Upgrade Guide for Linux
Note
If you're upgrading to QMetry v8.24.1.1, update the Automation API to its latest version.
For more information, refer Install/Upgrade Automation API Feature for Online Installations
This guide is intended for customers running QMetry containers on Linux and outlines the steps to upgrade from an older version of QMetry to the latest release. In addition to upgrading QMetry, it also includes the upgrade of Apache Tomcat to version 11.0.5.
The guide provides detailed instructions for backing up the QMetry database, upgrading the application, updating containers, and configuring SSL and Jira integration.
System Requirements and Pre-requisites
Before upgrading, ensure the following:
For Online Upgrade
MySQL version for both QMetry Reports and QMetry Application is 8.0.40.
Internet connection is enabled on the server.
For Offline Upgrade
Perform the following steps:
Download Docker images of QMetry products.
Download the required Docker images.
Install Docker on the system before executing the Docker commands.
Download the container image. For more information, refer to Downloading Docker image of the QMetry Application.
Transfer and restore the downloaded Docker images.
Move the downloaded Docker images and LinuxQMetryAppTomcatUpgrade.zip to the target server.
To restore the container image, refer to Restoring Docker image of the QMetry Application .
Once this is done, ensure the following:
MySQL version of QMetry Reports and QMetry Application is 8.0.40.
QMetry Online and Offline Upgrade Process for Linux
To upgrade QMetry to the latest version, perform the following steps:
Step 1: Backup the Existing QMetry Database
To backup your existing QMetry database, perform the following steps:
Take a backup of the "qmetry" database. The backup is saved in /opt by default.
Run the following command to replace the username, password, and backup file location.
docker exec qmetryapp_db sh -c 'exec mysqldump -uroot -p<password> --triggers --routines --hex-blob --single-transaction --lock-tables --no-create-db qmetry' > /opt/qmetry_backup_<date>.sql
Example 17.docker exec qmetryapp_db sh -c 'exec mysqldump -uroot -pqmetry --triggers --routines --hex-blob --single-transaction --lock-tables --no-create-db qmetry' > /opt/qmetry_backup_2023-01-01.sql
Verify that the database is backed up and is available.
Step 2: Download Required Files
Download the required files by following these steps:
Get the latest version of QMetry Upgrade Installer from the QMetry Support Portal.
Download
LinuxQMetryAppTomcatUpgrade.zipto the QMetry Application Server on the host machine.
Step 3: Run the QMetry Upgrade
To run QMetry Upgrade, perform the following steps:
To list the running containers, run the following command:
docker ps
If Docker is not running, run the following command:
docker start qmetryapp_db docker start qmetry_app_1
Note
Make sure to replace the container names with the appropriate application names as specified in the previous command.
Go to the directory where the LinuxQMetryAppTomcatUpgrade.zip file is located and unzip the file LinuxQMetryAppTomcatUpgrade.zip on the host machine.
unzip LinuxQMetryAppTomcatUpgrade.zip
Go to the extracted QMetry directory
cd LinuxQMetryAppTomcatUpgrade
Run the following command to grant execution permissions to the upgrade script.
chmod +x upgrade.sh
If your QMetry Version is below 8.9.0.3
Validate the name of your existing container and license volume in the upgrade.sh file before running it.
To validate the name of your existing container and license volume, perform the following steps:
Run the following command to check the Docker volumes' names
docker volume ls
Docker volume name should be qmetry_license.
Run the following command to check the Docker containers' names
docker ps
Docker container name should be qmetry_app_1.
If the names differ, update the upgrade.sh file with the correct values with these steps:
Open upgrade.sh in edit mode.
Run the following command:
vi upgrade.sh
Update the file with the correct volume and container names.
Press i to change the file mode to insert.
Update the variables according to the existing volume and container name.
exist_license_volume → Value from docker volume ls for license exist_qmetry_container → Value from docker ps for qmetry
Press Esc, and then type:wq to save the changes.
Run the upgrade script:
sh upgrade.sh
The process may take some time to complete. Kindly be patient and allow it to finish properly.
Step 4: Enter the Required User Inputs
The upgrade utility will prompt you to confirm whether you want to proceed with the upgrade.
Mode of Installation | Prompt | Values | Default | Details |
|---|---|---|---|---|
Linux Online Installation | Do you want to make an online installation (Y or N)? | Y,y, N,n | Y | Enter “Y” to begin the online upgrade. |
Linux Offline Installation | Do you want to make an online installation (Y or N)? | Y,y, N,n | N | Enter “N” to begin the offline upgrade. |
- | Please enter the directory path of the .tar file for the Docker image | - | - | For offline upgrade, mention the directory path of the .tar file for the Docker image. For example, /opt/qtm |
Step 5: Verify QMetry Container Status
Run the following command to list the running containers.
docker ps
Step 6: Log in to QMetry
Open the QMetry application in your browser and verify it by logging in.
Step 7: Install or Upgrade QMetry Jira Add-on
Download the correct Jira add-on version that matches your QMetry version. Refer to the table below to find the compatible Jira add-on version based on your QMetry version.
QMetry Version | Jira-addon Version Required |
8.24.x | 2.3.9_jira9 (Jira Version 9x), 2.3.9 (Jira Version 10x) |
8.23.0 | 2.3.7_jira9 (Jira Version 9x), 2.3.7 (Jira Version 10x) |
8.22.1 | 2.3.5 |
8.21.0 | 2.3.3 |
For more information on QMetry Jira Integration, refer to the Steps to Install and Configure the QMetry Jira Integration app .
Reconfiguring SSL After Upgrading QMetry to the Latest Version
If you have configured SSL (https) in Tomcat inside the container, you must reconfigure it in the new Docker container.
If you encounter any issues during the upgrade, please submit a support ticket on the Support Portal.