- This is the instruction to upgrade qTest Sessions v3.0.1, v3.0.2, v3.0.3, v3.0.4 to v.3.0.9 on load balancing environment, where multiple instances of qTest Sessions were installed, and each instance is running on its own Windows server
- qTest Sessions v3.0.9 only works with qTest Manager v8.4+
- You will also need to upgrade PostgreSQL database engine to 9.5 for qTest Sessions v3.0.9 to work
Before you begin
- Make sure qTest Manager is running and your qTest license file has been imported
- Make sure your server environment meets recommended hardware requirements
Upgrade qTest Sessions
1. Stop all qTest Sessions instances
Make sure all qTest Sessions instances are not running by following below steps:
- Access to each qTest Sessions server and
- Right click on qTest Sessions icon in system tray then go to qTest Session Service - Running menu group and select Stop menu item
2. Upgrade PostgreSQL database engine to 9.5
Access to the database server where PostgreSQL was installed and is managing your qTest Sessions database.
Follow these instructions to Upgrade Postgres 9.4 to 9.5, as Sessions 3.0.9 requires Postgres 9.5 to work successfully.
When you are done, proceed to the next step to upgrade qTest Sessions.
3. Upgrade qTest Sessions
Access to a server that qTest Sessions was installed.
Download qTest Sessions 3.0.9. Once downloading completes, double click on the downloaded installer to start the update wizard.
Click the Next button. The installer will start to extract files.
After the files are extracted, you will be allowed to specify web server ports for qTest Sessions
By default, the Configuration Wizard indicates 4 port numbers used by previous installation of qTest Sessions for HTTP, Admin, AJP and HTTPS ports. However, you can freely define your own ports depending on security rules of your network by selecting Use custom ports
- Please make sure the ports you selected above are not blocked by your firewall
- When specifying the port numbers, make sure the selected ports are all available and there are no other applications running on them. Follow these instructions to check your network ports to check your network ports
- If you are installing qTest Sessions on the same machine with qTest Manager, a best practice is to select Use custom ports option then specify the port numbers that are not occupied by qTest Manager instance.
In the next screen, you will have an option to enable a secured connection (HTTPS) between users’ browsers and qTest Session servers.
If you have an existing certificate, you need to specify the locations of the Certificate file and the Private Key file by clicking on the Browse button.
You can optionally provide your Chain Certificate, which is your certification authority's certificate.
Again, the configuration wizard will automatically select the options that you have chosen in previous installation.
- If you're enabling secure connection but using a self-signed certificate, beware that the first time you access to qTest Sessions from a web browser, the web browser will show the security warning for the unsecured connection. You must accept the untrusted connection for the system to work properly
- Click Next, you are then required to configure the connection to your existing PostgreSQL database on your database server
- You can select the checkbox to Reset data, and existing data in the database schema will be removed
Click Next then you will be presented with a screen to configure Redis server. Make sure you enter the correct Hostname and Port where Redis was installed and is running, then click Next.
Next, you will configure the information of your Elasticsearch server. Unless you want to make some changes to reflect the new environment in this upgrade, it is highly recommended you keep these previous configuration unchanged
- Cluster name: the Elasticsearch cluster name, default is elasticearch
- Host name: the name (or IP address) of the server that you have installed Elasticsearch
- HTTP Port: default is 9200, or what you have configured in previous installation.
- TCP port: default is 9200, or what you have configured in previous installation.
Next screen is for specifying existing a directory to store session data, it is highly recommended that you keep the value unchanged. Click Next to continue.
Next, specify qTest URL and qTest Master Token to connect to your qTest Manager instance. Click Next to continue.
- Your qTest Manager instance must be running
- The port must be included in the URL: http://[qTest_Manager_IP_Address]:[HTTP_Port] or http://[qTest_Manager_Domain_Name]:[HTTP_Port]
- If your qTest Manager is using SSL, you need to input the URL with HTTPS protocol and HTTPS port. For example: https://[qTest_Manager_IP_Address]:8443 or https://[qTest_Manager_Domain_Name]:8443
- Go to Get qTest Master Token for instructions to get your qTest Master Token
After you have input all required information and click on Next button, the wizard starts to configure qTest Sessions.
After this process is done, you will be directed to the final information screen, where you can review all the installed components and their settings
Click Finish to exit the installation wizard
Now repeat step #3 to upgrade qTest Sessions on other servers.
4. Configure qTest Manager
This step is to make sure the URL of qTest Sessions Load Balancer are kept unchanged after you perform qTest Sessions upgrade to the new version.
- Login to your qTest Manager using a Site Administrator account
- Go to the Site Administration page and click on the tab SYSTEM CONFIGURATIONS
- In the QTEST EXPLORER | SESSIONS section, ensure the URL of your qTest Sessions site is the public IP Address of qTest Sessions Load Balancer
You have finished upgrading qTest Sessions to version 3.0.9, now you can access to qTest Sessions site and verify the new version.