Follow

Deployment Guide

QMetry_Logo.png

Download the deployment guide in pdf.

Introduction to QMetry

QMetry is an Enterprise Test Management solution used by Quality Assurance teams globally to track their manual and automated tests to ensure quality products.  

By using QMetry, QA practitioners can help the entire development team get detailed and granular insights into the state of the Testing cycle, and into other important metrics like requirements coverage. QMetry integrates seamlessly with numerous products in adjacent ALM spaces like defect tracking, requirements management and test automation.

About This Guide

QMetry offers on-premise deployment for companies that wish to install, manage and maintain their installations behind their corporate firewall. QMetry on-premise solution has all the functionality of the SaaS solution and gives better control and check over third-party products that require business regulation. This guide provides the hardware and software requirements needed to install QMetry, along with various supported deployment topologies.   

Key Benefits of On Premise installations :

Security and Backup : Companies can decide the best approach to safeguard their test data on the internal networks. This installation gives better control over data backups schedules. 

Product Upgrade Flexibility : QMetry provides several updates in form of patches and releases in a year. This installation gives Administrators an option to upgrade or continue using the current version of QMetry.  Based on team's schedule administrators can decide upgrading the version of the product.

Configuration and Integration : QMetry integrates with various defect trackers, requirements trackers - if these 3rd party tools are accessible only in company's internal networks than On Premise installation should be preferred. Also, administrators can have better control over configuration options for LDAP and SMTP. 

Hardware Specifications

Hardware Specifications can be different based on the Configuration Topologies selected.  

Basic Configuration 

Item Minimal Hardware Requirements Recommended Hardware Requirements
Operating System

Linux (64 bit)

RHEL 7

CentOS 7

Windows Server 2012 Standard

Linux (64 bit)

CentOS 7

HDD 250 GB 500 GB
RAM 8 GB 16 GB
CPU 4 8
Processor 2.4 GHz or better 3.46 GHz
Disk I/O  100MB/s  400MB/s 

Recommended and Advanced Configurations 

Item Minimal Hardware Requirements Recommended Hardware Requirements  
   Payara Server(s) Database Server(s)  Payara Server(s)  Database Server(s) 
Operating System

Linux (64 bit)

RHEL 7

CentOS 7

Linux (64 bit)

RHEL 7

CentOS 7

Linux (64 bit)

CentOS 7

Linux (64 bit)

CentOS 7

HDD 50 GB 500 GB 100GB 500GB 
RAM 4 GB 8 GB 16 GB 16 GB
CPU 4 Cores 4 Cores 8 Cores 16 Cores 
Processor 2.4 GHz or better 2.4 GHz or better 3.46 GHz or better 3.46 GHz or better 
Disk I/O  512KB/s  200MB/s  512KB/s 400MB/s 
Network I/O  100MB/s  100MB/s  1GB/s  1GB/s 

The above server configurations are supported as physical or virtual servers. We support most prominent virtualization technologies as far as above mentioned operating systems are installed.

Software Requirements 

JDK must be installed and The version of the JDK must be at least 1.8 (latest Build) (To verify, run command: java -version on server)

Deployment Topologies

Basic Configuration
Single Server: QMetry web/app server and the database are installed on the same machine.

This topology example is for a single server deployment of QMetry with Application Server such as Payara and Database System such as MySQL. In this type of installation, QMetry application, database system, and application server are installed on the same server.

Pros: Simple and Quick to Install on a Single Server
Cons: Performance could be an issue as the DB and Web-server are sharing the same CPU. Single point of failure.

How: In this scenario, you have server A for hosting QMetry application.

  • Install MySQL Server on server A and Install QMetry Database
  • Install Payara Application Server on server A and Deploy QMetry Application
  • Take the backups from same server A and transfer physical backups to another secured media (Daily, Weekly, Monthly basis).

 

Standard Configuration (Recommended)
Two Servers: QMetry web/app server and the database are installed on two separate servers.
This example shows a two-server deployment of QMetry. In this type of installation, QMetry application and Payara server are installed on the same server and only database system is installed on a separate server.
Pros: Compared to the basic performance this configuration results in better performance, However the database server needs to have better Disk I/O rate (400MB/s) . Recommended for large and fast growing databases.
Cons: More expensive than the single server configuration.

How: In this scenario, you have server A and server B for hosting QMetry application.

  • Install MySQL Server on server A and Install QMetry Database
  • Install Payara Application Server on server B and Deploy QMetry Application pointing to database hosted on server A
  • Take the backups from same server A and transfer physical backups to another secured media (Daily, Weekly, Monthly basis).

 

Advanced Configuration

Clustered: This topology example demonstrates a fully distributed enterprise deployment of QMetry. In this type of installation, QMetry is installed on a server farm. Redundant load balances direct web traffic to two web/app servers. Application servers access the database which is replicated on a different server.

Pros: Configuration with no single point of failure. Better Performance, However the database servers need to have better Disk I/O rate (400MB/s). Recommended for large and fast growing databases. High availability and failover.
Cons: Higher Cost. Advanced administration skill required.

How:  In this scenario, you have multiple servers (A, B, C, D, E,..) for hosting QMetry application in distributed environment.

  • Install MySQL Server on server A and Install QMetry Database
  • Install Payara Application Server on server B and Deploy QMetry Application pointing to database hosted on server A
  • Install Payara Application Server on server C and Deploy QMetry Application pointing to database hosted on server A
  • Configure Load Balancer between server B and C
  • Setup Replication on server D for having hot real time backup and high availability if in case of master database server failure
  • Take the backups from same server D and transfer physical backups to another secured media (Daily, Weekly, Monthly basis).
  • Install MySQL and Payara on server E to have N+1 redundancy setup as Disaster Recovery Plan
    • Configure Database as slave on server E against master on server A
    • If in case application server component failed, then you can redirect all traffic to server E
    • If in case database server component failed, then you can promote slave as master on this server

Contact Us

Please request for detailed installation guide by emailing us at support@qmetry.zendesk.com or please contact your sales representative.

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Article is closed for comments.
Powered by Zendesk