Perform migration manually

Tosca Commander stores its project data in repositories. If the data structure, i.e. the schema version, changes, you need to migrate these repositories. You also need to migrate XEngines to upgrade your XModules and linked TestCases.

This chapter describes how to perform your upgrade migrations manually. For information on how to migrate via Tosca Administration Console, see chapter "Perform migration with the Administration Console".

Migrated repositories and TestCases are not downward compatible.

Migrate repositories

Check chapter "Schema version" for the schema version of Tricentis Tosca 13.1. If the schema version has not changed between 13.0 and 13.1, you can skip this step.

Make sure you have created a backup of your database before migration.

If the migration fails, you must load the backup before making another migration attempt.

In this case, create a new workspace to connect to the migrated repository.

Tricentis recommends that you implement and test the database migration on a test database first. If the migration on your test database was successful, continue migrating your productive database.

Single-user repositories are automatically migrated when you open them for the first time with Tosca Commander.

To migrate multi-user repositories, i.e. repository databases, you need to have ALTER, CREATE and DELETE access rights for

  • creating tables

  • deleting and creating indexes in the respective database

To migrate, call up the program DbRepositorySchemaMigrator.exe via command line. This program is located at %COMMANDER_HOME%.

Use the following syntax in the command line:

Syntax:

DbRepositorySchemaMigrator.exe <database type> [Schema name] [tablespace] <connection string> [-s]

  • Replace <database type> with the database type of your repository. Supported types are Oracle, MS SQL Server, DB2, or SQLite.

  • Replace [Schema name] with the database schema name. This parameter is optional.

  • Replace [tablespace] with the tablespace name of your database. This parameter is optional.

    The name of the tablespace depends on which database you use: Tablespace (DB2), Userspace (Oracle), FileGroup (MS SQL).

  • Replace <connection string> with an applicable connection string. You can use the workspace connection string in Tosca Commander under Project->Info.

    The connection string must contain the user that you use to access the common repository.

  • The -s is an optional parameter. It allows you to perform the migration without any user interaction (silent mode).

For SQLite repositories, specify the entire path for the CommonRepository.db file, including the file name.

Example syntax:

DbRepositorySchemaMigrator.exe "SQLite" "[12030000]" "C:\Tosca_Projects\Tosca_CommonRepositories\qTestIntegration\CommonRepository\CommonRepository.db" [-s]

View results

Once the migration is done, DbRepositorySchemaMigrator.exe displays a message indicating whether the migration was successful or not.

You can view migration results in the log file SchemaMigration_<File name>.txt, located at %APPDATA%\TRICENTIS\TOSCA TestSuite\7.0.0\Temp\TCTempLog.

Multi-user workspaces are migrated when you open them for the first time with Tosca Commander after your have migrated the repository database.

Migrate XEngines

Migrate XEngines to make sure that your existing XModules are compatible with the current Tricentis Tosca version.

To migrate, right-click the project root element and select XEngines Migration->Update project to current version from the context menu.

You can choose to create a backup in the subsequent dialog. If you do, Tricentis Tosca creates the following elements:

  • a .tde backup for multi-user repositories

  • a .tsu subset backup for single-user repositories

The XEngine migration updates all existing XModules with the information they require to ensure compatibility.

However, the migration does not automatically import any XModules that Tricentis delivers in the new version's standard subset. To have access to new XModules, you need to import the Standard subset.

Instead of migrating, you can also manually merge existing XModules with XModules from the subset (see chapter "Merge Modules").