Transforming Repositories into New Versions

You transform repositories when you upgrade to a new Innovator version.

Reusing Repositories

If you want to use the new and improved functions of the new Innovator version, you need to perform a transformation of the repositories in order to be able to reuse them in the new version.

The transformation of repositories is embedded in a certain sequence of work steps that are required for the migration of model data and settings in the current Innovator version when an update takes place.

Note

For a detailed description of the work steps, see the migration manual, which is available in this help as a browse sequence and as PDF in the customer area.

Alternatively, you can continue to use repositories in the corresponding predecessor version - even with project licenses - without a migration, and transform them later if required.

Attention

If you want to use your own base and add-on templates (profiles) from a previous version for models in the current version, it is preferable that you transform a master data repository which contains all templates in the form of master models. You can then export the configuration files from the newly-transformed master models.

See the Migration manual for a detailed description of this.

Please check the Migration manual for information on how to use the transformer in the command line.

Transformation of Data Repositories or Model Versions

Prerequisites

The transformation can be performed once:

The current Innovator version has been installed
The current main license server is running
The repositories (model servers) to be transformed have been closed in the predecessor versions

Context

The transformer makes extensive changes to all components in the program that are included within the scope of delivery if required by further development that has taken place in Innovator. This means you do not have to carry out any automated customizations.

Any customizations you may have made are created in many situations and automatically converted. However, there are certain customizations that cannot be adopted as standard.

Transformation can occur consecutively for various repositories.

You can also use the transformer in the same way as with data repositories when transforming model versions. Select the appropriate data type.

If you select a sub directory under \inoprj as source directory, then this is automatically adopted as target directory.

How to proceed

Start Transformer (inotrans.exe).

The dialog of the same name appears.
Select the Data Repositories entry from the Type drop-down list.
Select the 15.2 version in the Source group and use the button to select the source directory if it is different from the directory suggested.
If necessary, enter a pattern for constraining repository selection. You can use asterisk as wildcards.

The list is limited accordingly.
Select one or more 15.2 repositories from the Repository list.

If you select precisely one repository you can then enter a new name in the Target group; if this is not the case, the repositories' names are adopted.
Select the target directory (which differs from the source directory) for the repositories from the Target group.
If you have selected precisely one source repository, then you can enter a new name for Innovator's 16.0 target repository in the Repository field.
Click on Apply to start transforming data.

The transformer converts the source repository/repositories for Innovator into the data format used for Innovator 16.0.

You then need to adopt the content of the change set when transforming the data repository. An additional progress bar appears for this.

Once the transformation has taken place, check whether your model data has been successfully adopted into the new repository.