Migrate Configuration

Click here to see this page in full context

migrating a configuration

proiv dashboard

Migrating a Configuration

The Configuration Migrator form gives you the ability to migrate configuration files from a previous PROIV release and upgrade them for use in the current install. The expected starting point is a freshly installed version of PROIV with only a Base deployment.

On the bottom left of the navigation panel, click the Migrate (↑) button next to the Migrate Configuration.
The Configuration Migrator dialog appears.

This displays a list of Default Port Numbers from the installed version. These will replace the port numbers in the configuration that is migrated.
The Default Proiv Home File Path is shown. This will be used to replace the equivalent path in the migrated configuration.
Click the Browse button and select the JSON configurations files that you want to migrate. This must include the Base default file, application.json. On selection, a list of the chosen configuration files is displayed.
The Run Migration button is now enabled.
Click Run Migration.
At this point the configuration files are uploaded to the server. They are run through a configuration upgrade that moves them from their original version to the currently installed version. The port number and home path replacements are then applied.
A Confirm Configuration Migration dialog is shown. This lists all the changes that will be applied to the files. The Cancel Migration button allows you to rewind the whole upload and return to the initial installation.
Click Complete Migration to finalize the migration. Existing configuration files will be moved to a backup folder under the SystemServices installation. The amended files will be moved into the live config folder and the application redeployed with the new settings.

Deploying a Configuration

The migrated configurations along with the profiles (if any) are automatically added to the list of deployments in the Deployments page. By default, the components of the newly migrated non-base configurations are disabled for deployment. Check and amend the new configurations as needed. To deploy a component, you must turn ON the slider. Refer to Working with Deployments for more information.