| Table of Contents | ||||
|---|---|---|---|---|
|
...
For additional information on verifying pre-requisites refer this article.
- The three servers should be on the same network and able to communicate with each other. Refer QMetry Deployment Document for the requirements.
- All the servers should have support of these commands: unzip, wget, curl and vim.
- Internet access should be enabled on all 3 servers to install using docker.
- Ensure Proxy Servers are not blocking downloads from the Internet.
- Docker installation requires root user access. To install using a non-root user, follow the steps specified here before starting the install on both QMetry and Report servers.
- QMetry and Report Servers should be able to communicate over 80/443 and Database Server 3306/DB Ports. Ports 8080 and 33061 should be enabled/open on Reports Server to allow connections from QMetry application server.
- Docker is installed under /var/lib/ directory. We recommend allocating enough space here to ensure QMetry has enough space to save your data.
- Data of QMetry attachments added is saved under : /var/lib/docker/volumes/qmetry_attachment/_data
- Get the following files from QMetry Support: QMetryApp.zip, Spark_Report_Install.zip, License and docker credentials required for installation.
- Post installation, QMetry Application and Report tool both should be configured either on https or http.
- Following Ports should be open on respective servers:
| Installation | Ports that need to be enabled |
|---|---|
| QMetry Database Server | 3306 |
| QMetry Application | 80/443 |
| QMetry Reporting Tool | 80/443, 8080, 8000, 33061 |
Setting up QMetry DB Server in AWS
...
- Login to AWS Management Console and open the Amazon RDS console.
- RDS > Databases > Actions > Stop RDS Service.
- Go to Configurations tab > Parameter Group.
- Search and then add / edit the following parameters.
| 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 |
...
After waiting for about a minute, command docker ps should return the following :
.png?version=1&modificationDate=1586753872060&cacheVersion=1&api=v2&width=1000)
Step 4 - Restart Reports Services
...
Go to QMetry > Customization > Insight Configuration
...
Configuration
...
- Enter Host : Reports Server Host Public IP/DNS
- Enter Port : 33061
- Enter Username : root
- Enter Password : qmetryreports@!Nf0#
Enter Database Name : qtmanalytics
...
Cick Test to ensure successful connection and then hit
...
"
...
...
Test
...
and
...
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.
...