Menu

Insights 1.12.2 to 1.15.3 Single Server Upgrade Guide for Linux (non-Docker)

Overview

In this article, we provide step-by-step instructions to upgrade qTest Insights 1.12.2 to qTest Insights 1.15.3 on a single Linux Machine (non-Docker.) Please read the instructions thoroughly before starting your installations.

To request assistance with upgrading or obtain the self-upgrade links, complete the Upgrade Request Form and reference the OnPremise Upgrades Guide.

Note: If you are performing a fresh install, use the OnPremise New Install Form and reference the OnPremise Install Guide.

Before You Begin

 Upgrade qTest Insights from 1.12.2 to 1.15.3 

 Access the current directory "qtestctl" where you've installed Insights 1.12.2.

$ ./qtestctl stop
$ ./uninstall 

Download the new package for qTest Insights 1.15.3 

NOTE:

  • If you plan to upgrade qTest Insights in the same server as other qTest application(s), e.g. qTest Manager, you do not need to re-download the package but use the one you have already downloaded 
  • To learn more about qtestctl, refer to this article qTest OnPremise - Technical detail about qtestctl
 $ wget <ENTER DOWNLOAD LINK HERE>

Extract the Package  

 $ tar -zxf qtestctl-4.0-linux-x64-full.tgz

Access the Package 

 cd qtestctl/ 
Modify the Config File 
 vim qtest.config 

Open the file \qtestctl\qtest.config, and modify the following section only.  

1 Config application list

1.1 If you are upgrading qTest Insights on a separate server, make sure there is 'insights' in apps list

apps = ['insights']

1.2 If you are upgrading qTest Insights on the same server with other qTest application(s), e.g. qTest Manager, append insights to the app list.

apps = ['manager', 'insights'] 

2 For Insights HTTP:

...
external {
postgres {
  host = '<IP address of Postgres server>'
  port = <Postgres port>
    auth {
user = ‘postgres’ 
    pass = '<password of postgres user>'
  }
    db {
    qtest = '<qTest Manager database>'
    session = '<Sessions database>'
}
}
}
...

/* application configurations */
Insights {
//Insights HTTP Port, make sure the port is not being used by other application
  httpport = <qTest Insights port>
//Insights Admin Port, make sure the port is not being used by other application
  adminport = <qTest Insights admin port>
...
scheduler {
...
//Scheduler host (same machine with Insights)
server = '<qTest Insights server>'
}
}

3 For Insights HTTPS:

...
external {
postgres {
  host = '<IP address of Postgres server>'
  port = <Postgres port>
    auth {
user = ‘postgres’ 
    pass = '<password of postgres user>'
  }
    db {
    qtest = '<qTest Manager database>'
    session = '<Sessions database>'
}
}
}
...
/* common configurations */
common {
ssl {
enabled = true
cert = "<path to certificate file>"
key = "<path to private key file>"
pass = "<passphrase of the private key>"
strict = false
}
}

/* application configurations */
Insights {
//Insights HTTP Port, make sure the port is not being used by other application
  httpport = 8081
//Insights Admin Port, make sure the port is not being used by other application
  adminport = 8007
ssl {
enabled = common.ssl.enabled
port = <qTest Insights https port>
cert = common.ssl.cert
key = common.ssl.key
pass = common.ssl.pass
}
...
scheduler {
...
//Scheduler host (same machine with Insights)
server = '<qTest Insights server>'
}
}

Install and Start

  1. Execute this command to initially set up the application:
    $ ./qtestctl --offline start
  2. Once you see this message, qTest Insights has been started.
    started.png
  3. The command will take control of the Command Prompt. Keep it running. Open your web browser, access to qTest Insights using its URL http://<Insights_host>:<Insights_http_port> to validate if it has started successfully.
    HINT: Open http://<Insights_host>:<Insights_http_port>, ify you get the message "Access denied. Please login again through qTest", that means Insights has started successfully.
    accessdenied.png
  4. Go back to the Command Prompt and stop the running process (CTRL + C to terminate)

Set up Linux Daemon

Note: If you install qTest Insights in the same machine with other qTest application(s), you only need to set the daemon once and only once when you finished installing ALL the applications in this server. Refer to this article to learn more about installing qtest service.

  1. Execute this command to run qTest Manager as a OS Service.
    $ ./install
  2. Start the OS service.
    $ systemctl start qtest
  3. To check if the service is up, use command:
    $ systemctl status qtest

active.png

Migrate Data from Insights 1.12.2 to Insights 1.15.3

  1. Stop Insights 1.15.3 before performing data migration
  2. Migrate Scheduler data
  3. Copy data from directory \qtestctl\insights\build\insightsscheduler\Schedules of Insights 1.12.2 to the new location of Insights 1.15.3 at:
    \qtestctl\insights\build\insightsscheduler\Schedules

Migrate Web Data

  1. Under the Root folder of Insights 1.12.2 \qtestctl\insights\build\tomcat\webapps\ROOT Copy the following folders to the new location of Insights 1.15.3 at \qtestctl\insights\build\tomcat\webapps\ROOT
  • CustomReports
  • ExecutedReports
  • rdDataCache
  • rdDownload
  • SavedBookmarks
  • SavedDashboards

Start Insights 1.15.3

Start Insights 1.15.3</p

  1. You now have qTest Insights upgraded to 1.15.3.
  2. You will want to access your qTest Insights instance via your browser to verify if the upgrade process completes successfully.
  3. Then you may want to uninstall qTest Insights 1.12.2.
Powered by Zendesk