Upgrade Tosca Extensions

This chapter contains information on how to upgrade Tricentis Tosca Extensions from version 15.1 STS to version 15.2 LTS.

Tricentis Data Integrity

As of Tricentis Tosca 15.2 LTS, reconciliation tests also support data sets in blob storage. Consequently, we reworked the Complete Row by Row Comparison Module.

If you want to use the updated functionality in your existing reconciliation tests, you need to migrate the Complete Row by Row Comparison Module that's in your workspace. To do so, right-click the Module and select Tosca DI Migration from the context menu.

Tosca Connect

To enable the communication between Tosca Commander and Tosca Connect, Tosca Commander and the Tosca REST API Service must use the same version.

If you upgrade Tosca Commander, you also have to upgrade the Tosca Server, which contains the Tosca REST API Service.

To ensure full functionality, use Tosca Connect 17.3.3 or higher. For information on how to upgrade Tosca Connect, see this Tricentis Knowledge Base article.

Tosca Continuous Integration

To upgrade Tosca Continuous Integration, follow the steps below:

1. If you have changed any default values in your configuration files, create a backup of those files. During the upgrade, Tricentis Tosca overwrites the existing files in your standard installation folders.

   For detailed information on configuration files, see the respective sections in the Tricentis Tosca manual:

   • Continuous Integration with Remote Service

   • Continuous Integration with Tosca Distributed Execution

   • Continuous Integration with build server

2. If you use Tosca Server with an HTTPS binding, set up the CI client authentication. Tosca Server only allows authenticated requests. Whenever it receives a request, Tosca Server checks whether a user with these credentials exists; if that's true, it proceeds with the task. Click here for more information on how to set up authentication via Tricentis User Administration.

   CI clients also need to authenticate. You have to create at least one user in Tricentis User Administration for your CI clients; you can use the same account for multiple clients. This user has to have a personal access token in Tricentis User Administration. You need the token's client ID and client secret when you configure your clients after the upgrade.

3. Update the new configuration files with information from your backups.

Do not replace the version 15.2 LTS configuration files with your backup files.

Tosca Orchestrated Service Virtualization

To upgrade Tosca OSV, follow the steps below:

1. Ensure that you have upgraded Tosca Commander. Tosca Orchestrated Service Virtualization (OSV) and Tosca Commander must use the same version.

2. Backup your databases if you need the information of your previous virtualizations (optional).

3. Reinstall Tosca Orchestrated Service Virtualization as described in chapter "Install Tosca OSV".

4. Manage your licenses in the OSV Monitor via Environment->Account as described in chapter "License management".

5. In the Tosca OSV Monitor, clear the database for each OSV Environment in the Edit Environment window by using the option Create Database. This is necessary because Tosca OSV does not work with database schemes of previous versions.

6. Transfer the Scenarios to your OSV Environment as described in chapter "Transfer Scenarios".