This article outlines the prerequisite applications and databases that are necessary for a successful installation of Tricentis AnalyticsVersion 1.3.1These prerequisites must be installed and configured prior to beginning installation .
Tricentis AnalyticsVersion 1.3.1 is only compatible with:
qTest Manager 9.7.1
Currently the Tricentis Analytics installer is available for a Windows OS. If you want to use Tricentis Analytics and are using a Linux or Docker Operating System, you need to install a Windows Server VM on those machines, in order to use Tricentis Analytics.
The following Tricentis applications, that you are reporting from, and associated database prerequisites must be installed prior to the installation of Tricentis Analytics:
Tosca 12.3 (for Tosca users)
You must know which repositories are included in your Tosca Data.
qTest Manager 9.7.1 + Postgres (for qTest users)
Collect the following Postgres database information before running the installer:
If you are using a Read Replica database for Manager, you should use that specific database information.
ElasticSearch 6.3-6.8 (For qTest Customers Only)
As of the Tricentis Analytics 1.3.1 Patch, qTest users must make crucial changes to your ElasticSearch database. Please refer to the Tricentis Analytics 1.3.1 Patch notes for further instruction.
Collect the following information for the version of ElasticSearch you have installed, which is also supported and enabled in qTest Manager 9.7.1:
ElasticSearch URL: this is the IP and Port needed for installation
Enabling ElasticSearch in Manager was first introduced with Manager 9.5.3 when ElasticSearch became a prerequisite for qTest OnPremise customers. If you have already enabled and migrated your data from Hibernate Search to ElasticSearch, or you have had a fresh install of Manager 9.5.3+, you will not need to perform this migration/enablement action again.
MSSQL 2016 is used with the Tricentis Analytics Reporting Database.
You must have:
A user created to use the database as a SQL user for the connection setup.
For long-term and enterprise use: Standard Version (recommended)
EC2 or RDS
If you install the default named instance of MSSQL, then your server should be localhost.
If you use MSSQL RDS, then you should use ip or domain to connect.
If you would like to use Management Studio (the UI client tool), you can download it here.
Management Studio requires a system reboot. Keep all of the prerequisites ready so that you will not have to restart the system in the middle of the Tricentis Analytics installation. Your SQL server timezone must be set to UTC.
Important Windows Information
If you are using Windows 2016, make sure that you have Microsoft .NET Framework 4.7.1 installed. For instructions on this step, read this article.
Required Ports for Tricentis Analytics
Default TCP Ports: (these are not interchangeable or configurable. Validate to check that these ports are not being used by other applications):
80 (open both in and outbound)
443 (open both in and outbound)
4242 (open inbound)
4247 (open inbound)
Tricentis AnalyticsAuthority Web App Port (this is configurable):
5000 (open both in and outbound)
Port for Tricentis Analytics internal Postgres (this is configurable if necessary):
Internal port for AppSync (this is configurable if necessary):