Upgrade Tosca Extensions

This topic describes the upgrade process for Tosca extensions to version 2024.2. If you use any of these extensions, their upgrade is part of your upgrade workflow.

Please note that instructions only apply to upgrades from these versions:

  • Versions that are supported around the time of the 2024.2 release: 2024.1 and 2023.2

  • Versions that are in extended support around the time of the 2024.2 release: 2023.1, 16.0, 15.2, and 15.0.

For information on how to organize upgrades for end-of-life versions, check out "Upgrade end-of-life versions".

Tosca Connect

Tosca Connect allows you to synchronize information on errors and requirements between Tosca and third-party systems.

To upgrade, follow these steps:

  1. Make sure you use Tosca Connect 17.3.3 or higher. If you don't, upgrade Tosca Connect as described in this Tricentis Knowledge Base article (opens in new tab).

  2. Upgrade Tosca Commander and Tosca Server. The communication between Tosca Connect and Tosca Commander runs via REST API Service, which is part of Tosca Server.

    Note that Tosca Commander and Tosca Server must use the same version.

Tosca Continuous Integration (legacy)

Tosca Continuous Integration (Tosca CI) allows you to incorporate Tricentis Tosca into your own CI/CD pipeline.

Note that this section only applies to legacy versions of Tosca CI.

To upgrade, follow these steps:

  1. If you changed default values in your configuration files, back up these files. During the upgrade, Tosca overwrites your existing configuration files with the 2024.2 configuration files.

    For detailed information on Tosca CI configuration files, check out the respective manuals:

  2. Enter the information from your backups into the new configuration files.

    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.

  1. Check out "Changes and deprecations", to find out about changes and potential extra steps. For example, if we implement changes to settings, you may need to re-configure settings differently.

Tosca Orchestrated Service Virtualization

Tosca Orchestrated Service Virtualization (Tosca OSV) allows you to simulate and record services that your test application needs to interact with.

To upgrade, follow these steps:

  1. If you want to keep information on previous virtualizations, back up your databases.

  2. Uninstall your existing version of Tosca OSV.

  3. Upgrade Tosca Commander. Tosca OSV and Tosca Commander must use the same version.

  4. Install Tosca OSV2024.2.

  5. Manage your licenses in the Tosca OSV Monitor via as described in chapter "License management".

  6. Open the Tosca OSV Monitor and manage licenses and databases:

    • Manage your licenses in Environment->Account.

    • Clear the database for each OSV Environment in the Edit Environment window, by using the option Create Database. This is necessary because Tosca OSV doesn't work with database schemes of previous versions.

  7. Transfer the Scenarios to your OSV Environment.

Tricentis Data Integrity

Tricentis Data Integrity (DI) is part of the Tosca Commander installation. So, when you upgrade Tosca Commander, you also upgrade Tricentis Data Integrity automatically.

However, you may have to perform a few extra steps after the upgrade. For example, if we implement changes to DI Modules, you need to migrate those Modules and adapt your TestCases. To find out about changes and potential steps after an upgrade, check out "Changes and deprecations".