In this guide, we'll run you through installing QMetry Database, QMetry Test Management application and QMetry Reporting Tool in a 3 Tier Architecture.
AWS 3 Tier Architecture
Server 1 | QMetry App |
Server 2 | QMetry Reports |
AWS RDS | QMetry DB |
For additional information on verifying pre-requisites refer this article.
Installation | Ports that need to be enabled |
---|---|
QMetry Database Server | 3306 |
QMetry Application | 80/443 |
QMetry Reporting Tool | 80/443, 8080, & 33061 |
For database you need to setup a RDS.
Step 1. Create a DB parameter group by following the below steps :
Step 2. Edit the DB parameter group you created above.
Parameters | Values |
---|---|
lower_case_table_names | 1 |
max_allowed_packet | 536870912 |
character_set_server | utf8mb4 |
collation_server | utf8mb4_unicode_ci |
innodb_thread_concurrency | 10 |
query_cache_limit | 1073741824 |
table_definition_cache | 2000 |
group_concat_max_len | 1536000 |
innodb_autoinc_lock_mode | 2 |
tx_isolation | REPEATABLE-READ |
sql_mode | STRICT_TRANS_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION |
binlog_error_action | ABORT_SERVER |
binlog_format | ROW |
binlog_group_commit_sync_delay | 0 |
binlog_group_commit_sync_no_delay_count | 0 |
binlog_gtid_simple_recovery | 1 |
binlog_max_flush_queue_time | 0 |
binlog_order_commits | 1 |
binlog_row_image | FULL |
binlog_rows_query_log_events | 0 |
binlog_stmt_cache_size | 32768 |
max_binlog_stmt_cache_size | 18446744073709547520 |
log_bin_trust_function_creators | 1 |
log_bin_use_v1_row_events | 0 |
Step 3.
Save the following details for QMetry Installation.
Step 1. Copy the QMetryApp.zip received from QMetry Support to your server. Navigate to the directory where this file is kept and execute the following commands.
Step 2. Modify docker-compose.yml file with the MySQL DB details:
Execute the below commands:
Step 3. Execute the following command.
Step 4. Enable Service for Docker Engine
You will be asked for credentials. Enter docker credentials shared as a part of installation package.
The installation may take a while. Once the installation is complete, execute the following command.
The following message will be displayed.
Step 5. Getting your QMetry License and Installing it.
Step 6. Access QMetry application using the following details:
Note : This installation installs QMetry over Apache Tomcat 9.x, and Open JDK 11 in a docker container.
Step 7. After the above steps are completed, log into QMetry application.
Step 8. Additional Tomcat Configuration: QMetry is installed with a default configuration of minimum and maximum heap memory utilization. You can modify these settings depending on your hardware configuration. Refer Additional Configuration for more details.
If you have purchased Advanced Reporting then you will need a separate server for QMetry Reporting.
This step we'll run you through installing QMetry Test Management Reports in your environment.
Hardware Configurations Recommended
Supported OS : Linux - Cent OS 7 and 8, RHEL 7 and 8
Server Configurations | Small Teams < 50 Users | Medium Teams < 500 Users | Large Teams 500+ Users | |||
Stand Alone Server | ||||||
| Min | Recommended | Min | Recommended | Min | Recommended |
CPU | 4 Cores | 4 Core | 8 Core | 16 Core | 16 Core | 24 - 32 Core |
Memory | 8 GB | 16 GB | 16 GB | 24 GB | 32 GB | 32 - 64 GB |
HDD (Free Space) | 100 GB | 250 GB | 50 GB | 100 GB | 50 GB | 500 GB |
Upload the Spark_Report_Install.zip to the /opt directory of the Report server and unzip it
Options | Details | Example |
---|---|---|
Number of CPU's to allocate | Allocate 3/4th of the available CPUs. For example if CPU has 8 cores, enter 6 To check total CPUs, run the command : lscpu | 6 |
Memory to allocate in GB(s) | Allocate 3/4th of total memory on server. For example for 24GB, enter 18 To check total memory, run the command : free -h | 18 |
Wait for the script file to finish executing.
Once the script finishes executing it will prompt to enter the following parameters
Options | Details | Example |
---|---|---|
Enter Mysql Database Host IP / DNS Name (Qmetry) | QMetry DB Host Public IP/DNS | 10.10.11.100 |
Enter Mysql Database Port (Qmetry) | QMetry App MySQL DB Port. Enter 3306, unless QMetry DB port is different | 3306 |
Enter Mysql Database Schema (Qmetry) | QMetry App DB schema name. Enter : qmetry | qmetry |
Enter Mysql Database Username (Qmetry) | QMetry App DB username. Enter : root | root |
Enter Mysql Database Password (Qmetry) | QMetry App DB password. If it is unchanged from default, enter : qmetry | qmetry |
Enter Mysql Database Host IP / DNS Name (Reports) | Enter the static docker IP : 10.5.0.7 as the IP address of QMetry Reports server | 10.5.0.7 |
Enter Mysql Database Port (Reports) | Enter the port where reports DB is running. Enter : 3306 | 3306 |
Enter Mysql Database Schema (Reports) | Enter the database schema name of QMetry Reports DB - | qtmanalytics |
Enter Mysql Database Username (Reports) | Enter username of QMetry Reports DB | root |
Enter Mysql Database Password (Reports) | Enter password of QMetry Reports DB - qmetryreports@!Nf0# | qmetryreports@!Nf0# |
Enter Port To Start SyncJob (Reports) | Reports Sync Job runs from this port : 8080 | 8080 |
Do you want to Run Force Sync Now ? (y/n) | Enter y to sync all the QMetry data to Reports DB with the current script. Always enter y at the time of fresh reports install | Type : y |
Enter Memory to allocate in GB(s) to Spark | Entered memory would be used by the sync job while running a full sync of data. Enter 3/4th of total memory available on server. For example, if memory on server is 24 GB, enter 18 | 18 |
Note: In cases when you need to force sync to re-sync any missing data, just repeat step 3, and skip qll parameter details (by hitting enter) and just enter y when prompted for a force sync.
Wait for the script to finish executing.
After waiting for about a minute, command docker ps should return the following :
Go to QMetry > Customization > Insight Configuration
Enter Database Name : qtmanalytics
Click Test to ensure successful connection and then hit "Test & Save"
Note : "Sync Data" is required first time after reports installation. Time taken to sync depends on amount of data in QMetry. Sync Progress and Status can be monitored as shown in the below screenshot. QMetry custom reports remain inaccessible during a sync in progress and is recommended to be run only during off-peak hours.
Users can start using QMetry Reports when the sync is completed. QMetry remains available during this time.
Your QMetry and Reports Installation is complete.
With the release of v8.5.2, QMetry is providing capability of installing Redis server. Overall performance and scalability can be improved using Redis caching. To install the Redis Server, refer to Installing Redis Caching Server.
If you are facing any issues during the installation process, write us at qtmprofessional@qmetrysupport.atlassian.net. This will automatically open a ticket with our support team and help you to follow the progress.