Menu

qTest Controller - Setting up qTest Launch with Postgres Read Replica 9.7.1 OnPremise

Overview

qTest Launch supports Read Replica from version 1.5.2 On Premise. The goal for this is to split complex queries from the qTest Manager production database.

Prerequisites

  • This article assumes you have the knowledge to create a Postgres read-replica server
  • You have successfully set up qTest Manager Read Replica

Notes:

  • Although qTest Launch also supports Read Replica, setting up Read Replica in qTest Launch is optional. So if you do NOT want to support Read Replica, simply discard these instructions
  • qTest Launch uses qTest Manager's databases, so setting up Read Replica in qTest Launch requires the same Read Replica configurations as qTest Manager. You will need to obtain this information, which should be the same as qTest Manager's Read Replica configuration:
    • Read Replica database server host: this is the Postgres database server where qTest Manager's Read Replica database is running
    • Read Replica database server port: the port that qTest Manager's Read Replica database server is listening
    • Database username and password: credentials to access to qTest Manager's Read Replica database on Postgres server
    • qTest Manager's Read Replica database name
  • These instructions are verified on qtestctl 6.4

Stop Launch

  • Linux (non-Docker)- Access the current directory "qtestctl" where you've installed your latest version of Launch.
    $ ./qtestctl stop
  • Windows
    C:\[path_to_qtestctl]>net stop qtest
  • Docker- Access the current directory "qtestctl" where you've installed your latest version of Launch.
    $ ./shutdown

Modify qtestctl/launch/build.gradle

Add or modify line 79. Notes: Don't forget to fill your replicated DB information into the placeholders. 

77 environment([
78 PG_URL: dbUrl,
79 RR_PG_URL: "postgresql://{DB_USERNAME}:{DB_PASSWORD}@{REPLICATED_DB_HOST}:{REPLICATED_DB_PORT}/{QTEST_REPLICATED_DB_NAME}",
80 PORT: config['launch.port'],
81 ROOT_URL: config['launch.url'],
82 QTEST_URL: config['manager.url'],
83 PM2_HOME: pm2Dir
84 ])

Restart qTest Service and Verify 

  • Linux (non-Docker)
    $ systemctl start qtest
  • Windows
    C:\[path_to_qtestctl]>net start qtest
  • Docker
    $ ./startup

Access Launch from the 9-box in qTest Manager and verify connectivity

Powered by Zendesk