Upgrade Tosca Server and its features

This chapter contains information on how to upgrade the Tricentis Tosca Server and all its features from version 15.2 LTS to version 16.0 LTS.

Preparatory steps

Before you upgrade the Tosca Server, you need to create backup files for the Tosca Server features that you use.

Note that the paths may vary based on the directory paths that you provided during the installation.

Tosca License Administration

If you use Tosca License Administration, create a backup of the following files and folders:

  • Tosca License Administration appsettings.json file located at C:\Program Files (x86)\TRICENTIS\Tosca Server\LicenseAdministration.

  • The App_Data folder located at C:\Program Files (x86)\TRICENTIS\Tosca Server\LicenseAdministration.

Tosca Administration Console (includes Tricentis User Administration)

If you use Tosca Administration Console, create a backup of the following files and folders:

  • Tosca Administration Console appsettings.json file located at C:\Program Files (x86)\TRICENTIS\Tosca Server\ToscaAdministrationConsole.

  • The folders Identity Management and UserData. If you use an SQLite database, this folder is by default located at C:\ProgramData\TRICENTIS\ToscaServer.

    If you use a MSSQL or PostgresSQL database, use the corresponding location and ensure to also back up any data protection key files stored in the Identity Management folder.

Tosca Distributed Execution

If you use Tosca Distributed Execution (DEX), create a backup of the following files:

  • The DEX Server Tricentis.DistributionServerService.exe.config file located at C:\Program Files (x86)\TRICENTIS\Tosca Server\DEXServer.

  • The DEX Monitor appsettings.json file located at C:\Program Files (x86)\TRICENTIS\Tosca Server\DexMonitor.

Automated Object Service

If you use Automated Object Service (AOS), create a backup of the AOS appsettings.json file.

The file is located at C:\Program Files (x86)\TRICENTIS\Tosca Server\AutomationObjectService.

Interactive Testing

If you use Interactive Testing, create a backup of the Interactive Testing appsettings.json file.

The file is located at C:\Program Files (x86)\TRICENTIS\Tosca Server\InteractiveTestingStandalone.

Tricentis File Service

If you use the Tricentis File Service, create a backup of the Tricentis File Service appsettings.json file.

The file is located at C:\Program Files (x86)\TRICENTIS\Tosca Server\FileService.

Tricentis Test Data Service

If you use Tricentis Test Data Service, create a backup of the following files:

  • The appsettings.json file located at C:\Program Files (x86)\TRICENTIS\Tosca Server\TestDataService.

  • The TestDataService folder located at C:\ProgramData\TRICENTIS.

  • The database of the created repositories. The default location is C:\ProgramData\TRICENTIS\ToscaServer\TestDataService.

Exploratory Testing Server

If you use the Exploratory Testing Server, perform the following steps:

  1. Session data of ongoing and past sessions that you've stored on Tosca Server will not be accessible after the upgrade.

    • Make sure to timebox and finish ongoing sessions before you start the upgrade. Import the results into a workspace in Tosca Commander to persist the files and session data. This ensures that you have access to them independently of Tosca Server.

    • To store data from past sessions, create a backup of the server.db file and the contents of the data folder. The default location is C:\ProgramData\TRICENTIS\Exploratory Testing.

  2. Create a backup of the Exploratory Testing Server Web.config file located at C:\Program Files (x86)\TRICENTIS\Tosca Server\ExploratoryTestingServer.

  3. Remove the existing server.db file. The default location is C:\ProgramData\TRICENTIS\Exploratory Testing. This file isn't compatible with the latest version of Tosca Server and might prevent it from starting up if you don't remove it.

Tosca REST API Service

If you use the Tosca REST API Service, create a backup of the Tosca REST API Service TCAPIRestServiceStandalone.exe.config file.

The file is located at C:\Program Files (x86)\TRICENTIS\Tosca Server\RestApiService.

Upgrade Tosca Server

To upgrade Tosca Server, follow the steps below:

  1. Uninstall the old version of Tosca Server. This also removes user defined settings.

  2. Optionally, install the latest .NET versions before you install the new version of Tosca Server. Otherwise, Tosca Server installs these .NET versions during the setup. However, you can update minor .NET versions after the installation.

  3. Install the new version as described in chapter "Installation process". Refer to your backup files to configure your settings during the installation.

  4. If you use Tricentis Test Data Service, perform the following actions after the server installation:

    • To migrate your data, you must recreate your Test Data Service repositories manually. To do so, create new repositories with the same names and database types.

    • Copy and paste the backup TestDataService folder to C:\ProgramData\TRICENTIS\ToscaServer to replace the files.

  5. Go to Settings->Tricentis Services and make sure that the server endpoint address is the Tosca Gateway's address.

  6. If you upgrade from Tosca 15.0 or lower and you use Tosca Server with an HTTPS binding, set up authentication. Tosca Server only allows authenticated requests. This means that users need to sign in whenever they perform an action that pings Tosca Server or try to access a server feature on the server landing page.

    If you use Tosca Server Repository workspaces, users only have to authenticate once when they open the workspace.

    If you already manage your users in Tricentis User Administration, you don't have to perform any extra steps. In this case, users sign in with their Tricentis User Administration credentials after the upgrade.

    If you don't use Tricentis User Administration yet, you need to set it up for authentication.

With the exception of Test Data Service (see step 4), don't replace the config.json file with files from previous versions. Use the backup files only as a reference to re-configure your settings during the installation process.

If you encounter unexpected behavior in a Tosca Server feature after the upgrade, compare the backed up Web.config or appsettings.json file of the respective feature with the upgraded version.