The page provides instructions on upgrading an existing installation of Liberator, and should be read in conjunction with Installing Liberator.
These instructions are not suitable for upgrading from Liberator 6.x to Liberator 7. For more information, see Upgrading to Caplin Platform 7.
Liberator 6.2 must be deployed on Deployment Framework 6.2.
Liberator 7 must be deployed on Deployment Framework 7.
|You cannot use these instructions to upgrade from Liberator 6.x to Liberator 7. See Upgrading to Caplin Platform 7.|
To upgrade an existing installation of Liberator, follow the instructions below.
Stop all components running under the Deployment Framework:
Copy the Liberator installation file to
Deploy the new version of Liberator:
As part of deployment, the Deployment Framework copies configuration-override files for the new version of Liberator to the
<Framework-root>/global_config/overrides/Liberatordirectory. Existing configuration-override files are not overwritten. When a file cannot be copied because an older version of the file already exists in the
<Framework-root>/global_config/overrides/Liberatordirectory, the Deployment Framework prints a warning to the console.
Confirm the new version of Liberator has deployed correctly:
If any configuration override files failed to copy in step 3 above, compare the current override files with the override files from the newly deployed Liberator, and manually update the current configuration override files.
See the release notes for the new version of Liberator to learn about new configuration items included in the new version.
The current configuration override files for Liberator can be found at
The configuration override files for the newly deployed Liberator can be found at
Restart the Deployment Framework
Test your upgraded installation of Liberator. See Installing Liberator: Test your installation.