QMetry Test Management v8 Install Documents
QMetry Test Management Server supports multiple deployment environments and configurations, including Linux, RHEL, Docker, Podman, AWS, and online or offline installations.
Depending on the selected environment and required capabilities, the installation may also include supporting components such as Redis, Automation API, ActiveMQ, and QMetry BDD.
The QMetry installation process follows a progressive flow, beginning with environment planning and selection of the appropriate deployment architecture. Once the core QMetry Application and Reports components are installed, additional services can be added based on requirements, followed by licensing, security configuration, final system configuration, and validation.
The following table provides a consolidated overview of the relevant installation documents, their purpose, applicability, and recommended order of use.
Plan and Prepare
Review the following documents before selecting or running an installer.
Choose QMetry Deployment path
This is the most important cluster. You do not execute every document here. Choose one path based on your environment.
Environment | Runtime | Installation document |
|---|---|---|
Linux | Docker | |
Linux | Docker | |
Linux | Docker | |
Linux | Docker | |
RHEL 8/9 | Podman | QMetry and Reports Installation on Linux – 2 Tier (RHEL8, RHEL9 & Podman) |
RHEL 8/9 | Podman | QMetry and Reports Installation on Linux – 3 Tier (RHEL8, RHEL9 & Podman) |
AWS Linux | Cloud/container | |
AWS Linux | RDS + ECR | |
AWS + RHEL | RDS + ECR / RHEL | QMetry and Reports Installation on AWS (using RDS & ECR) for RHEL8 and RHEL9 |
Install Redis caching
Once the core QMetry environment is selected, determine whether Redis is required. The official index provides separate online, offline and Podman Redis procedures, as well as combined QMetry+Redis installation guides.
Environment | Purpose | Document |
|---|---|---|
Docker / Online | Install Redis separately | |
Docker / Offline | Install Redis without internet | |
RHEL / Podman | Podman-based Redis | |
Linux / 3-tier | Combined QMetry + Redis setup | |
Linux | Combined QMetry + Redis setup |
Install Automation API
Treat Automation API as an optional functional extension, not part of every basic QMetry installation.
Environment | Related components | Document |
|---|---|---|
Docker / Online | Automation API + Redis + ActiveMQ | Install/Upgrade Automation API Feature for Online Installations |
Docker / Offline | Automation API + Redis + ActiveMQ | Install/Upgrade Automation API Feature for Offline Installations |
RHEL / Podman | Automation API + Redis + ActiveMQ | Install/Upgrade Automation API Feature (RHEL8, RHEL9 & Podman) |
Install QMetry BDD
BDD is another optional product capability. Only use this cluster if BDD functionality is part of your implementation.
Runtime | Connectivity | Document |
|---|---|---|
Docker | Online | |
Docker | Offline | |
Podman | Depends on environment |
Configure QMetry Licenses
These documents make more sense after the application and reports components are running.
Purpose | Applies to | Document |
|---|---|---|
Activate licensed QMetry instance | Docker/QMetry | Steps To Apply License File – QMetry Tomcat installed on docker |
HTTPS for QMetry application | Docker | Installing SSL Certificates for QMetry Application installed with dockers |
HTTPS for QMetry application | Podman | Installing SSL Certificates for QMetry Application installed with Podman |
HTTPS for reporting endpoint | Reports |
Additional Configurations
Purpose | Document |
|---|---|
Apply additional environment/application configuration | |
Apply additional environment/application configuration |