Introduction
If you have uninstalled a CAST Imaging installation and have retained the existing application data on disk, then it is possible to reuse this existing data with a brand new installation of CAST Imaging (rather than perform an in-place upgrade). This process is described below.
Step 1 - Run the install
Microsoft Windows (traditional installer)
Follow the process for a brand new "from scratch" installation as described in CAST Imaging installation on Microsoft Windows: when the installer prompts you to choose a storage location for the configuration files and application data, ensure that you enter the locations of your existing data. If you did not customize these locations in the previous installation, then the default locations in the installer can be left as they are:
Click to enlarge
Then allow the installer to complete and then check that all services are running as described in CAST Imaging installation on Microsoft Windows.
Docker installer
Follow the process for a brand new "from scratch" installation as described in CAST Imaging installation for Docker on Linux or Microsoft Windows: when you run the imagingsetup command to run the installer, ensure that you are installing to the location of the existing data from the previous installation. Then allow the installer to complete and then check that all Docker containers are running.
Step 2 - Migrate the data (optional)
A structural change has been implemented in CAST Imaging 2.18 to the Neo4j database in which the CAST Imaging data is stored, primarily to improve performance and this change requires that any existing data (i.e. applications imported in previous releases) is migrated to ensure that it matches the new storage structure. Therefore, if you are installing CAST Imaging ≥ 2.18 and you are re-using application data from CAST Imaging ≤ 2.17, you must manually run this migration process as described below:
Locate the following tool:
Microsoft Windows traditional installer: %PROGRAMFILES%\CAST\ImagingSystem\tools\Neo4jDatamigrate.exe Docker installer - at the root of the installation location (unless in a custom location): - Linux: /opt/CAST/container-support/Neo4jDatamigrate.exe - Microsoft Windows: C:\CAST\container-support\Neo4jDatamigrate.exe
Run this tool either by creating a batch script or by running it directly from a CMD window (ensure the CMD window is executed with elevated permission) using the following syntax:
--username neo4j_user --password neo4j_password --host neohost --port bolt_port --database neo4j --all --migrate
| Command | Mandatory? | Description |
|---|---|---|
| --username |  | Must be set to the Neo4j database username. By default this is set to "neo4j", which will be used if you omit this parameter. |
| --password | | Must be set to the Neo4j database password. By default this is set to "imaging", which will be used if you omit this parameter. |
| --host | | Must be set to the hostname/IP address on which your Neo4j database is installed. By default this is set to "localhost", which will be used if you omit this parameter. |
| --port | | Must be set to the port number on which your Neo4j database is listening. The installer will set this automatically to "7687" (but it can be customized), which will be used if you omit this parameter. |
| --database |  | Must be set to "neo4j". This parameter is mandatory. |
| --all | | Mandatory parameter. |
| --migrate | | Mandatory parameter. |
For example:
Microsoft Windows traditional installer / Docker installer on Microsoft Windows All commands: Neo4jDatamigrate.exe --username neo4j --password imaging --host localhost --port 7687 --database neo4j --all --migrate Mandatory commands only: Neo4jDatamigrate.exe --database neo4j --all --migrate Docker installer on Linux - Linux all commands: ./Neo4jDatamigrate --username neo4j --password imaging --host localhost --port 7687 --database neo4j --all --migrate - Linux Mandatory commands only: ./Neo4jDatamigrate --database neo4j --all --migrate
Step 3 - Login to CAST Imaging and check existing applications
Browse to the following location and login with a user that has the ADMIN role:
http://localhost:8083
Check that all applications are listed in the Admin Center and can be successfully accessed:
