Upgrade Tosca Server

For upgrades from Tosca Server 16.0 or newer, we offer a simplified upgrade process that preserves previous configurations. With this process, Tosca Server automatically transfers your configurations and settings to the new version.

The only exceptions are Exploratory Testing and Interactive Testing. Tosca Server does upgrade them automatically with everything else, but you still need to manually back up and update their configuration files.

We strongly recommend that for 2023.2, 2023.1, and 16.0, you always try the simplified upgrade and don't uninstall and reinstall Tosca Server. If you uninstall/reinstall, you have to manually back up all your configuration files and populate the new version's configuration files as described in the other upgrade process.

Preparatory steps for Exploratory Testing Server and Interactive Testing

If you use Exploratory Testing and/or Interactive Testing, perform these steps before the upgrade:

1. Back up the configuration files listed in "Tosca Server configuration files". Keep these things in mind:

   • You only need to back up the files that are listed for Exploratory Testing and Interactive Testing.

   • You only need to back up the files for the features you use. For example, if you only use Interactive Testing, you only need to back up the Interactive Testing configuration files.

2. If you use Exploratory Testing, perform these additional actions:

   • Finish ongoing sessions and import the results into Tosca Commander. Tosca Server doesn't persist the files and data of ongoing sessions during the upgrade. Importing ensures that you have access to them independently of Tosca Server.

   • Remove the existing server.db file located at C:\ProgramData\TRICENTIS\Exploratory Testing. This file isn't compatible with the latest version of Tosca Server and might prevent it from starting up.

Upgrade process

Since Tosca Server supports implicit upgrades, you don't need to uninstall the old version first. Instead, just install the new version:

1. Make sure you meet the installation requirements in "Before you start".

2. Trigger the upgrade:

   • For attended installation, run the executable file.

   • For unattended installation, run the command "Tricentis Tosca Server 2024.2.exe" /s /qn.

   Depending on your system environment, you may need to run as an administrator.

3. If you use Exploratory Testing and/or Interactive Testing, re-populate the settings. Use your backups as references.

   Only use your backup files as a reference. Don't replace any new version files with your backup files. Don't paste the entire content from your backup files without checking for differences between settings in the new and the old version.

4. Open Tricentis Service Configuration and verify your settings. Then, select Save in any tab. This is an important step to finalize your upgrade.

Troubleshooting

Tosca Server upgrades component by component: it backs up the configuration files of the first component, upgrades the component, and populates the new configuration files. Then it repeats the process for the next component, and so on.

The backups of your configuration files are in a sub-folder of the data storage path: <your data storage path>/Installer/Backup.

• In GUI installations, Tosca Server uses the data storage path in Set common application data path.

• In unattended mode, Tosca Server uses the data storage path you defined with the DATADIR parameter when you installed the previous version.

If Tosca Server encounters an issue during the upgrade—or you cancel the upgrade manually—Tosca Server uninstalls all new components. You can then fix whatever prevents the upgrade and start another one by triggering the installation of 2024.2. Please note that this isn't a rollback. Tosca Server simply removes the new components, but doesn't restore the old.

We strongly recommend that you always try an implicit upgrade. If you uninstall the old version first, you have to manually back up your configuration files and populate the new version's configuration files. In this case, follow the other upgrade process.

If you upgrade from an older version, you need to follow our old upgrade process:

• Create your backups.

• Perform the upgrade process, which includes restoring your data manually.

Preparatory steps for Exploratory Testing Server

If you use Exploratory Testing, you need to perform additional steps before you start:

1. Finish ongoing sessions and import the results into Tosca Commander. Tosca Server doesn't persist the files and data of ongoing sessions during the upgrade. Importing ensures that you have access to them independently of Tosca Server.

2. Remove the existing server.db file located at C:\ProgramData\TRICENTIS\Exploratory Testing. This file isn't compatible with the latest version of Tosca Server and might prevent it from starting up.

Upgrade process

To upgrade to 2024.2, follow these steps:

1. Create backups of your configurations. You only need to do this for the Tosca Server features you actually use.

2. Uninstall the old version of Tosca Server.

3. Install the new version as described in "Install Tosca Server".

4. Re-populate the settings, using your backups as reference.

5. If you use Tricentis Test Data Service, perform the following actions:

   • 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.

   • Paste the backup TestDataService folder to C:\ProgramData\TRICENTIS\ToscaServer to replace the files.

With the exception of Test Data Service, only use your backup files as a reference when you install the new version. Don't replace any new version files with your backup files. Don't copy and paste content from your backup files without checking for differences between settings in the new and the old version.

6. In Tosca Commander, go to Settings->Tricentis Services and make sure that the server endpoint address is the Tosca Gateway address.

7. If you upgrade from Tosca 15.0 or 15.1 and you use Tosca Server with an HTTPS binding, set up authentication. Tosca Server now only allows authenticated requests. This means that users must 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 already manage your testers in Tricentis User Administration, you don't have to perform any extra steps for your testers. They can 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.

   Please note that if you use Tosca Distributed Execution, you also need to set up authentication for Agents or AOS workspace users. For details, check out the Tosca Distributed Execution setup topics.