1.0

1.0.2-funcrel

New Features

Summary	Details
Minimum version check introduced	Version checks have been added to both the CAST Console v2 Enterprise backup tool ("Console-V2-Node-Backup-Enterprise.exe") and the "Cast_Imaging_V3_Migration.bat" script to verify that the minimum required releases are installed: CAST AIP Core 8.3.54 and CAST Console 2.11.0.
Support for CAST Imaging v3 deployed with HTTPS	The migration tool now supports CAST Imaging v3 deployed with HTTPS via the "–usehttps" option defined in the "migration.conf" file.
Support for custom persistence data schema name backup for CAST Console v2 Enterprise	If your CAST Console v2 Enterprise installation uses custom schema names instead of the default "aip_node" and "aip_config" schemas, the "Console-V2-Node-Backup-Enterprise.exe" tool now supports two new options to specify these custom names: "–nodeschema" and "–configschema".

Feature Improvements

Summary	Details
Force option for CAST Console v2 Enterprise backup	The CAST Console v2 Enterprise backup ("Console-V2-Node-Backup-Enterprise.exe") process can now be run in "force" mode via the option "–force" - i.e. the backup will continue regardless of any errors.
Improved options for migration tool	The "migration.conf" tool used by the migration tool contains various new/updated options: "–casthomedir" has been renamed "–cast84homedir" to avoid confusion, "–backup" and "–backupdir" have been introduced to allow the V3 data persistence schemas to be backed up before the migration starts.
Improved check only option for CAST Console v2 Enterprise backup	The CAST Console v2 Enterprise backup ("Console-V2-Node-Backup-Enterprise.exe") process can now be run in "check only" mode via the option "–reportonly" - i.e. only checks are run and no backup is performed.
Compatibility Inspector can be output during the CAST Console v2 Enterprise backup	It is now possible to output the Compatibility Inspector to file as part of the CAST Console v2 Enterprise backup ("Console-V2-Node-Backup-Enterprise.exe") process via the option "–validationreport".
Improved log messages	Logging has been improved to remove contradictory messages such as "Operation failed" followed by "Operation finished successfully".

Other Updates

Internal Id	Details
IMAGMIG-19	Improved application filtering now output by the Compatibility Inspector (or –validationreport option) to check for invalid application schemas and empty applications that will cause the migration to fail. Applications that fall into this category will have the status "Excluded" and issue should be investigated before a migration is started..
IMAGMIG-18	Improved health checks on target CAST Imaging v3 installation: now also checks values stored in the persistence schemas as "keycloak.uri".

Resolved Issues

Customer Ticket Id	Details
53525	Improvements made to add as many checks as possible during the backup phase (invalid application schemas, empty applications) etc. that will cause the migration to fail.
53773	Fixes an issue where executables were not working on Windows Server 2019.
53744	Fixes an issue where a null value is erroneously created in the "created_date" column in the "application" table in the CAST Imaging v3 schema "admin_center" after migration.

1.0.1-funcrel

Feature Improvements

Summary	Details
Health check timeout improvement	Health check timeouts for Imaging v3 services have been increased from 5 seconds to 60 seconds to allow for more reliable service monitoring.

Resolved Issues

Customer Ticket Id	Details
52730	Resolves a migration failure that occurred when Imaging v3 was configured with HTTPS. The migration tool now supports HTTPS connections to Imaging v3 on port 443.

1.0.0-funcrel

Note

Initial release of the extension: a set of command line tools to migrate your data to CAST Imaging v3. See the migration documentation for more details.

Known Issues

Internal Id	Details
IMAGKSL-2296	The migration will fail on the "Neo4j" migration step when the migration batch is executed in same CMD window as used by the "Neo4j" backup process (in other words, this can occur when the CAST Imaging "viewer" v2 and the CAST Imaging "viewer" v3 components are installed on the same machine. Ensure that the migration batch file is run in a new CMD window (i.e. not the same window used for the Neo4j backup).
IMAGKSL-2330	Applications containing only EGL technology (which is unsupported in v3), will still be eligible (incorrectly) to undergo a re-scan in CAST Imaging v3 (post migration) resulting in an empty Overview page.

Internal Id

Details

IMAGKSL-2296

The migration will fail on the "Neo4j" migration step when the migration batch is executed in same CMD window as used by the "Neo4j" backup process (in other words, this can occur when the CAST Imaging "viewer" v2 and the CAST Imaging "viewer" v3 components are installed on the same machine. Ensure that the migration batch file is run in a new CMD window (i.e. not the same window used for the Neo4j backup).

IMAGKSL-2330

Applications containing only EGL technology (which is unsupported in v3), will still be eligible (incorrectly) to undergo a re-scan in CAST Imaging v3 (post migration) resulting in an empty Overview page.