The page provides instructions on upgrading an existing installation of Liberator, and should be read in conjunction with Installing Liberator.

Contents:

## Requirements

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.

1. Read the release notes for the new version of Liberator and all versions in between the currency deployed version and the new version. Take note of any extra upgrade steps.

 To find the version number of the installed blade, run the `./dfw versions` command.
2. Stop all running Caplin Platform components:

``$./dfw stop`` 3. Copy the new Liberator installation kit to the Deployment Framework’s `kits` directory. 4. Deploy the new kit: ``````$ ./dfw deploy

Deploying Liberator kit Liberator-7.1.9-313149-x86_64-pc-linux-EL6-gnu.tar.gz
Kit will be saved in kits/archive.
Remove unpacked kit directory - Liberator-7.1.6-312215 (y/n) ? n (1)
Kit successfully unpacked.
is the same version as the kit just deployed.
Not copying override file cfgauth.conf from kit (2)
Not copying override file cluster.conf from kit
Not copying override file javaauth.conf from kit
Not copying override file java.conf from kit
Not copying override file jmx.conf from kit
Not copying override file openauth.conf from kit
Not copying override file rttpd.conf from kit
Not copying override file snapshot.conf from kit
Not copying override file tokenauth.conf from kit
Not copying override file xmlauth.conf from kit

Please review the Liberator release note and merge these files if required.``````
 1 The Deployment Framework prompts you to remove the previously unpacked kit directory (`kits//-`). Removing the unpacked kit directory does not remove the blade’s override files copied to `global_config/overrides/`. 2 Override files from the new version of the blade are not copied to the directory `global_config/overrides/` if they would overwrite existing files in that directory.
5. Check the blade installed correctly by listing all installed blades and their versions:

``$./dfw versions`` 6. Check if there have been any changes introduced to the override files in the new version of the blade. Manually merge any changes to the override files under the `global_config/overrides/<blade_name>` directory. To check for changes to override files between versions of a blade, download the installation kits for both versions, unpack the kits, and use the `diff` command to compare override directories. ``````$ tar xzf Liberator-7.1.6-312215-x86_64-pc-linux-EL6-gnu.tar.gz
$tar xzf Liberator-7.1.9-313149-x86_64-pc-linux-EL6-gnu.tar.gz$ diff Liberator-7.1.6-312215/etc/overrides/etc \
> Liberator-7.1.9-313149/etc/overrides/etc``````

If the `diff` output reveals that a new configuration item has been introduced, check the blade’s release notes for guidance on its use before copying the configuration item to the appropriate file under the `global_config/overrides/<blade_name>` directory.

 The override files for Liberator 6 and Transformer 6 were packaged with the Deployment Framework 6. From Liberator 7 and Transformer 7, the override files are packaged in the `etc/overrides/etc` directories of the Liberator and Transformer deployment kits .
7. Restart Caplin Platform components:

``\$ ./dfw start``