MSI Repackaging - Overview

The conversion process involves several steps:

The Repackager displays the variables contained in the "legacy application" package. These variables are adopted as public properties into the MSI-based software.
Fixed default values must have been defined for the properties in the MSI-based software. The Wizard suggests default values (if the variables can be resolved). You can change these default values.
The Repackager analyzes the "legacy application" package and displays the analysis results, e.g. what commands in the original package cannot be converted.
Using the eScript package commands that can be migrated, the Repackager generates an MSI-based software (MSI file *.msi).
The commands of the original "legacy application" package that cannot be adopted into the MSI-based software are adopted unchanged into the new MSI Package.
If the associated program files are less than 10 MB, the program files will be stored inside the MSI file. (The repackager will create internal .CAB files.) Otherwise, the program files will be stored in the package directory’s Extern$ subdirectory.

The MSI Package is stored in the package directory.